RTRoutetrack Tech
Guides › Warehouse & WMS

Warehouse Management Systems in the UAE: Free Zones, Bonded Stock, Customs and Costs

A warehouse management system in the UAE has to track stock across mainland, free-zone and bonded regimes. Here's what each regime demands from the software, how customs and VAT links work, and the costs and go-live timelines to plan for.

Routetrack Tech editorial team · November 2026 · 12 min read

Your UAE warehouse regime decides what the WMS must do

Before you shortlist vendors, settle one question: which customs and tax regime does each square meter of your warehouse sit under? A warehouse management system in the UAE that works fine for a mainland Dubai distribution center can fail an audit in a JAFZA, KEZAD or SAIF Zone facility. Free-zone and bonded stock carries a legal status the system has to track, and a mainland WMS has no reason to. The software is mostly the same. The data model, the customs links and the reconciliation reports are what differ.

The UAE has dozens of free zones, and customs is administered at emirate level. Dubai Customs, Abu Dhabi Customs (through the ATLP platform), Sharjah Customs and the federal authorities all work within the GCC Common Customs Law, but each has its own procedures and systems. In practice you're running one of three operating models, and plenty of companies run two or more at once.

Advertisement
RegimeCustoms status of stockWhat the WMS must addTypical audit pressure
Mainland warehouseDuty paid on import (the standard GCC rate is 5% of CIF value, with exceptions by product)Standard WMS, VAT-ready invoicing links, Arabic labeling for consumer goodsLow to moderate; mostly VAT and product compliance
Free-zone warehouseOutside the customs territory; duty arises when goods enter the mainlandStock status by inbound declaration, free-zone-to-mainland and zone-to-zone movements, re-export tracking, Designated Zone VAT logic where it appliesModerate to high; free-zone authority and customs stock audits
Bonded (customs) warehouse, mainland or zoneDuty suspended until ex-warehousing for local use, or waived on re-exportLine-level declaration references, partial drawdown against declarations, storage-period alerts, customs-format reconciliationHigh; licensed facility, financial guarantee and periodic reconciliation

Our position: if a meaningful share of your volume, say a fifth or more, is re-export or duty-suspended, make customs-status tracking a must-have inside the WMS itself. Don't plan to rebuild it in spreadsheets or the ERP. Spreadsheet reconciliation breaks down fast once partial drawdowns and value-added services enter the picture, and that's where penalties and guarantee disputes start.

Tracking duty-suspended and free-zone stock at declaration level

Most WMS platforms track inventory by SKU, lot, serial number, location and owner. Bonded warehouse software adds another dimension: the customs status of each unit and the declaration that brought it in. Without that, you can't show an auditor which pallet of a fast-moving SKU arrived under which bill of entry, or how much duty is still suspended.

Data the system has to hold

  • Customs status per stock unit: duty suspended, duty paid, in transit, temporary admission, or free-zone (non-mainland) stock. The same SKU will often sit in several statuses at once.
  • Inbound declaration number at line level, with declared quantity, HS code, origin, CIF value and currency, stored against the receipt and carried through every putaway and move.
  • Partial drawdown: when 40 of 400 cartons leave for the mainland, the system should reduce that declaration's balance and link the outbound declaration to it.
  • Allocation rules by declaration, usually FIFO by declaration date, so the oldest suspended stock moves first and storage-period limits aren't breached.
  • Status-changing events such as relabeling, kitting, repacking or light assembly. Value-added services can change the HS classification or quantity units, so the system must record input-to-output conversion ratios.
  • Exceptions: damages, destruction under customs supervision, samples and count variances, each with an approval trail.

A hypothetical worked example

Say an electronics distributor holds stock in a Jebel Ali free-zone warehouse. It re-exports most of its volume to Saudi Arabia, Oman and East Africa and sells the rest into the Dubai mainland. One inbound container of 1,200 laptops is split three ways over six weeks: 500 units re-exported to Riyadh, 300 to Nairobi, and 400 moved to the mainland in four lots, each needing an import declaration and duty payment. The WMS has to show at any moment that 1,200 received equals 800 re-exported, plus whatever has gone to the mainland, plus what remains on hand. Every figure must tie to a declaration number. If the system only knows "laptops, 400 on hand," finance ends up rebuilding that ledger by hand every month.

Red flags in vendor demos

  • Customs references stored only in a free-text field on the receipt header, not on the line or the stock unit.
  • No report that reconciles opening balance, receipts, dispatches and closing balance per declaration.
  • A "customs module" built for one EU or US regime and described as "configurable" for the UAE, with no live UAE reference sites.
  • Stock status changes that can be made without a reason code or user audit trail.

Linking the WMS to UAE customs systems and brokers

