E-commerce Website Launch Checklist for Dubai and the UAE

An online store in Dubai is ready to launch when four things are true: it meets the UAE’s consumer rules for e-commerce, money moves correctly from checkout to your bank, a customer on a phone can find a product and pay without friction, and you can measure every order. Everything else on this checklist supports one of those four. Work through it in order, because the legal and payment items take the longest to fix late.

In short

• Put your licensing details, Arabic product information and Arabic invoices in place before launch.
• Test every payment method with real transactions, including refunds and failed payments.
• Publish clear shipping, returns and warranty pages and link them from checkout.
• Walk through checkout on real phones in both Arabic and English.
• Add Product structured data, connect Google Merchant Center and verify purchase tracking.
• Load test the live setup well before White Friday or Dubai Shopping Festival campaigns.

Legal and tax basics for a UAE online store

This is the part most store owners leave to the week before launch, and it is the part that can force changes to templates, invoices and product data. Settle it first.

What consumer protection law expects from online sellers

The UAE Government portal’s consumer protection page explains that the Consumer Protection Law, Federal Law No. 15 of 2020 as amended by Federal Decree Law No. 5 of 2023, covers goods and services sold across the mainland and free zones, and goods sold through e-commerce platforms registered in the UAE. It does not cover sales between customers in the UAE and e-commerce businesses registered outside the UAE.

For a store registered here, the same page lists what online businesses must provide: details about their licensing entity, and information in Arabic about the product or service, its specifications, the terms of contract, payment and warranty. It also says suppliers must give a dated invoice showing the trade name, address, type of goods, price and quantity, and that the invoice must be in Arabic, with any other language optional.

In practical terms, that turns into a short list of build tasks:

• A footer or About page that names your trade licence and the authority that issued it.
• Arabic product titles, descriptions and specifications, not only an Arabic menu.
• Terms of sale, payment terms and warranty terms available in Arabic.
• Order confirmation emails and invoices generated in Arabic, with English alongside if you want it.

VAT on prices, checkout and invoices

The UAE Ministry of Finance states that VAT was introduced on 1 January 2018 at a standard rate of 5%. Article 3 of Federal Decree Law No. 8 of 2017, published by the Federal Tax Authority, sets that standard rate, and Article 65 requires a registrant making a taxable supply to issue a tax invoice, with the Executive Regulation specifying the data it must contain and the conditions for electronic tax invoices.

For the store itself, check that prices display consistently (inclusive or exclusive, never a mix), that the tax line on the cart matches the tax line on the invoice, that shipping is taxed the way your accountant expects, and that credit notes are produced when you refund. Ask your tax adviser to review a sample invoice from the staging site before launch, not after the first quarter’s return.

Your licence and the e-commerce law

The UAE Government portal’s digital invoicing page notes that Federal Decree Law No. 14 of 2023 concerning modern technology based trade requires digital traders to give customers detailed digital invoices, and that the VAT law recognises tax invoices in written or electronic form. Make sure your licence activity covers online selling before you take the first order.

The legal and tax points above are a summary of official UAE Government sources as of September 2026. They are indicative and are not legal or tax advice.

Payments: card gateways, buy now pay later and cash on delivery

Payment problems are the most expensive launch bugs, because they fail quietly. A customer who sees an error rarely emails you; they buy somewhere else.

Card gateways

Choose a gateway that supports the currencies and card types your customers use, settles to your UAE bank account, and handles 3D Secure authentication without breaking the mobile flow. Then test more than the happy path. A good test set covers a successful payment, a declined card, an abandoned authentication step, a payment that succeeds at the gateway but fails to update the order, and a full and partial refund. That fourth case matters most: if the gateway’s callback to your store fails, you have taken money for an order your system thinks is unpaid.

Buy now pay later

Instalment providers now sit alongside card payments at many UAE checkouts. If you add one, check three things: the provider’s messaging appears on product pages only where the price qualifies, returns and partial refunds flow back to the provider correctly, and the extra payment step still works inside the in app browsers of Instagram and TikTok, where a lot of mobile traffic lands.

Cash on delivery

Cash on delivery still widens the audience for many UAE stores, but it changes your operations. Decide before launch how you will confirm orders, whether you cap order values, how your courier remits cash, and how refused deliveries return to stock. Tag these orders separately in your store and in analytics, so you can compare their completion rate with prepaid orders after a few months.

Test the payment that fails, not only the one that works. The failed callback is where stores lose money without noticing.

Arabic and English product content

A bilingual store is two stores that share one database. Each language needs its own product titles, descriptions, category names, filters, size guides, error messages and emails. The checks that catch most issues:

• Arabic pages render right to left, including the cart, checkout fields and order summary.
• Numbers, prices and phone fields remain readable in the Arabic layout.
• Search finds products when customers type in Arabic, not only in English.
• Switching language keeps the customer on the same product or category, with the cart intact.
• Each language version has its own URL, title tag and meta description.

Machine translation is a reasonable first draft for long catalogues, but have a fluent reviewer check your top sellers, size guides and policy pages at minimum. Our guide to Arabic and English bilingual websites goes deeper into layout, URLs and hreflang.

