Ask any plant head at an Indian steel mill what their ERP struggles with, and the answer is rarely "reports" or "dashboards." It is that the software was never built to think in heats, coils, grades and yield. Generic ERP counts pieces. Steel does not move in pieces. It moves as a heat of molten metal that becomes coils, plates and bars, each carrying a grade, a chemistry, a mill test certificate and an actual weight that never quite matches the theoretical one. When your ERP cannot hold those concepts natively, your team ends up running the real plant in spreadsheets and treating the ERP as an expensive filing cabinet.
This guide walks through the four ideas a real steel ERP software has to get right — heats, coils, grades and yield — and how a ready, AI-native platform can adapt to them without a bespoke build. If you run an integrated plant, a re-rolling mill, a processing centre or a stockyard, this is the vocabulary your system needs to speak. For the full picture, our steel ERP software pillar page ties every one of these threads together.
Why generic ERP breaks on the shop floor
A conventional ERP models inventory as countable, interchangeable units: 500 screws, 20 laptops, 8 pumps. Steel violates every assumption in that model. Two coils of the same nominal specification can differ in weight by dozens of kilograms. A single heat splits into many products across many customers. A grade is not a label — it is a chemistry with tolerances that decide whether material can ship or must be held. And the number that actually gets invoiced is the weighbridge weight, not the count on a challan.
Force steel into a piece-counting ERP and three things happen. Traceability collapses because heat numbers live in a notebook, not the system. Costing drifts because material is valued on theoretical weight while it is bought and sold on actual weight. And yield — the single most important lever on steel margin — goes unmeasured because the ERP has no concept of input weight versus output weight. A purpose-built steel ERP fixes the data model first, and everything else follows.
Heats: the unit of truth in a steel plant
Everything in a steel operation traces back to a heat — the batch of molten steel tapped from a furnace, identified by a heat number and defined by its chemistry. Get heat tracking right and quality, compliance and traceability all become straightforward. Get it wrong and every customer complaint turns into an archaeology project.
What a heat record must carry- The heat number as the master identifier, generated at the furnace and carried forward to every downstream product.
- Full chemistry — carbon, manganese, sulphur, phosphorus and the rest — captured against grade tolerances.
- The linked mill test certificate (MTC) so quality data travels with the material, not in a separate folder.
- A live parent-child link from the heat to every coil, plate, billet or bar it produces, and onward through each processing step.
Forward and backward traceability
The test of real heat tracking is simple: pick any dispatched bundle and ask two questions. Which heat did this come from? And which other customers received material from the same heat? A steel ERP answers both in seconds. That capability is not a nice-to-have — it is what turns a quality claim, a customer audit or a recall from a week of panic into a five-minute query. Pixel ERP maintains this genealogy automatically as material flows, so nobody has to reconstruct it after the fact.
Coils, plates and bars: tracking form as well as material
A heat becomes physical products, and those products have form: a coil has an inner and outer diameter, a width, a thickness and a running weight; a plate has length, width and thickness; a bar has a section and a length. Two coils from the same heat and grade are still distinct objects with their own weights and their own histories once processing begins.
A steel ERP therefore tracks stock at the level of the individual coil or lot, not as an anonymous tonnage bucket. That is what lets a stockyard say "we hold 4.2 tonnes of this grade in three coils, one of which is already committed to an order" rather than just "we have some." It is also what makes weight-accurate picking, ageing analysis and grade-wise stock reports possible. When your inventory is coil-level, your steel processing planning and your dispatch both get sharper.
Grades and chemistries: the specification master
Grade is where steel ERP earns its keep. A grade master holds the chemistry ranges, mechanical properties and customer-specific requirements that define whether material conforms. During inspection, dimensional and metallurgical results are checked against the relevant grade, and hold-and-release control is tied directly to the heat and coil record so out-of-spec stock cannot quietly ship.
- A grade and specification master that stores chemistry ranges, mechanical properties and named customer specs.
- Tolerance checks at goods-receipt and after each processing step, flagging anything outside band.
- Quality hold and release workflows attached to the heat/coil so material is blocked until cleared.
- Grade substitution rules — so planning knows when a higher grade can legitimately fulfil a lower-grade order, and at what cost.
Because Pixel ERP is configured rather than custom-coded, your metallurgist can add a new grade attribute, tighten a tolerance or introduce a customer specification through no-code tools — live, without waiting on a developer release. That matters in a business where a single new export customer can bring a whole new spec sheet.
Yield: the number generic ERP never measures
On high-value steel, yield is margin. Every operation — slitting, cut-to-length, shearing, pickling, annealing — converts input weight into a smaller output weight plus scrap, end-bits and process loss. If your ERP does not record input weight against output weight at each step, you are flying blind on the one metric that most directly controls profitability. Our companion post on ERP for steel processing: slitting, cutting and scrap tracking goes deep on this; here is the essential idea.
Yield has to be measured per operation, machine and grade
A single blended "yield %" for the whole plant hides the losses that actually cost money. Real steel ERP records yield at the operation level, so you can see that one slitter runs at 96% on a given grade while another runs at 91%, or that a particular grade consistently loses more at cut-to-length. Those differences are invisible in a piece-counting system and obvious in a weight-native one. Pixel ERP captures the weights at each step and turns them into yield-by-machine, yield-by-grade and scrap-recovery reporting you can actually act on.
Steel ERP readiness checklist
Use this as a quick scorecard when you evaluate any steel ERP software. The more boxes it ticks natively — without "we can customise that" — the closer it is to fitting a real plant.
- Tracks material as heats and coils, not anonymous piece counts.
- Links mill test certificates to the heat and carries them to dispatch.
- Holds a grade master with chemistry, mechanical properties and customer specs.
- Runs tolerance and quality hold/release tied to the heat/coil record.
- Reconciles theoretical vs weighbridge weight at receipt and dispatch.
- Records input vs output weight and scrap at every processing operation.
- Reports yield by operation, machine and grade, not a single blended number.
- Lets non-technical staff change grades, tolerances and reports with no code.
Generic ERP vs a steel ERP, at a glanceCapability Generic ERP Steel ERP (Pixel ERP) Inventory unit Countable pieces Heats, coils and lots by actual weight Grade & chemistry A text field, if that Full grade master with tolerances Traceability Manual, in notebooks Automatic heat-to-dispatch genealogy Weight handling Theoretical only Theoretical reconciled to weighbridge Yield & scrap Not measured Per operation, machine and grade Changing the system Developer & release cycle No-code configuration, live
Frequently asked questionsIs a steel ERP just a generic ERP with a steel module bolted on?
No. The difference is in the core data model. A steel ERP treats heats, coils and actual weight as first-class objects and carries grade and traceability through every step. A generic ERP with a light "steel add-on" still counts pieces underneath, which is where it breaks. Pixel ERP is built to operate in heats, coils and weight and adapts to your plant without custom development.
Can it link mill test certificates to finished dispatches?
Yes. Every heat carries its MTC and chemistry, and Pixel ERP maintains the parent-child link from heat to coil to processed product to dispatch. Any shipped item can be traced back to its originating heat and forward to every customer that received material from it.
How is yield actually calculated?
Each processing operation records input weight against output weight, with scrap, end-bits and process loss captured at the step. Yield is then reported by operation, machine and grade — not as a single plant-wide figure — so you can see exactly where weight and margin are lost.
Do we need a custom build to get steel-specific behaviour?
No. Pixel ERP is a ready, AI-native ERP product that is configured, not custom-coded. Your grades, tolerances, weight logic and processing steps are set up through no-code configuration, so you get steel fit in weeks and can keep changing it without depending on one developer.
Does it work for processing centres and traders, not just integrated plants?
Yes. Integrated plants use the full heat-to-dispatch chain; processing centres lean on yield and tolerance control; traders and stockists rely on grade-wise, weight-accurate stock and fast weight-based invoicing — all on the same adaptable platform. See our steel and steel processing page for how it maps to your setup.
Keep reading
| Capability | Generic ERP | Steel ERP (Pixel ERP) |
|---|---|---|
| Inventory unit | Countable pieces | Heats, coils and lots by actual weight |
| Grade & chemistry | A text field, if that | Full grade master with tolerances |
| Traceability | Manual, in notebooks | Automatic heat-to-dispatch genealogy |
| Weight handling | Theoretical only | Theoretical reconciled to weighbridge |
| Yield & scrap | Not measured | Per operation, machine and grade |
| Changing the system | Developer & release cycle | No-code configuration, live |
Is a steel ERP just a generic ERP with a steel module bolted on?
No. The difference is in the core data model. A steel ERP treats heats, coils and actual weight as first-class objects and carries grade and traceability through every step. A generic ERP with a light "steel add-on" still counts pieces underneath, which is where it breaks. Pixel ERP is built to operate in heats, coils and weight and adapts to your plant without custom development.
Can it link mill test certificates to finished dispatches?
Yes. Every heat carries its MTC and chemistry, and Pixel ERP maintains the parent-child link from heat to coil to processed product to dispatch. Any shipped item can be traced back to its originating heat and forward to every customer that received material from it.
How is yield actually calculated?
Each processing operation records input weight against output weight, with scrap, end-bits and process loss captured at the step. Yield is then reported by operation, machine and grade — not as a single plant-wide figure — so you can see exactly where weight and margin are lost.
Do we need a custom build to get steel-specific behaviour?
No. Pixel ERP is a ready, AI-native ERP product that is configured, not custom-coded. Your grades, tolerances, weight logic and processing steps are set up through no-code configuration, so you get steel fit in weeks and can keep changing it without depending on one developer.
Does it work for processing centres and traders, not just integrated plants?
Yes. Integrated plants use the full heat-to-dispatch chain; processing centres lean on yield and tolerance control; traders and stockists rely on grade-wise, weight-accurate stock and fast weight-based invoicing — all on the same adaptable platform. See our steel and steel processing page for how it maps to your setup.