Hardware supply agreements: what UK buyers and suppliers need to settle

If you promise a customer a 48 hour replacement, but your own supplier only promises to inspect faults when stock is available, you have a hardware supply problem before the first unit ships.

That gap is where many UK hardware deals go wrong. A reseller agrees service levels to win the customer. An integrator assumes the manufacturer will keep a model available. A buyer expects a device to work with an existing estate because the sales discussion sounded confident. Then the batch arrives late, the firmware needs patching, or the product marking route is different from the one the team assumed.

A hardware supply agreement is the document that closes those gaps. For buyers, suppliers and resellers of physical hardware, it should do more than repeat price and quantity. It should allocate who is responsible for specifications, ordering, delivery, acceptance, risk, title, warranty handling, embedded software, safety escalation and exit. If the hardware is supplied alongside installation, support or other services, the better fit may be a combined Goods & Services Agreement. If the relationship covers several product lines or a wider purchasing arrangement, a broader Supply Agreement structure may make more sense.

Match the promise you make to the promise you receive

The first negotiation is not about legal wording. It is about whether your downstream promise to the customer is actually supported upstream.

If your customer contract says hardware will ship within five business days, be careful if your supplier terms call all lead times estimates. If you offer next day swap-out, check whether your supplier will provide advance replacements or only repair after return. If you tell customers a model will remain available for a rollout, confirm whether the supplier can substitute products, withdraw a line, or allocate stock elsewhere during shortages.

A sensible starting list is short:

• Which dates are firm and which are estimates.
• Which stock, repair or replacement commitments are backed by the manufacturer.
• Which assumptions depend on third party carriers, component availability or import timing.

If the supplier wants flexibility, the buyer can ask for something in return, such as notice of shortages, priority allocation, approved alternatives, cancellation rights, or a right to source elsewhere if milestones are missed. The point is not to eliminate risk. It is to stop one party silently carrying all of it.

Define the product properly before purchase orders start flying

Many hardware disputes are really specification disputes. The box delivered may be genuine, new and undamaged, but still not be the product the buyer thought it was getting.

The agreement should identify the hardware with enough precision that both sides can tell whether the order has been performed. That usually means model names, part numbers, hardware revisions, accessories, spares, power supplies, mounting kits and any region specific configuration. If packaging, labelling, kitting, serial number capture or branded presentation matters, say so.

Compatibility is the next pressure point. A supplier rarely wants to guarantee that a device will work in every customer environment. A buyer does not want to discover after deployment that a switch, terminal or sensor only works if other conditions are met. The contract should spell out where the line sits. Is the supplier warranting compatibility with named operating systems, networks or peripherals, or is the buyer taking responsibility for suitability in its environment?

Hardware increasingly arrives with more than hardware. There may be embedded firmware, management portals, mobile apps, drivers, APIs or update services. If so, the agreement should say whether those elements are included, licensed separately, or subject to third party terms. It should also state whether updates are required for the hardware to perform as described, whether security patches will be made available, and whether the supplier can discontinue software support while the hardware is still under warranty.

On ordering mechanics, avoid assuming that a purchase order by itself answers everything. The contract should explain:

• how forecasts are provided and whether they are binding or informational only
• when an order becomes accepted
• whether minimum order quantities or call-off commitments apply
• whether the supplier may substitute equivalent products and, if so, on what approval process

Decide what counts as delivery, acceptance and ownership

Delivery language sounds routine until a shipment is delayed, damaged or only partly complete. Then everyone starts asking when risk passed, who should claim against the carrier, and whether the buyer must still pay.

The agreement should separate four ideas that are often muddled together: delivery, risk, title and acceptance. Delivery answers where and how the goods must arrive. Risk answers who bears the loss if the goods are damaged or lost. Title answers who owns them. Acceptance records how the buyer inspects and signs off the goods. The agreement should explain how apparent defects are reported and what remedies remain if a problem is found later. Sign-off should not be presented as automatically ending every right to reject or leaving a warranty as the only route; the effect depends on the contract and applicable law, including rights that cannot be excluded.

The agreement should address each point separately: where delivery occurs, when the buyer takes responsibility for loss or damage, when ownership transfers, and how inspection or testing is recorded. If the parties want different milestones for those matters, the drafting should say so expressly and be checked against the law that applies to the deal.

For hardware, practical acceptance wording is often more valuable than abstract legal theory. Consider whether the buyer has a fixed period to inspect for shortages, transit damage and obvious defects. State how installation or continued use affects contractual sign-off, without treating that as a blanket waiver of rights, and give latent defects a clear reporting and remedy route.

