Stacked Discounts, Broken Margins: The Math to Run Before You Combine Codes, Bundles, and Sales

You launch a flash sale at 20% off. A week later you add a bundle deal that shaves another 15% when someone buys two products together. Then an affiliate posts your old 10%-off welcome code and it still works. None of these discounts look dangerous on their own — they were each modeled, approved, and reasonable in isolation. The problem is that customers don't experience them in isolation. They stack. And the moment three reasonable discounts land on the same checkout, you can slide from a healthy margin into literally losing money on every sale without ever running a single number that told you so.

Why stacked discounts don't just add up — they multiply

Here's the mental model most people default to: "20% off plus 15% off is 35% off." That's wrong, and it's wrong in the direction that hurts you. Discounts applied sequentially multiply against a shrinking base, not the original price. Take a $50 product. A 20% code brings it to $40. A 15% bundle discount then applies to that $40, not the original $50, bringing it to $34. A 10% loyalty or affiliate code then applies to $34, landing at $30.60. Add it up: you gave away $19.40, or 38.8% of the original price — not the 45% your gut math suggested, but still enough to wipe out most of the margin on a lean digital product, especially once you account for payment processing and any affiliate commission layered on top of that same sale.

The trap isn't that the math is hard. It's that nobody runs it, because each discount gets approved on its own merits by someone (often you, at 11pm, trying to hit a launch goal) who isn't thinking about the other two discounts that are already live.

A worked example: the $47 ebook that stopped making money

Say you sell a $47 ebook with roughly 90% gross margin after payment processing — a typical profile for a digital download with no per-unit fulfillment cost. That leaves about $42 of contributed profit per sale before you touch a single promotion. Now layer in a real-world stack a lot of creators run without noticing:

At $28.76, you've kept roughly 61% of list price — down from the 90%-margin sale you modeled. If that same order also carries a 20% affiliate commission (calculated on the discounted price, as most affiliate setups do), you're netting closer to $23 on a product you priced at $47 assuming near-full margin. That's not a discount anymore. That's a different product at a different price point that you never actually decided to sell.

The rule of thumb: cap total combined discount, not each individual one

The fix isn't to stop running promotions — flash sales, bundles, and welcome codes all genuinely move revenue. The fix is to stop approving discounts one at a time and start capping the total combined discount any single order can receive. A simple, defensible rule that works for most digital-product creators: no single checkout should ever exceed 30% off list price, combined, across every code, bundle, and sale that applies. If your gross margin sits above 90% (typical for ebooks, templates, and presets), you can flex that closer to 35%. If you're selling something with real delivery cost — a printed component, a live coaching seat with your time priced in — pull the cap down to 15-20%.

Once you have a cap, the operational question becomes: how do you actually enforce it? A few concrete tactics that work without needing custom code:

Where store.fan gives you the levers

This is exactly the kind of quiet math that's easy to skip when you're moving fast, which is why the discount tooling matters as much as the discipline. Inside your dashboard, store.fan's discount codes support start and end dates and usage limits, so a launch-week code can't quietly keep working into next quarter and stack with whatever you run next. Pair that with the store designer's content blocks to make bundle pricing explicit on the page itself — showing the bundled price as a fixed number rather than "20% off" language reduces the odds a customer also tries to apply a percentage-based code on top of it. If you haven't set up codes yet, it takes minutes once you create your store, and the same dashboard gives you a customer list so you can see exactly who used which code and when, which is invaluable when you're auditing a stack after the fact.

It's also worth remembering why this math matters more for digital creators than it might for a traditional retailer: on paid plans, store.fan takes 0% platform fees, so the margin you protect is margin you actually keep. That makes disciplined discounting a direct lever on take-home income, not just a vanity metric buried in a spreadsheet. If you're comparing options, the pricing page lays out what's included at each tier, and a live example store shows how bundle and sale pricing can be presented cleanly without inviting stacking confusion.

A discount you didn't model isn't a discount — it's an accident that happens to look like a sale.— store.fan team

Bundles are the sneakiest stack of all

Sitewide sales are easy to spot because they're loud and temporary. Bundles are the quiet risk because they feel permanent and structural — you built the bundle once, priced it, and moved on. The problem is that a bundle discount almost never gets re-evaluated once a sitewide promotion launches on top of it. If your "Ebook + Workbook" bundle is already priced 15% below buying both separately, and then you run a 25% sitewide flash sale, the bundle buyer is getting a stack whether you meant to offer one or not. The fix is to explicitly decide, per bundle, whether sitewide codes are allowed to apply to it at all — and to say so clearly in your discount code setup rather than leaving it to chance.

FAQ

None of this is an argument against running promotions — flash sales, bundles, and welcome codes are genuinely some of the highest-leverage tools available on a storefront, and store.fan is built to make them easy to launch. The argument is for running the sequential math before you stack them, setting one combined-discount ceiling instead of approving each promotion in isolation, and using the dashboard's start/end dates, usage limits, and customer list to enforce that ceiling automatically instead of trusting memory. Do the arithmetic once, set the cap, and every discount you run after that protects the margin you actually meant to keep.