Manufacturing ERP: Quality Holds, Lot Traceability, and Recalls

In real projects...

Lot traceability is non-negotiable for recalls and customer trust—serial/batch must flow shop floor to shipment. Pair with MRP and shop floor execution.

A common issue we see...

Partial receipts and backflushing that lose lot genealogy when yields vary.

For example...

Scan materials at consumption with lot validation.
Record co-product/split lots with clear genealogy.
Hold quarantine inventory with electronic status.
Run mock recalls timed against regulatory expectations.
Integrate supplier COAs to inbound inspection.

Common mistakes (and how to avoid them)

Letting “floor stock” bins bypass system transactions.
Ignoring rework routing and cost absorption rules.
Weak alignment between quality holds and shipping releases.
Paper travelers that never sync to ERP lot records.

Note: Representative scenarios for education; follow product safety regulations.

Methodology: This article is an educational guide built from public ERP documentation and widely used implementation patterns. Any mini “scenario walkthroughs” are illustrative and not client-specific.

Lot traceability in manufacturing ERP is most valuable when a recall or quality event occurs. The time to build the trace chain is before production starts—not after a non-conformance is discovered.

Configure lot control at goods receipt: capture the supplier batch number, your internal lot number, and expiry date for every controlled component.
Link component lots to production work orders so that every work order records which specific raw material batches were consumed.
Record any in-process quality inspection results against the work order and the lots used, with a clear pass/fail decision before the batch moves to the next stage.
Assign a finished goods lot number to each production batch and record it on the goods receipt to the finished goods location.
Link the finished goods lot to the customer despatch record so that every shipped lot can be traced back to its source batches.
Test the full backwards trace periodically: select a finished goods lot and trace it back to all raw material batches used in its production.

Artifacts to expect:

Lot receipt record with supplier batch number, internal lot number, and expiry date.
Work order lot consumption record (raw material batches used per production batch).
In-process quality inspection results per lot and work order.
Finished goods lot record linked to production work order.
Customer despatch record with finished goods lot number.
Periodic backwards trace test results.

What usually goes wrong (failure modes)

Lot numbers are not captured at goods receipt, breaking the trace chain at source
Goods are received into the ERP without batch numbers, making it impossible to trace raw materials back through production to finished goods.
Mitigation: Make lot number capture a mandatory field at goods receipt for all controlled items. A receipt without a valid lot number should be blocked by the ERP until the information is provided.
In-process quality holds are bypassed and non-conforming material continues to production
Quality hold status is recorded in a separate system and does not block the ERP work order from processing lots that have failed inspection.
Mitigation: Configure quality hold statuses in the ERP lot master so that a lot on hold cannot be issued to a work order until the hold is released by an authorised quality reviewer.
Finished goods despatch records do not include lot numbers
Despatch records show quantities shipped to customers but do not record the specific lots shipped, making customer-level traceability impossible during a recall.
Mitigation: Make lot selection mandatory for all despatch transactions involving controlled items. The ERP should record the specific lot number on every customer despatch line.

Controls and evidence checklist

Make lot number capture mandatory at goods receipt for all controlled items.
Configure ERP quality holds that block lot usage until released by an authorised reviewer.
Record lot consumption on all work orders rather than using backflush without lot assignment.
Record finished goods lot numbers on all despatch transactions.
Conduct periodic backwards trace tests and document results.
Archive quality inspection records with lot references for the minimum required retention period.

Implementation checklist

Define which materials require lot control before configuring the ERP—not all items need lot tracking.
Configure mandatory lot capture at goods receipt and test with representative purchase order scenarios.
Configure quality holds and test that a held lot cannot be issued to a work order.
Test the full trace chain with a pilot production order before going live.
Train receiving and production staff on lot recording requirements with examples of what happens when a lot is missing.
Conduct a backwards trace test after the first ten production orders and document any gaps found.

Frequently asked questions

Where do teams usually lose time in ERP lot traceability implementation?

Most time is lost during recall or investigation events when lot numbers were not captured at every stage of the production process, forcing teams to trace movements through paper records and warehouse staff memory. Configuring mandatory lot number capture at goods receipt, production confirmation, and despatch—before these transaction types go live—is far less disruptive than retrofitting lot tracking after a quality event. A one-hour configuration session per transaction type is the investment that prevents a recall crisis.

How should we test lot traceability before relying on it?

Review traceability completeness by running a backwards trace from a finished goods lot number to all raw material batches consumed in its production. If the trace breaks at any stage—missing a component lot, an intermediate stage, or a sub-assembly—that gap needs to be addressed before the next regulatory audit or customer traceability request. Run this test after the first ten production orders and monthly during the first quarter after go-live.

When should we review and update lot control configuration?

Adjust lot control rules when new raw materials are added, when production processes change, or when regulatory requirements in a target market create new traceability obligations. Lot tracking configurations are tightly linked to production BOMs and routing—any change to production structure should trigger a review of the corresponding traceability configuration to confirm the trace chain remains intact. A BOM change that removes a component from lot control can silently break traceability.

Sources

Conclusion and next steps

Lot traceability in manufacturing ERP works only when lot numbers are captured at every transaction point—receipt, production, and despatch—without exception.

Run a backwards trace test after your first ten production orders. If the trace breaks anywhere, fix the gap before production volumes scale. A trace chain that works at low volume will work at high volume; one that breaks early will only get harder to fix.