EDIFACT ORDERS: A Complete Guide to the International Purchase Order Message
How UN/EDIFACT ORDERS compares to the X12 850, its segment structure, and what to watch for when trading with European and global manufacturing partners.
In this article
If your supply chain includes European trading partners — especially in automotive or manufacturing — you'll run into UN/EDIFACT sooner or later. The ORDERS message is its purchase order, and while it accomplishes exactly what an X12 850 does, the syntax looks unfamiliar the first time you see it.
1. What is EDIFACT ORDERS?
ORDERS is the UN/EDIFACT message for communicating a purchase order from a buyer to a seller — segments for parties, line items, quantities, and pricing, wrapped in EDIFACT's own envelope structure.
2. Syntax differences from X12
| Concept | X12 | EDIFACT |
|---|---|---|
| Segment terminator | ~ (tilde) | ' (apostrophe) |
| Element separator | * (asterisk) | + (plus) |
| Component separator | (not typically used) | : (colon) |
| Interchange header | ISA | UNB |
| Message header | ST | UNH |
3. Message structure
- UNB/UNZ — interchange envelope (sender, receiver, control reference)
- UNH/UNT — message envelope (wraps one ORDERS message)
- BGM — beginning of message: document type and number
- DTM — dates (order date, requested delivery)
- NAD — name and address for each party (BY=Buyer, SU=Supplier, DP=Delivery Party)
- LIN/QTY/PRI — one loop per line item with quantity and price
4. Example ORDERS message
UNB
This is an envelope or control segment. Select a highlighted segment on the left (shown in green) for a full business explanation.
5. Working with qualifiers
EDIFACT leans heavily on qualifier codes to give context to raw values — for example, QTY+21:100 means 'quantity qualifier 21 (ordered quantity), value 100.' Getting qualifier code lists agreed upon with each trading partner ahead of time avoids a huge share of onboarding friction, since many qualifiers have multiple valid codes for similar concepts (e.g., different item number type codes for buyer's vs. supplier's part numbers).
6. How ORDERS works, end to end
Here's the complete flow from the buyer's ERP to the supplier's order confirmation — the same order-to-acknowledgment journey the X12 850 makes, just with EDIFACT's own envelope and gateway terminology. Press Play Flow to watch it travel, or click a step for detail.
How it works
How EDIFACT ORDERS Works
Sender
Buyer
Receiver
Seller / Supplier
Direction
Buyer → Seller
Standard
UN/EDIFACT
Version
D.01B
Transport
AS2 / SFTP / VAN
Business Purpose
Order Management
Sender — Buyer
EDI Transmission
ORDERS
Purchase Order Message
UN/EDIFACT D.96A / D.01B
Receiver — Seller / Supplier
Related transaction flows
Need help understanding this EDI flow?
Ask EDI AI →EDIFACT ORDERS workflow. Steps: Buyer ERP Order, Generate ORDERS, SFTP / AS2 / VAN, Buyer Gateway, Translate to ERP, Confirm with ORDRSP. Transmitted from Buyer to Seller / Supplier via AS2, SFTP, VAN, following UN/EDIFACT D.96A / D.01B.
7. Validation
- UNH message reference number must be unique within the interchange.
- Each NAD segment must use a valid, agreed party qualifier.
- UNT segment count must match the actual segments transmitted.
- Every LIN loop should have at least one QTY segment.
8. Common errors
| Error | Likely Cause | Fix |
|---|---|---|
| Interchange rejected at UNB/UNZ | Control reference mismatch between UNB and UNZ | Ensure translator auto-generates matching references |
| Supplier can't resolve item number | LIN item number type qualifier mismatch (BP vs. SA) | Agree on and document the qualifier before go-live |
Related transactions
Purchase Order Response Message
UN/EDIFACT ORDRSP is the supplier's response to an ORDERS message, confirming, amending, or rejecting the purchase order — the EDIFACT counterpart to the X12 855.
Despatch Advice Message
UN/EDIFACT DESADV is the international equivalent of the X12 856 Advance Ship Notice, describing what was shipped and how it is packed.
Invoice Message
UN/EDIFACT INVOIC is the electronic invoice message, the EDIFACT counterpart to the X12 810, used to bill for goods or services delivered.
Frequently asked questions
Same business purpose, different syntax — colons and pluses instead of asterisks, and different segment names.
Have a follow-up question about this topic?
Ask EDI AI →