Your software causes damage: who pays?

Your software causes damage: who pays?

Updated on 21 November 2026.

In short: from 9 December 2026, software, an app or an AI system is a product, just like a toaster. If it is defective and injures someone or damages their private property, its manufacturer pays, even without fault, and no contract can exempt it. Your business is concerned if it develops, sells under its own brand, imports from outside the EU or modifies products that contain software. If you are only a user, the new rule does little for you: your business property and business data are excluded. Two checks are needed before the end of the year: your role in the supply chain, and your contracts and insurance.

What changes on 9 December 2026

Since 1985, a simple European rule has protected victims: if a defective product causes damage, its manufacturer compensates, without the victim having to prove fault. This is called strict or no-fault liability. The victim only has to show the defect, the damage and the link between the two.

The rule was designed for objects: a boiler that explodes, a toy that injures. It left a gaping hole: software. Nobody really knew whether an app or firmware (the program built into a device) was a "product".

Directive (EU) 2024/2853, published on 18 November 2024, closes that hole. It replaces the 1985 directive for all products placed on the market or put into service after 9 December 2026. The points that matter to a business owner:

  • Software is a product, whether installed on a device, accessed online or sold as a subscription (the text mentions "software as a service"). AI systems are explicitly covered, and their developers are manufacturers.
  • An AI that learns remains its manufacturer's responsibility: when judging a defect, the court takes into account the product's ability to "continue to learn" after it has been sold.
  • Updates count. A manufacturer can no longer say "the defect appeared after the sale" if it comes from an update, or from the lack of a security update it controlled.
  • Cybersecurity is part of the definition of a defect: cybersecurity requirements relevant to safety are among the criteria.
  • Proof becomes easier for the victim. The court can order the company to disclose its technical documents, and presume a defect when the product is too complex to explain (the text mentions machine learning).
  • Covered damage is wider: medically recognised harm to psychological health, destruction or corruption of private data. The €500 threshold that the old directive allowed for property damage disappears.
  • No clause can limit this liability towards the victim (Article 15). Terms and conditions saying "we accept no liability" are worthless against it.

What does not change: the victim has three years to act from the moment they know of the damage, the defect and the liable party, and in any case no more than ten years after the product was placed on the market (twenty-five years for a personal injury that develops slowly).

And in Belgium?

The directive must be transposed by 9 December 2026, and it leaves Member States almost no leeway: it is a "maximum" harmonisation, neither stricter nor more lenient. On 16 October 2026 the government tabled a bill amending the Civil Code and adding an Article 877/1 to the Judicial Code (Chamber document 56K1784). The Justice Committee adopted its articles on 13 November; at the time of writing, the plenary vote has not yet taken place. The timetable is tight, but the content is known: it is that of the directive.

Is your business concerned?

The directive targets "economic operators". The question is therefore not "do you use software?" but "what role do you play in placing it on the market?".

Your situation Your role under the directive What it means
You develop and sell software, an app, an online service, an AI system Manufacturer Liable first
You sell under your own name or brand a product made by someone else (white label) Manufacturer Liable as if you had made it
You buy outside the EU (China, United States, United Kingdom) and resell in Belgium Importer Liable if the manufacturer is not established in the EU
You "substantially" modify a product (new functions, replaced firmware, changed risk profile) and then resell it Manufacturer of the modified product Liable for what you changed
You simply resell (shop, webshop) Distributor Liable only if you do not name the European manufacturer or importer within one month
You use software for your work Potential victim Little protection: see below

A few useful details:

Free and open-source software is not covered if it is developed or supplied outside a commercial activity. A company that sells open-source software, or supplies it in exchange for personal data, is covered again.

Small software publishers keep some protection. A micro or small enterprise that supplies a software component to a manufacturer can agree by contract that this manufacturer will not seek recourse against it (Article 12). The victim will always be compensated by the manufacturer of the complete product.

An IT integrator is rarely a manufacturer. Installing and configuring software for a client, within the framework set by the publisher, is in principle not a substantial modification. The line is crossed when you change its functions or its safety level, then put it back on the market.

As a user: why the directive does little for you

This is the point most summaries miss. The directive only gives a right to compensation to natural persons, and it excludes two things that are essential for a business:

  • damage to property used exclusively for professional purposes;
  • destruction or corruption of data used, even partly, for professional purposes.

In practice, if an accounting package corrupts your client files, or a faulty update locks your cash register, the directive will not help you. Your remedy remains the contract with your supplier, with its caps and exclusions, which in principle remain valid between businesses. For an online service, the supplier's liability is often capped, for example at the amount paid over a given period: read that clause before an incident forces you to.

Your employees, on the other hand, are natural persons: if they are injured by defective equipment, or their private property is damaged, the directive applies to them.

One condition not to overlook: install updates. The directive states that the manufacturer is in principle not liable for a defect that a security update would have fixed if it is the owner who did not install it. Letting updates pile up means losing an argument on the day a device causes damage. It also states that it does not require any manufacturer to supply updates: that obligation will come from another text, the Cyber Resilience Act (see below).

An illustrative case

An invented case, but built from common situations. A six-person business in Liège sells online, under its own brand, smart plugs and thermostats made in Asia, controlled by an app supplied by the manufacturer. In February 2027, an app update disrupts some thermostats, which stay stuck at full power. In one flat, an electric radiator overheats and damages a parquet floor and a sofa.

Before 9 December 2026, the customer would have had to fight to prove that an app is a product, and the €500 threshold could have applied. Under the new rules:

  • the business is the manufacturer, since the thermostat carries its brand;
  • the defect comes from an update under the manufacturer's control: it cannot argue that it appeared after the sale;
  • its terms and conditions, which exclude all liability, are worthless against the customer;
  • it can turn against the Asian manufacturer, if its contract provides for it and if it manages to make it pay.

