Compendium

Retail / Supply-Chain / GS1 / Commerce DSLs Family Index

14 min read

Retail / Supply-Chain / GS1 / Commerce DSLs Family Index

type: language-family-index family: retail-supplychain languages_catalogued: 26 tags: [language-reference, family-index, retail-supplychain, gs1, epcis, gtin, edi, edifact, ansi-x12, ubl, peppol, factur-x, zugferd, oagis, cxml, rosettanet]

Retail / Supply-Chain / GS1 / Commerce — Family Index

Family overview

The retail and supply-chain “language” stack is, by historical accident, one of the most layered DSL ecosystems in computing. At the root sits GS1, the not-for-profit standards body whose General Specifications govern the world’s barcodes — UPC, EAN-13, ITF-14, GS1-128, GS1 DataMatrix, GS1 QR. GS1 also owns the identifier hierarchy that the rest of the stack depends on: GTIN (Global Trade Item Number, the number behind every UPC/EAN), GLN (Global Location Number, addressing trading parties and physical sites), SSCC (Serial Shipping Container Code, addressing logistic units / pallets), plus GIAI, GRAI, GSRN, GDTI, GINC for assets, returnables, service relations, documents, and consignments. Application Identifiers — the parenthesised (01), (10), (17) codes — are the micro-DSL that parses a GS1-128 payload into discrete GTIN/batch/expiry fields.

On top of identifiers sits traceability. EPCIS (Electronic Product Code Information Services) is GS1’s event-tracking lingua franca: an XML and JSON-LD schema for “what, where, when, why” events as products move through a supply chain. EPCIS 2.0 was ratified by GS1 in June 2022 and published as ISO/IEC 19987:2024 on 22 March 2024, making EPCIS a full ISO standard. EPCIS travels with CBV (Core Business Vocabulary), the controlled vocabulary that gives the events their semantic anchors (business steps, dispositions, source/destination types). EPCIS adoption has gone from “nice to have” to compliance-mandatory under regimes like FDA DSCSA (manufacturers compliant May 2025, wholesalers August 2025, small-dispenser exemption ends 27 November 2026) and EU FMD; the EU Deforestation Regulation (EUDR), now applying from 30 December 2026 after the December 2025 postponement, is pulling commodity-traceability into the same orbit even though EUDR uses its own Information System rather than EPCIS proper.

