Van Sales Software: Why Route Accounting Is Still Underserved in 2026

By Sufyan · 2026-05-08 · 4 min read

Last month I sat in a distributor's office in Lahore watching a guy reconcile 14 van loadings on paper. Paper. In 2026.

He had three notebooks open, a calculator, and a face that said he'd been doing this for 22 years and didn't trust the laptop next to him. His son — the one who'd convinced his dad to buy a tablet-based van sales app two years ago — was sitting across the room looking embarrassed.

I asked why the app wasn't being used for the reconciliation.

"It tracks the orders. It doesn't track this."

This being: damaged stock returns, unsold SKUs going back to the warehouse, free schemes given out, cash collected vs cash deposited, credit notes issued on the route, and the small differences that pile up across 30 vans every single day. Route accounting. The unsexy spine of FMCG distribution that almost every van sales software pretends to handle and very few actually do.

The gap nobody fixed

Here's the thing. The van sales software category exploded between 2018 and 2023. Everyone shipped an app. Order capture, GPS, beat plans, a dashboard. Beautiful screenshots. Investor decks talking about "AI for FMCG."

But if you sit with a distributor's accountant — not the sales manager, the accountant — and ask them what they need, you'll hear the same list I've heard in Karachi, Sharjah, Lagos, and Nairobi:

Match van loading to van returns, SKU by SKU, batch by batch
Reconcile cash collected against invoices in real time
Track expired and damaged returns separately from saleable returns
Handle replacement schemes without breaking the GST/VAT trail
Print a route settlement sheet the salesman actually signs at end of day

Most van sales apps stop at order capture and a payment receipt screen. The accounting layer underneath — the reason route accounting software exists as a category — got skipped because it's hard, regional, and unglamorous.

I got this wrong at first too. When we started building Zivni, I thought the prize was in the field — better order entry, faster sync, voice input, shelf photos. All the things that look great in a demo. We shipped that. Customers liked it. And then within 90 days every single one of them asked the same question: can your software close my van at end of day without my accountant redoing it in Excel?

That question is the entire ballgame.

Why it stayed underserved

A few reasons, honestly.

First, the big global players — Salesforce Field Service, SAP DSD modules — were built for markets where vans don't actually sell off the truck. In the US or most of Europe, the truck delivers pre-booked orders. In Pakistan, UAE, Egypt, Indonesia, Kenya? The salesman is also the cashier, the credit officer, the merchandiser, and sometimes the guy who decides which shop gets the last carton of the promo SKU. The accounting complexity sits in the van, not the back office.

Second, regional players like FieldAssist and BeatRoute focused — rightly — on retail execution and SFA. Route accounting was treated as an integration problem. "We'll push the data to your ERP and let SAP handle it." Except 70% of distributors in emerging markets aren't on SAP. They're on Tally, QuickBooks, a custom FoxPro thing from 2009, or nothing.

Third, the math is genuinely annoying. A single van doing 40 outlets a day with 60 SKUs, mixed cash and credit, multiple promo schemes, returns at three different value points (saleable / near-expiry / damaged), and a driver who pockets ₨ 200 for tea — try modeling that cleanly. I've seen engineering teams quit over less.

What good route accounting actually looks like

I'll keep this practical because that's what the post deserves.

A proper van sales software with real route accounting should close the van in under 10 minutes at end of day. Not 10 minutes of the salesman tapping screens — 10 minutes including the supervisor's review. If your current tool takes 45 minutes and ends with someone opening Excel, it's not route accounting software. It's an order app with a receipt printer.

It should also handle the three flows that break most systems:

Loading variance. What was issued from the warehouse vs what the salesman acknowledges receiving. Sounds simple. It is not. Batch numbers, expiry dates, free goods, and trade returns from yesterday all collide here.
In-route adjustments. A shopkeeper rejects 2 cartons because the case is dented. Replacement issued from van stock. Credit note generated. The accounting entry needs to happen now, not at midnight when sync runs.
Settlement. Cash + cheques + digital payments + credit sales + returns + expenses, all rolled into one signed sheet. Printed. Two copies. Because the supervisor still wants paper and that's fine.

If your software can do those three cleanly, the rest — GPS, beat planning, shelf photos — is gravy. If it can't, you're going to keep losing 1-3% of revenue to leakage that nobody can quite explain at the monthly review.

A small confession

Look, I'm biased. We build Zivni and route accounting is a chunk of what we obsess over. But the reason I'm writing this isn't to pitch — it's because every time I talk to a distributor in this region, the conversation drifts to the same place. The field part is mostly solved. The accounting-on-wheels part isn't.

There's a 47-year-old finance manager in a Karachi distribution house who told me last quarter that he'd switch software tomorrow if someone could give him a clean route settlement report his auditor would accept without questions. Just that. One report.

That's the bar in 2026. Not AI. Not fancy dashboards. A report a tired accountant can sign off on at 9 PM and go home.

Which makes me wonder — if it's that specific, why is the category still this empty?