Coupon Stacking: What It Is, How It Works, and How Merchants Can Control It

Coupon stacking is when a shopper combines more than one discount, like a promo code and loyalty points, on a single order. Seven in 10 shoppers across every income group are now engaging in active value-seeking behavior, according to Deloitte’s 2025 holiday retail survey, and stacking multiple ways to save is one of the clearest signs of it.

For merchants, that raises a real question: how many discounts should a customer be allowed to combine, and where’s the line before it eats your margin? This guide covers what coupon stacking is, how shoppers do it, real examples, and a practical framework for deciding which of your incentives, coupons, loyalty points, gift cards, referral credit, and membership perks, should be allowed to stack together.

TL;DR

• Coupon stacking means combining two or more discounts, like a promo code and loyalty points, on one order
• Stores that allow stacking usually control it on three separate levels: product discounts, order discounts, and shipping discounts, not with one on-off setting
• A new promotion should default to non-stacking until a merchant deliberately allows combinations, since accidental stacking is what quietly erodes margin
• Coupons are only one of six incentive types that can stack: promo codes, loyalty points, gift cards, store credit, referral credit, and membership perks each carry a different risk profile
• Gift cards, store credit, and loyalty point balances are payment methods, not discounts, so they shouldn’t be forced to compete with a coupon code
• Limiting stacking abuse comes down to usage caps, minimum order thresholds, and watching redemption velocity, not blocking stacking altogether

What Is Coupon Stacking?

Coupon stacking is the practice of combining two or more discounts on a single order instead of using just one. A shopper who applies a 20% off code, then redeems loyalty points on the same cart, is stacking coupons.

The term gets used alongside a broader one: discount stacking. Discount stacking covers any combination of price reductions, sale pricing, automatic promotions, bundle deals, and coupon codes together. Coupon stacking is the narrower case where at least one of the combined discounts is a code the customer actively enters or redeems.

Three coupon types show up in most stacking situations. A manufacturer coupon comes from the brand that makes the product and is usually honored across many retailers. A store coupon comes from the retailer itself and only works there. A digital promo code is issued for online use and is the most common format merchants control directly.

Whether stacking is even possible depends entirely on the merchant’s own rules. Some retailers allow one code per order and nothing more. Others allow a code to combine with automatic sale pricing but not with a second code. There’s no universal standard, which is exactly why merchants need a deliberate policy rather than a default.

How to Stack Coupons: A Step-by-Step Walkthrough

Stacking coupons correctly comes down to knowing what’s allowed and applying discounts in the right order.

• Know the coupon types you’re holding: A manufacturer coupon, a store coupon, and a digital promo code are often treated differently by the same retailer, so check which category each one falls into before you try to combine them.

• Check the store’s stacking policy before checkout: Most retailers publish their combination rules in an FAQ page or in the terms attached to the promotion itself. If nothing is published, assume only one code per order until proven otherwise.

• Apply discounts in the right order: Sale pricing typically applies first, then a coupon code, then loyalty points or cashback last, since points usually redeem against whatever balance remains after other discounts.

Watch for common mistakes that void a stack:

• Entering a manufacturer coupon and a store coupon in the wrong sequence at checkout
• Trying to combine two codes that are flagged by the retailer as mutually exclusive
• Missing a minimum purchase threshold required for the second discount to apply
• Assuming a sitewide sale automatically stacks with a welcome code, when many sitewide sales explicitly exclude new promo codes

If a stack fails silently, check the order total against each discount individually before assuming the system is broken. Most failed stacks come down to an exclusion rule the customer didn’t see, not a technical error.

Coupon Stacking Examples

Real stacking scenarios usually involve two or three discount types layered on top of each other, not just two competing percentage-off codes.

