Freight Forwarding Software for Operators across the UAE

Who this is for: UAE freight forwarders, NVOCCs, customs brokers, and multi-modal 3PL operators handling regular Jebel Ali, Al Maktoum, Khalifa Port, or Fujairah operations. Not positioned as a sub-20-shipment-a-month freight agent app — those are well-served by off-the-shelf platforms; custom software is for operations where UAE-specific integration depth and multi-corridor scope justify bespoke build.

Six connected capability areas: (1) Mirsal 2 and Dubai Trade integration layer with direct declaration workflow. (2) Multi-modal corridor orchestration across sea, air, road, and Etihad Rail. (3) Rate management with disruption-aware pricing. (4) Documentation and compliance automation. (5) AD Ports and Abu Dhabi Customs integration for capital operations. (6) Client portal and shipment visibility with real-time corridor status.

CargoWise, Descartes, Magaya, Riege Scope, and Shipamax are mature global freight platforms with significant UAE deployment. These handle core freight forwarding operations, accounting, and carrier integration at scale.

Custom freight forwarding software is designed to sit alongside these platforms, closing UAE-specific gaps — Mirsal 2 and Dubai Trade integration at the declaration level rather than reconciliation level, AD Ports and Abu Dhabi Customs workflow integration, Etihad Rail freight corridor support as it matures through 2025-2026, disruption-aware rate management reflecting Red Sea Cape routing, and documentation automation tuned to UAE FTA free trade agreement benefits. The global platform retains its accounting and carrier integration authority; the custom layer handles UAE-specific operational depth.

Dubai Customs' Mirsal 2 processes 98% of customs declarations electronically. Dubai Trade portal handles booking confirmation, release orders, and customs billing. Both are accessible via integration for registered users.

The integration layer drives Mirsal 2 declarations directly from shipment data — pre-arrival where applicable, standard where pre-arrival not used. Dubai Trade booking, release, and billing operations run from the same platform without duplicate portal entry. Mirsal 2 inspection notifications, amendments, and release events flow back to shipment status automatically. Typical outcome is a material reduction in declaration errors, a time saving per shipment measured in hours, and improved customs relationship through pre-arrival clearance usage.

UAE freight operates across multiple corridors — Jebel Ali sea freight (15.5M TEU 2024), Al Maktoum and Dubai International air cargo (2.2M tonnes 2024), GCC road corridors to Saudi Arabia and Oman, Etihad Rail freight with the Khalifa-Fujairah bonded corridor piloting Q4 2025, and Fujairah and Khalifa Port sea alternatives.

The orchestration layer models each shipment's planned multi-modal route. Booking spans carriers per mode — shipping lines (Maersk, MSC, CMA CGM, Evergreen, ONE, Hapag-Lloyd), air carriers (Emirates SkyCargo across 140 destinations, Qatar Airways Cargo, Etihad Cargo, and freighter operators), road carriers including UAE operators, and rail through Etihad Rail's operational corridor. Handoff points tracked with customs documentation continuity.

Red Sea disruption since late 2023 has added 10-14 days to Asia-to-Europe trade via Cape of Good Hope routing — a fundamental transit-time shift that invalidates rate cards built around pre-disruption Suez assumptions. Client quoting systems that don't reflect current routing reality surface as commercial and operational problems.

Rate management runs from current operational data — carrier GRIs (General Rate Increases), PSS (Peak Season Surcharge) applications, BAF (Bunker Adjustment Factor) changes, and transit-time reality. Quote validity windows aligned to carrier commitment windows. Booking confirmation captures locked-in rate against live market. Historical rate performance analysed per lane to inform spot vs contract pricing strategy.

Freight forwarding documentation typically involves bill of lading (master and house), airway bill, commercial invoice, packing list, certificate of origin, phytosanitary or health certificate where applicable, and hazmat DGN for dangerous goods. Manual assembly per shipment creates error rates and slows clearance.

Documentation is generated from shipment data with format variation per destination country and per commodity. UAE FTA free trade agreement benefits — including CEPA with India and similar agreements — captured at tariff-line level where applicable. Hazmat DGN workflow supported with IMDG, IATA DGR, and ADR compliance. Sanctions screening across UN, OFAC, and EU lists for all parties with continuous refresh rather than per-shipment lookup.

Here's where custom freight forwarding software typically sits in a wider stack.

Global freight platforms — we sit alongside CargoWise, Descartes, Magaya, Riege Scope, and Shipamax for accounting, global carrier integration, and cross-office 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, booking, and release operations.

Warehouse and cold chain — we connect with Manhattan WMS, Blue Yonder, Oracle WMS, and cold chain providers (Sensitech, Controlant) where freight includes bonded or cold storage legs.

Client portals and visibility — we integrate with or replace project44, FourKites, Shipsy, and similar visibility layers where client-facing transparency is competitive differentiation.

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 Mirsal 2 posture, Dubai Trade integration, AD Ports workflow, corridor exposure, and rate management approach. Output is a detailed report covering current-state map, platform architecture, integration scope per port and carrier, phased implementation plan, and fixed-price build proposal.

Build for a core freight forwarding layer runs twelve to sixteen weeks from discovery completion. Full Mirsal 2 integration, multi-modal corridor orchestration, and rate management rollout phases in over nine to fifteen months depending on volume and corridor breadth.

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