Inventory Shrinkage in Field Operations: Causes, Formula and Prevention

Inventory management
October 23, 2026
8 min read

Inventory shrinkage explained for field operations: the formula, the classic causes, and why vans and forward stocking locations shrink 5-15% when counts are manual. Learn the prevention systems that hold field stock accuracy above 99%.

Inventory shrinkage: the stock you paid for but cannot find

 

Inventory shrinkage is the gap between the stock your system says you own and the stock a physical count actually finds. Book stock says 40 units. The shelf holds 34. Six units are gone. No sale, no scrap record, no transfer. Just a write-off that lands straight on your margin. That is shrinkage in inventory, and it is one of the few supply chain losses that stays invisible until someone counts.

 

The calculation is simple. Take the value of your recorded stock (book stock). Subtract the value of your counted stock. Divide the difference by book stock and multiply by 100. Record €200,000, count €188,000, and your shrinkage rate is 6%. Most companies run this maths once or twice a year, after an annual count or an inventory audit across distributed locations. By then the loss is history. You can book it, but you cannot explain it.

 

Most advice on inventory shrinkage is written for retail: shoplifting, POS fraud, cashier error. Useful if you run stores. Less useful if you run engineer vans, forward stocking locations and consigned stock at customer sites. At Ventory we work with exactly those operations, and shrinkage there follows different rules. This post covers both: the standard definition and causes first, then the field-specific mechanics and the prevention systems that actually close the gap.

 

Why shrinkage deserves a line on your P&L review

 

Shrinkage is not a rounding error. Per the National Retail Federation's National Retail Security Survey, retail shrink reached 1.6% of sales in 2022, around $112.1 billion in losses. The more telling number sits inside that figure: 27% of shrink came from process failures, control gaps and errors. Not thieves. Broken process.

 

In field operations that process share dominates. There is no shoplifter in a locked van. What you have instead are parts consumed on jobs and never logged, transfers that leave one location and never arrive in the record at the next, and consigned stock used without a usage report. Across field operations we see vans and forward stocking locations commonly shrink 5-15% when counts are manual.

 

Stat card: vans and forward stocking locations commonly shrink 5-15% of inventory when counts are manual, across field operations

 

And the write-off is only the visible cost. Phantom stock, inventory your ERP believes exists but does not, drives the expensive second-order effects: engineers dispatched to a van that does not hold the part, failed first-time fixes, emergency shipments, and buffer stock ordered because nobody trusts the numbers. Ventory customers typically find that fixing shrinkage visibility cuts stockouts and excess stock at the same time, because both were symptoms of the same bad data.

 

The causes of inventory shrinkage

 

The classic causes of inventory shrinkage apply to any stockholding operation:

 

  • External theft. Shoplifting and organized retail crime. The biggest single slice in retail at 36% per the NRF survey.
  • Internal theft. Employees removing stock. 29% of retail shrink.
  • Administrative and process error. Mis-picks, unrecorded movements, wrong receipts, data entry mistakes. 27% in retail, far more in field operations.
  • Vendor fraud and receiving errors. Short shipments booked in at full quantity.
  • Damage, expiry and obsolescence. Stock that physically exists but has no value, and never gets written down until a count forces the issue.

 

Now move that list outside the warehouse. In the field, theft is rarely the main story. Shrinkage happens quietly, location by location:

 

  • Engineer vans. A technician uses three fittings on a job and logs none. The van's trunk stock drifts further from the ERP with every ticket closed.
  • Forward stocking locations. Nobody staffs them. Engineers pick what they need, returns pile up in corners, and the record only resets at the next audit, months later.
  • Consignment and customer sites. Your stock sits on their shelf. A nurse or operator uses an item and the usage report never comes. You cannot bill it, and you cannot replenish what you do not know is gone.
  • In transit between locations. A part leaves the warehouse for a van or a forward stocking location. The sending system says shipped. The receiving side never confirms. The item now exists nowhere.
  • Returns and swaps. A swapped part comes back from a job and skips the system on the way in. Good stock gets counted as gone; defective stock gets counted as good.

 

None of this is malicious. It is what happens when the inventory system lives in the warehouse and the inventory lives in the field. We covered that structural gap in detail in the spare parts field gap.

 

What inventory shrinkage prevention looks like in the field

 

Retail prevention is cameras, tags and loss prevention teams. Field operations need something else: a system of record that travels with the stock. We call it the field inventory layer, the connective tissue between your ERP and every van, locker and consignment shelf. Effective inventory shrinkage prevention in the field stands on four mechanics.

 

1. Capture at the moment of movement. Every pick, use, transfer and return gets scanned on a phone, in seconds, at the point where it happens. Multi barcode scanning makes this faster than not scanning: one camera pass books an entire shelf or kit. If logging takes longer than skipping, people skip.

 

2. Count small and often. Replace the annual wall-to-wall count with cycle counting: five minutes per van per week, rotating through forward stocking locations by risk. Shrinkage found within days is explainable and fixable. Shrinkage found after a year is just a number.

 

