B2B Integration

Heat and Coil Traceability on the EDI 856

When a coil leaves a mill or a service center, the paperwork has to say exactly which coil it is. More metals customers now want that answer inside the EDI 856 advance ship notice: heat number, coil or tag ID, and weights for each individual piece, not just a total for the order line.

Getting this right depends less on the X12 standard than on where your ERP keeps the data. This article walks through how heat and coil traceability is usually carried in an 856, where it breaks, and what to check before a customer’s spec lands on your desk.

Why customers ask for piece-level detail

A buyer receiving steel wants three answers before it unloads the truck: what is on it, which heats it came from, and whether the certifications match. With piece-level data in the ASN, the receiving dock can scan each tag, match it to the 856, and put the material away against the right purchase order and heat without anyone keying it in.

Traceability matters again later. If a quality problem shows up in a finished part, the customer traces it back through its own production records to a coil, then to a heat, then to the mill’s test results for that heat. If the heat number never made it into their system at receipt, that chain breaks at the first link.

How the data usually sits in an 856

An 856 is built as a hierarchy. For metals shipments the common order is shipment, then order, then the individual pack (a coil, a bundle, or a lift), then the item inside it. Each level carries its own details:

  • Shipment level: carrier, bill of lading, ship date, and total weight for the load.
  • Order level: the customer’s purchase order and release numbers.
  • Pack level: one entry per coil or bundle, with the tag or barcode number printed on its physical label.
  • Item level: product, grade, dimensions, quantity, and the heat number.

The exact segments and qualifiers come from the customer’s implementation guide. Some want the heat number as a product reference on the item line, others as a separate reference segment, and many want gauge, width, and net, gross, and theoretical weights as measurement segments. Two customers buying the same product can ask for the same facts in different places, which is why each one gets its own map.

Where traceability breaks

The heat number lives in inventory, not on the order

Most ERP systems tie the heat number to an inventory record or a tag, not to the sales order line. If the ASN is generated from order data alone, the heat is simply missing. The map has to read the pick or shipping record that links each tag to its heat, which often means pulling from a different table than the rest of the 856.

Slitting and cut-to-length create new pieces

Processing turns one master coil into several slit coils or a stack of sheets, each with a new tag. The customer still wants the original heat on every one of them, and sometimes the parent coil ID as well. If the processing step does not carry the parent’s heat forward to each child tag, the ASN can only report what the system knows.

Mixed heats in one bundle

A bundle or lift built from more than one heat needs either one item line per heat or a rule against mixing. Some customer specs forbid mixed heats in a single pack; others accept them if every heat is listed. Either way, the decision has to be made on the shop floor before the 856 is built.

Weights that disagree

Scale weight, theoretical weight, and invoiced weight can all differ. If the 856 reports one and the 810 invoice bills another, the customer’s three-way match fails and the invoice waits. Agree up front which weight each document carries.

Timing

An ASN that arrives after the truck is not an advance ship notice. It should be generated at shipment confirmation, not batched with invoicing at the end of the day, or the receiving dock is back to paper.

The test report that travels with the heat

Piece-level ASNs pair with test data. Many metals customers also want the chemistry and mechanical results for each heat, either as an EDI 863 report of test results or as a certification file. The heat number is the key that ties the two together, so an error in one shows up in both. We cover that document in mill test reports over EDI.

What to check before the spec arrives

  1. For every tag on a truck, can your shipping process tell you the heat number, the parent coil if it was processed, and the actual weight?
  2. Does the barcode on the label match the tag ID your system stores, character for character?
  3. Is the ASN triggered by shipment confirmation, or by something that happens later?
  4. Do you have a rule for mixed-heat bundles?
  5. Which weight does each document carry: the 856, the 810, and the packing list?

If any answer is “it depends who is on shift,” fix that first. The map can only send what the system records.

How we handle it

Foundational has managed EDI for mills, service centers, and processors for more than 25 years, and metals transactions are central to that work. A significant number of the metals companies we work with run on IBM i, and our team knows where heat and tag data tend to live in those systems. We build the 856 map from the records that actually hold the traceability data, test it against the customer’s spec, and keep it current when the spec changes. We process over 47,000 EDI transactions a month for Nucor, and McNeilus Steel grew its EDI program by 500% with us (read the McNeilus case study).

For the full list of metals documents we manage, see EDI for steel processing. If a customer has just sent you an 856 spec with traceability requirements, send it to us and we will tell you what your system needs to supply. If EDI itself is new to you, start with what to do when a customer requires EDI.

Ready to simplify your EDI operations?

Talk to a specialist about your trading partners, ERP, and current EDI setup. Talk to a Specialist
← Mill Test Reports over EDI: How the 863 Works
EASI Standards EDI: Integration for Embellished Activewear →
← All posts