Manufacturing & OperationsGlossary

What Is Traceability?

Also known as: lot traceability, serialization, genealogy

Definition

Traceability is the ability to follow the history, location, and application of a part or material through the supply chain and production process, both backward to its sources and forward to every product and customer it reached.

Traceability Explained

Traceability runs in two directions and both must work. Backward traceability answers what went into a given serial number: which heat lot of bar stock, which solder paste reel, which operator, which machine, which inspection results, which revision of the work instruction. Forward traceability answers the recall question: given a suspect raw material lot, which finished units contain it and which customers received them. Systems that capture consumption but not genealogy can often answer the first question and not the second, which is the one that matters in a containment event.

The mechanics in ERP rest on lot control and serial control. Lot control tracks a quantity of material sharing a common origin, such as a heat, a batch, or a supplier shipment, and is standard for raw material in metals, chemicals, and electronics. Serial control tracks individual units and is required for high-value assemblies, safety-critical components, and most defense deliverables. Infor SyteLine and LN both support lot and serial tracking with as-built configuration records, and the practical work is enforcing the transactions so genealogy is actually captured rather than assumed.

Regulatory and contractual drivers differ by industry but converge on the same requirement. AS9100 expects traceability appropriate to risk, with full traceability mandated for critical items. Defense contracts frequently impose serialized item management and counterfeit-parts prevention obligations that require documented chain of custody. FDA-regulated device manufacturing requires device history records and unique device identification. In each case the obligation extends beyond the plant to what suppliers can demonstrate.

The dominant cost of poor traceability is scope of containment. When a supplier reports a defective heat lot, a plant with tight lot genealogy quarantines 60 units at three customers. A plant that pools material into a common bin without lot separation must assume every unit built in the affected window is suspect, which can mean thousands of units, months of production, and a recall notification whose cost exceeds the plant's annual quality budget. The traceability investment is best evaluated against that exposure, not against transaction effort.

Why It Matters

Determines the size of a recall or containment, which is usually the single largest financial risk a discrete manufacturer carries.
Required by AS9100, IATF 16949, FDA device regulation, and most defense contracts, so gaps are a market-access issue not just a quality issue.
Enables genuine root cause analysis by linking defects back to specific lots, machines, operators, and process parameters.
Supports counterfeit-part prevention and chain-of-custody obligations that are increasingly explicit in defense and aerospace supply agreements.

In Practice

A supplier issues a notice on a single bar-stock heat. Plant A tracks heat numbers through machining into serialized assemblies and identifies 61 affected units at two customers within four hours. Plant B commingles bar stock in a rack and backflushes at standard, so it can only bound the exposure by date range: roughly 4,800 units across eleven customers over seven weeks. Same defect, same supplier. The difference in containment cost was not a quality difference, it was a transaction-discipline difference.

Frequently Asked Questions

What is the difference between lot and serial traceability?

Lot traceability tracks a group of units sharing a common origin, such as a heat of steel or a batch of resin, and is efficient for bulk and raw material. Serial traceability tracks each individual unit with a unique identifier and is required for high-value, safety-critical, or configuration-managed items. Many products use both: serialized assemblies built from lot-controlled materials.

Does traceability require an MES, or is ERP enough?

ERP alone can maintain lot and serial genealogy if every issue and receipt transaction is recorded accurately and promptly. An MES becomes valuable when you need process parameters, test results, and operator and machine identity captured automatically at each operation, since manual capture at that granularity is unreliable. The decision usually turns on required data density rather than on traceability itself.

Related Terms

PPAP (Production Part Approval Process)

PPAP (Production Part Approval Process) is a standardized supplier approval package, originating in the automotive industry, that demonstrates a supplier's production process can consistently produce conforming parts at the quoted rate before shipments are authorized.

Rework

Rework is action taken on nonconforming product to bring it into full conformance with the original specification. It differs from repair, which makes product acceptable for use without meeting the original requirement.

First Pass Yield

First pass yield is the percentage of units that complete a process correctly the first time, without rework, repair, or retest. Units that eventually pass after rework are excluded, so the metric captures hidden factory loss.

Go Deeper

Free Tool

Inventory Carrying Cost Calculator

Build your true annual carrying cost from capital, storage, insurance, and obsolescence components - and see what an inventory reduction target is worth.

Multi-Site ERP Deployment: Strategies and Pitfalls

Multisite ERP deployment explained: single instance vs multi-instance, template-based rollout, site sequencing and data harmonization for manufacturers.

MES-ERP Integration for Discrete Manufacturing

MES-ERP integration guide for discrete manufacturers: architecture patterns, ISA-95 mapping, SyteLine and LN connectors, costs, timelines, and AI-driven sync.

Working with Traceability in a live environment? Our engineers do this every day - and our AI agents automate most of it.

Talk to an Expert Browse the Full Glossary

Back to Glossary

Try it here, free

Food Lot Traceability SQL Query Generator (Forward and Backward)

Open full tool

Fill in your table and column names to get recursive SQL that traces a lot back to suppliers or forward to customers.

Fill in

Lot number to trace

Genealogy table

Table with one row per consumption of a lot into another lot

Input lot column

The ingredient or component lot that was consumed

Output lot column

The lot produced from it

Quantity column

Shipment table

Shipped lot column

Customer column

Ship date column

Maximum depth

Generated code

Free, optional. Reopen it on any device.

Download:

Backward trace: which ingredient lots went into this lot

WITH RECURSIVE back_trace AS (
  SELECT input_lot AS lot_no, output_lot AS used_in, qty_consumed AS qty, 1 AS depth
  FROM lot_genealogy
  WHERE output_lot = 'FG-240918-03'
  UNION ALL
  SELECT g.input_lot, g.output_lot, g.qty_consumed, b.depth + 1
  FROM lot_genealogy g
  JOIN back_trace b ON g.output_lot = b.lot_no
  WHERE b.depth < 10
)
SELECT lot_no, used_in, qty, depth
FROM back_trace
ORDER BY depth, lot_no;

Forward trace: where did this lot go

WITH RECURSIVE fwd_trace AS (
  SELECT output_lot AS lot_no, 1 AS depth
  FROM lot_genealogy
  WHERE input_lot = 'FG-240918-03'
  UNION ALL
  SELECT g.output_lot, f.depth + 1
  FROM lot_genealogy g
  JOIN fwd_trace f ON g.input_lot = f.lot_no
  WHERE f.depth < 10
)
SELECT DISTINCT s.customer_id, s.lot_no, s.ship_date
FROM shipment_lines s
WHERE s.lot_no = 'FG-240918-03'
   OR s.lot_no IN (SELECT lot_no FROM fwd_trace)
ORDER BY s.ship_date, s.customer_id;

Mock recall timing record

-- Start the clock when you run the queries, stop when the customer list is verified.
-- Record: lot traced = FG-240918-03, query run time, rows returned, reconciliation of produced vs shipped vs on hand.

Table and column names above are generic placeholders, not the schema of any specific ERP. Map them to your own genealogy and shipping tables. The WITH RECURSIVE form works in PostgreSQL, MySQL 8, SQLite and others; SQL Server uses WITH without the RECURSIVE keyword and Oracle accepts it from 11gR2. Test against a copy of the data and watch for circular lot references, which the depth limit guards against.