On this page
- The short answer
- Which steel business you run
- Map the real steel lifecycle
- What makes steel different
- Can a generic ERP work?
- The customer specification
- Where heat identity begins
- FOLLOW THE HEAT
- If you did not create the heat
- Physical identity below the heat
- RECONCILE THE WEIGHT
- Do not call it all “loss”
- Yield from the real record
- Quality attached to material
- Quality status must act
- Trace a complaint backwards
- Find downstream material
- WIP and yard inventory
- Multiple plants and yards
- Grade and size planning
- The rolling programme
- Semi-finished inventory
- Downstream processing
- Outside processing and job work
- Allocate the right stock
- Dispatch and the order
- The quality certificate
- The weighbridge
- Costing
- Recovered scrap and rework
- The difficult scenarios
- Standard or custom?
- Red flags
- Evaluation record
- What customer proof?
- Nezone Group proof
- How exactllyERP fits
- Checklist
- Go Deeper
One company may melt scrap and create its own heat. Another may buy billets, blooms, ingots, coils or plates and inherit the supplier’s heat or material identity. A downstream processor may cut, slit, coat, draw, galvanise or otherwise transform purchased steel without operating a melt shop at all.
That is why an ERP should not be judged simply by asking whether it supports manufacturing, inventory or batch tracking.
The buyer needs to know whether the operating record can preserve the material identity that matters, reconcile weight through each transformation, keep quality evidence attached to the material, and connect the customer’s specification to the exact stock that is finally dispatched.
The useful question is not “Does your ERP support steel manufacturing?”
It is “Can you show us where this material came from, what happened to its weight, what quality evidence belongs to it, and whether the material dispatched is exactly what the customer ordered?”
The short answer
A steel company should evaluate ERP by following the real material and commercial chain.
Melt-and-roll route
For a melt-and-roll operation, that chain may include:
- source material
- heat
- casting
- billet / bloom / slab
- reheating
- rolling
- finishing
- bundle / coil / plate / section
- quality evidence
- warehouse / yard
- dispatch
Reroller or downstream route
For a reroller or downstream processor, the operating record may begin differently:
- purchased billet / coil / plate
- inherited supplier heat or material identity
- processing
- finished physical stock
- quality evidence
- warehouse / yard
- dispatch
The exact route depends on the business.
The important test is whether the proposed ERP can preserve the right genealogy, reconcile input and output weight, distinguish usable output from recoverable or non-conforming material, maintain quality history, and connect the customer’s specification to the material actually delivered.
A module checklist alone cannot prove that.
First identify which steel business you actually run
Before comparing ERP vendors, define where your own steel operating record begins.
Possible operating models include:
Do not force your business into a generic “steel mill” model if that is not how you operate.
Ask:
Where does material first enter our control, and which identity must we preserve from that point onward?
That answer should determine where the ERP genealogy begins.
Map the real steel lifecycle before choosing software
Do not begin with the software menu.
Begin with the material and the customer requirement.
At minimum, map the stages that apply to your business:
Then ask:
At which stages can material identity, weight, specification, quality status or commercial value change?
Those are the points the ERP evaluation must test.
What makes steel ERP requirements different?
Steel businesses still need ordinary ERP capabilities:
The difference is often in how those capabilities connect to physical material.
A customer may order a specific grade, section, size, tolerance or quality-document requirement.
The material may carry a heat or supplier heat identity.
The material may change physical form several times.
Its weight may split into saleable output, WIP, recoverable scrap, rework, downgrade, rejection, co-product where relevant and genuine process loss.
Quality evidence may need to remain attached to the exact physical material eventually dispatched.
So the buyer should not ask only whether the ERP has production, stores and QC modules.
Ask whether those modules preserve the same physical and commercial truth.
Can a generic ERP still be right for a steel company?
Yes.
A steel company should not choose industry-specific software merely because it carries a steel label.
Some businesses have simpler transformation chains.
Some already use specialist plant, MES, laboratory, weighbridge or quality systems around a broader ERP.
Some generic platforms may support the required model through configuration, extensions or connected applications.
The decision should depend on what your critical workflows require.
Ask:
Which steel-specific concepts must the ERP understand directly?
Which can be configured without making operations fragile?
Which belong in connected specialist systems?
Which require custom development?
The label matters less than the evidence.
A claim of steel-industry expertise should make the demonstration more demanding, not less.
Translate the customer specification into an operating requirement
A steel sales order can represent more than an item and a quantity.
Depending on the business, the customer may require combinations of:
The ERP evaluation should test whether that requirement remains intact from the order through stock allocation or production planning to final dispatch.
Ask:
Can the commercial requirement the customer placed remain connected to the material we actually plan, produce or allocate?
Do not accept a demonstration where the order specification is re-entered manually into production, QC or dispatch.
Decide where heat or material identity begins
Identity we create
For some businesses, the ERP may create the heat.
Identity we inherit
For others, the ERP must preserve an identity created by the supplier.
The starting point may therefore be:
Do not assume every steel company creates its own heat.
The useful question is:
What identity arrives with the material, what identity do we create, and which of those identities must survive downstream?
The ERP should preserve the right starting history for the actual business model.
FOLLOW THE HEAT
For a business that creates a heat, this should be one of the hardest ERP tests.
A possible chain may look like:
- charge / source material
- heat
- casting
- billet / bloom / slab
- reheating
- rolling / processing
- finished bundle / coil / plate / section
- quality evidence
- warehouse / yard
- dispatch
The exact stages differ.
The principle does not:
Can the ERP preserve the genealogy from the heat to every relevant downstream material identity?
The heat number should not exist only in the melt-shop record and disappear during rolling, finishing, stores or dispatch.
If you did not create the heat, preserve it
A reroller, service centre or downstream processor may buy material that already carries supplier heat or source identity.
The buyer should then ask:
Can we preserve the supplier’s heat or material identity when we receive, store, process, split, cut, roll, coat, treat or dispatch the material?
The fact that the company did not create the heat does not make genealogy irrelevant.
The ERP should be able to distinguish:
That distinction matters when a customer complaint, quality investigation or supplier issue must be traced backwards.
Track physical identity below the heat
A heat may produce several downstream physical units.
Depending on the product, the business may need to distinguish:
So:
Heat number is not always the complete inventory identity.
The ERP evaluation should ask:
- Which physical material came from this heat?
- Which coil, bundle, plate or piece is this?
- What does it weigh?
- Where is it?
- What quality status applies?
- Is it free, held or committed?
- Which order can it satisfy?
The physical stock record should remain connected to the genealogy behind it.
RECONCILE THE WEIGHT
Steel is a material business.
For every important transformation, the buyer should be able to answer:
What weight went in?
What weight came out?
What remains as WIP?
What was recovered?
What was rejected, reworked or downgraded?
What became a co-product where relevant?
What was genuine process loss?
The ERP should not only post a finished quantity.
It should make the material balance understandable.
This is the steel equivalent of a traceability test: the buyer should be able to follow not only identity, but also the movement of weight.
Do not call every difference “loss”
If input weight and saleable output differ, the entire difference should not automatically be classified as unexplained wastage.
Depending on the process, the difference may include:
The exact categories depend on the plant and product.
The important buyer question is:
Can the ERP explain where the weight went rather than hiding the difference inside one loss number?
That distinction matters operationally and financially.
Calculate yield from the real production record
Yield can be valuable, but it should come from the real input/output record rather than an isolated spreadsheet.
The ERP may need to compare, where applicable:
For a melt-and-roll operation, the business may evaluate melting yield, rolling yield or both.
For a downstream processor, the relevant yield may arise from the processing stage rather than melting.
Do not impose one universal steel-yield formula.
Ask:
Which yield matters to our process, and can the ERP calculate it from the production record we actually use?
Keep quality evidence attached to the material
Steel quality should not exist as an isolated QC department record.
Depending on the product and customer requirement, the quality record may involve:
The exact tests differ by grade, product, customer and standard.
The universal principle is:
The quality evidence must belong to the material it describes.
If material changes form, moves location, is reworked, downgraded or dispatched, its relevant quality history should remain understandable.
Make quality status affect what can happen next
A quality result is operational only if it influences the material.
Ask:
- Can material be placed on hold?
- Which physical stock is affected?
- Who can release it?
- Can only part of a heat or output be affected?
- What happens after rework?
- What happens after downgrade?
- Does the original identity/history remain?
- What happens after rejection?
- Can non-conforming stock be allocated accidentally?
Then ask the vendor:
Show us a quality result that changes what the business can do with the material.
That is a much stronger test than asking whether the ERP has a QC module.
Trace a customer complaint backwards
Do not test traceability only from production forward.
Start with material already supplied to a customer.
Ask:
Which exact physical material was dispatched?
Then trace backwards through:
- dispatch
- coil / bundle / plate / physical identity
- quality evidence
- rolling / processing history
- semi-finished identity
- heat or inherited supplier heat
- source material where relevant
The precise path depends on the business.
The important point is that a customer complaint should not require people to reconstruct genealogy from separate spreadsheets.
Find every downstream material identity from the same source
Traceability should also work forward.
Start with a heat or inherited supplier material identity.
Ask:
Which semi-finished and finished material came from this source?
Where is it now?
What has already been dispatched?
Which customers or orders were affected where relevant?
This matters when an upstream quality or supplier issue is discovered after material has already moved through several downstream stages.
Forward and backward traceability should be tested separately.
Manage WIP and yard inventory by the attributes that matter
Steel stock often needs more context than item code and quantity.
Depending on the business, inventory may need to remain identifiable by:
The ERP evaluation should answer:
Which exact physical material do we have, where is it, what does it weigh, what specification does it satisfy, and is it available to promise?
That is more useful than a total stock figure alone.
Preserve identity across multiple plants, yards and warehouses
A steel company may operate across several plants, yards, depots or warehouses.
The ERP should preserve material identity when stock moves.
Ask:
- Which heat or source identity moved?
- Which physical coil / bundle / plate moved?
- What weight moved?
- From which location?
- To which location?
- What quality status applied?
- Was it free or committed?
- Did the transfer create a new physical identity?
The transfer should not become a break in the genealogy.
Multi-location visibility is valuable only if the business can still identify the material.
Connect grade and size planning to demand
Steel planning should not stop at:
“How many tonnes should we produce?”
Depending on the process, planning may need to consider:
The ERP evaluation should ask:
Show us how a real customer specification becomes an executable production or processing requirement.
The exact scheduling model will differ between a melt shop, rerolling mill and downstream processor.
The buyer should evaluate the model that matches the real operation.
Use a rolling programme that reflects actual demand and capacity
Where rolling is part of the operation, the ERP should be able to support a rolling programme using the dimensions that matter to the plant.
Confirmed exactllyERP capability includes rolling programme planning by:
The buyer should nevertheless bring the real mill logic to the demonstration.
Ask:
- Which open orders drive the programme?
- Which grade and size combinations are required?
- Which semi-finished stock is available?
- What capacity or shift constraints matter?
- What happens when the plan changes?
- How is actual output compared with the programme?
Do not accept a generic production schedule as proof until the steel-specific planning logic has been demonstrated.
Keep semi-finished inventory visible
For businesses using semi-finished material, ERP should not make the material disappear between process stages.
Examples may include:
The ERP evaluation should ask:
What semi-finished material exists right now, what heat or source does it belong to, what does it weigh, where is it, and what can it become next?
WIP and semi-finished inventory should be operational stock, not merely accounting values.
Preserve genealogy through downstream processing
Steel may be:
A mother coil or source material can create multiple downstream physical identities.
The ERP should preserve the relationship.
Ask:
Which source material created this daughter material?
and:
Which downstream material came from this source?
The same principle applies whether the processing happens inside the plant or in a separate internal location.
Keep outside processing and job work inside the genealogy
External processing should not break material identity.
Where material is sent to an outside processor or job worker, ask:
- What material left?
- What heat or supplier heat did it carry?
- What physical identity did it have?
- What weight was sent?
- What process was expected?
- What came back?
- What new identity was created?
- What weight returned?
- What scrap / rejection / process difference occurred?
- What history remains?
Confirmed exactllyERP capability includes job work / subcontract processing while preserving original heat/material traceability.
But the buyer should still ask the vendor to demonstrate the exact outside-processing workflow used by the business.
Allocate the right stock to the right order
Available stock is not automatically eligible stock.
The buyer should test whether the ERP can match the customer requirement with material that actually satisfies it.
Depending on the business, eligibility may involve:
Then test:
Confirmed exactllyERP capability includes order-to-stock allocation and partial fulfilment.
The demonstration should show the buyer’s real allocation rules.
Connect actual dispatch material to the customer order
At dispatch, the ERP should know more than the total quantity leaving the gate.
The buyer should be able to establish:
Confirmed exactllyERP capability includes actual dispatch weight capture.
Where the customer’s commercial model requires it, exactllyERP also supports weight-based billing.
Do not assume every steel company bills in the same way.
The ERP should support the commercial model actually agreed with the customer.
Keep the quality certificate connected to the shipment
Where the customer requires a Material Test Certificate or other quality certificate, the certificate should relate to the material actually dispatched.
Confirmed exactllyERP capability includes:
The buyer should ask:
Which test/quality evidence appears on this certificate?
Which heat/material does it belong to?
Which shipment received it?
The certificate should not be prepared as a disconnected document whose relationship to the shipped material depends on manual checking.
Integrate the weighbridge where the operating process requires it
Many steel businesses depend on physical weight capture.
Confirmed exactllyERP capability includes weighbridge integration.
But the evaluation should begin with the business process rather than the interface itself.
Ask:
- At which inbound or outbound stages is weight captured?
- Which transaction does the weight update?
- Which material identity is being weighed?
- Is gross/tare/net treatment relevant to the process?
- What happens if the weighbridge or integration is unavailable?
- Who can correct an erroneous weight?
- How is manual intervention controlled?
Do not treat “weighbridge integration” as sufficient evidence until the end-to-end operating scenario has been shown.
Connect material movement to costing
Steel costing should reflect the production and material model the business actually uses.
Confirmed exactllyERP capability includes:
The buyer should ask how costs follow the actual process.
Depending on the operation, that may include:
Do not assume one universal steel-costing formula.
The important question is:
Can management explain why this production output or heat cost what it did using the operational record that created it?
Make recovered scrap, rejection, rework and downgrade visible
A steel ERP should not force every non-standard outcome into one generic scrap transaction.
Confirmed exactllyERP capability includes handling for:
The buyer should test what each means operationally.
Ask:
Does the material remain identifiable after its status changes?
Can it re-enter production where allowed without losing genealogy?
Can downgrade preserve the original heat/material history?
Can rejection remain visible rather than being removed through an unexplained adjustment?
This is important for both material reconciliation and costing.
Make the vendor demonstrate the difficult steel scenarios
Do not allow the steel ERP demonstration to become a tour of inventory, production and QC screens.
Give every shortlisted vendor the same difficult scenarios.
The point is not that every ERP should navigate identically.
The point is that every vendor should prove the same business outcome.
Record what is standard, configured, extended or custom
After each important steel scenario, classify how the proposed result is delivered.
The proposed product supports the requirement as part of normal capability.
The result depends on settings, masters, workflows or configurable behaviour.
Another application, specialist system or extension is part of the proposed solution.
Development is required specifically for the requirement.
The claim remains proposed until evidence is provided.
None of these labels is automatically good or bad.
The buyer needs to understand what will have to exist in production to reproduce what was demonstrated.
Iron & Steel ERP red flags
The demo assumes every steel company starts with scrap
The vendor may not understand where this buyer’s actual material genealogy begins.
Heat number exists only in the melt-shop record
Downstream rolling, stores, QC or dispatch may no longer preserve the genealogy.
Purchased billet, coil or plate loses the supplier heat
A reroller or processor cannot trace material back to the source it actually received.
Finished stock is only item + quantity
The business cannot distinguish physical material by heat, grade, size, identity, weight and quality status where required.
All input/output difference is called loss
Recovered material, WIP, rework, downgrade or other outcomes may be hidden.
Weight reconciliation depends on spreadsheets
The material balance is outside the production record.
Recovered scrap is adjusted manually without genealogy
Material can re-enter the process without a trustworthy source history.
Downgrade creates an unrelated new item
The original heat or material history disappears.
QC result is not tied to the material dispatched
The certificate and the shipment can describe different realities.
A failed quality result does not control material use
QC is reporting, not an operational gate.
Customer specification is re-entered during planning
Commercial and production requirements can diverge.
Stock is allocated without checking specification eligibility
Available material may not actually satisfy the order.
Partial dispatch breaks the order/material relationship
The remaining balance becomes unclear.
Certificate preparation is disconnected from shipment identity
Quality documentation depends on manual reconciliation.
Outside processing breaks heat or material genealogy
The business loses the relationship once material leaves the plant.
Weighbridge integration is demonstrated without the business transaction
A technical connection exists, but the operating control remains unclear.
“Steel ERP” is demonstrated through a feature checklist
The vendor has not proved the difficult material flow.
Customer proof is only a logo
The reference does not reduce uncertainty about the buyer’s actual steel route.
A practical Iron & Steel ERP evaluation record
For each critical steel workflow, record the evidence.
| Evaluation area | What the buyer should establish |
|---|---|
| Business model | Where the material genealogy actually begins |
| Customer specification | How grade, size, dimension and other requirements remain connected |
| Source material | Which incoming material identity must be preserved |
| Heat identity | How internally created or inherited heat identity is handled |
| Semi-finished material | How billet, bloom, ingot, slab or other WIP remains visible |
| Physical stock identity | How coil, bundle, plate, piece or other identities are distinguished |
| Forward genealogy | Which downstream material came from a heat/source |
| Backward genealogy | Which source/heat created dispatched material |
| Weight reconciliation | How input, output, WIP, recovered material and loss close |
| Yield | How relevant production yield is calculated from actual records |
| Recovered scrap | How recoverable material is identified and reused |
| Rework | How genealogy survives reprocessing |
| Downgrade | How changed specification/status preserves source history |
| Rejection | How non-conforming material remains controlled and visible |
| Quality | How heat/material test history remains connected |
| Certificate / MTC | How quality evidence relates to the material dispatched |
| WIP / yard / warehouse | How grade, heat, physical identity, weight and status remain visible |
| Planning | How customer demand becomes grade/size/shift/production requirement |
| Rolling programme | How order demand and material availability influence the programme |
| Allocation | How eligible stock is reserved against the correct order |
| Partial fulfilment | How dispatched and remaining order/material balances remain clear |
| Dispatch | How actual physical material and actual weight are recorded |
| Weighbridge | How physical weight capture connects to the correct transaction |
| Job work | How external processing preserves source identity and quantities |
| Costing | How material and conversion costs connect to the production record |
| Multi-location | How plant/yard/warehouse transfers preserve genealogy |
| Integration | Which surrounding systems remain and who owns each boundary |
| Delivery method | Standard / configuration / extension / custom / not demonstrated |
| Follow-up | What evidence remains unresolved |
Do not turn this into a percentage score.
One unresolved critical genealogy or quality-control requirement can matter more than many minor feature matches.
What customer proof should a steel ERP vendor provide?
A useful customer reference is not simply another company with “Steel” in its name.
Ask for proof closest to the uncertainty you are trying to remove.
If your concern is melt-shop genealogy, ask:
Which customer actually creates heats and follows them through downstream production?
If your concern is rerolling, ask:
Which customer receives billet or other semi-finished material with inherited heat identity and preserves it through finished production?
If your concern is coil or service-centre processing, ask:
Which customer can trace mother material to downstream daughter material after slitting, cutting or other processing?
If your concern is weight reconciliation, ask:
Which customer accounts for input, saleable output, recoverable material, rework and process loss from the production record?
If your concern is quality, ask:
Which customer keeps heat/material test history connected to the physical stock and certificate dispatched?
If your concern is outside processing, ask:
Which customer preserves genealogy while material leaves and returns from a job worker or subcontractor?
Customer evidence should validate the difficult workflow.
Not decorate the proposal.
This Buyer Guide relies on one named Exactlly Iron & Steel customer story, set out in the next section.
The buyer should still hold Exactlly to the same evidence standard and require the actual workflow to be demonstrated.
Relevant operating evidence: Nezone Group
Nezone Group provides named proof that Exactlly operates inside a long-running, distributed steel manufacturing and distribution environment.
Nezone Group has used exactllyERP for more than 10 years across a multi-location, multi-plant and multi-warehouse steel manufacturing and distribution operation.
Its approved Exactlly evidence includes:
- multi-plant manufacturing;
- multi-location and multi-warehouse operations;
- production planning;
- production transactions;
- batch identity;
- grade-, size-, thickness- and specification-wise inventory;
- inter-plant and inter-warehouse transfers;
- weighbridge and weight-based transactions;
- production costing, held as standard against actual;
- yield and scrap;
- distributor and dealer orders;
- customer credit-limit controls;
- dispatch;
- collections;
- a relationship extending more than 10 years.
The useful evidence is not simply that Nezone is a steel company.
It is that production, the commercial and manufacturing identity of the stock, the movement between plants and warehouses, weighment, dispatch and the dealer channel remain connected in one operating record across a geographically distributed business.
This supports the proof role:
MANUFACTURE THE MATERIAL. KEEP ITS IDENTITY. MOVE IT. SELL IT.
Nezone represents a downstream steel manufacturing and distribution model: tubes, pipes, sections and engineering products.
Buyers should still evaluate the specific traceability, production and quality workflows that apply to their own steel process.
The customer story proves the long-running distributed steel operating environment.
The product demonstration must prove the buyer’s specific steel workflows.
How exactllyERP fits into this evaluation
exactllyERP should be evaluated against the same difficult steel scenarios.
Do not ask Exactlly only:
“Do you have a Steel ERP?”
Bring the actual operating model.
Include:
- where material enters your business;
- raw material or purchased semi-finished material;
- internally created or supplier heat identity;
- grades;
- sizes / sections / dimensions;
- melt / casting stages where applicable;
- rolling or processing stages;
- semi-finished inventory;
- coil / bundle / plate / piece identity;
- production weight records;
- recovered scrap;
- rework / downgrade / rejection;
- QC and certificate requirements;
- plants / yards / warehouses;
- order-allocation rules;
- dispatch and billing model;
- outside processing;
- weighbridge requirements;
- systems that must remain connected.
Confirmed exactllyERP capability for Iron & Steel includes:
- heat number creation and tracking through production and dispatch;
- preservation of supplier/inherited heat identity for purchased billet, coil or other material;
- scrap/raw-material grade-wise inventory and issue to heat;
- input/output weight reconciliation by production stage;
- melting and rolling yield calculation;
- recovered scrap, rejection, rework and downgrade handling;
- rolling programme by grade, size, shift and order demand;
- semi-finished inventory such as billet, bloom or ingot where applicable;
- finished inventory by grade, size, heat and physical identity such as bundle or coil;
- weighbridge integration;
- heat-wise QC/test history;
- Material Test Certificate / quality certificate linked to heat and dispatch;
- order-to-stock allocation and partial fulfilment;
- actual dispatch weight capture;
- weight-based billing where the customer’s commercial process requires it;
- job work / subcontract processing while preserving original heat/material traceability;
- per-heat or production-linked costing;
- cost treatment for energy, fuel, consumables and overheads where applicable;
- multi-location plant, yard and warehouse inventory;
- forward and backward heat/material traceability from source to dispatched customer and vice versa.
Those capabilities should still be demonstrated against the buyer’s own route.
The relevant questions are:
Where does our material identity begin?
How does it survive every transformation?
How does the weight reconcile?
How does QC control the physical material?
How do we prove that the dispatched material satisfies the customer order?
The buyer should record what is standard, configured, extended, integrated or custom.
Customer evidence should supplement that evaluation when relevant proof is available.
It should not replace the demonstration.
Iron & Steel ERP Evaluation Checklist
Operating model
Customer specification
Source material
Heat / genealogy
Weight reconciliation
Yield
Quality
Certificate / MTC
Semi-finished / WIP
Finished inventory
Planning / rolling
Allocation / dispatch
Weighbridge
Job work / subcontract processing
Costing
Multi-location
Integration / coexistence
Vendor evidence
The buyer is evaluating the ERP as an operating system for the real steel-material lifecycle rather than as a list of manufacturing features.