Direct answer: A procurement contract-change and supplement-agreement page is not "sign an amendment and stamp it". The page should state: what counts as a contract change (scope/specification/quantity/price/delivery/place/payment/warranty/subcontracting/suspension/termination) and what is only performance detail; how a change is initiated and how impact is assessed (price/delivery/quality/inventory/cash flow/risk); who approves and to what authority; how the supplement/variation order is drafted (number, basis, old vs new clauses, effective date, retroactivity, unchanged clauses, signature); how systems/orders/acceptance/invoices/payment/budget are synchronised; disputes, evidence and archive; public boundary. On the rules: MOF Internal Control Application Guideline No. 16 (Contract Management) Article 11 allows supplementary agreement where terms are unclear; Article 12 requires timely reporting of contract change/termination, mutual agreement and handling under authority and procedure; Article 15 requires contract registration to cover conclusion, performance and change; Guideline No. 7 (Procurement) requires price, contract, acceptance, payment and records control; the Tendering and Bidding Law Article 46 requires a written contract per the tender documents and the winner's bid, and prohibits another agreement departing from the substantive content. This article is current to 2026-11-10 and is a summary of public rules and page method, not legal/procurement/audit advice; the company's contract policy, authority and applicable project rules control.
This article is for procurement, legal, finance, quality, R&D, planning and website teams at equipment, electronics, automotive-parts, medical-device, hardware, chemical, packaging and export manufacturers in Changzhou and nearby. It covers how to write and accept a procurement contract-change and supplement-agreement page. The usual gap is "oral changes, do-then-sign, price changed but delivery not, no old-vs-new clauses, approval beyond authority, departure agreements in tendered projects, systems and contract out of sync", ending with a page that only says "flexible response to change", while acceptance/payment/audit/disputes still disagree.
First classify: what changed, and is it a contract change. Then calculate: price/delivery/quality/inventory/cash-flow impact. Finally put it in writing: old vs new clauses, effective date and retroactivity, with approval, systems, acceptance and payment synchronised. Changing only the price is not change management.
How does this page relate to contract signing, order change, price linkage, quantity tolerance, assignment and dispute pages?
The contract-change/supplement page answers "how procurement contract terms/scope/quantity/price/delivery are changed, who approves, how it is documented and executed"; the contract signing/technical quality agreement page answers "how terms are set the first time"; the order change/cancellation/expedite page answers "how customer orders change within the change window and how cancellation/expedite is charged"; the price linkage page answers "how index triggers adjust price"; the quantity tolerance page answers "over/under shipment/measurement/reconciliation"; the assignment/subcontracting page answers "changing the entity/performer"; the contract dispute page answers "what to do when negotiation fails". Contract change is the main page for "how an effective contract is modified" and cannot be replaced by an order-change or price-linkage page.
Common breaks: oral changes/WeChat confirmation; do-then-sign; price changed but delivery/quality/inventory not; no old-vs-new clauses; approval beyond authority; departure agreements in tendered projects; contract changed but system not; acceptance/invoice/payment still on old terms; missing change records. The page separates "classification—assessment—approval—clauses—execution—archive—boundary" so procurement/legal/finance/quality/R&D/planning share one vocabulary.
| Page | Question it answers | Key content | Cannot replace |
|---|---|---|---|
| Contract change/supplement | How an effective contract is modified | Classification, assessment, approval, clauses, execution | First signing |
| Contract signing/quality agreement | How terms are set first | Scope, price, quality, breach | Later changes |
| Order change/cancellation/expedite | How customer orders change | Change window, cancellation, expedite fee | Procurement contract change |
| Price linkage | How index triggers adjust price | Index, formula, window | Scope/quantity change |
| Quantity tolerance | Over/under shipment/measurement | Tolerance, weighing, replenishment | Contract clause change |
| Assignment/subcontracting | Changing entity/performer | Assignment, subcontracting, control | Term adjustment |
| Contract dispute | What to do when talks fail | Negotiation, arbitration, litigation | Change management |
Page relationships are editorial; the company's contract policy, authority and applicable project rules control.
What counts as a contract change, and what does not?
Usually a contract change: scope/workload, technical specification/drawings, quantity/batch, price/tax rate/currency, delivery/place/Incoterms, payment/terms/prepayment, warranty/acceptance standard, packaging/logistics, subcontracting/performer, suspension/extension/termination. Usually not a contract change: performance details that do not affect rights/obligations (contact person, minor delivery-time adjustment, packaging label position), options already agreed (within quantity tolerance, price-linkage formula, framework call-off), internal scheduling. The boundary should state "change type/trigger/who decides/record", and make clear that an agreed mechanism prevails and does not require a separate supplement.
Acceptance checks: change-type list; examples of counts/does not count; boundary with order change/price linkage/quantity tolerance/assignment; decision owner; records; mechanism first. Common gaps: every adjustment called a change; should sign but does not; order/email used instead of contract; duplicate changes; unclear boundary.
| Type | What to write | Evidence | Common gap |
|---|---|---|---|
| Scope/specification | Work scope, drawings, technical agreement, acceptance | Change request | Oral drawing change |
| Quantity/batch | Quantity, batch, MOQ, adjustment outside tolerance | Order/agreement | Order used instead |
| Price/tax/currency | Unit price, tax, currency, FX, formula | Quote/calculation | Price only |
| Delivery/place | Delivery, partial, place, Incoterms | Agreement | Oral promise |
| Payment/terms | Payment terms, prepayment, settlement | Agreement | No approval |
| Warranty/acceptance | Warranty, acceptance standard, spares | Quality agreement | Quality missing |
| Entity/subcontracting | Assignment, subcontracting, control change | Due diligence/approval | Mixed with change |
| Not a change | Performance details/options/internal scheduling | Policy | Over-changing |
The boundary is editorial; the contract, company policy and applicable rules control.
How should change initiation and impact assessment be accepted?
Initiation should state at least: who raises (procurement/R&D/quality/planning/supplier/customer), why (design/specification, quantity, supply, price/index, policy, force majeure), what changes, urgency, expected effective date, attachments (drawings/specification/quote/minutes). Impact assessment should state at least: price (incremental cost/unit price/tax/tooling/freight, using the original pricing basis or cost model), delivery/capacity, quality/validation (sample/PPAP/inspection), inventory (raw/WIP/finished/obsolete), cash flow/budget, contract/compliance risk, alternatives and consequences of not changing. Assess "incremental only, no double counting", and separate from price linkage/VA/VE savings.
Acceptance checks: initiator/reason; change content; urgency/effective date; attachments; price increment; delivery/capacity; quality/validation; inventory; cash flow/budget; risk; alternatives/no-change; review. Common gaps: no request; oral; price only; inventory/quality missing; double counting; no alternative.
| Item | What to write | Evidence | Common gap |
|---|---|---|---|
| Initiator/reason | Who/why/source | Request form | Oral request |
| Change content | Scope/spec/quantity/price/delivery/payment | Attachment | Unclear |
| Urgency/effective date | Normal/urgent, expected effective, retroactive need | Request | Do-then-sign |
| Price impact | Incremental cost, unit price, tax, tooling/freight | Quote/model | Unit price only |
| Delivery/capacity | Delivery, partial, capacity, bottleneck | Plan | Delivery missing |
| Quality/validation | Sample, PPAP, inspection, warranty | Quality record | Validation missing |
| Inventory/cash flow | Raw/WIP/finished/obsolete, budget/terms | Inventory/finance | Inventory missing |
| Alternative/no change | Alternatives, consequences, risk | Assessment | No comparison |
Impact assessment is editorial; the company's cost, planning, quality and finance basis control.
How should approval, authority and the tendering red line be accepted?
Approval should state at least: change value/percentage thresholds, escalation when delivery/quality/compliance/safety is affected, initiator/reviewer/approver/signer roles, legal/finance/technical sign-off, conflict-of-interest recusal, and the deadline for after-the-fact confirmation of urgent changes. Guideline No. 16 Article 12 requires timely reporting where there is unfairness, error, fraud or policy/market change, mutual agreement and handling under authority and procedure; Article 15 requires change registration. For projects subject to mandatory tendering, the Tendering and Bidding Law Article 46 requires a written contract per the tender documents and the winner's bid and prohibits another agreement departing from the substantive content; where substantive change is involved, legal/tender management should first decide whether re-tendering or approval is required, rather than "routing around" bid commitments in a supplement.
Acceptance checks: value/risk thresholds; roles/sign-off; urgent change; recusal; tender-project judgment; re-tender/approval; records. Common gaps: no thresholds; beyond authority; urgent change not ratified; legal not involved; departure agreement in tendered project; no judgment record.
| Item | What to write | Evidence | Common gap |
|---|---|---|---|
| Value/percentage threshold | Approval tiers by increment/contract ratio | Authority table | No thresholds |
| Risk escalation | Delivery/quality/compliance/safety triggers | Policy | Value only |
| Roles/sign-off | Initiate/review/approve/sign, legal/finance/technical | Approval | Beyond authority |
| Urgent change | Pre-conditions, after-the-fact deadline | Record | Not ratified |
| Conflicts of interest | Declaration/recusal | Declaration | No recusal |
| Tender project | Substantive departure? re-tender? | Legal opinion | Sign anyway |
| Approval record | Version/opinion/condition/date | System | No record |
| Signature authority | Power of attorney/seal/signer | Authority/seal | Unauthorised |
Approval/red line are editorial; the company's authority, contracts and applicable tendering rules control, and it is not legal advice.
How should the supplement agreement/variation order be drafted and accepted?
A supplement should state at least: number/linked master contract, parties, recitals (original contract/reason), changed scope, old-vs-new clause comparison (original text/replacement), price/tax/currency, delivery/place/Incoterms, payment/terms, quality/acceptance/warranty, effective date/retroactive scope, unchanged clauses remain valid, precedence in conflict, attachments, signature/seal. "Price adjusted to X" is not enough; someone who did not attend the negotiation must be able to execute and reconcile from the document. A variation order suits simple/urgent changes but still needs number, basis, amount, time, approval and settlement; it cannot replace a major supplement.
Acceptance checks: number/link; parties; recitals; old/new clauses; price/tax; delivery/payment/quality; effective/retroactive; unchanged clauses; precedence; attachments; signature. Common gaps: no number; new price only; old clause not superseded; unclear retroactivity; missing attachment; incomplete signature.
| Clause | What to write | Evidence | Common gap |
|---|---|---|---|
| Number/link | Supplement number, master contract number | Register | No number |
| Parties/recitals | Parties, original contract, reason | Agreement | Reason unclear |
| Scope | Changed work/specification/quantity | Attachment | Vague scope |
| Old/new clauses | Original/replacement, clause number | Comparison | New price only |
| Price/tax/currency | Unit price, tax, currency, FX | Agreement | Tax/currency missing |
| Delivery/payment/quality | Delivery, place, terms, acceptance, warranty | Agreement | Price only |
| Effective/retroactive | Effective date, retroactive scope, conditions | Agreement | Unclear |
| Unchanged/conflict | Unchanged clauses valid, precedence | Agreement | Old clause conflict |
The clause list is editorial; the company's contract template, legal review and contract control.
How should execution, system synchronisation and reconciliation be accepted?
After the change takes effect, synchronise at least: contract register/version, price master, purchase order/delivery, budget/commitment, inventory/safety stock, quality plan/inspection standard, supplier portal/statement, invoice/payment terms, insurance/guarantee. Execution should state who updates what and when, who reviews, how the old version is invalidated, and how systems reconcile; the first order/payment verifies "contract—order—acceptance—invoice—payment" consistency. Guideline No. 16 Article 14 requires finance to settle after checking contract terms and to refuse payment where performance is not per contract or a written contract should have been signed; Article 15 requires change registration/archive. If systems are not synchronised, the change stays on paper.
Acceptance checks: register/version; price master; order/delivery; budget/inventory; quality; reconciliation; invoice/payment; insurance/guarantee; first-order validation; old version invalidated. Common gaps: contract changed but system not; order at old price; budget not adjusted; acceptance on old standard; invoice at new price but order at old; no first-order validation.
| System/step | What to write | Evidence | Common gap |
|---|---|---|---|
| Contract register | Version, change number, effective date, status | Register | Version chaos |
| Price master | New unit price, tax, currency, effective date | System | Old price |
| Order/delivery | Quantity, delivery, place, partial | Order | Order unchanged |
| Budget/inventory | Commitment, safety stock, obsolete | System | Budget unchanged |
| Quality/acceptance | Inspection, sample/PPAP, warranty | Quality record | Old standard |
| Reconciliation/invoice | Statement, invoice, tax, payment terms | Reconciliation | Three-way mismatch |
| Insurance/guarantee | Cover, guarantee, security, validity | Policy/guarantee | Not updated |
| First-order validation | Contract—order—acceptance—invoice—payment consistent | Sample check | No validation |
System synchronisation is editorial; the company's ERP/contract-system capability and finance policy control.
How should disputes, evidence and archive be accepted?
Common change disputes: whether the change exists, oral promises, price increment, retroactive scope, delivery responsibility, quality responsibility, whether old clauses still apply. The evidence chain should include at least: change request, impact assessment, quote/cost model, minutes/emails, approval records, supplement/variation order, order/delivery, acceptance/inspection, invoice/payment, correspondence. Archive by master contract + change number + version, able to answer "who approved what and when, from which batch/payment it applies"; e-signature/scans must be verifiable. Guideline No. 16 Article 13 requires dispute handling through negotiation/arbitration/litigation with authority recorded; Article 15 requires change registration/archive.
Acceptance checks: dispute types; evidence list; version/number; approval chain; effective evidence; e-signature/scan; archive; access. Common gaps: WeChat only; no version; missing approval; no effective-date evidence; scattered archive; untraceable.
How should the website page be written, and what must not be published?
Suggested sections: (1) change definition/boundary; (2) initiation and impact assessment; (3) approval/authority/tendering red line; (4) supplement/variation-order elements; (5) execution/system synchronisation/reconciliation; (6) disputes/evidence/archive; (7) contact window/update date. The public page explains "scope, process, roles, approval, clause elements, records" and does not publish specific contracts/prices/suppliers/customers, change registers, cost details, approval opinions, dispute details or system screenshots. The English page should use consistent terms (contract change, variation order, supplement agreement, scope change, impact assessment, retroactive adjustment, approval authority, contract register, three-way match) and state the cut-off date.
Do not turn the change page into "flexible response/change anytime", and do not claim "zero change/zero dispute" if it cannot be proven. The page should let procurement/legal/finance/quality/R&D judge "whether this change should be signed, who approves, how to calculate, how to execute", without exposing contract and price information.
Go-live acceptance checklist
Ten checks: change definition/boundary; initiation/impact assessment; approval/authority; tendering red line; supplement elements; execution/system synchronisation; reconciliation/first-order validation; disputes/evidence; archive/access; public boundary. Each needs evidence and a review date. The pass standard is not "there is a supplement template", but that procurement/legal/finance/quality can judge whether a change exists, how price/delivery/quality are calculated, who approves, from which batch it applies, and whether systems and reconciliation agree.
Before go-live, run a tabletop exercise on a real (redacted) change: design change → impact assessment → quote/cost model → approval → supplement → order/system update → first-order acceptance/payment, simulating "urgent change done before signing", "additional scope in a tendered project" and "supplier asks for retroactive price adjustment", to see whether the page and process work.
| Check | Pass standard | Evidence | If failed |
|---|---|---|---|
| Definition/boundary | Counts/does not count, boundary with order/index/tolerance | Policy | Add boundary |
| Initiation/assessment | Request, price/delivery/quality/inventory/cash flow | Assessment | Add assessment |
| Approval/authority | Thresholds, sign-off, urgent change, recusal | Approval | Add approval |
| Tendering red line | Substantive-content judgment, re-tender/approval | Legal opinion | Add judgment |
| Agreement elements | Number, old/new clauses, effective/retroactive, unchanged | Agreement | Add clauses |
| System sync | Register/price/order/budget/quality | System | Add sync |
| Reconciliation/first order | Contract—order—acceptance—invoice—payment consistent | Sample check | Add validation |
| Disputes/evidence | Request/approval/correspondence/effective evidence | Archive | Add evidence |
| Archive/access | Master contract + change number + version, access control | Archive | Add archive |
| Public boundary | No contracts/prices/suppliers/register | Page/permissions | Take down |
The acceptance list is editorial; the company's contract policy, authority and system capability control.
Who should read it, who should not, and what decisions does it support?
For procurement, legal, finance, quality, R&D, planning and website teams at equipment, electronics, automotive-parts, medical-device, hardware, chemical, packaging and export manufacturers in Changzhou and nearby; also for companies handling "oral changes, do-then-sign, price only, approval beyond authority, departure agreements in tendered projects, systems out of sync". Not for teams without procurement contract-change management, or that want one page to replace legal/procurement/audit advice.
Read it if: building a contract-change/supplement page; only "flexible response"; oral changes; do-then-sign; price only; no old/new clauses; departure agreement in tendered project; systems out of sync. Not suitable if: treating "change" as "notice"; "order" as "contract"; "supplement" as "a universal patch"; "page" as "legal opinion/audit conclusion". Supports: definition/boundary, initiation/assessment, approval/red line, agreement elements, system sync, disputes/archive and public-boundary self-checks.
FAQ
What is the difference between the contract-change page and the order-change page?
The contract-change page answers "how the terms/scope/quantity/price/delivery/payment of an effective procurement contract are changed, who approves, how it is documented and executed"; the order-change page answers "how customer orders change within the change window, and how cancellation/expedite is charged". The former changes contractual rights/obligations, the latter changes specific order arrangements; an order change cannot replace a contract change, and a contract change cannot use an order or email instead of a supplement.
Which changes require a supplement agreement?
Usually changes to scope/specification, quantity/batch (beyond the contract option), price/tax/currency, delivery/place/Incoterms, payment/terms, warranty/acceptance, subcontracting/performer, suspension/extension/termination require a supplement or variation order. Options already agreed (quantity tolerance, price-linkage formula, framework call-off) follow the original mechanism without a separate supplement; whether writing is mandatory depends on company policy and the contract, but oral changes should be avoided.
How is the change price set, and can it be retroactive?
Price follows the original pricing basis/cost model/quote increment, counting only the increment caused by the change and avoiding double counting with price linkage or VA/VE savings; state unit price, tax, currency, tooling/freight and effective date. Retroactivity is not automatic; it applies only where the supplement clearly states the retroactive scope and conditions. Urgent changes may be performed first but must be confirmed in writing within the policy deadline; "done first" must not become a default price increase.
What should be noted for contract changes in tendered projects?
The Tendering and Bidding Law Article 46 requires a written contract per the tender documents and the winner's bid and prohibits another agreement departing from the substantive content. Where price, scope, quality, delivery or other substantive content is changed, legal/tender management should first decide whether it departs from the substantive content and whether re-tendering or approval is required; do not "add" conditions not committed in the bid through a supplement. Applicability is subject to project rules and legal advice.
How should change approval/authority be set?
Set thresholds by incremental value/contract ratio/risk, define initiate/review/approve/sign roles and legal/finance/technical sign-off; delivery, quality, compliance or safety impact can trigger escalation; urgent changes state pre-conditions and the after-the-fact deadline; conflicts of interest are declared/recused. Guideline No. 16 Article 12 requires timely reporting, mutual agreement and handling under authority/procedure; Article 15 requires change registration.
How should systems and reconciliation be synchronised after a change?
Synchronise contract register/version, price master, purchase order/delivery, budget/commitment, inventory/safety stock, quality plan/inspection standard, supplier statement, invoice/payment terms, insurance/guarantee; the first order/payment verifies "contract—order—acceptance—invoice—payment" consistency. Guideline No. 16 Article 14 requires finance to settle after checking contract terms and to refuse payment where performance is not per contract or a written contract should have been signed.
Should the website publish change/price information?
Usually not specific contracts/prices/suppliers/customers, change registers, cost details, approval opinions, dispute details or system screenshots; it can publish change scope, process, roles, approval principles, agreement elements, record requirements and update date. The goal is to let customers/suppliers understand the change-management method, not to disclose contract positions.
One-sentence takeaway
The procurement contract-change and supplement-agreement page on a Changzhou manufacturer's website is not about "flexible response"; it is about turning change definition/boundary, initiation and impact assessment, approval/authority/tendering red line, supplement elements, execution/system synchronisation/reconciliation, disputes/evidence/archive and public boundaries into a checkable list, so procurement/legal/finance/quality can judge whether a change exists, how to calculate it, who approves, from which batch it applies and whether systems agree.
Research method and limitations
This article is a summary of public rules and page method, not legal/procurement/audit advice. It uses no unpublished company contracts/prices/suppliers/customers, change registers, cost details, approval opinions, dispute details or system screenshots; the tables and acceptance items are editorial and not legal/procurement/audit conclusions. MOF Internal Control Application Guideline No. 16 (Contract Management), No. 7 (Procurement) and the Tendering and Bidding Law are public sources; the company's contract policy, authority, applicable project rules and contracts control. This article does not decide whether any specific change price/retroactivity is reasonable, and does not promise "zero change/zero dispute"; companies should set them item by item based on contract, supplier, project and finance basis.
Sources and basis
Current to 2026-11-10; the official pages below control.
- MOF Internal Control Application Guideline No. 16 — Contract Management (Cai Kuai [2010] No. 11): Linyi Finance Bureau. Article 11: supplementary agreement where terms are unclear; Article 12: timely reporting of change/termination, mutual agreement and handling under authority/procedure; Article 14: finance settles after checking contract terms; Article 15: registration covers conclusion, performance and change.
- MOF Internal Control Application Guideline No. 7 — Procurement (Cai Kuai [2010] No. 11): Linyi Finance Bureau. Procurement plans, supplier selection, price determination, contracts, acceptance, payment and records; used for price/contract/payment consistency in changes.
- Tendering and Bidding Law of the PRC: Hangzhou Xihu District Government. Article 46: a written contract per the tender documents and the winner's bid; no other agreement departing from the substantive content; used for the tendered-project change red line.