3. Alert on variance, not on audit day. When a count disagrees with book stock, when a transfer is not received, when consigned usage stops reporting, someone should know the same day. Alerts and notifications turn shrinkage from an annual surprise into a daily exception queue.

 

4. Close the loop with the ERP. Field transactions sync back automatically, so book stock and reality stop diverging in the first place. The table below maps the mechanics to each location type.

 

LocationHow it shrinksThe fix
Engineer vansParts used on jobs but never logged; trunk stock drifts from the ERP with every closed ticketScan at the moment of use; five-minute weekly cycle count per van
Forward stocking locationsUnstaffed sites; unrecorded picks and returns accumulate between auditsRisk-based cycle counts; variance alerts the same day
Consignment and customer sitesStock consumed without a usage report; billing and replenishment lag behind realityDigital usage capture with real-time consigned stock visibility
In transit between locationsItems leave one site and never arrive in the record at the nextScanned transfers with send and receive confirmation on both ends
Returns and swapsSwapped and returned parts skip the system on the way back inMandatory return scan before the job can close

 

The proof

 

A national ambulance service runs Ventory across a 100-vehicle fleet and holds 99.76% rolling stock accuracy, counted continuously rather than annually. Across customers managing 450+ field locations, field adoption sits above 95%, because scanning is faster than the paperwork it replaced. The downstream numbers follow the accuracy: 70% fewer stockouts, 35% less excess stock, and +30% productivity for the teams who used to spend their days reconciling and searching.

 

Getting started

 

  1. Measure your baseline. Count a sample of vans and forward stocking locations this month. Run the shrinkage formula per location. Expect uncomfortable numbers; that is the point.
  2. Rank locations by exposure. High-value parts, consigned stock and unstaffed sites first.
  3. Start a focused first scope at 3-5 locations. Put mobile scanning, cycle counts and variance alerts live where the loss is worst.
  4. Review variances weekly. Every gap gets a cause: unlogged use, transit loss, return not booked. Causes get fixes; write-offs get smaller.
  5. Scale on evidence. Deployment runs 4-8 weeks. Roll out to the rest of the network once the first scope shows the accuracy curve bending.

 

Ready to find out where your stock is actually going? Talk to the Ventory team.

 

Field notes

 

  • 27% of shrink comes from process failures and errors, not theft, per the NRF survey. In field operations that share is far higher.
  • Vans and forward stocking locations commonly shrink 5-15% when counts are manual. Scanned, cycle-counted locations hold above 99%.
  • A 100-vehicle ambulance fleet runs 99.76% rolling accuracy: shrinkage prevention is a daily habit, not an annual event.

 

Frequently asked questions

 

What is inventory shrinkage?

 

Inventory shrinkage is the difference between the inventory your records say you hold (book stock) and the inventory a physical count confirms. It covers theft, administrative error, unrecorded usage, vendor fraud, damage and expiry. The loss is written off against margin, which makes shrinkage a direct profit leak rather than an accounting detail.

 

How do you calculate inventory shrinkage?

 

Subtract the value of counted stock from the value of book stock, divide by book stock, and multiply by 100. If records show €200,000 and the count finds €188,000, shrinkage is 6%. Calculate it per location, not just in total: a healthy network average can hide individual vans or sites losing 15%.

 

What causes inventory shrinkage in field operations and which systems prevent it?

 

Field shrinkage is driven by process gaps rather than theft: parts used on jobs but never logged, transfers lost between locations, consigned stock consumed without a usage report, and returns that skip the system. Prevention needs a field inventory layer: mobile barcode scanning at the moment of movement, frequent cycle counts, automatic variance alerts, and two-way sync with the ERP so book stock stays true.

 

What is a normal inventory shrinkage rate?

 

Retail averaged 1.6% of sales in 2022 per the NRF National Retail Security Survey. Field operations run far wider: vans and forward stocking locations commonly shrink 5-15% when counts are manual, while digitally tracked field networks hold accuracy above 99%. If you have never measured per location, assume you are closer to the first number than the second.

 

Does inventory shrinkage prevention slow down field engineers?

 

Not if the tooling is built for the field. A multi barcode scan books a full kit in one camera pass, and a weekly van count takes about five minutes. Adoption above 95% across 450+ field locations shows engineers keep using it, because scanning replaced paperwork rather than adding to it.

 

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 →

Not sure where your field inventory leaks?

Ten questions. You get a field readiness score, a gap tier and the three fixes worth doing first.

Start the assessment
Ventory

Ventory is the field inventory layer between your ERP or WMS and the teams working outside the warehouse: engineer vans, forward stocking locations, consigned stock and loaner kits.

About Ventory

See it on your own field stock.

Book a demo
See what's really happening in your field inventory.
Join the global enterprise teams who trust Ventory to manage inventory beyond the warehouse.
Enterprise-validated
SOC 2 compliant
Live in 4-8 weeks
Mobile-first