Direct answer: A procurement framework-agreement/annual-framework and call-off page is not a line saying "sign an annual contract and ship against it". The page should state: scope and types (annual/category/project/service framework; single/multiple suppliers; volume commitment/no commitment; fixed/index-linked price); term and renewal; pricing mechanism (price list, discount/tier, index link, FX/tax/freight, adjustment trigger and cap); minimum purchase/forecast/take-or-pay (distinguished from "non-binding forecast"); call-off rules (who may call off, format, confirmation, lead time, ASN, acceptance, three-way match); change (price/specification/quantity/delivery/supplier); termination/exit/last buy/transition; public boundary. On the rules: MOF Internal Control Application Guideline No. 7 (Procurement) requires reasonable sourcing methods, a pricing mechanism, contracts signed within authority and performance tracking; No. 16 (Contract Management) requires written contracts, counterparty qualification/capability review, complete terms, signature within authority, performance monitoring, change/termination, dispute handling, registration/archive and annual evaluation; No. 6 (Fund Activities) requires authorised payment approval. This article is current to 2026-11-09 and is a summary of public rules and page method, not legal or procurement-audit advice; company procurement/contract policy, framework agreements, orders and system configuration control.
This article is for procurement, legal, finance, quality, supply-chain 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 framework-agreement/annual-framework and call-off page. The usual gap is "framework treated as an order, no pricing mechanism, minimum volume written as a forecast, unauthorised call-off, delivery/acceptance/reconciliation disconnected, verbal changes, no transition at expiry", ending with a page that only says "long-term cooperation, settle per order", while ordering/delivery/settlement/exit still disagree.
A framework is not an order: the framework sets conditions, and the call-off creates the specific supply obligation. Pricing needs a mechanism: price list/discount/index link/cap and approval. Volume must be explicit: minimum purchase, take-or-pay and "forecast" are not the same. "Long-term cooperation, settle per order" is not enough.
How does this page relate to tender, contract signing, exclusivity/minimum purchase, index-linked pricing, supplier portal and three-way match pages?
The framework-agreement page answers "how procurement conditions for a future period are set, called off, changed and exited"; the procurement tender page answers "how suppliers are selected and awarded"; the contract signing page answers "terms/priority/signature/version"; the exclusivity/minimum-purchase/take-or-pay page answers "volume commitment/exclusivity/shortfall"; the index-linked pricing page answers "adjustment formula/trigger/disputes"; the supplier portal/SRM page answers "registration/RFQ/order/ASN"; the three-way match page answers "order/goods receipt/invoice reconciliation". The framework page is the main page for "conditions + call-off" and cannot be replaced by an ordinary contract or order page.
Common breaks: treating the framework as a "guaranteed-volume contract"; price only says "market price"; minimum volume/forecast mixed; unauthorised/verbal call-off; delivery/ASN/acceptance/reconciliation in separate silos; price adjustment without formula/cap; changes not in writing; unclear shares in multi-supplier frameworks; no renewal/transition at expiry; no last buy/tooling/drawing transfer on exit. The page separates "type—term—price—volume—call-off—change—exit—public boundary" so procurement/legal/finance/quality/supply chain share one vocabulary.
| Page | Question it answers | Key content | Cannot replace |
|---|---|---|---|
| Framework/call-off | How conditions are set/called off/exited | Type, term, price, volume, call-off, change | Ordinary contract/order |
| Tender | How suppliers are selected/awarded | Scope, documents, evaluation, award | Framework conditions/call-off |
| Contract signing | Terms/priority/signature/version | Technical agreement, deviations, signature | Call-off/shares |
| Exclusivity/minimum | Volume commitment/exclusivity/shortfall | Minimum, take-or-pay, antitrust | Non-binding framework |
| Index-linked pricing | Formula/trigger/disputes | Index, threshold, cap | Framework term/call-off |
| Portal/three-way match | Order/ASN/reconciliation | Order, delivery, receipt, invoice | Framework pricing/volume |
Page relationships are editorial; company procurement/contract policy, framework agreements and system configuration control.
Which framework types exist, and what are they used for?
At least: annual framework (common materials/consumables, annual price list/discount); category framework (one category with multiple suppliers, call-off by share/quote); project framework (engineering/retrofit/equipment, by project scope and milestones); service framework (maintenance/logistics/testing, by service catalogue and SLA). Further dimensions: single vs multiple suppliers; with minimum volume vs without (forecast only); fixed price vs index-linked; group framework with plant call-off vs single-plant framework. The type determines "who signs, who calls off, how price is set, how volume is committed, how shares are allocated". Do not call every long-term relationship a "framework agreement", and do not write a framework as an "indefinite, price-less, volume-less" letter of intent.
Acceptance checks: type; scope; single/multiple; volume/no volume; fixed/index; signatory; call-off entity; share rule; term. Common gaps: mixed types; over-broad scope; multi-supplier without shares; unclear group/plant authority; indefinite term.
| Type/dimension | What to write | Evidence | Common gap |
|---|---|---|---|
| Annual framework | Common materials, annual price list/discount, call-off | Agreement | Treated as guaranteed volume |
| Category framework | Category scope, multiple suppliers/shares/quote | Category strategy | Unclear shares |
| Project framework | Project scope, milestones, changes | Project agreement | Scope creep |
| Service framework | Service catalogue, SLA, pricing | Service agreement | No SLA |
| Single/multiple | Exclusivity/second source, shares, switch | Agreement/strategy | Fake multi-source |
| Volume/no volume | Minimum/take-or-pay vs forecast | Clause | Forecast as commitment |
| Fixed/index | Fixed/index/FX/adjustment | Price clause | "Market price" |
| Signatory/call-off | Group/plant/authorised person | Authority | Unauthorised call-off |
Type classification is editorial; company category strategy, contract policy and organisation control.
How should term, pricing mechanism and minimum volume be accepted?
Term: start/end, renewal conditions, notice period, treatment of call-offs after expiry, and separation of price validity from agreement term. Price: price list/unit price/discount/tier, tax-inclusive/exclusive, currency/FX, freight/packaging/tooling amortisation, adjustment trigger (index/market/cost), formula, cap/floor, approval and effective date; not just "market price". Minimum volume: distinguish minimum purchase/take-or-pay (shortfall payment/compensation) from forecast/rolling estimate (non-binding); state unit, measurement period, shortfall calculation, offset/carry-forward and force majeure; assess the competition, bargaining and flexibility impact of exclusivity/minimum volume and seek legal advice where needed. A framework is not automatically exclusive or guaranteed-volume.
Acceptance checks: term/renewal; price composition; tax/currency; adjustment formula/cap; approval/effective date; minimum/take-or-pay; forecast; shortfall calculation; measurement/period. Common gaps: indefinite; vague price; no formula; minimum/forecast mixed; unclear shortfall.
| Item | What to write | Evidence | Common gap |
|---|---|---|---|
| Term | Start/end/renewal/notice/expiry treatment | Agreement | Indefinite |
| Price composition | Unit/discount/tier/freight/packaging/amortisation | Price list | Total only |
| Tax/currency | Tax-inclusive/rate/currency/FX | Clause | Unclear basis |
| Adjustment | Trigger/index/formula/cap/approval/effective date | Clause/record | Market price |
| Minimum volume | Quantity/period/unit/shortfall/compensation | Clause | Written as forecast |
| Forecast | Rolling forecast/non-binding/sharing frequency | Clause | Treated as commitment |
| Exclusivity/share | Scope/share/exceptions/competition assessment | Clause/opinion | Fake exclusivity |
| Renewal/exit price | Renewal price/last-buy price/transition price | Clause | Dispute at expiry |
Term/price/volume are editorial; the framework agreement, pricing policy and legal advice control.
How should call-off, orders and performance be accepted?
A framework is not an order: state who may call off (position/authority/limit), call-off format (PO/system order/written notice), supplier confirmation (acceptance/lead time/quantity), applicable price, lead-time start, delivery location/packaging/ASN, acceptance standard, quality responsibility, invoice and three-way match, delay/expedite/cancellation, partial delivery/over-under delivery. The call-off must reference the framework number and price version, avoiding "verbal/WeChat orders"; the system should validate authority, limit, price and duplicate orders. Whether no call-off during the term is a breach depends on whether the agreement commits a minimum volume/take-or-pay; it cannot be assumed. Performance monitoring covers OTD, quality, ASN, reconciliation and exception escalation.
Acceptance checks: call-off authority; format/reference; confirmation; price version; lead-time start; delivery/ASN; acceptance; three-way match; delay/cancellation; OTD. Common gaps: verbal call-off; no authority; wrong price version; unclear lead-time start; acceptance/reconciliation disconnected.
| Item | What to write | Evidence | Common gap |
|---|---|---|---|
| Call-off authority | Position/limit/approval/acting | Authority | Anyone can call off |
| Call-off format | PO/system/written, framework number/price version | Order | Verbal/WeChat |
| Supplier confirmation | Acceptance/quantity/lead time/exception | Confirmation | Deemed acceptance |
| Price application | Price list/discount/adjustment effective date | Order | Wrong version |
| Lead-time start | Order confirmation/deposit/drawing/kit | Clause | Unclear start |
| Delivery/ASN | Location/packaging/label/ASN/window | Logistics | No ASN |
| Acceptance/quality | Standard/sampling/nonconforming/claim | Acceptance sheet | No standard |
| Reconciliation/payment | Three-way match/invoice/terms/variance | Reconciliation | Mismatch |
Call-off/performance are editorial; framework agreement, order terms, quality agreement and system capability control.
How should change, termination, exit and renewal be accepted?
Change: price/tax/FX, specification/alternative, quantity/share, delivery/destination, supplier addition/removal, call-off entity; require written change, authority approval, effective date, impact on open orders and price retroactivity rules. Termination: expiry, mutual agreement, breach, force majeure, supplier exit/sanctions/bankruptcy; state notice period, open orders, last buy, tooling/drawings/technical data/inventory handling, warranty/claims and transition supply. Renewal: performance/price/quality/delivery assessment, re-tender or negotiation, price update, share adjustment. Register/archive: framework, price versions, call-offs, changes, acceptance, reconciliation and evaluation. Guideline No. 16 requires performance monitoring, change/termination under authority, dispute handling, registration/archive and annual evaluation.
Acceptance checks: change types; written/approval/effective date; open orders; termination events/notice; last buy; tooling/data/inventory; warranty/claims; transition; renewal assessment; archive. Common gaps: verbal change; termination without transition; unclear last buy; no data transfer; auto-renewal.
| Item | What to write | Evidence | Common gap |
|---|---|---|---|
| Change types | Price/spec/quantity/delivery/supplier/entity | Change order | Verbal change |
| Change approval | Authority/effective date/open-order impact | Approval | Execute first |
| Price retroactivity | Ordered/delivered/inventory treatment | Clause | Dispute |
| Termination events | Expiry/mutual/breach/force majeure/exit | Clause | No termination right |
| Notice/transition | Notice period/transition supply/switch plan | Notice | Sudden stop |
| Last buy | Last order/quantity/price/lead time | Agreement | Unclear |
| Tooling/data/inventory | Ownership/transfer/buy-back/count | List | No transfer |
| Renewal/evaluation | Performance/price/quality/delivery, re-tender | Assessment | Auto-renew |
Change/termination/exit are editorial; framework agreement, contract policy and supplier-exit process control.
How should the website page be written, and what must not be published?
Suggested sections: (1) framework types and scope; (2) term and renewal principles; (3) pricing mechanism (price list/discount/index/tax/currency); (4) minimum volume/forecast/take-or-pay distinction; (5) call-off/order/delivery/acceptance/reconciliation; (6) change/termination/exit; (7) contact window/update date. The public page explains "types, principles, process, roles, boundaries" and does not publish specific price lists/discounts, minimum volumes/shares, supplier names/contacts, contract terms, system screenshots/accounts or undisclosed disputes. The English page should use consistent terms (framework agreement, annual framework, call-off, price list, discount/tier, index-linked, minimum purchase, take-or-pay, forecast, ASN, three-way match) and state the cut-off date.
Do not turn the framework page into a "long-term cooperation letter of intent", and do not claim "guaranteed supply/best price/unlimited volume" if it cannot be proven. The page should let suppliers and internal teams judge "how to join, how to call off, how price changes, how volume is calculated, how to exit", without exposing price and share positions.
| Section | What to write | Evidence | Avoid |
|---|---|---|---|
| Type/scope | Annual/category/project/service, single/multiple | Agreement/strategy | Mixed types |
| Term/renewal | Start/end/notice/renewal | Clause | Indefinite |
| Price mechanism | Price list/discount/index/cap/approval | Price clause | Market price |
| Volume | Minimum/take-or-pay/forecast distinction | Clause | Forecast as commitment |
| Call-off/performance | Authority/format/lead time/ASN/acceptance/reconciliation | System/order | Verbal call-off |
| Change/exit | Change/termination/last buy/transition | Process | Sudden stop |
The page structure is editorial; public statements must be true and verifiable, and the framework agreement and disclosure requirements control.
Go-live acceptance checklist
Ten checks: type/scope; term/renewal; pricing/tax/currency; minimum volume/forecast/take-or-pay; call-off authority/format/confirmation; lead time/ASN/acceptance/three-way match; change/price retroactivity; termination/exit/last buy; renewal assessment/archive; public boundary. Each needs evidence and a review date. The pass standard is not "the page says long-term cooperation", but that procurement/legal/finance/quality/supply chain can judge whether the framework is valid, the call-off is authorised, how price changes, how volume is calculated and how exit transitions.
Before go-live, run a tabletop exercise with a real (redacted) category: framework initiation → tender/negotiation → agreement → call-off → delivery/ASN → acceptance → three-way match → price adjustment → share adjustment → termination/renewal, simulating "verbal call-off", "wrong price version", "minimum volume shortfall" and "supplier exit", to see whether the page and process work.
| Check | Pass standard | Evidence | If failed |
|---|---|---|---|
| Type/scope | Annual/category/project/service, single/multiple | Agreement/strategy | Add type |
| Term/renewal | Start/end/notice/renewal | Clause | Add term |
| Pricing | Price list/discount/index/tax/currency/cap | Price clause | Add mechanism |
| Volume | Minimum/take-or-pay/forecast distinction/shortfall | Clause | Add basis |
| Call-off authority | Position/limit/format/confirmation | Authority/order | Add authority |
| Performance/reconciliation | Lead time/ASN/acceptance/three-way/OTD | System/document | Add process |
| Change/retroactivity | Approval/effective date/open orders/price retroactivity | Change order | Add approval |
| Termination/exit | Notice/last buy/tooling/data/transition | Agreement/list | Add exit |
| Renewal/archive | Assessment/re-tender/register/annual evaluation | Record | Add assessment |
| Public boundary | No price list/minimum/shares/terms | Page/permissions | Take down |
The acceptance list is editorial; company procurement/contract policy, framework agreements and audit requirements control.
Who should read it, who should not, and what decisions does it support?
For procurement, legal, finance, quality, supply-chain and website teams at equipment, electronics, automotive-parts, medical-device, hardware, chemical, packaging and export manufacturers in Changzhou and nearby; also for companies handling "framework treated as an order, no pricing mechanism, minimum volume mixed with forecast, unauthorised call-off, unclear multi-supplier shares, verbal changes, no switch at expiry, no exit transition". Not for teams without framework procurement, or that want one page to replace legal advice/contract audit.
Read it if: building a framework/call-off page; only "long-term cooperation, settle per order"; indefinite framework; vague price; minimum volume as forecast; unauthorised call-off; multi-supplier without shares; verbal changes; no exit transition. Not suitable if: treating "framework" as "order"; "forecast" as "commitment"; "call-off" as "order anything"; "page" as "contract/legal advice". Supports: type/term, price/minimum volume, call-off/performance, change/exit and public-boundary self-checks.
FAQ
What is the difference between a framework agreement and an ordinary procurement contract?
An ordinary procurement contract usually sets the specific item, quantity, price, delivery and payment; a framework agreement sets conditions for a future period (category, pricing mechanism, term, call-off method, minimum volume), with specific supply created by call-off/order. A framework is not an order, nor automatically exclusive or guaranteed-volume; whether a specific supply obligation arises depends on the call-off and the volume-commitment clause.
Must a framework agreement state a minimum purchase volume?
No. It can be a committed framework with minimum purchase/take-or-pay, or a non-minimum framework with rolling forecasts only. The key is to state the difference between minimum and forecast, unit, measurement period, shortfall calculation, compensation, offset/carry-forward and force majeure; do not write "forecast" as "commitment", and do not hide exclusive/minimum arrangements behind a "framework". Assess the competition and flexibility impact of exclusivity/minimum volume and seek legal advice where needed.
How should index-linked price adjustment be set?
State price composition (unit/discount/tier/freight/packaging/tooling amortisation), tax/rate, currency/FX, adjustment trigger (index/market/cost), formula, data source, cap/floor, approval and effective date; define retroactivity for ordered/delivered/inventory quantities. Do not write only "market price" or "mutual negotiation", which invites disputes when prices move.
How is a call-off placed, and when does a contract form?
The framework should state who may call off (position/authority/limit), call-off format (PO/system order/written notice), supplier confirmation, price version, lead-time start, delivery/acceptance/reconciliation; the call-off references the framework number and price version, and after confirmation forms the specific order as agreed. Verbal/WeChat call-off, unauthorised call-off and wrong price version are high-risk; the system should validate authority, limit and duplicate orders.
How should shares be allocated in a multi-supplier framework?
State the share rule (fixed percentage/rotation/quote/performance adjustment), scope, exceptions (capacity/lead time/sole source), adjustment cycle and basis; suppliers need to see the rule, not necessarily the specific shares. Shares should link to performance, price, quality, delivery and risk, avoiding "fake multi-sourcing" or shares that never adjust; exclusive/minimum arrangements should be assessed separately.
How should expiry/termination transition work?
State notice period, open orders, last buy (quantity/price/lead time), tooling/drawings/technical data/inventory handling, warranty/claims, transition supply and switch plan; after termination, close call-off access and update system price/supplier status. Before expiry without renewal, assess alternative suppliers/inventory/customer impact; do not stop supply suddenly. Assess performance/price/quality/delivery before renewal, and re-tender if necessary.
Should the website publish prices, minimum volumes and suppliers?
Usually not specific price lists/discounts, minimum volumes/shares, supplier names/contacts, contract terms, system screenshots/accounts or undisclosed disputes; it can publish framework types/scope, term/renewal principles, pricing mechanism, minimum vs forecast distinction, call-off/acceptance/reconciliation process, contact window and update date. The goal is to let suppliers understand "how to work together", not to disclose price and share positions.
One-sentence takeaway
The procurement framework-agreement and call-off page on a Changzhou manufacturer's website is not about "long-term cooperation, settle per order"; it is about turning types/scope, term/renewal, pricing/tax/currency, minimum volume/forecast/take-or-pay, call-off authority/format/confirmation, lead time/ASN/acceptance/three-way match, change/price retroactivity, termination/exit/last buy, renewal assessment/archive and public boundaries into a checkable list, so procurement/legal/finance/quality/supply chain can judge whether the framework is valid, the call-off is authorised, how price changes, how volume is calculated and how exit transitions.
Research method and limitations
This article is a summary of public rules and page method, not legal, procurement or contract-audit advice. It uses no unpublished company price lists/discounts, minimum volumes/shares, supplier names, contract terms, system screenshots or undisclosed disputes; the tables and acceptance items are editorial and not legal/procurement-audit conclusions. MOF Internal Control Application Guideline No. 7 (Procurement), No. 16 (Contract Management) and No. 6 (Fund Activities) are public sources; company procurement/contract policy, framework agreements, orders, pricing policy and system configuration control. This article does not decide whether any specific framework clause is lawful/reasonable, and does not promise "best price/guaranteed supply"; companies should set them item by item based on category, supplier, legal and business reality.
Sources and basis
Current to 2026-11-09; the official pages below control.
- MOF Internal Control Application Guideline No. 7 — Procurement (Cai Kuai [2010] No. 11): Linyi Finance Bureau. Sourcing methods, pricing mechanism, contract signing, acceptance, payment and procurement records.
- MOF Internal Control Application Guideline No. 16 — Contract Management (Cai Kuai [2010] No. 11): Linyi Finance Bureau. Written contracts, counterparty qualification/capability review, term review, signature within authority, performance monitoring, change/termination, dispute handling, registration/archive and annual evaluation.
- MOF Internal Control Application Guideline No. 6 — Fund Activities (Cai Kuai [2010] No. 11): Linyi Finance Bureau. Fund authorization, approval and verification; payment under authorised approval; used here for framework call-off settlement/payment controls.