Laptop Procurement for Distributed Teams: Buying Hardware Where You Have No Entity

TL;DR

• Laptop procurement for a distributed team is a delivery problem with a purchase attached. Choosing the machine is the easy part and almost never the thing that goes wrong.
• If everybody is in one country and you buy from one supplier, you do not need to think about this. You need a preferred specification and a lead time.
• Four routes exist: buy centrally and ship, buy locally in each country, let the employee buy and expense it, or use a platform that holds stock regionally. Each fails differently.
• Customs, import duty and warranty validity are the three things that turn a straightforward purchase into a three-week problem, and all three are decided by the route rather than by the vendor.
• Nobody in the platform market publishes a price. Hardware resellers publish, platforms do not, and that difference tells you what you are really buying.
• Measure time from accepted offer to a working machine, split by country. That single number justifies or kills every option on this page.

The Starter Who Worked From a Phone for Nine Days

A 150-person company hired a designer in Brazil. The offer was accepted on a Monday, the start date was three weeks out, and IT ordered a laptop from the supplier they always used, in the Netherlands. It shipped on the Thursday.

It reached Brazilian customs the following week and stopped. The company had not sent a commercial invoice with the right declared value, there was no local tax identification on the paperwork, and the courier wanted somebody in-country to act as importer of record. Nobody at the company could be that person. After a week of emails the device was released on payment of duty and handling that came to a little under half what the laptop had cost. The designer, meanwhile, had started. She spent nine days reading documents on her phone and borrowing her partner's computer for calls.

Nothing here was a procurement failure in the conventional sense. The right machine was bought, at a good price, from a reliable supplier, in reasonable time. The purchase was fine and the import was the product. For a company hiring across borders, procurement stops being about price per unit and becomes about whether a configured machine can lawfully and predictably reach a person in a particular country on a particular date.

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

This is what laptop procurement for distributed teams is supposed to solve.

When You Don't Actually Need to Change Anything

When the manual way is genuinely fine

Everybody in one country, one supplier, a known lead time, and a cupboard with a spare or two. At that shape procurement is a purchase order and the only improvement available is agreeing a specification so nobody debates it per hire. Platforms add cost and solve a problem you do not have.

When friction starts appearing

The signal is the second improvisation. A manager buys a laptop on a card because the normal route would take too long. Somebody ships a machine in their luggage. A new starter is told to buy their own and claim it back. Each of these is somebody routing around a process that did not fit, and two of them in a quarter is the process telling you something.

When it becomes a liability

Once improvised purchases become normal you have lost the register, the warranty position and the security baseline at the same time. Devices bought on cards are not in the asset system, not covered by a corporate warranty arrangement, and frequently not configured to any standard. That is three problems arriving as one, and it is usually discovered during an audit rather than at the time.

The edge case that forces it

The first hire in a country where you have no entity, no local supplier relationship and no tax registration. Everything that was implicit becomes explicit: who imports the device, who pays duty, whose name is on the invoice, and what happens to the warranty. Companies handle the first one badly, learn, and then handle the fourth one well. The question is how many bad ones you want first.

Five Questions People Ask at the Point of Hiring

"How long will it take to get them a laptop?" Domestically, days. Internationally, anywhere from three days to three weeks depending entirely on the route you choose.

"Who pays the import duty?" Somebody always does. Whether that is you, the courier on your behalf, or an unlucky employee is determined by paperwork you fill in before shipping.

"Will the warranty work there?" Only if the machine was bought under an arrangement valid in that country. Manufacturer warranties are frequently regional rather than global.

"Can the employee just buy one and expense it?" They can, and you should understand what you are giving up before deciding that it is the answer.

"What specification should we buy?" Less important than every question above, and the one most companies spend the most time on.

The Four Routes, and How Each One Fails

Buy centrally and ship

What it is. One supplier relationship, usually in your home market, with devices shipped out to wherever people are.

When it's right. Domestic hires and nearby countries with simple customs arrangements. Volume gives you a better unit price and a single warranty relationship.

When it fails. Crossing borders. You become an exporter, which means commercial invoices, declared values, duty, and in many countries a requirement for an importer of record you do not have. The laptop in the opening of this piece was bought through exactly this route and it was the right route for 90 per cent of that company's hires.

Buy locally in each country

What it is. A supplier in each market, buying and delivering domestically.

When it's right. Countries where you have an entity, a local card, and enough hires to justify the relationship. Delivery is fast, the warranty is valid, and there is no import at all.

When it fails. It needs a local payment method and somebody to manage the relationship, which is exactly what you do not have in a country where you employ one person. It also fragments your specification, because local suppliers stock different models, and within a year the fleet is inconsistent.

