By [Author Name] · [Date] · [X] min read · [Table of Contents]
TL;DR
- Vendor consolidation means reducing the number of suppliers doing the same job, usually to cut administration and improve commercial terms.
- If you have two suppliers and both work, you don't need this, and the project will cost more attention than it returns.
- It does three things: fewer relationships to manage, one record instead of several, and more volume with whoever is left.
- Three shapes exist: consolidate to one global supplier, keep a primary with regional exceptions, or consolidate the record and keep the suppliers.
- Decide on coverage first and price second, because the discount is smaller than the gap a dropped supplier leaves.
- Done right, you can answer "who ships our laptops" with one name and no footnotes.
Four suppliers. One handles Europe, one handles the United States, one was brought in for a single office in Singapore and nobody can remember why, and one is a local reseller somebody's manager has used for years. Each sends a different invoice format, two of them have portals with their own logins, and the only place the full picture exists is a spreadsheet maintained by one person who is currently on holiday.
The pressure to fix this usually comes from outside the team that feels the pain. Finance wants fewer suppliers in the ledger, procurement wants negotiating weight, or an audit flags that nobody has reviewed these relationships in three years. Meanwhile the people actually running equipment are reasonably happy, because each of those four suppliers is good at the one thing it was brought in for. That mismatch is why consolidation projects stall.
Best tools for HR Operations
The real issue isn't how many suppliers you have. It's that you have four relationships and one record, and the record is the thing failing. Consolidation is one way to fix that and it's rarely the cheapest. Fixing the record directly is usually faster, less disruptive and about a tenth of the work, which is why the useful first question is whether the supplier count is the problem at all.
When You Don't Actually Need Vendor Consolidation
When two suppliers is genuinely fine. A primary that covers most of your markets and one specialist for a region it doesn't reach. That's not fragmentation, it's sensible coverage, and consolidating it means either dropping the region or forcing the primary to serve it badly. Two good suppliers beats one adequate one in almost every case I've looked at.
When the friction starts showing. The signal is administrative rather than operational. Three invoice formats, two portals, nobody sure which supplier has which devices, and a quarterly reconciliation that takes most of a day. Delivery still works. It's the paperwork around delivery that's eating somebody's week, and that's a genuine cost even though nothing is visibly broken.
When it becomes a liability. Two triggers. Somebody asks for a complete list of who holds your hardware and the answer requires four exports and a manual merge. Or a security review asks which subprocessors touch employee devices and you cannot produce the list confidently. At that point the supplier count has become an evidence problem rather than an efficiency one.
The edge case that breaks everything. One of the four quietly stops performing and nobody notices for a quarter, because no single person is watching all four. I've seen a supplier's service degrade for five months before it surfaced, and it surfaced through a hiring manager complaint rather than through any review. Four relationships with no owner is the real risk here, not four relationships as such.
What Teams Actually Need from Consolidation
> "Who do I call when something goes wrong?" > One name per country, written down, with an escalation path above them. > Most equipment incidents are resolved by knowing who to ask, and four suppliers means four answers and a delay while somebody works out which applies.
> "Can I see everything in one place?" > A single record of what exists and where, regardless of which supplier handled it. > This is the benefit people actually want from consolidation, and it's achievable without consolidating suppliers at all.
> "Are we paying four different prices for the same laptop?" > A comparison you can run, which means consistent device specifications across suppliers. > Usually you are, and usually the variance is smaller than expected, which is useful to know before building a business case on it.
> "Which supplier has our devices right now?" > Per-supplier custody, including anything sitting in a warehouse you've never visited. > Devices in a supplier's storage are the easiest population to lose, because they're nobody's day-to-day concern.
> "What happens to the stuff in their warehouse if we leave?" > A clause, a cost and a process, agreed before you give notice rather than after. > This is the part of a consolidation project that surprises people, and it can make a saving disappear entirely.
The Three Shapes of Consolidation
Consolidate to one global supplier. What it is: pick one vendor, move everything to it, close the others. When it's right: when one supplier genuinely covers all your markets and you have enough volume to matter to them. Also right when the administrative overhead has become the dominant cost, which happens sooner than people expect. When it fails: on the markets at the edge. Every vendor has countries it serves through partners, and those are the countries where your service level drops after consolidation. The failure is predictable and specific, and it always lands on the market that was previously handled by the specialist you just dropped.
Primary plus deliberate exceptions. What it is: one supplier handles the bulk, and named exceptions stay with specialists, documented as a decision rather than as an accident. When it's right: this is the honest answer for most companies with people in more than about eight countries. You get most of the administrative benefit and keep coverage where it's hard. When it fails: when the exception list is never reviewed. An exception justified in 2024 may be unnecessary now because the primary has expanded, and nobody checks, so the list only ever grows. Put a review date on it or it becomes the fragmentation you were trying to fix.
Consolidate the record, keep the suppliers. What it is: leave the supply arrangements alone and put one asset register above them, fed from all four. When it's right: when the pain is genuinely administrative and your suppliers each perform well. This is much faster than a supplier migration and it delivers the single most wanted benefit, which is one view of everything. When it fails: when the invoicing and commercial overhead is the real problem, since this does nothing about either. It also needs somebody to own the register, and a register fed from four sources by hand degrades quickly unless the feeds are automated.
How to Choose: Five Questions Before You Start
What is the administrative cost, in hours? Measure it rather than asserting it. Count the hours somebody spends per month on supplier invoices, portals, reconciliation and chasing, then multiply by twelve. That's the number your business case rests on, and it's frequently either much larger than anyone claimed or small enough that the project isn't worth running. Either answer saves you from a bad decision.
Which of your markets does each supplier actually serve directly? Build the grid. Your markets down the side, suppliers across the top, and in each cell write direct, partnered or not served. The pattern tells you immediately whether one supplier could cover you, and in most cases it shows two or three markets where no single vendor is strong. Those markets are the whole decision.
How much volume do you actually represent? Be realistic, because this determines whether consolidation improves your terms at all. A company buying 200 machines a year is not a volume customer to a large vendor, and consolidating three small accounts into one slightly less small account rarely moves pricing much. The administrative saving is real, the commercial saving often isn't, and conflating them produces a business case that fails to deliver.
What's in each supplier's warehouse? Ask now, in writing. Devices sitting in supplier storage are a real asset and a real liability, and extracting them during an exit is the single most common cause of consolidation projects running over. If one supplier is holding 40 machines, that's 40 devices to retrieve, inspect, re-enrol and redistribute, and that work belongs in the project plan rather than in a surprise.
Who will own the surviving relationship? Consolidation concentrates risk, which is the trade you're making. One supplier means one point of failure and a much greater need for somebody to actively manage it. Name that person before you start, and if the answer is the same overloaded person who currently manages four suppliers badly, consolidation will not fix the underlying problem and may make it worse.
The Arithmetic, With the Working Shown
Consolidation business cases are usually built on a discount nobody has confirmed and an administrative saving nobody has measured. Here's how to build one that survives contact with a finance review.
Take a worked example with every input stated. An example whose inputs are hidden is an advertisement rather than an argument, which is most of what passes for a consolidation business case. Say four suppliers, 240 devices a year, and an average device cost of $1,450, giving roughly $348,000 of hardware spend. Now add the three categories of saving separately rather than as one number.
Administrative saving. Suppose reconciliation, invoice handling and portal admin take 14 hours a month across the four. Consolidating to one might reduce that to 5 hours, saving 9 hours a month or 108 hours a year. Value that at whatever your loaded hourly cost is and you have a real figure, and crucially a figure that does not depend on any vendor agreeing to anything.
Commercial saving. This is the one to be sceptical about. A consolidated account might improve device pricing by a few per cent, so on $348,000 a 3 per cent improvement is around $10,400 a year. Worth having. But get it in writing before counting it, because the quoted improvement at the start of a consolidation discussion and the terms available at signature are frequently different numbers.
Transition cost. Almost always omitted and almost always substantial. Retrieving devices from the exiting suppliers' warehouses, re-enrolling them, migrating records, running two systems in parallel for a quarter, and the internal time to manage all of it. For a four-supplier consolidation I would budget a full quarter of somebody's part-time attention plus the physical costs, and that is a one-off charge against a recurring saving.
| Line | How to get the number | Typical size | Confidence |
|---|---|---|---|
| Administrative hours saved | Count the hours now, estimate after | Real and measurable | High |
| Device pricing improvement | Get it in writing before counting it | A few per cent at most | Low until signed |
| Fewer invoices and ledger entries | Ask finance what it costs them | Small but genuine | Medium |
| Device retrieval from exiting suppliers | Count what is in their warehouses | One-off, often large | Varies |
| Record migration and parallel running | A quarter of part-time attention | One-off, underestimated | Low |
| Coverage lost in edge markets | Name the markets, price the workaround | The real risk | Knowable, rarely assessed |
The last row decides it. If consolidation leaves you with a market where delivery goes from five days to three weeks, price that. Three weeks of delay on a new starter has a cost, even if it's hard to put in a spreadsheet, and the honest version of the business case names it rather than leaving it out because it's inconvenient.
The Markets Where One Supplier Never Works
This section exists because the pattern is consistent enough to plan around, and because consolidation decks tend to present global coverage as a solved problem.
Three categories of market reliably break single-supplier arrangements. The first is anywhere you have people and no registered entity, because the importer-of-record question has to be answered by somebody and not every supplier can be that somebody everywhere. The second is markets with complex import rules or long customs processes, where local presence matters more than platform quality. The third is small markets with one or two employees, which are not commercially interesting to a large supplier and therefore get whatever service the partner network provides.
So before you consolidate, list your markets in three buckets: where you have an entity, where you don't but your preferred supplier operates directly, and where you don't and they operate through a partner. That third bucket is your exception list, and it should stay an exception list rather than being optimistically folded into the main arrangement.
A practical note on how to test this rather than take an answer on trust. Pick the two hardest markets on your list and ask the candidate supplier to walk through one real delivery and one real collection in each, naming the party responsible at every step. The answers come back in one of two registers. Either you get a process with named parties and stated timeframes, or you get capability language, and the shift from "we do" to "we can support" is the tell. It costs you an hour and it's the most reliable signal available.
The Decision Table: Which Shape Fits You
| Situation | Scale / Size | Setup | Primary Pain | Recommended Starting Point |
|---|---|---|---|---|
| Two suppliers, both performing | Any | Any | None, honestly | Leave it alone |
| Several suppliers, paperwork is the pain | 100 to 500 people | Distributed | Admin hours and reconciliation | Consolidate the record, keep suppliers |
| Several suppliers, commercial pressure | 300+ people | Mostly offices | Finance wants fewer ledger entries | Primary plus named exceptions |
| One supplier covers all your markets | 50 to 300 people | Distributed in few countries | Four relationships, one owner | Consolidate to one |
| People in 10+ countries | 100 to 1,000 people | Fully distributed | No vendor covers everything | Primary plus a reviewed exception list |
| A supplier has been quietly failing | Any | Any | Nobody is watching the four | Fix ownership first, then consider |
| Devices sitting in supplier warehouses | Any | Distributed | Custody is unclear | Audit the warehouses before anything |
Most companies above about eight countries land on the primary-plus-exceptions row, and that is not a compromise. It's the correct answer to a coverage problem that no vendor has solved.
What the Market Looks Like, and What That Means for a Negotiation
Worth knowing before you open a consolidation discussion, because the information asymmetry in this category is unusual.
I read the pricing pages of the main equipment logistics vendors on 28 October 2026, and the result was uniform enough that it changes how you should plan the project rather than merely who you should shortlist. Workwize publishes no rate card. Firstbase publishes nothing. GroWrk publishes nothing, and leans on a cost estimator whose outputs are modelled rather than quoted. allwhere is consultation-only. Deel IT publishes no IT rate card. Esevel is quote-based across three named tiers.
RemoAsset is the exception in that group, publishing $1,499 a year for its Subscription tier, with procurement and retrieval stated across 80+ countries and a 60% reduction on retrieval charges at that tier. Disclosure: RemoAsset is our own product, so the limits belong in the same paragraph. It does no network discovery, so it won't find hardware you've lost track of. It does no software licence management. And only the Subscription tier publishes a figure, because the pay-as-you-go side is quoted.
The practical meaning is simple. You cannot shop this category quickly, and a consolidation project should budget four to six weeks just to get three vendors to produce numbers you can set side by side. It also means your own data is the strongest asset you bring to the table. A vendor quoting into a blank is guessing; a vendor quoting against your real country list, headcount per market and last two quarters of joiner and leaver counts has to be specific. So assemble that page before the first call, and send it to all three.
One more thing on negotiating position. Consolidating to one supplier reduces your optionality, and reduced optionality is worth something to the supplier. That's a legitimate thing to ask them to pay for, and the way to ask is in term length rather than in headline rate: a shorter initial term with a review point is usually easier to get than a bigger discount and is worth more to you if the coverage turns out to be patchier than promised.
Running the Exit Without Losing Devices
The commercial half of a consolidation project gets all the attention and the physical half causes all the problems. So plan the exit as a logistics exercise with dates, not as a contractual one.
Start with an inventory of what each exiting supplier physically holds. Not what your record says they hold: what they say they hold, in writing, with serial numbers. Those two lists will differ. And the difference is the first thing to resolve, because once the relationship is ending the supplier's motivation to help you reconcile drops sharply. Ask for it while you are still a customer in good standing and before you give notice.
Then split what they hold into three categories, because each needs a different decision. Devices in storage awaiting assignment can be shipped to the new supplier's warehouse or distributed directly to people who need them. Devices in transit have to be allowed to land before anything else happens, which sets your earliest possible cutover date. And devices out with employees are the ones to leave alone: do not try to collect and re-ship machines that are working fine just to put them under the new arrangement, because that is weeks of disruption to no operational benefit. Transfer the record, not the hardware.
That last point is worth emphasising because it is the most common unforced error. A consolidation does not require the fleet to move. It requires the responsibility for the fleet to move, which is a data exercise plus a set of agreements about who handles the next event for each device. The machines in people's hands can stay exactly where they are and simply be collected by the new supplier when their user eventually leaves.
Now set the sequence. Overlap, do not cut over. Run the new supplier for new joiners first, while the old suppliers continue handling anything already in flight and any collections already triggered. That gives you a period where both arrangements are live, which feels untidy and is much safer than a hard switch, because the first few transactions with a new supplier are when you find out what the contract did not say.
| Stage | What happens | Do not skip |
|---|---|---|
| Before notice | Written inventory of what each supplier holds, by serial | Reconciling their list against yours |
| Week 1 | New supplier takes all new joiners only | Confirming who handles in-flight collections |
| Weeks 2 to 4 | Storage stock moves or is distributed | Checking device condition on arrival |
| Weeks 2 to 8 | Old suppliers finish anything already triggered | A named end date per supplier |
| Week 6 | Record migration, including historical custody | Keeping the old exports somewhere findable |
| Weeks 8 to 12 | Old relationships close, final invoices settled | A final confirmation that nothing remains |
| Month 4 | Sample the new record for accuracy | Comparing against the pre-project error rate |
Two details that save money. Agree the final invoice basis before giving notice, because storage charges have a habit of continuing on devices nobody has asked them to move. And get a written confirmation from each exiting supplier that they hold nothing of yours, dated, at the end. That one email is the thing you will want in eighteen months if a device surfaces, and it costs nothing to ask for while the relationship is still cordial.
The Alternative Nobody Proposes: Fix Ownership and Change Nothing Else
Before committing to any of this, it is worth taking seriously the option that no consultant will suggest, because there is no project in it.
Most of the pain described at the top of this article comes from four relationships having no single owner, rather than from there being four of them. Nobody is watching all four, so a supplier's performance can slip for months. Nobody holds the full picture, so a complete device list needs a manual merge. Nobody reviews the arrangement. So an exception from two years ago is still an exception. Every one of those is an ownership failure and not a count failure.
So the cheap experiment is this. Give one person the whole supplier portfolio for a quarter, with an explicit remit: hold the full device list, review each supplier's performance monthly, and bring a recommendation at the end. Three months later you will either have a working arrangement with four suppliers and no project, or you will have a well-evidenced case for consolidation built by somebody who now understands all four relationships. Both outcomes are better than starting the project first.
I would run that experiment in almost every case. And the reason is a pattern rather than a principle. Consolidation projects that begin with a measured administrative cost and a per-market coverage grid tend to go well. Projects that begin with a general sense that four suppliers is too many tend to produce a single supplier, a coverage gap in two markets, and a saving that nobody can locate in the following year's numbers. The difference between those two is about three weeks of somebody actually looking.
One caveat, stated fairly. If the pressure is coming from finance or procurement for reasons of their own, such as reducing ledger entries or meeting a supplier-count target, then the ownership experiment will not satisfy them and you should not pretend it will. In that case the honest route is to agree the consolidation and spend your energy on the exception list, since that is where the operational quality is won or lost regardless of how many names end up on the supplier register.
What to Put in the New Contract
Consolidation concentrates everything into one agreement, which makes that agreement worth more attention than any of the four it replaces. Six clauses carry most of the value.
Per-market service levels rather than a global one. A single delivery window across eighty countries is a number that cannot be true, so it will be quietly treated as aspirational. Name your top six markets by headcount and get a stated window for each, with a different and longer window acknowledged for everywhere else. A vendor who will do that is telling you they understand their own operation, and a vendor who insists on one global figure is telling you the opposite.
The importer of record, per market. This is the clause that decides whether a shipment stalls. For every market where you have people and no registered entity, the agreement should name who acts as importer. If the answer is you, that is workable as long as you know it in advance and have the tax identifiers, and it is a serious problem if you discover it when a laptop is sitting in a bonded warehouse.
Retrieval terms, with the day-30 behaviour spelled out. Collection is easy in the first fortnight and hard afterwards, so the valuable part of the clause is what happens when a former employee stops responding. Who chases, how many times, over what period, and what the outcome is when it fails. A contract that covers collection and goes silent on non-response has covered the easy half.
Storage, with a unit and a rate. Devices between users have to live somewhere, and storage is the line item most often priced separately and least often asked about. Get the rate, the unit and the point at which it starts, because a free-storage-for-30-days arrangement behaves very differently from a per-device-per-month one once you have a quarter with more leavers than joiners.
Data export, including history. Ask what you can take out and in what format, and specifically whether custody history comes with it or only current assignments. This is the clause that protects you if this supplier turns out to be the wrong choice, and it is far easier to negotiate before signature than during an exit.
Notice, and what happens to the devices on exit. Short notice periods are worth more than discounts in a category where coverage claims are hard to verify in advance. Pair it with a written statement of who holds the hardware at termination, who ships it where and what that costs, which is the question that turns an exit from a negotiation into an administrative task.
How to Tell a Real Exception From a Habit
If you take the primary-plus-exceptions route, and most companies above eight countries should, the exception list is where the quality of the decision lives. The difficulty is that two very different things look identical on the list.
A real exception is a market where your primary vendor genuinely cannot perform to an acceptable standard, usually because of import complexity, an absence of local presence, or a partner arrangement that adds weeks. Those exceptions should persist, be documented with the reason, and be reviewed rather than removed.
A habit looks the same on paper. It is something else entirely, and it takes three forms: a supplier somebody has used for years, a relationship inherited from an acquisition, or a local reseller a regional manager prefers. None of those is illegitimate and none of them is a coverage fact. That means they will not survive a review and should not be filed alongside the ones that will.
Three questions separate them, and all three can be answered in an afternoon. First: has the primary vendor been asked to quote and perform in this market, with a specific case, within the last year? If not, the exception is untested and is a habit until proven otherwise. Second: what specifically goes wrong when the primary handles it, named as an outcome rather than as a concern? A real exception produces a specific failure like a three-week customs hold or no retrieval capability at all. Third: would you choose this supplier today if you were starting fresh? That question is unfair and useful. And the hesitation in the answer tells you most of what you need.
Then write the list properly, which takes about twenty minutes and is the part that gets skipped. One row per exception. The market, the supplier, the specific reason, the date it was agreed, the date it will next be reviewed, and the person who owns the review. An exception list without dates and owners is indistinguishable from the fragmentation it replaced, and in eighteen months nobody will remember which entries were decisions and which were accidents.
One last thing on reviews, because annual is the wrong cadence for this. Review the exception list whenever your primary vendor expands coverage, which they will announce, and whenever your headcount in an exception market crosses a threshold that makes that market commercially interesting to the primary. Both of those are events rather than dates. Catching them is worth more than a calendar reminder arriving in a quarter when nothing has changed.
The Cost of Consolidating Badly
The costs here are unusually predictable, which is the one good thing about them.
The first lands on an individual. A new starter in a market that used to be handled by the specialist you dropped now waits three weeks for a laptop. Their first impression of the company is a bad one and their manager's impression of your team is worse. And because it affects one person at a time it never generates a formal escalation, it just quietly erodes confidence in the process.
The second is the devices you forgot to retrieve. Every exiting supplier is holding something: machines in storage, machines in transit, machines awaiting repair. If the exit isn't planned as a physical project, those devices stay where they are and become somebody else's asset in practice. I've seen a company discover eleven laptops in a former supplier's warehouse fourteen months after the relationship ended, and the commercial conversation about getting them back was not a comfortable one.
The third is the record discontinuity, and it's the one with the longest tail. You move to a new supplier, their platform holds the record from that date forward, and the history from the old suppliers is now a set of exports in a folder. The current state is fine. The custody trail is broken at the migration date, which matters exactly when somebody asks about a device that changed hands before it. Insist on importing history rather than just current assignments, and if that's not possible, keep the old exports somewhere findable and note the date the discontinuity occurs.
So the diagnostic worth sitting with: are you consolidating suppliers, consolidating spend or consolidating the record? Only the third one is nearly always worth doing, and it's the one that needs the least disruption.
Two Things That Look Like Consolidation and Are Not
Worth naming, because both get presented as consolidation wins and neither one reduces the work.
The first is consolidating the invoice without consolidating the supplier. Some vendors will act as a reseller for another vendor's service, which means you receive one invoice while two companies still perform the work. Finance is happier and your operational position is unchanged, except that you now have a party in the middle when something goes wrong in a market. That can be a reasonable trade if the invoice overhead was genuinely the pain, and it is a poor trade if you believed you were reducing the number of organisations touching your hardware. Ask directly whether a market is served by the vendor or resold. Because the answer rarely appears in a proposal.
The second is subtler. It is consolidating onto a vendor whose coverage is itself a partner network. Every logistics vendor partners somewhere, which is fine and unavoidable, but a vendor that partners nearly everywhere is a coordination layer rather than an operator. Again, not automatically wrong: a good coordination layer with one contract and one escalation path may be exactly what you want in place of four relationships you manage yourself. The thing to avoid is paying for consolidation while keeping all the variability, which is what happens when the coordination layer is thin and every problem still routes to a different local party.
One question separates the two. It is the same question in both cases. In each of my markets, who physically does the work, and who do I call when it fails? If the answer to the second question is one party for every market, you have consolidated something real. If it is one party who will then find out for you, you have bought a layer, and you should price it as a layer rather than as a supplier reduction.
When You're Ready to Move Beyond Four Suppliers and a Spreadsheet
The signals are specific. Nobody owns all your supplier relationships, and a complete device list requires more than two exports plus a manual merge that somebody performs from memory. Reconciliation takes more than half a day a month. A supplier's performance has slipped and you found out from a complaint rather than a review. Any two of those and the current arrangement has stopped being deliberate.
Start with the grid and the hours. Markets down the side, suppliers across the top, direct or partnered or not served in each cell, and a measured count of administrative hours. Those two artefacts take an afternoon and they'll tell you which of the three shapes above you're actually choosing between, which is more than most consolidation projects know at their third steering meeting.
RemoAsset is a candidate for the primary role in a distributed fleet, with a published annual figure and the three limits named above. If your markets include two or three where no vendor is strong, keep the specialists for those and write the exception list down with a review date on it. That's not a failure of consolidation. It's what consolidation actually looks like when it's done honestly.
Frequently Asked Questions
What is vendor consolidation?
It's reducing the number of suppliers doing the same job. For equipment that means moving from several regional or specialist providers to one primary supplier, or else to a primary plus a short list of exceptions that somebody has written down and dated. Three or four becomes one, or one plus two. The goals are fewer relationships to manage, one record instead of several and better commercial terms, and those three arrive in descending order of reliability.
How much does vendor consolidation actually save?
Less than most business cases claim. And from a different place than expected. The administrative saving is real and measurable: count the hours spent now on invoices, portals and reconciliation. The commercial saving is usually a few per cent at best and should not be counted until a supplier has put it in writing. Transition costs are routinely omitted and frequently exceed the first year's saving.
Should we consolidate to one global equipment supplier?
Only if one supplier genuinely serves every market where you have people, which for companies above about eight countries is rare. The more common right answer is a primary supplier plus a documented exception list for the markets where no vendor is strong. Write the exception list with a review date. Because the thing that turns a sensible exception list into fragmentation is nobody ever revisiting it.
What happens to devices in a supplier's warehouse when we leave?
Whatever the contract says. And often the contract says nothing, which is why this question belongs in the exit clause before you sign rather than in the notice email. Ask who holds the devices, who pays to move them, where they go and how long it takes. Plan the retrieval as a physical project with a date, because devices left in a former supplier's storage have a way of staying there.
Can we consolidate the record without changing suppliers?
Yes, and this is the most underused option in the category. One asset register fed from all your suppliers delivers the single view that people actually want from consolidation, without a migration, a transition cost or a coverage risk. It needs an owner and ideally automated feeds. And it leaves the commercial fragmentation in place, so it suits teams whose pain is administrative rather than financial.
How long does an equipment vendor consolidation take?
Plan for two quarters. And expect the physical half to take longer than the commercial half. Getting comparable quotes from three vendors in a category where almost nobody publishes pricing takes four to six weeks on its own. Then the migration, the warehouse retrievals and a period of parallel running add a further quarter, and running two systems briefly is much safer than a hard cutover.
Does consolidating suppliers improve our security posture?
Indirectly, and only if you do the work. Fewer subprocessors is genuinely easier to document and review, which helps with customer questionnaires. But the improvement comes from having one data processing agreement and one evidence trail you actually keep current, not from the supplier count itself, and consolidating without tightening the evidence leaves you in the same position with fewer names on the list.
Fix the record first, and then decide whether the supplier count was ever the problem.
