FSMA 204 Food Traceability Guide for Restaurants

Understanding FSMA 204 and Restaurant Applicability

Does the federal government require restaurants to track every piece of cheese or leaf of romaine lettuce that enters their kitchen? The short answer is yes—but with significant, business-saving exemptions, and a newly extended timeline. The U.S. Food and Drug Administration (FDA) has finalized the Requirements for Additional Traceability Records for Certain Foods, commonly known as FSMA 204 (implementing Section 204(d) of the FDA Food Safety Modernization Act).

Originally scheduled to take effect in January 2026, the compliance and enforcement date has officially been extended to July 20, 2028, following an administrative delay from the FDA and subsequent congressional funding restrictions under the FY2026 appropriations act (P.L. 119-37, Division B). This extension is designed to give the commercial food industry, particularly retail food establishments (RFEs) and restaurants, the necessary time to coordinate with distributors and establish digital or physical recordkeeping frameworks.

This article provides an educational breakdown of how FSMA 204 applies directly to commercial restaurant operations in the United States. It is not intended as formal legal advice, but rather as an operational blueprint to help operators understand their direct compliance obligations.

To understand the regulatory landscape of commercial kitchens, operators must distinguish between direct federal regulations and state or local food safety ordinances. Direct federal laws, such as FSMA 204, apply uniformly across the country to all businesses engaged in manufacturing, processing, packing, or holding food for U.S. consumption. This differs from the FDA Food Code, which serves as a model code—a set of recommendations that has no binding legal power until formally adopted by individual state, county, or municipal health departments. While a restaurant's day-to-day operations are heavily shaped by local health department inspections, the FDA holds direct federal enforcement authority for FSMA 204, allowing federal inspectors (or state inspectors acting under FDA commission) to conduct direct record audits at any retail facility.

Integrating a comprehensive FSMA traceability protocol alongside a restaurant's existing voluntary or mandatory safety plans, such as a [commercial kitchen HACCP plan](/resources/usa-restaurant-haccp-plan-guide), is the gold standard for maintaining active managerial control over biological and chemical hazards.

---

The Food Traceability List (FTL): Is Your Menu Covered?

The additional recordkeeping requirements of FSMA 204 do not apply to all foods. Instead, they are strictly limited to foods listed on the FDA's official Food Traceability List (FTL), as well as any multi-ingredient foods that contain FTL items as ingredients (provided the FTL ingredient remains in the same form, such as fresh, in which it appears on the list).

The FDA designated the FTL using a rigorous risk-ranking model that evaluated various commodity-hazard pairs based on factors like outbreak frequency, severity of illness, and contamination likelihood. For restaurant operators, the following 18 primary categories of FTL foods represent the most common ingredients that trigger compliance:

