Collective Claims and Class Actions Under the EU Product Liability Directive, What French Manufacturers, Importers and Marketplaces Must Do Before France's 2026 Transposition

Product liability collective actions in France are entering a period of rapid, structural change. Directive (EU) 2024/2853, the revised Product Liability Directive, or RPLD, must be transposed into French law by 9 December 2026, expanding strict liability to digital products and software, widening the circle of liable operators, and shifting the burden of proof in ways that make collective claims substantially easier to mount. At the same time, France has already moved ahead of the transposition deadline with national measures, notably Decree No. 2025‑1191 and related reforms to its collective redress framework, that reshape how representative actions are brought, funded and enforced.

For general counsel, product‑safety officers and compliance teams at manufacturers, importers and online marketplaces, the window for preparation is narrowing fast. This guide provides the France‑specific, operational playbook that high‑level summaries of the Directive leave out.

Executive Summary: What Manufacturers Must Decide Now

With the transposition deadline set for 9 December 2026, every manufacturer, importer and marketplace operator selling products in France should treat the next months as a compliance sprint, not a waiting period. The five actions below represent the minimum immediate response.

1. Audit your product portfolio for RPLD exposure. Map every product, including standalone software, firmware, IoT components and AI‑enabled devices, against the expanded definition of “product” under the RPLD. Products that previously fell outside the 1985 Directive may now trigger strict liability.
2. Preserve evidence now. Lock down design files, risk assessments, testing records, software version logs and patch histories. Under the RPLD’s new disclosure and causation‑presumption rules, gaps in your evidence trail become the claimant’s advantage.
3. Review and update insurance coverage. Confirm that your product‑liability policy responds to collective claims, software‑related defects and recall costs. Notify your insurer or broker of the changing regulatory environment and request a coverage gap analysis.
4. Revisit supply‑chain contracts. Check that indemnity, warranty and recall‑cost‑allocation clauses in supplier, importer and marketplace agreements reflect the broader liability chain the RPLD creates.
5. Prepare a crisis‑communications protocol. Collective actions attract media attention. Draft holding statements, designate spokespersons and align legal, compliance and communications teams on messaging before a claim materialises.

Quick Legal Primer: RPLD Changes That Matter for Product Liability Collective Actions in France

Directive (EU) 2024/2853 repeals and replaces the original 1985 Product Liability Directive (85/374/EEC). For manufacturers operating in France, several changes directly amplify the risk and reach of collective claims.

• Expanded product definition. Software, whether embedded or standalone, digital manufacturing files and AI systems are now expressly covered. This brings app developers, SaaS providers and IoT manufacturers within the strict‑liability regime for the first time.
• Broader liable‑operator list. Beyond traditional manufacturers and importers, the RPLD may capture authorised representatives, fulfilment service providers and, crucially, online marketplaces where no other liable operator within the EU can be identified.
• Lowered causation threshold. Courts may presume a causal link between the defect and the damage where the claimant demonstrates that the product was defective and the damage is consistent with the defect. This is a significant departure from the existing French requirement that claimants prove causation independently.
• Disclosure of evidence. Defendants can be ordered to disclose relevant evidence, including technical data and internal testing records, if the claimant has presented facts and evidence sufficient to support the plausibility of the claim. Failure to disclose may result in a presumption of defectiveness.
• Extended limitation periods. The RPLD introduces a long‑stop period and preserves Member State discretion on certain limitation rules, meaning collective actions may be viable for a longer window than under existing French law.

Industry observers expect these changes to lower the barriers to collective product liability claims in France significantly, making it easier for representative bodies to assemble claimant groups and establish liability without the granular, case‑by‑case causation evidence historically required.

France’s National Measures: Decree No. 2025‑1191 and Collective Redress France Reforms

France has not waited for the RPLD transposition deadline to modernise its collective redress framework. A series of legislative and regulatory measures adopted in 2025 have already reshaped the procedural landscape for product liability collective actions in France.

