Route Planning Software for FMCG Sales Teams: How to Actually Optimize Daily Beats

A rep in Karachi once told me he spent 2 hours and 40 minutes a day just driving between shops. Not selling. Not talking to shopkeepers. Just sitting on his bike, dodging traffic on Shahrah-e-Faisal, going from one outlet to the next in an order someone drew on paper in 2019.

That conversation is basically why we built the route planning module inside Zivni.

Here's the thing about FMCG field sales — the math is brutal. If your reps are wasting 30% of their day on travel, you're either hiring more reps to hit the same coverage, or you're accepting lower productivity per head. Neither is fun. And both show up in your secondary sales numbers eventually.

So let's talk about what actually works when you're trying to fix this.

What a daily beat should actually look like

A beat (or PJP — permanent journey plan, if you're old school) is just the sequence of outlets a rep visits on a given day. Sounds simple. It is not.

A good beat balances four things at once: geographic clustering so the rep isn't zigzagging, outlet priority so A-class shops get visited first when energy is high, visit frequency rules (some shops weekly, some biweekly), and time windows because the kiryana store next to the mosque shuts for 45 minutes at 1pm and your rep needs to know that.

Most distributors I meet in Pakistan and the UAE are doing this in Excel. Or worse — in the head of a senior sales officer who's been there 12 years and "just knows" the area. Which works fine until he quits. Then you're rebuilding from scratch.

Good FMCG route planning software does three jobs:

• Clusters outlets by location so travel time drops
• Respects business rules (frequency, priority, working hours)
• Adapts when reality changes — a new outlet opens, an old one shuts, traffic shifts

That third part is where most tools fall over. Static routes are easy. Routes that actually update when your market changes? Harder.

The mistakes I made building this

I got this wrong at first. Honestly.

When we started Zivni, I assumed the answer was pure optimization — feed the algorithm every outlet, every constraint, let it spit out the mathematically perfect route. Classic engineer brain.

Then we ran a pilot with a beverage distributor in Lahore. The system gave reps a "perfect" route. Reps ignored it. Why? Because the algorithm didn't know that Bashir at outlet #47 only places orders after he's had his second chai, around 11am. It didn't know that the wholesale market gets jammed on Fridays. It didn't know which shopkeeper owes money and needs to be visited with the area manager, not the junior rep.

So we rebuilt it. Now the planner suggests, but the supervisor can override. The system learns from overrides. If a rep consistently visits outlet X before outlet Y even though the algorithm says otherwise, the system asks why and adjusts the rule.

That hybrid — algorithm plus human judgment — is what actually moves the needle. Pure AI route planning sounds sexy in a pitch deck. In the field it gets you mutiny.

A few specific things we've seen work across our customers:

Cluster by density, not distance. A rep covering 35 shops in a 2km radius will outperform one covering 28 shops spread over 8km. Obvious, right? But most beat plans I audit don't reflect this.

Front-load A-class outlets. Top 20% of outlets usually drive 60-70% of revenue. Visit them between 9:30 and 12:30 when both rep and shopkeeper have energy. Don't save your best account for 4pm when everyone's tired.

Build in slack time. A beat with zero buffer breaks the moment one shopkeeper wants to chat for 15 minutes. We recommend planning for ~80% of the rep's working hours, leaving 20% for the chaos that always happens.

Track plan vs actual. This is where GPS matters. Not to spy — to learn. If reps consistently skip the same three outlets, those outlets either need to move beats or get dropped. The data tells you.

How sales route optimization actually shows up in numbers

One of our customers in Sharjah — mid-size FMCG distributor, around 40 reps — was averaging 22 productive calls per rep per day before they switched to Zivni. After three months of running optimized beats with weekly tuning, they hit 31. That's a 41% jump in coverage with the same headcount.

The travel time per visit dropped from 14 minutes to about 9. Strike rate (orders per visit) actually went up too, which surprised me at first but makes sense — reps arriving less rushed sell better.

Not every customer sees those numbers. Some get 15% gains. Some get 50%. Depends mostly on how messy the starting point was. If your beats were already tight, you'll get less. If they were drawn on a napkin in 2018, you'll get a lot.

A quick reality check though — software won't fix a bad sales culture. If your reps are faking visits, no route planner saves you. You need GPS verification, photo capture at outlet, and a supervisor who actually reviews the data weekly. The tech is maybe 40% of the answer. Process and people are the other 60.

Where to start if you're doing this on paper today

Don't try to optimize everything in week one. Pick one city, one set of beats, maybe 8-10 reps. Map every outlet with GPS coordinates (this alone takes 2-3 weeks if you've never done it). Then run optimized beats for a month and compare to your old plan. Productive calls per day, distance traveled, strike rate, secondary sales — those are the four numbers I'd watch.

If the pilot works, roll out city by city. Don't big-bang it. I've seen too many distributors try to flip 200 reps overnight and end up with chaos for six weeks.

And if your senior sales officer who "just knows" the area pushes back? Make him the pilot champion. His knowledge is genuinely valuable — the goal is to capture it in the system, not replace him with it.

What's the average productive calls per day across your team right now? If you don't know, that's probably the first problem to fix.