Retail EDIFACT — Alphamega, Sklavenitis, Lidl, Papantoniou
Long before any legal e-invoice obligation, Cypriot grocery retail already exchanges its commercial documents over EDI (Electronic Data Interchange — structured document exchange between computers, paperless). The dominant format is EANCOM, the subset of the EDIFACT standard defined by GS1 for retail. The chains — Alphamega, Sklavenitis Cyprus, Lidl Cyprus, Papantoniou and the local chain Metro — send orders to and receive despatch advices and invoices from their suppliers in this format.
History — how EDI reached Cypriot retail
Cypriot retail organised itself around a few family groups and international chains. EDI arrived there by the same logic as elsewhere in Europe: as volumes grew, manual order entry became a bottleneck. Cyprus's membership of GS1 provided the common language (GTIN, GLN) that makes EANCOM interoperable with foreign suppliers. The arrival of Lidl and the expansion of Greek-origin chains such as Sklavenitis accelerated the professionalisation of exchanges, those groups importing their continental EDI practices.
Governance — GS1 Cyprus + EANCOM
The GS1 Cyprus organisation assigns company prefixes and administers GTIN identifiers (product barcodes) and GLN (location codes). The EANCOM standard itself is maintained worldwide by GS1: for retail, it pins down which EDIFACT segments are mandatory and how to fill them. There is no specific national governance beyond GS1 — that is the strength of the standard: a German supplier speaks the same EANCOM as a Cypriot supplier.
Schema — the ORDERS / DESADV / INVOIC trio
The EANCOM commercial cycle rests on three cardinal messages:
- ORDERS — the order issued by the chain to the supplier.
- DESADV — the despatch advice announcing a delivery's contents, often tied to an SSCC logistics label.
- INVOIC — the invoice, reconciled against the order and the receipt.
Example ORDERS message from Alphamega to a supplier, GS1 identifiers in support:
UNH+1+ORDERS:D:01B:UN:EAN010'
BGM+220+PO-ALM-2026-77410+9'
DTM+137:20260616:102' ' order date
DTM+2:20260620:102' ' requested delivery date
NAD+BY+5290000123450::9' ' buyer Alphamega (GLN)
NAD+SU+5290000987651::9' ' supplier (GLN)
NAD+DP+5290000123467::9' ' delivery warehouse (GLN)
LIN+1++5290011223344:EN' ' product (GTIN-13)
QTY+21:240:PCE' ' 240 units
PRI+AAA:0.89' ' unit price
UNS+S'
CNT+2:1'
UNT+12+1'Chains — local vs Greek
| Chain | Profile | EDI note |
|---|---|---|
| Alphamega | Hypermarkets, major Cypriot player | Mature EANCOM, broad supplier base |
| Sklavenitis Cyprus | Greek-origin chain | Imports its continental EDI practices |
| Lidl Cyprus | International discounter (Schwarz) | Highly standardised EDI, strict requirements |
| Papantoniou | Regional supermarkets (Paphos) | EANCOM on core range |
| Metro | Local Cypriot chain | Progressive EDI adoption |
Adoption — suppliers and VANs
- Supplier onboarding: chains often mandate EDI above a certain volume, with an EANCOM implementation guide and a conformance test.
- Transport: messages carried over VANs (value-added networks) or point-to-point AS2; some small suppliers use web portals (web-EDI).
- PEPPOL coexistence: the EANCOM INVOIC can be paired with a PEPPOL invoice for flows requiring EN 16931 compliance.
- Voluntary: no legal obligation — EDI prevails through commercial efficiency, not a mandate.
Common pitfalls
- Wrong GLN. Confusing the head-office GLN with the delivery-warehouse GLN delivers to the wrong place or blocks reconciliation.
- Unsynchronised GTIN. A product whose GTIN is not up to date on the chain's side triggers an order-line rejection.
- Diverging EANCOM version. Each chain pins an EANCOM version/subset; sending a segment not allowed by its guide causes a rejection.
- Skipping the DESADV. Without the despatch advice, the receipt is not pre-populated and the INVOIC does not reconcile automatically.