When enterprise devices come off warranty, repair the ones with a clean repair history, healthy batteries and years of security support left, and replace units that have hit your repair limit. Refresh the whole model once its security support end date is close. Make the call with a written rule, not one repair quote at a time, so the decision holds up when finance asks why.
If you’re the IT leader with a batch of rugged or shared devices about to lose coverage, this post gives you the five signals that decide each device, a repair limit you can set this week, what each option really costs, and your choices once the warranty ends.
Key takeaways
- Decide by rule, not by quote. A written repair limit makes every out-of-warranty decision consistent and defensible.
- Five signals decide each device. Repair history, battery health, security support, repair availability and the role the device plays.
- Security support end dates turn a device decision into a model decision. When a model’s support is close to ending, refresh the model rather than repairing units one by one.
- The invoice is the smallest part of the cost. IT time, spares and downtime usually outweigh the repair bill.
- Fix warranty coverage at the next refresh. Coverage terms are negotiable when you’re buying a whole fleet.
How to decide whether to repair or replace devices coming off warranty
Decide each out-of-warranty device against the same five signals, and let a pre-set repair limit make the call. A device that passes all five is worth repairing, one that fails your repair limit should be replaced, and a model whose security support is ending should be refreshed as a group.
| Signal | What to check | Points to repair | Points to replace | Points to refresh the model |
|---|---|---|---|---|
| Repair history | Repairs per serial number in the last 12 months | None or one, unrelated | Repeat repairs on the same unit | Repeat repairs across many units of one model |
| Battery health | Whether the battery lasts a full shift and can be swapped | Swappable battery, replacement available | Fixed battery that no longer lasts a shift | Swelling or failing batteries across the model |
| Security support | The model’s published security update end date | Two or more years of updates left | Not a per-unit signal | Support ends before the next planned refresh |
| Repair availability | Parts, certified repair and turnaround after warranty | Parts in stock, certified repair in Canada | Parts scarce or repair slow for this unit | Model past end of service life, no repair path |
| Role criticality | What stops when this device fails | Shared or backup role, spares on hand | A route, till or shift stops without it | Every role on the model is critical |
Start from an accurate device list with model, serial, purchase date and repair history. If you can’t produce one quickly, getting a handle on how many devices you own comes first, because every signal above is checked per serial number.
The five signals that decide repair, replace or refresh
Each signal answers one question about a device or a model, and together they cover nearly every out-of-warranty decision. The first four describe the device. The fifth describes what its failure costs you.
Repair history by serial number
Repair history tells you whether a device is unlucky or worn out. One repair for a cracked screen says little, while the same unit returning three times in a year is telling you it will keep returning.
Look at the pattern across the model as well. When many units of one model show repeat repairs, the problem is the model’s age, and repairing units one by one only delays a refresh you’ll need anyway.
Battery health and swappable batteries
Battery health decides more out-of-warranty calls than any other component, because a device that can’t last a shift is out of service even when nothing is broken. A swappable battery turns that into a cheap fix, while a fixed battery that has worn down usually means a repair close to the cost of a new unit.
Watch for swelling. A swollen battery is a safety issue as well as a reliability one, and it’s a strong sign the whole model is reaching the end of its life.
Security update support end dates
Security support decides whether repairing a device is worth it at all. Manufacturers in Google’s Android Enterprise Recommended program must publish a security update support end date, the last month and year the device is guaranteed to receive security updates, along with how often updates arrive.
Once a model is past that date, every repair extends the life of a device that’s no longer being patched. The post on devices aging out of security updates covers your options in depth, and the end-of-service-life FAQ explains the terms you’ll see in manufacturer notices.
Parts and repair availability after warranty
Repair availability changes once a model ages, because parts become scarce and certified repair slows down. Ask what an out-of-warranty repair costs, how long it takes from shipment to return, and whether parts for this model will still be available in a year.
Role criticality and the cost of downtime
Role criticality decides how much a failure costs while you wait. A shared device with spares behind it can wait for a repair, while a driver’s handheld or a till scanner stops work the moment it fails. Critical roles justify replacing sooner and keeping a properly sized spare pool to cover repairs.
How to set a repair limit for out-of-warranty devices
A repair limit is a written rule that sets the most you’ll spend on one device before replacing it. It works best as two limits together, a cost limit per repair and a count limit per device over a set period.
For illustration only, a team might decide that any single repair quote above half the price of a new device triggers replacement, and that a third repair on one serial within twelve months does too. Pick numbers that fit your fleet, write them down, and apply them to every device. Adjust them once, at the next budget cycle, rather than case by case.
Here’s what actually happens without a limit. Each repair quote looks cheaper than a new device, so every one gets approved, and the fleet ends up carrying old units that have each been repaired several times. The rule exists to stop that drift.
Repair, replace or refresh: what each option costs beyond the invoice
The repair invoice is usually the smallest cost of keeping an old device. IT time to triage and ship it, spares to cover it while it’s away, and the work that stops while a worker waits all add to it, and none of them appear on the repair bill.
Replacing a unit costs more up front but resets its repair history and battery. Refreshing a model costs the most at once, but it replaces a group of devices that would otherwise fail one at a time, each with its own downtime and handling. The ways to reduce mobile device total cost of ownership show where those hidden costs sit.
Repairs also feed the repair queue. If out-of-warranty devices are adding to a growing queue, the post on why your break/fix backlog keeps growing covers how to find the bottleneck.
Options when warranty coverage ends
When warranty coverage ends, you can extend it, pay per repair, hand repairs to a managed lifecycle program, or plan to fix coverage at the next refresh. Most fleets use a mix, depending on the model and the role.
Extended or renewed coverage
Extended coverage makes sense for models with years of security support left and roles where downtime is expensive. It rarely makes sense for a model close to its support end date, because you’d be insuring devices you should be replacing.
Paying per repair
Paying per repair suits low-criticality devices with a clean history. It keeps costs variable, and the repair limit keeps it from drifting.
Managed lifecycle programs
A managed lifecycle program takes over repair logistics, spares and tracking for the fleet, so out-of-warranty devices go through the same tracked loop as everything else. It fits fleets where IT is carrying repairs on top of its main work.
Negotiating coverage at the next refresh
You have the most say over warranty terms when you’re buying a whole fleet. One Canadian freight carrier we work with was running handhelds close to six years old, with batteries swelling and hardware failing in the field, and had first looked at buying more of the same legacy model. Instead, a full-fleet replacement was negotiated with a six-year warranty, one year beyond standard terms, including battery coverage, which addressed the exact failure that had plagued the old fleet.
If budget is the obstacle, the post on refreshing a fleet without a major capital spend covers phasing and funding, and what a healthy refresh cycle looks like covers staggering it.
Out-of-warranty decisions for retail, logistics and healthcare fleets
The five signals apply everywhere, but each industry weights them differently. Role criticality and the operating environment shift the balance.
Retail store scanners and printers
Retail fleets often have many units of a few models, so model-level refresh decisions matter more than unit-level repairs. Swappable batteries and devices that arrive staged and enrolled, as in our work with a national retailer across hundreds of stores, make keeping devices in service far cheaper.
Rugged handhelds in transportation and logistics
Rugged handhelds in trucks and depots wear fastest at the battery, the scan engine and the connectors. Cold, heat and drops shorten their life, so repair history and battery health usually decide the call before security support does.
Shared clinical devices in healthcare
Shared clinical devices are cleaned and charged constantly and pass between staff every shift. Security support carries extra weight here, because these devices handle patient information and a device past its support end date is hard to defend in a privacy review.
Repairing out-of-warranty devices in Canada
Where an out-of-warranty device is repaired affects both turnaround and risk. A device shipped across the border for repair adds courier time and customs handling to every repair, and any device that still holds corporate or customer data raises chain-of-custody questions on the way out and back.
Repair done in Canada keeps the loop shorter and the custody trail simpler. Ask any repair provider where repairs actually happen and how devices are tracked while they’re away.
Where PiiComm fits
Out-of-warranty repair decisions are part of our lifecycle management program. Repairs, spare pool management and asset tracking are handled by our own technicians in Canada, so every device carries its repair history and the signals above are on record when a decision comes up. At refresh, our strategic sourcing team negotiates coverage terms for the whole fleet.
It doesn’t fit everyone. A small fleet with a clean repair record and someone tracking it every month will usually do well with the repair limit and signals in this post.
Questions IT leaders ask about devices coming off warranty
Should I repair or replace devices coming off warranty?
It depends on each device’s repair history, battery health, security update support, repair availability and role. Repair devices with few past repairs and years of support left, and replace devices that hit your repair limit. Refresh any model whose security support ends before your next planned refresh.
How do I decide when a device is worth repairing?
Set a repair limit, such as a maximum repair cost relative to a new device and a maximum number of repairs per device in a year. Repair anything under the limit if the model still has security support. Devices over the limit, or models near the end of support, should be replaced.
What’s the total cost of keeping old devices?
More than the repair invoices. Include your team’s time handling repairs, spares needed to cover devices that are away, and the work that stops while a worker waits. Then account for security risk once a model stops receiving updates, since that cost never appears in the repair budget.
Can enterprise devices be repaired after warranty ends?
Usually, yes, on a pay-per-repair basis or through extended coverage or a managed program. Repair gets harder as a model ages, because parts become scarce and turnaround slows. Check parts availability and the model’s security support end date before committing to repair a group of devices.
How long should rugged devices stay in service?
There’s no fixed age. Keep rugged devices while they receive security updates, last a full shift, and stay under your repair limit. In harsh environments, battery and connector wear often ends a device’s useful life before its security support does, so track both.
Should we buy extended warranty for enterprise devices?
Buy it for models with years of security support left in roles where downtime is expensive. Skip it for models close to their support end date, since you’d be insuring devices you should replace. Coverage is usually easiest to negotiate when buying a whole fleet at refresh.
How do I track device age and repair history?
Keep one asset record per device with model, serial number, purchase date, warranty end date, security support end date, site and every repair. Update it at each repair and swap. With that record, the repair-or-replace decision becomes a lookup rather than an investigation.
Where to start
Pull your list of devices coming off warranty, check each against the five signals, and write down a repair limit before the first out-of-warranty quote arrives. Flag any model whose security support ends before your next refresh, because that group is a refresh decision, not a repair one.
References
- Google, Android Enterprise Recommended requirements. Manufacturers must publish the security update support end date and update frequency for validated devices.