Quarry ERP and Weighbridge Integration: How to Stop Material Leakage at the Gate

A stone crusher unit runs on tonnage. Royalty, diesel consumption, blasting cost, subcontractor payout and the sales invoice are all derived from a weight reading taken at a bridge near the gate, usually a long way from the accounts office. When that reading lands on a paper slip and gets keyed into a spreadsheet at the end of the shift, the arithmetic starts to rot. Slips go missing. Tare weights get reused from memory. The gap between what left the site and what was billed becomes impossible to reconstruct a month later.

Why does quarry weighbridge data go missing?

Ask any plant to produce three numbers for the same month: crusher production, closing stockyard survey, and total invoiced dispatch. In a manual setup those three rarely agree within five percent. The variance is not automatically theft. Moisture in the boulder feed, screen fines that never make a saleable grade, double weighing of the same vehicle, and internal movements between the pit and the stockyard all contribute.

The problem is that a spreadsheet cannot separate those causes. Every unexplained tonne looks the same. Once a plant has a system that timestamps each weighment against a specific vehicle, a specific gate pass and a specific order line, the variance splits into categories you can act on. That reclassification, not the software licence, is what actually changes the numbers.

How does weighbridge integration with an ERP actually work?

Every digital weight indicator emits a serial data stream, typically over RS-232 or RS-485, converted to Ethernet or USB where the cable run is long. The stream repeats the current reading many times a second along with a stability flag.

A capture service running on the weighbridge terminal listens to that port, discards unstable readings, and only accepts a value once the indicator has settled for a configured number of consecutive frames. It then posts that value to the ERP against an open weighment record. The operator never types a weight. They select the vehicle, the material and the order; the number arrives on its own.

The record itself follows a two-pass pattern:

1. The loaded vehicle drives on. The system reads gross weight and holds the record open.
2. The vehicle is identified by RFID tag, ANPR plate read or driver card, and matched to the master.
3. The system pulls the stored tare for that vehicle, or requires an empty pass if the tare has expired.
4. Net weight is computed by the system, never entered.
5. The dispatch ticket prints with a serial number, vehicle, material grade, net tonnage and order reference.
6. A gate pass is generated with a validity window measured in minutes.
7. The ticket posts an inventory issue against the correct stockyard bin and a pending invoice line.
8. Royalty and district permit quantity are consumed from the available balance on the same transaction.

Once that loop is closed, the sales invoice, the stock ledger and the royalty register are all children of one event. They cannot disagree unless somebody reverses the parent, which leaves an audit trail.

Which controls actually reduce material theft?

Software does not stop a determined operator. It removes the easy routes. In practice these six controls do most of the work:

• System-held tare. Tare weights live in the vehicle master with an expiry date. An operator cannot type a lower tare to inflate net weight on a purchase or deflate it on a sale.
• Tolerance bands per vehicle. Each vehicle has a rated capacity. A load outside the configured band raises a supervisor approval rather than printing silently.
• ANPR plate matching. The camera reads the plate at the moment of weighing and compares it to the vehicle on the record. A mismatch blocks the ticket. This kills the classic swap where one truck is weighed and the slip is issued against another.
• Gate pass validity windows. A pass that is valid for fifteen minutes cannot be reused on a second trip later in the shift.
• Duplicate and reprint locking. Reprints are watermarked, counted and attributed to the user who requested them.
• Segregation of duty. The person who creates the vehicle master is not the person who weighs, and neither of them can edit a posted ticket.

SyvaSoft builds these controls into Quarry360, its ERP for quarry and crusher operations, precisely because the failure mode at most plants is procedural rather than technical. The hardware usually works. The gaps sit around it.

What does beltscale data add that a weighbridge cannot?

A weighbridge tells you what left the property. It says nothing about what the plant made. A beltscale on the crusher discharge conveyor reports tonnes per hour continuously, which gives you three things a gate reading never will.

First, a genuine production figure per shift, per crusher and per product grade. Second, a running measure of plant utilisation, since idle belt time is visible as flat output rather than as an absence of data. Third, a defensible loss percentage. If the beltscale says 4,100 tonnes were produced, the stockyard survey moved by 300 tonnes and dispatch was 3,600 tonnes, you are looking at roughly 200 tonnes of unexplained variance rather than a vague sense that something is wrong.

Diesel is worth instrumenting on the same principle. Litres issued per vehicle per kilometre, and litres per tonne crushed, both become trend lines rather than monthly totals. Fuel and tyre cost is often the second largest controllable line at a quarry after power.

How do you cost a tonne of aggregate correctly?

Most quarries know their selling price per tonne to the rupee and their cost per tonne only approximately. A workable costing model separates five buckets:

1. Drilling and blasting — explosives, licences, contractor charges, allocated per tonne of rock broken.
2. Excavation and hauling — excavator hours, tipper trips, diesel and operator wages from pit face to crusher hopper.
3. Crushing and screening — power or diesel for the plant, wear parts such as jaw plates, cone liners and screen mesh, plus scheduled maintenance.
4. Royalty, DMF and statutory — per-tonne rates set by the state mineral rules, plus district mineral foundation contributions.
5. Overheads — establishment, compliance, weighbridge operations, administration.

The difficult part is joint costing. One boulder feed produces several saleable grades at once: 20mm, 12mm, 6mm, M-sand and quarry dust. Allocating plant cost equally per tonne makes fines look unprofitable and coarse aggregate look better than it is. Most plants get a more useful picture by allocating on relative sales value, so each grade absorbs plant cost in proportion to what the market pays for it. Whatever basis you choose, keep it stable across periods. Changing the allocation basis mid-year makes trend analysis meaningless.

Where does subcontract and job work fit?

The second largest reconciliation gap after dispatch is job work. A plant crushes boulder supplied by a third party, or sends its own boulder to another crusher, and the material moves without a sale. If those movements are not tracked as subcontract challans with an expected return quantity and a conversion yield, they become a permanent hole in the stock ledger.

Track three things per job work order: quantity sent, expected recovery by grade, and actual recovery. The difference between expected and actual yield is a negotiation point with the contractor and a genuine cost input for your own planning.

What should you check before buying quarry ERP software?

1. Ask for a live demo against your own weight indicator model, not a simulator.
2. Confirm the system holds tare in the master and blocks manual override without approval.
3. Check whether royalty and permit balances are consumed on the dispatch transaction itself.
4. Confirm the GST tax invoice and e-way bill are generated from the same ticket, with no re-keying.
5. Ask how Tally or your existing financial ledger will be synchronised, and how often.
6. Ask what happens when the network drops. A gate cannot stop working because a link is down, so offline weighment with later synchronisation is mandatory.
7. Insist on a two-week parallel run against manual slips before cutover.

None of this is exotic. It is ordinary discipline applied to a measurement that happens hundreds of times a day. Plants that get it right usually find that the first month of clean data is more valuable than any dashboard they were sold, because for the first time the argument about where the tonnage went can be settled with a record instead of an opinion.