Revised EU Product Liability: What Dutch Businesses Must Know (2026)

EU product liability Netherlands practitioners face a decisive period as the revised EU Product Liability Directive (Directive (EU) 2024/2853) reshapes how defective-product claims are litigated, proven and insured. The directive replaces the framework established by Directive 85/374/EEC, which dated back to 1985, and extends strict liability into territory that older rules never contemplated, software, digital services, connected devices and AI-enabled products. Member States are required to transpose the revised directive into national law by 9 December 2026, with its rules applying to products placed on the market or put into service after that date.

For Dutch manufacturers, importers, platform operators and insurers, the reform alters not only substantive liability but the evidentiary balance in court and the shape of the coverage that responds to a claim. This article maps those changes into a litigation-focused playbook, with practical steps for compliance, evidence preservation and insurance review.

Quick summary, what the revised PLD does (headline changes)

The revised PLD modernises the EU’s strict liability regime and broadens it in ways that will directly affect Dutch businesses. At a high level, the reform does the following:

• Expands the definition of “product”. Software, firmware, digital manufacturing files and AI systems are now expressly within scope, alongside tangible goods. A product is no longer limited to a physical object that leaves a factory.
• Extends strict liability to digital and AI-enabled products. Defective software and connected devices can give rise to no-fault liability in the same way as a defective kettle or car component.
• Widens the pool of potentially liable parties. Manufacturers, importers, own-branders, authorised representatives, fulfilment service providers and, in defined circumstances, online marketplaces may all be exposed.
• Modifies the burden of proof. The directive introduces disclosure powers and rebuttable presumptions designed to help claimants overcome the technical complexity of modern products.
• Addresses post-sale conduct. Software updates, patches, security maintenance and lifecycle monitoring are relevant to whether a product is defective and to when liability crystallises.
• Preserves joint and several liability. Where more than one party is responsible, a claimant can pursue any of them for the full loss, leaving contribution to be sorted out between the defendants.
• Adjusts limitation and long-stop rules. The regime retains limitation and long-stop periods but recognises that latent harm, particularly from substances and certain products, may surface long after a product is placed on the market.

The authoritative text of the revised directive is published on EUR-Lex, and the European Commission’s consumer policy materials explain the policy rationale. Dutch stakeholders should treat those as primary sources and watch the national transposition legislation, which will set the precise rules applied by Dutch courts.

What the revised PLD changes for manufacturers in the Netherlands

For manufacturers, the reform is less a cosmetic update than a recalibration of exposure. The combination of a wider product definition, strict liability for digital elements and easier routes to proof means that products previously thought to sit outside the no-fault regime may now be squarely within it. The practical obligations run across the whole product lifecycle, from design and documentation through to post-sale monitoring and software maintenance.

Who is a “producer” under the new PLD

The revised PLD casts the net of responsible parties more widely than its predecessor. A “producer” or “economic operator” is no longer confined to the entity that physically manufactured a finished good. Under the revised framework the category can capture:

• The manufacturer of the product or of a component, including software incorporated into or supplied with the product.
• Importers who place a product from outside the EU onto the Union market.
• Own-branders who put their name, trade mark or distinguishing feature on a product.
• Authorised representatives and fulfilment service providers where no EU-established manufacturer or importer can be identified.
• Online marketplaces and platform providers in defined circumstances, particularly where they present a product in a way that suggests they are the supplier or fail to identify a liable economic operator.

For Dutch businesses this matters because a claimant who cannot locate a manufacturer abroad can increasingly turn to the party closest to the domestic market. Importers and own-branders should assume they are in the frame and manage risk accordingly.

Duties and compliance actions manufacturers should take

Strict liability does not require a claimant to prove negligence, but it does not make defect inevitable either. The best defence to product defect litigation in the Netherlands is a disciplined compliance record that demonstrates the product met the safety the public was entitled to expect. Practical actions include:

• Safety-by-design. Build hazard analysis, cybersecurity resilience and fail-safe behaviour into the development process, and document the design choices and the standards applied.
• Documentation discipline. Maintain a complete, retrievable technical file covering specifications, risk assessments, test data, instructions and warnings. Under the new disclosure regime, this material may have to be produced in litigation, so it must be accurate and defensible.
• Software patch and update policies. Because defectiveness can be assessed against post-sale conduct, define clear policies for security patches, feature updates and end-of-support dates, and record when and why updates were issued.
• Incident logging and monitoring. Operate a lifecycle monitoring process that captures field reports, near-misses and failure data, feeding into a corrective-action loop. This is both a safety obligation and a litigation asset.
• Clear instructions and warnings. The adequacy of instructions and the foreseeability of misuse are relevant to the defect analysis, particularly for connected and AI-enabled products whose behaviour may not be intuitive to users.

