The product. The evidence. The responsibility.Independent product liability resource
ProductLiability.helpProducts · Defects · Evidence

The topic library

A connected view
of product responsibility.

Browse the questions, evidence and relationships that shape a product-risk investigation.

Showing 61 to 75 of 142 topic guides

61 / What counts as a product?

Products Integrated Into Other Products: Classification and Boundaries

A product can remain a product after incorporation into another movable item or an immovable. Directive (EU) 2024/2853 expressly preserves that classification. Integration creates a need to identify the supplied item, the larger product, their manufacturers and the boundaries of the alleged damage.

Read guide
62 / What counts as a product?

Are Raw Materials Products Under EU Product Liability Law?

Raw materials are expressly included as products under Directive (EU) 2024/2853. Materials incorporated into finished goods can also be components. Batch identity, processing history and the alleged unsafe characteristic matter more than whether the material was sold in a consumer package.

Read guide
63 / Updates, cybersecurity and control

Automatic Updates and Product Liability

Automatic delivery changes who initiates an update, but actual installation, manufacturer control and the alleged safety consequence still require proof.

Read guide
64 / Updates, cybersecurity and control

Cybersecurity Incident Records as Liability Evidence

Security incident records can connect a vulnerability, product behaviour and harm. Preserve their meaning and limits rather than treating an alert as complete proof.

Read guide
65 / Updates, cybersecurity and control

Can a Defective Software Update Create Product Liability?

A software update can introduce a safety defect. A claim still needs the relevant product, responsible operator, covered damage and causal link.

Read guide
66 / Updates, cybersecurity and control

End-of-Support Decisions and Product Liability

A support deadline is a lifecycle decision, not an automatic end to every liability issue. Examine continuing control, safety expectations and applicable obligations.

Read guide
67 / Updates, cybersecurity and control

Failed Updates and Product Liability

A failed update may leave a product in an unsafe state. Identify the installation stage, resulting configuration and harm mechanism before attributing liability.

Read guide
68 / Updates, cybersecurity and control

Missing Security Updates and Product Liability

A missing update matters where it is necessary to maintain product safety and the statutory conditions, including manufacturer control, are satisfied.

Read guide
69 / Updates, cybersecurity and control

Optional Updates and Product Liability

An optional-update label does not resolve whether a release was necessary for safety, actually available or within manufacturer control.

Read guide
70 / Updates, cybersecurity and control

Security Patches and Product Liability

Security patches can correct an unsafe condition or introduce a different defect. Their purpose, actual deployment and effect need separate evidence.

Read guide
71 / Updates, cybersecurity and control

Software Update Evidence Checklist

Organise update evidence around identity, release state, manufacturer control, delivery, safety and harm. Record uncertainty rather than treating missing data as proof.

Read guide
72 / Updates, cybersecurity and control

Third-Party Updates and Manufacturer Responsibility

Third-party delivery does not automatically end manufacturer responsibility. Examine authorisation, integration and update capability for the particular change.

Read guide
73 / Updates, cybersecurity and control

Unsupported Software and Product Liability

Unsupported software describes a maintenance status. Liability depends on its actual safety condition, the relevant control relationship and harm caused by an alleged defect.

Read guide
74 / Updates, cybersecurity and control

Update Rollbacks and Liability Evidence

A rollback records a later change in product state. It can inform an investigation without proving that the withdrawn release caused the incident.

Read guide
75 / Defectiveness and expected safety

Can a Product Be Defective Even If It Works as Designed?

Matching a design or delivering an advertised function does not decide expected safety. A product may work as specified while exposing users to an unsafe risk.

Read guide