• Cheeses (other than hard cheeses): Includes fresh soft or unripened cheeses (such as cottage, chevre, cream cheese, mascarpone, ricotta, queso fresco, and queso blanco) and soft-ripened or semi-soft cheeses (such as brie, camembert, feta, mozzarella, monterey jack, and muenster). This category excludes cheeses that are frozen, shelf-stable at ambient temperature, or aseptically processed.
• Shell Eggs: Raw shell eggs from domesticated chickens.
• Nut Butters: All types of peanut and tree nut butters (e.g., almond, cashew, hazelnut). This excludes soy or seed butters.
• Fresh Cucumbers: All varieties of fresh, whole cucumbers.
• Fresh Herbs: All fresh herbs (such as parsley, cilantro, and basil), excluding dill.
• Fresh and Fresh-Cut Leafy Greens: All types of fresh leafy greens (including Romaine, iceberg, spinach, kale, arugula, and chard) and fresh-cut salad mixes. This excludes whole head cabbages.
• Fresh Melons: Whole or cut melons (such as cantaloupe, watermelon, and honeydew).
• Fresh Peppers: All varieties of fresh hot and sweet peppers.
• Fresh Sprouts: All varieties of fresh sprouts (such as alfalfa, bean, and clover).
• Fresh Tomatoes: All varieties of fresh tomatoes.
• Fresh Tropical Tree Fruits: Fresh mango, papaya, guava, lychee, starfruit, and jackfruit. This excludes bananas, citrus, and avocados.
• Fresh-Cut Fruits and Vegetables: Any fresh-cut fruit or vegetable products prepared and sold raw.
• Finfish: Fresh, frozen, or previously frozen finfish, including histamine-producing species (tuna, mahi mahi, mackerel), ciguatoxin-associated species (grouper, snapper), and other species (salmon, cod, trout). This excludes Siluriformes fish (catfish), which fall under USDA jurisdiction.
• Smoked Finfish: Refrigerated, frozen, or previously frozen smoked fish products.
• Crustaceans: Fresh, frozen, or previously frozen shrimp, crab, lobster, and crayfish.
• Molluscan Shellfish (Bivalves): Fresh, frozen, or previously frozen oysters, clams, and mussels (excluding the shucked adductor muscle of scallops). Note that raw bivalves covered by the National Shellfish Sanitation Program (NSSP) may have partial exemptions, but standard restaurants must still track their receiving events.
• Ready-to-Eat Deli Salads: Refrigerated, ready-to-eat deli salads containing FTL ingredients, such as potato salad, macaroni salad, egg salad, or pasta salad. This excludes meat salads.

If your restaurant menu includes none of these FTL items, you are completely unaffected by FSMA 204. However, because almost every commercial restaurant serves fresh tomatoes, shell eggs, soft cheeses (like mozzarella or feta), or fresh salad greens, virtually all non-exempt operations are impacted.

---

Navigating Restaurant Exemptions (Full & Partial)

Recognizing the heavy operational burden that strict traceability places on small businesses, the FDA and Congress established several critical exemptions specifically for retail food establishments and restaurants.

The Small Restaurant Exemption (Full Exemption)

Under 21 CFR § 1.1305(i), any small restaurant or retail food establishment is fully exempt from the requirements of the Food Traceability Rule if its rolling average annual monetary value of food sold or provided during the previous 3-year period is $250,000 or less (adjusted for inflation, with 2020 as the baseline year).

Crucially, FDA guidance clarifies that this sales calculation is performed at the individual location level, not the overall brand, owner, or franchise network level. This means that a specific franchised location of a large national chain might be legally exempt if that individual unit's annual food sales remain under $250,000, even though the parent brand handles billions in annual revenue.

Non-Profit Restaurants (Full Exemption)

Non-profit food establishments, such as charitable kitchens, soup kitchens, or non-profit school cafeterias, are entirely exempt from the rule (§ 1.1305(i)).

Direct-from-Farm Purchases (Partial Exemption)

Under 21 CFR § 1.1305(j), if a restaurant purchases an FTL food directly from a farm, it is exempt from the standard, complex recordkeeping requirements of the rule. Instead, the restaurant must meet a much simpler recordkeeping standard:

1. Document the official name and physical address of the farm.
2. Document the specific types of food purchased from that farm.
3. Maintain these simplified records for 180 calendar days from the date of purchase.

Ad Hoc Purchases between Restaurants (Partial Exemption)

If a restaurant location experiences an unexpected ingredient shortage on a busy Friday night and makes an emergency, ad hoc purchase of FTL food (e.g., buying three cases of Romaine lettuce) from another local restaurant or grocery store outside of its normal purchasing channels, it is partially exempt. The buying restaurant must simply maintain a record of the purchase for 2 years, documenting the product name, quantity, purchase date, and the seller's name and address. This partial exemption also applies to ad hoc transfers between different locations of the same restaurant brand.

The Spreadsheet Threshold (Partial Recordkeeping Exemption)

For restaurants that exceed the $250,000 small operator exemption, their annual food sales dictate the format in which they must keep records:

• The Paper/PDF Tier ($250,01 to $1,000,000): Restaurants with an average annual monetary value of food sold of more than $250,000 but $1 million or less are exempt from the requirement to provide the FDA with an *electronic, sortable spreadsheet* within 24 hours of a request. These mid-sized operators can maintain their records as physical papers, scanned PDFs, invoices, bills of lading, or digital files, provided they are legible, protected from loss, and accessible within 24 hours.
• The Digital Spreadsheet Tier (Over $1,000,000): Large restaurants with more than $1,000,000 in average annual food sales must maintain their records in a format that allows them to generate and provide the FDA with a clean, electronic, sortable spreadsheet within 24 hours of an official request during an outbreak investigation.

---

Key Compliance Activities for Restaurants: CTEs and KDEs

The operational framework of FSMA 204 relies on documenting Critical Tracking Events (CTEs) and capturing their corresponding Key Data Elements (KDEs). While food manufacturers and distributors must track multiple CTEs (such as harvesting, cooling, initial packing, and shipping), a standard restaurant only performs one primary CTE: Receiving.

The Receiving CTE (§ 1.1345)

Receiving is defined as the event in a food's supply chain when food is received by an entity (other than a consumer) after being transported from another physical location. For restaurants, this occurs when a delivery truck pulls up to the back dock and unloads FTL items.

Under § 1.1345, the receiving restaurant must record and maintain the following KDEs for 2 years:

1. Traceability Lot Code (TLC): The unique alphanumeric identifier assigned to that specific batch of food by the initial packer or grower. This is the single most important data element under FSMA 204.
2. Food Quantity and Unit of Measure: The specific amount of food received (e.g., "15 cases," "200 lbs").
3. Product Description: Detailed information about the food, including the brand name, variety, pack size, and packaging type.
4. Previous Supplier Location Description: The business name, physical address, and contact information of the distributor or shipper that sent you the food.
5. Receiving Location Description: The business name, physical address, and contact information of your specific restaurant location where the food was delivered.
6. Date of Receipt: The exact calendar date the delivery was accepted at the restaurant.
7. TLC Source Details: The official identity of the entity that originally assigned the Traceability Lot Code. This must be documented using their FDA Food Facility Registration Number, or a direct web link that provides their physical location address.
8. Reference Document Name and Number: The specific ID of the commercial document associated with the shipment (e.g., invoice number, bill of lading number, or purchase order number).

Restaurants do not need to generate new TLCs. When you receive FTL food, the supplier is legally obligated to send you these KDEs (including the TLC). To ensure compliance, operators must establish clear data sharing protocols with their suppliers, ensuring that TLCs are printed clearly on invoices, advance shipping notices (ASNs), or accessible via an online supplier portal. Furthermore, restaurants are entirely exempt from keeping track of FTL foods once they are prepared, cooked, or served to consumers. You do not need to link TLCs to specific menu items or guest checks.

The Central Kitchen Exception: Transformation and Shipping CTEs

Many restaurant brands utilize a central kitchen, commissary, or preparation facility that processes ingredients and ships them to individual restaurant locations. If your brand operates a central kitchen, that facility is acting as a manufacturer/processor and distributor, meaning it is subject to the Transformation and Shipping CTEs.

• Transformation (§ 1.1350): Occurs when a food on the FTL is changed (e.g., chopped, mixed, cooked, blended, or repackaged) or when a multi-ingredient food is made using an FTL item. A central kitchen must record the TLCs of all incoming ingredients, assign a *new* TLC to the transformed output food, and maintain detailed records of the transformation date, quantity, and location.
• Shipping (§ 1.1340): Occurs when food is transported from one physical location to another. The central kitchen must record the new TLC, the shipping date, quantity, receiving locations, and proactively send these shipping KDEs forward to the receiving restaurant locations.

The individual receiving restaurant locations must then record these incoming TLCs as standard receiving events, maintaining the records for 2 years.

---

Practical FSMA 204 Receiving Log Template

The following simplified spreadsheet layout represents a compliant, sortable log format that a manager of a large restaurant (over $1M in sales) should maintain for incoming FTL deliveries. This format ensures all required Receiving KDEs are linked directly to the Traceability Lot Code:

---

What a Regulatory Auditor Reviews During an Audit

