Looks like you're in . Want the local site?
Custom Liquid for Arabic RTL and English LTR storefronts, Telr or PayTabs payment integration, Shopify Markets for QAR, USD, SAR, and AED, and checkout configuration built for the Gulf market.
You are building or rebuilding a Shopify store that needs to serve both Arabic and English-speaking customers. Bilingual Shopify stores require more than translation. The data architecture, template logic, and RTL implementation all need to be built with both languages in mind from the start.
You have an Arabic Shopify store where the RTL layout breaks in certain sections or app-injected blocks. Shopify's native RTL handles the theme core, but custom sections and third-party apps frequently introduce LTR assumptions. Targeted Liquid and CSS fixes restore directional consistency without a full rebuild.
You need payment processing configured for the Qatar market. Shopify Payments is not available in Qatar. Telr and PayTabs are the standard Shopify-compatible options for the GCC market. Configuration requires more than app installation: checkout flow, order handling, and PCI documentation all need to be completed correctly.
You sell across the GCC and need multi-currency Shopify Markets configured. QAR, SAR, AED, and USD in a single Shopify store requires structured Shopify Markets configuration. Without it, currency display is inconsistent and customers from other GCC countries see pricing that was not designed for their market.
You are on Shopify Plus in Qatar and want to use checkout extensibility. Checkout.liquid is deprecated. Checkout extensions allow bilingual checkout UI, market-specific payment method ordering, and custom messaging within the checkout, which is particularly valuable for Gulf-market stores where checkout language and payment presentation are important conversion factors.
You are an international brand entering the Qatar market and need a Gulf-ready Shopify store. International brands expanding into Qatar need a store that is technically ready for Arabic-speaking customers, Gulf-market payment expectations, and QAR pricing, not a global store with Arabic added as an afterthought.
Shopify's native RTL support handles CSS direction and text alignment correctly for most of the theme. Custom Liquid sections, app-injected blocks, and checkout UI extensions frequently introduce LTR assumptions that break Arabic layout. These require targeted Liquid and CSS fixes that go beyond the theme editor.
A store serving both Arabic and English customers needs a content architecture that makes managing two-language product data, collections, and pages maintainable over time. This is not just a translation problem: it is a data architecture problem that determines how much work every future content update costs.
Shopify Payments is not available in Qatar. Payment processing must be handled through third-party payment gateways. Telr and PayTabs are the most commonly used options for Shopify stores in Qatar and the wider Gulf market. Configuration, checkout integration, and ongoing PCI compliance considerations differ from Shopify Payments setups.
Qatar-based merchants often sell to customers across the Gulf Cooperation Council region. QAR, SAR, and AED are the primary currencies for the GCC market, with USD needed for international reach. Shopify Markets handles the core of this, but configuration for Gulf-specific currency display and pricing requires careful setup.
A written theme spec precedes all development. Custom Liquid is written to support both Arabic RTL and English LTR within the same theme. This covers section schema, block-level directionality, conditional rendering based on active locale, and correct handling of typographic conventions for both scripts.
Shopify's native RTL support provides the CSS and Liquid foundation for Arabic storefronts. Custom Liquid development extends this foundation to cover edge cases: third-party app blocks that inject LTR content, custom section layouts where flexbox or grid direction needs explicit locale-aware handling, icon and image directionality, and form field alignment. The output is an Arabic storefront where direction is consistent throughout, not just in the theme's default sections.
Managing Arabic and English content on a single Shopify store requires a structured approach. Shopify's native translation system (Translate and Adapt) and third-party translation apps handle the storefront language layer. The data architecture underneath, including metafield schema, collection structure, and page templates, needs to be designed to support bilingual content without creating maintenance overhead. We design this architecture from the start so it scales.
Metafields extend the product data model beyond Shopify's default fields. For Qatar merchants with Arabic-language product attributes, we design the metafield namespace and key structure to support bilingual data, build definitions in the admin, and wire them into Liquid templates across product, collection, and page contexts.
Shopify Payments is not available in Qatar. Telr and PayTabs are both established payment processors with Shopify integration support for the GCC market. Integration covers gateway configuration, checkout payment flow, order management in the Shopify admin, and testing across card payment, and where applicable, additional payment methods relevant to the Qatar market. PCI compliance considerations are documented as part of the handover.
Shopify Markets is configured for the Gulf market with QAR as the base currency and USD, SAR, and AED as additional markets. Configuration covers currency display formatting, market-specific pricing rules, and correct currency presentation at checkout for each market. Geolocation-based market assignment is configured so customers are routed to the correct currency from session start.
Collection filtering is built to work correctly in both Arabic and English, with filter labels and taxonomy mapped to the actual product catalogue in both languages. Product page template routing handles different product types for each market and language context.
Checkout language, payment method display, and address field configuration are set for both Arabic and English checkout flows. For Plus merchants, checkout UI extensions allow more precise bilingual and market-specific customisation within the checkout.
Third-party apps are reviewed for RTL compatibility and performance cost. Apps that inject LTR-only code into the storefront are identified and either replaced or wrapped with directional CSS fixes. Apps that duplicate native functionality are removed.
Core Web Vitals are measured and addressed at the theme level. Arabic font loading for both display and body text is optimised, as Arabic web fonts can have a significant impact on Largest Contentful Paint if not loaded correctly.
GA4 implementation with correct market attribution across all Shopify Markets configurations. Analytics event tracking is set up to distinguish QAR, SAR, AED, and USD transactions by market.
Audit of current theme RTL implementation, bilingual content architecture, payment gateway configuration, Shopify Markets setup, app stack, and analytics. Produces a written report with prioritised findings and recommended scope.
Bilingual content architecture, metafield schema, RTL/LTR conditional Liquid structure, payment gateway integration requirements, and Shopify Markets currency configuration are documented before development begins.
Custom theme development covering Arabic RTL and English LTR, metafield wiring, collection logic in both languages, and market-specific conditional rendering are built to spec in a staging environment.
Telr or PayTabs integration is completed and tested. Shopify Markets is configured for QAR, USD, SAR, and AED with correct currency display and geolocation-based market routing.
Arabic storefront is reviewed end-to-end for directional consistency. LTR edge cases from app injections and custom sections are identified and fixed. Core Web Vitals are tested with Arabic font loading factored in.
Documented handover covering Liquid code, bilingual content architecture, metafield schema, payment gateway setup, and Shopify Markets configuration. Ongoing admin configuration instructions in English (Arabic summaries available on request).
Shopify provides native RTL support that covers CSS direction, text alignment, and the core theme layout for Arabic storefronts. This handles the majority of RTL requirements correctly. The gaps appear in custom Liquid sections, third-party app blocks, and checkout UI extensions that were built with LTR assumptions. A store built on Shopify with Arabic as the store language will look mostly correct, but a thorough RTL audit typically finds a number of directional issues in non-standard sections and app-injected content that require targeted fixes.
Both Telr and PayTabs are established payment processors with Shopify integration support and a track record in the GCC market. The choice between them depends on several factors: transaction fee structure, supported card schemes, settlement currency preferences, the level of support provided during integration, and whether the merchant has an existing banking or payment processing relationship with either provider. Both options are viable for Qatar-based Shopify stores, and both require configuration beyond simple app installation. The diagnostic phase includes a payment gateway review that helps clarify the right choice for the specific merchant's situation.
Shopify Markets allows a single Shopify store to serve different currency markets with distinct pricing, currency display, and checkout currency. For a Qatar-based store serving QAR, SAR, AED, and USD, each currency is configured as a separate market with geolocation routing so customers are automatically assigned to the correct market based on their location. Pricing can be set as exact currency conversion from the QAR base, or as market-specific prices where the merchant wants explicit control over the price in each currency. Currency formatting is configured at the market level, and checkout displays the customer's market currency throughout.
Shopify's native Translate and Adapt app handles storefront language translation for most content types. Product titles, descriptions, collection names, and page content can all be managed in multiple languages from a single admin. Metafields require additional configuration to support translated values. The architecture we design ensures that both Arabic and English content is stored as structured data, making updates and additions manageable without technical involvement for each change. The storefront then serves the correct language based on the customer's active locale.
A single Shopify store with Shopify Markets shows one currency per customer session, determined by the customer's market. The store does not display multiple currencies on the same page simultaneously, as this would create checkout inconsistencies. What Shopify Markets does is ensure each customer sees the correct currency for their market throughout their entire session: browsing, cart, and checkout all display the same currency. A customer in Saudi Arabia sees SAR; a customer in Qatar sees QAR; a customer elsewhere sees the relevant market currency or a fallback.
A Shopify Diagnostic for a Qatar store covers RTL implementation quality across all sections and app blocks, bilingual content architecture, payment gateway configuration, Shopify Markets currency setup, app stack performance impact, and analytics accuracy. The output is a written report with specific findings, prioritised by impact, and a recommended scope of work. The diagnostic takes approximately five to seven business days and does not require any commitment to proceed with development.
Not a black box. Real specialists you can call, with their names on the work.
A Shopify Diagnostic is a structured audit of your current or planned store covering RTL implementation, bilingual content architecture, payment gateway configuration, Shopify Markets multi-currency setup, app stack, and analytics. The output is a written report with prioritised findings and a clear scope of work. There is no commitment beyond the diagnostic itself.
Ignited Nepal
Growth engineering · replies within 1 business day
By continuing you agree to our privacy policy.
