Multi-Site Hardware Standardisation: Why Variety Costs
An estate spread across many sites accumulates variety, and the variety is what makes it expensive to run. The hardware cost of standardising is usually smaller than the operational cost of not doing it.
What variety actually costs
Five costs, and only the first is obvious.
Spares multiply. Five printer models means five printhead part numbers, five media specifications and five sets of spares — or, more commonly, no spares for most of them.
Configuration multiplies. Each model needs its own profile, its own templates and its own settings. Our scanner configuration guide covers why a single saved profile is what makes fleet deployment quick.
Documentation and training multiply. Staff moving between sites encounter different equipment, and written procedures either cover one variant or become unusably long.
Troubleshooting is slower. A problem on one model tells you nothing about the others, and nobody accumulates depth on any of them.
Firmware and compatibility testing multiply. Each platform needs validating separately against your systems.
The pattern: the hardware saving from buying whatever was cheapest per site is spent several times over on the other five.
Standardising does not mean buying current
The point that changes the economics.
If your estate runs a particular model, the question is not whether that model is current. It is whether adding more of it keeps everything uniform — and it does.
That is why buying a discontinued model refurbished frequently beats buying a current one new. The refurbished unit matches the configurations, templates, firmware, spares and staff knowledge you already have. The new one starts a second standard.
Our TCO guide covers where this reasoning holds, and our switch guide covers it for networking specifically, where the argument is strongest because switches last so long.
The limit: a platform whose parts market is thinning has a shorter practical life than its condition suggests. Ask about availability before committing to extending a standard. Our spares guide covers watching for it.
Standardise the things that repeat
Not everything needs to be identical, and forcing uniformity where sites genuinely differ produces workarounds.
Worth standardising: device models within a category, media and ribbon specifications, receipt and label templates, network equipment models, and the configuration profiles applied to each.
Not worth forcing: quantities, which follow site size; and anything driven by a genuine environmental difference — a site with chilled storage needs devices rated for it, and a site with high-bay racking needs extended-range optics that a small site does not.
The test is whether the difference is a real requirement or an accident of purchasing history. Most variety in a multi-site estate is the second.
Central spares beat per-site spares
Once the estate is uniform, this becomes possible and it is considerably cheaper.
Holding one spare of each type at every site means idle inventory multiplied by site count. Holding central stock with next-morning courier delivery covers everywhere for a fraction of that.
Two conditions make it work. The estate must be uniform enough that one spare type covers many sites — which is the payoff for standardising. And next-morning must be acceptable for that equipment; where a failure stops trading immediately, a local spare is still warranted.
The usual arrangement: local spares for the few things that stop work instantly, central stock for everything else. Keep local spares configured and charged rather than boxed — a spare needing setup is not a spare.
Roll out in waves
Standardising an existing estate happens over time rather than at once.
Pilot properly first. Two or three genuinely representative sites — including a busy one and an awkward one, not the two nearest head office — through a full trading period. Our rollout guide covers what a pilot surfaces.
Replace on failure and on refresh rather than replacing working equipment. Standardisation is reached by making every replacement the standard model, which costs nothing extra.
Accept a transition period. For a while you hold spares for both the old and new standard. That is a cost, and it is temporary.
Keep retired units as spares for the sites not yet converted — the cheapest known-compatible source available. Our decommissioning guide covers handling data first.
Document the standard
A standard that exists only in someone’s head is not a standard.
Record: the model for each category, the exact media and ribbon specifications including width, core size and winding direction, the configuration profile, the firmware level, and the template versions.
That document is what lets a site order correctly without asking, and what lets a replacement be configured before it reaches the operator. Our consumables guide covers the physical measurements worth recording.
Review it when models become unavailable, and update deliberately rather than letting each site solve the problem independently — which is how the variety accumulated in the first place.
Common questions
Why does hardware variety cost more than it saves?
Because spares, configuration profiles, templates, documentation, training and compatibility testing all multiply per model. The saving from buying whatever was cheapest per site is spent several times over on those.
Should standardising mean buying the current model?
Not necessarily. If your estate runs a particular model, adding more of it keeps configurations, templates, firmware, spares and staff knowledge uniform — so a discontinued model bought refurbished frequently beats a current one that starts a second standard.
Should every site have identical equipment?
No. Genuine environmental differences justify variation — chilled storage needs temperature-rated devices, high-bay racking needs extended-range optics. The test is whether a difference is a real requirement or an accident of purchasing history.
Central spares or one at every site?
Central for most things, once the estate is uniform enough that one spare type covers many sites. Keep local spares only for equipment whose failure stops trading immediately — and keep those configured and charged rather than boxed.
How do I standardise an estate that is already varied?
Pilot properly, then make every replacement and refresh the standard model rather than replacing working equipment. Accept a transition period holding spares for both, and keep retired units as spares for sites not yet converted.
Tell us what models are in your estate and we will advise on parts availability before you commit to extending a standard.
