The rule applies to persons who manufacture, process, pack or hold foods appearing on the FDA's Food Traceability List (FTL), and to foods that contain FTL items as ingredients. That list is broader than people expect: soft cheeses, shell eggs, nut butters, fresh-cut fruit and vegetables, leafy greens, melons, herbs, tropical tree fruits, finfish, crustaceans, molluscan shellfish and ready-to-eat deli salads all appear.

The ingredient clause is the one that catches manufacturers out. A firm that considers itself outside food traceability because it makes a shelf-stable finished product can still be in scope because one ingredient is on the list.

The requirement isn't that you can find the records within 24 hours. It's that you can provide them as an electronic sortable spreadsheet, covering the requested foods and date range, within 24 hours of the FDA asking.

Sortable is the operative word. A folder of PDFs, a shared drive of delivery notes and an ERP export that doesn't carry lot genealogy won't satisfy it. If joining your data requires a person who understands three systems, you don't have 24 hours, you've however long that person takes.

• Small producers below defined revenue thresholds have partial or full exemptions, which are measured on averages over a rolling period.
• Foods that undergo a kill step may be exempt at the point the step occurs, but records upstream of it can still be required.
• Retail food establishments and restaurants have modified requirements rather than none.
• Foods not on the FTL are out of scope, until an FTL ingredient enters the formula.
• Customers frequently impose FSMA 204-shaped requirements contractually regardless of exemption, which is why exempt firms often build the capability anyway.

1. Scope. Screen every finished product against the FTL, including ingredient-level exposure. Most firms discover more in scope than expected.
2. Define the traceability lot code. Decide what a lot is, where it's assigned, and where it changes. Write it down once and enforce it in the system.
3. Map the CTEs to real operations. Not to a process diagram, to the actual points where material moves and changes.
4. Close the transformation gap. Ensure input-to-output genealogy is captured automatically at production, not reconstructed later.
5. Fix supplier inbound data. Agree lot code formats and delivery data with suppliers, and capture what arrives in whatever form it arrives.
6. Test the 24 hours. Run an unannounced drill and time it end to end, including producing the sortable file.

Worldover treats a lot as a live object rather than a field on a document. Receiving, transformation, creation and shipping are ordinary operational events, and recording them produces the KDEs as a side effect. When the request comes, the sortable record is generated from data that has been continuously correct, and Willow AI can answer the scoping questions in plain language while the report is produced. See Worldover for food and ingredients, where traceability, HACCP plans and batch records sit on the same live data.