Should Your IT Team Run a Warehouse?
Every company above a certain size runs a device warehouse. Most just haven't admitted it — which is why it's a closet, staffed by nobody, run without receiving, inventory, or custody. The question isn't whether to run the warehouse. It's who should.
Somewhere in your office is a room that isn't on any org chart.
It holds new laptops still in boxes, returned laptops that may or may not work, a shelf of chargers and docks, several machines awaiting "wiping at some point," and at least one device nobody can identify. IT people call it the closet, the cage, the back room. Here's what it actually is: a warehouse — with inbound freight, stored inventory, fulfillment, and returns — being operated with none of the disciplines warehousing exists to provide.
No receiving process, so things enter unrecorded. No serialized inventory, so counts are beliefs. No custody, so "who had access" is "whoever had the key." No replenishment logic, so stock-outs are discovered by the new hire who needed the laptop. This isn't an IT failure. It's what happens when a company runs a logistics operation without deciding to — and every company above a modest headcount is running one, admitted or not. Devices arrive, get stored, get configured, get shipped, come back, and get retired. That is a warehouse workload. The only open question is who operates it, and to what standard.
Why IT teams are the wrong crew for it — through no fault of their own
Warehousing and IT are different professions that happen to touch the same objects.
Device logistics is receiving discipline, bin management, pick accuracy, kitting, pack-out, carrier management, returns processing, cycle counts, custody documentation. It rewards process repetition and physical rigor. IT work is systems, identity, security, applications, and judgment under ambiguity. It rewards exactly the opposite temperament. Handing the warehouse to the IT team means your most expensive technical staff spend hours unboxing, labeling, taping, and standing in line at a shipping counter — work they're overqualified for, undertrained in, and guaranteed to deprioritize the moment a real IT problem appears. Which is daily.
So the closet gets run in the gaps. And logistics run in the gaps produces exactly what you'd predict: shrinkage nobody can quantify, "spares" that turn out to be broken, ship dates that slip against start dates, wipes that happen eventually, and an asset register that diverges a little further from reality every month. The people aren't failing. The org design is — it assigned a logistics operation to a team hired for something else and gave it no standards, no space, and no headcount.
The honest build-vs-buy question
Once you name the warehouse, the question becomes a normal operations decision: build the function properly, or buy it as a service.
Building it properly means paying for it properly. Dedicated space fit for storing device inventory securely — access-controlled, organized, sized for refresh surges, not a closet. At least one person for whom logistics is the job, not a side duty — receiving, inventory, kitting, shipping, returns, five days a week, with coverage for the days they're out. Tooling: serialized asset tracking that's actually maintained, label printing, carrier accounts, a wipe-and-certify process that stands up to an auditor. And management attention to keep all of it honest. For a large enterprise moving devices every day, that investment can clear its bar. For a mid-market company, the arithmetic is brutal: it's a full operational function — space, headcount, tooling, and process — acquired to serve one company's device flow, sitting underutilized between surges, and dependent on the one person who runs it never leaving.
Buying it means plugging your fleet into an operation that already exists — a real facility with receiving, serialized inventory, imaging benches, kitting, shipping, returns, and certified destruction, run by people whose entire profession this is, amortized across many fleets instead of carried by one. The economics come from the sharing; the quality comes from the specialization. You pay for device flow, not for standing capacity.
The line that makes buying safe: custody, not ownership
The historic objection to outsourcing anything near the fleet is dependency — the fear, learned from a generation of MSP contracts, that the vendor ends up owning your environment and the exit costs a fortune.
Device logistics done right is built on the opposite stance: your device, your paper, our custody. The assets are yours and stay on your books. The records — serials, assignments, movement history, wipe certificates — are yours, produced continuously, portable on demand. What the operator holds is custody and execution: the physical work, done to standard, documented as it happens. If you ever leave, you leave with your fleet and your complete history, and the operator has to win the renewal on performance, because the exit was engineered to be cheap.
That's the test to apply to anyone offering to run your device operation — including us. Who owns the assets? Who holds the records? What, exactly, does leaving cost? An operator with good answers is selling you a function. An operator with vague ones is selling you a dependency with shelves.
The warehouse exists either way. Name it, and then decide — deliberately — who should run it.