Proof of RoHS compliance is not a single certificate. It is a defensible evidence trail: an EU Declaration of Conformity backed by technical documentation, which in turn is built from supplier material declarations and analytical test data at the component level. A supplier emailing you a one-page "RoHS certificate" has given you an input, not the finished proof an auditor or customer will accept.

This distinction matters most when your components come from outside the EU, where the supplier carries no direct legal obligation under the Directive and the burden shifts onto you as the importer or manufacturer placing the product on the market. This guide explains exactly what documents prove RoHS compliance, how to verify them, and what to require from suppliers inside and outside the EU.

If you are trying to gauge how exposed your current records leave you, you can book a compliance risk assessment to review your RoHS evidence across products and suppliers.

What Counts as Proof of RoHS Compliance

Under Directive 2011/65/EU (RoHS 2), the legal proof that a product meets RoHS is the EU Declaration of Conformity (DoC), supported by technical documentation that the manufacturer must compile and retain. By drawing up the DoC, the manufacturer assumes legal responsibility for the product's conformity.

Everything a supplier sends you sits one level below that. Material declarations, test reports, and certificates of conformance are the raw evidence that lets you compile the technical file and sign the DoC with confidence. They are necessary, but on their own they are not the regulatory proof.

For a framework-level overview of obligations, see Certivo's RoHS compliance framework page.

Proof of RoHS compliance evidence chain from supplier data to Declaration of Conformity

Click on image to view full

The two layers of RoHS proof

The Documents That Actually Prove RoHS Compliance

Three document types do the real work. Each answers a different question an auditor or OEM customer will ask.

EU Declaration of Conformity (DoC)

The DoC is the manufacturer's signed legal statement that the product meets the requirements of Article 4 of the Directive. It must follow the model structure in Annex VI and identify the product, the legislation applied, and the responsible economic operator. Manufacturers and importers must keep the DoC for 10 years after the product is placed on the market.

Technical documentation (the technical file)

The technical file is the assembled evidence behind the DoC. The recognized way to structure it is the harmonized standard EN IEC 63000:2018, adopted through Commission Implementing Decision (EU) 2020/659, which replaced EN 50581:2012 (withdrawn 18 November 2021). Products assessed against EN IEC 63000:2018 benefit from a presumption of conformity. The standard specifically describes how material declarations move through the supply chain, which is why clean supplier data is the foundation of the file.

Supplier evidence that feeds the file

This is the layer you collect from vendors and the layer that breaks down most often at scale:

📄 Full material declarations (FMD) or supplier declarations, commonly exchanged in IEC 62474 or IPC-1752A formats

📊 Analytical test reports generated using the IEC 62321 series of test methods

📌 Certificates of conformance that reference the correct substances and thresholds, not a generic statement

A certificate of conformance and a mill test report each tell you different things, and knowing how to read both is part of validating RoHS proof. Automating that collection is covered in Certivo's streamline supplier documentation use case.

The 10 Restricted Substances and Thresholds You Are Proving Against

Your evidence has to demonstrate that each homogeneous material stays within the maximum concentration values set in Annex II. The four phthalates were added by Commission Delegated Directive (EU) 2015/863 and have applied since 22 July 2019 (22 July 2021 for medical devices and monitoring and control instruments).

The thresholds apply at the homogeneous material level, not the component or product average. This is the single most common reason supplier evidence fails review: a part-level pass can still hide a non-compliant plating, solder, or polymer. Managing this is a question of BOM-level compliance intelligence rather than paperwork collection.

RoHS compliance restricted substance thresholds for homogeneous materials reference card

Click on image to view full

Why a "RoHS Certificate" Alone Is Not Proof

Many suppliers respond to a RoHS request with a self-declared certificate carrying a logo and a sentence. Treat it as a claim to be verified, not as proof. A certificate becomes defensible evidence only when it is traceable to the restricted substances, the correct thresholds, the specific part numbers, and ideally underlying test data.

