FSMA 204

The specific points in the supply chain where FSMA 204 requires the capture of Key Data Elements (KDEs). These events include:

• Harvesting: Initial acquisition of raw food commodities
• Cooling: Initial temperature reduction of a raw agricultural commodity
• Packing: Placing food into a container for the first time
• Transforming: Changing a food product's state (e.g., cooking, commingling)
• Shipping & Receiving: Transfer of physical possession between entities

Each CTE triggers a mandatory record creation event, forming the backbone of the traceability lot code linkage.

The specific pieces of information that must be captured and shared at each Critical Tracking Event. FSMA 204 mandates a standardized set of KDEs to ensure interoperability across disparate systems:

• Traceability Lot Code (TLC): A unique identifier assigned to a specific batch or lot
• Product Description: The standardized name and variety of the food
• Quantity and Unit of Measure: The amount of product involved in the event
• Location Identifier: The physical address and GPS coordinates where the event occurred
• Date and Time: The precise timestamp of event completion
• Reference Document Number: Links to bills of lading, purchase orders, or invoices

This structured data schema is designed to be machine-readable for rapid electronic sorting during a recall.

The universal connector that links all KDEs across the supply chain. A TLC is a unique alphanumeric identifier assigned at the initial packing or transforming event that remains associated with the food throughout distribution. Key characteristics:

• Persistence: The TLC must remain unchanged as the product moves through different entities
• Granularity: Defined at the lot level, not the individual item level, unless the food is on the Food Traceability List (FTL) as a high-risk item
• Linking Mechanism: Receivers must record the TLC of incoming product and link it to any new TLCs they generate during transformation

The TLC is the primary query key that the FDA will use to request a Traceability Lot Code Record within 24 hours of a formal request.

A specific list of foods for which additional traceability records are required under FSMA 204. The FDA created this list based on a Risk-Ranking Model that evaluated foods based on:

• Frequency of Outbreaks: Historical association with foodborne illness
• Severity of Illness: Potential for hospitalization or death
• Contamination Probability: Likelihood of microbial or chemical contamination
• Consumption Patterns: Volume and demographic exposure

Current FTL items include:

• Leafy Greens: Fresh and fresh-cut lettuce, spinach
• Melons: Cantaloupe, honeydew, watermelon
• Tomatoes: Fresh market tomatoes
• Finfish: Tuna, mahi-mahi, snapper (histamine risk)
• Shell Eggs: Raw, unpasteurized eggs
• Nut Butters: Peanut butter and tree nut butters

Entities handling only non-FTL foods are exempt from the rule's recordkeeping requirements.

The mandatory output format for providing traceability records to the FDA within 24 hours of a request. The agency requires an electronic, sortable spreadsheet that allows rapid filtering and pivot analysis. Technical requirements:

• Format: Must be a native spreadsheet format (e.g., .xlsx, .csv) not a scanned PDF or image
• Sortability: Every KDE column must be independently filterable and sortable
• Flat Structure: Data must be presented in a single, denormalized table linking all CTEs by TLC
• Rapid Retrieval: Systems must be capable of isolating a specific lot's entire chain of custody within the 24-hour window

This requirement effectively mandates digitization of supply chain records, as paper-based systems cannot meet the 24-hour electronic sort and submission deadline.

While FSMA 204 does not explicitly mandate temperature monitoring, the Traceability Lot Code provides the backbone for linking cold chain telemetry to specific lots. Integrating IoT sensor data with FSMA 204 records enables:

• Conditional Acceptance: Automatically rejecting lots that experienced temperature excursions during transit
• Dynamic Shelf-Life: Adjusting expiration dates based on actual thermal history rather than static assumptions
• Root Cause Isolation: Pinpointing the exact CTE and location where a cold chain break occurred

Best practice involves embedding IoT sensor identifiers as reference document numbers within the KDE schema, creating an auditable link between the product's thermal history and its traceability record. This integration transforms compliance data into a proactive quality assurance asset.