Industries · Logistics & Supply Chain

Logistics AI built for UAE and GCC operators.

Last-mile, network planning, customs-risk scoring, demand forecasting and port-yard optimisation — integrated with your TMS, WMS, POS and customs declaration systems. Measured cost-to-serve and dwell-time reductions inside one operating quarter.

Request a lane back-testWhatsApp the teamDownload the GCC Cross-Border Playbook

Cross-border. Multi-modal. Integrated with your TMS, WMS and customs system.

GCC trade corridor map with last-mile and port-yard overlays for UAE to KSA flows

Lane · UAE-KSA · Saih Shuaib → Batha

3 vehicles · ETA tightened

Live

Berth seq.

Updated

Eid forecast

Band ±5%

Customs

Green

Last-mile re-routed on E11 / E311 / E611 toward Saih Shuaib. Berth-sequence advisory accepted by the yard planner. Eid demand band tightened.

11%
Cost-per-drop reduction across a 1,600-vehicle last-mile fleet
14 pp
Cross-border UAE-KSA demand-plan MAPE improvement on Ramadan-Eid
38%
Red-channel false-positive reduction at a GCC customs authority
7%
Equipment-move reduction on a Navis N4-integrated yard sequence

The problem on the table

The routing engine has not been retrained in 14 months.

The demand plan for the cross-border KSA lane keeps missing the Eid spike. The customs risk-scoring model produces too many red-channel diversions that block legitimate trade. The new yard-optimisation pilot at the port still has not connected to Navis N4 in production. The CFO is watching cost-per-shipment quarter on quarter.

Cross-border data

Every customs authority has a different API.

Mirsal 2, FASAH, Bayan, Asyad eClearance, Bahrain ofoq and Hukoomi customs each speak their own language. Without a unified corridor data layer the model dies in the integration phase.

TMS lock-in

Vendor-bundled AI is locked to the parent platform.

Operators with mixed TMS, WMS and POS inheritance cannot rely on a single supplier's AI. Brocode is portable across Blue Yonder, SAP TM, Manhattan, Oracle TMS, Korber and Navis.

Peak-season volatility

Ramadan, Eid and Hajj break standard demand models.

Generic seasonality does not capture Hijri-calendar effects, payday cycles or the cross-border pre-Hajj wave. The Brocode demand stack is built for it.

Use-case map

Nine concrete AI use cases the operations COO recognises.

Across last-mile, network planning, customs, port-yard and cold-chain. Each panel is in production with a GCC operator.

Last-mile vehicle routing

Time-window, capacity, driver-shift and Friday-prayer constraints encoded into the solver. Real-time re-routing on HERE, Google Maps or Mapbox; connectors to Onfleet, Bringg and Locus. Live ETA models tuned to UAE traffic by emirate.

Demand & network planning

Hierarchical demand models keyed to Ramadan, Eid, Hajj, DSF/DSS and school terms, with cross-border lane awareness for UAE-KSA, UAE-Oman, UAE-Qatar and GCC Customs Union flows. The planner uses it every Sunday morning.

Customs risk scoring

Entity-and-shipment risk models on Mirsal 2 (Dubai), FASAH and Bayan (KSA). WCO SAFE-aligned, AEO-aware. Cuts red-channel false positives while preserving the SAR-equivalent compliance signal.

Port yard & berth sequencing

Navis N4 and CATOS coexistence via the TOS Adapter layer. Berth-and-yard sequence models, equipment-pool deployment, with a documented sub-second latency target for live decisions.

Cold-chain exception models

IoT-fused exception detection on Roambee, Tive and Sensitech telemetry; regulator-aware temperature deviation reporting for pharma, fresh and dairy lanes.

Container damage & gate OCR

Computer vision at the gate for container number OCR, IMO seal recognition and damage classification. Reduces manual gate-in / gate-out paperwork on Jebel Ali and Khalifa Port flows.

Document intelligence on customs

Bilingual Arabic-English extraction across bills of lading, commercial invoices, certificates of origin and PEL declarations. Cuts manual rekey across Mirsal 2 and the FTA reporting layer.

Driver and equipment dispatch

Driver-and-tractor pairing optimisation across the yard and the over-the-road network. Considers HSE windows, training currency and the maintenance cycle.

Customer-service shipment copilot

Multilingual shipment status summarisation across TMS, WMS and POS for the call-centre desk. Reduces inbound queries on tracking and ETA without retraining the agent.

Integration mechanism

Built to live inside the logistics estate you already run.

Named connectors across the TMS, WMS, POS and customs systems. The TOS Adapter pattern for Navis N4. A unified GCC trade-corridor feature store. Procurement gets the integration map on the first call.

