How do you document compliance for a product assembled from third-party tested components?

Default hero background
Uncategorized
Jason van de Zande

Document compliance for a product assembled from third party tested components by building one complete technical documentation file that links each component’s test evidence to the finished product’s design, intended use, and reasonably foreseeable misuse, then fills any gaps with product level risk assessment and verification. The goal is traceable, up to date EU product compliance documentation that market surveillance can review quickly.

This approach matters because component certificates rarely cover the exact final configuration, labeling, instructions, packaging, or combined hazards created during assembly. Under the General Product Safety Regulation (EU) 2023/988 (GPSR), you need evidence that the finished consumer product placed on the EU market is safe, not only that parts were tested.

The sections below explain what documentation you need, how to compile supplier evidence, and the common failure points for assembled products.

What compliance documentation is required when using third-party tested components?

You need EU product compliance documentation that proves the finished assembled product is safe and traceably supported by component compliance evidence, including supplier test reports, specifications, and your own product level assessment. Third party test reports help, but they must be relevant to your exact build, intended use, and labeling, and they must be organized for rapid access by authorities.

In practice, authorities and marketplaces expect a coherent set of records that answers three questions: what the product is, what hazards it can create, and what evidence shows those hazards are controlled. For assembled products, that means you document both the parts and the integration work you performed.

  • Product identification: model or SKU, photos or drawings, variants, and a clear description of intended use and target users.
  • Bill of materials and supplier traceability: component list, supplier names, part numbers, revision levels, and change history.
  • Third party test reports for relevant components: full reports where possible, not only summaries, plus the test standard, sample description, and results.
  • Specifications and declarations from suppliers: material declarations, safety data where relevant, and any limitations or conditions of use.
  • Product level risk assessment: hazards introduced by assembly, foreseeable misuse, and risk controls such as design features, warnings, and instructions.
  • Labeling and instructions: EU language requirements as applicable, safety warnings, age grading where relevant, and installation or maintenance steps.
  • Quality and production controls: incoming inspection criteria, assembly work instructions, final checks, and how you ensure ongoing consistency.
  • Accident and complaint handling process: how you capture safety related feedback and trigger corrective actions.

If you sell into the EU without an EU based economic operator in your supply chain, GPSR requires you to designate a GPSR Responsible Person established in the EU. That economic operator must be able to provide certain information and documentation to authorities upon request, so your file needs to be complete, current, and easy to retrieve.

How do you build a technical documentation file from supplier test reports?

Build a technical documentation file by mapping each supplier test report to a specific component, revision, and safety requirement, then adding product level documents that show the assembled configuration remains safe. The key is traceability: every claim about safety, materials, or performance should point to a report, specification, or controlled internal record.

  1. Freeze the product definition: lock the BOM, drawings, firmware versions if applicable, and packaging and labeling versions for each SKU and variant.
  2. Collect complete supplier evidence: request full third party test reports, not only certificates, and confirm the tested sample matches your component revision and material.
  3. Create an evidence matrix: a simple index that lists each safety topic and links it to the relevant component report or internal verification record.
  4. Check applicability: confirm the test conditions match your use case, including voltage, load, temperature, user group, and installation method.
  5. Add assembly specific verification: document torque settings, adhesives, wiring routing, software configuration, or other integration steps that affect safety.
  6. Document labeling and instructions control: show how warnings and instructions align with identified hazards and foreseeable misuse.
  7. Set a change control rule: define when a supplier change, material substitution, or design tweak triggers a documentation update or re-testing decision.

A practical tip is to store supplier reports alongside the exact purchase specification and revision history. When a marketplace or authority asks for evidence, you can show that the report corresponds to the component you actually used, not a similar earlier version.

What are common gaps that cause compliance failures for assembled products?

Common compliance failures happen when companies rely on third party test reports for components but cannot prove the assembled product is equivalent to what was tested, or when the technical documentation file lacks traceability, version control, and product level risk analysis. These gaps often surface during marketplace checks or authority requests under the Market Surveillance Regulation (EU) 2019/1020 (MSR).

  • Mismatch between tested sample and shipped product: different material grade, supplier, revision, or manufacturing process than the report covers.
  • Missing integration risk assessment: hazards introduced by assembly such as overheating, sharp edges, pinch points, stability issues, or combined chemical exposure.
  • Incomplete reports: only a certificate page without methods, sample description, pass criteria, or limitations.
  • No documentation for variants: colorways, bundles, accessories, or regional packaging changes that alter warnings or use conditions.
  • Weak labeling and instructions: warnings not aligned with foreseeable misuse, missing key safety steps, or inconsistent product identifiers across packaging and listings.
  • Poor document control: no revision dates, no owner, and no clear process for updates after supplier changes.
  • Unclear roles for EU communication: the EU based economic operator cannot quickly provide documentation or route safety concerns back to the manufacturer as required.

To prevent these issues, treat component compliance evidence as inputs, not the final answer. Your assembled product file should read like a single story: what you built, what could go wrong, and what evidence shows you controlled those risks.

How EARP helps with documenting compliance for assembled products?

We help you turn scattered supplier files and third party test reports into a complete, audit ready EU product compliance documentation package for the finished product, aligned with GPSR expectations and organized for fast responses to authority or marketplace requests. We act independently in the EU so your documentation stays consistent even as your supply chain evolves.

  • Technical documentation file build and review that connects component evidence to the final product configuration and variants
  • Gap checks to identify missing applicability details, revision mismatches, and assembly introduced hazards
  • Document control and storage so files stay current, retrievable, and ready to provide to authorities when requested
  • EU based GPSR Responsible Person support as an economic operator that can maintain required information availability and route risk information back to the manufacturer in line with MSR Article 4 expectations

To get your assembled product documentation organized for EU market access, review our compliance services and then contact our team to discuss your product, components, and current documentation set.

Related Articles