↑↓ selectEnter openEsc close

    1. Elbuz

    How to run a catalog update manually and on schedule

    11 min readUpdated

    Elbuz updates the catalog by itself after the nightly import of all price lists, or you start it with a button or from Elbuz Flows. By morning the catalog is current, hands-free.

    When you need this:

    • All price lists are imported — the update starts by itself; on by default.
    • Some sources are parsers — the update waits for parsing and starts a minute later.
    • You need it now — the “Update” button; progress is in the Operations Center, the window can close.
    • You need photos and attributes from parsers — cost is shown upfront: €0.05 per product.

    Where to start: check the shared set's checkboxes — run after import.

    What a catalog update run can do

    How to run an update: with the button and after price lists are imported

    There are five ways to start a run — two in this section, three in the next one. They all lead to the same place, but with different settings. That difference is what most often causes results to fall short of expectations.

    1. The “Update” button in the window

    The simplest case: settings are taken from the window as they are, progress shows in the Operations Center in the right panel, or in a modal log window if the Operations Center isn't available. Everything you've selected takes effect.

    In a window opened from a specific price list's card, there's an arrow next to the button. It doesn't open another way to start the same run but a separate one-time mode — one-time field update.

    2. Automatically after all price lists are imported

    The most common way, and it's on by default. It's controlled by the “Update catalog after import” system setting. It triggers every time all price lists are imported — both on schedule and after you import all price lists with a button. The schedule itself is set in the “Schedule setting” window, opened from the menu of the “Price lists” window. The schedule hint describes the link directly: “Scheduled import of all price lists + base catalog update”.

    The nightly run uses the window's checkboxes — including the delete checkboxes. The schedule overrides only three things: it forces “Update products” on, and takes “Add new products” and “Add photo” not from the window but from the system setting of the same name, “Add new products” (Catalog update → Run and general rules). All other checkboxes on the “Settings” tab — including “Update attributes”, “Delete attributes”, “Update photo”, “Delete all photos before updating” and “Add video” — are read from the shared set, just as when you click “Update”.

    This product-adding setting applies only to a scheduled run. When all price lists are imported with a button, the update that follows doesn't add new products or their photos — regardless of the setting and the window's checkboxes.

    The key takeaway: a checkbox selected “just to check once” and forgotten will fire on its own at night. “Delete all photos before updating” wipes the images of all matched products and uploads them again, and “Delete attributes” wipes their specifications — neither can be undone. For parser sources, re-uploading photos at night also costs money: €0.05 per product. Before leaving the window to the schedule, go through the “Settings” tab and make sure both delete checkboxes are cleared.

    You can't keep the catalog untouched at night by clearing “Update products” in the window: the schedule forces it on. Turn off the “Update catalog after import” system setting instead.

    Other ways to run it

    3. Delayed run after parsing

    If parsers among the sources have unfinished tasks, the update doesn't start right away. The log gets the line “Price lists loading completed. Batch processing will be launched after parsing is complete”, and the app waits. On every tick it checks whether another run, a price list import or parsing is still going. Once all is clear, it waits one more minute and starts — with method 2's three overrides and the other checkboxes from the window. New products are added here too only if all price lists were imported on schedule.

    The left branch is price lists without parsers: the update runs right away. The right branch is unfinished parsing: the app waits until the run slot, the import and the parsers are all free, then one more minute.
    noyesnoyesyes, waits for the next ticknoImport of all price lists finished — onschedule or with a buttonIs “Update catalog after import” on?The catalog isn't updated; theexport, if enabled, is built anywayAre some sources parsers withunfinished parsing tasks?Base catalog updatenew products — only for ascheduled runThe log shows “Batch processingwill be launched after parsing iscomplete”Check on each tick: is another run, aprice list import or parsing inprogress?One-minute pauseTranslation and export — if enabled
    • Start or end
    • Action or result
    • Decision: the path depends on the answer

    4. After a single price list is imported on schedule

    The narrowest mode — and the only one where content checkboxes are really overridden with zeros. After each source is imported, if this is enabled for it, an update runs with “Update products” only: no new products, no photos, no attributes. Checkboxes not on this list — “Add video”, “Add files”, “Update options” — are taken from the window, as in the other methods.

    5. From Elbuz Flows

    Automation scenarios have the “Update base catalog” operation — the same run, with no parameters, using the current settings. It passes counters to the flow: how many products were updated, how many were added, and the total.

    What follows an update and what prevents it from starting

    What follows an update

    After all price lists are imported (methods 2 and 3), the app can run two more steps. Both are turned on in “System settings”, the “Catalog update” section → “Run and general rules”.

    • “Translate texts after update” — right after the catalog update, translates empty fields into other languages, so new products reach exports already translated. Off by default, and it works only when the catalog was actually updated; what gets translated is set in the “What to translate automatically” row. Details: Bulk translation of the catalog into other languages.
    • “Build exports after update” — builds export templates after all price lists are imported, even if the automatic catalog update is off. When the update waits for parsing to finish, the export waits too and runs once — after the update and translation.

    These steps don't follow the “Update” button or a scheduled import of a single price list.

    What prevents a run from starting

    Two runs can't work at once. A run takes a lock when it starts and holds it to the end; a second run is refused with “Batch processing is already running in another process — this run was rejected”. If a run fails or hits the time limit, the lock is released at once. A live run refreshes the lock at each stage boundary where it checks the stop button; a lock not refreshed for over two hours counts as left from a dead process and is taken over — a failed run won't block you forever.

    The second obstacle is a scheduled price list import that's in progress. A catalog update isn't started on top of it. The process's own steps bypass this check: when the import finishes and the app starts the update itself, it goes through.

    How to monitor a run and stop it

    Progress shows in the Operations Center in the right panel; if it isn't available, a modal log window opens. It shows the step lines, the “Products updated” and “Products added” counters, and at the end “Data update completed!” and “Time elapsed”.

    The line worth reading before you go check prices in the catalog is “Abnormally low supplier prices ignored: N…” with a list of price lists. The app writes it as a warning, and only in a run over all price lists when the filter rejected something.

    The stop button in the Operations Center writes “Import interrupted by the user!” to the log. It doesn't take effect instantly: the run checks the stop flag at stage boundaries, and there are four of them — before the price update, before adding products, before “Updating product status and availability” and before “Profit calculation”. Each stage is one large database query that can't be interrupted midway. Whatever is already written stays written; there's no rollback.

    The button works the same for a run over all price lists and a run for a single source. The system has one stop flag per user — you can't stop just one of two simultaneous runs, but two simultaneous runs never happen anyway.

    You can close the “Updating base catalog” window as soon as the run starts: once started with the “Update” button, the update runs to the end even if the browser tab is closed, with a four-hour limit. Progress shows in the Operations Center (“Notifications and operations”, “Active” tab); you can close the panel too — the log is still collected. At the end, the operation card shows “Done”.

    Log lines are kept for 14 days, operation summary cards for 90 days. Which products changed and what they had before the run shows on the “Operation history” tab if the “Value change history” setting was turned on in advance. It's recorded only for a run that finished, kept for 7 days, and values can be restored one product at a time.

    What happens to the catalog if a run breaks off, and how bulk changes from price lists differ from changes in the catalog grid — Bulk changes in the catalog.

    How much an update costs

    The update itself is free. Only content is charged — photos and attributes — and only for products from parser sources. Regular file price lists cost nothing, however many items they contain. The “Add categories” checkbox adds no separate charge: it only widens the range of products counted for photos and attributes.

    The rate is €0.05 per product. A product is counted once, even if both its photos and attributes are updated. The window header has a separate badge for this: “Content cost: 12.35€ (247)” — the amount and the number of products. It appears only when paid operations are on and is recalculated every time you touch the related checkboxes.

    Completely free with fixed payment and paid unlimited descriptions.

    If your balance is too low, a warning is added to the badge, and the “Update” button becomes physically unavailable — you can't click it. If the balance runs out during a run, the content step writes “Insufficient balance to add content” with the amount to the log and stops, but the rest of the run continues: prices and availability are updated either way.

    Which system settings change the result

    Part of the update's behavior is controlled not by the window but by system settings — mostly the “Catalog update” → “Run and general rules” section; for the rest, the section is given in brackets. Below are the ones that change the result most visibly. The state in the column is the default, checked on the demo database; it may have been changed in your account.

    System settings that affect the catalog update
    SettingDefaultWhat it changes
    “Update catalog after import”onThe same nightly run using the window's checkboxes; it also triggers after you import all price lists with a button. Turning it off is the only way to keep the catalog from updating at night
    “Add new products”offWhether the nightly run creates new products and adds photos to them. The window's “Add new products” and “Add photo” checkboxes don't affect this. After you import all price lists with a button, new products aren't added
    “Matched products only”offNarrows the update, field clearing and availability reset to products found in price lists
    “Clear supplier before update” (Price lists → Import and parsing)onThe product's link to its supplier is rebuilt on every run
    “Recommended price control” (Catalog update → Stores and stock)onAdds a separate “Updating RRP” step — the recommended price is collected from all price lists
    “Per-price-list field rules”offIn a run over all price lists, non-system fields are also picked up from each source's settings
    “Check uniqueness by EAN” (Price lists → Product matching)offThe barcode becomes the key for merging new products: items with the same go into one catalog card. Items without a barcode are added as usual — by the regular key (manufacturer SKU + name + link). The run log gets the line “…items sharing a barcode were merged into one product card. Items merged: N” — it shows how many rows were merged
    “Fill the “Model” field”offA new product's model is built from its name automatically
    “Value change history” (Catalog → Data processing rules)offA snapshot of values before and after the run — what you can later use to prove what exactly changed

    There's also a group of settings for warehouses, stores and option products: stock by warehouse, availability status by quantity, product price from warehouse price, main product price from option products. They also apply during the catalog update, but they concern price selection rather than data transfer — and belong to a neighboring topic.

    Scenarios

    Update prices and availability every night — and nothing else

    What to turn on: the “Update catalog after import” system setting and a schedule for importing all price lists. In the window opened from the “Price lists” menu (the shared set), leave the default checkboxes as they are, and on the “Settings” tab make sure “Delete all photos before updating” and “Delete attributes” are cleared.

    What you get: after every import of all price lists, the price, RRP, cost price, quantity and availability status go to the catalog — these five “Field links” rows are on from the start. If some sources are parsers with unfinished tasks, the update waits for them (delayed run).

    What won't happen: names and descriptions aren't transferred while their “Field links” rows are off, nor are photos of existing products while “Update photo” is cleared. New products don't appear while the system setting of the same name, “Add new products”, is off: the window's checkbox doesn't affect the nightly run.

    Don't update the catalog at night — run it manually

    What to turn on: turn off the “Update catalog after import” system setting.

    What you get: price lists are imported on schedule, but the catalog doesn't change until you click “Update”.

    What won't happen: clearing “Update products” in the window isn't enough for this — the schedule forces it on.

    New products from price lists should appear at night by themselves

    What to turn on: the “Add new products” system setting (Catalog update → Run and general rules).

    What you get: the nightly run creates products from unmatched price list rows and adds photos to them.

    What won't happen: after you import all price lists with a button, new products aren't added — regardless of the setting and the window's checkboxes.

    What to do when an update didn't start or stopped

    Common problems
    What you seeWhyWhat to do
    New products aren't added after the nightly run, although “Add new products” is selected On schedule, adding products (and their photos) is controlled not by the window but by the “Add new products” system setting (Catalog update → Run and general rules) — it's off by default Turn on that setting or add products manually with the “Update” button (scheduled run)
    “Batch processing is already running in another process — this run was rejected” is already in progress: the lock is held by another run Wait for it to finish. A lock not refreshed for over two hours is taken over automatically (what prevents a run)
    “Batch processing is currently running. Please wait for it to finish — a repeated run is blocked.” The same state, shown as a bar in the window; the “Update” button is inactive Wait. Progress shows in the Operations Center (run log)
    “Scheduled price list import is in progress — catalog update start was rejected” A scheduled price list import is running; a catalog update isn't started on top of it Wait for the import to finish. If the run after import is on, the update starts by itself (when it starts)
    “Price lists loading completed. Batch processing will be launched after parsing is complete” Some sources are parsers with unfinished tasks Nothing: the app starts the update by itself a minute after parsing ends (delayed run)
    “Insufficient balance to add content” with an amount Not enough money for photos and attributes from parser sources: €0.05 per product Top up the balance or clear “Update attributes” and “Update photo”. Prices and availability are updated without content too (what costs money)
    “Import interrupted by the user!” Stop was clicked, and the run saw the flag at a stage boundary Whatever was written stays written. Start the run again (“Stop” button)
    You clicked stop, but the run keeps going for a few more minutes The stop flag is checked at four stage boundaries; the current stage is one large database query and runs to the end Wait for the nearest boundary. What was written before it stays written (“Stop” button)

    FAQ

    Is the scheduled nightly run different from the “Update” button?

    In three ways: the schedule turns on “Update products” itself, and takes “Add new products” and “Add photo” from a system setting. All other checkboxes, including deleting photos and attributes, are read from the window's shared set — scheduled run.

    Will the update stop if I close the window or the browser?

    No. Once started with the “Update” button, it runs to the end with a four-hour limit; progress shows in the Operations Center — monitor a run.

    How do I prevent an employee from updating the catalog?

    Remove the “Catalog update from price lists” row for their group in “Group permissions”. This doesn't block work with price lists, and the update after price lists are imported keeps running — who has access.

    Will new products get translated automatically?

    Yes, if “Translate texts after update” is on in “System settings”: empty fields are translated right after the update that follows importing all price lists — what follows an update.

    Can I run two updates at once — for different price lists?

    No. While one run is going, a second one is refused with “Batch processing is already running in another process — this run was rejected”. Wait for the first to finish — what prevents a run.

    Where to find it and who has access

    “Update” button
    header of the “Updating base catalog” window
    Schedule
    “Price lists” → menu → “Schedule setting”
    Access right
    the “Catalog update from price lists” row in “Group permissions”; the schedule doesn't check it

    How to open the update window — How to update your catalog from price lists.

    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