Driver cabinet for a carrier: trip order, documents, refuels
The challenge
A carrier with nine reefer trucks ran its trips in a system, but drivers lived outside it: the dispatcher forwarded the customer order via Viber, refuels were dictated over the phone, and reefer fuel was not tracked at all — written off “by eye” together with the truck. Meanwhile the trackers of several trucks periodically “teleported” them to South America at 200 km/h, and the map showed nonsense.
What was built
We extended the driver cabinet inside the existing trip system. The driver signs in from the phone and sees only the current trip: route, customer, trip documents and an “Order #…” row — the PDF opens in an embedded viewer right in the Android browser, photos and Word/Excel in a new tab. A refuel is logged with a button and a receipt photo; a separate “Reefer refuelled” button keeps the reefer tank as its own fuel store on the trailer with its own burn. For GPS we added a false-point filter: a position faster than 150 km/h or outside Europe is discarded and the last genuine point from history is used.
Only their own trip
the driver sees the current trip, route and documents; other trips and company money are out of reach.
Customer order on the phone
the order PDF opens in the embedded viewer without downloading files; photos too.
Refuels with a photo
litres, amount, station and receipt logged in a minute and posted straight to trip expenses.
Reefer fuel separately
the reefer tank keeps its own balance on the trailer; reefer burn never mixes with the truck.
Service requests
the driver describes a problem with photos, a mechanic takes the job; the owner sees who took it.
False GPS point filter
jumps above 150 km/h or outside Europe are dropped, so the map and mileage stay truthful.
The result
The dispatcher stopped forwarding orders to messengers and refuels are no longer written down “from voice”. Reefer fuel is visible as a separate figure per trailer for the first time, and the “trips to Peru” vanished from the map.
Tech stack
Have a similar challenge?
Discuss a projectNext case
Standalone instance
A carrier’s own TMS instance in a day →