Magento Developer UAE: 12 questions answered.

A proper Arabic Magento store needs more than just translating strings:

1. RTL stylesheets, Magento 2 ships native RTL support via direction: rtl + a separate i18n.csv per locale. We flip the entire layout, mirror icons, swap left/right margins programmatically.
2. Arabic-friendly fonts, Cairo or Tahoma for body, Almarai or IBM Plex Sans Arabic for headings. Subset to Arabic glyphs to keep page weight down.
3. Numerals, CSS font-feature-settings: "tnum" for prices; many UAE shoppers prefer Arabic-Indic numerals (٠١٢٣٤٥٦٧٨٩) on PDP, Western numerals on checkout.
4. Currency placement, د.إ 1,250 (right-side AED symbol) is standard.
5. Locale-aware structured data, hreflang ar-AE + ar-SA, JSON-LD inLanguage: "ar", OG locale ar_AE.

Ships natively in Hyvä Themes, Hyvä has first-class Tailwind RTL support.

Most Dubai DTC stores need 2-3 carriers for cost + speed coverage:

• Aramex, UAE-founded, regional leader. Native Magento 2 module. Best for cross-emirate + GCC export. Domestic same-day across all 7 emirates standard.
• Emirates Post, cheapest for low-value (< AED 50). Slower but reliable. Direct API.
• Quiqup, Dubai-founded same-hour delivery. Best for restaurants, pharmacies, urgent fashion. API integration via Magento custom module.
• Careem, ride-hailing-turned-logistics. Careem Box = scheduled, Careem NOW = food delivery. Magento integration via Careem Logistics API.
• Fetchr, tech-forward UAE delivery, cash-on-delivery + GPS-pinpoint addressing (good in areas without street numbers).
• DHL Middle East, international + premium domestic.

We wire these via ShipperHQ (rule engine) or direct Magento modules, same-hour for Dubai, same-day for Abu Dhabi/Sharjah, next-day for Northern Emirates.

Depends on volume + data-residency requirements:

• AWS Bahrain (me-south-1), AWS’s only Middle East region until 2024. ~20-40ms latency to Dubai/Abu Dhabi. Best for > AED 5M stores with auto-scaling needs. Magento Marketplace recommends AWS. Pay in USD.
• Etisalat / e& Cloud, UAE-domestic, data stays in UAE (good for federal contracts requiring local data residency). Slightly higher latency variance but no cross-border bandwidth costs. Pay in AED, local invoice with TRN.
• Du Cloud, Du’s competitive offering, similar to e&.
• Microsoft Azure UAE Central / North, in-country regions launched 2019. Good for enterprises already on Microsoft 365 / Dynamics.
• Adobe Commerce Cloud, Frankfurt region with Bahrain Fastly edge, 30-50ms to UAE. Good if you’re on Adobe Commerce.

For most UAE stores AED 1-10M revenue, Cloudways / Hyvä Cloud + Bahrain edge is the right balance.

UAE has ~89% expat population, Indians ~38%, Pakistanis ~13%, Filipinos ~7%. Whether you add their languages depends on your category:

• Yes, FMCG / groceries / mobile recharge / remittance / household services. Hindi + Urdu + Tagalog massively reduce drop-off for these segments.
• Maybe, fashion / lifestyle / electronics. AR + EN usually enough; Hindi can help on Carrefour-tier mass retail.
• No, luxury / jewellery / B2B / government. AR + EN cover > 95% of buying decision-makers.

Magento handles 4+ language stores cleanly via store-views with shared catalogue:

1. One website, four store_views (ar_AE / en_US / hi_IN / tl_PH).
2. Language-switcher in header with flag + native script (English / العربية / हिन्दी / Filipino).
3. One PIM, four sets of attribute translations.
4. hreflang strip linking all four for SEO.

Hyvä supports this out-of-the-box.

Almost certainly yes if you’re on Luma. Dubai luxury + jewellery shoppers convert dramatically better on fast image-rich stores:

• Lighthouse 95+ on Hyvä vs typically 35-55 on Luma luxury themes (heavy gallery + zoom JS), Google ranks fast pages higher for “jewellery dubai” / “watches dubai” queries.
• Hyvä Checkout loads in < 1s, 50% lower bounce vs Magento Luma checkout, especially mobile (which is > 70% of UAE traffic).
• Native Arabic RTL, Tailwind RTL works flawlessly out-of-the-box. Luma RTL needs heavy custom CSS.
• Tabby / Tamara widgets render natively without the React/jQuery double-render Luma has.
• High-res PDP galleries with lazy-loaded WebP/AVIF, critical for jewellery zoom & 360-spin without killing mobile data.

Typical migration timeline: 4-6 weeks. Conversion lift in the first 90 days post-launch is usually 8-25% from speed alone, then optimisation work compounds it. See our Hyvä service page for fixed-price tiers.

This drives Magento tax engine + invoicing setup:

• Mainland Trade Licence (issued by DED-Dubai or equivalent), full UAE market access, can sell anywhere in UAE without restriction. 5% VAT applies on B2C + B2B (with TRN reverse charge).
• Free-Zone licence (DMCC, JAFZA, DIFC, ADGM, SHAMS, RAKEZ, etc.), tax holiday on corporate income (originally 50 yr, now affected by 9% federal CT 2023+), but VAT still applies on UAE-mainland sales. Designated Zones (e.g. JAFZA Designated) may be VAT-free for cross-border B2B but mainland B2C still 5%.
• Offshore (JAFZA Offshore, RAK ICC), cannot sell into UAE mainland. Magento store typically used for international export only.