⚠️ A statement that a product is "RoHS compliant" with no reference to the current 10 substances, no homogeneous-material basis, and no test method is a red flag in any customer audit or regulatory inspection. If you cannot show how the claim was substantiated, you cannot rely on it.

This is why mature programs separate certificate validation from certificate collection. Receiving a document is not the same as confirming it says what it needs to say. Certivo's approach to replacing manual material-disclosure chasing addresses exactly this gap.

What Proof to Require From Suppliers Outside the EU

This is where most teams get stuck, because the legal logic is counterintuitive.

Who is legally responsible

RoHS obligations attach to economic operators who place electrical and electronic equipment on the EU market: manufacturers, authorised representatives, importers, and distributors. A component supplier based outside the EU that is not itself placing finished product on the EU market carries no direct obligation under the Directive.

That means the legal duty lands on you. If you import the finished product, Article 9 requires you to ensure the manufacturer carried out the conformity assessment, drew up the technical documentation, and that the product bears CE marking. You must keep a copy of the DoC for 10 years and be able to make the technical documentation available to authorities.

Documentation to require from non-EU suppliers

Because a non-EU supplier is not bound by RoHS, you cannot assume its declaration meets EU evidentiary standards. Require the evidence that lets you build your own technical file:

📌 Full material declarations mapped to your bill of materials, not a blanket statement

📊 IEC 62321 test reports from an accredited laboratory for high-risk materials

🔗 Part-number-specific traceability so declarations map to the components you actually buy

📄 Supplier contact and identity details, since you may need to evidence the economic-operator chain

Building this across a global, multi-tier supply chain is a data problem, not a filing problem. Certivo's supplier and contractor management solution centralizes that collection so the evidence maps back to specific parts.

RoHS compliance responsibility across manufacturer importer and distributor for non-EU suppliers

Click on image to view full

How to Verify Supplier RoHS Evidence Is Valid

Collecting documents is the easy half. Confirming they hold up is where audit exposure is won or lost.

• Check the test method. The IEC 62321 series is the recognized standard. XRF screening (IEC 62321-3-1) is a screening tool, while definitive techniques such as ICP-OES, GC-MS for phthalates and brominated flame retardants, and the IEC 62321-7 methods for hexavalent chromium confirm borderline results.

• Check currency. A declaration predating the July 2019 phthalate applicability date does not prove compliance against all 10 substances.

• Check scope. Confirm the evidence covers the exact part number and material, measured at the homogeneous-material level.

• Check exemptions. Many lead applications rely on Annex III and Annex IV exemptions that are regularly extended, split, or revoked, so an expired exemption can quietly turn compliant evidence into a gap.

Several of these substances also appear on the REACH SVHC Candidate List, so RoHS and REACH evidence often need to stay consistent for the same part. Reading a stack of mill test reports by hand does not scale, which is why Certivo automates mill test report analysis at the document level.

Building an Audit-Ready RoHS Evidence Trail

The reason RoHS proof becomes painful is structural. Declarations live in inboxes, test reports live in shared drives, and the link back to specific parts lives in someone's memory. When a customer or regulator asks for evidence on a given SKU, the retrieval scramble begins.

A continuous approach treats RoHS evidence as managed data rather than static files. Certivo's compliance engine, CORA, applies deterministic, traceable rules to supplier documents: its Liaison agent runs the supplier campaigns and chases missing responses, its Examiner agent extracts and validates against the restricted-substance limits, and its Registrar agent assembles the certificates and audit trail. The result is audit-ready documentation with historic state tracking, so you can show not only that a product was compliant but when and on what evidence.

That shift, from reactive document chasing to CORA-powered regulatory intelligence with continuous monitoring, is what lets electronics and industrial manufacturers respond to RoHS evidence requests in hours rather than weeks. For a broader view of moving off spreadsheets, see Certivo's guide to future-proofing RoHS supply chains.

To see where your current RoHS evidence has gaps before a customer or auditor finds them, book a compliance risk assessment.