What to save in a China supplier due diligence file in 2026

Source note: Based on public due diligence concepts in forced-labor and import-compliance guidance. Source background.

A due diligence file is useful only if someone can understand it later. Buyers should save evidence in a way that shows what was checked, what was missing, and why the transaction was approved.

A supplier file should tell a story in records: who was checked, what was confirmed, what did not match, and why the buyer continued or paused. That is more useful than a folder full of screenshots that nobody can interpret six months later.

Teams often collect screenshots, certificates, chat logs, and invoices but never connect them. When a dispute occurs, the file becomes a pile of attachments instead of a decision record.

The common failure is collecting evidence without connecting it to a decision. When a problem appears, the team cannot tell what was actually approved. A short decision note can save hours later because it explains the business judgment at the time.

Use folders for identity, ownership, payment, product, export route, compliance, communication, and decision notes. Date each important item.

Each document should be tied to an entity and a transaction role. Keep the file readable for someone who did not join the calls.

• What fact does this document prove?
• Which entity does it belong to?
• Does it support or conflict with the supplier's story?

If a later reviewer cannot tell what was approved, the file has not done its job.

Update the file at onboarding, deposit payment, pre-shipment, balance payment, and any later supplier-structure change.

Update the file at onboarding, deposit, pre-shipment, balance payment, and whenever the supplier structure changes.

A credible file lets a new reviewer understand the decision without calling the sales team. A weak file contains many documents but no reasoning.

The file should explain why the buyer moved, paused, or asked for more evidence.

Close the review with a short note: the counterparty being checked, the document set received, the unresolved point, and the decision taken.

Write it for the person who may read the file later, not for the person who already knows the deal. That keeps the record useful if a shipment, payment, or customer audit becomes messy.

For sensitive orders, pair this review with specialist advice and a documented approval trail.

For this topic, keep the review tied to the actual order rather than a general supplier profile. In the case of What to save in a China supplier due diligence file in 2026, the buyer should write down the exact decision it needs to make: whether to pay, sign, ship samples, accept a document, or escalate the file for management approval.

The buyer should close the review with a short decision note. Name the supplier, the order, the key risk checked, the evidence received, and the point that still needs judgment. This note prevents a long message thread from becoming the only record of the decision.

If the buyer proceeds despite an unresolved point, state the control that reduces the risk. That control may be a smaller deposit, staged shipment, pre-shipment inspection, customer approval, or a second source. The goal is to make the commercial decision visible before pressure builds.

A short closing note should name the next action and the person responsible for it. Without that note, the same question often returns during balance payment, shipment release, or a later dispute, when the buyer has less room to ask for documents.

Buyers should also keep the rejected path visible. If the supplier could not explain a record, refused to identify the right company, or sent a document that did not match the order, write that fact into the file. A rejected explanation can matter as much as an accepted document because it shows how the buyer controlled the decision.

The review should also save rejected evidence. A wrong license, outdated certificate, mismatched bank notice, or incomplete explanation can matter later because it shows what the supplier tried to use and why the buyer asked for a cleaner record.

Use simple version names for revised files so the final decision does not depend on memory. Date each revision clearly.