Van Sales Expiry Tracking: The Mobile Inventory Challenge

The twelve hours a day when nobody knows what's happening to your inventory

Your van leaves the depot at 6 AM carrying ₹3 lakhs of inventory. It visits 40-60 retail points across its beat. It returns at 7 PM with unsold stock, cash, and a story about the day that may or may not match what actually happened. For those twelve hours, the inventory on that van exists in a state that's best described as managed optimism — you loaded it, you trust the salesman, and you'll reconcile when he gets back. Probably.

Van sales is the backbone of FMCG distribution in India. It's also where every inventory discipline you maintain at the depot — FEFO enforcement, batch tracking, temperature control, shrinkage monitoring — goes to die. The moment stock transfers from your warehouse to a van, it exits the system in every way that matters. You know what was loaded. You know what comes back. The twelve hours in between is a black hole.

This isn't primarily a trust problem (though shrinkage is real and we'll get to it). It's a visibility problem. Even a perfectly honest salesman operating with the best intentions can't maintain FEFO discipline on a van carrying mixed batches of 40 SKUs in crates that were packed for space efficiency rather than expiry sequence. The systems and physical constraints simply don't support it. And the financial consequences — returns, expiry, shrinkage — accumulate across every van, every day, every route, until they represent a line item that most distributors have learned to accept as "the cost of doing business" rather than what it actually is: a systems failure with a measurable price.

the FEFO death spiral that nobody talks about

Here's a pattern that plays out on vans across India every single day, and it explains why certain batches of product seem to circle through the distribution system indefinitely until they expire.

Day one: the van is loaded with 50 units of Batch A (expires in 60 days) and 50 units of Batch B (expires in 90 days). Batch B was loaded last, which means it's on top, which means it's what the salesman reaches for first. Day one sales: 30 units of Batch B, because it was accessible and because retailers — being rational — prefer fresher stock when given the choice. Day one returns to depot: all 50 of Batch A, untouched, plus 20 remaining of Batch B.

Day two: the depot loads the returned Batch A (now 58 days to expiry) alongside new Batch C (90 days). Batch C goes on top because it just came off the production line and was staged near the loading bay. Sales: Batch C moves. Batch A comes back again. Now 56 days.

After two weeks of this, Batch A has taken ten round trips on vans, been rejected by multiple retailers who saw the approaching expiry date and asked for something fresher, and is now at 30 days — past the point where most retailers will accept it. It finally expires in the warehouse, and the write-off gets attributed to "slow-moving stock" rather than what it really was: a loading sequence problem that condemned this batch to an endless loop of van trips from which it was never going to escape.

The reason this is a death spiral and not just an inconvenience is that it's self-reinforcing. The older batch gets harder to sell, which means it's more likely to come back, which means it takes another trip, which makes it older, which makes it harder to sell. Without a system that forces FEFO at the loading dock — "Batch A goes on top, Batch C goes on the bottom, and the salesman sells from the top" — the oldest batch will always be the last one sold, which means it will frequently not be sold at all.

the end-of-day reconciliation that isn't one

In theory, the end-of-day process works like this: van returns, physical count matches the system, batch-wise returns are logged, discrepancies are investigated, and stock is properly reintegrated into depot inventory.

In practice, the van returns at 7 PM. Everyone — the salesman, the warehouse staff, the supervisor — wants to go home. The reconciliation is a quick count of cartons (not units, not batches — cartons). "Looks about right." The returned stock gets dumped in the returns area. Tomorrow's loading picks from whatever's there, mixed batches and all.

The 2-3% discrepancy that routinely emerges between loaded quantity, sold quantity, and returned quantity gets absorbed into "shrinkage," which is the accounting term for "we don't know where it went." Across 10 vans running 300 days a year, that 2-3% adds up to lakhs. Some of it is genuine damage or spoilage. Some of it is pilferage. And some of it is simply the result of counting cartons instead of units, which means the error might not exist at all — it might just be a rounding error compounded across a hundred transactions. You don't know, because the reconciliation process wasn't designed to tell you.

temperature: the shelf life killer you can't see

A van operating in Indian summer conditions subjects its inventory to 35-45°C for 10-12 hours. The printed shelf life on the product assumes "store in a cool, dry place." The inside of a van in May is neither cool nor dry. Every hour at elevated temperature reduces the effective shelf life of temperature-sensitive products, even if the calendar says they still have months remaining.

Chocolate and confectionery melts, blooms, and distorts. The return gets logged as "damaged" and attributed to the manufacturer, when it was actually heat-damaged on your van. Biscuits accelerate their staling. Snacks lose their texture. Personal care products — creams, lotions — undergo separation and degradation. The products technically haven't expired, but they've functionally degraded to the point where selling them creates customer complaints, and the complaints get attributed to "product quality" rather than "we baked it in a van for six hours."

