How to Verify a Chinese Supplier: 3-Layer Workflow

The three verification layers

Verification should follow the transaction. Start with the entity that will quote, contract, invoice, receive payment, and take responsibility. Then test whether the evidence applies to the exact product and production route. Finally, make the order controls enforce the facts that mattered to the decision.

Layer	Buyer question	Typical evidence	Useful outcome
1. Entity and company	Who is the legal counterparty and who receives money?	Chinese business license, public registration record, quote, contract, invoice and bank-beneficiary details	Names and roles are explained or escalated
2. Product and documents	Does the claimed capability or document apply to this model, site and requirement?	Specification response, process map, report scope, certificate scope, sample record and document identifiers	Scope and gaps are visible
3. Order and execution	What stops an unapproved change or weak shipment?	Controlled specification, approved sample, inspection plan, deviation log, change approval and payment-release conditions	Evidence is connected to a release decision

Layer 1: establish the legal counterparty

Ask for a clear image or PDF of the Chinese business license and preserve the original Chinese company name. Use the field-by-field business license guide when translating its entries, then search the National Enterprise Credit Information Publicity System using that name or the Unified Social Credit Code. The official help page says the system provides market-entity credit information and that public data may originate from market regulators, other government departments, and the entity itself. That makes it a valuable public-record starting point—not a complete due-diligence conclusion.

What a business license can show

the registered legal name and Unified Social Credit Code;
registered status, legal representative, registered address and stated business scope, subject to the current public record;
a stable Chinese identifier for reconciling other transaction documents.

What it does not show

that the company owns or operates the factory shown in marketing material;
that it can produce the buyer’s exact specification, volume or quality level;
that a certificate or test report covers the quoted model;
that the company will perform, or that a bank account change is legitimate.

Build one counterparty reconciliation sheet

Copy names; do not “tidy” them into an assumed match. Record the Chinese and English versions, the document and date, and the role each entity claims to perform. Then compare the website footer, business license, quotation header, proposed contract party, invoice issuer, bank beneficiary, certificate holder and report applicant. Use the dedicated company entity mismatch workflow when names diverge.

Check	Explained	Partly explained	Unresolved
Quote name versus license	Exact legal name or documented trading relationship	Translation difference with supporting Chinese identifiers	No documentary link to the licensed entity
Contract versus bank beneficiary	Same entity, or disclosed authorized collection arrangement accepted by the buyer	Related entity explanation but authority or controls incomplete	Late account switch, personal account, or beneficiary with no explained role
Website versus certificate/report	Holder/applicant and production site roles reconcile	Group or subcontract arrangement only partly documented	Different entities or sites with no scope explanation

Layer 2: verify the product and evidence scope

Convert every broad claim into a scoped question. “We are certified” becomes: which legal entity, site, standard, certificate number, issuing body, validity period and scope? “Our product passed testing” becomes: which model, sample configuration, standard or method, report number, laboratory, issue date and tested clauses?

A factory audit report can describe observations at a named site on a particular date. It does not automatically authenticate every document, prove product compliance, or guarantee future output. A test report can record results for submitted samples and a stated scope. It does not automatically cover a different model, material, component, factory or destination-market obligation. A management-system certificate concerns its stated holder, site and scope; it is not a product approval.

Divide checks by evidence owner

Public records: registration and public credit information available through the relevant official system.
Supplier-provided: license copy, process map, specification response, subcontractor disclosure, reports, certificates, sample data and commercial documents.
Issuer or third-party checks: certificate/report confirmation, laboratory-scope review, site visit or audit, product testing and independent inspection.
Buyer-controlled: the correct specification revision, destination-market requirements, approved deviations, approval authority and release conditions.

Layer 3: control the actual order

Issue one controlled specification and use the RFQ Builder so every supplier prices the same basis.
Require comply, deviation or unknown against each critical requirement.
Approve a defined sample and record its revision, components, finish, packaging and exceptions.
Bind the accepted specification, evidence index, deviation log and change-control process to the purchase order or contract.
Set inspection and payment releases around evidence that can actually be checked.
Retain the quotation, approvals, change messages, inspection material, shipping documents and final payment record.

When to pause the next payment or release

Pause when a decision-critical point remains unresolved—not because a checklist produced a score. Examples include a new beneficiary that cannot be reconciled, refusal to identify the contracting entity, an unexplained production-site change, a report that does not cover the quoted model, a material or component substitution without buyer approval, or a failed inspection without an accepted disposition. The pause is a control point for clarification and independent verification, not an accusation of fraud.

Buyer path: from discovery to retained evidence

Preserve the supplier’s claimed identity and original documents.
Query the public record and record the access date.
Reconcile all transaction entities and roles.
Map product claims to model-, site- and scope-specific evidence.
Use a sample, audit, testing or inspection only for the question it can answer.
Resolve or formally accept deviations before the relevant release.
Retain evidence with identifiers, dates and decision owners.

Limitation: absence of a problem in a public search is not proof of capability or integrity. A convincing document is not proof of authenticity or applicability. Verification should be refreshed when the entity, site, product, bank beneficiary, specification, report scope or transaction structure changes.