The U.S. Food Traceability Rule, known as FSMA 204, was supposed to take effect on January 20, 2026. In August 2025 the FDA proposed a 30-month extension to July 20, 2028, acknowledging that few companies could comply in time because every partner in a supply chain must be ready before accurate data can flow. Congress then directed the agency not to enforce the rule before that date, and the FDA has said it will follow that direction. Many food companies breathed a sigh of relief. The smart ones treated the delay as a runway.
FSMA 204 is fundamentally a data problem that happens in motion: on farms, at packhouses, in trucks, at distribution centers and at receiving docks. That makes shipment monitoring, the combination of IoT devices, logistics events and integration that tracks goods between parties, one of the most practical ways to get ready. This article explains what the rule requires, where shipment data fits, and a step-by-step plan for using the extra time well.
What FSMA 204 Requires, in Plain Terms
The rule applies to foods on the FDA’s Food Traceability List, which includes items such as leafy greens, fresh-cut fruits and vegetables, cucumbers, tomatoes, peppers, melons, fresh herbs, soft cheeses, shell eggs, nut butters and many finfish and shellfish. Foods that contain a listed food as an ingredient are covered if the listed food remains in the form in which it appears on the list.
Covered companies must keep records of Key Data Elements (KDEs) associated with specific Critical Tracking Events (CTEs), and maintain a written traceability plan. The CTEs defined in the rule are:
- Harvesting
- Cooling before initial packing
- Initial packing of a raw agricultural commodity
- First land-based receiving of food from a fishing vessel
- Shipping
- Receiving
- Transformation, such as cutting, mixing or repacking
At the heart of the system is the traceability lot code (TLC). It is assigned at initial packing, at first land-based receiving and at transformation, and must not be changed during simple shipping. When the FDA asks during an outbreak, recall or other public health threat, covered firms must produce an electronic sortable spreadsheet with the relevant traceability information within 24 hours, or within a reasonable time the agency agrees to.
For logistics teams, shipping and receiving events matter most. In practice they require linking each movement to the TLC, quantity and unit of measure, product description, the shipping and receiving locations, the date, and the location description of whoever assigned the TLC, known as the TLC source. Those records must line up between the shipper and the receiver.
Why the Delay Does Not Mean “Wait”
The extension changes the enforcement date, not the scope of work. Three realities make starting now the lower-risk path.
- Interdependence. A distributor cannot capture accurate receiving KDEs if suppliers do not send them. Onboarding hundreds of suppliers and carriers takes years, not months.
- Customer requirements. Large retailers and food service buyers have been asking suppliers for traceability data on their own timelines, independent of FDA enforcement.
- Operational value. The same data that satisfies FSMA 204 also narrows recalls, reduces waste from temperature excursions and speeds dispute resolution with carriers. Those savings start as soon as the data flows.
The FDA is also still refining the details. It scheduled a public meeting on lot-level traceability for November 6, 2026, and continues to publish FAQs, supply chain examples and exemption notices. Companies that already have a working data model can absorb such updates far more easily than those starting from scratch.
FSMA 204 is enforced in 2028, but it is built in 2026 and 2027. Use the runway to make shipment data reliable, linked and shareable.
Where Shipment Monitoring Fits
FSMA 204 does not require IoT sensors. Its KDEs are business records. But shipment monitoring technologies make those records more complete, more timely and easier to trust, and they add condition data that supports food safety decisions.
Identity and event capture
Barcodes and labels on cases and pallets carry the GTIN, the lot and often a serial shipping container code. GS1-128 labels and, increasingly, 2D barcodes using GS1 Digital Link let scanners at shipping and receiving capture the TLC automatically instead of keying it by hand. RFID and the newer battery-free Bluetooth tags can capture movement events without line-of-sight scanning.
Location and condition
Cellular trackers and data loggers record location, temperature and sometimes humidity, light and shock during transit. For cold chain categories that dominate the Food Traceability List, this condition history is not a KDE, yet it is exactly what quality teams need when deciding whether to accept, reject or quarantine a shipment.
Integration and sharing
Event data must land in a system that links CTEs end to end. GS1’s EPCIS 2.0 standard provides a common model for “what, when, where, why and how” events and is widely used for this purpose. Advance ship notices via EDI can carry lot-level details from shipper to receiver, while APIs and data platforms bring IoT telemetry into the same record.
Data quality and trust
Traceability records are only useful if partners and regulators believe them. Automatic capture reduces transcription errors, but it also needs controls: validation rules that reject malformed lot codes, reconciliation between what was shipped and what was received, time-stamped and tamper-evident storage, and clear ownership for correcting mistakes. Sensor data needs its own hygiene, including calibration records for loggers, documented alert thresholds by product, and a rule for which device is authoritative when a carrier’s reefer unit and a pallet tracker disagree. Defining these rules early avoids long arguments during an actual investigation, when time matters most.
Reference Architecture for a Traceability-Ready Shipment Flow
- Identify. Assign the TLC at packing or transformation and encode it, with the GTIN, in a scannable label on every case. Use the same TLC source location identifier, ideally a GS1 Global Location Number, consistently.
- Capture at shipping. Scan cases or pallets when they are loaded. The warehouse system generates a shipping event with all KDEs and sends an advance ship notice containing the lots to the receiver.
- Monitor in transit. Attach a tracker or logger per trailer or per pallet, linked to the shipment ID. Stream location and temperature to a monitoring platform with alerts for excursions and delays.
- Capture at receiving. The receiver scans inbound units and reconciles them against the ship notice. Discrepancies, such as missing lots or unexpected quantities, are flagged immediately.
- Store and link. Shipping, transit and receiving events are written into an event repository that links them by TLC and shipment, with full lineage through any transformation.
- Respond. A prebuilt query generates the FDA sortable spreadsheet for any product, lot range and date window, and a recall workflow uses the same data to identify affected customers.
Decision guide: choosing monitoring technology by lane
Not every shipment needs the same level of instrumentation. Choose based on product risk, value, lane length and how often you need data.
- Short regional reefer lanes: trailer-level telematics from carriers plus scanning at both ends is often enough. Negotiate data access in carrier contracts.
- Long-haul and cross-border lanes: real-time cellular trackers per load provide location and temperature alerts and evidence for claims.
- High-risk or high-value products: pallet-level or case-level sensing, such as single-use trackers or battery-free tags read by gateways at facilities.
- Ocean and air imports: trackers with global connectivity and regulatory approval for air transport, combined with lot data from the foreign supplier.
- Reusable assets: tagging totes, crates and pallets helps maintain chain of custody where products move between containers.
A 20-Month Roadmap to July 2028
With roughly twenty months left before enforcement begins, a phased plan keeps the effort manageable and leaves time for supplier onboarding and testing.
Months 1–3: Scope and baseline
Inventory every product that is on the Food Traceability List or contains a listed food. Map each facility’s CTEs and the systems that hold the relevant data today. Check exemptions carefully with the FDA’s online tool rather than assuming. Run a first mock request to see how long it takes to produce a sortable spreadsheet for a single lot; the answer is usually sobering and provides a useful baseline.
Months 4–9: Data model and internal capture
Design the event model, standardize location identifiers and product master data, and fix internal capture at your own docks and production lines. Choose monitoring technology per lane and start linking tracker data to shipment IDs. Draft the written traceability plan, including how TLCs are assigned and who maintains records.
Months 10–15: Partner onboarding
Prioritize suppliers and customers by volume and risk. Offer more than one onboarding path, such as EDI, API, a supplier portal and, for the smallest partners, a mobile app. Add contractual requirements for KDE delivery and carrier data access to new agreements and renewals.
Months 16–20: Prove it
Run quarterly mock recalls across several partners, measure response times, and fix the gaps that appear. Train staff on exception handling, such as receiving a lot without complete KDEs. Keep monitoring FDA updates and adjust the traceability plan as guidance evolves.
Worked Example: A Fresh-Cut Produce Processor
Consider a hypothetical processor that buys whole lettuce and tomatoes from about forty growers, produces salad kits, and ships to regional distribution centers for retailers. Its products are clearly on the Food Traceability List and it performs transformation, so it must assign new TLCs.
Discovery shows three gaps. Many growers send lot numbers only on paper bills of lading. The processor’s production system records which input lots go into each run, but not in a format that can be queried quickly. And temperature data from carriers is available only on request, by email.
The improvement plan addresses each gap. Growers are onboarded to a supplier portal where they submit harvest, cooling and shipping KDEs, and the largest growers integrate via EDI. Receiving staff scan inbound case labels, and the system blocks receipt of lots without required KDEs. Production records are moved into an event model where each output TLC links to its input TLCs. Outbound pallets receive labels carrying the GTIN and new TLC, and each outbound load gets a cellular tracker whose readings are linked to the shipment record.
Within a few months, the processor can generate a sortable spreadsheet for any finished-goods lot in minutes. Excursion alerts let the quality team intervene during transit rather than discovering problems at the customer’s dock, and a mock recall exercise shows that the affected scope can be narrowed to specific lots rather than entire production days.
The team also learns where to stop. Case-level sensing was considered for every outbound case, but the analysis showed that one tracker per load, combined with scan events at both docks, met quality and compliance needs on most lanes at a fraction of the cost. Case-level tags were reserved for a premium product line shipped on longer routes, where excursions had historically caused the most rejected loads. Matching the technology to the risk, rather than buying the most granular option everywhere, kept the program affordable enough to extend to all growers.
Common Pitfalls
- Treating FSMA 204 as an IT reporting project and ignoring dock-level processes where data is actually created.
- Creating new lot codes at shipping, which the rule prohibits outside the defined events.
- Collecting IoT telemetry that is not linked to shipment and lot identifiers, so it cannot be used in an investigation.
- Relying on PDFs and emails for supplier data, which breaks the 24-hour response.
- Instrumenting every lane at the same level instead of matching technology to risk.
- Never testing the process with mock recalls before an actual FDA request arrives.
Outlook: Traceability as a Competitive Capability
By 2028, traceability data is likely to be a condition of doing business with major buyers regardless of exemptions. GS1’s Sunrise 2027 push for 2D barcodes at retail point of sale will make lot and expiry data available deeper in the chain, and battery-free sensing is bringing item-level visibility within reach for high-volume perishables. The companies that build linked, event-based shipment data now will be the ones able to offer customers faster recalls, verified cold chain and lower waste as part of their value proposition.
Conclusion
The FSMA 204 extension gives food companies until July 20, 2028, but it does not shrink the work. Shipment monitoring sits at the center of that work because shipping and receiving events tie the whole chain together. Map your CTEs, encode TLCs in scannable labels, link IoT condition data to lots and shipments, onboard suppliers early and test with mock recalls. Do that over the next twenty months, and compliance becomes a by-product of a supply chain that is simply better run.
How Hanoi Technology Can Help
Hanoi Technology helps food and logistics companies connect trackers, scanning and EDI into an event-based traceability platform that can answer an FDA request in hours.