↑↓ selectEnter openEsc close

    1. Elbuz

    Pricing rules: how a supplier price becomes your price

    12 min readUpdated

    Elbuz calculates your prices from supplier prices: exchange rate, markup or discount, delivery, rounding. You describe your policy in rules once, and prices are recalculated on every price list import.

    When you need this:

    • A supplier discounts the whole price list — one rule with a minus lowers all its prices.
    • Cheap products earn a higher percentage than expensive ones — a threshold ladder picks the markup by price.
    • Dozens of suppliers, one policy — global rules by category apply to every price list.
    • A price surprised you — “Product markup history” shows each calculation step.

    Where to start: set up your first rule for one price list.

    What pricing rules can do

    A price dip where ladder tiers meet, when a product that costs more to buy ends up cheaper in your store, is removed with the “Markup at tier boundaries” list. More: how to remove the price dip where tiers meet.

    What to set to get the margin you want

    The first place people lose money: markup is calculated from the purchase price, margin from the selling price. These are two different numbers, and mixing them up costs you exactly the difference.

    Buy for 100, sell for 150. The markup is 50 %: you added half of 100 to 100. The margin is 33 %: your fifty hryvnias are a third of the 150 in revenue. Sell for 200 — markup 100 %, margin 50 %. The higher the markup, the wider the gap between the two.

    Pricing rules act on the purchase price. The “%” column is a percentage added to the supplier price, not a share of revenue. For a 30 % margin, don't put 30 in “%”: you'll get about 23 %. A 30 % margin needs a markup of about 43 %, a 50 % margin a 100 % markup.

    To calculate the markup for a target margin, divide the margin by one minus the margin. Margin 0.25 → 0.25 / 0.75 = 0.33, so a 33 % markup. Margin 0.4 → 0.4 / 0.6 = 0.67, so 67 %.

    What a rule can do to a price

    The word “markup” is on the buttons and in column headers, but a rule can do more to the supplier price than add a markup.

    1. Add a percentage. The “%” column in the rules grid. The price plus a percentage of it.
    2. Multiply by a coefficient. The “*” column. A coefficient of 1.3 is the same 30 % markup, just written differently. In a rule without thresholds, a negative coefficient means division: set −2 and the price is halved. In a threshold rule, a negative coefficient gives a negative price — don't use it there.
    3. Add or subtract an amount. The “+/-” column. Plus one hundred hryvnias on each item — or minus one hundred if the supplier gave you a hundred off each product. A discount is a negative value: there is no separate mechanism for it, and none is needed. The percentage, the coefficient and the amount can all be negative. One caveat: in a rule without thresholds the result is taken as an absolute value, so a discount larger than the price flips to a plus — minus one hundred on a product priced at fifty gives fifty, not minus fifty.
    4. Convert at the exchange rate. The type “Price + exchange rate. Settings source: currency list + price list.” The rate comes from the price list column settings; for rows without one, it comes from the currency list, including the rate markup set there in the “+%” column.
    5. Add the delivery cost. In two ways. The type “Adding product shipping costs” takes the “Delivery” field from the category card and adds it only to products whose categories have this field filled in. The type “Adding a fixed shipping cost for all price list products” takes the “Delivery cost” field from the source card — one amount for the whole price list; for an Excel source in “Configure per sheet” mode, the amount set for each sheet.
    6. Take the value from another field. The “Source field” and “Destination field” columns. By default a rule reads “Price” and writes to “Price”, but you can set, say, “RRP” as the source and “Price” as the destination. That's how you build a rule like “sell strictly at the supplier's recommended price”.

    These actions are not applied one at a time but as a chain: first the exchange rate, then everything else in the order of the chain of types, and rounding at the end. Here is the whole path of a price from the supplier's file to your store.

    The path of a price from the supplier's file to the product in your store
    YesNoPrice in the supplier's fileFirst type in the chain — usually«Price + exchange rate»Does the product have a rule withthe «Priority (discard others)»checkbox?The product is set aside: only thisrule will calculate itOther markup types — one by one,top to bottomPrice list rules: percentage,coefficient, valueGlobal rules by category: thresholdladderDelivery cost from the category cardor the source cardPrice after all rulesRounding: up, down or to twodecimalsPrice step, if setProfit and final price of the price listproductMatched catalog product — and onto your store
    • Action or result
    • Decision: the path depends on the answer

    It works on three levels, and the levels don't interfere with each other:

    • One price list. Rules set on the “Pricing” tab of a specific source apply only to its products (rules for one price list).
    • All price lists at once. Global rules by category — the same “ladder”, set up once and serving every source (one policy for all).
    • Individual base catalog products. Prices of your catalog products are recalculated by a separate mechanism — that's covered in another article and only mentioned here.

    How to round a price

    Rounding is applied after all rules, to the already calculated price. There are three mechanisms, and they are independent.

    Rounding to a whole number. Two switches in system settings: Account → System settings → “Catalog update” section → “Prices and markups” subsection.

    System settings, Catalog update, Prices and markups subsection with the rounding and markup settings
    1Round up
    2Round down
    3Apply markup once
    1. Round up — the final price is rounded up to a whole number.
    2. Round down — the final price is rounded down to a whole number.
    3. Apply markup once — the markup is applied only to products that have not had it applied yet.
    SettingDescription in the interfaceDefault
    Round up“The final price is rounded up to a whole number.”off
    Round down“The final price is rounded down to a whole number.”off
    Markup for subcategories“A markup set for a category applies to all its nested categories.”off
    Apply markup once“The markup is applied only to products that have not had it applied yet.”off
    Do not set the price below purchase price + N %“After formulas and markups, a price below cost + N % is raised to this floor.” N is the field next to the switch; 0 means not below the purchase price itself. More: price not below the purchase priceoff

    When both rounding switches are off — the default — the price is rounded to the kopiyka (two decimals).

    The setting's own help says so directly: “Rounding is applied after the markup. Rounding up and down enabled together conflict — choose one.” If you turn on both anyway, rounding up runs first, then rounding down — so in effect you get rounding down.

    Price step. The “Price multiplicity” field in the “Prices” section of the source card. For an Excel source in “Configure per sheet” mode, the step is set for each sheet in the “Import from sheets” window, and the card doesn't have this field. A step of 10 rounds the price up to the nearest ten: 173 becomes 180. It works only when both the step and the price are greater than one — so low-priced items aren't spoiled.

    Protection against stacking. The “Apply markup once” setting applies the markup only to products that haven't had it applied yet. The help explains why: “Protects against compounding the markup on repeat runs: without it the price creeps up with every update.”

    In most cases the pre-markup price is restored from the original, so the problem doesn't always occur. If prices creep up from update to update, turn on exactly this setting.

    When prices are recalculated

    The most common pricing question is: “I changed the rule, why are the prices the same?” The answer: the rule and the price live separately.

    The rule changes instantly, prices don't. Editing a rule does not trigger an automatic recalculation. The new price appears on the next price list import or after you run the recalculation yourself. A recalculation can't be reversed: there is no “Undo” button here.

    Automatically, on import

    Pricing is one of the operations run on every price list import. In the list of operations it's called “Repricing”, and it comes after matching price list products to base catalog products and before applying field formulas. Before it runs, the system saves the supplier price separately, so there is something to calculate from next time.

    Manually, with a button

    The magic wand button in the rules toolbar has the tooltip “Apply markup to products”. It:

    1. restores the original supplier prices — that is, undoes the effect of previous markups;
    2. re-reads exchange rates from the currency list and the price list settings;
    3. runs every type in the chain again.

    The category selected in the tree doesn't affect the recalculation: the button always recalculates the whole price list by all rules — just like on import. The exchange rate and delivery are applied once, however many times you click the button.

    While it runs, the toast “Processing data, please wait” is shown; at the end — “Product prices calculated”. Two entries appear in the work log: “Apply markup/discount (without loading the price list)” and “Markup/discount applied”.

    The same button in the global window behaves differently. When the window is opened from the menu, it has no specific price list, so it goes through the active sources of enabled suppliers — but skips those in the “Only this source's rules” mode. And that's the mode a new source is created in.

    There is no “N sources skipped” message: the toast still says “Product prices calculated”. If you need to recalculate a specific price list, open that source's “Pricing” tab and click the button there. About source modes — one policy for all suppliers.

    How to see where a price came from

    You don't need to work out the price in your head — the system records every rule that applied and shows it step by step. The window is called “Product markup history” and opens from the row context menu: in the price list product grid and in the base catalog grid.

    Product markup history window with the original price, the calculation step and the final price
    1Original price
    2First numbered step
    3Final price
    1. Original price — the price from the supplier price list before any processing.
    2. Step 1 — the first numbered calculation step; here a price conversion by exchange rate.
    3. Final price — the price after all steps, with the resulting profit.

    What it shows: “Product ID”, “Name”, “Category”, “Original price”, “Rate”, then numbered steps. Each step names the markup type, the action in words — “Add”, “Subtract”, “Multiply by”, “Divide by” — the filter of the rule that applied (“price from … to …”, “Manufacturer …”), and the price after that step. At the end — “Final price” and the profit.

    A step from a global rule has the line “Rule source: global markup rules” under the type name. In the “Global and own” modes this shows which rule came from the global rules and which from the price list's rules, and in what order they applied.

    This is your main troubleshooting tool. If a price isn't what you expected, look here, not in the rules grid: the list of steps shows exactly which type and which rule applied, and whatever isn't in the list didn't apply.

    Check in five steps

    The quickest way to make sure your settings work before touching the whole catalog:

    Check on one product

    No new step and the price hasn't changed — check these four things in turn:

    1. whether the right category is selected in the tree;
    2. whether the banner “These rules apply to sources in the…” is shown above the grid — then you were editing the global rules, not the price list's rules;
    3. whether the source is in the “Only global rules” mode (source mode);
    4. whether the chain has a type that reads the price list's rules (chain of types).

    You can ask the same thing in words. In the product card, click “✦ AI” → “Where does this price come from?”: the consultant shows step by step which supplier offer was chosen and why, which markup rules applied and which price field formulas were used.

    For a whole price list — the “✦ AI” button in the source header → “How this price list takes part in price choice”. How the button works — in the article about the AI consultant.

    Scenarios

    Build delivery of bulky products into the price

    Task: in a category of large appliances, a fixed delivery amount must be added to the price.

    What to turn on: in the category card, in the collapsible “Extras” section, fill the “Delivery” field with the amount.

    What you get: the type “Adding product shipping costs. Settings source: category directory.” adds this amount to the price of the category's products. In a new source's chain it comes last, so the amount is added after the ladder and category rules, and rounding comes after it.

    What won't happen: products in nested categories won't get the parent's amount — fill the field in each category or copy the amount to nested ones with the button next to the field (tooltip “Apply shipping costs to child categories and products”). Products with a zero price won't get the amount.

    A different price at weekends

    Task: on Saturday and Sunday prices should be 5 % higher than on weekdays.

    What to turn on: markup rules don't know the day of the week, so a price list formula does this. In the source's “Field formulas”, add a formula for the “Price” field:

    CASE WHEN DAYOFWEEK(CURDATE()) IN (1, 7) THEN ROUND({Price list: Price} * 1.05, 2) ELSE {Price list: Price} END

    DAYOFWEEK(CURDATE()) returns today's day number: 1 is Sunday, 7 is Saturday. On weekdays the formula leaves the price as the markup calculated it.

    For the catalog to get the new price every day, schedule the import of all price lists — then the base catalog update runs right after it.

    What you get: the formula is calculated on every price list import; in the default order of operations it comes after the “Repricing” step, so it multiplies the already marked-up price. A price list imported on Saturday or Sunday gets the weekend price, one imported on a weekday gets the regular price.

    What won't happen: the price won't change by itself at midnight — only with the next price list import. If the price list wasn't imported on Monday, the weekend price stays.

    The “Apply formulas” button in the formulas window calculates from the already calculated price: at the weekend each click adds another 5 %. The safe manual recalculation is “Apply markup to products”: it first restores the supplier price, then runs the rules and numeric formulas.

    What to do when prices are wrong

    Common problems
    What you seeWhyWhat to do
    The rule is created, but product prices are the same The rule and the price live separately: editing a rule doesn't trigger an automatic recalculation Click “Apply markup to products” or wait for the next price list import (when prices are recalculated)
    “Product prices calculated”, but prices haven't changed The window was opened from the menu, with no price list: the recalculation only goes through sources in the “Only global rules” and “Global and own” modes Open the “Pricing” tab of the source you need and click the button there (manual recalculation)
    The price was rounded down although “Round up” is on Both rounding switches are on; rounding up runs first, then rounding down Leave only one of them on (rounding)

    FAQ

    I set a rule — why haven't prices changed?

    A rule takes effect on the next price list import. To see the result right away, click “Apply markup to products” on the source's “Pricing” tab (when prices are recalculated).

    How do I make a discount instead of a markup?

    Use a negative value: −15 in the “%” column lowers the price by 15 %, −100 in the “+/-” column subtracts one hundred hryvnias. There is no separate mechanism for discounts (discount on the whole price list).

    The rule was created on the price list tab — why doesn't it work?

    Most likely the price list's chain has no type that reads the price list's rules — check “Markup types” (chain of types). The second reason: the source is in the “Only global rules” mode, which the banner above the grid shows.

    Prices go up with every price list update — why?

    The markup is applied on top of an already marked-up price. Turn on “Apply markup once” in system settings (protection against stacking).

    Can I set a custom markup for one catalog product?

    Not with rules: they calculate prices of price list products, and the price reaches the catalog card through matching. A custom markup for an individual catalog item is set in its card.

    Can I undo a price recalculation?

    No. Neither a recalculation, nor deleting a rule, nor spreading rules across child categories can be rolled back. Test a new rule on one product (check).

    Where to find it and who has access

    Menu
    Directories → Processing price lists → Pricing rules
    From the price list card
    the “Pricing” tab to the right of the source list
    From the price list product grid
    row context menu → “Markup settings”
    From the list of price lists
    “Menu” above the list → “Markup” → “Global markup rules”
    From the category card
    the collapsible “Markup / Discount (global settings for all products)” section
    Markup types
    menu in the source header → “Prices and markups” → “Markup types”
    Access rights
    the “Pricing rules” window; the “Pricing” tab is a separate rights block of the source card
    Prepare
    an imported price list and a decision on how much to earn on each category

    Opened from the source card, the window shows that price list's rules. Opened any other way, it shows the global rules for all sources, with the banner “These rules apply to sources in the…” above the grid. More: two sets of rules.

    Main menu with the Directories section and the Processing price lists group expanded
    1Pricing rules
    1. Pricing rules — the menu item that opens the window with the markup rules.

    The window has no desktop shortcut — only the menu and the buttons listed above.

    The rights block for the “Pricing” tab also unlocks the “Prices” section of the source card and the “Markup” item in the menu of the price list list. Without it, a manager sees the source and its products but not the rules or price fields. Bulk mode changes also require the right to edit price lists.

    The menu item is restricted separately from the window. The markup section in the category window is its own rights block inside the categories window. The markup type windows and the type filter window have no access check of their own: they open from windows whose access has already been checked.

    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