In FMCG the list price is almost never the price.
Between list price and what a customer actually pays sit trade schemes, slabs, free goods, retro-claims and settlement — and the gap between the two is a substantial share of revenue. That, together with batch and shelf life on nearly every movement, is what makes FMCG SAP distinctive. The transaction volume is high; the pricing logic behind each transaction is higher still.
What makes FMCG and Consumer Products different from a standard SAP landscape.
None of this is exotic. All of it is known. It goes wrong anyway, because the test plan is usually written against the process rather than against the way the process actually behaves here.
Promotions settle long after they sell
A scheme runs, a distributor claims, the claim is validated against actual sales, and settlement follows — often across periods. The accrual raised at sale and the amount finally settled must reconcile. That reconciliation is where money is lost, and it cannot be tested inside a single cycle without deliberately constructing the elapsed state.
Pricing conditions interact in ways nobody holds in their head
Slabs, free goods, combination offers, customer-specific rates and channel differences all resolve on one document. The failure is rarely a wrong price on a simple order — it is a wrong price on the combination that only a few customers ever trigger.
Batch and shelf life touch nearly every movement
Batch determination, FEFO picking, remaining shelf-life checks at despatch and customer-specific shelf-life requirements sit on ordinary transactions. A rejected delivery here is a customer-facing failure, not an internal one.
Returns are a normal flow, not an edge case
Damaged goods, expiries, market returns and distributor claims for them run continuously, and each has credit, stock and tax consequences. Treating returns as an exception under-scopes a routine part of the business.
Secondary sales data arrives from outside SAP
Distributor sell-out data feeds claims, schemes and replenishment, and it arrives incomplete, late or restated. Testing the calculation without testing the ingestion tests half the process.
The failures that reach production.
Each of these is quiet. Nothing errors, nothing is flagged, and no check that reads configuration would have caught it.
What was accrued at sale and what is settled on the claim drift apart, and the difference is only visible once claims arrive — well after go-live.
Pricing conditions interact, so a new offer alters the outcome for a customer segment nobody was testing.
Configuration that is slightly stricter than the commercial agreement stops trucks, and it surfaces in the first real despatch window.
Where we would put the effort.
Scope is agreed with you before anything starts. This is where we would argue it belongs in FMCG and Consumer Products, and why.
Promotion lifecycle including settlement
Scheme through sale, accrual, claim and settlement run as one scenario with constructed elapsed state, so the reconciliation is proved rather than assumed.
Pricing combination coverage
The interacting combinations that real customers trigger, not one clean order per condition type.
Batch, FEFO and shelf-life scenarios
Determination and remaining-life checks tested against the commercial agreement, not only against the configuration.
Returns and credit flows
Damages, expiries and market returns tested for their stock, credit and tax consequences.
Industry knowledge, stated plainly.
Our exposure to FMCG and consumer products comes from Rufouss engagements and from consultants who have worked in consumer goods organisations, including the pricing, distribution and order-to-cash side of SAP.
Where we do not have that depth, we say so rather than take work on the assumption we will pick it up as we go. That answer has cost us engagements. It is still the right one, and it is the reason this page lists nine industries rather than thirty.
About SAP quality in FMCG and Consumer Products.
What is the single most under-tested area in FMCG SAP?
Claims settlement. Promotions are tested at the point of sale, where they are visible, and settled weeks later, where they are not. The reconciliation between accrual and settlement is where the money is, and it rarely fits inside a test cycle unless the state is deliberately constructed.
How do you cover pricing without testing every combination?
By testing the combinations that actually occur rather than the full matrix, which is usually far too large. Real order history tells you which combinations exist; the long tail matters less than the twenty that carry most of the volume and most of the value.
Is trade promotion a good automation candidate?
The pricing calculation is — it is deterministic and it is re-run at every scheme change. The claims and settlement side involves external data and judgement, and is usually better handled as designed scenarios with prepared data.
Where this work usually starts.
Take any one of these on its own, or as one stage of a longer arc.
Tell us where your FMCG and Consumer Products programme is.
No business case needed, and a straight answer either way — including when the honest answer is that you do not need us yet.