↑↓ selectEnter openEsc close

    1. Elbuz

    Whose price goes to the catalog when several suppliers have the product

    13 min readUpdated

    When a product is in several price lists, Elbuz picks one price on every catalog update by your rule — minimum, average or maximum — weighing supplier priority and stock. No manual comparing needed.

    When you need this:

    • Your main supplier should win — a smaller coefficient in its card makes it win even when slightly pricier.
    • One has stock, another is cheaper but on pre-order — the price comes from the one with stock once “In stock” gets higher priority.
    • Competitor price lists sit alongside — their prices stay out unless the “Competitor” group is checked.

    Where to start: check your supplier coefficients in the “Contacts” grid.

    What price selection does

    What this gives your business is covered separately: what it does for your store.

    How the app picks a price

    The “Price selection” card is on the “Settings” tab. The hint under its title states its purpose: “Which price from the price lists goes to the catalog if several suppliers have the product.”

    The card has four controls; in the window opened from the “Price lists” toolbar menu (the shared set for a run across all price lists) it has five. Explanations sit behind the “?” icon next to each name: hover over it to see the tooltip.

    The “Price selection” card in the base catalog update window
    1Price selection type
    2Price field
    3Prices greater than zero
    4Ignore RRP-flagged price lists
    5Ignore abnormally low price, %
    1. Price selection type — minimum, average or maximum is applied to the price multiplied by the supplier's coefficient, not to the raw price.
    2. Use field when selecting price — which price list field counts as the price.
    3. Select prices greater than zero — skips suppliers who sent an empty price.
    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; the field exists only in the shared set (opened from the burger menu) and works only in a run over all price lists.
    Controls of the “Price selection” card
    ControlValuesDefault
    “Price selection type”“minimum”, “average”, “maximum”minimum
    “Use field when selecting price”any price field of the price list: “Price”, “RRP”, “Cost price”, “Price from price list”, “Old price”, “Sale price” and others“Price”
    “Select prices greater than zero”removes rows without a price from the comparisonoff
    “Ignore prices with the RRP flag when choosing a price”excludes recommended-price lists from the comparisonoff
    “Ignore abnormally low supplier price, %” — shared set only0–99: an offer cheaper than the median of all the product's supplier prices by more than this percentage doesn't take part in selection0 — off
    One run, from the ranking number to the price in the card. The yellow diamond at the top decides how many passes by stock status there will be; the middle one decides how the remaining offers turn into one price. A product that got no offer goes down the bottom branch
    noyesminimum or maximumaverageyesnoYou click “Update”For every price list row, a rankingnumber:price × coef. + supplier valueFiltering: the row is matched, thesupplier is enabled,its group and stock status arechecked in the gridsDo the checked statuseshave different “Priority”?One pass over allchecked statusesPasses from the highest “Priority” tothe lowest —each next pass takes only productswithout a price“Price selection type”The row with the lowest or highestranking number wins — its pricegoes to the productThe product gets the average of the“Price” field,the coefficient is ignoredDid the product getat least one offer?The reset does not touch it —the card keeps what price selectionwroteStock reset: the status with the “Outof stock” flagand quantity 0 — for the enabledfield links“Stock status” and “Quantity”
    • Action or result
    • Decision: the path depends on the answer

    Why the cheapest price didn't win

    This is the key thing to know about this card. Before comparing, the app calculates a ranking number for each price list row:

    price × supplier coefficient + supplier value

    It then takes the lowest (or highest) of these numbers. The coefficient and value come from the supplier card; they start at 500 and 10000. As long as nobody changes the coefficients, all suppliers are compared on the same scale and the cheapest one really wins.

    As soon as even one supplier has a different coefficient, the result stops matching the “minimum” label. Here are three cases calculated with the same formula the app uses:

    Who wins when coefficients differ
    Supplier ASupplier BWho wins
    price 100, coef. 500 → 60,000price 120, coef. 500 → 70,000A — it's cheaper
    price 100, coef. 500 → 60,000price 120, coef. 400 → 58,000B, even though it's more expensive
    price 100, coef. 500 → 60,000price 9999, coef. 1, value 0 → 9,999B at any price

    The practical rule is simple: a smaller coefficient means a higher supplier priority. A coefficient many times off from the rest cancels price comparison altogether — that supplier will always win, whatever it charges.

    What goes to the catalog is the raw price of the winning row, not the calculated number: the ranking number is used only for comparison.

    Three more details of the same calculation:

    • a coefficient of 0 means the highest priority — the price enters the comparison without a multiplier, as if the coefficient were 1;
    • if the selected source field is zero, the priority is calculated from the RRP field of the same row;
    • if the row has no supplier at all, 500 and 10000 are used.
    Rows of one product from different suppliers with their prices
    1Lowest price
    1. The row with the lowest price is the one that reaches the catalog.

    “Average” and “maximum”

    “Maximum” mirrors “minimum”: the same ranking number, only the highest one is taken.

    “Average” works differently, and it's worth knowing this before you turn it on:

    • there's no winning row: the app doesn't look for the best offer but calculates the average and writes it to the price field;
    • the average is calculated from the “Price” field, even if a different field is selected in “Use field when selecting price”;
    • rows with a zero price aren't included in the average;
    • stock, supplier and other fields come from one of the offers that has a price and wasn't discarded as abnormal.

    The consultant explains in plain words why this price was chosen. In the price lists window, with two or more price lists enabled, the chat offers the prompt “Which price is chosen and stock from several price lists”: the selection rule (minimum, average, maximum price or priority), supplier coefficients, groups, stock rules — and where each of them is changed.

    For one source, use the “✦ AI” button in its header → “How this price list takes part in price choice”; for one product, “Where does this price come from?” in the product card.

    Where the supplier coefficient is set

    It isn't in the catalog update window. The is set in the “Contacts” window (menu Directories → Contacts → Contacts) with two grid columns:

    • “Price selection priority, coef.” — the multiplier;
    • “Price selection priority, value” — the addend.

    Both columns are edited right in the cell: change the number, click outside, and it's saved. Zero in the coefficient column means the highest priority: that supplier beats everyone with 500; if several have zero, the cheapest of them wins. To give a supplier normal priority again, enter 500 and 10000, not zero and not an empty field.

    Contacts grid with the two price selection priority columns
    1Price selection priority, coef.
    2Empty or zero value
    1. Price selection priority, coef. — the multiplier applied to the supplier's price; a smaller number means the supplier is chosen even when it is more expensive.
    2. An empty or zero value in the column — the program substitutes 500 and 10000.

    Both columns are hidden by default — you first need to add them to the “Contacts” grid through column selection. The same two fields are also in the contact card, in the “Finance” section.

    This is where people trip up: the update window says “minimum”, the coefficient is set in another window, and it's the coefficient that decides the result. If no coefficient is set anywhere, the default applies and the rule really is simple: the cheaper one wins.

    “Finance” section of a supplier card with the price selection priority fields
    1Price selection priority, coef.
    1. Price selection priority, coef. — a lower number means a higher supplier priority; it is the same value as in the hidden grid column.

    Which offers take part in the comparison

    Before comparing prices, the app filters price list rows. A row takes part only if all of these hold:

    • it has with a catalog product — an unmatched row doesn't take part in price selection at all;
    • the supplier is enabled;
    • the price list is a main one, not a child;
    • in a run across all price lists — the source is enabled;
    • the contact group is checked in the “Price selection by contact group” grid;
    • the stock status is checked in the “Select price based on stock status” grid;
    • if “Select prices greater than zero” is on — the row has a price;
    • if “Ignore prices with the RRP flag when choosing a price” is on — the source isn't marked as an RRP price list;
    • in a run across all price lists with the “Ignore abnormally low supplier price, %” threshold set — the row's price isn't below the median of all the product's offers by more than the threshold.

    The last item protects you from price list mistakes: a supplier entered some prices in the wrong currency or dropped a zero. The filter works only in a run across all price lists and only for products with at least two offers; it doesn't discard inflated prices. More: filtering out an abnormally low price.

    Offers from a disabled supplier take part neither in price comparison nor in the median calculation for the filter, so disabling a supplier is enough to remove it from selection.

    One more item on this list doesn't work as you'd expect. The “source is enabled” check applies only in a run across all price lists. If you open a disabled source with its own “Update my catalog” button and click “Update”, the catalog is updated from it — in this mode the source's disabled state isn't checked.

    If no offer meets the conditions, the product gets no price at all — and then the stock reset picks it up.

    Before your first run

    Before your first run

    Discounted, used or refurbished items are separate products, and their offers are not mixed with new ones: product condition. To see all supplier offers for one product, use search in the catalog and price lists.

    Stock status priority

    The “Select price based on stock status” grid sits below the price selection card. Its rows are created automatically from your stock status list, and only one is enabled — the status with the “In stock” flag. Columns: “Active”, “Stock status” and “Priority”.

    Grid “Select price based on stock status” with Active and Priority columns
    1Active
    2Priority
    3Preorder row, unchecked
    1. Active — only checked statuses take part in price selection.
    2. Priority — a higher number means that status is considered first.
    3. The Preorder row is unchecked, so offers with this status are not used.

    “Priority” isn't a sort order but a sequence of passes. The app groups the checked statuses by this number and goes from highest to lowest, and each next pass touches only the products the previous one didn't. So a higher number means a higher priority.

    By default every row has zero, so there's one pass and all checked statuses are equal. Example: give “In stock” priority 10 and “Pre-order” 0, check both, and the price comes from the supplier with stock, even if the pre-order offer is cheaper. Products with no in-stock offer get a price in the second pass.

    Contact groups

    The second grid is “Price selection by contact group”. Here too all rows are created from the directory, and one group is enabled: suppliers.

    Grid “Price selection by contact group”
    1Competitor row, unchecked
    1. The Competitor group is unchecked: competitor prices sit in the same price lists but never reach the catalog.

    You need this setting because competitor price lists usually live in the same system as supplier price lists. Uncheck the supplier group or check an extra one, and the catalog gets prices you don't buy at. The app applies the same group list when adding new products to the catalog.

    What goes to the product along with the price

    From the winning row, the product card gets the supplier, the source, the link to the price list row and the price update date. In addition:

    • old price is filled with the previous value if the new price differs from it;
    • the stock status change date is updated only when the status actually changed;
    • a zero from the price list doesn't overwrite the category or manufacturer — the app protects these values itself.

    All of the above is blocked by the flag: such a product keeps its previous price, previous supplier and previous update date.

    That last point matters for deletion by days.

    System settings that also change the price

    Part of the behavior is set not in the update window but in the “Processing price lists” section of the system settings. These apply to the whole account at once, not to a single price list.

    System settings that affect the product price
    SettingWhat it changes
    “When updating the BC, control the RRP based on products from all price lists”Adds a separate “Updating RRP” step
    “When updating the BC, select the minimum price from option products for the main product”The main product's price comes from the cheapest option
    “When updating the BC, use the max. price of option products for the main product”The same, but from the most expensive option
    “When updating the BC, copy the price from the main product for option products”The reverse direction: options get the main product's price
    “When updating the BC, update the product price from the warehouse price”The price comes from the warehouse purchase price plus markup
    “When updating the BC, process only found products from price lists”Limits both the update and the stock reset to found products
    “When updating the BC, set the stock status “Out of stock” if fewer than N suppliers have the product in stock in price lists”“Out of stock” status by number of suppliers

    RRP is picked separately

    The is collected not with the price but in a separate run step, “Updating RRP”, turned on by the system setting “When updating the BC, control the RRP based on products from all price lists” (on by default).

    This step has its own rules, different from the main price selection:

    • the RRP is taken from every enabled price list that has one — including regular supplier price lists; if some sources are price lists with the RRP flag, their recommended price is written last and takes precedence;
    • the raw recommended price is compared, without the supplier coefficient;
    • “minimum”, “average” or “maximum” — the same “Price selection type” radio as for the price;
    • the step doesn't touch products with a fixed price.

    Scenarios

    Take the price from whoever has the product in stock, and use “pre-order” only when nobody has it in stock

    What to turn on. On the “Settings” tab, in the “Select price based on stock status” grid, check “Active” for the “In stock” and “Pre-order” statuses. In the “Priority” column, give “In stock” a higher number than “Pre-order”, for example 10 and 0.

    What you get. The first pass picks a price only among “In stock” offers. The second pass takes only products that haven't got a price yet and looks among “Pre-order” offers. A cheaper pre-order offer no longer beats an in-stock one.

    What won't happen. If both statuses have the same “Priority”, there's one pass and the statuses are equal — the cheaper offer wins, whatever its status.

    Your main supplier should win even when another one is slightly cheaper

    What to turn on. In this contact's card, “Finance” section, or in the “Contacts” grid, set “Price selection priority, coef.” lower than for the rest. Suppliers without a set coefficient use 500, so give the main supplier, say, 450. If it should always win at any price, give it a coefficient of 0. Leave “Price selection type” at “minimum”.

    What you get. Its price is multiplied by a smaller number, and it wins until the price difference outweighs the coefficient difference: with 450 versus 500 and the same “Price selection priority, value”, as long as it's less than one ninth more expensive. The catalog gets its own price from the price list, not the calculated number.

    What won't happen. In “average” mode the coefficient has no effect at all — the average is calculated from the “Price” field.

    Competitor and RRP price lists sit alongside, but only supplier prices should reach the catalog

    What to turn on. In the “Price selection by contact group” grid, leave only the supplier group checked. In the “Price selection” card, turn on “Ignore prices with the RRP flag when choosing a price”.

    What you get. Rows from competitors and from price lists with the RRP flag don't take part in price comparison. The same group list applies when the update adds new products to the catalog.

    What won't happen. RRP price lists don't drop out of the run entirely: the separate “Updating RRP” step takes the recommended price from them, and it takes precedence over the RRP from other price lists while the system setting “When updating the BC, control the RRP based on products from all price lists” is on.

    What to do when the catalog shows the wrong price

    Common problems
    What you seeWhyWhat to do
    The catalog got a price that isn't the cheapest The winning supplier has a smaller priority coefficient than the rest — the comparison uses the price multiplied by it Compare the values in the “Price selection priority, coef.” column of the “Contacts” grid; you'll need to add the column first (supplier coefficient)
    The price came from a supplier that doesn't have the product in stock Several statuses are checked in the stock status grid, and all have “Priority” zero — they're equal Give the in-stock status a higher “Priority” than the rest (stock status priority)
    The catalog got competitor prices An extra group is checked in the “Price selection by contact group” grid Leave only the supplier group checked (contact groups)
    The price was updated from a disabled source In a run for a single source, the “source is enabled” check isn't performed Run the update from a disabled source only on purpose (which offers take part)
    “Products updated: 0”, although the price list was imported No price list row passed the filtering before price comparison Check product matching, supplier and source status, and the checkmarks in both grids (which offers take part)

    FAQ

    Can I see in advance which price the app will pick?

    No, there's no preview. You see the result in the product cards after the run; the consultant explains why this price won via the “Where does this price come from?” button in the product card (AI prompt).

    Can I take the name from one price list and the price from another?

    No. The name, description, category and other enabled fields come from the offer that won price selection. To write fields from a specific price list, use a one-time field update by matching.

    Can I set a markup in this window?

    No. The price in a price list row is already calculated by pricing rules; here it's only picked and carried over to the catalog.

    Is the quantity in the supplier's warehouse taken into account?

    No. An “In stock” offer with one unit counts the same as one with a hundred; only the status matters (stock status priority).

    How do I give a supplier normal priority again?

    Enter 500 and 10000 in its card — the default coefficient and value. Zero in the coefficient means the highest priority, not “not set” (supplier coefficient).

    I changed settings in one price list — why doesn't the run across all price lists see them?

    Each entry point opens its own set of settings, and sets aren't inherited: the source header opens the price list's set, the toolbar menu and “All products” open the shared one (entry points).

    Where it is 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.

    Menu
    Directories → Processing price lists → List of price lists
    From a source header
    pick a source → “Update my catalog” button
    From the window menu
    toolbar menu → “Updating base catalog”
    From the “All products” tab
    “All sources” node → “All products” tab → “Update my catalog”
    Access right
    the “Catalog update from price lists” row in “Group permissions”, separate from “Price lists”
    Before you start
    matched products, an enabled supplier and source, the “Stock status” row in “Field links”

    The “Price selection” card and two grids are on the “Settings” tab; the “Update” button that starts the run is in the window header.

    Each entry point opens its own set of settings: the button in a source header opens that price list's set; the toolbar menu and the “All products” tab open the shared set for a run across all price lists. Sets aren't inherited.

    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