> ## Documentation Index > Fetch the complete documentation index at: https://docs.closient.com/llms.txt > Use this file to discover all available pages before exploring further. # EPCIS 2.0 Conformance > The roles, binding, and industry profiles Closient's EPCIS 2.0 implementation claims — and states plainly which it does not. EPCIS is a large standard covering warehouse logistics, environmental telemetry, asset pairing, and business-document exchange. Closient implements the part that answers two questions: **where did this lot go, and what else is affected.** The rest we have deliberately not built, and this page says which is which. ## The role we claim EPCIS 2.0 has no compliance levels or certification badge. Conformance is claimed per role, and an implementation is judged only on the roles it names. | Role | Status | Notes | | --------------------------------------- | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | EPCIS 2.0 capture interface server | **Claimed** | Documents arrive, are validated, and become a queryable traceability record. | | EPCIS 2.0 data | **Claimed** | 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**. ## What we support * **Supported** — built, and exercised by our conformance suite. * **Stored, not interpreted** — we keep your data faithfully; we do not act on it. * **By design** — a product decision, not on the roadmap. * **Not built** — a real gap in a role we claim, being closed. ### Capture | Capability | Status | Notes | | ------------------------------------------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Asynchronous capture with a pollable job | Supported | 202 plus a Location header; per-event errors name which events failed by index. | | All-or-nothing capture | Supported | The default — a traceability ledger should not absorb half a shipment. proceed is available when you want it. | | ObjectEvent, AggregationEvent, TransformationEvent | Supported | TransformationEvent is how one raw lot becomes many finished products, and how a recall is scoped to those rather than the whole line. | | TransactionEvent, AssociationEvent | Supported | Accepted and stored so your record is complete; no workflow is built on them. | | Lot attributes (ILMD) — harvest dates, growing area, expiry | Supported | | | Validation — malformed documents rejected | Supported | 58 of 58 corpus documents (valid and deliberately invalid) handled correctly, 0 wrongly accepted (C-5411). | | Capability discovery (OPTIONS) and the full GS1-\* header set | Supported | 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). | ### Traceability | Capability | Status | Notes | | --------------------------------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------ | | Recall blast radius — what else is affected | Supported | Walks transformations forward from a lot to every finished product carrying it. | | FSMA 204 Critical Tracking Events | Supported | Harvest, cooling, initial pack, ship, receive, land receive — derived automatically from captured events (C-2474). | | FDA export, and historical "what was on file as of" | Supported | | ### Sensor and environmental data | Capability | Status | Notes | | ------------------------------------------------------- | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | | Sensor readings on events (sensorElementList) | Stored, not interpreted | Captured and returned verbatim. We do not evaluate thresholds, raise excursion alerts, or monitor cold chain. | | Cold-chain excursion alerting, environmental monitoring | By design | 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. | ### Interchange | Capability | Status | Notes | | --------------------------------------------- | --------- | ---------------------------------------------------------------------------------------------------------------------------------------- | | JSON and JSON-LD | Supported | | | XML, EPCIS 1.2, and older interchange formats | By design | 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. | ### Federation | Capability | Status | Notes | | --------------------------------------------------- | --------- | ----------------------------------------------------------------------------------------------------------------------------------- | | Named queries, standing queries, subscriptions | By design | Genuinely valuable and genuinely unbuilt — every read today is scoped to the organization that captured the events (C-5416). | | Cross-party event deduplication (GS1 event Hash-ID) | By design | Duplicate detection today is a Closient-internal fingerprint and will not match a hash computed by another implementation (C-5414). | ## Industry profiles | Profile | Position | | -------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | | 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. | Nothing on our site, in our docs, or in a sales conversation implies DSCSA/Rx or GDST readiness until those rows change. ## How we know * **6 of 63** official EPCIS 2.0 REST operations served (5 of 29 paths), all within the roles claimed above. * **58 of 58** real EPCIS documents from an independent conformance corpus handled correctly (0 wrongly accepted, 0 server errors). * Measured against the GS1 EPCIS 2.0 REST binding and an independent 138-document conformance corpus, both checked in CI on every build. **Why we publish the gaps.** A claim is only worth something if it survives being checked, and the fastest way to find out whether we are honest is to look at what we admit when nobody is forcing us to.