The fix is straightforward in concept: insulated containers for temperature-sensitive products, route timing that minimises heat exposure (deliver perishables in the morning, shelf-stable products in the afternoon), and temperature indicators that provide evidence of exposure. The challenge is that all of these solutions have costs — insulated containers take up space and reduce the van's carrying capacity, morning-priority routes require reorganising beats, temperature indicators require someone to actually check them. Most distributors accept the temperature damage as a cost of doing business because the mitigation costs feel more immediate than the damage costs, which are diffused across hundreds of small incidents.

the loading discipline problem that creates all the downstream problems

The most impactful intervention in van sales expiry management is also the earliest one in the daily sequence: how the van is loaded in the morning.

The ideal loading process: the system generates a load list based on route requirements, prioritising oldest acceptable batches. Physical loading follows the list sequence, with oldest batches loaded last so they come off first. The salesman receives a batch-wise manifest and records sales against specific batches.

The actual loading process at most depots: load whatever's in the staging area, fill crates to maximise space utilisation, give the salesman a total quantity count, and wish him well. Sales are recorded against "Product X, quantity Y." Batch? "Whichever batch I pulled out of the crate."

The gap between these two processes is the entire van sales expiry problem in miniature. If you get the loading right — oldest batches on top, FEFO enforced before the van leaves the dock, manifest that the salesman can actually follow — a significant portion of the downstream problems (returns, aging loops, batch confusion) simply don't occur. If you get the loading wrong, no amount of downstream intervention can fully compensate.

what the salesman needs (and what he currently has)

Most van sales operations have equipped their salesmen with handheld devices that handle order capture, invoice generation, payment recording, and route tracking. These devices solved the order management problem. They didn't solve the expiry management problem.

What the salesman needs on his handheld: batch-wise inventory showing what's on the van right now, FEFO prompts that tell him which batch to sell first for each SKU, warnings when he's about to sell a newer batch before an older one, and real-time stock position visible to the depot so that someone at base can flag issues during the day rather than discovering them at 7 PM.

What the salesman needs in his incentive structure: rewards for FEFO compliance (selling older batches first), penalties or reduced commissions for high return rates, and recognition for zero-shrinkage trips. The current incentive structure — volume sold, outlets covered, payments collected — creates rational behaviour that is completely misaligned with expiry management. The salesman who pushes 250 cartons onto two large retailers (hitting his volume target in an hour) and the salesman who carefully distributes 250 cartons across 30 retailers according to velocity and capacity are compensated identically, even though the first salesman is almost certainly creating return liability that the second one isn't.

the returns loop that turns waste into a recurring event

The most insidious aspect of van sales returns is that returned stock often gets re-loaded onto vans and sent back out. It comes back from Retailer A, goes to the returns area, gets loaded onto tomorrow's van (because it's still within shelf life, technically), goes to Retailer B, gets rejected (because the retailer sees the approaching expiry date), comes back, gets loaded again. Each round trip costs fuel, salesman time, and shelf life. The product degrades with each cycle of heat exposure and handling.

Breaking this loop requires quarantine discipline at the depot — returned stock must be assessed for remaining sellable life before it can be re-loaded. If a product comes back with less than 30 days of shelf life, it should go to a discount channel or be written off immediately, not re-enter the van cycle. The emotional resistance to this is understandable (writing off a product that's "still good for 25 days" feels wasteful), but the economic reality is that sending it on another van trip costs more than the product is worth.

the measurement that changes behaviour

The single most powerful metric for van sales expiry management is the route-level return rate. Not the aggregate return rate across all vans (which averages out the problem stores and masks the patterns), but the return rate for each specific route, each specific salesman, each specific SKU category.

When you can see that Route 7 has a 12% return rate while Route 3 has 4%, and both cover similar retailer profiles with similar products, you know that the difference is operational — loading discipline, salesman behaviour, retailer management — and you can investigate and fix it. When you can see that Salesman X sells 20% more volume than Salesman Y but generates 40% more returns, you know that Salesman X is pushing stock rather than placing it, and you can adjust his incentives accordingly.

Daily: verify that reconciliation was batch-level, not carton-level. Weekly: review return rates by route and flag anomalies. Monthly: assess salesman performance on FEFO compliance and return rates. Quarterly: restructure routes and loading processes based on the patterns that the data reveals.

The van that returns with accurate batch records and minimal returns isn't just a well-managed vehicle. It's the difference between margins that exist on paper and margins that exist in your bank account.

ShelfLifePro's van sales module brings depot-level batch tracking to mobile distribution. FEFO-enforced loading, real-time batch visibility on handheld, and return reconciliation that works. Because twelve hours of invisibility shouldn't cost you lakhs.