E-COMMERCE CRO

UAE buyers abandon checkout when the language switches from Arabic to English — and when COD is not offered

Session recordings on UAE e-commerce stores show a consistent pattern: buyers who arrived on an Arabic product page drop off disproportionately when the checkout loads in English. A second drop occurs when buyers reach the payment step and find that cash on delivery is not available. These are trust problems, not traffic problems. More ad spend does not fix either of them.

Request your CRO Audit → View the evidence →
This is for you if

This service is for three types of UAE e-commerce operators.

You have a Shopify store with Arabic and English language versions. Traffic is coming in but conversion on the Arabic-language path is significantly lower than on the English path. You suspect the checkout is the problem but you have not confirmed it with data.

You switched to card-only checkout after experiencing a high rate of COD returns or fraud. Your checkout abandonment rate increased after the change but you have not measured the full conversion cost of removing COD. You want to understand whether the fraud reduction justifies the conversion loss, and whether there are middle-ground options.

You are a brand from Australia, the US, or Europe setting up a UAE storefront. You know the market has high smartphone penetration and strong e-commerce growth, but you are not sure which trust signals, payment methods, and checkout configurations apply to UAE buyers specifically. You want the UAE CRO setup done correctly from the start.

What's broken

Four conversion barriers specific to UAE e-commerce stores

Arabic product pages with English-language checkout

A buyer who navigates the store in Arabic — reads the Arabic product description, sees Arabic pricing, uses the Arabic navigation — arrives at a checkout that switches to English. The language change signals something has changed: either the buyer has left the familiar part of the store, or the store was not fully built for Arabic-speaking buyers. Session recordings on bilingual UAE stores consistently show elevated drop-off at the checkout page entry for Arabic-language visitors compared to English-language visitors on the same store. This is a trust gap caused by an incomplete localisation that most store owners do not connect to their checkout abandonment rate.

No COD option for first-time buyers

In the UAE, cash on delivery preference is particularly strong for first purchases with unfamiliar brands. A buyer who does not know your brand, has no purchase history with you, and cannot verify your reliability through personal experience or strong social proof is being asked to hand over card details to an unknown entity. COD removes that barrier: the buyer does not pay until they have the product in hand. Stores that remove COD entirely to manage fraud risk lose a significant portion of first-time buyer conversions to competitors who offer it. The trade-off between fraud reduction and conversion loss is calculable, and for most stores the conversion loss exceeds the fraud saving.

Tabby and Tamara BNPL not visible on product pages

