Delivery Tracking Software for Operators across the UAE

Who this is for: UAE 3PL providers running multi-carrier shipments, freight forwarders with carrier optionality (air, sea, road combinations), e-commerce fulfilment operators serving regional sellers and direct brands, cross-border courier operators (MENA-wide, GCC-specific), and specialised delivery operators (pharmacy, cold chain, high-value) where shipment visibility is a commercial differentiator. Not positioned as a single-carrier tracking app replacement — those are typically available directly from the carrier.

Six connected capability areas: (1) Carrier-agnostic tracking aggregation. (2) Customer-facing visibility layer with branded experience. (3) Multi-language customer UX. (4) Exception management workflow. (5) Analytics and performance reporting. (6) Integration with order management and customer service systems.

project44, FourKites, FarEye, EshopBox, and Convey (now part of project44) are mature global visibility platforms with significant UAE deployment. project44 and FourKites are enterprise-focused with strong carrier network depth globally. FarEye handles end-to-end logistics including dispatch. EshopBox serves e-commerce sellers with fulfilment-focused tracking.

Custom delivery tracking software is designed to sit alongside these platforms, closing UAE-specific gaps — regional carrier integration (iMile, Quiqup, Mawgs, Emirates Post) at parity with global carriers, bilingual Arabic-first customer UX with right-to-left layout, Dubai Trade and Mirsal 2 customs visibility for cross-border flows, and customer communication via WhatsApp (which UAE customers prefer over SMS for many segments). The visibility platform retains its carrier network authority; the custom layer handles UAE-specific integration and customer experience.

UAE multi-carrier operators handle shipments across Aramex (regional leader), DHL Express, FedEx, UPS, Emirates Post/EmPost, regional carriers iMile and Quiqup, and international carriers on specific lanes. Each carrier exposes tracking through its own API — different authentication (OAuth, API keys, basic auth), different rate limits, different status taxonomies (DHL uses different milestone codes from Aramex), different update cadences.

The aggregation layer maintains integration with each carrier API, normalises status codes to a unified customer-friendly taxonomy, handles rate limit management and retry logic, and preserves raw carrier events for audit. Carrier swap (where the operator chooses to route through a different carrier) preserves tracking continuity — customer sees consistent experience. New carrier addition is typically 2-4 weeks of API integration work on top of the aggregation framework.

Customer-facing tracking pages render the operator's brand rather than the carrier's — consistent with the rest of the operator's customer experience. Live ETAs are calculated from carrier events enriched with traffic, weather, and historical performance data to provide accurate expected delivery windows rather than raw carrier estimates.

Proactive delay notifications surface to customers before they ask — customs hold detected, delivery attempt failed, carrier network disruption. Delivery window choice lets customers select time slots where the operator's service permits. Self-service reschedule and address-update flows handle common exceptions without customer service involvement. Customer preferences (SMS, WhatsApp, email, in-app) are respected per customer with preference captured at first shipment.

UAE customer base spans Arabic (primary for many Emirati and GCC customers), English (common shared language), Hindi and Urdu (significant South Asian customer base), and Tagalog (Filipino customers). Tracking UX operates in all these as first-class languages.

Tracking page layout flips for Arabic right-to-left with culturally-designed content rather than literal translation. SMS, WhatsApp, and email notifications send in customer's chosen language with templates designed for each. Customer service integration routes by language preference — non-English queries don't get lost in English-language queues. Language preference preserved across sessions and channels.

Shipment exceptions happen continuously — customs hold (pending clearance at origin, transit, or destination), failed delivery attempt (customer unavailable, address issue, access blocked), damaged or missing goods, address corrections requested mid-transit, customer unavailable for signature-required delivery. Each exception type needs different handling.

The workflow structures exception types with routing rules — customs exceptions route to the customs team, failed delivery attempts route to last-mile coordinators, damaged goods route to claims team. Customer communication is templated per exception type and localised. Resolution time is tracked against SLA. Root-cause analytics surface systemic issues — which carriers have higher customs hold rates, which addresses see repeat failed deliveries, which product categories show damage patterns. Dubai Trade and Mirsal 2 customs events surface to the tracking layer where the operator or their broker has B2G access, translating customs events into friendly customer terms rather than opaque silence.

Here's where custom delivery tracking platform typically sits in a wider stack.

Core visibility platforms — we sit alongside project44, FourKites, FarEye, EshopBox, and Convey for carrier network depth and visibility authority.

Carrier integration — we integrate with Aramex, DHL Express, FedEx, UPS, Emirates Post, iMile, Quiqup, and international carriers for carrier-specific API access and event ingestion.

Order management and customer service — we connect with Shopify, Magento, WooCommerce, Oracle Commerce, and SAP Commerce for order context; Zendesk, Freshdesk, Salesforce Service Cloud, and Intercom for customer service integration.

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 customer experience, operations, and technology teams, we map current carrier integration scope, customer-facing tracking UX, multi-language support, and exception workflow. Output is a detailed report covering current-state map, platform architecture, integration scope per carrier, phased implementation plan, and fixed-price build proposal.

Build for a core delivery tracking platform runs ten to fourteen weeks from discovery completion. Full carrier aggregation, customer-facing UX, multi-language, and exception workflow rollout phases in over nine to twelve months depending on carrier count and customer segment scope.

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