Short answer: Selling in more than one country means three separate jobs: currency (show local prices, charge in local currency where possible), language (real translations with correct hreflang, not a browser‑translate button), and layout (full right‑to‑left for Arabic, not a flipped stylesheet). Get the URL structure right so each market can rank, keep the checkout local, and test the Arabic experience end to end.
Currency
- Display prices in the visitor's currency (geolocation, with a manual switcher).
- Charge in local currency where your gateway supports it — it reduces failed payments and chargebacks.
- Handle rounding to sensible local price points (not "€19.37").
- On Shopify: Markets + Shopify Payments handles multi‑currency cleanly. On WooCommerce: a currency plugin plus a gateway that settles in multiple currencies.
- Show taxes and duties correctly per market (VAT‑inclusive in the EU/UK, GST‑inclusive in AU, etc.).
Language
- Real translations. Machine translation as a starting draft is fine; ship human‑reviewed copy for anything that sells (product pages, checkout, policies).
- URL structure: subfolders (
,) or subdomains, consistently. Avoid parameters. - hreflang tags on every page linking all language versions plus
. This is what stops Google showing the wrong version and treating them as duplicates. - Translate metadata, alt text, structured data, and transactional emails — not just the visible page.
- A visible language switcher that keeps the user on the same page in the new language.
Arabic RTL — a layout job, not a toggle
- The whole document direction flips (
): navigation, product grids, form fields, icons, progress steps, carousels. - Use CSS logical properties (
, not) so one codebase serves both directions. - Numbers and prices usually stay left‑to‑right within RTL text — handle the bidi carefully.
- Choose a font with strong Arabic coverage; test line height and letter spacing separately from Latin.
- Mirror directional icons (back arrows, chevrons); don't mirror logos or images of real things.
- Test the full flow in Arabic: browse → product → cart → checkout → confirmation email.
SEO and performance
- Each market's pages should be genuinely localised (currency, shipping, examples) — not thin duplicates.
- Don't let the translation layer add render‑blocking scripts; it shouldn't cost you Core Web Vitals.
- Submit a sitemap that includes every localised URL.
Key takeaways
- Currency, language and layout (RTL) are three separate pieces of work.
- Charge in local currency where you can; show local prices always.
- hreflang + a clean subfolder structure is what makes multi‑language rank instead of cannibalise.
- Arabic RTL flips the entire layout — build with logical properties and test the whole checkout.
FAQ
Shopify or WooCommerce for multi‑currency?
Shopify Markets is the smoother path. WooCommerce is more flexible if you need specific local gateways (Mada, PayTabs, Tabby) without transaction penalties.
Do I need separate stores per country?
Usually not — one store with Markets/localisation is simpler to run. Separate stores only for very different catalogues or operations.
Is a translation app enough for Arabic?
For text, partly. For layout, no — RTL needs proper implementation across the theme.
Alamin Sultan
Web developer for real estate and e‑commerce. WordPress · Next.js · MERN.