FSMA 204 Food Traceability Rule: What Foreign Exporters Must Build Before July 2028

The FDA Food Traceability Rule under section 204(d) of the Food Safety Modernization Act changes traceability from a general one-step-forward, one-step-back exercise into a linked, lot-level recordkeeping system for higher-risk foods. It applies across the supply chain to covered persons that manufacture, process, pack, or hold foods on the Food Traceability List for consumption in the United States. That scope includes foreign companies. A producer, processor, cold store, consolidator, or exporter outside the United States can therefore hold information that a US importer, distributor, or retailer needs in order to comply. Registration alone does not satisfy this rule. The business must be able to identify the relevant lot, describe what happened to it at each covered event, and transmit the required data quickly enough for the next supply-chain partner to preserve the chain.

What changed about the compliance timeline

The original compliance date was January 20, 2026. FDA later proposed a 30-month extension to July 20, 2028. Congress then directed FDA not to enforce the Food Traceability Rule before July 20, 2028, and FDA has stated that it intends to comply with that direction. The precise legal point matters: the rule itself has not disappeared, and the current FDA page describes the extension as proposed while separately confirming the congressional non-enforcement direction. Foreign exporters should use July 20, 2028 as the current enforcement planning date without treating the additional time as a reason to stop implementation. Traceability depends on shared data across multiple companies, so a facility that waits until 2028 may discover that its lot codes, supplier records, customer systems, and commercial documents cannot be connected without redesigning normal operations.

First determine whether the food is on the Food Traceability List

The additional records apply to foods specifically named on the Food Traceability List and to foods that contain a listed food as an ingredient when that ingredient remains in the same form in which it appears on the list. The list includes categories such as certain cheeses, shell eggs, nut butters, cucumbers, fresh herbs, leafy greens, melons, peppers, sprouts, tomatoes, tropical tree fruits, finfish, crustaceans, molluscan shellfish, and ready-to-eat deli salads. Coverage must be evaluated against the exact description, commodity, form, and exemptions—not against a broad assumption that every food or no processed food is covered. A mango exporter, seafood processor, cheese producer, salad manufacturer, or company using fresh listed ingredients should document its coverage analysis product by product. That analysis should also identify whether a kill step, transformation, or another exemption changes the obligation at a particular point in the chain.

Critical Tracking Events define when data must be captured

The rule organizes traceability around Critical Tracking Events, usually called CTEs. Depending on the operation, these events include harvesting, cooling before initial packing, initial packing of a raw agricultural commodity, first land-based receiving of food obtained from a fishing vessel, shipping, receiving, and transformation. A foreign business does not select one generic record set for the whole facility. It identifies which CTEs it performs for each covered food and then captures the Key Data Elements assigned to those events. A farm that harvests and initially packs fresh produce has different event duties from a plant that transforms covered ingredients into a new food, while an export warehouse that receives and ships covered lots has another record pattern. Mapping the physical product flow is therefore the first technical step.

Key Data Elements make the record usable

Key Data Elements, or KDEs, describe the who, what, where, and when of each CTE. Depending on the event, the required information can include the traceability lot code, the product description, quantity and unit of measure, location descriptions, dates of receipt or shipment, the immediate previous source or subsequent recipient, and references to source documents. The goal is not to collect isolated spreadsheets. The data must connect one event to the next through a traceability lot code and consistent location information. If a commercial invoice uses one product name, the warehouse system uses another, and the importer receives a third internal code with no cross-reference, the records may exist but still fail to produce a usable trace.

The traceability lot code is the connecting key

The traceability lot code, commonly abbreviated TLC, is the identifier that links the KDEs for a specific lot as it moves through the supply chain. The rule limits when a new TLC may be assigned. In general, the code is created at initial packing for certain raw agricultural commodities, at first land-based receiving for food obtained from a fishing vessel, or when food is transformed. Companies downstream must preserve and pass the TLC rather than silently replacing it with an unrelated internal lot number. Internal systems may still use their own warehouse or order identifiers, but the business needs a durable cross-reference to the TLC and the location where the code was assigned. Relabeling, repacking, mixed pallets, and consolidation are common points where that link is lost.

