FSMA 204 in the WMS: CTE × KDE Matrix, TLC Rules, and FDA Export Guide

Points essentiels à retenir

• FSMA 204 codifies seven critical tracking events, and growing is not one of them.
• A WMS must preserve the regulatory traceability lot code across routine warehouse movements and shipping.
• Shipping and standard receiving each require eight KDEs linked to the relevant traceability lot.
• All required records are subject to the 24-hour availability rule, but not every request requires a sortable spreadsheet.
• Supplier, processor, 3PL, WMS, MES, ERP, and EDI data must reconcile without manual reconstruction.

What does FSMA 204 currently require, and which dates should warehouses monitor?

The codified FSMA 204 compliance date remains January 20, 2026. FDA proposed moving it to July 20, 2028, but that proposal had not been finalized as of September 16, 2026. Separately, federal appropriations provisions restrict the use of covered funds for enforcement before July 20, 2028.

Separate the legal compliance date, FDA’s proposed extension, and appropriations-based enforcement restrictions

The Food Traceability Rule was published on November 21, 2022. It requires covered persons that manufacture, process, pack, or hold foods on the Food Traceability List to maintain key data elements, or KDEs, for specified critical tracking events, or CTEs. FDA explains that the rule covers domestic firms and foreign firms producing food for U.S. consumption in its current Food Traceability Rule overview.

The dates represent different legal concepts and should not be merged in a WMS project plan:

For our WMS projects, Generix recommends treating enforcement timing as a governance watchlist rather than a reason to pause data design. Supplier onboarding, lot lineage, location master data, reference-document mapping, retention, and export testing require coordination across organizations and cannot be created reliably after an FDA request arrives.

Dated watchlist: the FDA rulemaking docket and the December 11, 2026 federal funding checkpoint

Warehouse, legal, and food-safety teams should monitor two independent tracks: whether FDA finalizes, changes, or withdraws the proposed compliance-date extension, and whether Congress replaces or continues the applicable funding conditions after December 11, 2026. The checkpoint is an editorial planning inference, not a statement that the statutory or regulatory compliance date changed.

Section 770 also appears in the June 4, 2026 House text of H.R. 8646, but the measure had not been enacted as of September 16, 2026. It must therefore remain in a legislative watchlist, not in the WMS rules engine as current law.

FSMA 204 CTE × KDE matrix for WMS design

FSMA 204 codifies seven CTEs: harvesting, cooling before initial packing, initial packing, first land-based receiving, shipping, receiving, and transformation. A WMS may create receiving and shipping records directly, depend on upstream CTE records, and exchange transformation records with an MES or production system.

The seven codified CTEs and the records a warehouse may create, receive, or depend on

The current 21 CFR Part 1, Subpart S reviewed September 16, 2026 defines the seven events and their KDEs. Growing is not a CTE, although a traceability plan may require farm maps and other farm-related information.

This execution view complements our detailed WMS definition: the issue is not what a WMS is, but how regulatory events and partner records become governed warehouse transactions.

The eight shipping KDEs and eight receiving KDEs that must stay linked to each traceability lot

Under 21 CFR 1.1340(a), the eight shipping KDEs are the TLC; quantity and unit of measure; product description; immediate subsequent recipient location; ship-from location; shipping date; TLC source location or source reference; and reference document type and number. The shipper must provide elements one through seven to the immediate subsequent recipient, excluding the transporter.

Standard receiving under 21 CFR 1.1345(a) also has eight KDEs: TLC; quantity and unit of measure; product description; immediate previous source location; receiving location; receiving date; TLC source location or source reference; and reference document type and number.

Our recommended design links each shipping or receiving event to one or more traceability-lot records rather than storing a single free-text lot on the order header. An inbound ASN can prepopulate KDEs, but receipt confirmation should validate the actual quantity, date, facility, partner, TLC, and source reference before the record becomes exportable.

Where must the traceability lot code be assigned and preserved?

A new TLC is normally assigned only at initial packing, first land-based receiving of seafood, or transformation. Routine receiving, storage, pallet movement, picking, and shipping should preserve the existing regulatory TLC unless Subpart S expressly provides an exception.

The three assignment triggers: initial packing, first land-based receiving, and transformation

Section 1.1320(a) establishes three normal assignment triggers:

