Skip to main content
Back to Standards
Electronic Product Code Information Services logo

Electronic Product Code Information Services

EPCIS

A global GS1 standard for creating and sharing visibility event data across supply chain enterprises. EPCIS provides a common language for capturing what, where, when, and why events occur as physical or digital objects move through business processes. Version 2.0, ratified in June 2022, introduces a JSON/JSON-LD binding alongside the original XML binding, adds REST API support, and is accompanied by the Core Business Vocabulary (CBV) 2.0 for standardized event semantics. Originally developed from the MIT Auto-ID Center's Physical Markup Language concept.

Overview

EPCIS is a GS1 standard for capturing and sharing supply chain visibility event data across trading partners. It provides a standardized way to record what happened, where, when, and why as physical or digital objects move through business processes, enabling end-to-end traceability from manufacturing through distribution to the point of sale.

Background

EPCIS traces its origins to the MIT Auto-ID Center, which published a 2001 paper proposing the Physical Markup Language (PML) as a universal language for describing physical objects. When EPCglobal took over the Auto-ID Center's work in 2004, PML was reconceived as Electronic Product Code Information Services. The first version of the EPCglobal Architecture Framework (2005) positioned EPCIS within a broader architecture for RFID-based object tracking in supply chains. EPCIS 1.0 was ratified in April 2007, with over 30 companies having already used the draft standard for data exchange.

Purpose & Scope

EPCIS defines a data model for visibility events — discrete records of business activities involving identified objects. Despite the "EPC" in its name (a historical artifact from its RFID origins), EPCIS supports any identification scheme including GS1 barcodes, RFID tags, and other identifiers. The standard covers:

  • Object Events — observations of objects at a location and time
  • Aggregation Events — packing or unpacking of objects into containers
  • Transaction Events — association of objects with business transactions
  • Transformation Events (since EPCIS 1.1) — processes where inputs become outputs
  • Association Events (since EPCIS 2.0) — linking objects to other entities

Each event captures four dimensions: What (identified objects), Where (location), When (timestamp), and Why (business context drawn from the Core Business Vocabulary).

Version History

Version Year Key Changes
1.0 2007 Initial release
1.1 2014 Class-level identification, Transformation Events
1.2 2016 Error declaration, master data in headers
2.0 2022 JSON/JSON-LD binding, REST API, digital link URIs

Serializations & Technical Formats

EPCIS 2.0 supports both XML and JSON/JSON-LD bindings. The XML binding follows the established EPCIS document format, while the JSON-LD binding enables semantic web interoperability and aligns with modern REST API patterns. The accompanying Core Business Vocabulary (CBV) 2.0 provides standardized identifiers for business steps, dispositions, and other event context.

Governance & Maintenance

EPCIS is developed and maintained by GS1, the global standards organization responsible for barcodes, EDI, and supply chain standards. The standard goes through a formal ratification process involving GS1 member organizations worldwide. Conformance testing is administered by designated testing partners.

Notable Implementations

EPCIS is deployed across pharmaceutical supply chains (for drug serialization and traceability mandated by regulations like the US Drug Supply Chain Security Act), food safety traceability, retail inventory management, and logistics. The standard is supported by numerous commercial middleware and integration platforms that have received GS1 compliance certification.

Further Reading