• A shopper buys a skincare set during a seasonal sale, applies a first-order welcome code on top of the sale price, then redeems loyalty points to cover the last few dollars of the total
• A subscription box customer on their third reorder applies an automatic loyalty discount for repeat subscribers and uses referral credit earned from inviting a friend
• A shopper buys a bundle deal, then applies a birthday reward code for free shipping on the same order
• A shopper redeems a store credit balance left over from a return, then applies a percentage-off code to the remaining balance due

Each of these works because the merchant deliberately decided which combinations were safe. The next section breaks down how to make that decision for every incentive type you run, not just coupon codes.

Coupon Stacking Is Only One Kind of Stackable Incentive

Coupon stacking is just one slice of a bigger question: which of your incentive types should ever be allowed to share a cart. Most merchants ask “how many coupons can a customer use?” when the real question is which of six incentive types are allowed to combine.

Three of these rows need more explaining than a table cell can hold.

Store credit and coupon codes

Store credit gets implemented two different ways across the industry. It can be a discount that competes with, and often blocks, promo codes. Or it can be a payment instrument that doesn’t. Neither approach is universal. Check which one your platform actually uses before promising customers anything.

If store credit is configured as a discount, a customer holding store credit and a percentage-off code gets told to pick one. That’s a poor experience for someone who was already refunded once. The guardrail worth setting either way: exclude store credit redemption on clearance items and already-heavily-discounted carts. A return shouldn’t become a route to buying below cost.

Referral credit and welcome offers

The double dip nobody documents: a new customer arrives through a friend’s referral link and receives referral credit. They also grab the sitewide welcome code advertised on your homepage. You’ve now paid twice to acquire one customer, and taught them that first-order pricing is negotiable.

The safer default is to make referral credit and acquisition offers mutually exclusive. Referral credit can still stack with ordinary sitewide referral marketing promotions that aren’t specifically aimed at new customers. Watch for referral credit farming too. Self-referral, disposable email addresses, and credit stacking across a small ring of linked accounts are the usual abuse patterns.

Membership perks as stacking depth

Reframe stacking depth as a benefit customers earn, not a leak merchants have to tolerate. A workable mechanic: non-members get one code per order, members get a code plus points redemption, and top-tier members get a code plus points plus free shipping. The margin exposure is the same at every tier. For members, though, it buys retention instead of just handing out a discount.

Why Merchants Allow (or Restrict) Coupon Stacking

Merchants allow coupon stacking, specifically, because it can lift average order value. That same flexibility creates real margin risk.

The case for allowing it: stacking gives customers a reason to add one more item to hit a threshold. It reinforces loyalty discount programs by letting points feel additive rather than substitutional. It also clears inventory faster during a sale when a customer feels they’re getting an exceptional deal.

The case for restricting it: two codes compounding on the same order can erode margin faster than either discount was designed to allow. Stacking also risks cannibalizing full-price sales, since customers who would have paid full price learn to wait for a combination. And it distorts campaign attribution when a sale can’t be traced to a single promotion.

Most merchants land somewhere in between. Allow one promo code plus points or store credit, and treat two order-level percentage codes as mutually exclusive by default. That single rule, once decided, is what your ecommerce promotions calendar should be built around.

How to Prevent Coupon Stacking Abuse

Preventing abuse doesn’t mean turning stacking off. It means putting specific limits around it.

• Set explicit stackable or non-stackable flags on every code, rather than relying on staff memory to enforce a policy
• Cap the total stacked discount at a maximum threshold per order, so no combination of codes can push a discount past a set ceiling
• Use unique, trackable codes with a redemption limit per customer, instead of one shared code that can circulate publicly
• Monitor redemption velocity for signs of abuse, since a sudden spike in stacked redemptions from a small cluster of accounts is a common fraud signal
• Review coupon scam patterns periodically, since abuse tactics evolve faster than a static policy can account for

These controls work because they target the behavior that actually causes damage, uncapped combination depth and unlimited redemption, rather than banning stacking outright and losing the AOV benefit it can deliver.

