A quality alert arrives Monday morning at 8:30 a.m. A supplier has just flagged a potential defect in an ingredient delivered over the past six weeks. Your question is not regulatory — it is operational: how quickly can you identify every batch of finished product manufactured with that ingredient, list every customer who received it, and block the stock still sitting in your warehouse?
If the answer is “several days,” your ERP is not ready for a product recall. If the answer is “a few hours,” you have probably configured your lot traceability modules correctly. This guide details what your system must be capable of, how to prepare it, and what the four major ERP platforms offer out of the box.
The First 72 Hours of a Product Recall: What Your ERP Must Be Able to Do
Identifying Affected Lots in Real Time: Upstream and Downstream Traceability
Bidirectional lot traceability is the technical foundation of any controlled recall. In a correctly configured ERP, every batch of finished product carries the complete history of its composition: which raw material lot, which component lot, which production date, which equipment, which operator.
Upstream traceability answers the question: “does this finished product batch contain the suspect ingredient?” Downstream traceability answers the inverse: “where are all the finished products that incorporated the problem raw material lot?”
In a recall, both directions are required simultaneously. Upstream defines the technical scope of the problem. Downstream defines the commercial scope: which customers received which products, on which dates, on which delivery notes.
Without native bidirectional traceability in the ERP, this reconstruction is done manually across Excel files, paper delivery notes, and dispatch emails. In practice, that takes days rather than hours, and the recall scope widens by precaution because no one knows exactly what they know.
Mapping Recipients: Delivered Customers, Warehouses, Lots in Transit
Once the affected lots are identified, the ERP must generate a consolidated dispatch list: for each problematic lot, which customers were delivered, which quantities, on which dates, with which delivery note or invoice numbers. This list is the working document for the crisis cell when communicating with customers.
The ERP must also cover lots currently in transit (shipped but not yet received by the customer) and stock still held in your own warehouse or at a distributor. These three situations — already delivered, in transit, in stock — require different actions and must be clearly distinguished in the report.
ERPs that handle advanced logistics (integrated or connected WMS) provide real-time visibility into which warehouse holds each lot, on which pallet, at which location. This level of precision directly reduces the time needed to physically block stock.
Stock Hold: Blocking Lots in Clicks, Not Hours
A lot hold (quality block) must be a fast, traceable operation that is automatically propagated to all downstream processes. In a well-configured ERP, changing a lot status from “available” to “blocked” or “quarantined” is enough for the system to automatically refuse its dispatch, its use in production, and its invoicing.
The typical statuses in industrial ERPs are: available (unrestricted), blocked (cannot be used), in quarantine (awaiting analysis), to be destroyed (confirmed irreversible decision). These statuses have direct implications for automated processes: a “blocked” lot cannot be picked on a manufacturing order, shipped on a sales order, or proposed by planning algorithms (MRP/DRP). This systemic behaviour ensures no operator can inadvertently bypass the hold.
Tracking who changed the status, when, and with what reason is part of the mandatory audit trail for recall files.
The ERP Data You Need Before a Crisis Hits
Lot Numbering and Multi-Level Traceability
Multi-level lot traceability means the ERP maintains the link between: the raw material lot received from the supplier, the semi-finished lot from the first transformation, and the finished product lot delivered to the end customer. Every intermediate level in the bill of materials must be tracked.
This configuration is not automatic in most ERPs: you must explicitly set up lot number management at each BOM level, and activate lot propagation during manufacturing orders. A company that uses lots for finished products but not for raw materials (or vice versa) loses upstream traceability, and with it the ability to answer quickly “which raw materials went into this finished product lot.”
In sectors with strict traceability requirements (food and beverage, pharma, medical devices, automotive), this configuration is non-negotiable and must be verified regularly — not only at initial implementation.
CMMS Integration: Linking the Defective Lot to the Production Sequence
A Computerised Maintenance Management System (CMMS) integrated with the ERP connects a defective lot to the production sequence that generated it: which production line, which equipment, which time window, which operator. This information is essential for root-cause analysis.
When the ERP and CMMS are integrated (or part of the same system), the quality investigation can cross-reference the production log (date and time the lot was manufactured) with maintenance records (last equipment inspection, last sensor calibration, outstanding maintenance alert). This cross-reference typically identifies the technical cause of the problem within hours rather than days.
Without this integration, quality teams must manually interview production and maintenance staff, reconstruct the timeline in a spreadsheet, and hope that the production paperwork for the week in question is still accessible.
Quality Documents Attached to the Lot: Certificates of Analysis and Test Results
Every raw material lot received from a supplier should be accompanied by a Certificate of Analysis (CoA) certifying its compliance with specifications. In a well-configured ERP, this certificate is attached to the lot at goods receipt, accessible from the lot record, and exportable in seconds for inclusion in the recall file.
Similarly, quality control results performed during production or on the finished product (physicochemical analyses, microbiological tests, dimensional checks) should be attached to the corresponding lots. During a recall, the internal or external investigator will systematically request these documents: being able to provide them in real time shortens the investigation and reduces legal risk exposure.
The QMS Module in Crisis Management
Auto-Opening a Major Non-Conformance from the Lot Alert
An integrated QMS (Quality Management System) module allows the ERP to automatically open a Non-Conformance Record (NCR) as soon as a lot alert is triggered. This non-conformance inherits the lot data: lot number, quantity, supplier, dates, associated test results.
The distinction to master is between an internal non-conformance (detected before delivery, handled internally with no visible customer impact) and an external recall (consumer safety recall, involving customer communication and potentially a regulatory notification). Both are opened as NCRs in the ERP, but their validation workflows, their recipients, and their traceability obligations differ.
For an external recall, regulatory obligations vary by sector: the EU GPSR Regulation (EU) 2023/988 requires notification via the Safety Business Gateway for general consumer products, while the food, pharmaceutical, and medical device sectors have their own notification channels. Our dedicated article on ERP and GPSR covers these obligations in detail.
CAPA Plan Linked to the Recall: Corrective Actions, Deadlines, Owners
The CAPA (Corrective and Preventive Actions) plan is the operational management document once the scope is identified. It lists every action to take: stock hold, customer communications, product withdrawal, root-cause investigation, production process changes.
In an ERP with a QMS module, the CAPA is linked to the NCR and follows its own lifecycle: open, in progress, verified, closed. Each action is assigned to an owner, with a deadline and a progress status. This traceability prevents blind spots (an action that “no one got around to”) and constitutes the documentary proof that the company managed the recall in a structured way — something a regulatory auditor or insurer may request.
Supplier Communication: Follow-Up and Alternative Qualification
A recall triggered by a supplier problem requires a parallel process on the procurement side: notifying the supplier, suspending current orders for the suspect component, launching a supplier investigation (8D or equivalent), and identifying an alternative supplier if the component is critical.
The ERP allows you to export the list of open orders for that supplier and component, issue a Supplier Non-Conformance Report (SNCR) from the QMS module, and switch future procurement to a substitute supplier during the investigation. All these actions are tracked in the supplier record and the component history.
What SAP, Dynamics 365, Odoo and Sage X3 Offer Natively
SAP S/4HANA: Batch Where-Used and QM for Cross-Border Recalls
SAP S/4HANA has a native feature called Batch Where-Used that reconstructs the complete traceability of a lot in all directions within minutes: which raw materials contributed to this finished product lot, and in which finished products was this raw material lot incorporated. This traceability crosses BOM levels, production sites, and group entities.
The QM (Quality Management) module manages lot statuses (unrestricted, quality inspection, blocked), inspection orders linked to lots, and quality certificates. For cross-border recalls involving customers in multiple countries, SAP Global Trade Services (GTS) can be activated to manage regulatory communications with customs authorities and product safety agencies in each country.
Microsoft Dynamics 365 SCM: Item Tracing and Quarantine Orders
Dynamics 365 Supply Chain Management offers Item Tracing, accessible from the quality management menu, which allows you to trace an item or lot in both directions (upstream and downstream) through all recorded transactions: receipts, manufacturing orders, shipments, transfers.
Quarantine Orders physically block a lot or item in a dedicated quarantine area, with status management and an audit log. Quality Associations allow you to automatically trigger a quality inspection order for any lot received from a specific supplier or any finished product lot from a given process, reducing the risk of a non-conforming lot slipping through quality control.
Odoo 17-18: Bidirectional Lot Tracking and Quality Alerts
Odoo has a native lot traceability module activable per product. In versions 17-18, bidirectional tracking (upstream and downstream) is available from the lot record via the “Traceability” button. The graphical interface displays the complete tree of stock moves associated with the lot.
Odoo’s Quality module enables you to create quality control points on manufacturing or receipt operations, trigger Quality Alerts that block production or delivery pending validation, and manage non-conformances with an approval workflow. Automatic lot blocking on alert is configured through quality rules and trigger actions.
Sage X3: Multi-Level Lot Numbers and Quality Block
Sage X3 (rebranded as Sage X3 by Acumatica) manages lot numbers at every BOM level and maintains manufacturing links between lots, enabling multi-level upstream-downstream traceability. The quality block (status “Blocked” on a lot) applies automatically to all transactions: a blocked lot cannot be shipped, picked on a production order, or sold.
Multi-site management is native: in a group with several plants, a lot blocked at headquarters is visible and blocked across all sites. This consistency is critical for multi-site businesses operating under a single legal entity with stock flows between sites.
Simulating a Recall Before It Happens: The ERP Crisis Drill
Test Data and Recommended Scenarios
An ERP product recall drill involves selecting a fictitious lot or a real low-value lot, simulating a quality alert, and measuring the time needed to produce the complete list of affected finished product lots and delivered customers.
The recommended scenario: a raw material lot received six weeks ago, incorporated into three different finished products, delivered to fifty customers across two countries. The goal is to verify that the ERP can reconstruct this scope in under four hours, autonomously, without calling the logistics or production teams.
The drill must also test the blocking process: hold the stock lots, verify that open orders on those lots are blocked, and confirm that no stock movement is possible on the blocked lots.
Drill KPIs: Tracing Time and Coverage Rate
The two key indicators of a recall drill are:
- Full tracing time: elapsed time between the initial alert and the production of the exhaustive list of affected lots and delivered customers. The commonly accepted benchmark in food and beverage and pharma is under four hours. Beyond that, the recall scope tends to widen by precaution.
- Lot identification coverage rate: the proportion of genuinely affected lots that the system identified during the simulation. A rate below 100% reveals traceability gaps (unnumbered lots, manufacturing operations not recorded in the ERP, off-system stock transfers).
Both indicators should be documented and shared with the quality management team. They constitute proof that traceability is operational, not merely configured.
The 3 Most Common Gaps Found During Drills
Gap 1: off-ERP stock movements. Transfers between warehouses or customer returns managed manually, without entry in the ERP, create holes in traceability. The lot “believes” it is in warehouse A when it is physically in warehouse B or with a carrier.
Gap 2: lot traceability enabled for finished products but not for raw materials. Without lot numbering on raw materials, upstream traceability stops at the finished product. The business can identify which customers received which finished products, but cannot trace back to the supplier ingredient or its receipt date.
Gap 3: untracked Work-in-Progress (WIP). Lots in the middle of production (semi-finished goods awaiting the next step) are sometimes not recorded in the ERP in real time. During a recall, these in-progress lots are invisible to the system: they appear neither in stock nor in shipments. Their identification then depends on the paper production sheets held by shop-floor teams.
10 Checkpoints to Verify Your ERP Is Ready for a Recall
- Lot numbering is active at every BOM level: raw material, semi-finished, finished product.
- Bidirectional traceability works: the ERP can start from a raw material lot and list all finished products that incorporated it, and vice versa.
- The quality block propagates automatically: a blocked lot cannot be shipped, picked on a production order, or invoiced, with no manual override possible.
- All stock movements pass through the ERP: transfers, customer returns, inventory adjustments.
- Supplier certificates of analysis are attached to receipt lots and accessible from the lot record.
- Manufacturing orders record the consumed component lots in real time, not retrospectively.
- An NCR can be opened directly from a lot record, with automatic inheritance of lot data.
- The dispatch list by lot is exportable in under 5 minutes: customers, quantities, dates, delivery note numbers.
- Lot statuses are shared across all group sites in real time.
- A fictitious recall drill has been conducted within the last 12 months, with documentation of the tracing time and coverage rate.
These 10 points do not cover all sector-specific regulatory obligations (GPSR, Regulation (EC) 178/2002 for food, GMP for pharma), but they constitute the operational minimum for a recall to be orchestrated within the first 72 hours.
To explore the regulatory and quality dimensions further, read our ERP and GPSR guide on Safety Gate notification obligations, our complete ERP and QMS guide on non-conformances and CAPA, and our food and beverage ERP comparison on lot traceability in food processing and agriculture.
