EU Product Liability Directive (2024/2853) Pages on Changzhou Manufacturer Websites: How Should They Be Accepted?

Direct answer: The EU's new Product Liability Directive (Directive (EU) 2024/2853) is not automatically covered by "the product has CE marking and we bought product liability insurance". It applies from 9 December 2026 to products placed on the EU market or put into service on or after that date, replacing the 1985 Directive 85/374/EEC; it brings software, AI systems and digital manufacturing files into the definition of "product", adds importers, authorised representatives, fulfilment service providers, distributors and some platforms to the EU liability chain, widens compensable damage (including psychological harm and data destruction/corruption), and strengthens court disclosure and presumptions of defect/causation. A manufacturer's "EU Product Liability Directive" page should state the products/roles covered, the EU responsible operator, technical files and batch traceability, software updates and cybersecurity, how defectiveness is assessed, evidence cooperation, recall/incident response and the limits of insurance—not just "we value quality".

This guide is for equipment, electrical/electronic, appliance, automotive, medical device, consumer product, software/smart-hardware and export trading companies in Changzhou and nearby areas. It explains how to write and accept an EU Product Liability Directive page. Information is current to 2026-11-05. It is a review of public rules and project practice, not EU legal, litigation, insurance or compliance advice; the specific liability, defences, damages, limitation periods and national transposition depend on the directive, Member State law, the courts and the insurance contract.

How does the PLD page relate to product liability insurance, GPSR, recall, warranty and CE pages?

The product liability insurance page answers "what the policy covers, excludes and how claims work"; the GPSR product page answers "product safety duties, the EU responsible person, traceability and recall"; the recall/traceability page answers "how to stop sales, recall and notify after a problem"; the warranty/returns page answers "contractual warranty and after-sales"; the CE page answers conformity assessment under specific product rules. The PLD page answers "when a defective product causes damage, who pays, for what, how is it proven and how long do claims last". Insurance transfers risk and cannot replace statutory liability; GPSR/CE are ex-ante safety duties, not a liability finding.

Common breakpoints: treating a CE certificate as an exemption; treating insurance as "no need to manage liability"; treating the GPSR EU responsible person as the only PLD operator; covering only quality warranty and missing software/updates; covering only Chinese law and missing Member State transposition; confusing "defective" with "non-conforming/breach of contract". A page that states roles, products, evidence, updates and incident response gives sales, legal, quality and after-sales one playbook.

This page map is editorial; PLD duties follow Directive (EU) 2024/2853 and the European Commission page.

What is the timeline, transition and limitation period?

The directive was adopted on 23 October 2024, published on 18 November 2024 and entered into force on 8 December 2024; Member States must transpose it by 9 December 2026. It applies to products placed on the market or put into service on or after 9 December 2026; products placed earlier remain under the old Directive 85/374/EEC. Claims: the victim has 3 years from knowledge of the damage, defect and liable operator; claims generally expire 10 years after placing on the market; for health-related damage with slow-emerging symptoms, up to 25 years. National transposition may affect procedure and boundaries.

The page must not present "entry into force" as "application", nor "transposition deadline" as "all Member States have implemented identically". Products placed before 9 December 2026, new models/substantially modified products after that date and continuous software updates may fall under different rules; cross-border/platform sales also depend on the platform's role. State entry into force/transposition/application/legacy products/limitation periods, and flag Member State differences.

Dates/periods follow Articles 2, 16–17 and 22 and the Commission page; national transposition may adjust procedural details.

Who can be held liable in the EU?

The manufacturer is the primary liable person (including a person placing the product on the market/putting it into service); a non-EU manufacturer remains liable, but the victim can claim against the EU importer or authorised representative; in their absence, against the fulfilment service provider. The victim can ask the distributor for the identity of the EU liable operator; with no EU operator or no response within 1 month, the victim can claim against the distributor. Platforms can be liable when acting as manufacturer/importer/authorised representative/fulfilment service provider/distributor; mere intermediaries are handled under the DSA and related rules.

Acceptance checks: product/sales model; who the EU importer/authorised representative/fulfilment service provider is; whether contracts define roles; the distributor information-response process; platform sales terms; whether a non-EU entity has an EU contact. Common gaps: assuming "FOB factory/the customer is the importer" means no exposure; an authorised representative appointed only for CE/GPSR but not PLD; distributors unaware of the 1-month rule; unclear platform seller entity; contracts without responsibility/allocation or recourse.

