The product. The evidence. The responsibility.Independent product liability resource
ProductLiability.helpProducts · Defects · Evidence
Home / Topic library / Supplier Testing Records and Product Liability

Components and supply-chain liability

Supplier Testing Records and Product Liability

A supplier test report is only as useful as its link to the affected component, test method and operating conditions. Passing a test does not automatically establish legal safety; failing one does not establish every claim element.

A test result must answer a defined question

Supplier testing records can support or challenge an explanation of a defective component, but the meaning of a pass depends on what was tested. A dimensional check, electrical endurance test and finished-product safety test address different properties. Begin by identifying the alleged failure mechanism and asking whether the supplier's test could detect it. A report headed approved does not establish that every relevant risk was examined.

The component and supply-chain liability overview places testing alongside integration, actor responsibility and damage. Article 7 of Directive (EU) 2024/2853 assesses product defectiveness through all relevant circumstances. Tests can supply important evidence within that assessment. They do not replace the legal inquiry or establish causation merely because a supplier used a recognised laboratory or an impressive number of test cycles.

Identify the sample and its relationship to production

Check whether the tested item was a design prototype, routine production sample, returned component or unit recovered from the incident. Record part numbers, revisions, batch identifiers and selection methods. A prototype with different materials may support a design proposition without demonstrating the condition of a later production batch. A sample selected by the supplier may not represent every variation within the affected population.

Determine whether testing occurred before or after the relevant manufacturing change. A report can be valid for an earlier revision yet uninformative about a changed coating or firmware version. Where a supplier combines several reports into one certificate, obtain enough detail to identify which observations concern which product state. Sampling uncertainty should be described rather than hidden behind a single overall pass label.

Examine the method and acceptance criteria

Preserve the procedure, equipment, calibration information, environmental conditions and acceptance limits where relevant. Ask whether the test measured the property associated with the alleged defect. A connector may pass a basic continuity test while failing under vibration. An adhesive may meet initial strength requirements but degrade under the intended combination of temperature, moisture and load.

The specified limit also needs interpretation. A result just inside a procurement tolerance does not independently establish that the complete product provided the required safety. Conversely, a result outside a commercial tolerance may concern appearance rather than a safety characteristic. Explain how the measurement relates to the product's use, foreseeable interactions and alleged harm. This connects the supplier's data to a meaningful defectiveness question.

Distinguish component testing from integration testing

Suppliers often test components under conditions that differ from the finished product. A power unit tested on a laboratory bench may receive steadier ventilation than it receives inside a casing. A software component may pass its own unit tests while being used with incompatible timing assumptions. Identify which environmental or interface conditions were imposed by the product manufacturer.

Read both sides of the specification. Determine whether the supplier communicated operating limits and whether the integrator followed them. The guide to defective components in finished products examines the wider causal relationship. Testing records help establish one part of that relationship, including whether the alleged fault came from component manufacture, final-product design or the interaction between them.

Preserve negative results and later changes

An investigation needs failed tests, retests and deviations as well as the final acceptance certificate. A component may pass after rework or after the test method was altered. Record what changed and why. A repeat test can resolve a measurement error, but it can also obscure a reproducible fault if the original conditions are lost. Keep the sequence understandable.

Where supplier testing informed a design or production change, preserve the corresponding decision and affected range of products. Article 7 states that a better product appearing later does not, by itself, make an earlier product defective. A later improved test similarly does not automatically prove an earlier defect. It can still be relevant evidence if it explains a previously undetected failure mechanism or the scope of a production problem.

Assess independence and reproducibility proportionately

An external laboratory may provide useful independence, but its report still needs a defined sample and method. An internal supplier test can also be informative when its raw observations and conditions are documented. Evaluate the evidence rather than assigning reliability solely by organisation type. Where parties obtain conflicting results, compare product states and test setups before assuming one result must be dishonest or technically wrong.

A reproducible fault supports the proposed mechanism only to the extent that the reproduction matches relevant conditions. If a test applies stresses far beyond foreseeable use, explain why that method is informative. If the incident destroyed the original item, distinguish direct observations from tests on substitute samples. State what the results establish and which links, including the connection to the damage, remain inferential.

Keep testing evidence separate from procedural conclusions

Article 9 permits conditional disclosure of relevant evidence under court control, with proportionality and confidentiality safeguards. A focused request might concern a named component revision, test protocol or failed batch. It is more informative than assuming a claimant automatically receives every supplier laboratory record. Article 10's proof rules and rebuttable presumptions also have their own conditions.

A completed test assessment should identify the sample, method, relevant conditions, result, uncertainty and legal question informed. It should explain the relationship to the incident-time product and any competing cause. Supplier test records then become evidence a reader can evaluate, rather than an unexplained assurance that passing means no liability or that any failed measurement guarantees compensation.

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.

  • Sample identity and production revision
  • Test procedure, raw results and acceptance limits
  • Retest, deviation and integration test history

Independent educational information at EU Directive level. National implementing law and procedure require separate review.

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