There is a quiet accounting problem inside most steel businesses, and it has nothing to do with the finance team. It is that the ERP costs and prices material one way — by nominal, theoretical weight — while the market buys and sells it another way, by actual weighbridge weight. The gap between those two numbers is small on any single coil and enormous across a year of tonnage. That gap is exactly where a generic ERP quietly leaks margin, and where a real steel ERP software earns its place.
This post is about weight-based costing in steel: why theoretical weight is a trap, why the weighbridge has to be the source of truth, and how an AI-native ERP reconciles the two so your margin is calculated on reality. If you have ever seen a "profitable" order turn out flat once the actual weights landed, this is the article for you.
Theoretical weight vs actual weight: the core problem
Steel has a theoretical weight — the number you get from dimensions and density: width × thickness × length × a constant. It is a fine planning figure. It is a terrible costing figure. Rolling tolerances, coil-to-coil variation, moisture, scale and trimming all mean the steel that crosses your weighbridge rarely weighs exactly what the formula says. Sometimes it is heavier, sometimes lighter, and the direction is not random across your suppliers.
A generic ERP typically values stock and calculates cost on the theoretical figure because that is the number it was handed at purchase-order time. Do that consistently and you build an error into every cost, every valuation and every margin report. On low-margin, high-tonnage steel, a one-to-two percent weight discrepancy is not a rounding issue — it can be the whole profit on the deal.
A worked example
Say you buy a lot billed at a theoretical 25.0 tonnes, but the weighbridge reads 24.6 tonnes on arrival. You have paid for 25.0 and received 24.6. If your ERP keeps costing on 25.0, every downstream product carries a cost that is too low, your inventory is overstated by 0.4 tonnes, and the loss surfaces — unexplained — only at stock-take. Now run that pattern across hundreds of inward lots a month. A steel ERP catches it at the gate by reconciling billed weight against actual weight the moment the truck is weighed.
Why the weighbridge has to be the source of truth
In a weight-native business, the weighbridge is not a checkpoint — it is the system of record for quantity. Every inward and outward movement should be anchored to a captured weighment, and that number should flow straight into costing, inventory and invoicing without re-keying. Manual entry between the bridge and the ERP is where errors and, occasionally, leakage creep in.
- Automatic capture from the weighbridge into the inward/outward record, tare and gross both logged.
- Reconciliation of billed/theoretical weight against actual weight, with variance flagged when it breaches a tolerance.
- Weight-anchored valuation so stock is always carried at actual received weight, not nominal.
- An audit trail linking each weighment to its heat, coil, vehicle and document.
Pixel ERP integrates directly with weighbridges so the measured weight becomes the costing and invoicing weight automatically. That single design choice removes the most common source of margin error in steel — and it is one reason weighbridge integration sits at the centre of our steel ERP approach.
There is a second, quieter benefit: disputes shrink. When the weight on your dispatch document is the same weight you captured at the bridge, and it agrees with what the customer weighs at their end, reconciliation stops being a monthly argument. Short-weight claims, credit notes and endless email threads over "your challan says 24.8 but we received 24.5" largely disappear, because every figure in the chain descends from one measured weighment rather than from a formula nobody trusts. For a business running hundreds of dispatches a month, that reduction in friction is worth as much as the margin the reconciliation protects.
What weight-based costing actually has to include
Costing a tonne of steel is more than "purchase price per tonne." A real steel ERP builds landed and processed cost by weight, layer by layer:
- Base material cost at actual received weight.
- Freight and handling apportioned by weight across the lot.
- Conversion and processing charges — slitting, cutting, pickling — costed against the input weight consumed.
- Yield loss and scrap, so the cost of good output absorbs the weight that became scrap, net of scrap recovery value.
- Duties, cess and other levies that ride on weight or value.
Only when all of those are weight-accurate does gross margin per order, per grade or per customer mean anything. Because processing yield feeds directly into cost, weight-based costing and yield tracking are two sides of the same coin — our post on ERP for steel processing covers the scrap side in detail.
Weight-accurate pricing and invoicing
The mirror image of costing is pricing. Steel is sold by weight, so the invoice has to reflect the actual dispatched weighbridge weight, not the challan count or the theoretical figure. A steel ERP prices and invoices on the measured outbound weight, applies the correct grade-based rate, and keeps the GST e-invoice consistent with the weighment. That consistency — gate weight equals invoice weight equals the number your customer weighs on their side — prevents disputes and keeps reconciliation clean.
Where generic ERP gets it wrong — and Pixel ERP gets it rightQuestion Generic ERP Pixel ERP What is the costing weight? Theoretical / PO weight Reconciled weighbridge weight Where does weight come from? Manual entry Direct weighbridge capture Is variance flagged? No Yes, against tolerance, at the gate Are processing & scrap in cost? Rarely Yes, by input weight and yield Does the invoice match the bridge? Often not Always — same weighment Changing a costing rule Developer request No-code, done by your team
| Question | Generic ERP | Pixel ERP |
|---|---|---|
| What is the costing weight? | Theoretical / PO weight | Reconciled weighbridge weight |
| Where does weight come from? | Manual entry | Direct weighbridge capture |
| Is variance flagged? | No | Yes, against tolerance, at the gate |
| Are processing & scrap in cost? | Rarely | Yes, by input weight and yield |
| Does the invoice match the bridge? | Often not | Always — same weighment |
| Changing a costing rule | Developer request | No-code, done by your team |
None of this requires a bespoke system. Pixel ERP is a ready, AI-native ERP product that adapts to steel weight logic through configuration — so your costing rules, tolerances and rate structures are set up, not hand-coded, and your own team can change them later. Learn how the platform itself is built on our Pixel ERP™ page.
Frequently asked questionsWhy not just cost everything on theoretical weight for simplicity?
Because simplicity here costs money. Theoretical weight ignores rolling tolerance, scale, moisture and trimming, so it is systematically wrong — and on high-tonnage, thin-margin steel a one-to-two percent error can erase the profit on a deal. Costing on reconciled actual weight is the only way margin reports reflect what really happened.
How does weighbridge integration work in Pixel ERP?
The weighbridge feeds gross and tare weights directly into the inward or outward record, linked to the vehicle, heat and coil. That measured weight becomes the costing and invoicing weight automatically, with variance against billed/theoretical weight flagged when it exceeds your tolerance.
Can it handle both weight-based and piece-based items?
Yes. Steel moves by weight, but consumables, spares and packaging may be counted. Pixel ERP handles weight-based and piece-based items side by side, so the whole operation runs on one system rather than steel in spreadsheets and everything else in the ERP.
Does weight-based costing complicate GST and e-invoicing?
No — it makes it cleaner. Because the dispatched weighbridge weight drives both the invoice and the GST e-invoice, the tax document matches the physical reality your customer receives, which reduces disputes and reconciliation effort.
Do we own the data and the weight history?
Yes. Pixel ERP runs on your own cloud account with your data under your control — no shared multi-tenant database and no per-user licence lock-in. For a business where weighments and traceability underpin every invoice, that ownership matters.
Keep reading
- Pillar guide: Steel ERP software for plants and processing
- Steel ERP: managing heats, coils, grades and yield
- ERP for steel processing: slitting, cutting and scrap tracking
- Industry: steel and steel processing solutions
- Book a demo and cost a real order on actual weights
Why not just cost everything on theoretical weight for simplicity?
Because simplicity here costs money. Theoretical weight ignores rolling tolerance, scale, moisture and trimming, so it is systematically wrong — and on high-tonnage, thin-margin steel a one-to-two percent error can erase the profit on a deal. Costing on reconciled actual weight is the only way margin reports reflect what really happened.
How does weighbridge integration work in Pixel ERP?
The weighbridge feeds gross and tare weights directly into the inward or outward record, linked to the vehicle, heat and coil. That measured weight becomes the costing and invoicing weight automatically, with variance against billed/theoretical weight flagged when it exceeds your tolerance.
Can it handle both weight-based and piece-based items?
Yes. Steel moves by weight, but consumables, spares and packaging may be counted. Pixel ERP handles weight-based and piece-based items side by side, so the whole operation runs on one system rather than steel in spreadsheets and everything else in the ERP.
Does weight-based costing complicate GST and e-invoicing?
No — it makes it cleaner. Because the dispatched weighbridge weight drives both the invoice and the GST e-invoice, the tax document matches the physical reality your customer receives, which reduces disputes and reconciliation effort.
Do we own the data and the weight history?
Yes. Pixel ERP runs on your own cloud account with your data under your control — no shared multi-tenant database and no per-user licence lock-in. For a business where weighments and traceability underpin every invoice, that ownership matters.
Keep reading
- Pillar guide: Steel ERP software for plants and processing
- Steel ERP: managing heats, coils, grades and yield
- ERP for steel processing: slitting, cutting and scrap tracking
- Industry: steel and steel processing solutions
- Book a demo and cost a real order on actual weights