Elbuz lets you limit a catalog update to one price list or category and shield individual products from it, so a wrong setting doesn't wipe descriptions, photos or products store-wide. What a run erases can't be restored, so check settings before the first run.
When you need this:
- First run on a live catalog: a one-category filter limits the value update to it.
- Handwritten descriptions and prices: the “Do not update” and “Fixed Price” card flags shield the product.
- A forgotten delete option: it fires at night on its own; an eight-item checklist finds it in minutes.
Where to start: the checklist before you first click “Update”.
What catalog protection does
- Limits the update to one price list, to categories or to a field condition.
- Erases a field, photos or attributes before writing new ones, only when you turned this on.
- Shows which settings take products off the storefront and delete them across the whole catalog.
- Shields individual products and fields from the run with flags.
- Lets you check the settings before the first run.
How to update only part of the catalog
There are four ways, and you can combine them.
- One source instead of all. Open the window with the button in the header of the price list you need: the update takes offers only from it, with its own field links and its own settings.
- Filter by catalog categories. On the “Additional” tab, click “Set filter by: categories”; the number in brackets next to it shows how many categories are already selected. The usual category picker opens.
- Field conditions. In the same place, the condition builder has two tabs: “Base catalog products” and “Products from price lists”. The first narrows which catalog products get updated, the second which price list rows are taken into account. Below the builder, the app spells out the condition in plain language: read that line before saving.
- Selected price list rows. Not from this window: in the price list product grid you select rows and add them to the catalog with a separate action. This mode only adds new products and stops there; it updates nothing else.
An empty filter means “all products”, and the tab hint says so directly: “The update affects only products matching the filter. An empty filter updates all products.” The builder operators are the usual ones: for numbers, equals, not equals, greater, less, between; for text, also “contains”, “begins with”, “ends with”, “empty”, “not empty”.
Autosave doesn't cover filter conditions: save them with the “Save condition” button.
1
Set filter by: categories2
Condition builder tabs3
Save- The button opens the category picker; the selection is written to the database.
- Two tabs of the condition builder: base catalog products and products from price lists.
- The button saves the condition (labelled «Save» on screen; «Clear All» next to it resets it).
The filter doesn't limit everything. Run an update of one price list with a filter on one category, and you can still deactivate products across the whole store.
- The filter narrows: the main value update, unlinking products from the price list before the update, the stock reset for products with no offer, the “Force update from this source” column and “Clear catalog field before updating”. Products outside the filter stay linked to the supplier and keep their stock.
- Bypassing the filter writes the system setting “When updating a BC, use the field update settings for each price separately”.
- Across the whole catalog, ignoring both the filter and the selected source: the stock reset for bundles, deactivation “not found in price lists”, deactivation and deletion by days current, deactivation of products in disabled categories.
If the filter condition can't be applied (say, it refers to a deleted field), the run unlinks nothing, resets no stock, clears no fields, and the log shows “The filter condition on the “Additional” tab could not be applied — unlinking products from the price list and the stock reset were skipped in this run. Check the condition.”
What a run erases with no undo
None of the operations below asks for confirmation. You check a box or enter a number, click “Update”, and it runs silently along with everything else. The window has no “Cancel” button, and there is no rollback.
Each item has a safeguard: flags that save your data.
Clearing a catalog field before the update
The “Clear catalog field before updating” column in the “Field links” grid. The run erases the field at the product update step, before writing new values: in a one-source run only in products matched with that price list, in an all-price-lists run in every catalog product. “Additional” tab filters narrow this step too. Products with “Do not update” and prices of fixed-price products are left alone.
Then the regular update writes the new value, but only to products the price list gave one to. If a product dropped out of the price list, the cell was empty or a logical condition didn't trigger, the field stays empty for good. The previous value isn't stored anywhere.
Worth knowing:
- The checkbox works even on a disabled row. The field is erased even if the link row itself is disabled and no new value goes into the field. Don't need clearing? Uncheck the checkbox itself.
- No “Update products”, no clearing. A run with that option unchecked doesn't erase fields. Clicking “Stop” before the product update starts also stops the run before the field is erased.
- A run for all price lists takes checkboxes from the shared set. Checkboxes in a specific source's set apply to a run for that source; a run for all price lists uses the “for all price lists” set, and then the field is erased across the whole catalog.
Turn this column on only when the price list is guaranteed to give a value to every product matched with it.
Deleting all photos before the update
The “Delete all photos before updating” checkbox in the “Photos and media” group. Old images aren't kept anywhere: affected products lose everything they had, both uploaded by hand and photos from other price lists and parsers. Exactly what the price list gave this time is left.
The query has one safeguard: photos are deleted only for products this run brings new price list links to. A product with no photo in the price list keeps its images. A product is left with no images at all in two cases: with cloud photo storage on (old images and their files are deleted before new ones upload), and when the run broke off between deletion and upload: two separate queries, no shared transaction.
The scheduled run reads this checkbox too, along with the photo step it works with. So one forgotten checkbox means that every night the images of products the price list brought new links to are wiped and uploaded again. The app never clears this checkbox automatically.
Deleting attributes
The “Delete attributes” checkbox, with the hint “Remove attributes from base catalog products before updating”. Previous attribute values aren't kept. Two product card flags protect them: “Do not update attributes” and “Do not update”. The “Read only” checkbox in a directory attribute doesn't stop this step: the catalog update doesn't read it at all.
Three things about this option:
- The checkbox does nothing on its own. The attribute step runs only with “Update attributes” on; for new products, deletion doesn't run at all. A delete option without the other one is dead.
- Attributes are overwritten even without this option. When the attribute step runs, old values of the attributes the price list is about to write are always erased. The option widens the scope: with it, a product loses all its attributes, not only those that came in the price list.
- The step is limited by the filter and the selected source, unlike deactivation. It affects only products matched with price list rows that have attributes in the price list at all.
The scheduled run reads the delete option too. Turned on attribute deletion together with attribute update and forgot? It fires on the next nightly run, without you and without any warning.
An empty price list cell overwrites the value
The most common way to lose data: a field link is on but both row flags are unchecked, so the price list writes empty values to the catalog too. How to avoid it: four flag combinations.
When products disappear from the storefront or the database
Three “Additional” tab settings take products missing from price lists off sale or delete them, all across the whole catalog: neither the filter nor the selected source narrows them. Any number above zero in the deletion days field erases cards on the next run, without confirmation; zero or empty means “off”. One more mechanism has no setting: every run takes products in disabled categories off sale.
More: What happens to a product missing from price lists.
1
Deactivate products not found in price lists2
Days before deactivation3
Days before deletion- The checkbox deactivates base catalog products that are not found in price lists.
- The field with days a product stays current before it is deactivated; 0 means the feature is off.
- The field with days a product stays current before it is deleted; 0 means the feature is off.
What protects products from the update
| Safeguard | What it shields |
|---|---|
| “Do not update” on the product | No update step touches the product: no field update, clearing, deactivation or deletion |
| Price, recommended price, cost price, old price and the link to the supplier. It also blocks both days-current steps: deactivation and deletion. It doesn't shield from deactivation “not found in price lists” | |
| “Do not update photo” and “Do not update attributes” | Images and attributes of a specific product. Such products are left out of both the content steps and the cost estimate |
| Bundle product | Bundles are excluded from deactivation “not found in price lists”: what you put together yourself isn't supposed to be found at the supplier |
| “Update if value is not empty in price lists” | A specific field from being overwritten by an empty price list cell. You set it in each “Field links” row separately, and it works not for every field: it doesn't protect quantity and stock status |
| “Do not set the price below purchase price + N %” | The price from falling below “cost price + N %”, after formulas and markups, so it catches both a formula error and a markup that's too small. Turn it on in price and markup settings; off by default. How to combine it with repricing: price no lower than purchase price |
| “Value change history” | Shields nothing, but keeps a snapshot of values before and after the run: the only way to see later what exactly changed |
A first run without surprises
A sequence of steps that removes almost every risk and takes a few minutes.
Before you first click “Update”
Happy with the result? Remove the filter and run it for the whole catalog. Not happy? You spoiled one category, not the store.
Scenarios
First run on a live catalog
What to turn on: open the window with the “Update my catalog” button in the header of one source, set a filter by one category on the “Additional” tab and go through the checklist.
What you get: values are updated only in products of that category. If you don't like the result, one category is affected, not the store.
What won't happen: the filter doesn't limit deactivation and deletion by days, so both days fields must be set to zero; see what the filter doesn't narrow.
Handwritten descriptions and prices must survive every run
What to turn on: in the product card, “Do not update” or “Fixed Price”; on the text rows of “Field links”, “Update if value is not empty in price lists”.
What you get: no update step touches a product with “Do not update”, prices don't change for a product with “Fixed Price”, and an empty price list cell doesn't overwrite text.
What won't happen: “Fixed Price” doesn't save a product from deactivation “not found in price lists”; see what protects products.
What to do when something disappears from the catalog
| What you see | Why | What to do |
|---|---|---|
| “The filter condition on the “Additional” tab could not be applied — unlinking products from the price list and the stock reset were skipped in this run. Check the condition.” | The filter condition is invalid: most often it refers to a field that no longer exists. Such a condition selects no products: the main value update didn't run, and unlinking, the stock reset and clearing fields before the update were skipped. The other run steps went as usual | Open the “Additional” tab, check the condition against the plain-language line below the builder, fix or clear it and run again (part of the catalog) |
| Products lost all their photos | “Delete all photos before updating” is checked: for products the price list brought new links to, old images are wiped, and the new ones didn't upload. The nightly run reads this checkbox too, so nobody has to start the update by hand for this to happen | Uncheck the checkbox. Old images weren't kept, so you'll have to restore them from another source (deleting photos) |
| Products lost their attributes overnight, although nobody ran the update by hand | The shared set has both “Update attributes” and “Delete attributes” checked: the nightly run reads both options and wipes all attributes before writing new ones | Uncheck “Delete attributes” on the “Settings” tab. Previous values weren't kept (deleting attributes) |
FAQ
Can I restore deleted products, photos or attributes?
No, previous values aren't stored anywhere. You can see what changed only if the “Value change history” setting was turned on in advance; see what the log shows.
Will a category filter limit deactivation and deletion of products?
No. The filter narrows the value update, unlinking from the price list and the stock reset, while deactivation and deletion by days run across the whole catalog; see what the filter doesn't narrow.
Will the “Read only” checkbox in an attribute protect it from deletion?
No, the catalog update doesn't read it. A product's attributes are protected by its card flags “Do not update attributes” and “Do not update”; see deleting attributes.
Will “Delete all photos” erase images of a product that has no photo in the price list?
No. Photos are deleted only for products this run brings new links to from the price list; a product with no photo in the price list keeps its images; see deleting photos.
Does “Clear catalog field before updating” work if the link row is disabled?
Yes: the field is erased, and no new value comes into it. Don't need clearing? Uncheck the checkbox itself; see clearing a field.
Where to find it and who has access
- Filter and activity
- the “Updating base catalog” window → “Additional” tab
- Delete options
- the same window → “Settings” tab
- Access right
- the “Catalog update from price lists” row in group permissions
How to open the window: How to update your catalog from price lists.
Related topics
- For the big picture of the update: How to update your catalog from supplier price lists.
- To set up which fields are transferred: Which fields to copy from a price list to your catalog.
- To remove delete options from the nightly run: How to run a catalog update manually and on schedule.
- If a product went off sale or disappeared from the database: What happens to a product missing from price lists.
