For each import, Elbuz counts what the supplier sent: items, items without a price, items priced above or below your catalog — next to previous runs. You see if the supplier cut the range or something got lost.
When you need this:
- Fewer items — the “In price list” tile and the “Loaded” history column show rows read and rows left.
- Products without a price — the “No price” tile turns yellow; if no row has a price, the run's cell turns red.
- First time or a month already? — six charts cover the last 50 runs.
Where to start: the source's “Log” tab → the “In price list” tile.
What the log numbers show
- Last run tiles — how many products are in the price list, how many have no price, how many your rules removed.
- Prices vs. catalog — how many price list items are priced higher or lower than in your catalog.
- Run history — the source's last 200 imports with the status and numbers of each.
- Charts — how volume, prices, reliability, duration and catalog coverage changed over 50 runs.
What the supplier sent this time
The row of tiles below the health card shows the numbers of the last run. They answer the question “what came in”.
“In price list” — how many rows remained in the price list after the import. It's the main number of the whole log, and you should read it next to the previous rows of the history table: 1468 today vs. 1475 last time is normal, 322 vs. 580 is a reason to open the file.
An item missing from the new file is gone from the price list after the import: it doesn't stay with zero stock and isn't flagged separately.
As soon as at least one product row is read from the new file, the program deletes all old rows of this source — along with attributes, photos and warehouse stock — and writes what arrived in their place. So “In price list” is always the content of the latest file, not an accumulated list.
Old rows stay in two cases. If no product row was read from the file, the deletion doesn't start. If a stop rule set to “Block” canceled the transfer, the price list stays as it was before this run.
All log numbers describe the source's price list, not your catalog. Prices and availability in product cards are changed by a separate step — the base catalog update.
After importing one source, start it with the “Update my catalog” button in the source header; after importing all price lists, the “Update catalog after import” setting runs it. More in How to update your catalog from supplier price lists; what happens to a product that's gone from every price list — Whose price goes to the catalog.
“No price” — how many items arrived with a zero or negative price. The tile turns yellow as soon as the value is above zero.
A special case: if “No price” equals “In price” — that is, nothing has a price at all — the “No price” cell in that run's row is highlighted in red.
It's a classic sign that the price column got shifted: the supplier rearranged the columns in the file, but the column addresses in the card stayed the same. If the program has seen this price list's headers before, it will tell you itself with the line “Price columns have moved” in a yellow banner (about column shifts).
1
In price list2
No price3
Deleted4
Suspicious- In price list — rows that remain after all ignore rules are applied.
- No price — rows without a usable price.
- Deleted — rows removed by the ignore rules, not lost products.
- Suspicious — stays at zero unless the price-jump check is turned on; it is off by default.
“Deleted” — and this is where the most common misreading starts.
“Deleted: 527” doesn't mean the supplier stopped selling 527 items. This tile counts exactly one thing: how many rows your own ignore rules removed during this import. The supplier sent them as usual — you set up a rule once, and it drops these items from the file every time.
So this number tells you about your settings, not about the supplier. If it stayed at 527 and suddenly became 900, the supplier didn't cut anything — your ignore rule started catching too much, most often because the supplier renamed a category or added a word to product names.
How many rows the file actually had is shown in the “Loaded” column of the history table — the number of raw rows read from the file before any processing. The difference between “Loaded” and “In price” is everything filtered out along the way: ignore rules, duplicates and filters.
For the source in the screenshot above, it looks like this: 592 rows were read from the file, ignore rules removed 257, 322 remained in the price list — duplicates and filters removed the rest.
How price list prices differ from your catalog
Two neighboring tiles — “Catalog higher” and “Catalog lower” — compare the price list price with the price of the same product in your catalog: the first counts items whose catalog price is higher than the price list price, the second those where it's lower.
Together they show how far the price list drifted from your prices this time: if almost all items suddenly land in one of them, the supplier rewrote prices in bulk. Items not yet linked to your catalog aren't counted — there's nothing to compare. Products with a locked price count here; only “Suspicious” skips them.
Before drawing conclusions from these two tiles, check them on one product: open the source's “Products” tab and compare the supplier's price with the price of the same item in your catalog. One check per source — and from then on you read the pair of tiles with confidence.
“Suspicious” — a tile that turns red as soon as the value is above zero. And for almost everyone it always shows zero.
Zero in the “Suspicious” tile doesn't mean “prices are fine”. An item is marked suspicious only when the “Product price deviation from catalog” stop rule is on, and it's off by default. While the rule is off, the tile simply can't show anything but zero.
How this rule works and why it catches only price increases — Price list stop rules.
How to compare with previous imports
Further down the tab, below the charts, is a table where each row is one , newest first.
Eight columns: “Date”, “Status”, “Format”, “Loaded”, “In price”, “No price”, “Deleted”, “Time”. The “Format” column shows xml for XML sources, parser for site parsers and the file extension for the rest; a duration under a minute is shown in seconds, a longer one as “2 min 14 s”.
1
Loaded rows2
Rows left in price3
Blocked run4
Run time- Loaded — raw rows in the file.
- In price — rows that remained after the rules.
- Blocked — the file was rejected and the previous data is shown.
- Time — how long the run took.
| Status | What it means |
|---|---|
| “Done” | The step-by-step log of this price list has no error rows |
| “Error” | At least one step ended with an error. The run's numbers can still look perfectly normal: part of the work was done |
| “Blocked” | A stop rule canceled the data transfer; “previous data shown” is added under the badge. “In price” and “No price” are old, “Loaded” and “Deleted” come from the rejected file: “Loaded 2249 · In price 26” is normal here |
| “Canceled” | The run was stopped with the “Stop” button or was found dead |
| “Running” | The run is open and not closed yet |
“Running” deserves a separate note. The import process can break off without closing its row — and then the run will stay in this status indefinitely.
The program fixes this itself, but not on a schedule — when you open the “Log” tab: each time, it checks runs older than fifteen minutes and moves dead ones to “Canceled”.
A run counts as alive if its process is alive and it wrote something to the log in the last fifteen minutes. So a stuck “Running” goes away by itself — but only after someone opens the tab to look.
- Start
- State
- End
The page shows 50 runs. The “Show more” button appears only when there are exactly 50 and loads the next 50; when the server returns fewer, the button disappears — the history has ended.
The program keeps the last 200 runs per source. Cleanup runs at the start of each import — run 201 pushes out the oldest. The limit is per source, not per account: a source no longer imported keeps its 200 rows indefinitely. The log can't be exported to a file, and what's pushed out doesn't come back.
Is it the first time or has it been like this for a month: charts
Above the table is the chart block. All six charts are built from the same 50 runs of the first page, in chronological order from left to right. The table answers “what happened this time”, the charts — “is it the first time or has it been like this for a month”.
1
Run reliability2
Stop-rule frequency3
Catalog coverage- Run reliability — share of successful runs.
- Stop-rule frequency — which rules fired and how often.
- Catalog coverage — percent of price list products matched to the catalog.
- “Price list volume and products without price” — the bars show “In price”, the red line “No price”. A line that has risen to the height of the bars means prices are no longer being read.
- “Price change vs catalog” — three series of bars: “Catalog higher”, “Catalog lower” and “Suspicious”. It's a per-run total, not the price history of a specific product.
- “Run reliability” — a donut with the status breakdown. Done is green, Error is red, Blocked is amber, Canceled is gray; statuses that didn't occur aren't in the donut. “Running” never gets into it, even if there are such rows on the page.
- “Stop-rule frequency” — how many times each rule triggered over these 50 runs. If none ever did, the chart is replaced by the line “Stop rules have never triggered”.
- “Import duration, sec” — the time of each run. A sharp rise means the supplier started sending a noticeably larger file or their server responds more slowly.
- “Catalog coverage, %” — the share of price list rows that have a match in your catalog. A drop means the price list now has more items that don't match anything you have yet.
1
Stop rules have never triggered- Instead of a chart, the card shows that no stop rule has ever triggered for this source.
Below the block is a permanent hint that briefly names the two most common causes of spikes: “A sharp rise in “No price” likely means the price column shifted during load. A spike in “Suspicious” is a sharp price jump (e.g. the price-list currency changed).”
Scenarios
The price list has noticeably fewer items
What to do. Compare “Loaded” and “In price” with the previous history rows.
What you get. “Loaded” dropped — the file came in shorter, ask the supplier. “Loaded” is as before but “Deleted” grew — your ignore rules started catching too much.
The supplier rewrote prices in bulk
What to do. Look at “Catalog higher” and “Catalog lower” and check one product on the source's “Products” tab.
What you get. You see which way and for how many items prices diverged. To have such a file stopped automatically, set up a stop rule — Price list stop rules.
Prices are no longer being read
What to do. If “No price” equals “In price” and the red line on the chart has risen to the bars, check the column addresses.
What you get. Most often the supplier rearranged the columns; the program suggests new addresses itself — Price columns have moved.
What to do when run numbers look odd
| What you see | Why | What to do |
|---|---|---|
| “previous data shown” under the “Blocked” badge | A reminder that “In price” and “No price” in this row come from the previous successful import, while “Loaded” and “Deleted” come from the rejected file | Read this row as “there was no new data this time” (history table) |
| “Canceled” badge | The run was stopped with the “Stop” button, or it was silent for over 15 minutes and was found dead | If you didn't stop it yourself, the process broke off; run the import again |
| “Running” badge on an old run | The process died without closing its row | Just open the “Log” tab: the check runs every time and moves the row to “Canceled” itself (history table) |
| “Stop rules have never triggered” | No rule triggered in the 50 runs shown | Nothing: this is normal, the line replaces an empty chart (about the charts) |
| The “Catalog coverage, %” chart went down | The supplier added items to the file that you don't have yet, and dropped | Match the supplier's new items with your catalog (about the charts) |
FAQ
I clicked “Show more”, but the charts didn't change. Is it a bug?
No. The charts are always built from the first 50 runs, however many rows you load into the table. The history table gives the wider picture.
Can I export the log to a file for a report?
No. Each source keeps its last 200 runs, run 201 pushes out the oldest, and what's pushed out doesn't come back. If you need history for a report, record the numbers while they're still there (run history).
How do I find out which product disappeared from the price list?
Not from the log: it works with numbers. Look up specific items on the source's “Products” tab.
An item is missing from the new file. Will it stay in the price list with zero stock?
No. As soon as at least one product row is read from the new file, the source's old rows are deleted, and the price list holds only the content of the latest file (the “In price list” tile).
A “Blocked” row shows Loaded 2249 but In price 26. Is that right?
Yes. “Loaded” and “Deleted” come from the rejected file, “In price” and “No price” from the previous successful import. There was no new data this time (statuses).
Where to find it and who has access
- Menu
- Directories → Processing price lists → List of price lists → source → “Log” tab
- Access right
- the “Price lists” window (in the menu — “List of price lists”)
Other ways into the log — Price list log.
Related topics
- If you need the overall picture across all suppliers — Price list log.
- If a run was blocked or the price list came in empty — Price list import blocked or price list empty.
- If the history shows “Error” — Why a run ended with an error.
- If you want to see how a single product's price moved — Product price history.
