Van Stock Management for Utility and Telecom Field Engineers

The warehouse that drives away every morning

A utility or telecom fleet is a warehouse with no walls. 300 vans, each carrying 200 to 400 SKUs of connectors, meters, routers, cable, clamps and safety kit. That is a seven-figure stock holding, split across hundreds of moving locations, and in most operations nobody can say what is in any single van right now.

Van stock management is the discipline of knowing exactly that. Not what was loaded last quarter. What is on the shelf behind the driver seat today, per van, per SKU, per engineer. Most ERPs cannot answer the question. They book stock to a cost centre called "field" and lose sight of it the moment it leaves the depot. We covered the fundamentals in our guide to trunk stock management. This post takes the fleet view: what changes when you run vans by the hundred.

Ventory is a field inventory platform that gives utility and telecom operators real-time visibility of stock in every van, forward stocking location and depot, connected to the ERP they already run. More on where it fits later. First, the problem.

Why van stock management decides your first-time fix rate

Every truck roll that ends without a fix costs twice: the wasted visit and the repeat visit. Aquant's 2025 field service benchmark found that 14% of service visits are unnecessary, and that low performers see avoidable dispatch rates of 24% against 3% for top performers. A large share of those failed visits comes down to one thing: the engineer arrived without the right part.

At fleet scale the stakes compound. A 2% stock accuracy problem in one van is an annoyance. Across 300 vans it is thousands of failed jobs a year, missed SLA penalties, and a parts budget that grows while service levels fall. Utility and telecom operators typically respond by loading more stock into every van. That fixes nothing. It hides the visibility problem under working capital.

The alternative is boring and effective: per-van visibility, scan-based movements, and smart replenishment that tops up each van from the nearest forward stocking location based on what was actually used.

Why van stock fails differently at fleet scale

A 10-van plumbing firm can manage van stock on a spreadsheet and a Saturday count. A 500-van fibre rollout cannot. Five failure modes appear only at scale:

• Ghost stock. The ERP says the part is in van 214. It was used 3 weeks ago and never booked out. Planners order against stock that does not exist, and engineers stop trusting the system.
• Shrinkage without a signal. Parts leak: left on site, swapped between vans, taken for private jobs. Without per-van records there is no baseline, so shrinkage only shows up in the annual write-off.
• Just-in-case over-ordering. Engineers who have been burned by a stockout order double. Multiply one cautious engineer by 300 and you get 35% excess stock parked in vans, aging and untracked.
• Counts that require recalling vans. If the only way to count is to bring vans back to the depot, counts happen once a year, cost a day of productivity per van, and are wrong again within a month.
• Replenishment blind spots. Depots replenish on requests, not on consumption. Vans near a forward stocking location stay full while vans 90 minutes away run empty on the same SKU.

None of these are people problems. They are system problems. Engineers are measured on jobs closed, not stock booked. Any process that asks for manual admin at the end of a 10-hour shift will fail quietly.

What a fleet-scale van stock system needs

Field service tools bolt on a parts list. Warehouse systems assume racks and staff. A fleet needs something narrower and sharper:

• Every van as a real stock location. Van 214 is a location with its own stock record, min-max levels and count history, visible to planners in real time, not a line in a cost centre.
• Scan-based issue and return. The engineer scans a part against the job in seconds, with multi-barcode scanning that reads whatever label the manufacturer printed. If it takes longer than that, it will not happen.
• Offline first. Basements, rural cabinets and underground car parks have no signal. The app must capture movements offline and sync later, or your data quality dies exactly where the work happens.
• Replenishment from forward stocking locations. Consumption on a job triggers a pick at the nearest FSL or in-night locker drop. The engineer collects on the morning route instead of driving to the depot.
• Cycle counts in minutes, not recalls. Engineers count their own van in a guided 10-minute flow at the start of a shift, using instant cycle counting, so accuracy is maintained continuously.
• ERP connection, not ERP replacement. Finance still owns the ledger. The field layer feeds every movement back so the ERP is right for once, whether that ERP is SAP, Oracle, Dynamics, Sage or NetSuite.

