How Pixel ERP Manages Heats, Coils and Grades in a Steel ERP

Ask any steel processor where their real production data lives and the honest answer is usually a stack of registers, a whiteboard in the rolling mill and a spreadsheet the quality team maintains by hand. A generic ERP built for counting cartons simply has no concept of a heat splitting into coils, a coil being slit into narrower coils, or a grade carrying a chemistry that must be certified. So the ERP records a vague finished quantity while the plant keeps the truth somewhere else.

That gap is expensive. When a customer disputes a grade, when an auditor asks for full traceability, or when a bad batch has to be recalled, nobody can walk the material backwards from the dispatched coil to the original heat in minutes. A steel processing operation needs an ERP that thinks the way the plant thinks — in heats, coils, bundles, lots and grades — not one that flattens all of that into a single stock line.

A heat is the unit of melting — one batch from the furnace or the incoming supplier certificate — and in Pixel ERP it becomes a first-class identity the moment material is received or produced. Each heat carries its own number, its source (in-house melt or a specific supplier lot), its grade, its declared chemistry and its mill or internal test certificate. From that point every downstream coil, bundle and off-cut inherits a permanent link back to its parent heat.

What the heat record captures out of the box:

• Heat number and origin — unique identity tied to the melt or the incoming supplier lot and its documents.
• Grade and chemistry — declared composition against the grade specification, with pass or fail on acceptance.
• Test certificates — mill certificate and any internal lab results attached to the heat, not filed away separately.
• Weight in and weight out — captured in tonnes and kilograms so the heat reconciles against its coils and scrap.
• Full lineage — every coil, slit coil and bundle produced from the heat linked back to it automatically.

Because this is a configured product and not a one-off build, if your plant numbers heats a particular way, or maps supplier heats to your own grade codes, that becomes a no-code setting rather than a software change.

Coils are where most steel ERPs quietly lose the plot. A single hot-rolled coil goes into a slitting line and comes out as several narrower coils plus edge trim and scrap. Later one of those slit coils is re-slit, cut to length or sent for galvanising. Pixel ERP models each of these conversions as a real transaction with defined inputs and outputs, so the parent coil, the child coils and the by-products all stay connected by weight.

That means at any moment you can point at a slit coil in the yard and see the coil it came from, the heat behind that coil, its grade and its certificate — and equally, from a heat you can fan out to every coil it ever became. This is the traceability spine that makes recalls, complaints and audits a five-minute query instead of a two-day paper hunt. It also feeds straight into yield and weight-based costing, because every conversion already knows its input and output weights.

In Pixel ERP a grade is not just a label — it is a specification with a chemistry range, acceptance rules and, where you want it, grade-based pricing. When material is received or produced, its declared chemistry is checked against the grade specification, so off-spec material is flagged rather than silently mixed into good stock. When an order calls for a specific grade, the system only lets the right material be allocated, so you never dispatch a lower grade against a premium order by mistake.

A grade record typically drives:

• Acceptance — incoming or produced material validated against the grade chemistry range before it counts as good stock.
• Allocation — sales orders reserve and dispatch only the correct grade, with substitution rules where you allow them.
• Pricing — grade-linked rates so quotations and invoices reflect the true value of what is shipped.
• Certificates — test-certificate formats configured per grade and per customer, generated from the heat and coil data automatically.

Every one of these behaviours is configuration inside the product, which is why adapting Pixel ERP beats trying to bolt grade logic onto a generic system after the fact.

Here is how a single coil moves through the steel ERP from gate to dispatch:

• Inward — the HR coil is weighed on the weighbridge, its heat number and supplier certificate are captured, and its grade chemistry is validated on receipt.
• Storage — the coil lands in a yard location with its weight, grade and heat, visible in real-time stock by grade and by heat.
• Slitting — a slitting job consumes the parent coil and produces child slit coils plus edge trim and scrap, each new coil linked to the parent and the heat.
• Value addition — a slit coil is sent for galvanising as job-work, tracked at the vendor by weight and received back against a challan.
• Order allocation — a customer order for a specific grade reserves the matching coils; wrong grades are simply not offered.
• Dispatch — the coil is weighed out, a grade-specific test certificate is generated from its heat data, and the e-invoice and e-way bill are raised on the actual dispatched weight.

Every step above leaves an auditable trail, so the finished delivery still knows the heat it was born in. For the compliance side of that final step, see our companion guide on weighbridge, tonnage and GST e-invoicing.

Because Pixel ERP is AI-native, you do not have to build a report to find a heat. You ask — "where is heat 4821 now?", "which coils came from last Tuesday's melt?", "what closing stock do I hold in grade E250?" — and get the answer with the numbers behind it, on screen or by voice across the yard.

The same intelligence watches for trouble it can see in the data: a grade running short against confirmed orders, a heat whose coils are drifting off-spec, or material ageing in the yard. It surfaces these early, so heat, coil and grade data becomes a decision tool rather than a filing cabinet.