Transport Management System for Shippers across the UAE

Who this is for: UAE shippers, 3PL providers, and contract logistics operators managing 50+ daily shipments or handling regular GCC cross-border operations. Not positioned as a sub-20-vehicle dispatch app — those are well-served by off-the-shelf dispatch apps; custom TMS software is for operations where federation-wide integration depth and multi-modal scope justify bespoke build.

Six connected capability areas: (1) Salik and Darb-aware route optimisation with planning-time toll pricing. (2) WPS and MoHRE-aware dispatch with driver availability from labour compliance. (3) Mirsal 2 and AD Customs outbound integration. (4) Multi-modal lane modelling including Etihad Rail freight. (5) Carrier tendering with contract and spot rate management. (6) Emissions and Net Zero 2050 reporting from operational data.

Oracle Transportation Management, SAP Transportation Management, Blue Yonder TMS, MercuryGate, and Descartes are mature global TMS platforms with significant UAE deployment. These handle core transport operations, carrier integration, and cross-region visibility at scale.

Custom TMS software is designed to sit alongside these platforms, closing UAE-specific gaps — Salik and Darb toll integration at planning level, WPS and MoHRE labour compliance at dispatch level, Mirsal 2 export declaration workflow native, Etihad Rail freight corridor as lane alternative, and UAE Net Zero 2050 emissions reporting built on operational data. The global platform retains carrier integration and financial authority; the custom layer handles UAE federation-specific depth.

Salik (Dubai) and Darb (Abu Dhabi) toll gantries impose per-passage charges that materially affect route cost economics. A route optimisation engine that models only fuel, time, and distance systematically undervalues alternative routes that avoid gantries for equivalent or near-equivalent transit time.

The route optimisation layer integrates Salik and Darb gantry locations and tariff structures into the cost function. Route alternatives evaluated on fuel + time + toll + operational cost. Client chargeback priced at planning time rather than reconciled retroactively against Salik and Darb statements. Cross-emirate routing respects toll structure differences, particularly where Dubai-Abu Dhabi routing has multiple gantry-count options. Typical outcome is a material reduction in toll cost at route level for operators where tolls represent a meaningful cost line.

UAE Wage Protection System requires monthly salary transfers via approved banking channels — UAE Central Bank-regulated with specific timing and approved banks. MoHRE labour compliance spans visa validity, Emirates ID currency, and labour contract status. Driver licence class from RTA or respective emirate authority sits alongside these compliance layers.

The dispatch layer ingests WPS status monthly from approved banking integration, MoHRE visa and Emirates ID status, RTA licence class and expiry, MoI violation patterns, and leave or medical status. Dispatch decisions surface these factors — a driver with a WPS issue, expiring licence, or invalid visa is surfaced or blocked rather than dispatched with exposure. Driver availability planning reflects the labour reality continuously rather than per-shift lookup.

UAE outbound shipments to Oman, Saudi Arabia, or deep export require Mirsal 2 export declarations (Dubai Customs) or AD Customs equivalents. GCC cross-border transit requires additional documentation — Saudi SABER registration for product-regulated goods, Oman customs transit declarations, hazmat documentation.

The outbound integration drives Mirsal 2 and AD Customs declarations directly from shipment data. GCC cross-border transit documentation generated from the same data set. Return cargo documentation handled for empty or laden backhaul. Pre-arrival declaration used where appropriate. Saudi SABER and similar product-regulation workflows supported for relevant commodity classes.

Etihad Rail Phase 2 is operational across Mussafah-Fujairah with the bonded Khalifa-Fujairah corridor piloting through late 2025. Rail freight offers different cost, duration, capacity, and emissions profile vs road freight — particularly for Abu Dhabi to Fujairah movements where port-pair or fuel distribution runs are relevant.

The lane modelling layer treats rail as modal alternative alongside road, sea-road combined, and air. Modal choice per shipment optimised on cost, duration, reliability, and emissions. Intermodal handoff points (Khalifa Port, Fujairah rail terminal) modelled with customs documentation continuity. As the bonded corridor matures through 2026, the lane modelling updates without operator intervention.

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

Global TMS platforms — we sit alongside Oracle OTM, SAP Transportation Management, Blue Yonder TMS, MercuryGate, and Descartes for carrier integration and financial authority.

Fleet telematics — we integrate with Samsara, Geotab, Trimble, Motive, Fleet Complete, and regional providers Trakom and Mozone for vehicle telematics and driver behaviour data.

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

WMS and warehouse — we connect with Manhattan WMS, Blue Yonder WMS, Oracle WMS, SAP EWM, and Körber for inventory and location authority.

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 planning posture, WPS and MoHRE integration, Mirsal 2 outbound workflow, and modal mix. Output is a detailed report covering current-state map, platform architecture, integration scope per authority and carrier, phased implementation plan, and fixed-price build proposal.

Build for a core TMS layer runs twelve to sixteen weeks from discovery completion. Full Salik/Darb integration, WPS-aware dispatch, Mirsal 2 outbound, and multi-modal lane modelling rollout phases in over nine to fifteen months depending on shipment volume and corridor breadth.

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