A weighbridge often sits next to a platform that cannot read it. That is one of the most common sources of wasted time in the sector. Somebody types the tonnage from the weighbridge terminal into the job system. That system then exports it to the accounts package, and again to the EA returns spreadsheet. Each transfer is a chance for error. From October 2026 that is also a legal risk. The DEFRA Digital Waste Tracking Service wants correct tonnage for each movement, sent inside two days.
Weighbridges output data in a few standard ways. Most current indicators use TCP/IP. They open a point on the local network. Software can ask that point for the gross weight, the tare weight and the net tonnage after each weighing. Older equipment often uses RS-232 serial output. Some weighbridge management software (products like Weightron or Avery Weigh-Tronix systems) also expose their own API or database that third-party systems can connect to.
In principle a platform can read any of them as it happens. The vehicle arrives. The operator starts the job. The vehicle weighs in, and the software takes the gross weight. The vehicle tips and weighs out. The net tonnage goes onto the job record by itself. No manual entry. The tonnage feeds into the invoice, the EA return, and from October 2026, the DWT portal submission.
In practice, most off-the-shelf platforms do not do this by default. Weighbridge integration is commonly listed as an optional paid module or a custom integration project, priced separately from the base platform. The reason is that every weighbridge is a little different. Most vendors will not build and keep a general connection to hardware they do not control.
By hand the work runs like this. The terminal prints a ticket. The operator reads the tonnage and types it into the job system. The job is closed and the invoice made. At the end of the month somebody fills the EA return spreadsheet from that system. This works at low volume. It breaks down when:
Connect with us about waste management software · · Replies within 24 hours
Many sites take mixed loads. One delivery holds several waste streams, and each stream has its own European Waste Catalogue code. The physical weighbridge measures total vehicle weight. The software must split that tonnage correctly. It records the weight in. The operator then gives a share of it to each EWC code as the vehicle tips. The weight out confirms the total.
Most waste management platforms assume single-stream loads. Operators with mixed loads often end up using estimated split percentages, which introduce inaccuracy into both the management system records and the EA returns. Under DWT, per-EWC-code tonnage is a required field. Estimated splits are not an acceptable record for a regulated system.
A properly integrated weighbridge system does the following automatically:
| Step | Manual workflow | Integrated workflow |
|---|---|---|
| Vehicle arrives | Paper/manual check-in | Number plate recognition or job scan: job opens automatically |
| Gross weight | Weighbridge ticket printed, re-entered manually | Weight written to job record in real time via TCP/IP |
| Material assignment | Operator types EWC codes separately | EWC codes pre-loaded from booked job; operator confirms or adjusts |
| Tare weight | Re-entered manually or looked up from card file | Read from weighbridge on exit, or from registered vehicle tare record |
| Invoice generation | Manually created from entered tonnage | Auto-generated from confirmed net tonnage, applying contract rate |
| EA/DWT submission | Manual data export or spreadsheet entry | Auto-populated, submitted to DEFRA portal within the 2-day window |
| Record retention | Paper tickets + spreadsheet exports | All records stored in system, searchable, exportable for 4+ years |
OpenWeigh is a standalone weighbridge software product aimed at simpler weighbridge sites. Pricing starts from £25 per month for basic sites. It handles weighbridge ticket generation, vehicle records, and basic reporting, but is not a full waste management platform. For operators who only need basic digital weighbridge records and manual DWT submission, OpenWeigh costs less than an upgrade to a full platform.
The limitation is that OpenWeigh does not connect to job management, invoicing, or route planning. It is a weighbridge-specific tool. Some operators run OpenWeigh next to a separate job system. They still type the data twice. The problem is now only at the weight, and not across the whole job.
Some larger operators run an ERP that was never built for waste. That may be a general accounting system such as Sage, or a build of their own from the 1990s. These systems often have no waste-specific data structures and no API for modern integration. The weighbridge data must then come in through a spreadsheet, a screen somebody types into, or a weak file link. That link breaks when either system changes.
This is the hardest integration problem to solve with off-the-shelf software. Every platform sold to the waste sector assumes its own data model is the centre of the system. The ERP sits at the centre, and the weighbridge software sits at the edge. The connection must therefore be built for that ERP data model. The model changes with each version, and with each set-up.
Connect with us about waste management software · · Replies within 24 hours
The article gives the reason and then moves on, but it is the whole story. No vendor will build and keep a general connection to weighbridge hardware. The equipment differs at every site, and none of it is theirs.
That is a market problem, not a technical one. The work is one job, done once, for a few common indicator protocols. One vendor that did it would carry the cost alone, and gain little. Every vendor therefore charges for a connection built for one customer at a time. The sector pays for the same work again and again.
A shared foundation is where such work belongs. A weighing, a gross weight, a tare, a net tonnage and an EWC split are declared once, for every operator system. The indicator connection is built once, against the foundation, and every site that uses that indicator has it. Each operator still owns its own system above that.
We explain how a whole sector shares one foundation in bespoke software for a whole sector. We describe the market it creates in what does an interoperable software market look like.
A bespoke waste management system can be built around the specific hardware on site. Rather than buying a generic platform and hoping the weighbridge module covers the edge cases, the integration is designed from the hardware spec outward. The TCP/IP point of your own indicator is written down, and the data format is mapped. The job system then reads it straight, with nothing in between.
Some sites are complex. Several lanes. Mixed streams tipped together. Hauliers from other firms arriving. Commercial accounts to invoice. A connection built for them removes the whole class of error that a ready-made platform works around. It also means the DWT submission workflow can be built into the job completion process rather than bolted on as an afterthought. A good system keeps a full audit trail, to the second. Any tonnage figure somebody disputes can be traced to the weighbridge reading that produced it. See what bespoke systems include as standard for more on these capabilities.
The constraint is timeline. Any bespoke system needs to be in production before October 2026 to meet the DWT mandate. You may have found that your platform reads the weighbridge badly. You then have three choices. Buy and set up the connection part from your current vendor, which is quickest but may still fall short. Look at another ready-made platform. Or have a connection built for you.