The deadline is not the argument.

Somewhere in your inbox is a vendor deck with a countdown clock on slide two. This post is the search result that beats it. The FSMA 204 compliance date has already moved roughly thirty months, the move was never even finalized as a rule, and FDA is actively asking industry what else to loosen. Any architecture pitched on deadline panic is falsifiable in one search — so here is the record, sourced, followed by the case for doing the work anyway. The second part is the one your steering committee should fund.

The date record, checkable

• The original compliance date was January 20, 2026 — set in the final traceability rule.
• FDA proposed moving it to July 20, 2028 in a proposed rule published August 7, 2025 — Federal Register 2025-14967 — a roughly 30-month slip.
• That extension was never finalized as a rule. The operative protection is the Continuing Appropriations Act of 2026 directing FDA not to enforce before the extended date — an appropriations rider, not a completed rulemaking.
• FDA is soliciting further flexibilities. A public meeting and request for comments on lot-level traceability challenges was noticed in the Federal Register on May 28, 2026 — "Challenges and Solutions in Lot-Level Food Traceability."

Direction of travel: softening. Not repealed, not dead — softening. The honest planning posture is July 2028 as a floor that de-risks the investment, with the possibility it moves again priced in.

Grade your vendors with this list

A GS1- and FDA-literate reviewer will catch each of these in a pitch. Use the list on everyone, including us:

1. "The deadline is January 2026." Superseded a year ago; anyone still saying it has not read their own regulatory slide.
2. "July 2028 is final." It is not finalized as a rule; it rests on an appropriations act. The nuance cuts both ways and an honest vendor states it.
3. "FDA is holding firm." FDA noticed a public meeting soliciting flexibilities in May 2026. Holding firm is not what that is.
4. "You must buy now to make the date." With a 2028 floor and softening direction, urgency pricing is a sales posture, not a regulatory fact.
5. "Compliance requires our platform." The rule requires records and 24-hour retrievability. The records are an event schema; no named product appears anywhere in it.

A vendor who gets the date wrong is telling you how they handle every other checkable fact — schema versions, conformance claims, what their validator actually pins.

The case that survives any date

Here is the uncomfortable symmetry: if the deadline were the only reason to build traceability records, the honest date record would kill the project. So build on the reasons that hold at any date:

The maintenance tax is real and runs now. Every quarter your team maintains a home-grown event model — hand-rolled schemas, side-table lot codes, per-partner reconciliation glue — you pay engineers to re-implement a layer GS1 already standardized. That cost is independent of FDA entirely.

Record quality pays operationally. Lot-grain records with one TLC home turn "recall everything that looks like this" into "withdraw exactly this lot and know who received it." Receiving diffs catch shorts and substituted lots the week they happen, not at year-end. A trace query answering in one call is a mock-recall exercise that takes a coffee break. These returns arrive whether or not an inspector ever asks.

A team that builds for the honest date builds better. Deadline-driven scope produces a demo: the checklist fields, a report generator, a prayer. Floor-driven scope produces correctness: conformant events validated against the pinned official schema, computed identity, append-only records. When the date does arrive — 2028 or otherwise — the compliance artifact is a query over records you were already using to run receiving. The deadline becomes the safety net under a decision that paid for itself, never the headline.

What is worth doing now, regardless

Three moves, none of which are wasted in any regulatory future: capture conformant records — events that validate against GS1's own schema, so the record outlives every vendor decision including ours; compute identity from content — CBV §8.9 hashes, so two parties agree on what an event is with no coordination; and hold lot discipline — one TLC, stamped at birth, referenced everywhere.

The technical series works each piece: the CTE/KDE mapping, the traceability lot code, and the one-call trace. The same argument in the executive register — for the person who owns the steering committee, not the sprint — is at visibility.cloud.

Every fixture in the series validates today with npx epcis.dev validate — no account, no meeting, exit code is the answer. That is the vendor-evaluation standard this post is arguing for. Hold us to it first.