Device loss rarely begins in the finance report. It begins on the floor. In a busy warehouse, shared kit is always moving: scanners, handhelds, radios, printers and batteries pass between people, shifts, zones and teams at pace. When control is manual, visibility weakens. A paper log goes un-updated. A spreadsheet is accurate in theory but out of date in practice. A supervisor knows where a device should be, but not where it actually is.
At first this feels manageable. People work around it. Devices are found, replacements ordered, managers intervene, the shift starts. The trouble is that the workaround hides the true cost. What looks like resilience is often the process quietly absorbing avoidable waste every day.
Why this matters more as operations scale
The warehouse is carrying more strategic weight than it used to. UKWA and Savills reported that Great Britain's warehouse market grew by 22% between 2021 and 2024, reaching just under 690 million sq ft, with online retailers increasing their footprint from 8 million sq ft to 69 million sq ft, a rise of 813%.
Scale changes the asset-control problem. A process that worked when movement was simpler may not hold up across multiple shifts, larger teams and higher throughput. For continuous improvement and transformation teams, warehouse asset tracking isn't a narrow admin tweak. It's part of making a larger, faster, more complex operation easier to control.
Why budget checks make loss harder to ignore
Through a normal period, missing or damaged devices get treated as separate incidents. A replacement is ordered, a supervisor investigates, the site absorbs the disruption and moves on. A budget review brings the pattern into view. Replacement costs sit against forecast. Repair spend is examined. Shift-readiness issues get discussed alongside productivity. Finance asks why loss keeps recurring.
That pressure is useful. It's the moment to move from anecdote to evidence. The task isn't to say "we're losing devices". It's to show what the losses are really costing, why the current process allows them to continue, and what better traceability would change.
The real cost is bigger than the replacement value
The most visible cost is replacement spend, and it's the one finance can see clearly. But it's only part of the picture. There is also:
- Time spent searching for missing equipment.
- Delay when operatives can't start because the right devices aren't available.
- Supervisor time spent investigating what happened.
- Admin in logging, reporting, ordering and reconciling.
Then there's accountability. If no one can prove who collected a device, when it came back, or what condition it returned in, the site has limited ability to change behaviour. So device loss shouldn't be judged on the price of the asset alone. The more important question is what weak control is doing to shift readiness, management time and operational discipline.
What should trigger investment in better traceability
The trigger isn't one missing scanner. It's the point where asset issues become visible enough to affect cost, productivity or confidence in the operation. The strongest triggers are practical, measurable and familiar:
- Recurring loss and damage are being normalised. When missing scanners are expected and replacement spend is treated as a normal cost of running the site, the issue is no longer the asset. It's the absence of a reliable chain of custody.
- Shift teams lose time finding devices before work can begin. If operatives wait for scanners and supervisors chase equipment, the site loses productive time before work has properly started. The workarounds adapt, but they still consume time.
- Records exist, but they aren't trusted. Spreadsheets and sign-out sheets can create the appearance of control. If supervisors still walk the floor, check cages and rely on memory, the record isn't doing its job.
- Accountability is unclear when something goes wrong. This isn't about blame, it's about clarity. The site should be able to answer who collected an asset, when, whether it came back and whether damage was reported.
- Peak periods expose the weakness. Many manual processes look fine in normal trading. The cracks show when volume rises, temporary labour increases and managers have less time to intervene.
- The improvement case keeps stalling because the evidence is incomplete. Everyone can describe the waste, but the business case struggles because the numbers aren't there to back it.
Tracking is more than knowing where assets are
Asset tracking is often discussed as if the question is location. Location matters, but it isn't enough. A device can be on site and still unavailable. It can be in use but assigned to the wrong person. It can be returned but damaged, or recorded in a spreadsheet but not physically ready for the next shift.
Better tracking is really about the chain of custody: who collected an asset, when, whether it was returned, and what happened during that usage cycle. The value isn't only finding things faster. It's designing a process where asset movement is controlled by default, rather than reconstructed after something goes wrong. And the strongest improvements support the people running the operation rather than replacing them. Good control makes the right behaviour the easiest behaviour, without asking supervisors to become administrators.
What a good improvement case should measure
Before investing, define what improvement needs to prove. The best pilot metrics are usually the simplest:
- Loss and damage. Has the number of missing, damaged or unreturned devices reduced?
- Time. Are supervisors and operatives spending less time finding, issuing and resolving asset issues?
- Shift readiness. Can teams access the devices they need faster, with less intervention?
- Accountability. Can the site see who collected and returned assets, rather than relying on informal knowledge?
- Management confidence. Are reports clearer, investigations easier and conversations with finance more evidence-led?
A strong case connects three things: cost (loss, damage, repair, replacement), time (searching, issuing, investigating, delayed starts) and control (visibility of who had what, when it moved, whether it came back). Leadership rarely approves change because a process is untidy. They approve it when the current process is costing enough to justify the change.
The right time to act is before the next pressure point
Asset issues tend to surface during reviews, audits, budget discussions and peak preparation. Those moments create attention. But if the site already sees recurring loss, unclear accountability or shift-readiness friction, waiting usually means carrying the same cost into the next reporting period. That doesn't mean every site needs a transformation project. It means the problem should be assessed properly: what's being lost, where time is wasted, which assets are hardest to control, and what better visibility would change. The faster those answers come, the faster the site can decide whether there's a credible case for change. A short warehouse asset diagnostic is a sensible place to start, and the same approach extends across the rest of the eLocker ecosystem.
