TL;DR

Most IT vendor management practice grew up around software. Renewal dates, licence counts, seat true-ups, security questionnaires. Hardware and logistics vendors fail in a different shape entirely. They do not fail at renewal, they fail on a Tuesday when a laptop does not arrive in Lisbon and nobody can tell you where it is.

  • Software vendors fail at renewal. Hardware vendors fail mid-delivery.
  • Ask about coverage by country, not coverage in general.
  • The useful metric is time to a working device, not time to ship.
  • Find out who is the subcontractor, because there usually is one.
  • Exit matters more here: who holds your stock if you leave.
  • Review on incidents, not only on anniversaries.

Hardware vendors fail differently

A software vendor relationship is mostly stable and occasionally expensive. The risk concentrates at renewal, which is why the discipline is built around contract dates and entitlement counts.

A hardware and logistics vendor is the opposite. The contract is rarely the problem. The problem is operational and continuous, and it shows up as a device that did not arrive, a return that was never collected, or stock that nobody can locate.

Applying software vendor management to that relationship produces a tidy renewal calendar and no visibility into the thing that actually goes wrong.

What to watch instead

Delivery performance by country. Exception rate. Time from request to a person actually working. Recovery rate on returns. None of those appear on a renewal calendar.

Our note on implementing IT asset management covers the internal record-keeping those measures depend on.

Ask about coverage by country, not in general

Every vendor in this space says global. Nearly none means it uniformly.

The honest structure behind most global claims is a core set of markets served directly, a wider set served through partners, and a long tail served by whoever can be found at the time.

Question Weak answer Useful answer
Which countries do you cover Global, 100 plus A list, split by direct and partner
Who delivers in market X Our network A named partner and how long they have worked with you
What is lead time in market X Typically a few days A number, and what it was last quarter
What happens on a failed delivery We re-attempt Who contacts the employee, and when
Can you collect in market X Yes Yes or no per country, since recovery is harder than delivery

The last row separates vendors faster than any other question. Delivering into a country is comparatively easy. Collecting from a residential address, often from somebody who has just left the company, is much harder, and the list of countries where a vendor can do both is always shorter than the list where it can deliver.

Measure time to a working device

Vendors report what they control, which is dispatch. That is reasonable and it is not the number that matters to you.

The number that matters spans from the moment a request is raised to the moment a person is working on the device. It includes stock availability, procurement, configuration, shipping, customs where relevant, delivery attempts and enrolment.

Most of that sits with the vendor. The parts that do not are worth separating out so the measure is fair, but the whole figure is what your business experiences.

Track the exceptions separately

An average is misleading here because the distribution is not normal. Most deliveries are fine and a small number are badly wrong, and the average hides exactly the cases worth discussing.

Report the median, and report the count of deliveries that took more than double it. That second number is the agenda for the vendor review.

Our piece on IT operations metrics worth reporting covers how to present that without producing a dashboard nobody reads.

Find out who is actually doing the work

In logistics there is almost always a subcontractor, and that is not a problem in itself. Nobody owns couriers in forty countries.

It becomes a problem when nobody tells you, because it changes who is accountable when something fails and how quickly anybody can find out what happened.

Three questions settle it. Who physically handles the device in each market. How long that relationship has existed. What happens to your service if that partner is replaced.

The security angle

Subcontracting also matters for anything involving data. A device being collected and wiped passes through hands that are not your vendor’s, and the sanitisation standard applied is whatever the actual processor applies.

NIST Special Publication 800-88 on media sanitization sets out what sanitisation means in practice, and it is worth asking which level is applied and whether a certificate is produced per device. ISO/IEC 27001 on information security management is the usual frame for the wider information security question, and a vendor certified against it should be able to describe how subcontractors are managed under that scope.

The decision table

How much vendor management effort is warranted depends on exposure.

Situation Scale Setup Primary pain Recommended starting point
One country, one vendor Under 50 staff Local supplier Little Annual review, track exceptions only
Several countries, one vendor 50 to 200 Global claim Coverage uneven Performance split by country
Several vendors by region Series B+ Grown organically No comparable data One metric definition across all of them
Vendor is also the asset record Any Vendor portal is the source Exit risk Export monthly, keep your own copy
High churn workforce Any Constant joiners and leavers Recovery rate Measure returns, not just deliveries

