EPCIS (Electronic Product Code Information Services)

What is EPCIS?

EPCIS (Electronic Product Code Information Services) is a GS1 standard for capturing and sharing supply chain visibility events across trading partners. Where RFID hardware captures the physical movement of tagged items, EPCIS defines how to record, store, and exchange the resulting business events - who observed what item, when, where, and why.

Developed by GS1, EPCIS enables interoperability between organisations that may use different internal systems. A pharmaceutical manufacturer, a wholesale distributor, and a retail pharmacy can each record events in their own EPCIS repository and share them with partners using a common language. The current version is EPCIS 2.0 (published 2022), which adds JSON/JSON-LD support, a REST API, and alignment with GS1 Digital Link URIs alongside the original XML and SOAP interface from EPCIS 1.2.

EPCIS works with any automatic identification technology - UHF RFID , NFC , barcodes, or manual data entry. The standard is technology-agnostic; what matters is the event data, not how it was captured.

How it works: the four dimensions

Every EPCIS event answers four questions, known as the four dimensions:

• What: Which item or items were involved? Identified using an EPC (Electronic Product Code) or a GTIN -based identifier. Can be a single serialised item, a case, a pallet, or a class of trade items.
• When: The date and time the event occurred, recorded in ISO 8601 format with timezone. EPCIS distinguishes the event time (when it happened in the physical world) from the record time (when it was entered into the system).
• Where: The physical or logical location, expressed as a GLN (Global Location Number) or sub-location. Identifies the facility, dock door, production line, or specific storage location where the event took place.
• Why: The business context - what business process generated this event, and what was the disposition of the item afterwards. Expressed using standardised vocabulary from the Core Business Vocabulary (CBV), such as commissioning, shipping, or receiving.

Events are submitted to an EPCIS repository (a server that stores and serves event data) and queried by authorised trading partners. In EPCIS 2.0 this is done via a REST API with JSON-LD payloads. In EPCIS 1.2 the interface used SOAP/XML.

Event types

EPCIS defines four event types, each modelling a different category of supply chain action:

EPCIS 2.0 vs EPCIS 1.2

EPCIS 2.0, released in 2022, is a substantial update that modernises the standard for web-native environments:

EPCIS 1.2 remains widely deployed, particularly in pharmaceutical track-and-trace systems built before 2022. EPCIS 2.0 repositories are required to support both XML and JSON-LD and may optionally support EPCIS 1.2 XML for backward compatibility.

Core Business Vocabulary (CBV)

The Core Business Vocabulary (CBV) is a companion GS1 standard that defines standardised values for the business-context fields in EPCIS events. Without CBV, every organisation would invent its own terminology for business steps and dispositions, making cross-company interpretation impossible.

CBV defines two key field types:

• Business step (bizStep): The process step that generated the event. Common values include commissioning (item brought into the supply chain), shipping (item handed to a carrier), receiving (item accepted at a location), retail_selling (item sold to a consumer), decommissioning (item removed from circulation), and inspecting (item checked without a change of custody).
• Disposition: The state of the item after the event. Values include active, in_transit, in_progress, available, sold, recalled, destroyed, and dispensed (pharma). Disposition enables a query like "show me all items currently in transit between facility A and facility B."

CBV values are expressed as URIs (e.g. https://ref.gs1.org/cbv/BizStep-commissioning in EPCIS 2.0, or urn:epcglobal:cbv:bizstep:commissioning in EPCIS 1.2). Organisations can also define their own extension vocabulary for steps not covered by the standard.

EPCIS in practice

EPCIS is mandated or strongly recommended by several regulatory frameworks:

• US DSCSA (Drug Supply Chain Security Act): Requires US pharmaceutical manufacturers, wholesale distributors, and dispensers to exchange serialisation and traceability data. EPCIS is the interoperability standard of choice for DSCSA-compliant systems. Full interoperability requirements took effect in November 2024.
• EU Falsified Medicines Directive (FMD): Requires individual-pack serialisation and verification for prescription medicines across the EU. Manufacturers upload serialised item data; pharmacies verify against the EMVS (European Medicines Verification System) before dispensing. EPCIS is used internally by many participants to manage their own supply chain visibility alongside EMVS submissions.
• Food safety and traceability: GS1 and the FDA's FSMA 204 rule (Food Safety Modernization Act) require enhanced traceability records for high-risk foods. EPCIS provides the event structure for recording where food items originated, where they were processed, and where they were shipped.
• Retail inventory visibility: Large retailers use EPCIS to receive item-level RFID event data from suppliers. Receiving events confirm delivery; floor observation events feed inventory replenishment systems.

Advantages

• Interoperable across companies: Because all parties use the same GS1-defined event structure and CBV vocabulary, data produced by one organisation can be consumed by any other EPCIS-compliant system without custom integration work.
• Technology agnostic: Works with UHF RFID, NFC, GS1-128 barcodes, QR codes, DataMatrix, or manual entry. The event format is the same regardless of how the item was identified.
• End-to-end supply chain visibility: Events recorded at every hand-off point - manufacturer, 3PL, distributor, retailer - can be queried to reconstruct the complete journey of any serialised item.
• Regulatory compliance: Widely accepted as the standard for pharmaceutical serialisation compliance (DSCSA, FMD) and food traceability (FSMA 204).
• Flexible querying: EPCIS repositories support queries by EPC, time range, location, business step, and disposition - enabling both real-time lookups and historical analysis.
• GS1 Digital Link alignment (2.0): EPCIS 2.0 identifiers are resolvable web URIs, enabling integration with web-based product data and the broader GS1 linked-data ecosystem.

Limitations

• Complex to implement: EPCIS requires significant integration effort - ERP systems, WMS platforms, and RFID middleware must all be configured to generate correctly structured events with valid GS1 identifiers.
• Requires trading partner agreement: Both sides of a hand-off must agree on which EPCIS repository to use, which events to share, and what level of access each party has. Onboarding trading partners is often the largest implementation challenge.
• Data quality dependency: EPCIS is only as useful as the underlying capture data. Missing reads, incorrect location codes, or mis-scanned barcodes produce misleading event records that are difficult to reconcile after the fact.
• Not a real-time streaming protocol: EPCIS is an event repository standard, not a low-latency messaging protocol. For real-time tag-read streaming from RFID readers, purpose-built protocols such as LLRP or message brokers (MQTT, AMQP) are used upstream of EPCIS.
• GS1 identifier prerequisite: Effective EPCIS use requires properly assigned GS1 Company Prefixes and serialised GTINs . Organisations without GS1 membership must obtain these before they can generate valid EPCIS events.

Common applications

• Pharmaceutical serialisation: Item-level track-and-trace from manufacturer to pharmacy, satisfying DSCSA and FMD requirements. Each saleable unit carries a serialised GTIN; EPCIS events record every custody transfer.
• Food traceability: Lot-level and item-level traceability for fresh produce, seafood, and dairy under FSMA 204 and retailer mandates. Enables rapid recall isolation - identifying exactly which stores received affected product within hours rather than days.
• Retail supply chain: Retailers such as Target and Walmart require RFID-enabled suppliers to provide EPCIS advance ship notices (ASNs) and receiving confirmations, enabling automated inventory reconciliation at the DC and store level.
• Customs and border control: Some customs authorities accept EPCIS event data as supporting documentation for import/export declarations, linking physical shipments to their complete chain of custody records.
• Cold chain monitoring: EPCIS extension fields (user extensions or ILMD - Instance/Lot Master Data) carry temperature and humidity readings alongside standard event data, providing combined custody and condition records for temperature-sensitive goods.

Related standards and protocols

Related