When food safety professionals at smaller produce operations talk about "FSMA compliance," they are often thinking about one regulation when their actual exposure spans two distinct regulatory requirements. The Produce Safety Rule and the Food Traceability Rule (implementing FSMA Section 204) are separate rules with different scopes, different compliance timelines, and different recordkeeping obligations. Conflating them creates two kinds of risk: spending resources on requirements that do not apply to your operation, and failing to recognize requirements that do.
This post works through the structural differences between the two rules and addresses the most common overlap questions we hear from food safety managers and supply-chain coordinators.
The Produce Safety Rule: What It Covers
The Produce Safety Rule (21 CFR Part 112) was finalized in November 2015 and has phased into compliance since 2018. It sets minimum standards for the safe growing, harvesting, packing, and holding of fruits and vegetables grown for human consumption. The rule covers on-farm activities: agricultural water quality, worker health and hygiene, biological soil amendments, equipment sanitation, and training.
The Produce Safety Rule is primarily a farming regulation. Its requirements fall on entities that grow produce in the United States. Distributors and downstream food processors who do not conduct growing activities are generally outside its scope unless they also pack or hold produce at a farm-level facility. The rule applies to farms regardless of whether their produce ends up on the Food Traceability List under Section 204.
There are several exemption categories. Farms below a certain average annual monetary value threshold are exempt or subject to modified requirements. Farms that conduct direct sales to qualified end-users under the Tester-Hagan exemption have modified requirements. Produce that is rarely consumed raw or is typically processed before consumption is excluded from certain provisions.
The Food Traceability Rule (FSMA Section 204): What It Covers
The Food Traceability Rule (21 CFR Part 1, Subpart S) was finalized in November 2022 with a compliance deadline of January 20, 2026. It requires entities that manufacture, process, pack, or hold foods on the Food Traceability List to maintain records of Key Data Elements at each applicable Critical Tracking Event and to provide those records to FDA within 24 hours of a written request.
Unlike the Produce Safety Rule, the Food Traceability Rule is supply-chain-wide, not farm-specific. It applies to growers, packers, processors, distributors, and retailers if they handle a covered commodity on the Food Traceability List. A distributor who never touches a farm is still subject to FSMA Section 204 if it ships bagged spinach or fresh-cut strawberries. A processor who converts fresh tomatoes into a processed tomato product may or may not be covered, depending on whether the processed form remains on the FTL.
The key question for each operation is: does your facility perform a Critical Tracking Event on a food on the Food Traceability List? If yes, FSMA Section 204 applies to that activity, regardless of whether you are also subject to the Produce Safety Rule.
Commodities: Where the Scope Differs
The Produce Safety Rule applies broadly to fruits and vegetables grown for human consumption, with specific exclusions (grains, tree nuts in some circumstances, etc.). The Food Traceability List under Section 204 is a specific enumerated list of 16 high-risk food categories selected by FDA based on risk factors including outbreak history. Not all produce subject to the Produce Safety Rule is on the FTL, and not all foods on the FTL are produce subject to the Produce Safety Rule (shell eggs, certain nut butters, and seafood categories are on the FTL but not subject to PSR farm-level requirements).
Leafy greens are on both. Fresh tomatoes are on the FTL. Cucumbers, peppers, and fresh herbs are on the FTL. Cantaloupes are on the FTL. For fresh produce operations that grow or handle these commodities, both regulations are active obligations with different, non-overlapping requirements.
The Produce Safety Rule does not require you to maintain traceability lot codes. The Food Traceability Rule does not regulate your irrigation water quality or worker hygiene practices. They address entirely different risk factors and compliance activities. Meeting one does not satisfy the other.
Recordkeeping: The Practical Difference
The recordkeeping obligations are where the two rules diverge most significantly in day-to-day operations.
Under the Produce Safety Rule, farms must maintain records documenting compliance with specific standards: agricultural water testing results, training completion records, applications of biological soil amendments, and corrective actions taken for any deficiencies. These records are facility-level and activity-level records held by the farm. They are not lot-linked in the supply-chain traceability sense.
Under the Food Traceability Rule, covered entities must maintain Key Data Element records linked to specific traceability lot codes at each Critical Tracking Event. Those KDE records must follow the lot through the supply chain. A receiving CTE record must capture the traceability lot code from the shipper. A shipping CTE record must capture the traceability lot code and be linkable to the receiving record for the same lot. The design intent is that FDA can reconstruct the full chain of custody for a specific lot by requesting records from each entity that handled it.
This means a produce farm that grows leafy greens has Produce Safety Rule obligations (water testing, worker hygiene records) and Food Traceability Rule obligations (growing CTE records including traceability lot code, growing area coordinates, commodity description, and harvest date). Those are separate record sets maintained for separate regulatory purposes, though a well-designed records management system keeps them linked.
Where Operations Commonly Confuse the Two
The most common confusion we encounter is operations that have undergone Produce Safety Rule compliance audits, received a good-standing assessment, and concluded they have their regulatory recordkeeping handled. That assessment may be accurate for Produce Safety Rule purposes, and it says nothing about Food Traceability Rule readiness.
The second common confusion is the reverse: operations that have built detailed lot-level traceability systems and believe that demonstrates Produce Safety Rule compliance. Again, different rule, different requirements. Lot-level traceability records do not substitute for agricultural water testing documentation or corrective action records under PSR.
We are not suggesting that compliance with both rules is burdensome in an unreasonable way. For most covered produce operations, the two obligations share some administrative infrastructure (records management systems, certificate filing, training documentation) but address entirely separate operational domains. The practical question is whether your compliance program has assessed your exposure under both rules independently, rather than assuming that readiness for one implies readiness for the other.
A Practical Starting Point
If you are unsure which rules apply to your operation, start with two questions. First, do you grow produce in the US? If yes, the Produce Safety Rule likely applies to your farming activities, with possible exemptions based on size and direct-sale arrangements. Second, do you manufacture, process, pack, or hold any food on the Food Traceability List? If yes, the Food Traceability Rule likely applies to your relevant CTEs, regardless of whether you farm.
For operations that do both, which is common for vertically integrated grower-shippers, both rule sets are active. A grower-shipper who grows, packs, and ships bagged spinach has PSR obligations at the farm level and Food Traceability Rule obligations at the packing and shipping CTEs. The records are different, the enforcement mechanisms are different, and the compliance program needs to address both explicitly.