Logistics operators in the UAE buy visibility and still cannot answer where a shipment is. The platform is in place, the carrier integration is connected, the dashboard shows tracking, and yet the customer call still triggers someone phoning a broker or a warehouse to find out. The instinct is that the tracking is not good enough and a better platform is needed. That instinct is wrong in a specific, expensive way: visibility in a multi-modal journey does not fail inside the legs, where the carrier provides data. It collapses at the handoffs between modes, custodians, and systems, in the bands where the shipment is real but no system is watching it. The operator did not buy too little tracking. It bought tracking for the parts that were never the problem.
This piece is a perspective on why multi-modal shipment visibility breaks at the handoffs rather than within the legs. The argument is opinionated. We are not arguing that carrier tracking is useless, or that operators are careless. We are arguing that a UAE multi-modal journey is a sequence of well-instrumented legs separated by blind bands at every change of custody and system; that the cost, the customer-facing failures, and the firefighting all concentrate in those bands; and that the durable fix is connecting the handoffs, not buying another platform that tracks the legs better. Visibility is not a tracking quality problem. It is a continuity problem at the seams.
The audience for this analysis is operators and technical leads of UAE freight forwarders, 3PLs, and supply-chain operators who have invested in tracking and still spend their day reconstructing shipment status across systems. The useful diagnostic question is not "is our tracking accurate" but "when a shipment moves from the carrier to customs, from customs to the warehouse, and from the warehouse to the road, does any system observe it during those moves, or is it dark until the next system picks it up".
The Journey, Leg by Leg and Band by Band
Below is a multi-modal journey shown as what it actually is: instrumented legs interrupted by blind bands at the handoffs. The point is not that any leg is poorly tracked; it is that the bands between them, arrival to customs, customs to warehouse, warehouse to onward carrier, are where the shipment is unobserved and where the operator's day is spent. Tap any leg or band to see what is happening there, where visibility goes, and what connecting it changes.
A multi-modal journey: visible legs, blind handoffs
Tap a leg or a blind band for what happens there and what connecting it changes
Why the Seams, Not the Legs, Are the Problem
The reason visibility fails at the handoffs is that each leg is observed by whoever owns that leg, and no one owns the transition between legs. The carrier exposes vessel-level data for the ocean leg. The broker sees the clearance. The warehouse system holds the goods while they are stored. The fleet or onward carrier tracks the final leg. Each of these is genuinely instrumented within itself. The shipment is dark in the moments it has left one party's domain and not yet entered the next, because those moments belong to no system. Buying a better platform for the legs improves the parts that already worked and leaves the bands that never did exactly as dark as before.
The UAE makes this acute because multi-modal is the normal case, not the exception. A single shipment routinely arrives by sea at a major port, clears customs, transfers into a bonded or free-zone warehouse, and dispatches by road or air, crossing four custodians and four systems in one journey. Each transition is a blind band, and a journey with several modes has several of them. An operator whose platform tracks legs well is well-instrumented for the parts of the journey that were never causing the customer escalations and blind for the parts that always were.
This is why the failure is structural rather than a tooling deficiency. The customer-facing answer, where is my shipment, is only as good as the weakest band in the chain, because answering it means stitching together every system the shipment passed through, including the gaps where it was in none of them. The operator that is exposed here is not the one with poor tracking; it is the one with good tracking and unconnected handoffs, spending its operational capacity reconstructing what happened in the seams.
The shift in one observation
Multi-modal visibility read as a tracking-quality problem produces another platform that tracks the legs better. Read as a continuity problem at the seams, it produces a decision to connect the handoffs. The operators who spend their day on the phone reconstructing shipment status are usually the ones who upgraded the legs. The ones who do not are the ones who closed the bands.
Where the Better-Platform Instinct Breaks
The buy-better-tracking instinct breaks in four predictable places across a real multi-modal journey.
Carrier tracking mistaken for visibility
Vessel-level carrier data is real but coarse and stops when the leg ends. Treating it as shipment visibility hides the fact that the journey is mostly handoffs, and the gap only appears when the carrier signal does not reach the next custodian.
Arrival-to-customs left dark
Between the carrier signal stopping and customs status becoming visible, the shipment exists only in someone else's system. This first blind band is where the operator's day starts, with a call to a broker to find out what the platform cannot show.
Warehouse system not connected
A bonded or free-zone warehouse runs its own system that does not talk to the tracking platform. The shipment is dark from clearance until it is booked into the warehouse, and dark again at dispatch, two more bands no leg upgrade touches.
The answer is a reconstruction
Because the bands are uncovered, answering where is my shipment means reconstructing across every system it passed through. The customer-facing service level is set by the worst band, not the best leg, and no leg improvement raises it.
The Numbers
Two Ways to Approach Visibility
The difference between operators who can answer where a shipment is and those who reconstruct it is whether the handoffs are connected, not how good the legs are.
| Dimension | Better platform for the legs | Connected handoffs |
|---|---|---|
| Carrier leg | Tracked, sometimes upgraded again. | Tracked and held against the shipment continuously. |
| Arrival to customs | A blind band. A phone call. | Covered by connected customs and broker milestones. |
| Warehouse | Invisible to the end-to-end view. | Receipt and status linked to the shipment record. |
| Dispatch | Custody change unobserved. | Captured at the point custody changes. |
| Customer answer | A reconstruction across systems. | One lookup against a continuous record. |
An operator that cannot say where a shipment is rarely has bad tracking. It has good tracking and unconnected handoffs, and the journey is mostly handoffs. Upgrading the platform improves the parts that already worked and leaves the bands that never did exactly as dark as before.
What Connected Handoffs Look Like
The pattern in operators who can answer a status question with one lookup is recognisable. Carrier data is ingested and held against the shipment rather than checked on a portal when someone asks. The arrival-to-customs band is covered by connected customs and broker milestones, so the shipment is observed while it moves from the carrier domain into clearance. Warehouse receipt and status are linked to the shipment, so the end-to-end view does not blank out while goods are stored. The dispatch handoff is captured at the point custody changes. The result is a continuous record across the seams, so where is my shipment is one lookup rather than a reconstruction, and a delay in a band is seen while it can still be acted on.
This does not necessarily mean replacing the tracking platform or the carrier, broker, and warehouse systems already in place. In many operations the handoffs can be connected around the existing systems, so the bands are covered without changing what tracks each leg. Replacement becomes the better option mainly where the existing platform cannot hold a continuous shipment record across systems it does not own. Which applies is specific to the systems and the route profile, and is established in scoping before any build commitment.
How This Sits Alongside the Operator's Own Responsibilities
The configuration keeps a clear separation. The operator runs the logistics business, holds the relationships with carriers, brokers, and warehouses, makes every operational and commercial decision, and is responsible for its own customs and regulatory compliance. The software is the instrumentation: connecting the handoffs so the shipment record is continuous across the systems the operator does not control.
This is the role BY BANKS is positioned for. We are an independent software engineering company based in the UAE. We design and build software and hand it over to the operator who runs it. We are not a carrier, broker, or warehouse operator, we do not move goods or make customs determinations, and we are not affiliated with or endorsed by any carrier, authority, or portal operator. The operator owns its operations, its commercial decisions, and its own compliance; we build the system that keeps visibility continuous across the handoffs. The accountable party leads and owns the obligations; we build to their direction.
Where This Analysis Is Useful
The conversations where this perspective is most useful tend to be at three moments: an operator that has invested in tracking and still spends its day reconstructing status; a technical lead who realises the platform tracks legs the customer never asks about and is dark at the handoffs the customer always does; or an operator scaling multi-modal volume and finding the phone-the-broker model no longer copes. The honest answer is usually the same: the journey is mostly handoffs, the visibility level is set by the weakest band, and connecting the seams beats upgrading the legs.
For broader related work, see our perspective on why Dubai customs is a layered integration problem and our perspective on why citizen-portal projects succeed or fail before any code. The applied work sits across our supply chain visibility platform and freight forwarding software capabilities, within the broader logistics software practice and our operational platforms work. Get in touch if a 45-minute conversation about a specific route profile would be useful.
Frequently Asked Questions
No. We are an independent software engineering company based in the UAE. We design and build software and hand it over to the operator who runs it. We are not a carrier, broker, or warehouse operator, we do not move goods or make customs determinations, and we are not affiliated with or endorsed by any carrier, authority, or portal operator. On any engagement, the operator owns its operations, its commercial decisions, and its own customs and regulatory compliance. We build the system that connects the handoffs; the operator and its partners run the legs.
Because a good platform usually tracks the legs well and is dark at the handoffs, and the journey is mostly handoffs. The point is not to replace what tracks the legs; it is to cover the bands between them where the shipment belongs to no system. If your status questions still require phoning a broker or a warehouse, the platform is not the gap; the seams are.
No. They are an observational generalisation of a typical multi-modal journey, used to make the continuity point clear. They describe no specific shipment, carrier, broker, warehouse, lane, or determination. The actual handoffs and systems differ by operation, and the right coverage is established against the specific route profile, not from this generalisation.
Often not. In many operations the handoffs can be connected around the existing tracking, carrier, broker, and warehouse systems, so the bands are covered without changing what tracks each leg. Replacement becomes the better option mainly where the existing platform cannot hold a continuous shipment record across systems it does not own. Which applies is specific to the systems in place and is established in scoping before any build commitment.
It is sequenced and does not require pausing operations. The usual starting point is the blind band that generates the most customer escalations and manual reconstruction, often arrival to customs or the warehouse handoff, connected first so the worst band stops setting the service level. The remaining bands follow in order of operational cost. The order is driven by where the reconstruction effort concentrates, which scoping establishes for the specific route profile.
Multi-modal shipment visibility is widely treated as a tracking-quality problem and is in practice a continuity problem at the seams. A UAE journey is well-instrumented legs separated by blind bands at every change of custody and system, and the cost and the customer escalations live in the bands, not the legs. The operators who can answer a status question with one lookup are the ones who connected the handoffs rather than upgraded the legs again. The build is software work; the operations, the commercial decisions, and customs and regulatory compliance remain entirely the operator's and its partners', and the system simply keeps the shipment record continuous across the seams so the answer is a lookup and not a reconstruction.
References to multi-modal logistics, UAE port and airport infrastructure, free zones, bonded warehousing, and carrier and customs systems are descriptive of publicly known structures. This article cites no market figures; the legs and bands are an observational generalisation of a typical journey, not a specific shipment, lane, or determination. Patterns and observations reflect our perspective and are observational estimates rather than measured statistics. BY BANKS is an independent software engineering company; we are not a carrier, broker, or warehouse operator, we do not move goods or make customs determinations, and we are not affiliated with or endorsed by any carrier, authority, or portal operator. On any engagement, the operator owns its operations, its commercial decisions, and responsibility for its own customs and regulatory compliance. This article is not customs, contractual, or operational advice; operators should obtain qualified advice for their specific obligations. Public sources used in this piece are listed on our Sources and Data page.
Ready to Build Something?
If this resonated, let's talk about how we can apply these ideas to your business.
Start a Conversation