Skip to main content

Merchant radar

Merchant radar · E-commerce

New product liability rules, software included

Deadline
22 days to go
Status
adopted
Date
confirmed
Affects
manufacturers, importers, marketplaces
Updated on

For products placed on the market or put into service after 8 December 2026, manufacturers, importers and, as a fallback, distributors are liable for defective products without proof of fault.

In short

  • What: Under no-fault liability, people harmed by a defective product, software included, can claim compensation.
  • Who: Manufacturers and importers; distributors, platforms and fulfilment service providers as fallbacks. Selling goods you substantially modified without the manufacturer's consent makes you the manufacturer.
  • Which products: Goods, electricity, digital manufacturing files and software, including cloud software, except free and open-source software outside a commercial activity.
  • When: Products placed on the market or put into service after 8 December 2026; older products stay under the previous law.
  • What to check: Your role per product, and whether you can name its manufacturer and importer.

Does this apply to me?

The new German Act names these roles.

Roles and liability
RoleLiable?When exactly
Manufacturer, including makers of software and of digital manufacturing files for 3D printers or milling machinesYes, where a defect in its product causes damage.Under the new Act and the Directive, software and digital manufacturing files count as products. Free and open-source software developed or supplied outside the course of a commercial activity is excluded. Recital 16 of the Directive names drills, lathes, mills and 3D printers among the machines such files can control.
Importer or authorised representativeYes, like the manufacturer.Under the new Act, this applies where the manufacturer is based outside the EU. Under the Directive, the manufacturer remains liable as well. An authorised representative is a person based in the EU with a written mandate from the manufacturer to carry out specified tasks on the manufacturer's behalf.
Fulfilment service providerOnly as a fallback.Under the new Act, a fulfilment service provider is liable like the manufacturer where there is no importer based in the EU and no authorised representative. The term covers anyone who, in the course of a commercial activity, offers at least two of four services for a product they do not own: warehousing, packaging, addressing and dispatch. Postal services and freight transport services are excluded.
DistributorOnly as a fallback.Under the new Act, a distributor is anyone in the supply chain, other than the manufacturer and the importer, who makes a product available on the market. A distributor is liable like the manufacturer only where no manufacturer, importer, authorised representative or fulfilment service provider based in the EU can be identified. There is a further condition: the injured person asks the distributor to name one of them or its own supplier, and the distributor fails to do so within one month of receiving the request. Article 8(3) of the Directive sets the same one-month period.
Provider of an online platform, such as a marketplaceOnly as a fallback, like a distributor.Under section 13 of the new Act, this fallback liability applies only where the other conditions in that section are also met. The term "online platform" has the meaning given in the Digital Services Act.
Anyone who substantially modifies a productYes, as the manufacturer of the modified product.Under the new Act, three conditions apply. The modification comes after the product was placed on the market or put into service. It is made without the manufacturer's consent. The modified product is then made available on the market or put into service. Article 8(2) of the Directive words the consent condition as "outside the manufacturer's control". Under section 9(4) of the new Act, the person who made the modification is not liable for defects in parts the modification did not affect.

The new Act covers injury to body or health, including medically recognised harm to psychological health. Damaged property counts too, except the defective product itself and property used exclusively for professional purposes. Destroyed or corrupted data are included, unless used for professional purposes. Under the previous Act, injured parties bear the first 500 euros of property damage. The Government bill's explanatory memorandum says the Directive removes this excess and the cap on liability for personal injury.

An example

A hypothetical example: an online shop sells new and used goods.

Who is liable, case by case
CaseWho is liableBasis
The shop sells branded goods from a manufacturer based in the EU.The manufacturer. The shop is a distributor and liable only as a fallback.Under the new Act, a distributor is liable only where no EU-based manufacturer, importer, authorised representative or fulfilment service provider can be identified. Even then, the distributor is liable only if it fails to name one of them, or its own supplier, within one month of the injured person's request.
The shop buys directly from a manufacturer outside the EU and imports the goods itself.The manufacturer and, alongside it, the importer. Whether the shop is itself the importer is a question for its legal adviser.Under section 10 of the new Act, the importer is liable like the manufacturer. Under Article 8(1) of the Directive, the manufacturer remains liable as well.
The shop remanufactures used devices and sells them.The shop counts as the manufacturer if it substantially modifies the devices without the original manufacturer's consent.The European Commission's information page on liability for defective products gives remanufacturing as an example of a substantial modification. Recital 39 of the Directive says that a product which is substantially modified and then made available on the market or put into service is considered a new product.
The shop reworks old furniture or clothing (upcycling) and sells the results.The shop counts as the manufacturer if it substantially modifies the item without the original manufacturer's consent.The Government bill gives upcycling as an example. Reworking can change a product's risk profile so that it counts as a new product. In the bill's view, it is then appropriate for whoever places the reworked product on the market to be liable as its manufacturer.
The shop repairs or services customers' devices without substantially modifying them.According to the official papers on the bill, the shop is not liable for that work under the Product Liability Act.The explanatory memorandum to the Government bill (Bundestag printed paper 21/4297, in German) says that repairs and other work that do not involve substantial modification create no liability under the Act. In its reply to the opinion of the Bundesrat (the chamber representing the federal states), the Federal Government states that merely installing, repairing or servicing a product creates no such liability.

