One Equipment Vendor Globally, or One Per Region

TL;DR

• A single vendor gives you one contract and one register. Regional vendors give you better coverage and several sets of records that will not agree.
• The register is the thing that decides this. If you keep one you control, a split arrangement is workable. If you expect a vendor's system to be the source of truth, it is not.
• Global coverage lists count countries a courier reaches, not countries where stock sits. Every vendor's real list is far shorter.
• Nobody publishes a price, so a split arrangement cannot be benchmarked against a consolidated one except by quoting both.
• The hybrid is usually right: one primary vendor plus a specialist for the one or two markets they serve badly.
• Consolidating for its own sake, when one region is genuinely poorly served, trades a real problem for a tidier diagram.

The Tidy Diagram That Cost a Week

A 300-person company with people across Europe, North America and two Asian markets consolidated onto a single vendor. The case was sound on paper: one contract, one invoice, one register, one relationship to manage instead of four.

The vendor's coverage list included every country they operated in. What it did not say, and what nobody asked, was where stock physically sat. Europe and North America were served from real warehouses. The two Asian markets were served by a partner, from a hub several days away.

For eleven months this was invisible, because nothing failed in those markets. Then a laptop died in Singapore and the replacement took nine working days, during which a senior engineer worked on a personal machine. The same failure in Amsterdam would have been resolved the next morning.

Recommended Tools

Best tools for Device Management

B BambooHR HR management system L Lattice Performance management D Deel Global payroll & EOR

View all recommended tools

Nothing about the consolidation was wrong as a decision. The error was comparing vendors on a coverage list rather than on stock location, and discovering the difference through an incident rather than through a question that takes one email.

Why Companies End Up Split Without Deciding To

Very few companies choose a regional structure deliberately. Most arrive at one through a sequence of individually reasonable decisions, which is worth recognising because the fix depends on how you got there.

It usually starts with one awkward country. The main vendor cannot serve it well, somebody finds a local reseller, and a second arrangement exists. Nobody calls this a structural decision because it is one country and it works.

Then an acquisition arrives with its own vendor. Unwinding that during an integration is nobody's priority, so it continues, and now there are three.

Or a regional office hires somebody capable who sets up what they need locally, reasonably, because waiting for the central arrangement to cover them would have taken months.

None of those is a mistake in isolation. The problem is that nobody ever stood back and asked whether the resulting structure is the one they would choose, and so nobody built the one thing that makes it viable, which is a register spanning all of it.

So if you are reading this with three vendors you did not plan, the first move is not consolidation. It is producing a single list of what you own across all of them, which tells you whether the structure is actually a problem or merely untidy. Those are different conditions and only one needs fixing.

What Each Structure Actually Gives You

Read the last row carefully, because the two failure modes are not equivalent. A badly served country is visible once somebody is affected and fixable with a second vendor. A fleet nobody can see whole is invisible indefinitely and gets worse as it grows.

The Register Decides It

This is the whole decision compressed into one condition, and it is worth being blunt about.

A split arrangement works if, and only if, you maintain a single register you control. Not inside either vendor's system. A spreadsheet, a database, anything you own, covering every device regardless of which vendor supplied it.

If you have that, regional vendors are a perfectly sound structure. You get depth where you need it, the vendors do what they are good at, and you can still answer how many machines the company owns and where they are.

If you do not have that, and you expect one vendor's platform to be the source of truth, a split arrangement produces exactly what it sounds like: two or three partial pictures, none complete, diverging continuously. That is the state that ends with devices nobody can account for.

So the question is not really one vendor or several. It is whether you own your own register. If you do, the vendor count is an operational preference. If you do not, consolidation is the only thing keeping your records coherent, and it is a fragile way to achieve it because it ties your most durable asset to a supplier you might leave.

Five Questions That Settle It

Where do your people actually are, by headcount? Write the list. Teams routinely describe themselves as global on the strength of a handful of people outside the main markets, and that handful is a courier problem rather than a structural one.

