Supplier Exit / Contract Termination / Transition Pages on Changzhou Manufacturer Websites: How Should They Be Accepted?

Direct answer: A supplier exit/contract termination is not "send an email saying we're done". It is a reviewable process covering trigger, contractual/legal basis, notice/cure period, settlement/damages, work-in-progress/inventory/tooling/drawings/software handover, last-time buy, second source, customer/regulatory notification and transition. Under Chinese law a contract may be terminated by agreement, by a contractual termination right, or by statutory grounds; termination takes effect when the notice reaches the other party (unless the contract/law provides otherwise), unperformed obligations end, performed obligations may be restored/remedied with damages, and settlement/liquidation clauses survive. International sales may also be governed by the CISG avoidance/notice/damages rules. A website supplier-exit page should explain "how it is triggered, noticed, settled, handed over and transitioned"—not just "we may terminate at any time". Information is current to 2026-11-06. This is a review of public rules and project practice, not legal, procurement, audit or contract advice; specifics follow the contract, the Civil Code/CISG, customer contracts and legal advice.

This guide is for procurement, SQE, quality, legal and website teams at equipment, electronics/electrical, automotive, medical device, hardware, chemical, packaging and export manufacturers in Changzhou and nearby areas. A supplier exit may be driven by performance, financial distress, compliance, strategy, EOL, a customer-directed change or contract expiry; handled badly it produces line stops, unrecoverable tooling/drawings, unapproved customer changes, scrapped inventory and warranty with no owner.

How does the exit/termination page relate to force majeure, order cancellation, supplier financial risk, PCN/EOL and quality claim pages?

The force majeure page answers notice/evidence/mitigation when performance is impossible; the order change/cancellation page answers a single order's change/cancellation; the supplier financial risk page answers insolvency/cash-flow risk; the PCN/EOL page answers change/discontinuation notice; the quality claim page answers quality losses/chargebacks; the exit/termination page answers "how the relationship ends, is handed over and transitioned". It does not replace those pages, but it uses their evidence.

Common breakpoints: stopping orders without a contractual basis; no notice/cure period; no settlement of WIP/materials/tooling/inventory; tooling/drawings/software withheld; switching suppliers without customer approval; no last-time buy/bridge stock; second source not validated; warranty/spares/service cut off; confidentiality/IP/dispute clauses not preserved; the website says "may terminate at any time/no liability". Separate "trigger—basis—notice—settlement—handover—transition—after-sales"; then procurement, SQE, legal, finance and the customer share one playbook.

This page map is editorial; the contract, Civil Code/CISG, customer contracts and legal advice control.

What triggers a supplier exit?

Common triggers: (1) performance (sustained quality/delivery/cost/service shortfall); (2) financial (insolvency/cash flow/unpaid wages/enforcement); (3) compliance (bribery/forced labour/environment/safety/data/sanctions); (4) strategy (category exit/group central procurement/geographic change); (5) EOL/discontinuation/technology obsolescence; (6) customer-directed change/customer request to switch; (7) contract expiry/non-renewal; (8) force majeure/long-term inability to perform; (9) merger/change of control. Each trigger implies a different basis/notice/cure/settlement; performance/compliance usually start with remediation/audit, financial/force majeure may require urgent switching, and a customer-directed change needs customer approval first. Do not write every exit as "buyer may terminate at any time".

Acceptance checks: trigger type; basis; urgency; remediation/audit; customer approval; contract expiry; evidence. Common gaps: no basis; stopping a poor performer without remediation; no financial early warning; compliance issue not investigated; customer-directed change not discussed; EOL not notified; expiry with no transition.

Triggers/handling are editorial; specific basis/procedure follow the contract, law and customer requirements.

How should the legal basis for termination be explained?

