Break/fix in enterprise mobility is not a model you select from a menu. It is a physical event that will happen to every rugged device you deploy, and the only real question is how long resolution takes once it does. That number is set long before the device fails, by systems your organisation either built or skipped.
A handheld out of service is a worker who cannot scan, pick, deliver, or chart. One unit down is a nuisance. Across a fleet spread over dozens of sites, the delay compounds into missed shipments, understaffed shifts, and paper workarounds that create errors of their own.
This article works through what actually happens when a rugged device fails. The resolution process stage by stage, the repair-or-replace decision, how to size a spare pool for a distributed fleet, the cost that never reaches the repair invoice, disposition of the devices that never come back, and the Canadian logistics layer that shapes all of it.
Key takeaways
- In enterprise mobility, break/fix is an unavoidable physical event rather than a commercial model you can opt out of, because every rugged device you deploy will eventually fail.
- The repair itself is the minority of resolution time, with intake, triage, warranty verification, spare preparation, and reverse logistics consuming most of the clock.
- The repair-or-replace-or-retire decision should be structured in advance against remaining life, warranty status, damage category, and OEM support, not improvised per ticket.
- An unmanaged spare pool is inventory rather than coverage, because spares that are unconfigured, out of date, or unlocatable do nothing at the moment of failure.
- Devices that never return to service are part of the break/fix stream and still carry live data, so disposition through Secure Decommissioning is part of the process, not a separate afterthought.
What break/fix means for enterprise mobile devices
Break/fix for enterprise mobile devices is the process of diagnosing a failed field device, deciding whether to repair or replace it, and returning a working unit configured to the worker’s role and applications.
The device that comes back has to carry the right operating system, the current gold image, its MDM enrolment, and the line-of-business software the job depends on. A repaired chassis that boots to a factory state has not resolved anything.
This is a different subject from the one that dominates the search results. In general IT, break/fix describes an hourly-billed provider who fixes servers, switches, and workstations on call, chosen as an alternative to a managed contract. That debate is about billing models and retainers. It has nothing to do with a scanner that took a hard drop onto a concrete floor.
The distinction matters because it changes what break/fix is. In general IT you are deciding whether to buy the service at all. In enterprise mobility you are not.
Rugged devices run in cold storage, on loading docks, in ambulances, and across job sites, and they fail as a function of that environment. A mobility break/fix event is absorbed, not purchased, and what varies is the speed and the cost of absorbing it. Both are governed by decisions made before anything broke.
Mobile break/fix differs from IT break/fix in four ways
The two share a name and almost nothing else. Four differences separate a mobility break/fix programme from the IT support contract the term usually describes.
| Dimension | Traditional IT break/fix | Enterprise mobile break/fix |
| Physics of failure | Software and hardware faults on servers, switches, and workstations | Physical damage from environment and duty cycle, traced back to how the device was matched to its environment |
| Geography | Devices on site, carried down the hall to the IT desk | Devices dispersed across delivery trucks, warehouse aisles, hospital wards, and remote job sites |
| Configuration | A reimage restores the machine to service | A replacement is inert until it carries the correct OS, gold image, MDM enrolment, and line-of-business application |
| Vendor process | One support contract or retainer | Zebra, Honeywell, and Samsung each run separate warranty and RMA processes, with their own rules and handling |
Remote monitoring reaches only part of this. You can push a patch to a device. You cannot push a new charging port. A mixed fleet means a mixed set of administrative paths, and that is where the days quietly disappear.
We see the same pattern in nearly every fleet we take on. Devices get shipped for repair before anyone has established whether they are under warranty, and the diagnostic fee arrives on a unit that was already scheduled for retirement. In theory triage and warranty verification happen first. In practice the device is already in a box heading to a depot, because that felt like action.
The 7 stages of a break/fix resolution
A break/fix resolution is a sequence, and the repair sits near the middle of it. Seven stages separate the moment a device fails from the moment the fleet record closes, and time leaks out of every one of them. Finding where it leaks is the whole exercise, because the repair itself is rarely the bottleneck.
- Intake. A fault has to reach the right queue through a channel built to receive it. When the report lands in a site manager’s inbox or a group chat instead, no clock starts, and the device sits idle while everyone assumes someone else has logged it. A programme with no defined intake channel is not slow. It has not begun.
- Triage. This is the stage most often skipped. The question is whether the fault is hardware, software, or user error. A device shipped to a depot when it needed a reboot burns freight and a diagnostic fee for nothing, and the worker waits days for a fix a short call would have delivered.
- Identification. Before anything moves, you need the serial number, the service history, and any prior work on this specific unit. The asset register that should hold that information is frequently a spreadsheet last reconciled more than a year ago. When you cannot identify the device, you default to the most expensive decision available.
- Warranty verification. Its failure mode is almost universal. Coverage falls into one of three states, in warranty, out of warranty, or damaged outside what the warranty covers. Most organisations establish which state applies when the repair invoice arrives, which is exactly too late to change the decision. Verifying coverage first is the difference between an OEM repair at no cost and a paid repair on a device the manufacturer would have handled.
- The repair-or-replace decision. It sits at the centre, and it earns its own section below. What matters here is that it depends entirely on the four stages before it. A decision made without identification and warranty status is a guess.
- Spare issue and configuration. This is where a good process still fails on execution. A replacement is not a device in a cupboard. It is a device that has been charged, enrolled, and loaded with the current image, ready to work the moment it arrives. A hot spare two OS versions behind still has to be prepared under pressure and does not count as coverage until it is.
- Reverse logistics and reconciliation. The failed unit has to come back, get tracked, and have its records closed, whether it returns to service, moves to a repair depot, or goes to disposition. When that final step is skipped, and it usually is, the fleet count on paper drifts away from the fleet that physically exists, and every future decision inherits the error.
Look at where the failure modes cluster. Identification, warranty verification, spare configuration, and reconciliation are not repair tasks. They are lifecycle functions, the running discipline of knowing what you own, what state it is in, and where it is. This is what Lifecycle Management does, and an organisation that has not built it cannot make the repair decision quickly no matter how skilled the technician holding the screwdriver. The repair was always the easy part.
When to repair, replace, or retire a failed device
Repair spend looks unpredictable because the decision that drives it is made ad hoc, one device at a time, by whoever happened to pick up the ticket. No individual repair is ruinous. The unpredictability comes from having no framework, so the same fault gets repaired on Monday and replaced on Thursday depending on who was at the desk.
A defensible decision weighs five inputs, and none of them is the repair quote in isolation.
| Input | What to weigh |
| Remaining useful life | Measured against your refresh cycle. Spending on a device six months from planned retirement rarely makes sense. |
| Repair cost as a share of replacement | The ratio matters more than the absolute figure. A low-cost repair on a near-dead device is still a poor use of money. |
| Warranty and coverage status | A covered repair and an out-of-pocket one are different decisions on identical hardware. |
| Damage category | A cracked screen is a contained, known-cost fix. A logic board fault or water ingress damages components that have not failed yet. |
| Device generation and OEM support | A model Zebra or Honeywell no longer supports is a dead end regardless of the quote, since the next failure will have no path at all. |
Those inputs resolve into three paths.
- You repair when the unit has meaningful life left and the fault is contained to a known-cost component.
- You replace from spare stock when downtime cost outweighs repair economics, which across a distributed fleet describes most incidents, because a worker left idle costs more than the difference between repair and replacement.
- You retire when the model is past OEM support, the repair approaches replacement cost, or the unit has failed repeatedly and is telling you something.
The retire path is where most organisations stop thinking, and that is the costly place to stop. The retire pile is the largest single category on many of the fleets we take on, and until we name it, nobody has.
A retired device is not a resolved one. It still holds corporate data, may still hold a live SIM, and now sits in a drawer outside any tracked process. The break/fix decision that ends in retirement has not ended. It has moved the device into a second stream that needs its own handling.
Where break/fix resolution time actually goes
The repair is the smallest part of resolution time. Most of the days a broken device spends out of service are consumed before and after the bench work, not during it, and that is where the cost and the frustration actually live.
Account for the full clock. There is time before a ticket is even raised properly, while the fault sits in an inbox. There is time in triage, or time lost to skipping it and shipping a device that needed a reboot.
There is time to establish warranty status, time to locate and prepare a spare that carries the current image, and time for reverse logistics to close the loop at the end. Bench repair is one line in that list, and usually not the longest. We see the same distribution on nearly every fleet we assess.
The labour hidden in those steps is real and measurable. Research VDC Research conducted for Dell, surveying 461 IT decision-makers across North America and Europe in January 2025, found that every device failure costs an average of 37 minutes of lost worker productivity. That is the number people expect, the cost of the idle worker.
The figure that matters more is the one the same study places beside it, 26 minutes of IT support labour on every failure. That 26 minutes is work your team performs on every incident, and it appears on no repair invoice, in no vendor quote, and in no line of the hardware budget that repair spend is tracked against. Multiply it across a fleet’s annual failure volume and the coordination cost rivals the repair cost, invisibly.
What break/fix costs beyond the repair invoice
Repair spend shows up as a hardware line item, and that single accounting choice makes everything expensive about break/fix invisible to the people approving the budget. They see the depot invoice, not the four costs stacked behind it, because none of those costs has a line of its own.
| Hidden cost | What it is |
| Internal coordination labour | IT time spent triaging, verifying, chasing OEMs, and closing tickets. |
| Lost productivity | Not only the idle worker but anyone downstream who cannot finish their own task until the scan, the pick, or the delivery happens. |
| Freight | Moving devices that never needed a depot, the direct cost of skipping triage. |
| Capital tied up in spares | Bought reactively at list price, because a device purchased in a panic costs more and is rarely the configured unit you needed. |
Give yourself the categories and run your own numbers against them. The point is that four real costs are being absorbed into a line labelled something else, and on the fleets we assess this hidden coordination cost regularly rivals the repair spend it hides behind.
There is a further cost that never touches an IT budget at all. Zebra’s Warehousing Vision Study, published in February 2025 and surveying more than 1,700 associates and decision-makers, found that 93 percent of associates agree that better availability of automation and mobile technology would help attract and retain warehouse staff. Working equipment is a retention factor in a labour market where retention is expensive, and a worker handed a broken or half-configured device several times a month draws a quiet conclusion about the employer. That cost lands in HR and operations, never in the repair ledger, which is precisely why it goes unmanaged.
If you want the categories laid out inside the full picture, our device lifecycle management guide walks through them as a next step.
How to size a spare pool for a distributed fleet
Ask how many spares to hold and you will be told three to five percent of the fleet. It is a reasonable place to start and a poor place to stop, because it is a single average applied across organisations whose failure rates and logistics have nothing in common. A wash-down food plant and a corporate retail floor running the same device count do not carry the same spare requirement, and the percentage hides that.
Four variables move the real number.
| Variable | What it does to the number |
| Failure rate by environment | Cold storage, wash-down lines, and outdoor use destroy devices far faster than a climate-controlled retail floor, so a fleet split across those conditions needs its spares weighted toward the harsh end. |
| Repair turnaround | Every extra day a device spends in the resolution loop is a day a spare has to cover in its place, so slow reverse logistics quietly raises the number you must own. |
| Geographic dispersion | A spare in a Mississauga stockroom does nothing for a depot in Thunder Bay when the truck rolls at six the next morning. Positioning is a distribution question, not only a quantity one. |
| Seasonal load | A fleet running flat out through a November peak needs deeper cover than the same fleet idling in March, and a static percentage set once a year serves neither season well. |
The problem is almost never a pool that is too small. It is a pool that is unmanaged. Spares sit unconfigured, or two OS versions behind and useless the moment they are needed. Spares get issued as permanent replacements and never replenished, so the pool bleeds down until an incident finds it empty. Others go missing because nobody tracked where they went. A pool in that state is not coverage against downtime. It is inventory on a shelf, and inventory does not answer a page at two in the morning.
Secure decommissioning for devices beyond repair
Every break/fix programme produces a second stream, the devices that will never go back into service, and most organisations have no process built to catch it. They have a repair path. They do not have a disposition path, so the failed-for-good units accumulate wherever there is a spare drawer.
Look at what collects there. Units beyond economical repair. Units cannibalised for parts to keep others running. Units sent out under advance replacement whose originals were never returned. Units from models that lost OEM support partway through their deployed life. All of them share one trait, which is that they still exist and still hold data.
The risk is concrete and understated. A device that failed physically has not been wiped, and a cracked screen erases nothing on the storage inside it.
The category break/fix generates most of is the device that will not power on, and a device that will not power on cannot be remotely wiped through your MDM. The data is still there. It is simply sitting in a unit nobody can log into, in a drawer nobody is tracking.
The cost environment around that exposure is not small. The 2026 IBM Cost of a Data Breach Report puts the average breach lifecycle at 205 days, up six percent from the year before. That is the figure that maps directly to a dead handheld sitting untracked for months before anyone asks where it went. The same report records a record average breach cost of CA$7.11 million for Canadian organisations, which describes the environment a lost data-bearing device sits inside rather than a price tag on any single unit.
The national numbers show where the attention is not going. Statistics Canada reports that spending by Canadian businesses on recovering from cyber security incidents doubled from roughly $600 million in 2021 to $1.2 billion in 2023, while spending on prevention and detection rose far more slowly over the same period, from $9.7 billion to $11.0 billion. Canadian businesses are paying more to clean up than they are investing to get the process right, and an untracked pile of failed devices is exactly the kind of gap that becomes cleanup.
Disposition done properly is a defined sequence. Data is sanitised, SIMs are destroyed, and units with no residual value go to certified recycling rather than a bin, which is the work behind our recognition as a 2023 Leader in Sustainability by Call2Recycle Canada. Where value remains, it is recovered through trade-in or resale. Recovery on a damaged unit is usually low but not always zero, since a model still under OEM support can carry trade-in value even with a cracked screen. This is IT asset disposition handled as Secure Decommissioning, the deliberate close of the lifecycle rather than a drawer.
Break/fix logistics in Canada
Geography changes the arithmetic of break/fix in Canada, and it changes it in ways a support model designed for a denser market gets wrong. Five realities separate a Canadian rugged fleet from the same fleet in one dense metro.
- Distance. A fleet spread across six provinces and three time zones has a spare logistics problem a single-metro operation never encounters. Next-day delivery carries an asterisk the moment you move north of the population corridor.
- Cross-border repair routing. A depot repair routed through a United States facility adds customs clearance on both legs, plus duty and brokerage exposure that never appears in the headline price. It also means a device holding Canadian corporate data leaves the country for the duration, which is a control question before it is a cost one.
- Remote and northern sites. Mining, energy, northern health, and public safety operations run on shipping windows that make spare positioning a design decision, because a missed window is not a late delivery but a multi-week one.
- A worker reporting a fault in Quebec should be able to report it in French, and an intake channel that works only in English gets bypassed, which routes the fault straight back to the inbox that stops the clock before it starts.
- Site density. Canadian enterprises tend toward many small sites rather than a few large ones, which changes spare pool arithmetic and makes on-site technician dispatch uneconomical across most of the country. Coverage has to come from spare positioning and configured replacement, not from a van.
This is why we built support from Canadian facilities, staffed by Canadian people, making Canadian decisions about where a device goes. It is an operational stance, not a data residency claim, and for a distributed fleet running coast to coast to coast it is the difference between a plan that works on a map and one that works in Thunder Bay.
How PiiComm delivers break/fix through Lifecycle Management
PiiComm does not sell break/fix as a standalone service, and that is a design decision rather than a gap in the catalogue. The reason runs through everything above. Identification, warranty verification, spare configuration, and reconciliation have to exist before the repair decision can be made quickly, and a vendor who only repairs inherits your inventory, warranty, and configuration problems at the worst possible moment, the moment a device is already down. A repair-only shop cannot fix what it never built.
So break/fix runs as a function of Lifecycle Management, and the pieces connect. A Canadian-based support desk acts as first line for the mobile worker, troubleshooting connectivity and hardware directly and triaging every device before anything ships, which stops the freight-and-diagnostic waste that untriaged shipping creates. Warranty status is verified and OEM coordination handled on your behalf before a repair path is chosen, not after the invoice lands.
Behind that sits a managed hot spare pool of your specific devices, held charged and configured to your current gold image and MDM profile, so a replacement is working equipment rather than bare hardware the day it arrives. Certified technicians trained on Zebra and Honeywell rugged platforms handle the bench work, with RMA processing and reverse logistics run as one loop, and PiiComm holds Zebra Premier Solution Partner status and is certified on SOTI MobiControl and 42Gears SureMDM, the platforms your enrolments actually run on.
Bi-directional ServiceNow integration posts depot status changes back to the originating ticket, so your own ITSM system stays current without anyone rekeying it, and reconciliation runs through the AIM portal, our proprietary asset management platform, so the fleet count stays honest. Replacement follows the model the situation calls for, advance replacement or replacement upon receipt. Devices that cannot be recovered move into Secure Decommissioning rather than a drawer.
The result is that the four lifecycle functions the repair decision depends on are already running when a device breaks, which is what makes the response fast. We see the difference on every fleet we onboard this way. If you want to know where your own break/fix process leaks time and cost, a fleet assessment is the place to start.
Seven questions to ask a break/fix provider
Use these when you evaluate any provider, PiiComm included. Each is a question a lifecycle-integrated provider answers in a sentence, and a repair-only vendor answers with a pause.
- Who verifies warranty status, and at what point in the process?
- Where does the repair physically happen, and does the device cross a border?
- Who owns the spare pool, and who keeps it configured to our current image?
- What happens to a device that cannot be economically repaired?
- How does a fault get reported, and does that channel work in French?
- How does device status reach our own ITSM system?
- How is the asset count reconciled after a repair closes?
Break/Fix FAQs
What is break/fix?
Break/fix for enterprise mobile devices is the process of diagnosing, repairing or replacing a rugged device that has failed in the field and returning a working, configured unit to the worker who depends on it. It spans the full path from fault report to closed asset record, not the bench repair alone.
What is a break/fix issue?
In mobility, a break/fix issue is a hardware or configuration fault that stops a device working, most commonly drop damage, screen breakage, battery failure, charging port wear, or scanner faults. These are physical failures driven by environment and duty cycle, not software errors.
Is break/fix the same as managed services?
No, break/fix is a single event and managed services is the ongoing system that determines how fast that event resolves. The two are not alternatives, and the quality of your Lifecycle Management sets your break/fix speed.
Does PiiComm offer break/fix support on its own?
Yes, PiiComm delivers break/fix as a function of Lifecycle Management, because fast resolution depends on identification, warranty verification, and spare configuration that a standalone repair service cannot provide.
How quickly can a broken device be replaced?
Replacement speed depends on whether a configured spare already exists, because a hot spare held charged, enrolled, and loaded with the current image ships as working equipment while an unconfigured spare has to be prepared first.
Who pays for a repair not covered by warranty?
The device owner does, because most rugged device warranties cover manufacturing defect rather than drop damage, which is the most common field failure. Verifying warranty status before repair determines which side of that line a given fault falls on.
What happens to devices that cannot be repaired?
They move into Secure Decommissioning, where data is sanitised, SIMs are destroyed, and units are directed to certified recycling or value recovery. This closes the asset record rather than leaving a data-bearing device untracked.
Is after-hours break/fix support available?
A Canadian-based support desk provides first-line coverage for mobile workers, so a fault is logged and triaged when it happens rather than the next business morning. The coverage in place is defined by the support agreement.
What does break/fix cost?
Break/fix cost falls into categories rather than a single figure, spanning the repair or replacement itself, internal coordination labour, lost productivity, freight, and capital held in spares. The repair invoice is usually the smallest of these.