Euro prices on an Arabic store: fix the site before the ads.

If shoppers in the UAE, Saudi Arabia, Oman or Bahrain add to cart and then don't buy, check the store before you change the Meta ads. A price left in euros, a checkout that's only half translated, English reviews and a page that reads left to right can stop the sale at the moment of paying. No targeting change fixes that.

On the call where we saw this, our advice was to pause the ads in those markets, take a week or two to fix the currency and the Arabic version, and relaunch. If the problem is still there after the fix, then look at Meta.

What the store looked like from the Gulf

On a mentoring call, a consultant brought us a European ecommerce client that shipped to the Gulf from a warehouse in Dubai. Its Meta ads converted in most countries, but Saudi Arabia, Oman, Bahrain and the UAE produced one or two orders at most. Was the traffic bad, or was the site wrong for the market? We walked through the store as a shopper there would:

• The currency. One market view still showed EUR. Switched to Arabic, the checkout turned the digits into Arabic numerals but left the amount in euros. It translated the numbers, not the currency.
• The reviews. Every product review was in English. Reviews are where a shopper goes to decide, so they need to be readable too.
• The rest of the page. The trust lines (secure payments, fast shipping, customer support), the product headline and the "You might also like" row stayed in English, and punctuation landed on the wrong side of the text. That pattern usually means a translation plugin changing the text it can reach, not a localized page.
• The first screen. In our experience, many everyday shoppers in the UAE would rather read Arabic than long English sentences. We'd open the store in Arabic for Gulf visitors, with English one tap away.

Why it looked like a traffic problem

The analytics showed traffic and add-to-carts from the Gulf, so people were entering the funnel. But average time on page there sat below a minute, against about three minutes or more in the other countries. Our read: a large share of visitors couldn't use the page and left, a few understood enough to add to cart, and the euro price stopped them at payment.

A shopper paying a euro price with a local card doesn't know what the bank will charge once it converts the amount and adds its fees. Where buying online runs on trust, that doubt is enough to step back.

You can check the same pattern in GA4. Put Average engagement time per session next to the Country dimension, then add Language, which GA4 records as the language of the visitor's browser or device. If one region engages far less while still adding to cart, read it as a page problem first.

Fix the store, then relaunch

• Show the local currency. On Shopify, selling in local currencies lets customers see prices, pay at checkout and get refunds in their own currency. AED and SAR are on Shopify Payments' accepted currencies list, and the full feature needs Shopify Payments with one-page checkout. Check each market against that list.
• Translate everything a buyer reads. Shopify shows your default language wherever a translation doesn't exist, which is how English reviews and trust lines end up on an "Arabic" page. A client of ours runs its site in three languages with each version written by people, not generated by a plugin.
• Flip the layout. Arabic reads right to left. Shopify says the latest Horizon themes support right-to-left languages; with any other theme, confirm it before you publish Arabic.
• Open in the right language. Shopify's language redirection switches the storefront to the visitor's browser language, once that language is added, assigned to the market, translated and published.

Then turn the ads back on and compare the same numbers: engagement time by country, add-to-carts, orders.

Common questions

Why do I get add to carts but no purchases from one country?

When other countries convert on the same ads and one region doesn't, check what that region sees at checkout first: the currency, the language of the checkout and the reviews, and whether the page reads in the right direction. Compare average engagement time per session by country in GA4. If that region engages far less but still adds to cart, treat it as a site problem before a targeting problem.

Should I show prices in dirhams or riyals for Gulf shoppers?

In our view, yes. A shopper paying a euro price with a local card can't tell what will be charged after the bank converts it and adds its fees. On Shopify, selling in local currencies lets customers see prices, pay at checkout and get refunds in their local currency. AED and SAR are on Shopify Payments' accepted currencies list, and full functionality needs Shopify Payments with one-page checkout.

Does Shopify support Arabic right-to-left layouts?

Shopify says the latest versions of themes in the Horizon family support right-to-left languages such as Arabic, Hebrew and Urdu. With any other theme, confirm right-to-left support with the theme developer so the layout is correct. Shopify's checkout includes translated content for 49 languages, Arabic among them.

How do I compare engagement by country in GA4?

Add the Country dimension and the Average engagement time per session metric to a report or exploration, then add Language, which GA4 records as the language of the user's browser or device. GA4 counts a session as engaged if it lasts longer than 10 seconds, has a key event, or has 2 or more page or screen views.

Should I pause Meta ads while I fix the store?

For the affected markets, that's what we recommended: stop the ads there, take a week or two to fix currency and translation, then relaunch and compare the same metrics. If the problem persists after the fix, then look at the Meta ads and the targeting.