How Swiss Manufacturers Should Prepare for the EU Product Liability Directive 2026

Product liability in Switzerland is entering a new era of complexity. The revised EU Product Liability Directive (Directive (EU) 2024/2853) must be transposed into national law by every EU Member State by 9 December 2026, and its reach extends well beyond the borders of the European Union. For Swiss manufacturers, software developers and exporters that place products on the EU market, the Directive introduces strict liability for software, including stand-alone software, clarifies that a failure to provide necessary security or functional updates can constitute a product defect, and shifts important evidentiary burdens toward producers.

Even though Switzerland is not itself required to transpose EU directives, any Swiss business that sells, distributes or licenses products to customers within the EU must understand, plan for and comply with these changes now.

This guide provides a practical compliance playbook: the legal changes that matter, how they apply to Swiss exporters, the operational steps to implement before the deadline, the contract clauses to draft and the insurance reviews to initiate. Two immediate decisions face every affected Swiss manufacturer: (1) whether to adapt internal processes, contracts and product-lifecycle management to meet the new EU standard, or (2) whether to restrict or restructure EU market placement entirely. The sections below equip in-house counsel, product managers, CE/QA directors and compliance officers with the information they need to make, and implement, that choice.

What the Revised EU Product Liability Directive Changes

The EU Product Liability Directive, as revised by Directive (EU) 2024/2853, replaces the original 1985 framework (Directive 85/374/EEC) with a regime designed for a digital, connected economy. The changes are substantial and affect every link in the product supply chain. Below is a structured overview of the three most consequential shifts.

Scope: What Counts as a Product?

Under the revised Directive, the definition of “product” now explicitly encompasses software, including stand-alone software that is not embedded in or bundled with a physical device. This means a Swiss firm that develops and licenses a mobile application, an enterprise SaaS tool or an AI model to EU customers is now classified as a producer of a “product” for the purposes of strict liability. Digital manufacturing files, such as 3D-printing blueprints, and related digital services that are integrated into or interconnected with a product are similarly captured. The practical consequence is that liability for software is no longer a matter of contractual negotiation alone; it is a statutory obligation.

Defect Standard and Proof: Mandatory Safety Requirements and Presumptions

The revised Directive clarifies the defect standard by linking it to the safety that a person is entitled to expect, taking into account the product’s presentation, its reasonably foreseeable use, the moment it was placed on the market or put into service, and, critically, any mandatory safety requirements in EU law. Non-compliance with such requirements creates a strong presumption of defect. Furthermore, the burden of proof shifts: where a claimant faces excessive technical or scientific difficulty in establishing defectiveness or the causal link, courts may presume defect or causation. This reversal of evidentiary default is a significant departure from the claimant-friendly but still traditional burden in the 1985 Directive and means manufacturers must be prepared to demonstrate safety affirmatively.

Who Can Be Liable Under the EU Product Liability Directive?

The circle of potentially liable parties has widened. The Directive imposes strict liability on manufacturers, importers and, in defined circumstances, authorised representatives and fulfilment service providers. Where a defective product is placed on the EU market and no EU-based manufacturer or authorised representative can be identified, the importer or even the distributor may be treated as the liable “manufacturer” for the purposes of the Directive. For Swiss exporters, this creates a direct incentive to ensure that their EU distribution chain is clearly documented and that at least one EU-established entity formally accepts the role of authorised representative or importer.

Online platforms that allow consumers to conclude transactions may, in certain circumstances, also bear liability, an important consideration for Swiss businesses selling through EU marketplaces.

Does Product Liability Switzerland Law Require PLD Compliance? Territorial Scope and How PLD Applies to Swiss Exporters

Swiss domestic product liability law, principally the Swiss Product Liability Act (Produktehaftpflichtgesetz, PrHG), which entered into force in 1994 and was modelled on the original 1985 EU Directive, does not automatically incorporate the revised EU Directive. Switzerland is not an EU Member State and is not bound by the transposition obligation. However, the territorial reach of the revised PLD means that Swiss exporters who place products on the EU market, or whose products are put into service within the EU, will be subject to the national implementing laws of the Member State in which harm occurs.

