Real-time van inventory tracking: why end-of-day reconciliation isn't enough

A snacks and confectionery distributor running eleven vans out of a single depot had end-of-day reconciliation down to a routine. Every van came back by 6pm, the supervisor matched loaded stock against sales, returns and cash, and the numbers closed within a rupee or two most nights. On paper, the operation looked tight.

The problem showed up at 11am, not at 6pm.

A rep on route 4 sold out of the fast-moving 200g pack by mid-morning. He didn't know it — the load sheet from that morning said he'd started with 60 units, and he'd lost count of exactly how many he'd sold across fourteen stops, three of them with mixed-case orders and one return. He kept quoting the item to outlets, kept taking orders for it, and kept getting turned away or forced into an awkward "I'll deliver it tomorrow" at the counter. By the time the van returned and the day closed, the office could see exactly what had happened — down to the unit — but only after it no longer helped anyone. The sale was already lost, and the outlet had already noticed.

Multiply that across eleven vans and a few fast movers each, five days a week, and it stops being an edge case. It's a steady leak of orders the business is capable of fulfilling, just not from the van that happened to be standing in front of the customer.

Why the end-of-day number arrives too late

End-of-day reconciliation answers a real question: did the stock, the sales and the cash all agree by the time the van came back. That's the finance question. It's necessary, and it catches shrinkage, pricing errors and missed entries after the fact.

It doesn't answer the operational question a rep or a supervisor needs answered during the route: what does this van actually have on it, right now, at stop nine.

Without that, distributors fall back on the load sheet — what left the depot that morning — and mental math. Both degrade the same way over the course of a day:

• Split cases and mixed units. A rep loads 4 cases of one SKU and sells individual pieces at some stops, full cases at others. Tracking the remaining count by hand means subtracting differently at every stop.
• Returns and swaps. A damaged or wrong item comes back mid-route and gets added back to stock, or exchanged for another SKU. That's another manual adjustment nobody has time to do accurately at stop eleven.
• Multiple reps on the same van, different shifts. Handover between a morning and evening rep resets whatever mental tally existed.
• No visibility from the office. A supervisor fielding a call from an outlet ("does van 4 have the case-pack litchi drink?") has no way to answer without phoning the rep and waiting for him to count.

None of this is about carelessness. It's the natural failure mode of tracking a number that changes at every stop using a method — memory, a paper load sheet, a phone call — that only updates once a day.

What changes when the count moves with the sale

The fix isn't a better end-of-day process. It's making the same number the reconciliation checks at 6pm also correct at 11am, by updating it at the moment of the actual transaction instead of the moment someone gets around to reconciling it.

In practice that means every sale, return, and damage entry the rep records on the field app adjusts the van's on-hand count immediately, unit by unit, whatever mix of cases and pieces the transaction used. A supervisor or the rep himself can then check what's actually left on the van at any point in the day — not what was loaded that morning, not a guess, the current count.

That changes three things on the ground:

• The rep stops overselling. He sees zero on the litchi drink before he offers it at the next stop, and either skips it or flags a transfer instead of promising something he can't deliver.
• The office can move stock mid-route. If van 4 is out of a fast mover and van 7 has surplus, a supervisor who can see both counts in real time can redirect a case between routes before the day ends, not after.
• Load planning improves the next morning. A pattern of vans running out of the same SKU by midday is a loading problem, and it only shows up if someone can see when — not just whether — a van hit zero.

None of this replaces end-of-day reconciliation. It changes what reconciliation is checking: instead of catching a full day's drift after the fact, it's confirming that a number that was already accurate all day stayed accurate through the final return and cash count.

The offline problem underneath it

The reason so many distributors settle for once-a-day visibility isn't unwillingness — it's that routes run through basements, warehouses and rural stretches with no signal, and a stock count that depends on a live connection to the office breaks exactly where it's needed most: mid-transaction, at a stop with no bars.

The count has to update locally on the device the instant the rep records the sale, whether or not the phone has a connection at that moment, and sync to the office the moment it does. If real-time tracking means "real-time when there's signal," it isn't real-time — it's just end-of-day tracking with better excuses.

Practical takeaway

If you're evaluating real-time van inventory tracking, or trying to decide whether your current system actually delivers it, check for these:

1. Does the on-hand count update per transaction, not per sync? A sale, return or damage entry should adjust the van's stock the moment it's recorded, not when the device next reaches the internet.
2. Can a supervisor see any van's current stock without calling the rep? If the honest answer is "call and ask," you have a load sheet, not real-time tracking.
3. Does it survive dead zones? Confirm the count updates offline and reconciles correctly once the connection returns — test it in an actual low-signal stop, not just on office wifi.
4. Can stock move between vans mid-route? A transfer recorded on one device should reduce that van's count and increase the receiving van's count, both visible immediately.
5. Does the end-of-day reconciliation match the running count, not replace it? The two should agree by design — the day's close is a confirmation of a number that was accurate all along, not the first time anyone saw it.

iotoms tracks van stock the same way it tracks a sale: the moment a rep records it on the field app, on-hand quantity updates for that van, offline or on, and the office sees it live across every van in the fleet — the same count that closes the day is the one that was correct at 11am.