↑↓ selectEnter openEsc close

    1. Elbuz

    How to find out which products ignore rules removed

    3 min readUpdated

    Elbuz records every item an ignore rule deleted from a price list: name, SKU, price and the rule. No guessing why a product vanished — the log shows it.

    When you need this:

    • A product vanished, but no rule seems to cover it — “Field” and “Value” show which rule fired.
    • Checking a new rule — after an import, the log shows what it caught.
    • Finding a specific deleted item — export the log to CSV, search in Excel.
    • A run broke off — the log and counters show what fired.

    Where to start: turn on “Log deleted products” in the price list card and import the price list.

    What the deleted products log does

    How to see what the rules deleted

    Ignoring works silently: the import log shows only the total number of deleted items. If you need to know not “how many” but “what exactly”, turn on the log.

    Turn it on first

    The checkbox isn't in this window but in the price list card: the “Products” section, the “Cleanup and service” subsection, the “Log deleted products (ignore rules)” checkbox. Its tooltip is upfront about the cost: “Record all products deleted by the ignore operation. Enables diagnostics, but slows down price list loading.”

    Cleanup and service subsection of the Products settings in the price list card
    1Log deleted products (ignore rules) checkbox
    1. Log deleted products (ignore rules) — the second checkbox of the Cleanup and service subsection; it is off for this source.

    It's off by default. It's a troubleshooting tool, not for constant monitoring: turn it on, import the price list, take a look, turn it off.

    Order matters: the checkbox first, then the run. The log is filled at the moment of deletion, so turning it on after products have disappeared won't show you what they were: those rows are no longer in the price list.

    What the log shows

    The “Deleted products log” window opens with the list button on the button bar — it's there only in a specific price list's mode. At the top are two counters: “Total records” and “Last deletion” with a date.

    Deleted products log window with the record counter, toolbar and grid column headers
    1Total records counter
    2Rule type column
    3Export to file (CSV) button
    1. Total records counter — shows how many deleted products the log holds.
    2. Rule type column — shows which kind of rule removed the product.
    3. Export to file (CSV) button — downloads the log as a CSV file.

    Each row is one deleted product: when it was deleted, by which rule type, by which field and value, followed by the item itself: name, SKU, supplier SKU, manufacturer, supplier category, price.

    The “Rule type” column has four values, and it tells you at a glance where the deletion came from: “By keyword” — a rule from the “Keywords” tab, “SQL: price list” — a logical condition of this price list, “SQL: sheet” — a sheet condition, “SQL: global” — a global condition.

    The export button gives you the whole log as a CSV file — Excel opens it, and it's handy for finding a specific item. The trash button clears this price list's log: “Clear all log records for this price list?”.

    The log lasts one run. Every import and every click on “Apply rules to products” with the checkbox on erases this source's previous records, and they can't be restored. Need history across several runs? Export a CSV after each one.

    What remains if a run breaks off

    Applying rules isn't “all or nothing” — neither from the button nor during an import. Each rule runs as a separate step: if the log is on, the rows the rule matches are first copied to the log and then deleted from the price list. Rules run one after another in the usual order.

    A run from the “Apply rules to products” button breaks off

    • Rows. What the rules deleted before the break is gone from the price list. Rules not yet reached didn't fire — their rows stay.
    • Deleted products log. It has records from all rules that finished. Since a record goes to the log before deletion, it may also contain an item from the rule where everything stopped, even though that item is still in the price list.
    • Price list counters are recalculated only at the very end of a run. If it broke off, the item count in the list of price lists stays old until the next run or import that reaches the end.
    • Clicking again is safe: the rules go over the remaining rows, and nothing already deleted is deleted twice or duplicated. But with the log on, a repeat first erases the broken run's records, so the log keeps only items the repeat deleted. Need the full list? Export a CSV before clicking again.
    • If the server returned an error, the “Processing data, please wait” toast disappears and a red message with the error text shows for a few seconds. The button is active again and the indicator next to it hides — click it right away, no need to reopen the window.

    A price list import breaks off

    During an import, the rules work on a temporary set of rows from the new file, not on the price list rows. These rows move into the price list only after the whole chain of operations finishes. If the import breaks off earlier, no new rows reach the price list, filtered or not.

    The app removes old price list rows at the start, as soon as the file it read contains products. Exception: a price list with a stop rule in “Block” mode keeps old rows until the new file is checked. So after a break, a price list without such a stop rule may stay empty until the next complete import.

    The deleted products log is never temporary: the ignore operation itself erases and fills it. If the import broke off after it, the log shows items removed from the new file, though the file never reached the price list. The import log gets the “Products removed:” line only when the ignore operation finishes.

    A repeat here is a new import: the file is reread and all rules apply from scratch.

    Scale limits

    • There's no cap on the number of rows. Each rule is one delete query across all price list rows, without splitting into batches. The number of rules in a run isn't limited either.
    • A manual run doesn't go to the background queue. It runs within the request from the open window, and “Done” appears once the server has gone through all rules. The “Processing data, please wait” toast shows for at most 200 seconds: if the run takes longer, the toast disappears and the button stays greyed out until the server responds.
    • The log doubles each rule's work. With “Log deleted products” on, a rule goes over the rows twice — first copies matching rows to the log, then deletes them. Without it, there's one pass. That's what the checkbox tooltip warns about.

    Scenarios

    A product vanished from the price list — find the rule and bring the product back

    What to do. Turn on “Log deleted products”, import the price list and open the log. Find the item, and in the “Rule type”, “Field” and “Value / Rule SQL” columns — the rule that removed it. In the rules window, clear its “Active” checkbox or fix the value, and import the price list again.

    What you get. The row returns to the price list with the supplier's file, if the supplier still sends it. Ignoring doesn't touch your catalog: a product that was already in the catalog never disappeared from it.

    Keep deletion history across several runs

    What to do. After each import, export the log with the “Export to file (CSV)” button.

    What you get. Each file is the list of what was deleted in one run: the next import or “Apply rules to products” erases the source's previous records.

    What to do when the log is empty

    The deleted products log doesn't show what you expect
    What you seeWhyWhat to do
    The log is empty, although products were deleted The “Log deleted products” checkbox is off; or the log has already been overwritten — both the next price list import and the next click on “Apply rules to products” erase it Turn the checkbox on in the price list card and run an import (deleted products log)

    FAQ

    Can I restore a product from the log in one click?

    No: the log toolbar has only “Refresh”, “Clear filter”, “Export to file (CSV)” and “Clear log for this price list”. How to bring a product back — see the scenario.

    Can I see what was deleted yesterday if the log was off?

    No. The log is filled at the moment of deletion, and rows already deleted are no longer in the price list. Turn the checkbox on and import the price list again.

    Does the log slow down the import?

    Yes: with the checkbox on, each rule goes over the rows twice — copies them to the log, then deletes them. Turn the log on while troubleshooting, then turn it off.

    Where can I see how many products were deleted without the log?

    In the import log, the “Products removed:” line with a number. A second such line is the pass of rules narrowed by your catalog categories.

    Do log records come back after a rule is removed?

    No. Log records aren't restored by removing the rule or by a new import: the price list's log is cleared before every run.

    Where to find it and who has access

    Log
    “Ignore rules” of a specific price list → the “Deleted products log” button
    Turn on
    price list card → “Products” → “Cleanup and service” → “Log deleted products”
    Access right
    the same access as to the “Ignore rules” window
    Prepare
    turn the checkbox on before the import: the log isn't filled retroactively

    The log has no menu item: it opens only with a button in the price list's rules window. How to open the rules window — see the main article.

    Related topics

    Was this article helpful?

    Missing a feature? Tell us.

    We will add it for free if other users need it too.

    If only you need it, we will agree on it separately.

    Article contents

    Suggest an improvement

    Try Elbuz free