Late delivery also needs commercial consequences. A buyer may want service credits, price adjustment, expedited shipping at the supplier's cost, or termination rights for repeated delays. A supplier may insist that dates are estimates and that delay caused by customer changes, site readiness or missing information should move the timetable. Both positions can be documented. What causes trouble is leaving them unstated.

Title and stock location become even more important where goods are stored before deployment. If stock sits in a warehouse, on consignment, or at a third party logistics provider, agree who bears shrinkage, theft and insurance risk, and who can count or reclaim stock if the relationship ends.

Build a fault and returns process that works after the sale

When hardware fails, the legal issue and the operational issue happen at the same time. The customer wants a working device, not a debate about the cause. Your agreement should therefore turn warranty language into a process.

That process should say how faults are reported, what information must be supplied, who diagnoses the issue, where goods are returned, who pays carriage, whether the supplier can repair before replacing, whether advance replacement units are available, and what happens if no fault is found. If a defect only appears at scale, for example across a batch or product line, the contract should also allow the parties to move beyond one-unit-at-a-time RMA handling.

Be careful about promising a commercial warranty that goes further than the law or further than your own supplier support. If you sell to consumers, a warranty sits alongside statutory rights; it does not remove them. Goods sold to consumers must still meet the relevant legal standards, and a warranty card or RMA policy cannot take those rights away. See the GOV.UK guidance on implied rights.

In business to business supply, there is more room to negotiate, but not unlimited freedom. Certain rights can be implied into contracts for goods, and terms seeking to vary or exclude them need to be valid and reasonable. That means a supplier should not assume that a broad disclaimer will always be effective, and a buyer should not assume that silence preserves every protection in the same way as a consumer sale.

Fault handling is also where liability usually bites. One defective batch can trigger engineer visits, customer service credits, removal and reinstall costs, or replacement purchases from another source. The agreement should address what losses each party bears, whether liability is capped by reference to fees, orders or another measure, and whether particular categories of loss are excluded where the law allows. There is no universal formula. The sensible position depends on the product, the margins, the supply-chain role of each party and the kind of damage a failure could realistically cause.

Do not forget firmware and software in this section. Sometimes the hardware is sound, but a firmware bug causes failure. The agreement should say whether bugs, security vulnerabilities and software support issues are handled under the hardware warranty, under a separate software licence, or under support terms with different remedies.

Write in the compliance and safety response, not just the sales promise

A hardware supply agreement can allocate responsibilities, but it does not itself satisfy the underlying product compliance and safety rules. Those rules still apply according to the product sector and the role your business plays in the chain, such as manufacturer, importer or distributor.

That matters because there is no single universal UKCA only rule for all hardware across the UK. The applicable conformity route depends on the product and where it is being placed on the market. For Great Britain, see the Great Britain conformity-marking guidance. Northern Ireland follows a different route; see the Northern Ireland conformity-marking guidance.

The contract should therefore require the right party to provide the right material for the product in question. Depending on the sector, that may include markings, declarations, technical documentation, instructions, safety information, batch or serial traceability details, importer details, and evidence that the product can lawfully be supplied in the relevant market. A buyer should not simply assume those documents will appear when needed. A supplier should not promise blanket compliance without checking the product category and its own role.

Some product-safety obligations continue after sale. The OPSS guidance for businesses concerns consumer products, including traceability, incident reporting and corrective action. The duties for a particular hardware line depend on its product category, whether it is supplied in Great Britain or Northern Ireland, and whether the business is the manufacturer, importer, distributor or seller. The agreement should support the applicable duties with practical cooperation terms. In particular, it helps to agree:

• what incident information must be escalated and how quickly
• which party can require a stop-sale, quarantine or field correction
• what traceability records must be kept so affected products can be identified
• who handles regulator contact, customer communications, returns and corrective action costs

Plan the exit while the relationship is still working

Termination clauses in hardware deals are often too short for the operational reality. Even if the legal right to end the contract is straightforward, the practical unwind rarely is.

Think about what should happen to accepted but undelivered orders, bespoke configured stock, deposits, consigned inventory, spare parts, tooling, serial number records, access to software portals, and outstanding warranty cases. If the buyer has customers relying on installed hardware, it may need continued access to updates, documentation or support for a transition period. If the supplier has ringfenced stock or ordered components against forecasts, it may want cancellation charges or a commitment that certain work in progress will still be purchased.

Termination for cause should also match the realities of supply. Repeated late delivery, repeated quality failures, non-payment, insolvency events, breach of compliance obligations, or failure to cooperate on a serious safety issue may each justify different remedies or cure periods. There is no benefit in copying a generic termination clause that ignores the way hardware relationships actually fail.

If you would like help drafting or reviewing terms for a hardware supply arrangement, you can contact Sprintlaw on 08081347754 or team@sprintlaw.co.uk.