EPCIS (Electronic Product Code Information Services)

EPCIS is an open GS1 standard that enables trading partners to share information about the physical movement and status of products as they travel through the supply chain. It answers four fundamental questions about any supply chain event — What (which products), When (timestamp), Where (location), Why (business context) — and in v2.0 adds a fifth dimension: How (sensor/IoT conditions such as temperature and humidity).

---

How it works

EPCIS operates through a capture-and-query model: at each supply chain point, an EPCIS Capturing Application records events into an EPCIS Repository; downstream, an EPCIS Accessing Application queries those repositories to retrieve event histories. No single organisation needs to hold all the data. (Source: MyProductPassport, updated 2026-07-22)

A subscription mechanism enables push delivery: systems can register a callback URL to automatically receive matching new events, rather than polling.

---

Current standard version

EPCIS 2.0.0 (ratified 22 June 2022); companion standard CBV 2.0.0 ratified same date. The GS1 artefacts page labels the combined bundle as "EPCIS / CBV 2.0.1" — a minor point release of the PDF document. The canonical machine-readable repository entry reads 2.0.0. (Source: GS1 standards repository, ref.gs1.org, as-of 2026-07-22)

---

Five event types

Event type	What it captures	Notes
ObjectEvent	A physical or digital object observed, commissioned, or decommissioned at a location	Most commonly used event type
AggregationEvent	Packing/unpacking — items into cases, cases onto pallets, pallets into containers	ADD action = packing; DELETE action = unpacking; parentID + childEPCs fields
TransactionEvent	Physical products linked to a business transaction (purchase order, invoice, despatch advice)	Connects goods movement to commercial records
TransformationEvent	Manufacturing/processing: input products consumed (inputQuantityList) → output products produced (outputQuantityList)	Supports optional ilmd field for expiration dates and similar attributes
AssociationEvent	Long-term/permanent association between a sensor device and a reusable container or asset	New in v2.0 — e.g. attaching an IoT temperature logger to a cold-chain container

(Sources: MyProductPassport, 2025-08-14 updated 2026-07-22; TrackVision AI, 2024-11-11; GS1 White Paper on VCs + EPCIS, 2022-04)

---

v1.2 vs v2.0: what changed

Feature	EPCIS 1.2	EPCIS 2.0
Data format	XML only	XML + JSON + JSON-LD
API protocol	SOAP/WSDL	REST/OpenAPI (+ legacy SOAP retained)
IoT sensor data	❌	✅ temperature, humidity, pressure, shock, tilt
GS1 Digital Link identifiers	❌	✅ product IDs expressed as Digital Link URIs
Event types	4 (Object, Aggregation, Transaction, Transformation)	5 (+ AssociationEvent)
Linked data	❌	✅ JSON-LD context for semantic web
Push delivery	❌	✅ HTTP Callback (webhook) + optional WebSocket
Conformance artefacts	XSD schemas	XSD + OpenAPI JSON + JSON Schema + SHACL

(Sources: Digimarc, 2022-07-06; MyProductPassport, 2025-08-14 updated 2026-07-22; GS1 standards repository, 2026-07-22)

---

Core Business Vocabulary (CBV)

CBV is a companion standard to EPCIS defining the permitted values for EPCIS event context fields. It specifies approximately 41 standardised business step codes (bizStep field — e.g. shipping, receiving, packing, commissioning) and disposition codes indicating object state after an event (e.g. sellable_not_accessible, in_transit). CBV ensures events are semantically interoperable across different organisations' systems. (Source: TrackVision AI, 2024-11-11)

---

Relationship to GS1 Digital Link

In EPCIS 2.0, product and location identifiers can be expressed as GS1 Digital Link URIs ^[1] rather than legacy EPC URN notation, making events directly resolvable as web resources. (Source: TrackVision AI, 2024-11-11)

