TL;DR
- Laptop lifecycle management is the work between signing a purchase order and closing the asset record: sourcing, imaging, export, import, delivery, support, recovery, wiping and disposal.
- Most teams do not need a partner for it until the second country. One country and a cupboard is a solved problem.
- The part that surprises people is not shipping. It is import tax, which is charged on the freight as well as the goods in most places.
- Retrieval fails far more often than delivery, because delivery has a motivated recipient and retrieval has a former employee.
- There are four honest models: do it yourself, use your hiring partner, use a regional reseller, or use a specialist platform. Each fails somewhere specific.
- Pick on the shape of your estate, not on the vendor’s country count. A list of 80 countries tells you nothing about the three you hire in.
A company hires its eleventh engineer. The first ten were in one city, so the laptop question had one answer: somebody walked to the cupboard, took a machine off the shelf, ran the setup script, and handed it over. Total elapsed time, about forty minutes, most of it spent waiting for the operating system.
The eleventh engineer is in Manila. The same forty minutes becomes six weeks. Somebody buys a laptop from a retailer, ships it with a courier, and the parcel stops at customs because the paperwork describes it as a gift. Somebody else pays an import charge on a company card without knowing whether it was the right amount. The engineer starts work on a personal machine, which means the security policy is already broken on day one, and nobody writes that down anywhere.
The instinct is to treat this as a shipping problem. It is not. Shipping is the one part of it that a courier will do reliably for a published price. The real issue is that a laptop crossing a border stops being an object in transit and becomes a taxable import, a customs declaration, an asset on a register, a security boundary, and eventually something you have to get back from somebody who no longer works for you.
What laptop lifecycle management actually covers
The phrase gets used loosely, usually by somebody selling software. It is worth being precise, because the gap between what the term covers and what any one supplier does is where budgets go wrong.
A complete laptop lifecycle management brief has nine jobs in it. Sourcing the machine, which means deciding the specification and finding stock in the right country. Imaging and enrolment, which means the device arrives already under your management rather than needing a remote session on day one. Export from wherever it ships from. Import at the destination, which is the customs declaration, the duty and the tax. Delivery to a named person at an address that may be residential. Support while it is in service, including the machine that dies in month four. Recovery when the person leaves. Wiping, to a standard you can evidence. And disposal or redeployment, which decides whether the asset becomes a credit or a cost.
Almost nobody does all nine. A courier does one. A reseller does two or three. A hiring partner usually does none of them and will say so if you ask directly. Platforms that advertise the full set generally mean they coordinate the full set through local partners, which is a reasonable thing to do and a different thing from doing it.
The test worth running on any supplier is to ask which of the nine they perform themselves, which they subcontract, and which they do not touch. The answer is usually honest, and it is usually narrower than the homepage suggests.
When you do not need any of this
This matters more than the rest of the page, because most teams reading about laptop lifecycle management do not yet need to buy anything.
One country, under about thirty people
A cupboard, a spreadsheet and a named person who owns it will beat any platform. The overhead of a vendor relationship is real and the problem you are solving is not. The honest advice is to keep the spreadsheet accurate and revisit the question when the second country appears.
You hire in one country and occasionally send somebody abroad for a few months
That is a travel problem, not a distribution problem. The laptop goes with the person as accompanied baggage and comes home the same way. Most customs regimes treat travellers differently from freight, which is why the same machine costs nothing in a suitcase and attracts tax in a box.
Your people buy their own machines against a stipend
This is a legitimate model with a real cost attached, which is that you do not own the asset, cannot enforce the build, and have no mechanism to get anything back. Some companies accept that trade deliberately. The failure mode is accepting it by accident, discovering at the first security review that nobody knows what anybody is working on, and then trying to retrofit control onto machines people own.
Everyone is a contractor supplying their own tools
Then the equipment question is a commercial term in the contract rather than an operations problem. Be careful that the contract actually says so, because a lot of them are silent and the silence gets expensive at the point somebody leaves holding data.
The point at which this stops being true is specific and recognisable. It is the second country, or the first time somebody leaves and you cannot get the machine back, or the first security questionnaire from a customer that asks how you evidence disk encryption on devices you have never physically seen.
The five questions people ask at eleven at night
These are the questions that actually get typed into a search box, in roughly the order they arrive.
How long does it take?
Within a country where you hold stock, two to five working days. Cross-border into a market with a local supply chain, one to two weeks. Cross-border into a market without one, where the machine is imported specially, three to six weeks and sometimes longer. The variance is almost entirely customs, not freight. Freight is the predictable part.
Who pays the import tax?
Whoever the shipping terms say. This is the single most expensive detail in the whole process and it is decided by three letters on a commercial invoice. Delivered Duty Paid means the sender settles it before the parcel moves. Delivered at Place means the recipient is asked for money before the courier hands anything over. Sending a work laptop to a new starter and having a courier demand a payment from them at the door is a genuinely bad first week, and it happens constantly.
Can we just buy it locally?
Often, and it is usually the right answer when the market supports it. A machine bought inside the destination country has no import event, no customs risk and a warranty that a local service centre will honour. The constraints are specification consistency, which varies by market, and keyboard layout, which sounds trivial until a developer has the wrong one.
What happens when it breaks?
Ask before you buy, not after. A manufacturer warranty is frequently regional rather than global. A machine bought in one country and carried to another may be outside its service territory, which turns a two-day repair into a shipping exercise in both directions.
How do we get it back?
The question nobody asks at the start and everybody asks later. It deserves its own section, below.
What a day one ready laptop actually means
Most of the delay in getting somebody working is not the shipping. It is what has to happen after the box arrives, and almost all of that can be moved to before the box ships.
The standard worth holding is that the person opens the lid, connects to their own wifi, signs in with their company identity, and is working. No remote session with IT. No downloading a management agent. No being walked through a settings menu by somebody six time zones away who is doing it from memory.
Getting there means four things happen before despatch. The device is enrolled with your management tool at the point of purchase, so it is under policy the first time it connects rather than the first time somebody remembers. Disk encryption is on and the recovery key is escrowed somewhere you can find it, which is the difference between a locked-out employee being an inconvenience and being a lost machine. The applications the role actually needs are already installed, which requires somebody to have written down what each role needs. And the device is associated with the correct person in your register before it moves, not after it arrives.
That last one sounds like paperwork and is where most laptop lifecycle management actually fails, because it decays fastest and nothing downstream works without it. A machine that ships without being assigned is a machine that will be assigned from memory in three weeks, or not at all.
On specification, the useful discipline is fewer options, not better ones
Two or three standard builds covering most roles, with a documented exception route for the people who genuinely need something else, beats letting everybody choose. Standardising is not about saving money on the purchase, although it does. It is that every variant you allow multiplies the support surface, the spare parts you need to hold, and the number of different answers you have to give when something breaks in a market you have never visited.
The exception route matters as much as the standard. Accessibility requirements and genuine role requirements should not be queued behind somebody who wants a larger screen, and the most common design error is routing all three through one approval process.
Customs is the part that surprises people
Two details account for most of the shock, and neither is obvious.
The tax base usually includes the freight
Import tax in most regimes is charged on a value that is the goods plus insurance plus freight, not the goods alone. Ship a machine worth a thousand with a hundred of expedited courier, and the tax is assessed on eleven hundred. Paying for speed therefore raises the tax bill as well as the shipping bill, which is not how anybody budgets it. The arithmetic is small on one machine and material on fifty.
Duty and tax are different things and they behave differently
Laptops are covered by the World Trade Organization Information Technology Agreement, and the signatories to it generally apply no duty to portable computers regardless of where they were made. So the customs duty on a laptop is very often zero. People hear that and conclude the import is free. It is not. Value added tax or its local equivalent still applies, and that is the number that actually lands. Budgeting duty and forgetting tax gets you the wrong answer by the whole amount.
There are two further traps that catch people repeatedly. Low value thresholds, the level below which a shipment attracts no duty or tax, are usually tested on the goods value alone while the tax above that line is charged on the goods plus freight. Two different bases in one transaction. And the threshold being clear of duty and tax does not make it clear of charges, because several customs authorities apply a processing fee to low value consignments that would otherwise pay nothing.
Splitting an order into smaller parcels to stay under a threshold does not work. Customs authorities aggregate multiple consignments to the same recipient, and the practice is well enough known that it invites attention rather than avoiding it.
The machine that dies in month four
Delivery gets all the planning attention and in-service failure gets almost none, which is odd, because a laptop that stops working in a market where you have no presence is a harder problem than one that never arrived.
Three questions decide how bad it gets, and all three are cheaper to answer before you buy. Is the warranty valid where the person is? Manufacturer warranties are frequently regional, so a machine bought in one territory and used in another may sit outside its service area entirely. Is there a service centre within reach? A valid warranty in a country with no authorised repairer means shipping the machine out and back, which is three weeks during which somebody is not working. And what does the person use meanwhile?
That third question is the one that actually gets answered badly. The usual answer is a personal machine, which recreates the unmanaged device problem you solved on day one, except now it is invisible because nobody logs it. A buffer of spare machines held in or near the markets where you have real headcount is unglamorous and it is the thing that makes the other two questions survivable.
How large a buffer is a judgement rather than a formula, but the shape of it is that spares are insurance priced against downtime rather than stock priced against purchase. A team that cannot tolerate a week of lost work in a given market needs cover in that market, and a team that can does not.
The related decision is repair against replace. Out of warranty, in a market with no service centre, the shipping in both directions plus the parts frequently exceeds the residual value of a three year old machine. Having a stated threshold, a value below which you simply replace, removes a recurring argument and gets people working faster.
Retrieval is harder than delivery, and the reason is motivation
Delivery has a recipient who wants the parcel. They will answer the door, chase the courier, and rearrange their day. Retrieval has a former employee who has already moved on, possibly did not leave happily, and has no reason to spend a Tuesday morning finding a box.
That asymmetry is the whole problem, and it means retrieval has to be designed rather than requested. The things that measurably work are unglamorous. Send packaging rather than asking somebody to find a box. Book the collection yourself and tell the person a time rather than asking them to arrange one. Start on the last working day rather than after it, because the day somebody still has a company email address is the last day the request arrives from inside the company rather than from a stranger. And give a specific alternative, a drop-off point and a deadline, because a request with no deadline is a request that will be done later.
The recovery rate difference between a planned process and an emailed request is large, and it is the single highest return change most teams can make. It costs nothing except deciding who owns it.
The honest caveat is that some devices never come back. Plan a write-off path with an approval level attached, because a process that has no way to close an unrecoverable asset leaves the register permanently wrong, and a permanently wrong register is worse than a smaller accurate one.
Wiping, and what evidence actually looks like
Every supplier says they wipe devices. The question that separates them is what you receive afterwards, because a claim that a wipe happened is not evidence that it did.
Useful evidence names the specific device by serial number, states the method used, records the date and the operator, and confirms the outcome. A certificate that says a batch of devices was processed on a date tells an auditor nothing about the one machine they are asking about, and the one machine they are asking about is always the one that held something sensitive.
There is a second question most teams do not think to ask, which is what happens to a device that fails the wipe. Drives do fail, and a drive that cannot be verified as erased has to be physically destroyed rather than quietly redeployed. Ask what the exception path is and what you receive when it is used. A supplier who has a clear answer has done this before.
The modern complication is that full disk encryption changes the argument
On a machine where the disk was encrypted from first boot and the key is destroyed, the data is unreadable without any overwriting at all. That is a legitimate and widely accepted approach, and it is much faster. It depends entirely on the encryption having been on from the beginning, which is precisely why the enrolment discipline described above matters at the other end of the device’s life. A machine that spent its first three weeks unencrypted because it shipped unenrolled cannot rely on key destruction for the data written in those three weeks.
If customers send you security questionnaires, the wiping evidence is one of the items that comes up most often and is hardest to produce retrospectively. It is worth deciding what you need before you choose a supplier, rather than discovering the gap while filling in a form with a deadline.
The asset register, and the six fields that do the work
The register is referred to constantly and specified almost never. In practice most of its value comes from a small number of fields, and most of its failure comes from having too many.
Serial number, because it is the only identifier that survives a rebuild, a rename and a change of holder. Model and purchase date, which together give you the age and therefore the refresh decision. Current holder, which is the field that decays fastest and matters most. Location by country, because that is what determines your import history and your retrieval difficulty. Status, meaning in service, in stock, in transit, with a leaver, or written off. And the enrolment identifier linking the row to the same device in your management tool.
Six fields, maintained accurately, outperform thirty maintained approximately. The common failure is a register designed by somebody who wanted completeness, filled in enthusiastically for two months and abandoned, after which it is worse than nothing because people still half trust it.
The test that tells you whether yours is real is a reconciliation
Take twenty rows at random and confirm each one against the management tool and the named holder. If more than two are wrong, the register is decorative. Running that check quarterly on a sample is cheap and it is the only thing that reliably catches drift before it compounds.
The second test is the leaver replay. Take the last twenty people who left and ask what happened to each of their devices. The answers will divide into returned, still out, and unknown. The size of the unknown column is the honest measure of whether your process works, and it is usually larger than anybody expects the first time somebody counts it.
Four models, and where each one fails
Strip away the branding and there are four ways to do this. None is correct in general. Each is correct somewhere.
Do it yourself
You buy, you ship, you chase. Cheapest in cash and most expensive in attention. Works well in one or two countries where somebody competent owns it. Fails at the point that person goes on holiday, or at the fourth country, where the knowledge required stops being general and starts being local.
Use your hiring partner
If an employer of record or a staffing provider already employs the person, asking them to supply the laptop is a natural move. Sometimes they will. The failure is that this is usually a separate product with separate commercial terms rather than part of the employment service, and discovering that at the point of need is a bad time. The other failure is that it ties your hardware to your employment arrangement, so changing one disturbs the other.
Use a regional reseller
Strong where they operate, which is often very strong indeed: local stock, local warranty, local service, a human who answers the phone in the right time zone. Fails as a global answer, because you end up with four relationships, four invoicing arrangements, four asset exports and no single view of what you own.
Use a specialist platform
One relationship, one asset register, coverage across many markets, retrieval and wiping included. Fails on depth in any specific market compared with a good local reseller, and fails commercially for small estates, because the pricing models generally assume a committed volume. Several publish no per-device rate at all, which makes a small deployment impossible to model before you talk to somebody.
Disclosure: RemoAsset, which appears in the comparison below, is owned by the same people who publish this site. It is named here with its limitations stated, and its competitors are described on the same terms. HROpsLab takes no vendor money and sells no placements.
Platforms in this category include Workwize, GroWrk, allwhere, Esevel, Firstbase and RemoAsset, alongside the equipment arms of broader hiring platforms such as Deel. Coverage claims vary and are difficult to compare, partly because a country appearing on a list can mean a warehouse, a partner, or a willingness to arrange something. Ask which of the three it is for the specific markets you care about.
RemoAsset publishes a subscription that starts at 1,499 dollars a year and states coverage of 80 or more countries. Its own limitation, stated plainly, is that it publishes no per-device rate, so a team with six machines in two countries cannot model the cost from the website and has to ask. For an estate of that size a regional reseller is frequently the better answer, and a subscription entry point suits a committed estate rather than an occasional need.
How to choose: five questions that actually separate the options
How many countries, and are they the same countries next year?
One or two stable markets points at local resellers. Five or more, or a list that changes with each funding round, points at a platform, because the cost of opening a new market is where platforms earn their keep.
How many machines a year?
Under about twenty, the subscription models rarely pay for themselves and you are better served by a reseller and a disciplined spreadsheet. Over about a hundred, the manual approach stops scaling and the question becomes which platform rather than whether.
Do you need to evidence anything to anybody?
If customers ask how you prove a device was wiped, or an auditor wants an asset register that reconciles, that requirement will drive the decision more than price. Evidence is the thing hardest to retrofit, and the thing most teams discover they need after they have chosen on cost.
Who owns this internally?
If the answer is nobody, buying software will not fix it. The most common failure in laptop lifecycle management is not a bad vendor, it is an unowned process. A platform with no internal owner produces an expensive and equally inaccurate register.
What happens on the day somebody leaves in your hardest country?
Walk that specific case through with any supplier before signing. Not the easy market, the hard one. The answer to that question is the product.
The decision table
| Situation | Scale | Setup | Primary Pain | Recommended Starting Point |
|---|---|---|---|---|
| Single country, office or hybrid | Under 30 people | Cupboard and a spreadsheet | None yet | Keep the spreadsheet accurate. Buy nothing. |
| Second country just opened | 30 to 80 | Ad hoc courier shipments | Customs surprises and slow starts | Local reseller in the new market, correct shipping terms |
| Several markets, growing | 80 to 300 | Mixed, no single register | Nobody knows what is owned or where | Specialist platform, chosen on your actual markets |
| Hiring through an employer of record | Any | Employment handled, equipment unclear | Assumed the laptop was included | Confirm in writing whether equipment is in scope before the start date |
| Outsourced or offshore team | Any | Provider supplies the people | Unclear who owns the devices | Settle ownership in the contract, not after the first incident |
| High turnover, distributed | 100 plus | Delivery solved, recovery not | Devices never come back | Design retrieval first, including a write-off path |
| Audited or regulated | Any | Working but unevidenced | Cannot prove wiping or custody | Choose on evidence and certificates, not on price |
What getting this wrong actually costs
The visible cost is a late laptop, and that is the smallest part of it. A new starter idle for a week is a real number and an easy one to calculate, which is precisely why it gets quoted and the larger costs do not.
The first invisible cost is the security gap. Somebody who starts work on a personal machine because the company one has not arrived creates a period during which company data sits on an unmanaged device. That period is rarely documented, almost never remediated, and extremely awkward to describe honestly in a customer security questionnaire two years later.
The second is the register that drifts. Each unrecorded machine is individually trivial. Fifty of them is an asset register that nobody trusts, and an asset register nobody trusts gets abandoned, after which you are reconstructing ownership from expense claims and memory. The reconstruction costs far more than the discipline would have.
The third is the tax position taken by accident. Import charges paid on personal cards and reclaimed as expenses, shipments described loosely on customs paperwork, machines that entered a country without a clear record of who imported them. None of it is dramatic at the time. All of it is difficult to unwind later, and it tends to surface during diligence, when the cost of an unclear answer is at its highest.
None of those three costs appears on a laptop lifecycle management quote, which is exactly why the decision gets made on the price of shipping.
The question worth sitting with is not whether you can afford a better process. It is what your current one would look like written down and shown to somebody who had to rely on it.
Where to go next
This page is the general shape of laptop lifecycle management. The detail that matters is almost always country specific, because the rules, the supply and the practical workarounds change at every border.
The first country guide beneath this page covers the Philippines, which is one of the largest destinations for distributed hiring and one where the customs detail is genuinely worth knowing before the first shipment rather than after it.
For the systems side of this rather than the logistics side, our guide to device lifecycle management covers the asset register, the enrolment model and the tooling that sits underneath all of the above.
HROpsLab publishes independent comparison work across HR and IT tooling. We sell nothing, we take no vendor money, and we publish no paid placements. Where a vendor publishes no price, we say so rather than estimating, and where a product is our own we state that too.
Frequently asked questions
What is laptop lifecycle management?
It is the full set of work between deciding to buy a machine and closing its record at the end of life: sourcing the right specification in the right country, imaging and enrolling it before it ships, exporting and importing it, delivering it to a named person, supporting it in service, recovering it when the holder leaves, wiping it to an evidenced standard, and then redeploying or disposing of it. Most suppliers perform some of those nine jobs and coordinate the rest, so the useful question to ask any vendor is which ones they do themselves.
Do we need a laptop lifecycle management platform?
Probably not until the second country, or until the first time you cannot get a machine back from somebody who has left. A single country with fewer than about thirty people is well served by a cupboard, an accurate spreadsheet and a named owner, and adding a vendor relationship at that size usually costs more attention than it saves. The signals that the answer has changed are a second market, a failed recovery, or a customer asking you to evidence how devices are wiped.
Is there customs duty on importing a laptop?
Frequently not, because portable computers fall under the World Trade Organization Information Technology Agreement and signatory countries generally apply a zero duty rate to them whatever their origin. That is the detail people hear and then misread, because duty being zero does not mean the import is free. Value added tax or its local equivalent still applies and is usually the larger number, so a budget that accounts for duty and omits tax will be wrong by the entire amount that actually gets charged.
Why is the import tax higher than we calculated?
Almost always because the tax base includes the freight and the insurance, not just the value of the machine. A laptop worth a thousand shipped with a hundred of courier is typically assessed on eleven hundred, which means paying for faster shipping also increases the tax. The other common cause is a low value threshold being tested on the goods value alone while the tax above that line is charged on the fuller base, so a shipment that looked marginally exempt turns out not to be.
Should we ship laptops or buy them locally?
Buy locally wherever the market genuinely supports your specification, because a machine purchased inside the destination country has no import event, no customs risk and a warranty a local service centre will actually honour. The reasons to ship instead are specification consistency across a team, a market where the configuration you need is not stocked, and keyboard layout, which sounds minor until a developer receives the wrong one and quietly becomes less productive for a year.
Who should pay the import charges, us or the employee?
You should, and the mechanism is the shipping term on the commercial invoice rather than a reimbursement policy. Delivered Duty Paid means the sender settles duty and tax before the goods move, so nothing is asked of the recipient. Delivered at Place means a courier will ask your new starter for money at the door before handing over a laptop they did not order, which is a poor first week and an avoidable one, since the only difference is three letters agreed when the shipment is booked.
How do we get laptops back from people who have left?
By designing the recovery rather than requesting it, and by starting on the last working day rather than after it, while the person still has a company email address and some reason to respond. What measurably works is sending packaging instead of asking somebody to find a box, booking the collection yourself and telling them a time, offering a drop-off alternative, and attaching a deadline. Also plan a write-off path with an approval level, because some devices will never return and a register with no way to close them stays permanently wrong.
How many countries does a provider need to cover?
Only the ones you hire in, which is why a headline country count is close to useless as a selection criterion. A list of eighty markets tells you nothing about the three that matter to you, and a country appearing on it can mean a local warehouse, a partner arrangement or simply a willingness to try. Ask which of those three applies in each of your actual markets, and ask what happens on the day somebody leaves in the hardest one, because that answer is the real product.