Current status
Plan for July 20, 2028 without misstating the rule.
The original compliance date was January 20, 2026. FDA proposed a 30-month extension to July 20, 2028. Congress later directed FDA not to enforce the Food Traceability Rule before July 20, 2028, and FDA says it intends to comply with that directive. The extension itself remains proposed as of this review date.
That distinction matters. July 20, 2028 is the current no-enforcement-before date, not a reason to claim that the rule is already being enforced or that an organization has been certified.
Applicability
Start with the food, activity, and exemption analysis.
The rule generally applies to people who manufacture, process, pack, or hold a food on the FDA's Food Traceability List, or a food containing a listed food as an ingredient, when a covered activity is performed.
The rule includes full and partial exemptions, modified requirements, and waivers. Applicability can depend on the food, activity, business type, sales, processing, packaging, and supply-chain facts. Treat an exemption as a documented conclusion, not an assumption.
CTEs and KDEs
The rule defines seven Critical Tracking Events.
A Critical Tracking Event, or CTE, is a supply-chain activity that triggers a recordkeeping obligation. Key Data Elements, or KDEs, are the facts that must be captured and linked to that event and, where required, to a traceability lot code and its source.
| Critical Tracking Event | Plain-language meaning | Example KDE categories |
|---|---|---|
| Harvesting | Removing a raw agricultural commodity from its place of growth or raising. | Commodity, quantity, harvest location, date, and receiving business details. |
| Cooling before initial packing | Cooling a raw agricultural commodity before it is initially packed. | Commodity, quantity, cooling location, date, and linked harvest information. |
| Initial packing | Packing a raw agricultural commodity for the first time. | Traceability lot code, product description, quantity, location, date, and source details. |
| First land-based receiving | The first land-based receipt of food obtained from a fishing vessel. | Traceability lot code, species and product details, quantity, location, date, and vessel information. |
| Shipping | Arranging transport of an FTL food from one location to another. | Traceability lot code, quantity, product description, ship-from and ship-to locations, date, and reference documents. |
| Receiving | Receiving an FTL food at a location after transport. | Traceability lot code, quantity, product description, previous source, receiving location, date, lot-code source, and reference documents. |
| Transformation | Changing an FTL food, its package, or label, including combining ingredients or creating a new food. | Input and output traceability lot codes, product descriptions, quantities, location, and date. |
The exact KDEs differ by CTE and situation. Use the regulation and FDA guidance, not this summary, to define your required fields.
Open the FDA CTE and KDE referenceTraceability plan
Document how the traceability system actually works.
A covered organization's written traceability plan generally describes:
- Procedures and locations used to maintain required records
- Procedures used to identify foods on the FTL
- How traceability lot codes are assigned, when applicable
- A point of contact for plan and record questions
- A farm map when the rule requires one
- Updates that reflect current practices and retained prior plans
Record availability
Build a repeatable 24-hour response process.
Required records generally must be provided to FDA within 24 hours of a request, or within another reasonable time agreed to by FDA. Records generally must be retained for two years from the date they were created or obtained, subject to the rule's specific provisions.
In specified circumstances involving a foodborne illness outbreak, recall, or other public-health threat, FDA may request relevant information in an electronic sortable spreadsheet. FDA provides a template, but does not require use of that specific template.
Operational business case
Faster traceability can reduce disruption, but the value must be scoped honestly.
FDA's final regulatory analysis explains that faster, more precise traceability can shorten recalls and withdrawals and avoid pulling unaffected product into an overly broad action. FDA estimated industry-wide annualized non-health benefits from avoiding overly broad recalls and withdrawals at $233 million to $1.8 billion, with a primary estimate of $575 million in 2020 dollars.
Those figures describe the expected impact of the rule across the industry. They are not TraceGuard AI savings, customer outcomes, or a guarantee that a particular recall will be smaller. A company-specific business case should separately measure observed labor time and drill performance using its own baseline.
Build a time-value estimate with disclosed assumptionsWhere TraceGuard AI fits
Review, assess, and determine with the evidence intact.
Review
Find the suppliers, ingredients, lots, shipments, customers, and supporting documents tied to the event.
Assess
Run a timed mock recall, trace backward and forward, reconcile volume, and expose gaps while there is time to fix them.
Determine
Give the PCQI or authorized reviewer the organized facts to record the determination, sign the closeout, and assign actions.
FSMA 204 readiness features are in Early Access. TraceGuard AI currently assesses receiving, transformation, and shipping records in the product workflow. The FDA rule also defines harvesting, cooling before initial packing, initial packing, and first land-based receiving. Early Access output is a readiness aid, not an FDA submission, legal opinion, or compliance certification.
The closeout report
The assessment ends with an actionable Mock Recall Report.
The report preserves what the team reviewed, what the exercise revealed, and what the authorized reviewer determined. It can include the following evidence:
FAQ
FSMA 204 questions teams ask first.
What is FSMA 204?
FSMA 204 commonly refers to the FDA Food Traceability Rule in 21 CFR Part 1, Subpart S. It adds traceability recordkeeping requirements for covered foods and activities across the supply chain.
Is July 20, 2028 the compliance date?
FDA proposed extending the original compliance date by 30 months to July 20, 2028. Congress subsequently directed FDA not to enforce the rule before that date, and FDA states that it intends to follow that directive. Teams should track FDA updates because the formal compliance-date extension remains a proposed rule as of this page's review date.
Does FSMA 204 require a PCQI?
The Food Traceability Rule does not itself establish a specific PCQI role. Many organizations still assign readiness and recall-review work to a PCQI, QA lead, or food-safety leader because those teams already own related records, exercises, and corrective actions.
Does TraceGuard AI certify FSMA 204 compliance?
No. TraceGuard AI organizes records, assessments, evidence, findings, and reports. Your organization and qualified advisors remain responsible for determining applicability and compliance.
This page is educational and does not provide legal or regulatory advice. Consult the regulation, current FDA materials, and qualified advisors for determinations specific to your operation.
Turn readiness work into a repeatable process.
Connect the records, practice the response, record the determination, and keep the report ready for internal review.