A product code tells a trading business what it sells. A batch or lot identifier can help establish which particular units it received, where they remain and, where records support the connection, which customers received them. This difference becomes important when a supplier reports a manufacturing problem or several customers describe a similar fault. A firm that can identify a genuinely affected production population may investigate it more accurately than one that can retrieve only a product-family name. But traceability does not come from collecting a batch field in isolation: the physical labels, stock movements and order history must remain connected.
This procedure is for UK product SMEs designing a proportionate chain of information from goods-in to customer order. The relevant legal requirements depend on the product category, territory and economic-operator role. The Office for Product Safety and Standards (OPSS) describes product identification and traceability within applicable safety frameworks; the particular requirement for a batch, lot or serial number is not identical for every stock item. The operational aim is to make each recorded identifier useful when evidence or a targeted response is needed, without claiming a database field alone establishes regulatory compliance.
1. Decide what traceability needs to answer
Begin with practical questions. If a supplier reports that one production batch used an incorrect component, can purchasing identify the affected deliveries? Can the warehouse locate units still held? If customer contact is necessary, can the company identify orders that may have been supplied from that population? A detailed traceability scheme should follow the questions relevant to the product's risk and the business's actual responsibilities, not a generic wish to record every available code.
Distinguish SKU, supplier lot, manufacturer batch, serial number, goods-receipt reference and internal warehouse location. They are not interchangeable. One supplier shipment can contain several manufacturing batches; one manufacturing batch can arrive across multiple deliveries. An internal receiving reference may help trace what the business handled but cannot automatically substitute for a manufacturer's production identifier.
Record which fields are mandatory under the relevant product requirements and which are adopted as additional business controls. A specialist product may warrant serial tracking whilst a low-risk commodity is managed by receipt and lot. If the item has no readable batch information, state that fact and identify what can still be traced rather than inventing a production code from the delivery date.
2. Collect the source identifier while receiving evidence exists
At goods-in, compare the actual goods with purchase order, approved product specification, supplier delivery note and any relevant manufacturer documents. Record the exact identifier printed on the unit, packaging or documentation, along with the SKU, variant, received quantity and date. Preserve its original character sequence and any leading zeros. A transcription error that changes one digit can defeat a later investigation.
Check the scope of the code. It may represent a lot of finished units, a date of manufacture, a packaging run or an expiry reference. Do not label every string on a carton as a factory batch without source confirmation. Where one pallet contains different codes, capture distinct quantities rather than assigning the pallet's first visible identifier to every unit.
Take a legible reference photograph if appropriate and record where the code was observed. A barcode scanner can reduce transcription work, but only if the system knows how to distinguish the product identifier from the lot field. Test scan outputs with actual supplier packages instead of assuming every printed barcode contains the same type of information.
3. Keep physical batches identifiable in storage
A receiving record loses value when goods are later combined in a way that destroys their original identity. Decide whether different lots must occupy distinct bins, use labelled containers, or be tracked through a pick process that captures the exact lot removed. The required arrangement depends on product type, warehouse systems and the consequence of losing the distinction.
Do not treat total SKU quantity as evidence of lot quantity. If twenty units from lot A and thirty from lot B share a location, an inventory system that reports fifty undifferentiated units cannot later prove which twenty units were shipped. Either preserve separation or record the actual lot at pick or dispatch using an operationally dependable method.
Apply restrictions at the right level. A concern involving one batch should not automatically make every unrelated item safe, nor should staff release goods from the implicated lot merely because an unaffected lot passed inspection. Where the affected boundary remains uncertain, keep that uncertainty explicit and obtain appropriate review.
4. Link dispatched goods to orders when the purpose requires it
If customer-level traceability is necessary or useful, define where the batch association is captured: picking, packing, shipping confirmation or another controlled event. The association should identify actual units supplied, not just the lot the warehouse intended to pick. If staff substitute units after picking because of damage or shortage, the dispatch record must reflect the change.
Many small organisations may start with a controlled spreadsheet or scanning process instead of expensive serial-tracking software. Whatever tool is chosen, test whether an authorised employee can follow a specific lot from supplier receipt to remaining stock and relevant customer orders. If the answer requires guessing from dates or FIFO assumptions, describe it as an estimate rather than verified traceability.
Protect customer information. The need to investigate a product concern does not justify making order details available to everyone who can view warehouse stock. Connect data with appropriate access roles and retention practices; maintain enough evidence for legitimate product and customer-service requirements.
5. Handle returns and rework without losing origin
A returned unit should be matched to its actual product identity and, where possible, the relevant batch or serial information. If a customer removed the outer packaging, the lot may no longer be visible. Do not assign the last-shipped batch merely because the order date looks similar. Record the available evidence and uncertainty.
Keep items with questionable condition or identity away from unrestricted saleable stock pending the appropriate assessment. Repackaging and rework can change physical labels or configuration; preserve the relationship between the original item, work performed and any new identifier where required by the applicable processes. Releasing stock because an employee has reconciled the total SKU count is not the same as confirming lot-level suitability.
Link a verified defect to the actual observed unit and avoid overclaiming the cause. Several complaints from one lot may support further investigation but do not themselves prove a manufacturing fault. A technically competent review may be necessary, particularly where safety-relevant characteristics are involved.
6. Use lot records to scope supplier and safety investigations
When the supplier reports a problem, establish precisely which production population, revision and time period may be implicated. Match the identifiers with your goods-received history and current holdings. Identify uncertain or missing links rather than assuming an unaffected status from silence. Preserve supplier correspondence and the evidence used to reach a decision.
Under applicable product safety rules, the business may have duties to investigate and act on risks. OPSS product-safety advice for businesses and GOV.UK guidance on product safety and metrology in Great Britain provide context, but their rules are product- and role-dependent. A batch list is not proof that a formal recall is or is not required; that decision needs appropriate specialist assessment.
Plan a controlled stock hold where warranted. Locate affected goods, identify dispatch records that may need examination and distinguish confirmed lot matches from probable or unknown connections. Supplier credit negotiations are separate from deciding what is appropriate for any potentially unsafe units.
7. Test the chain with a trace-forward and trace-back exercise
Choose one actual batch and start at receiving: identify the supplier and receipt date, quantity and current stock. Then follow it forward through movements and any customer orders that the business intends to track. Reverse the exercise from one dispatched order to its source lot. Document missing evidence rather than altering historic entries to make the test appear successful.
Check whether stock quantities reconcile after returns, transfers and partial shipments. A batch may be moved from one warehouse to another or split across several sales channels. Verify the same units are not assigned to two orders or duplicated by an integration retry. A unique transaction reference helps staff identify whether a movement already posted before attempting to repeat it.
Set the frequency and scope of retesting according to product risk and operational changes. A new supplier, different packaging label or updated scanning system may deserve an additional exercise. Do not claim that a single successful trace test demonstrates perfect compliance for every product or all historical shipments.
8. Keep the process proportionate and maintainable
Assign an owner for supplier identifier definitions, goods-in capture, warehouse labelling and customer-order linkage. In a small business one person may hold several responsibilities, but each step needs an understood confirmation. Train people to distinguish different code types and to escalate unreadable or conflicting labels.
Review traceability after a real complaint or supplier change. If the business routinely loses batch identity when opening cartons, fix that physical handover before buying more sophisticated reporting software. If records are accurate internally but cannot be matched to customer orders, assess whether the original traceability objective requires additional dispatch capture.
Traceability is valuable because it allows the business to act on evidence with appropriate scope. The essential chain is an identified source population, real received quantities, controlled physical identity, documented stock movement and order linkage where needed. A short reliable record is more useful than a long form whose links disappear after the first warehouse transfer.
Batch and lot identifiers turn a product issue from a catalogue problem into a traceable incident
When a product complaint or safety concern appears, knowing only the SKU is often not enough. UK product-safety guidance places importance on traceability information that can identify the product and the economic operators responsible for it. For a small product business, batch, lot, serial or production-run identifiers can sharply reduce the scope of an investigation.
Without that level of traceability, one defect report may force the business to treat every unit of the same product as potentially affected. With reliable batch data, the team can compare complaints against supplier deliveries, production dates or inbound shipments and decide whether the issue is isolated or clustered.
Design the record before an incident happens
Where practical, capture the relevant identifier at goods receipt and preserve it through fulfilment, returns and customer-service records. The identifier should be linked to supplier, receipt date, quantity and any quality checks performed. If individual-unit tracking is disproportionate, batch-level traceability may still provide useful containment.
The operational payoff is speed: a business can identify which stock remains on hand, which customers may have received affected units, and which supplier shipment needs investigation without reconstructing the history from invoices and email.
Scope note: exact traceability obligations depend on the product category and applicable product-safety regime. Batch or lot tracking is presented here as an operational control, not as a universal legal requirement for every product.
Reference websites
Track a receipt-only batch or record which lot each customer receives?
The answer depends on actual traceability objectives and product obligations. Both methods provide useful but different levels of confidence.
| Criterion | Receipt and stock location tracking | Receipt-to-customer lot linkage |
|---|---|---|
| Evidence | Links source shipment and lot to quantity held. | Also links actual shipped units to orders. |
| Investigation | Can identify potentially affected stock in the warehouse. | Can identify orders associated with the lot where captured. |
| Effort | Receiving and stock segregation or lot identification. | Requires dependable pick and dispatch capture. |
| Weakness | May not reliably identify which customer got a lot. | Incorrect picks or missed scans can break the chain. |
| Best fit | Where the scope and purpose require current-stock traceability. | Where customer-level traceability is necessary or justified. |
Practical decision: define the evidence required by the relevant product obligations and investigations, then test the chain end to end. Side A: OPSS — Product safety for businesses, business traceability responsibilities with product- and role-specific conditions. Side B: GOV.UK — Product safety and metrology in Great Britain, territorial and applicable framework context. The two operational tracking models are editorial options, not exact mandated UK software configurations.