Customs integration is where UAE projects slip. Each emirate runs its own platform. Dubai uses Mirsal, reached through Dubai Trade. Abu Dhabi uses ATLP. Sharjah and the northern emirates have their own channels. Free-zone authorities often run separate portals for gate passes and stock movements, and these are distinct from customs declarations.

You have three realistic integration patterns:

  1. Through a licensed customs broker. The WMS sends a structured file or API message (shipment, lines, HS codes, values, origin) to the broker's system, which files the declaration and returns the declaration number. This is the most common route for mid-sized operators and the fastest to stand up.
  2. Through a regional trade-compliance middleware layer that already connects to several emirate platforms. It costs more, but it pays off if you run sites in more than one emirate or across the GCC.
  3. Direct connection to the customs platform where it offers system-to-system interfaces to registered traders. You get the most control and the most ongoing maintenance, so it usually only pays off at high declaration volumes.

Whichever you choose, the integration has to be two-way. The WMS sends draft declaration data and receives the approved declaration number, status and any customs holds. Stock shouldn't be released for dispatch until approval comes back. Ask vendors to show this hold-and-release step running, not just a file export.

For most single-emirate operators with moderate declaration volumes, the broker route is the better fit because you avoid owning the interface and your broker already absorbs platform changes. Make sure the contract states who owns the data mapping and who fixes it when a platform update breaks it.

VAT designated zones, e-invoicing and the tax records your WMS feeds

Free-zone inventory compliance isn't only about customs. The UAE charges VAT at 5%, and a subset of free zones is listed by Cabinet Decision as Designated Zones. Not every free zone is on that list. Within a Designated Zone, certain supplies of goods can be treated as outside the scope of UAE VAT, but only if the zone and the business meet conditions, including keeping internal procedures and records on how goods are stored and moved. Goods leaving a Designated Zone for the mainland are generally treated as an import, with VAT accounted for at that point.

That puts specific demands on the WMS:

  • Each location and site record should carry a flag for Designated Zone status, and the flag should flow into the ERP's tax determination.
  • Movements between a Designated Zone, a non-designated free zone and the mainland need distinct transaction types. Don't record them as generic transfers.
  • Keep records of physical goods movement for at least the general UAE tax record-retention period, which is typically five years. Customs may set its own requirements, so confirm both.

Two other obligations raise the stakes. First, the UAE is introducing mandatory structured e-invoicing in phases, with larger businesses first. The WMS doesn't issue tax invoices, but its shipment and delivery data feeds the ERP invoices that will be reported, so mismatches between dispatched and invoiced quantities will surface sooner. Check the current timetable for your business size. Second, free-zone entities seeking Qualifying Free Zone Person treatment under the UAE corporate tax regime (9% on non-qualifying income) must show their income comes from qualifying activities and transactions. Movement records showing goods stayed within or moved between designated zones can support that analysis.

These rules are detailed and still being refined. Have a UAE-registered tax adviser confirm your Designated Zone status, the VAT treatment of each movement type and your e-invoicing phase before you finalize the WMS transaction design. Changing that design after go-live costs far more.

PDPL, data residency and Arabic labeling requirements

Personal data in the warehouse

A WMS holds more personal data than buyers expect: operator logins and productivity records, driver names and vehicle plates at the gate, CCTV-linked dock events, and consignee names, phone numbers and addresses for e-commerce fulfillment. Onshore UAE businesses fall under the federal Personal Data Protection Law (Federal Decree-Law No. 45 of 2021). Some free zones, notably DIFC and ADGM, have their own separate data protection regimes. Global operators should map how these interact with GDPR for European customers, India's DPDP Act, or Saudi Arabia's PDPL if they serve KSA from a UAE hub.

Put these in the RFP:

  • Role-based access to consignee and employee data, with field-level masking for temporary and agency staff.
  • Configurable retention and purge rules for consignee addresses and labor-tracking data.
  • A documented list of the vendor's hosting regions and sub-processors. Microsoft, Oracle and AWS all offer UAE cloud regions, and several WMS vendors can host there on request, sometimes at a premium.
  • A data processing agreement that covers cross-border transfers and breach notification.

Implementing regulations under the federal PDPL have developed slowly, so ask counsel to confirm current requirements. In-country hosting isn't always legally required for private-sector logistics data, though government-linked customers, healthcare and some regulated sectors often demand it by contract.

Arabic and bilingual labeling

Food, cosmetics and many consumer products sold on the mainland must carry Arabic labeling under UAE and GCC standards, enforced by federal bodies such as the Ministry of Industry and Advanced Technology and by emirate municipalities. Re-export stock bound for other GCC markets often has similar needs. Many free-zone warehouses apply Arabic stickers as a value-added service before goods cross to the mainland.

