What it does
Eight modules that switch on per company, so a one-truck operation is not paying for a dispatch board it will never open. The two at the top never switch off.
In the truck
Installed to the home screen it opens full screen, with the hauler’s own icon, and it does not need a browser or a signal to work.
A stop recorded in a basement is saved on the phone and sent up on its own when service returns. The queued count sits in the top bar so the driver can see nothing is lost — and re-entering a stop that says it is waiting is the one thing that makes two of them.
The driver’s, then the restaurant’s. Where a site has a standing authorization on file the app says so and skips the second one. Nobody there? Pick a reason and write a line — that is a proper record, not a shortcut, and it does not block finishing the stop.
A pin that starts on the street address and drags onto the real container — round the back, down the alley, behind the gate. Directions then go to the spot a driver last worked from, not to where the post arrives.
The grease, water, solids and oils split — which has to add to a hundred, give or take half a point — plus whether FOG was leaving the inspection port and the condition of the grease removal device. Only on a trap; a cooking oil pickup never asks.
Facility, quantity received, scale ticket, and the facility representative’s signature. That is the moment the record becomes a document and the customer copies go out — not when the truck left the restaurant.
The whole app, sign-in screen included, switched per person and remembered on the device. A shared cab phone can sit in whichever language suits whoever uses it most.
At the desk
The first panel is exceptions, not statistics: stops signed with nobody present, manifest emails that did not arrive, discrepancies against what the facility received, and sites now past their pattern. When it says all clear, it means it.
Set how often each site is serviced once. Press build and every active schedule becomes dated visits. Due dates come from actual pickups, so a site done early because a driver was passing counts as done.
You see the order and the mileage before anything changes, with a warning if the tank fills part-way and they will have to unload first. It does not know about the school on Shaw at three o’clock — if your order is better, leave it alone.
A finished manifest is never changed in place. Correcting it issues a new version marked CORRECTED with the date and the name, and keeps the original. An invoice is voided with a reason and its work becomes billable again.
Sites, containers, contracts, every manifest, documents with expiry dates, the activity log, and every email ever sent to them. “Can you send me everything from March” is three clicks, and each attachment carries only their own pages.
Gallons by customer, sites overdue, facility discrepancies, what is missing from your customer files, who owes what. Open any of them, change the dates, add a column, save it under your own name. Everything exports.
Pick a customer and a period and you are shown every stop that would be billed before you commit. Minimums and fuel surcharges land on their own lines so the arithmetic is visible. A stop on a live invoice can never appear on a second one — the database enforces it, not somebody remembering.
Your customers
Any contact on a customer record can be given a sign-in of their own. There is no password to issue and none to reset — they ask for a link and it comes to the address you already send their paperwork to.
They see their own locations, their own service history, their own manifests and their own sent invoices. They can ask for a collection, ask for a container to be taken away, or ask to start service somewhere new. A person answers it; nothing they press sends a truck.
One load routinely carries restaurants that compete with each other. The transporter’s stored manifest holds every page, because that is the transporter’s legal record — but every copy that leaves the building is rebuilt from that customer’s pickups alone.
Emailed automatically when the load closes, downloaded from the portal, or sent again by the office months later: same rule, every route out.
The modules
Turning one on takes effect on the next click, without anybody signing in again. The core two can never be switched off — a billing dispute must not lock a company out of records it is legally required to keep.
| Module | What it does | Included in |
|---|---|---|
| Manifests | Field capture, signatures, manifest PDFs, customer copies | Core — never off |
| Customer records | Customers, sites, contacts, containers, documents | Core — never off |
| Reporting | Twenty-two standard reports, a custom builder, CSV export | Every plan |
| Service contracts | Agreements, renewals, notices to a previous hauler | Operate |
| Pricing | Rates per customer or per site, minimums, fuel surcharges | Operate |
| Scheduling & dispatch | Recurring schedules, work orders, the day board | Operate |
| Routing | Orders the day from the yard, watches the tank fill | Operate |
| Invoicing & payments | Invoices from completed work, payments, ageing | Complete |
| Customer portal | Their own sign-in: history, manifests, invoices, requests | Complete, or $75/mo |
In every plan
We will put two of your real service locations into a working account, so you are looking at your customers rather than a demonstration.