Distributing packaged snacks across 900 retail outlets through a network of regional distributors sounds like a growth story. In practice, it became a reconciliation nightmare for this Indian FMCG manufacturer. Distributors submitted scheme claims, the manufacturer could not verify sell-through at the outlet level, and every month ended in dispute. Three specific pain points drove the project.
Distributors filed GST-linked claims for trade promotions and volume incentives with no outlet-level evidence. Manual cross-checks took weeks and still left room for double-claiming.
Primary invoices showed goods dispatched to distributors. What happened after that was invisible. The sales team had no data on which SKUs were actually moving at which outlets.
Secondary sales data was compiled manually from distributor Excel sheets, emailed in, and consolidated by one person. By the time a report reached management it was three weeks stale.
| Area | Before | After Zoho |
|---|---|---|
| Scheme claim verification | Manual, 2-3 week cycle, no outlet proof | Automated CRM workflow, outlet-level evidence mandatory, 3-day turnaround |
| Secondary sales data | Excel files emailed by distributors, 18-day lag | Daily web form entry, real-time in Analytics dashboard |
| Dispute rate | Monthly disputes on average 30-35% of scheme payouts | Disputes down 43%, most resolved before payout |
| Stock visibility | Primary dispatch only, secondary was a black box | Full primary-to-outlet chain visible, batch tracked |
| Field rep accountability | Visit logs in paper registers, no link to sales outcomes | CRM visit records linked to outlet sell-through, commission tied to data quality |
| Management reporting | Monthly consolidated PDF, often incomplete | Live dashboards, weekly automated summary email to leadership |
Audited all existing distributor master data: names, GST numbers, territory assignments, and outstanding scheme claim history. Mapped 900 outlets to their parent distributors and identified 14 distinct scheme types active in the current trade year. Defined the minimum evidence required for each scheme type before a claim could be approved.
Built the distributor and outlet account hierarchy in CRM. Created a custom Scheme Claim module with mandatory fields for outlet code, scheme period, claimed quantity, and supporting secondary dispatch reference. Configured Inventory to accept secondary dispatch entries from a Zoho Creator web form shared with distributors. Set up automated stock reconciliation between primary dispatch and secondary entries.
Connected CRM and Inventory to Zoho Analytics claim reporting via native connectors. Built five dashboards: outlet sell-through by SKU, distributor performance comparison, scheme utilisation vs budget, claim anomaly flags, and field rep visit-to-sales conversion. Set up automated alerts when a distributor submitted a claim that exceeded their verified secondary dispatch for the scheme period.
Conducted virtual walkthroughs with all distributor points of contact on the secondary dispatch form. Ran two-day field training for the 18-person sales team on CRM outlet visit logging. Backfilled three months of historical secondary sales data to give Analytics enough baseline for trend analysis at go-live.
The root cause of scheme leakage was not dishonest distributors, it was absent data. When both sides could see the same outlet-level secondary sales numbers, the disagreements resolved themselves. Zoho did not change the relationship, it simply removed the information gap that made disputes inevitable.
How were the 900 outlets onboarded into Zoho CRM for FMCG distributors without a large IT team?
Outlets were bulk-imported from the existing distributor Excel masters using CRM’s import wizard. Each outlet record was linked to its parent distributor account automatically using the distributor code as a lookup key. The process took two days and required no custom development. Field reps verified and corrected their own territory records during the first week of using the system.
What stopped distributors from inflating their secondary dispatch entries to match inflated claims?
Secondary dispatch entries in Inventory were capped by the primary dispatch quantity for each batch. A distributor could not log more secondary units than they had received in primary stock for the same SKU and period. Zoho Analytics then flagged any claim where the scheme-eligible secondary quantity was less than the claimed quantity, triggering a manual review before payout was released.
Does Zoho Inventory stock tracking support GST-compliant documentation for trade promotions in India?
Yes. Zoho Inventory generates GST-compliant credit notes and debit notes that can be linked to scheme payouts. For trade promotions structured as price adjustments, the system records the scheme reference against the relevant tax invoice, ensuring the credit note carries the correct GST treatment and the distributor has a valid document for their own GST reconciliation.
Can this setup scale if the manufacturer adds more distributors or new geographies?
The architecture scales without structural changes. Adding a distributor means creating a new account in CRM, assigning it a territory, and sharing the secondary dispatch form link. Analytics dashboards are built on dynamic queries, so new distributors and their outlets appear automatically once their data starts flowing. The manufacturer tested this during the project by onboarding a new distributor in week seven without involving the implementation team.
We've helped 50+ businesses implement Zoho and NetSuite. Let's talk about yours.