TRADACOMS — the UK-origin retail EDI standard

TRADACOMS (TRADing data COMmunicationS) is the very first mass-market retail EDI standard in Europe, published in 1982 by the ANA (Article Number Association, now GS1 UK). An EDI standard is a shared grammar that lets a retailer's computer and a supplier's computer exchange orders and invoices without human intervention. TRADACOMS predated EDIFACT and EANCOM — it remains the historical anchor of UK EDI, still present in legacy form across British grocery retail.

History — from the ANA 1982 to the GS1 UK legacy

In the late 1970s, the Article Number Association coordinated EAN barcode rollout across British retail. Once products were uniquely identified, the logical next step was to exchange commercial documents (order, delivery, invoice) in structured electronic form. In 1982 the ANA published TRADACOMS — the first mass-market retail EDI standard in Europe, several years before the United Nations standardised EDIFACT (1987).

Tesco, Sainsbury's, Marks & Spencer, Boots and ASDA adopted it massively through the 1980s and 1990s, over value-added networks (VANs: INS, GEIS, IBM). TRADACOMS became the default language of British retail. EANCOM, published in 1990 as an international UN/EDIFACT subset, was designated successor — but migration stayed slow: the installed TRADACOMS base was enormous and it simply worked.

1979       | The Article Number Association (ANA) coordinates EAN barcode
           | adoption in UK retail. The need to exchange orders and
           | invoices electronically emerges naturally between retailers
           | and their suppliers.
           |
1982       | TRADACOMS (TRADing data COMmunicationS) is published by the
           | ANA — the first mass-market retail EDI standard in Europe,
           | predating EDIFACT (1987) and EANCOM (1990).
           |
1985-1995  | Mass adoption by Tesco, Sainsbury's, Marks & Spencer, Boots,
           | ASDA. TRADACOMS becomes the dominant retail EDI rail in the
           | UK, carried over VANs (INS / GEIS / IBM).
           |
1990       | GS1 publishes EANCOM (a UN/EDIFACT subset) as the
           | international successor. The UK begins a slow migration —
           | but TRADACOMS remains massively deployed.
           |
2000-2010  | GS1 UK (former e.centre, former ANA) officially recommends
           | migration to EANCOM then GS1 XML. TRADACOMS no longer
           | evolves: the last schema update dates from the late 1990s.
           |
2010-2026  | TRADACOMS persists in legacy at many historical suppliers.
           | GS1 UK no longer actively maintains the standard but still
           | publishes the reference documentation.

Governance — ANA then GS1 UK

The standard was governed by the ANA, renamed e.centre in the early 2000s, then merged into GS1 UK, the British arm of the global GS1 organisation. GS1 UK still publishes the TRADACOMS reference documentation for historical purposes, but no longer evolves the schema: no new version has been issued since the late 1990s.

GS1 UK's official position is unambiguous: new deployments should use EANCOM (EDIFACT) or GS1 XML, aligned with international practice and interoperable beyond the UK market alone. TRADACOMS is a standard to maintain, not to extend.

Technical schema — TRADACOMS segments

TRADACOMS uses a segment syntax with its own separators, distinct from EDIFACT. A file opens with an interchange header segment STX and closes with END. Each inner message is framed by MHD (message header) and MTR (message trailer). A few structural segments:

• STX — Start of Transmission: sender, recipient (EAN/GLN codes), date, time, reference.
• MHD / MTR — message boundaries (header / trailer), with a segment counter.
• TYP — transaction type (e.g. 0430 NEW-ORDERS for an order).
• SDT / CDT — Supplier / Customer Details: parties identified by EAN location code.
• OLD — Order Line Detail: order line (product EAN, quantity, price, pack).
• END — end of transmission with the total message counter.

STX=ANAA:1+5012345000008:TESCO STORES+5060000000001:SUPPLIER+260616:101430+00001++ORDHDR'
MHD=1+ORDHDR:9'
TYP=0430+NEW-ORDERS'
SDT=5012345000008:0001+TESCO STORES LTD'
CDT=5060000000001:0002+ACME SUPPLIES LTD'
FIL=00001+1+260616'
MTR=6'
MHD=2+ORDERS:9'
CLO=:0001+TESCO DC LITTLEWICK+DA11 9DB'
ORD=ORD-2026-0042::260616'
DIN=260620+++0001'
OLD=1+5012345678900::EAN'
OLD=1++24+CASE+12.50'
MTR=6'
MHD=3+ORDTLR:9'
OTR=1'
MTR=2'
END=8'

TRADACOMS vs EANCOM / EDIFACT

Adoption — a persistent legacy

• Still in production at many historical suppliers connected to the big British chains, who never migrated a system that works.
• The large retailers (Tesco, Sainsbury's, ASDA, Morrisons) now accept EANCOM/GS1, but their VANs often convert TRADACOMS ↔ EANCOM behind the scenes to avoid breaking legacy connections.
• No future evolution — GS1 UK issues no new version; every new supplier onboarding uses EANCOM or GS1 XML.
• UK retail EDI market — the largest in Europe by volume; TRADACOMS remains its founding layer, even as its share mechanically declines each year.

Common pitfalls

• Parsing TRADACOMS with an EDIFACT engine. Separators and the terminal apostrophe differ; a naive EDIFACT mapper fails. A dedicated TRADACOMS parsing profile is required.
• Confusing location code with product number. The 13-digit EAN code in STX/SDT identifies a party (GLN), not a product. The product is the EAN-13 inside OLD.
• Assuming a 1:1 equivalence with EANCOM. TRADACOMS ↔ EANCOM conversion loses or approximates some fields: validate segment by segment, not in bulk.
• Believing the standard is maintained. TRADACOMS is frozen. Any new functional need must go through EANCOM or GS1 XML — do not wait for a patch.
• Forgetting the VAN context. Many TRADACOMS flows still transit over legacy value-added networks; migration to AS2/AS4 or PEPPOL must be planned with the retailer.

Cross-links

• United Kingdom hub — full view
• UK retail EDIFACT — Tesco, Sainsbury's, ASDA
• UK automotive EDI — JLR, Nissan, Toyota
• NHS PEPPOL — 2014 mandate
• GS1 UK — organisation and standards
• GS1 — EANCOM (international successor)