How forward and backward lot tracing works in a distribution ERP, and why it matters for food safety audits, supplier recalls, and customer protection.
Lot traceability is the ability to track a specific batch of product from the moment it enters your facility through every step of storage, production, and distribution until it reaches the final customer. For food distributors, bakeries, and any business handling perishable or regulated products, lot traceability is not optional. It is required by food safety regulations, expected by customers and auditors, and essential for protecting your business when a supplier issues a recall or a customer reports a problem.
Despite its importance, many distributors handle lot tracking manually — in spreadsheets, on paper logs, or through memory. This approach works until it doesn't, which is usually during an audit or a recall, when the stakes are highest and the time pressure is most intense. An ERP system with built-in lot traceability makes these high-pressure moments manageable by keeping the trail intact as a byproduct of normal daily operations.
Forward tracing starts with a specific lot of incoming material and follows it through every downstream step. For example: a flour supplier notifies you that lot FL-2026-0325 may be contaminated. Forward tracing answers the question "where did this flour go?"
In Ask the Ledger, you select the lot, click Trace with direction set to Forward, and the system shows every manufacturing order that consumed flour from that lot, every finished product lot that resulted from those manufacturing orders, and every customer shipment that included those finished products. The result is a tree view showing the complete chain from ingredient to customer, with quantities at each step.
This trace should take seconds, not hours. Auditors and regulators expect you to produce a recall trace quickly. If it takes your team a day to assemble the information from spreadsheets and paper records, you fail the audit — not because the data doesn't exist, but because it isn't accessible under pressure.
Backward tracing starts with a customer complaint or a finished product lot and works upstream. A customer reports a problem with a batch of cheese danishes. Backward tracing answers the question "what went into this product and where did those ingredients come from?"
Select the finished product lot, click Trace with direction set to Backward, and the system shows the manufacturing order that produced it, every ingredient lot consumed in that production run, and the supplier and receiving details for each ingredient lot. This identifies whether the issue is isolated to one ingredient, one supplier, or one production run — information that determines the scope of any corrective action.
Effective lot traceability requires data capture at specific operational moments. The ERP should record lot information automatically during these transactions without requiring separate data entry:
When a recall is necessary, the system should generate a recall packet that includes all affected lots (ingredient and finished product), all manufacturing orders involved, all customer shipments affected, and customer contact information for notification. Ask the Ledger includes Mark Recall, Recall Packet, and Hold Lots functions directly on the lot traceability screen. The recall packet exports as HTML for immediate review or regulatory submission.
The hold function is equally important. When a lot is placed on hold, the system prevents it from being used in production or shipped to customers until the hold is released. This quarantine capability stops the problem from growing while the investigation is underway.
Lot traceability and expiration tracking work together. Every lot has a received date and an expiration date. The system can generate reports showing all lots expiring within a configurable window (7, 14, or 30 days) so that production planning can prioritize using near-expiry ingredients and sales teams can discount near-expiry finished goods rather than writing them off.
FEFO (First Expiry, First Out) inventory logic ensures that the oldest stock is used first during both production and shipping. This is a food safety requirement that reduces waste and prevents the common scenario where newer stock gets used while older stock expires in the back of the warehouse.
Lot traceability is one of those features that seems optional until you need it urgently. Evaluate it during the ERP selection process, not after implementation. Ask vendors to demonstrate a full forward and backward trace with real data, including the time it takes to produce a recall packet. For Ask the Ledger's approach, see ERP for Bakeries and ERP for Food Distributors.