Ask any transport manager running cross-border freight out of Dar es Salaam how they answer the question "where's my truck?" and most will give you the same answer: they call the driver.
It's not a bad system. It's just not a system. It's a phone call, made by someone senior enough to know which driver to call, to a person who might be in a weighbridge queue, out of network near the border, or simply asleep. Twenty minutes later, the answer that comes back describes where the truck was twenty minutes ago — not where it is now, and not why it took an extra half day to get there.
Multiply that by a fleet of 40 trucks and a customer on the other line asking the same question about their cargo, and "where's my truck" stops being a small inconvenience. It becomes the single most repeated, most disruptive question in the operation — one that pulls a dispatcher off everything else, several times a day, for an answer with a built-in delay.
The real cost isn't the phone call
The phone call is annoying. The actual cost is what happens in the gap it can't see.
A truck idles for six hours at a weighbridge and nobody notices until the driver mentions it at the next checkpoint. A route detour adds two hours that never gets explained. A breakdown happens forty kilometres off the planned corridor and the first anyone hears of it is a call for help, not an alert.
None of these are dramatic events. They're small, quiet gaps in visibility — and on a corridor like Dar es Salaam to Zambia, which runs roughly 1,980 km and 36 hours under normal conditions, a few unexplained hours here and there compound fast across a fleet running that lane every week.
What live tracking actually needs to do
A GPS dot on a map answers "where is the truck right now." That's the easy 20% of the problem. The harder, more useful 80% is:
Historical playback. Not just where the truck is, but where it's been — the ability to scrub back through a completed trip and see the actual route, not the planned one. That's what turns "the driver said he stopped for two hours" into a route history you can check.
Off-route and idle alerts. A truck that drifts off a planned corridor, or sits still for longer than a stop should take, should raise a flag on its own — not wait for someone to notice it's been six hours since the last update.
Tamper detection. A tracking device that goes offline mid-corridor is either a technical fault or something worth investigating. Either way, it shouldn't be silent.
One map, every trip. Not a separate tracking app bolted onto a separate dispatch system bolted onto a separate spreadsheet. The trip, the route template, and the live position need to be the same record — otherwise you're reconciling three sources of truth instead of reading one.
How this works inside the system we built
Our Transport Management System, built on Odoo, plans every trip against a route template — the corridor, its checkpoints, distance and expected transit time set once and reused on every trip that runs it. From there, live GPS telemetry updates on the map in real time, with full historical playback available on any trip, completed or in progress.
If a truck drifts off-route, idles longer than expected, or its tracking device goes quiet, the system flags it — rather than waiting for a phone call to surface the problem.
It's the same trip record dispatch is already working from, not a separate tracking layer someone has to check in a different tab. And it's built to hold up at real operational scale: the system has been load-tested against 10,000 trips with 500 vehicles simulated concurrently and 20 dispatch users on it at once — against a full operational database, not a demo tenant with ten sample records.
What to look for if you're evaluating GPS fleet tracking software in Tanzania
If you're comparing options, three questions cut through most of the marketing quickly:
Does it show historical playback, or only a live dot? A live position is useful in the moment and useless a week later when you're trying to reconstruct what happened on a specific trip.
Does it live inside your dispatch and billing system, or next to it? Tracking that isn't connected to the trip record, the driver record, and eventually the invoice just becomes one more screen to check.
Has it been tested at the scale you're planning to reach, not just the scale you're at today? A system that works cleanly with ten trucks and falls over at fifty is a problem you'll hit exactly when you can least afford it.
"Where's my truck" should be a glance, not a phone call. If it still isn't, that's usually a sign the tracking exists somewhere in your operation but isn't wired into the rest of it.
See it on a live corridor: Transport Management System for Cross-Border Freight — or request a demo to see the live map on your own fleet's route.