In steel trading, weight is money. A lorry of structural channels, TMT bars or HR sheet is billed by the kilogram, so a small error in the weighment turns straight into steel that leaves the yard without being billed.
One of the most common ways this happens is tare manipulation: the empty weight of the lorry is recorded higher than it really is. This post explains how it works, what software can and cannot do about it, and the controls SteelERP gives you to make short loading visible.
How Tare Fraud Works
Every dispatch involves two weighments:
- Gross Weight: The weight of the lorry loaded with the steel.
- Tare Weight: The weight of the empty lorry, taken before loading.
The net weight of the steel delivered is calculated as:
Net Weight = Gross Weight - Tare Weight
If the recorded tare weight is higher than the lorry's true empty weight, the net comes out lower. The yard bills for less steel than was actually loaded, and the difference leaves on the lorry unbilled. The same trick works in reverse on the purchase side: an understated net on an incoming mill lorry means your stock is short of what the paperwork says was received.
What the Leak Adds Up To
An illustration, not a measured figure: a 0.3% error on a 30-tonne load is 90 kg. At an assumed ₹50 per kg (substitute your own rate), that is ₹4,500 on one lorry. If it happens on just one lorry a day, it comes to about ₹13.5 lakh over 300 working days.
Common Ways the Figures Get Manipulated
1. A Different Number Between the Slip and the Books
Whether weights go into a register, a spreadsheet or an ERP, someone types in the figure from the weighbridge slip. SteelERP works the same way: supervisors enter the weighments themselves. A form field alone does not stop a wrong number. What does is making every entry traceable to a person, a time and a lorry, and making the gap between what was ordered and what was billed easy to see. The controls below do that.
2. An Inflated Tare Run
The lorry is weighed empty while carrying extra weight (spare tyres, tools, a full water or fuel tank, loose timber) that is taken off before loading. The scale reads correctly, but the tare it records is not the lorry's real empty weight.
3. Tampering With the Weighbridge Itself
Interference with the load cells or the indicator can shift readings up or down. No ERP can detect this from the data alone. It needs physical checks: calibration on schedule, an occasional test with a known load, and a camera on the platform.
How SteelERP Makes Short Loading Visible
SteelERP does not connect to your weighbridge. It records the weighments your team enters, calculates the net weight itself, and ties every figure to a lorry, a challan and a user:
- Tare, then gross, in sequence: The empty lorry weight is recorded when loading starts. If a lorry is loaded in batches, each weighment must be heavier than the one before it, and the final gross closes the load. SteelERP works out the net loaded weight (final minus empty) and spreads it across the items on that lorry, so nobody writes a net figure by hand.
- Ordered weight against actual weight, per item: Every line carries the weight that was ordered and the actual loaded weight. The delivery challan and the bill use the actual figure, so a lorry that goes out light or heavy shows up line by line against the order.
- Challan-linked records: Each delivery sub-order is one lorry, with its own vehicle number, loading, weighments, challan and delivery status. When an order is split across lorries, each lorry's weight stays tied to its own challan instead of disappearing into a daily total.
- Audit log: When loading is completed, the change to each item's actual quantity, weight and pieces is written to the audit log with the user and the time. Later corrections to the empty or final truck weight are logged the same way, with who made them and the value entered. Admins can review the log on each order, purchase order and lorry.
- Challan print-variance report: Lists challans generated on one day but not printed that same day, or never printed at all. Paperwork that is raised and then held back deserves a question, and this report puts it on one screen. A separate list shows challans still waiting to be printed and how long each has been pending.
- Role and yard scoping: Truck weights can be changed only by specific roles, and only while the lorry is in Loading or Loaded status. Delivery supervisors work on the lorries assigned to them, and each user can be limited to the warehouses they work in. An optional IP allow-list can restrict non-admin users to your office or yard network (Admins are not restricted by it).
- The inbound side: A purchase order takes a separate purchase advice for each mill lorry, and goods are received into the yard that actually took them. An optional Security truck-in step records the lorry at the gate before unloading.
- Weekly anomaly flags: Advisory anomaly detection flags unusual weekly swings in each product's movement and in the total kilograms dispatched and received, with the numbers behind each flag.
A Practical Routine for the Yard
- Photograph the weighbridge slip for each lorry and attach it to the order, so the typed figure can be checked against the slip later.
- Where you can, have different people record the weights and raise the challan.
- Spot-check ordered against actual weight on dispatched lorries every week. Look for the same vehicle, supervisor or customer coming up light again and again.
- Check the print-variance report daily for challans that were raised but not handed over.
- Keep the weighbridge calibrated, and test it with a known load now and then.
Securing Your Stockyard
Software will not stop a determined operator from misreading a scale. What it can do is take over the arithmetic, tie every weighment to a lorry, a challan and a name, and put the gaps where an owner will see them. Together with physical checks on the weighbridge, that makes tare manipulation much harder to hide.