The European Union's revised Product Liability Directive has a deadline that is easy to read past. Member states must transpose it into national law by 9 December 2026, and when they do, a regime built for defective goods in the 1980s will apply to something it was never written for: software. The change is not confined to large technology companies. It reaches small software vendors, manufacturers of connected devices with embedded firmware, and the integrators who assemble third-party components into systems sold under their own name. For those firms, the deadline is less a legal formality than a documentation and contract-review project with a fixed end date.
What now counts as a product
The core move is definitional. The original directive was built around tangible goods. The revised text extends the concept of a product to software, including embedded firmware, standalone applications and AI-enabled systems, along with digital manufacturing files and the digital services integrated into or interconnected with a product. Liability no longer stops at the casing a firm ships.
For smaller firms, the practical effect is that the boundary between a service and a product has largely gone. A subscription tool that updates itself, a diagnostic module bundled into a machine, a model that scores or classifies — all of these now sit inside a regime designed for physical goods.
The directive also treats a firm that substantially modifies a product as a manufacturer of that modification, which is a live question for anyone who pushes firmware updates or customises a third-party platform for a customer. An integrator that assembles components into a system placed on the market under its own name may be treated as the manufacturer of the whole, even where the defective element came from a supplier.
The burden of proof moves
Claimants still have to establish a defect, damage and a causal link. What changes is what happens when that is unreasonably difficult. Where technical or scientific complexity makes it excessively difficult for a claimant to prove defectiveness or causation, courts may presume one or the other. Presumptions may also follow where a product fails to meet applicable safety requirements, or where a defendant does not comply with an order to disclose evidence.
For a small vendor, that reframes the value of its own records. In a dispute turning on whether a defect existed at the time of placing on the market, the manufacturer's design documentation, test results, risk assessments and post-market monitoring are the evidence that rebuts the presumption. Firms that can show why a design decision was taken, what was tested and what changed after release are in a materially different position from firms that cannot. The directive does not require a small company to hold a legal department. It does reward the ones that can reconstruct a decision made three years earlier.
Disclosure turns documentation into an operating discipline
Courts will be able to order disclosure of relevant evidence, subject to proportionality and confidentiality protections. In practice that means version histories, bug reports, incident logs, release notes and the internal correspondence that explains them. A firm that cannot produce these may face an adverse presumption rather than a neutral outcome.
The preparation is unglamorous: a retention schedule that matches the product lifecycle rather than the tax year, a version control system that records which customers received which build, and a clear record of when a known issue was identified and what was done about it. For firms used to treating documentation as a by-product of engineering, this is the part that requires a change of habit.
Contracts and insurance were written for hardware
Most small firms' contractual architecture predates the new exposure. Supplier agreements typically carry indemnities and warranties scoped to physical goods; customer contracts often cap liability at the value of the licence fee. Those arrangements may not survive contact with a third-party claim, and in some jurisdictions consumer-facing exclusions are not enforceable at all.
The review has three parts. First, supplier terms: does an indemnity from a component supplier extend to software and to AI-enabled functionality, and is it backed by insurance? Second, customer terms: what is warranted, what is excluded, and does the limitation of liability hold up against a claim for personal injury or property damage? Third, insurance: many product liability policies were written around tangible products, and a small firm should establish whether software, embedded firmware and AI-enabled functionality are clearly covered, or whether they fall between product liability, professional indemnity and cyber cover. Ambiguity in a policy is a question to resolve before a claim, not after.
Why the timing matters
The new regime applies to products placed on the market after transposition. Products already in the field remain governed by the old rules. That is often read as breathing space. It is better understood as a cut-off: the design, testing and documentation decisions taken during 2026 will determine the exposure attached to everything shipped from December onwards.
The exposure window is long. The directive retains a long-stop limitation period, extended in defined cases where symptoms of an injury are slow to appear, and the window lengthens where the manufacturer retains control over the product — including the right to modify it or to supply updates. For a software vendor, that is the normal way of operating. A product that is updated for a decade is a product the manufacturer has stayed close to for a decade.
Conclusion
For most SMEs, the useful way to read the 9 December 2026 date is as the end of a preparation period rather than the start of a legal question. The firms that will find the transition least disruptive are those that can already show documented design decisions, testing records and update histories, and whose contracts and insurance match the exposure they now carry. The Global SME Awards category is a natural frame for the companies affected here: the exposure falls on the same businesses that supply, integrate and maintain the software embedded in everyday products.
