Trade scheme management is the definition, execution and settlement of the discounts, free goods and incentives a brand offers its channel — calculated consistently wherever the sale happens, and reconciled to a claim the parties agree on.
Why trade scheme management matters
Trade spend is typically one of the largest lines in a consumer-goods P&L, and it is the least controlled. Schemes are designed centrally, applied by hundreds of people in the field, and claimed back weeks later by distributors working from their own records. Every step is a place for the number to change.
The failure is rarely dramatic. It is a scheme applied at the wrong slab, a benefit given twice, a claim submitted for outlets that were not eligible — small errors at large volume. Disputes then consume finance and sales time at month end, and the disagreement is usually not about intent but about arithmetic done in two places.
How trade schemes work
A scheme has three parts, and precision in each is what makes it settleable:
- Eligibility — who qualifies and over what period: which customers, groups, territories or channels, and whether the scheme is judged per document or across a period.
- Condition — what must be true to earn the benefit: a quantity, a value, a specific item or item group, or a combination of these with and/or logic.
- Benefit — what is given: a percentage or absolute discount on the line, free goods, free goods from a defined group, or points credited to the account.
Slab structures are common — buy 10 get 1, buy 25 get 3 — and introduce the most valuable behaviour in the mechanism: an order just below a slab boundary is worth flagging, because a small increase changes the economics for both sides.
Settlement then closes the loop: consumption is recorded, budgets are drawn down, and a claim is generated on an agreed cycle.
An example
A scheme offers 3% on orders above 50,000 in a month, and 5% above 80,000. A distributor reaches 78,400. Under the scheme as written they earn 3%, or 2,352. Ordering 1,600 more moves them to the 5% slab, worth 4,000 — a 1,648 improvement for 1,600 of additional purchase. Nobody spots that at month end by reading a ledger; it has to surface while there is still time to act.
Common variations
- Per-document vs. period schemes. Applied to a single order or invoice, or accumulated across a month or quarter.
- On-invoice vs. off-invoice. Deducted on the invoice, or settled later as a claim or credit note — which changes both cash flow and how the discount is reported.
- Budgeted schemes. Capped by an account or territory budget, so spend cannot exceed plan.
- Purchase-side schemes. The same mechanics applied to what a business buys rather than what it sells.
Limitations worth stating
Schemes are easy to launch and hard to retire. Overlapping schemes create ambiguity about which applies and whether they stack, and that ambiguity is usually resolved differently in the field than in finance. The safeguard is a single authoritative calculation — one engine, one set of rules, evaluated at posting rather than at the point of estimation — so what a rep quotes, what a distributor claims and what head office computes are the same number by construction rather than by reconciliation.
How xMatix supports trade scheme management
xMatix Rewards runs a scheme engine covering fifteen scheme types, with conditions expressed over quantity, value, item and item group using and/or or custom logic. Benefits can be line-level percentage or absolute discounts, free items, free item groups, or reward points on the account.
Schemes carry per-account budgets with tracked utilisation and a consumption ledger, an approval workflow, and a claim-generation frequency — so entitlement, spend against budget and the resulting claim are one chain rather than three reconciled records.
The calculation is authoritative rather than advisory: schemes are recomputed server-side when the document posts, so an estimate shown during order capture in the field cannot diverge from settlement. Schemes apply in take-order and catalogue ordering flows alike, including offline capture on the mobile app. When an order sits just below a slab, Sense Assist raises a scheme-gap nudge stating the shortfall and what reaching the next slab is worth.
Discount groups and rule-based account groups sit alongside, so pricing, discounting and scheme segmentation are driven by the same account attributes.
Related: how trade schemes work in FMCG · trade scheme & promotion management software · distributor management system · secondary sales
