Message us on WhatsApp
    Back to glossary
    Standards

    EANCOM: the EDIFACT subset for retail

    EANCOM is the EDIFACT subset for retail and FMCG, maintained by GS1. It keeps the EDIFACT structure but narrows messages down to what trade needs and requires GS1 identifiers: GTIN for products, GLN for parties and locations, SSCC for logistic units. Retailers ask for it for ORDERS, DESADV and INVOIC.

    Full definition

    EANCOM is the EDIFACT subset dedicated to retail and FMCG, maintained by GS1. It simplifies EDIFACT through strict rules and the use of GS1 identifiers (GTIN, GLN, SSCC). It is the default format required by retailers across Romania and Europe for ORDERS, DESADV and INVOIC.

    EANCOM compared with EDIFACT

    EANCOM is not a separate standard, but a stricter way of using EDIFACT:

    EDIFACT and EANCOM: main differences
    AspectEDIFACTEANCOM
    RoleGeneral standard, for several industriesSubset for retail and FMCG
    Maintained byThe United NationsGS1
    IdentifiersVaried codes, depending on the partnerGTIN, GLN and SSCC
    OptionsMany optional segments and codesStricter rules and fewer options

    EANCOM messages in retail

    The usual flow between retailer and supplier uses these EANCOM messages:

    • ORDERS: the order; ORDRSP: the order response.
    • DESADV: the despatch advice; RECADV: the receiving advice.
    • INVOIC: the invoice; REMADV: the remittance advice.
    • PRICAT: the price catalogue; INVRPT: the inventory report.

    Illustrative example: GS1 identifiers in EANCOM

    The segments below show where the GS1 keys appear. In NAD, the trailing qualifier 9 points to GS1 as the coding agency; in LIN, SRV marks a GTIN; in GIN, BJ marks an SSCC. The codes are fictitious, with valid check digits. The example is illustrative and simplified; follow the partner's implementation guide.

    Illustrative example
    NAD+DP+2000003000036::9'
    LIN+1++5940000000011:SRV'
    GIN+BJ+359400000000000012'

    Common mistakes with EANCOM

    • A directory version different from the one the retailer requires.
    • GLN, GTIN or SSCC codes with a wrong check digit.
    • A missing or wrong agency qualifier, for example no 9 for GS1.
    • Segments the retailer's guide makes mandatory but that are missing from the message.
    • Assuming two retailers require exactly the same EANCOM; each publishes its own rules.

    How EDIconnect works with EANCOM

    EDIconnect converts automatically between your ERP and the EANCOM format each connected retailer requires. You work from the Web EDI portal or through ERP integration, without writing messages by hand.

    EANCOM in the EDIconnect platform

    Frequently asked questions about EANCOM

    What is EANCOM?
    EANCOM is the EDIFACT subset for retail and FMCG, maintained by GS1. It uses GS1 identifiers such as GTIN, GLN and SSCC.
    What is the difference between EDIFACT and EANCOM?
    EDIFACT is the general standard. EANCOM narrows it for retail, with stricter rules and GS1 identifiers.
    Which EANCOM messages are used in retail?
    Most often ORDERS, ORDRSP, DESADV, RECADV and INVOIC. Other messages in use are REMADV, PRICAT and INVRPT.
    Do I need a GTIN and a GLN for EANCOM?
    EANCOM relies on GS1 keys: GTIN for products and GLN or ILN for locations. Location codes can come from GS1 or from an ILN series, while GTINs are obtained through a GS1 licence.
    Do all retailers use the same EANCOM?
    No. Each retailer publishes its own implementation guide, with versions, mandatory segments and codes of its own, which apply on top of the standard.
    Reviewed by The EDIconnect Team : EDI & Business Operations experts · Last updated: June 13, 2026

    Need EANCOM with retailers?

    EDIconnect converts between your ERP and EANCOM and takes each connected retailer's specification into account.

    Last updated: November 2026.