What Is Lot Traceability?

Definition

Lot traceability is tracking a batch of product from supplier through production to customer, so it can be located quickly in a recall.

When a supplier reports a contaminated ingredient, a food company has to answer two questions fast: which of our products used it, and where did those products go? Lot traceability is the record-keeping that makes those answers possible in minutes instead of days.

Forward vs. backward traceability

• Backward traceability (trace back): starting from a finished product lot, identify every ingredient lot and supplier that went into it.
• Forward traceability (trace forward): starting from an ingredient lot, identify every finished product made with it and every customer who received it.

A complete system does both. Together they let a company recall only the affected product instead of everything made in a given week.

Regulatory and retailer requirements

In the U.S., the FDA's Food Traceability Rule under Section 204 of the Food Safety Modernization Act (FSMA) requires companies that handle foods on the Food Traceability List to keep specific records. These include Key Data Elements (KDEs) for Critical Tracking Events (CTEs) such as receiving, shipping, and transformation, along with traceability lot codes. Records must generally be provided to FDA within 24 hours of a request. The compliance date is currently July 20, 2028.

Many retailers and distributors also set their own traceability and recall-readiness requirements for suppliers, often stricter than the regulation.

How ERP handles lot tracking

A modern ERP for food and beverage companies, such as Acumatica, tracks lots as part of everyday transactions rather than in a separate log:

• Receiving: supplier lot numbers and expiration dates are captured when goods arrive.
• Production: each batch records which ingredient lots were consumed and creates a new finished-goods lot.
• Inventory: lots are tracked by location, with first-expired, first-out picking.
• Shipping: each order records the lots sent to each customer.
• Reporting: trace-forward and trace-back reports run from the same data.

Running a mock recall

A mock recall tests whether the system and the team can actually trace a lot under pressure. A typical drill:

1. Pick an ingredient lot or finished lot at random.
2. Trace it backward to suppliers and forward to customers.
3. Account for 100% of the quantity: used, on hand, and shipped.
4. Time the exercise and document gaps.
5. Fix the process, then repeat on a regular schedule.

Learn more about Acumen's ERP services or see ERP implementation.

Example: tracing an ingredient lot

A sauce manufacturer learns that a spice supplier's lot may be contaminated. In the ERP, the quality manager runs a trace-forward report on that lot. It shows the spice went into three production batches, which became four finished-goods lots. Two lots are still in the warehouse and are placed on hold. The other two shipped to six customers, who are contacted the same day.