Supplier Address Consistency Checks in China Verification

Address differences need labels

A Chinese supplier may have a registered office, factory site, warehouse, export office and sales showroom. Different addresses can be normal. They become risky when no one can explain which address controls production or documents.

The file should list each address type and source: registration, business license, factory photos, invoice, website, shipping label and audit report. The buyer should label every address instead of forcing them to match.

The file should start with the live commercial record. Name the SKU, account, supplier, route, claim or customer promise that creates the exposure. Then name the evidence owner and the next event that should reopen the review. This keeps the work close to operations instead of turning it into a detached compliance memo.

Case pattern: three addresses, no labels

A buyer sees one address on the license, another on the website and a third on the invoice. The supplier says all are normal but never labels their roles.

The buyer should ask for an address map before relying on factory or delivery claims.

The team should write the corrective note while the facts are fresh. The note should say what changed, which file now supports the decision and what the business will stop claiming until stronger evidence exists. That sentence prevents a private fix from turning into another public promise.

Create an address map

The map should list address, source, role, date checked and whether it matters for production, payment, delivery or dispute handling.

If the factory address differs from the registered entity, record the relationship and decide whether on-site verification or production access is needed.

• List every address source.
• Label each address role.
• Ask for factory relationship evidence.
• Compare address changes over time.
• Record whether mismatch affects order terms.

Review rhythm

Use one small sample each month while the issue remains active. Pull one recent order, one public page, one internal note and one customer or platform message. If those records tell the same story, record the sample date and move on. If they conflict, fix the specific field and ask whether other products, suppliers or routes share the same weakness.

The review should stay practical. A seller does not need a meeting for every small discrepancy. It needs a habit that catches drift before the drift reaches a customer, a platform reviewer, a customs desk or a payment partner.

Send the supplier the address map and ask them to confirm each role in writing.

The sample should include one negative example when possible. A complaint, rejected shipment, failed document request or confused customer message often shows the gap faster than a clean order. The reviewer should not treat the negative example as proof of failure. It is a stress test for the file.

If the sample exposes a gap, the team should fix the live record first and the policy note second. Customers, carriers and platforms see the live record. A polished internal rule does not help if the product page, invoice, support script or supplier instruction still says something else.

The review note should also record what the business will not expand yet. Do not add a new market, claim, bundle, route, supplier or campaign while the evidence for the current scope remains unresolved. This limit keeps a small file gap from becoming a wider operating problem.

That restraint is part of the control, not a delay tactic.

Handoff note

The handoff should be readable in ten minutes. It should name the business owner, file owner, missing evidence, accepted limit and next review trigger. If the answer depends on a chat thread or one employee memory, the record is too fragile.

Keep the handoff beside the working file. Product issues belong with listing, label, sample and complaint records. Supplier issues belong with purchase and due diligence records. Account and payment issues belong with access logs, finance approvals and platform notices.

Add an expiry trigger: a product version change, supplier change, new market, policy update, route change, complaint pattern or certificate date. Evidence that lacks a trigger can look complete long after it stops matching the live business.

Closing note

Address mismatches are easier to manage when the file labels each location.

A clear map beats a vague argument about whether addresses should match.

Reference links

• China National Enterprise Credit Information Publicity System