Proten runs 5 tonne trucks between Lusaka, the Copperbelt, Kasumbalesa and Livingstone. Every consignment is tracked against an approved route corridor, sealed at loading, and released only against a one time code held by the person receiving it.
All units are 5 tonne flatbeds with a hardwired tracker and a cargo door sensor. Trucks already on a run are shown with their current load. Your selection carries through to the booking form.
Price scales with road distance and cargo weight up to the 5 tonne limit. Cross border runs carry a clearing line, and goods in transit cover is priced off the value you declare.
Demo figures. Replace the tariff in assets/js/data.js with your real fuel, permit, border and insurance costs before quoting a client.
Fill in the route and cargo details. You get a tracking code as soon as the booking is confirmed, and the consignee gets the handover code by SMS when the truck arrives.
A tracking code on its own is not enough. You also confirm the last four digits of the mobile number on the booking, so a guessed code gets nobody anywhere.
Tap a demo consignment to fill the form, then try changing the PIN to see the refusal and the logged attempt.
--
| Tracking code | Route | Truck | Booked | Status |
|---|
This table is scoped to one client account. In the real system that scoping is enforced in the database with row level security, not in the page, because one missing filter on one endpoint would expose the whole client book.
Every load that leaves the depot follows the same checks. Each control below is a live rule in this demo, not a claim on a brochure. Open the dispatch console and trigger an incident to watch them fire.
Each run has an agreed corridor. Drift beyond the limit raises a critical alert with the distance off route and the direction of travel.
CORRIDOR_DEVIATION · 4 kmAuthorized stops are on the plan with a dwell allowance. Standing still anywhere else, or overstaying a listed stop, calls dispatch.
UNSCHEDULED_STOP · 12 minA numbered seal is logged at loading and checked at every handover. A door opening away from an authorized stop is not ambiguous, so it is treated as critical.
DOOR_OPEN_IN_TRANSIT · SEAL_BROKENThe consignee gets a six digit code by SMS. The driver cannot close the delivery without it. Three wrong attempts hold the load and call dispatch.
OTP_FAILED · 3 attemptsPositions, seal checks, checkpoints and handovers are chained by hash. Editing history after the fact breaks the chain and the console shows exactly where.
SHA-256 audit chainA critical alert must be acknowledged within five minutes or it escalates to the duty manager automatically. Detection without a staffed response is theatre.
ackSla · 300 sHardwired units authenticate with a client certificate and buffer positions on board through dead zones, so the trail has no holes and a spoofed feed is rejected.
SIGNAL_LOSS · 15 minClients see their own consignments only. Drivers see the trip in front of them. Location history is staff data as well as cargo data, so views are logged.
TRACK_LOOKUP auditIllustrative quotes for this demo build, not real client statements.
We ship copper components to Kasumbalesa every fortnight. Seeing which checkpoint the truck has cleared has cut our follow up calls to almost nothing.
The handover code is what sold us. Our finance team finally has proof of delivery they can file without chasing anyone.
Booking a 5 tonne truck used to mean a phone call and a guess. Now I pick the truck, see the price, and track it myself.
The questions clients ask most before their first booking.
Writing binary protocol handlers for tracker hardware is months of work with no competitive advantage at the end of it. Buy the positioning layer, build the shipment layer, because that is where the value and the differentiation sit.
The interface is the easy half. Here is the order of work, from hardware through to the first live shipment.
Existing client, new corridor, or a partnership enquiry. Send a message and dispatch will get back to you.
Head office and main dispatch point for all routes.