Sector · Steel trading
The arithmetic of buying by the tonne and selling by the metre.
An ERP for firms that buy and sell profiles, sheet, rebar, pipe, angle, and NPU/NPI/IPE/HEA products. Built not for producers but for traders and steel service centres: buying by the tonne, selling by the metre, piece, or kilo, with cutting and haulage in between.
In steel trading, margin hides in the accuracy of unit conversion. The same item is bought by the tonne, quoted by the metre, invoiced by the kilo, and shipped by the piece. Every error between those four units is written straight into losses.
That is why multi-unit conversion sits at the core of ScalaSteel. A product card requires either weight per metre (kg/m) or weight per length (kg/piece); without one of them the card will not save — a card that cannot be converted is a card that cannot be sold.
Standard dimension catalogues arrive with their weights for box and rectangular profiles, IPE, HEA, HEB, NPU/UPN, NPI/INP, angle, flat bar, pipe, rebar, and sheet. Closed profiles subtract the EN 10219 corner radius.
kg ↔ metre ↔ piece ↔ tonne conversion runs through a single service. Quotes, orders, shipments, and invoices all draw on the same source, so no document drifts between units.
At goods receipt, theoretical weight sits beside weighbridge weight; the deviation is recorded and feeds supplier performance. Every record keeps the “from the scale / entered by hand” distinction.
Work-order lengths are packed with an FFD algorithm, the remaining offcut is calculated and added to the real cost. Leftover pieces return to stock.
Account balance, open order value, and cheques in portfolio combine into a single risk score. Orders that exceed the limit go to approval.
After import charges, haulage, and waste are allocated, profit per tonne is reported by product, customer, and batch.
Eleven rules run continuously: critical stock, late shipments, cheques nearing maturity, limit breaches. Repeat alerts are de-duplicated.
Technology stack
A product card cannot be saved without conversion data (kg/m or kg/piece). The constraint is deliberate: letting an incomplete card into the system produces a wrong price in every document that follows.
Weighbridge integration is abstracted behind a single endpoint (`GET /api/receipts/scale`). Today it simulates a reading and returns `source: "simulation"`; when a serial or TCP device is connected only that endpoint changes and the record schema stays identical.
e-Invoice, e-Archive, and e-Waybill endpoints manage document state and UUID, so swapping the integrator leaves the business logic untouched.
What people ask us, answered briefly and plainly.
ScalaSteel is a sector-specific ERP for steel trading. An ERP for firms that buy and sell profiles, sheet, rebar, pipe, angle, and NPU/NPI/IPE/HEA products. Built not for producers but for traders and steel service centres: buying by the tonne, selling by the metre, piece, or kilo, with cutting and haulage in between.
Stock bought by the tonne not converting correctly into per-metre or per-piece prices; Deviation between theoretical weight and weighbridge weight going unrecorded; Offcut waste from cutting never reaching the cost calculation; Account balance, open orders, and cheque exposure not visible together.
Multi-unit conversion: kg ↔ metre ↔ piece ↔ tonne conversion runs through a single service. Weighbridge and weight deviation: At goods receipt, theoretical weight sits beside weighbridge weight; the deviation is recorded and feeds supplier performance. Cutting optimization: Work-order lengths are packed with an FFD algorithm, the remaining offcut is calculated and added to the real cost. Risk limit: Account balance, open order value, and cheques in portfolio combine into a single risk score. Profitability per tonne: After import charges, haulage, and waste are allocated, profit per tonne is reported by product, customer, and batch. Alert engine: Eleven rules run continuously: critical stock, late shipments, cheques nearing maturity, limit breaches.
Node 20, Express 5, Sequelize, MySQL 8, React 19, Vite 6, Tailwind v4.
Pricing depends on how many people will use it, which sections are opened, and whether it must connect to other programs. After the conversation we send a written quote with scope, timeline, and a firm price within 48 hours at the latest.
Yes. For one year after delivery, updates, technical support, and server maintenance continue at no extra charge.
Let's begin
Which units do you work in, which document chain do you follow? We map the scope and prepare a clear quote within 48 hours.