We model this in Magento with:

• Multiple tax classes (mainland B2C 5% / free-zone B2B 0% / export 0%)
• TRN-validated B2B reverse charge invoicing
• FTA-compliant tax invoice format with TRN, supply date, AED amount

UAE’s Personal Data Protection Law (PDPL) is Federal Decree-Law No. 45 of 2021, in force since January 2022. It’s GDPR-flavoured but with key UAE differences:

• Scope, PDPL applies to UAE-mainland processing. DIFC has its own DPL 2020 (more EU-aligned), and ADGM has its DPR 2021. Free-Zone stores fall under whichever zone’s rules.
• Consent + lawful basis, mandatory for personal data, similar to GDPR Article 6.
• DSAR rights, access, rectification, erasure, objection, same as GDPR.
• Cross-border transfers, allowed to “adequate” jurisdictions or with safeguards (similar to GDPR SCCs).
• No fixed fines yet, PDPL fines are determined per case (vs GDPR’s 4% global turnover cap), but Cybercrime law has separate criminal penalties.
• Mandatory DPO only above certain processing volumes, lighter than GDPR.

We configure Magento customer + sales_order retention rules, DSAR automation, cookie banner copy, and PDPL-aligned privacy policy.

Tabby and Tamara are essential for UAE DTC under-35, ~40% of UAE millennials expect a Pay-in-4 / Pay-Later option. Both have official Magento 2 modules:

• Tabby, founded in UAE/SA, biggest BNPL in MENA. Pay-in-4 (4 instalments, 0%) + Pay-Later (30 days). Strong Apple Pay integration. Higher fees (3.5-6%) but typically lifts AOV 30-50%.
• Tamara, KSA-founded, very strong in KSA + UAE. Pay-in-3 + Pay-in-4. Slightly cheaper than Tabby. Often the better pick for KSA cross-border.

We install, configure, and wire the on-site widgets:

1. PDP price-line widget (“Or 4 payments of AED X with Tabby”)
2. Cart-page widget
3. Checkout step with KYC redirect
4. Webhook for order confirmation + cancellation flow
5. Fallback to Telr/PayFort if Tabby is declined

Both run sandbox accounts for QA. Most UAE stores ship both BNPL providers as customer choice.

The three dominant UAE gateways each have a different integration flavour:

• Telr, UAE-founded (Dubai), strong AED + multi-currency support, hosted-page + JS-SDK both available. Official Magento 2 module on Telr’s GitHub. Best for SMEs that want a quick spin-up. Supports 3DS2 + Mada cross-border.
• PayFort (Amazon Payment Services), the regional Amazon-owned gateway, very common with mid-market UAE / KSA stores. Hosted checkout + merchant page + tokenization. Solid Magento 2 module + good fraud tools.
• Network International, the largest acquirer in the Middle East, best for established UAE retailers with bank-direct relationships. Direct API + 3DS2 + multi-currency. Slightly heavier integration but lowest MDR rates at scale.

We integrate any of them, many UAE stores run Telr + PayFort fallback + Tabby/Tamara as a multi-rail stack.

The best of any country we work with, 6-8 hours of working overlap, daily:

• India Standard Time = UTC+5:30
• UAE Gulf Standard Time = UTC+4 (no DST)
• UAE is just 1.5 hours behind IST.
• Overlap window: 9 AM, 5 PM IST = 7:30 AM, 3:30 PM GST, covers your entire UAE working day.

Daily 12 PM GST review on staging is the typical cadence (the Dubai lunch slot, ideal for 30-min syncs). Slack / WhatsApp async covers the rest. We’ve worked with Dubai, Abu Dhabi, Sharjah, and DIFC clients for years, the time-zone advantage means changes requested at 9 AM Dubai are typically deployed to staging by 2 PM Dubai the same day.

The TRN (Tax Registration Number) is the FTA-issued 15-digit number that’s required on all UAE B2B tax invoices. Validating it at checkout matters because:

1. An invalid TRN means the FTA rejects your tax invoice, you can’t reclaim input VAT.
2. Without TRN you can’t apply reverse-charge B2B treatment.
3. Customers with valid TRN often expect zero-VAT invoicing on cross-emirate B2B.

We add a trn field to the Magento customer entity + checkout, and validate via:

• FTA TRN Verify API (real-time, returns business name + status)
• Format validation (15 digits, starts with 100)
• Auto-set tax class to “B2B with TRN” on validation success
• Auto-emit FTA-compliant tax invoice with TRN, supply date, AED line totals, VAT-line breakdown

Invoice-template integration with Microsoft Dynamics / Zoho Books / Xero UAE for accounting reconciliation.

Yes, KSA is the natural expansion market. Three patterns:

• Single-store, geo-priced, one storefront with VAT calculated by destination (5% UAE / 15% KSA). Ships from UAE warehouse via Aramex cross-border. Cheapest, but checkout feels foreign to KSA buyers.
• Two storefronts, shared catalogue, store for UAE (AED, 5% VAT, FTA TRN) and store for KSA (SAR, 15% VAT, ZATCA-compliant invoicing, Mada-first checkout). One Magento backend. Most popular pattern.
• Two websites, two backends, legally separate UAE LLC + KSA LLC with separate licenses. Best for AED 50M+ stores. website-level split.

Key KSA differences:

• VAT 15% (vs UAE 5%) + ZATCA Phase 2 e-invoicing mandatory
• Mada debit-card scheme dominant (vs UAE Visa/MC)
• Tamara bigger than Tabby in KSA
• Arabic-first checkout, KSA buyers expect AR default, not EN