What scheme management actually covers
A trade scheme has a life cycle, and most distributors only manage the middle of it. The brand designs and funds a scheme. It has to be communicated to the field, applied correctly at the point of order, paid out to the retailer, recorded against the right invoice, and then claimed back from the brand with enough documentation to survive scrutiny.
Four of those six steps are where money goes missing, and none of them are visible in a P&L. Scheme leakage does not appear as a line item — it appears as a margin that is mysteriously thinner than the price list implies. That is why a distributor can carry a 6% headline margin, work hard, and still wonder where the money went.
The scale is the reason this matters more than it appears. At 15–25% of revenue, trade schemes are usually the largest controllable cost in the business — larger than salaries, larger than transport. A 20% leak on that is worth more than most distributors earn in a quarter.
The six scheme types used in Indian trade
They are not interchangeable. The common mistake is running whichever structure the brand circulated rather than the one that fits the objective — and each type fails in a different way.
Quantitative (free goods)
High reconciliation effortBuy Q, get F free. The classic 10+1 or 20+2.
- Best for:
- Opening new outlets, because the retailer's cash outlay does not change.
- Fails when:
- Free units move through stock without an invoice line, so they are the hardest type to reconcile and the easiest to over-issue.
Flat / value discount
Low reconciliation effortA fixed rupee amount off per case or per order.
- Best for:
- Clearing ageing stock, because the discount is explicit and easy to time-box.
- Fails when:
- Least risky. The discount appears on the invoice, so claims are straightforward.
Slab / volume
Medium reconciliation effortA rate that improves once the outlet crosses a volume threshold.
- Best for:
- Lifting volume from outlets that already stock you.
- Fails when:
- Retailers pull orders forward at period end to cross the threshold, creating a spike then a dead month, often followed by returns.
Seasonal / festive
Medium reconciliation effortA time-boxed scheme tied to a festival or season.
- Best for:
- Capturing demand peaks where the consumer is already buying.
- Fails when:
- Post-expiry payouts. Field staff keep honouring a scheme after it closes, and the brand rejects the claim.
Retailer-specific / conditional
High reconciliation effortApplies only to a named outlet class, territory or SKU set.
- Best for:
- Rewarding range compliance and protecting shelf position.
- Fails when:
- Applied to ineligible outlets or SKUs, which is the single most common source of rejected claims.
Bulk pack / combo
Medium reconciliation effortA special pack or bundled SKU sold at a combined price.
- Best for:
- Raising average bill value without discounting the base SKU.
- Fails when:
- Inventory drift. If the combo is not set up as its own SKU, stock counts stop matching.
The three points where money leaks
Leakage is usually blamed on field indiscipline. It is more often a data problem: scheme planning, field execution and claim reconciliation run on disconnected systems, so nothing checks anything else.
01Distributor pass-through
The brand funds a scheme, but not all of it reaches the retailer — or more than intended does.
- Schemes applied to SKUs that were never eligible
- Two overlapping scheme periods both honoured on the same invoice
- Manual calculation errors on slab thresholds
- Discretionary extensions granted by a salesman to close a month
02Field activation
The scheme exists on paper but never reaches the outlet, so the spend buys nothing.
- Salesmen unaware a scheme is live, or working from an outdated circular
- Scheme communicated verbally and applied inconsistently across a beat
- No proof the outlet was told, so under-performance cannot be diagnosed
- Outlets outside the eligible class receiving it anyway
03Claim settlement
You paid the scheme out but the brand short-pays or rejects the claim.
- Scheme value calculated on MRP rather than landed cost
- Missing invoice references linking the payout to a specific sale
- Period dates that do not match the scheme circular
- Claim reversals not processed when goods come back as sales returns
No single transaction in that list looks wrong on its own. That is precisely why manual reconciliation never finds it — the loss only exists in aggregate. More on the mechanics in preventing scheme leakage.
Why claims get short-paid
Most schemes are brand-funded, wholly or partly, and you recover the cost by raising a claim. Claims fail on documentation far more often than on entitlement. The four recurring reasons: scheme value calculated on MRP rather than landed cost, missing invoice references linking a payout to a specific sale, period dates that do not match the scheme circular, and claim reversals never processed when goods came back as sales returns.
That last one is the quietest. When a retailer returns stock that carried a scheme benefit, the benefit should reverse. On manual systems it almost never does, so you have paid a scheme on goods you took back and are still carrying.
The fix is timing as much as tooling. Reconcile payouts against claims monthly, not quarterly. By quarter end the invoices needed to substantiate a disputed claim are scattered across three months of records, and the practical outcome is that you write off the difference rather than fight for it.
What scheme management software has to do
Use this as the evaluation checklist. A system that reports on schemes after the fact is a report; the value is in what it prevents at order entry.
01Rule-based scheme configuration
Every live scheme is defined once with its eligibility conditions — SKU list, outlet class, territory, date window, slab thresholds — rather than living in a circular and someone's memory.
02Automatic application at order entry
The correct scheme is applied when the order is taken, on the salesman's phone, against the live rules. Nothing is calculated by hand and nothing depends on the salesman remembering.
03Overlap and eligibility control
Blocks a second scheme on the same line when two periods overlap, and refuses application to an ineligible SKU or outlet class. This is where most pass-through leakage stops.
04Landed-cost valuation
Values free goods at what you actually paid rather than at MRP, so the claim you raise matches the cost you incurred and does not get short-paid.
05Claim generation and reconciliation
Assembles claims with the invoice references and period dates attached, then reconciles what the brand settled against what you paid out — monthly, not at quarter end.
06Claim reversal on returns
When goods come back as a sales return, the associated scheme benefit reverses automatically. Unreversed claims on returned stock are a quiet, recurring loss.
07Scheme performance analytics
Shows which schemes moved secondary sales and which only moved primary dispatch, by SKU, outlet class and beat.
08Field visibility
Live schemes visible to every salesman in the app, with the eligible SKU list, so activation does not depend on a WhatsApp forward.
Registers vs spreadsheet vs scheme engine
A spreadsheet is better than a register at recording what happened, but neither can do the one thing that matters — check eligibility on the line, in the market, before the scheme is given.
| Registers | Spreadsheet | Scheme engine | |
|---|---|---|---|
| Scheme applied at order entry | By memory | After the fact | Automatically, by rule |
| Ineligible SKU blocked | No | No | Yes |
| Overlapping periods caught | No | Manually, if noticed | Yes |
| Free goods valued at landed cost | Rarely | If formula is right | Always |
| Claim reversed on sales return | No | Manual | Automatic |
| Claim assembled with invoice refs | Manual | Manual | Generated |
| Leakage visibility | None | None | Per SKU and outlet |
| Typical leakage | 20–30% | 20–30% | Materially lower |
Leakage bands reflect SpireStock's published scheme research for Indian general trade. Figures reviewed August 2026.
Size your own leakage
A worked example on a mid-sized distributor, using the middle of the published leakage band:
- Monthly sales = ₹40,00,000
- Schemes at 6% of sales = ₹2,40,000 per month
- Leakage at 20% = 2,40,000 × 20% = ₹48,000 per month
- Annual leakage = 48,000 × 12 = ₹5,76,000
- As a share of annual sales = 5,76,000 ÷ 4,80,00,000 = 1.2%
₹5,76,000 a year — 1.2 percentage points of margin
On a 6% headline margin, that is a fifth of the entire margin lost to a problem that produces no visible symptom.
Frequently asked
What is scheme management in FMCG distribution?
Scheme management is the design, deployment, application and reconciliation of trade promotions across the distribution channel — flat discounts, quantitative free-goods schemes, slab incentives, seasonal offers and retailer-specific deals. It covers configuring each scheme, applying it correctly at order entry, tracking what was paid out, and claiming the brand-funded portion back.
How much do Indian FMCG companies spend on trade schemes?
Roughly 15–25% of revenue goes to trade schemes, which makes it one of the largest and least controlled lines in the business. Independent measurement suggests a large majority of trade promotions fail to break even on ROI when measured properly, so both the spend and the waste are substantial.
What is scheme leakage and how much is normal?
Scheme leakage is the gap between the promotional spend intended and the benefit that actually reaches the right recipient. Manual scheme management in India typically causes 20–30% leakage. It comes from schemes applied to ineligible SKUs, overlapping periods claimed twice, post-expiry payouts, and discretionary extensions by field staff.
Why is a 10+1 scheme not a 10% discount?
Because the free unit spreads across eleven delivered units, not ten. The effective discount is 1 ÷ 11 = 9.09%. The general formula for a Q+F scheme is F ÷ (Q + F) × 100. Budgeting at 10% instead of 9.09% distorts scheme provisioning materially across a wide range over a quarter.
Should schemes be costed on MRP or landed cost?
Landed cost. Free goods cost you what you paid for them, not what they retail for. Calculating scheme cost on MRP overstates your outlay and is one of the most common reasons brand claims are rejected or short-paid.
What does scheme management software do?
It holds every live scheme as a set of rules with eligibility conditions, applies the right one automatically when an order is taken, blocks ineligible or overlapping application, values free goods at landed cost, generates claims with invoice references attached, reverses benefits when goods are returned, and reports which schemes actually moved secondary sales.
Can schemes be managed in Excel?
For one brand and a handful of simple schemes, yes. It breaks down once you carry several principals with concurrent schemes, because eligibility has to be checked per line at order entry and no spreadsheet does that in the market. Distributors handling three to five principals with multiple live schemes each routinely lose lakhs a year to reconciliation errors.
How often should scheme claims be reconciled?
Monthly. By quarter end the invoices needed to substantiate a disputed claim are spread across three months of records, and most distributors write off the difference rather than fight for it. Monthly reconciliation also surfaces a misconfigured scheme before it runs for another eight weeks.
Why do slab schemes cause problems at period end?
Retailers pull orders forward to cross the threshold, buying stock they cannot sell through. The result is a sales spike, a dead following month, and often returns or pressure for another scheme to clear what they took. Set slab thresholds per outlet from historical offtake rather than uniformly across the territory.
Should scheme performance be measured on primary or secondary sales?
Secondary — what the retailer actually sold through. A scheme that lifts primary dispatch but not secondary has simply moved stock into the retailer's godown, and it usually comes back as damage claims, returns, or demand for another scheme.