FatihGörgülü
Contact
Contact

Lot, Batch and Serial Number Tracking: How to Design End-to-End Traceability in ERP

Inventory tells you how much material you have. Lot, batch and serial tracking tells you which physical material you have, where it came from, which processes consumed it, what it became and where it was shipped. A robust ERP design manages not just an identifier but its attributes, status, genealogy and lifecycle.

Traceability is not a labeling project. It is the connected management of identity, attributes, movements, transformation, quality and shipment history.

Table of contents

Product, lot/batch and serial: three different traceability levels

Lot/batch identification groups physical quantities that share a common production, receipt or process context. Serial identification distinguishes one physical instance. The required level depends on risk, regulation, warranty/service needs, recall precision and operational cost.

Level

Item/product

Identifies

Product class

Typical use

General inventory and planning

Level

Lot / batch

Identifies

A group sharing a context

Typical use

Food, chemicals, metals, textiles, process manufacturing

Level

Serial

Identifies

One physical instance

Typical use

Machinery, electronics, equipment, service

Level

Lot + serial

Identifies

Production group and individual instance

Typical use

High-traceability products

GS1 distinguishes class-level, batch/lot-level and instance/serial-level identification. Greater granularity increases traceability precision but also data and marking effort.

A lot should be more than one number: ERP data model

Data layer

Lot master

Examples

Item, internal lot, source, production/expiry dates, status

Purpose

Stable identity and lifecycle

Data layer

Supplier references

Examples

Supplier, supplier lot, manufacturer, origin, PO/receipt

Purpose

External traceability

Data layer

Class / attributes

Examples

Color, grade, hardness, viscosity, heat no, thickness

Purpose

Flexible sector-specific data

Data layer

Subtables / measurements

Examples

Lab rows, test results, measurement points

Purpose

One-to-many detail

Data layer

Inventory split

Examples

Site, warehouse, bin, quality status, quantity

Purpose

Location/status visibility

Data layer

Documents

Examples

COA, certificate, image, report

Purpose

Evidence set

Data layer

Genealogy edges

Examples

Parent/child lot or serial, consumed quantity, work order

Purpose

Transformation trace

Data layer

Event history

Examples

Receipt, transfer, QC, consumption, production, shipment

Purpose

Lifecycle events

When should a lot number be assigned?

Point

Pre-reserved

Best fit

Pre-printing or regulated preparation

Main control

Cancel unused identities

Point

Production start

Best fit

Identity needed through the process

Main control

Link lot to work order early

Point

Production receipt

Best fit

Lot becomes relevant at output

Main control

May be too late for WIP traceability

Point

Purchase receipt

Best fit

Supplier-lot material

Main control

Preserve supplier lot separately

Point

Quality release

Best fit

QC-controlled material

Main control

Do not delay identity; change status instead

Principle

Identity creation and usability are different events. A received lot can exist while its quality status is still pending.

Supplier lot versus internal lot

Do not overwrite the supplier lot when creating an internal lot. A common robust model keeps the internal lot as the company's operational key and stores supplier/manufacturer lot as a cross-reference for external traceability.

  • Define whether repeated deliveries of the same supplier lot become one or several internal lots.
  • Do not merge different supplier lots without understanding recall impact.
  • Capture manufacturer separately when distributor and manufacturer differ.
  • Keep certificate number separate from lot number.
  • Preserve quality history when returned material is received again.

Assign serial numbers early or late?

Assignment point

Work-order reservation

Best fit

Customer/project identity known early

Trade-off

Unused reserved serials

Assignment point

First operation

Best fit

Individual trace through production

Trade-off

Early physical marking

Assignment point

Critical assembly

Best fit

Identity begins when chassis/core is created

Trade-off

Prior WIP needs another identity

Assignment point

Final operation / receipt

Best fit

Serial needed mainly for finished goods

Trade-off

Less production detail

Assignment point

Before shipment

Best fit

Sales/warranty-only identification

Trade-off

Weak production genealogy

Decision test

If you must answer which operations, tests and components belong to one individual product, assigning its serial only at shipment is usually too late.

Serial tracking at subassembly and finished-good levels

Not every WIP item needs a serial. Serialise subassemblies when they are serviceable, high-value, safety-critical or require individual history, and preserve parent-child relationships to the finished serial.

Example genealogy

  1. 1

    Raw material lots

    Steel, paint and cable lots

  2. 2

    Serialized subassemblies

    PCB serial, motor serial

  3. 3

    Finished serial

    Machine/device serial

  4. 4

    Customer shipment

    Serial linked to order/customer

  5. 5

    Service

    Replacement component serials extend genealogy

Split, merge, repack and rework

Event

Split

Required relationship

Parent to multiple child quantities or controlled same-lot split

Event

Merge/blend

Required relationship

Multiple input lots to one output batch with consumed quantities

Event

Repack

Required relationship

Source lot preserved; packaging batch where needed

Event

Rework

Required relationship

Original identity linked to rework output