The thermostat sold in 2025 stays under the old regime. The one sold in January 2027 falls under the new one.

In practice: three options

Option Cost Time Risk
Do nothing None today None You discover your role as manufacturer or importer on the day of a claim, with insurance that may not cover software
Review it yourself A few hours Half a day for the inventory, plus the meeting with your broker Fine for a business selling only one or two products; risk of missing a role (white label, direct import)
Get support Depends on the size of your catalogue One or two meetings Full inventory of products and software, supplier contracts reviewed with your lawyer, precise questions for your insurer

In every case, four steps are enough to start:

  1. List what you place on the market: products, apps, online services, products under your brand, imports from outside the EU.
  2. Keep track of your suppliers: name and European address of the manufacturer or importer for each product. A distributor who can name them within a month is not liable.
  3. Call your broker: does your product liability insurance cover software, updates, damage to data? Ask for the answer in writing.
  4. Review your purchase contracts: do they provide for recourse against your non-EU supplier, a warranty on updates, a support period?

For your IT person

Time scope. The criterion is the date each product was placed on the market or put into service (Article 2(1)). For continuously updated software, the directive reasons in terms of "manufacturer's control": as long as it supplies or authorises updates, the product remains under its control, and the defect is assessed at the moment it leaves that control (Article 7(2)(e)). An update that substantially modifies the product makes it a new product, with a new ten-year period (Article 17(1)(b)).

What is not a product. "Information" is not a product: the content of files, e-books or "the mere source code" of software are not covered (recital 13). An AI model running within a service, however, is.

Related services. A digital service without which the product cannot perform one of its functions (a thermostat's cloud, for example) is a component of the product (Article 4, points 3 and 4). Its failure makes the product's manufacturer liable.

Evidence. Article 9: disclosure of relevant evidence, limited to what is necessary and proportionate, with protection of trade secrets. Article 10: defect is presumed if the defendant fails to disclose, if the product does not meet a mandatory safety requirement, or in case of obvious malfunction; a presumption is also possible where technical complexity creates excessive difficulty.

Exemptions. The "development risk" defence (Article 11(1)(e)) remains: the manufacturer escapes liability if it proves that the objective state of knowledge did not allow the defect to be discovered. But the "defect appeared after placing on the market" exemption does not apply to a related service, software or its updates, the lack of a necessary security update or a substantial modification, where these are within the manufacturer's control (Article 11(2)).

What comes next. Since 11 September 2026, the Cyber Resilience Act (Regulation (EU) 2024/2847) has required manufacturers of products with digital elements to report actively exploited vulnerabilities and severe incidents; its other obligations, including vulnerability handling throughout the support period, apply from 11 December 2027. A breach of the CRA will weigh in the assessment of a defect under the directive. As for the specific directive on civil liability for AI, proposed in 2022, the Commission formally withdrew it in October 2025: for AI, the product liability directive is now the reference text, alongside general liability law.

For the regulatory side of AI (AI Act obligations, timetable), see our article on the AI Act and SMEs. For day-to-day update discipline, ten pitfalls of an SME's PC fleet and IT monitoring.

Test yourself

Under the new European directive on defective products, applicable from 9 December 2026, is software sold as an online subscription (SaaS) a product?

Show the answer

Answer: Yes, software is a product however it is supplied

Recital 13 of Directive (EU) 2024/2853 covers software that is installed, accessed online or supplied as a service.

A Belgian SME sells smart thermostats made in Asia under its own brand. What is its role under the 2024 European directive on defective products?

Show the answer

Answer: Manufacturer, since it puts its name or brand on the product

Directive (EU) 2024/2853 treats as a manufacturer anyone who presents themselves as such by putting their name or brand on the product.

A defective management software corrupts an SME's client files. Does the 2024 European directive on defective products entitle it to compensation?

Show the answer

Answer: No, data used for professional purposes is excluded; the contract is the remedy

The directive only protects natural persons and excludes data used, even partly, for professional purposes.

This article explains general rules; it does not replace a lawyer's advice on your situation.

Sources

Belgian Chamber of Representatives. (2026). Projet de loi modifiant les dispositions du Code civil relatives à la responsabilité du fait des produits défectueux et insérant l'article 877/1 dans le Code judiciaire (DOC 56 1784). https://www.lachambre.be/kvvcr/showpage.cfm?section=/flwb&language=fr&cfm=/site/wwwcfm/flwb/flwbn.cfm?legislist=legisnr&dossierID=1784

Council Directive 85/374/EEC of 25 July 1985 on the approximation of the laws, regulations and administrative provisions of the Member States concerning liability for defective products. (1985). Official Journal of the European Communities. https://eur-lex.europa.eu/eli/dir/1985/374/oj

Directive (EU) 2024/2853 of the European Parliament and of the Council of 23 October 2024 on liability for defective products and repealing Council Directive 85/374/EEC. (2024). Official Journal of the European Union, L 2024/2853. https://eur-lex.europa.eu/eli/dir/2024/2853/oj

European Commission. (2025, 6 October). Withdrawal of Commission proposals (C/2025/5423). Official Journal of the European Union. https://eur-lex.europa.eu/eli/C/2025/5423/oj

European Commission. (n.d.). Cyber Resilience Act: reporting obligations. Shaping Europe's digital future. https://digital-strategy.ec.europa.eu/en/policies/cra-reporting

Regulation (EU) 2024/2847 of the European Parliament and of the Council of 23 October 2024 on horizontal cybersecurity requirements for products with digital elements (Cyber Resilience Act). (2024). Official Journal of the European Union. https://eur-lex.europa.eu/eli/reg/2024/2847/oj

← Back to articles