Demo

    Scale house and weighbridge software demo.

    This is a clickable version of the weighbridge billing platform we built for a waste and recycling yard. It shows the part that matters most: a scale house screen where the weight comes from the scale rather than from someone typing it, and two ticketing flows that treat inbound and outbound loads as the different transactions they are.

    What to look at

    The scale house screen

    Live readings from connected scales, with ticket creation and active dispatches on the same screen, so the operator is not moving between windows mid-weigh.

    Inbound and outbound tickets

    Waste coming in and recycled material going out run as separate flows, each with its own capture, pricing and invoicing, because they are not the same transaction.

    Materials, rates and discounts

    Rate structures and charge rules per material, with contracted rates and discounts held against the customer rather than in someone's head.

    Reporting and export

    Ticket volumes, weights and financial summaries, filterable by date, customer, material and driver, and exportable when someone asks.

    The system this came from

    The production platform replaced handwritten weights and after-the-fact invoicing. The software is wired into the yard's weighbridge, so weights are captured rather than transcribed, invoices are raised when a job completes rather than at the end of the week, and the yard manager has a live view of what is on the scale and what has moved today.

    Answered before you ask

    Will this work with our own weighbridge?

    Usually. It depends on what the scale indicator exposes, whether that is a serial output, a network connection or a vendor SDK, and that is one of the first things we check on a scoping call. We have a system in production reading live weights directly from the hardware.

    Can it handle our own rate structure?

    Rates, charge rules, materials and per-customer contracted pricing are configuration in this system. Waste pricing tends to be local and full of exceptions, so the part we would build for you is whatever your rules do that the settings screen does not already cover.

    Is the demo connected to a real scale?

    No. The readings are simulated, the data is invented, and nothing persists between reloads. The screens and the flows are the ones from the production system, which does read live weights off the hardware rather than asking anyone to type them in.

    Do inbound and outbound loads work differently?

    They do, and it is the part most products get only approximately right. Incoming waste material and outgoing recycled material have their own capture, pricing and invoicing rules, because they are not the same transaction. This system treats them as two flows.

    Related

    Tell us what it has to do.

    Describe what you’re building, what it has to do and when it needs to be live. You’ll get back the architecture we’d use, the trade-offs, and a realistic timeline, before anything is signed.