E-COMMERCE REDESIGN

UAE e-commerce redesigns for brands moving from English-only to bilingual Arabic/English are not a translation project — they are a full RTL design system project

Ignited Nepal redesigns UAE e-commerce stores for the bilingual market. RTL design system, Arabic web typography, COD and Tabby/Tamara integration, WhatsApp chat, and Arabic SEO — all built from the redesign phase, not retrofitted after launch.

This is for you if

This service is for UAE e-commerce brands that built their store for an English-speaking audience and are now ready to reach the Arabic-speaking majority — or brands that have an Arabic version of the site that was produced by overlaying translated content on the English design rather than building a proper RTL design system.

Your store is English-only and you are losing the Arabic-speaking majority of UAE online shoppers

You have an Arabic version that was created by translating the English content into a mirrored copy, with text that runs right-to-left in a layout that was built left-to-right

Your checkout does not include COD, Tabby, or Tamara, and you know this is limiting conversion with UAE buyers who prefer these payment methods

Your store does not have a WhatsApp chat entry point, and UAE buyers are contacting you through personal WhatsApp numbers rather than a structured channel

You want to reach Arabic-speaking buyers through Arabic search, but your current store has no Arabic SEO structure

What's broken

Four reasons UAE e-commerce redesigns fail to reach the Arabic-speaking market

The redesign brief describes "adding Arabic to the current design" rather than building a separate RTL design system

Arabic is not a content layer that can be added to an existing English design system. An English-language e-commerce store is built on a left-to-right layout: navigation flows left to right, icons point in the direction of user progression (a right-pointing arrow means "next"), text anchors left, and the visual hierarchy is designed for a reader who scans from left to right. An Arabic version of the store requires a complete mirror of this system: navigation flows right to left, icons must be directionally flipped, text anchors right, and the visual hierarchy is designed for a reader who scans from right to left. Arabic web typography requires specific font choices — not all Arabic fonts render correctly at screen sizes, and Latin web fonts cannot be substituted. A brief that describes "adding Arabic" to the English design will produce an Arabic version that feels incorrect to Arabic-speaking buyers, because it is the English layout with Arabic text inside it.

COD and local payment methods are not included in the redesign scope

A redesigned checkout that still only accepts Stripe credit card payments has not addressed the primary conversion barrier for UAE buyers. Cash on delivery remains a significant payment preference in the UAE market, particularly for first-time buyers who have not previously purchased from a brand. Tabby and Tamara are the dominant BNPL providers in the UAE and are expected by buyers who routinely use BNPL for purchases above AED 200. If the redesign brief does not explicitly include COD, Tabby, and Tamara integration in the checkout scope, the redesigned store will have a conversion problem with a structural cause — the payment options do not match what UAE buyers expect to see. The redesign is an opportunity to fix this, but only if the brief includes it.

WhatsApp chat integration is not built into the redesign

UAE buyers expect a WhatsApp chat entry point on an e-commerce store, and its absence is a trust signal that registers as a gap. WhatsApp is the primary customer communication channel in the UAE market. A floating WhatsApp button with click-to-chat functionality — pre-populated with the store name and a standard opening message — is the most direct way to capture buyers who want to ask a pre-purchase question rather than send an email or fill in a contact form. Buyers who cannot find a WhatsApp contact option do not typically look for the email address — they leave. A redesign that does not include a WhatsApp integration in the brief has missed the most important UAE customer service touchpoint and will produce a store that still has the same contact conversion gap.

Arabic SEO is not planned as part of the redesign scope

The Arabic version of the store needs an SEO structure that is built from the redesign phase, not retrofitted after launch. A bilingual store requires: a URL structure for Arabic pages — typically an /ar/ subdirectory — that is established at the redesign phase so that Arabic pages are indexed under a stable URL from day one; Arabic meta titles and descriptions that are written for Arabic search queries rather than machine-translated from English meta data; and hreflang tags implemented correctly to tell Google which version of each page to show to Arabic-speaking and English-speaking searchers. Retrofitting Arabic SEO after launch on a store that was launched without this structure means reindexing, potential duplicate content issues, and a delay of three to six months before Arabic search visibility begins to build. Building it from the redesign phase costs the same amount of work and avoids the delay entirely.

What we engineer

What an Ignited Nepal e-commerce redesign covers for UAE brands

RTL design system

We design a complete right-to-left design system for the Arabic version of the store. Navigation, icons, layout, and typography are mirrored and adapted for Arabic — not translated from the English layout.

Arabic web typography

We select and implement Arabic web fonts that render correctly at screen sizes across mobile and desktop, and test the typography across devices before launch.

COD, Tabby, and Tamara integration

The checkout is built to include cash on delivery and the UAE's leading BNPL providers from the redesign scope, not added as afterthoughts post-launch.

WhatsApp chat integration

