↑↓ selectEnter openEsc close

    1. Elbuz

    How to update your catalog from supplier price lists

    7 min readUpdated

    Elbuz moves prices and stock from imported price lists to matched products — one price list or all at once, and overnight by itself. No manual price edits.

    When you need this:

    • A supplier changed prices and stock — price, RRP, cost price, quantity and availability reach matched products without opening cards.
    • Several suppliers carry a product — one offer goes to the catalog, per your price selection rule.
    • A supplier mixed up currency or a zero — given a threshold, a price far below other suppliers' median stays off your site.
    • Price lists import overnight — the catalog updates once all are in.

    Where to start: “Initial setup”.

    What the catalog update does

    What happens during an update

    A run goes in steps, and each step writes a line to the log. The order is fixed and can't be changed, but it's worth knowing: the log shows how far the run got and what exactly it did.

    1. Adding categories — if copying the category structure from the price list is turned on.
    2. Updating products — the main step: values from price lists go into catalog fields according to the links. Fields marked “Clear catalog field before updating” are cleared right here, before new values are written; this doesn't add a separate log line.
    3. Updating RRP — a separate step, if recommended retail price control is turned on.
    4. Forced field updates — for links marked “Force update from this source”.
    5. “Products updated: N” — the first number the whole run is for.
    6. Updating price history — how many points were added today.
    7. Adding new products and “Products added: N” — if turned on.
    8. Matching identical products — for newly created products, Elbuz looks for the same items in other price lists.
    9. Updating product status and availability, profit calculation, updating stock by store.
    10. Updating product attributes and updating product photos — paid steps — what the update costs.
    11. Product sorting and product indexing.
    12. “Data update completed!” and “Time spent”.

    Besides these steps, a run always does a few things that don't show in the log:

    • sets the modification date on every product it touched, even if no values changed: a run for one source — on products linked to or matched with that price list; a run for all price lists — on the whole catalog;
    • recounts products in categories and by manufacturer, updates card completeness scoring and page URLs;
    • rebuilds the internal table the storefront works from;
    • clears the storefront : after a run for one source — selectively, new product cards and lists of categories where products changed; a full run also reindexes search.

    A supplier sends a price list with five thousand items. To move just the price and availability by hand, you'd open five thousand cards and change two fields in each. The update does the same in one click and tells you at the end how many products it touched.

    Whose offer goes into the product

    A catalog product is often matched with rows from several price lists: three suppliers have it in stock, a fourth on pre-order, a fifth with a wrong price. The update writes values from one offer only. Which one is decided by three cards on the “Settings” tab below the “What to update” card: “Price selection”, “Select price based on stock status” and “Price selection by contact group”.

    For each product, the run goes through six steps.

    1. Picks the candidates. A matched price list row takes part if its contact group is checked in the groups grid. Offers from disabled suppliers take no part — neither in comparing nor in writing. In a run for all price lists, the row must also come from an enabled main price list (child price lists don't take part). “Ignore prices with the RRP flag when choosing a price” drops recommended price lists; “Select prices greater than zero” drops rows without a price.
    2. Discards abnormally low prices — only in a run for all price lists, and only if the “Ignore abnormally low supplier price, %” field holds a number greater than zero (details below).
    3. Goes in passes by stock status. First it looks at offers with statuses that have a higher “Priority”; products that got nothing on this pass move on to the next.
    4. Compares prices by “Price selection type”: minimum, average or maximum.
    5. Writes the winner. From its row, the product gets the price and every field turned on in “Field links”, plus the supplier, price list and price update date. A product with a fixed price keeps its price, supplier and price update date; other fields are still written.
    6. Resets availability for products with no offer. Products that got nothing at any step get a stock status with the “Out of stock” flag and zero quantity — if the status and quantity rows are turned on in “Field links”. Which products get reset depends on whether the run is for one price list or for all.
    Price selection card in the Updating base catalog window
    1Price selection type
    2Use field when selecting price
    3Select prices greater than zero
    4Ignore prices with the RRP flag
    5Ignore abnormally low supplier price, %
    1. Price selection type — prices are compared as price × supplier coefficient + value, not as bare prices.
    2. Use field when selecting price — which field of the price list row is compared.
    3. Select prices greater than zero — rows without a price are left out of the comparison.
    4. Ignore prices with the RRP flag — price lists marked as RRP do not take part in price selection.
    5. Ignore abnormally low supplier price, % — 0 means off, recommended threshold is 50; works only in the shared run.

    How “Price selection type”, the comparison field, the stock status queue and contact groups work, with calculation examples — see Supplier price selection.

    How to keep a mistakenly low price off your site

    This guards against a price list error no other price selection check catches. In a hryvnia price list, a supplier put some prices in dollars, lost a zero or misplaced a comma. After conversion and markup, the item costs dozens of times less than it should, wins “Minimum” — and reaches your site: say, 38 instead of about 619, as at other suppliers.

    The field is in the “Price selection” card, only in the shared set — the window opened from the “Price lists” toolbar menu or the “Products” tab in “All sources” mode. The window opened with “Update my catalog” from one price list's card lacks it. Values run from 0 to 99; 0 or an empty field means “off”, which is the default.

    How filtering works on every run for all price lists:

    1. For each product, Elbuz collects the prices of all its offers from enabled main price lists where the price is above zero. It takes the row's “Price” field — after markup and conversion, the number that would go to the catalog. Checked contact groups and the RRP price list checkbox apply. Disabled suppliers' offers are left out of the median. Stock status doesn't matter: a pre-order offer with a normal price counts too.
    2. A product with fewer than two such offers isn't checked: there's nothing to compare against. Offers are counted — that is, price lists of enabled suppliers, not the suppliers themselves: two price lists from one supplier make two offers.
    3. The median is calculated — the price in the middle of the sorted list. Unlike the arithmetic mean, one wrong price barely shifts it.
    4. An offer cheaper than the median by more than the set percentage is flagged and takes no part in price selection. The next supplier gives the product its price, under the usual selection rules.
    Example: five suppliers, 50% threshold
    SupplierPrice in the price list rowWhat happens
    A600Takes part and wins “Minimum” — 600 goes to the catalog
    B619Takes part; this is the median of 38, 600, 619, 640, 655
    C and D640 and 655Take part
    E38Cutoff — 619 × (1 − 0.5) = 309.50. The price is lower, the offer is discarded. Without filtering, 38 would go to the catalog

    When a product has only two offers, the median is the average of the two prices. So with a 50% threshold, the lower price is discarded only if it's less than a third of the higher one: 38 vs. 619 — discarded, 300 vs. 619 — not.

    What you'll see after the run:

    • in the operation log — the line “Abnormally low supplier prices ignored: N (lower than the median of other suppliers by more than 50%). These prices are highlighted in the price-list products.”, followed by which price lists and how many: “Price list A — 12, Price list B — 3”, up to ten price lists, largest count first. If nothing was discarded, there's no such line;
    • on the “Products” tab of the price list card, the price in such a row is highlighted amber, with the tooltip “Price ignored when choosing the product price: it is lower than the median price of all suppliers by more than the threshold (batch processing)”. A price outside the limit relative to the catalog is highlighted red — that's a different flag;
    • the price list row itself doesn't change: its price stays as the supplier sent it.

    Only a run for all price lists recalculates these flags: they're cleared at its start and set again. A run for one price list leaves them alone. Re-importing a price list clears the flags on its rows. Once the supplier fixes the price, the next run for all price lists won't discard their offer.

    Why only a run for all price lists. A run for one price list picks the price within that price list; other suppliers give the product nothing. Discarding a cheap offer there would leave the product with no offer and “Out of stock”. The overnight run after all price lists are imported reads the shared set, so filtering works there too.

    Start with a 50% threshold: a price half the median gets discarded. The usual gap between suppliers is a few to a few dozen percent; a currency error is dozens of times. An 80–90% threshold catches only the grossest errors; 10–20% starts discarding legitimate sale prices.

    What filtering doesn't do: discard inflated prices, check products with a single offer, fix the price list or notify the supplier. The median uses the “Price” field even if “Use field when selecting price” is set to another field. A sharp price change for the same product since the previous import is caught by the “Abnormal product price” stop rule — price list stop rules.

    A run for one price list vs. a run for all

    The window opened with “Update my catalog” from a price list card and the window from the toolbar menu start the same run, but with a different scope. That decides which price a product gets and whose availability gets reset.

    How the two runs differ
    WhatOne price listAll price lists
    SettingsThat price list's own setShared set
    Where the offer is picked fromOnly that price list's rowsRows of all enabled main price lists
    Must the price list be enabledFor price selection — no: a disabled price list still updates products. But availability reset and field clearing aren't done for a disabled price listYes, disabled price lists take no part
    Filtering abnormally low pricesNoIf a threshold is set
    Availability reset for products with no offerProducts matched with this price list's rows, and products that were linked to it, dropped out of it and have no offer in any other enabled price listThe whole catalog, including products added by hand and not matched with anything
    Clearing fields before updateOnly products matched with this price listThe whole catalog
    Deactivating and deleting productsThe whole catalog — what happens to such productsThe whole catalog

    The second table row matters most: a run for one price list writes its own offer into the product, even if another supplier is cheaper. A product carried by A and B gets B's price and availability after a run for B. If B's offer fails selection (say, its status is unchecked in the status grid), the product goes “Out of stock” though A has it. The next run for all, overnight included, restores A's price. A single-list run suits adding a new supplier's range or testing settings; daily price updates come from a run for all.

    In a run for one price list, a product that dropped out of it gets “Out of stock” only if no other enabled price list has it; otherwise a run for that price list or for all decides. A run for all gives “Out of stock” to every product with no offer. To limit this to products found in price lists, use the “Matched products only” system setting (system settings). What happens next — deactivation, deletion after a set number of days — see What happens to a product that's no longer in price lists.

    Scenarios

    Initial setup: from matched products to the overnight update

    What to do:

    1. In the window from the “Price lists” toolbar menu (the shared set), check what gets updated and turn on the field links you need — Which fields to copy from a price list to your catalog.
    2. Run the update with a filter for one category and check a few products — a first run without surprises.
    3. Leave the “Update catalog after import” setting on — scheduled run.

    Result: after every import of all price lists, the catalog gets prices and availability on its own, plus names, descriptions and photos for the rows you turned on.

    New supplier: add their range from their price list, update prices from all

    What to do: start the first run from the new supplier's price list card with “Update my catalog”, then rely on the run for all price lists — with the button from the toolbar menu or overnight.

    Result: the run for one price list adds the range and shows how its data lands. The daily update for all price lists picks the price among all suppliers.

    What won't happen: a run for one price list doesn't compare prices with other suppliers — how the two runs differ.

    A supplier sometimes gets the currency or zeros wrong — such a price must not reach your site

    What to turn on: in the window from the “Price lists” toolbar menu (the shared set), in the “Price selection” card, enter 50 in the “Ignore abnormally low supplier price, %” field. Run the update for all price lists — with the “Update” button in this window or overnight.

    Result: a product with at least two offers (price list rows) won't get a price half the median of all suppliers' prices; the next supplier sets it. The operation log shows “Abnormally low supplier prices ignored: N…” with a list of price lists, and discarded prices are highlighted amber in those price lists' products. Once the supplier fixes the price list, the next run for all price lists takes their price into account again.

    What won't happen: a product carried by only one supplier isn't protected — for it, turn on the “Abnormal product price (vs. previous load)” stop rule, which warns about a sharp price change on import (price list stop rules). A run for one price list doesn't discard abnormal prices.

    What to do when the catalog shows the wrong price

    Common problems
    What you seeWhyWhat to do
    The run finished, the log says “Products updated: 0” No price list row passed selection: no matched products, the supplier or source is disabled, the contact group or stock status isn't checked in the grids, or the filter excludes everything Check product matching, whether the source and supplier are enabled, the checkboxes in the grids and the filter conditions (part of the catalog)
    A product on your site costs dozens of times less than at suppliers One supplier made a mistake in the price list (currency, an extra or missing zero), and their price won “Minimum”. Filtering abnormal prices is off, or the update ran for one price list, or only this supplier carries the product Set a threshold in the shared set's “Ignore abnormally low supplier price, %” field and run the update for all price lists (filtering abnormal prices)
    “Abnormally low supplier prices ignored: N (lower than the median of other suppliers by more than N%). These prices are highlighted in the price-list products.” Filtering is working: offers cheaper than the median by more than the threshold took no part in selection. The line is followed by the price lists and the number of discarded prices in each Open the “Products” tab of the listed price lists, find prices highlighted amber and check with the supplier. If legitimate prices get discarded, raise the threshold (filtering abnormal prices)
    After updating one price list, a product got a price that isn't the lowest, or “Out of stock”, although another supplier has it A run for one price list picks the offer only among that price list's rows Run the update for all price lists — from the “Price lists” toolbar menu — or wait for the overnight run (one price list vs. all)

    FAQ

    I clicked “Update” — what exactly changes in the catalog?

    In a fresh account — the price, RRP, cost price, quantity and stock status of matched products. Names, descriptions, photos and attributes change only once you turn on their rows — “Field links”.

    Can I undo an update?

    No. There's no rollback, and the stop button interrupts a run only between stages — whatever was written stays. That's why the first run is done on one category — a first run without surprises.

    Can I see what will change before running it?

    No, there's no preview. Run the update with a filter for one category and look at the products — updating part of the catalog.

    Does the update calculate the price by my rules?

    No. The price in a price list row is already calculated by pricing rules; the update just moves the finished number. If you don't like the price, edit the pricing rules.

    Does the update match price list rows with products?

    No. A price list row is linked to a product before the update, in another window — product matching. An unmatched row can only be added by the update as a new product.

    Where to find it and who has access

    The “Updating base catalog” window has no menu item and no desktop shortcut. It opens only from the “Price lists” window.

    Where: Directories → Processing price lists → List of price lists.

    From a source card
    “Price lists” → pick a source → “Update my catalog” button
    Other ways in
    the “Price lists” toolbar menu or the “Products” tab in “All sources” mode
    Access right
    the “Catalog update from price lists” row in “Group permissions”, separate from “Price lists”
    Before you start
    an imported price list, matched products, an enabled supplier and source
    Price list window: source header with the button row above the source card
    1Update my catalog
    1. Update my catalog — the button in the source header; it opens the update window for this one price list.

    Which way you come in matters. The button in a source's header opens the settings of that price list: the update takes offers only from it. The toolbar menu and the “Products” tab in “All sources” mode open the shared set — the one used to run all price lists at once.

    These are two separate sets of settings, and neither inherits from the other. Checkboxes, field links, filters, days of relevance — each has its own. If you set something up in one supplier's card and an all-price-lists run starts overnight, that run uses the shared set, where your checkboxes aren't.

    Open burger menu in the price lists toolbar with the Updating base catalog item
    1Updating base catalog
    1. Updating base catalog — opens the settings shared by all price lists, unlike the button in a source header.

    The window header reads “Updating base catalog”, with the source name on the line below if you came from a specific price list's card. No source name in the subtitle means you're in the shared set, and your changes affect all price lists.

    The right is checked when you open the window and when you click “Update”; there are no separate rights for tabs or checkboxes. Removing the right takes away the “Update” button, but not the update after price lists are imported: that one is turned off by a system setting — scheduled run.

    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