Freight, Fleet, and Clearing Management for Tanzania's Transport Corridor — Avoiding Demurrage and Detention Costs

Dar es Salaam port is the gateway for far more than Tanzania itself — Zambia, the DRC, Malawi, Rwanda, Burundi, and Zimbabwe all move a significant share of their import and export cargo through it, onward by road along what's usually called the Central Corridor. That means a large share of Tanzania's transport and logistics companies aren't just trucking businesses — they're also, in the same breath, clearing agents, because the truck and the customs declaration for what's on it are the same job.

One business, two jobs that have to stay in sync

If you run cross-border haulage out of Dar es Salaam, you're almost always managing two things at once for every consignment:

1. The physical movement — dispatching a truck and driver, tracking the trip to the border and beyond, keeping the vehicle's compliance documents current.
2. The customs clearance — lodging the TANSAD declaration, tracking duty assessment and payment, and getting the container released before it starts costing money just for sitting still.

When these two sides are tracked in different places — a driver's WhatsApp group for dispatch, a clearing agent's own paper file for the declaration, and a spreadsheet someone updates once a day to try to reconcile the two — the gap between them is exactly where costs and mistakes creep in.

Fleet compliance: the paperwork that grounds a truck

A truck can't legally move without its compliance documents current — and a corridor truck typically needs more of them than a domestic-only one:

• Insurance
• Road licence
• LATRA (Land Transport Regulatory Authority) permits
• COMESA Yellow Card (third-party insurance valid across COMESA member states)
• SUMATRA-equivalent requirements depending on the route

Any one of these lapsing mid-trip is a real, expensive problem — a truck held at a border post for a permit that expired three days ago is a truck earning nothing while still costing fuel, driver wages, and often demurrage on the cargo it's carrying. Tracking document expiry dates against a dispatch calendar, not just a filing cabinet, is what actually prevents this.

Demurrage and detention: the clock that never stops for you

These two charges are where cross-border freight margins actually get eaten, and they work differently from each other:

• Demurrage accrues while a container sits at the port, past its free period — typically 7 free days before charges start, though this varies by shipping line and terminal.
• Detention accrues after the container leaves the port, while it's still out with you (at a depot or your own yard) before being returned empty — typically 3 free days.

Both are calculated the same way: free days, then a daily rate for every day past that. The problem in practice isn't the formula — it's that "how many days has this container actually been sitting" requires knowing exactly when it was discharged, when it left the port, and when it's actually returned, which are three different milestones often tracked (if they're tracked at all) in three different places.

What full corridor visibility actually requires

Putting fleet, trip, and clearing data in one place means being able to answer, for any container right now:

• Which truck and driver is hauling it, and where they are in the trip
• Which clearing declaration it's tied to, and what stage that declaration is at
• How many demurrage or detention days it's already accrued, and what that's costing
• Whether the truck itself is even legally allowed to be on the road today

Most companies currently answer this with a manually compiled daily tracking spreadsheet — someone cross-referencing the trucking dispatch board against the clearing file against the shipping line's own container status page, once a day, by hand. It works, but it's a day behind by design, and it doesn't scale past a handful of containers before someone misses one.

How eSecured ERP addresses this

eSecured ERP Platform's Logistics, Clearing, and Container Tracking modules are built to share the same data, not three separate systems that have to be manually reconciled:

• Job & Trip Management — dispatch a truck and driver against a job, track the trip status from dispatch to delivery, and record income and costs in whichever currency the job is priced in
• Fleet compliance tracking — every vehicle document (Insurance, Road Licence, LATRA, COMESA, and more) with its own expiry date and an automatic alert window before it lapses, so a truck's paperwork never becomes a border-post surprise
• Clearing & Forwarding — the full customs declaration lifecycle (Draft → Lodged → Assessment → Paid → Released → Delivered → Closed) with a document checklist, so nothing gets lodged with TRA incomplete
• Container Tracking — every milestone from vessel arrival through to empty return, with demurrage and detention calculated automatically from the same free-day and daily-rate figures you'd otherwise be tracking by hand
• Corridor Tracking Report — the one report that actually replaces the manual spreadsheet: one row per container, joined to its trip (truck, driver, checkpoint progress) and its clearing declaration, so you see the whole picture without cross-referencing three separate tools

Because it's the same underlying data, a container's demurrage clock, its clearing stage, and the truck assigned to move it once released are always looking at the same numbers — not three versions that might already disagree by the time someone checks.

Getting started

If you're currently reconciling trucking dispatch against clearing status by hand, the fastest way to see the difference is to look at a single container end-to-end: discharge date, clearing stage, assigned trip, and current demurrage/detention days, all in one row instead of three files.

Read the Logistics module documentation →, the Clearing & Freight module →, or the Customs Clearing Process in Tanzania guide → for the step-by-step declaration process this all builds on.