A floating WhatsApp button with click-to-chat functionality is built into the redesign as a standard element, not an optional extra.

Arabic SEO structure

/ar/ subdirectory URL structure, Arabic meta titles and descriptions, and hreflang tags are built from the redesign phase so that Arabic search visibility begins building from day one.

Bilingual UX

The language switcher, currency display, and user account flows are designed for bilingual operation — not two separate stores running on the same platform with different themes.

Conversion audit of the existing store

Before any design work begins, we audit the current store's conversion data to identify the specific barriers the redesign must address beyond the bilingual requirement.

What changes

What is measurably different after the redesign

Before
After
Before Arabic is not a content layer that can be added to an existing English design system. An English-language e-commerce store is built on a left-to-right layout: navigation flows left to right, icons point in the direction of user progression (a right-pointing arrow means "next"), text anchors left, and the visual hierarchy is designed for a reader who scans from left to right. An Arabic version of the store requires a complete mirror of this system: navigation flows right to left, icons must be directionally flipped, text anchors right, and the visual hierarchy is designed for a reader who scans from right to left. Arabic web typography requires specific font choices — not all Arabic fonts render correctly at screen sizes, and Latin web fonts cannot be substituted. A brief that describes "adding Arabic" to the English design will produce an Arabic version that feels incorrect to Arabic-speaking buyers, because it is the English layout with Arabic text inside it.
After Arabic version: A complete RTL design system that feels correct to Arabic-speaking buyers — not the English layout with Arabic text inside it.
Before A redesigned checkout that still only accepts Stripe credit card payments has not addressed the primary conversion barrier for UAE buyers. Cash on delivery remains a significant payment preference in the UAE market, particularly for first-time buyers who have not previously purchased from a brand. Tabby and Tamara are the dominant BNPL providers in the UAE and are expected by buyers who routinely use BNPL for purchases above AED 200. If the redesign brief does not explicitly include COD, Tabby, and Tamara integration in the checkout scope, the redesigned store will have a conversion problem with a structural cause — the payment options do not match what UAE buyers expect to see. The redesign is an opportunity to fix this, but only if the brief includes it.
After Payment options: COD, Tabby, and Tamara are available at checkout from launch day.
Before UAE buyers expect a WhatsApp chat entry point on an e-commerce store, and its absence is a trust signal that registers as a gap. WhatsApp is the primary customer communication channel in the UAE market. A floating WhatsApp button with click-to-chat functionality — pre-populated with the store name and a standard opening message — is the most direct way to capture buyers who want to ask a pre-purchase question rather than send an email or fill in a contact form. Buyers who cannot find a WhatsApp contact option do not typically look for the email address — they leave. A redesign that does not include a WhatsApp integration in the brief has missed the most important UAE customer service touchpoint and will produce a store that still has the same contact conversion gap.
After WhatsApp chat: A floating WhatsApp button with click-to-chat is live on the store for both Arabic and English versions.
Before The Arabic version of the store needs an SEO structure that is built from the redesign phase, not retrofitted after launch. A bilingual store requires: a URL structure for Arabic pages — typically an /ar/ subdirectory — that is established at the redesign phase so that Arabic pages are indexed under a stable URL from day one; Arabic meta titles and descriptions that are written for Arabic search queries rather than machine-translated from English meta data; and hreflang tags implemented correctly to tell Google which version of each page to show to Arabic-speaking and English-speaking searchers. Retrofitting Arabic SEO after launch on a store that was launched without this structure means reindexing, potential duplicate content issues, and a delay of three to six months before Arabic search visibility begins to build. Building it from the redesign phase costs the same amount of work and avoids the delay entirely.
After Arabic SEO: /ar/ subdirectory URLs, Arabic meta data, and hreflang tags are implemented and indexed from launch day.
How it works

How the redesign process works

  1. 01

    Bilingual audit and brief

    Weeks 1 to 2

    We audit the current English store's conversion data and assess the bilingual requirements: payment method gaps, WhatsApp integration status, current Arabic SEO structure (or absence of one), and the scope of the RTL design work.

  2. 02

    RTL design system

    Weeks 3 to 5

    We design the right-to-left design system for the Arabic version: mirrored navigation, directionally correct icons, Arabic web font selection and testing, and RTL layout specifications for each page type.

  3. 03

    Arabic UX and checkout

    Week 5

    The checkout flow is designed for the Arabic version with COD, Tabby, and Tamara integration specified. WhatsApp chat integration is designed into the layout for both language versions.

  4. 04

    Development

    Weeks 6 to 9

    The bilingual store is built on the confirmed platform. /ar/ subdirectory URL structure is implemented. Hreflang tags are configured. Arabic meta data is written. COD, Tabby, and Tamara are integrated in the checkout. WhatsApp click-to-chat is implemented.

  5. 05

    QA and launch

    Week 10

    Both language versions are tested across mobile and desktop. Arabic typography is tested on Android and iOS. Hreflang implementation is tested using Google Search Console's International Targeting tool. The store launches with a monitoring plan for both language versions.

