FMCG Distributor Integration Case Study: The Order-Inventory-Rebate Data Chain
Background
A leading FMCG company earned the vast majority of its revenue offline, through a network of hundreds of first-tier distributors and tens of thousands of terminal stores. Before channel digitalization, its data situation was typical for the industry:
- Distributors placed orders by emailing or messaging Excel files, keyed into the ERP daily by a coordination team;
- Distributor inventory was reported monthly in spreadsheets, already stale by the time it reached headquarters;
- Rebate accounting relied on manual comparison of shipments against attainment data, with a cycle spanning weeks and constant disputes from distributors.
The ask was clear: see channel sell-through, calculate channel spend accurately, and do it without forcing distributors to replace their systems.
The solution: one order-inventory-rebate data chain
The company built three links on an iPaaS platform.
Orders. Distributors onboarded in two batches by digital maturity: top distributors with ERPs such as Kingdee or Yonyou connected via APIs, with requisitions mapped automatically into ERP sales orders; mid-tier distributors ordered through a brand-provided portal feeding the same platform. Every order carried the "distributor code + external order number" idempotency key, and ERP approval and shipping statuses flowed back within minutes — distributors could see live order status for the first time.
Inventory. Top distributors pushed daily inventory snapshots via API or file, normalized to base units and hung on the organization tree; central and regional warehouses synced near real time from the company's own WMS. The company gained, for the first time, channel-wide inventory visibility from central warehouse to distributor warehouse, with a weekly distributor turnover dashboard.
Rebates. Rebate policies — monthly attainment, quarterly ladders, special programs — were structured on the platform; shipment and payment data flowed in daily from the ERP to compute each distributor's progress and estimated rebate automatically; approved results generated settlement documents written back to the ERP. Distributors could check their attainment detail in the portal at any time, turning month-end arguments into continuous reconciliation.
The phased rollout
Phase one (about three months): API-direct orders for top distributors, master data governance, SKU mapping, and the idempotent order link. Phase two (about three months): full order coverage via the portal plus inventory snapshots and the organization tree for top distributors. Phase three (about four months): structured rebate policies, attainment computation, and portal-based reconciliation.
Three decisions mattered most. Master data came first — the opening two months went almost entirely into product and distributor master data, and later smoothness traced back to that. No distributor was forced to change systems — API where possible, portal otherwise — which drove onboarding rates far above a "uniform DMS" mandate. And read-only before bidirectional — backhaul first, then price and policy distribution once trust was built.
Outcomes (qualitative)
Orders moved from same-day manual entry to minute-level automation, with coordinators shifting to exception handling. Channel inventory went from lagging monthly reports to T+1 snapshots, enabling overstock alerts. The rebate cycle shrank from weeks to days with visibly fewer disputes. And the distributor data asset became the input for later smart replenishment and diversion-monitoring initiatives.
Lessons
The hard part of FMCG channel integration is never the technology — it is distributor heterogeneity and willingness, which a tiered onboarding strategy solves. Rebates are the most sensitive data for distributors and therefore the strongest lever: data in exchange for policy transparency is a trade both sides win. And master data investment is silent early on, but it caps the quality of every link that follows.