Most FMCG founders build their early distribution the same way. A handful of distributors are onboarded through personal relationships. Orders come in over WhatsApp. A sales rep follows up. Someone enters the order into a spreadsheet or Tally. Delivery happens. The process works well enough at twenty dealers. It works reasonably at fifty.
Somewhere between eighty and a hundred and fifty dealers, it stops working. Orders get missed. Pricing inconsistencies surface in the monthly reconciliation. A distributor disputes an invoice. The operations team is spending more time managing order chaos than building the network. The founder is fielding complaints that should not be reaching them.
This is the operational wall that most FMCG startups hit before ₹10 crore GMV. The product did not fail. The market did not close. The infrastructure was not built to handle the load that growth created.
Why Infrastructure Decisions Get Deferred
The deferral is understandable. In the early stages of an FMCG startup, every rupee of operating budget is competing against product development, marketing spend and working capital for inventory. Infrastructure that is not visibly broken does not get prioritised against things that are visibly on fire.
WhatsApp ordering works at twenty dealers. A spreadsheet tracks orders well enough at thirty. The founder knows the infrastructure is fragile but the fragility is not causing operational failures yet. The investment in fixing it gets deferred to next quarter, then the quarter after that.
The problem is that distribution infrastructure does not fail gradually. It fails suddenly, at the point where network complexity exceeds the capacity of informal processes to manage it. By the time the failure is visible, the brand has already absorbed the consequences: dealer relationship damage, margin leakage from uncontrolled pricing and an operations team that has been operating in crisis mode for months.
The right time to build infrastructure is before it is needed, not after it has visibly failed.
The Infrastructure Stack by GMV Stage
The infrastructure decisions that matter most depend on where the brand is in its growth trajectory. Not everything needs to be built at once. The sequencing matters as much as the components.
Below ₹1 crore GMV: foundations only
At this stage, the dealer network is small enough that informal processes are genuinely manageable. The infrastructure investment required is minimal but the foundations that will matter later should be put in place now, because retrofitting them later is significantly more disruptive than building them correctly from the start.
The foundation at this stage is clean dealer account records. Every dealer should be onboarded with a consistent account record: business name, contact details, geography, assigned pricing tier and credit limit. This seems basic. Most early-stage FMCG startups do not do it. When they try to migrate to a structured ordering platform at ₹5 crore GMV, the first project they face is reconciling three years of inconsistent dealer account data.
The second foundation is a defined pricing structure. Price lists by dealer tier, with scheme structures documented as formal policies rather than informal agreements. The pricing does not need to be enforced by a system at this stage. But it needs to exist as a documented structure that can be configured into a system when the time comes.
₹1 crore to ₹3 crore GMV: structured order capture
At this stage, order volume is high enough that manual processing is creating measurable overhead and the risk of ordering errors is increasing. The infrastructure priority is structured order capture: moving dealer ordering off WhatsApp and into a channel where orders are recorded automatically at the point of placement.
This does not require a fully featured dealer commerce platform at this stage. A structured web portal where dealers can place orders and see their account status is sufficient. The critical requirement is that orders are captured in a structured format at placement, not reconstructed from communication threads by a processing clerk.
The operational benefit at this stage is primarily time recovery for the operations team and a reduction in order entry errors. The longer-term benefit is that every order placed through the structured channel produces a clean data record that will feed reporting and eventually AI capabilities as the network grows.
₹3 crore to ₹7 crore GMV: pricing governance and credit control
At this stage, the dealer network is large enough that pricing inconsistencies are creating measurable margin leakage and credit exposure is a genuine financial risk. The infrastructure priority is pricing enforcement and credit limit management at order placement.
Pricing enforcement means that when a dealer places an order, the price applied is determined by the system based on their tier and the applicable scheme, not by a sales rep's judgement or memory. Exceptions are possible but they require an approval workflow that creates a record. Informal discounting at the rep level stops being possible because the system applies pricing, not the rep.
Credit control means that orders placed by dealers who have exceeded their credit limit are flagged or blocked at order submission, not discovered during the weekly finance review. The operations team stops managing credit exposure reactively and the finance team stops finding overexposed accounts in the monthly reconciliation.
₹7 crore to ₹10 crore GMV: delivery visibility and secondary sales reporting
At this stage, the dealer network is large enough that delivery disputes are a regular operational occurrence and the absence of secondary sales data is limiting the quality of distribution decisions. The infrastructure priority is closing the fulfillment loop and building the reporting layer.
Delivery visibility means that when an order is dispatched, the dealer can track it through the ordering platform and a delivery confirmation is captured at the point of delivery, not reconstructed from rider communication the following day. Disputes are resolved from the delivery record rather than from negotiation.
Secondary sales reporting means that the manufacturer can see what dealers are selling, at what velocity and in which markets, from the structured order data the platform captures. This visibility informs stock positioning, promotional deployment and distributor performance assessment in ways that are not possible when secondary sales data is absent.
The Cost of Getting the Sequencing Wrong
The sequencing matters because each layer of infrastructure depends on the one below it. Pricing governance cannot be enforced if dealer accounts are not clean and consistently structured. Secondary sales reporting is not meaningful if order capture is still informal and incomplete. Delivery tracking produces an audit trail that is only useful if the orders it is tracking against were placed through a structured channel.
Founders who try to skip stages, deploying a full dealer commerce platform with all capabilities at once when the dealer account data is still a mess and the pricing structure is still informal, typically face a failed deployment. The platform is configured on bad data and the dealer adoption is poor because the operational benefit to dealers is not clear enough to justify changing their ordering behaviour.
The brands that scale distribution infrastructure cleanly are the ones that build each layer on top of a working foundation rather than trying to implement the full stack before the foundations are solid.
What to Prioritise if You Are Already Past ₹5 Crore Without the Infrastructure
Many founders reading this are already past the GMV stage where certain infrastructure decisions should have been made and are now managing the consequences of that deferral. The operational wall has either already arrived or is visibly approaching.
The starting point in this situation is not to implement everything at once. It is to identify the most damaging current problem and fix that first. For most founders at this stage, the most damaging problem is pricing inconsistency and the margin leakage it is causing. Structured order capture with pricing enforcement is the first priority.
The dealer account cleanup that should have happened earlier needs to happen now, before the platform is configured. This is typically a two to four week project depending on network size and the state of existing records. It is not optional. A dealer commerce platform configured on inconsistent account data will reproduce the inconsistency at scale rather than resolving it.
Once order capture and pricing governance are working, the other layers: credit control, delivery visibility and secondary sales reporting can be added in sequence without disrupting the operations that are now running on the structured foundation.
Summary
The operational wall that FMCG startups hit before ₹10 crore GMV is a predictable consequence of infrastructure decisions deferred during earlier growth stages. The wall is not inevitable. It is the result of building distribution network scale on top of informal processes that were never designed to handle it.
The infrastructure that prevents the wall is not complex. Clean dealer account records, structured order capture, pricing enforcement and credit control at order placement, delivery visibility and secondary sales reporting. Each layer is straightforward. The discipline is in building them in the right sequence, before the network scale makes informal processes visibly inadequate rather than after.
Founders who invest in this infrastructure before they need it scale their distribution networks without operational crises. Founders who defer it until the crisis is visible spend the next six months rebuilding infrastructure under operational pressure, which is the most expensive way to build anything.
