A component purchase often depends on documents as much as on electrical data: the RoHS declaration, the REACH substance statement, the conflict minerals response and the quality certificates that back the part number. Knowing where each document lives and what it proves saves the sourcing review from chasing the wrong file or accepting a generic statement that does not cover the part. This guide maps the compliance and quality document set for Good-Ark components and the workflow for requesting what the product page does not show.
The document set a compliance review needs
A compliance review for a discrete component typically needs the substance declarations — RoHS and REACH — the conflict minerals response, the quality system certificates and the part-specific documents such as the datasheet, the qualification report and the material or finish data.
The substance declarations state the restricted materials in the part and the directive or regulation they address. The conflict minerals response follows the supply-chain reporting format and covers the metals in the part’s construction. The quality certificates document the supplier’s quality system and its registration to the standards the program requires, and the part-specific documents tie the part number to its electrical, reliability and material data. The review assembles the set by regulation and by program: the buyer’s compliance questionnaire names the documents, and the supplier’s document map shows where each one is found.
What each document proves — and its limits
Each document proves a defined scope: a RoHS declaration covers the restricted substances in the product at the declaration’s date, a REACH statement covers the listed substances and their communication duties, and a certificate proves a quality system or a product property only within the scope and the date it states.
The limits are as important as the claims. A RoHS declaration applies to the product configuration and the date it was issued; a change in the part or the regulation can make an old declaration insufficient. A REACH statement addresses the substances the regulation lists at the time of the statement, and the communication obligations change as the candidate list grows. A quality certificate covers the system or the product scope it names — not every part the supplier makes, unless the certificate’s scope says so. The review matches the document’s scope and date to the part number and the program’s requirement, and asks for an update when the two do not align.
Where Good-Ark publishes the documentation
Good-Ark publishes its quality and compliance documentation through the official site pages: the quality management page and the compliance page are the entry points for certificates and substance information, and the product pages carry the datasheet and the part-specific data.
The quality management page is the starting point for the quality system and the documentation path, and the compliance page covers the environmental and substance declarations. The product pages provide the datasheet for each part, and the certificate and qualification documents that are not on the product page are requested through the official channel. The document map is simple: product data on the product page, quality and compliance data on the site’s official pages, and anything part-specific that is not published requested from the engineering or quality team with the part number and the program requirement.
What to send when you request documents
Send the part number, the document type and the program requirement when you request compliance documentation, because the quality team can only confirm scope and provide the correct revision when the request names the part and the standard it must meet.
The request that gets a useful answer lists the exact part numbers, the documents needed — RoHS declaration, REACH statement, conflict minerals form, qualification report — and the program or customer requirement that defines the expected format and revision. A request without the part number returns a general statement that may not cover the part in review. The request should also name the date or the revision the program expects, so the supplier can confirm whether the published document matches or a newer revision is needed. The document request is part of the sourcing record, and it belongs with the order and the qualification files.
The verification workflow for a compliance package
Verify the package by checking each document against the part number, the document scope and the revision date, and by confirming that the substance and certificate statements cover the product configuration being purchased.
The verification starts with the part number: the RoHS declaration, the REACH statement and the quality certificate must name or clearly cover the exact part. The scope is checked against the product configuration — package, finish and variant — because a change in any of these can move the substance content. The date is checked against the regulation revision the program requires, and a document that is older than the regulation update is flagged. The completed package is filed with the order so the next audit can reproduce the review. The workflow turns a stack of certificates into a defensible compliance record.
| Document | Covers | Verification point |
|---|---|---|
| RoHS declaration | Restricted substances | Part configuration and date |
| REACH statement | Listed substances | Current candidate list |
| Conflict minerals response | Supply-chain metals | Format and reporting period |
| Quality certificate | System or product scope | Scope and registration date |
Document request path
Start the compliance review at the official pages, request the part-specific documents with the part number and the program requirement, and verify each document’s scope and date before it enters the sourcing record.
The compliance package is only as strong as its weakest match: a generic statement for the wrong part, or a certificate whose scope does not cover the product, fails the audit no matter how many documents are filed. Use the official pages as the map, request the part-specific revisions through the quality and engineering team, and check the scope and date of every document. The sourcing review that passes is the one whose documents match the parts it claims to cover.
For quality and compliance documentation on Good-Ark parts, the quality management page and the compliance page are the official starting points, and the sample and quote guide explains the request path; after you share the part number and the document list, the engineering and quality team can confirm the package for your review.