Logistics and supply chain analytics for Dubai and the UAE
Logistics in the UAE runs through a small number of very large places: Jebel Ali and DP World, Dubai South and Al Maktoum airport, KIZAD and AD Ports in Abu Dhabi, SAIF Zone and Hamriyah in Sharjah. Around them sit freight forwarders, third-party logistics providers, last-mile fleets serving e-commerce and grocery, and distributors running their own warehouses and vans. Their data lives in a transport or warehouse system, a finance system, a telematics portal, a customs account and a dispatch spreadsheet, and none of those agree on what a completed job is.
A logistics dashboard is worth building only if it puts cost, service and utilisation on the same list of jobs that finance invoices. That is a modelling problem before it is a visual one, which is why this page spends most of its length on definitions and sources. Every KPI below has a formula; every system has a connection method and a catch.
The page follows the Power BI dashboards by industry UAE structure used across the site: the questions, the definitions, the systems, the calendar, a demo you can open, and how the project is priced. It is delivered remotely on GST hours, as a fixed price quoted before work starts.
The questions a logistics dashboard must answer
A useful logistics dashboard answers a short list of operational and commercial questions, and most of them need data from more than one system. The list below is what a general manager, an operations head and a finance manager in a UAE logistics business tend to ask in the same meeting.
- What does a shipment cost us, in AED, by route, customer and mode, and is it rising?
- Are we delivering on time and in full, and when we are not, which failure is it — late, or short?
- How much of the fleet is working, how much is idle, and where is the idle time — the yard, the port gate or the customer’s loading bay?
- How sensitive is our margin to the monthly UAE fuel price change, and did last month’s cost rise come from price or from driving?
- What are Salik and other tolls costing per route, and would a different route be cheaper once time is counted?
- How fast does the warehouse turn a receipt into pickable stock (dock-to-stock), and how accurate is picking?
- How much are we paying in demurrage and detention, to which lines, and why?
- How long does customs clearance take by declaration type through Dubai Trade and Mirsal 2, and how much of that is inspection?
- Which customers and lanes make money after direct cost, and which only look busy?
- What is our DSO by customer, and how much of the receivable is post-dated cheques not yet due?
KPI definitions
These are the definitions we would put in front of a logistics business on day one of a build, written so that finance and operations can argue with them before the model is built rather than after. Each carries a formula and the trap that most often makes the number wrong.
| KPI | Definition | Formula | Watch out for |
|---|---|---|---|
| Cost per shipment | All direct costs attributable to a shipment, in AED, divided by the number of shipments in the period, by route, customer and mode. | (Fuel + driver cost + tolls + third-party carrier + handling + customs fees) ÷ shipments completed | Fuel bought in a month is not fuel used on a shipment; allocate from fuel-card transactions by vehicle and date, not from the monthly invoice. |
| OTIF (on time, in full) | Share of orders delivered on the agreed date and with the full quantity, with the two failure modes reported separately. | Orders delivered on time AND in full ÷ orders due in the period | The agreed date must be the one confirmed to the customer, not the one the TMS defaulted to; if the promise date is edited after the fact, OTIF is fiction. |
| Fleet utilisation | Productive hours or loaded kilometres as a share of available hours or total kilometres, by vehicle and by day. | Loaded km ÷ total km, and productive hours ÷ (available hours − scheduled maintenance) | Idle time at a port gate or a mall loading bay is not the same as idle time in the yard; telematics can distinguish them if the geofences are set. |
| Fuel cost per kilometre | Fuel spend in AED divided by kilometres driven, by vehicle class and month, with the monthly UAE pump price carried as a separate attribute. | Fuel-card spend (AED) ÷ odometer km in the same period | UAE fuel prices change monthly; report litres per km alongside AED per km so a price change is not mistaken for a driving change. |
| Salik and toll cost per route | Toll charges attributed to a route or trip from the Salik statement, in AED, so route choice can be costed. | Sum of toll transactions matched to the trip by tag and timestamp | Salik statements are by tag, not by trip; matching needs the vehicle-to-tag register and the trip timestamps from the TMS or telematics. |
| Dock-to-stock time | Elapsed time from a vehicle arriving at the receiving dock to the goods being available to pick in the WMS. | Put-away confirmation timestamp − gate-in timestamp, median and 90th percentile | Use the median and the 90th percentile, not the average; one container held for inspection will otherwise hide a week of normal receipts. |
| Pick accuracy | Share of order lines picked with the correct item and quantity, before packing checks catch them. | 1 − (lines with a pick error ÷ lines picked) | Only counts if errors are recorded at the pack station; if the WMS overwrites the pick with the corrected quantity, the error disappears. |
| Customs clearance lead time | Elapsed time from declaration submission (Dubai Trade / Mirsal 2) to customs release, by declaration type and inspection outcome. | Release timestamp − submission timestamp, by declaration type | Separate inspected from non-inspected declarations; the mix drives the average more than the broker does. |
| Demurrage and detention cost | Charges incurred for containers held beyond free time at the port (demurrage) or outside it (detention), in AED, by shipping line and cause. | Sum of line invoices coded to demurrage or detention, matched to the container and the delay cause | The cause has to be recorded when the container is released, not reconstructed from the invoice a month later. |
| Lane margin | Revenue less cost per shipment for a defined origin–destination pair, by customer, so unprofitable lanes are visible. | Invoiced revenue for the lane − cost per shipment × shipments on the lane | Fixed costs (yard, warehouse lease) are excluded here by design; report contribution, not net profit, and say so on the page. |
Systems we typically connect
The connection method decides whether refresh is automatic, and the catch decides whether the number is right. Excel dispatch sheets are listed deliberately: in many UAE fleets they are the only record of who drove what, and pretending otherwise produces a dashboard with a hole in it.
| System | How it connects | Refresh | The catch |
|---|---|---|---|
| TMS / WMS (SAP EWM, Infor, Manhattan, Blue Yonder, Odoo Inventory, custom) | Database read access or the vendor API; custom systems usually via SQL views | Nightly, with hourly incremental for yard and dispatch tables where the source allows | Job, order and shipment IDs rarely match the finance system’s; a mapping table is built and owned in the model. |
| Telematics / GPS feeds | Vendor API or scheduled CSV export | Hourly or daily aggregates; raw pings are summarised before they reach the model | Geofences for ports, yards and customer sites must be defined before idle time means anything. |
| Customs declaration exports (Dubai Trade / Mirsal 2) | Declaration report exports to a fixed folder, read by Power Query | Daily | Exports are per declarant account; a group with several licences has several exports to combine. |
| Finance (Tally, Odoo, SAP Business One, Dynamics 365 Business Central) | ODBC via gateway (Tally), database or API (Odoo, SAP B1), OData (Business Central) | Nightly | Revenue is by invoice; cost is by shipment; the model has to hold the join, and it is usually the customer PO or the job number. |
| Fuel-card statements | Monthly CSV or portal export | Monthly, or weekly where the provider offers it | Transactions carry the card, not the vehicle; the card-to-vehicle register has to be maintained. |
| Salik statements | Portal export to a fixed folder | Monthly | By tag, not by trip; matching to trips needs timestamps from the TMS or telematics. |
| Excel dispatch sheets | Read from a fixed SharePoint folder by Power Query | Daily | Common, and usually the only record of who drove what; the sheet is kept but given a fixed structure so the query survives Monday morning edits. |
Seasonality and calendar logic
A logistics model in the UAE has to know four things about the calendar, and they are built into the date table as attributes rather than remembered by whoever reads the report.
- Ramadan: delivery windows shift towards the evening and early morning, working hours are reduced by law, and daily throughput falls while per-hour productivity often rises. A month containing Ramadan is compared with the previous year’s Ramadan month, not the same calendar month.
- Summer midday break: between 15 June and 15 September, outdoor work is paused during the midday hours. Yard and cross-dock productivity per shift drops in a way that is not a performance problem, and the model flags those days so the comparison is fair.
- Q4 retail peak: from roughly October to December, e-commerce and retail volumes rise and last-mile cost per delivery usually falls as density improves. Cost per shipment is reported alongside shipments per route so the effect is visible.
- Comparable-period toggles: every page carries a toggle between same calendar period, same Ramadan-adjusted period and same number of working days, and the page says which is selected.
Open the logistics demo
Demo built on synthetic data to show layout, KPI definitions and interaction. Not client data. Open the logistics and supply chain demo opens in this site; nothing to install and nothing to sign up for.
Interactive analytics and key metrics overview.
LogisticsAndSupplyChain Performance
Core metrics tracking
Regional Distribution
Click a bar to focus (Top 7)
Three things to look for while it is open:
- Drill from a customer’s lane margin to the shipments behind it, and note that the cost per shipment on each line is built from the same components the KPI table defines.
- Switch the comparable-period toggle from calendar month to Ramadan-adjusted and watch the OTIF comparison change.
- Filter to one entity and one emirate and see that fleet utilisation, idle time and toll cost all respect the same filter, because they sit on one model.
Multi-entity and multi-emirate
A typical group has a forwarding entity licensed in Dubai, a warehouse entity in a free zone such as KIZAD or JAFZA, and a fleet company in Sharjah, each on its own ledger and often on different systems. The model carries an entity dimension and an emirate dimension from the first day, so a lane margin can be shown for the group and for each company, intercompany charges between them are eliminated in the model rather than in a workbook, and row-level security lets each general manager see their company while the group sees all of them.
VAT treatment differs across those entities, and the model has to hold the difference without giving advice about it. Services supplied by a mainland forwarder and services supplied from a designated free zone can be treated differently; international transport has its own treatment; imports may be reverse-charged. The dashboard reports output and input VAT by entity and return period so the figures can be reconciled to each entity’s VAT return. We are not tax agents; your adviser decides the treatment, and the model reports what the ledger records under it. The Power BI consulting UAE page covers the Abu Dhabi and multi-emirate side in more depth.
How a logistics project runs
The project follows the single-department dashboard sequence described on the Power BI dashboard development Dubai page: requirements and a sketch of each page; the model, with the job-to-invoice mapping table built first because everything depends on it; a first build; a week of use by the operations and finance people who will read it; refinements; acceptance against reconciled totals; and training for a named owner. If the dispatch sheet is doing more than it should, the Excel to Power BI migration Dubai page describes how it is brought into the model without breaking Monday morning. Afterwards, the Power BI managed services UAE service keeps the gateway, the telematics feed and the monthly Salik and fuel-card loads running. Distributors whose problem is stock and margin rather than movement will find the retail analytics Dubai page closer to their shape.
Questions about logistics & supply chain analytics
What KPIs should a logistics dashboard show?
Can Power BI connect to our TMS, WMS and GPS data?
How do you handle fuel and toll cost changes?
Can drivers and operations staff see it on mobile?
Can one dashboard cover several companies and emirates?
How much does a logistics dashboard cost?
Fixed price for a logistics dashboard
Quoted before work starts against a written scope. The quote is the price.
A logistics build is quoted the same way as every other project on this site, with the scope itemising the things that drive effort in this sector.
It starts with a short discovery call, at no charge, and a look at your current reports and the systems behind them. From that we write a scope: the sources we will connect, the model we will build, the pages and visuals, the users and their security, the training and the handover.
We then quote a fixed price against that scope. The quote is the price. If we find something worse than expected inside the scope, that is our cost, not yours. If you want something outside the scope, we quote it separately before doing it, and you decide.
Payment is staged against the milestones written into the scope, so you are never paying ahead of what you have seen. Where a figure is published on this site it is a starting point rather than your quote, because the number depends on your systems; we would rather you knew how the price is built than read a "from" price as though it already applied to you.
The reporting diagnostic is a fixed AED 4,950. That is the whole amount. Nothing is added at checkout. A logistics & supply chain build is quoted rather than sold from a page: builds start at AED 15,500 and most land in the AED 15,500 to AED 62,000 range, depending on the systems joined, the state of the data and the number of entities, pages and trained users. Those figures anchor the conversation; the number in your written quote is the one you pay.
The written scope for a logistics & supply chain build itemises:
- Sources: TMS or WMS, telematics, customs exports, finance, fuel-card and Salik statements, dispatch sheets — and how each connects.
- The job-to-invoice mapping: whether a common key exists or has to be built.
- Entities and emirates covered, and the security roles.
- Pages and mobile layouts, including any driver or yard view.
- Calendar logic: Ramadan, summer break and peak-period comparisons.
Talk through your logistics & supply chain reporting
Get started — four quick questions takes about a minute and books a thirty-minute call at no charge, on GST hours.