Shipping, returns and the policy pages customers read

Customers read policy pages at the moment of doubt, usually just before paying. Write them for that moment: short, specific and linked from the product page and checkout.

• Shipping: which emirates and countries you deliver to, delivery windows you can actually meet, how charges are calculated and what happens on public holidays.
• Returns and exchanges: the window, the condition items must be in, who pays return shipping, and how and when refunds reach the original payment method.
• Warranty: what is covered, for how long and how to claim.
• Privacy: what customer data you collect and why. Our UAE PDPL website privacy checklist covers this in detail.
• Contact: a phone or WhatsApp number and an email that someone answers.

Keep the policy wording and the store settings aligned. A returns page promising free returns while the system charges return shipping is a complaint waiting to happen.

Mobile checkout on real devices

Google’s mobile first indexing documentation says Google uses the mobile version of a site’s content for indexing and ranking, so the mobile store is the version that counts in search as well as in sales. Test it on actual phones, both iPhone and Android, on mobile data rather than office wifi.

1. Arrive from an ad or social link

   Open a product link from Instagram or WhatsApp and check that the in app browser shows the product, prices and add to cart button correctly.

2. Build a cart

   Add a product with variants, change quantity, apply a coupon, remove an item. Every change should update totals without a full reload.

3. Check out as a guest

   Forcing account creation before payment is a common reason customers leave. Offer guest checkout and invite account creation after the order.

4. Enter a UAE address

   Many addresses here rely on building names, areas and landmarks rather than postcodes. Make fields fit that reality, and make the phone field accept the formats customers type.

5. Pay and confirm

   Complete payment with each method, then check the confirmation page, the email or SMS, and the order in the admin.

Speed belongs in this test too. Heavy product images and third party scripts slow checkout more than most owners expect; our Core Web Vitals guide explains what to measure.

Product structured data and Google Merchant Center

Google offers two routes for product data, and it recommends using both. Its Product structured data introduction says that providing both structured data on web pages and a Merchant Center feed maximises your eligibility to experiences and helps Google understand and verify your data.

Structured data on product pages

For pages where customers can buy, Google’s merchant listing documentation uses Product and Offer markup. The required properties include the product name, image, price and a three letter ISO 4217 currency code, and merchant listings require a price greater than zero. Recommended properties include availability, GTIN, shipping details and return policy.

Before launch, check that the structured data matches what the page shows. If the page says a product is on sale and out of stock, the markup must say the same. Run key templates through Google’s Rich Results Test, and remember that Arabic and English versions each need correct markup.

Google Merchant Center

According to Merchant Center Help, Google can add products to Merchant Center automatically from your store if you use structured data, allow Google to collect it, and verify and claim your website. Google says it checks the site at least once every 24 hours for new products and updates. Set this up before launch so any disapproved products surface while you still have time to fix them.

Analytics purchase events you can trust

If you cannot see which channel produced an order, you cannot decide where to spend next month’s budget. Google’s GA4 ecommerce guide sets out a sequence of recommended events, including view_item, add_to_cart, begin_checkout, add_shipping_info, add_payment_info, purchase and refund. The purchase event carries a transaction ID, value, currency and the items bought.

The checks we would run before launch:

• Place test orders and confirm that each one appears once in GA4 with the correct value and currency.
• Reload the confirmation page and make sure it does not record a second purchase.
• Confirm that orders paid through an external gateway page still return to your confirmation page and fire the event.
• Record cash on delivery orders in a way you can separate from prepaid orders.
• Make sure ad platform conversions and your consent banner behave as configured.
• Exclude your own test orders from reports, or delete them before going live.

Load testing before White Friday and Dubai Shopping Festival

Sale periods bring the heaviest traffic many stores see, and they are when a slow or broken checkout costs the most. The Dubai Media Office describes the Dubai Shopping Festival as an annual event organised by Dubai Festivals and Retail Establishment, and retailers across the UAE run promotions around it and around White Friday. Check the official dates each year before planning campaigns.

A useful load test is realistic, not heroic. Simulate customers browsing categories, searching, adding to cart and checking out, on the production hosting with sale prices and coupon rules switched on. Watch for:

• Checkout and payment steps slowing down before product pages do.
• Stock levels going wrong when many customers buy the same item at once.
• Coupon or discount logic that becomes slow under load.
• Plugins, apps or search services with rate limits you did not know about.
• Page caching accidentally serving one customer’s cart or prices to another.

Plan a freeze on non urgent changes before the sale, keep someone available who can reach the hosting provider and gateway, and prepare a simple maintenance message in both languages in case you need it.

Final sign off before launch

Use a table like this in the last week, with one named owner per row. If a row has no owner, it has not been checked.

Most stores do not fail on design; they fail on the unglamorous rows of that table. If you are planning a new store or rebuilding an existing one, our e-commerce website development team builds bilingual stores in Dubai and launches them with SSL, sitemap submission and conversion tracking in place. When you are ready to grow traffic afterwards, SEO services are available on an optional monthly retainer.