How to take over a van sales route without losing the customers

A beverage distributor running nine vans out of a single depot had one route that quietly outperformed the other eight for years — same 52 stores, same rep, since before anyone else on staff had joined the company. Then he gave two weeks' notice to go work for a competitor's distributor across town. The owner wasn't worried at first. The stores were still there, the stock was still there, the price list was still there. What he didn't have was a record of anything else: which owner liked a Tuesday morning drop before the lunch rush, which corner store got a standing five-case discount because they'd been loyal since year one, which two accounts were one late delivery away from switching anyway, and who to call first when the news got out.

The route was never really in the system

None of that had ever been written down, because it never had to be. The rep carried it the same way a good route rep always does — in his head, refreshed every visit, adjusted every week. The system had the transaction history: what each store bought and when. It didn't have the reasons, the relationships, or the risk. So when the new rep started, he had a stop list and a price sheet, and nothing that told him a particular owner needed to be reminded, gently, that a payment was three days late instead of being told flatly that his credit was on hold.

Six stores stopped ordering within the first month. Two more cut their order size in half. None of them called to complain first — they just quietly gave more of their shelf space to the rep who used to make Tuesday deliveries and was now doing the same route for someone else. By the time the pattern showed up in the monthly revenue-by-route report, it read as one bad month. It took a second bad month, and a delivery driver mentioning he'd seen the old rep's new company's van parked outside two of "our" stores, before anyone connected the dots.

Why the loss looks like something else

This is the part that makes it hard to catch in time: a departing rep rarely takes an account by asking for it. The account just stops feeling like anyone is paying attention, and a competitor's rep is usually already circling, because route reps talk to each other and everyone in the trade knows when someone's given notice. The store owner isn't being disloyal — they're reacting to the fact that the thing they were actually loyal to, a person who knew their business, left. If the new rep shows up cold, reading a printed stop list like a stranger, that reaction is instant and it looks, from the office, exactly like a slow month rather than an emergency.

The other reason it's missed is that the handover usually happens under time pressure that discourages doing it well. Two weeks' notice isn't much time to ride along, take notes, and brief a replacement — so most distributors either rush a half-day handover or skip it and hope the price list and order history are enough. They aren't. Order history tells you what a store bought. It doesn't tell you why they might stop.

The turning point: making the account belong to the company, not the rep

The fix the distributor landed on didn't try to make the departing rep hand over more — by the time someone's leaving, that conversation is often adversarial, and information volunteered under those conditions is unreliable anyway. Instead, they changed what got captured in the first place, starting with the next hire. Every visit already had a check-in, an order, and a check-out logged automatically by the field app; they added the habit of a short note against the stop whenever something mattered — a payment promise, a complaint, a preferred delivery window, a competitor sighting. None of it took more than a few seconds, because it was typed once, at the stop, not reconstructed later from memory.

When the next rep left eight months on, the transition looked completely different. The manager pulled every note logged against that route's 52 stops, sorted by store, and had a real briefing document in twenty minutes instead of a blank page. The new rep's first visits weren't cold calls — they opened with "I saw you had a late delivery last month, that shouldn't happen again" instead of a stranger's stop-and-scan. The owner also called the top accounts personally in the first week, which cost an afternoon and signaled, more than any process change, that the company — not the rep — was the one showing up for them.

Practical takeaway: protecting a route through a rep change

• Capture relationship context at the stop, continuously, not just transaction data — a one-line note on a payment issue, a preference, or a competitor sighting is worth more during a handover than a quarter of order history.
• Treat resignation notice as a briefing deadline, not two weeks of business as usual — pull every note and visit pattern for the route on day one, don't wait for the exit interview.
• Call the top accounts yourself before the new rep's first visit. A personal call from ownership is the single strongest signal that the relationship is with the company.
• Brief the new rep on the story behind each account, not just the stop order and price list — who's price-sensitive, who's slow to pay, who's actually at risk.
• Watch order size and frequency by store for the first six weeks, not just route revenue — a handful of quietly shrinking accounts hides inside a route total that still looks normal.
• Assume a competitor already knows the rep is leaving. Route reps talk. The window to reassure an account is days, not weeks.

iotoms logs every visit from the same field app a rep uses to sell, so a store's history — orders, notes, payment promises, anything a rep flagged in the moment — is already in the console under that account before a handover has to happen, not reconstructed from a departing rep's memory after the fact.