The scoping question a Director of Fresh actually asks is not "what does the rule say" — it is "which of the things I sell does this bite, and how much of my fresh program is in scope." The honest answer for a grocer: the covered categories land squarely on the perimeter of the store — the fresh and prepared departments that already generate the most shrink, the most customer complaints, and the most investigations. Which is the tell that getting the record right here pays operationally long before any deadline is in view.

What the Food Traceability List actually covers

FSMA 204 does not cover your whole assortment. It covers foods on the Food Traceability List (FTL), published by FDA under the FSMA 204 rule. The categories that bite a grocery perimeter, in plain terms:

  • Fresh leafy greens and fresh-cut leafy greens — the bagged salads, spring mix, romaine, the category with the longest recall history.
  • Fresh herbs, fresh cucumbers, fresh tomatoes, peppers, sprouts, melons (cantaloupe), and tropical tree fruits.
  • Shell eggs.
  • Nut butters.
  • Cheeses (certain soft/semi-soft and fresh soft cheeses).
  • Fresh finfish, smoked finfish, crustaceans, and molluscan shellfish — much of your seafood case.
  • Ready-to-eat deli salads.

Two scoping facts that change how much of your operation is in play:

  1. "Contains a listed food as an ingredient" pulls prepared items in. A made-in-store deli salad or a prepared item built on a listed food inherits the obligation. For a grocer with a real prepared-foods program, the FTL reaches past the produce cooler into the kitchen.
  2. The list is versioned and can change. FDA maintains the FTL and can revise it. Scope to the current list, but build the record layer so adding a category later is a configuration change, not a new project.

What "covered" actually requires of you at receiving

For a covered food, receiving is a Critical Tracking Event, and the rule names the Key Data Elements you have to keep and be able to produce in a sortable electronic form:

  • the traceability lot code (the identifier that makes a lot-level withdrawal possible instead of a category-wide dump),
  • the product identifier and description,
  • the quantity and unit of measure,
  • the location that shipped it and the location that received it,
  • the date of receipt (and, for a transformation, the date and the new lot linkage).

The value of holding those elements electronically is not the audit. It is that a lot code plus a record with a witness turns "recall everything that looks like this" into "withdraw exactly this lot, and know who received it" — narrower shrink, faster resolution, fewer good cases in the dumpster.

The date, read honestly — do not let anyone sell you the deadline

You will be pitched the FSMA 204 date as your urgency. Here is the read that survives a search, so nobody sells you a moved clock as a fixed one:

  • The original compliance date was January 20, 2026.
  • FDA proposed to extend it to July 20, 2028 — a roughly 30-month slip.
  • That extension was never finalized as a rule. It rests on the Continuing Appropriations Act of 2026 directing FDA not to enforce, not on a completed rulemaking.
  • FDA is actively soliciting further flexibilities — a public meeting and request for comments on lot-level traceability challenges was noticed in the Federal Register on 2026-05-28.

Treat July 2028 as a floor that de-risks the investment, not a gun to the head. The right reason to fix your fresh receiving record is that it tightens the perimeter departments that already cost you the most — the deadline is the safety net under a decision that pays for itself, never the headline. If a vendor leads with the FSMA date as your urgency, that is the tell they are selling fear instead of a return.

What ships today

Plainly: the strict-conformance capture spine — official-schema validation, an append-only record, a performer (who) stamped at the dock — passes 683/683 conformance tests, and its stateless doors are live: POST https://epcis.dev/translate, /validate and /hash. No conformance attestation has ever been issued, and none is claimed. The FTL-scoped receiving product is a named entry in the open P0 ledger — a build task with an owner, not a live demo. Read this article for the scoping.

The move

Scope your FTL exposure to the perimeter and the prepared-foods kitchen, hold the receiving KDEs electronically for a lot-level withdrawal, and treat the 2028 date as the floor under an operating return. The full two-clock read for the store — the lane and the dock in one refresh — is the parent: GS1 Sunrise 2027 and FSMA 204 for grocery.

Your capture workspace is provisioned from the seat list, in order — one email when your seat is ready, and the only thing to leave is an address:

→ Put me on the seat list — pick Retailer or point of sale, the segment that receives the covered load.