Row four deserves attention. If the vendor’s portal is where your asset data lives, leaving that vendor means leaving your records. Export it on a schedule into something you control, regardless of how good the portal is.

The exit question nobody asks until late

With a software vendor, exit means exporting data and stopping payment. With a hardware vendor it can mean physical property sitting in a warehouse you do not control.

Three things to establish before signing, not during a transition.

  • Who owns stock held on your behalf, and how quickly it can be released or shipped onward.
  • What happens to devices in transit at the moment notice is given.
  • What the asset data export looks like, in what format, including serials and history.

The first is the one that causes real disruption, because a dispute about warehoused stock can freeze your ability to equip anybody while it is resolved.

Running two vendors during a transition

Overlapping for a period costs more and is usually right. A hard cutover on a logistics relationship means any in-flight shipment becomes somebody’s argument.

RemoAsset handles procurement and delivery, recovery and storage of your stock under one relationship, which reduces the number of handover points but makes the exit questions above more rather than less worth asking.

Review on incidents, not anniversaries

An annual review arrives eleven months after the thing worth discussing and is dominated by whatever happened in the last fortnight.

A better rhythm is a short quarterly conversation built from the exception list, plus an immediate review triggered by any incident above a defined threshold.

The threshold should be operational rather than financial. A single delivery that took five weeks is worth a conversation even though it cost very little, because the cause is probably still present.

What to bring to it

The exception list with dates and countries, the median time to working device, the recovery rate on returns, and any open stock discrepancies. Four items, and all four come from your own records rather than the vendor’s reporting.

ISO 55001 on asset management systems describes asset management systems in general terms and is a reasonable reference point for what a mature version of this looks like, though most teams need the four numbers long before they need a framework.

RemoAsset handles procurement, recovery and storage under one relationship across the markets you hire in. More on asset operations at PeopleOpsHQ.

Frequently asked questions

How is IT vendor management different for hardware vendors?

The failure mode moves. Software vendors concentrate risk at renewal, which is why the standard discipline is built around contract dates, licence counts and entitlement true-ups. Hardware and logistics vendors rarely fail at renewal and routinely fail mid-delivery, so the things worth watching are delivery performance by country, exception rate, time to a working device and recovery rate on returns.

What should we ask a hardware vendor about global coverage?

Ask for the country list split into markets served directly and markets served through partners, then ask specifically whether they can collect as well as deliver in each one. Nearly every vendor claims global coverage and almost none means it uniformly. Collection from a residential address, often from somebody who has already left, is significantly harder than delivery, so the list where both work is always shorter.

What metric should we hold an equipment vendor to?

Time from request to a person actually working on the device, not time to dispatch. Dispatch is what the vendor controls and reports, but the business experiences the whole span including stock availability, configuration, customs, delivery attempts and enrolment. Report the median rather than the mean, and separately report how many deliveries took more than double it, because the distribution is not normal and the average hides the cases worth discussing.

Does it matter if a vendor subcontracts delivery?

Subcontracting itself is normal, since nobody owns couriers in forty countries. What matters is knowing it, because it changes who is accountable when something fails and how fast anyone can establish what happened. Ask who physically handles devices in each market, how long that relationship has existed, and what happens to your service if the partner is replaced. It matters more where data is involved, since the sanitisation standard applied is whatever the actual processor applies.

What should we establish about vendor exit before signing?

Who owns stock held on your behalf and how quickly it can be released, what happens to devices in transit when notice is given, and what the asset data export contains including serials and history. The stock question causes the most disruption, because a dispute over warehoused equipment can freeze your ability to equip anybody while it is resolved. Plan to overlap two vendors through a transition rather than cutting over hard.

Should the vendor’s portal be our asset record?

It can be the working system and it should not be the only copy. If the portal is where your asset data lives, then leaving that vendor means leaving your records, which is a dependency worth avoiding regardless of how good the portal is. Export on a monthly schedule into something you control, with serial numbers and assignment history, so the exit conversation is about logistics rather than about data.

How often should we review an equipment vendor?

Quarterly and on incident, rather than annually. An annual review arrives eleven months after the thing worth discussing and is dominated by whatever happened in the previous fortnight. Trigger an immediate review on any operational incident above a defined threshold, set in operational rather than financial terms, since a delivery that took five weeks is worth discussing even though it cost very little.