The Netherlands Authority for Consumers and Markets (ACM) supervises product safety and recall obligations that sit alongside the PLD, in particular under the EU General Product Safety Regulation framework; manufacturers should align their compliance programmes with both the liability regime and the regulatory safety framework, as the two intersect at the moment a defect is discovered.

Draft defensive contract clauses and recall planning

Strict liability cannot be contracted away as against an injured consumer, but contractual engineering remains essential for allocating risk up and down the supply chain. Supplier and distribution agreements should include calibrated indemnities, data-access and cooperation clauses enabling the retrieval of technical evidence from component suppliers, warranties on conformity and recall-cost allocation mechanisms. A standing recall and incident-response plan, naming decision-makers, communication channels and insurer notification steps, turns a crisis into a managed process and limits the litigation fallout that follows a serious defect.

Implementation in the Netherlands, timeline, transposition and pending claims

The revised directive is EU legislation and does not apply directly in the way a regulation would. It requires transposition into Dutch law before it takes effect domestically, which makes the national legislative process the critical event for Dutch businesses to track.

Transposition mechanics

An EU directive sets the result that each member state must achieve while leaving the form and method of implementation to national authorities. The revised PLD must be transposed by 9 December 2026. In the Netherlands, transposition proceeds through a legislative bill that amends or supplements existing law, most relevantly the product liability provisions currently found in Book 6 of the Dutch Civil Code (Burgerlijk Wetboek). The bill passes through the responsible ministry, consultation, the Council of State (Raad van State) and parliament before publication in the national legislation database at wetten. overheid. nl. Until the Dutch transposition text is published, the precise domestic wording, including any national options the legislature exercises, remains provisional. Businesses should monitor government.

nl and official channels for the formal bill, and treat the published statute, not the directive alone, as the operative source once it is in force.

Effect on pending claims and limitation periods

One of the most practically important questions is temporal: which regime governs a product placed on the market before transposition, and what happens to claims already in progress? As a general matter, the revised rules apply to products placed on the market or put into service after the new regime takes effect, while products placed on the market under the old framework continue to be judged under the prior rules. This creates a transitional period in which practitioners must identify the correct placement date before assessing exposure.

Limitation is a related and often decisive issue. The PLD operates with both a limitation period, running from the point the injured person knew or should have known of the damage, the defect and the identity of the liable party, and a long-stop period measured from the moment the specific product was placed on the market, put into service or substantially modified. The revised directive provides for an extended long-stop in cases where symptoms of a personal injury are, according to medical evidence, slow to emerge. The interaction between these EU-derived periods and the limitation regime in the Dutch Civil Code must be worked through carefully, because a claim that is live under one measure may be time-barred under another.

For latent harm, a substance whose effects emerge over years, the long-stop takes on particular significance. Litigators should calendar both periods from the earliest defensible start date and preserve evidence well before any deadline bites.

Liability for software, connected devices and AI in the Netherlands

The most consequential change for the EU product liability Netherlands landscape is the explicit inclusion of software, connected devices and AI-enabled products within strict liability. Products that update themselves, learn from data or depend on cloud services do not fit neatly into a model built for static physical goods, and the revised PLD confronts that reality directly.

Defect standards for software and firmware

A product is defective when it does not provide the safety that a person is entitled to expect, assessed against all the circumstances. For software and firmware, those circumstances now expressly include the product’s capacity to continue to learn or acquire new features after deployment, the effect (or absence) of updates and upgrades, and reasonably foreseeable cybersecurity requirements. A device that was safe at launch can become defective if the manufacturer fails to supply a security update that was within its control to provide. Conversely, a defect introduced by a third party’s unauthorised modification may shift responsibility away from the original producer.

Dutch courts assessing a software defect will have to engage with technical realities, version histories, patch cadence, and whether a vulnerability was known and remediable, in a way that traditional product cases rarely required.

Causation and testing, forensics, reproducibility and expert evidence

Proving that a software or AI defect caused a specific harm is technically demanding. Faults may be intermittent, environment-dependent or triggered by inputs that are hard to recreate. For both claimants and defendants, the centre of gravity in product defect litigation in the Netherlands will increasingly be forensic and expert evidence. The priorities are:

