Shopify Markets makes selling into the UAE look like a checkbox. Add the region, enable a currency, switch on a translation app, done. The store will take orders in that state, which is exactly why the problems surface later — in an accountant's email, or in a conversion rate that is inexplicably poor for a market with strong demand.
There are three things to get right, and they interact.
VAT: the display rule is the one that catches people
The UAE charges VAT at a standard rate on most goods. The part that trips up stores built for other markets is not the rate, it is the presentation: consumer-facing prices in the UAE are expected to be shown inclusive of VAT. A store that displays a tax-exclusive price and adds tax at checkout is doing something a local shopper does not expect, and it produces exactly the sticker shock at the payment step that kills conversion.
In Shopify, that means enabling tax-inclusive pricing for the market rather than leaving the store on its home-market behaviour. Check it on a real product page in the UAE context, not in the admin. It is a per-market setting and it is easy to configure the tax rate correctly while leaving the display wrong.
The second half is the invoice. A tax invoice in the UAE has content requirements — your TRN, the customer's where applicable, the tax amount stated separately, and the required identifying wording. Shopify's default order confirmation is not a tax invoice and does not become one because VAT was collected. Most stores selling seriously into the Emirates end up with an invoicing app or a small custom template, and it is far cheaper to decide that before the first quarter closes than after.
Registration thresholds are a question for your accountant rather than your developer, and the answer depends on where you are established and how much you sell into the country. Ask before you launch, not after.
AED pricing: rounding is a merchandising decision
Shopify can convert prices automatically from your base currency using live rates. Left alone, that produces prices like 273.41 AED, which read as machine output and quietly signal that the store is foreign and the price is provisional.
Two things to configure:
- Price rounding. Set it so converted prices land on a clean ending rather than wherever the exchange rate puts them. This is a single setting and it does more for perceived legitimacy than most redesigns.
- Fixed prices for your top sellers. Rather than converting, set the AED price explicitly for the products that carry your volume. It protects your margin from rate movement and lets you price to a psychological point rather than to a calculation.
Then check the whole journey in AED — product page, cart, checkout, confirmation email. Currency inconsistencies almost always appear at the boundary between Shopify and something else: an app-rendered upsell, a subscription widget, an email template with a hardcoded symbol.
Arabic is a storefront, not a toggle
This is where most stores stop short, and it is the part that separates a store that sells in the UAE from a store that merely accepts orders from it.
Arabic is right-to-left. Adding a translation without adding proper RTL support gives you Arabic words in a left-to-right layout: navigation on the wrong side, form labels misaligned, breadcrumbs running backwards, icons pointing the wrong way. It reads as broken to a native speaker even when every word is correct.
What actually needs doing:
- The theme has to support RTL — the dir attribute set on the document, and a stylesheet that mirrors layout rather than only flipping text.
- A font that renders Arabic properly at your body sizes. Many popular Latin web fonts have no Arabic coverage and the browser silently falls back to something that does not match your design.
- Translated content that includes the commercial copy — product titles, descriptions, size guides, shipping and returns policies. A store with an Arabic interface and English product descriptions has translated the furniture and not the goods.
- Checkout and transactional emails in the same language as the storefront the customer used.
Decide honestly whether you can maintain it. A half-maintained Arabic storefront that drifts out of date is worse than a well-built English one, and for some catalogues English-only is a defensible choice in a market with high English proficiency. What is not defensible is launching Arabic, letting it rot, and concluding the market does not convert.
hreflang, if you run more than one English storefront
If you serve the UAE, the UK and Australia with separate English URLs, search engines need to be told these are regional variants of the same page rather than duplicates. Shopify emits hreflang automatically for markets configured with their own domains or subfolders, and the automatic output is correct more often than not — but it is worth verifying rather than assuming, particularly the x-default and the reciprocity between variants.
Get this wrong and the symptom is subtle: the right page exists, the wrong regional version ranks, and shoppers land on a storefront quoting a currency they cannot pay in.
Payments and delivery expectations
Cards dominate in the UAE more than they do in India, but cash on delivery still matters for a meaningful slice of shoppers depending on category, and the local wallets are worth supporting. Check what your payment provider actually supports for AED settlement rather than assuming your home-market gateway covers it.
Delivery promises are held to a high standard. Next-day within the main cities is common enough that a vague "3–5 business days" reads as slow. If you can be specific by emirate, be specific.
A pre-launch checklist
- Prices display inclusive of VAT on the storefront, verified on a product page in the UAE context.
- A compliant tax invoice is generated, with TRN and the tax amount stated separately.
- Rounding configured; fixed AED prices set for top sellers.
- Currency consistent through cart, checkout and every email.
- RTL layout correct, not just translated text.
- Arabic font renders at body sizes.
- Product descriptions and policies translated, not only the interface.
- hreflang verified across your English regional storefronts.
- Payment methods and delivery promises checked against local expectation.
None of this is difficult individually. What makes it a project is that tax, pricing and language all touch the same templates, and a change to one keeps breaking the checks you already ran on another. Do them in that order, and re-verify the whole journey once at the end rather than after each change.
We build and run stores for brands across the Emirates — if you want the setup reviewed before you launch, that is what our Dubai team does, and a store audit will tell you which of the checks above your current storefront fails.