Common questions

Frequently asked questions about bilingual Arabic/English e-commerce redesign in the UAE

What does a bilingual Arabic/English e-commerce redesign require technically on Shopify?

A bilingual Arabic/English Shopify store requires a translation app that supports RTL layout — Weglot and Langify are the most commonly used options for UAE bilingual stores on Shopify, each with different approaches to RTL handling. The theme must be built or adapted to support RTL CSS layout, meaning that the direction property in the stylesheet switches to rtl for the Arabic version and all layout elements — navigation, product cards, form fields, checkout steps — render correctly in right-to-left flow. Arabic web fonts must be loaded as custom fonts because Shopify's default font library does not include the Arabic typefaces needed for a professional Arabic store experience. The /ar/ subdirectory URL structure for Arabic pages must be configured correctly so that Shopify's canonical URL handling does not create duplicate content issues between the English and Arabic versions.

How long does an Arabic RTL e-commerce redesign take compared to an English-only redesign?

An Arabic RTL e-commerce redesign takes approximately 30 to 40 percent longer than an equivalent English-only redesign, primarily because the RTL design system requires a separate design phase and the bilingual QA process covers twice the number of page templates. A ten-week English-only redesign typically extends to thirteen to fourteen weeks when the RTL Arabic version is built in parallel. Brands that build the English version first and then add Arabic as a second phase typically experience a longer total timeline because the RTL requirements were not factored into the original design decisions, requiring rework at the design stage rather than parallel work from the start. Building both language versions from the same design phase is the more time-efficient approach for a brand that needs both.

How do I include COD and Tabby/Tamara in a UAE e-commerce redesign scope?

COD requires a Shopify app or custom payment method configuration that enables the cash on delivery option in the checkout, along with a post-order workflow for flagging COD orders for the fulfilment team. Tabby and Tamara are both available as Shopify payment gateway integrations through their respective official Shopify apps, and both require a merchant account with the provider before integration can begin. The redesign brief should specify: which payment options are to be included, the placement of Tabby and Tamara badges on the product page (equivalent to the Afterpay placement in the Australian market, above the fold at the price line), and the COD workflow requirements for the store's operations team. All three payment methods should be in a merchant testing environment before the redesign development begins so that integration can be completed and tested within the development timeline rather than being delayed by merchant onboarding.

How do I set up Arabic SEO correctly from a redesign rather than retrofitting it later?

Arabic SEO built from a redesign requires four elements established at the development phase: an /ar/ subdirectory URL structure for all Arabic pages (not a subdomain, which creates additional crawl budget and authority splitting considerations); hreflang tags on every page specifying the English version and Arabic version as alternate language targets for ar-AE; Arabic meta titles and descriptions written from Arabic keyword research rather than machine-translated from English meta data; and an Arabic XML sitemap submitted separately to Google Search Console under the same property as the English site. Retrofitting these elements after launch on a store that launched without them requires a URL migration (with 301 redirects from any Arabic pages that were indexed under incorrect URLs), a resubmission to Google Search Console, and a waiting period of three to six months before the corrected structure is fully indexed. Building it correctly from the redesign phase avoids this delay.

Should a UAE brand redesign on Shopify or WooCommerce for the bilingual Arabic/English requirement?

Shopify is the more practical platform for UAE bilingual stores because the available translation apps — Weglot and Langify — are built and maintained specifically for Shopify's architecture, and the checkout customisation options for COD and BNPL integrations are well-supported through the Shopify App Store. WooCommerce supports bilingual operation through WPML or Polylang, but RTL layout support requires additional theme development work and the COD and BNPL integrations for the UAE market are less mature in the WooCommerce ecosystem than in the Shopify ecosystem. For a UAE brand investing in a bilingual redesign, Shopify reduces the ongoing maintenance overhead and provides more stable integrations for the payment methods that matter in the UAE market. The platform assessment at the start of the redesign process should confirm this recommendation or identify any specific requirements that make WooCommerce the better choice for the brand's particular catalogue or operational setup.

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
Start here

A bilingual redesign is a design system project, not a translation project

Reaching the Arabic-speaking majority in the UAE requires a store that feels correct to Arabic-speaking buyers — not a store that reads in Arabic but thinks in English. The RTL design system, the payment options, the WhatsApp channel, and the Arabic SEO structure all need to be built from the redesign phase. Request your E-commerce Redesign Audit from Ignited Nepal. We will assess your current store's bilingual readiness, identify the gaps in payment options, SEO structure, and RTL design, and produce a brief for a redesign that reaches the full UAE market from launch day.