• Reproducibility. Where a fault can be reliably reproduced under controlled conditions, causation becomes far more tractable. Where it cannot, the case may turn on presumptions and inference.
• Forensic preservation. Logs, telemetry, firmware images, configuration states and model versions must be captured early and preserved in a defensible chain of custody, because they are frequently overwritten.
• Agreed expert protocols. Parties benefit from agreeing, at an early stage, the methodology, test environment and data sets that experts will use, reducing the risk of duelling and irreconcilable expert reports.

Dutch courts apply national procedural law to how evidence is gathered and tested while looking to EU law for the interpretation of the substantive directive. That split makes early procedural planning essential: the forensic groundwork done in the first weeks after an incident often determines the outcome.

Allocation of liability for AI components and training data

AI-enabled products raise a distinctive allocation question. Liability for AI products in the Netherlands may involve a chain of actors: the manufacturer that integrated the system, the provider of the underlying model, and the party that supplied or curated the training data. Where a harmful output traces to flawed training data or a defective model rather than the integration, contribution and indemnity between these parties becomes the real battleground, even though the injured claimant can proceed against any of them under joint and several liability.

Contracts between integrators and model providers should anticipate this by addressing data provenance, model warranties, update responsibilities and indemnities, because the directive’s generosity to claimants does not resolve who ultimately bears the cost between commercial parties.

Burden of proof, evidence preservation and expert strategy

The revised PLD recalibrates the evidentiary balance that has long made product cases hard for claimants. Recognising that modern products are opaque and that relevant information sits almost entirely with the producer, the directive introduces disclosure obligations and rebuttable presumptions. The burden of proof under the PLD remains on the claimant to establish defect, damage and the causal link, but the path is eased where the claimant faces excessive difficulty, particularly with technical or scientific complexity, or where the defendant fails to disclose relevant evidence within its control.

Practical steps for plaintiffs

Claimants should move quickly and build the record deliberately. Key steps include:

• Early preservation letters. Put the producer and relevant economic operators on notice to preserve logs, firmware, design files and field data before they are overwritten or destroyed.
• Targeted disclosure requests. Use the directive’s disclosure mechanism to seek the specific technical material needed to show defect and causation, framing requests precisely enough to resist arguments of disproportionality.
• Documenting difficulty. Where the claimant faces genuine technical complexity, document it, because that difficulty can trigger the presumptions that ease the burden of proof.

Practical steps for defendants

Defendants should treat evidence management as a liability-reduction exercise long before litigation starts:

• Source code and build custody. Maintain versioned, timestamped records of code, builds and configurations so that the state of the product at the relevant time can be proven rather than reconstructed.
• Expert validation. Engage technical experts early to test the alleged defect, probe reproducibility and prepare a credible alternative-cause analysis.
• Disclosure discipline. Respond to legitimate disclosure requests in a measured, documented way; unjustified non-disclosure risks triggering an adverse presumption that the product was defective.

Sample evidence checklist for Dutch litigation

A working evidence file should capture: the exact product and version, its placement-on-market date, design and test documentation, instructions and warnings, update and patch history, field-failure and incident data, forensic logs and telemetry, communications about known issues, and the chain of custody for every item preserved.

Cross-border claims and enforcement, EU litigation tactics

Product supply chains and consumer markets rarely respect borders, so cross-border product liability in the Netherlands is a routine feature of the new landscape. A Dutch manufacturer may be sued in another member state, and a Dutch claimant may have a choice of forum. The EU framework on jurisdiction and the recognition and enforcement of judgments, principally the Brussels I Recast Regulation (Regulation (EU) No 1215/2012), governs much of this, while national procedural law fills the gaps. Practitioners should keep a short tactical checklist in mind:

• Jurisdiction analysis. Identify where the defendant is domiciled, where the harmful event occurred and where the damage was suffered, as these can open multiple competent fora.
• Forum strategy and lis pendens. Where parallel proceedings threaten, the first-seised rule can be decisive; moving promptly to the preferred forum may secure a procedural advantage.
• Choice of law. Determine the applicable substantive law early, the Rome II Regulation contains specific rules for product liability, since outcomes on limitation, defences and quantum can differ between member states even under a harmonised directive.
• Enforcement planning. Confirm that any judgment obtained will be recognisable and enforceable where the defendant holds assets, and factor that into the decision on where to litigate.

