Sales teams track dispatches closely. We think the orders that did not go, and the reasons why, tell a brand far more about its network.
Ask a sales head how distribution went yesterday and the answer is usually about dispatches: how many outlets were served, what value was invoiced. Those numbers matter. But they describe the part of the day that worked. The part that did not work, the orders still sitting on a distributor’s pending list, is where the useful information is.
Take a brand that sells packaged bakery products: bread, rusk, cakes and cream rolls, through distributors to local stores. A sales rep books an order at a store on Monday. By Wednesday it has not been delivered. Nobody has said why.
From head office, that order is just “pending”. But pending can mean very different things:
| The real reason | Who should act | What happens if nobody knows |
|---|---|---|
| The distributor is out of that SKU | Head office and the plant | The store buys a rival product; the brand never sees the lost sale |
| The van does not cover that beat until Thursday | The area sales executive | The rep keeps promising a delivery that cannot come |
| The store has unpaid dues and the distributor is holding supply | Sales and the distributor together | A credit problem is mistaken for a delivery problem |
| The order was wrong, a duplicate or the wrong SKU | The sales rep | The store waits for something it never wanted |
Each reason has a different owner and a different fix. Without the reason, all of them land in the same place: the area sales executive’s phone, the next morning, asking every distributor the same question.
Reasons go unrecorded not because distributors hide them, but because recording them is extra work for no visible benefit. Typing a reason into an app nobody reads feels pointless. Explaining it on a phone call works, but the explanation dies with the call. And short shelf life makes this sharper in bakery: a cream roll order that waits three days may not be worth sending at all.
So the fix is not a stricter rule. It is making the reason cheap to give and useful once given.
We built our Distributor Management System around this idea. The distributor works from WhatsApp, in Hindi or English. Asking “Pending kya hai?” lists the outlets waiting, oldest first. If an outlet cannot go today, the distributor gives the reason in the same chat. That reason is posted to the distributor’s WhatsApp group, where the area sales executive and the sales team see it straight away. If an order is wrong, it is cancelled and the rep who booked it gets a WhatsApp message.
Two habits close the loop. Every morning, each distributor gets their own pending list. At 10 pm, the group names outlets still waiting too long and distributors whose stock was not updated that day, and tags the area sales executive. Nobody has to call to find out what is stuck.
Once reasons are written down, they can be read as a pattern rather than a stream of excuses. We would review them weekly:
The playbook on cutting follow-up calls covers how area sales executives can change their mornings once this is in place.
A distribution network that reports only successes looks healthy until a store stops ordering. A network that reports its gaps, with reasons, can be fixed while there is still time. If you want one change this quarter, make the pending reason as easy to send as the dispatch. More on secondary sales in the DMS guides.
Because “pending” can mean a stock-out, a route gap, a credit hold or a wrong order. Each has a different owner, and without the reason every case ends in a follow-up call.
In the same WhatsApp chat used for dispatch. The reason is posted to the distributor’s group so the area sales executive and team see it without calling.
At 10 pm, the distributor’s WhatsApp group names outlets still waiting and stock not updated that day, with the area sales executive tagged.
See it on your own data. Distributor Management System — Dispatch from WhatsApp. Book a 30-minute working session with an engineer.
