The morning the milk does not arrive
It is seven in the morning. The dairy supplier has not confirmed today’s delivery. Your store manager sent the quantity on a WhatsApp group last night, between forty other messages. Someone replied with a thumbs-up, and nobody is sure whether that meant “seen” or “it is on the truck”.
By ten, your biggest outlet is out of milk and the second-biggest is rationing it. You spend the next hour on the phone, scrolling back through the group to find out who said what.
What it costs
Suppose a food distributor supplies twelve outlets, and each outlet sells ₹30,000 a day of dairy and chilled items that depend on one early delivery. If one late delivery takes out three outlets for half a day, the lost sales are roughly three outlets times ₹15,000, so ₹45,000 in a morning. If that happens twice a month, it is about ₹11 lakh a year, before counting customers who simply buy elsewhere next time.
The larger cost is the hours. If a manager and an assistant each spend ninety minutes a day chasing confirmations, that is close to six hundred hours a year spent following up rather than planning.
Why it happens
WhatsApp is excellent for a quick question. It is a poor place to keep a commitment, because a message is not an order. There is no agreed format, no quantity field, no delivery date, no status. Whether a message was seen is not the same as whether it was accepted.
The problem grows with every supplier and every outlet you add. Five suppliers are manageable by memory. Twenty are not, and the person who remembers everything becomes the single point of failure. When that person is on leave, the process leaves with them.
There is also no record to learn from. Which supplier delivers on time? Which one changes prices after confirming? You may hold strong opinions, but you cannot show a supplier a count of late deliveries when negotiating, because nobody has counted.
What changes it
The first change is organisational. Decide who is allowed to raise an order, who at the supplier confirms it, and by what time. Write down the reorder level for each fast-moving item, so an order follows a rule and not a mood.
The second is a single record of each order: item, quantity, requested date, confirmed date, received date. It can begin as one shared sheet with agreed columns. A confirmation that does not arrive within a fixed window, say two hours, goes to a named person.
The third is a monthly scorecard per supplier: orders confirmed on time, deliveries on the promised day, short supplies, price changes. This is the evidence for your next negotiation, and the quickest way to learn which supplier you can depend on.
Once the rule and the record are stable, your software can raise the order automatically when stock falls below the reorder level, and send the supplier the same message every time. WhatsApp can still carry the message. It just stops being the place where the order lives.
What this does not fix
A clean process does not make a supplier reliable. If one dairy is simply unable to deliver by seven, the scorecard will tell you so, but you still need a second source. Reorder levels also need reviewing: a level set for a normal week will fail in a festival week. And small suppliers who work only by phone will not change overnight, so expect to keep some manual routes for a while.
If supplier coordination is where your growth has started to strain, scale describes how this kind of operating discipline is put in place.