Your whole operation in one place, for bulk fuel carriers and the sites they supply. Dispatch loads, track trucks, read BOLs and watch tank levels from one screen, then invoice without retyping a thing.
Dispatch a load once. Every surface after that already knows it.
What follows is one working day as Haulpoint sees it - Load 7742, 50,000 litres of clear diesel loaded at the rack, from the customer’s order the day before to your recap, the invoice and the driver’s pay at the end.
15:08-1
Customers place tomorrow’s fuel through their own order form - no login, no phone tag - and each order lands on the board as a load waiting for a truck. Dispatch schedules what the customer typed; nobody copies it out of an inbox.
16:40-1
Loads live on a week board - chips you drag between drivers and days. When the board is set, each driver’s day goes out by SMS. If the plan changes after that, the next text says CORRECTION, and the chip wears an amber dot until it is re-sent.
04:05
The driver touches his fob on and the day opens: the logbook starts counting, the engine reports off its own data bus, and both cameras wake with the ignition. Drive, on duty and the seven-day cycle keep themselves from there.
A hard brake or a phone in a hand clips twelve seconds against the driver, so coaching opens with footage rather than an argument - the whole of what a separate telematics subscription was for. The camera is Haulpoint’s own, supplied on the rate - or the day runs off the telematics already in the trucks.
04:52
The driver photographs the bill of lading from the phone browser they already have. The document number, product, corrected litres and load time land on the load by themselves - the corrected figure, not the gross printed beside it.
Where the scan and the planned quantity disagree, the scan is what gets invoiced - and the sheet stays on the load, so a delivery questioned in November is settled by opening it.
06:14
Brightness encodes progress: a load takes colour only once paper exists, and the truck’s live position rides the LOADED pill.
Arrival and departure come off the site’s own geofence, so DELIVERED is something the truck reported rather than a box somebody remembered to tick.
17:05
The recap reaches the customer that evening, the invoice bills the scanned litres at month end, and every two weeks the driver signs off their own hours by text before the pay run settles. None of it is typed twice.
05:59+1
Site gauge consoles report by email each morning, and Haulpoint reads them on arrival. Each day becomes a reconciliation sheet per site - opening volume, receipts, transfers, closing volume - so the people hauling the fuel and the people storing it look at one set of numbers.
Set an alert level per tank. Cross it and a bell and a critical email go to whoever should know. The point of watching a site is the call before it runs dry, not the sheet afterwards.
Prairie Fuels
Wheatland Colony
Submit your fuel order.
Delivery date
Wed, Jul 8, 2026Colony yard
+ Add loadGeneral notes (optional)
| Driver | Tue 7 | Wed 8 | Thu 9 |
|---|---|---|---|
K. Morin163 · 171 | 774250CD | ||
T. Rehn168 · 567 | 773828CD | 1180-20450DL | |
R. Dionne131 · 561 / 563 | Off | 1180-20528CG | 1180-20828CG |
Wednesday, July 8th Unit: 163 Load #: 7742 50,000 Clear Diesel 4. Redcliff Notes: rack card at the gate
haulpoint.app/f/daily-report?d=…
CORRECTION - this replaces the earlier text: Wednesday, July 8th Unit: 131 Load #: 1180-205 28,000 Clear Gas 2. Elkwater cardlock
haulpoint.app/f/daily-report?d=…
EDMONTON TERMINAL
BULK LOADING RACK 264
Bill of lading
DATE
JUL 08
UNIT
163
TRAILER
923
DRIVER
K. MORIN
Load start
04:31
Load finish
04:52
Destination
REDCLIFF
Total litres by product
| Load | Status | Region | Destination | Products | Driver | BOL | |
|---|---|---|---|---|---|---|---|
| 1180-204 | LOADED | NGT | Willow Creek | DD · 50,000 L | TRRehn | BOL | › |
| 1180-205 | CONFIRMED | MRD | Elkwater cardlock | CG · 28,000 L | RDDionne | No upload | › |
| 7742 | DELIVERED | RCF | Redcliff | CD · 50,132 L | KMMorin | BOL | › |
| 1180-207 | TEXTED | NGT | Cypress Lake | CD · 32,000 L | MBByrne | No upload | › |
| 7746 | UNSENT | RCF | Burdett cardlock | CG · 20,000 L | JTRoy | No upload | › |
Wheatland Colony - Daily Recap - July 8
17:05Wednesday, July 8
Scheduled for Thu, Jul 9
Sent by Haulpoint on behalf of Prairie Fuels.
View BOLsDispatch, deliveries and tank inventory - haulpoint.app
The demo below is the real dashboard, dressed as a bulk fuel carrier’s workspace: loads dispatched by text, BOLs read at the rack, billed from the scanned litres at month end. Every screen in the rail opens, and the theme toggle at its foot is the real one.
331R. Cardinal97 km/h
Highway 21, Beaver County, AB
318M. Beaudry104 km/h
Highway 16, Parkland County, AB
326T. Ostrowski98 km/h
Township Road 540, Lamont County
312Parked
Beaver Hills yard, bay 3
55%
49,994
Tank 1
Clear Gas
44%
40,476
Tank 2
Dyed Gas
61%61%
72,90072,900
Tank 3
Dyed Diesel
38%
11,900
Tank 4
DEF
$724/month5 units, with hardware
You’ll talk to the person who built it, not a sales queue.
Most of those lines are sold as separate subscriptions somewhere else - a TMS, a telematics platform, a tank monitor, a document drive. Here they are one bill, and the hardware is part of the offer: camera and GPS supplied - or Haulpoint reads the hardware already in your units.
Month to month - leave any time.No onboarding fee.Support is your account manager, not a call centre.
Haulpoint is web software for bulk fuel carriers and the sites they supply. It runs the dispatch board, texts each driver their day, collects their hours, tickets and bills of lading, tracks tank levels at supplied sites, and turns the day’s litres into recaps, invoices and pay.
Trucking fleets that haul bulk fuel - dispatching loads, scanning BOLs at the rack, and billing by the litre. The sites you deliver to see their own tank levels and delivery numbers, but the platform is built for the carrier.
Through their own order form - a link, no login. It lands on the carrier’s dispatch board as a load waiting for a truck, exactly as the customer typed it. Dispatch schedules it from there; nobody copies tomorrow’s fuel out of an inbox or a voicemail.
The driver photographs the BOL at the rack. Haulpoint reads the document number, product and corrected litres off the image and attaches it to the load, so nothing is retyped. Where the scanned litres and the planned quantity disagree, the scan is what gets billed.
Filed on the load or the unit they belong to as they are captured - BOLs, scale tickets, shop invoices, inspection photos. Months later they are still one search away, so nobody phones a driver hunting lost paper, and a disputed delivery is settled by opening the load.
Bulk sites email their gauge reports in, and Haulpoint reads the tank levels out of them. Each day becomes a reconciliation sheet per site - opening volume, receipts, transfers, closing volume - so what a carrier says it delivered can be checked against what the tanks show.
No. A driver gets a link by text and files their hours, loads and BOL photos from the phone browser they already have. No app to install, no password to reset - which matters on a crew that changes through the season.
Yes, nightly. The whole database and every stored document - BOL scans included - are copied to an independent archive at a separate provider, chosen so the copy survives even the loss of Haulpoint’s own hosting. The archive only grows: a file deleted in the app stays in it.
It can. One road-and-cab camera carries the telematics: GPS, engine diagnostics off the truck’s own J1939 bus, hours of service the truck keeps itself, and safety events that roll up per driver. Fleets keeping their Samsara hardware run the software half alone - Haulpoint reads the boxes already installed.
Every powered unit bills the same - tractors, straight fuel trucks and pickups. They all get the same features, so they all carry the same rate. Monitored tanks are free: their gauges already carry a monitoring fee, and reading them should not cost twice.
An account manager with a direct line - the same person every time, who knows your fleet, your sites and your setup. Questions go to the people who build and run Haulpoint, not a ticket queue or a call centre reading a script.
You talk to the person who built it, about how your operation runs today. If it fits, setup starts with your fleet list and your sites - no onboarding fee, no long contract, so the risk of trying it is a month.
Tell us how it runs now - the trucks, the tanks, the paper. The person who built it answers, usually the same day, with what it would take and what it would cost.