Liable persons follow Articles 4 and 8 and the Commission page; the specific case depends on the actual role and national law.

What counts as a "product"? Software, AI, digital files and substantial modification

"Product" covers all movable items, even when integrated into another item; software (embedded or supplied separately), AI systems and digital manufacturing files are included. A software defect existing at release can trigger liability, including defects that become apparent after release through updates, upgrades or machine learning. A product that is substantially modified (e.g. remanufactured) is considered a new product, and the person making the modification becomes the manufacturer. Whether a digital service/remote data processing counts as a "product" depends on its integration with the product and national law.

Acceptance checks: product list (hardware/software/digital files); software version and release records; AI model/training/update records; OEM/ODM and brand-owner roles; remanufacturing/refurbishment/modification process; subscription/remote-service contracts; cybersecurity support period. Common gaps: listing only hardware; treating software as a "service"; missing update logs; selling refurbished units as old stock; unclear brand-owner/contract-manufacturer responsibility; remote services without version/support period.

Product scope follows Article 4 and the Commission page; the treatment of digital services/remote processing depends on national law and the specific integration.

How is "defectiveness" assessed?

Defectiveness is not a synonym for "non-conforming" or "has a fault"; it means the product does not provide the safety a person is entitled to expect, or does not meet the safety level required by EU/national law. All circumstances are relevant: product presentation/warnings, reasonably foreseeable use, time of placing on the market/use, the product's ability to continue learning or acquire new features, applicable safety requirements, cybersecurity/update support, recalls/corrective actions. Price, alternatives and the use environment may also matter.

Acceptance checks: safety expectation and intended use; instructions/warnings; foreseeable misuse; market date; software updates/learning; safety rules/standards; known risks and corrections; batch/version. Common gaps: "complies with a standard" treated as no defect; instructions without warnings; foreseeable misuse ignored; software updates change behaviour; known risks not corrected; batches/versions mixed.

Defectiveness follows Article 7 and the Commission page; the specific case is decided by the court on the evidence.

What damage is compensable?

Compensable damage includes death or personal injury (physical and psychological harm); damage to or destruction of property (other than the defective product itself and property used exclusively for professional purposes); and destruction or corruption of data (non-professional use; the exact scope follows national law). The new directive removes the old €500 threshold for property damage and does not allow the old liability caps; national law determines calculation and non-material loss. Contractual clauses cannot simply exclude statutory liability.

Acceptance checks: damage type; whether property is exclusively professional; whether data is non-professional; caps/deductibles; insurance coverage; Member State differences; claim notification/defence. Common gaps: assuming only personal injury; ignoring data; assuming the €500 threshold still applies; a contract saying "all liability excluded"; insufficient insurance limits; assessing a cross-border case under Chinese law.

Damage follows Article 6, the Commission page and national transposition; this is not an opinion on damages amounts.

How should evidence disclosure and presumptions be accepted?

In principle the victim must prove the defect, the damage and causation; but the new directive introduces court disclosure of evidence: where proportionate and necessary, a court may order a party to disclose relevant evidence in its control (technical files, tests, software logs, incident records). If the defendant fails to comply, defectiveness may be presumed; defectiveness may also be presumed where the product does not comply with mandatory safety requirements or the damage results from an obvious malfunction in normal/foreseeable use. Where technical/scientific complexity makes proof excessively difficult, defect and/or causation may be presumed if the conditions are met (rebuttable).

Acceptance checks: completeness of technical files; test/version/update logs; incident/complaint records; evidence index and access control; disclosure response process; confidentiality/trade-secret protection; legal counsel coordination. Common gaps: scattered files; no software logs; records created after the incident; slow identification during disclosure; refusing everything as "trade secret"; unaware of the presumptions.

Evidence/presumption rules follow Articles 9–10, the Commission page and national procedural law; the court decides the specific case.

What defences remain, including development risk?