What Changed and When

France’s collective redress overhaul, enacted through legislation effective from May 2025 and supplemented by Decree No. 2025‑1191, introduced several significant reforms. These include a more unified procedural framework for collective actions across all civil matters, replacing the patchwork of sector‑specific regimes that existed since the original action de groupe was introduced in consumer law in 2014. The reforms also introduced civil penalties for non‑compliance with court orders in collective proceedings, strengthened the powers of approved representative bodies, and clarified procedural rules for case management and notification of affected consumers.

Decree No. 2025‑1191, published in the Journal Officiel and available on Legifrance, provides implementing detail on registration requirements, the format of notifications to potential claimants, and the mechanics of court‑supervised settlement or judgment in group proceedings. These rules are already in force and apply independently of the RPLD transposition.

The practical effect of this sequencing is that French courts already have enhanced procedural tools for managing collective claims. Once the RPLD’s substantive liability provisions are transposed, the combination of a broadened strict‑liability regime with an upgraded procedural infrastructure will create a notably more claimant‑friendly environment than existed even twelve months ago.

Standing and Procedure: Action de Groupe vs RPLD Representative Actions

The French Action de Groupe

Since 2014, France has permitted approved consumer associations and certain qualified entities to bring collective actions on behalf of groups of consumers who have suffered similar harm. The French model operates on an opt‑in basis: consumers must affirmatively join the group after a court has ruled on the defendant’s liability. The mechanism was initially confined to consumer and competition disputes but has since been extended to health, environmental and discrimination matters, and is now unified under the 2025 reforms.

Representative Bodies Under the RPLD

The RPLD requires Member States to ensure that representative actions are available for product liability claims brought under the Directive. This interacts with the EU Representative Actions Directive (Directive 2020/1828), which France has also been implementing. Under these combined frameworks, qualified entities, typically consumer organisations with a track record of public‑interest advocacy, can bring actions both domestically and cross‑border.

Early indications suggest that France will retain its opt‑in model for product liability collective actions even after RPLD transposition, but the broader range of compensable damage and the lowered evidentiary thresholds mean that each individual claim within a group will be easier to sustain. The likely practical effect will be larger claimant groups forming more quickly, particularly in product categories where harm is widespread but individually modest, exactly the pattern seen with consumer electronics, household appliances and connected devices.

Practical Defence Playbook: Defending Collective Product Liability Claims From Pre‑Litigation to Court

Immediate Evidence Preservation and Digital Forensics

The single most critical step when a collective claim is anticipated or filed is locking down evidence. Under the RPLD’s disclosure regime, courts can order manufacturers to produce technical documentation, and a failure to do so triggers a presumption of defectiveness. This makes proactive evidence preservation not just good practice but a litigation necessity.

• Freeze all design and testing records. Issue a litigation hold across engineering, quality assurance and regulatory teams covering the product in question.
• Capture software state. For digital products, preserve the exact version of firmware or software that shipped, plus all subsequent patches and update logs with timestamps.
• Secure customer complaint data. Centralise all complaints, warranty claims and field reports, these will be scrutinised by claimants seeking to establish pattern evidence.
• Engage forensic experts early. For IoT and connected products, instruct independent digital forensics specialists to image devices and server‑side data before it is overwritten.

Product Recall vs Class Action: Decision Framework

One of the most consequential decisions a manufacturer faces is whether to initiate a voluntary recall or stand and defend against a prospective collective claim. The table below provides a structured framework for that decision.

Early Engagement and ADR Strategies

French courts encourage, and in some cases require, pre‑litigation mediation or conciliation. Engaging early with consumer associations, particularly those with standing to bring an action de groupe, can be strategically advantageous. A negotiated resolution before formal proceedings avoids the reputational cost of a public judgment, limits the scope of discovery, and often achieves more controlled cost outcomes.

Tactical Litigation Defences

