Food Lot Tracking: What Your Warehouse Has to Record

If your warehouse receives, stores and ships foods on the FDA's Food Traceability List, your lot job is mostly to keep someone else's lot code intact. You record the traceability lot code at receiving, record it again at shipping, and pass it on. In general you do not create a new one; the exceptions are repacking, relabeling, commingling and receiving from a supplier the rule does not cover.

This post covers the U.S. FDA Food Traceability Rule (21 CFR Part 1, Subpart S, often called FSMA 204) from the point of view of the building in the middle of the chain. It is a plain-language summary, not legal advice.

Which foods does the Food Traceability Rule cover?

The rule applies to people who "manufacture, process, pack, or hold" foods on FDA's Food Traceability List (21 CFR 1.1300). Holding counts, so a distribution center or cold store is in scope for listed foods even if it never opens a case.

FDA's list page (updated July 24, 2026) includes, among others:

• Cheeses other than hard cheeses
• Shell eggs
• Nut butters
• Fresh cucumbers, herbs, leafy greens, melons, peppers, sprouts, tomatoes and tropical tree fruits
• Fresh-cut fruits, fresh-cut leafy greens and other fresh-cut vegetables
• Finfish, smoked finfish, crustaceans and molluscan shellfish (bivalves), including frozen forms
• Refrigerated ready-to-eat deli salads

The list has no beverage category: the rule reaches a product only if it is on the list, or contains a listed food as an ingredient that "remains in the same form" as listed. The forms are specific. Cheeses are excluded if frozen, previously frozen, shelf stable or aseptically processed, while finfish stays on the list fresh, frozen or previously frozen. Flag listed foods at the item level, not the category level.

Which exemptions should a distributor check?

Section 1.1305 has exemptions a warehouse should check item by item before building records:

• Kill step already applied. Food you receive "that has previously been subjected to a kill step" (1.1305(d)(5)).
• Kill step downstream. Food shipped to a customer who will apply a kill step, under a written agreement that both parties keep and that "must be renewed at least once every 3 years" (1.1305(d)(6)).
• Raw bivalve shellfish covered by the National Shellfish Sanitation Program, or by an FDA equivalence determination (1.1305(f)).
• Exclusive USDA jurisdiction, under the meat, poultry and egg products inspection acts (1.1305(g)).
• Transporters of food (1.1305(n)).

Some exemptions are partial. Commingled raw agricultural commodities are exempt (1.1305(h), with an exception for produce covered by Part 112), but a registered facility still keeps immediate previous source and immediate subsequent recipient records for two years.

When does a warehouse have to comply?

The original compliance date was January 20, 2026. FDA's rule page, current as of October 8, 2026, says FDA "proposed to extend the compliance date for the rule by 30 months to July 20, 2028," and that the Continuing Appropriations Act of 2026 "directed FDA not to enforce the Food Traceability Rule prior to that same date." Check FDA's rule page for current status.

The delay moves enforcement, not the requirements. In a June 10, 2026 update on tabletop exercises held from March 9 to April 1, 2026, FDA reported that "Most firms responded within 24 hours," and that supply chain coordination "more than any particular technology" drove the strongest results.

What does a warehouse record when food comes in and goes out?

The rule organizes records around critical tracking events. For a warehouse, those are receiving and shipping. Holding ("storage of food" and activities incidental to it) is not itself an event that triggers a record; the receiving and shipping records prove where a lot was while you held it.

At receiving, 21 CFR 1.1345(a) asks for, per traceability lot:

• The traceability lot code
• Quantity and unit of measure
• Product description
• Location description for the immediate previous source (not the trucking company)
• Location description for where you received it
• Receipt date
• Location description for the traceability lot code source, or the lot code source reference
• The reference document type and number, such as the bill of lading or invoice

A location description is the business name, phone number and address. The rule's lot code source reference is an alternative way to point FDA to that description, and its examples are the source's FDA Food Facility Registration Number or a web address.

At shipping, 21 CFR 1.1340(a) asks for the same shape of record pointed the other way, and 1.1340(b) says you must send items one to seven (everything except the reference document) to the recipient, in electronic, paper or other written form.

If you receive a listed food from someone the rule does not apply to, 1.1345(b) changes the receiving record, and the lot code is one "you must assign if one has not already been assigned" (retail food establishments and restaurants excepted). That is the main case where a pure receive-and-ship warehouse becomes a lot code source.