Every covered business needs a traceability plan

A written traceability plan explains how the company maintains the records required by the rule. It should describe the procedures used to maintain the records, explain how the company identifies foods on the Food Traceability List, describe how traceability lot codes are assigned when the company performs an event that permits assignment, and identify a point of contact for questions about the plan and records. Farms may also need a map showing the areas in which covered foods are grown or raised, with additional aquaculture information where applicable. The plan should match actual operations. A template that says data is collected electronically is not enough if staff at the receiving dock still record supplier lot information on paper that never reaches the export documentation.

FDA may require records within 24 hours

Covered records must be made available to FDA within 24 hours after a request, or within another reasonable time to which FDA agrees. In specified circumstances connected to an outbreak, recall, or other public-health threat, FDA may also request an electronic sortable spreadsheet containing the relevant traceability information. This requirement changes the standard for record readiness. A foreign exporter cannot assume it will have several weeks to collect documents from farms, brokers, warehouses, and freight forwarders after FDA asks. The records may be maintained as original paper records, electronic records, or true copies, but the company must know where they are, how they connect, who can retrieve them across time zones, and how the data will be converted into a form FDA can review.

Foreign suppliers must coordinate with US importers before shipping

The rule is operationally different from FDA food facility registration, Prior Notice, and the Foreign Supplier Verification Program, but those systems intersect in practice. The importer needs confidence that its foreign supplier can transmit accurate traceability data for covered foods. Purchase specifications should say which party creates the TLC, which fields must appear on advance shipping notices and commercial records, how location identifiers will be represented, and how corrections will be controlled. The parties should test a real lot from origin through US receipt. A successful test means both sides can reconstruct the lot without relying on one employee's memory or manually searching unconnected messages. FSVP approval of a supplier does not replace FSMA 204 records, and an active FDA facility registration does not prove traceability readiness.

Exemptions require evidence, not assumptions

The final rule contains full and partial exemptions and modified requirements, including provisions based on certain farm sales, direct-to-consumer transactions, specified processing, transporters, commingled raw agricultural commodities, and other defined circumstances. An exemption is only as reliable as the facts and records supporting it. A company should identify the exact regulatory basis, document the relevant sales or process conditions, and reassess the conclusion when products or customers change. It is risky to rely on statements such as 'we are small,' 'the food is frozen,' or 'the importer handles FDA compliance' without checking the rule's actual definitions. A business may be exempt for one product flow and covered for another.

A practical implementation plan for 2026 through 2028

1. Build a product-by-product Food Traceability List matrix that records the food, form, ingredient status, process, customer, and the reason it is covered or exempt.
2. Map every Critical Tracking Event performed by the facility and assign ownership for each required Key Data Element.
3. Define the traceability lot code format, the TLC source location, and the cross-reference to existing batch, pallet, invoice, and shipment identifiers.
4. Update supplier and customer data requirements so required traceability information travels with the product instead of arriving only after a problem.
5. Write the traceability plan, retention procedure, correction controls, and 24-hour FDA response process, including weekend and time-zone coverage.
6. Run mock traces in both directions using real lots, measure the time required, record gaps, and repeat until the team can produce a complete, sortable response.

What FDABridge can do

FDABridge helps foreign food manufacturers and exporters connect FDA registration, US Agent, FSVP, Prior Notice, labeling, and traceability obligations into one workable market-access plan. For FSMA 204 readiness, we can help screen products against the Food Traceability List, map CTEs and KDEs, review data exchanged with the US importer, and identify gaps before a customer audit or FDA request exposes them. The regulatory starting points are FDA's Food Traceability Final Rule page at https://www.fda.gov/food/food-safety-modernization-act-fsma/fsma-final-rule-requirements-additional-traceability-records-certain-foods and the Food Traceability List at https://www.fda.gov/food/food-safety-modernization-act-fsma/food-traceability-list. To discuss your product flow, visit https://fdabridge.com/contact.