The practical test is straightforward: if a product reaches an EU consumer or business user, whether sold directly, through a distributor, via an online marketplace or through an OEM integration, the revised PLD framework governs claims for defect-related damage. Swiss exporters EU compliance therefore depends not on Swiss domestic transposition, but on the nature and destination of the export itself.

Case Examples: When Swiss Exporters Are Exposed

• Industrial IoT device with OTA updates. A Swiss manufacturer sells a connected sensor to a German distributor. After deployment, the manufacturer delivers over-the-air firmware updates to units in the EU. If a security vulnerability in an update causes physical damage or data loss exceeding the Directive’s thresholds, the manufacturer is the producer under PLD. Its failure to provide a timely security patch could itself be treated as a defect.
• Stand-alone enterprise software licensed to an EU customer. A Zurich-based software company licenses a logistics-management application to a French enterprise. The software malfunctions, causing a warehouse automation failure that injures a worker. Under the revised PLD, the software is a “product” and the Swiss licensor is the producer, subject to strict liability under French implementing law.
• Component integrated by an EU OEM. A Swiss chip designer supplies processors to an Italian medical-device maker. The chip contains a firmware defect that contributes to a device malfunction. The EU OEM is liable to the injured party under PLD, but holds contractual recourse rights against the Swiss component supplier. Robust indemnity and warranty clauses are critical.

Software, Updates and Post-Market Obligations, Operational Checklist

The revised Directive makes software update liability a central feature of the new regime. Where a product, whether hardware, firmware or stand-alone software, requires updates to remain safe, a failure to provide those updates within a reasonable time can constitute a defect for which the producer bears strict liability. This creates enforceable post-market obligations that go far beyond traditional product-safety recall duties.

The following operational checklist maps the key actions Swiss manufacturers and software developers should implement before 9 December 2026.

Patching Policy Template

Every Swiss exporter placing software or connected products on the EU market should formalise a patching and update policy that addresses the following elements:

• Defined support period. State the minimum period during which security and functional updates will be provided. This should reflect the product’s reasonably expected useful life and, where applicable, any EU sector-specific requirements (e.g., under the Cyber Resilience Act).
• Severity classification. Adopt a vulnerability severity framework (e.g., CVSS) and define response-time targets for each severity level, critical vulnerabilities should trigger patches within days, not weeks.
• Delivery mechanism. Specify how updates will reach end users (OTA push, manual download, distributor-managed rollout) and ensure the mechanism is documented and auditable.
• User notification. Implement a clear process for notifying end users when updates are available and when support periods approach expiry.
• End-of-life procedure. Document the process for communicating end-of-support status and, where applicable, for migrating users to supported alternatives.

Evidence and Logging Requirements

Under the revised Directive’s disclosure and evidence rules, manufacturers may be ordered by courts to disclose relevant evidence. Proactive logging is therefore both a compliance requirement and a litigation-defence strategy. Swiss manufacturers should ensure:

• Version-controlled release logs recording every software build, patch and update pushed to EU-deployed products.
• Automated telemetry capturing update-installation status per device or licence, stored in tamper-evident formats.
• QA and testing records for each release, including regression tests, security scans and sign-off documentation.
• Vulnerability intake logs recording the date each vulnerability was reported, triaged, patched and deployed.

Update Obligations by Product Type

Contract Strategies to Allocate and Limit PLD Risk

The revised Directive cannot be contracted out of in the consumer-facing relationship: strict liability is mandatory and any clause purporting to exclude or limit it vis-à-vis the injured party is void. However, business-to-business contracts within the supply chain remain the primary tool for allocating economic risk, defining responsibility for updates and ensuring that the party best placed to prevent a defect carries the corresponding financial exposure. For Swiss exporters navigating supply-chain liability, the following contract strategies are essential.

Sample Clauses

Indemnity clause (component supplier → OEM): “The Supplier shall indemnify and hold harmless the Buyer against all claims, losses, costs and expenses (including reasonable legal fees) arising from a defect in the Supplied Component, including any defect attributable to a failure by the Supplier to provide security or functional updates as required by applicable product liability and product safety legislation in the jurisdiction in which the End Product is placed on the market.”