Tabby and Tamara are the dominant BNPL providers in the UAE and the GCC. For products priced above AED 200, displaying the instalment amount (through Tabby or Tamara's Shopify widgets) on the product page — directly under the price — reduces price resistance in the same way Afterpay does in Australia. When BNPL is available at checkout but not displayed on the product page, buyers who would convert on the instalment amount never see it during the add-to-cart decision. The widget placement is under the product price, above the Add to Cart button, and should be visible without scrolling on both Arabic and English versions of the page.

Trust signals displayed in English only

SSL badges, payment security icons, return policy summaries, and brand guarantee statements are conversion tools. On a store where a significant portion of buyers navigate in Arabic, trust signals displayed only in English are partially inert — they are present on the page but do not communicate to the Arabic-speaking buyer with the same force as Arabic-language equivalents. This is not about translation for the sake of completeness. It is about placing trust-building information in the language the buyer is using at the moment they are deciding whether to trust the store with their money.

What we engineer

The CRO deliverables for a UAE e-commerce store

Bilingual conversion funnel audit

Separate analysis of the Arabic-language buyer path and the English-language buyer path — comparing drop-off rates at each funnel step to identify where the trust gap between the two experiences is largest.

Checkout localisation review

Assessment of the Arabic checkout experience — language, layout, payment option display, trust signals — with specific recommendations for closing the gap between the Arabic product page experience and the checkout experience.

COD conversion impact analysis

Calculation of the current conversion cost of COD absence (or the fraud cost of COD presence), with a recommendation on COD strategy and, where applicable, the configuration of COD verification options (OTP confirmation, prepaid COD) that reduce fraud without removing the option.

Tabby and Tamara BNPL placement

Implementation of Tabby and/or Tamara widgets on product pages in both Arabic and English versions, with instalment amounts displayed above the fold on products above the AED 200 threshold.

Arabic trust signal implementation

Review and implementation of Arabic-language versions of trust badges, return policy summaries, and payment security signals on product pages targeting Arabic-speaking buyers.

Session recording and heatmap analysis

Hotjar or Microsoft Clarity data reviewed separately for Arabic-language and English-language buyer sessions, identifying the specific moments where Arabic buyers exit and English buyers do not.

Mobile checkout optimisation

Review of the checkout experience on iOS and Android on UAE mobile networks, with specific attention to load time, form field usability, and payment method display on small screens.

A/B testing roadmap

A prioritised sequence of tests starting with the highest-impact hypothesis from the audit — typically the checkout localisation gap or the COD decision — with success metrics defined before the test begins.

Request your CRO Audit →
What changes

Four outcomes from a CRO engagement for a UAE e-commerce store

Before
After
Before A buyer who navigates the store in Arabic — reads the Arabic product description, sees Arabic pricing, uses the Arabic navigation — arrives at a checkout that switches to English. The language change signals something has changed: either the buyer has left the familiar part of the store, or the store was not fully built for Arabic-speaking buyers. Session recordings on bilingual UAE stores consistently show elevated drop-off at the checkout page entry for Arabic-language visitors compared to English-language visitors on the same store. This is a trust gap caused by an incomplete localisation that most store owners do not connect to their checkout abandonment rate.
After The engagement separates Arabic and English buyer behaviour in the data, giving you a precise view of where the bilingual experience is creating conversion loss and where it is not. You are not applying generic CRO changes to a market with specific localisation requirements.
Before In the UAE, cash on delivery preference is particularly strong for first purchases with unfamiliar brands. A buyer who does not know your brand, has no purchase history with you, and cannot verify your reliability through personal experience or strong social proof is being asked to hand over card details to an unknown entity. COD removes that barrier: the buyer does not pay until they have the product in hand. Stores that remove COD entirely to manage fraud risk lose a significant portion of first-time buyer conversions to competitors who offer it. The trade-off between fraud reduction and conversion loss is calculable, and for most stores the conversion loss exceeds the fraud saving.
After Arabic-speaking buyers complete the purchase on a checkout that is consistent with the product page experience they arrived from. The language switch that session recordings currently show as a drop-off trigger is removed or substantially mitigated.
Before Tabby and Tamara are the dominant BNPL providers in the UAE and the GCC. For products priced above AED 200, displaying the instalment amount (through Tabby or Tamara's Shopify widgets) on the product page — directly under the price — reduces price resistance in the same way Afterpay does in Australia. When BNPL is available at checkout but not displayed on the product page, buyers who would convert on the instalment amount never see it during the add-to-cart decision. The widget placement is under the product price, above the Add to Cart button, and should be visible without scrolling on both Arabic and English versions of the page.
After First-time buyers who previously abandoned because COD was unavailable now have a pathway to complete a purchase. Tabby and Tamara instalment amounts are visible on product pages for products where BNPL is a conversion driver. The payment option configuration is set up to serve the UAE market specifically, not adapted from an Australian or US template.
Before SSL badges, payment security icons, return policy summaries, and brand guarantee statements are conversion tools. On a store where a significant portion of buyers navigate in Arabic, trust signals displayed only in English are partially inert — they are present on the page but do not communicate to the Arabic-speaking buyer with the same force as Arabic-language equivalents. This is not about translation for the sake of completeness. It is about placing trust-building information in the language the buyer is using at the moment they are deciding whether to trust the store with their money.
After Every trust signal on the store communicates in the language the buyer is using. Arabic-speaking buyers see the same quality of trust information as English-speaking buyers. The gap that previously existed — visible in lower conversion rates on the Arabic-language path — is closed.
How it works

How a CRO engagement works for a UAE e-commerce store

  1. 01

    Bilingual analytics audit

    Days 1-7

    We review Google Analytics 4 with language segmentation applied, confirm that Arabic and English buyer paths are tracked separately, and install or review Hotjar or Microsoft Clarity with the same segmentation. We map the specific funnel steps where Arabic buyers exit.

  2. 02

    Audit findings

    Days 8-12

    We present the findings with data separated by language path, device type, and funnel step. You see exactly where the conversion gap between Arabic and English buyers is coming from.

  3. 03

    Implementation and testing

    Days 13-50

    Changes are implemented in priority order: checkout localisation, payment option configuration, BNPL placement, and trust signal updates. Each structural change that can be A/B tested is tested before being declared final.

  4. 04

    Review and roadmap

    Days 51-60

    Results are reviewed against the pre-engagement baseline for both language paths. The 90-day testing roadmap addresses the next tier of conversion improvements beyond the structural fixes completed in the engagement.

Request your CRO Audit →
Common questions

Frequently asked questions about E-commerce CRO

How do I create an Arabic checkout experience on Shopify for UAE buyers?

Shopify supports Arabic as a native checkout language through the Shopify Markets feature and the Shopify Translate and Adapt app. To localise the checkout for Arabic-speaking UAE buyers: enable the Arabic language in your Shopify Markets settings, use Translate and Adapt to review and correct machine translations in checkout copy (automated Arabic translation in Shopify is functional but sometimes produces formal MSA Arabic where UAE buyers expect Gulf Arabic phrasing), and confirm that the checkout layout renders correctly in right-to-left text direction on both iOS and Android. Payment method names and trust signal text in the checkout should also be translated — not just the product and navigation copy. If your store uses a custom checkout UI (available on Shopify Plus), the Arabic localisation requires additional configuration in the checkout extensibility editor.

Should I offer COD on my UAE Shopify store — what are the trade-offs?

COD increases first-time buyer conversion, particularly for buyers unfamiliar with your brand, but it introduces return-to-sender risk (buyers who order COD and then refuse delivery) and fraud risk (bulk COD orders placed without intent to receive). The standard mitigation for UAE stores is OTP-confirmed COD: the buyer provides a phone number at checkout, receives an SMS confirmation code before dispatch, and the order is only shipped after the code is confirmed. This reduces COD fraud significantly without removing the option for genuine buyers. The decision on whether to offer COD depends on your average order value, fulfilment model, and the proportion of first-time buyers in your customer mix. For most UAE DTC stores with products under AED 500, the conversion gain from offering OTP-confirmed COD outweighs the fraud and return costs.

How do I add Tabby and Tamara BNPL to my Shopify product pages?

Both Tabby and Tamara have official Shopify apps available in the Shopify App Store. Installation involves connecting the app to your Shopify store and entering your merchant credentials. The apps provide widgets that display the instalment amount (typically 4 equal payments) directly on the product page, calculated dynamically from the product price. For the widget to appear above the fold, you may need to adjust its placement in the Shopify theme editor — the default placement in some themes positions it below the Add to Cart button. Both apps support Arabic-language display, which should be enabled for stores targeting Arabic-speaking buyers. Tabby and Tamara each have minimum and maximum transaction amounts (typically AED 50 to AED 10,000) and require a merchant account with the respective provider.

How do I run session recording and heatmap analysis on a bilingual Arabic/English Shopify store?

Hotjar and Microsoft Clarity both support recording sessions on multilingual Shopify stores without additional configuration — the recording captures user behaviour regardless of language. To analyse Arabic versus English buyer behaviour separately, use the segment or filter function in both tools: filter sessions by URL (if your Arabic and English stores are on separate URLs or subdomains) or by browser language setting (if you use a single URL with language detection). In Google Analytics 4, add a secondary dimension of "Browser Language" to your funnel analysis to separate Arabic-language sessions. The most revealing comparison is the checkout page drop-off rate for Arabic-language sessions versus English-language sessions — this single metric identifies the presence and approximate magnitude of the checkout localisation gap.

What is the average e-commerce conversion rate for a UAE Shopify store?

UAE e-commerce conversion rates average approximately 1-2.5% across categories, with significant variation by product type, traffic source, and the quality of the Arabic-language experience. Stores with a strong COD option, visible Tabby or Tamara BNPL, and a fully localised Arabic checkout consistently convert above the UAE average. Mobile commerce accounts for a high proportion of UAE e-commerce traffic, so mobile checkout optimisation has an outsized impact on overall conversion rate compared to many other markets. A reasonable 90-day target for a UAE store after a CRO engagement that addresses the Arabic checkout gap and COD configuration is 1.8-2.5% overall, with the Arabic-language path approaching parity with the English-language path.

Our team

The people behind the work

Not a black box. Real specialists you can call, with their names on the work.

Niraj Raut

Niraj Raut

Founder — Ecommerce SEO
Keshab Joshi

Keshab Joshi

PPC Expert
Hawrry Bhattarai

Hawrry Bhattarai

Google Ads Expert
Arogya Rijal

Arogya Rijal

SaaS SEO Expert
About Us →
Start here

A bilingual store needs a bilingual CRO approach

The conversion problems on a UAE e-commerce store are not the same as the problems on an Australian or US store. The audit starts with your data, separated by language path, to find the specific points where UAE buyers are leaving and why.

Request your CRO Audit →