English Name Confusion in China Supplier Verification

English names can drift

A supplier may use one English name on its website, another in email signatures and another in a proforma invoice. That does not prove wrongdoing, but it can hide the legal entity behind the deal.

The verification file should start with Chinese legal name and unified social credit code, then list all English names used in commercial documents.

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 English names

A buyer receives a quotation under one English name, a website under another and an invoice under a third. The Chinese legal name appears only on the license.

The buyer needed an alias table before deciding whether the documents referred to the same entity.

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 alias table

List Chinese legal name, credit code, English aliases, website names, email domains and invoice names in one table.

When an English alias cannot be tied to the Chinese legal entity, ask the supplier to explain it in writing.

• Use Chinese legal name as anchor.
• Record every English alias.
• Match email domain and website names.
• Compare invoice issuer with legal entity.
• Ask for written explanation of aliases.

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.

Build the alias table before contract drafting. It prevents the wrong name from entering purchase documents.

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

English name cleanup makes supplier verification less fragile.

The buyer should know which company stands behind every alias.

Reference links

• China National Enterprise Credit Information Publicity System