Most e-commerce projects in Dubai fail on decisions made in the first two weeks, not on the build. The platform, the payment stack, the delivery integration and the entity you trade under are all chosen early, they all constrain each other, and by the time the design is signed off they are effectively fixed.
This is the sequence we walk clients through before any code is written — and the UAE-specific constraints that make the answers different from what a generic e-commerce guide will tell you.
1. Decide the trading entity before the platform
Whether you trade through a mainland licence or a free-zone entity changes what you can sell to whom, which payment gateways will onboard you, and how VAT is handled on your invoices. Free-zone companies face restrictions on selling directly into the mainland without a distributor or additional licensing, and payment providers assess your licence category during onboarding.
This is not a technical detail. It determines whether a gateway integration you have already built will actually go live. Confirm the entity and licence category first, and get written confirmation from your payment provider that your category is eligible before it goes into the build plan.
2. Platform: the real question is catalogue complexity
The platform argument usually gets framed as hosted versus self-hosted. The better frame is how complex your catalogue and pricing rules are.
Hosted commerce (Shopify and equivalents)
Right when you have a conventional catalogue, standard variants, and a need to launch this quarter. You get PCI scope handled, a maintained checkout, and an app ecosystem that covers most local integrations. The constraint is the checkout itself: deep customisation of the payment step is limited, and some local gateway and cash-on-delivery workflows sit awkwardly inside it.
Open-source commerce (WooCommerce, Magento and equivalents)
Right when you need control over pricing logic, B2B account pricing, multi-warehouse stock, or a checkout that has to behave differently for different customer types. You take on hosting, security and upgrade responsibility in exchange. Budget for it explicitly — an unmaintained open-source store is the single most common source of compromised customer data we see.
Headless or custom
Right when commerce is one surface of a larger product, when you are selling through several channels that must share one inventory truth, or when the buying experience itself is the differentiator. It is the most expensive option and the correct one less often than vendors suggest.
3. Payments: plan for three methods, not one
UAE shoppers do not all pay the same way, and a checkout built around cards alone leaves conversion on the table. Plan the build for at least three paths:
- Cards through a locally acquiring gateway. Local acquiring matters — it affects approval rates and settlement currency.
- Cash on delivery, which remains meaningful in the region and is a genuine engineering requirement, not a toggle. It changes your order state machine, your reconciliation, your returns handling and your fraud exposure.
- Buy-now-pay-later and digital wallets, which carry real share among younger buyers and are usually a straightforward integration if planned for up front.
Also settle currency display early. Showing AED while settling in another currency creates reconciliation work and refund disputes that are tedious to unwind later.
4. Delivery and address data
UAE addressing does not follow the postal-code model most checkout forms are designed around. A form that requires a postcode and a street number will cost you orders. Build the address step around emirate, area, building and landmark, with a map pin where you can — couriers route on the pin far more reliably than on the text.
On the fulfilment side, decide early whether you are integrating a courier's API for label generation and tracking or handling it manually. Manual is fine at low volume and becomes the bottleneck faster than teams expect.
5. Arabic is a layout decision, not a translation task
If Arabic is on the roadmap at all, build right-to-left support from the first sprint. Retrofitting RTL into a design system that assumed left-to-right touches every component — icon direction, input alignment, carousels, progress indicators, breadcrumbs — and costs several times what it would have cost to do at the start.
Plan for genuinely bilingual product data too: titles, descriptions, attributes and category names all need a second field and an editorial process to keep them in sync.
6. Data residency and privacy
The UAE has federal personal data protection legislation, and sector-specific rules apply in some free zones. Know before you choose hosting where customer records will physically sit, what your provider commits to contractually, and how you would respond to a data subject request. For most retail catalogues this is straightforward; for anything touching health, finance or government customers it drives the hosting decision outright.
7. What the build actually contains
Storefront design is the visible part and usually the smaller half of the work. A realistic scope also includes:
- Product data import and normalisation from whatever you have today
- Inventory sync with your existing system of record, and what happens when it fails
- The order state machine, including cash-on-delivery and partial returns
- Tax configuration and compliant invoice generation
- Analytics and consent handling that survives tracking restrictions
- Staging, backups, and a restore you have tested
If a proposal prices the storefront and treats the rest as "integration to be confirmed", the number you are looking at is not the number you will pay. Our guide to estimating development costs covers how to scope this internally before you request quotes.
8. Launch is when SEO starts, not when it ends
Replatforming without a redirect map is the most reliable way to lose the organic traffic you already had. Before launch, export every indexed URL, map it to its destination, and keep the map in version control. Category and product URLs, filtered views, and old campaign landing pages all need a decision.
After launch, the ranking work is structural: unique category copy, product schema, fast rendering on a mid-range phone on mobile data, and internal links from content to commercial pages.
A sensible starting point
For most first e-commerce builds in Dubai: a hosted platform, one locally acquiring gateway plus cash on delivery, an address form designed for UAE addressing, RTL support scaffolded from day one, and a deliberate plan to revisit the platform once you know what your catalogue and margins actually look like in production.
See how we deliver e-commerce development in Dubai, or read our guide to choosing a software development partner in Dubai.