FMCG Beat Planning with AI: How Smart Route Optimization Is Cutting Costs by 30%

By Sufyan · 2026-06-11 · 5 min read

A sales supervisor in Lahore once told me his reps drove past 14 shops every morning to reach the first one on their beat list. Fourteen. Just because the route was drawn up in 2017 by someone who's no longer at the company, and nobody wanted to touch it.

That's the FMCG distribution problem in one sentence.

Beat plans get treated like sacred documents. They shouldn't be. They're working hypotheses about which outlets a rep should visit, in what order, on which day — and most of them are wrong by the time the ink dries. Outlets close. New ones open. A road gets dug up for six months. A wholesaler poaches three retailers. The plan keeps going as if nothing changed.

And then somebody wonders why the cost-to-serve keeps climbing.

What 30% actually means

When distributors I talk to say AI route optimization cut their costs by 30%, they're rarely talking about one big number. It's a stack of smaller wins that add up.

Fuel: down 18-22% on average, because reps stop zigzagging across the same neighborhood twice in a week. Productive call time: up roughly 27% in the pilots I've seen, because reps spend less of the day in traffic and more in front of shopkeepers. Outlet coverage: typically a 12-15% jump in the same headcount, because the algorithm finds shops the manual plan was skipping. Strike rate per visit goes up too, since reps actually arrive when the owner is in the shop — not during the 2pm nap window every retailer in South Asia respects.

Stack those together and you get something close to a third of the operating cost gone. Honestly, the first time I saw the math laid out properly, I assumed someone had cooked the numbers. Then I looked at the GPS traces. The old beats were that inefficient.

The core insight isn't fancy. Reps were optimizing for memory and habit, not geography. AI just doesn't have either.

Where the smart systems are actually winning

Good field sales route planning software doesn't hand you one perfect map and call it done. It does three things on a rolling basis:

It clusters outlets by real travel time, not straight-line distance. A shop that's 400 meters away as the crow flies but on the wrong side of a divided road is treated as further than one 1.2 km down a clear street. Sounds obvious. Almost nobody used to model it that way.

It re-sequences daily routes based on what happened yesterday. If a rep got blocked out of four shops in a row because the owners weren't there, the system shifts those visits to a different time window — or a different day — automatically. The beat isn't a weekly grid anymore. It's a living thing.

It scores outlets by economic contribution, not just frequency. A high-frequency, low-value shop quietly gets visited less. A growing outlet gets a tighter visit cadence. The supervisor doesn't have to fight this battle with the rep every quarter. The plan just reflects it.

Platforms like Zivni have built their FMCG beat planning around exactly this — feeding rep GPS data, outlet productivity, and order patterns back into a planning loop that reshuffles routes weekly rather than annually. The teams using it stop arguing about whose beat is harder and start arguing about whose conversion is lower, which is a much more useful conversation.

I used to think the hardest part of all this was the algorithm. I was wrong. The hardest part is convincing a 12-year veteran rep that the new beat order isn't an insult to his judgment. It's a tool. He still owns the relationship. The software just handles the part of the job nobody enjoyed anyway — figuring out which left turn saves four minutes.

The parts nobody puts in the case study

Here's the thing about AI route optimization sales pitches: they skip the messy bits.

Data quality kills more pilots than bad algorithms do. If your outlet master has three entries for the same kiryana store (one with a typo, one with the old owner's name, one geo-tagged on the wrong street), the system optimizes for fiction. The first six weeks of any real rollout is just cleaning. Nobody puts that in the brochure.

Then there's the political problem. Beat boundaries are often drawn around informal arrangements — this rep's brother-in-law owns a shop on that route, this supervisor's territory was promised to him in 2019. An algorithm doesn't know any of that. It'll happily redraw boundaries that took years of internal negotiation to settle, and the rollout stalls in week three when two managers stop talking to each other.

And connectivity. A lot of the markets where this matters most — interior Sindh, rural Kenya, tier-3 Indonesia — have patchy data. The software has to work offline-first, sync when it can, and never lose a single order in the gap. The companies that get this part right win. The ones that demo beautifully on stage at conferences and then crumble in a village with one bar of signal do not.

There's also a real question about how much optimization is too much. If you squeeze every minute out of a rep's day, you've also removed the slack that lets him actually sell — to listen to a shopkeeper complain about a competitor, to notice that a new brand showed up on the shelf, to build the kind of trust that gets you preferential display next month. A beat plan that's 100% efficient on paper is often worse than one that's 85% efficient and leaves room to be human.

The distributors getting the full 30% cost reduction aren't the ones running their reps the hardest. They're the ones who freed up the time the old plan was wasting, and let the reps spend half of it selling and half of it going home earlier. Turnover drops. Recruitment costs drop. Suddenly that 30% looks conservative.

Which raises a question I don't have a clean answer to yet — if the software keeps getting better, what's the actual job of a beat planner in five years?

The Alif Zero Network
Alif Zero is one of several businesses operated by Sufyan. The FMCG distribution technology in this piece is being built at Zivni — an AI-powered field sales platform for distributors.