Skip to main content
Closient implements EPCIS 2.0 (Electronic Product Code Information Services) per ISO/IEC 19987:2024 for capturing and querying supply chain visibility events. Events answer the four dimensions of supply chain visibility: What, When, Where, and Why.

Event Types

Event Structure

Every event has four dimensions:

What (Identifiers)

  • epcList — list of individual EPC/GTIN URIs involved
  • quantityList — class-level quantities (GTIN without serial, plus quantity and UOM)
  • parentID — container identifier for aggregation events
  • inputEPCList / outputEPCList — for transformation events

When (Time)

  • eventTime — when the event occurred (ISO 8601)
  • eventTimeZoneOffset — timezone offset (e.g., +05:30)
  • recordTime — when the system captured the event (set automatically)

Where (Location)

  • readPoint — GS1 Digital Link URI of the scan location
  • bizLocation — GS1 Digital Link URI of the business location

Why (Business Context)

  • bizStep — business step from CBV 2.0 vocabulary (40+ values)
  • disposition — object state after the event (20+ values)

Capturing Events

Events are deduplicated by SHA-256 hash. Submitting the same event twice returns the existing event without creating a duplicate.

Business Step Vocabulary (CBV 2.0)

Common business steps:

Disposition Vocabulary

Common dispositions:

Persistent Dispositions

EPCIS 2.0 introduces persistent dispositions — dispositions that remain in effect across events:
  • persistent_disposition_set — dispositions to add to the object’s persistent state
  • persistent_disposition_unset — dispositions to remove
This enables tracking long-lived states like certifications or regulatory holds that span multiple events.

Instance/Lot Master Data (ILMD)

The ilmd field carries master data that is defined at the instance or lot level at the time of creation:

FSMA 204 export text fields

The FSMA 204 exports (the FDA JSON records-request export and the Sortable Spreadsheet workbook) carry plain text in every free-text field. This holds even though the underlying value was typed as rich text.
  • Traceability Product Description is the product’s description as of the event, flattened to plain text: markup and script payloads are removed, and entities are decoded. It is not a byte-for-byte copy of the stored rich text. When a product has no description, the product name is used; when neither exists, the export falls back to the GTIN.
  • Workbook cells are always written as text. A value that begins with =, +, - or @ stays visible as written and is never evaluated as a spreadsheet formula.

Querying Events

See the EPCIS API reference for the full query interface including filtering by EPC, business step, disposition, location, and time range.