Food Traceability Requirements: FSMA Rule 204 Compliance Guide
Food Traceability Requirements: FSMA Rule 204 Compliance Guide
Most food manufacturers already track lots in some form — but FSMA Rule 204 raises the bar significantly, requiring specific data elements that many existing systems simply don't capture.
What FSMA Rule 204 Actually Requires
The FDA's Food Traceability Rule (21 CFR Part 1, Subpart S), finalized in November 2022 under FSMA Section 204(d), establishes new traceability record-keeping requirements for anyone who manufactures, processes, packs, or holds foods on the Food Traceability List (FTL). The rule's compliance deadline is January 20, 2026 — which sounds distant, but building compliant systems takes longer than most teams expect.
The core obligation: if the FDA requests your traceability records during a foodborne illness investigation or recall, you must produce them within 24 hours. That's not 24 business hours. That's one calendar day. For manufacturers relying on spreadsheets scattered across departments or paper logs in filing cabinets, that requirement alone should prompt an immediate operational review.
The rule also introduces a new vocabulary that matters for implementation. Understanding these terms precisely determines whether your records are compliant or not.
Key Definitions You Need to Know
- Traceability Lot Code (TLC): A descriptor (number, letter, or symbol, or combination) used to identify a traceability lot. You assign this — but it must be consistent and linkable across your supply chain.
- Critical Tracking Event (CTE): A specific point in the supply chain where traceability data must be captured. The rule defines seven CTEs: harvesting, cooling, initial packing, first land-based receiving, shipping, receiving, and transformation.
- Key Data Elements (KDEs): The specific pieces of information that must be recorded at each CTE. These vary by event type but include things like TLC, location identifiers, dates, and product quantities.
- Traceability Lot Code Source (TLC Source): The location where the TLC was assigned — a farm, packing facility, or processing plant.
Which Foods Are Covered: The Food Traceability List
Rule 204 doesn't apply to every food you make — only foods on the FDA's Food Traceability List. Current FTL foods include:
- Fresh fruits and vegetables (specific varieties including leafy greens, tomatoes, peppers, cucumbers, melons, herbs, and others)
- Shell eggsNut butters
- Ready-to-eat deli salads
- Soft cheeses
- Seafood (finfish, smoked finfish, crustaceans, mollusks)
- Fresh-cut fruits and vegetables
If any ingredient in your finished product comes from an FTL food, the rule may apply to your operation — even if your finished product itself isn't on the FTL. For example, if you manufacture a ready-to-eat wrap containing leafy greens, your transformation CTE records for those greens must meet Rule 204 standards. Review your ingredient list against the full FTL at FDA's FSMA traceability page before assuming you're exempt.
The Critical Tracking Events Manufacturers Must Document
For most food manufacturers and co-packers, the two most operationally significant CTEs are Transformation and Shipping.
Transformation CTE (Manufacturing/Processing)
When you combine FTL ingredients into a new product — or process an FTL food — you must record:
- The new TLC you're assigning to the finished product
- The TLC(s) of each FTL ingredient used in the transformation
- The location description and FDA facility identifier (if applicable) for your facility
- The date of transformation
- The product description and quantity
- A reference document (batch record, production order) linking back to these details
Shipping CTE
Every time you ship an FTL food or a product containing FTL ingredients, you must record:
- The TLC(s) being shipped
- The product description, quantity, and unit of measure
- The location you're shipping from (with FDA facility identifier)
- The location you're shipping to
- The shipment date
- A reference document (BOL, invoice, or similar)
You're also required to provide your supply chain partners with this information — either directly or through a reference document. That means your downstream customers need the TLC to maintain their own receiving records.
FSMA 204 Compliance Checklist for Food Manufacturers
Use this checklist to assess where your operation currently stands:
Step 1: Scope Assessment
- ☐ Identify all SKUs that contain FTL foods as ingredients
- ☐ Identify all CTEs that apply to your specific operation type
- ☐ Determine which facilities in your supply chain are subject to the rule
- ☐ Confirm whether any exemptions apply (small businesses under $1M average annual food sales are exempt; very small businesses under $250K have modified requirements)
Step 2: Records Infrastructure
- ☐ Audit your current lot tracking system — can it capture all required KDEs?
- ☐ Verify records can be produced in electronic, sortable format within 24 hours
- ☐ Ensure records are maintained for a minimum of 2 years
- ☐ Establish a consistent TLC format and assignment procedure
- ☐ Link production batch records to TLCs so you can trace backward from finished product to incoming ingredients
Step 3: Supplier Alignment
- ☐ Contact key ingredient suppliers: are they assigning TLCs? Are they Rule 204 compliant?
- ☐ Update purchase orders and receiving procedures to require TLC documentation on COAs and delivery documents
- ☐ Confirm your inbound receiving records capture TLC, TLC source, and reference document for every FTL ingredient delivery
- ☐ Identify gaps where suppliers aren't yet providing required data
Step 4: Outbound Communication
- ☐ Update shipping documentation (BOLs, invoices, packing lists) to include TLC for all FTL-applicable products
- ☐ Notify distribution partners and direct customers that TLC data will be included on shipment documents
- ☐ Establish a process to respond to customer TLC inquiries within 24 hours
Step 5: Internal Training and Procedures
- ☐ Train receiving staff on capturing and recording TLCs from supplier documents
- ☐ Train production staff on transformation CTE documentation requirements
- ☐ Train shipping staff on outbound KDE requirements
- ☐ Write or update SOPs for each applicable CTE
- ☐ Conduct a mock 24-hour records retrieval drill before the compliance deadline
Common Implementation Mistakes to Avoid
Assigning TLCs that don't match downstream shipments. If your internal lot code doesn't travel with the product on shipping documents, your downstream partner can't link their receiving records to your production records. The TLC must be consistent from your facility through to the customer's receiving log.
Treating Rule 204 as an IT project only. Compliance requires changes to SOPs, supplier contracts, shipping documents, and staff training — not just a software upgrade. Start with operational workflows before selecting technology.
Assuming your ERP already handles this. Many ERP systems track internal lot numbers but don't capture TLC Source location, FDA facility identifiers, or the specific KDE format Rule 204 requires. Validate your system against the actual KDE requirements for each CTE — don't assume.
Overlooking co-manufacturing relationships. If you're a co-packer producing product for a brand, clarify in writing who is responsible for assigning TLCs and maintaining records. Both parties may have obligations under the rule depending on who controls the transformation step.
How Label and Formula Compliance Intersects with Traceability
FSMA 204 traceability records won't help you if the label on your product doesn't accurately reflect what's inside. During a recall, FDA will cross-reference your traceability records against your label, formula, and supplier documentation. Mismatches — an undeclared allergen, an ingredient not reflected in the ingredient statement, a supplier substitution that wasn't updated on the label — can transform a targeted recall into a much broader one.
Before your next SKU launch, it's worth verifying that your label, formula, and supplier documentation are fully aligned. Our annotated sample report shows exactly how a pre-launch SKU review catches these mismatches before they become recall events: view the RecallGuard sample report here.
Building Your 204 Compliance Timeline
With the January 20, 2026 deadline in view, here's a practical phasing approach:
- Now through Q2 2025: Complete scope assessment, audit existing records systems, identify technology or SOP gaps
- Q3 2025: Update supplier agreements and receiving procedures; begin system modifications
- Q4 2025: Staff training, SOP finalization, full system testing
- Q1 2026: Mock 24-hour retrieval drill; remediate any gaps before the compliance date
If you're also managing label compliance for new SKU launches during this period, a structured pre-launch review process can catch documentation gaps — supplier COAs, specification sheets, allergen declarations — that directly affect your traceability records' completeness. The RecallGuard $349 Single SKU Review covers label-formula alignment, allergen declaration accuracy, and supplier documentation gaps in one structured review — the same documentation categories Rule 204 will put under scrutiny during any FDA investigation.
To see how the review process works in 85 seconds, watch the RecallGuard walkthrough here.
This guide reflects FDA requirements as of the date of publication. Rule 204 implementation guidance continues to evolve — monitor the FDA's FSMA traceability page for updated compliance resources and industry guidance documents.