EU Product Liability Directive: What to Document Before December 9

If you sell to Europe, a date matters to you. It is December 9, 2026. After that date, a new product liability regime applies to what you ship. The rules are broader. Claims are easier to bring. And your documents may become the main evidence.

This article is written for manufacturers, not lawyers. It explains the change in plain words. Then it shows what to do with your manuals, records, and software files. It is not legal advice. Ask your counsel how the law applies to your products.

What changes on December 9, 2026

The EU adopted a new Product Liability Directive. Its number is 2024/2853. It replaces rules that date back to 1985. Each EU country must turn it into national law by December 9, 2026.

The new rules apply to products placed on the EU market, or put into service, after that date. Products placed on the market earlier stay under the old rules.

Here are the changes that matter most for manufacturers:

• Software counts as a product. That includes stand-alone software and software built into hardware. It also includes digital files used to make physical goods.
• Updates matter. A maker can be liable for harm caused by an update. It can also be liable for failing to supply a needed security patch.
• Claims get easier. Law firm summaries say the old minimum amount for property damage claims is gone. The old liability cap is gone too.
• Courts can order disclosure. A court can ask a manufacturer to hand over technical information. If the maker does not, the court may presume the product was defective.
• Complex products get special treatment. If a product is too technical for a claimant to analyze, courts may ease the claimant’s burden of proof.

Why documentation is now your first line of defense

Think about what happens after an accident. Someone says your product caused harm. Their lawyer asks how it was designed, tested, and described to users.

Under the new rules, a court can order you to produce those records. If your files are complete, you can show what you knew and what you told users. If your files are missing, messy, or out of date, you have a problem.

That is why documentation moves from “paperwork” to “evidence.” Good records help you prove three things:

1. You warned users clearly.
2. You controlled the design and the changes.
3. You kept the product safe after it shipped, including software updates.

For more on the US side of this risk, read our guide on common documentation mistakes that lead to liability claims.

Who is affected, even if you are not in the EU

Many US manufacturers think this does not apply to them. That is risky. The directive is about where a product is placed on the market, not where it was built.

You may be affected if you:

• Ship equipment, parts, or connected products to EU customers.
• Sell through EU distributors or online marketplaces.
• Make software, firmware, or apps that run inside a product.
• Supply components to a company that sells in the EU.

When a maker is outside the EU, the law looks for another responsible party. That can be an importer, an authorized representative, or a fulfillment provider. Those partners will ask you for documents. Having them ready makes you easier to work with.

What a defense-ready documentation file includes

There is no single official list for every product. The right set depends on what you make. Still, most strong files share the same parts.

Check your product file before December 9

Tick what you can prove today. You will get a score and a list of gaps to fix first.

0 of 12 ready

Start ticking items to see your result.

Copy my gap listStart over

A self-check, not legal advice. Ask counsel how the directive applies to your products.

1. User-facing safety content

This is what you told the user. It includes manuals, quick-start guides, labels, and on-screen messages. Warnings should say the same thing everywhere. State the intended use. State the known misuse risks.

2. Design and risk records

Keep risk assessments, design reviews, and test reports. Date them. Link each one to the product model. If you changed a design after a problem, record why.

3. Software and update records

List the software and firmware version in each product release. Keep release notes. Log security patches. State how long you will support the product. Customers should know when support ends.

4. Revision history and change control

Record who approved each change, when, and why. Tie each manual revision to the serial numbers or builds it covers. This lets you show which instructions a specific unit shipped with.

5. Service and maintenance documents

Include service manuals, parts lists, and maintenance schedules. These show how you expect the product to be kept safe over its life.

6. Translations

If you ship in other languages, keep every version. Each one should match the current source text. A warning that changed in English but not in German is a gap.

7. Complaint and incident records

Log reports of failures, injuries, and near misses. Record what you did in response. This shows you monitored the product after sale.

8. Supplier and component information

Keep records of key components and where they came from. If a part fails, you will need to trace it fast.

A five-step documentation review

You do not need to rebuild everything. Start with a review. This approach works for most teams.

1. List your EU-bound products. Include every model, variant, and software release that will ship after December 9.
2. Map your documents to each product. For each one, note what exists and where it lives.
3. Check versions. Can you tell which manual and software version shipped with a given serial number? If not, fix that first.
4. Close the gaps. Update missing warnings. Refresh old translations. Add update logs. Fill in missing risk records.
5. Set ownership and access. Pick one owner per product file. Store everything in one searchable place. Test that you can pull the full file in a day.

Common gaps we see in manufacturer files

• Old versions disappear. The latest manual is easy to find. The one from three years ago is not.
• Warnings do not match. The manual says one thing. The label or software screen says another.
• Translations lag. The source text changes. The translated copies do not.
• Software notes stay with engineering. Release notes never reach the product file.
• No link between manual and build. Nobody can say which instructions shipped with which unit.

Most of these come from weak change control. Our guide on how to keep manuals current after product changes shows a simple process to fix them.

What to do before and after December 9

In the next two weeks: List your EU-bound products. Pick an owner for each product file. Run the review above on your top sellers.

Before December 9: Close the biggest gaps. Make sure warnings match across manuals, labels, and software. Update translations. Start logging software updates in the product file.

In early 2027: Extend the review to the rest of your catalog. Set a review date each year. Build the file into your normal release process, so it stays current without extra effort.

If you also sell machinery in the EU, pair this work with our EU Machinery Regulation manual checklist. The two efforts overlap. You can do much of the work once.

How CPG Documentation can help

Our team builds and cleans up product documentation for manufacturers. We can audit your current files and find gaps. We can also rewrite unclear warnings, rebuild version control, and keep every language in sync.

• Technical writing support for manuals, warnings, and service content.
• Document production to keep layouts, versions, and formats under control.
• Translation of safety content so every language matches your source.

Want a second set of eyes on your files before December 9? Contact our team to talk through a documentation review.

Frequently asked questions

When does the new EU Product Liability Directive apply?

It applies to products placed on the EU market or put into service after December 9, 2026. EU countries must pass national laws by that date. Products placed on the market earlier stay under the old rules.

Does the directive affect US manufacturers?

It can. The rules follow the product into the EU market. If you sell to EU customers, through distributors, or through online marketplaces, your products may be covered. Importers and authorized representatives may carry liability when the maker is outside the EU. They will likely ask you for documents.

Is software covered?

Yes. The directive treats software as a product. That includes stand-alone software and software inside hardware. A maker can be liable for harm from a faulty update or from failing to provide a needed security patch.

Which documents should we keep?

Keep manuals and warnings, risk assessments, test reports, software version and update logs, revision history, translations, service documents, and complaint records. Make sure you can link each document to the product models and serial ranges it covers.

How long should we keep records?

Claims can generally be brought up to 10 years after a product is placed on the market. Some cases of latent injury can run longer. Ask your legal counsel to set a retention period for your products.

How is this different from the EU Machinery Regulation?

The Machinery Regulation sets product and documentation requirements before you sell. The Product Liability Directive deals with compensation after a product causes harm. Good documentation helps with both, so plan the two together.

This article is general information, not legal advice. Check dates and scope with qualified counsel. Further reading: Gibson Dunn client alert, Barnes & Thornburg alert, Wolf Theiss overview.