The product. The evidence. The responsibility.Independent product liability resource
ProductLiability.helpProducts · Defects · Evidence
Home / Topic library / Manufacturer Liability Explained

Economic operators and responsibility

Manufacturer Liability Explained

Manufacturers include producers, developers, commissioning businesses and businesses presenting a product as their own. Liability still requires the applicable defective-product conditions.

Manufacturer status reaches beyond production

A manufacturer can be responsible under Directive (EU) 2024/2853 without personally operating the factory that assembled the product. Article 4 includes development, manufacture and production, arranging design or manufacture, presenting a product as one's own through branding, and production for one's own use. Those categories require examination of what a particular legal entity actually did. The everyday distinction between a brand and a factory does not settle the statutory question.

Article 8(1)(a) places the manufacturer of a defective product within the liability framework. That role does not dispense with the remaining conditions of the claim. The product must fall within the applicable framework, there must be a legally relevant safety defect, covered damage and a causal connection. A malfunction, commercial disappointment or complaint about service is not by itself proof of a compensation claim.

Match the entity to the affected product

Begin with the model, batch, serial number and incident-time software version. Then identify the legal entity named in packaging, instructions, declarations, release documentation and purchase records. A brand may be owned by one company, licensed by another and used by a third selling entity. Record which document connects each business to the specific product instead of assigning responsibility to a corporate group as a whole.

The economic operator framework helps place the manufacturer alongside importers, component suppliers and other relevant actors. Preserve historical evidence because current branding may differ from the branding used when the affected unit was supplied. Where names conflict, retain both records and explain the conflict. A changed company name, acquisition or common registered address should lead to further identity research rather than an assumed transfer of every relevant legal role.

Commissioned and own-brand products

A business that has a product designed or manufactured can satisfy Article 4 even where an independent contractor performs the physical work. A separate branch of the definition concerns presenting oneself as manufacturer through a name, trademark or other distinguishing features on the product. These routes may overlap, but it remains useful to identify the evidence for each. A purchase order and the finished product's presentation answer different questions.

A retailer's name on a receipt alone should not be confused with branding that presents the item as its own manufactured product. Compare the product, packaging, manual, listing and supply agreement. The dedicated discussion of own-brand manufacturer liability examines that evidence more closely. Contractual statements describing a supplier as solely responsible may inform internal allocation; they do not conclusively override the Directive's definition or remove the injured person's statutory rights.

Components and manufacturer control

A finished product manufacturer cannot answer every component allegation merely by naming an outside supplier. Article 8 also covers damage caused by a defective component integrated into or interconnected with the product within that manufacturer's control. The separate component manufacturer route has its own conditions, including that the component caused the product to be defective. Both the component and integration history therefore need investigation.

Article 4 includes authorisation or consent to specified third-party actions within manufacturer control and also retained ability to supply software updates or upgrades. Technical compatibility alone should not be treated as permission for every later addition. Preserve integration approvals, release arrangements and product representations. An authorised software dependency may present a different responsibility question from an unapproved alteration installed by an unrelated third party after the product left the relevant manufacturer's control.

Defences require a particular factual basis

Article 11 provides exemptions that an economic operator must prove where applicable. They include not having placed the product on the market or put it into service, specified timing of defectiveness, compliance with legal requirements and the objective state of scientific and technical knowledge. These are defined legal conditions, rather than a general defence that reasonable care was taken. Strict liability and negligence ask different questions.

The timing exemption has important limits when defectiveness results from a related service, software, missing safety updates or substantial modification within manufacturer control. Consequently, a delivery date alone may not resolve responsibility for a later software-related defect. Keep the alleged defect mechanism precise and distinguish the condition at initial supply from later changes. A new release that remedies a vulnerability is relevant evidence, but it does not automatically establish liability for every earlier version.

Dates and external contracts

The corrected Article 2 scope concerns products placed on the market or put into service after 8 December 2026; the national transposition deadline is 9 December 2026. Establish the affected product's relevant dates and examine implementing national law. The date someone discovers a manufacturer or reports an accident should not be substituted for the market-placement inquiry. Older products require consideration of the preceding framework and applicable national rules.

Manufacturer liability towards the injured person must also be kept separate from supply-chain recovery. Under Article 15, contractual provisions cannot exclude or limit Directive liability in relation to that person. An indemnity between businesses may nevertheless matter to a separate dispute about allocation, subject to the applicable law.

What a useful manufacturer file contains

A mature investigation connects the alleged defect to a traceable product and a traceable manufacturer. Keep design responsibility, actual production, commissioning and brand presentation as separate entries, even where the same company performs all four functions. Add component and update-control documents where relevant. Preserve conflicting records and their dates so that later reviewers can understand why an initial identification changed.

For example, a business commissions a connected appliance and sells it under its trademark while a contractor builds the hardware. Both relationships need examination, together with the software integration history. Finding the contractor's invoice does not erase the commissioning or branding evidence. Conversely, establishing the brand business's manufacturer status does not prove what caused the injury. Role identification and technical causation should advance together, with conclusions limited to the evidence available.

Records that help the review

Use the following as a practical starting point. Select and preserve records appropriate to the product, incident and applicable procedure.

  • Product model, batch and incident-time software release
  • Legal producer, commissioning and brand identities
  • Design contracts and component integration approvals
  • Update permissions and lifecycle change records

Potential manufacturer status does not dispense with proof of defect, covered damage and causation.

Primary sources and legal scope

This page explains the EU Directive framework. Check national implementing law, the corrected temporal scope and relevant procedure before applying it to a case.

    Source register: corrected scope verified 16 October 2026. Article references identify the legal basis. No qualified legal review or national implementation status is claimed.

    Continue the research