TMS / WMS
Named connectors for Blue Yonder TMS & WMS, SAP TM, SAP EWM, Manhattan Active, Oracle TMS and Korber WMS. Coexistence with the supplier's AI modules where they are already paid for.
Port operating systems
Navis N4 and CATOS via the TOS Adapter pattern. Berth, yard and equipment-pool signals on a documented latency budget.
Customs estate
Mirsal 2 (Dubai), FASAH and Bayan (KSA), Asyad eClearance (Oman), Bahrain ofoq, Hukoomi customs (Qatar). AEO and WCO SAFE-aware risk treatment.
Routing & maps
HERE Maps, Google Maps Platform and Mapbox; live ETA models tuned to UAE traffic patterns by emirate and time-of-day.
IoT & telemetry
Roambee, Tive and Sensitech for cold-chain; vehicle telematics from major fleets; container reefer-status feeds.
GCC trade-corridor data
Unified feature store covering UAE, KSA, Oman, Qatar, Bahrain and Kuwait trade calendars and customs documentation differences.

Customs & standards

Anchored to the customs authorities and trade frameworks that decide your dwell time.

Dubai Customs & Mirsal 2

Direct integration into Mirsal 2 declarations with documented data-handling for trade-sensitive fields and an audit trail customs can inspect.

KSA — FASAH, Bayan, ZATCA

FASAH manifest, Bayan declaration and ZATCA invoice fields handled. AEO-aware risk treatment that respects Saudi Customs operating practice.

WCO SAFE & AEO

Risk-scoring models built to the WCO SAFE framework with explicit handling for Authorised Economic Operator status across the GCC.

UAE PDPL & data residency

Trade and customer data stays inside the country. Named DPO point of contact aligned to UAE Federal Decree-Law 45.

Reference engagements

Four anonymised cases across last-mile, customs, network plan and port.

All numbers are signed off by the engagement lead and verified against the operator's own reporting before publish.

“Last-mile fleet of 1,600 vehicles. Cost-per-drop down 11 percent. On-time-in-full up 4 percentage points. The dispatcher kept the desk; the routing model retrained weekly.”
UAE express operator — last-mile
“Cross-border UAE-KSA demand-plan MAPE improved by 14 percentage points on the Ramadan-Eid window. The planner kept Sunday morning; the model handles the lane mix.”
Regional integrator — cross-border demand
“Customs risk-scoring reduced red-channel false positives by 38 percent with no measurable drop on confirmed non-compliance, validated by the authority's own audit team.”
GCC customs authority — risk scoring
“Navis N4-integrated yard sequence model on a flagship UAE container terminal cut equipment moves by 7 percent. The TOS supplier was kept in the loop on the integration pattern.”
UAE port operator — Navis N4 yard

Vs the alternatives on your shortlist

Platform plays, TMS-bundled AI, Big-4 supply-chain practices or in-house build.

A senior COO has usually been offered all four. The comparison reflects the first-call brief our engagement leads hear.

Capability	Platform plays (Maersk / Flexport)	Vendor-bundled (Blue Yonder / SAP)	Big-4 supply-chain
Mirsal 2 / FASAH / Bayan native integration			Within own platform
Navis N4 coexistence via TOS Adapter		OEM-locked	Limited
Portable across mixed TMS / WMS estates	Platform-locked	Locked to TMS supplier	Customer-defined
GCC calendar-aware demand (Ramadan / Eid / Hajj / DSF)	Generic seasonal	Generic seasonal	Generic seasonal
AEO-aware customs risk treatment			Limited
UAE-resident engineers named on the SoW	Mixed	Mixed	Offshore-led
Running models the planner uses every Sunday	Dashboards	Platform output	Network-design study

Compared with Maersk Flow / Flexport-style platforms; Blue Yonder, SAP IBP, Manhattan Active AI modules; Accenture SCM, Deloitte SCO, EY SC, KPMG.

Free download

GCC Cross-Border Logistics AI Playbook

30-page reference covering the UAE-KSA-Oman-Qatar trade corridors, the Ramadan/Eid/Hajj demand cycles, customs-authority API and documentation differences (Mirsal 2, FASAH, Bayan, Asyad eClearance, Bahrain ofoq) and the AEO-aware risk-scoring pattern.

Ramadan / Eid / Hajj demand-cycle calibration
Mirsal 2 / FASAH / Bayan / Asyad eClearance API mapping
AEO-aware customs risk-scoring pattern
Navis N4 TOS Adapter coexistence pattern
Worked example: tier-1 3PL across three GCC lanes
Sample tender response and SoW template

FAQ

The questions a COO asks before the second meeting.

If something is missing here, message us on WhatsApp or send it via the form below.

The vendor-bundled AI is locked to the parent platform and tuned to a global pattern. Brocode is portable across mixed TMS, WMS and POS estates and writes models that account for GCC calendar effects (Ramadan, Eid, Hajj, DSF) and the specific customs systems your shipments hit. We coexist with the vendor module rather than duplicating it, and we document the coexistence pattern in writing.

Talk to the engagement lead

Tell us about the lane, the fleet or the terminal you want back-tested.

Six short questions, then a senior logistics engineer responds within one business day with a scoped back-test outline.

Prefer to chat?

Many operators ping the team on WhatsApp first. The message is pre-filled with the use case so you do not type the brief twice.

Continue on WhatsApp

Continue exploring