FSMA 204 traceability records: what food distributors must keep

What FSMA 204 asks food distributors to do#

FSMA 204, the FDA food traceability rule, asks companies that manufacture, process, pack or hold foods on the Food Traceability List to keep specific traceability records and provide them to FDA on request. For a food distributor, that generally means recording lot-level information whenever listed foods are received, shipped or transformed.

The rule rests on two ideas. Critical tracking events are the supply chain steps at which records are kept. Key data elements are the facts recorded at each event, anchored by a traceability lot code that ties the food back to where it was packed or transformed.

Treat the compliance date as something to verify, not remember, because FDA has already announced a delay to the original date. Check FDA's Food Traceability Rule page and confirm with counsel before setting a project plan, and use any extra time on the hardest part, which for many distributors is capturing lots at pick.

Does the rule apply to your operation?#

Whether FSMA 204 applies to a distributor depends on what it handles and what it does with the food. Work through these questions with counsel, site by site.

The answers can differ by warehouse and by activity. A company may hold listed foods at one site, repack them at another and only broker them through a third, so classify each site and activity rather than the company as a whole.

• 1Do you hold, ship or receive any foods on FDA's current Food Traceability List?
• 2Do you take physical possession of the food, or only arrange its sale?
• 3Do you repack, relabel, split, commingle or otherwise transform listed foods?
• 4Do any of the rule's exemptions or partial exemptions fit your business or products?
• 5Which of your customers are retail food establishments or restaurants with their own obligations?
• 6Do 3PLs, cold storage providers or carriers keep records on your behalf, and under what agreement?

Critical tracking events and key data elements for distributors#

The critical tracking events that most often apply to a distributor are receiving, shipping and transformation. The table summarizes when each applies and the kinds of key data elements typically recorded; the rule text and FDA guidance define the exact elements, so confirm the list with counsel before designing system fields.

In general, a distributor that only receives and ships passes along the traceability lot code it received rather than assigning a new one, and records the source of that code. A distributor that repacks or relabels may be performing transformation, which can change what it must assign and record.

Where traceability records live in a distributor's systems#

A distributor's FSMA 204 traceability records rarely live in one system. Receiving data sits in the WMS, order data in the ERP, ship documents in EDI and TMS records, and supplier lot information often on paper labels or PDFs. The gaps between those systems are where most readiness work happens.

Practical steps to get record-ready#

Getting record-ready for FSMA 204 is mostly data plumbing between systems a distributor already runs. The steps below follow an order many operations teams find workable, starting with scope and ending with a test.

The test matters most. A mock request that asks for every shipment of one lot, run from live systems, shows quickly whether lot data is captured at pick or only at receipt.

• 1Match your item master against the current Food Traceability List and flag covered items.
• 2Map each covered item's path: suppliers, storage sites, any repacking, and the customers who receive it.
• 3Decide how lot codes will be captured at receipt and at pick, whether by scan, ASN or manual entry.
• 4Align location identifiers for suppliers, your sites and customers across ERP, WMS and TMS.
• 5Confirm you can produce a sortable electronic list of all shipments of one lot on short notice.
• 6Write or update a traceability plan if the rule requires one for your operation, and name its owner.
• 7Set retention for traceability records to meet the rule's own minimum period and any longer customer or contract requirements, agreed with counsel.
• 8Review supplier, 3PL and customer agreements so lot data flows in both directions.

Illustrative: a produce and dairy distributor prepares lot-level records#

Illustrative: a fictional regional distributor of produce, dairy and specialty cheeses serves restaurants and independent grocers from its own cold storage warehouses. Several of its items are on the Food Traceability List. Its WMS captures lot codes at receipt for full pallets, but not for cases picked onto mixed customer pallets.

The COO's team adds lot scanning at pick for covered items, maps different supplier lot formats into one field, and links each shipment's lot to the customer order and invoice. A mock recall exercise then lists every customer that received a given lot from the ERP and WMS, without anyone opening a paper file.

The same linked history now shows supplier quality trends, temperature holds and customer returns by lot, analysis the company could not run before.

Lot-level history beyond compliance, and how SourceX approaches it#

Lot-linked receiving, shipping, hold and recall records describe how a food supply chain actually works. That makes them useful for internal analysis and, with care, for AI developers building traceability, recall and exception tools. They also contain supplier names, customer locations and prices that need review before any outside use.

SourceX begins with a metadata-only fit check and, for companies that proceed, runs the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery. Rights review covers supplier and customer agreements, preparation removes personal and confidential details, and a SourceX Evidence Packet records what was approved. Regulatory recordkeeping obligations stay with the company and are not affected by a license.