BeforeArabic 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.
AfterArabic version: A complete RTL design system that feels correct to Arabic-speaking buyers — not the English layout with Arabic text inside it.
BeforeA 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.
AfterPayment options: COD, Tabby, and Tamara are available at checkout from launch day.
BeforeUAE 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.
AfterWhatsApp chat: A floating WhatsApp button with click-to-chat is live on the store for both Arabic and English versions.
BeforeThe 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.
AfterArabic SEO: /ar/ subdirectory URLs, Arabic meta data, and hreflang tags are implemented and indexed from launch day.