# What Is Production Traceability? How to Build an Unbroken Lot and Serial Record from Raw Material to Customer

> What is production traceability? Build lot and serial tracking in 6 steps: backward and forward tracing, a capture-point table, GS1 barcodes and regulation.

Source: https://digitalbridge.com.tr/en/blog/production-traceability-guide.html
Publisher: Digital Bridge Teknoloji (https://digitalbridge.com.tr)
Topic: Industry 4.0
Published: 2026-10-08 · Updated: 2026-10-22

Production traceability is the ability to show which raw material lots a product was made from, on which machine, in which shift and with which process settings, and which customer received it. In a well-built system, one lot number leads backward to the supplier and forward to the customer in minutes; on paper it takes hours or days.

## Key takeaways

- Production traceability works in two directions: backward tracing finds a defect's source, forward tracing sets the scope of a recall.
- Finer granularity (lot, shift, case, serial number) costs more to capture but shrinks the quantity you would recall.
- Records should be captured at six points, from goods receipt to dispatch, at the line and when the event happens.
- A product genealogy exists only when warehouse management, MES and ERP share the same lot identity.
- In ETQ's 2024 survey, 73% of quality leaders had experienced at least one product recall in the previous five years.

This article covers lot and serial tracking in any sector. [Traceability](https://digitalbridge.com.tr/en/glossary.html#traceability) sits at the heart of quality and traceability, the fourth stage of our [Industry 4.0 roadmap for SMEs](https://digitalbridge.com.tr/en/blog/industry-4-0-roadmap-smes.html); statistical process control (SPC), 8D problem-solving and recall drills all depend on it.

## What does production traceability actually cover?

Production traceability answers two questions:

- **Backward tracing:** "Which raw material lot, which supplier and which machine did this defective product come from?" This underpins root cause analysis and supplier claims; steps D2 and D4 of an [8D problem-solving](https://digitalbridge.com.tr/en/blog/8d-problem-solving.html) report rest on this record.
- **Forward tracing:** "Which finished products did this suspect raw material lot go into, and which customers received them?" This sets the scope of any recall.

The structure linking the two is the **product genealogy**: each finished lot is tied to the intermediate and raw material lots it consumed, and each lot to its work order, machine, operator and process data. How deep the genealogy needs to go depends on your sector and your customers. For an example of part- and carton-level tracking in made-to-order production, see [furniture manufacturing software](https://digitalbridge.com.tr/en/blog/furniture-manufacturing-software.html).

Granularity is a design decision too:

| Level | What it identifies | Typical use | Recall scope |
|---|---|---|---|
| Batch / lot | Products made under the same conditions | Food, chemicals, plastics | The whole lot |
| Shift / day | Output in a time window | Low-cost starting point in volume production | Wide and vague |
| Case / pallet | Shipping unit | Logistics and distribution | Medium |
| Serial number | Each individual item | Automotive parts, electronics, machinery | Affected items only |

In practice the most common situation is weak, shift- or day-level traceability: the finished label carries only a production date, and which raw material lots were on the line that day can only be estimated from stores issue notes. That usually gets through an audit, but when a real problem arises it forces you to treat a whole day's, or even a week's, output as suspect.

Finer granularity costs more to capture but narrows the scope of a recall. The right level comes from weighing how much product you would have to pull back if something went wrong against the cost of collecting the data.

## What does weak traceability cost?

When a quality problem escalates, poor production traceability multiplies the bill: a company that cannot say which products are affected has to recall far more, just to be safe.

> In a survey of more than 750 quality leaders in the US, UK and Germany by ETQ (part of Hexagon), a quality management software provider, **73% had experienced at least one product recall in the last five years**, with the financial cost per recall reported to reach $99.9 million in the US alone. ([ETQ Pulse of Quality in Manufacturing 2024, via PR Newswire](https://www.prnewswire.com/news-releases/global-quality-in-manufacturing-survey-from-etq-reveals-dramatic-rise-in-product-recalls-302211545.html))

In the same ETQ survey, 61% attributed up to half of their recalls to supplier issues. A system that does not tie raw material lots to finished goods cannot show where the problem came from, or pass the cost back to the supplier.

In the food sector the picture is more visible still. According to the European Commission's [Alert and Cooperation Network 2024 Annual Report](https://ec.europa.eu/newsroom/sante/items/882537/en), the EU's Rapid Alert System for Food and Feed (RASFF) received 5,250 notifications of public health risks in 2024, up 12% on 2023. We cover the food-specific set-up in [food traceability and digital HACCP](https://digitalbridge.com.tr/en/blog/food-traceability-digital-haccp.html), and linking temperature records to lots in [cold chain monitoring](https://digitalbridge.com.tr/en/blog/cold-chain-monitoring-haccp.html).

Regulators are also shortening the clock. The US Food and Drug Administration's [food traceability rule](https://www.fda.gov/food/food-safety-modernization-act-fsma/fsma-final-rule-requirements-additional-traceability-records-certain-foods) requires records for foods on its traceability list to be made available **within 24 hours** of a request, and as an electronic sortable spreadsheet when needed. The original compliance date was 20 January 2026; as of 2026, following a Congressional directive, the FDA has said it will not enforce the rule before 20 July 2028. A 24-hour response is a hard target to meet from paper records.

For readers dealing with Turkish suppliers or plants: food and feed businesses in Türkiye are required to maintain traceability under Law No. 5996 on veterinary services, plant health, food and feed, while Law No. 7223 on product safety places responsibility for withdrawing unsafe industrial products on the manufacturer. In automotive supply chains, [IATF 16949](https://digitalbridge.com.tr/en/glossary.html#iatf-16949), the International Automotive Task Force's quality management standard, makes traceability an explicit requirement.

## How do you build a production traceability system? Six steps

1. **Set scope and granularity.** Which product families, at what level (lot, case, serial)? Put customer specifications, sector standards and past complaints on the table.
2. **Map the critical capture points.** Typical points are goods receipt, issue from stores, consumption at the line, creation of intermediates, packing and dispatch. At each one, record which lot, how much, when and by whom.
3. **Choose a coding standard.** For labels that other companies will read, standards from GS1, the global barcode standards body (GS1-128, GS1 DataMatrix), are the common choice. On small surfaces or for direct part marking, 2D codes (DataMatrix, QR) work best; laser marking gives permanence where labels fall off.
4. **Capture data at the line.** Records should be taken where and when the event happens, via handheld terminal, fixed scanner or operator panel. Consumption written in a notebook at the end of the shift is an estimate, not traceability. If line-side capture is part of a manufacturing execution system ([MES](https://digitalbridge.com.tr/en/glossary.html#mes)) project, our [MES implementation checklist](https://digitalbridge.com.tr/en/blog/mes-implementation-checklist.html) will help.
5. **Connect the systems.** Raw material lots live in the warehouse management system (WMS), work orders in MES, and sales and delivery notes in enterprise resource planning (ERP). A genealogy only exists when all three share the same lot identity. We explain the split in [MES vs ERP](https://digitalbridge.com.tr/en/blog/mes-vs-erp.html) and the warehouse side in our [warehouse management system guide](https://digitalbridge.com.tr/en/blog/warehouse-management-system-guide.html).
6. **Test it regularly.** The only way to know the system works is to pick a lot at random, trace it backward and forward and time the exercise. We set out how in our [product recall drill guide](https://digitalbridge.com.tr/en/blog/product-recall-drill.html).

### Which data should you capture at each point?

This summary table is a good starting point when designing traceability capture points:

| Capture point | Minimum data | Typical tool |
|---|---|---|
| Goods receipt | Supplier, supplier lot no., internal lot no., quantity, expiry date, incoming inspection result | Handheld terminal, label printer |
| Issue from stores | Internal lot no., quantity, target work order | Handheld terminal |
| Line-side consumption | Work order, machine, lots consumed, timestamp | Operator panel, fixed scanner |
| Process | Critical parameters such as temperature, pressure, time, torque | PLC (programmable logic controller), sensors, SCADA |
| Packing and palletising | Finished lot or serial no., case and pallet code | Label printer, fixed scanner |
| Dispatch | Pallet code, customer, delivery note no., vehicle | Handheld terminal, ERP |

Each row of the capture-point table answers a question you will be asked during a recall. Skip a row and that link in the chain becomes guesswork, so if scope must shrink, cut product families rather than rows.

## Where does the traceability chain usually break?

In production traceability projects, the record chain usually breaks at the same five points:

- **Blending and splitting.** When several lots meet in a silo, tank or mixer, or one lot is split across work orders, the chain breaks unless proportions and timestamps are recorded. In textiles, a fabric batch split across several cutting orders is the classic case; we cover it in [textile batch tracking](https://digitalbridge.com.tr/en/blog/textile-production-tracking.html). The same problem in tanks and mixers, where production follows recipes, is handled in [batch traceability in chemical manufacturing](https://digitalbridge.com.tr/en/blog/batch-traceability-chemical-manufacturing.html).
- **Rework and scrap.** If a reworked item gets a new identity, its link to the original must be kept.
- **Stock issue discipline.** If the warehouse picks the most convenient lot rather than the one on the record, the data and reality drift apart. [FIFO and FEFO methods](https://digitalbridge.com.tr/en/blog/fifo-fefo-inventory-methods.html) are the foundation here.
- **Documents scattered across inboxes.** Supplier certificates of analysis and specifications often stay as email attachments. In [Smart360](https://digitalbridge.com.tr/en/smart360.html), an attachment received in SmartMail is saved to a SmartFiles folder in one click, and a file uploaded under the same name becomes a new version rather than overwriting the old one.
- **Process data kept separately.** If temperature, pressure or torque values are not tied to the lot, "under what conditions was this lot made?" has no answer. The same data feeds [SPC and Cpk analysis](https://digitalbridge.com.tr/en/blog/spc-cp-cpk-explained.html).

When traceability records meet quality data, the source of a defect becomes visible. We show how each fabric roll's defect map is matched to loom and yarn lot in [AI fabric defect detection](https://digitalbridge.com.tr/en/blog/ai-fabric-defect-detection.html).

Traceability data is increasingly shared with customers too: in automotive, pack labels feed the despatch advice through [automotive EDI integration](https://digitalbridge.com.tr/en/blog/automotive-edi-integration.html), while in textiles product records are becoming the EU's [digital product passport](https://digitalbridge.com.tr/en/blog/digital-product-passport-textiles.html).

## How does Digital Bridge build production traceability?

At Digital Bridge we do not see traceability as buying a label printer and a scanner. We build it as one data chain from capture point to report:

- **We map the process with you.** In [production traceability and barcode](https://digitalbridge.com.tr/en/industry-40/production-traceability-barcode.html) projects we walk every capture point from goods receipt to dispatch on site and set the granularity against your customers' requirements.
- **We select or build the line-side hardware.** We specify [industrial data terminals](https://digitalbridge.com.tr/en/industrial-products/industrial-data-terminals.html) for dusty, humid or cold environments and, where needed, design the hardware in-house.
- **We tie work orders to lots.** On the [MES production management](https://digitalbridge.com.tr/en/industry-40/mes-production-management.html) side we link consumption, machine, operator and process data to each lot. Our MES integrates with Logo, SAP, Mikro and bespoke ERP systems.
- **We make warehouse and ERP speak the same identity.** Through [system integrations](https://digitalbridge.com.tr/en/technology-hardware/system-integrations.html) we join the lot flow between [warehouse and inventory management](https://digitalbridge.com.tr/en/software-solutions/warehouse-inventory-management-wms.html) and ERP into one genealogy, so backward and forward reports come from a single query.

We do not sell this as a packaged product; after a needs analysis we set out scope, phases and cost in a written proposal.

If you supply the automotive industry, we cover the additional requirements – the traceability plan, record retention and customer response times – in [IATF 16949 traceability requirements](https://digitalbridge.com.tr/en/blog/iatf-16949-digital-traceability.html).

## Your next step: measure your current traceability

Test the traceability you have today with a simple exercise: pick a finished lot from last month at random and time how long it takes to find the raw material lots it used and the customers who received it. The time taken, and the gaps you hit, show where a project should start. Then [contact us](https://digitalbridge.com.tr/en/contact.html) with the results and we will review your site together.

For more on quality, maintenance and production management, browse [our complete Industry 4.0 guide](https://digitalbridge.com.tr/en/blog/topic/endustri-40.html).

## Frequently Asked Questions

### Should we track by lot or by serial number?

Serial tracking is needed when product value is high, when a customer specification requires item-level records, or when you want to recall only the affected items. For batch processes such as food, chemicals and plastics, lot tracking is usually sufficient. Many plants use both: lots for raw materials and serial numbers for finished goods.

### Isn't our ERP enough for traceability?

ERP can hold lots on the purchasing, stock and sales side, but it rarely captures which raw material lot was consumed on which work order and machine, and in what quantity, at the line. MES or a line-side data capture application fills that gap. A complete genealogy needs ERP, warehouse management and production records to share the same lot identity.

### Which barcode type should we use?

For labels read by other companies along the supply chain, GS1 standards such as GS1-128 and GS1 DataMatrix are the safe choice. For direct part marking or small surfaces, 2D DataMatrix is the usual answer. Codes used only inside your own plant allow more freedom; what matters most is that the code stays readable in your environmental conditions.

### How long does it take to implement traceability?

It depends on the number of products and capture points, the systems to be integrated and the line-side hardware required, so a single figure would mislead. The most reliable route is to start with one product family or line, establish recording discipline and then roll out to other lines. The phases are agreed in writing at proposal stage.

### Can we collect data from our existing machines?

In most cases, yes. Counters, parameters and status can be read from machines with a PLC; older machines without one can be fitted with external sensors or an operator panel. The right method is assessed machine by machine on site. The goal is to record lot information together with process data, without manual entry.

### What is the difference between backward and forward traceability?

Backward traceability starts from a defective product and finds which raw material lot, supplier and machine it came from; it underpins root cause analysis and supplier claims. Forward traceability starts from a suspect raw material lot and finds which products it went into and which customers received them; it sets the scope of a recall.

### Is production traceability a legal requirement?

In many sectors, yes. In Türkiye, food and feed businesses must maintain traceability under Law No. 5996, and Law No. 7223 on product safety makes manufacturers responsible for withdrawing unsafe products. IATF 16949 explicitly requires traceability in automotive, and the FDA requires food exporters to the US to provide records within 24 hours of a request.