• Initial packing of a non-seafood raw agricultural commodity on the Food Traceability List.
• First land-based receiving of covered seafood directly from a fishing vessel.
• Transformation of a covered food, which creates an output traceability lot linked to applicable input TLCs, descriptions, and quantities.

A warehouse can perform a transformation depending on the activity, not the department name. Repacking or handling that creates a new traceability lot must be assessed with the food-safety and regulatory team. Generix recommends documenting this decision in transaction rules and acceptance tests rather than letting operators choose an event type informally.

Exceptions at receiving and why shipping must not create a replacement TLC

Section 1.1320(b) says other activities, including shipping, must not establish a new TLC except where Subpart S provides otherwise. One specific receiving rule applies when covered food comes from a person to whom Subpart S does not apply: if no TLC has already been assigned, the receiver assigns one, except when the receiver is a retail food establishment or restaurant.

A WMS may still create an internal lot, license plate, pallet ID, or inventory status. That identifier does not replace the regulatory TLC. At shipment, the WMS must retrieve and communicate the TLC assigned by the TLC source. Our design reviews therefore test split pallets, consolidation, replenishment, cross-docking, returns, and intracompany transfers for accidental TLC overwrites.

How should a WMS model FSMA 204 traceability data?

The TLC should be a distinct, governed regulatory object, linked to CTE records, products, quantities, locations, partners, and source documents. It should not be overloaded into a supplier-lot, ERP-batch, pallet, or license-plate field whose value can change during ordinary warehouse execution.

Separate the regulatory TLC from supplier lots, ERP batches, license plates, pallets, and internal tracking codes

A robust model preserves both identity and relationships:

• The regulatory TLC identifies the traceability lot within the TLC source’s records.
• A supplier lot or ERP batch supports commercial and production processes but may not have the same assignment logic.
• A license plate or pallet ID identifies a handling unit that may contain multiple lots or be rebuilt repeatedly.
• An internal tracking code can support local operations, provided the original TLC remains available and communicable.
• The TLC source location or source reference must resolve to controlled location information rather than an ungoverned note.
• Reference-document type and number should point to records such as an ASN, bill of lading, purchase order, work order, invoice, batch log, or database record.

This model depends on timely transaction data. Our guide to real-time data in WMS operations explains the broader execution context; for FSMA 204, timeliness must also be combined with lineage, retention, and controlled corrections.

Maintain transformation lineage and partner references without imposing case serialization or EPCIS

For transformation, the data model needs a many-to-many relationship between input traceability lots and each output lot, including the quantity consumed from every applicable input. A single flattened batch field cannot reliably represent mixing, partial consumption, or multiple outputs.

FSMA 204 does not prescribe a specific recordkeeping technology. FDA’s Food Traceability Rule FAQs state that EPCIS is an optional interoperability approach, not a compliance requirement. In addition, 21 U.S.C. 2223(d)(1)(L)(iii) bars FDA from imposing a product-tracking requirement to the case level.

EDI, APIs, spreadsheets, labels, and portals can all contribute to the record chain. Our EDI network supports 300+ active interconnections across 50 countries, helping suppliers, processors, customers, and 3PLs exchange governed partner data. This collaborative approach is particularly relevant when Canadian or Mexican entities supply or handle foods destined for U.S. consumption: FSMA 204 is not their domestic rule, but covered U.S. food flows can depend on their data.

How can the WMS produce the 24-hour FDA record package and conditional sortable spreadsheet?

All required records must generally be available within 24 hours, but a sortable spreadsheet is conditional. The export process should first evaluate the FDA request context and entity thresholds, then generate the required records, explanations, and filters from governed source data.

Apply the request-context and entity-threshold gates before selecting the export format

Under 21 CFR 1.1455(c)(1), required records must be made available within 24 hours of an authorized FDA request, or within another reasonable time agreed by FDA. The electronic sortable spreadsheet requirement applies when FDA makes the public-health request described in section 1.1455(c)(3), including situations involving outbreak mitigation, recall implementation, or another threat to public health.

Before selecting a format, the export workflow should evaluate:

• whether the request invokes the public-health circumstances in section 1.1455(c)(3);
• which foods, date ranges, TLCs, facilities, and CTE records FDA specified;
• whether the requested information falls within sections 1.1325 through 1.1350; and
• whether the responding entity belongs to a category allowed to use another format.

