EPCIS 2.0 event capture
Record what happened to your products, from manufacturing to shelf, as standard EPCIS 2.0 events.
What EPCIS is for
EPCIS 2.0 is the GS1 standard for recording what happened to a product, where, when and why.
Food traceability
FSMA 204 requires traceability records for foods on the FDA's Food Traceability List.
Recall scope
Scope a recall to the finished products that carry an affected lot.
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
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 the GS1 CBV vocabulary and stored.
Trace
Read back your events and trace a lot forward to every finished product that carries it.
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
Materials, recyclability and environmental-impact fields sit on the product record, next to the EPCIS events for that product.
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.
-
DSCSA / Rx
No claim. 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. 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. Count reads from the capability registry rather than being retyped, so it can't drift. 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. 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. By design -
Cross-party event deduplication (GS1 event Hash-ID)
The standard event Hash-ID is stored for newly captured events whose @context it can resolve; events captured earlier have none until a backfill runs. Duplicate detection still uses a Closient-internal fingerprint scoped to one organization, and the Hash-ID is not yet queryable. By design
12 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
EPCIS 2.0 REST binding for event capture, in JSON and JSON-LD.
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.
API Key Auth
Scoped API keys with rate limiting.
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?
Capture your first event. The quickstart is at docs.closient.com.