Does the EU Product Liability Directive cover software? — AI Automation article by Rui Codex

Yes. The EU Product Liability Directive, formally Directive (EU) 2024/2853, classes software as a product, so a supplier can face liability for damage caused by a defect, including one introduced by an update. The rules apply to products placed on the market after the transposition date, so contracts, logs and update processes should be reviewed before then.

Key takeaways

  • Software falls within the scope of the directive, so software suppliers should treat themselves as potentially liable manufacturers.
  • A supplier that controls updates can face responsibility for defects introduced through those updates.
  • Courts can order disclosure of evidence, which makes release records, version histories and logs central to any dispute.
  • Contracts, engineering records and update processes should be reviewed before the new rules apply to products placed on the market.

Does the directive treat software as a product?

Yes. The directive's definition of a product includes software, so a defect in a software product can give rise to liability in much the same way as a defect in physical goods. The change matters most for suppliers whose revenue comes from licences, subscriptions or ongoing updates rather than a single sale.

Member States must transpose the rules into national law by 9 December 2026, and according to the official text the new regime applies to products placed on the market after that date, as stated in Directive (EU) 2024/2853 on EUR-Lex. Do not rely on summaries for the transitional wording; read the official text directly, because the boundary between old and new products decides which releases are exposed.

This article is general information and not legal or tax advice. Belgian implementation will follow the national transposition, so the Belgian text should be checked once it is published.

Who is responsible when an update causes damage?

The party that controls the update is the first to examine. Under the EU Product Liability Directive (Directive (EU) 2024/2853), a manufacturer that keeps the ability to change a product after it is placed on the market can be answerable for defects arising from those changes, including updates and upgrades. A defect introduced later does not, by itself, remove responsibility.

When the supplier keeps control

If your platform pushes updates centrally, you control the timing, content and rollback. Responsibility is hard to shift to the customer, because the customer never selected the change. The trade-off is that frequent small releases reduce known defects but multiply the points where a new defect can enter.

When the customer changes the system

Customers often configure, extend or connect software themselves. A change made by the customer, or by an integrator it hired, can weaken the link between the supplier's product and the damage. That defence works only when the records show who changed what and when, which is why configuration history matters as much as code history.

Hosted and installed software carry different exposure. A hosted service gives the supplier continuous control, while installed software on a customer's own servers means the supplier may hold fewer facts about the environment. Either way, the supplier should know which version runs where.

Can a claimant obtain a supplier's evidence?

Yes, in qualifying cases. The directive provides for a court to order a defendant to disclose relevant evidence, and it sets conditions under which a defect may be presumed where proof is excessively difficult for the claimant, as set out in Directive (EU) 2024/2853 on EUR-Lex.

In practice, a supplier's internal records can become the central evidence. Without release notes, test results and timestamped logs, the supplier may be unable to show what was delivered, when a fix was made or what the customer had configured.

Keeping records has trade-offs. Detailed logs help a defence but can hold personal data, so retention periods and access rights need design, not just storage. Short retention reduces that exposure but may leave no evidence when a claim arrives years later.

What should a software supplier do first?

Start with an inventory of what you place on the market and what you can change after delivery. Most gaps appear at the boundary between product teams and operations teams, so the inventory should include hosted services, mobile clients, connectors and third-party components.

  1. List every product version and the customer environments it runs in.
  2. Record which parts you can update remotely and who holds that control.
  3. Map each release to its test evidence, release notes and approval.
  4. Log configuration and integration changes with user and timestamp.
  5. Review contracts for liability caps, cooperation duties and evidence access.
Tip: Ask engineering to demonstrate a rollback of your last production release and show the records it generates. If the trail is incomplete, that gap is the first thing to fix.

Insurance and contracts come next. Check whether your liability cover reflects software defects and how your customer agreements allocate responsibility for configuration changes. Those documents should be reviewed with qualified counsel, while the engineering evidence is prepared by the technical team.

Hypothetical examples of update-related claims

Here are two hypothetical scenarios:

  • A scheduling module receives a central update that changes how break times are calculated. A customer's payroll export is wrong for a period, and the supplier must show whether the change was tested, approved and reversible. The release record and rollback procedure decide how quickly the facts can be established.
  • A connector between a stock system and a webshop is updated to a new field mapping. Stock levels then display incorrectly, and the customer's integrator had edited the mapping shortly before. The configuration history becomes the key evidence, because it separates the supplier's change from the customer's.

Neither scenario describes a real client. Both show why the same records serve the supplier's own release process and any later dispute, so they should be built into daily engineering work rather than assembled after a complaint.

Where do common approaches fail?

Most approaches work until the moment someone needs the evidence. The table compares common measures on qualitative criteria, so you can see where each is strong and where it breaks down.

ApproachStrengthWhere it fails
Contract liability capsSets expectations between the partiesDoes not bind injured third parties and does not replace good records
Detailed loggingSupports a defence with timestamped factsCreates personal data that must be governed and kept only as long as needed
Frequent small releasesShortens the time a known defect stays liveMultiplies the number of changes that each need evidence
Reliance on third-party componentsSpeeds up deliveryLeaves the supplier answering for parts it did not write unless the chain of responsibility is documented

The pattern is consistent. Each measure is useful, but none removes the need for an engineering record that can be produced quickly and explained plainly.

How can Rui Codex help with this work?

Rui Codex provides technical implementation support for software suppliers and their customers, including update pipelines, logging design and integrations between systems. It does not provide legal, tax or compliance advice, audits or certification, so the legal reading of the directive belongs with qualified counsel.

Rui Codex is led by a founder with 200+ projects delivered. Its services include custom software development, system integrations and technical measures for AI systems. Published project descriptions are in the case studies section, which shows what each project covered.

Frequently Asked Questions

Is standalone software covered by the new directive?

Yes, standalone software can fall within the directive because its definition of a product includes software. Whether a specific product is covered depends on the facts and on the national law that transposes the directive, so suppliers should read the official text against their own product range. Keep version records that show when each product was placed on the market.

Can a supplier still be liable after shipping a fix?

Possibly, yes. A fix does not automatically end responsibility for a defect that existed when the product was placed on the market, and a claimant can still rely on the period before the fix. Records showing when a defect was introduced and when it was corrected are therefore essential to any defence.

Which records should a supplier keep for a product claim?

Keep release notes, version histories, test results, configuration records and incident logs, each with a clear timestamp and an owner. Set retention periods in a written schedule that also covers personal data held in logs. Those records show what was delivered, when it changed and who approved it, which is the evidence a court would look for first.

Does Rui Codex give legal advice on the directive?

No. Rui Codex provides technical implementation support, such as update pipelines, logging design and system integrations, and it does not give legal, tax or compliance advice, audits or certification. A supplier should involve qualified counsel to interpret how the directive applies to its contracts and products.

Conclusion

The directive makes software suppliers answerable for how they build, ship and update software, not only for what they sold at the start. Suppliers do not need to wait for national transposition to act. Start with an inventory, tighten control over updates and keep records that show what changed and when. Where the engineering work is complex, a project consultation can map the technical side while your counsel handles the legal reading. Request a project consultation at Rui Codex or email info@ruicodex.com to discuss your project.

Sources

Tags: EU Product Liability Directive software liability software updates GDPR compliant software software development company Belgium system integration Belgium AI automation Belgium compliance engineering

Need Help Implementing This?

Our team can help you put these insights into practice. From AI automation to custom software development, we build solutions that deliver real results.

Send a project request