Software liability arrives with a 9 December 2026 deadline

The workload

Directive (EU) 2024/2853 replaces the EU's 1985 product liability regime and, for the first time, writes software explicitly into the definition of a product. Article 4(1) states that 'product' means all movables, and lists electricity, digital manufacturing files and software among them. A SaaS founder's workload under this directive is not a filing or a fee; it is understanding that the product now sits inside a strict-liability regime, where a claimant does not need to prove negligence, only that the product was defective and caused the type of damage the directive recognises.

What the documents show

Verified: the directive's own text states, in recital 20, that the destruction or corruption of data, such as files deleted from a hard drive, is now compensable, including the cost of recovering or restoring the data, though the recital also notes that no material loss arises automatically if the data can be recovered at no cost, for example from a backup. Verified: recital 18 carves out free and open-source software developed or supplied outside a commercial activity, on the reasoning that such software has not been placed on the market in the directive's sense; supplying it for a price changes that analysis. Verified: the same directive's Official Journal text sets the transposition date, at Article 22, as 9 December 2026, not 2 August 2026, a date some secondary commentary has repeated in error; the directive was done at Strasbourg on 23 October 2024 and, per recital 63, does not apply to products placed on the market before the transposition date.

The operating cost

The directive sets no fee; it sets a liability standard, and Member States' transposing statutes, not all yet written as of the retrieval date, will carry any procedural cost such as court fees. What is stated is the shift from a negligence standard to strict liability for defective products placed on the market after the transposition date, which insurers typically price into product-liability premiums, though no specific premium figure appears in either source.

The stop condition

Editorially, since the sources describe scope rather than an exit point: the obligation does not expire; it attaches to any covered software placed on the market after 9 December 2026 in a Member State that has transposed the directive on schedule, and continues for the life of that product. The nearer, checkable date is the transposition deadline itself, since national implementing statutes may add detail the directive's own text leaves open.

• Is the software supplied for a price or otherwise in a commercial context, which would take it outside the free and open-source carve-out?
• Does the product retain a means for the manufacturer to push updates, since the directive treats that as keeping the product within the manufacturer's control?
• Has the relevant Member State's transposing statute, due by 9 December 2026, actually been checked, since the directive leaves implementation detail to national law?

The directive's own recitals are specific about what changed and when; the most common error to correct is the transposition date itself, which the text gives as 9 December 2026.