Update SLA clause (software licensor → integrator): “The Licensor shall provide security updates for Critical and High-severity vulnerabilities within [14] calendar days of confirmed triage. Functional updates required to maintain compliance with mandatory safety requirements shall be provided within [30] calendar days. Update delivery shall be logged and the Licensor shall provide quarterly compliance reports to the Integrator.”

Limitation of liability tied to revenue: “The aggregate liability of either Party under this Agreement shall not exceed [200]% of the total fees paid or payable by the Buyer in the [12]-month period preceding the event giving rise to the claim; provided, however, that this limitation shall not apply to liabilities arising from (a) wilful misconduct or gross negligence, (b) death or personal injury caused by a defective product, or (c) mandatory statutory obligations under applicable product liability law.”

What Not to Rely On

Swiss exporters should not assume that general limitation-of-liability clauses drafted under Swiss domestic law (particularly the Swiss Code of Obligations) will be effective in an EU PLD claim governed by a Member State’s implementing law. Specific risks include:

• Blanket exclusions of consequential loss, these may be overridden where the Directive mandates compensation for specific damage categories.
• Choice-of-law clauses selecting Swiss law, EU courts will typically apply the mandatory provisions of their own PLD implementing law to consumer claims, regardless of a B2B choice-of-law clause further up the chain.
• Reliance on “as-is” delivery terms, delivering software without warranties of fitness or security is incompatible with the PLD’s strict-liability framework and creates audit risk under the EU Cyber Resilience Act as well.

Insurance, Recalls and Product-Safety Logistics for Swiss Exporters

The financial exposure created by the revised PLD, particularly the inclusion of software, connected products and the broadened circle of liable parties, demands a thorough review of existing insurance coverage. Many Swiss product liability policies were written for a pre-digital product landscape and may contain exclusions that leave software-related claims uninsured.

Industry observers expect a significant wave of policy reviews and renegotiations in the second half of 2026 as Swiss exporters and their brokers recalibrate coverage to the new Directive’s scope. Recall costs, in particular, are often excluded from standard product liability policies and must be addressed through dedicated product-recall or product-contamination endorsements.

From a logistics perspective, Swiss manufacturers must decide whether recall coordination will be managed directly from Switzerland or delegated to an EU-based representative. Under EU market-surveillance regulations, the responsible economic operator in the EU (typically the importer or authorised representative) must be able to cooperate with Member State authorities, provide documentation and coordinate corrective actions. Swiss manufacturers should pre-negotiate recall workflows with their EU partners and document them in distribution agreements.

Insurance Checklist

• Review product liability policy scope. Confirm that the policy covers software, firmware updates and connected-product risks, not only physical products.
• Check territorial coverage. Ensure coverage extends to claims brought in EU Member States under their PLD implementing laws.
• Verify recall-cost coverage. Secure a dedicated product-recall endorsement or stand-alone policy covering logistics, customer notification, replacement and disposal costs.
• Add cyber/technology liability. Where products include software or cloud-connected features, ensure cyber liability coverage applies to product-related incidents, not only data breaches.
• Confirm retroactive cover. For products already on the EU market before 9 December 2026, confirm that policies provide retroactive coverage for incidents arising after transposition from products placed on the market earlier.
• Align policy with contract indemnities. Ensure that insurance coverage matches the indemnity obligations assumed in supply-chain contracts.

Litigation and Evidence Strategy, Record Keeping and Disclosures

One of the most consequential procedural changes in the revised EU Product Liability Directive is the introduction of mandatory disclosure obligations. Where a claimant presents facts and evidence sufficient to support the plausibility of a claim, the court may order the defendant to disclose relevant evidence in its control. Refusal or failure to comply may lead to a presumption of defect or causation, a powerful incentive for manufacturers to maintain comprehensive records.

For Swiss manufacturers, this shifts the litigation strategy from reactive document production to proactive evidence architecture. The cost of building and maintaining proper records is modest compared to the cost of an adverse presumption in a multi-million-franc damages claim.

Preserve the Right Evidence

The following categories of evidence should be preserved as a matter of routine, with defined retention periods aligned to the Directive’s limitation rules and the product’s expected useful life:

• Design and development records: Requirements specifications, design-review minutes, risk assessments (FMEA, HAZOP), and safety-case documentation.
• Software version history: Complete version-control logs (e.g., Git commit history), build artifacts and release notes for every version deployed to EU-market products.
• Update and patch logs: Timestamped records of every update pushed, including deployment success/failure rates per device or licence.
• QA and testing archives: Test plans, test results, regression-test reports, penetration-test reports and security-audit findings.
• Vulnerability management records: Intake logs, triage decisions, remediation timelines and closure records for every reported vulnerability.
• Customer communications: Copies of safety notices, recall communications, update notifications and end-of-support advisories sent to EU customers or distributors.

Decision Matrix: Placing New Products on the EU Market After 9 December 2026

Not every Swiss manufacturer will face the same level of exposure under the revised PLD. The matrix below provides a structured framework for assessing the risk profile of a new product launch and the appropriate commercial decision. The likely practical effect will vary depending on product type, software complexity and the maturity of the manufacturer’s post-market support infrastructure.

Implementation Roadmap and Internal Governance: 30/60/90 Day Plan

Effective PLD transposition 2026 readiness requires coordinated action across multiple functions. The roadmap below assigns ownership and establishes a meeting cadence to ensure that compliance milestones are met before the 9 December 2026 deadline.

Days 1–30: Assessment and gap analysis

• Legal: Map all products currently placed on the EU market; identify EU distribution partners; review existing contracts for PLD-relevant clauses.
• R&D / Engineering: Audit current update and patching capabilities; assess evidence-retention infrastructure.
• QA: Review testing and release documentation standards against PLD disclosure requirements.

Days 31–60: Remediation and drafting

• Legal: Draft or amend supply-chain contracts (indemnities, update SLAs, limitation clauses); engage insurance broker for policy review.
• Product / R&D: Implement patching-policy template; define supported-life periods; deploy logging infrastructure.
• Supply chain / Sales: Notify EU distributors and importers of new contractual requirements; appoint or confirm EU authorised representative.

Days 61–90: Validation and sign-off

• Legal + QA: Conduct a tabletop PLD-readiness exercise (simulated claim scenario); validate evidence-retention chain.
• Executive / Board: Sign off on PLD compliance policy; approve updated insurance cover; confirm go/no-go for each product line.
• Ongoing governance: Establish quarterly PLD compliance review meetings (Legal, R&D, QA, Product) with documented minutes and action tracking.

Reporting and Disclosure Obligations by Entity Type

The revised Directive assigns different obligations depending on the entity’s role in the supply chain. Swiss manufacturers must understand not only their own duties but also those of their EU-based partners, as gaps in the chain create shared exposure.

Conclusion

The revised EU Product Liability Directive represents the most significant expansion of product liability in Europe in four decades, and its impact on product liability in Switzerland, particularly for exporters, is immediate and substantial. Swiss manufacturers, software developers and connected-product companies that sell into the EU cannot afford to treat this as a distant regulatory matter. The 9 December 2026 transposition deadline is the hard boundary; the operational, contractual and insurance readiness work must be completed well before that date.

Early indications suggest that manufacturers who begin the assessment and remediation process now, using the structured 30/60/90 day roadmap, contract templates and decision matrix provided in this guide, will be best positioned to continue serving EU customers without interruption and with manageable legal exposure. Those who delay face a binary choice: rush to comply under pressure, or restrict EU market access entirely.

For a downloadable compliance checklist, sample contract clauses and a tailored advisory assessment, qualified Swiss liability counsel listed in the Global Law Experts lawyer directory can provide jurisdiction-specific guidance aligned with the frameworks outlined in this article.

This article is published for general informational purposes and does not constitute legal advice. Readers should consult qualified legal counsel for advice specific to their circumstances.

Sources

1. Directive (EU) 2024/2853, Revised Product Liability Directive (Official Journal of the European Union)
2. European Parliamentary Research Service (EPRS), Briefing on the Revised Product Liability Directive
3. European Commission, Product Liability Directive Information Page
4. Swiss Product Liability Act (Produktehaftpflichtgesetz, PrHG), Fedlex
5. Swiss Product Safety Act (Produktesicherheitsgesetz, PrSG), Fedlex
6. ICLG, Product Liability Laws and Regulations: Switzerland