Related: Dispute Resolution · Company Formation.
Direct answer
- Formation is not enough. A reliable contract identifies the correct PRC entity and preserves evidence connecting the signatory, seal or electronic account to that entity. A chop is an important practical indicator of assent, but not every contract requires one and a stamped document is not automatically safe.
- Write measurable performance. Specs, inspection, acceptance, and liquidated damages that a Chinese tribunal can apply beat elegant common-law prose that local practice ignores.
- Choose the dispute path before the fight. Court vs arbitration, seat, language, and interim-measures reality should match where assets and evidence sit.
- Bilingual drafts need a controlling-language clause and a lawyer who reads for meaning conflicts, not only dictionary translation.
At a glance
| Template / topic | Must nail | Frequent gap |
|---|---|---|
| Formation and authority | Legal rep, articles, official company seal | Contract-seal / finance-seal misuse |
| Sales / supply | Specs, inspection, quality metrics, Incoterms | Vague acceptance criteria |
| Distribution / agency | Territory, exclusivity, online channels, exit | Unclear IP and MAP control |
| OEM / ODM | Tooling, molds, IP, audit, subcontract bans | No mold ownership clause |
| Services / SaaS | Data, SLAs, liability caps, deliverable IP | Ignoring localization duties |
| Payment security | Deposits, guarantees matched to risk | Unsecured full prepayment |
| Liquidated damages | Realistic figures + loss evidence plan | Punitive figures adjusted downward |
| Dispute clause | Forum, seat, language, rules named clearly | Copy-paste prestige institution only |
Scope and legal framework
In scope: mainland PRC commercial contract formation and validity themes under the Civil Code; common templates for cross-border trade and services; payment and performance; e-commerce interfaces; M&A/investment contract touchpoints; dispute-clause design at overview level.
Out of scope: full litigation/arbitration procedure (see dispute guide); specialized IP prosecution (see IP guide); employment contracts (see employment guide).
Book III of the Civil Code addresses offer, acceptance, contract form, performance and remedies. Civil Code Article 469 recognises written, oral and other forms and treats qualifying retrievable data messages as writing. A particular form may still be required by another law or by the parties; formal written execution remains operationally advisable for material deals.
Practical workflow
- Counterparty KYC - licence, legal representative, chops, beneficial owners, litigation search.
- Draft bilingual - decide controlling language; align commercial meaning, not just words.
- Chop execution - company-seal protocol and signature blocks that match practice.
- Perform and file evidence - delivery, quality, and payment records as if litigation is coming.
Payment, guarantees, and performance
- Name the event that makes payment due.
- Deposits, guarantees and retainage need a release rule.
- Inspection and acceptance facts start many clocks.
- A liquidated-damages figure can be adjusted if it is grossly higher or lower than loss.
Deposits, advance payments, bank guarantees, and personal guarantees from founders each carry different enforcement profiles. Late-performance remedies include agreed damages (subject to adjustment under Civil Code principles) and carefully drafted termination rights.
E-commerce and platform sales
Online channel control, MAP policies, live-streaming promotions, and consumer-protection rules affect brand owners. Platform rules can change practical enforcement faster than statutes.
M&A and investment contracts
Share purchase, JV, and capital-increase documents interact with foreign-investment negative lists, merger filing thresholds, and sector licences. See the company formation guide.
Common mistakes
- Treating execution as a slogan: either assuming every contract needs a chop or assuming any signature is enough without checking identity, authority and surrounding evidence.
- Leaving English and Chinese versions inconsistent with no controlling-language clause.
- OEM deals without mold/tooling ownership and audit rights.
- Liquidated damages set as punishment rather than a defensible estimate of loss.
- Dispute clauses that name a prestigious forum but ignore asset location and interim measures.
- Treating WeChat negotiations as a substitute for a chopped formal contract on major deals.
Action checklist
- Verify counterparty chops and legal-representative authority.
- Define specs, acceptance, and quality remedies in measurable terms.
- Allocate IP and tooling ownership for any China manufacturing.
- Set payment security proportional to performance risk.
- Draft a usable dispute clause - not a copy-paste orphan.
- Archive the executed Chinese version and seal specimens.
Decision tools and contract architecture
The following tools convert the proposal's core principle into an operating system: identify the right party, establish a defensible execution route, write measurable performance, and create evidence as the deal runs.
Decision tree: can this execution route be defended?
- A company chop on the agreed text is still the strongest ordinary proof.
- A wet-ink signature needs proof the signer had authority.
- WeChat or email can bind if the terms are complete and attributable, but they are harder to prove.
- A sales confirmation should match the chopped or signed form, not contradict it.
Registered Chinese name, unified social credit code, address and bank-account match checked
Do not rely on a brand, factory nickname, Hong Kong affiliate or payment recipient as if they were interchangeable.
Legal representative, authorised signatory, company/contract chop or controlled e-signature.
Use a power of attorney, board approval, appointment evidence, seal specimen or platform audit trail proportionate to risk.
Exchange complete identical counterparts, prohibit post-signature changes and retain the execution record.
Legal outcome remains fact-dependent. Civil Code Article 504 addresses acts by a legal representative exceeding internal authority; it is not a substitute for diligence.
Operational timeline: contract to evidence file
This is a procedural sequence, not a statutory filing deadline. Sector approvals, court steps and arbitral timetables vary.
Entity, licence, authority, account and regulatory checks.
Output: verification pack
Specifications, language, risk allocation and annexes.
Output: issues table
Controlled signing, chop or e-sign process.
Output: complete counterpart
POs, delivery, testing, acceptance, changes and payment.
Output: transaction file
Notice, cure, mitigation, preservation and forum review.
Output: claim-ready record
Statutory matrix: rule, trigger and qualification
| Provision | Core rule | Trigger / threshold | Qualification or exception |
|---|---|---|---|
| Civil Code Art. 469 | Contracts may use written, oral or other form; retrievable data messages can be written form. | The content can be tangibly represented and accessed for reference. | Another law or the parties may require a particular form. |
| Arts. 471 and 481 | Parties may contract through offer and acceptance; acceptance must ordinarily arrive within the offer's period. | Communications and conduct satisfy the applicable formation rules. | A quotation, PO or message chain may matter before the planned long form is signed. |
| Art. 490 | Where a written contract is required, signature, seal or fingerprint ordinarily marks formation. | A party performs the principal obligation and the other accepts it before formal execution. | The contract may form upon acceptance of performance despite missing formal execution. |
| Art. 504 | An act by a legal representative exceeding internal authority can bind the legal person. | The act is made in the legal person's name. | Not where the counterparty knew or should have known of the restriction. |
| Arts. 509 and 577 | Perform as agreed and in good faith; non-performance or defective performance can trigger breach liability. | An obligation is due and is not performed as agreed. | Remedy and proof depend on the contract, facts and other applicable rules. |
| Art. 585 | Parties may agree liquidated damages or a loss-calculation method. | Agreed amount is substantially below loss or excessively above loss. | A court or tribunal may adjust on request; evidence remains important. |
| E-Signature Law Arts. 13–14 | A reliable electronic signature has the same legal effect as a handwritten signature or seal. | Exclusive control, detectability of changes and reliability conditions are satisfied. | Platform labels alone do not prove reliability; preserve authentication and audit records. |
| SPC Evidence Rules Arts. 14–15, 93–94 | Instant messages and other digital records can be electronic evidence. | Identity, completeness, system reliability, preservation and ordinary-business creation support authenticity. | Cropped screenshots alone may be weak; original or equivalent output and context matter. |
Comparison: PRC court litigation or arbitration?
- A PRC court clause can help with local interim measures.
- Onshore arbitration (CIETAC, BAC, SHIAC and others) is a designed choice, not a slogan.
- Offshore arbitration depends on New York Convention enforcement facts.
- A silent clause usually leaves you in court, not in your preferred institution.
| Decision factor | PRC court route | Arbitration route |
|---|---|---|
| Best fit | Mainland counterparty/assets, direct court procedure and a valid jurisdictional connection. | Commercial parties seeking a chosen institution/seat, procedural flexibility or cross-border award route. |
| Clause design | Identify a competent court and preserve a sufficient connection; mandatory jurisdiction rules still apply. | Name the institution, seat, language, scope and arbitrator arrangements clearly. |
| Interim protection | Direct applications under applicable PRC procedure. | Depends on seat, institution and court assistance; plan the preservation route before signing. |
| Confidentiality | Court process and judgments may be less private, subject to legal rules. | Often a reason to arbitrate, but scope depends on rules, law and agreement. |
| Evidence burden | Both routes reward contemporaneous Chinese-language operational records, authenticated electronic evidence and a coherent loss calculation. | |
Annotated document structure
Chinese legal name, code, address, notices, signatory and execution route.
Scope, specifications, price, tax, currency, orders, delivery and Incoterms.
Inspection, acceptance, rejection, deemed acceptance and signed change control.
IP, data, tooling, warranty, indemnity, caps, insurance and force majeure.
Cure, suspension, termination, inventory/tooling return, remedies, notices and forum.
Drawings, BOM, SLA, test plan, price list, authorised contacts and reporting forms.
Legal and contractual authority hierarchy
- Mandatory PRC rules prevail over contrary contract wording.
- The controlling language version of the main contract comes next.
- Schedules and purchase orders must not contradict the main text.
- Later chats are evidence, not an automatic amendment.
Foreign governing-law language does not override mandatory PRC rules that apply to the transaction. Contract templates and platform rules sit below governing law.
Illustrative liquidated-damages calculation
subject to the contractual cap, exclusions, mitigation record and possible adjustment under Civil Code Article 585.
Illustration: RMB 500,000 × 0.0005 × 12 = RMB 3,000, before applying any cap or legal adjustment. This example is not a recommended rate, statutory tariff, outcome prediction or original empirical dataset.
Compliance and evidence risk matrix
Control: reconcile before payment or execution.
Control: annex a measurable protocol.
Control: obtain clause-specific advice.
Control: meaning reconciliation and controlling-language clause.
Control: authorised-channel and change-control rules.
Control: periodic file audit.
Pre-signing compliance checklist
- Match the Chinese legal name, unified social credit code, licence, address, bank account, invoice issuer and performing entity.
- Document the authorised signatory, seal type or e-signature account and preserve supporting authority proportionate to deal risk.
- Meaning-check both languages for price, IP/data, quality, acceptance, remedies, termination and dispute clauses.
- Attach measurable specifications, test method, sample size, approver, deadline, rejection/cure path and change-control form.
- Map sector licences, import/export, product, data, foreign-investment and competition constraints before relying on the contract.
- Choose payment security and remedies that match the performance risk and evidence the business can actually produce.
- Identify binding notice channels; control how POs, email, e-sign platforms and WeChat may create or change obligations.
- Test the dispute clause against asset location, interim relief, language, service, institution/court competence and enforcement route.
- Create the verification, execution and performance folders before signing; name owners and retention rules.
Provision-level source cards
Arts. 469, 471, 481 and 490: form, offer/acceptance and execution/performance route. Art. 504: legal-representative authority. Arts. 509 and 577: performance and breach. Art. 585: agreed damages and adjustment.
National Laws and Regulations DatabaseArts. 2–6: electronic signature/data-message concepts and written/original/retention functions. Arts. 13–14: reliable signature conditions and legal effect.
MOFCOM laws databaseArts. 14–15 identify electronic data and original/equivalent output. Arts. 93–94 state authenticity factors and circumstances supporting authenticity.
Supreme People's CourtCorporate organisation and legal-representative context. Use together with Civil Code authority rules and the company's registered information.
State Council / official textAccess checked 11 August 2026. The cards identify the provisions supporting the visual tools; they do not replace the full official text or transaction-specific advice.
Revision history
| Version | Date (UTC) | Summary |
|---|---|---|
2026-08-11-core-guides-v1 | 2026-08-11 | Batch 1 content upgrade: direct answer, at-a-glance table, primary-authority list, common mistakes/checklist hardening, authorship and legal-review disclosure, revision history; reviewer fields aligned to confirmed DJCF counsel (English names). |
| Live baseline | 2026-07-30 / various 2026-08 edits | Original national practice guide structure without full E-E-A-T upgrade standard. |
City guides
Compare local practice and find counsel where this practice is covered: