Elbuz drops what you don't sell from supplier price lists on import: those items never reach the price list or your catalog. This repeats with every file.
When you need this:
- The supplier sends their whole range — drop unwanted brands and sections by name, SKU or category.
- The file has blank rows and section “headers” — a default condition on every price list removes them.
- You don't want a brand from any supplier — one global rule covers all price lists.
- A rule caught too much — clear its checkbox; the next import brings the rows back.
Where to start: test your first rule on one price list.
What ignore rules can do
- Drop items by keyword — a price list field plus a value: name, SKU, manufacturer.
- Drop a whole supplier section — the matching branch of the category tree is cleaned up along with the products.
- Check several fields together — a condition with “and” and “or”, for example “price equals 0”.
- Apply to all price lists or to one — a global set and a set for each source.
- Can be added in bulk — from the price list product grid, from the category tree, or from an Excel file.
- Show exactly what was deleted — the deleted products log, with the rule type.
Global rules and rules for one price list
There is one window but two rule sets in it, and they are never shown together. Open it from the menu and you see only global rules, with the caption “Settings for all price lists are used” under the button bar. Open it from a source's card and you see only that source's rules; global ones aren't listed.
This affects display only. When a price list is imported, both sets run: global rules first, then the source's own rules.
To see everything at once, use “Show ignore rules from all price lists” — the database icon in the button bar. It exists only in global mode and simply removes the filter: the grid shows rules from all sources, and the “Supplier” and “Price list” columns tell you whose each one is.
Removing the filter doesn't change what the buttons act on. The “Delete all rules” menu item erases rules of the current window only, even when the screen shows rules from every price list.
In global mode that means global rules; in a source's window, that source's rules. Other rules stay put — which is more good than bad, but the result won't match what you saw on screen.
There is a third level too: rules for a single Excel sheet. If a price list has per-sheet settings turned on, you can open the window for one sheet, and its rules are visible only there.
How to drop products by keyword
A rule has two parts: a price list field and a value to look for in it. The hint under the button bar says the same: “Add a rule: pick a price field and enter a value — matching items will not be loaded into the catalog. The “Logical condition” tab is for complex SQL filters.”
1
Add2
Delete3
Apply rules to products4
Deleted products log5
Partial match- Add — creates a new ignore rule.
- Delete — removes the selected rules.
- Apply rules to products — runs all rules over the loaded rows.
- Deleted products log — shows what was removed earlier.
- Partial match — whether the value is searched as a substring.
“Add” opens the field picker: a search box (“Search field…”), a “Recently selected” section with your last five fields, then two groups: “Catalog fields” and “Product attributes”. Only the first hundred fields are drawn; the rest hide behind the hint “Not all shown” — use search.
1
Search field2
Recently selected3
Catalog fields- Search field — type to filter the list of fields.
- Recently selected — fields used last time.
- Catalog fields — the group of standard catalog fields.
After you pick a field, the “New ignore rule” window opens. It has five rows:
- “Field” — the name of the field you just picked, read-only.
- “Value” — what to look for. The cursor is already here. It can't be left empty: Elbuz replies “Enter a value to search for”.
- “Partial match” — cleared. It has its own section below; it's the most important checkbox in the window.
- “Description” — a note for yourself; it affects nothing.
- “Active” — selected. Cleared means the rule stays in the list but doesn't run.
1
Value2
Partial match3
Active- Value — the text that identifies rows to ignore.
- Partial match — unchecked, so the whole value must match.
- Active — checked, the rule is enabled.
“Create” adds the rule to the grid, highlights it and scrolls so the new row is visible. The grid is sorted newest first.
The rules grid
There are nine columns: “Applies to” (the price list field), “Value”, “Partial match”, “Description”, “Active”, “Supplier”, “Price list”, “Date added” and “Date updated”. The middle four — value, partial match, description and active — can be edited right in the grid. Click a cell to edit; leaving it saves at once (no “Save” button here), and an “Updated” toast appears.
“Date updated” stays empty until the rule is edited at least once: the date is set when you edit, not when you create.
You can filter and sort the grid by any column — the filter row sits under the headers. With a few hundred rules, that's the only way to find the one you need.
The fields people actually use
The list has many fields — over ninety in a specific price list's window — but almost all filtering is built on four:
- Name — the most common choice: suppliers put everything into the name.
- Manufacturer SKU
- Supplier SKU
- Category from price list
Exact or partial match: the main trap
The “Partial match” checkbox is cleared by default. That means the rule looks for the value whole and exact: a price list row is deleted only if the field matches the value from the first character to the last.
Enter Car care in a rule and the “Car care” category disappears, but “Car care and lubricants” stays. Enter Bosch and items named exactly “Bosch” disappear, but “Bosch GSB 13 RE drill” doesn't. This is the mistake that makes a rule look created while the price list doesn't change.
A rule whose value is a piece of a name doesn't work without the checkbox. To drop everything that contains a word, turn on “Partial match”. The rule then fires on any row that has the word anywhere: at the start, in the middle or at the end.
There is a flip side. The checkbox makes a rule much broader than it looks: Bosch with partial match drops “Bosch drill”, “Adapter for Bosch” and “Bosch alternative” alike. That's why values are more often entered exactly, without partial match.
Case doesn't matter in either mode: bosch and BOSCH are the same to the rule. The window has no case switch.
One rule is one field and one value. You can't write “or” or “except” here: two brands mean two rules. More complex conditions are built on the next tab.
How to drop a whole supplier section
When you don't need a whole section rather than a single product, base the rule on the “Category from price list” field. The value is compared with the section name as the supplier wrote it in their file — not with your category name. Those are different things.
Such a rule removes more than products. It also cleans the supplier's category tree — but how deep depends on the same “Partial match” checkbox.
- Checkbox cleared. The section itself and its first-level subsections disappear. Anything one level further down stays in the tree.
- Checkbox selected. The whole branch disappears, all the way down: the rule checks the full category path, and the section name appears in it at every level below.
Subsections go with their parent — with no separate warning and no list of what will go. If in the “Tools” section you only don't need “Drills”, ignore “Drills”, not “Tools”. And mind the depth: without the checkbox the tree is cleaned only one level down, and half the branch stays in the price list.
The “Select product categories” button
The button bar has one more category action — “Select product categories”. It works the other way round: instead of dropping a category, it narrows an existing rule to a few of your catalog categories. Select the rule's row in the grid, click the button, check the categories — and the rule applies only to products already in them.
With no row selected, the button silently does nothing: click the rule first, then the button.
During import such a rule runs not at its usual place in the chain but later, after products are sorted into your catalog categories: at the ignore step rows have no category yet. What this pass deletes goes into the import log as a separate, second “Products removed:” line.
Narrowing relies on the “Distribute products across base catalog categories” operation. Turn it off in the “Operations” window and the category in the rows stays empty, so the rule deletes nothing. For the same reason it won't touch items that no distribution rule sorted: they have no category, so they don't fall under the narrowing.
If you need to limit a rule to a supplier's section rather than your own, use the “Category from price list” field: it's already known at the ignore step.
How to set a condition on several fields
The window's second tab is for cases where one field isn't enough. The caption above the builder says it plainly: “Set a condition to ignore items in the price list”.
A condition is built from rows: field, operator, value. Rows are joined with “AND” or “OR” and can be nested in groups. Fields come from the same columns you see in the price list product grid — over a hundred, a third of them numeric.
Operators depend on the field type. Numeric: “equal”, “not equal”, “less”, “less or equal”, “greater”, “greater or equal” and “between”. Text: “contains”, “doesn't contain”, “equal”, “not equal”, “begins with”, “doesn't begin with”, “ends with”, “doesn't end with”, “is empty” and “is not empty”. Numeric fields have no “is empty” — catch a blank price with “equal 0”.
Under the builder, Elbuz shows the assembled condition in plain language — reread that line before saving; it's the best way to catch mistakes like a swapped “and” and “or”. “Reset” clears the builder, “Save” stores the condition; an “Updated” toast confirms it.
Where the condition is stored depends on how you opened the window: from the menu, it becomes common to all price lists; from a source's card, it's that source's condition; from the sheets window, it's the condition for a single sheet.
The simplest use is price: the condition “Price equal 0” drops items the supplier sent without a price. Keyword rules can't do this — there, values have to be listed one by one.
The condition every price list already has
Check before configuring: every price list source has a ready-made ignore from day one, written when the source is created.
It reads like this: drop a row whose name, manufacturer SKU and supplier SKU are all empty at the same time.
Such rows are common in supplier files: blank rows between blocks and section “headers” in Excel — what a person sees as formatting, the program reads as an item with no name and no SKUs. The condition removes them before you ever see them.
You can view and change it on this window's “Logical condition” tab.
1
First condition row2
Plain-language condition3
Save- First row — Name is empty; the other two rows (manufacturer SKU, supplier SKU) are joined with AND.
- Plain-language reading of the condition under the builder.
- Save — stores the condition (not pressed here).
This condition belongs to a specific price list. There's one more, common to all sources — you set it in the same window opened from the menu. By default it's empty.
When a rule takes effect
There are three moments, and the difference matters.
- On every price list import. The main mode. The rules are run by the “Remove products that are on the ignore list” operation, and afterwards the import log gets a “Products removed:” line with a count.
- When you click “Apply rules to products”. A one-off pass over rows that are already loaded.
- When added from another window. When a rule is created from the product grid or the category tree, the rows are deleted at once, with no separate command.
A rule created here, though, deletes nothing when it's created. Rows already loaded stay until the next import or until you click the button.
The “Apply rules to products” button
The button is in the bar only when the window is opened for a specific price list. It runs all rules over the loaded rows in turn: global rules with the global logical condition first, then sheet conditions if set up, then the price list's own rules and condition, and last — rules narrowed to your catalog categories.
Here those work right away: the rows already have categories from the previous import.
While it runs, the button is greyed out, a spinner turns next to it, and a “Processing data, please wait” toast stays up. “Done” tells you it has finished.
With “Log deleted products (ignore rules)” on, a manual pass fills the deleted products log like an import does — first erasing this source's previous entries. If the pass deletes anything, the price list's counters are recalculated: the item count in the list of sources changes at once.
- Action or result
- Decision: the path depends on the answer
Its place in the operation order
During an import the price list goes through a chain of operations, and ignoring comes second — right after product categories are detected and well before products are distributed across your catalog categories.
That tells you what fires where. The supplier's category is already known at this point, so rules on the “Category from price list” field run right here, in step two.
Your catalog category is still empty, so rules narrowed to it are postponed and run later — with the “Distribute products across base catalog categories” operation, which sets that category. In the import log they produce a second “Products removed:” line.
You can turn the operation off or move it in this price list's “Operations” window. The rules then stay in place, but nothing applies them during import — except those narrowed to catalog categories: they come with the distribution operation and don't depend on ignoring being off. Operation order has its own article, Order of operations during price list import.
- Action or result
- Decision: the path depends on the answer
How to lift a rule and what won't come back
This window is the only place where ignoring is lifted. Neither the supplier's category tree nor the AI matching window has a “restore” action.
There are two ways, with different consequences:
- Clear the “Active” checkbox in the rule's row. The rule stays in the list but is no longer applied. This is reversible: select the checkbox again and the rule works again.
- Delete the row — select the rule and click the trash icon in the button bar. Elbuz asks to confirm; after that the rule is gone for good. There's no undo.
If you have many rules and need none of them any more, the “Additional operations” menu has a “Delete all rules” item with the confirmation “Delete all rules?”. Remember the two sets: only the rules of the window you're in are erased.
What comes back and what doesn't
The main thing people expect and don't get: removing a rule restores nothing by itself. Ignoring doesn't mark rows as hidden — it deletes them. Only a new import of the supplier's file can bring deleted rows back.
- Price list products reappear on the next import — as long as the supplier still sends them in the file.
- Branches of the supplier's category tree are restored from the file the same way.
- Deleted products log entries never come back — not by removing the rule, not by a new import: this price list's log is cleared before every import.
- Products in your catalog never disappeared: ignoring doesn't touch the base catalog at all. An item you've already created stays, even if its source in the price list is now ignored. You'll have to remove it from there separately.
If you're unsure about a rule, don't delete it — clear “Active” and import the price list. You'll see the result without losing the rule itself: selecting the checkbox again is one click, while a deleted row can't be restored from anywhere.
Scenarios
Test your first rule on one price list
The quickest way to make sure filtering works the way you intended before adding hundreds of rules:
Test on one price list
Made a mistake? The rule is turned off with one checkbox, and the next import brings the rows back. That's why testing on one rule and one price list is cheaper.
Skip a brand you don't sell from every supplier
Open “Ignore rules” from the menu — that's the global set. “Add” → the “Name” field → the brand name in “Value”, with “Partial match” selected. A rule in the global set applies to every price list: on import, every row with that word in its name disappears — including alternatives and accessories that mention the brand.
What won't happen: rows already loaded won't disappear when you create the rule. Global mode has no “Apply rules to products” button — click it in each price list's rules window separately, or wait for the next import.
Skip a supplier's brand only in your catalog category
Open “Ignore rules” from the price list card, create a rule (for example, “Name” with the brand name and “Partial match” selected), select its row in the grid, click “Select product categories” and check your category. A row is deleted only if it matches the rule's value and the product is sorted into that category.
What won't happen: on import, this rule fires only together with the “Distribute products across base catalog categories” operation; turn it off and nothing is deleted. Items the distribution operation didn't sort into any catalog category aren't touched by the rule either.
How to drop one supplier's section or a batch of items straight from the product grid — scenarios for adding rules in bulk.
What to do when the wrong items disappear
| What you see | Why | What to do |
|---|---|---|
| The rule is created, but the products are still in the price list | A rule created in this window deletes nothing when it's created | Click “Apply rules to products” or wait for the next price list import (when a rule takes effect) |
| The price list was imported, but products that should have disappeared are still there | Three possible causes: the rule's “Active” is cleared; the “Remove products that are on the ignore list” operation is turned off in the “Operations” window; the rule is in the other set — global instead of the price list's, or the reverse | Check, in turn, the “Active” checkbox, the operation in the “Operations” window, and which entry point you opened the window from (two rule sets) |
| A rule with part of a name has never fired | “Partial match” is cleared, so the rule looks for the whole value, from the first character to the last | Turn on “Partial match” in the rule's row (exact or partial match) |
| More was deleted than expected: a whole category branch is gone | With “Partial match” selected, the rule removes the entire branch, all the way down, and every section whose name contains the word | Delete or turn off the rule and import the price list again — the branch is restored from the supplier's file (how to lift a rule) |
| A rule narrowed to catalog categories deleted nothing | Narrowing is checked after the “Distribute products across base catalog categories” operation: either it's turned off in the “Operations” window, or the items matched no distribution rule and have no category | Turn on the distribution operation; if you need to limit by the supplier's section rather than your own, use the field, “Category from price list” (supplier section) |
| The import log has two “Products removed:” lines instead of one | The second line is a separate pass for rules narrowed to your catalog categories: it runs after products are distributed across categories | To see which rules have categories checked, select a rule and click “Select product categories” (narrowing by category) |
| “Delete all rules” didn't erase everything that was on screen | Showing rules from all price lists only removes a filter; deletion works on the set of the window you're in | Delete another price list's rules in that price list's window (two rule sets) |
| The “Select product categories” button clicks, but nothing opens | No rule row is selected in the grid | Click the rule's row first, then the button (selecting categories) |
| “Enter a value to search for” | In the new rule window, the “Value” field is empty or contains only spaces | Enter the text to filter items by (creating a rule) |
| “Error: This entry already exists!” | The server didn't accept the edit, and the cursor went back to the “Value” field. The message itself is misleading: Elbuz doesn't check for duplicates, and two identical rules are saved silently | No need to look for a duplicate — repeat the edit. If it happens again, refresh the grid with “Refresh” and try once more |
| “Error”, with a long technical server response below it | The grid didn't receive the list of rules: a dropped connection, an expired session or a server error | Refresh the grid with “Refresh”; if it happens again, reopen the window and contact support, including this text |
| An “access denied” image instead of the window | Your user's group doesn't have access to the “Ignore rules” window | Ask the owner to grant access to the window in group permissions (who has access) |
FAQ
I created a rule — why are the products still in the price list?
A rule created in the “Ignore rules” window deletes nothing when it's created. It takes effect on the next price list import, or right away with the “Apply rules to products” button in a specific source's rules window (when a rule takes effect).
How do I remove a category from the ignore list?
Only in the “Ignore rules” window: delete the rule's row with the trash icon or clear “Active”. Neither the category tree nor AI matching has such an action. The products come back with the next price list import.
A rule deleted more than I expected. How do I get it back?
Turn off or delete the rule and import the price list again — the rows come back with the supplier's file. Removing the rule alone restores nothing: ignoring deletes rows, it doesn't hide them.
Does ignoring delete products from my catalog?
No. Rules work only with the supplier's price list rows. A product you've already added to your catalog stays; you have to remove it separately.
Why can't I see rules I'm sure I created?
Most likely you're looking at another set: from the menu you see global rules, from a source's card — that source's rules, from the sheets window — the sheet's rules. The “Show ignore rules from all price lists” button in global mode shows them all together.
Can one rule drop two different brands?
Not with a keyword rule: one rule is one field and one value. Two brands mean two rules, or one condition with “or” on the “Logical condition” tab.
Can I set an expiry date for a rule?
No, rules have no start or end dates. A temporary rule is turned off with the “Active” checkbox and turned back on manually.
Can I see in advance how much a rule will delete?
No, there's no preview. The count appears after the run in the “Products removed:” line of the import log, and the list in the deleted products log.
Where to find it and who has access
- Menu
- Directories → Processing price lists → Ignore rules (global rules)
- From the price list list
- menu above the list of sources → “Ignore rules” (global); menu in the header → “Processing rules” → “Ignore rules” (for the selected price list)
- From the price list card
- “Additional” section → “Ignore rules”
- From the Excel sheets window
- “Ignore rules” — rules for the price list and for a single sheet
- Access rights
- the “Ignore rules” window; “Add” and “Delete” are separate rights
- Have ready
- a loaded price list and a list of what you don't sell, written the way the supplier writes it
The entry point decides whose rules you see and edit: from the menu — global rules for all price lists; from a source's card — that source's rules.
1
Ignore rules- Ignore rules — second item in the Processing price lists group, right below the list of price lists.
The window has no desktop shortcut. Without the “Delete” right, the “Delete all rules” item is hidden too; all other buttons are available to anyone who can open the window. The “Deleted products log” has no rights of its own: anyone with access to “Ignore rules” can open it.
Related topics
- If rules are in place but don't fire during import — Order of operations during price list import.
- If the supplier has dozens of categories you don't need — Price list category matching.
- If you need to filter out products the supplier doesn't have — Availability for one price list.
