Practical framework / 5 MIN READ
Make coupon combinations predictable at checkout
Translate promotion terms into a tested set of eligibility and stacking rules.
AI-assisted research and analysis for the SNS Creative Fieldbook
Sources checked 2026-11-06
A discount campaign is an executable rule, not just a headline. Customers need to know whether offers combine, and the checkout must implement the same promise.
What you will leave with: Create a small promotion test matrix that covers overlapping codes, automatic offers and threshold conditions.
Use this when
- Several promotions can be active at once.
- Customers report that codes fail or produce unexpected totals.
This is not a profit model or a universal description of how every commerce platform applies discounts.
Write the offer as a rule with inputs
Specify eligible products, customers, dates, minimum quantities or spending, usage limits and exclusions. Clarify whether thresholds are assessed before or after other discounts under the actual implementation. Include timezone and currency when they can affect eligibility.
Avoid relying on a slogan such as “20% off everything” when the configuration excludes meaningful categories. If the offer is restricted, the public wording should convey that before a shopper builds a cart. Separate a discount from a gift card or store credit, which may operate as payment rather than a price reduction.
Describe how overlapping offers should behave
List automatic promotions, welcome codes, loyalty rewards and shipping offers that could meet in the same cart. Decide which combinations are intended and which are not. Do not assume “one code per order” prevents an automatic discount from also applying.
Shopify documents combinations of product, order and shipping discounts, with behavior depending on settings and circumstances. Verify the actual platform version and configuration rather than copying arithmetic from a generic example. Sequential percentages and additive percentages can produce different totals; the customer-facing saving must match the system.
Build carts that probe the boundaries
Test just below and at the threshold, an excluded item, a mixed eligible cart, a returning customer and a previously used code. Include an expired code and a legitimate combination. Record the expected result before running the test so a surprising total is not retroactively declared correct.
Check the explanation shown when a code cannot apply. It should identify a useful reason without exposing private eligibility data. A generic “invalid” message can make a legitimate customer think the promotion itself is broken. Verify that removing an item recalculates the discount and any associated shipping benefit.
Reconcile the promise after launch
Monitor support reports and a small sample of completed promotional orders. A headline can be approved correctly while a later setting change alters the result. Assign an owner for unexpected combinations and a safe way to pause the offer without breaking unrelated purchases.
Treat a pricing error as an operational issue requiring the appropriate review, not an opportunity to blame customers for using an available code. Preserve the relevant configuration and terms. Learn from the boundary case and add it to the next test matrix. Avoid claiming a promotion’s success solely from discounted revenue without assessing the appropriate economics separately.
Make the reasoning concrete.
A fictional stationery shop offers 10% off eligible products and a separate 10% order code. In a simplified checkout where the percentages apply sequentially to a $100 eligible subtotal, the result is $81, not $80.
Verified combination
Opening: Test the actual checkout and describe only the supported saving.
Hypothesis: The offer and charged total agree.
Risk: Shipping, tax and platform rules may change the final payable amount.
Add the percentages in copy
Opening: Advertise the combination as 20% off without checking execution.
Hypothesis: The headline is easy to write.
Risk: Sequential discounts do not produce that result in this hypothetical configuration.
Use the test order as the configuration check and obtain separate economic approval. Do not extrapolate this simplified arithmetic to every platform.
Take the questions into your next brief.
Use these prompts in your own notes. Nothing is submitted from this page.
Eligibility
Which products, people and dates qualify?
Combination
What happens when each active offer overlaps?
Threshold
When and on what amount is eligibility calculated?
Boundary carts
Which cases could expose an incorrect rule?
Incident owner
Who can investigate and pause a wrong discount?
Watch for the wrong conclusion.
- Assuming percentages always add together.
- Testing only the ideal qualifying cart.
- Writing broad offer copy before checking exclusions.
Your next action
Create five boundary carts and compare their actual totals with the written promotion rules.
Sources & scope
Frameworks, worksheets and proposed tests are original editorial synthesis. Examples are hypothetical and do not report measured outcomes. Source checking is not an independent audit of effectiveness. Platform features and applicable law can change. No named human author or reviewer is claimed.
- Shopify Help Center: Combining discounts →Primary provider guidance · Supports: Documents how eligible product, order and shipping discounts can combine. Exact behavior depends on configuration and plan; examples here are hypothetical.