A “buy more, save more” offer needs a precise definition of what counts. Does the threshold apply to one product, any products in a category or items from a manufacturer? Which customer groups qualify, and what happens when a shopper removes one item? Answer those questions before configuring the promotion.
Discounts PRO supports category, manufacturer and product discount rules, with settings such as fixed or percentage amounts, customer group, dates, repeat behavior and tax inclusion. Use a small written specification so the rule and the storefront message describe the same offer.
Write the offer in testable language
Instead of “discount cameras,” write an explicit example: “Eligible retail customers receive the configured category discount when the cart contains the required quantity of qualifying cameras during the promotion dates.” Then specify the actual threshold, amount and eligible items in your implementation notes.
Do not assume the extension interprets every combination of units and repeated discounts in the way your marketing text suggests. Confirm the configured behavior with a controlled cart and the documentation for your installed version.
| Decision | Question to settle |
|---|---|
| Scope | Product, category or manufacturer? |
| Threshold | Which quantities qualify and which items contribute? |
| Amount | Fixed amount or percentage, applied to which unit? |
| Audience | Which customer group receives the offer? |
| Timing | Which dates and store time zone define the active period? |
| Interaction | What happens with existing specials and coupons? |
Test immediately below and above the threshold
If an illustrative offer requires three qualifying units, test two, three and four units. Include a mixed cart with eligible and ineligible products. If products can belong to more than one category, include those products in the test selection.
Next, remove an eligible item after the discount appears and confirm the total recalculates. Change quantities from both the product page and cart controls. The promotion should remain understandable when shoppers cross the threshold in either direction.
Make repeat behavior explicit
A repeated offer and a once-per-order offer can produce different results when the cart contains several qualifying groups of items. Use simple numbers on staging to reveal the difference. Record the eligible subtotal, the intended discount and the final amount.
For example, a hypothetical fixed discount of five currency units applied twice should be distinguishable from a single five-unit discount. This is an arithmetic illustration, not a recommended live price or a claim about every rule configuration. Verify the extension’s unit and repeat settings against your intended offer.
Review customer groups, taxes and overlapping rules
Test a guest and representatives of the customer groups your store uses. An offer that appears correctly for a retail customer should not silently affect a wholesale group unless that is intended. Check the order summary with the tax configurations relevant to your supported customers.
Then add an existing product special or coupon to the test cart. Document how overlapping rules behave and confirm that the combined result is commercially acceptable. Avoid relying on a general assumption that all promotions always stack or that none of them do.
Keep the customer message close to the result
Use a clear multilingual cart message that names the relevant offer. If shoppers need one more qualifying item, ensure the explanation matches the actual threshold. Do not show a promised discount before you know which products and customer group qualify.
On phones, check that promotional messages do not obscure quantity controls, the final total or the checkout action. The checkout testing checklist includes the interaction with the order summary and payment journey.
Reconcile the promotion after launch
Compare a small set of completed orders with the written rule, not just the displayed banner. Review how discount amounts are recorded in order totals and passed to downstream reports. If supplier prices change during a campaign, revisit your own commercial calculations; our supplier-update workflow helps keep source changes controlled.
At the end of the campaign, check that the date restriction works and that expired promotional text is removed from the relevant pages. Keep the tested configuration and results as a reference for the next offer rather than recreating the rule from memory.