The FDA Food Traceability Final Rule (21 CFR 1.1330–1.1455) — FSMA 204 — has been in effect for cold-storage 3PLs since January 20, 2026. If you receive, hold, transform, or ship any food on the Food Traceability List (FTL), you must keep specified records for 24 months and produce them in a sortable electronic format within 24 hours of an FDA request. This is what that actually means in your warehouse.
The rule defines Critical Tracking Events (CTEs) — receiving, transformation, creating, shipping — at which Key Data Elements (KDEs) must be captured. For a cold-storage 3PL the relevant CTEs are receiving and shipping; transformation comes into play only if your facility repacks or relabels FTL product.
The KDEs include traceability lot codes, supplier or recipient information, location identifier, date and quantity, and a description sufficient to identify the food. The data has to be linked through the chain so a regulator can trace one lot from your receiving dock back to the supplier and forward to the customer in 24 hours.
The Food Traceability List runs to 16 categories: cheeses (other than hard cheeses), shell eggs, nut butters, cucumbers, fresh herbs, leafy greens, melons, peppers, sprouts, tomatoes, tropical tree fruits, fresh-cut fruits and vegetables, finfish, smoked finfish, crustaceans, mollusks, and ready-to-eat deli salads. A 3PL handling any of these touches FSMA 204.
A frozen-food distributor running breaded fish, ready-to-eat seafood, or fresh-cut produce moving through a cold dock has FTL exposure. A frozen-bakery and protein operation may not. Pull the FTL against your inventory before assuming you are out of scope.
The most operationally consequential requirement: when FDA asks, you must produce records as a sortable electronic spreadsheet (or equivalent) within 24 hours. Not a stack of paper, not a PDF dump — a sortable, filterable file the inspector can manipulate. Most 3PL operators are not currently set up for this, and a paper-based receiving log will not pass.
WMS systems with FSMA 204 export functionality are now standard on enterprise platforms; mid-market WMS upgrades during 2024–2025 added the export. If your WMS does not have it, that is the first conversation.
At receiving, you capture: the traceability lot code your supplier provided, the date received, the quantity, the location code (which warehouse, which zone), and the supplier identification. The traceability lot code travels with the product through your operation; it is not yours to assign or change unless transformation occurs.
The cold-side check at receiving — pulldown temperature documentation, dock-side temperature, blast-freezer cycle log if relevant — is part of the broader food-safety record but FSMA 204 specifically asks for the lot code linkage. Both records matter.
Internal moves between locations within your facility do not create new CTEs as long as the traceability lot code is preserved. The location KDE updates when product moves between zones, but the lot code does not change. WMS handles this automatically if configured; manual operations risk losing the lot linkage.
A repack or relabel — taking received product and reassembling it into different SKUs or pack configurations — is a transformation CTE and creates a new traceability lot. Your output lot code links back to the input lot codes through your transformation record.
At shipping, you capture: the traceability lot code, the date shipped, the quantity, the recipient identification, and the location. The customer's lot code is your lot code (or your transformation-output lot code) — they must match.
BOL printing on a customer pick should pull the traceability lot code automatically; manual handwriting introduces breakage and an audit gap. WMS-driven BOL with lot-code printing is the operational standard.
You hold records for 24 months from creation. Cloud archive is acceptable; the 24-hour production window must still be met. Records can live in your WMS, in a separate archive, or in a regulator-friendly export format that you maintain — the format does not matter as long as the production timeline does.
A 3PL that subcontracts receiving documentation to a third party still holds the recordkeeping obligation; the third-party data must flow back into your archive. Get the data flow right at contract level.
Temperature records are not a FSMA 204 KDE per se, but FDA inspection of an FTL product trace will pull cold-chain documentation as part of the broader investigation. A cold-storage 3PL with continuous monitoring (ColdSentry or equivalent) and exportable per-lot temperature records is producing the audit defense regulators expect.
A 12-hour gap in temperature records during a power event, with no documentation of corrective action, weakens the broader food-safety case even if the FSMA 204 lot-code records are clean. Both records matter.
If you have not already: confirm WMS export of FSMA 204 records in sortable format. Pull a test-trace exercise on a recent inbound and walk it forward — receiving, holding, shipping — to verify lot-code continuity. Audit BOL printing for lot-code presence on every outbound. Confirm 24-month archive scope and access path. Train receiving leads on what they capture and why.
On a service-contract account we coordinate cold-chain documentation with FSMA 204 record needs and document the integration in ArcticOS. The two records — temperature continuity and lot-code traceability — together build the defense.
Yes. The rule applies to any person who manufactures, processes, packs, or holds an FTL food. Holding includes warehousing for a customer. The customer's ownership does not relieve the 3PL of recordkeeping obligation.
January 20, 2026. The rule was finalized in November 2022 and the original date was January 2026; FDA confirmed the deadline through 2025.
FSMA 204 sits under FDA enforcement authority. Violations can result in warning letters, injunctions, seizure of product, or in extreme cases criminal penalties. Operationally, a customer audit failure on FSMA 204 is more likely to cause contract loss than FDA enforcement action.
Paper can satisfy creation and retention, but not the 24-hour sortable-spreadsheet production requirement. You must be able to convert to electronic sortable format on request, which in practice means electronic capture from the start.
Suncoast Cold Systems handles commercial cold-storage and 3PL warehouse refrigeration across Tampa, St. Petersburg, Clearwater, Brandon, Riverview, Temple Terrace, and Wesley Chapel. 24/7 dispatch. Licensed Class A A/C Contractor (FL #CAC1824642), EPA 608 Universal, OSHA 30 Construction. Synthetic-refrigerant systems only — no industrial ammonia.
The other federal compliance regime that applies to every cold-storage rack.
The pharmaceutical cold-chain analog — what GDP requires of a pharma 3PL.
When the rack drops on a 60,000 sq ft freezer — protect product and traceability documentation through the disruption.