January 20, 2026 was the compliance deadline for the FDA Food Traceability Rule, the regulation implementing Section 204(d) of the Food Safety Modernization Act. Food producers handling commodities on the Food Traceability List are now operating under an enforcement posture, not a preparation posture. If your traceability program is still being built, the pressure to move quickly is real. If you believe your records are in order, this post covers what FDA will look for when it asks.
What the Rule Actually Requires
The Food Traceability Rule (21 CFR Part 1, Subpart S) creates two interlocking obligations. First, you must maintain records of specific Key Data Elements at each Critical Tracking Event that applies to your operation. Second, you must be able to provide those records to FDA within 24 hours of a written request, or such other timeframe as FDA may specify.
Six Critical Tracking Events (CTEs) are defined under the rule: growing, receiving, transforming, creating, shipping, and cooling. Not every CTE applies to every operation or every commodity. A distributor who receives and ships fresh leafy greens has receiving and shipping CTE obligations but not growing CTE obligations. A produce processor who transforms fresh whole tomatoes into a chopped tomato product has a transformation CTE. The specific CTEs you must address depend on where in the supply chain you operate and what you do with the food.
Key Data Elements (KDEs) are the specific data fields you must record at each CTE. For a shipping CTE, the required KDEs include a traceability lot code, the location where the food was shipped from, the date of shipment, a reference document number, the quantity and unit of measure, and a product description. For a receiving CTE, you must capture the traceability lot code, the location from which the food was received, the date of receipt, and similar reference information.
The traceability lot code (TLC) is the linchpin of the entire system. A TLC is a code that allows an entity to identify the food and its origin. If your suppliers are not assigning codes that meet the TLC definition, your downstream compliance is built on a structural flaw. The code must trace to a specific production event, not just a date or product name shared across multiple lots.
The 24-Hour Records Request in Practice
The 24-hour provision is where most operations discover the gap between having records and being able to produce them quickly. FDA's written request will specify a particular traceability lot code or a batch of product from a specific location and date range. You must produce the relevant KDE records within 24 hours, or within such additional time as FDA may allow.
In practice, this means identifying which receiving records correspond to the requested lot, finding the associated certificates or reference documents, tracing any transformations that occurred at your facility, and identifying all downstream shipments containing that lot. If those records are in separate systems with no automated connection (receiving logs in a spreadsheet, shipping records in an ERP, certificates attached to emails), 24-hour retrieval under pressure is an operational problem, not an administrative one.
A useful planning test: pick a specific lot code you received last month and time how long it takes to assemble the complete KDE record set for that lot, from original receipt through final outbound shipment. That elapsed time, under non-emergency conditions, is your baseline. Real recall conditions add time, not subtract it.
Who Is Covered
The rule applies to entities that manufacture, process, pack, or hold foods on the FDA Food Traceability List (FTL). The FTL includes 16 categories: fresh leafy greens, fresh herbs, nut butters, shell eggs, several seafood categories, fresh-cut fruits and vegetables, tropical tree fruits, melons, peppers, sprouts, tomatoes, and cucumbers, among others.
There is a small business exemption: entities with average annual monetary value of food manufactured, processed, packed, or held below $1 million are generally exempt. For any commercial-scale operation, however, this threshold is unlikely to apply. If you are reading this post because you are actively concerned about compliance, you are almost certainly above the exemption level.
The rule also covers entities at multiple supply-chain levels, not just farms or processors alone. A distributor who receives and re-ships leafy greens has receiving and shipping CTE obligations. The fact that you do not grow the food does not exempt you from the traceability records requirement for the CTEs that apply to your activities.
Where Most Compliance Programs Fall Short
The most common gap we see is not ignorance of what KDEs to capture. Most food safety professionals understand the required fields. The gap is in the completeness and retrievability of those records under time pressure.
Supplier lot code quality is a persistent issue. If your tier-1 suppliers are assigning lot codes that consist only of a date or only of a product name, those codes do not meet the TLC definition. They are not unique identifiers for a specific production lot. Downstream receivers who accept those codes without requiring correction are building a compliance system on an inconsistent foundation.
Documentation linkage is a second common problem. The rule requires that you can connect your receiving record to your shipping record for the same lot. If those records exist in different systems with no automated linkage, every lot-trace request requires manual reconstruction. That reconstruction takes time and introduces the possibility of missing a related record.
A third gap is record completeness for transformations. When you transform a covered food (for example, processing raw produce into a cut or mixed product), the transformation CTE requires that you record both the input lot codes and the output lot codes. Many operations track the output lot well but maintain incomplete records of which input lots contributed to a specific transformation batch.
What Adequate Compliance Looks Like
FDA accepts paper records. The requirement is not for digital systems. What the requirement is for, practically speaking, is complete records at each required CTE and a mechanism to retrieve those records for a specific lot within 24 hours.
Paper-based systems can be compliant if they are well organized and the lot-linkage relationships are documented clearly. The question is whether your actual paper records are complete for every shipment, or whether there are gaps from weeks when volumes were high and record-keeping discipline slipped.
Digital systems do not automatically make you compliant either. A digital system full of incomplete certificates or inconsistent lot codes is not more compliant than a well-organized paper system. The data quality behind the records matters as much as the format they are in.
A Note on What Loamy Does and Does Not Do
Loamy ingests supplier certificates, extracts the KDE fields they contain, and builds a traceability graph that links those records to receiving and shipping events. When FDA asks for lot-trace records, the graph returns the relevant chain in seconds rather than hours. That speed matters operationally.
We want to be direct: Loamy is not a compliance certifier, and using Loamy does not make your operation legally compliant. Compliance depends on the data quality of the underlying records you maintain. What Loamy does is reduce the time to retrieve and organize those records, and reduce the probability that a lot linkage is missed when you are under pressure to respond to a time-sensitive request.
The enforcement window is open. The practical test for any food producer is whether your operation could respond to a 24-hour records request today, without advance notice, for a specific lot that moved through your facility in the last 30 days. If that question is uncomfortable to answer, the time to address the underlying gaps is before the request arrives.