Materials and lot tracking for manufacturers
When a supplier lot turns out to be bad, you need to know quickly which work orders used it, which finished lots it went into and which customers received them.
Scope a lot tracking project
An ERP or MRP system plans what a plant should make and what it should buy. It is usually weaker at recording what actually happened on the floor: which pallet of material went to which line, how much was used, what is still sitting in staging and what was scrapped. Those facts live on paper travelers, whiteboards and spreadsheets until something goes wrong. We build the tracking layer that captures them with scans, and post the transactions your ERP expects, so it stays the system of record for cost and planning.
Inbound materials
Receiving for a plant looks like receiving for a distributor, with one addition: the supplier’s lot travels with the material. When a supplier sends an X12 856 Ship Notice/Manifest with lot detail, receiving can check it instead of retyping it. When it does not, receiving captures the supplier lot from the label or the certificate of analysis.
What we typically build:
- Receipt by scan with supplier lot, internal lot ID, quantity, expiry where it applies, and the purchase order line.
- Quality hold on receipt for materials that need inspection, so held stock cannot be issued until someone releases it.
- Labels that carry the lot. GS1 describes its Digital Link standard as a way to encode identifiers such as GTINs, GLNs and SSCCs “along with batch numbers, serial numbers, expiry dates and more”, so one 2D barcode can identify the item and the lot together.
Lot and serial genealogy
Genealogy is the record that links inputs to outputs. It has to work in two directions:
- Trace back, from a customer complaint to the finished lot, then to every input lot and its supplier.
- Trace forward, from a suspect supplier lot to every work order that consumed it, every finished lot it went into and every shipment that carried those lots.
Both depend on three records made at the right moment: the issue of material by lot to a work order, the creation of the output lot or serial number at completion, and the shipment by lot or serial. For serialized assemblies, the record also links each finished serial to the serials of its major components.
We model these as events: what was handled, where, when and in which step. That is the same shape as GS1’s EPCIS standard, whose version 2.0 (dated June 2022 on GS1’s page) added a JSON syntax and a REST API for capturing and querying event data. Using the same shape keeps the door open to sharing events with customers later. It is a design practice, not a certification.
WIP and staging inventory
Material issued to the floor but not yet consumed is a blind spot. If the ERP backflushes components when a work order completes, line-side stock is invisible until then, or it is counted twice: once in the stores record and once on the floor. Partial pallets come back to stores without a label, and scrap is written off at month end with no lot attached.
What we typically build:
- Staging and line-side locations as real locations, so material moves there by scan and stays visible.
- Issue by scan to a work order, or backflush from the line location instead of from main stores, whichever matches how your floor works.
- Returns to stores with a new label that carries the original lot and the remaining quantity.
- Scrap by reason and lot, recorded when it happens.
Finished goods and customers
At completion, the finished lot gets its label and moves to put-away. Picking follows first-in, first-out or first-expired, first-out rules by lot. On the customer side, the usual EDI documents are the 850 Purchase Order, the 856 ship notice with lot or serial detail where the customer asks for it, and the 810 Invoice. Customers who manage your stock at their site may also want the 846 Inventory Inquiry/Advice. We build the pack-out scanning that makes those documents accurate, not just the messages themselves.
Integration with ERP and MRP
We do not replace your MRP. The tracking layer posts the transactions it already expects: receipts, issues, completions, transfers, adjustments and shipments. The decisions we settle during requirements analysis are specific:
- Which system assigns lot numbers, and in what format.
- Whether backflushing stays on, and for which items.
- How postings flow: in real time through an API, or in batches through files.
- What happens when the ERP rejects a posting. Each rejected transaction goes to an error queue with an owner, not into a log nobody reads.
The integration inventory worksheet is a good place to list these before a first conversation. For raw materials, the reorder point calculator helps check whether current minimum levels match usage and lead time.
Example (fictional). A maker of small hydraulic fittings buys brass bar in bundles. A customer reports cracked fittings from finished lot EX-F-4471. The plant’s records show which work order made the lot but not which bundles it used, because bar is issued to the saw area in bulk each morning. The written requirement becomes: “Each bundle moved to a saw is scanned to the active work order. When the work order completes, the system records every bundle lot consumed. A trace-back report from any finished lot lists its input lots and suppliers.” The acceptance test runs one work order across a bundle change and checks that both bar lots appear in the trace.
Where to start
Pick one product family and walk it from the receiving dock to the shipping dock. A Scope and plan engagement produces the process map, the interface list and requirements with acceptance tests for that family. Receiving and issue by lot make a sensible first build, because genealogy can only start from the first scan. After go-live, documentation and onboarding and training give every shift the same procedure.
Scope your project.
Tell us what you need to track, which systems you run and when it has to work. We reply with questions or a time to talk.