Is any region genuinely badly served by your best single option? Ask every vendor which of your countries have local stock and which are partner-served. If the answer is clean across all your markets, consolidate. If one region is consistently partner-served, that is the candidate for a specialist.

Do you maintain your own register today? Honestly. Not whether you could, whether you do.

Who would manage three relationships? A split arrangement needs somebody to own it. At a company with one person doing this part-time, three vendors is a real burden rather than an abstraction.

And what does the fragmentation cost you commercially? Volume concentrated in one place buys something, even in a category where nobody publishes a rate. Splitting it across three vendors means three smaller customers, and that shows up in both price and attention.

A sixth question worth adding if you have grown through acquisition. How many of your current arrangements did anybody actually choose? Inherited vendors persist long past the point where they make sense, because unwinding one is always somebody's second priority, and a structure assembled by accident deserves examining on its merits rather than being defended as the status quo.

The Hybrid Almost Everybody Should Consider

The conversation gets framed as a binary and the right answer is usually neither pole.

One primary vendor for the bulk of your fleet, plus a specialist for the one or two markets they serve badly. You get a single register covering most devices, one main relationship, and real depth in the market that was going to be the problem.

The cost is one extra relationship and a register that has to span both, which brings you back to the condition above. It is the same condition, and it applies to any arrangement with more than one supplier.

When to add the specialist: a market with enough people that replacement speed matters, consistently partner-served by your primary, and far enough away that a hub shipment is measured in days rather than hours.

When not to: three people in a country, however awkward it is. That is a courier arrangement and a spare machine held locally, which costs a fraction of a second vendor relationship and solves the same problem.

The spare-machine answer deserves more credit than it usually gets. A single standard laptop sitting with a trusted person in a difficult market solves the replacement problem almost completely, for the price of one device and no contract at all. It only works if your fleet is standardised, which is a separate argument for standardising, and it fails if the spare quietly becomes somebody's second machine, so it needs recording in the register like anything else.

Running the Register Across Several Vendors

If you land on a split arrangement, this is the operational work that makes it viable, and it is less than people fear.

One file, one owner, one update cadence. Every device regardless of supplier, with a column naming which vendor manages it. Monthly is enough at most sizes, weekly if you are hiring heavily.

Reconcile against each vendor's own list on the same day. Pull all of them in one sitting rather than checking one vendor this month and another next, because discrepancies are only meaningful when the snapshots are from the same moment. Staggered checks produce differences that look like missing devices and are really just timing, which wastes an afternoon and teaches people to ignore the exercise.

Agree a single identifier. Serial number is the obvious one and it is the only field every vendor will hold. Internal asset tags are useful and no vendor will track them unless you ask, so if you use them, put them in your file rather than expecting anybody else to.

And define the statuses yourself. One vendor's in storage is another's awaiting redeployment, and a third may have no status for a machine with a leaver. Map each vendor's vocabulary onto yours once, write the mapping down, and the monthly reconciliation becomes mechanical rather than interpretive. That mapping is also the first thing a successor needs, since without it the file looks consistent and means different things in different rows.

So the recurring cost is perhaps two hours a month. That is the real price of a split arrangement, and it is worth knowing before you choose one because it is paid every month rather than at signature.

What the Volume Concentration Buys

Being fair to the consolidation argument, it is not only about tidiness, and the commercial half is usually understated.

Attention. In a category where every arrangement is scoped individually, being a vendor's meaningful customer rather than a small one affects how quickly a problem gets escalated and who picks up the phone. That is hard to price and easy to feel.

Rate. Nobody publishes, so this cannot be verified from outside, and it is reasonable to assume a vendor seeing your whole fleet quotes differently from one seeing a third of it.

And a single negotiation. Three contracts renewing on three dates means three conversations a year rather than one, each of which requires somebody to prepare, compare and decide.