The newest GS1 wave is GS1 Digital Link — a URI syntax (https://id.gs1.org/01/9521234567890) that makes a barcode web-resolvable, so a single 2D code can drive both POS scanning and consumer/brand experiences. The standard is at v1.1.1 (with a v1.2.0 GS1-Conformant Resolver published January 2026); the GS1 Web Vocabulary provides Schema.org-aligned product metadata for the resolved content. This is the substrate for Sunrise 2027, GS1’s global initiative for retail POS systems to be capable of scanning 2D codes (GS1 QR built to Digital Link, or GS1 DataMatrix) alongside 1D UPC by 31 December 2027 — Tesco became the first UK supermarket to ditch traditional UPCs in April 2026, with Walmart, Target, Kroger, and Woolworths committed to piloting.

Parallel to GS1’s identifier-and-event stack runs the EDI universe: UN/EDIFACT (with the D.96A subset still the most-deployed retail flavour, formalised in GS1 EANCOM), ANSI X12 (with VICS EDI the retail subset), and a clutch of newer XML/JSON-based B2B languages — UBL 2.4 (ISO/IEC 19845, published by OASIS in June 2024), Peppol BIS Billing 3.0 (a UBL-based EN 16931 CIUS, current November 2025 release, mandatory for Belgian B2B from 1 January 2026 and on similar trajectories in France, Poland, and Germany), Factur-X / ZUGFeRD (hybrid PDF/A-3 + embedded UN/CEFACT CII XML invoice, refreshed to Factur-X 1.0.8 / ZUGFeRD 2.4 on 15 January 2026), cXML (Ariba/SAP B2B, currently at Reference Guide 1.2.069/070 in 2026), OAGIS (10.12 released June 2025), and RosettaNet PIPs running on RNIF 2.0.01 for high-tech and semiconductor supply chains. The dominant 2026 reference architecture: GS1 identifiers in the barcode, EPCIS for event traceability, UBL/Peppol or EDIFACT for transactional messaging, GDSN for master-data sync.

In our deep library

None catalogued. These standards do not have standalone deep-library notes; they sit on top of XML/JSON schemas and are documented in the source-of-truth specs (GS1, OASIS, UN/CEFACT, X12, OpenPeppol).

Cross-reference:

  • financial-regulatory — sibling family; UN/EDIFACT, ANSI X12, ISO 20022, and SWIFT MX are catalogued there as financial-message DSLs. The retail and financial uses of EDIFACT/X12 share syntax but use different segment/transaction-set inventories.
  • api-description — XSDs, JSON Schemas, and OpenAPI definitions used to formalise UBL, EPCIS, cXML, OAGIS payloads.
  • notation-spec — ABNF/EBNF/grammar formalisms underlying GS1 Application Identifier parsing.
  • citation-formats — Schema.org cross-link: schema:Product, schema:Offer, schema:ProductGroup and the GS1 Web Vocabulary alignment with Schema.org.
  • identity-auth-policy — AS2/AS4, OAuth, and certificate-based authentication for Peppol Access Points and EDI VAN replacements are adjacent.
  • healthcare-clinical — pharma-traceability DSCSA EPCIS feeds and HL7 FHIR are cousins; EPCIS is the “logistics side” of pharma identity.

Tier 3 family table — GS1 identifiers & barcodes

FormatFirst appearedOriginTypeStatus (2026)URL
GS1 General Specifications1974 (UPC), formalised as GS1 GenSpecs since the 1990s; current edition annualGS1 (formerly Uniform Code Council, EAN International)Master standard governing barcode symbologies (UPC, EAN-13, ITF-14, GS1-128, GS1 DataMatrix, GS1 QR) and identifier constructionActive, annual revision; v25 is the 2025 edition with v26 in 2026https://www.gs1.org/standards/barcodes-epcrfid-id-keys/gs1-general-specifications
GTIN (Global Trade Item Number)1974 (as UPC); GTIN umbrella term 2005GS18/12/13/14-digit numeric identifier for trade items; GTIN-12 ≡ UPC, GTIN-13 ≡ EAN-13Active; foundationalhttps://www.gs1.org/standards/id-keys/gtin
GLN (Global Location Number)1989GS1 (EAN)13-digit identifier for legal/functional/physical locations and trading partiesActivehttps://www.gs1.org/standards/id-keys/gln
SSCC (Serial Shipping Container Code)1989GS118-digit identifier for logistic units (pallets, cartons in transit)Active, ubiquitous in DESADV/ASNhttps://www.gs1.org/standards/id-keys/sscc
GS1 Application Identifiers (AIs)1990sGS1Parenthesised micro-DSL (01)9521234567890(17)260901(10)BATCH1 parsed inside GS1-128 / GS1 DataMatrix payloadsActive, list grows annuallyhttps://www.gs1.org/standards/barcodes/application-identifiers
GS1 EPC Tag Data Standard (TDS)2005 (EPCglobal), TDS 2.1 (2024)GS1 EPCglobalRFID tag identifier encoding; binary EPC encodings mapping to URI form urn:epc:tag:...Active, TDS 2.1 current; aligned with EPCIS 2.0https://ref.gs1.org/standards/tds/
GS1 Digital Link2018 (v1.0), v1.1.1 current; Conformant Resolver v1.2.0 (Jan 2026)GS1URI syntax https://id.gs1.org/01/0952… making barcodes web-resolvable; basis for Sunrise 2027Very active; v1.1.1 standard, July 2025 EPC-compression TS 1.0.0https://www.gs1.org/standards/gs1-digital-link
GS1 Web Vocabulary2018GS1Schema.org-aligned RDF/JSON-LD vocabulary for product metadata published at resolved Digital Link URIsActivehttps://www.gs1.org/voc/
GS1 NPC (National Product Classifier)Regional, variesGS1 country MOs (e.g., GS1 US)Country-specific product classification codes layered atop GTINActive, minor regionalhttps://www.gs1us.org/
GS1 LCL (Locale Configuration Layer)2010sGS1Country/locale configuration for resolvers and Digital Link behaviourActive, adjacenthttps://ref.gs1.org/standards/lcl/

Tier 3 family table — Event tracking / EPCIS

FormatFirst appearedOriginTypeStatus (2026)URL
EPCIS 2.01.0 (2007); 1.2 (2016); 2.0 ratified June 2022GS1 (EPCglobal lineage)XML and JSON-LD schema for supply-chain visibility events (“ObjectEvent”, “AggregationEvent”, “TransactionEvent”, “TransformationEvent”, “AssociationEvent”); REST API binding new in 2.0Active, published as ISO/IEC 19987:2024 on 22 March 2024https://www.gs1.org/standards/epcis
CBV (Core Business Vocabulary) 2.01.0 (2011); 2.0 (2022)GS1Controlled vocabulary for EPCIS bizSteps, dispositions, source/destination typesActive, ISO/IEC 19988:2024https://ref.gs1.org/cbv/
EPC Pure Identity URIs2005GS1 EPCglobalURI namespace (urn:epc:id:sgtin:…, urn:epc:id:sscc:…) used as primary identifier in EPCIS eventsActive, foundationalhttps://ref.gs1.org/standards/tds/

Tier 3 family table — Product data sync

FormatFirst appearedOriginTypeStatus (2026)URL
GDSN (Global Data Synchronisation Network)2004GS1XML schema for master-data sync between supplier and retailer data pools; Maintenance Release 3.1 seriesActive; MR 3.1.36 deployed Aug 2026, MR 3.1.37 Nov 2026, MR 3.1.38 Feb 2027https://www.gs1.org/standards/gdsn
1WorldSync / AtrifyCommercial provider1WorldSync (Chicago)Largest GDSN-certified data pool; not a language but the dominant commercial implementationActive commercialhttps://www.1worldsync.com/
PIES (Product Information Exchange Standard)Late 1990s; PIES 8.0 released 2 April 2026Auto Care Association (ASC X9/SEMA lineage)XML schema for automotive aftermarket product data; companion to ACES 5.0Active, PIES 8.0 (April 2026)https://www.autocare.org/data-standards/product-information-exchange-standard-(pies)
ETIM (European Technical Information Model)1990s; ETIM 9.0 (2021), 10.0 (2023), 11.0 in planning (Jan 2026 approval)ETIM International, NetherlandsClassification standard for technical/electrical/HVAC products; ETIM IXF XML format + BMEcat 5.0Active, ETIM 11.0 release planning approved January 2026https://www.etim-international.com/
Schema.org Product / Offer / ProductGroup2011 (Schema.org founding)Google, Microsoft, Yahoo, YandexRDFa/JSON-LD vocabulary; Web-of-data product metadata; aligned with GS1 Web VocabularyVery activehttps://schema.org/Product

Tier 3 family table — EDI / B2B messages

FormatFirst appearedOriginTypeStatus (2026)URL
UN/EDIFACT D.96ADirectory 96A released 1996UN/CEFACTSegment/element EDI syntax; D.96A is the most-widely-deployed retail directory (ORDERS, DESADV, INVOIC, ORDRSP, PRICAT) — formalised as GS1 EANCOM subsetPersistent legacy active; D.96A still dominant in European retail in 2026https://unece.org/trade/uncefact/introducing-unedifact
GS1 EANCOM1990 (D.93A); D.96A and D.01B subsets still in useGS1EDIFACT subset profile for retail (ORDERS, DESADV, INVOIC etc.) with GS1 identifiers baked inActive, dominant EDI flavour for grocery and FMCGhttps://www.gs1.org/standards/edi/
ANSI X12 (VICS subset)1979 (X12); VICS retail subset 1986ANSI ASC X12 / VICS (Voluntary Interindustry Commerce Standards)Transaction-set EDI dialect; VICS profiles 850/810/856/812/832 for retail; also catalogued in financial-regulatoryActive, dominant in North American retailhttps://x12.org/
cXML (Commerce XML)1999Ariba (now SAP)XML B2B messaging — PunchOut catalogues, purchase orders, invoices; Ariba Network standardActive, Reference Guide 1.2.069 (Feb 2026), 1.2.070 (May 2026)https://cxml.org/
xCBL (XML Common Business Library)1999Commerce One / SAPXML B2B predecessor; widely superseded by UBL and cXMLLegacy, low new adoptionhttps://xml.coverpages.org/xCBL.html
OAGIS (Open Applications Group Integration Specification)1995 (1.0); OAGIS 10 since 2014; 10.12 released June 2025Open Applications Group (OAGi)XML Business Object Documents (BODs) for ERP/A2A/B2B integration; canonical-data-model styleActive, OAGIS 10.12 (June 2025)https://oagi.org/
RosettaNet PIPs / RNIF 2.0.011998RosettaNet consortium (now under GS1 US)XML “Partner Interface Process” message choreographies for high-tech, semiconductor, chemical supply chains; RNIF 2.0.01 is the implementation frameworkMaintained, narrow industry usage (semiconductors, electronics, chemicals); now stewarded by GS1 UShttps://www.gs1us.org/resources/rosettanet
CIDX (Chem eStandards)1985Chemical Industry Data ExchangeChemical-industry B2B XML; partially absorbed into RosettaNet PIPsLegacy, surviving usage inside larger RosettaNet-aligned deploymentshttps://www.gs1us.org/industries/chemical

Tier 3 family table — E-invoicing / digital commerce

FormatFirst appearedOriginTypeStatus (2026)URL
UBL (Universal Business Language) 2.4UBL 1.0 (2004); UBL 2.4 published 20 June 2024; UBL 2.5 in developmentOASIS UBL TCXML library of 93 business documents (Invoice, Order, DespatchAdvice, Catalogue, RemittanceAdvice etc.); ISO/IEC 19845Active, UBL 2.4 OASIS Standard (June 2024); UBL 2.5 in TChttps://docs.oasis-open.org/ubl/os-UBL-2.4/UBL-2.4.html
EN 16931Published 2017CEN (European Committee for Standardization)EU semantic model for the core invoice; the standard that EU B2G/B2B invoicing rests onActive, mandatory reference under Directive 2014/55/EU and growing B2B mandateshttps://www.cencenelec.eu/areas-of-work/cen-cenelec-topics/digital-society/einvoicing/
Peppol BIS Billing 3.03.0 (2017); November 2025 release currentOpenPeppolEN 16931 CIUS (Core Invoice Usage Specification) on UBL 2.1 syntax; transported over Peppol AS4 networkMandatory in 2026 for Belgian B2B (1 Jan 2026); rolling mandates in France, Poland, Germany, Romaniahttps://docs.peppol.eu/poacc/billing/3.0/
Factur-X / ZUGFeRDZUGFeRD 1.0 (2014); 2.0 (2019); Factur-X 1.0.8 / ZUGFeRD 2.4 effective 15 January 2026FNFE-MPE (France) + FeRD (Germany)Hybrid PDF/A-3 with embedded UN/CEFACT CII XML; EN 16931-conformantActive, joint FR/DE refresh January 2026 added sub-line itemshttps://www.ferd-net.de/en/standards/zugferd/factur-x
UN/CEFACT Cross Industry Invoice (CII)2011UN/CEFACTXML invoice schema; alternative syntax to UBL under EN 16931; the XML inside Factur-X/ZUGFeRDActivehttps://unece.org/trade/uncefact/xml-schemas

Total: 26 entries across 5 sub-tables.

Notable threads

  • GS1 Digital Link is the most consequential change to retail identifiers in 50 years. Since 1974, the UPC barcode has been a pure numeric lookup key — you scan it, the POS does a database lookup. GS1 Digital Link reframes that scan as a URL resolution: the same 2D code resolves to a Schema.org-tagged page (consumer experience, allergen data, recall info) when read by a phone, and to a GTIN when read by a POS scanner via the embedded AI structure. This is technically a re-encoding (the URL is still parsed for AI (01) → GTIN at POS) but operationally it collapses the “consumer QR” and the “retail barcode” into a single symbol — eliminating the pre-2024 pattern of stacking two codes on a pack.

  • Sunrise 2027 is the forcing function. GS1 has set 31 December 2027 as the deadline for global retail POS systems to be 2D-capable (GS1 QR built to Digital Link, or GS1 DataMatrix), keeping 1D UPC scanning as a fallback. Tesco became the first UK supermarket to drop traditional UPCs in April 2026; Walmart, Target, Kroger, and Woolworths have committed to piloting. Real-world adoption will lag the 2027 deadline — most analysts expect dual-code packaging through 2028–29 — because the constraint is not POS hardware (which has been 2D-capable for years) but the install base of label-design and ERP master-data pipelines that still assume GTIN-as-12-digit-number.

  • EPCIS 2.0 → ISO/IEC 19987:2024 is the standardisation milestone of the cycle. EPCIS was a GS1-only standard for 15 years; the March 2024 ISO/IEC publication makes it citeable in regulation in jurisdictions that require ISO references (rather than industry-body references) for compliance. The practical consequence is regulatory: FDA DSCSA (small-dispenser exemption ends 27 November 2026), EU FMD pharma, and emerging EUDR-adjacent commodity-traceability regimes can now point at an ISO number rather than a GS1 URL. EPCIS 2.0 also added a long-overdue REST/JSON-LD binding (the prior XML-only EPCISDocument was a 2007-era SOAP-adjacent shape), which finally makes EPCIS approachable from a modern API stack.

  • UBL + Peppol is winning EU e-invoicing. EN 16931 is the semantic standard; UBL and UN/CEFACT CII are its two permitted syntaxes; Peppol BIS Billing 3.0 (UBL-based) is the dominant CIUS in practice. Belgium’s 1 January 2026 B2B mandate was the milestone — every VAT-registered Belgian business must now exchange e-invoices structured to Peppol BIS 3.0 over the Peppol AS4 network. France’s mandate is staged through 2026–2027 (with Factur-X as the permitted hybrid format), Poland’s KSeF is rolling, and Romania, Greece, Germany are on similar trajectories. The 2024–26 cycle has effectively decided the EU-wide format question in UBL’s favour.

  • Factur-X / ZUGFeRD’s “embed the XML inside the PDF” approach has proven unexpectedly durable. When the format launched in 2014, the industry consensus was that hybrid PDF-plus-XML would lose to pure-structured (UBL or CII) because pure-structured is simpler to process. The opposite happened: in France and Germany, where AP clerks still review PDFs and the legal “human-readable” requirement is strong, the hybrid format scaled faster than pure XML did. The 15 January 2026 refresh to Factur-X 1.0.8 / ZUGFeRD 2.4 (jointly published by FNFE-MPE and FeRD) added sub-line items and maintained EN 16931 conformance — a healthy sign that the format is being actively maintained as the French B2B mandate progresses.

  • EDIFACT D.96A’s persistence is one of computing’s better-kept secrets. UN/EDIFACT Directory 96A was published in 1996. Thirty years later it remains the dominant EDI directory for European retail — ORDERS, DESADV (Despatch Advice / ASN), INVOIC, PRICAT, ORDRSP — embedded in GS1 EANCOM profiles, transported over AS2/AS4 or VAN connections, processed by SAP IDOC mappings written in the early 2000s. The reason is pure switching-cost economics: an EDIFACT D.96A integration that works is cheaper to maintain than to replace, and no replacement (UBL, Peppol, JSON) addresses the established trading-partner-network problem better than the status quo. Expect D.96A in production well into the 2030s.

  • The supply-chain-traceability regulatory wave is the demand driver for EPCIS through 2026–2030. FDA DSCSA reached full-interoperability for manufacturers (May 2025) and wholesalers (August 2025); the small-dispenser exemption ends 27 November 2026. EU FMD pharma traceability has been live since 2019. EUDR (EU Deforestation Regulation) applies from 30 December 2026 after the December 2025 postponement, requiring geolocation-based traceability for cattle, cocoa, coffee, palm oil, rubber, soy, wood — and although EUDR uses its own Information System rather than EPCIS, the upstream supplier networks doing the data capture have largely chosen EPCIS-shaped event records because the same supply chains already run EPCIS for pharma or food. Net: EPCIS is becoming the de facto “supply-chain event” wire format, and regulatory traceability is what is finally pulling it from “GS1 niche” to “universal lingua franca.”

  • The OAGIS / cXML / RosettaNet XML B2B world quietly continues. None of these have headline news, but all are actively maintained: OAGIS 10.12 (June 2025), cXML Reference Guide 1.2.069 (February 2026) and 1.2.070 (May 2026), RNIF 2.0.01 still the implementation framework for high-tech and semiconductor PIPs. They are the canonical example of “the boring layer that runs the world” — every Ariba/SAP-procurement transaction flows over cXML, every large ERP-to-ERP integration touches OAGIS BODs, every chip-supply-chain handoff between TSMC and a fabless customer rides RosettaNet. The 2026 reality is that EDI, EDIFACT, ANSI X12, UBL, and these XML B2B languages coexist in parallel rather than supersede each other.

Citations

Graph View