This is the slice Ventory is built for. Ventory sits between the ERP and the fleet as the field inventory layer for field service operations: per-van visibility, scan-based movements, offline mobile apps engineers actually use, and replenishment rules per van and per FSL. It is not a workforce management tool and it does not schedule jobs. It makes the stock side of every job accurate.

Proof: what accurate van stock looks like

A national ambulance service runs its vehicle and station stock on Ventory and holds 99.76% rolling stock accuracy across the operation. Vehicles are checked and replenished on shift, not recalled. In field service deployments across engineer fleets, operators using a dedicated field inventory layer report a 70% reduction in stockouts and 30% productivity gains, with stock managed across 450+ field locations from a single view.

The pattern repeats: accuracy first, then everything else follows. Replenishment gets leaner because it runs on real consumption. Excess stock drops because nobody needs a private buffer. First-time fix rises because the part the app promised is actually on the shelf.

Getting started: 5 steps for fleet operators

1. Baseline 20 vans. Physically count a sample and compare against the ERP. The gap you find is your business case. Most fleets find 15 to 30% variance.
2. Define van-level min-max. Use 6 months of job consumption data to set stock profiles per van type and region, not one master list for the whole fleet.
3. Pilot with one region. 30 to 50 vans, full flow: scan on use, guided counts, FSL replenishment. Measure stockouts, count time and accuracy weekly.
4. Wire it to the ERP. Every field movement posts back automatically. No swivel-chair admin, no month-end reconciliation marathon.
5. Roll out by region. With a proven playbook, national fleets go live in 2-3 months, not the multi-year timeline of an ERP extension project.

Field notes

• 14% of field service visits are unnecessary (Aquant, 2025); parts availability is a leading cause you can actually control.
• A national ambulance service holds 99.76% stock accuracy across vehicles without ever recalling them for counts.
• Fleets that replenish vans on scanned consumption instead of engineer requests cut stockouts by up to 70%.

Running a van fleet and still counting by recall? Talk to us and see your fleet as stock locations within weeks.

Frequently asked questions

What is van stock management?

Van stock management is the practice of tracking the parts and materials carried in field service vehicles as formal inventory locations: what each van holds, what each engineer uses per job, and when each van needs replenishment. Done well, it gives planners real-time visibility per van and feeds every movement back to the ERP.

How do you count van stock without recalling vans?

With guided mobile cycle counts. Each engineer counts their own van in a short app-guided flow, typically under 10 minutes, at shift start or on a rolling schedule. The system compares the count to expected stock and flags variances immediately, so accuracy is maintained continuously instead of rebuilt once a year.

What is ghost stock in a van fleet?

Ghost stock is inventory the system believes is in a van but is physically gone: used on a job and never booked, left on site, or moved to another van. It causes failed jobs because dispatch relies on stock that does not exist. Scan-based issue at the point of use is the only reliable cure.

How does replenishment from forward stocking locations work?

Each van has min-max levels per SKU. When a scanned job consumption takes a van below minimum, the system creates a replenishment order at the nearest forward stocking location or locker point. The engineer collects on route the next morning. This cuts depot trips and keeps van stock lean because top-ups follow real usage.

Does van stock software work offline?

It has to. Utility and telecom work happens in basements, plant rooms and rural areas without coverage. A field-grade system captures scans and counts offline and syncs automatically when the device reconnects, so data quality does not depend on signal strength. Ventory's mobile apps are built to work offline by default.

About Ventory

Ventory is the field inventory layer for regulated, high-stakes industries. We give MedTech, 3PL, Aerospace, Energy and FMCG leaders real-time visibility and control over inventory outside the four walls, in hospitals, ambulances, trunk stock, consignment locations, and field service vans. Ventory is ERP-agnostic (SAP, Oracle, Dynamics, Sage, NetSuite) and trusted by a global medtech manufacturer, a national ambulance service, global logistics and consumer-goods operators. See how it works →