EDIFACT ORDCHG — Purchase Order Change
Buyers transmit ORDCHG to revise quantities, dates, prices, ship-to, or cancel lines while preserving the original order reference.
✦ What It Does
ORDCHG references the original ORDERS document and lists deltas: which lines change, new requested dates, or replacement ship-to NAD.
Implementation guides may require explicit change reason in BGM or RFF and cumulative version numbers to avoid out-of-order processing.
Suppliers typically answer with ORDRSP or a subsequent acceptance workflow per MIG.
⚡ When It's Used
- Demand forecast shifts require more or less material mid-program.
- Store openings or closings change ship-to NAD on open orders.
- Promotional corrections after ORDERS was released.
- Carrier or Incoterms updates affecting delivery window.
- ERP change orders batch into overnight ORDCHG files.
Who Uses EDIFACT ORDCHG
European retail & brands
Common in EDIFACT-first programs where purchase order change flows between HQ, DCs, and suppliers across the EU and APAC.
Global manufacturers
Automotive, industrial, and CPG companies standardize on EDIFACT for plants and suppliers outside North America.
3PLs & carriers
Logistics service providers consume or produce the message when the contract mandates UN/EDIFACT syntax and directories.
Key Segments & Constructs
EDIFACT uses a hierarchical structure: UNH (message header) opens the transaction; BGM (beginning of message) carries the document name and reference; party data uses NAD; lines often use LIN with QTY, PRI, and MOA. Exact segment requirements depend on the message directory (D.96A, etc.) and your trading partner's implementation guide.
BGM
Change document function and linkage to original order reference.
RFF
Buyer order version, agreement, or change request identifiers.
LIN / QTY / DTM
Per-line deltas: new quantities, dates, or line cancellations.
NAD
Updated delivery party or ship-to when DC assignments change.
Related Messages
Need Help with EDIFACT ORDCHG?
Better EDI maps, tests, and operates EDIFACT alongside X12—same platform, translation when partners use different standards.
Talk to an EDI Expert