Skip to main content
World's First AI B2B Platform

FSMA 204 Operations

FSMA 204 Checklist: Map CTEs, KDEs, and Traceability Lot Codes

An operational checklist for mapping covered foods, Critical Tracking Events, Key Data Elements, traceability lot codes, plans, exports, and exceptions.

By BoxNCase Editorial · November 20, 2026

FSMA 204 readiness becomes manageable when the work is organized around actual product flows. The Food Traceability Rule requires additional records for certain foods, using Critical Tracking Events (CTEs), Key Data Elements (KDEs), and traceability lot codes as core concepts.[1] A generic traceability software purchase is not the same as mapping those requirements to receiving, transformation, and shipping operations.

This checklist is a project framework, not a determination that a business or product is covered. Use the official rule, FDA guidance, and qualified advice for scope and legal interpretation.

1. Create a product scope register

List every food and ingredient that could intersect the Food Traceability List. Record SKU, product description, supplier, form, process, and the source used for the scope decision. Add a field for exemption or modified-requirement analysis and an accountable owner.

Do not classify only at the category level. “Cheese,” “seafood,” or “produce” can be too broad for a reliable decision. Preserve the specific product facts. Review private-label, kit, prepared, transformed, and ingredient-containing products separately.

Evidence to retain: source URL, source date, reviewer, decision, rationale, and next review date.

2. Draw the physical flow

Map what actually happens from supplier to customer. Include receiving docks, cross-docks, storage locations, repacking, transformation, case breaking, lot commingling, relabeling, transfers, shipping, returns, and disposal. Identify where the business takes possession and where it creates a new lot or product relationship.

Use interviews and floor observation, not only application diagrams. Warehouse staff may perform steps that are absent from the official procedure. A traceability model that misses relabeling or transformation will produce incomplete event history.

3. Identify the applicable CTE at each step

For each flow step, determine whether it corresponds to a Critical Tracking Event under the rule. CTEs can include harvesting, cooling, initial packing, first land-based receiving, shipping, receiving, and transformation depending on the actor and product.[1]

Create a matrix with one row per event type and columns for facility, system, operator role, trigger, required records, and exception path. If a step is not a CTE, document why it still matters operationally or why it is outside the rule mapping.

4. Map KDEs to the moment they are known

For every applicable event, list the required Key Data Elements and identify the first reliable source. Supplier identity may come from a purchase order, lot information from a label or advance ship notice, quantity from receiving, and timestamp from the warehouse system.

Capture data where it originates. Reconstructing an event from invoices after the fact can lose time, location, lot, or transformation context. If one KDE depends on manual entry, define validation and an exception queue.

Control question: Can the system distinguish “missing,” “not applicable,” and “not yet received”? A blank field should not carry three meanings.

5. Protect traceability lot codes as exact identifiers

Treat a traceability lot code as a string. Preserve leading zeros, punctuation, spaces where valid, and original case. Avoid spreadsheet conversions and barcode parsers that alter the value. Store the scanned value and, where useful, the raw barcode data separately.

Link the lot code to product, event, quantity, location, and source information. Do not assume the code is globally unique outside that context. Define how corrections are made without erasing the original value.

6. Map transformation and commingling

Transformation creates parent-child relationships between inputs and outputs. The data model should show which source lots contributed to which output lots, the event time, location, quantities, and responsible process. If lots are commingled, document how the business preserves the required linkage.

Test difficult scenarios: partial use of a lot, rework, repacking, returns to stock, damaged cases, and a finished item that draws from several ingredient lots. These are where simplistic one-lot-per-order models fail.

7. Write the traceability plan from the system map

FDA describes traceability plan requirements that include procedures for maintaining records, procedures for identifying foods on the FTL, procedures for assigning traceability lot codes when applicable, a point of contact, and additional farm map information where relevant.[1]

The plan should name real systems and fallback methods. State who resolves missing KDEs, who can approve corrections, how supplier data is escalated, and how records are produced. Version the plan and record training.

8. Build and test record exports

FDA's FAQ says covered entities do not routinely submit records, but FDA may request them, including in an outbreak investigation, and may request a sortable spreadsheet in some cases.[2] Build an export that preserves field meaning, identifiers, time zones, and source references.

Run a drill with a product, lot, and date range. Ask a team that did not build the export to interpret it. Measure time to assemble, missing records, ambiguous columns, duplicate events, and inaccessible attachments. Keep the drill result and remediation owner.

9. Validate trading-partner exchange

Define how suppliers and customers provide or receive required information. EDI, APIs, portals, EPCIS, spreadsheets, and labels can all participate. GS1 EPCIS is a standard for sharing visibility event data, but using the standard does not automatically map every required KDE or exemption.[3]

Test malformed files, missing lots, duplicate shipments, revised advance notices, and partner outages. Quarantine exceptions instead of silently accepting incomplete data.

10. Prepare for system outages

Traceability obligations do not disappear when a warehouse system is unavailable. Create controlled offline forms with exact field definitions. Number or otherwise track records, protect them from alteration, and define how they are entered and reconciled when systems return.

Include traceability continuity in cyber and disaster exercises. A restored database may still be incomplete if the business processed shipments manually during the outage.

11. Track the current timeline accurately

FDA's official page says it proposed extending the compliance date to July 20, 2028, and that Congress directed FDA not to enforce before that same date.[1] Treat the extension as proposed rulemaking plus a non-enforcement direction, not as permission to stop implementation. Supply-chain data changes require partner coordination and repeated testing.

Definition of ready

A readiness claim should mean the scope register is reviewed, CTE/KDE matrix is complete, exact lot handling is tested, transformation links work, the traceability plan matches operations, partner exchanges are validated, and a records drill succeeds with documented exceptions. Software installation alone is not readiness, and no checklist can guarantee compliance.