Together, Digital Link + EPCIS form a DPP-ready architecture: Digital Link provides the QR-scannable URI entry point for accessing passport data, while EPCIS provides the event history that populates the traceability sections of the Digital Product Passport. EPCIS 2.0's JSON-LD support enables events to be published as semantic web / linked data, making them machine-discoverable without prior schema agreement — aligning with the European Commission's vision of a decentralised DPP ecosystem. (Source: MyProductPassport, updated 2026-07-22)

---

Retail and ecommerce applications

GS1 US identifies the following EPCIS use cases for retail: sharing product information, demand planning, new product introductions, supply route analysis, real-time inventory corrections, and faster and more targeted recall execution. (Source: GS1 US Benefits of EPCIS PDF)

When paired with item-level data capture methods like RFID, businesses gain near real-time inventory understanding with fewer stockouts, fewer shipping errors, and better forecasting. (Source: Tracex Technologies, date unknown)

[!unverified] The RFID + EPCIS inventory benefit claim (fewer stockouts, shipping errors, better forecasting) sourced from Tracex Technologies blog with no publication date. Treat as vendor claim pending independent benchmark source.

Kezzler, a serialisation and traceability platform vendor, describes EPCIS 2.0 as enabling "AI-ready data" for intelligent supply chain operations by standardising visibility event data down to serial item level. (Source: Kezzler blog, 2025-08-04 webinar companion)

---

Regulatory compliance drivers

EU Digital Product Passport (ESPR/DPP)

MyProductPassport describes EPCIS as the "event backbone" for Digital Product Passport|EU Digital Product Passports under ESPR, transforming a passport from a static data sheet into a comprehensive, verifiable record of a product's entire lifecycle. (Source: MyProductPassport, updated 2026-07-22)

The EU is aligning DPP technical requirements with GS1 Digital Link (for URI-based product identifiers) and EPCIS 2.0 (for supply chain event data). (as-of 2026-07-22) (Source: MyProductPassport, updated 2026-07-22)

For apparel and textiles, the ESPR delegated act mandating DPPs is planned for 2027 with enforcement likely from 2028. (as-of 2026-07-22)

KPMG's 2026 European DPP Readiness Survey found that 81% of European companies lack the structured lifecycle data required for DPP compliance. (as-of 2026, second-hand citation) (Source: Fairlymade.com citing KPMG 2026)

EU Deforestation Regulation (EUDR)

GS1 published a provisional EUDR standard (version p.0.0, September 2025) referencing EPCIS as a mechanism for communicating reference and verification numbers. EUDR compliance deadlines (as-of 2025-09-24): 30 December 2026 for large/medium operators; 30 June 2027 for micro/small operators. (Source: GS1 EUDR Provisional Standard p.0.0, ref.gs1.org, 2025-09-24)

US Drug Supply Chain Security Act (DSCSA)

DSCSA requires all pharmaceutical trading partners to exchange serialisation data (T3: Transaction Information, History, Statement) electronically in EPCIS format. Staggered deadlines (as-of 2025-01): manufacturers May 27 2025; wholesale distributors August 27 2025; large dispensers November 27 2025; small dispensers (under 26 FTE) November 27 2026. (Source: Frier Levitt, 2025-01-01)

US Food Safety Modernization Act — FSMA 204

FSMA 204 (FDA Food Traceability Rule) originally mandated compliance by January 2026; the FDA proposed a 30-month extension, with practical enforcement not expected before July 2028. EPCIS 2.0 is the primary proposed data exchange format for Critical Tracking Events. (Source: QRStuff blog; date unknown — treat as potentially stale)

---

Implementation challenges

MyProductPassport identifies four key EPCIS adoption challenges (as-of 2026-07-22):

1. Data sovereignty and privacy — events may expose commercially sensitive supplier relationships and production volumes
2. Legacy system integration — older ERP/WMS systems were not designed to generate EPCIS events, requiring middleware or re-implementation
3. Scalability — high-volume supply chains generate millions of events daily
4. Standardisation of business context — trading partners must agree on CBV codes and event granularity