Under Chinese law there are at least four routes: (1) termination by agreement (both parties agree); (2) contractual termination (the contract specifies the event and the terminating party's right); (3) statutory termination (e.g. force majeure defeating the purpose, anticipatory breach, delayed performance after demand, fundamental breach); (4) expiry/completion (not termination, but the relationship ends). Relevant Civil Code articles include Article 562 (agreement/contractual termination), Article 563 (statutory termination), Article 565 (termination effective on notice reaching the other party), Article 566 (consequences/restoration/damages/security) and Article 567 (settlement/liquidation clauses survive). International sales may also be governed by CISG avoidance/notice/damages; application/exclusion is confirmed by the contract and counsel. Do not present "the buyer is unhappy" as statutory termination.

Acceptance checks: termination type; contract clause; statutory ground; notice; demand/cure; effective date; evidence; CISG/applicable law. Common gaps: no contractual basis; dissatisfaction treated as statutory termination; no demand; notice not delivered; effective date unclear; insufficient evidence; no CISG/law clause.

Legal basis follows Civil Code Articles 562/563/565/566/567, the CISG and the contract text; this is not legal advice.

How should the termination notice and cure period be written?

The notice should state: parties/contract/orders; termination type/basis (clause/ground); facts/evidence; remediation items and deadline (if applicable); effective date; treatment of WIP/inventory/tooling/drawings/software/spares; settlement/damages/retention; handover/transition; confidentiality/IP/warranty/dispute clauses that continue; contact/delivery method. Performance/compliance issues usually get a cure period/audit/corrective opportunity; fundamental breach/insolvency/safety may allow immediate termination, but still need a basis/evidence. Notice must be deliverable and on record (EMS/email/signature/notarisation); the effective date follows the contract/law. Do not rely on WeChat/verbal notice. Give a reasonable cure period—not "notice today, stop tomorrow".

Acceptance checks: notice content; basis; facts/evidence; cure period; effective date; handover/settlement; delivery; surviving clauses. Common gaps: vague notice; no basis; cure period too short; verbal only; effective date unclear; handover/settlement not stated; no proof of delivery.

Notice content/procedure is editorial; specifics follow the contract, Civil Code/CISG and legal advice.

How should settlement and damages be handled after termination?

Settlement should cover at least: delivered/accepted goods payment; work-in-progress (WIP) completion/transferability/scrap; dedicated/general materials; tooling/fixtures/gauges/software/licences; inventory/consignment/VMI; cancellation/rework/sorting/freight/storage costs; services performed but not invoiced; retention/quality retention; breach/damages/set-off; tax/invoicing. Distinguish "contractual/actually incurred/provable/mitigable"; damages are limited to foreseeable loss (per law/contract) and the non-breaching party must mitigate. After termination, a guarantor's liability/security contract follows Article 566 (unless otherwise agreed). Settlement needs a list/records/confirmation by both parties; do not "write everything off on termination".

Acceptance checks: delivered/WIP; materials/tooling/fixtures; inventory; costs; retention; damages/set-off; tax/invoice; records; mutual confirmation. Common gaps: WIP ignored; materials/tooling not compensated; inventory scrapped; costs without records; retention not returned; damages without basis; invoice/tax missed; no confirmation.

Settlement/damages are editorial; specifics follow the contract, Civil Code/CISG, tax rules and legal advice.

How should handover and transition be accepted?

The handover list should include at least: drawings/technical specifications/software/licences/passwords/data; tooling/fixtures/gauges/jigs/spares/special tools; WIP/inventory/consignment/VMI; supplier/sub-supplier list/purchase contracts; quality records/PPAP/COA/traceability; customers/contracts/orders/open items; warranty/after-sales/spares; confidentiality/IP/data deletion/return. The transition plan should state: schedule/milestones; owners; last-time buy/bridge stock; second source/new supplier audit/samples/PPAP/capacity; customer/regulatory notification/approval; trial run/switchover/discontinuation; risks/rollback. Handover is not "zip the files and send them"—it must be verifiable, producible and traceable.

Acceptance checks: drawings/software/data; tooling/fixtures/spares; WIP/inventory; sub-suppliers; quality records; customers/contracts; schedule; second source; customer approval; trial run/rollback. Common gaps: incomplete drawings; software/passwords withheld; tooling retained; spares cut off; sub-suppliers unclear; quality records missing; customer not approved; no trial run; no rollback.

Handover/transition is editorial; specifics follow the contract, customer requirements and product/regulation.

How should last-time buy, inventory and a second source be arranged?

Before exit, calculate: current orders/forecast; last-time buy (LTB) quantity/MOQ/price/lead time; bridge/safety stock; WIP/finished goods/consignment; EOL/discontinuation date; alternative materials/second source; customer approval/PPAP; storage/shelf life/scrap. Build the second source early: audit/capability/samples/testing/PPAP/small batch/mass production; do not treat "we found an alternative" as "validated". LTB must avoid both "buy too much and scrap" and "buy too little and stop the line"; use forecast + LTB + bridge + customer confirmation. Customer-directed/regulated parts need customer approval; do not stop the old supply before the switch.

Acceptance checks: LTB; MOQ/price/lead time; bridge stock; EOL; alternatives/second source; customer approval; PPAP; storage/shelf life; switchover. Common gaps: LTB not calculated; too much/too little; no bridge; second source not validated; customer not approved; old supply stopped before switch; shelf life/storage ignored.

LTB/second source is editorial; specifics follow the customer/contract/capacity/regulation.

How should customers, regulators and the website be informed?

Customer/regulatory communication follows the contract/regulation: customer-directed suppliers/PPAP/change notification/recall/quality agreements may require prior approval; medical device/automotive/aerospace may require change notification/validation; export control/sanctions/forced labour/environmental issues may require reporting. The public website page should state only the "generic exit/termination process, notice, settlement, handover, transition, contact", not specific suppliers/customers/contracts/disputes; individual exits are communicated in writing, not "publicly shamed". External statements must be truthful and verifiable; do not write "may terminate at any time/no liability/switch guaranteed".

Acceptance checks: customer notice; regulatory reporting; contract requirements; approval; website disclosure boundary; written notice; confidentiality. Common gaps: customer not approved; regulation missed; contract breached; website publicises a dispute; verbal only; confidentiality leaked.

Communication/disclosure is editorial; specifics follow the contract, regulation and customer requirements.

Which clauses survive termination?

Usually surviving: settlement/liquidation (Article 567); confidentiality; IP/licence; warranty/after-sales/spares; outstanding payment/invoice/tax; dispute resolution/jurisdiction/arbitration; limitation of liability/indemnity; data return/deletion; compliance/audit (if agreed); force majeure/notice (for open items). Termination does not affect the validity of settlement/liquidation clauses; a guarantor's liability follows Article 566 (unless otherwise agreed). The contract should state "survival", otherwise after termination there is "no basis". The website can say "after termination, settlement, confidentiality, IP, warranty and disputes are handled per contract"—not "all obligations end on termination".

Acceptance checks: settlement/liquidation; confidentiality; IP/licence; warranty/spares; payment/tax; disputes; liability limit; data; audit; survival clause. Common gaps: no survival clause; warranty cut off; IP unclear; confidentiality lapses; no dispute route; data not deleted; audit right lost.

Survival clauses are editorial; specifics follow the contract, Civil Code/CISG and legal advice.

How should the website exit/termination page be written?

Suggested content: (1) scope/trigger types; (2) contractual/legal basis; (3) notice/cure period/effectiveness; (4) settlement/damages; (5) handover (drawings/tooling/software/data/spares); (6) last-time buy/inventory/second source; (7) customer/regulatory notification; (8) survival clauses (confidentiality/IP/warranty/disputes); (9) contact/version/update date. The public page explains the generic process/principles, not specific suppliers/customers/contracts/disputes; individual exits are in writing. The page must be truthful and verifiable; do not write "may terminate at any time/no liability/switch guaranteed/zero risk".

The English page should use consistent terms (supplier exit, termination, cure period, WIP, last-time buy, transition, survival, tooling transfer) and state the review date. Link it to the supplier code of conduct, PCN/EOL, financial risk, quality claim and order cancellation pages.

This page structure is editorial; external statements must be truthful and verifiable, per the contract/law/customer requirements.

What must not be written?

High-risk claims: "may terminate at any time/without cause" (contract/law may restrict); "no liability whatsoever" (statutory/contractual liability cannot be waived in one sentence); "all obligations end on termination" (settlement/confidentiality/IP/warranty/disputes may survive); "the supplier must hand over unconditionally/waive claims" (depends on contract/law); "the customer will certainly approve a switch" (customer-directed/PPAP/change notice); "the second source can ramp up immediately" (audit/samples/PPAP/capacity); "the more last-time buy the safer" (inventory/scrap/shelf life); "publish a supplier blacklist/dispute on the website" (reputation/privacy/contract risk); "switch guaranteed/zero line stop" (cannot guarantee). These are inaccurate or misstate contract/customer/operational risk.

Safer wording: "Exit/termination follows the contractual/legal basis, notice/cure period, settlement/handover, last-time buy/second source, customer/regulatory notification and survival clauses; specifics follow the contract and legal advice." The website explains the generic process, not individual cases; external promotion must comply with advertising/fair-competition law; customer/supplier data needs authorisation/redaction.

These red lines are editorial; whether a statement breaches a contract/infringes rights is determined by the contract/regulator—not this article.

Go-live acceptance checklist

Ten checks: trigger/basis, notice/cure, settlement, handover, last-time buy/inventory, second source, customer/regulatory, survival clauses, website disclosure, records/version. Each needs an owner, evidence and review date. The pass condition is not "the page says we can terminate", but that a supplier/internal team can find the basis, notice, settlement, handover and transition path.

Before go-live, run one real exit scenario through: trigger → basis → notice/cure → settlement → handover → LTB/second source → customer/regulatory → survival → review. Any step that fails is a gap in the page or contract.

This checklist is editorial; specifics follow the contract, Civil Code/CISG, customer requirements and legal advice.

Who should read this, who should not, and what decisions does it support?

It suits procurement, SQE, quality, legal and website teams at equipment, electronics/electrical, automotive, medical device, hardware, chemical, packaging and export manufacturers in Changzhou and nearby areas; also companies handling a poor performer, financial risk, compliance issue, EOL, customer-directed change or contract expiry. It does not suit companies with no supplier relationship, one-off transactions, or teams wanting one page to replace contract/legal/customer approval/switch validation.

Read it if a supplier is persistently underperforming; there is financial/compliance risk; EOL/customer-directed change; contract expiry; tooling/drawings/software handover; second source/customer approval. Skip it if you terminate at will, do not settle, do not hand over, do not inform the customer, or publish a blacklist. It supports self-review of trigger/basis, notice/cure, settlement, handover, LTB/second source, customer/regulatory, survival and page disclosure.

FAQ

Can a supplier be terminated "at any time"?

Not necessarily. It depends on the contract, statutory grounds, notice and cure period; termination by agreement, contractual termination, statutory termination and expiry are different. Terminating without a basis/notice/cure may be a breach; even urgent cases (fundamental breach/insolvency/safety) need evidence/procedure. Confirm with legal counsel.

When does a termination notice take effect?

Civil Code Article 565: the contract is terminated when the notice reaches the other party; if the notice states that the contract terminates automatically if the debtor fails to perform within a period, follow the notice. The contract/law/delivery method also matter. The notice must be deliverable and on record, with basis, cure period, effective date, settlement/handover—not verbal/WeChat only.

What must be settled after termination?

Delivered/accepted payment, WIP, dedicated/general materials, tooling/fixtures/gauges/software, inventory/consignment, cancellation/rework/freight/storage costs, retention/quality retention, breach/damages/set-off, invoice/tax. Distinguish contractual/actually incurred/provable/mitigable; a guarantor's liability follows Article 566 (unless otherwise agreed).

How should tooling/drawings/software be handed over?

Per contract/ownership/licence: drawings/specifications/software/passwords/data, tooling/fixtures/gauges/spares, WIP/inventory, sub-suppliers/contracts, quality records/PPAP, customers/contracts/open items. Handover must be verifiable, producible and traceable; software/data need licence/deletion/return; withholding may breach the contract/infringe rights. Confirm with the contract/legal counsel.

How early should a second source be prepared?

Depends on the category/customer/PPAP/capacity: audit/samples/testing/PPAP/small batch/mass production may take weeks to months; customer-directed/regulated parts also need customer approval. Do not stop the old supply just because "an alternative was found"; validate/trial run/bridge stock/rollback before switching.

Can the website say "may terminate at any time/no liability"?

Not recommended. Write "per contract/legal basis, notice/cure, settlement, handover, LTB/second source, customer/regulatory and survival clauses; specifics follow the contract and legal advice". The website is a generic process description, does not disclose individual suppliers/customers/disputes, and makes no "zero risk/switch guaranteed" promise.

One-sentence takeaway

A Changzhou manufacturer's supplier exit/termination page is not about "we may terminate at any time". It should turn trigger/basis, notice/cure, settlement, handover (drawings/tooling/software/spares), last-time buy/second source, customer/regulatory and survival clauses into a reviewable process—so a supplier/internal team can find the basis, settlement, handover and transition path.

Method and limitations

This is a review of public rules and project practice, not an audit, legal, procurement or contract opinion on any company, supplier, contract or exit. No undisclosed supplier, contract, customer or exit data were used. Triggers, processes, settlement, handover, LTB/second source and acceptance items are editorial suggestions, not legal/procurement conclusions. Specific termination basis, notice, settlement, handover, customer approval and survival clauses depend on the contract, Civil Code/CISG, customer contracts and legal advice.

Sources and scope

Information is current to 2026-11-06. The following are official legal/standards pages; their text controls.

1. Civil Code of the People's Republic of China: NPC/CAC. Articles 562/563/565/566/567: termination by agreement/contract/statute, notice, consequences, settlement/liquidation clauses.
2. UNCITRAL, CISG: UNCITRAL. Avoidance/notice/damages in international sales (if applicable).
3. ISO, ISO 9001 (quality management systems): ISO. Clause 8.4 control of externally provided processes, products and services (see the standard text).
4. ISO, ISO 44001:2017 — Collaborative business relationships: ISO. Lifecycle/exit/governance framework for collaborative relationships.