Those categories include qualifying farms at no more than $250,000, qualifying retail food establishments or restaurants at no more than $1 million, and qualifying other persons at no more than $1 million. The regulation uses rolling previous-three-year calculations and inflation adjustments from a 2020 baseline.

Generate CTE-specific rows, KDE columns, code explanations, and source references from governed data

The output should identify each CTE and place the associated KDEs in sortable columns while preserving the link to the relevant traceability lot. It should also include information needed to understand internal or external codes, glossaries, abbreviations, record relationships, and source references.

FDA provides an electronic sortable spreadsheet template with sample data, but use of that specific template is not mandatory. Our preferred architecture separates a reusable regulatory dataset from the presentation format, allowing the same governed records to populate the requested spreadsheet or another permitted package.

Records must generally be retained for two years from creation or receipt. Export logic should therefore query current and archived WMS, ERP, MES, and partner records without breaking the relationships among TLCs, CTEs, locations, quantities, and reference documents.

Test retrieval, filtering, reconciliation, English-language output, and secure submission without manual reconstruction

A warehouse should run scenario-based tests before relying on the export:

• retrieve records by TLC, product, date range, supplier, customer, and facility;
• reconcile received, transformed, held, and shipped quantities without assuming they will always balance exactly;
• explain internal codes and maintain English-language output or provide an English translation when requested;
• verify that archived and offsite records remain accessible from the facility within the required period;
• apply role-based access, approval, and audit controls before release; and
• submit through the secure method specified for the FDA request.

Manual spreadsheet reconstruction creates delay and introduces uncontrolled joins. Generix favors an export service that reads governed execution and integration data, logs the request scope and filters, produces a reviewable package, and records approval without changing the underlying CTE history.

FSMA 204 WMS implementation checklist for warehouses and 3PLs

Implementation should be organized around data ownership, partner contracts, and executable acceptance tests, not a generic recall drill. A 3PL may maintain records for another entity, but each covered party remains responsible for ensuring that its required records can be retrieved and provided.

Assign data ownership and acceptance tests across suppliers, processors, 3PLs, customers, WMS, ERP, MES, and EDI teams

Use the following checklist to move from regulatory interpretation to warehouse execution:

• Scope foods and entities: identify applicable Food Traceability List flows, facilities, legal entities, exemptions, and partial exemptions.
• Map CTEs: determine which facilities harvest, cool, initially pack, first receive seafood on land, ship, receive, or transform food.
• Map every KDE: assign a system of record, owner, validation rule, retention rule, and exception process.
• Protect the TLC: prevent receiving, palletization, relocation, replenishment, picking, and shipping from replacing it with an internal code.
• Govern transformation: define which repacking or processing activities create a new lot and preserve input-to-output lineage.
• Onboard partners: specify mandatory inbound ASN or document fields, outbound data, acknowledgments, and rejection handling.
• Test 3PL segregation: preserve owner, facility, customer, product, TLC, and source references across shared inventory and systems.
• Build conditional exports: distinguish the general 24-hour record package from the public-health sortable-spreadsheet condition and threshold exceptions.
• Retain evidence: test two-year retrieval, controlled corrections, audit history, code explanations, and English-language output.
• Monitor legal status: recheck the FDA docket and federal funding position before publication, go-live, and each compliance review.

Our food and beverage WMS checklist provides additional operational criteria. For FSMA 204 specifically, our Solochain WMS capabilities include lot and batch tracking, integrated WMS-MES processes, item traceability reporting, and item recall reporting. These capabilities support data readiness but do not, by themselves, constitute automatic legal compliance.

We invite warehouse, integration, food-safety, and 3PL teams to request an FSMA 204 data-readiness workshop. Together, we can map existing receiving, transformation, shipping, partner-onboarding, and FDA export processes around our Solochain WMS and our EDI solutions, without assuming that software replaces legal analysis or guarantees compliance.

En résumé

• The codified rule, proposed extension, and enforcement-funding restrictions must remain separate in project documentation.
• TLC preservation is a cross-system control spanning inbound partner data, warehouse execution, transformation, and outbound communication.
• A relational CTE and KDE model is more reliable than storing traceability data in free-text order or batch fields.
• The FDA export should be generated from governed records only after request-context and threshold checks.
• Collaborative WMS, MES, ERP, and EDI governance reduces dependence on manual traceback reconstruction.