Let the employee buy and expense it

What it is. The person buys a machine and claims it back.

When it's right. As a deliberate fallback for markets you genuinely cannot reach, and for short contractor engagements. It is fast and it always works.

When it fails. Ownership. An expensed device looks very much like a payment to the employee unless you have written otherwise, the specification is whatever they chose, the device is not configured to any standard, and there is nothing to recover at the end. It also creates a tax question in some jurisdictions about whether the reimbursement is a benefit. Used once in an emergency it is sensible. Used as a policy it quietly converts your fleet into other people's property.

A platform holding regional stock

What it is. A provider that keeps hardware in warehouses near your people and ships domestically within each region.

When it's right. When you hire across several countries and the import problem is recurring rather than occasional. Shipping within a country avoids customs entirely, which is the actual value, and it is worth more than the unit price difference.

When it fails. Unit cost. You pay a margin over buying direct, and if your hiring is concentrated in one or two countries you are paying for flexibility you will not use. Coverage also varies far more than the marketing maps suggest, so the question is never whether a provider covers a country but whether they hold stock there.

Customs, Duty and the Importer of Record

Three terms cause most of the pain, and understanding them takes ten minutes and saves weeks.

Customs clearance is the process of a shipment being inspected and released into a country. It needs accurate paperwork: a commercial invoice showing what the item is and what it is worth, the correct commodity code, and the details of who is receiving it. Most delays are paperwork rather than inspection.

Import duty and tax are charged on the declared value, at rates set by the destination country, and somebody has to pay them before release. The choice that matters is whether you ship on a basis where the sender pays everything or one where the receiver is billed. Shipping on terms where your new employee receives a bill for several hundred pounds on their first week is a mistake you make exactly once.

Importer of record is the party legally responsible for the import. In many countries this must be an entity registered locally. If you have no entity there, you either use a provider who acts in that role, ship on terms that handle it, or you discover at the border that nobody can.

What to do:

• Ship on terms where the sender settles duty and tax, so no employee receives a bill.
• Confirm who acts as importer of record for each destination before the device leaves.
• Declare the real value. Understating it to reduce duty creates a worse problem than the duty.
• Check whether the manufacturer's warranty is valid in the destination country, because many are regional.
• Send the device to a residential address only after confirming the courier will deliver there without a business registration.

And ask any platform the specific question rather than the general one. Not "do you cover Brazil" but "do you hold stock in Brazil, or does this ship from somewhere else and clear customs". The answers are very different and only one of them is fast.

Measuring What You Actually Have Today

Before evaluating anything, produce the number the whole decision rests on. It takes about an hour.

Take the last 15 starters. For each, record the date the offer was accepted and the date they had a configured, working machine. Not the shipping date and not the arrival date. The day they could do their job.

Split the list by country and take the median of each group. Then note, for each case, which of the four routes was used and whether anybody had to improvise.

That last row is more common than it sounds, and it is a useful finding on its own: a company that cannot say how long it takes to equip a new hire does not yet know whether it has a problem worth spending money on.

Getting the Machine Configured Before It Reaches Them

Procurement delivers a laptop. Somebody still has to turn it into a company laptop, and where that happens decides whether your new starter has a working day one or a frustrating one.

Three arrangements are common, and they differ by weeks of elapsed time.

Configured before shipping. The provider or your IT team sets the machine up, enrolls it, installs what is needed, and ships it ready. The person opens the box and signs in. This is the best experience and it requires either in-house capacity or a provider who offers it, and it adds a step before dispatch rather than after.

Enrollment on first boot. The machine ships untouched from the manufacturer or reseller and configures itself the first time it connects, pulling its settings and applications from your management system. For Apple hardware this runs through Apple Business, the free platform that replaced Apple Business Manager, Apple Business Essentials and Apple Business Connect when those were retired in April 2026, and which now carries Apple's own built-in device management at no cost. Windows and Android have equivalents. It is the most scalable arrangement and depends on devices being bought through a route that can register them to your organisation, which is precisely why where you buy matters to how you deploy.

Configured by the person, with instructions. A document, a call, and somebody installing things themselves. It always works and it is the slowest, least consistent option, and the one that produces machines configured eight different ways.

So the point that connects this to procurement: automated enrollment generally requires that the device was purchased through the manufacturer or an enrolled reseller, so that it can be associated with your organisation before anybody opens it. A laptop bought on a card from a consumer retailer frequently cannot be registered this way, which means the improvised purchase does not only skip your asset register, it also skips your deployment process. That is the hidden cost of the card purchase, and it is larger than the price difference.

