Lot traceability across suppliers, production, and shipments

A supplier flags a material lot, and your quality manager needs to know where it went. Lot traceability links that received material to the production batches that consumed it and the shipments containing their output. It also works in reverse: a finished-goods batch should lead back to its production and supplier records. A lot number on a label helps identify the material, but the movement records establish the path.

Start with one product and follow its records across receiving, production, storage, and shipping. The process below uses the event-based approach described by GS1’s traceability standards. The quantities and identifiers in the worked example are hypothetical. Permute publishes this article and sells connected business data and custom applications; its reporting role is explained separately.

Identify the product and lot together

A supplier’s batch code may not be unique across suppliers or products. Retain the supplier identity, supplier product code, lot code, and your internal item ID on the receipt. If your warehouse assigns another lot reference, keep both and record the mapping. Replacing the supplier’s code with an internal code without preserving that relationship makes later investigation harder.

A lot identifies a group of units; a serial number identifies an individual unit. Choose the level your process needs and keep it consistent when records cross systems. GS1’s system architecture distinguishes product identity combined with a lot from serialized identity. A shipment or pallet reference serves another purpose and should remain linked to the items it contains.

Record the events that change location or composition

GS1 describes critical tracking events, such as receiving, packing, and shipping, and the key data elements that explain each event. For your workflow, assign an owner to capture the event reference, product and lot, quantity and unit, time, location, and related document. Keep the original source reference so another person can inspect the evidence later.

Receiving establishes which supplier lot entered a location. Production records establish which input lots were consumed in which output batches. Shipping establishes which finished lots left for which destinations. A warehouse transfer changes the location without creating new production. Keep those event types distinct so a report does not treat a transfer as another receipt from the supplier.

When production splits a lot or combines inputs, record the actual input-to-output relationships. A bill of materials describes the intended recipe or component structure; it does not establish which physical lots were consumed on a particular run. Capture substitutions, rework, and recorded losses under the rules your production and quality owners approve.

Follow a material lot through two production batches

Consider a hypothetical process with no yield loss, unit conversion, or other ingredients. Receipt R1 brings 100 kilograms of material M from supplier lot S1 into the plant. Production batch B1 consumes 60 kilograms and B2 consumes 40 kilograms. Each produces the same quantity of finished material. The simplified quantities make the relationships easy to check; they are not a claim about a real manufacturing process.

Tracing forward from S1 identifies B1 and B2, both shipments, and 30 kilograms remaining at the plant. Tracing backward from SH1 identifies B1, production event P1, and supplier lot S1. The two directions answer different questions: where a material went and what contributed to a shipment. Retain the links even after the on-hand balance reaches zero.

Now remove the lot reference from SH2. The total quantity can still reconcile, but the relationship between the shipment and B2 is no longer established by that record. Flag the missing reference and assign an investigation owner. A matching date or quantity may help locate evidence; it should not silently become a confirmed lot match.

Test the records your lot tracking software can retrieve

Ask a vendor to trace a supplied sample in both directions using the edition and configuration you would buy. For example, ERPNext’s traceability report documentation describes following serialized and batched items through their lifecycle. That is a documented capability to investigate, not proof that your existing receipts or production records contain the required references.

• Can the report distinguish identical lot codes from two different suppliers?
• Does a split production run retain every input-to-output link rather than only the most recent batch?
• Can a reviewer follow a return to its original shipment without counting it as new production?
• Does a missing lot reference remain unresolved instead of being filled from the latest receipt?
• Can the responsible person retrieve the evidence after an item is discontinued or a user leaves?

Have someone outside the setup team repeat the trace using the report and its source references. Compare the remaining quantities with inventory reconciliation, but test the links separately: a correct stock total does not establish complete batch history. Keep the findings and unresolved records with the evaluation.

Where Permute fits across traceability records

Permute sells connected business data and custom applications. We can scope a reporting workflow that combines supported sources and supplied receiving, production, and shipment records. The work includes declared mappings between product references and retained source IDs, with uncertain relationships left visible for review.

Your quality and operations owners decide which events establish a valid relationship and how corrections should be represented. Those rules can support a repeatable exception report with source evidence and access controls. A reviewer can inspect which shipment lacks a lot reference and return to the underlying record. The manufacturing dashboard article discusses presenting operational exceptions with their source context.

Keep quality decisions and source corrections with their owners

A reporting workflow cannot recover an unrecorded physical movement from a stock total. Permute does not certify traceability compliance, decide whether a product is safe, or authorize a recall. The responsible team determines the required investigation and any action. Source corrections and external system updates require their own verified scope and authorization.

A quality management system may hold reviews and decisions that need to stay linked to the batch. The quality management software comparison covers that separate evaluation. Confirm the access and retention requirements for your own records rather than assuming a software feature establishes compliance.

Make the next investigation repeatable

Lot traceability needs a recorded path from receipt through production to shipment, plus a way to follow that path backward. Start with one product, verify the identifiers, and test a missing link as well as a complete example. Reconcile quantities while keeping unresolved relationships visible. Retain the source records so another reviewer can repeat the investigation after the material has left the plant.

Questions about tracing lots across records