The lot code does not have to be printed on the carton: FDA's lot code page says it can travel on a bill of lading, an advance ship notice, an email or a QR code. A code you can scan, though, is a code you can capture without retyping. GS1 US guidance for FSMA 204 (Release 3.0, December 2025) treats the lot code as a GTIN plus batch/lot and says best practice is to put "at a minimum, the GTIN, date, and batch/lot" in the barcode. See barcode scanning in the warehouse for how that capture works.

Supplier compliance will be mixed: use advance ship notices where suppliers send them. Receive each lot on a mixed-lot pallet as its own line, not as one pallet quantity. Keep a manual entry path for unlabeled product, with validation so a lot code field cannot be saved blank.

Which floor jobs change the lot code, and which don't?

Under 21 CFR 1.1320, a lot code is assigned at initial packing, first land-based receiving from a fishing vessel and transformation. For other activities, such as shipping, "you must not establish a new traceability lot code." The rule defines transformation as changing a food, "e.g., by commingling, repacking, or relabeling." FDA's February 2026 draft guidance applies that to warehouse work:

Your own pallet IDs sit alongside the supplier's lot code, never in place of it. If a shipping record shows your pallet ID where the lot code belongs, the chain breaks at your building. Any job that repacks, relabels or commingles a listed food needs its own procedure.

Do moves between your own buildings count as shipping?

According to FDA's draft guidance, moving food between two of your own locations at different street addresses is a shipping event, with shipping records at one end and receiving records at the other. The draft describes a narrow exception for ad hoc transfers between retail or restaurant outlets, which does not apply when locations regularly share inventory. A warehouse that replenishes its own stores or a second building should treat each transfer of a listed food as a shipment.

How fast do you have to produce the records?

When FDA asks, records must be available "within 24 hours (or within some reasonable time to which FDA has agreed)" (21 CFR 1.1455(c)(1)). When the request is to help with an outbreak, a recall or another public health threat, 1.1455(c)(3) adds a duty to provide the information in an electronic sortable spreadsheet, also within 24 hours. Small businesses have exceptions to the spreadsheet requirement; for example, persons other than farms, retailers and restaurants with average annual food sales and held-for-fee value of no more than $1 million, adjusted for inflation from 2020. Records are kept for two years (1.1455(d)), on paper or electronically.

Another entity may keep the records for you (1.1455(b)), but the 24 hours stay yours, and 1.1315 requires a written traceability plan with a named contact.

Run a mock request: pick a listed item and a date range, start the clock, and produce a sortable file with the full receiving and shipping records, not just lots and customers. Time it against 24 hours, and run one outside office hours.

How does FEFO fit with lot tracking for food?

FEFO, first expired first out, needs a date on the record, and lot tracking needs a code. Both usually come off the same case label, so capture them in one scan. See FIFO vs FEFO for the general choice. Three food-specific points:

• Food dates are mostly not a federal safety rule. USDA's Food Safety and Inspection Service says that "except for infant formula, product dating is not required by Federal regulations," and that a "Best if Used By" date "is not a purchase or safety date." Cut-offs are usually set by each customer's minimum remaining shelf-life terms.
• Know which date your suppliers print. GS1 US guidance for standard case code labeling (Release 3.1), written for brand owners labeling cases, lists production date AI (11), packaging date AI (13), best before AI (15) and expiration or use-by AI (17), and says: "It is a best practice to have one date code per product to align with the human readable text on the case." Where a supplier prints a pack or production date, convert it to an expiry using the item's shelf life so FEFO compares like with like.
• Capture the lot no later than the pick. One lot per location, or per license plate, tells you which lot a pick took. Mixed-lot locations picked by location only are where lot codes get lost. The pick gives you the lot; the rest of the shipping record still comes from the order and the documents.

What to check this month

• Flag listed foods at the item level, and record which exemptions apply.
• Confirm receiving captures the supplier's lot code and lot code source for every listed item.
• Confirm shipping records and outbound documents carry the same lot code.
• Write down which jobs repack, relabel, recoup or commingle, and give them their own procedure.
• Restock a returned listed food only if it comes back with its original lot code.
• Run one mock records request and time it.