The Margin Stack30 DAYS FREE + Free Analytics Session $500

What's Inside / The money / S3 Discounting

Section S3 · The money

An ecommerce discount strategy built on who actually needs the code

Most discount strategy is a calendar: a sale in spring, one at end of financial year, a big one in November. Section S3, Discounting, plans it around people instead, because the same 15% off is a smart offer to one customer and a pure giveaway to another.

The short answer

Discounting bands every customer by how dependent they are on a code, scores every promo's give against the margin behind it in the Promo Ledger, and lets you simulate one promo or the whole calendar before it runs. Discount-dependent buyers worth moving back to full price become a win-back list.

5.0 on Google · 100+ businesses · $153M revenue influenced

S3 Discounting · Promo Ledger
Blufire Promo Ledger showing discount given, realised CM1 and a verdict for each promotion

Real product screen, shown on sample data.

What the section is

Every promo, and where its give went.

The top of the section reads the period's discounting in one row: discount given, the CM1 left after it, the promo CM1 rate against your house average, and how many promos are underwater or margin-thin. Below that, the give is split by mechanic into product give, which hits CM1, and free-shipping give, which lands in CM2.

The Promo Ledger then lists every code, automatic discount and manual adjustment, with its orders, share of new customers, discount given, realised CM1 and a verdict. Click a row for the redeemers behind it. For the full method on scoring a single code, see which discount codes are quietly giving margin away.

See the money group→
Promo LedgerEvery promo's give against its CM1, sorted by discount given, with a margin verdict on each row.
Where the give goesDiscount dollars split into product give and free-shipping give, per mechanic.
Dependency bandsEvery customer banded by the share of their orders that used a discount.
Promo-Restructure SimulatorPrice one promo, or the whole promo calendar, before it runs.
“Quick to take action, and bring a lot of experience… a partner who can strategically execute and adapt to fast-paced industries.”
Braden Hodges · Google review· Google review
Cheapest LiquorA$0 to A$1Min under 12 months, in one of retail's most price-brutal categoriesRead the case study →
PanasonicRainCoCheapest LiquorKing CoolingAuto ComfortiHeat & CoolAACAEInsider Experience SportsInterosPeter JacksonLa TrobeToy World
Dependency bands in depth

Four kinds of customer, four different offers.

Dependency is a lifetime property, so the bands read every customer's whole history rather than one date range. Full-price loyal customers buy without a code, and discounting them is pure leak. Mixed customers sometimes use one. Discount-dependent customers used a discount on more than half their orders. Discount-only customers have never bought without a promo.

Each band shows its customer count, the CM1 it has produced and the discount dollars it has received, so you can see where the give actually lands. A common pattern is the smallest bands soaking up the most discount while the biggest band barely needs it.

That changes the strategy question. It stops being "how deep should the sale go?" and becomes "who should see it?". A code aimed at discount-only buyers is an acquisition cost you can weigh against new-customer CAC. The same code sent to the full list hands margin to people who were going to pay full price anyway. Guests with no customer record are excluded from the bands, so the read is about people you can actually target.

Who uses it

Planning the calendar with the whole table.

The CMO or retention lead owns the calendar. Before a promo is briefed, it goes through the Promo-Restructure Simulator, and the audience is cut by dependency band rather than sent to the whole list.

The founder reads the verdict column. A promo marked margin-thin gets restructured; one that is underwater gets killed. The share of new customers on each row says whether a code is finding people or just paying existing ones.

The CFO reads discount given against realised CM1 and the promo CM1 rate against the house average, because a promo calendar is a margin budget whether or not anyone calls it one.

Ops plans stock against the calendar that survives the simulator, not the one copied from last year.

What changes

From a sale calendar to a discount strategy.

TodayWith Blufire

Every promo goes to the whole list.

The audience is cut by dependency band, and full-price loyal customers keep paying full price.

Free shipping is treated as free.

Free-shipping give is its own line, landing in CM2 next to product give.

Manual discounts and one-off adjustments are never reviewed.

Every code, automatic and manual discount sits in one ledger with a verdict.

The calendar is judged after it runs.

One promo or the whole calendar is simulated on margin first.

The core metric, worked

One promo week, planned two ways.

1,000 customers expected to buy in a 15% off week. A$90 average order, 50% CM1 at full price, so each order earns A$45, or A$31.50 after a A$13.50 discount. Plan A sends the code to everyone. Plan B holds it back from the full-price loyal band, who buy at full price regardless.

Worked example / demonstrative numbers
Full-price loyal (600), plan A: discount given on orders they would place anyway, 600 × A$13.50−A$8,100
Mixed (250): 150 would buy anyway, 150 × A$13.50 given away−A$2,025
Mixed (250): 100 genuinely new orders, 100 × A$31.50+A$3,150
Discount-only (150): all new orders, 150 × A$31.50+A$4,725
Plan A, code to everyone: incremental CM1−A$2,250
Plan B, code withheld from full-price loyal: incremental CM1+A$5,850

Same discount, same week, same customers. Plan A loses A$2,250 of margin. Plan B earns A$5,850, a swing of A$8,100, which is exactly the give that went to people who did not need it.

The split between "would buy anyway" and "genuinely new" is the assumption to test, not trust. The ledger shows realised CM1; proving incrementality needs a holdout, which Experiments runs. Try your own depth and volume in the discount impact calculator.

FAQ

Questions operators ask.

Target discounts at the customers who need one to buy, and keep them away from customers who pay full price anyway. Plan the calendar on contribution margin rather than revenue, simulate each promo before it runs, and review every code after it ends. The depth of the discount matters less than who receives it.
Look at the share of each customer's orders that used a discount across their whole history. Customers who have never bought without a promo are discount-only; more than half discounted makes them discount-dependent. Blufire bands every identified customer this way and shows the CM1 and discount dollars each band carries.
Yes. Free shipping is money you would otherwise have collected, so it is a give just like a percentage off. It reduces shipping revenue rather than product margin, so Blufire records it as free-shipping give in CM2, separately from product give, which reduces CM1.
As often as the margin supports, which is a question you can answer before the sale rather than after. Frequent promos train customers to wait for a code. Simulating the calendar against your dependency bands shows whether another sale mostly reaches new buyers or mostly discounts people who would have bought anyway.

Ready to see what you are actually keeping?

Free for 30 days. Free to install.