FSMA food traceability rule: what restaurants need to know

FDA’s Food Traceability Rule adds recordkeeping for certain foods on the Food Traceability List. Restaurants generally maintain receiving records for covered foods, but may not need transformation records for foods prepared and sold directly to consumers. FDA says it will not enforce the rule before July 20, 2028; existing one-up, one-back records remain in effect.

A new rule layered on existing records

The Food Traceability Rule, sometimes called FSMA 204, adds records for certain foods FDA has placed on the Food Traceability List (FTL). It does not replace the existing one-up, one-back traceability records for foods generally. Covered entities may need key data elements (KDEs) linked to critical tracking events (CTEs), such as receiving, shipping, or transformation. A restaurant manager should distinguish these additional requirements from the current purchase invoices and recall records already used by the operation.

Current compliance timing

The original compliance date was January 20, 2026. FDA proposed moving it to July 20, 2028, and the 2026 continuing appropriations law directed FDA not to enforce the rule before that same date. FDA states it intends to comply with that direction. Treat this as a delayed enforcement/compliance timeline for the added traceability rule, not as cancellation of the rule. Continue the existing records required by other regulations and prepare suppliers, systems, and staff for the upcoming requirements.

Which foods are in scope

The FTL names foods for which additional traceability is required, including some produce, seafood, cheeses, eggs, and nut butters. Scope depends on the specific listed food and its form; a food merely containing an FTL ingredient may or may not be covered depending on whether it remains in the form included on the list. Do not assume that every tomato, cheese, or seafood product is covered or that every menu dish needs a traceability code. Use FDA’s current Food Traceability List and FAQ to assess the ingredient and supply-chain event.

Restaurant receiving records

Restaurants generally must maintain receiving KDEs for FTL foods they receive unless an exemption applies. Many data points will be provided by suppliers. Establish a process for capturing the supplier, product description, quantity, date, lot or traceability lot code where applicable, and source information required by the rule. Keep the record retrievable and connected to invoices or receiving documents. The manager should identify who receives and stores the data, how corrections are recorded, and who can retrieve it during an FDA request.

Direct consumer sales versus shipping to another business

A restaurant that prepares a listed food and sells it directly to consumers generally does not need to keep transformation or shipping KDEs for that consumer-facing activity. If a central kitchen transforms food and ships it to a restaurant or retail business, different records may apply: the central kitchen can be acting as a manufacturer/processor and may have to maintain receiving, transformation, and shipping information. Moving food between separate street-address locations can count as shipping even if both locations belong to the same company.

Exemptions are specific

FDA identifies exemptions, including a small retail food establishment or restaurant based on average annual food value over the preceding three years, adjusted for inflation, and certain direct farm-to-retail situations. A direct farm sale may still require a limited record of the farm’s name and address for a defined period. The exemption applies to an individual establishment and does not automatically cover every location owned by a chain. Do not rely on a franchise-wide assumption; assess each facility and the exact transaction.

Build a practical system before the deadline

Use the transition time to map which FTL foods are received, which supplier documents contain required data, and how records are stored. Test whether staff can locate a product lot quickly and export the relevant information in a sortable format. Train receivers not to discard shipping labels, invoices, or lot codes before records are captured. Coordinate with suppliers about electronic data delivery. The rule generally requires records to be maintained for two years and made available within 24 hours of a request, subject to the rule’s terms.

Traceability during a recall or illness investigation

If FDA or a supplier alerts the restaurant to a suspected food, identify the product and lot, stop use or sale, segregate stock, and follow the recall procedure. Records should help link the source, delivery, storage, prep, and service dates. Traceability does not guarantee that food is safe; it helps narrow the affected lot and act quickly. Preserve original records, note corrections transparently, and cooperate with the regulator. Do not throw away labels or combine lots in a way that destroys supplier identity.

Points to remember

• Use the exact product, source, jurisdiction, and process information rather than relying on assumptions.
• Document controls and escalate unclear or safety-sensitive situations to the person in charge.

Prepare records that can be retrieved quickly

The practical test is whether the establishment can identify what it received and provide the requested information in a usable form. Decide whether records will be kept electronically, on paper, or through supplier systems; assign a person to capture them; and define a backup when that person is absent. Link supplier invoices and lot-code records so staff do not have to search unrelated files during an urgent request. Train receivers to preserve labels and avoid separating a product from its traceability information before the details have been recorded. Conduct a short mock retrieval using a product on the current Food Traceability List: start from a menu item or receiving date, locate the supplier and lot, and measure how long retrieval takes. Fix gaps such as unreadable scans, inconsistent product names, or a missing location identifier. Because FDA may update guidance and the compliance timetable, designate someone to check official updates. Preparation can begin now even though FDA’s current materials describe a delayed compliance date and non-enforcement period.

Prepare records that can be retrieved quickly

The practical test is whether the establishment can identify what it received and provide the requested information in a usable form. Decide whether records will be kept electronically, on paper, or through supplier systems; assign a person to capture them; and define a backup when that person is absent. Link supplier invoices and lot-code records so staff do not have to search unrelated files during an urgent request. Train receivers to preserve labels and avoid separating a product from its traceability information before the details have been recorded. Conduct a short mock retrieval using a product on the current Food Traceability List: start from a menu item or receiving date, locate the supplier and lot, and measure how long retrieval takes. Fix gaps such as unreadable scans, inconsistent product names, or a missing location identifier. Because FDA may update guidance and the compliance timetable, designate someone to check official updates. Preparation can begin now even though FDA’s current materials describe a delayed compliance date and non-enforcement period.