The round itself is the one part of a milk business that cannot be automated away. Somebody has to carry the milk to the door. What can be improved is everything around it: the order of the stops, who covers which street, what happens when a customer is away, and what happens when something goes wrong at the door.
This guide covers route sequencing, running a round with more than one person, handling complaints, and dealing with cancellations and pauses — the four operational problems that decide whether a round stays profitable as it grows.
Sequencing a round
Most rounds were not designed. They accreted: a customer joined, then their neighbour, then someone two streets over, and the order is now the order in which people signed up. Re-sequencing an existing round is usually the single largest time saving available to a milk business, and it costs nothing.
Map what you actually do
For one week, write down the order you visit and roughly the time at each stop. Do not plan from memory — the round you think you run and the round you run are rarely the same.
Work in loops, not out-and-backs
A route that ends where it started wastes no return distance. The most common avoidable cost in a small round is a single distant customer that turns a tight loop into a spur — and that customer is often also one of the smallest accounts.
Put the time-sensitive stops first
Customers who need milk before they leave for work, shops that open at a fixed hour, anyone who has complained about timing. Everything flexible goes later in the loop, where a delay costs nothing.
Group by building, not by street
Five flats in one block are one stop, not five. Sequencing by building rather than by address order can remove a surprising amount of walking.
Count the marginal customer honestly
Before adding a customer who is off-route, work out what they add in minutes and fuel against what they add in revenue. Some accounts genuinely lose money, and the only way to know is to look at revenue per customer alongside where they sit on the route.
Running a round with more than one person
The moment a second person delivers — a family member, a hired helper, someone covering while you are ill — three things break at once: who recorded what, who collected what, and who the customer holds responsible.
Split by area, never by customer
Two people covering overlapping areas on alternate days produces double deliveries and missed ones. Give each person a contiguous block and keep it stable, so they learn their customers.
One record, not two
The most common failure is two people keeping separate notes that get combined at month end. Whether you use a book or an app, there must be exactly one record of deliveries, updated as they happen.
Decide the cash rule before you need it
Money collected at the door by someone other than the owner needs a rule from day one: what gets collected, what gets recorded immediately, and when it is handed over. “We will sort it out later” is how good working relationships end.
Write the handover down
If you are away, the person covering needs the round order, quantities, any customer-specific instructions (“gate is locked, leave at side door”), and who to call. A five-minute written list prevents most of the problems that come from a covered round.
Handling complaints at the door
Complaints in a milk round are nearly always one of four things, and each has a standard answer that works better than improvising.
“The milk was sour”
Replace it, that day, without an argument. The cost of a litre is trivial against the cost of the account, and the replacement is remembered far longer than the fault. Then check whether it is a pattern — same customer, same day, same part of the route — because a recurring sour complaint is usually a storage or timing problem on your side.
“It was late”
Late is only a problem when it is unpredictable. A customer who knows milk arrives at 6:30 plans around it; a customer who gets it at 5:45 one day and 7:15 the next cannot. If timing complaints are increasing, the answer is usually route sequencing rather than leaving earlier.
“The quantity was short”
This is the one that damages trust most, because it implies dishonesty rather than inconvenience. Check the entry, show the record, and if there is any doubt, credit it. A dated delivery log turns this into a thirty-second conversation instead of a standoff.
“The bill is wrong”
Go through it line by line with them rather than defending the total. In most cases the customer has forgotten a week, and seeing the dates resolves it. In the minority of cases where you are wrong, correcting it immediately and visibly is worth more than the amount.
Two rules that hold across all of these: respond the same day, and record the outcome. A complaint that is resolved and noted stops being a risk; one that is resolved verbally and forgotten comes back at billing time.
Cancellations, pauses and win-backs
Distinguish a pause from a cancellation
Most people who stop milk for two weeks are travelling, not leaving. Treat them as paused: keep the account, keep the rate, and confirm the restart date. Losing a customer to a holiday because nobody followed up is the easiest possible loss to avoid.
Ask why, once
One question, without pressure: “Is there something we could have done better?” Roughly half the answers are price or a competitor and you cannot do much. The other half are timing, quantity flexibility or an unresolved complaint — all of which are fixable, and all of which are probably affecting other customers who have not said anything.
Watch the quiet decline
Customers rarely cancel abruptly. They reduce from two litres to one, then to alternate days, then they stop. A falling quantity over two or three months is a cancellation in progress, and it is far easier to address then than after. This is the practical reason to keep records at the entry level rather than as monthly totals — the trend is invisible in a single month’s number.
Make restarting easy
An account that closes cleanly, with the balance settled and no bad feeling, is a customer who may come back. One that ends in a dispute over an unpaid final month never will. Send the final bill promptly and politely, whatever you feel about the departure.
Where to go next
For the records that make all of this visible, read keeping a customer ledger that holds up and the complete guide to milk delivery apps. For demand patterns across the year, see seasonal milk demand planning. For billing, how automated dairy billing works.
Milk Diary keeps a dated, per-customer delivery log with morning and evening shifts, which is what makes quantity disputes, quiet declines and pause handling straightforward rather than guesswork. It is free on Google Play and works offline.