A defendant may argue that it did not place the product on the market/put it into service; the defect did not exist at that time; the defect resulted from compliance with mandatory rules; or the state of scientific and technical knowledge at the time did not make the defect discoverable (development risk defence). However, the development risk defence does not apply to problems arising after placing on the market from a failure to provide necessary software updates/update defects, and Member States may restrict/exclude it for specific product categories. "We did not know then" is not a universal exemption, especially for continuous updates, cybersecurity and known risks.

Acceptance checks: defence grounds and evidence; market date/state of the art; mandatory rules; update support period; Member State differences; contractual recourse; insurance. Common gaps: treating development risk as the default; no contemporaneous technical records; advertising support after updates stop; not checking national carve-outs; missing supplier recourse clauses.

Defences follow the relevant articles, national transposition and the Commission page; this is not litigation strategy advice.

Operational checklist for Chinese exporters

Prepare in seven blocks: product—role—files—updates—incidents—contracts—insurance. Product/software list and versions; EU importer/authorised representative/fulfilment service provider/distributor roles; technical files, testing, risk assessment and batch traceability; software update/cybersecurity support period and logs; complaints/incidents/recall/CAPA; contractual allocation and recourse; insurance and limits. Products placed before 9 December 2026 remain under the old directive, but new models, substantial modifications and updates after that date should be prepared under the new rules.

The most commonly missed items are "software and updates" and "the EU responsible operator": many companies prepare CE technical files but have no version/update logs; write "the customer is the importer" without an authorised representative/fulfilment service provider; buy insurance without incident response or an evidence pack. Appoint a PLD owner, build an evidence index and run an annual exercise.

This checklist is editorial; specific liability, documents and contracts follow the directive, national law, customer contract and professional advice.

How should the website PLD page be written?

A public page should include: products/software covered, roles and the EU liable operator, defectiveness and safety expectations, technical files/batch traceability, software updates and support period, complaints/incidents/recall, evidence-disclosure cooperation, limitation periods/Member State differences, the limits of insurance and contact/version. Write verifiably: state "we have files/processes/roles", not "fully compliant/never liable/all products safe".

Separate "public information" from "case/customer documents": technical files, tests, software logs and incident records are provided on a need-to-know basis; the public page gives scope, process and contacts, and does not publish customer/victim data. If supplying components or carrying out contract manufacturing, state that the company supports the machine builder/brand owner with files and traceability and does not declare the whole product compliant. Multilingual pages should match sales countries.

This page structure is editorial; external claims must be truthful and verifiable, per the directive, national law, customer contract and competent authority.

What must not be written?

High-risk claims: "CE means we cannot be sued" (CE is market access, not a civil exemption); "product liability insurance means no problem" (scope/limits/exclusions apply); "we only do B2B/components, so it does not apply" (products/roles may still be covered); "contracts signed before 9 December 2026 are all under the old law" (look at the product placement date and national law); "software is a service, not a product" (the new directive expressly covers it); "development risk is universal" (update/known-risk exceptions); "all products are zero-defect/absolutely safe" (cannot be guaranteed); "compensation is capped" (the old caps are not allowed). These are inaccurate or misstate responsibility.

Safer wording: "products/roles covered, technical files/traceability, update support, complaints/recall, evidence cooperation and insurance limits, subject to national transposition and the specific case". External promotion must also comply with advertising/fair-competition law; customer/victim information needs authorisation/redaction.

These red lines are editorial; whether a claim is false advertising/non-compliant is determined by regulators and the contract, and this is not legal advice.

Go-live acceptance checklist

Ten checks: product/software scope, roles/EU operator, defectiveness/safety expectations, technical files/batches, software updates/support period, complaints/incidents/recall, evidence-disclosure cooperation, limitation periods/Member State differences, insurance limits, and page wording/version. Each needs an owner, evidence and review date. The pass condition is not "the page says compliant", but that a customer/court/insurer can see what the product is, who is liable and how an incident is investigated and compensated.

Before go-live, run one real product/software version through: scope → roles → defect/safety → files → updates → incidents → evidence → limitation periods → insurance → page wording. Any step that fails is a gap in the page or the process.

This checklist is editorial; specific compliance requirements follow the directive, national law, customer contract and professional advice.

Who should read this, who should not, and what decisions does it support?

