Legal Representative Changes in Chinese Supplier Reviews

A name change in management needs context

The legal representative appears in Chinese company records and often signs or controls formal matters. A change does not prove danger, but buyers should know when it happened and whether other records changed at the same time.

The review should compare legal representative changes with shareholder changes, address changes, business scope changes, litigation, bank changes and contract signer changes. Multiple changes near a large order deserve more attention than one old update.

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: new signer, old bank account

A supplier changes its legal representative and asks the buyer to sign with a new manager. The bank account stays the same, but the contract authorization is missing.

The buyer should request authorization and update the supplier file before placing a larger order.

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.

Write a change note

The note should say what changed, when it changed, which records were checked and whether the change affects contract authority or payment.

If several changes cluster together, add a management or ownership question to the next supplier call.

• Record legal representative change date.
• Check current contract signer authority.
• Compare ownership and address changes.
• Review bank details after management changes.
• Keep a short dated decision note.

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.

Ask who has authority to sign the current order and save the answer with the company record.

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

Management changes deserve context, not panic.

A dated note keeps the buyer from relying on an old company profile.

Reference links

• China National Enterprise Credit Information Publicity System