Event

Transformation

Required relationship

Input-output genealogy at each production step

Event

Subcontracting

Required relationship

Outbound identity linked to returned identity and outside operation

Barcode and label design

A label should not duplicate the database. Encode identifiers and operational essentials; keep rich test, certificate and attribute data in ERP behind that identity.

Purchase receipt lot label

GS1-128 or DataMatrix

Item

RM-STEEL-304

Internal Lot

INT-L260921-0042

Supplier Lot

SUP-HT88931

Quantity

1,250 KG

Receipt

21.09.2026

Quality

QC PENDING

(01)08690000012345(10)INT-L260921-0042(17)270630

Keep internal and supplier lot as separate data elements.

Serialized finished-good label

GS1 DataMatrix / GS1-128 / internal standard

Item

MACHINE-X100

Serial

MCH-2026-000184

Lot

FG260921-03

Revision

R05

Production

21.09.2026

Project

PRJ-260117

(01)08690000056789(21)MCH2026000184(10)FG260921-03

The serial is the stable identity; project or revision can remain contextual attributes.

GS1 Application Identifiers include AI (10) for batch/lot, AI (21) for serial, AI (11) for production date and AI (17) for expiration date.

Quality status, shelf life and FEFO

  • Manage quality status separately from lot identity.
  • Calculate and validate expiration dates from controlled master data.
  • Support customer-specific minimum remaining shelf life.
  • Prevent blocked/rejected lots from appearing usable to MRP/ATP.
  • Use FEFO as a warehouse selection rule, not merely as a stored date.

Forward and backward genealogy

Question

What went into this finished serial?

Expected answer

All parent lots/serials and quantities

Question

Where was this supplier lot consumed?

Expected answer

Work orders and produced outputs

Question

Which customers are affected by this input lot?

Expected answer

Output lots/serials → shipments → customers

Question

Which subassemblies are installed in this serial?

Expected answer

Child serial list

Question

Where was this subassembly serial used?

Expected answer

Finished parent serial

Question

What happened after rework?

Expected answer

Original and resulting identity plus rework order

ERP transactions that should preserve lot/serial identity

Transaction

Purchase receipt

Control

Capture internal + supplier/manufacturer identity

Transaction

Warehouse transfer

Control

Preserve identity

Transaction

Production issue

Control

Record consumed lot/serial

Transaction

Production receipt

Control

Create/select output identity and genealogy

Transaction

Subcontracting

Control

Preserve or explicitly transform identity

Transaction

Quality

Control

Change status, not identity

Transaction

Sales shipment

Control

Record customer-lot/serial relation

Transaction

Customer return

Control

Validate original identity

Transaction

Inventory adjustment

Control

Adjust at lot/serial level with audit

Data volume and performance

Serialisation can multiply record volume dramatically. Separate master and event data, index frequent lookup keys, store direct parent-child genealogy, design scanner/offline flows and audit label reprints or duplicate scans.

ERP traceability design checklist

  • Define which items need lot, serial or both.
  • Define the exact event that creates each identity.
  • Store supplier lot separately from internal lot.
  • Use flexible attributes/subtables for sector-specific lot data.
  • Preserve genealogy through split, merge, rework and subcontracting.
  • Assign serials early enough for the required production/test history.
  • Link critical subassembly serials to the finished serial.
  • Keep barcode payload focused on operational identifiers.
  • Make shipment capture mandatory for forward traceability.
  • Test recall queries both forward and backward.
  • Include stock at subcontractors and quality locations in recall scope.
  • Plan indexing, archiving and scanner integration for data volume.

Design principle

Good traceability is not about generating more numbers. It is about assigning the right identity at the right granularity and never breaking that identity chain from receipt through production, quality, subcontracting, shipment and service.

Frequently asked questions about lot and serial traceability

Are lot and batch the same?
They usually serve the same group-level traceability purpose, although terminology may vary by sector and company.
Should supplier lot become the internal lot?
It can, but storing internal and supplier/manufacturer lots separately usually provides better uniqueness and external traceability.
When should serial numbers be assigned?
Early if individual production/test/component history is required; later if serialisation is only needed at finished-goods or warranty level.
Should every subassembly have a serial?
No. Serialise subassemblies when individual history, serviceability, value or safety justifies the operational cost.
Should every attribute be encoded in the barcode?
No. Encode stable identity and operational essentials; keep rich attributes, tests and documents in ERP.

Related pages:

Related content

Relevant resource

Resources and checklists

Use the resources surface when you want a checklist, decision note, or downloadable asset to make this topic more concrete.

Continue →

Conversation

If this is active, let us talk

If this topic matches a live project, sponsor decision, or delivery pressure, you can get in touch directly.

Continue →

Framework

Return to the ERP framework

Use the ERP framework when you need the wider sponsor, delivery, and transformation picture beyond a single topic.

Continue →

Standards and technical references

Lot, Batch and Serial Number Tracking: End-to-End Traceability in ERP | Fatih Görgülü