Port Operations Software for Terminals across the UAE

Who this is for: UAE terminal operators, stevedoring companies, free zone logistics operators (JAFZA, KEZAD), and port-adjacent 3PL providers handling regular volume at Jebel Ali, Khalifa Port, Fujairah, Port Rashid, or Al Maktoum cargo operations. Not positioned as a small inland container depot or yard app — those are well-served by off-the-shelf yard management tools; custom port operations software is for ecosystem-level integration across terminals, customs, free zones, and rail.

Six connected capability areas: (1) Terminal-customs operational layer with Mirsal 2 and AD Customs integration. (2) JAFZA and KEZAD free zone workflow integration. (3) Rail freight corridor integration for Khalifa Port-Fujairah and expanding network. (4) Transhipment and re-export live tracking. (5) Commercial performance reporting across flow types. (6) Dwell time analytics per container, per flow, per client.

Navis N4, Kaleris, Cyberlogitec OPUS, and Tideworks are mature terminal operating systems with significant UAE deployment. These handle container lifecycle — discharge, yard, gate-out, load — at scale. They are the operational backbone of modern terminals.

Custom port operations software is designed to sit alongside these terminal operating systems, closing UAE ecosystem gaps — Mirsal 2 and Dubai Trade integration at operational level rather than at release handoff only, AD Ports and Abu Dhabi Customs integration for capital operations, JAFZA and KEZAD workflow integration, and Etihad Rail freight corridor as native modal handoff. The terminal operating system retains container lifecycle authority; the custom layer handles UAE ecosystem depth.

Terminal operating systems manage container lifecycle events — vessel-side discharge, yard moves, gate-in and gate-out transactions, reefer power events, vessel-side load. Customs systems manage declaration lifecycle — declaration submission, inspection selection, release authorisation. The integration between the two typically exists at release handoff — customs releases the container, terminal operating system permits gate-out.

The operational layer deepens this integration. Mirsal 2 declaration status tracked continuously against terminal events. Inspection hold events trigger terminal planning adjustments. Pre-arrival customs clearance reflected in terminal discharge planning. AD Customs operations supported in parallel for Khalifa Port and Fujairah. Dubai Trade portal milestones — manifesting, booking confirmation, release orders, billing — synchronised with terminal workflow.

JAFZA (Jebel Ali Free Zone Authority) and KEZAD (Khalifa Economic Zone Abu Dhabi) run their own operational workflows — manifesting, customs treatment for bonded movement, free zone internal inventory operations, and outbound processing for re-export or onward UAE entry. These workflows sit alongside terminal operations but are typically managed in parallel systems.

The integration treats JAFZA and KEZAD operations as native workflow extensions. Bonded movement documentation generated automatically. Free zone inventory moves tracked with customs posture per container. Outbound processing for re-export or onward UAE entry drives customs declaration workflow downstream. JAFZA and KEZAD specific requirements — manifesting templates, customs treatment codes, bonded transfer documentation — handled natively.

Etihad Rail Phase 2 is operational across the network with the bonded Khalifa Port-Fujairah corridor piloting through late 2025 and expanding through 2026. Khalifa Port and Fujairah both have rail connection. Rail creates modal handoff volume terminal operators need to plan for — slot availability, loading and discharge capacity, customs documentation continuity across port-rail movement.

The rail integration treats freight corridor as native modal handoff. Slot planning integrated with terminal yard operations — rail-bound containers staged appropriately, rail-arriving containers handled through terminal workflow. Customs documentation continuity maintained across port-rail handoff. Cross-modal cost and emissions reporting supported for commercial and Net Zero 2050 reporting obligations.

UAE terminal operations handle significant transhipment volume — containers discharged from inbound vessels, re-staged in yard, reloaded onto outbound vessels without formal UAE import. Re-export operations also meaningful — containers imported into UAE then re-exported. Distinguishing these flows from import-destined cargo matters for operational planning, customs posture, and commercial reporting.

The live tracking layer distinguishes flow types — transhipment, import-destined UAE, free zone entry, re-export, and onward GCC movement. Dwell time per flow type tracked live. Commercial performance reported per flow — transhipment dwell tight against vessel schedule, import dwell tracked against customs release, free zone entry tracked against bonded transfer workflow. Retroactive flow classification replaced by live operational visibility.

Here's where custom port operations software typically sits in a wider stack.

Terminal operating systems — we sit alongside Navis N4, Kaleris, Cyberlogitec OPUS, Tideworks, and RBS TOPS for container lifecycle and yard operations authority.

Customs and port systems — we integrate with Mirsal 2 (Dubai Customs), Dubai Trade portal, AD Ports, Abu Dhabi Customs, and Etihad Rail freight systems for declaration and modal handoff.

Free zone authorities — we integrate with JAFZA (Jebel Ali Free Zone Authority) and KEZAD (Khalifa Economic Zone Abu Dhabi) operational systems for bonded movement and free zone workflow authority.

Adjacent logistics — we connect with WMS systems (Manhattan, Blue Yonder, Oracle WMS), TMS platforms (Oracle OTM, SAP TM), and freight forwarding platforms (CargoWise, Descartes) where terminal operations feed into broader supply chain operations.

Integration approach is scoped during discovery. We don't ask you to rip and replace anything that works.

Discovery runs four to six weeks. Working with your operations, commercial, compliance, and technology teams, we map current terminal operating system posture, customs and free zone integration, rail corridor planning, and transhipment workflow. Output is a detailed report covering current-state map, platform architecture, integration scope per authority and TOS, phased implementation plan, and fixed-price build proposal.

Build for a core port operations layer runs twelve to sixteen weeks from discovery completion. Full Mirsal 2 and AD Customs integration, JAFZA and KEZAD workflow, Etihad Rail corridor connection, and transhipment live tracking rollout phases in over nine to fifteen months depending on terminal volume and ecosystem breadth.

Pricing varies by terminal volume, integration scope, and ecosystem breadth. A bracket isn't published; discovery produces a fixed-price proposal with no obligation to proceed.