Compliance
FSMA 204 and recall readiness: a practical guide for food brands
Published · 5 min read
The short answer
FSMA section 204 is FDA's Food Traceability Rule. It requires firms that make, pack, hold, or ship foods on the Food Traceability List to keep specific records at specific supply-chain steps and hand them to FDA within 24 hours on request. FDA has said it will not enforce the rule before July 20, 2028, but the records it asks for are the same ones you need to run a fast recall today.
This guide is general information, not legal or regulatory advice. Rules and dates change; confirm current requirements on FDA's Food Traceability Rule page or with a food safety professional before relying on them.
What FSMA 204 is
The FDA Food Safety Modernization Act (FSMA) became law in 2011. Section 204 of that act directed FDA to set additional recordkeeping requirements for foods it designates as high-risk. FDA published the resulting final rule, "Requirements for Additional Traceability Records for Certain Foods" (21 CFR Part 1, Subpart S), in November 2022. Most people call it the Food Traceability Rule or simply FSMA 204.
The goal is speed. When there is an outbreak, FDA wants to trace a contaminated food back to its source and forward to where it was sold quickly, using records that every firm in the chain keeps in a consistent way.
Who it applies to
The rule applies to persons who manufacture, process, pack, or hold foods on FDA's Food Traceability List (FTL), with a number of full and partial exemptions (for example, certain small producers and some foods that receive a validated kill step). The list includes categories such as soft and semi-soft cheeses, shell eggs, nut butters, fresh herbs, leafy greens, melons, peppers, sprouts, tomatoes, tropical tree fruits, fresh-cut fruits and vegetables, finfish, crustaceans, molluscan shellfish, and ready-to-eat deli salads.
Importantly, coverage also extends to foods that contain an FTL food as an ingredient, as long as the FTL ingredient remains in the same form (for example, fresh). A deli salad made with fresh herbs, or a sandwich spread built on a nut butter, may be covered. Check the current list and exemptions against your own ingredients rather than assuming your category is out of scope.
The compliance date
The rule originally set a compliance date of January 20, 2026. In August 2025, FDA proposed extending that date by 30 months, to July 20, 2028. Separately, a subsequent federal appropriations law directed FDA not to enforce the rule before July 20, 2028, and FDA has said the extension does not change what the rule requires. As of November 2026, July 20, 2028 is therefore the date most firms are planning around, but confirm the current status with FDA before you set an internal deadline.
Do not read the extension as a reason to wait. Large retailers and distributors have been asking suppliers for traceability data on their own timelines, and the records the rule describes are exactly what you need to scope a recall in hours instead of days.
Critical tracking events and key data elements
The rule is built on two ideas. Critical tracking events (CTEs) are the supply-chain steps where records must be kept. Key data elements (KDEs) are the specific pieces of information to record at each one.
| Event | Who typically records it | Examples of key data elements |
|---|---|---|
| Harvesting and cooling | Farms | Commodity, quantity, location, date |
| Initial packing | Packers of raw agricultural commodities | Traceability lot code assigned, quantity, packing date and location |
| First land-based receiving | Receivers of food from fishing vessels | Traceability lot code, quantity, vessel and landing information |
| Shipping | Anyone shipping an FTL food | Traceability lot code, quantity and unit, recipient, ship date, source of the lot code |
| Receiving | Anyone receiving an FTL food | Traceability lot code, quantity and unit, shipper, receive date, source of the lot code |
| Transformation | Manufacturers and processors | Input lot codes and quantities, new traceability lot code, output quantity, date |
Two KDEs deserve special attention. The traceability lot code is a lot code assigned at initial packing, first land-based receiving, or transformation, and it must travel with the food. The traceability lot code source is the place where that code was assigned. Firms that only receive and ship must pass the lot code along; they do not assign a new one.
The traceability plan and the 24-hour request
Covered firms must keep a written traceability plan describing how they maintain records, how they identify FTL foods, how they assign traceability lot codes, and a point of contact. When FDA requests records (typically during an outbreak investigation), firms must provide them within 24 hours, and in some circumstances as an electronic sortable spreadsheet. Records generally must be kept for two years.
The 24-hour window is the real test. If your receiving, production, and shipping records live in different places, assembling a sortable spreadsheet for one lot across all three can take far longer than a day.
A practical readiness checklist
- Inventory your ingredients against the current Food Traceability List and exemptions. Write down which finished products are covered and why.
- Make the traceability lot code a field, not a note. Every receipt, production run, and shipment of a covered food should carry it in your system of record.
- Record transformation properly. For each production run, capture which input lots were consumed and in what quantity, and assign a new lot to the output.
- Capture who you received from and who you shipped to on every line, with dates and quantities.
- Write the traceability plan and name an owner.
- Practice producing the records. Run a mock recall and time how long it takes to produce a sortable list for one lot.
Where an ERP helps, and where it does not
Most of the KDEs above are by-products of transactions a manufacturer already records: purchase receipts, work orders, and shipments. An ERP that carries lot numbers on all three can produce much of the 204 record set from data you already keep.
Here is what Skygn does today, stated plainly:
- Lot numbers and expiry dates are recorded on purchase receipts, against the supplier.
- Completing a work order creates the output lot and records genealogy links from every input lot consumed, with quantities, which is the transformation record.
- Shipment lines carry the lot, the customer, the quantity, the date, and the tracking number.
- The recall screen traces any lot forward to every customer shipment (including finished goods built from it) and backward to source lots and suppliers, and exports the result to CSV. The report builder includes a lot register you can export or schedule by email.
And what it does not do: Skygn does not currently generate a pre-formatted FSMA 204 sortable spreadsheet, does not have dedicated fields for every KDE (such as a separate traceability lot code source, or harvesting and cooling data that farms record), and does not certify that you comply. You would assemble a 204 response from Skygn's lot, receipt, and shipment exports. Compliance is a program you run; software is one input to it.
For a deeper look at the mechanics of traceability systems, see lot traceability software for food manufacturers.
The bottom line
FSMA 204 formalizes what good recall practice already looks like: consistent lot codes, recorded at every step, retrievable fast. If you build those habits now, the 2028 date becomes a formality. If you would like to see how Skygn records lots across receiving, production, and shipping, request a demo or review the features.
Frequently asked questions
- When is the FSMA 204 compliance date?
- The original compliance date was January 20, 2026. In 2025 FDA proposed a 30-month extension to July 20, 2028, and an appropriations law directed FDA not to enforce the rule before July 20, 2028. Confirm the current status on FDA's website before planning.
- Does FSMA 204 apply to my product if only one ingredient is on the Food Traceability List?
- It can. The rule covers foods that contain an FTL food as an ingredient when that ingredient remains in the same form, for example fresh. Exemptions exist, including for some foods that receive a kill step, so review the current list and exemptions for your specific products.
- Does using an ERP make me FSMA 204 compliant?
- No software makes a firm compliant on its own. An ERP that records lots on receipts, production, and shipments can supply most of the required records, but you still need a written traceability plan, correct lot code practices, and the ability to produce records within 24 hours.
See it on your own items, lots, and recipes
Skygn is the ERP for food & beverage and CPG brands. One plan with every module, and a 14-day free trial.