Most service centers maintain good cert traceability through receiving (Step 1) and storage (Step 2). The break happens at value-added processing — when the material changes form. That's Step 3, and it's where the cert chain stops following the material.
This isn't a rare failure. It's the default outcome when value-added operations aren't specifically engineered to propagate cert data.
What Value-Added Operations Do to the Cert Chain
Slitting changes width. Blanking changes dimensions. Leveling changes flatness. Shot blasting changes surface condition. Pickling changes surface chemistry. Cut-to-length operations change length.
None of these operations change the material's chemistry or mechanical properties. The original mill cert — with its heat number, chemistry, tensile and yield values — still applies to every piece that comes out of every one of these operations. The cert doesn't become invalid because the coil became a strip.
But operationally, the piece that comes out of the slitting line looks different from what went in. It has different dimensions. It may have a different SKU. In most ERP implementations, it gets a new inventory record — and that new record doesn't automatically carry the heat number from the original coil.
The Step 3 Break in Detail
Follow a specific coil through the three steps:
Step 1 — Receiving: The coil arrives. The receiver matches the heat number on the physical coil to the heat number on the mill cert. The receiving record is created with the heat number and cert reference. The coil enters stock linked to its cert. This step works.
Step 2 — Storage: The coil sits in the warehouse. The inventory record maintains the heat number and cert reference. The coil can be located, its cert retrieved, its heat number confirmed. This step works.
Step 3 — Slitting: The coil goes to the slitting line. The slitter produces six strips of different widths. The ERP creates six new inventory records — one per strip. In a default ERP configuration, these six records are created without inheriting the parent coil's heat number. The six new records show grade, dimension, and weight. They show no heat number. They show no cert reference.
At this point, six certified strips of steel exist in the warehouse, and the system has no record of which heat they came from.
Why ERP Systems Don't Prevent This
This is a structural issue, not a bug.
ERP systems are designed to create new stock records when a processing operation creates a new dimension or a new SKU. The new record is a new inventory item — optimized for picking, shipping, and reordering. It was not designed to propagate cert data from the parent record.
In most ERP implementations, propagating the parent heat number to child records requires either a custom workflow configuration, a manual data entry step performed by the slitting operator, or a post-processing data reconciliation step. None of these are standard out-of-the-box behavior.
The operational result: the people who configure ERP systems for service centers are optimizing for inventory accuracy and warehouse efficiency. Material traceability is a quality function that may not have been at the table during the ERP configuration project. The gap gets noticed the first time a quality-critical customer asks for heat-number documentation on a slit strip.
What ASTM Actually Requires
ASTM standards don't specify a software system or a documentation format. What they require is that any test report issued for a material can be traced back to the heat that was tested.
If a slit strip cannot be traced to its source coil's heat number, it cannot be presented as certified to ASTM. It doesn't matter that the original coil cert is on file. If the strip-to-coil link doesn't exist in your records, the strip's cert is unverifiable.
Customers conducting quality audits — particularly in automotive, energy, and defense supply chains — will test this chain. They'll ask: show me the heat number for this strip. Show me the cert for that heat. Show me how you know this strip came from that coil.
If the answer requires manual reconstruction rather than a system record, that's a finding.
The Fix
Configure the processing workflow to propagate the parent heat number to all child items created by processing operations. This is a workflow rule, not a technology purchase. Your existing ERP almost certainly supports parent-child record relationships — the configuration question is whether heat number inheritance is turned on.
If your ERP doesn't support automatic propagation, implement a manual step: the slitting operator logs the parent coil heat number against the strip run before the strips are put away. The log entry is the traceability record.
The operational cost is low. The compliance cost of not doing it is not.