How 99minds Enforces Discount Stacking Rules

Stacking lives on the coupon rule in 99minds, not on an individual code. A merchant sets the stacking decision once on the rule, and every code minted from it inherits it identically.

Stacking itself is three independent axes rather than one switch: whether a code combines with product discounts, with order discounts, and with shipping discounts. That separation lets a merchant allow a code to sit on top of a product-level sale while still blocking it from combining with another order-level promo, without one setting forcing the other.

All three flags start unchecked on a new rule. A rule is non-stacking until a merchant deliberately opts in, which is the safe default and worth stating plainly, since unintended discount pile-up eating margin is the actual fear most merchants have.

The coupon type itself, fixed amount, percentage, free shipping, or free product, determines which axis a given discount occupies, so type and combination flags have to be read together when you’re setting a rule up.

Stacking is also the last of several gates, not the only one. Scope (which products or collections a rule applies to), minimum purchase requirements, usage limits, and an expiration window all decide whether a discount applies at all before stacking is even evaluated. Most real-world “stacking problems” turn out to be scope or threshold problems once you dig into them.

One Stacking Model Across Loyalty, Referral, and Promotions

One coupon rule object controls stacking for every reward type in 99minds, not just standalone promo codes.

• Every incentive that behaves like a discount, a standalone promo, a loyalty points reward, a referral reward, or a membership perk, is issued from the same coupon rule object, so a merchant learns the stacking model once and it applies everywhere, not per program
• Automation-triggered rewards, like a sign-up reward or an anniversary reward workflow, decide when a reward is issued, while the coupon rule behind that reward decides how it stacks
• A separate eligibility layer, built around cart-based conditions, can gate whether a reward applies at all, which is a different question from whether it stacks once it does apply

• Balance-type instruments, gift cards, store credit, and loyalty points balances, carry no stacking flags at all in 99minds, since they’re value the customer already holds, applied as payment against what’s owed, not a discount competing for the same order total
• That resolves the store credit ambiguity raised earlier in this guide directly: 99minds always treats balances as payment, never a configurable discount, so store credit never competes with, or blocks, a promo code

• The stacking decision is defined once and applies everywhere a merchant sells, though exactly how multiple qualifying discounts resolve at the point of sale can vary by sales channel
• Treat any specific “which discount wins” example as channel-specific rather than universal, since checkout-time resolution isn’t identical across every place a merchant sells

Should Your Store Allow Coupon Stacking? A Decision Checklist

Run through these questions before turning any stacking flag on.

• Can your current margin absorb two discounts compounding on the same order, not just one
• Does your vertical have thin enough margins that even a small stack meaningfully changes unit economics
• Is the promotion meant to drive average order value, or simply to clear specific inventory
• Do you have a way to cap total stacked discount at a maximum threshold before you turn stacking on
• Can you track redemption velocity per customer, so a sudden spike gets flagged before it scales
• Does the combination make sense from the customer’s side, or does it feel like a loophole they stumbled into

If most of these have a clear yes, controlled stacking is usually safe. If you’re unsure on more than one, start with a single allowed combination, like points plus one code, before opening things up further.

Conclusion: Get Your Stacking Rules Right

Coupon stacking isn’t a yes or no decision. It’s a set of choices about which of your incentives, coupons, loyalty points, gift cards, store credit, referral rewards, and membership perks, should be allowed to share a cart, and under what conditions.

The merchants who get this right treat stacking as three separate axes, product, order, and shipping, default to non-stacking, and cap the total discount depth rather than banning combinations outright. They also recognize that balances like gift cards and store credit aren’t discounts at all, so they never need to compete with a coupon code in the first place.

99minds builds this exact model into its coupon management platform, alongside the loyalty points, referrals, memberships, and gift card tools that make up the rest of your incentive stack, so every reward type follows one stacking rule instead of a different one per program.

Frequently Asked Questions on Coupon Stacking