The EU definition extends beyond physical goods
A product is not limited to an object bought in a retail shop. Article 4 of Directive (EU) 2024/2853 begins with movable things and expressly includes electricity, digital manufacturing files, raw materials and software. It also recognises that a product can be integrated into or interconnected with another movable or an immovable. The definition is designed to support analysis of modern products containing physical and digital elements.
This guide explains that EU framework rather than proposing a universal definition for every jurisdiction. Other legal systems and other EU instruments can use different scope rules. Even within the Directive, classification is only the entry point. Commercial context, product dates, defectiveness, damage, causation and responsibility remain separate questions. Describing something as a product does not establish that an injured person has a successful claim.
Physical products retain their individual identities
Appliances, bicycles, machines and other movable goods remain central examples. Identify the particular model, unit and relevant configuration. Two visually identical devices can have different manufacturing batches or control software. The guide to physical products and product liability explains why serial numbers, condition photographs and supply records matter when an investigation begins with a tangible item.
An item does not lose all product relevance when fitted into a building or larger assembly. A pump incorporated into an installation can still require its own description. Distinguish the supplied article from installation work and surrounding construction. A defect in an item, a defect in its installation and an unsafe interaction can involve different facts, even where the visible outcome is the same.
Components can be tangible or intangible
Article 4 defines components broadly, covering tangible or intangible items, raw materials and related services integrated into or interconnected with a product. A battery, control program and qualifying remote service can therefore each require examination. The explanation of components as products shows how an item can retain its own product identity while also forming part of a finished product.
Record both identities instead of forcing the investigation to choose one legal object prematurely. A component may be alleged to have made the finished product unsafe, while the finished product's design or instructions may explain the interaction. Article 8 addresses product and component manufacturers under specified conditions, and Article 11 includes relevant exemptions. A component list identifies potential evidence sources without proving that every listed supplier is liable.
Software is expressly included
Software qualifies through an express reference in the product definition. It can be supplied separately, embedded in hardware or made available through a network. The Directive's recitals discuss operating systems, firmware, applications and AI systems among software examples. The absence of a physical disc or a separate consumer purchase does not itself exclude the software from product classification.
The dedicated software product liability guide owns the broader software liability discussion. For product mapping, identify the relevant release, build and configuration and distinguish it from the hardware and remote services with which it interacts. A label such as platform can conceal several supplied software components. Preserve what was actually installed rather than assuming a current download represents the incident version.
Manufacturing files have a specific definition
Digital manufacturing files are expressly included as products. Article 4 defines them through the functional information enabling automated machinery or tools to produce a tangible item. A file directing a 3D printer or automated machine tool can therefore require examination in its own right. The retained guide on digital manufacturing files explains the definition and the distinction between original design, conversion and actual machine input.
Digital files generally are not all products merely because they are downloadable. A document, picture or information source does not automatically become a digital manufacturing file because someone uses it when making an object. Its function and content matter. Preserve the file revision and production chain so an alleged geometry fault can be distinguished from unsuitable materials, machine settings or later modifications.
Electricity and raw materials are included too
Electricity is expressly part of the product definition, despite not resembling a packaged good. That classification does not turn every power interruption into a defective-product claim. An investigation still needs to describe the alleged unsafe supply characteristic, the affected equipment and the causal pathway. Household wiring, protective equipment and an appliance may present alternative or interacting explanations for an incident.
Raw materials are also expressly included, with gas and water identified as examples in the recitals. Materials incorporated into a finished article can additionally be components. Batch traceability and processing history are particularly important here. An unsafe finished item might result from a supplied material characteristic, unsuitable processing or a later change, so the classification should not pre-empt analysis of where the alleged unsafe condition originated.
Related services require a separate relationship analysis
The Directive does not treat every service associated with a product as a standalone product. Article 4 provides a specific related-service definition and includes qualifying related services among components. The existing connected products and related services guide explains that definition. Identify the relevant product functions and the service relationship rather than assuming every subscription, website or internet connection has the same legal status.
This distinction is particularly useful for a device combining local control software and remote processing. The local software can qualify as a product while a continuing service requires examination through the component relationship. The article on intangible components sets out why non-physical inputs need accurate descriptions. Executable code, ordinary content, data and a qualifying related service should not be collapsed into a single digital category.
Commercial activity and product dates remain boundaries
Article 4's market-supply definitions concern commercial activity and can include supply free of charge. A zero price is therefore not a complete scope answer. Article 2 separately excludes free and open-source software developed or supplied outside commercial activity. Examine the relevant actor and activity, particularly where a commercial product integrates components created by independent contributors.
Corrected Article 2(1) applies to products placed on the market or put into service after 8 December 2026. Article 21 preserves the predecessor Directive for earlier products within its stated transition rule. The 9 December 2026 transposition deadline is a distinct matter. Check the applicable national implementing law and the particular product chronology; the accident date alone does not select the governing regime.
Preserve what changes during an investigation
Repairs, resets and ordinary servicing can change both physical and digital evidence. Document the condition before intervention where safe and lawful, then record what changed and why. A later examination should be able to distinguish the incident state from damage created during emergency response or subsequent testing. Preservation does not require keeping a dangerous product in operation.
Record who holds the item or digital copy, how it was obtained and any limits on its reliability. A current source-code repository, a retained production sample and a recovered damaged unit provide different kinds of evidence. Clear provenance helps a later reviewer decide what each record can establish without treating every available copy as an exact representation of the product involved.
A product map supports the remaining legal questions
After classifying the relevant items, assess the alleged unsafe characteristic under Article 7 and the evidence of damage and causation under Article 10. Identify economic operators by their actual statutory roles under Article 8. Article 6's exclusions also make product boundaries important when separating damage to the defective item from injury or damage to other property. Neither a brand name nor a technical failure supplies every necessary answer.
The practical guide to identifying the relevant product in an investigation provides a way to record those facts. Preserve original identifiers, versions, relationships and changes, and state unresolved points clearly. A reliable map allows later findings to be updated when evidence improves, while avoiding an early assumption that the most visible device or business must explain the entire incident.
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, component and service relationship map
- Hardware identifiers and software build records
- Commercial supply and relevant market-date evidence
- Records of integration, authorisation and later changes
Product classification is an entry point. It does not establish a defect, recoverable damage or the identity of a liable actor.
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.
- Directive (EU) 2024/2853, consolidated text: Articles 2, 4, 6, 7, 8, 10, 11, 21, 22 ↗
- Official Journal corrigendum, 7 May 2026: Article 2(1) ↗
- Official Journal Directive (EU) 2024/2853, recital 13 and 16: digital scope and product categories ↗
Source register: corrected scope verified 16 October 2026. Article references identify the legal basis. No qualified legal review or national implementation status is claimed.