Every time you cut a plate or split a coil, you create a traceability problem. The original mill cert covers the full heat. The cut pieces and remnants are fractions of that heat — and each one needs a traceable link back to the original cert.
The fix is straightforward. The execution requires a deliberate process, because the default behavior of most inventory systems actively works against it.
The Two Models for Handling Post-Cut Traceability
There are two valid approaches to maintaining cert linkage after cutting operations. The choice between them depends on what your customers require.
Model 1: Cert relay. Each cut piece references the original mill cert. The cert isn't copied or duplicated — it's referenced. The piece ID, the lot record, or the shipping document points back to the original cert number and heat number. The customer receives the original MTC along with a reference showing which piece came from which heat.
Model 2: Cert supplement. The service center or distributor issues a new document — a supplemental cert or a test report — that references the original mill cert and describes the piece's relationship to it. The supplement identifies: the original heat number, the original cert reference, the cut dimensions of the piece, and the date and nature of the processing operation.
Both are valid. Cert relay is simpler and is preferred where the original cert is sufficient to meet the customer's requirements. Cert supplements are used when the customer requires documentation issued on the supplier's letterhead, or when the original cert format doesn't accommodate the piece-level detail the customer needs.
Where Traceability Breaks After Cutting
The breakpoints are predictable.
ERP creates a new stock item at the cut. When a plate is cut to a non-standard dimension, most ERP systems create a new inventory record for the resulting piece. That new record has its own item number, its own location, its own lot ID — and in a default configuration, it carries no reference to the parent material's heat number. The cert link is severed at the creation of the new record.
Coil-to-strip conversions. A coil is slit into eight strips. All eight strips have the same heat number — they're fractions of the same certified heat. But the slitting operation creates eight new inventory records, and in most implementations, only the records for the strips that go to active orders carry a cert reference. The rest are filed as "uncertified remnant" and lose their heat number linkage within weeks.
Partial pallet picks. Material is received on a pallet of 20 pieces, all from the same heat. Orders pick 3 pieces, then 5 pieces, then 4 pieces over several weeks. If the system updates the cert linkage only on the first pick and treats subsequent picks as "same pallet," the later picks may not have a complete individual cert record.
The Slitting Case in Detail
Slitting is the highest-volume cert-traceability problem in metals service centers. A single coil can generate dozens of strips going to dozens of different customers. Each strip is a different dimension, potentially a different SKU, potentially going to a customer with different cert requirements.
The correct approach: the original coil heat number is the anchor through all operations. When the coil goes to slitting, each resulting strip is assigned an ID that carries the coil's heat number as a parent reference. The strip ID, the heat number, and the cert reference travel together through the system from slitting through storage through shipping.
This is not a complex data model. It's a parent-child record with three fields: strip ID, parent coil heat number, parent cert reference. What makes it operationally difficult is that ERP systems typically create the strip records in a batch without parent references, and establishing those references requires either a custom configuration or a manual step that many implementations skip.
The Practical Solution
Use the heat number as the persistent anchor. Every cut, slit, or split operation creates new physical items but does not create a new heat. The original heat number propagates to every piece derived from it, regardless of what processing operations occurred in between.
Configure your inventory system so that processing operations inherit the parent heat number automatically. If your system can't do this without customization, the minimum viable alternative is a processing log that maps every output piece back to its input heat — maintained at the time of processing, not reconstructed afterward.