It suits manufacturers in Changzhou and nearby areas that export equipment, electrical/electronic goods, appliances, automotive parts, medical devices, consumer products, software/smart hardware, or sell through platforms/cross-border e-commerce to the EU. It also suits legal, quality, after-sales, sales and website teams assessing a PLD page. It does not suit businesses that do not sell to the EU, whose products are not placed on the EU market, or want one page to replace litigation/insurance/legal advice.

Read it if you are preparing before 9 December 2026; your product contains software/AI/updates; an EU customer/importer is asking about liability; you are building or revising a liability page; or you need to separate PLD, GPSR, CE, insurance and recall. Skip it if you treat CE as an exemption, insurance as everything, or only write about Chinese law. It supports self-review of scope, roles, files, updates, incidents, evidence, limitation periods, insurance and page wording.

FAQ

When does 2024/2853 apply?

It entered into force on 8 December 2024 and Member States must transpose it by 9 December 2026; it applies to products placed on the market or put into service on or after 9 December 2026. Earlier products remain under 85/374/EEC; new models, substantial modifications and updates need separate assessment.

Are software and AI "products"?

Yes. The directive expressly covers embedded or standalone software, AI systems and digital manufacturing files; a software defect existing at release can trigger liability, including defects emerging after release through updates/upgrades/machine learning. Whether a remote digital service is a product depends on integration and national law.

Can a non-EU manufacturer still be liable?

Yes. The non-EU manufacturer remains liable, but the victim can claim against the EU importer, authorised representative or (in their absence) fulfilment service provider; the victim can ask the distributor for the operator's identity and claim against the distributor if there is no EU operator or no response within 1 month. Platforms are treated according to their actual role.

What damage is covered, and is there a cap?

Death/personal injury (including psychological), property damage (excluding the defective product itself/exclusively professional property), and data destruction/corruption (non-professional use, per national law). The old €500 threshold is removed and the old liability caps are no longer allowed; calculation and non-material loss follow national law.

Is the development risk defence still available?

In principle yes: prove the defect was not discoverable given the objective state of scientific and technical knowledge at the time. It does not apply to post-market problems from a failure to provide necessary software updates/update defects, and Member States may restrict/exclude it for specific categories. "We did not know then" is not a universal exemption.

How should the website/customer statement be written?

State products/software, roles/EU operator, defectiveness/safety expectations, technical files/batches, update support, complaints/recall, evidence cooperation, limitation periods/Member State differences, insurance limits and contact/version; do not write "CE = exempt, insurance = no issue, zero defects, compensation is capped". Case/customer documents are provided on a need-to-know basis.

One-sentence takeaway

A Changzhou manufacturer's EU Product Liability Directive page is not about "CE marking and insurance". It should turn product/software scope, the EU liable operator, defectiveness and safety expectations, technical files/batch traceability, software updates and support periods, complaints/recall, evidence-disclosure cooperation, the 3/10/25-year periods and insurance limits into a verifiable checklist—so a customer, court and insurer can see who is liable and how an incident is investigated and compensated.

Method and limitations

This is a review of public rules and project practice, not an audit or legal opinion on any company's products, software, liability, litigation, insurance or compliance. No undisclosed customer product, incident, litigation or policy data were used. Scope, roles, documents, updates, evidence and acceptance items are editorial suggestions, not legal/insurance conclusions. Specific liability, defences, damages, limitation periods and national transposition depend on the directive, Member State law, the courts and the insurance contract.

Sources and scope

Information is current to 2026-11-05. The following are EU official/legal pages; their articles, transposition laws and guidance control.

1. Directive (EU) 2024/2853 on liability for defective products and repealing Council Directive 85/374/EEC, adopted 23 October 2024, OJ L 2024/2853, published 18 November 2024: EUR-Lex. Products/software/AI, liable operators, damage, evidence, defences, limitation periods and transposition.
2. European Commission, Liability for defective products: European Commission. Objectives, damage types, liable operators, software/AI, periods and application date.
3. European Commission, EU adapts product liability rules to digital age and circular economy (9 December 2024): European Commission. Software/AI/digital services, EU operators and platforms.
4. Council Directive 85/374/EEC on liability for defective products: EUR-Lex. The old liability framework and transitional application.
5. Regulation (EU) 2023/988 on general product safety (GPSR): EUR-Lex. Product-safety duties, EU responsible person, traceability and recall, distinct from PLD civil liability.