FSMA 204 (21 CFR 1, Subpart S): KDEs at CTEs, sortable records in 24 hours, compliance 20 Jul 2028 · no carrier mandated · GS1-128 and 2D codes are the industry baseline.
FSMA 204 is a data regulation: Key Data Elements captured at Critical Tracking Events, produced to FDA as a sortable spreadsheet within 24 hours. It never tells you how to mark a case. That silence is where the real operating decision lives — because the cost of compliance is the cost of capture, and capture cost is set by the carrier. Printed GS1 codes are the baseline; RFID changes the economics wherever goods move faster than people can aim a scanner.
A single-dock operation receiving dozens of cases an hour can meet FSMA 204 with printed GS1 labels and disciplined scanning. The data model matters more than the carrier — get lot-linkage right first.
Pallets through a dock door, mixed cases in a cooler, product moving at line speed: RFID captures the same KDEs without line of sight, in bulk, automatically — turning the 24-hour FDA request from a fire drill into an export.
| Criterion | QR / printed 2D code | NFC chip (Aeroz) |
|---|---|---|
| Satisfies FSMA 204 | Yes — with disciplined manual capture | Yes — capture is automatic at the read point |
| Scan labor per pallet | Every case aimed and scanned by hand | Portal read on the move, all cases at once |
| Cold, wet, frost conditions | Labels fog, freeze, tear; scans fail | Reads through frost and packaging |
| Transformation events (mixing, portioning) | Manual association, highest error step | Input units read in bulk at the kettle or line |
| 24-hour FDA response | Depends on every scan having happened | Query the event log; gaps visible before FDA asks |
| Cost per case | Printing cost | Cents — recovered where scan labor and recall scope shrink |
Recalls are where the difference is measured in money: with precise unit- and case-level custody data, a recall scopes to the affected lots actually shipped — not to everything that might have been. One over-broad recall commonly costs more than tagging years of production.
KDEs captured at each CTE for Food Traceability List items, traceability lot codes linking inputs to outputs, records sortable and electronic, produced to FDA within 24 hours of request. Compliance date: 20 July 2028.
FDA does not require barcodes, RFID or any marking technology — it requires the data. Industry practice standardises on GS1 identifiers; how they are carried and captured is your operating decision.
Major retail and foodservice buyers are pushing traceability data requirements upstream in supplier agreements — several with RFID case-tagging programs already running. Your carrier decision may arrive in a vendor manual before it arrives from FDA.
RTE and multi-ingredient foods must link every input lot to the output lot. This join is where paper systems break — and where automated capture at the point of transformation earns its keep.
No. It requires Key Data Elements at Critical Tracking Events and 24-hour electronic production of records. Any carrier that gets accurate data captured qualifies — the question is at what labor cost and error rate.
For low-velocity operations with disciplined scanning, yes. The failure mode is volume: every missed scan is a hole in the record FDA asks for, and holes are found during investigations, not audits.
Dock doors, coolers, and transformation steps — anywhere goods move in bulk or conditions defeat handheld scanning. And in recall scope: precise custody data shrinks recalls to what actually shipped.
That is NFC's lane: a tap on retail packaging can open provenance, freshness and recall status for the shopper — a different job from the case-and-pallet logistics RFID handles, on the same identity backbone.
A fixed-fee Aeroz audit maps your products, line speed and regulation against both carriers and returns a written recommendation with a scoped pilot plan, cost and timeline. $5,000 books it online; no commitment to proceed.