For the VP of supply chain and distribution at a multi-unit QSR — the seat with an RFID rollout funded or in flight, measured on receiving labor and inventory accuracy, and an unanswered question about where the data lives.

Let's say the honest thing first, because your vendors will not: Sunrise 2027 is not aimed at you. It is GS1's programme for retail point-of-sale — lanes reading 2D marks by end of December 2027 — and you do not run lanes. No Sunrise deck should ever be pointed at a QSR, and when one is, you have learned something about the vendor.

What is aimed at you is a side effect, and it is worth more than the programme itself: your suppliers sell to grocers too, and they are re-marking cases and upgrading identification on the Sunrise timeline whether you participate or not. Richer case marks, RFID programmes justified across their whole book of business, encoding decisions being made this artwork cycle and next. That wave has a property your capital committee should hear precisely: it collapses the marginal cost of fixing receiving capture — and it is moving through 2026 and 2027, which makes right now the cheapest moment in roughly a decade to change what your DCs and restaurants capture at the door. This is a timing argument, not a compliance argument. It would be true if FSMA 204 did not exist.

Why marginal capture cost collapses during a re-marking wave

Receiving capture has always had two cost components: what you deploy (readers, handhelds, software, process) and what your suppliers put on the case (the mark or tag your deployment reads). The second component is the historical killer — asking suppliers to re-mark cases for one customer's programme means funding their line changes, their label stock, their exception handling, per supplier, forever. Programmes die on that line item.

During the wave, that line item goes to approximately zero, because the supplier is re-marking anyway — for the grocery half of their book, for their own regulated marking, for programmes like the one in the public record below. Your ask stops being "change your line for us" and becomes "since you are already changing your line, here is the encoding that also serves your QSR customers." Same conversation, different decade of cost. The KDE-gap measurement your food-safety colleagues run — which lots, which identifiers, which data each supplier can actually emit — is cheapest during exactly this window too, for the same reason: you are measuring a wave in motion instead of commissioning one.

What the public record shows a QSR does with this window

The evidence here is deliberately narrow — one citable artifact, quoted to its exact scope. RFID Journal, December 19, 2023: Chipotle and its suppliers partnered to roll out RFID nationwide — approximately 3,200 US restaurants, roughly 330 product categories, expanding to 19 distribution centers, with the vendors named (Mojix software, Zebra handheld readers, Avery Dennison Smartrac tags). Mojix's president, on the record, attributed the programme to "the compliance requirements of FSMA 204."

Read what that artifact actually supports, no more: a national QSR will fund receiving-capture change at full scale when supplier tagging and a deadline make the economics line up — and it is a third party, not us, carrying the regulation-to-spend causal claim. It does not say Chipotle's numbers transfer to you, and we will not borrow their scale to imply yours. But the structural lesson travels: Chipotle rode a wave — suppliers tagging at source, cases arriving pre-identified — rather than fighting one, and riding is the only version of this programme whose supplier line item stays near zero. The cost and ROI shape of a chain-wide programme is its own read, including the receiving-efficiency evidence from the wider public record, each artifact quoted to its scope.

The DC expansion moment

If your network is adding or re-platforming DCs — and the growth curve of most fast-casual chains says some part of it is — the insertion point is already on your calendar. A DC being commissioned gets its receiving process designed once; capture at the dock door costs design intent there, versus retrofit cost everywhere else. The wrong sequencing is finishing the DC build this year and starting the capture conversation next year against the same walls. The window argument and the expansion argument compound: new dock, suppliers re-marking, one design decision.

And the question that decides whether any of it accrues value: where does what the dock reads live? A read that lands in a WMS field answers today's putaway and is gone as evidence. A read that lands in an event record — a conformant EPCIS 2.0 event with an attested who on the receiving scan, the observer distinct from the account that warrants the capture — is the record your food-safety team runs the next mock recall against, and the record a regulator-ready trace is computed from. Same hardware, same beep; the difference is entirely in the destination, which is the layer this platform is: every capture validated against the official GS1 EPCIS 2.0 schema, every open gap named in the open P0 ledger.

What to put in supplier agreements this cycle

The window is only cheap if you are specific while it is open. Four clauses, in supplier-agreement language, each one a question this quarter and a scorecard line next year:

  1. Case-mark encoding: which identifiers travel on the case — GTIN, lot, pack or production date — and in which carrier (2D mark, RAIN RFID, both).
  2. Timeline: when each category's re-marked cases start arriving, so your capture rollout waves match their marking waves.
  3. Data emission: whether the supplier can emit shipment-level events or ASNs that join to what your dock reads — the paperwork context that makes a received case reconcile itself against what was claimed to have shipped.
  4. Verification: a sample-and-check right, so "we encode lot on every case" is a measured rate, not a sentence in a deck.

Six quarters of wave remain. The read for your network — where your suppliers are on it, what your next DC should capture, and where the record lives — starts at get started: your address first under the one-message promise, then questions that branch on your answers, ending in a written read that locks when it ends.