EPCIS 2.0 expands the food event model beyond location and custody
GS1's current standard supports sensor, certification, and measured-concentration context, raising stronger questions about units, source quality, and the boundary between an event and a safety conclusion.
Editorial figure by Food Traceability Ledger. Source context: GS1.
More expressive data create more governance work
A temperature, concentration, certification, or condition value gains meaning from the instrument, method, unit, calibration, sample, location, time, product, lot, threshold, and decision context around it. Carrying the value in a standardized event can improve exchange but also make an unqualified number look more authoritative when it reaches a dashboard or downstream partner.
Implementations should retain the original measurement and provenance, identify any transformations, and separate observed data from a disposition or food-safety conclusion. A system may alert that a temperature exceeded a configured threshold without determining whether the food is unsafe. That decision can depend on product, duration, process, packaging, evidence, and qualified review.
The buyer test is semantic continuity
Ask two systems to exchange an event containing a product, lot, location, time zone, business step, disposition, sensor report, and later correction. Then compare what each user sees, what can be queried, which values remain typed and unit-aware, and whether the correction preserves the earlier event. Successful transport is not sufficient if semantic meaning changes.
Food Traceability Ledger will classify documented EPCIS support separately from independently observed interoperability. Provider pages should name the evidence and version where available and mark what is not established. Buyers should also maintain a fallback for partners and authority responses that use other formats.
Enterprise buyer test
Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.
A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.
What we will watch next
Food Traceability Ledger will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.