But none of that outweighs a market where replacement takes nine days. The commercial advantages of consolidation are real and incremental; a badly served region is a specific recurring failure that affects named people. Weight them accordingly rather than treating the diagram as the objective.

The Options

RemoAsset, named below, is owned by the same people who publish HROpsLab. Its limitations are stated as plainly as everybody else's.

RemoAsset

Procurement, deployment, tracking and retrieval for distributed teams, with enrolment into your management system before dispatch.

On this question: relevant mainly through one of its limits. It is weaker for hardware it did not supply, which matters in a split arrangement because devices from your other vendor are exactly that. Also publishes no price and requires a demo, and is not a device management system.

Workwize

Hardware lifecycle with owned warehouses. Domain is now goworkwize.com; the older address no longer resolves, verified 14 October 2026.

On this question: owned warehousing is the clearest form of regional depth available, and it applies in the countries where the warehouses are rather than everywhere. Ask for the warehouse list rather than the coverage list. No published price.

GroWrk

Wide country list, each arrangement scoped individually.

On this question: the obvious candidate when breadth is the actual constraint, because a scoped model can accommodate an awkward spread that a tiered product declines quietly. No published figures.

Firstbase

Subscription model with retrieval and replacement included.

On this question: per-person pricing across a mixed geography is simple to administer, which has real value if the alternative is reconciling three different units. No published price.

allwhere

Consultative and closer to a managed service.

On this question: a managed service can absorb the coordination burden of a complex geography, which is what a split arrangement costs you in hours. No published figures.

Deel IT

Devices attached to an employment platform.

On this question: coverage follows wherever the employment relationship already exists, which can be a genuine advantage in markets where you employ through them and is no help at all where you do not. No published price.

The Comparison

The Decision Table

How to Test Coverage Before You Restructure

The whole decision rests on which markets each vendor genuinely serves, and that is knowable in one round of emails rather than discovered through an incident.

Send your country list, ranked by headcount, and ask each vendor to mark every row. Three options: local stock, partner-served, or ship-only. That exercise takes a vendor ten minutes and nobody volunteers it unprompted.

Then ask for a replacement working-day target per country, with a remedy if missed. Expect confidence on some markets and hedging on others. The hedging is honest and useful; identical confidence everywhere usually means nobody checked.

Ask about collection separately from delivery. Retrieval coverage is almost always narrower, because getting a device back from a private address across a border is harder than sending one out. A vendor can genuinely ship to a country and have no practical route for recovering the machine, which matters enormously when somebody leaves.

And ask what they would do about a market they serve badly. Honest answers exist and they are informative: hold a spare locally, use a regional reseller for that country, or accept a longer target and plan around it. A vendor insisting every market is equally served has either not read your list or is hoping you will not test it.

A fifth question if the stakes are high enough. Ask who physically handles the device in each country, by the name of the firm. It is entirely possible that two vendors you are comparing use the same local partner in your second-largest market, in which case the depth argument collapses for that country and the decision rests on everything else. Vendors answer this readily and almost nobody asks.

Four questions, one email, and the structural decision usually answers itself. The markets that justify a specialist become obvious once every vendor has classified them, and so do the ones where consolidation costs you nothing.

Re-Check This Annually

Whichever structure you pick, it decays, and the decay is invisible until it is not.

Vendors open and close warehouses as their own customer base shifts. A vendor holding stock in your second-largest market at signature may not two years later, and nobody writes to tell you. The first sign is a replacement taking a week where it used to take a day.

Your own geography moves too. A market with three people when you signed may have thirty now, which changes whether it justifies depth. The country list that drove the original decision is a snapshot of a company you no longer are.

And account contacts change constantly in this category, which matters more in a split arrangement because you are maintaining several relationships rather than one.

