ORDERS is the EDIFACT/EANCOM message a buyer, usually a retailer, uses to send a purchase order to a supplier electronically. It carries the parties, the delivery point, items identified by GTIN, quantities, prices and delivery dates, and the supplier receives it straight in the ERP or the EDI portal, with no email or PDF.
ORDERS is the standardized EDIFACT message used to send a purchase order from a buyer (usually a retailer or distributor) to a supplier. It carries the party details, delivery locations (GLN), items (GTIN), quantities, negotiated prices, delivery terms and commercial conditions. In Romania, ORDERS is used by every major retailer (Carrefour, Kaufland, Lidl, Auchan, Mega Image, Profi, Selgros, Metro, Dedeman, Brico, Hornbach, Leroy Merlin, Penny etc.) to send orders to suppliers automatically, replacing email and PDFs.
An EANCOM ORDERS is built from segments, each with a precise role. The most common ones are:
| Segment | Role in the message |
|---|---|
| UNH | Message header: type (ORDERS), version (D.96A) and the EANCOM subset. |
| BGM | Beginning of the document: type (220 = order) and the order number. |
| DTM | Dates: order date (137) and requested delivery date (2). |
| NAD | The parties, identified by GLN/ILN: buyer (BY), supplier (SU), delivery party (DP). |
| LIN | The item line, with the product GTIN. |
| QTY | Ordered quantity (qualifier 21). |
| PRI | Net price of the item (qualifier AAA). |
| UNS, CNT | The separator between detail and summary, and the line count. |
| UNT | End of the message: segment count and message reference. |
The message below is an illustrative, simplified example with fictitious location codes and GTINs that have valid check digits. Read it segment by segment: a retailer orders two items, to be delivered to a warehouse.
UNH+1+ORDERS:D:96A:UN:EAN008'
BGM+220+PO-2026-0451+9'
DTM+137:20261118:102'
DTM+2:20261120:102'
NAD+BY+2000002000020::9'
NAD+SU+2000001000014::9'
NAD+DP+2000003000036::9'
LIN+1++5940000000011:SRV'
QTY+21:120'
PRI+AAA:4.35'
LIN+2++5940000000028:SRV'
QTY+21:48'
PRI+AAA:7.90'
UNS+S'
CNT+2:2'
UNT+16+1'ORDERS opens the document flow between retailer and supplier: ORDERS → ORDRSP → DESADV → RECADV → INVOIC. The supplier confirms the order with ORDRSP, announces the delivery with DESADV, the retailer confirms receipt with RECADV, and finally the supplier issues the INVOIC invoice. Every document points back to the original order through its number.
With EDIconnect you can receive ORDERS in the Web EDI portal or directly in your ERP, through integration. The document is converted automatically between the format the retailer requires and your ERP format, and from there you can confirm the order, send the DESADV and issue the invoice in the same flow.
EDIconnect receives ORDERS, converts them for your ERP and helps you continue the flow with confirmation, dispatch advice and invoice.
Last updated: November 2026. The example is illustrative and simplified; mandatory segments and codes differ from one retailer to another, so follow the partner's implementation guide.