But do not confuse any of this with device management itself. Enrollment places a machine under management; keeping it compliant, pushing policy and enforcing encryption is an MDM's job and a separate product from anything in this article.

Setting a Specification You Can Actually Buy

This page has twice told you to agree a specification. Here is what that means in practice, because the version most companies write is a single model number and it survives about four months.

Define a floor per role, not a model. Three tiers covers nearly everybody: a standard machine for work that lives in a browser and documents, a higher tier for engineering, design and video, and an exception process for anything else. Write the floor as a capability, memory and storage and processor class, rather than as a product name.

Then check the floor is buyable in your markets. This is the step that gets skipped. A specification achievable in one country may be unavailable or absurdly priced in another, and a rigid standard produces either delays or quiet non-compliance. Ask whichever supplier or platform you use to confirm the tiers are stocked in each country you hire into.

Allow the operating system to be a role decision, not a company one. Standardising on a single platform is cheaper to support and is frequently resisted by exactly the people whose productivity you most need. Decide it deliberately rather than by whoever argued hardest.

Review the floor annually, and write down who owns it. Specifications drift upwards through individual exceptions until the exception is the standard. One named person and one annual review prevents that without any process overhead.

And keep the whole thing to one page. A specification document that runs to six pages is a document nobody consults, which means purchasing decisions get made on availability and habit, which is the situation the specification existed to prevent.

How to Choose: Five Questions Before You Talk to Any Vendor

Where are you hiring in the next twelve months? Not where you have hired. Procurement arrangements are slow to change and the plan matters more than the history. A provider strong in Western Europe is of no use if next year's hiring is in South America.

Which countries have you got an entity in? Those are the countries where local purchase is available and is almost always the best answer: fast, duty-free, warranty valid, no platform margin. Reserve the harder routes for the markets that need them.

What happened the last three times somebody improvised? Find the card purchases and the expensed laptops. Each one marks a place your process was slower than the business needed, and that is a better guide to what to fix than any feature list.

Who configures the machine? Procurement delivers a laptop; somebody still has to make it a company laptop. Decide whether that happens before shipping, through an enrollment process on first boot, or by someone walking the new starter through it. This is where the deployment half lives and it is often forgotten in a purchasing conversation.

What is the warranty position in each market? Ask specifically whether a fault in month 14 is handled in-country or requires shipping the device somewhere. For a distributed team that answer is worth more than a small discount on purchase price.

When to Trigger the Order

A small process point that causes a disproportionate share of late laptops: most companies order hardware when the start date is confirmed, and the start date is confirmed later than the offer is accepted.

Order on offer acceptance, not on contract return and not on the first day of the notice period. The gap between those moments is routinely two to three weeks, which is the entire international lead time, and it is spent waiting for an administrative step that has no bearing on whether the person is joining.

The objection is obvious and worth answering. Occasionally somebody does not start, and you have bought a machine. That happens, and the cost is a laptop that goes into stock and is issued to the next hire, which is a minor inefficiency. The alternative cost is a person spending their first fortnight unable to work, repeated across every international hire, which is far larger and far more frequent.

What to do:

• Trigger the order from offer acceptance, with the recruiter or HR system raising it.
• Ship to arrive 3 to 5 days before the start date, not on it, so a delay has slack.
• For markets with a history of customs delay, add a further 10 working days.
• Keep 2 or 3 machines in stock per major region to absorb the exceptions.
• Record the actual elapsed time each hire, so your lead-time assumptions stay honest.

So treat the buffer as deliberate rather than as waste. A small amount of stock held regionally is the cheapest insurance available against the nine-day phone-only first week, and it costs a fraction of what a platform margin does.

Six Options Worth Knowing

The split worth understanding before the list: hardware resellers sell you machines and publish prices, while lifecycle platforms sell you the delivery and do not. Every platform below was checked against its own pricing page on 6 and 7 October 2026 and none publishes a figure. Two describe a model without numbers, GroWrk naming a per-order option alongside a subscription tier and allwhere referring to pay-as-you-go and fixed rates.

RemoAsset

Disclosure: RemoAsset is owned by the same people who publish HROpsLab. It is listed here because it competes in this category, and it is described with the same detail and the same limitations as everything else on this page.

Best for: companies whose procurement problem is that hardware must reach people in countries where they have no entity, and must then be tracked and eventually recovered.

Why companies choose it: purchase, delivery, the asset record and the eventual return run from one place, so the device arrives with a known serial against a known person and the register is correct without anybody maintaining it. For teams where the same device will later need retrieving from another country, buying and recovering through one platform removes the handoff that usually loses devices.

