Direct answer: A procurement order delivery-tracking/expediting page is not a line saying "order placed, waiting for delivery". The page should state: order confirmation and promised date (acknowledgement/confirmation, lead-time start, split/partial delivery, capacity/tooling/deposit/letter of credit/documents); delivery plan and early warning (T-7/T-3/T-1 milestones, production/kit/bottleneck/sub-tier suppliers, holidays/logistics booking, ASN); delay/expedite/line stop (cause, recovery plan, alternative/overtime/air freight, line-stop loss, escalation, written notice); OTD/performance and improvement (definition, on-time window, quantity/document accuracy, cause, scorecard); receiving/ASN/three-way match (booking, unloading, inspection, short/over, variance, return); exit/switch; public boundary. On the rules: MOF Internal Control Application Guideline No. 7 (Procurement) requires tracking contract performance, issuing a written report and solution for exceptions that may affect production/project progress, and keeping records/traceability; No. 16 (Contract Management) requires performance monitoring, change/termination, dispute handling and archive; the Civil Code sales-contract chapter sets delivery time/place, risk transfer, inspection/notice periods and over-delivery handling. This article is current to 2026-11-09 and is a summary of public rules and page method, not legal or supply-chain audit advice; the purchase contract/order, delivery agreement and actual receipt control.
This article is for procurement, planning, supply-chain, warehouse, quality, finance 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 order delivery-tracking/expediting page. The usual gap is "unclear lead-time start, verbal promised-date changes, no early warning, delay discovered late, expedite/air-freight/line-stop loss unallocated, OTD not assessed, ASN/receiving/reconciliation disconnected", ending with a page that only says "long-term cooperation, on-time delivery", while line stop/claims still disagree.
First define the date: acknowledgement, lead-time start, split/partial delivery, capacity/tooling/deposit conditions. Then set early warning: T-7/T-3/T-1 milestones, kit/bottleneck/sub-tier suppliers, ASN. Finally manage exceptions: cause/recovery, expedite/air freight/line-stop loss, escalation/written notice, OTD assessment. "On-time delivery" is not enough.
How does this page relate to material planning/shortage alerts, supplier portal, inbound logistics, order change and supplier scorecard pages?
The delivery-tracking page answers "what date did the supplier promise, where is it now, what if delayed, how is OTD assessed"; the material planning/shortage-alert page answers "forecast/MRP/safety stock/kit/escalation"; the supplier portal/SRM page answers "registration/RFQ/order/ASN/e-signature"; the inbound logistics/Milk Run page answers "route/ASN/delivery window/unloading/damage"; the order change/cancellation/expedite page answers "change window/cost/written confirmation"; the supplier scorecard page answers "QCDS/weights/rating/improvement". The delivery-tracking page is the main page for "order fulfilment" and cannot be replaced by a material-planning or portal page.
Common breaks: no lead-time start; verbal promised-date changes; no T-7/T-3/T-1 warning; kit/bottleneck/sub-tier suppliers opaque; delay discovered late; expedite/air-freight/line-stop loss not agreed; ASN/receiving/reconciliation disconnected; OTD definition unclear; exceptions not escalated; no switch on exit. The page separates "confirmation—plan—warning—exception—OTD—receiving—exit—public boundary" so procurement/planning/supply chain/warehouse/quality/finance share one vocabulary.
| Page | Question it answers | Key content | Cannot replace |
|---|---|---|---|
| Delivery/expedite | Promised date/current status/delay/OTD | Confirmation, milestones, warning, expedite, OTD | Material planning |
| Material/shortage | Forecast/MRP/safety stock/kit | Forecast, parameters, kit, escalation | Order promise/delivery |
| Supplier portal | Registration/RFQ/order/ASN | Account, order, ASN | Delivery performance |
| Inbound logistics | Route/window/unloading/damage | ASN, booking, unloading | Order delivery date |
| Order change | Change window/cost/confirmation | Cancellation, expedite, cost | Delivery tracking |
| Scorecard | QCDS/weights/rating/improvement | Score, rating, allocation | Daily expediting |
Page relationships are editorial; the purchase contract/order, delivery agreement and actual receipt control.
How should order confirmation and promised date be accepted?
Order confirmation should state at least: accept/reject/change, confirmation time limit, promised date, lead-time start (order confirmation/deposit/letter of credit/drawings/tooling/sample approval/kit), split/partial delivery, quantity/MOQ, packaging/documents, delivery place/transport, capacity/tooling/fixtures, outsourcing/sub-tier suppliers, exceptions (holidays/power curtailment/environmental). Civil Code Article 601: the seller delivers at the agreed time; if a delivery period is agreed, it may deliver at any time within that period; Article 602: if no/unclear delivery time, Articles 510/511(4) apply; Article 603: delivery place agreed/default rules; Article 604: risk before delivery on seller/after delivery on buyer (unless law/agreement). The order/contract should state these; "as soon as possible" is not enough.
Acceptance checks: acceptance/confirmation time limit; promised date; lead-time start; split/partial; quantity/MOQ; packaging/documents; delivery place; capacity/tooling; sub-tier suppliers; exceptions. Common gaps: no confirmation; no lead-time start; verbal date change; unclear split; capacity/tooling not assessed.
| Item | What to write | Evidence | Common gap |
|---|---|---|---|
| Accept/confirm | Accept/reject/change, confirmation time limit | Order confirmation | No confirmation |
| Promised date | Date/window, split/partial | Order | Verbal promise |
| Lead-time start | Confirmation/deposit/LC/drawings/tooling/sample | Clause | Unclear start |
| Quantity/MOQ | Order quantity/minimum lot/over-under | Order | Not stated |
| Packaging/docs | Packaging/label/documents/ASN | Clause | Missing |
| Delivery place | Place/transport/receiving window | Clause | Unclear |
| Capacity/tooling | Capacity/tooling/fixtures/outsourcing | Assessment | Not assessed |
| Exceptions | Holidays/power curtailment/environment/force majeure | Clause | Post-dispute |
Confirmation/date are editorial; the Civil Code sales chapter, purchase contract/order control.
How should the delivery plan and early warning be accepted?
The delivery plan should state at least: order/material/quantity/date; T-7/T-3/T-1 milestones (material preparation/start-up/completion/dispatch/arrival); production progress/kit/bottleneck process/equipment/labour; sub-tier suppliers/outsourcing; holidays/power curtailment/environment/logistics booking; ASN/dispatch notice; exception escalation. Early warning must be actionable: who, when, with what data, to whom, triggering what action (expedite/alternative/reschedule/air freight). Guideline No. 7 requires tracking contract performance, issuing a written report and solution for exceptions that may affect production/project progress; No. 16 requires performance monitoring. The page should state milestones/frequency/owner/escalation path, not just "regular follow-up".
Acceptance checks: order/date; milestones; progress/kit; bottleneck; sub-tier suppliers; holidays/power; ASN; exception escalation. Common gaps: no milestones; finished goods only; opaque bottleneck; sub-tier suppliers ignored; no escalation.
| Item | What to write | Evidence | Common gap |
|---|---|---|---|
| Order/date | Order/material/quantity/date | Order | Unclear |
| Milestones | T-7/T-3/T-1, material/start/completion/dispatch | Plan | No milestones |
| Progress/kit | Production progress/kit/bottleneck | Report | Finished goods only |
| Sub-tier | Outsourcing/sub-tier supplier/risk | List | Ignored |
| Holidays/power | Holidays/power curtailment/environment/logistics | Plan | Late discovery |
| ASN | Dispatch notice/booking/arrival | System | No ASN |
| Warning | Who/when/data/action/escalation | Record | No escalation |
| Written report | Exception/impact/solution/time limit | Report | Verbal |
Plan/warning are editorial; the purchase contract, delivery agreement and system capability control.
How should delay, expediting and line stop be accepted?
Delay handling should state at least: cause category (capacity/material/quality/equipment/labour/outsourcing/logistics/force majeure); impact (order/line/customer/inventory); recovery plan (overtime/extra staff/alternative material/outsourcing/split/air freight/transfer); expedite cost (overtime/air freight/dedicated truck/extra hours) allocation; line-stop loss (labour/equipment/customer claim/liquidated damages) calculation and evidence; escalation path (procurement/planning/supply chain/management); written notice/minutes/post-mortem. Guideline No. 7 requires written exception report/solution; No. 16 requires change/termination/dispute handling. The contract should state delay liquidated damages/compensation/cap/exemption/notice period, not dispute later.
Acceptance checks: cause; impact; recovery plan; expedite cost; line-stop loss; escalation; written notice; post-mortem. Common gaps: unclear cause; no recovery plan; expedite-cost disputes; no line-stop evidence; no escalation.
| Item | What to write | Evidence | Common gap |
|---|---|---|---|
| Cause | Capacity/material/quality/equipment/labour/outsourcing/logistics/force majeure | Record | Unclear cause |
| Impact | Order/line/customer/inventory | Assessment | Not assessed |
| Recovery | Overtime/staff/alternative/outsourcing/split/air freight | Plan | No plan |
| Expedite cost | Overtime/air freight/dedicated truck/extra hours | Quote/record | Dispute |
| Line-stop loss | Labour/equipment/customer claim/liquidated damages | Calculation/evidence | No evidence |
| Escalation | Procurement/planning/supply chain/management | Record | No escalation |
| Written notice | Exception/solution/time limit/responsibility | Notice/minutes | Verbal |
| Post-mortem | Root cause/corrective/preventive/assessment | Report | No review |
Delay/expedite/line stop are editorial; the contract breach/compensation clauses and actual loss evidence control.
How should OTD, performance and improvement be accepted?
OTD definition should state: by order line/quantity/date; on-time window (early/late counted?); promised date vs original date; partial/split delivery; quantity/document accuracy; customer-specified date; measurement period/data source/owner. Performance: OTD, delay days, expedite count/cost, line-stop count/loss, ASN timeliness, receiving variance, complaints; scorecard weights/rating/allocation/improvement. Improvement: root cause/corrective action/validation/closure; linked to supplier scorecard/admission/allocation. Guideline No. 7 requires post-purchase evaluation/records; No. 16 requires performance evaluation. The page should state "how calculated, by whom, where used", not just "OTD 95%".
Acceptance checks: definition; window; partial/split; quantity/document; period/data; scorecard; improvement; linkage. Common gaps: unclear definition; early/late disputes; partial delivery excluded; manual data; not assessed.
| Item | What to write | Evidence | Common gap |
|---|---|---|---|
| OTD definition | Order line/quantity/date, on-time window | Policy | Unclear |
| Promised/original | Promised or original date | System | Inconsistent |
| Partial/split | Whether partial/split counts | Rule | Missed |
| Quantity/document | Quantity accuracy/document accuracy | Receiving | Date only |
| Period/data | Period/data source/owner | Report | Manual |
| Scorecard | Weights/rating/allocation/improvement | Score | Not assessed |
| Improvement | Root cause/action/validation/closure | Record | No closure |
| Linkage | Admission/allocation/new projects | Record | No linkage |
OTD/performance are editorial; the procurement policy, scorecard and contract control.
How should receiving, ASN and three-way match be accepted?
Receiving: ASN/booking/arrival/unloading/count/appearance/batch/expiry/inspection; short/over/damage/wrong delivery/rejection; isolate/return nonconforming. Three-way match: order/goods receipt/invoice (quantity/unit price/amount/tax); variance handling/red-letter/claim; payment per acceptance/payment term. Guideline No. 7 requires acceptance/payment/records; No. 16 requires performance monitoring. The page should state "when ASN is sent, what receiving checks, how variance is recorded, reconciliation cycle", not just "inspect on arrival".
Acceptance checks: ASN; booking; arrival/unloading; count/appearance; batch/expiry; inspection; short/over/damage; nonconforming; three-way; variance; payment. Common gaps: no ASN; no count; no inspection; variance not recorded; mismatch.
| Item | What to write | Evidence | Common gap |
|---|---|---|---|
| ASN | Dispatch notice/booking/arrival | System | No ASN |
| Receiving | Count/appearance/batch/expiry | Receiving sheet | No count |
| Inspection | Standard/sampling/decision | Inspection sheet | No inspection |
| Short/over/damage | Record/photo/notice/claim | Record | Not recorded |
| Nonconforming | Isolation/return/sort/concession | Record | Mixed use |
| Three-way | Order/receipt/invoice/tax | Reconciliation | Mismatch |
| Variance | Variance/red-letter/claim/adjustment | Record | Not handled |
| Payment | Acceptance/payment term/approval | Payment record | Pay before acceptance |
Receiving/ASN/three-way are editorial; the purchase contract, acceptance standard and finance policy control.
How should the website page be written, and what must not be published?
Suggested sections: (1) order confirmation/promised date; (2) delivery plan/warning milestones; (3) delay/expedite/line stop; (4) OTD/performance/improvement; (5) ASN/receiving/three-way; (6) exit/switch; (7) contact window/update date. The public page explains "date basis, milestones, exception process, performance rules, boundaries" and does not publish specific orders/prices, supplier names/contacts, capacity/inventory, customer/line information, line-stop loss/claim amounts, system screenshots or undisclosed disputes. The English page should use consistent terms (purchase order, promised date, lead-time start, ASN, delivery schedule, expedite, line stop, OTD, root cause, scorecard) and state the cut-off date.
Do not turn the delivery page into an "on-time delivery" slogan, and do not claim "100% OTD/zero line stop" if it cannot be proven. The page should let procurement/planning/supply chain/warehouse/quality judge "what date is promised, where it is now, what if delayed, how OTD is calculated", without exposing order and customer information.
Go-live acceptance checklist
Ten checks: confirmation/promised date/lead-time start; split/partial/quantity; milestones/warning; bottleneck/sub-tier suppliers; delay/recovery/expedite/line stop; OTD definition/scorecard; ASN/receiving/inspection; three-way/variance/payment; exit/switch; public boundary. Each needs evidence and a review date. The pass standard is not "the page says on-time delivery", but that procurement/planning/supply chain/warehouse/quality can judge the date, warning, exception handling, performance and receiving reconciliation from the page.
Before go-live, run a tabletop exercise with a real (redacted) order: order → confirmation → promised date → T-7/T-3/T-1 → delay → recovery/expedite → receiving/ASN → three-way → OTD, simulating "unclear lead-time start", "sub-tier material shortage" and "line-stop loss dispute", to see whether the page and process work.
| Check | Pass standard | Evidence | If failed |
|---|---|---|---|
| Confirmation/date | Acceptance/promise/start/split | Order confirmation | Add confirmation |
| Quantity/packaging | Quantity/MOQ/packaging/documents/place | Order | Add clauses |
| Milestones/warning | T-7/T-3/T-1, progress/kit/bottleneck | Plan/report | Add milestones |
| Sub-tier | Outsourcing/sub-tier supplier/risk | List | Add management |
| Delay/expedite | Cause/recovery/cost/line stop/escalation | Record | Add process |
| OTD/score | Definition/window/partial/data/score | Report | Unify basis |
| ASN/receiving | ASN/count/inspection/short-over/nonconforming | Document | Add process |
| Three-way/payment | Order/receipt/invoice/variance/approval | Reconciliation | Reconcile |
| Exit/switch | Open orders/alternative/notice/inventory | Plan | Add exit |
| Public boundary | No orders/prices/customers/loss | Page/permissions | Take down |
The acceptance list is editorial; the purchase contract, delivery agreement and audit requirements control.
Who should read it, who should not, and what decisions does it support?
For procurement, planning, supply-chain, warehouse, quality, finance and website teams at equipment, electronics, automotive-parts, medical-device, hardware, chemical, packaging and export manufacturers in Changzhou and nearby; also for companies handling "unclear lead-time start, verbal date changes, no warning, late delay discovery, expedite/air-freight/line-stop disputes, OTD not assessed, ASN/receiving/reconciliation disconnected". Not for teams without PO delivery management, or that want one page to replace legal/supply-chain audit advice.
Read it if: building a delivery/expediting page; only "on-time delivery"; no confirmation/start; no milestones/warning; opaque bottleneck/sub-tier; no recovery; expedite/line-stop not agreed; unclear OTD; ASN/receiving/reconciliation disconnected. Not suitable if: treating "promised date" as "guarantee"; "expediting" as "phone calls"; "OTD" as "a slogan"; "page" as "contract/audit conclusion". Supports: confirmation/date, milestones/warning, delay/expedite, OTD/scorecard, ASN/three-way and public-boundary self-checks.
FAQ
What is the difference between delivery tracking and material planning/shortage alerts?
Material planning/shortage alerts address "what is needed, when, inventory/MRP/safety stock/kit", focused on demand and planning; delivery tracking addresses "for this placed order, what date did the supplier promise, where is it now, what if delayed, how is OTD assessed", focused on order fulfilment. They should link: a shortage alert triggers expediting, and a delivery exception feeds back into planning, but one page cannot replace the other.
When does the lead time start?
The contract/order should state whether it starts from order confirmation, deposit receipt, letter of credit, drawing/technical data confirmation, tooling/sample approval or kit/packaging confirmation; the start for each split/partial batch; whether holidays/power curtailment/force majeure extend it. Without a start point, "shipped" versus "overdue" becomes a dispute. Civil Code Article 601 requires delivery at the agreed time; if a period is agreed, delivery may occur at any time within it.
Can a supplier change the promised date?
It can be changed by agreement, but in writing/system confirmation, stating cause, impact, new date, expedite/alternative, cost/responsibility; no verbal or unilateral postponement. Changes involving price/quantity/delivery place/risk follow the contract change/Civil Code sales chapter; major changes require re-approval. Promised-date changes should be recorded and included in OTD/scorecard.
How should delays be warned/escalated?
Set T-7/T-3/T-1 milestones, track material/start/completion/dispatch/arrival, kit/bottleneck/sub-tier suppliers/holidays/logistics booking; on risk, the owner reports through the escalation path (procurement→planning→supply chain→management) with cause/impact/recovery/support needed; exceptions require a written report/minutes. Guideline No. 7 requires a written report and solution for exceptions that may affect production/project progress.
Who bears expedite/air-freight/line-stop loss?
Per the contract and cause: supplier-caused delay may allow claims for expedite/air freight/line-stop loss under liquidated damages/compensation clauses; buyer-caused (change/non-payment/no drawings/no receiving) is borne by the buyer; force majeure per contract/law. State cost items, calculation basis, evidence (quotes/invoices/hours/line-stop records), notice period and compensation cap; do not dispute verbally afterward.
How is OTD defined/assessed?
State by order line/quantity/date, on-time window (early/late counted?), promised or original date, whether partial/split counts, quantity/document accuracy, period/data source/owner; include in supplier scorecard weights/rating/allocation/improvement. Do not write "OTD 95%" without the basis; data should be traceable and exceptions reviewed/closed.
Should the website publish supplier delivery dates/KPIs?
Usually not specific orders/prices, supplier names/contacts, capacity/inventory, customer/line information, line-stop loss/claim amounts, system screenshots or undisclosed disputes; it can publish date basis, confirmation/warning process, delay/expedite/line-stop principles, OTD definition/scoring rules, ASN/receiving/reconciliation process, contact window and update date. The goal is to let suppliers understand fulfilment rules, not to disclose order and customer positions.
One-sentence takeaway
The procurement order delivery-tracking/expediting page on a Changzhou manufacturer's website is not about "on-time delivery"; it is about turning order confirmation/promised date/lead-time start, split/partial/quantity, T-7/T-3/T-1 milestones/warning, bottleneck/sub-tier suppliers, delay/recovery/expedite/line stop, OTD definition/scorecard, ASN/receiving/inspection, three-way/variance/payment, exit/switch and public boundaries into a checkable list, so procurement/planning/supply chain/warehouse/quality can judge the date, warning, exception handling, performance and receiving reconciliation.
Research method and limitations
This article is a summary of public rules and page method, not legal or supply-chain audit advice. It uses no unpublished company orders/prices, supplier lists, capacity/inventory, customer/line information, line-stop loss/claim amounts, system screenshots or undisclosed disputes; the tables and acceptance items are editorial and not legal/supply-chain audit conclusions. The Civil Code sales-contract chapter, MOF Internal Control Application Guideline No. 7 (Procurement) and No. 16 (Contract Management) are public sources; the purchase contract/order, delivery agreement and actual receipt control. This article does not decide whether any specific date/compensation clause is reasonable, and does not promise "100% OTD/zero line stop"; companies should set them item by item based on order, supplier, capacity, contract and data.
Sources and basis
Current to 2026-11-09; the official pages below control.
- Civil Code of the People's Republic of China, Book Three, Chapter VIII Sales Contracts (effective 1 January 2021): Kangle County People's Government (full text). Articles 595/596 contract definition/terms; Articles 601–608 delivery time/place/risk; Articles 620–623 inspection/notice; Article 629 over-delivery.
- MOF Internal Control Application Guideline No. 7 — Procurement (Cai Kuai [2010] No. 11): Linyi Finance Bureau. Contract performance tracking, written exception report/solution, procurement records/traceability, acceptance/payment.
- MOF Internal Control Application Guideline No. 16 — Contract Management (Cai Kuai [2010] No. 11): Linyi Finance Bureau. Contract performance monitoring, change/termination, dispute handling, registration/archive and annual evaluation.