A second example: a service provider maintains open-source shop software its original manufacturer no longer updates. The provider adapts the core code to a new PHP version and supplies the software only to paying customers. The table lists only what the sources say.

What the sources say
QuestionWhat the sources saySource
Does the open-source exception still apply?Under the new Act, only free and open-source software developed or supplied outside the course of a commercial activity is excluded. Recital 14 of the Directive explains that such software is by definition not placed on the market. Providing it on open repositories should not count as making it available on the market, unless this happens in the course of a commercial activity. Recital 14 and the explanatory memorandum both treat supplying software for a price as a commercial activity. The Cyber Resilience Act is a different law: an EU Regulation on the cybersecurity of products with digital elements. The Commission's guidance on that Regulation says that software under a free and open-source licence whose source code is shared only with paying customers is not free and open-source software for the purposes of that Regulation. The guidance is a draft: it is not binding and not yet formally adopted.Section 2(1) of the new Act; recital 14 of the Directive; explanatory memorandum on section 2; Commission guidance on the Cyber Resilience Act (in English, not binding)
Is the change substantial?Under the new Act, this is decided by German and EU product safety law. Where that law sets no standard, a change is substantial only if it meets two conditions. First, it alters the product's original performance, purpose or type in a way the manufacturer's original risk assessment did not foresee. Second, it changes the nature of the hazard, creates a new hazard or raises the level of risk. According to the explanatory memorandum, "hazard" means the risk that the product will cause harm to rights and legally protected interests. The Federal Government's reply adds that a change can create liability as a substantial modification only if it changes the hazard or the level of risk. Recital 40 says that changes made through software updates should be judged by the same principles, and the memorandum agrees. Where an update substantially modifies a product, the recital says the product should count as made available on the market or put into service when the change is made. The memorandum and the Federal Government say that repair and maintenance without substantial modification create no liability under the Act. The Commission's Blue Guide, which is not binding, says software updates could be treated like maintenance, provided they do not change the product in a way that may affect its compliance with the applicable requirements.Section 5(2) of the new Act; recital 40 of the Directive; explanatory memorandum and Federal Government's reply on section 5; Blue Guide, section 2.1 (not binding)
Does passing the software on to customers count as making it available?Under the new Act, making available on the market means any supply of a product for distribution, consumption or use on the EU market in the course of a commercial activity, whether in return for payment or free of charge.Section 6(2) of the new Act
What about the original manufacturer?Under the Directive, a product is also within the manufacturer's control where the manufacturer is able to supply software updates or upgrades, itself or through a third party. Recital 51 says the Directive obliges no one to supply updates or upgrades. Under the same recital, a manufacturer should still not escape liability for a defect caused by its failure to supply the security updates needed, unless supplying or installing the software is beyond its control. Under the new Act, the person who substantially modified a product is not liable for defects in parts the modification did not affect. That exemption does not cover the original manufacturer.Article 4(5) and recital 51 of the Directive; section 9(4) of the new Act

Whether these points make someone a manufacturer in a given case is for a legal adviser to judge.

The rules in detail

The Product Liability Directive (EU) 2024/2853 repeals its predecessor. Following a corrigendum, the Directive applies to products placed on the market or put into service after 8 December 2026. Germany's Act modernising product liability law (in German) contains a new Product Liability Act. Apart from a few provisions, it enters into force on 9 December 2026. Products placed on the market or put into service up to and including 8 December 2026 stay under the previous Act.

Under the new Act, placing on the market means first making a product available on the EU market. The Commission's non-binding Blue Guide to EU product rules (in German) says each individual product can be placed on the market only once.

The table covers software.

