FSMA 204 is in effect. What US grocers and distributors actually need in place now.

Why the January 2026 deadline still matters, even if you already missed it

FSMA Section 204 — the FDA's Food Traceability Rule — went fully enforceable on January 20, 2026. Every business that manufactures, processes, packs, or holds a food on the Food Traceability List (FTL) was required to maintain Key Data Elements (KDEs) for each Critical Tracking Event (CTE), plus produce that data within 24 hours on FDA request.

Some operators beat the deadline. Many are still catching up. This post is the no-nonsense version of what compliance actually requires and what records, systems, and workflows you need in place right now if you haven't finished the work.

The short version of what Section 204 demands

There are seven Critical Tracking Events (CTEs) you need to capture:

• Harvesting — for raw agricultural commodities
• Cooling — for raw agricultural commodities
• Initial packing — for raw agricultural commodities
• First land-based receiving — for foods obtained from a fishing vessel
• Shipping
• Receiving
• Transformation — when you change the food (cutting, cooking, packaging)

For each CTE, you capture a specific set of Key Data Elements (KDEs). For receiving (the CTE most grocers care about), that's at minimum: the traceability lot code, the quantity, the product description, the location identifier of where you received it, the date, the reference document type and number, and the entity you received it from.

On FDA request, you must be able to produce this information in an electronic sortable spreadsheet within 24 hours.

What that means operationally for a grocer or distributor

Three practical implications:

You need to capture lot-level data at receiving. If your current process is "we write down the invoice number and call it a day," you're out of compliance for any FTL product. Each incoming lot of FTL product needs its traceability lot code (TLC) captured alongside the quantity and supplier.

You need to link lot-level data to sale / onward shipment. When a lot moves out — sold to a customer, transferred to another location, consumed in food preparation — that outgoing movement must be tied back to the incoming lot. Otherwise a recall notification hits and you can't tell FDA "this specific lot went to these specific buyers."

You need the records retrievable in a structured, sortable format within 24 hours. That's the compliance bar. A shoebox of receipts isn't acceptable. A spreadsheet might be, if you can structure it quickly on demand. A proper inventory system that already has traceability baked in is the path of least resistance.

What the FDA will actually do if you can't produce records

FDA enforcement for Section 204 isn't the "random raid" scenario. It's almost always triggered by:

• A recall of an FTL product (Listeria in deli meats, Salmonella in peanut butter, etc.)
• A foodborne illness outbreak being traced back to a distribution lot
• A routine FDA inspection that spot-checks a few SKUs

When any of those fires, FDA sends a records request. You have 24 hours. You produce the sortable spreadsheet showing:

• What lots you received of the affected product
• When you received them
• Who you received them from
• Where those lots went (sold, shipped, transformed, wasted)

If you produce it cleanly, the enforcement action usually ends there. If you can't produce it, you're looking at: warning letters, Form 483 observations, potential injunctions, civil penalties, and reputational damage that outlasts the enforcement action itself.

The six things your receiving workflow needs right now

• Capture the traceability lot code on every incoming FTL item, regardless of whether the supplier puts it on the invoice or not. If the supplier isn't putting it on the invoice, call them — under FSMA 204 they're required to pass it to you.
• Tie the TLC to the specific physical stock that entered your warehouse or store, not just to the invoice line. If the invoice line says "500 lbs of shredded lettuce lot A12345," the system needs to know that those 500 lbs are now in cooler C on shelf 3.
• Enforce lot-level picking and shipping on the outbound side. When a customer orders 50 lbs of shredded lettuce, the system should record which lot went into that customer's order.
• Maintain the structured data in a sortable electronic format. Excel is fine at small scale. At any meaningful volume you need a purpose-built inventory / WMS system.
• Retain records for two years after the KDE was created.
• Be able to produce the sortable spreadsheet within 24 hours of a request. Test this. Pick a random lot you received 8 months ago and see how long it takes you to produce its full chain of custody. If it's longer than an hour, something in your workflow needs to be fixed.

Where OCR and auto-GRN fit in

The quiet reality of FSMA 204 compliance is that the audit-producing system and the daily-operations system need to be the same system. If receiving clerks are capturing data on a clipboard and someone later re-keys it into a tracking spreadsheet, two things go wrong: (1) errors creep in, (2) the full chain never exists in one place.

Invoice OCR solves this at the receiving step. You photograph the supplier invoice, every line including the traceability lot code is captured, and the incoming lot is recorded in the inventory system in the same action that you physically accept delivery. No re-keying, no parallel spreadsheet, no gap between the physical fact and the digital record.

See ShelfLifePro's Global Invoice OCR capability — it's purpose-built for exactly this kind of multi-field receiving workflow, and it handles US commercial invoice formats (KeHE, UNFI, Cardinal Health, McKesson) out of the box.

What FSMA 204 explicitly does NOT require

A few things the rule does NOT demand, which are worth knowing so you don't over-engineer your response:

• It doesn't require blockchain. Any structured electronic system that produces the sortable spreadsheet in 24 hours is sufficient.
• It doesn't require every food to be tracked. Only foods on the FTL. The FTL is specific — leafy greens, sprouts, finfish, shellfish, cheese (non-shelf-stable), tomatoes, peppers, cucumbers, tropical tree fruits, eggs (shell eggs), herbs (fresh), deli salads, ready-to-eat cold-cut luncheon meats, and nut butters.
• It doesn't require you to share KDEs with customers or partners proactively. You only produce records on FDA request (or when you initiate a recall, when the data flow goes the other direction).
• It doesn't require a specific system. FDA is system-agnostic. What they care about is that the records exist and are retrievable.

What to do this week if you're behind

Three-step checklist:

• Audit your FTL exposure. List every SKU you handle that's on the FTL. If you're a typical grocer with a produce section and a deli, it's usually 80-150 SKUs.
• Talk to your suppliers. Confirm they're passing the traceability lot code on the invoice or accompanying documentation. If they're not, they're also out of compliance — and you need the data, so push.
• Get your receiving process into a system that captures TLCs at lot level and retrieves them on demand. This is the highest-leverage fix. A 14-day free trial of ShelfLifePro (or equivalent purpose-built software) will let you feel the difference before you commit.

The longer play — traceability as an operational advantage

Plenty of grocers approach FSMA 204 as a compliance cost — something you do because you have to. The operators who treat it as an operational upgrade end up with something more valuable: lot-level visibility into their inventory, clean recall workflows that cost minutes instead of days, and the kind of supplier data that actually informs purchasing decisions. The FDA didn't build Section 204 to make your life harder. It built it because granular traceability is what an honest modern food supply chain looks like. Leaning into it is cheaper than resisting it.

Related reading

• Global Invoice OCR — receiving workflow for US distributors
• AI Features hub — smart procurement + OCR
• FSMA 204 Food Traceability: 2026 Compliance Checklist (earlier post)
• FSMA Lot-Level Traceability for Grocery
• FDA Drug Recall Response for Independent Pharmacies

Next step

Start a free 14-day trial. Upload one real receiving document and see the lot-level GRN written for you.