Cloud-based EPCIS platforms have emerged as a practical solution for onboarding smaller suppliers, offering hosted repositories, simplified capture interfaces, and pre-built integrations with ERP and WMS systems. (Source: MyProductPassport, updated 2026-07-22)

Digimarc VP of Innovation Dominique Guinard (GS1 Digital Link work group co-chair and EPCIS 2.0 contributor) attributed EPCIS 1.0's low post-2007 adoption to market unreadiness: "back then, transparency was a taboo subject. As a result, the need and/or demand for interoperability was limited." (Source: Digimarc, 2022-07-06)

---

Key terms

Term	Meaning
EPCIS	Electronic Product Code Information Services — GS1 standard for supply chain event data
CBV	Core Business Vocabulary — companion standard defining permitted business step and disposition codes
EPC	Electronic Product Code — serialised product identifier (e.g. SGTIN for trade items, SSCC for logistics units)
bizStep	EPCIS field specifying the business process step at which an event occurred (standardised by CBV, e.g. shipping, receiving)
disposition	EPCIS field specifying the business condition of the object after the event (e.g. in_transit, sellable_not_accessible)
ilmd	Instance/Lot Master Data — optional EPCIS field for static attributes such as expiration dates and lot numbers
Capturing Application	System that generates and writes EPCIS events to a repository
Accessing Application	System that reads and queries EPCIS event data from a repository
AssociationEvent	New EPCIS 2.0 event type for permanent/semi-permanent sensor-to-asset associations
JSON-LD	JSON Linked Data — EPCIS 2.0 serialisation enabling semantic web / linked data compatibility
OpenEPCIS	Open-source EPCIS 2.0 implementation (community project)

---

Vendor landscape (as-of 2026-07-22)

The following vendors provide cloud-based EPCIS platforms or EPCIS-integrated traceability solutions (vendor-attributed — independent comparative assessment not found):

• Kezzler — Connected Products Platform with EPCIS 2.0; Q1 2026 updates include enhanced Batch Flow visualiser and automated DPP workflows
• Digimarc — EPCIS 2.0 contributor; position papers on v1.2→v2.0 migration
• TrackVision AI — EPCIS 2.0 explainer and platform offering
• OpenEPCIS — open-source EPCIS 2.0 implementation
• IBM Sterling — mentioned in traceability context (no v2.0 content confirmed)
• SAP — mentioned in traceability context (no v2.0 content confirmed)

---

GS1 Digital Link + EPCIS + Sunrise 2027 convergence

GS1 Connect 2026 conference featured industry leaders discussing how breaking down data silos through shared standards unlocks the full potential of GS1 Sunrise 2027 — the initiative requiring all retail POS systems globally to be capable of reading GS1-compliant 2D barcodes by end of 2027. Until 90% of POS scanning solutions reach this capability, products using 2D barcodes on-pack must still carry a companion linear barcode. (as-of 2025-12-01) (Source: GS1 US, GS1 Connect 2026 promotional materials, 2025-12-01)

The GS1 Sunrise 2027 transition is a key upstream dependency for EPCIS-at-retail: 2D barcodes encoding GTINs as Digital Link URIs become the default on-pack data carrier, feeding event capture systems that write to EPCIS repositories.

---

Next frontier topics

• EUDR — EU Deforestation Regulation; GS1 provisional standard published; 4 dangling links; deadline Dec 2026
• Serialisation — foundational to EPCIS item-level tracking; 4 dangling links
• Supply Chain Visibility — broader discipline EPCIS feeds into; 4 dangling links
• DSCSA — US pharma EPCIS mandate; active enforcement deadlines; 3 dangling links
• GS1 Sunrise — 2027 POS barcode transition; convergent with EPCIS/Digital Link
• EPCIS CBV / Core Business Vocabulary — companion standard deserving its own page

References

1. e.g. ` — id.gs1.org/01/[GTIN]/21/[serial]`