Software, updates and defects
TopicWhat appliesSource
Software as a productRecital 13 of the Directive makes clear that software is a product for the purposes of no-fault liability, however it is supplied. It may be stored on a device, accessed through a communication network or the cloud, or supplied as software-as-a-service. The recital's examples include operating systems, computer programs, applications and AI systems. According to the explanatory memorandum, neither the Directive nor the German bill defines software.Recital 13 of the Directive; explanatory memorandum on section 2
What is not a productRecital 13 says that information is not a product. The rules should therefore not apply to the content of media files or e-books, or to the mere source code of software. Neither the Directive nor the memorandum says where mere source code ends and software begins.Recital 13 of the Directive
The manufacturer's controlUnder the new Act, a product is within the manufacturer's control where the manufacturer integrates, connects or supplies a component, including a software update or upgrade, or modifies the product. The same applies where a third party does so with the manufacturer's consent. Under recital 18 of the Directive, a manufacturer should not count as consenting to integration or connection merely because it makes this technically possible, recommends certain brands or does not prohibit related services or components.Section 8(2) of the new Act; recital 18 of the Directive
Later defects caused by softwareUnder the new Act, a manufacturer that has kept control of the product cannot rely on the defence that the defect probably did not exist when the product was placed on the market. This applies where the defect is caused, among other things, by software, including updates or upgrades, by missing software updates or upgrades needed to keep the product safe, or by a substantial modification. Recital 50 says manufacturers should remain liable for later defects that come from software under their control.Section 9(2) of the new Act; recital 50 of the Directive
CybersecurityUnder the new Act, whether a product is defective is judged, among other things, by the relevant product safety requirements. These include safety-relevant cybersecurity requirements. Recital 32 adds that a product can also be found defective because of a cybersecurity vulnerability.Section 7 of the new Act; recital 32 of the Directive
Recourse against small software makersUnder Article 12(2) of the Directive, a manufacturer that builds third-party software into its product as a component cannot recover compensation from the maker of the defective software if two conditions are met. First, the software's maker was a microenterprise or small enterprise when it placed the software on the market. Second, both sides agreed by contract to waive recourse. A small enterprise has fewer than 50 staff and an annual turnover or balance sheet total of no more than 10 million euros. A microenterprise has fewer than 10 staff and an annual turnover or balance sheet total of no more than 2 million euros. Recital 54 says such agreements should never limit or exclude liability towards the injured person.Article 12(2) and recital 54 of the Directive; Recommendation 2003/361/EC

Both size categories come from the Commission's SME Recommendation 2003/361/EC.

What to check

  • Which role do you play for each product: manufacturer, importer, distributor, fulfilment service provider or provider of an online platform?
  • Can you trace the manufacturer and importer of every item? Could you name them, or your own supplier, within one month of a request?
  • Do you offer at least two of the four fulfilment services (warehousing, packaging, addressing, dispatch) for goods you do not own? Under the new Act, postal and freight transport services are excluded.
  • Do you modify products before sale without the manufacturer's consent, for example by remanufacturing, upcycling, conversion or software changes?
  • Do you supply software or updates for a price, including as an online service? Does the exception for free and open-source software outside a commercial activity apply?
  • Was each product placed on the market or put into service after 8 December 2026? Those placed on the market or put into service up to and including that date stay under the previous Act.

Sources

  1. Berichtigung der Richtlinie (EU) 2024/2853, ABl. L, 2026/90364 vom 7.5.2026 (opens in a new tab)

    Amt für Veröffentlichungen der EU (EUR-Lex/Cellar) accessed

  2. Produkthaftungsgesetz (alte Fassung), § 11 Selbstbeteiligung bei Sachbeschädigung (opens in a new tab)

    Bundesministerium der Justiz und für Verbraucherschutz, gesetze-im-internet.de accessed

  3. Liability for defective products (opens in a new tab)

    Europäische Kommission, GD Binnenmarkt, Industrie, Unternehmertum und KMU accessed

History

  1. The German Act containing the new Product Liability Act enters into force, apart from a few provisions, and the old Directive 85/374/EEC is repealed.
  2. The Federal Law Gazette issue containing the German Act modernising product liability law (2026 I No. 321) was published.
  3. The German Act modernising product liability law (Federal Law Gazette 2026 I No. 321) is dated this day.
  4. The Bundestag's Committee on Legal Affairs and Consumer Protection published its recommendation and report on the Government bill as printed paper 21/8429.
  5. Following a corrigendum published on this day, the Directive applies to products placed on the market or put into service after 8 December 2026.
  6. The Government bill to modernise product liability law was published as Bundestag printed paper 21/4297.
  7. Directive (EU) 2024/2853 on liability for defective products was published in the Official Journal of the EU.

Glossary terms

Share on LinkedIn

Guidance, not legal advice: we name the document, the deadline and the primary source, and link to the other relevant sources. What applies in your case is for your legal adviser to judge.

Questions about implementing it in your shop?

We look at what the obligation means technically for your shop system and tell you plainly whether there is anything to build.

Search the website

Popular topics

All results