FSMA 204 for Produce Wholesalers: What Records Do You Actually Need?

1. Introduction

FSMA 204 does not require produce wholesalers to create a regulatory record every time a pallet moves, a pick slot is replenished or a case changes warehouse locations. The rule focuses on specific supply-chain events and the information connected to each traceability lot.

For wholesalers, the workflow is straightforward in concept: identify covered products, capture lot information at receiving, preserve lot identity through warehouse handling, and document which lots leave for each recipient.

2. Understanding FSMA 204 in a Produce Warehouse

Four terms are essential:

• Critical Tracking Event (CTE)

  An event for which FSMA 204 requires traceability records. For most wholesalers, the relevant CTEs are Receiving, Shipping and, when applicable, Transformation.

• Key Data Element (KDE)

  A specific piece of information that must be maintained for a CTE, such as the TLC, quantity, date or location.

• Traceability Lot Code (TLC)

  The identifier that connects a traceability lot with its required records.

• TLC Source

  The physical location where the TLC was assigned. It may differ from the supplier or warehouse that shipped the product to you.

Normal put-away, storage, replenishment and picking within the same location generally do not create separate Receiving or Shipping CTEs. Your internal process must still preserve enough lot identity to determine which TLC supplied an outbound shipment.

FDA is also considering flexibilities for difficult lot-level distribution scenarios, including mixed lots. Those discussions have not changed the requirements currently codified in 21 CFR Part 1, Subpart S.

3. What Do You Actually Need?

Start with the Food Traceability List, not your entire inventory. Covered produce categories include fresh cucumbers, herbs, leafy greens, melons, peppers, sprouts, tomatoes, specified tropical tree fruits, fresh-cut fruits and fresh-cut vegetables.

Coverage can depend on product form. Whole apples, for example, are not on the FTL, while fresh-cut apples fall within the fresh-cut fruit category.

For a basic receive-and-resell operation:

For Shipping, the shipper retains the required KDEs and provides the immediate subsequent recipient with the information specified in §1.1340(b). Reference-document type and number are retained by the shipper but are not among the items that paragraph requires to be transmitted.

Covered operations also need a Traceability Plan describing record locations and formats, how FTL foods are identified, TLC assignment when applicable, and the traceability point of contact.

4. Step-by-Step Guide

1. Step 1 Identify Which Products Are Covered

   Review your catalog at the SKU or product level against FDA’s Food Traceability List.

   Consider commodity, product form, processing and applicable exemptions. Maintain a classification that tells purchasing, receiving and operations which products require additional traceability records.

2. Step 2 Map the CTEs in Your Actual Workflow

   For each covered product, map what physically happens to it.

   A straightforward operation may look like:

   Supplier → Receiving → Storage/Picking → Shipping → Customer

   If you repack, relabel or commingle covered product, insert Transformation into the workflow.

   Transfers between company facilities at different street addresses also matter: the origin performs Shipping and the destination performs Receiving even when ownership does not change.

3. Step 3 Capture Receiving KDEs for Each Lot

   At receiving, record the required information for each traceability lot, not simply the total SKU quantity on the purchase order. Capture the TLC, TLC source or source reference, previous source, product description, quantity, receiving location and date, and reference document.

   Common mistake

   The supplier or previous source is not necessarily the TLC source. The TLC source is the physical location where that traceability lot code was assigned.

   If a covered wholesaler receives FTL food from a person to whom Subpart S does not apply and no TLC has been assigned, special Receiving provisions apply. A covered receiver that is not a retail food establishment or restaurant may need to assign the TLC itself.

4. Step 4 Preserve the Lot Link Through Storage and Picking

   Do not routinely assign a new TLC simply because product enters your warehouse. Preserve enough lot identity to answer: Which TLC or TLCs supplied this outbound order?

   If several tomato lots share a pick location, SKU-level inventory may show 180 cases available without identifying which lot supplied the 25 cases being shipped.

   Your process may use scanning, pallet or location controls, WMS logic, manual records or another reliable method.

   Practical tip

   FSMA 204 is technology-neutral. Barcode scanning can make lot tracking easier, but FDA does not require barcode scanning, GS1, RFID, EPCIS or a specific warehouse system.

5. Step 5 Separate Repacking and Other Transformations

   Repacking an FTL food is a Transformation event rather than an ordinary warehouse movement. Relabeling and commingling can also trigger Transformation requirements when the resulting food remains covered.

   Transformation records connect incoming lots with the resulting output. A “like into like” repack involving one traceability lot may retain the existing TLC under FDA’s described conditions, but Transformation records are still required and the TLC source changes to the repacking location.

   When multiple lots are combined, records must preserve the relationship between each applicable input lot and the resulting output lot.

6. Step 6 Create the Shipping Record for the Lots That Left

   When covered product leaves, maintain Shipping KDEs for each traceability lot shipped, identifying the immediate subsequent recipient—not the carrier—and the quantity shipped.

   The required downstream information can be communicated through an ASN, BOL, invoice, electronic message, QR code or another suitable mechanism. FDA does not require the TLC itself to be printed on every carton.

   Customer requirements may go further. A retailer can require PTI labels, GS1 identifiers, EDI 856 ASNs or case-level scanning even though those technologies are not themselves FDA mandates.

7. Step 7 Test Retention and Retrieval

   Required records generally must be retained for two years from the date created or obtained and may be paper, electronic or accurate copies. When FDA makes a qualifying request, they generally must be available within 24 hours, or another reasonable period agreed upon with FDA.

   Checklist

   • Can you identify every FTL SKU you currently handle?
   • Can Receiving capture the required KDEs by traceability lot?
   • Can staff distinguish the previous source from the TLC source?
   • Can you identify which TLCs supplied a specific outbound shipment?
   • Are repack and commingling operations recorded as Transformation when required?
   • Can required Shipping KDEs be passed to the next recipient?
   • Can your team retrieve and explain the relevant records within 24 hours?

5. Practical Tips for Produce Wholesalers

Reuse existing business records. Invoices, BOLs, ASNs, purchase orders, WMS records and production logs can contain required KDEs. Existing records may be supplemented with missing information rather than duplicated.

Standardize location data. Keep supplier identities, receiving locations, shipping origins and TLC sources distinct. Internal vendor codes alone may not provide the location information required by the rule.

Test realistic warehouse conditions. Run traces using partial pallets, replenished pick slots and multiple lots of the same SKU. These scenarios are more likely to reveal broken lot relationships than a test involving one intact pallet.

6. Common Challenges

Mixed-lot inventory. Multiple TLCs in the same pick location can make outbound lot identification difficult. FDA is examining potential flexibilities, but inferred lots and reasonable lot ranges should not yet be treated as finalized alternatives.

Missing TLC-source information. A lot code without the associated source information may leave the traceability record incomplete.

Physical movement that is not a sale. Intracompany transfers between different street addresses and movements through third-party cold storage can create Receiving and Shipping events even when commercial ownership does not change.

7. Practical Example

Consider an illustrative shipment of Roma tomatoes.

A wholesaler receives:

The warehouse stores the 50 cases and later ships 30 cases to Customer 1 and 20 cases to Customer 2.

No new TLC is needed merely because the tomatoes were stored, moved or picked within the warehouse. The Shipping records must show that 30 cases of LOT-A went to Customer 1 and 20 cases of LOT-A went to Customer 2, together with the other required Shipping KDEs.

If those tomatoes were opened and repacked instead, the workflow would move into Transformation requirements before the resulting product was shipped.