Foodservice & QSR.
The case arrived. The record can't say who received it. Your mock recall already knows: the trace-back crosses a franchise boundary where the data is contractually someone else's, and the record shows a case arrived at a DC — never who received it.
Verified 31 July 2026. The spine behind this page passes 683/683 conformance tests against GS1's normative artefacts, and its translate, validate and hash doors are live at epcis.dev. Every open gap is a named entry in the open P0 ledger; the dated summary is at What ships today.
This segment already funds capture at production scale when someone brings the data layer. The largest public RFID rollout in food service runs across roughly 3,200 US restaurants and hundreds of product categories — and it is the deploying software vendor's own president, a third party, who attributes it to FSMA 204's compliance requirements; a comparable programme in China reported around +30% receiving and inventory efficiency. That is the ROI shape to lead with. The 2028 enforcement floor is a de-risking date you beat early, never the reason to move — the rule's own record is softening, and anyone selling you the deadline is one search away from being caught.
The receiving scan at the store back door is the sharp case: a crew member on a handheld, a case recorded, and — in the standard as written — no field for the performer: the Who stops at the company's GLN. EPCIS 2.0 defines five event dimensions and no performer, so across a franchise boundary the gap is structural, not a data-quality project. The spine records the attested observer on every event, distinct from the account that warrants the capture. And the timing is external: your suppliers are re-marking on GS1's Sunrise 2027 schedule anyway, which makes 2026–27 the cheapest window in a decade to change what receiving captures.
The receiving run, worked: tunnel to back door, and the one hop the standard cannot narrate.
case urn:epc:id:sgtin:0614141.107346.2017lot 7A-4412recordTime stamped by the gateway
-
06:04
observing — the DC tunnel reader, at line speed
The observer is the tunnel itself — an embodied agent, attested like anyone else. who: thing · tunnel-2 (id.org.ai) · capturedBy: distributor acct
-
06:12
receiving — the store back door, a crew member on a handheld
Today’s standard records the company; this record also names the worker doing the task. who: human · crew (handheld) · capturedBy: operator acct
-
—
the same event, in the standard’s own projection
Validates against the pinned official schema and says: a company received a case. Five dimensions, no performer — the gap is structural, and across a franchise boundary it is the whole trace-back. The party at every hop is derived at read time from grant chains, never stamped.
See your first trace.
Capture workspaces for restaurant operators and their distributors are provisioned from the seat list, in order — one email when your seat is ready.
We answer in writing. We take at most five conversations a month, only when you ask for one, and only after you already have the written read.