EPCIS (Electronic Product Code Information Services) models the supply chain as a stream of events, each answering four dimensions: what object, when it happened, where it was, and the business step or disposition (the why). Version 2.0, ratified by GS1 in 2022, adds native JSON / JSON-LD bindings and a REST API, so events are web-friendly rather than locked in XML.
For a Digital Product Passport this is the traceability backbone: rather than asserting a flat claim like "made in the EU", a passport can reference the actual chain of EPCIS events — manufacture, packing, shipping, repair, recycling — that a market-surveillance authority or recycler can verify. TracePass can export passport lifecycle data as EPCIS 2.0 events.
Frequently asked
What do the four EPCIS dimensions mean?
Every EPCIS event captures what (the object or EPC), when (the timestamp), where (the location), and why (the business step and disposition, such as shipping or receiving). Together they let any reader reconstruct what happened to a product without a shared private database.
How is EPCIS 2.0 different from version 1.2?
EPCIS 2.0, ratified by GS1 in 2022, adds JSON and JSON-LD serialisations and a standard REST API alongside the original XML — making events natively web- and Linked-Data-friendly. That is what makes it a natural fit for a JSON-LD Digital Product Passport.