When a supplier reports a bad lot or a customer sends a part back, the answer should come from a query. Meta Smart Factory records lot and serial identity where the material passes: scanned at receiving in the WMS, booked against the work order in the MES, checked in Quality and labelled with GS1 batch and lot identifiers at shipment.
Talk to us about your traceabilityProduction traceability software records which material lots, machines, operators and inspection results went into each finished lot or serial number. The trail has to work both ways: backward from a shipped unit to its components and suppliers, and forward from a suspect incoming lot to every unit and customer it reached. The record has to be captured as material is received and consumed, because it cannot be rebuilt for product that has shipped.
How far back you can trace depends on what was captured at the time. These are the capture points, in the order the material moves.
Serial per unit, lot per pallet, batch per shift or a time window: each sets a floor on how small a recall can be, because containment covers every unit you cannot rule out. The level is fixed by what is scanned at the moment of consumption. Moving from shift-level to pallet-level identity changes what the operator scans, so decide it before go-live. A workable rule is to scan the traceable and expensive materials and backflush the fasteners.
Backflushing has a price. The WMS can deduct components from the BOM each time the PLC reports a good count, which keeps stock current but posts what the BOM says. Only an issue scanned or weighed at the point of use records which lot was really consumed. Where an operation was booked without a scan, the trail thins to the order.
A lot or batch number covers a quantity received or produced together, such as a pallet or a shift's output. A serial number identifies one unit. The WMS handles both. The finer level gives the smaller recall and costs a scan per unit where it is consumed.
You trace forward from the incoming lot. Where it was scanned at each operation, the query finds the other parts that shared it, and scan-verified loading shows which shipment each pallet left in. A quality hold can find material already staged, and the reject decision can be passed to the ERP through its interface, so stock is blocked there. The forward direction is usually the weaker one, so test it before you need it.
No. Receiving, picking, cycle counting and lot traceability run on scans alone, and inspections run on operator and inspector entry at the workstation. A machine connection adds the machine and shift to each measurement, and nobody has to remember them.
The WMS owns location, movement and lot identity, and the MES owns what happened at each operation. The item master and the bill of materials almost always stay in the ERP. Agree that boundary field by field, in writing, before the interface is built.
Run a Proof of Concept on one line with your own material. It typically takes 2 to 12 weeks depending on the product. Before go-live, pull a unit off the dock and ask for its full backward genealogy within the hour.