Test this in the demo, not after signing. The label engine must render right-to-left Arabic with correct letter joining on your actual thermal printers. It should merge bilingual fields (product name, ingredients, importer details, origin, correctly formatted expiry dates) from item master data and log which units were relabeled against which declaration. Garbled Arabic on a Zebra or Honeywell printer is a common, avoidable go-live failure.

Indicative costs, go-live timelines and how to shortlist

Most international WMS vendors sell into the UAE, usually through regional partners: SAP EWM, Oracle WMS Cloud, Manhattan Active Warehouse Management, Blue Yonder, Infor, Körber and Microsoft Dynamics 365 Supply Chain Management. Odoo's inventory app is a common mid-market choice through a large local partner network. Customs-status tracking is often delivered as a partner extension rather than an out-of-the-box feature, so evaluate the partner as carefully as the product.

The ranges below are typical 2026 market figures for a single site. They vary widely by contract, user count, automation and partner rates, so confirm them with vendors.

Cost itemMid-market (1 site, 15–40 users)Enterprise (multi-site or automated)
WMS subscription per yearUSD 25,000–90,000USD 120,000–400,000+
Core implementation and configurationUSD 40,000–150,000USD 200,000–800,000
Customs and bonded-stock extensionUSD 15,000–60,000USD 50,000–200,000
Broker or customs platform integrationUSD 10,000–40,000USD 40,000–150,000
Arabic label templates and printer setupUSD 3,000–15,000USD 10,000–40,000
In-country hosting premium (if required)0–15% of subscription0–20% of subscription

The main cost drivers are how many customs statuses and movement types you run, how many emirates and free zones you file in, whether VAS changes the HS classification, and how much data you must migrate from legacy bonded registers.

ScenarioTypical go-liveWhat usually sets the pace
Mainland site, standard WMS3–5 monthsERP integration and label testing
Free-zone site with re-export and mainland sales5–7 monthsDeclaration-level data model and broker integration
Bonded warehouse with customs integration7–11 monthsCustoms reconciliation sign-off and opening-balance migration
Multi-emirate or GCC hub rollout9–15 monthsMultiple customs platforms and tax-design approvals

Plan cutover for a quiet period, after a full stock count reconciled to your open declarations. Starting a bonded operation on a new system with unreconciled balances means carrying the variance into every audit afterward.

Next step: send your three shortlisted vendors one scripted scenario. Receive a container under a single declaration, split it into re-export, mainland import and a relabeled VAS lot, then produce the declaration-level reconciliation and a bilingual label. A vendor that can't run that script live with a UAE partner should come off the list, however strong the rest of the demo looks.

Quick answers

Does a free-zone warehouse in the UAE need a different WMS from a mainland one?

Usually it's the same product configured differently. A free-zone or bonded site needs customs-status tracking, declaration references at line level and movement types for zone-to-mainland and re-export flows. A mainland-only site generally doesn't. Confirm the vendor or its UAE partner has live free-zone references before you buy.

Can the WMS file customs declarations directly with Dubai Customs or Abu Dhabi?

Some setups connect directly to emirate platforms such as Mirsal in Dubai or ATLP in Abu Dhabi. Most mid-sized operators instead send structured data to a licensed customs broker, who files the declaration and returns the number. Direct connection makes sense mainly at high declaration volumes or for multi-emirate operators with in-house IT capacity.

Is every UAE free zone a VAT Designated Zone?

No. Designated Zones are a specific list set by Cabinet Decision, and the special VAT treatment also depends on the business meeting conditions on controls and record-keeping. Your WMS should flag designated locations separately. A UAE tax adviser should confirm your status and the VAT treatment of each movement.

Do we have to host WMS data inside the UAE?

Not always. The federal PDPL governs how personal data is processed and transferred, but in-country hosting is often a contractual requirement from government-linked, healthcare or regulated customers rather than a blanket legal rule for logistics data. Major cloud providers have UAE regions, so ask vendors whether they can host there and what it costs. Get counsel to confirm current rules.

How long does a bonded warehouse WMS implementation take in the UAE?

Plan on roughly 7 to 11 months for a single bonded site with customs integration, compared with 3 to 5 months for a standard mainland site. The slowest steps are usually reconciling opening balances against open declarations and getting sign-off on customs reconciliation reports. Multi-emirate rollouts take longer.

What should we test for Arabic labeling before signing?

Print real bilingual labels from your own item data on your own thermal printers during the demo. Check right-to-left rendering, letter joining, date formats and importer details. Also confirm the system logs which units were relabeled and links them to the relevant declaration.

Written by the Routetrack Tech editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.