A recall notice arrives. Nobody knows which customers received the affected batch — and the clock is already running.
When a food safety regulator issues a recall notice — or a customer flags a quality issue with a specific batch — the manufacturer has hours, not days, to identify every unit of affected product in the supply chain and initiate a withdrawal. The information needed to do this sits across three or four systems: raw material GRNs in the ERP, production batch records in the MES or paper traveller, finished goods dispatch records in the WMS, and customer delivery confirmations in the sales system.
Assembling this picture manually — tracing a raw material lot through production into finished goods and out to specific customer deliveries — typically takes a quality team 2–3 days. In a recall situation, that is 2–3 days during which affected product is still in the supply chain, being consumed by customers, and accumulating regulatory and reputational liability.
Batch genealogy is a linkage problem — every batch event from GRN to customer delivery is a node in a connected graph. HublerX maintains that graph continuously, linking every raw material lot to every production batch that consumed it, every finished goods batch produced from those runs, and every customer shipment that contained those goods. When a recall is triggered, the full genealogy is rendered in seconds — not assembled manually over days. The recall scope is known before the first regulatory call ends.
Live workflow view
The step-by-step sequence
- 1
Recall or traceability trigger received
A recall is triggered — by a regulatory notice, a customer complaint referencing a specific batch, an internal quality finding, or a supplier notification. The trigger is logged in HublerX with the affected raw material lot, batch ID, or finished goods code as the starting point for the genealogy trace.
On recall trigger · immediate - 2
Full batch genealogy traced automatically
HublerX traverses the batch graph from the trigger point — upstream to every raw material lot and supplier that contributed to the affected batch, and downstream to every finished goods batch produced, every shipment dispatched, and every customer delivery confirmed. The full genealogy is rendered as a structured map within seconds.
Immediately on trigger log - 3
Affected stock and shipments identified
HublerX identifies all affected stock currently in the plant — in raw material stores, WIP, finished goods — and all affected shipments already dispatched. For each dispatched shipment, the customer, delivery date, quantity, and current location are surfaced without manual report extraction.
Simultaneously with genealogy trace - 4
All functions and affected customers notified
Production, logistics, commercial, and procurement are notified simultaneously with their specific action — pause production, hold shipments, contact customers, raise supplier claims. Affected customers receive recall or withdrawal notifications with the specific batch codes, product descriptions, and return instructions.
Within minutes of genealogy trace - 5
In-plant stock quarantined
All affected stock identified within the plant — raw materials, WIP, and finished goods — is flagged for quarantine in the WMS. Work orders consuming the affected raw material lot are paused. Finished goods awaiting dispatch are held pending disposition.
On stock identification - 6
Regulatory submission package generated
HublerX generates the full traceability report for regulatory submission — batch genealogy map, affected quantity by customer, dispatch dates, quarantine actions taken, and timeline of response. The report is exportable as a PDF and covers FSSC 22000, BRC, and FSSAI traceability requirements without additional manual documentation.
On recall scope confirmation
Results are directional. Outcomes vary by ERP, WMS, and MES integration depth, and the completeness of batch records at the time of the recall trigger.
See how batch traceability works in your operation
30 minutes. Your ERP. Your batch structure.