REACH declarations and test reports: when are they needed and what do they prove?

A document is not the conclusion：One declaration or report cannot answer every REACH question

A customer may ask for a “REACH report”, but the applicable duty depends on whether the supply is a substance, mixture or article, and on the company’s role. A document title does not change the conditions in Articles 7, 31 or 33.

A supplier declaration records a statement for a defined product, version, lot or material. A laboratory report supports only the sample and analytes tested. Both must be connected to the current Candidate List and product configuration before supporting a compliance assessment.

Bottom line first

• There is no universal REACH certificate.
• Identify the product type and economic-operator role first.
• Declarations communicate known supply-chain information and scope.
• Test reports support only the sample, method and analytes tested.
• An SDS does not automatically replace Article 33 information for an article.

Information needed before deciding

• Legal product status: substance, mixture or article
• EEA role and supply-chain position
• Part number, revision, BOM and material-change history
• Candidate List version and check date
• SVHC CAS/EC number, material location and concentration basis
• Declaration product scope, issue date and signer
• Test sample identity, method, analytes and quantification limit
• Intended release and total annual tonnage
• Whether an SDS is required and current

Practical decision flow

Classify product and role

Confirm whether the transaction concerns a substance, mixture or article and the company’s REACH role.

Map materials

Link parts and high-risk areas to part numbers, revisions, BOMs and material data.

Check the list

Compare substance names, CAS/EC numbers and inclusion dates with ECHA’s current Candidate List.

Review declarations

Check the product scope, list version, threshold, date and limitations.

Close evidence gaps

Obtain material data, an updated declaration or targeted testing where documentation cannot support the conclusion.

What different evidence can support

Evidence	What it can support	Important limitation
Supplier declaration	A supplier’s written statement for a specified product and scope	It is not automatically full REACH compliance or an analytical result
Material declaration	A link between materials, components and substances of concern	Version, concentration basis and supply-chain reliability must be checked
Test report	Results for named analytes in the identified sample using a stated method	It cannot be extrapolated to every lot, material or REACH duty
Safety data sheet	Hazard and safe-use information for a substance or mixture	It may not establish an article-level SVHC conclusion
BOM/change record	The product configuration covered by the evidence	It does not itself establish chemical content

Common mistakes

Mistake：Treating ‘REACH compliant’ as a statutory certificate

**Risk：**Actual duties and limitations are obscured

**Better approach：**State the exact scope supported by the declaration or report

Mistake：Using one test for an entire product family

**Risk：**Material and supplier variation is uncontrolled

**Better approach：**Maintain traceability from sample to BOM and part number

Mistake：Using an SDS as proof for every article

**Risk：**Article 33 information may be missed

**Better approach：**Obtain article- or material-level information

Mistake：Omitting the Candidate List version

**Risk：**Newly listed SVHCs may not be assessed

**Better approach：**Record check date and official list source

Mistake：Reading only the report conclusion

**Risk：**Method, analyte and limit of quantification are ignored

**Better approach：**Review the report scope and limitations

Company action checklist

• Create a product–part–material–document matrix
• Require declarations to state list version and part number
• Set update triggers for high-risk materials
• Review laboratory method and sample identification
• Use SDSs for the substance/mixture communication to which they apply
• Keep information needed to perform applicable REACH duties for at least ten years

Manager summary

The objective is not to collect a generic certificate. Each declaration, material record and test result should be traceable to the product, version, Candidate List and legal duty it supports. Establish product type and role first, then close only the evidence gaps that matter.

Frequently asked questions

Does REACH require testing of every product?

No. Requirements depend on the product, role and duty; there is no universal testing rule for all products.

Can a supplier declaration be used?

Yes, as supply-chain evidence, if its product scope, date, list version and limits are reviewed.

Can an SDS replace an SVHC declaration?

Not necessarily. SDS duties chiefly concern substances and mixtures; an article may still have Article 33 duties.

When is testing useful?

When declarations or material data cannot resolve a defined chemical question and targeted testing can reduce the uncertainty.

Does a non-detect mean complete compliance?

No. Interpret the sample, analytes, method and quantification limit, alongside all other duties.

Official legislation and reference material

REACH Regulation (consolidated text)

EUR-Lex

• Legal status: Binding EU Regulation; consult the current EUR-Lex consolidated version

• Last checked: 2026-08-08

• Publication / update date: 2026-05-11 (current consolidation)

• Used for: Articles 7, 31, 33 and 36

Candidate List of substances of very high concern for Authorisation

European Chemicals Agency (ECHA)

• Legal status: Official current ECHA Candidate List

• Last checked: 2026-08-08

• Publication / update date: Current list page; 2026-02-04 update used for this review baseline

• Used for: SVHC entries and inclusion dates

Summary of obligations resulting from inclusion of SVHCs in the Candidate List

European Chemicals Agency (ECHA)

• Legal status: Official ECHA implementation summary; not a substitute for the Regulation

• Last checked: 2026-08-08

• Publication / update date: Publication/update date not stated on the linked official page; checked 2026-08-08.

• Used for: Article 7 notification and Article 33 communication

Safety data sheets

European Chemicals Agency (ECHA)

• Legal status: Official ECHA technical and supply-chain information

• Last checked: 2026-08-08

• Publication / update date: Publication/update date not stated on the linked official page; checked 2026-08-08.

• Used for: When SDSs apply and are updated

SCIP Database

European Chemicals Agency (ECHA)

• Legal status: Official ECHA Waste Framework Directive information

• Last checked: 2026-08-08

• Publication / update date: Publication/update date not stated on the linked official page; checked 2026-08-08.

• Used for: SCIP submission scope