So put a fifteen-minute review in the calendar annually: re-ask the four coverage questions, re-produce the country list by headcount, and confirm who your contact is at each vendor. That is the whole maintenance burden, and it is the difference between noticing a deteriorating arrangement in month fourteen rather than month thirty.

What Getting This Wrong Costs

Consolidating badly costs you a market. One region served from a hub several days away produces exactly the failure in the opening of this article, and it stays invisible until somebody important is affected, at which point it becomes urgent and the contract has eleven months to run.

Splitting badly costs you the register, which is worse because it does not resolve. Two or three partial pictures of what you own, diverging continuously, is how a company reaches three hundred people unable to answer a question that should take ten seconds. And the fix is not a vendor change. It is a reconciliation exercise across several systems, which is a fortnight of somebody's life.

A third cost sits between the two and gets attributed to the wrong thing. In a split arrangement, nobody owns the whole picture, so refresh planning happens per vendor rather than per fleet. One region replaces machines on a three-year cycle and another on four, not because anybody decided that but because each vendor advised separately. The result is a capital plan nobody can explain and an estate that ages unevenly.

There is also a quieter commercial cost to fragmentation that nobody measures. Three vendors each seeing a third of your volume treat you as a smaller customer than one vendor seeing all of it, and in a category where nothing is published and everything is scoped, being a priority account is worth more than it would be elsewhere.

Ask it this way before restructuring anything. If somebody asked today how many devices the company owns and where they are, how long would the answer take, and would it be right?

Moving From Several Vendors to One

If the answer is consolidation, the move itself deserves the same care as any other migration, and it has one extra complication: you are doing it several times.

Consolidate one region at a time rather than all at once. Each move has in-flight shipments, open collections and stock sitting somewhere, and handling three sets of those simultaneously is how devices disappear. A quarter apart is comfortable.

Export each outgoing vendor's full register before giving them notice, with every status rather than only active assignments. Machines in repair, in storage and awaiting collection are the three categories exports drop by default and the three most likely to be lost.

Decide what happens to stock each vendor holds before notice rather than after. Ship it to the incoming vendor, bring it to an office, or dispose of it, and get a storage end date in writing with a rate if it overruns.

And overlap each region for a full cycle. Let everything already in flight complete under the outgoing vendor rather than transferring a live shipment between two logistics providers, which is precisely where things get lost.

Then reconcile after each region rather than at the end. Three smaller reconciliations are far easier than one large one, and a discrepancy found in the first region tells you what to watch for in the second.

Start with the region you understand best rather than the one causing the most trouble. The first migration is where you learn how the incoming vendor actually handles an inbound fleet, which fields survive an import and how long each step really takes. Learning that in your most complicated market means absorbing two unknowns at once, and the difficult region benefits from going second with a process you have already tested.

When You're Ready to Decide

Two things first, and neither requires talking to a vendor.

Produce the country list by headcount, including the single-person markets. Most of this decision resolves on that one page, because the markets that justify a specialist are usually obvious once the numbers are written down rather than discussed.

Then establish whether you maintain your own register. If yes, you are choosing between structures and the answer is whichever gives better coverage. If no, build it before changing anything, because every structure in this article depends on it and consolidation only hides the problem.

With both in hand, send the same specification to three or four vendors, ask each one which of your countries have local stock, and the shortlist resolves itself. The vendors who are strong where you need strength will say so, and the ones who are not will say they cover the country, which is a different sentence and now you know the difference.

One closing caution about the direction of travel. Consolidation is easier to propose than to reverse, because having moved three regions onto one vendor, moving one back out means another migration with another set of in-flight shipments. So if a market is genuinely borderline, keeping the specialist for another year costs you a relationship and an hour a month, while consolidating prematurely costs a migration now and possibly another one later.

The tidiest structure is rarely the one that serves people best, and the diagram is not the point. The point is that somebody in your hardest market gets a working laptop quickly, and that you can say how many you own.

Frequently Asked Questions

HROpsLab takes no vendor money and publishes no paid placements.