Festive Margin Leaks: Auditing Promo Stacking, NDR Surges and Return Claims Before Big Billion Days

For Indian D2C brands and marketplace sellers, Big Billion Days and the Great Indian Festival compress a large share of the year's orders into a few weeks. The operational risk in that window is badly misunderstood: the danger is not that new problems appear. It is that every per-unit problem you already tolerate gets multiplied by your new volume — at exactly the moment nobody has time to look at a reconciliation sheet.

A ₹40 weight-slab discrepancy is a rounding error at 400 orders a day. The same ₹40, unfixed, at 3,000 orders a day for eighteen days is ₹21.6 lakh. Nothing about the leak changed. Only the multiplier did.

Three leaks account for most festive margin loss, and all three are auditable before the sale opens. Each section below links to a deeper guide if you want the full mechanics.

Leak #1: Promotion Stacking Below Cost

The mechanism. Festive discounting is configured by different people, in different consoles, on different schedules. A category manager sets a 25% lightning deal. A growth marketer leaves last month's 15% brand coupon live because nobody wrote down its end date. The marketplace applies a bank instant-discount it funds only partially. Each decision is defensible on its own. They compose multiplicatively, and no single console shows you the composed price.

Worked example. Take an SKU at ₹2,000 MRP with a ₹1,150 landed cost (COGS plus inbound freight):

• 25% lightning deal → ₹1,500
• 15% brand coupon still active → ₹1,275
• 10% bank offer, 50% seller-funded → a further ₹64 borne by you → ₹1,211 realised
• Marketplace commission and fulfilment fees at ~18% of realised → ₹218

Net realisation ₹993 against ₹1,150 landed cost: a ₹157 loss per unit, on an SKU whose dashboard still reports a healthy 25% discount. Sell 1,400 units over a weekend and the deal has cost ₹2.2 lakh in cash to run.

The failure mode that makes this expensive is not the size of the loss per unit. It is that a below-cost price sells faster, so your worst-margin SKU wins the traffic and exhausts its inventory first.

Full mechanics, including how to detect stacking after the fact in an order export: E-Commerce Order Margin Protection: How to Stop Discount Stacking & Negative Margin Exploits.

Leak #2: The COD and NDR Surge

The mechanism. Festive demand skews heavily toward COD and toward impulse purchases, which are the two order types most likely to fail on delivery. At the same time, courier networks are running at capacity with a large share of temporary staff. The result is a sharp rise in non-delivery reports — orders marked "customer not available", "address incomplete" or "customer refused".

Some of these are genuine. Some are not: sellers widely report NDRs logged against orders where the buyer received no call, a pattern that rises with network load. You cannot tell the two apart from the status code alone, which is precisely why this leak survives — the courier's record is the only record, unless you build your own.

Worked example. 2,000 COD orders a day, an NDR rate rising from a 12% baseline to 22% under peak load, and an RTO charge of ₹110 per shipment on your rate card:

• Incremental NDRs from the surge: 200/day
• If a third convert to RTO rather than reattempt: ~66 RTOs/day → ₹7,260/day in RTO freight alone
• Plus forward freight already spent, plus the unit locked in transit for 8–12 days across your highest-demand window

The freight is the visible cost and the smaller one. The real damage is the inventory: a unit in RTO transit during peak is a unit you cannot sell during peak, and it typically returns after demand has collapsed.

How to separate genuine failed deliveries from suspect ones in your own data: Detecting Fake Courier NDR Attempts: How to Identify Doorstep Delivery Fraud.

Leak #3: Returns Arrive After the Claim Windows Close

The mechanism. Festive returns land in a concentrated wave several weeks after the sale, and they skew toward the categories most exposed to abuse — apparel worn once, electronics returned after an event. Two clocks are running at the same time, in opposite directions.

The first is your warehouse throughput, which is already saturated with outbound festive volume. The second is the marketplace's protection-claim window — Amazon's SAFE-T and Flipkart's Seller Protection Fund. These are marketplace policy windows, not statutory deadlines, and the filing period differs by marketplace, by fulfilment programme and by claim reason. Check the current policy for the specific programmes you sell under; do not plan against a remembered number, because these terms are revised.

What is consistent is the structure of the trap: a claim window starts running when the return or refund is processed, while the evidence you need to file — the return's condition on arrival — only exists at the moment the box is opened. Process that box late and the window may already have closed, so an otherwise valid claim becomes unrecoverable for a paperwork reason.

Worked example. 900 festive returns, a 12% abuse rate (~108 claimable cases), average claim value ₹1,400. Filed in time, that is ₹1.51 lakh recoverable. Clear the backlog FIFO at a rate that pushes 40% of cases past their window and ₹60,000 of it is simply gone — not disputed, just unfiled.

Detecting the abuse patterns themselves — serial returners, empty-box and swap claims: E-Commerce Return Abuse & Wardrobing: How to Stop Empty Box Thefts & Serial Wardrobers.

The Pre-Sale Checklist

All three audits share a property worth stating plainly: they are only cheap before the sale opens. Each becomes substantially harder once volume arrives, and two of them become impossible to backfill.

1. Composed price floor per SKU. Every discount mechanism in one sheet, composed, net of fees, compared to landed cost. Fix anything below the line.
2. NDR baseline per courier and pincode cluster. Computed from the last 60 days. This is the measurement you cannot create retroactively once the surge is underway.
3. Returns evidence standard, agreed and staffed. Photograph-on-open, AWB visible, timestamped, with the queue sorted by claim-window expiry rather than arrival date.
4. One owner per leak. All three failures above are cross-functional, which in practice means unowned. Name a person for each before the sale, not during it.

If you want the wider version of this audit covering courier weight-slab creep, COD remittance reconciliation and zone misclassification as well, see The Pre-Festive Ops Freeze: 6 Leaks Indian D2C Brands Must Fix Before October 1.

The Underlying Point

Festive season does not create operational problems. It prices the ones you already have, at volume, in a window where you have no spare attention to notice the bill. The brands that come out of it with their margin intact are not the ones that ran the cleverest campaign — they are the ones that walked in already knowing their numbers.