When sites keep running short of working devices, the fleet usually isn’t too small. Devices are leaving service faster than they come back, and nothing fills the gap while they’re gone.
If store, depot, or warehouse managers tell you every week that they don’t have enough working handhelds, the fix is rarely buying more devices. It’s a spare pool, and a repair loop that keeps refilling it.
This post covers why shortages happen, how a spare pool works day to day, how to size and place one, and how to track it so shortages show up before a shift starts instead of during it.
Why sites run short of working devices
A site’s working device count falls a little every week. Devices break, batteries stop lasting a shift, a few go missing, and some sit uncharged or forgotten in a back room.
Each lost device should come back through repair or replacement. The shortage happens when that return trip is slow or untracked. A device sent for repair can be gone for weeks, and if nobody replaces it in the meantime, the site simply works with fewer devices.
Missing devices make it worse. When nobody knows which devices are at which site, a lost device isn’t noticed until someone needs it. The post on the device uptime problem for Canadian retailers covers how this shows up on the store floor.
What a spare pool is and how it works
Definition
A spare pool is a set of ready-to-use devices, already configured and enrolled, that replaces a broken device immediately. The broken device goes for repair, and when it comes back fixed, it refills the pool.
The key difference from a pile of extra devices is that a spare is ready the moment it’s needed. It’s charged, enrolled in your mobile device management (MDM) platform, set up for the right role, and labelled for the site.
A working spare pool runs as a loop. A worker reports a broken device, the site swaps in a spare, the broken device is shipped for repair, and the repaired or replacement device refills the pool. If any step in that loop stalls, the pool drains.
How many spares each site needs
The right number comes from your own repair data. Look at how many devices are out of service at a site in a typical week, and how long each one is gone. A site that loses a few devices a week to repairs that take 10 days needs more spares than one where failures are rare and swaps are fast.
Start by covering your busiest weeks, not your average ones. Peak season, harsh weather, and new hires all raise failure rates, and a pool sized for an average week runs dry when it matters most.
Seasonal sites need a plan of their own. If a store or depot doubles its staff for peak season, its spare pool should grow with it, and the extra spares should come back out when the season ends so they don’t sit idle for the rest of the year.
Then adjust as you go. If a site’s pool is regularly empty, it needs more spares or faster repairs. If spares sit untouched for months, some can move to a site that needs them.
Where spares should sit
A spare only helps if it’s close to the worker who needs it. A central stock of spares in head office doesn’t help a store three provinces away on a Saturday morning.
Most multi-site fleets keep a small number of spares at each site, with a larger pool at a regional or central location to refill them. High-failure sites and sites far from the central pool should hold more locally. For Canadian fleets, distance and winter shipping times matter, so remote sites usually need a larger local buffer than urban ones.
Here’s what actually happens when spares aren’t controlled. They get used as extra devices during busy periods, never get returned to the pool, and the site has no spares the next time something breaks. Keep spares physically separate, labelled, and counted.
How to run the spare pool day to day
The loop only works if each step has an owner and a time limit. These are the checks to put in place.
- A clear swap process that any site manager can follow without calling IT.
- A shipping step with a deadline, so broken devices leave the site within a day or two instead of sitting in a drawer.
- Repair turnaround tracking, with every device out for repair logged and aged.
- Automatic refills, so the pool is topped up when a repaired or replacement device is ready.
- A weekly pool report showing spares available at each site and any site running low.
- A count of missing devices, so losses are investigated rather than quietly absorbed.
Repair turnaround is usually the weakest link. The post on why device repairs take weeks covers how to measure and shorten it, and the post on why your break/fix backlog keeps growing covers what to do when the repair queue keeps getting longer. The older post on device spares strategies has more on the practical lessons.
What changes when the spare pool works
When the pool works, a broken device becomes a short interruption instead of a lost shift. Workers swap devices in minutes, and site managers stop spending their time chasing IT.
One national retailer we work with replaced an aging, inconsistent fleet of scanners and printers across hundreds of stores, with devices arriving ready to use and ongoing lifecycle management for support. The retail case study covers how that program was set up.
Where outside help fits
Running a spare pool across many sites is a logistics job as much as an IT one. Spares have to be configured, shipped, tracked, and refilled, and broken devices have to move through repair on time.
That’s the work behind lifecycle management. Our in-house Canadian team handles spare pool management, repair logistics, and asset tracking, so a broken device is swapped quickly and the pool stays full. The guide to choosing a lifecycle partner for multi-location retail covers what to look for if you’re comparing options.
Just know that it fits best for fleets spread across many sites. A single site with a small fleet can usually run a simple spare shelf and repair log without outside help.
Questions we hear about device spare pools
Why do our sites keep running short of working devices?
Because devices leave service faster than they return. Breakages, worn batteries, missing devices, and slow repairs reduce the working count, and without ready spares nothing fills the gap. The fix is a spare pool and a repair loop that refills it, not simply buying more devices.
How many spare devices should each site keep?
Size the pool from your own data. Look at how many devices are out of service at a site in your busiest weeks and how long repairs take, then hold enough spares to cover that. Adjust monthly, moving spares from sites that never use them to sites that keep running out.
How do I track repair turnaround and lost devices across sites?
Log every device that leaves a site for repair with the date it left, and report weekly on anything out longer than your target. Count devices at each site against your asset records each month, and investigate any device that can’t be found instead of writing it off.
Where to start
Ask each site how many working devices it has today and how many are out for repair, then compare that with your records. Pick the site that runs short most often and set up a small, labelled spare pool there with a simple swap and ship process. Measure how often it empties, and use that to size the pools for every other site.