Supplier compliance documents are regulated evidence, not filing. US CPSC rules at 16 CFR 1107.26 require children's product certificates, testing plans and test results including component part testing to be retained for at least five years. In the EU, Article 7 of RoHS Directive 2011/65/EU requires manufacturers to hold technical documentation and run internal production control, while REACH Article 33 requires suppliers to communicate substances of very high concern above 0.1% weight by weight, with parallel SCIP database notification to ECHA.
Supplier document management compliance is a regulated control, not an administrative filing exercise: under US CPSC rules, children's product certification records — including component part test results — must be kept for at least five years, and under EU RoHS and REACH the manufacturer must hold technical documentation and pass substance information down the chain regardless of who generated the underlying data. The practical consequence is that every supplier declaration, test report, certificate and substance datasheet needs to be mapped to a specific product, a specific regulation and a specific market, with its validity tracked. Shared drives and email threads cannot evidence which requirement a document supports or when it lapsed.
Because the regulator asks the manufacturer, not the supplier. The legal obligations to hold technical documentation, to declare conformity and to retain certification records attach to the party placing the product on the market, even though most of the underlying evidence — material declarations, component test reports, certificates of analysis — originates upstream.
That creates an asymmetry compliance teams live with daily. A component supplier generates the evidence; the manufacturer carries the liability if the evidence is missing, out of date, or issued against a superseded part revision. Vendor compliance records management is therefore part of the product compliance file, not part of procurement housekeeping.
The pattern is consistent across the three frameworks that generate most supplier paperwork for electronics, consumer goods and industrial equipment: the EU RoHS Directive (technical documentation and internal production control), REACH (substance communication and registration duties), and US equipment authorisation and product certification rules (declarations supported by retained test records). Each imposes a document duty that only resolves if the supply chain feeds it.
| Framework | Document duty |
|---|---|
| EU RoHS Directive | Technical documentation and internal production control |
| REACH | Substance communication and registration duties |
| US equipment authorisation and product certification rules | Declarations supported by retained test records |
Four categories recur, and each maps to a different legal hook. Declarations of conformity and certificates of compliance state that a part or product meets named requirements. Test reports and certificates of analysis are the laboratory evidence behind those declarations. Material and substance declarations identify which substances are present and at what concentration. Product approval and equipment authorisation records evidence market access.
| Document category | What it establishes |
|---|---|
| Declarations of conformity and certificates of compliance | State that a part or product meets named requirements |
| Test reports and certificates of analysis | Laboratory evidence behind those declarations |
| Material and substance declarations | Identify which substances are present and at what concentration |
| Product approval and equipment authorisation records | Evidence market access |
The distinction that matters in an audit is between a document that makes a claim and a document that proves one. A supplier declaration is a claim. The test report or analytical data behind it is the proof. A compliance file built only on declarations, with no retained underlying evidence, is thin in exactly the places a market surveillance authority or a CPSC enquiry will press.
Supplier's Declaration of Conformity (SDoC) is a recognised conformity assessment procedure in its own right, not an informal assurance. NIST's guidance on the use of supplier's declaration of conformity sets out the concept as a first-party attestation of conformity. In the US radio equipment context, SDoC under 47 CFR Part 15 functions as an equipment authorisation procedure, under which the responsible party declares compliance on the basis of its own test evidence rather than obtaining certification from a third party.
The operational consequence for retailers and third-party logistics providers is that they must be able to produce the SDoC documentation for products they list or handle. Supplier declaration of conformity tracking is therefore a distribution-chain obligation, not only a manufacturer one.
Three instruments drive the bulk of the requirement set described here.
The Consumer Product Safety Commission states that 16 CFR 1107.26 requires firms to keep records of their certificates of compliance, test results including component part testing, testing plans, and other actions taken to secure a high degree of assurance of compliance, for at least five years. CPSC confirms that electronic access to these records satisfies the requirement.
Two points practitioners routinely miss. First, component part test results are explicitly named — so supplier-generated evidence falls inside your own retention obligation, not the supplier's alone. Second, the five-year period runs on the records, meaning a supplier relationship that ends does not end the retention duty.
Article 7 of Directive 2011/65/EU (RoHS 2) requires manufacturers to draw up the required technical documentation and to carry out internal production control before placing electrical and electronic equipment on the market. That documentation rests on what suppliers state about materials, parts and processes. Where the manufacturer cannot evidence the restricted-substance status of a homogeneous material, the technical documentation is incomplete by definition.
REACH Article 33 requires any supplier of an article to provide recipients with the name of any substance of very high concern present in that article above 0.1% weight by weight, together with sufficient information to allow safe use. This is a cascading duty: your suppliers owe it to you, and you owe it to your customers.
In parallel, under the revised EU Waste Framework Directive, suppliers of articles containing SVHCs above that threshold must submit information to the SCIP database operated by the European Chemicals Agency. SCIP database submission requirements for suppliers mean that inbound substance information is not merely useful — it is the input to a legal notification you may have to make yourself.
The broader REACH architecture — registration, evaluation, authorisation and restriction — is set out in the Commission's Your Europe guidance on registering chemicals in the EU. The Swedish Chemicals Agency notes that the basic Regulation together with all amendments and corrections is available in EUR-Lex; practitioners should work from the consolidated text rather than the 2006 original, because the candidate list and the annexes change.
| Instrument | Jurisdiction | Core duty |
|---|---|---|
| 16 CFR 1107.26 (CPSC) | US | Keep certificates of compliance, test results including component part testing, testing plans and other actions for at least five years |
| Article 7, Directive 2011/65/EU (RoHS 2) | EU | Draw up the required technical documentation and carry out internal production control before placing EEE on the market |
| REACH Article 33 and SCIP (Waste Framework Directive) | EU | Communicate SVHCs above 0.1% w/w to recipients and submit information to the ECHA SCIP database |
Any manufacturer, importer or distributor placing electrical and electronic equipment, children's products or articles containing candidate-list substances on the US or EU markets. The exposure scales with supply chain depth, not company size: a product with 400 purchased parts from 60 suppliers carries 60 document relationships that must each be current at the moment of placing on the market.
The effect differs by role. Manufacturers carry the technical documentation and declaration duties. Importers must be able to obtain and present that documentation on request. Retailers and third-party logistics providers increasingly need SDoC documentation on file for the listings they operate. Authorised representatives hold whatever the mandate assigns to them — typically keeping the EU declaration of conformity and technical documentation at the disposal of national authorities.
| Role | Duty |
|---|---|
| Manufacturers | Carry the technical documentation and declaration duties |
| Importers | Must be able to obtain and present that documentation on request |
| Retailers and third-party logistics providers | Increasingly need SDoC documentation on file for the listings they operate |
| Authorised representatives | Hold whatever the mandate assigns — typically keeping the EU declaration of conformity and technical documentation at the disposal of national authorities |
The second-order effect is on engineering change control. A revised housing material, a resourced connector or a supplier site transfer invalidates the specific document that covered the previous configuration. Without conformity evidence traceability down to part revision, the compliance file silently decouples from the product being shipped.
At minimum, each document record needs the issuer identity, the issue date, the validity or expiry date where one exists, the part or product it covers including revision level, the regulation or standard it evidences, and the market it supports. Without those metadata fields, a PDF is storage, not evidence.
The audit chain runs: regulation → product → part → supplier document → validity at date of placing on market. Each link must be reconstructable without someone remembering where a file sits. Product compliance evidence management means holding that chain as structured data, with the bill of materials and target markets on one side and the supplier evidence on the other.
Documents lapse in two ways, and most systems only catch one. Date-based expiry — a certificate with a stated validity end — is visible in any calendar or spreadsheet. Requirement-based lapse is not: a declaration that was sufficient last quarter may be insufficient once a new substance is added to the REACH candidate list, a RoHS exemption expires, or a harmonised standard is superseded. Tracking supplier test report expiry dates solves half the problem. Monitoring regulatory change against your product portfolio solves the other half.
| Date-based expiry | Requirement-based lapse | |
|---|---|---|
| Trigger | A certificate with a stated validity end | A new substance added to the REACH candidate list, a RoHS exemption expiring, or a harmonised standard being superseded |
| Visibility | Visible in any calendar or spreadsheet | Not visible in a calendar or spreadsheet |
| Control | Tracking supplier test report expiry dates solves half the problem | Monitoring regulatory change against your product portfolio solves the other half |
The clearest figure is the CPSC minimum: at least five years for children's product certification records, including component part test results, under 16 CFR 1107.26. Customer-imposed periods in supplier requirements manuals are frequently equal or longer, and contractual retention can exceed the statutory floor. The working rule is to retain for the longest applicable period across statute, contract and customer requirement.
EU retention periods are set in the relevant sectoral legislation rather than in a single horizontal rule, and practitioners should check the specific directive or regulation applying to their product rather than assuming a common period. For RoHS, the Article 7 duty is to draw up and hold the technical documentation; the retention duration is specified in the directive's conformity assessment provisions and should be read against the current consolidated text in EUR-Lex.
Requests arrive in three situations: a market surveillance authority enquiry, a customer or notified body audit, and a marketplace or retailer listing review. None of them allow weeks of reconstruction.
The US model for radio and unintentional-radiator equipment under 47 CFR Part 15 places responsibility on a named responsible party who declares conformity on its own test evidence, with the documentation held and produced on request. The EU model places the declaration duty on the manufacturer, supported by technical documentation and, for RoHS, internal production control under Article 7 of Directive 2011/65/EU.
The substantive divergence is on chemicals. The EU imposes an affirmative, cascading communication duty through REACH Article 33 plus a notification duty to the ECHA SCIP database. There is no equivalent horizontal article-level communication duty in the US framework described in these sources; US obligations in the sources centre on certification, testing and record retention under CPSC rules. Teams selling into both markets therefore need two distinct evidence sets from the same supplier, and should request them as separate, named deliverables rather than through a single generic questionnaire.
| US | EU | |
|---|---|---|
| Declaration duty | Named responsible party declares conformity on its own test evidence under 47 CFR Part 15, with documentation held and produced on request | Manufacturer holds the declaration duty, supported by technical documentation and, for RoHS, internal production control under Article 7 of Directive 2011/65/EU |
| Chemicals communication | No equivalent horizontal article-level communication duty in the US framework described in these sources; obligations centre on certification, testing and record retention under CPSC rules | Affirmative, cascading communication duty through REACH Article 33 plus a notification duty to the ECHA SCIP database |
Start from the product, not the supplier. For each SKU and each target market, list the applicable regulations, then work down the bill of materials to identify which parts, materials and suppliers feed each requirement. A power adapter supplier owes different evidence from a plastics supplier; sending both the same questionnaire guarantees gaps that surface at audit.
Issue requests that name the document type, the part number and revision, the regulation or standard it must reference, and the due date. Free-text email requests produce free-text answers that cannot be verified against a requirement.
Verify before accepting. Confirm that the document is complete, signed where required, issued by the correct legal entity, dated, and applicable to the part revision you currently purchase. A declaration covering the previous revision is not evidence for the current one. This verification step is where most of the control value sits, and it is the step most often skipped. (Process recommendation based on standard compliance practice; not derived from a specific regulatory text.)
For REACH, treat inbound Article 33 information as a trigger, not an archive entry. When a supplier notifies an SVHC above 0.1% w/w, the immediate questions are which of your articles contain that part, whether your own Article 33 communication to customers must be updated, and whether a SCIP submission is required.
For CPSC-regulated children's products, confirm that every certificate of compliance has its supporting test results — including component part testing — and testing plan retained and retrievable for at least five years, and that electronic retrieval works for records held on supplier systems rather than your own.
For RoHS, audit a sample of technical documentation files against Article 7: can you show the material-level evidence and the internal production control record, or only a supplier declaration? If only the declaration, the gap is documented and dated, which is a better position than discovering it under enquiry.
The two moving parts that invalidate existing supplier evidence without any action on your side are the REACH candidate list, updated by ECHA on a rolling basis, and the consolidated RoHS text including exemption expiry dates in Annexes III and IV. Both are published in EUR-Lex and on ECHA's site; the Swedish Chemicals Agency confirms that the basic REACH Regulation with all amendments and corrections is available in EUR-Lex. Set a standing review against the candidate list at each update, and against exemption expiries annually.
| Moving part | Update cadence | Review cadence |
|---|---|---|
| REACH candidate list, updated by ECHA | Rolling basis | Standing review at each update |
| Consolidated RoHS text including exemption expiry dates in Annexes III and IV | As published in EUR-Lex | Annually, against exemption expiries |
Watch the REACH candidate list updates. The REACH candidate list, updated by ECHA on a rolling basis, and the consolidated RoHS text including exemption expiry dates in Annexes III and IV are the two moving parts that invalidate existing supplier evidence without any action on your side.
Discuss this signal with compliance peers, get the weekly digest, and never miss an enforcement deadline that affects your products.