Real application, sample data for a Johor Bahru hauler. Sign-in details are on the login screen itself.
Everything a waste hauler does between the bin and the invoice.
Real application, sample data for a Johor Bahru hauler. Sign-in details are on the login screen itself.
A hauler signs a customer, agrees a schedule and a rate, sends a truck, weighs the load, and bills for it. That is one continuous chain. In most yards it is spread across a scheduling whiteboard, a WhatsApp group, a folder of weighbridge slips, and an accounts package that knows nothing about any of it.
Every gap in that chain is a place where a pickup gets missed, a ticket goes unbilled, or an office re-types something a driver already recorded.
Sites, bin types, pickup days, frequency and rate. The contract is the thing everything downstream is derived from.
Scheduled services generate their own orders ahead of time; ad-hoc requests come in from the customer portal or the office.
The planner builds the day from open orders and truck types, sequences the stops, then publishes. Nothing reaches a driver until it is published.
Stops in order on the phone, with navigation, bin exchange, photos, signature and reason codes for a skip or a miss.
Transfer stops and landfills are part of the route, not an afterthought. Weighbridge tickets attach to the trip that produced them.
Completed work becomes invoice lines under the contract's own pricing rules, then a public payment link the customer can settle without an account.
Planning, dispatch, customers, assets, records, billing, reports and automations. The office lives here all day.
Today's route, stop by stop. Works with one thumb in a cab, and captures the evidence the invoice will need.
Request a pickup, see when the truck came, open the photos and the weight ticket, pay the invoice.
Most fleet screens are a table of trucks and a table of drivers. The Yard draws the day instead — each truck as a lane running from the depot, out through its stops, into the tip, and back — so idle time, an overloaded lane and a driver with nothing assigned are all things you see rather than things you calculate.
It is in the demo under Fleet & Assets → Yard, and it is the screen most worth opening first after the dashboard.
A node graph with event and schedule triggers: notify on a paid invoice, chase an overdue one, react when a stop is missed. Versioned, with a run history.
Ask about today's shift in plain language and get an answer from live data, not a generic model guess.
Tonnage, trips, service records and billing, filtered and pulled out in the shapes an accounts team already uses.
Business rules live in one place and are covered by tests, so the web app, the mobile apps and the automation engine cannot drift apart on what "completed" or "billable" means.
The demo is pinned to the day the sample shift ran, so every screen opens with a full day of work rather than an empty one. Sign-in details are on the login screen. Change whatever you like — the database is wiped and re-seeded on a schedule.