BeforeWPML handles the language management and translation layer for an Arabic WooCommerce store, but it does not apply RTL CSS. Adding Arabic as a language in WPML means your product content, navigation labels, and WooCommerce strings can be translated — but the visual layout of the page (text alignment, element direction, sidebar position, button placement, form field order) remains left-to-right. A correctly implemented Arabic RTL WooCommerce storefront requires theme-level changes: direction: rtl declarations on the html or body element when Arabic is the active language, mirrored layout for any flex or grid containers that have directional assumptions, right-aligned typography throughout the product pages and checkout, and RTL-specific adjustments to any JavaScript-driven components (carousels, sliders, checkout steps) that use directional logic. Some WooCommerce themes include a built-in RTL stylesheet. Where they do, it still requires testing against all WooCommerce page types — product listing, single product, cart, checkout, account pages — because RTL support in themes is inconsistently implemented and often incomplete on the WooCommerce-specific pages, which use templates the theme author may not have tested in Arabic.
AfterWhen your WooCommerce store is configured correctly for the UAE market, the Arabic storefront reads correctly — layout, typography, checkout flow, and all WooCommerce-specific pages are oriented for right-to-left reading. Arabic-first shoppers can complete the purchase path without encountering layout elements that are misaligned with their reading direction.
BeforeWooCommerce's built-in cash on delivery gateway works as follows: a customer selects COD at checkout, the order is created in WooCommerce with a Processing status, and the standard new-order email is sent to the store admin. There is no verification step between order placement and order dispatch. In the UAE, where COD is a significant payment method and non-delivery rates for unverified COD orders are higher than for verified orders, this default flow creates operational and financial risk. A customer who places a COD order and does not answer the door — whether due to a change of mind, an incorrect address, or an attempt to receive goods for free — results in a returned shipment and a logistics cost. The standard UAE COD workflow involves sending a WhatsApp message (or placing a confirmation call) to the customer after order placement, before the order is dispatched. In WooCommerce, this requires a custom order status between New Order and Processing (typically "Pending Verification"), a trigger that sends the WhatsApp message automatically when the order is placed, and a mechanism for the operations team to mark the order as verified before it moves to the packing and dispatch workflow. This is not available in the default WooCommerce COD gateway.
AfterCOD operations become more controlled. Orders do not move to processing and dispatch without a verification step. Your operations team can see at a glance which COD orders have been verified and which are pending, and the WhatsApp message is sent automatically rather than requiring a manual outreach step for every new COD order.
BeforeBoth Tabby and Tamara have official WooCommerce plugins. Installing the plugin does not make BNPL functional. The plugin must be connected to a UAE merchant account registered with Tabby or Tamara, configured for AED as the currency, and tested against the BNPL provider's sandbox environment before going live. The most common failure mode for UAE WooCommerce stores with Tabby or Tamara is that the plugin is installed and appears to show instalment amounts on product pages, but when a customer attempts to use BNPL at checkout, the payment either fails silently or returns an error. This is almost always a credential or currency configuration issue: the plugin is connected to a test API key rather than a live key, or the store's WooCommerce currency is set to USD rather than AED, which the BNPL provider's API does not accept for UAE merchant accounts. The fix requires obtaining live API credentials from Tabby or Tamara's merchant portal, configuring the WooCommerce currency to AED, updating the plugin settings with the live credentials, and running a complete end-to-end test through the BNPL checkout flow.
AfterBNPL works at checkout. Customers who see Tabby or Tamara instalment amounts on product pages can complete the BNPL payment without hitting an error at checkout. The instalment amount is calculated correctly in AED. Order status in WooCommerce updates correctly based on the outcome from the BNPL provider.
BeforeArabic-speaking shoppers read product pages differently from English-speaking shoppers. The primary product image is expected on the right. The product title, price, and add-to-cart area read from right to left. Product description paragraphs and bullet points are right-aligned. The checkout flow reads right to left. When a WooCommerce store has Arabic text content but a layout that remains LTR — because only the content was translated without RTL layout changes — the page creates cognitive friction for Arabic-first shoppers. The navigation is reversed from the expected direction. The checkout fields are aligned incorrectly. The visual hierarchy of the product page does not match the reading pattern of the target customer. This is not a translation problem. It is a front-end development problem: the CSS layout of the WooCommerce product page, cart, checkout, and account pages needs to be adapted for RTL display when Arabic is the active language.
AfterYour store is operationally ready for the UAE market — not a translated version of an English store, but a store that has been configured for how UAE customers buy.
