EPCIS 2.0 Events

EPCIS 2.0 is a major update that introduces many new features to lower barriers to adoption and better enable data sharing across the entire supply chain:

• Native JSON/JSON-LD support (in addition to XML) for REST-based APIs
• A REST API definition (OpenAPI 3.0) alongside the legacy SOAP/AS2 bindings
• The new AssociationEvent event type, to capture associations between objects
• The sensorElementList element, to support sensor data to track asset conditions and for use in industrial IoT processes
• The errorDeclaration mechanism, formalized for event correction workflows
• The persistentDisposition element, for dispositions that persist across events

Document envelope

All EPCIS 2.0 events are transmitted inside an EPCISDocument. The JSON-LD format requires an @context:

{ // JSON-LD context: always include the EPCIS 2.0 context URL. // Additional context entries declare extension namespaces. "@context": "https://ref.gs1.org/standards/epcis/2.0.0/epcis-context.jsonld", // Document type: always "EPCISDocument" for capture payloads "type": "EPCISDocument", // EPCIS schema version "schemaVersion": "2.0", // Timestamp at which this document was created (ISO 8601) "creationDate": "2026-06-12T10:15:30.000Z", // The event payload: a list of one or more EPCIS events "epcisBody": { "eventList": [ // ... events go here ... ] } } 

Identifier formats

EPCIS 2.0 accepts identifiers as either EPC URIs or GS1 Digital Link URIs:

Class-level vs. instance-level identification

• Serialized instance-level objects are listed in the epcList, childEPCs, inputEPCList, and outputEPCList elements.
• Lot- or quantity-based class-level objects are listed in the quantityList, childQuantityList, inputQuantityList, outputQuantityList elements, using QuantityElement structures:
  
  JSON

  { // Class-level identifier (typically an LGTIN for lot-managed product) "epcClass": "urn:epc:class:lgtin:4012345.012345.LOT2026A", // Numeric amount of the class-level object "quantity": 200.0, // Unit of measure per UN/CEFACT Rec 20 (e.g., KGM = kilogram). Omit for counts of base items. "uom": "KGM" }

Common event fields

The following fields are shared by all EPCIS 2.0 event types: