Message us on WhatsApp
    Back to glossary
    EDI Messages

    ORDERS: the EDI purchase order

    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.

    Full definition

    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.

    Examples

    • UNH+1+ORDERS:D:96A:UN:EAN008'
    • Automated purchase order sent by Kaufland to an FMCG supplier

    What an ORDERS message contains

    An EANCOM ORDERS is built from segments, each with a precise role. The most common ones are:

    Main segments of an ORDERS message (EANCOM)
    SegmentRole in the message
    UNHMessage header: type (ORDERS), version (D.96A) and the EANCOM subset.
    BGMBeginning of the document: type (220 = order) and the order number.
    DTMDates: order date (137) and requested delivery date (2).
    NADThe parties, identified by GLN/ILN: buyer (BY), supplier (SU), delivery party (DP).
    LINThe item line, with the product GTIN.
    QTYOrdered quantity (qualifier 21).
    PRINet price of the item (qualifier AAA).
    UNS, CNTThe separator between detail and summary, and the line count.
    UNTEnd of the message: segment count and message reference.

    Illustrative ORDERS example

    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.

    Illustrative example (EANCOM D.96A)
    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'

    Where ORDERS sits in the retail flow

    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.

    • The location codes in NAD (GLN or ILN) show who orders and where to deliver; see also the ILN code.
    • Items are referenced by GTIN, so your catalogue needs valid codes.
    • The order number in BGM is repeated in DESADV, RECADV and INVOIC.

    Common mistakes with EDI orders

    • Wrong GLN/ILN for the delivery point: the order arrives but cannot be assigned to the right store or warehouse.
    • A GTIN that does not exist in your ERP catalogue, so the line cannot be matched automatically.
    • Quantities or units of measure that differ from the ERP, which later show up as differences on the DESADV and the invoice.
    • An order price that differs from your price list, which holds up the invoice at checking.
    • Orders changed or cancelled by the retailer but not processed because the flow only reads the initial message.

    How EDIconnect handles ORDERS

    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.

    ORDERS in the EDIconnect platform

    Frequently asked questions about ORDERS

    What is ORDERS in EDI?
    ORDERS is the EDIFACT/EANCOM message for the purchase order, sent electronically by the buyer to the supplier. It replaces the order by email or PDF and can be loaded straight into the ERP.
    What information does an ORDERS message contain?
    The order number and date, the parties (buyer, supplier, delivery point) identified by GLN/ILN, the items by GTIN, quantities, prices and the requested delivery date.
    What is the difference between ORDERS and ORDRSP?
    ORDERS is the order sent by the buyer. ORDRSP is the supplier's reply, confirming, changing or rejecting the order.
    Which message follows ORDERS?
    After the order, the supplier can send ORDRSP, then DESADV when the goods leave, and finally INVOIC. The retailer confirms receipt with RECADV.
    How do I get ORDERS into my ERP?
    Through ERP integration or through the Web EDI portal, where orders can be viewed and exported. EDIconnect converts the document automatically between the retailer's format and your ERP format.
    Reviewed by The EDIconnect Team : EDI & Business Operations experts · Last updated: June 13, 2026

    Receiving EDI orders from retailers?

    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.