What a folder of certificates does and does not prove
Supplier document packs usually mix three different things: management system certificates, product or material recognition files, and third-party test reports. Their scope of validity is not the same. A system certificate says the plant's processes passed an audit; it does not say a given board is compliant. A material recognition file says a specific laminate or construction was recognised under stated conditions; it does not cover every stack-up the plant can build. A test report speaks only for the samples that were submitted. Treating all three as one undifferentiated category of "certification" is the most common distortion in supplier onboarding.
So the first step is not authenticity, it is type and scope. For every document, establish three facts: who issued it, the full legal name of the holder, and the applicability scope written in the document itself. If any of the three is vague, downstream comparison is meaningless.
UL file numbers: how to look them up, and what they establish
The useful information on a UL document is not the certificate artwork, it is the File Number and the Category Control Number (CCN). The file number takes the form E followed by digits and identifies the applicant's file; the CCN identifies the specific recognised product category within that file. Only together do they form a record you can look up.
For SKPCB, two UL records are publicly verifiable: ZPMV2.E326765 for the US and ZPMV8.E326765 for Canada (claim_id CERT-04 / CERT-05). One file number, E326765, carries two different category control numbers covering two markets. That structure matters during verification: seeing only a file number and concluding "UL certified" can hide the fact that your target export market is not inside the recognised scope.
The lookup itself is straightforward. Search the UL public product directory by file number and compare the returned applicant name, address and CCN against the document you hold. A mismatch in name or address does not automatically mean forgery — it may reflect a different legal entity inside the same group, or a plant relocation not yet reflected in the file — but any mismatch should be logged and explained by the supplier in writing.
One more frequently misread point: UL recognition for printed boards is typically tied to standards such as UL 796 (printed wiring boards) and UL 94 (material flammability classification), and the recognition is bound to specific base materials, minimum thicknesses, layer constructions and processing conditions. UL recognition is therefore not a blanket pass covering all capacity; it is a set of conditional combinations. Specific clause limits are defined by those standards and governed by the revision your drawing specifies; this article does not restate any threshold values.
System certificates vs compliance reports: different instruments, ask for them differently
On the system side, the SKPCB Huizhou entity (ENT-03, Huizhou Sunking Circuits Co., Ltd.) holds ISO 9001:2015, ISO 14001:2015 and IATF 16949:2016, all issued by DNV (claim_id CERT-01 / CERT-02 / CERT-03). Verify four things on a system certificate: certificate number, issue and expiry dates, certification body, and — most often skipped — the site address written inside the scope statement. That address has to match the plant actually building your order. For multi-site groups this is the single highest-value check.
RoHS and REACH work differently. What SKPCB provides are conformity reports for RoHS 2011/65/EU and REACH (EC) 1907/2006 (claim_id CERT-06 / CERT-07, docType=report) — not certificates. The distinction has practical consequences. A report is tied to specific submitted samples and a test date, and must be reissued after a material or supply-chain change. A certificate is tied to a system or product recognition, with a defined validity period and surveillance audits. When procurement writes "supply RoHS certificate," the better practice is to specify whether you want a report or a declaration, and to define what triggers reissue.
When a group holds certificates under different legal entities
Multi-entity, multi-site structures are common among PCB manufacturers, and certificates often sit under different legal names. SKPCB's ISO 13485:2016 is exactly this case: certificate number 134947, issued by NQA, held by Sunking Ji An Circuits Electronics Co., Ltd. (ENT-07, a legal entity distinct from the Huizhou entity ENT-03), with a scope covering the manufacture of circuit boards for medical devices (ventilators), valid until 2028-04-17 (claim_id CERT-08). The Ji An site address is Zongsi Road, Industrial Park Zone 2, Wan'an County, Ji An, Jiangxi (ENT-08).
Read that record on two levels. At the entity level, the medical device system certification sits with the Ji An entity; if your order is produced in Huizhou, that certificate is not the system basis for your order. At the scope level, the certification is explicitly limited to ventilator circuit boards and cannot be extrapolated to all medical device categories. Recording "who holds it, at which site, covering what scope" as three separate fields is far more useful than a single tick-box marked "has ISO 13485."
Read the other way round, entity attribution is a variable you can arrange at order placement, not a result you simply accept. If a project has to sit inside an ISO 13485 system, raise that requirement at the RFQ stage and name the legal entity and site in the purchasing documents. Using the certificate above as the example, work that requires ISO 13485 coverage can be placed with the Ji An site (Sunking Ji An Circuits Electronics Co., Ltd.); if the product falls outside the ventilator scope, run a scope applicability review before settling on the basis. Record that attribution in the order review file rather than leaving it as a verbal confirmation.
In total, SKPCB has 8 externally verifiable certification and compliance documents: seven under the Huizhou entity (three management systems, two UL market records, RoHS and REACH reports) plus the Ji An ISO 13485. Listing them grouped by holding entity rather than by certificate name reduces mistakes.
Make verification a repeatable action, not a one-off
Maintain a table in the supplier file, one row per document, with columns for document type (system certificate / product recognition file / test report), issuing body, full legal name of the holder, number, validity or test date, verbatim excerpt of the scope statement, and a "covers this project?" decision with the name of who decided. Annual re-approval then only has to review what changed.
Keep in mind that every concrete technical limit — flammability class, bond strength, solderability criteria, visual acceptance — is defined by the applicable standard and governed by the revision your drawing or purchasing specification calls out. Certification verification answers whether the plant has been audited and what the audit covered. It cannot answer whether a given board conforms. That belongs to the order-level inspection and test plan, a parallel track to certification review.
FAQ
Q1: We only have a UL file number, no certificate artwork. Is that sufficient?
The file number plus the category control number is the verifiable information; the artwork carries no independent weight. For SKPCB, ZPMV2.E326765 (US) and ZPMV8.E326765 (Canada) can be searched directly in the UL public product directory. The situation that warrants follow-up is the reverse: an image with no matching database record.
Q2: What is the difference between a RoHS "certificate" and a RoHS report?
They are different instruments. SKPCB supplies conformity reports for RoHS 2011/65/EU and REACH (EC) 1907/2006, tied to specific submitted samples and test dates, and reissue should be requested after material or supply-chain changes. If your own customer contract says "certificate," consider rewriting your purchasing specification as "conformity report plus retest on change" so acceptance criteria do not conflict.
Q3: The supplier produced an ISO 13485 certificate for the Ji An site, but my boards run at a different site. Can I cite it?
Not directly. System certification follows the legal entity and the site. SKPCB's ISO 13485:2016 (certificate 134947, issued by NQA) is held by Sunking Ji An Circuits Electronics Co., Ltd., with scope limited to circuit boards for medical devices (ventilators). Which site produces your order, and whether it falls inside that scope, has to be confirmed per order. Conversely, this is also something you can arrange when placing the order: work that needs the certified system can be assigned to the Ji An site with the entity named in the purchasing documents, and if the product sits outside the ventilator scope, a scope applicability review comes first.
Q4: How deeply should we verify the scope statement on a system certificate?
At minimum verify the site address and the business scope description, and confirm both match the plant actually taking your order. Numbers and dates only prove the certificate is live; they do not prove it covers your project.