A callback. A complaint. An audit finding. The moment a quality problem becomes apparent, exactly one question arises: Which parts are affected - and where are they?
If you can't answer this question within hours, you have a problem. Not just an operational one - but a legal one. The EU Product Liability Directive 2024, IATF 16949 and a growing number of industry-specific standards make traceability mandatory, not optional.
This guide explains what traceability in production actually means, which mandatory legal fields apply, why many companies believe they are traceable - but really aren't - and what a concrete quick start looks like.
|
THE MOST IMPORTANT FACTS IN BRIEF
|
|
BRIEFLY SUMMARIZED
|
Traceability in production refers to the ability to trace the materials and components of each manufactured product or batch, the process conditions under which it was manufactured, the tests it has undergone and to whom it was delivered.
ISO 9000:2015 defines traceability as 'the ability to trace the history, use or location of an item under consideration'. This definition sounds simple. Implementing it in a real manufacturing environment with several hundred components, dozens of suppliers and parallel production lines is complex.
Tracking describes the real-time tracking of a product along the production chain - where is this part right now? Traceability is the retrospective capability - where was this part, under what conditions was it manufactured, what quality results are available?
Both concepts complement each other, but are different requirements with different technical solutions. Traceability is relevant for the compliance requirements of most standards - the retrospective traceability of a quality event.
|
Direction |
Question |
Use case |
Example |
|---|---|---|---|
|
Backward traceability |
What materials/batches was this product made from? |
Customer complaint, recall |
Customer complaint → Which batch? → Which supplier? |
|
Forward traceability (Forward Traceability) |
To whom was this batch delivered? Which products are affected? |
Blocking of defective batches, recall action |
Defective steel in batch X → Which products? → Which customers? |
|
Internal tracking (process traceability) |
Under what conditions was production carried out? Which test values are available? |
Audit, root cause analysis |
Torque, temperature, worker ID, tool ID for each component |
Complete traceability is not a system - it is the interaction of four levels of data. If one of them is missing, there are gaps that become critical in an audit or recall.
Every batch of material that goes into production must be clearly identifiable and traceable. This means: batch ID, supplier, delivery date, material number and - in regulated industries - material certificate and traceability back to the origin of the raw material.
The relevant process parameters must be documented for each manufactured part or batch at the time of production: Machine number, tool ID, torque, temperature, pressure, feed rate, cycle - varying depending on the process. This data forms the basis of every root cause analysis.
Crucially, the process data must be linked to the batch number or serial number based on a time stamp - not just stored in parallel over time.
Each test result - IO or NOK, measured value, limit value, test date, tester ID or test equipment ID - must be assigned to the tested part or batch. Auditors require complete proof of this: Who tested what and when? With what means? What was the result?
Which customer received which batch? On which date? With which delivery bill number? In the event of a recall, this information is vital - and must be retrievable within hours, not days.
In practice, this level is often the best documented - because ERP systems have been tracking deliveries for decades. The weak point usually lies in the link to the production level: ERP knows the batch, MES knows the process parameters - but do they talk to each other?
Traceability is not an IT issue. It is a corporate security issue. If you can't say within two hours which customer parts are affected in an emergency, you either pay for a mass recall - or for a legal dispute. Both are more expensive than a good data infrastructure.
-Korbinian Hermann CEO, CSP Intelligence GmbH
Traceability in Germany and the EU is regulated by a network of standards, directives and industry-specific requirements. This overview shows what the most relevant regulations actually require - and what is often misinterpreted.
In clause 8.5.2, ISO 9001 requires organizations to identify the outputs of production and service provision throughout the entire provision process, where traceability is a requirement. Crucially, the standard does not prescribe how - but that traceability must be possible.
In practice, this means: documented batch numbers or serial numbers for all quality-relevant parts, allocation of process parameters to production batches and traceable test results for each batch or component.
IATF 16949 goes much further than ISO 9001. Section 8.5.2.1 explicitly requires traceability for all parts in the automotive industry - including parts from subcontractors. This means that not only the company's own production data must be traceable, but also the quality certificates of the supply chain.
|
IATF 16949 requirement |
The details |
Typical weak point |
|---|---|---|
|
Batch traceability down to serial number level |
It must be possible to assign each individual part to its time of production, its process parameters and its test result. |
Serial tracking ends at the sub-supplier boundary |
|
Traceability with sub-suppliers |
8.4.2: Suppliers must fulfill the same traceability requirements. |
No verification of supplier traceability |
|
Retention obligations |
Quality data: at least 15 years after the last delivery (longer depending on customer requirements). |
Data deletion after ERP migration without archiving |
|
Recalibration evaluation |
If a measuring device is found to be faulty, all parts tested with it must be traced. |
No link between test equipment ID and test results |
The new EU Product Liability Directive (Directive 2024/2853/EU), which must be transposed into national law by mid-2026, represents the biggest change in European product liability law since 1985. Three points are particularly relevant for manufacturing companies.
Conclusion : With the new Product Liability Directive, traceability is no longer an audit issue - it is liability protection. Companies without complete production data will bear a significantly increased liability risk from 2026.
In addition to the standards mentioned, there are a number of industry-specific requirements that are binding for suppliers to the German automotive industry. VDA Volume 6.3 defines process audit requirements including detailed proof of traceability. AIAG-VDA FMEA (since 2019) requires that traceability controls are explicitly considered in the risk assessment. The EU MDR (Medical Device Regulation) applies to medical devices, which prescribes unique device identification (UDI) and full traceability throughout the entire product life cycle.
The most common answer to the question "Is your production traceable?" is: "Yes, we have it all in the ERP". Or: 'Yes, we document all batches'. This is often true - but it's still not enough.
The ERP knows the batch. The MES knows the machine parameters. The quality system knows the inspection results. But which batch was tested at what time on which machine and with what result? If this link is missing, you have three data silos - but no traceability.
A genuine root cause analysis or a recall decision within hours is not possible under these circumstances. If you need days to do this, you have often already initiated a complete production stop or an uncontrolled recall in that time.
Many companies can trace their own production - but as soon as it comes to supplier parts, the traceability chains end. 'That's the supplier, they have to document it. This is legally correct - but it doesn't help if the auditor wants to see the complete component file or if recall coordination across several stages of the value chain becomes necessary.
Batch traceability is sufficient for many applications. In the safety-critical automotive industry - especially for safety-relevant components of IATF safety class A - serial number traceability is required: Each individual part must be able to be assigned to its specific time of production and its specific process parameters. Batch traceability is then not a sufficient solution.
Handwritten test reports, paper logbooks, Excel spreadsheets - they exist and are formally documented. But in the case of a recall involving 50,000 parts over 36 months, paper documents are not a practical traceability solution. They are an archive that nobody can search through.
|
SELF-CHECK: HOW GOOD IS YOUR TRACEABILITY REALLY? ① Can you name all customers who have received a specific faulty batch in under 2 hours? ② Can you retrieve the process parameter data record for each delivered part at the time of production? ③ Are test results linked to the test equipment ID and calibration status? ④ Is your traceability data still fully retrievable after 10 years? ⑤ Are subcontractor batch records linked to your own system? If you answered 'no' to any of these questions: Here are your gaps. |
An experienced auditor does not ask abstract questions about your traceability system. He puts a specific part on the table and asks: 'Show me the complete component file. This part file must be available within minutes - not in two hours.
|
Element |
What the auditor checks |
Typical location of gaps |
|---|---|---|
|
1. identification |
Serial number or batch number clearly present? |
Missing or duplicate serial numbers, illegible engravings |
|
2. proof of material |
Which raw material, which supplier, which batch? |
No supplier certificate or outdated document |
|
3. production parameters |
Machine ID, tool ID, critical process parameters at the time of production |
Parameters only at layer level, not at part level |
|
4. test certificate |
IO/NIO, measured value, limit value, inspector ID, test equipment with calibration certificate |
Collective records without component assignment |
|
5. release |
Who has released? When? With which proof of authorization? |
Release not documented or unauthorized person |
|
6. delivery |
Which customer, which date, which delivery bill number? |
Known in ERP, but not linked to production data |
|
7. recalibration |
Were all parts tested with a specific test equipment identified if this equipment was faulty? |
Test equipment ID not linked to test result |
When I walk into a production facility and ask: 'Show me the complete component file for this part here' - I can tell in the first three minutes whether traceability really works or whether it only exists on paper. It's usually the latter. Not because the data is missing, but because it doesn't work together.
-Amadeus Lederle Chief Technology Evangelist, CSP Intelligence GmbH
This 5-step plan is designed for companies that want to improve their traceability pragmatically and without a major IT project. The goal: audit readiness and recall capability within 2-3 months.
Create an overview of all systems in which quality-relevant data is stored: ERP, MES, QMS, standalone inspection systems, Excel spreadsheets, paper documents. For each system: What is stored? At what level (batch, serial number, shift)? How long is it archived? Is it linked to other systems?
This inventory typically takes 1-3 days and uncovers the most serious gaps. Our data audit sheet from the white paper structures this process.
Not every gap has the same risk potential. Prioritize according to two criteria: Which data is required by standards (IATF, ISO, customer requirements) and which data would be most critical in the event of a recall or audit? Start with the gaps that fulfill both criteria.
The simplest and most effective step: make sure that the batch number is used as a common key in all relevant systems. If ERP, MES and QMS use the same batch number, the data can be linked at any time - even if they are in different systems.
That sounds trivial. In practice, it is the most common starting point for rapid improvements: Different batch number systems are often maintained in different systems.
Paper test reports are archived but not searchable. Process parameters in machine logbooks exist but are not linked to the part. Identify the three most critical manual documentation processes and digitize them first. Systems like CSP IPM capture process data directly from the control level and automatically link it to the batch or serial number.
Take any delivery batch from the last six months and try to reconstruct the complete component file: Material, process parameters, test results, proof of delivery. Measure how long it takes. If it takes you longer than 30 minutes, you still have work to do. The goal: less than 10 minutes for the complete component file.
Complete digital traceability is not a product that you buy. It results from the controlled interaction of several systems that are connected via a common data key.
|
The system |
Traceability contribution |
Typical weakness |
Priority |
|---|---|---|---|
|
ERP (SAP, MS Dynamics, ...) |
Order-batch assignment, supplier verification, delivery documents |
No real-time reference to production level, batch granularity too coarse |
High |
|
MES (Manufacturing Execution System) |
Production orders, machine allocation, production parameters |
Often not linked to QMS or ERP |
High |
|
QMS / inspection systems |
Inspection results, IO/NIO, measured values, inspector IDs |
Collective records without individual part assignment |
Very high |
|
Worker guidance system |
Assembly steps, worker ID, tool ID per component |
Lack of serialization at individual part level |
High for automotive |
|
Archiving system |
Long-term archiving with retrievability after 15+ years |
ERP migration without data transfer, media discontinuity |
Very high |
Not every production process needs serial number traceability. The decision depends on three factors: Standard requirements, safety criticality of the component and recall efficiency.
|
Level |
When sufficient |
When not sufficient |
|---|---|---|
|
Batch traceability |
Mass production with homogeneous process conditions per batch. Low safety class. ISO 9001 without IATF. |
Safety class A according to IATF 16949 if individual parts of a batch had different process conditions. |
|
Serial number traceability |
Safety-relevant components (IATF class A). High-priced individual production. Medical technology (MDR). Aviation. |
Not required for simple standard or purchased parts without specific quality requirements. |
Traceability costs - in time, infrastructure and process costs. But the alternative is more expensive. And in a way that is particularly painful for companies: not predictable, but when it is most unfavorable.
|
Scenario |
Without complete traceability |
With complete traceability |
Difference |
|---|---|---|---|
|
Recall due to faulty supplier part |
Full recall: all 12,000 parts of the delivery month. Costs: approx. €2.4 million |
Targeted recall: 340 affected parts identified. Costs: approx. 280,000 € |
Savings: approx. €2.1 million |
|
IATF audit with traceability findings |
Class A findings: Production stop until shutdown. 3-5 days downtime. Costs: approx. 400,000 € |
No findings, all evidence retrievable. Audit duration: -40%. |
Savings: approx. 400,000 € + reputation protection |
|
Product liability claim without evidence |
Reversal of burden of proof according to new EU directive: No proof of production = presumed defect. Compensation possible. |
Complete production file as exculpatory evidence. |
Potential: Damages avoided |
These figures are reference values based on publicly available recall studies and industry reports. The actual ROI depends on the production volume, the industry and the type of quality incidents.
Investing in a complete digital traceability infrastructure is a real challenge for many SMEs. At the same time, practical experience shows that most of the necessary systems are already in place in most manufacturing companies - but they are not connected.