Where it struggles: it publishes no price and requires a demo, so it cannot be compared on paper. The unit cost of hardware through any platform is higher than buying direct from a reseller, which is the trade you are making for delivery and the lifecycle. It is not an MDM, so configuration enforcement needs something else, and it is not a certified disposition vendor. Coverage should be checked market by market rather than assumed from a map.

Workwize

Best for: multi-region fleets where holding stock close to people is the binding constraint.

Why companies choose it: regional warehousing means domestic shipping in each market, which avoids customs rather than managing it. Strong European coverage.

Where it struggles: no published price, and the multi-region machinery is more than a company hiring in two or three countries needs.

Deel IT

Best for: companies already employing or contracting through Deel.

Why companies choose it: the hire signal and the equipment request sit in one system, and for a company already using Deel to employ people internationally the countries tend to line up.

Where it struggles: quote-based, and most compelling as an extension of an existing relationship rather than chosen on procurement merits alone.

Firstbase

Best for: companies issuing a full home setup rather than a laptop.

Why companies choose it: desks, chairs and peripherals ship alongside the computer, which is a genuine logistics saving if your policy covers them.

Where it struggles: no published price, and the breadth is only worth paying for if you really do issue furniture.

GroWrk

Best for: hiring into Latin America and parts of Asia, where the larger providers subcontract.

Why companies choose it: in-country presence in markets that are otherwise slow, which is exactly where the import problem is worst.

Where it struggles: publishes nothing. Its page names an a la carte per-order model and a subscription tier called Flex without attaching figures to either.

allwhere

Best for: United States-led companies with international staff and real configuration requirements.

Why companies choose it: depth in deployment rather than only shipping, so machines arrive set up rather than merely arriving.

Where it struggles: consultation-only pricing, so nothing compares before a call.

What Each One Published

Checked against each vendor's own page on 6 and 7 October 2026. The pattern is the point: the companies selling hardware publish prices, and the companies selling delivery do not, because delivery cost depends on country in ways a table cannot hold.

The Decision Table

Most companies need two rows at once: local purchase in the markets where they are established, and a platform for everywhere else. Running one route for all countries is the most common and most expensive simplification in this area.

What Getting This Wrong Costs

The visible cost is the duty bill and the courier's handling fee, and it is the least of it. The real cost is the nine days in the opening of this piece, repeated. A new starter without a working machine is a person who cannot do the job you hired them for, during the fortnight when their impression of the company is being formed. That cost appears on no invoice and is the largest number in this entire topic.

The second cost is the fleet you did not intend to have. Every improvised purchase adds a device that is outside the asset register, outside the warranty arrangement, outside the security baseline and frequently owned by somebody other than the company. None of those is noticed at the time, because each one solved an urgent problem. They are noticed two years later when somebody tries to produce a device schedule and finds that a third of the fleet entered through routes nobody tracked.

The third is the employee who paid. Shipping on terms where the recipient is billed for duty puts a new colleague in the position of paying several hundred pounds to receive their work equipment, and then expensing it. It is recoverable and it is a dreadful first week. Companies do this once.

So ask the diagnostic question directly. Is this a price problem, a speed problem, or a reach problem? A price problem is solved by consolidating suppliers and agreeing a specification. A speed problem is usually internal approvals rather than logistics. A reach problem, which is what most distributed teams actually have, is solved by holding stock closer to people and is the only one of the three worth paying a platform margin for.

When You're Ready to Move Beyond One Supplier and a Courier

The signals are concrete. International starters are waiting materially longer than domestic ones, and you have the medians to show it. Somebody has improvised a purchase in the last quarter. You are hiring into a country where you have no entity and no local payment method. Or an employee has been asked to pay duty on their own laptop.

When those are true, the question is not which platform is best but which holds stock where you are hiring, and that is a market-by-market answer rather than a vendor-level one. Ask for it specifically.

If the same devices will later need recovering from those countries, buying and retrieving through one platform removes the handoff where devices usually disappear. RemoAsset is built around that single loop, which is why it fits companies with recurring international hiring and offboarding, and why it is the wrong purchase for a company buying 40 machines a year in one market where a reseller will serve them better and more cheaply.

And wherever you have an entity and a local card, buy locally. It is faster, there is no import, the warranty is valid, and nobody takes a margin. The sophisticated answer is not always the right one.

Frequently Asked Questions

HROpsLab takes no vendor money and publishes no paid placements, which is why this page recommends buying locally wherever you can, which earns nobody anything.