Elbuz records every catalog price change and charts it: when, by how much, minimum and maximum. Whoever changed it — price list, markup rule, marketplace, or a person in the card.
When you need this:
- A supplier raised a price, nobody recalls when — the chart shows the day and size of each change.
- Exchange-rate prices “change” by pennies daily — changes below the threshold stay off the chart.
- No time to check products daily — sharp jumps trigger a notification with examples.
- Need everything that got pricier? — filter the “Price dynamics” column in the product grid.
Where to start: turn on “Keep price history” in system settings.
What price history can do
- A chart and six tiles — current price, change over the period, minimum, maximum, average, and number of points.
- A point on the day of a change — the chart stores only changes, not daily price snapshots.
- A price check that runs without you — every night and after each catalog update from a price list.
- Minor-change threshold and retention period — up to 1095 days of history without penny-sized exchange rate swings.
- Price jump warning — a notification in the Operations center when a price changes by more than the threshold.
- A sparkline in the product grid and card — history is visible without a separate window, and “Catalog analytics” shows it for the whole catalog.
How to read the tiles and the chart
The window has no buttons — only numbers and a chart. At the top are six tiles:
- Current price;
- Change over period — the difference between the latest and the very first saved price, in money and as a percentage; the tile is red when the price went up and green when it went down;
- Minimum and Maximum;
- Average price;
- Price changes — the number of points on the chart, explained separately below.
“Average price” is calculated over points, not days. A price that held for six months weighs exactly as much in this average as a price that lasted one day. This average won't do for a report, but it's fine as a reference.
Below is the “Price dynamics” chart: two lines and one dashed line. “Price” with a fill, “Recommended price” — it appears only if the RRP is filled in at least one point — and a horizontal “Average”. Hovering over a date shows all lines for that day and the change from the previous point: “+120.00 (+12.50%)”.
1
Change over period2
Average price3
Price changes4
Step5
Recommended price6
Retention note- The change-over-period tile; its colour shows the direction of the change.
- The average price tile, calculated from the points, not from days.
- The price changes tile counts the points on the chart.
- A step: the line holds its level until the next change.
- The recommended price line appears only when the RRP is filled in.
- The line under the chart states the retention period.
Why a point on the chart is a day the price changed
Elbuz doesn't take a daily price snapshot: it records only what changed. The note under the chart says so directly: “A point on the chart is a day when the price changed; between points the price stayed the same.” Hence the stepped line and gaps of different lengths: neighboring points can be a day or three months apart.
Elbuz adds two points on its own, and without knowing about them the chart is easy to misread:
- The first one is the starting point. On the day history is turned on, the next price check saves the current price of every catalog product — otherwise later prices would have nothing to compare against. The start of the chart means you turned on history, not that the supplier did something to the price.
- The last one is today. Without it, the line would end on the date of the last change.
Three consequences people trip over:
- The chart appears before the first price change, but not on the day you turn history on. A starting point plus today's point is already a line, just a flat one. The window adds today's point only when the last saved one is older than today: on the day of the first check there's one point, and the line appears the next day. A flat line is an answer too: the price hasn't moved since history was turned on.
- The “Price changes” tile counts points, not changes. It includes the starting point, every price change, and today's point: a product whose price changed seven times shows 9 on the tile.
- One day, one point. If the price was changed in the morning and changed back by evening, history won't show it. Two updates in one day also give one point: the second overwrites the first. How many times the price list arrived doesn't affect the number of points.
“No data yet” doesn't always mean “history is building up”. It shows when there are fewer than two points, in three cases: the starting point was set today — the line appears tomorrow; the price is zero — such items aren't recorded; or the product was added after the last check and has no starting point yet.
When changes are recorded
Changes are recorded by the price check, and it starts on its own in two ways:
- every night at 4:10 AM — as a background scheduler task;
- at the end of each base catalog update from a price list — the update log shows the line “Updating price history, points today: N”.
The nightly check is needed because prices also change outside catalog updates: by hand in the grid, by pricing rules, by a field formula, or through marketplace sync.
Each check takes three steps in turn:
- deletes entries older than the retention period;
- adds points for products whose price or recommended price differs from the last saved one;
- recalculates the percentage of the last change shown in the grid next to the sparkline.
- Start or end
- Action or result
- Decision: the path depends on the answer
If the check broke off or didn't run, you don't need to start anything by hand. There won't be a duplicate for the day: history can hold only one entry per product per date, and a repeat check on the same day overwrites it.
If the price changed and there was no check that day, the next check — nightly or after a catalog update — compares current prices with the last saved ones and adds the difference. The change isn't lost, but the point gets the date of the check that recorded it.
The check has no limit on the number of products: each time it goes through the whole base catalog — every product with a price above zero. The volume of history is limited only by the retention period, at most 1095 days. Where history is displayed, there are limits of its own:
- the sparkline in the grid takes at most the last 30 points of a product and only for the last 365 days; the full history is in the window that opens on click;
- if a grid page has more than 300 rows, sparklines aren't drawn on it at all — reduce the page size;
- the overnight price jump warning counts all products that jumped — the notification title shows their real number — and gives up to five examples in the text.
How to turn on history and set the threshold and retention
Where: Account → System settings → “Price lists” section → “Import and parsing” subsection. All three settings are there.
Keep price history
The toggle that turns everything on, with the retention period field next to it. The period is set in days, from 1 to 1095, 180 by default. Entries older than this period are deleted by the first step of each check.
If you shorten the period, old entries disappear at the next check: nightly or right after a catalog update, whichever comes first. They can't be restored — history builds up from scratch. Before setting 30 days instead of 180, consider whether you'll need a comparison like “what was it in spring”.
Turning it off isn't the same as deleting. While the toggle is off, the check writes nothing and deletes nothing: the collected points stay in the database. The history window says “Price history is not being recorded”, and the sparkline in the “Price dynamics” column is empty.
When you turn the toggle back on, the chart returns with the same points, with two caveats:
- the very first check after turning it on deletes all points older than the retention period — including those that “outlived” it while history was off;
- there are no points for the time it was off. If the price changed during that time, the first check sets a point with its own date, and until then the line stays at the last saved price.
Skip minor price changes
A threshold in percent, 0.5% by default. It's needed because of exchange rates: prices recalculated by rate “change” by pennies almost every day without any decision by the supplier.
The threshold doesn't swallow gradual growth. The comparison is against the last saved price, so small steps add up and get recorded once together they exceed the threshold.
Warn about price jumps
A separate option on top of history, off by default. Once a day, Elbuz compares two neighboring points of every product. If the difference reaches the threshold (20% by default), a notification with a few example products arrives in the Operations center.
It's neighboring points that are compared: slow growth of a percent a week is normal catalog life, but a one-time jump is worth seeing.
1
Keep price history and retention period2
Minor change threshold, %3
Warn about price jumps- Keep price history — the switch and the retention period in days: records older than this are deleted automatically.
- Skip minor price changes — the threshold field in percent; changes smaller than this are not written to history.
- Warn about price jumps — off by default, turned on manually.
How to see history without a separate window
The same points are shown in three more places, and it's usually faster to look there.
The “Price dynamics” column in the product grid. A sparkline plus the percentage of the last change, and the hover tooltip reveals the numbers: what it was, what it is now, and the minimum and maximum for the period. The sparkline is drawn from three history entries, and a flat line is hidden.
Sorting and filtering work on this column, so it's handy for finding everything that got more expensive.
The “Product price history” chip in the product card, “Prices and stock” section: the same sparkline in the section header, and a gray icon instead when there are fewer than two entries. And the collapsible “Product price history” section in the product sidebar — the same chart in compact form, loaded when you click the header.
1
Price history chip2
Section title- The price history chip with the same mini chart; it opens the same window from the card.
- The section title, Prices and stock.
The “Catalog analytics” window reads the same history for the whole catalog at once: the “Price up” and “Price down” tiles, price movement by day, the top 10 products in each direction, and export of price movement to a file. If you need the full picture rather than one product, go there.
Scenarios
Find out about a sharp price increase without checking products every day
What to turn on: “Keep price history” and “Warn about price jumps” with a threshold in percent — from 1 to 500, 20 by default.
What you get: the nightly check compares today's point of each product with the previous one. If the jump either way reaches the threshold, the Operations center gets “Sharp price change: N products (threshold 20%)” with “Price up: …, price down: …” and up to five examples. Find them in “Catalog analytics” or with the “Price dynamics” column filter.
What you won't get: slow growth where each step is below the threshold won't trigger a notification. A catalog update from a price list doesn't send notifications — only the nightly check does.
Prices are recalculated by exchange rate, and the chart shouldn't drown in pennies
What to turn on: in “Skip minor price changes”, leave the toggle on — it's on by default — and set the threshold: from 0 to 50%, step 0.1, 0.5 by default.
What you get: a price change smaller than the threshold relative to the last saved point doesn't create a point. Small steps aren't lost: once together they reach the threshold, a point is recorded.
What you won't get: the threshold doesn't apply to the recommended price — if the RRP changed, there will be a point. The threshold also doesn't apply to a product with no points. Need every penny? Turn off the threshold toggle.
Compare prices with the same season last year
What to turn on: in “Keep price history”, set a retention period longer than a year — the field accepts from 1 to 1095 days.
What you get: points are kept until they reach that age. The “Product price history” window shows the whole series — it takes up to the last 1000 points of a product.
What you won't get: the sparkline in the “Price dynamics” column still shows only the last 365 days and no more than 30 points. Points for the time before history was turned on won't appear.
Prices are changed by hand or through marketplace sync, with no price lists
What to turn on: only “Keep price history”.
What you get: every night at 4:10 AM, the check compares current prices of the whole base catalog with the last saved ones and adds points for products whose price or RRP changed — no matter who changed them.
What you won't get: a point gets the date of the check, so a change made during the day lands on the chart with the next day's date. A price that was changed and changed back before night won't get into history.
What to do when there's no chart
| What you see | Why | What to do |
|---|---|---|
| “Price history is not being recorded” + “History storage is turned off, so there is nothing to show.” | The “Keep price history” option is off | Click “Turn on in settings” right in the window (three settings) |
| “No data yet” + “History is being recorded, but this product has no entries yet.” | The starting point was set today, the price is zero — such products never get into history — or the product was added after the last check | Check the product price and wait for the check: it sets the starting point, and the line appears the next day (how to read the chart) |
| The “Price dynamics” column is empty, although the price changed | The is drawn from three entries, and a flat line is hidden | Open the history window from the product card: the chart shows there even with two points (where else history is visible) |
| The chart has no “Recommended price” line | The RRP isn't filled in at any point | Fill in the recommended price — the line appears with new points (what the window shows) |
| The number on the “Price changes” tile doesn't match the number of changes | The tile counts points: the starting one, every change, and today's. Also, minor changes are cut off by the threshold, and each day gets one | Nothing; if you need penny-sized moves too, lower the threshold (how to read the chart) |
| History for old months has “disappeared” | The retention period has passed, and old points were deleted | Increase the period, up to 1095 days; deleted data won't come back (three settings) |
| “Sharp price change: 14 products (threshold 20%)”, “Price up: 11, price down: 3.” | The “Warn about price jumps” option was triggered | View the products in “Catalog analytics” or by filtering the “Price dynamics” column (where else history is visible) |
| The product sidebar has no “Product price history” section | The “Sidebar: competitor prices” block isn't granted | Grant the block, or open history from the grid (where to find it and who has access) |
| A yellow “ACCESS DENIED” sign instead of the window or the chart in the sidebar section | The group has no right to the “Product price history” window | Grant the group the right to this window (where to find it and who has access) |
FAQ
I turned on history — why is there still no chart?
The check hasn't run yet or ran only today: the first one after you turn it on sets a starting point for products, and the line appears the next day. If “No data yet” stays after that, check whether the product's price is zero.
Why are there fewer points than price list imports?
A point is set on the day the price changed, not on the day of the import: a price list can arrive every day with the same price and add nothing.
How do I see why the price changed?
Not in this window: the check sees only “before” and “after”. Look for the reason in “Product markup history” from the context menu of a product grid row (where the price came from).
Can I export a product's price history to Excel?
Not from this window: it has only the chart and tiles, with no period selection, and the figures for a day are shown in the hover tooltip. Price movement export is available in “Catalog analytics”, but for the whole catalog at once.
Will history appear for the months before I turned it on?
No. History starts on the day you turned on “Keep price history”: the first check sets the starting point, and earlier data will never appear.
Is history kept only for products from price lists?
No, the check goes through the whole base catalog: history includes manual edits in the card, the work of pricing rules, and marketplace sync.
Does history show the purchase price or supplier prices?
No. Your price and the recommended price are recorded: this is the history of a base catalog product, not of a price list row.
Does history show stock changes?
No. A change in stock quantity doesn't add a point: quantity changes almost every day and would turn the chart into a daily snapshot.
Where to find it and who has access
The window has no menu item or desktop shortcut: you open it from wherever the product is already shown.
- From the product grid
- the “Price dynamics” column → click the sparkline in the cell
- From the product card
- the “Prices and stock” section → the “Product price history” chip in the section header
- From the product sidebar
- the collapsible “Product price history” section
- From the product's “History” window
- the “Product price history” button
- Access right
- a separate right to the “Product price history” window; the sidebar section also needs the “Sidebar: competitor prices” block
- Before you start
- the “Keep price history” option is on; the chart appears the next day
Groups that had access to products have been granted the right to the history window. Without it, you see an “ACCESS DENIED” sign instead of the chart. Without the sidebar block, only the sidebar section disappears: history still opens from the grid and the card.
The fastest way is the base catalog product grid: the “Price dynamics” column shows a sparkline and the percentage of the last change, and clicking the sparkline opens the product's full history. The window title reads “Product price history: ‹product name›”, so with several windows open you can tell which is which.
1
Sparkline2
Column header- The sparkline shows the price history; clicking it opens the full history.
- The column header, which also drives sorting and filtering.
Related topics
- If the price changed and you need to understand how it was built — Pricing rules: how a supplier price becomes your price.
- If a field formula changes the price and a point on the chart surprised you — How to fill price list fields with a formula.
- If points appear after a catalog update rather than at night — How to update your catalog from supplier price lists.
