Trade Schemes Gone Wrong: When Schemes Create Returns
Why "Buy 10 Get 2 Free" creates 14% return liability. The scheme discipline framework that matches promotions to actual retailer velocity.
Trade schemes are a subsidy for returns, and nobody does the math
There is a ritual that plays out across Indian FMCG distribution roughly eight times a year (four quarter-ends, two festival seasons, and two occasions that brands invent because they need a reason to push stock). A brand principal announces a trade scheme — "Buy 10, Get 2 Free" is the classic construction, though the variations are endless — and within days the entire channel lurches into motion. Salesmen call their retailers with the good news. Retailers, confronted with the prospect of free goods, say yes. Primary billing numbers spike. Excel sheets turn green. Bonuses are earned. Everyone is happy.
Sixty days later, those "free" cases start coming back. Expired, unsold, and very much the distributor's problem. The happiness, it turns out, was borrowed from the future, at an interest rate that nobody bothered to calculate.
I want to walk through why this happens, why it keeps happening despite everyone involved being reasonably intelligent, and what you can actually do about it if you're a distributor who has noticed that your scheme-month margins mysteriously evaporate by the end of the following quarter.
Not sure how much you're losing to expiry?
Run a free inventory waste audit — find your bleeding SKUs in 60 seconds. No sign-up required.
Run free auditThe arithmetic that everyone avoids
Let's take a specific retailer. He sells 50 units a month of Product X, consistently, month after month. This is his velocity, and it is the single most important number in this entire discussion, though almost nobody tracks it at the retailer level.
The brand announces a scheme: buy 100, get 12 free. Your salesman presents this to the retailer as a windfall — "Sir, 12 units free, that's pure profit." The retailer, who is not stupid but who also does not have a system that tells him his own velocity, thinks about the margin on 12 free units and says yes. He now has 112 units of Product X sitting in his store.
At 50 units a month, he needs 2.24 months to sell through 112 units. If the product arrived with four months of shelf life remaining (which is optimistic — scheme products notoriously show up with three months or less), he is theoretically fine. But retailers don't sell in perfectly linear curves. The first 50 move at normal pace. The next 50 move at normal pace. The last 12 sit there, because nobody walks into a store and says "I'd like to buy the thing I always buy, but today I'd like 20% more of it." Consumer demand didn't change. Only the stock in the channel changed.
Those 12 units — the "free" ones — expire. The retailer returns them. And the distributor eats a loss that is precisely equal to the margin he earned on those 12 units, plus the handling cost, plus the logistics of collecting them, plus the warehouse space they occupy while he argues with the brand about credit notes. The scheme created a 10.7% return liability at the moment of billing, and nobody noticed because the moment of billing was a celebratory occasion.
This is not an edge case. This is the default outcome of aggressive trade schemes, and it happens at scale across thousands of distributors and lakhs of retailers every quarter.
Why rational people make irrational inventory decisions
The interesting question is not "why do brands run aggressive schemes" — that's straightforward, they need to hit quarterly targets and scheme-driven primary billing is the fastest lever they have. The interesting question is why retailers keep accepting quantities they cannot sell, and why distributors keep enabling this despite being the ones who absorb the loss.
The retailer's reasoning is actually quite logical given his information constraints. He sees free goods as free margin. He doesn't track his own velocity with any precision (he has a rough intuition, but rough intuition is exactly the wrong tool for a decision with a 60-day feedback loop). He faces social pressure from the salesman, who is standing in his shop with a scheme flyer and a quota to fill. And crucially, the downside is asymmetric in a way that favors saying yes: if the stock sells, he made extra money; if it doesn't sell, he returns it. The return option, in his mental model, is free.
It is, of course, not free. Returns damage his relationship with the distributor. They block shelf space that could hold faster-moving products. They tie up his working capital for weeks. And increasingly, distributors are pushing back on return acceptance, which means the "I'll just return it" insurance policy doesn't always pay out. But these costs are diffuse and delayed, while the scheme benefit is immediate and tangible, and humans are not well-calibrated for that kind of tradeoff.
The salesman, meanwhile, operates in a system that is almost perfectly designed to produce over-pushing. His incentive is primary sales — cases billed to the retailer. Returns are a "later" problem, and crucially, they are someone else's later problem. The salesman's bonus is calculated on billing. The distributor's P&L absorbs the return. In any system where the person making the decision doesn't bear the cost of the decision, you get exactly this kind of outcome, and you get it reliably, every quarter, forever.
The hidden costs are not actually hidden if you look
Distributors tend to think of scheme-related returns in terms of the direct product cost — "I lost ₹15,000 worth of goods to expiry this month." This is like measuring the cost of a car accident by the price of the bumper. The real costs are structural and compounding.
Start with working capital. When a distributor bills ₹5,00,000 of scheme stock, that cash is committed. If 12-16% of it comes back as returns, that's ₹60,000-₹80,000 that was locked up for 60-90 days and then evaporated. For a distributor running on 4-5% net margins (which is generous for Indian FMCG), that ₹80,000 return wipes out the profit on ₹16,00,000 of sales. You need to sell sixteen lakhs of goods just to recover from the returns on five lakhs of scheme billing. This is not a rounding error.
Then there's the logistics cost of collecting returns. Someone has to visit the retailer, verify the expiry, load the cases, transport them back to the warehouse, inspect them, sort them, and file a claim with the brand. In a market with 800 retailers, this is not a weekend project. I've spoken to distributors who estimate their return-handling cost at ₹15-25 per case, which on low-value FMCG products (a case worth ₹200-300) adds 5-10% on top of the product loss.
And then there's the cost that nobody puts on a spreadsheet: data pollution. When your primary sales numbers are inflated by scheme-driven over-billing, every downstream decision gets worse. Your demand forecast is wrong. Your inventory planning is wrong. Your next order to the brand is wrong. The brand's production planning, based on your inflated orders, is wrong. You have created a small, self-reinforcing ecosystem of bad decisions, all originating from the gap between what was billed and what was sold.
Velocity data is the boring answer to an expensive problem
The solution to scheme-induced returns is unglamorous, which is probably why it doesn't get implemented more often. It is: know the actual selling velocity of every product at every retailer, and use that number to cap scheme quantities.
That's it. That's the whole thing.
If you know that Retailer A sells 40 units of Product X per month, and someone tries to bill him 100 units because there's a scheme running, your system should flag this. Not block it — distributors don't want systems that prevent sales, and rightly so — but flag it, visibly, with a note that says "this retailer's 60-day sell-through capacity is 80 units, and you're billing 112 with scheme goods." Let the salesman override it if he wants, but make him acknowledge it. Make him own the return risk explicitly rather than discovering it two months later when the cases come back.
This requires tracking secondary sales (or at minimum, replenishment frequency) at the retailer level, which is genuinely hard. Most Indian distributors operate with billing software that tells them what went out the warehouse door and has very little visibility into what happens after that. The stock enters a retailer and enters a black box. It either gets reordered (good) or comes back expired (bad), and the distributor finds out which one happened only after the fact.
Building retailer-level velocity data is a multi-month project, not a software installation. You need consistent tracking, you need your salesmen to record secondary data during beat visits, and you need to maintain it long enough to establish reliable baselines. But once you have it, it transforms every scheme decision from "how much can I push" to "how much can this retailer actually sell," which is a fundamentally different (and much more profitable) question.
The conversations nobody wants to have
The hardest part of fixing scheme-induced returns is not technical. It's organizational. It requires having three uncomfortable conversations that most distributors avoid.
The first conversation is with your salesmen, and it sounds like this: "Your primary billing this quarter was ₹42 lakhs, which is excellent. Your returns from the previous quarter's scheme billing were ₹6.8 lakhs, which means your net contribution was ₹35.2 lakhs. I'm going to start measuring you on net contribution, not gross billing." This conversation is uncomfortable because it changes the incentive structure, and salesmen who have optimized their behavior for gross billing targets will push back, sometimes by threatening to leave. Some of them should leave. The ones who stay and adapt will build more sustainable retailer relationships and generate better long-term numbers.
The second conversation is with your retailers, and it sounds like this: "Bhai sahab, I know the scheme says buy 100, get 12 free. But your average monthly sale of this product is 40 units. If you take 112 units, you're sitting on nearly three months of stock, and half of that shelf life is already used up. Let me bill you 60 units with 7 free — you still get the scheme benefit, and nothing expires." This conversation is uncomfortable because you are literally talking a customer out of buying more. Every instinct in sales says this is wrong. But a retailer who buys 60 and sells 67 is vastly more profitable than a retailer who buys 100 and returns 22, and he's also a happier retailer, which means he stays your customer longer and causes fewer headaches.
The third conversation is with the brand, and it requires data. "Your Q3 scheme generated ₹50 lakhs in primary billing from my depot. Returns attributable to that scheme were ₹8 lakhs, which is a 16% return rate against a scheme cost you budgeted at 10%. Here is the data by retailer, by SKU, by batch. The scheme design pushed 22% more stock than aggregate retailer velocity could absorb. For Q4, I'm proposing we restructure the scheme to match secondary capacity — either smaller bonus ratios, or retailer-tiered quantities based on velocity, or a consumer-facing discount that pulls demand rather than a trade scheme that pushes stock." Brands, in my experience, are surprisingly receptive to this conversation when you bring data. They don't want returns either. They're just operating with the same information deficit everyone else is — they can see primary billing but not secondary movement, so they design schemes based on what they can measure rather than what matters.
Why this keeps happening despite everyone knowing better
There's a structural reason the Indian FMCG channel tolerates scheme-induced returns at the scale it does, and it's worth naming explicitly: the cost is distributed across the chain in a way that prevents any single actor from feeling enough pain to fix it unilaterally.
The brand eats some of the cost through credit notes (maybe 40-60% of the return value, after negotiation and delay). The distributor eats the rest, plus all the handling costs. The retailer loses shelf space and working capital but usually gets the return accepted. No single party bears the full cost, which means no single party has sufficient incentive to fix the system, which means the system persists in its current dysfunctional equilibrium. This is a classic coordination problem, and like most coordination problems, it gets solved by whoever has the best information, not by whoever has the most authority.
For distributors, the path forward is to become the entity in the chain with the best information. Know your retailers' velocity. Track scheme-level return rates. Calculate the true ROI of every scheme including returns and handling costs. When you can walk into a brand meeting and say "here's what actually happened versus what your scheme assumed would happen," you become a partner in scheme design rather than a warehouse for excess inventory. That's a meaningfully different position, and it's one that directly translates to margin preservation.
The uncomfortable truth is that some distributors actually benefit from the current system — the ones who hit primary billing targets, collect scheme margins, and successfully push return costs onto the brand. If that's your situation, none of this applies to you. But if you're the distributor whose net margins are getting eaten by returns that trace back to scheme-driven over-billing, the answer is velocity data, honest conversations, and the organizational courage to optimize for net contribution rather than gross billing. It is genuinely that simple, and genuinely that hard.
ShelfLifePro tracks stock from dispatch through secondary sale, with scheme-level return attribution and retailer velocity baselines. If you're tired of discovering return liability two months after it was created, [see how it works](/fmcg/).
See what batch-level tracking actually looks like
ShelfLifePro tracks expiry by batch, automates FEFO rotation, and sends markdown alerts before stock expires. 14-day free trial, no credit card required.