This is a clickable version of a roll-off dispatch and billing platform we built for a dumpster rental and waste logistics operator. Branding removed, data invented, everything else the same. Open it and go straight to the dispatch board, which is where most operators decide within a minute whether software understands their day.
Unassigned deliveries and pickups drag onto trucks and time slots, with the whole day visible at once instead of a list you have to hold in your head.
Customer, job address, container size, service zone and delivery window, with the price calculated from tonnage and zone fees up front.
Pending, scheduled and completed orders, revenue, monthly volume and container inventory by size, all in one view rather than four tabs.
The interesting screen. Container sizes and tonnage allowances, pricing, service zones, time slots and materials, editable without a developer.
The production platform replaced a whiteboard, a spreadsheet and a phone. It covers dispatch scheduling, order management, customer and vendor records, automated invoicing and real-time fleet tracking, and it sends status notifications as jobs move so the dispatcher stops answering calls asking where the truck is. It runs on React, Node.js, Express and Supabase, with Pusher driving live updates.
No. Every customer, address, order and figure in it is invented, and all client branding has been removed. Nothing persists either, so anything you change resets the moment you reload the page. The screens themselves are the ones from the production system.
That is usually the real question, and it is why we build rather than resell. Tonnage allowances, zone surcharges, per-customer contracted rates and extra charges are configuration in this system rather than code. Rules that go beyond the settings screen are what we would build.
One price, agreed at discovery and written down before anything starts. A single piece, dispatch on its own or invoicing wired into software you already run, is a much smaller job. You get a real number after a scoping call rather than a range that moves later.
That is the usual case. The dispatch board assigns work to named drivers and trucks, and the whole day is visible in one view rather than reconstructed from phone calls. Brokers who subcontract the work out are a different shape, and we would build that differently.
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.