If an FDA inspector or an authorized state/local sanitarian conducts a FSMA 204 record audit at your restaurant, they will specifically review the following elements to verify compliance:

1. The Food Traceability Plan (FTP) (§ 1.1315): Every covered restaurant must maintain a written FTP. The auditor will check that your plan includes:

• A detailed description of the procedures your restaurant uses to maintain required records (including where records are stored and how they are accessed).
• A clear list identifying all FTL foods currently handled or served by your kitchen.
• A description of how your restaurant records and links incoming Traceability Lot Codes to receiving events.
• A designated, current point of contact (and emergency contact) who is responsible for the traceability records and plan.
• If your restaurant grows sprouts on-site, a detailed farm map showing the growing and packing locations.

1. Two Years of Retrospective Records: The auditor will select random FTL shipments from your historical inventory and demand to see the associated receiving KDEs (including TLCs and supplier registrations) for those specific delivery dates.
2. The 24-Hour Response Verification: The inspector will issue a formal data request. Under § 1.1455, you must be able to provide the requested records within 24 hours of the request (or within a reasonable extension agreed to by the FDA). If your restaurant exceeds $1M in food sales, you must provide this data in an electronic, sortable spreadsheet.

---

Common Failures, Corrective Actions, and Evidence

To pass a FSMA 204 audit, managers must establish standard operating procedures (SOPs) to identify receiving failures and implement immediate corrective actions. The table below details common compliance failures, their resolution protocols, and the required evidence records:

To support these records, managers should establish a daily routine of matching delivery invoices against their receiving logs. Incorporating a robust [US restaurant FIFO food rotation checklist](/resources/usa-fifo-food-rotation-checklist) and a strict [FDA date marking system](/resources/usa-restaurant-date-marking-guide) ensures that once FTL ingredients are unboxed and prepped, they are used or discarded within the required 7-day window, preventing the growth of pathogens like *Listeria* and maintaining general food safety.

---

Local Caveats and State/Local Variations

A critical caveat for restaurant operators is that FSMA 204 is a federal regulation, whereas daily health inspections are governed by state, county, or city sanitary codes.

Your local health inspector (often called a sanitarian) conducts inspections based on the local retail food code. If your state is still operating under an older model code (such as the 2013 or 2017 FDA Food Code), local sanitarians may not mention FSMA 204 during their routine visits. However, this does not exempt your restaurant from federal compliance.

The FDA increasingly utilizes State-Federal Partnership Agreements and commissions state inspectors to conduct FSMA-specific audits on behalf of the federal government. This means that a local county inspector might wear two hats: one day checking your [commercial refrigerator temperature logs](/resources/usa-fda-food-code-temperature-guide) under local food code rules, and the next day demanding to see your electronic, sortable FSMA 204 spreadsheet on behalf of the FDA. Operators must prepare for federal traceability audits regardless of their local health code's current adoption status.

---

Streamlining Traceability in Your Kitchen

Manually logging Traceability Lot Codes, previous supplier locations, and FDA registration numbers for every single delivery of cheese, tomatoes, or salmon can quickly overwhelm a busy kitchen team. It is an administrative burden that invites human error, leading to skipped entries, lost papers, and failed audits.

Food Ops provides automated digital tools designed specifically to streamline restaurant operations, manage supplier documentation, and instantly generate FDA-compliant, sortable spreadsheets within seconds. Let us take the complexity out of compliance so your team can focus on what they do best: serving great food.

To see how Food Ops can automate your kitchen's traceability plans, verify your compliance status, and eliminate manual receiving logs, visit Food Ops to schedule a custom demonstration today.

---

Official sources

• FDA Food Safety Modernization Act (FSMA) Final Rule on Requirements for Additional Traceability Records for Certain Foods
• FDA Official Food Traceability List (FTL)
• FDA Small Entity Compliance Guide for the Food Traceability Rule
• U.S. Food and Drug Administration (FDA) Food Code 2022
• National Restaurant Association Food Traceability Guidance and Evaluation Tools