Because the directive harmonises the substantive standard but leaves procedure to each state, cross-border claims reward early strategic choices about forum, law and enforcement rather than reactive tactics once proceedings are under way.

Insurance implications, coverage, gaps and claims handling in the Netherlands

The reform’s impact on insurance is as significant as its impact on liability. Broader exposure to strict liability, especially for software and AI, tests whether existing policies respond, and reveals gaps that may not have mattered under the old regime.

Will standard product liability insurance cover revised PLD claims?

Whether standard product liability insurance in the Netherlands responds to a revised-PLD claim depends on the policy wording, and many wordings were drafted for a world of tangible products. Common friction points include definitions of “product” that may not clearly capture standalone software or digital services, exclusions for pure financial loss, cyber-related exclusions that could bite where a defect is a security vulnerability, and the treatment of recall and pure economic loss. A policy may cover the bodily injury and property damage limbs of a claim while leaving data-related or purely digital losses unaddressed.

The practical effect is likely to be a wave of wording reviews and a sharper underwriting focus on software and AI risk, with insurers clarifying definitions and pricing the expanded exposure. Policyholders should not assume continuity of cover simply because they have always carried product liability insurance.

Practical steps for policyholders and insurers

Both sides of the insurance relationship should act before a claim materialises:

• Map exposure to wording. Policyholders should audit their product portfolio against policy definitions and exclusions, identifying where software, firmware or AI elements may fall outside cover.
• Clarify triggers and notification. Confirm whether the policy is written on a claims-made or occurrence basis and ensure notification procedures are understood, because late or defective notice can forfeit cover.
• Address recall and mitigation. Check whether recall costs, corrective updates and crisis management are insured, as these are often where the real spend lies.
• Coordinate subrogation and contribution. Where multiple producers and insurers are involved, early coordination on subrogation and contribution preserves recovery rights and avoids value-destroying disputes between insurers.
• Underwriting and reinsurance review. Insurers should reassess accumulation risk from widely distributed software defects, a single flawed update can trigger many simultaneous claims, and ensure reinsurance arrangements reflect that correlated exposure.

Litigation playbook, plaintiff and defendant timelines and sample strategy

A disciplined timeline distinguishes a controlled case from a reactive one. On the claimant side, the sequence typically runs: incident and preservation notice, forensic capture, formulation of the defect and causation theory, disclosure requests, exchange of expert evidence, and then the choice between settlement and trial once the evidentiary picture is clear. On the defendant side, the priorities are immediate evidence lockdown, internal technical investigation, early expert engagement to test the alleged defect and alternative causes, a measured disclosure response, and a realistic exposure assessment to inform settlement strategy.

Pleadings in a product defect case should set out the specific product and version, the precise respect in which it failed to provide the expected safety, the damage and the causal link, and, for defendants, the applicable defences, including the state-of-the-art position where available and any third-party modification. Preservation and expert-exchange milestones should be fixed early; in software and AI cases, the party that controls the forensic record and secures credible, reproducible expert analysis usually controls the settlement dynamics. Settlement versus trial should be evaluated continuously against the strength of the causation evidence, the exposure under joint and several liability, and the availability of insurance to fund a resolution.

Comparison table, old PLD vs revised PLD (key changes)

Conclusion, immediate action checklist for Dutch businesses

The EU product liability Netherlands regime is shifting decisively ahead of the December 2026 transposition deadline, and preparation now will reduce both exposure and litigation cost later. The following eight steps give Dutch businesses a concrete starting point:

1. Review product liability insurance wordings against the expanded scope, focusing on software, AI and recall cover.
2. Map the product portfolio to identify items with digital, connected or AI elements now within strict liability.
3. Update supplier and distribution contracts with indemnities, data-access clauses and recall-cost allocation.
4. Strengthen technical documentation and version control so the state of any product can be proven in court.
5. Formalise software patch, update and end-of-support policies, and record their implementation.
6. Build an incident-logging and lifecycle-monitoring process feeding corrective action.
7. Prepare a recall and incident-response plan with named decision-makers and insurer notification steps.
8. Engage litigation and insurance advisers early, and track the Dutch transposition legislation as it is published.

Sources

1. EUR-Lex, EU legal texts and consolidated acts
2. European Commission, Consumer Policy and Product Liability
3. Government of the Netherlands
4. Wetten.overheid.nl, Dutch legislation database
5. Rechtspraak.nl, Dutch judiciary
6. Netherlands Authority for Consumers and Markets (ACM)
7. Nederlandse Orde van Advocaten (Dutch Bar)