• Absence of defect. The product conformed to its specification and met all applicable safety standards at the time of placing on the market.
• State of the art. The defect was not discoverable given the state of scientific and technical knowledge at the time.
• Contributory fault / misuse. The damage resulted wholly or partly from the claimant’s own misuse or failure to follow instructions.
• Compliance with mandatory standards. Where the defect results from compliance with mandatory national or EU regulations, the manufacturer may have a defence, though this is narrowly construed.
• Expiry of limitation period. Challenge whether claims fall within the applicable limitation period, particularly for products placed on the market many years ago.

Third‑Party Litigation Funding France: What to Expect and How to Prepare

The Evolving French Rules on Litigation Funding

Third‑party litigation funding in France has grown significantly in recent years, and the 2025 collective redress reforms have brought increased attention to the role of funders in group proceedings. While France does not yet have a comprehensive registration or licensing regime for litigation funders comparable to those in some common‑law jurisdictions, the reforms have introduced transparency and disclosure obligations. Funded collective actions must now comply with rules designed to ensure that the funder’s involvement is disclosed to the court and, in certain cases, to the defendant.

Recognising Funder Signals

Manufacturers should be alert to early signs that a funded collective action may be in preparation. These signals include pre‑action information requests styled as formal mise en demeure letters, coordinated complaints filed simultaneously through consumer platforms, or public solicitations by litigation funders inviting consumers to register claims. The involvement of a professional funder typically indicates that the claim has been assessed as commercially viable and will be pursued with substantial resources.

Defensive Contracting and Evidence Strategy

• Anti‑assignment clauses. Review warranty terms and general conditions to restrict the assignment of claims to third parties, including funders, though enforceability varies.
• Waiver limitations. Ensure that contractual limitation‑of‑liability clauses are drafted to withstand challenge under French consumer protection law, particularly for B2C products.
• Information barriers. Where commercially sensitive technical data is requested pre‑action, respond through counsel to protect privilege and limit the information available to funders for case‑building purposes.
• Funder disclosure requests. Be prepared to request that the court order disclosure of the funding agreement, including the funder’s share of any recovery and the extent of its control over litigation decisions.

Insurance, Indemnities and Commercial Steps to Limit RPLD Exposure

Insurance Coverage Review

The RPLD’s expanded scope, particularly its inclusion of software and digital products, creates potential coverage gaps in traditional product‑liability policies. Manufacturers should conduct an immediate review with their broker or insurer covering three areas: whether the policy definition of “product” extends to software and digital services; whether collective actions and representative proceedings are covered or excluded; and whether recall costs (including notification, logistics and remediation) are included or require a separate policy.

Drafting Supply‑Chain Contracts

The broadened liability chain under the RPLD means that contractual allocation of risk between manufacturers, importers and marketplaces is more important than ever. Key clauses to review or introduce include:

• Mutual indemnities. Each party in the supply chain should indemnify the others for losses arising from defects attributable to its acts or omissions.
• Recall‑cost allocation. Specify which party bears the cost of product recalls, including logistics, consumer notification, replacement and disposal, and ensure this aligns with insurance coverage.
• Evidence cooperation. Include obligations requiring each supply‑chain partner to preserve and produce evidence (design records, conformity assessments, testing data) in the event of a collective claim.
• Insurance requirements. Mandate minimum product‑liability insurance levels for all parties in the distribution chain, with certificate‑of‑insurance obligations.

Reinsurance Considerations

For manufacturers with significant French market exposure, early conversations with reinsurers about the impact of the RPLD on aggregate loss expectations are advisable. The likely practical effect of collective actions becoming easier to bring, and covering a wider range of products, will be upward pressure on reinsurance pricing for product‑liability portfolios. Engaging proactively allows manufacturers to secure coverage at current terms before the market fully prices in post‑transposition risk.

Sector Focus: Manufacturer Liability for Software Defects Under the RPLD

How the RPLD Treats Software as a Product

