Know What Happened.
At Every Step.
EPCIS 2.0 gives you event-based supply chain visibility. Capture, share, and query what happened to your products — from manufacturing to shelf.
Supply chains are opaque.
They don't have to be.
Regulators, retailers, and consumers demand to know where products have been and what happened along the way. EPCIS 2.0 is the global standard for answering those questions.
Traceability is no longer optional
FSMA 204 and EU Digital Product Passport mandate event-level traceability for food, pharma, and consumer goods.
Trading partners need interoperability
EPCIS is the lingua franca of supply chain events. Speak the same language as your suppliers and retailers.
Visibility drives efficiency
Pinpoint delays, prevent counterfeiting, and respond to recalls in hours instead of weeks.
What
Which products or assets were involved?
When
Exact timestamp of the event.
Where
Physical or digital location.
Why
Business context and reason.
How It Works
Four steps to full supply chain visibility.
Capture
Record supply chain events via our REST API or integrations. Every scan, shipment, and transformation becomes a structured EPCIS event.
Store
Events are validated against GS1 CBV vocabulary and persisted in a queryable repository with full audit trail.
Query
Ask questions about your supply chain: Where is this batch? What happened to this shipment? Who handled this product?
Share
Exchange event data with trading partners, regulators, and auditors using the standard EPCIS 2.0 REST interface.
Built for Compliance
Meet current and upcoming regulatory requirements with standards-based traceability data.
FSMA 204
FDA's Food Traceability Rule requires Key Data Elements for foods on the Food Traceability List. EPCIS events map directly to FSMA 204 Critical Tracking Events.
EU Digital Product Passport
The EU DPP requires lifecycle data for products sold in Europe. EPCIS provides the event data layer that DPP declarations rely on.
GS1 EPCIS Conformance
We claim the EPCIS 2.0 capture interface server and data roles — see exactly what's supported, by design, or not yet built below. Your data is portable and interoperable via the same standard REST binding. See details
What We Actually Support
EPCIS 2.0 has no compliance levels or certification badge. Conformance is claimed per role, and we only claim the roles we've built.
Roles
-
EPCIS 2.0 capture interface server
Documents arrive, are validated, and become a queryable traceability record. -
EPCIS 2.0 data
Events we emit validate against the standard's schema. -
EPCIS 2.0 query interface server (not claimed)
We serve a convenience read over your own events, not the standard's query interface — no named queries, no cross-organization access, no subscriptions. Traceability answers come from purpose-built endpoints, not a general query surface. -
Query callback interface implementation (not claimed)
Subscriptions are deliberately out of scope — see the federation row below, not accidentally missing.
Binding: REST over HTTPS. Serialization: JSON and JSON-LD. Vocabulary: GS1 CBV 2.0.
Industry Profiles
-
FSMA 204
Supported — CTE materialisation and ILMD KDE mapping shipped (C-2474).
-
DSCSA / Rx
No claim. C-1390 is unstarted; the bar is the GS1 US Rx EPCIS Conformance Testing Program via Drummond Group, which we have not been through.
-
GDST (seafood)
No claim.
Capture
-
Asynchronous capture with a pollable job
202 plus a Location header; per-event errors name which events failed by index. Supported -
All-or-nothing capture
The default — a traceability ledger should not absorb half a shipment. proceed is available when you want it. Supported -
ObjectEvent, AggregationEvent, TransformationEvent
TransformationEvent is how one raw lot becomes many finished products, and how a recall is scoped to those rather than the whole line. Supported -
TransactionEvent, AssociationEvent
Accepted and stored so your record is complete; no workflow is built on them. Supported - Lot attributes (ILMD) — harvest dates, growing area, expiry Supported
-
Validation — malformed documents rejected
58 of 58 corpus documents (valid and deliberately invalid) handled correctly, 0 wrongly accepted (C-5411). Supported -
Capability discovery (OPTIONS) and the full GS1-* header set
All 6 resources we answer OPTIONS on carry an accurate Allow header; every response, errors included, carries the 8-header GS1 set (C-5427). Count reads from the C-5427 registry rather than being retyped, so it can't drift the way the header count itself once did (C-5401's '2 of ~12' finding). Supported
Traceability
-
Recall blast radius — what else is affected
Walks transformations forward from a lot to every finished product carrying it. Supported -
FSMA 204 Critical Tracking Events
Harvest, cooling, initial pack, ship, receive, land receive — derived automatically from captured events (C-2474). Supported - FDA export, and historical "what was on file as of" Supported
Sensor and environmental data
-
Sensor readings on events (sensorElementList)
Captured and returned verbatim. We do not evaluate thresholds, raise excursion alerts, or monitor cold chain. Stored, not interpreted -
Cold-chain excursion alerting, environmental monitoring
A shipment that ran warm is a logistics problem. We are here for the product-quality consequence — a cooling CTE or a recall — not a temperature feed. By design
Interchange
- JSON and JSON-LD Supported
-
XML, EPCIS 1.2, and older interchange formats
EPCIS 2.0 is the JSON release and the REST binding defines JSON request bodies. We are not building a bridge to the previous generation. By design
Federation
-
Named queries, standing queries, subscriptions
Genuinely valuable and genuinely unbuilt — every read today is scoped to the organization that captured the events (C-5416). By design -
Cross-party event deduplication (GS1 event Hash-ID)
Duplicate detection today is a Closient-internal fingerprint and will not match a hash computed by another implementation (C-5414). By design
6 of 63 official EPCIS 2.0 REST operations served · 58 of 58 conformance corpus documents handled correctly · Full conformance declaration
API-First.
Standards-Based.
Built on the GS1 EPCIS 2.0 REST binding with JSON-LD payloads. No proprietary lock-in — your data speaks the global standard.
Read the DocsREST API
Standard EPCIS 2.0 REST binding. Capture and query events with simple HTTP calls.
JSON-LD
Linked data format with GS1 context. Machine-readable and semantically rich.
GS1 CBV 2.0
Core Business Vocabulary support for standardized business steps, dispositions, and source/destination types.
All Event Types
ObjectEvent, AggregationEvent, TransactionEvent, TransformationEvent, and AssociationEvent.
SOC 2 Type II
Enterprise-grade security and compliance controls.
99.9% Uptime
Built on AWS with multi-AZ redundancy.
API Key Auth
Scoped API keys with rate limiting and audit logging.
No Lock-In
Standard EPCIS format. Export your data anytime.
Learn the Standards
Understand the technology behind supply chain visibility.
Ready to Trace Your Supply Chain?
Get started with EPCIS 2.0 event capture on Closient — API-first, and built for scale.