What.
The What is the objects the event observed, carried as an epcList of instance identifiers or a quantityList of classes.
EPCIS 2.0 identifies objects with GS1 Digital Link: a GTIN with a serial for an instance, an SSCC for a logistic unit, a GIAI for an asset. The gateway normalises those identifiers when it computes the standard event hash, so the same object referenced two ways hashes the same.
The pages below are the object classes the old tree carried. They describe how the standard names each class; the hosted resolution of an identifier to a party is future tense, because nothing resolves a GS1 Digital Link to a party today.
epcListquantityList
Build state, 29 July 2026. The capture gateway is written and passing its conformance tests; nothing is hosted yet. The dated ledger is What ships today.
What, page by page.
-
01
Products
A product instance is a GTIN plus a serial; a product class is a GTIN. EPCIS 2.0 carries the first in the epcList and the second in the quantityList. The gateway validates the shape and normalises the Digital Link before it hashes the event.
-
02
Packages
A package is a packaged unit identified for tracking. Aggregation events record what was packed into what; the gateway stamps and appends the association without letting the sender assert the observer or the record time.
-
03
Assets
Returnable and fixed assets are identified by GIAI or GRAI. EPCIS 2.0 tracks their movement and status through object and transaction events, each validated against GS1's schema on capture.
-
04
Pallets
A pallet is a logistic unit with an SSCC. Aggregation events bind the cases on it; a later disaggregation records the split. Append-only storage keeps both, so the unit's history is the sequence of events, not a mutable current state.
-
05
Containers
A container is a logistic unit at the transport grain, identified by SSCC. Its events record loading, transport and unloading steps with CBV dispositions, stamped and hashed by the standard at the door.
-
06
Shipments
A shipment aggregates logistic units under a business transaction. EPCIS 2.0 links the objects to the transaction identifiers; the gateway records the association and stamps who captured it.
-
07
Services
Not every observation is a physical object: a service or a business transaction can be the subject of a transaction event. EPCIS 2.0 models it with the same envelope, and the gateway applies the same laws. A hosted service catalogue is future tense; the interface that accepts these events is written and runs locally.