If a broken price list got imported, the log shows what went wrong, and re-importing the correct file restores the price list products and catalog prices. No need to fix rows by hand.
When you need this:
- You can't tell what went wrong — the source log shows rows read and rows without a price per run.
- You need the price list products back — the correct file replaces all rows; matches and rules reapply automatically.
- The bad run reached the catalog — after the correct file, a new catalog update restores prices.
Where to start: source card → “Log” tab → compare the bad run with the previous one.
What you can fix
Stop rules work in advance: they either cancel an import or let it through with a warning. If a run has already gone through and the data is broken, here is what to do.
- See what went wrong — the log keeps the last 200 runs of the source.
- Restore the price list products — import the correct file again; no need to fix rows by hand.
- Restore prices in the catalog — run the base catalog update again.
How to see what the bad run broke
The log shows exactly what the bad run did. The “Log” tab keeps the last 200 runs of the source — older entries are deleted automatically. Compare the bad run's row with the previous one:
- “Loaded” — how many rows were read from the file;
- “In price” — how many of them remained after the rules;
- “No price” — how many came without a price;
- “Deleted” — how many were removed by ignore rules.
A sharp jump in “No price” is a typical sign that the price column shifted in the file; the log highlights a run in which every item came without a price on its own. Learn more: Price list log.
1
Loaded2
In price3
No price4
Deleted- Loaded — how many rows were read from the supplier file in this run.
- In price — how many products remain in the price list after the run.
- No price — how many products ended up without a price.
- Deleted — how many products were removed from the price list in this run.
How to restore the price list products
Importing the correct file again restores the price list products. Since every run replaces the source rows completely, you never get “mixed” data: after importing the correct file, the “Products” tab contains exactly what is in that file. You don't need to find and fix broken rows one by one.
You don't need to match products again either: manual links, category rules, ignore rules and markups are stored separately from the rows and are applied again automatically. Learn more: what a repeat import replaces.
Elbuz doesn't keep the previous file. A source holds one file, and a new one replaces the old one. So you will have to get the correct file from your supplier — from an email, via a link or from their customer portal.
How to restore prices in the catalog
If the bad run has already made it into the catalog, you restore it the same way: first import the correct file, then run the base catalog update again with the “Update my catalog” button. A manual import of one source doesn't update the catalog by itself (when prices reach the catalog).
Products already deleted by the “Days a product stays current; after that it is deleted” step won't come back this way — you will have to add them to the catalog from the price list again.
You can restore individual field values of catalog products only from the change history, and only if it was turned on before the run. Learn more: If a nightly run has already broken your data.
Scenarios
The price column shifted in the file
What to do. The log shows a sharp jump in “No price”. Compare the mapping in the “Columns” section of the source card with the new file, fix the price address and click “Import”.
What you get. The price list rows are replaced completely and the prices come back. How to map columns: How to map columns.
Your supplier has sent a broken file before, and price list prices must not break again
What to turn on. Stop rules with the “Block” action: the next file that crosses the threshold won't get into the source products, and the previous data stays in the database. Which rules to use and with which thresholds — see Stop rules and supplier price control.
FAQ
Can I go back to yesterday's price list file?
No. A source holds one file, and a new one replaces the old one. Get the correct file from your supplier and import it again.
Do I need to match products again after the correct file?
No. Manual matches, category rules, ignore rules and markups are stored separately from the price list rows and are applied again during import.
Will a stop rule cancel an import that has already gone through?
No. Stop rules check the file before import. A completed run is fixed by importing the correct file again.
How many past runs can I see in the log?
The last 200 runs of the source; older entries are deleted automatically.
Products were deleted from the catalog after their days of being current ran out — can I restore them?
No, there is no rollback. Add such products to the catalog from the price list again, as new ones.
Where to find it and who has access
- Menu
- Directories → Processing price lists → List of price lists
- Run log
- source card → “Log” tab
- Repeat import
- source card → “Import” button in the header
- Access right
- “List of price lists” window
- Have ready
- the correct file from your supplier
Related topics
- If you need the full picture from file to website — How to upload a supplier price list to Elbuz.
- If you want a broken file not to be imported next time — How to keep price list errors off your website.
- If the numbers in a run row are unclear — Price list log.
- If prices are fixed in the price list but the catalog still shows the old ones — When prices reach the base catalog.
