Stacking discounts — cashback, coupons, and sale prices — works less often than deal forums suggest: the layers almost never all combine at once and rarely in the order you assume. The workable sequence at most US retailers is: sale price first (it changes the item's price), then coupons (applied to the discounted price unless stated otherwise), then cashback (paid afterward on what you actually paid). A worked example on a $100 jacket at 30% off with a $20-off coupon and 5% card cashback: $70 after the sale, $50 after the coupon, $2.50 back — a net $47.50, not the $45 you get from wrongly compounding every layer.
Knowing which layers combine and which cancel each other is the difference between modest, repeatable savings and checkout dead-ends. This guide maps the stack, layer by layer, with the exclusions that matter.
What stacks with what?
| Layer | Changes the price? | Typical stacking behavior |
|---|---|---|
| Sale / markdown | Yes | Base layer; almost everything else applies on top |
| Manufacturer coupon | Yes | Usually stacks with store sales; excluded from clearance sometimes |
| Store coupon | Yes | Often cannot combine with other store coupons; one per order |
| Loyalty points / member price | Yes or deferred | Member pricing replaces sale pricing sometimes; read the tag |
| Cashback portal | No — pays later | Stacks with the above if you click through before checkout |
| Card cashback | No — pays later | Stacks with everything; independent of the merchant |
The key distinction: layers that change the price compete with each other, while layers that pay you afterward stack freely. Two price-changing discounts rarely combine; post-payment rebates generally don't care what discounts you already took.
Why do coupons exclude sale and clearance items?
Exclusions are how retailers cap the stack. Coupon terms routinely exclude clearance, doorbusters, gift cards, certain premium brands, and "limited edition" lines — and exclusions apply before the code ever runs, which is why a valid-looking code dies at checkout. The terms also usually name whether the coupon applies to the original price or the sale price; on sale-priced items, a "20% off full price" coupon may be worth nothing beyond the existing markdown. Read the exclusion line before building your plan around a code — it is the single most predictive line in the fine print.
Do cashback portals pay on the discounted price?
Portals pay a percentage of what the merchant reports as the qualifying sale, which is typically the subtotal after coupons and before tax and shipping — but policies differ by portal and merchant, and cashback is not guaranteed until confirmed. Two practical rules: trigger the portal click-through before adding coupons from elsewhere (switching tabs mid-checkout can break tracking), and never let a portal's rate decide the purchase, because a pending 5% can vanish on a tracking failure. Card cashback is the most reliable layer precisely because it is independent of the retailer's systems.
What is the optimal order of operations?
- Start with the sale price and check whether it is a real markdown or a perpetual "was" price.
- Apply the single best price-changing code; test whether a second combines, but expect one per order.
- Check coupon terms for category and brand exclusions before you build the cart.
- Click through a cashback portal with tracking enabled before checkout, once the cart is final.
- Pay with a card whose rewards category matches; that layer always stacks.
- Screenshot the final total and the portal confirmation — disputes are won with records.
How much can realistic stacking save?
As an example calculation (not a market claim): a $100 item at 30% off with one $20 coupon and 5% combined post-payment cashback nets about 52% off. That is close to the practical ceiling; claims of "80% off with stacking" usually involve compounding errors, store-credit accounting, or buying things you would not otherwise buy. Note the trap on the other side: chasing a 5% cashback on a $60 impulse add is spending $57 to earn $3. The stack optimizes a purchase you have already decided to make; it does not justify the purchase.
The Consumer Financial Protection Bureau maintains consumer tools covering how credit card rewards work if you want the card layer in detail. Retail terms and rates change constantly; everything here is subject to change.
The bottom line
Remember the two-layer rule: price-changers compete, pay-laters stack. Run sale, then one coupon, then portal and card, keep the screenshot, and treat any savings above half off as a sign you mis-added something. Skip the stack entirely when it is nudging you toward items you hadn't planned to buy — a discount on a non-purchase is still zero percent off your budget.
What about store credit, gift cards, and loyalty points?
These layers behave differently, and misreading them is how paper savings never become real ones. A "$20 back in store credit on $100" promotion is deferred value, not a discount: it arrives weeks later, often expires in 30 to 90 days, and only spends at the same retailer. Stack it last and only when you will genuinely return — an unused store credit is a donation with extra steps. Loyalty points are the same animal with worse exchange rates: their cash-equivalent value is whatever you can actually redeem them for, usually one cent or less per point on modest programs, and redeeming for merchandise typically values them lower still. Gift cards you bought at a discount are the exception — a prepaid 10% discount is a clean, stackable price cut, provided the card is for a store you already use.
Two corner cases complete the map. First, stacked promotions sometimes change the return math: pay $50 cash for an item that came with $20 store credit, then return it, and the refund may be reduced by the credit — or the whole return may be barred on promotion-heavy orders. Second, price adjustments interact unevenly with these layers: retailers that refund a price drop after purchase may compute it against the pre-coupon price, shrinking your adjustment. Neither trap makes stacking bad; both make record-keeping the deciding skill. Screenshot the cart, the codes, and the confirmation email, because the layers you cannot document are the layers a dispute process will not credit.
For more context, read How to tell if that “was” price is actually real.
For more context, read free shipping threshold.
For more context, read Timing purchases by the retail calendar.