Food Lot Traceability

A lot (also called a batch or lot number) is a discrete quantity of a material or product that was produced or received under uniform conditions. For a raw ingredient, a lot typically corresponds to a single delivery or a single production run at the supplier's facility. For a finished cafe product, a lot corresponds to a single production batch at your cafe. The lot is the fundamental unit of traceability. When you assign a lot number to a bag of flour upon receipt, you are creating a traceable identity for that specific quantity. As that flour is used in production, the lot number follows it. If that bag of flour is later found to be contaminated, the lot number lets you identify exactly which production batches used it, and therefore which finished products may be affected. Without lot-level tracking, a contamination event forces you into a worst-case recall: you must assume all products are potentially affected because you cannot narrow down which ones used the problematic ingredient. With lot-level tracking, you can limit the recall to the specific products that actually used the affected lot, dramatically reducing scope, cost, and customer impact. Lot numbers also enable quality analysis. If customers report that last Tuesday's bread had an off flavor, you can trace back to the specific flour, yeast, and water lots used that day and investigate whether one of them was the cause.

Traceability works in two directions, and you need both. Forward tracing (also called tracing forward or downstream tracing) starts with a raw material lot and follows it forward to every finished product that consumed it. The question forward tracing answers is: "This lot of eggs was recalled by the supplier. Which of our products used those eggs, and which customers received those products?" Forward tracing is what you need during a supplier-initiated recall. Backward tracing (also called tracing back or upstream tracing) starts with a finished product and follows it back to every raw material lot that went into it. The question backward tracing answers is: "A customer reported illness after eating our almond croissants from batch 2024-03-15-001. Which ingredient lots were used in that batch, and which suppliers provided them?" Backward tracing is what you need during a customer complaint or foodborne illness investigation. One-up-one-back traceability means you can trace one step forward to your customer and one step back to your supplier. Full chain traceability means you can trace across the entire supply chain. The FDA's FSMA Section 204 requires specific high-risk foods to maintain more comprehensive traceability records, often referred to as Key Data Elements (KDEs) at Critical Tracking Events (CTEs). For a cafe, the critical tracking events are: receiving raw materials, combining materials in production, and shipping or selling finished products. At each event, you record who, what, when, where, and the lot numbers involved.

The Food Safety Modernization Act (FSMA) fundamentally shifted US food safety regulation from reactive to preventive. Section 204 of FSMA specifically addresses traceability, establishing the Food Traceability Rule (21 CFR Part 1, Subpart S) that took effect in January 2026. The rule applies to foods on the Food Traceability List (FTL), which includes many items relevant to cafes: shell eggs, fresh-cut fruits, nut butters, soft cheeses, and others. If your cafe uses any FTL items, you are subject to enhanced traceability requirements. Key requirements include maintaining traceability records for each Critical Tracking Event. At receiving, you must record the traceability lot code, quantity, unit of measure, product description, and the location from which the food was shipped. During transformation (production), you must record the new traceability lot code for the output product, all input lot codes consumed, the date of transformation, and the location where it occurred. Beyond the FDA, other frameworks apply depending on your market. The EU's General Food Law (Regulation EC 178/2002) requires one-up-one-back traceability. GFSI-benchmarked standards like SQF, BRC, and FSSC 22000 require even more detailed traceability programs. If you sell to large retailers, their vendor requirements often exceed regulatory minimums. Even if your cafe is not currently subject to the strictest requirements, implementing lot traceability now is prudent. Regulations are tightening, customers increasingly expect transparency, and the cost of implementing traceability after a crisis is far higher than building it into your operations from the start.

Implementation begins at receiving. When a delivery arrives, assign a lot number to each distinct material. Many suppliers already print lot numbers on their packaging; you can use those, prefix them with your own identifier, or generate your own internal lot codes. The important thing is that every unit of inventory in your facility has a lot identity. Next, establish lot tracking during production. When a baker begins a batch, the system should record which ingredient lots are being used. This can be as simple as scanning a barcode on each ingredient container, or in smaller operations, selecting lots from a list in your cafe management software. The production batch receives its own lot number, and the system records the linkage between input lots and output lot. Storage and movement tracking ensures that lot identity is maintained through your facility. If flour lot A-2024-0315 is moved from dry storage to the production area, that movement should be recorded. This is especially important for materials that are partially consumed over time: you need to know when a lot was opened, how much remains, and when it was fully consumed. Finally, at the point of sale or shipment, the finished product lot number should be recorded against the customer order. For wholesale customers, this is typically captured on the invoice or packing slip. For retail, it may be captured via the production date printed on the label. The entire chain, from supplier lot to customer delivery, should be traversable in both directions within minutes, not hours or days. The FDA's target for trace-back exercises is 24 hours. Best-in-class operations aim for under one hour.

Having a traceability system is not enough; you must test it regularly. A mock recall (also called a traceability exercise) simulates a recall scenario to verify that your system works and that your team can execute the process under pressure. To conduct a mock recall, select a random raw material lot from your records. Then attempt to trace forward to identify every finished product batch that used it, every customer who received those products, and the quantities involved. Time the exercise. Your target should be to complete the trace within two hours (many standards require four hours, but faster is better). Then do the reverse: select a random finished product batch and trace backward to every ingredient lot and supplier involved. Again, time it. Document the results. Did you identify all affected products? Were there gaps in the chain? How long did it take? What bottlenecks did you encounter? Use the findings to improve your process, update your procedures, and retrain staff as needed. Best practice is to conduct mock recalls quarterly. Some certification standards require them at least annually. Each exercise should test a different product and a different scenario. Over time, your team builds muscle memory and confidence, so that when a real recall happens, the process is routine rather than chaotic. After each exercise, review any gaps with your team. Common issues include missing lot records at receiving, production batches with incomplete ingredient lists, and finished products shipped without lot numbers on packing slips. Address these gaps immediately.