↑↓ selectEnter openEsc close

    1. Elbuz

    How to set up promotions and discounts with rules

    13 min readUpdated

    Elbuz sets sale and wholesale prices by rules — for a category, brand, price range or customer group — and recalculates them on price list updates to keep up with supplier prices.

    When you need this:

    • A category or brand sale — one rule lowers prices for the filtered set.
    • Wholesalers, dealers and dropshippers get their own price — one rule per customer group.
    • Price depends on quantity — tiered discounts “from 5 pcs”, “from 20 pcs”.
    • Supplier prices changed — a batch update recalculates sale prices from the new ones.

    Where to start: product grid → additional operations menu → “Promotions / Discounts”, add a rule and apply it.

    What promotion rules can do

    How to choose: promotion or quantity discount

    A rule does one of two things, and the “Quantity price (wholesale)” checkbox switches between them.

    If you enter a number in “%” without a minus and without the checkbox, the window warns that the price will go up and fixes it to a minus in one click. If you tick the checkbox without a “Quantity” of 2 or more, it reminds you that the wholesale price won't work that way.

    Rules window with the dialog asking whether 7% was meant as a -7% discount
    1Yes, make it -7%
    2No, it is a markup
    1. Yes, make it -7% — stores the value as a discount.
    2. No, it is a markup — keeps the value as a price increase.
    Promotion (checkbox cleared)Discount (checkbox ticked)
    What it isa new product pricea price based on quantity
    When it appliesalways, while the rule is activewhen the customer buys the set quantity or more
    The “Quantity” fieldnot usedrequired: from how many pieces the price applies
    How it looks on the storefrontthe old price crossed out, the new one next to ita table “from 5 pcs — this price”

    One rule does one thing. To have both a promotion and a wholesale price, create two rules.

    How to calculate the sale price

    First the rule takes the “Price source field” — which product price to calculate from: the regular price, RRP, cost price or any price field of the catalog. Then this number is converted in one of four ways:

    ColumnWhat it doesExample
    Pricea fixed price, the same for all products of the rule499 — all products at 499
    %a percentage of the source price; a negative value lowers it−15 — minus 15%
    *a coefficient. A negative value means division, not minus0.85 — multiply; −1.2 — divide by 1.2
    +/−add or subtract a fixed amount−100 — UAH 100 off

    Fill in only one of these columns. The system goes through them in turn — price, percentage, coefficient, amount — and each next filled column overrides the previous one.

    If a row has both a percentage and a coefficient, only the coefficient takes effect. There will be no error — the result just won't be the one you expected.

    Rounding and rounding step

    • The resulting price is rounded according to the system's general rounding settings: up, down or, if both are off, to the cent.
    • “Rounding step” rounds the price up to a multiple of the given number: a step of 10 turns 487 into 490 and 1,049 into 1,050. Handy so that sale prices look like prices, not like the result of a division.

    Products whose price source field is empty or zero are skipped by the rule. Conversely, if all the conversions result in zero, that row is deleted — the catalog never has zero sale prices.

    How to set who and which products a rule applies to

    ColumnWhat it sets
    Activea disabled rule is not applied
    Prioritywhich price the storefront takes if a group has several: a lower number means higher priority; on a tie the lower price wins
    Start Date / End datethe promotion period, see promotion dates
    Price from / Price tothe rule works only within this price range, edges included. Without “Price to” the limits aren't checked at all
    Sort orderthe sequence in which rules are applied. It matters more than it seems — see below
    Notefor yourself: why the rule was created
    Price source fieldwhich product price the sale price is calculated from
    Customer groupwho the price is for, for example retail, wholesale, dealers, dropshippers — you create these groups yourself in the customer groups directory. Each group sees its own price
    Signed-in customers onlythe price is visible only to customers who are signed in to their account. Such a price overrides the regular sale price

    A rule has more columns than fit in the window: “Price source field”, “Customer group” and “Signed-in customers only” appear after you scroll horizontally.

    Product filtering

    Which products a rule applies to is set in a separate condition builder. Select the rule row and expand the “Custom filter” section below the table: the condition is built from product grid fields — category, brand, availability, stock, any catalog field.

    Below the builder, the system shows the condition you've built in plain language — check against this line. Save the finished condition with the button in the panel.

    An empty filter means “all products” — and it's the most common reason a promotion spreads to the whole catalog.

    The first rule by “Sort order” claims the product. Rules are applied one after another, and a product that already has a price for this customer group is skipped by the following rules.

    A general “minus 5% on everything” rule placed first won't let the narrower “minus 20% on clearance” work. Put narrow rules above general ones. “Signed-in customers only” prices are calculated separately: such a rule doesn't claim a product from a regular rule of the same group and isn't blocked by it.

    Promotion dates

    The “Sale price” field and exports (Prom, Rozetka, feeds)Site storefront
    Before “Start Date”the field isn't filled — feeds get the regular price. The discount columns of the Prom XLSX file are filled right away together with the dates: Prom itself keeps track of the discount period therethe price appears right after applying: the storefront doesn't check the start date
    After “End date”on the next apply the field is reset to zero, and feeds get the regular priceon the next apply expired prices are deleted

    After the end date the rule itself is disabled and “Sale price” is reset to zero — both for a rule-based promotion and for a manual card price whose end date has passed. Applying doesn't touch a valid manual price from the card; a value typed straight into the grid's “Sale price” column may be overwritten by the next apply.

    Product grid row for Dudao K15Pro showing the regular price 1002 and the sale price 902
    1Price
    2Sale price
    1. Price — the regular price of the product, 1002.
    2. Sale price — the price after the rule with dates is applied, 902.

    Dates take effect when rules are applied, not at midnight. Applying runs on the button, a batch update of price lists, saving a card or a price change in the grid. A promotion end is handled by any apply, across the whole catalog, even one that touched a single product. A promotion start sets the price only on products the apply touched; for a batch update, only those it changed. If promotion products aren't updated from price lists daily, click “Apply rules to products” on the start day — and if nothing was applied in the day after the end.

    For a storefront promotion “from Monday”, create the rule disabled and enable it on the right day.

    How to apply rules to the catalog

    A new or changed rule changes nothing until rules are applied. Applying is triggered in two ways:

    • With the button with a magic wand in the rules window (tooltip “Apply rules to products”);
    • Automatically — at the end of a batch update of price lists, and only for products that changed in that run.

    What happens during applying:

    1. Sale prices previously created by rules are deleted. Prices entered manually in the product card are left alone.
    2. Prices with an expired end date are deleted — all of them, including those entered manually in the product card — and rules with such a date are disabled.
    3. Active rules set new prices one by one according to their conditions.
    4. Prices are rounded and adjusted to the rounding step.
    5. The catalog field “Sale price” is reset to zero for products that lost a rule-based promotion and filled with the valid sale price — but only if no formula is set for this field. The formula takes precedence. Along with it, the discount columns of the Prom XLSX file are filled or cleared if you have a Prom template (discounts in the Prom file).
    The same order with the two forks that most often cause surprises: the narrow rule didn't work or the price didn't reach the field
    YesNoYesNo“Apply rules” or the end ofa batch update of price listsSale prices previouslycreated by rules are deleted.Manual ones are left alonePrices with an expired date aredeleted,and rules with such a date aredisabledActive rules one by one,in sort orderDoes the product already have apricefor this customer groupand the same “Signed-in customersonly”?The rule skips the product:the first by order claimed itThe rule calculates the price.Price → % → * → +/− —the last filled column overrides therestRounding and rounding stepIs a formula setfor the “Sale price” field?The formula takes precedence —the sale price doesn't go into thefieldThe “Sale price” fieldis filled with the result
    • Action or result
    • Decision: the path depends on the answer

    This answers the question “why did promotions disappear after price lists were updated”. They didn't disappear: they were recalculated from the suppliers' new prices. That's exactly what rules are for.

    If applying was interrupted

    Applying is a series of separate database writes with no shared rollback. The steps run in the order of the list above.

    • If it was interrupted midway, rule-based prices are already erased, and new ones were set only by the rules that had time to finish. The other products are left without a rule-based promotion. Manual prices from the product card aren't affected.
    • If it was interrupted before the last step, the “Sale price” field keeps the value from the previous apply.
    • Running it again is safe. It again starts by erasing all rule-based prices and sets them from scratch, so there will be no duplicates.

    Limits of a single apply

    • There's no ceiling. The system has no limit on the number of products or rules: each active rule processes all products that pass its filter.
    • There's no queue. The button runs applying as a single request to the server. Until the response arrives, the button is inactive and the message “Processing data, please wait” stays at the bottom.
    • If everything went through, “Operation completed successfully” appears. If the server returned an error, the browser shows a window with its status.

    What happens to prices already set

    A price set by a rule stays in the catalog until the next apply that touches this product. Each apply first erases prices created by rules and only then sets them again — from the rules that are currently active.

    What you didWhat happens to prices
    Cleared “Active” on an active rulePrices are removed right away: saving the change recalculates promotions across the whole catalog using the remaining active rules.
    Deleted a ruleAlso right away: deleting recalculates promotions across the whole catalog.
    Enabled the rule againPrices return on the next apply — recalculated from the current source price, not the ones from before disabling.
    Changed the percentage, filter, dates or other columnsNothing, until rules are applied with the button or a batch update.
    A product stopped passing the rule's filter, fell outside “Price from / to” or its source price became zeroThe sale price disappears on the next apply that touches this product.

    Which products each kind of apply touches:

    • the button with a magic wand, disabling or deleting a rule — the whole catalog;
    • a batch update of price lists — only the products changed in that run;
    • saving the product card — that one product;
    • changing a price field of one product in the catalog grid — that one product.

    So if a product dropped out of a rule's filter but the batch update didn't change it, the old sale price stays on it until you click the button or save the card.

    Applying writes the price to the field for products that have a valid sale price for the default group; a promotion only for other customer groups and a “Signed-in customers only” price don't go into this field — and so not into exports either. A product that lost a rule-based promotion (the rule was disabled or deleted, the product dropped out of the filter) gets zero in the field on the apply that touched it; a passed end date resets the field on any apply. A valid manual price from the card stays.

    Scenarios

    All labels below are columns of the “Promotions / Discounts” window. After each scenario you still need to apply the rules, otherwise nothing changes in the catalog.

    A category sale at minus 15% until the end of the month

    What to do. Add a rule, choose the regular price in “Price source field”, enter -15 in the “%” column and leave the other calculation columns empty. In “Custom filter”, set a category condition and save it. Set “End date” to the last day of the month, “Rounding step” to 10, and turn on “Active”.

    What you get. Every product in the category gets a price 15% lower than its regular one, rounded up to the nearest ten. When the regular price changes after a batch update, the sale price is recalculated from the new one.

    What won't happen. The promotion won't disappear exactly on the end date: expired prices are removed by the next apply. Products with a manual sale price in the card for the same customer group are skipped by the rule.

    A promotion with a crossed-out price on Prom or another marketplace

    What to do. A rule: “%” with a minus sign (-7), the “Quantity price (wholesale)” checkbox cleared, “Customer group” — retail (the default), the products you need in “Custom filter”, promotion dates. Apply the rules and check the “Sale price” column in the grid. Then in the export template: for an XML/YML feed — the price + oldprice tag pair (as for Prom), for the Prom XLSX file — nothing extra, the discount columns fill in by themselves (discounts in the file).

    What you get. “Sale price” holds a price 7% lower, the feed sends it together with the regular one, and the marketplace shows the old price crossed out. After the end date the next apply resets the field to zero, and the feed sends only the regular price again.

    What won't happen. The “Quantity price (wholesale)” checkbox makes it a quantity price — then “Sale price” isn't filled and the discount doesn't reach the marketplace. A positive number in “%” is a markup: the price ends up higher than the regular one.

    Tiered wholesale price: from 5 pieces and from 20 pieces

    What to do. Create two rules with the “Quantity price (wholesale)” checkbox ticked and the same “Customer group”. In the first, “Quantity” 5 and “%” -5; in the second, “Quantity” 20 and “%” -10.

    What you get. One product gets both prices: for discounts, a rule skips a product only when this group already has a price with the same quantity. Different tiers don't interfere with each other.

    What won't happen. A third rule with the same quantity as one of the first two won't work on these products if it's lower by “Sort order”. Quantity discounts don't fill the catalog's “Sale price” field.

    Minus 20% on one brand and minus 5% on everything else

    What to do. Two rules for the same customer group. The narrow one: “%” -20, a brand condition in “Custom filter”, “Sort order” 1. The general one: “%” -5, empty filter, “Sort order” 2.

    What you get. The brand's products get minus 20%, all others minus 5%. The narrow rule goes first and claims its products; the general one skips them.

    What won't happen. The discounts don't add up: a brand product won't get minus 20% plus another minus 5%. If you swap the “Sort order”, the general rule claims the whole catalog and the narrow one doesn't work anywhere.

    UAH 300 off products from 5,000 to 20,000

    What to do. Enter -300 in the “+/-” column, 5000 in “Price from” and 20000 in “Price to”.

    What you get. The rule affects only products whose value in the field from “Price source field” is within these limits, edges included.

    What won't happen. Without “Price to”, “Price from” alone limits nothing, and the rule applies to all products in its filter. Products outside the limits may be claimed by the next rule by “Sort order”.

    Minus 5% for wholesale customers on products over 1,000

    What to do. Click “Add promotion/discount rule”. In the rule row: “%” — -5, “Price source field” — the regular price, “Price from” — 1000, “Price to” — a number higher than your most expensive product, for example 9999999. “Customer group” — your wholesale group (a column on the right; you need to scroll the table to it). Leave the “Quantity price (wholesale)” checkbox cleared.

    What you get. Wholesalers always see the new price, regardless of quantity, on all products from 1,000 inclusive. Other customers see the regular price.

    What won't happen. Without “Price to” the discount applies to all products, not only those over 1,000. If you need quantity prices, tick “Quantity price (wholesale)” and fill in “Quantity”.

    What to do when prices aren't what you intended

    What you seeWhyWhat to do
    The promotion spread to the whole catalogthe rule has an empty filter — that means “all products”select the rule row, set a condition in “Custom filter” below the table and save it
    The rule is created, but there are no pricesrules haven't been appliedclick the magic wand button in the rules window
    Something other than intended took effectseveral calculation columns are filled — the last one winsleave only one filled: “Price”, “%”, “*” or “+/−”
    A coefficient with a minus sign raised the pricea negative coefficient means division, not subtractionto lower by an amount use the “+/−” column, for a percentage use “%”
    The narrow rule didn't workthe product was already claimed by a rule higher in “Sort order”move the narrow rule above the general one
    On the storefront the promotion started before the datethe storefront doesn't check the start datekeep the rule disabled until the right day
    On the promotion start day “Sale price” is still emptyrules haven't been applied that day yetclick the apply button or wait for a batch update
    The promotion didn't end on the date — the site or marketplace still shows a discountexpired prices are removed on the next apply of rulesapply the rules, then export the feed
    The “sale” price came out higher than the regular one“%” has a positive number — that's a markupenter the percentage with a minus sign
    “Sale price” is empty although the rule worksthe rule has “Quantity price (wholesale)” ticked — it's a quantity price and doesn't go into the fieldclear “Quantity price (wholesale)” if you need a promotion
    The price didn't change for some productstheir price source field is empty or zerocheck which field is chosen as the source
    The sale price didn't get into the “Sale price” fielda formula is set for this field — it takes precedenceturn off the formula or leave it as is
    A customer sees a different price than the managerthe price is tied to a customer group, and there's also a “signed-in customers only” pricecheck the customer's group and whether there's a signed-in-only rule
    The wholesale price applies from the first piecethe “Quantity” field isn't filled in the discount rulespecify from how many pieces the price applies
    The discount applied to all products, not from the set priceonly “Price from” is filled — without “Price to” the limits aren't checkedfill in “Price to”

    FAQ

    Why did the promotion start on the storefront before the start date?

    The storefront doesn't check the start date: the price appears right after rules are applied. The “Sale price” field and exports do take the date into account. For the storefront, keep the rule disabled and enable it on the right day. Learn more

    How do I send a promotion to Prom so customers see a crossed-out price?

    Fill in “Sale price” with a rule that has a percentage with a minus sign and no “Quantity price (wholesale)” checkbox, and in the export template send it together with the regular price. Step by step

    Will the regular price return on the marketplace after the promotion ends?

    Yes: any apply of rules after the end date resets “Sale price” to zero, and the feed sends the regular price. If there was no apply in the day after the end (a batch update, saving a card), click the button yourself. Promotion dates

    Why did the general rule work instead of the narrow one?

    A product that already has a price for this customer group is skipped by the following rules. Put narrow rules above general ones in the “Sort order” column.

    Will rules overwrite sale prices I set manually?

    No. Applying recalculates only prices created by rules. The exception is prices with a passed end date: applying deletes all of them, manual ones too.

    Why did sale prices change after price lists were updated?

    Rules are applied automatically at the end of a batch update for products that changed in that run. The sale price was recalculated from the supplier's new price.

    I disabled a rule — when will its prices disappear?

    Right away: saving the change, like deleting a rule, recalculates promotions across the whole catalog. Learn more

    Can I fill in both a percentage and a coefficient?

    You can, but only the last filled column in the order “Price → % → * → +/−” takes effect. Keep exactly one filled.

    How do I give a discount only to wholesale customers?

    With one rule where “Customer group” is the wholesale group. Only customers in this group will see the price. Example: minus 5% for wholesalers on products over 1,000.

    Can I make a promo code discount with promotion rules?

    No, a rule has no promo code field. A discount “for insiders” is given with a separate customer group and a rule for it. Site coupons on Elbuz Cart are in the “Coupons” section of the store settings.

    Where to find it and who has access

    The rules window has no menu item of its own: you open it from the product grid.

    Menu
    Directories → Base product catalog → Products
    Other entry points
    product grid → additional operations menu → “Promotions / Discounts”
    From the product card
    the sale prices section — a manual price for one product, not overwritten by rules
    Access right
    the product grid (the “Products” window in “Group permissions”)
    Prepare
    customer groups, if the price isn't for all customers
    The “Promotions / Discounts” window with the toolbar and the rule table header
    1Apply rules to products
    2Price source field
    3Price
    4Quantity price (wholesale)
    5Sort order
    1. Apply rules to products — runs all active rules over the catalog.
    2. Price source field — the price field the calculation starts from.
    3. Price — the calculation columns, together with %, * and +/- to the right of it.
    4. Quantity price (wholesale) — makes the rule work only from a given quantity.
    5. Sort order — the order in which rules are applied.

    Related topics

    • If the sale price is calculated from the wrong regular price — Product markups. How the regular price is calculated from the supplier's price automatically — what it gives your store.
    • If you need to understand when rules are applied on their own — Batch update.
    • If the “Sale price” field isn't filled — Catalog formulas.
    • If you need a manual sale price for one product — Product card.
    • If you need to create a wholesale customer group — Contacts.

    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