One of the most significant innovations of Directive (EU) 2024/2853 is its express treatment of software, including standalone applications, operating systems, AI systems and digital manufacturing files, as “products” subject to strict liability. This means that a developer whose software causes physical harm, property damage or data destruction faces the same liability framework as a manufacturer of physical goods, without the claimant needing to prove fault.

Evidence Preservation for Logs, Updates and Patches

Software products present unique evidentiary challenges. Unlike a physical product that can be inspected, software may have been updated, patched or entirely replaced between the time of the alleged defect and the time a claim is filed. Manufacturers of digital products should maintain:

• Version control archives. Complete, tamper‑evident records of every software version released, with timestamps and changelogs.
• Patch deployment records. Logs showing which patches were deployed, to which devices, and when, including evidence that consumers were notified.
• Telemetry and error data. Where the product collects usage or error data (consistent with GDPR), preserve this data as potential evidence of conformity or of the absence of defect.
• Third‑party component records. Documentation of all open‑source or third‑party libraries used, including known vulnerability disclosures at the time of integration.

Product Lifecycle and Obsolescence Risk

The RPLD’s extended liability window creates a particular risk for software products that reach end‑of‑life or end‑of‑support. Industry observers expect that manufacturers who discontinue security patches or functionality updates may face arguments that the product became defective through the manufacturer’s own inaction. Lifecycle policies should clearly communicate support periods, and end‑of‑life decisions should be documented with risk assessments showing that the decision was reasonable and that consumers were given adequate notice.

What Courts and Regulators Will Look For: Burden of Proof, Causation and Standards

Under existing French product‑liability law, rooted in Articles 1245 to 1245‑17 of the Civil Code, the claimant bears the burden of proving the defect, the damage and the causal link between them. The RPLD introduces significant modifications to this framework.

The new causation presumption is the most consequential change. Where a claimant demonstrates that the product was defective and that the damage suffered is of a kind consistent with the defect, the court may presume causation. This shifts the practical burden to the manufacturer to adduce evidence breaking the causal chain, a materially harder task in collective proceedings where the sheer number of claimants creates a strong inference of systematic defect.

The RPLD’s evidence disclosure mechanism reinforces this shift. If a court orders a manufacturer to produce technical documentation and the manufacturer refuses or fails to do so, the court may presume that the product was defective. For collective actions, where pattern evidence and systematic analysis are central to the case theory, this procedural weapon gives claimants and their representative bodies substantial leverage.

Compliance with harmonised European standards provides some evidential support for the absence of a defect, but it is not a complete defence. French courts have historically held that conformity with standards is a relevant factor but does not conclusively establish that a product was free from defects. Early indications suggest that this position will continue under the transposed RPLD, with courts looking beyond formal compliance to assess whether the product met the safety expectations of the general public.

Reporting Obligations by Entity Type

Conclusion and Recommended 90‑Day Action Plan for In‑House Teams

Product liability collective actions in France are being reshaped by the convergence of the RPLD and France’s own ambitious collective redress reforms. The transposition deadline of 9 December 2026 is not a distant policy event, it is an operational deadline requiring concrete action today. The following 90‑day action plan assigns accountability across the functions that must move first.

Manufacturers, importers and marketplaces that complete this plan within 90 days will be materially better positioned to defend against collective claims, negotiate with consumer associations from a position of strength, and demonstrate to courts and regulators that they took reasonable and proportionate steps to manage product safety risks. The cost of preparation is a fraction of the cost of responding unprepared to a funded collective action. Specialist product liability lawyers in France can provide tailored guidance on each of these steps.

Sources

1. Directive (EU) 2024/2853, Official text (EUR‑Lex)
2. French Decree No. 2025‑1191 / Journal Officiel (Legifrance)
3. Linklaters, “France adopts new rules for collective redress” (May 2025)
4. ICLG, France: Product Liability Laws and Regulations (2025)
5. Global Legal Post, Commentary on France collective redress law (January 2026)
6. Legal 500, France Product Liability Guide
7. DGCCRF, French product safety and recall guidance