Book Every Outlet on the Beat, Claim Every Scheme, and Collect Before the Credit Drifts

A beat is a fixed number of chances per day

An FMCG distributor does not have a long sales cycle to manage. There is a beat, a van, an executive, and a fixed number of shutters that will be open between the start of the round and the end of it. Everything the depot will earn that day is decided inside that window. If a shop is skipped, it is not deferred to next week in any meaningful sense — that week of sales goes to whichever competitor did open the shutter, and the shelf facing may not come back when you do.

Coverage is not the same thing as productivity

This is why the numbers that matter in FMCG are not the ones a general sales CRM reports. Visits made is close to useless on its own. What the depot needs is calls made against calls that actually billed, lines per call, and average drop size, broken down by beat and by day. A route where an executive walked into thirty-four shops and billed eleven is a very different problem from a route where he walked into fourteen and billed twelve, and both of them look like a full day in a visit log.

Once those three numbers are counted automatically as orders are booked, the conversation in the evening changes shape. Instead of asking where somebody was, a supervisor can ask why a particular beat has a drop size half of the beat next to it, and the answer is usually something fixable — a pack mix nobody is pushing, a scheme nobody quoted, or a set of outlets that stopped being called and nobody noticed because the total looked fine.

Memory is doing too much work at the counter

The classic FMCG order is booked in a memo pad while the retailer is half attending to a customer, and typed into a system hours later by someone who has since done thirty more calls. Lines go missing. A pack size becomes a guess. A scheme quantity is remembered as ten when the slab needed twelve. None of this is carelessness; it is the predictable outcome of asking a person to hold thirty shops of detail in their head until the evening.

What the salesman should be able to see while standing there

Booking at the counter fixes the problem by removing the gap. When the executive opens the outlet on the phone, the last three orders, the packs this shop actually takes, the schemes live on those packs today, and the balance outstanding are all on one screen. The order is built against the outlet record with the scheme attached, so the arithmetic that decides the claim later is captured at the moment it is agreed, in front of the person who agreed to it.

The other thing that view solves is the upsell nobody has time to think about. A shop that has bought the same six lines for four months is usually not refusing the seventh — it has simply never been offered on a day when anyone remembered. Pack mix sitting on the screen turns that into a prompt rather than an initiative.

Schemes in this trade move faster than any monthly plan

FMCG schemes are announced at SKU level, often mid-month, sometimes on a single pack size, and frequently in response to what a competitor did the week before. The slab is specific — a qualifying quantity, a free-goods or discount treatment, a hard last date. That specificity is exactly what does not survive being passed along verbally. By the time it has gone through a supervisor, a group chat and a tea break, three executives are quoting three slightly different offers, and every one of those differences becomes a claim dispute at month end.

One card, published the day the scheme opens

Holding the scheme as a record against the SKU changes what the field is working from. Each executive opening an outlet sees the schemes live on the packs that shop buys, with the qualifying quantity and the last date written down. Orders are booked with the scheme attached rather than annotated afterwards, which is what makes the claim working assemble itself as the month runs.

That last point is worth being blunt about, because it is where distributors lose real money quietly. A scheme claim submitted short is not usually a claim that was refused — it is a claim where the paperwork could not prove which outlets bought what under which offer, so the safe number went in instead of the true one. Booking the scheme with the order removes the reconstruction step entirely.

Shelf life makes this different from every other distribution vertical

A machinery dealer can leave stock in a godown for a year. An FMCG distributor cannot, and neither can the retailer. Stock aging on a shelf in a shop is still, commercially, your problem: it comes back as a return, or it comes back as a retailer who is annoyed enough to buy from someone else next week. The window in which it can still be sold through, redistributed or picked up is short and it closes silently.

What belongs here, and what stays in the DMS

To be explicit about the boundary: batch numbers, stock ledgers, the credit note itself and statutory invoicing belong in your DMS or ERP and stay there. What sits here is the chase around them. An executive flags aging or damaged stock at the counter with a photo and a quantity against that outlet. It becomes a pickup task on the route, then a claim with a status and an owner, then a settled item when the credit note lands. The point is not to duplicate the stock record. The point is that the claim stops being an argument settled by whoever remembers it most confidently.

Thin margins make working capital the real constraint

Distribution margins in this trade are slim enough that the business is really a working-capital business wearing a sales business hat. Money sitting in retailer credit is money not buying the next primary load, and the drift that causes it is almost never announced. A shop that agreed to seven days pays in nine, then in twelve, then in nineteen, and each individual slip is small enough that nobody escalates it. The cumulative effect across a beat is a depot that is short of cash on the day the principal wants payment.

Making drift visible while it is still small

Holding the agreed credit period on the outlet alongside what that outlet actually does turns an accumulating problem into a list. The shops that have moved are named, and by how much. Follow-up runs as scheduled tasks and WhatsApp reminders from the business number, which also takes the awkwardness out of it — a reminder that arrives on schedule from the depot is a process, whereas the same reminder delivered in person by the executive who wants an order tomorrow is a negotiation he will usually lose.

Collection and ordering also stop competing for the same conversation. The executive books the order at the counter; the reminder about the outstanding goes out on its own schedule with the ledger position attached. Both jobs get done, and neither is traded away for the other.

You are the secondary layer, and the vantage point matters

A distributor sits between a principal and a few hundred shops. Primary is what you buy; secondary is the round your own salesmen run every day, and it is the part nobody else can see for you. If you are looking at the same problem from the brand side — running a dealer or distributor network across regions, setting tier-wise price lists, sanctioning credit limits and designing the scheme slabs in the first place — start at the dealer CRM hub, which is written for that seat rather than this one.

Alongside the DMS, and alongside the wider distributor toolkit

Nothing here asks you to move the systems that already work. Your DMS keeps the stock and the invoices, your accountant keeps the books, and this layer keeps the orders, the calls, the schemes, the claims and the collections. It is available on a published price of ₹899/user/month + GST per executive, with no seat minimum, so a depot can put one beat on it and judge it on that beat before extending it to the rest of the team.