What's new
Chat on WhatsApp
Toggle Nav
My Cart
Magento Developer · United Arab Emirates

Magento developer in the UAE

I’m Kishan, an Adobe Certified Magento developer for stores in the UAE, working from Ahmedabad, India, just 1h30 ahead of Gulf time. A UAE store has to work in Arabic and English, right to left and left to right, and it has to handle cash on delivery, Tabby or Tamara, and addresses without postcodes. Those details are where I spend most of my time on a UAE build.

  • Arabic store view that is truly right to left, not just translated
  • Cards, Apple Pay, Tabby, Tamara and cash on delivery on one checkout
  • 5% VAT and TRN on invoices for your business customers
Reserve my slot See pricing
Free 30-minute call first Daily review at 12:00 Gulf time Quote in AED on request
  • Tabby and Tamara Split payments

    Many UAE shoppers split a payment into four with Tabby or Tamara. I put their widgets on product and cart pages with the right instalment amount, and test the refund flow back to both.

  • Arabic and English Two directions

    An Arabic store view has to flip the whole layout right to left: menus, sliders, price and quantity boxes, even arrow icons. I build both directions from the same theme, with an Arabic web font like Cairo or Tajawal.

  • PDPL UAE data law

    The federal PDPL (Decree-Law 45 of 2021) covers most mainland companies. If you are licensed in DIFC or ADGM, their own data protection rules apply instead, and I set consent and data requests up to match.

  • 1h30 Gulf time to Ahmedabad

    Neither country changes its clocks, so the gap stays 1h30 all year. 9:00 in the UAE is 10:30 for me, and 17:00 is 18:30. Your full working day sits inside mine.

What you get

Six things a UAE Magento store actually needs

Most of these are small on paper and annoying in real life: a broken Arabic menu, a BNPL widget that shows the wrong amount, an address form asking for a postcode nobody has. Here is what I fix and set up.

  • Card gateway that fits your licence

    I connect the gateway your bank or licence suits best: Telr, Network International, Amazon Payment Services (the old PayFort) or Checkout.com, with Apple Pay on top. If you also sell to Saudi Arabia, I add mada cards for those customers.

  • Cash on delivery, done properly

    COD is still common in the UAE, and it is also where most failed deliveries come from. I add OTP confirmation for COD orders, an optional COD fee, and limits per order value, so couriers do not drive to unconfirmed addresses.

  • Addresses without postcodes

    The UAE has no postcode system, yet default Magento asks for one. I replace it with emirate, area and building fields, plus a landmark or map pin, which is what Aramex, Emirates Post and local courier apps actually need.

  • 5% VAT and TRN on invoices

    VAT is 5% on most goods. Business customers want your TRN and theirs on the tax invoice, so I add a TRN field at checkout and an invoice template that matches FTA rules. E-invoicing is being phased in for UAE businesses, and I keep invoice data ready for it.

  • Arabic SEO that matches the English

    Each product gets an Arabic URL key, title and description, and hreflang links between the ar and en versions, so Google shows Arabic speakers the Arabic page instead of the English one.

  • Selling into the wider Gulf

    Plenty of UAE stores grow into Saudi Arabia, Oman or Qatar next. I set up extra store views, currencies and shipping rules in the same Magento install, so you do not need a second site for each country.

How it works

Five steps from booking to live: on Gulf time

With only 1h30 between us, we share nearly the whole working day: 9:00 in the UAE is 10:30 for me, all year round. I send a staging review at 12:00 Gulf time from day three, and the go-live runs around 3:00 at night, when UAE traffic is at its lowest.

  1. 01

    Audit

    Free 30-min audit of your UAE store, payment rails, VAT + TRN setup, Arabic RTL readiness, PDPL exposure, Aramex / last-mile rules. Booked in a GST-friendly slot.

    Day 1
  2. 02

    Quote

    Fixed-price written quote in USD with an AED equivalent on request. Reserved start date, risk register, written project plan. You sign, we book.

    Day 2
  3. 03

    Build

    Daily review around 12:00 Gulf time, 13:30 for me. Staging access from day 3 with a test cart that uses a real UAE address format, no postcode.

    Days 3-14
  4. 04

    Deploy

    Blue-green cutover scheduled for off-peak (3 AM GST typical, lowest UAE traffic). Old release stays warm 72 hours so rollback is one DNS flip away.

    Launch night
  5. 05

    Stabilise

    14 days of post-launch coverage in GST business hours. Anything that breaks because of the cutover gets fixed at no extra charge.

    Days 14-28
Pricing

Fixed prices in USD. AED equivalent on request.

Pick the tier that matches your UAE store. Anything out of scope after the audit gets quoted upfront, never billed silently.

  • Express

    $ 1,499 USD

    5-7 days · ~AED 5,500 equivalent

    Best for: Telr / PayFort / Network International setup, single-version Magento upgrade, or a one-off fix on a UAE store

    • Pre-project audit + UAE-specific compatibility report
    • Telr or PayFort or Network International gateway integration
    • Single Magento minor-version upgrade (e.g. 2.4.7 → 2.4.8)
    • PDPL + cookie banner audit (DIFC / ADGM-aware)
    • Blue-green deploy + 7 days post-launch coverage
    • AED-quote-on-request, pay in AED or USD
    Reserve Express slot
  • Most popular

    Standard

    $ 3,499 USD

    10-14 days · ~AED 12,850, most popular

    Best for: Arabic RTL storefront + Hyvä migration, Tabby/Tamara BNPL, mainland-vs-free-zone tax, or B2B Net-30 with TRN gating

    • Everything in Express, plus:
    • Native Arabic RTL Magento storefront with EN fallback
    • Hyvä theme migration or Luma redesign (Dubai luxury / fashion optimised)
    • Tabby + Tamara BNPL integrated (PDP + cart + checkout widgets)
    • Aramex + Quiqup + Emirates Post integration with same-day Dubai rules
    • B2B with TRN-validation + Net-30 + Mainland vs Free-Zone tax flow
    • 14 days post-launch coverage in GST business hours
    Reserve Standard slot

  • Enterprise

    Custom

    4-8 weeks · scoped to your luxury / multi-emirate stack

    Best for: Luxury / jewellery DTC, multi-emirate logistics, mainland-vs-free-zone tax architecture, KSA expansion

    • Everything in Standard, plus:
    • Multi-region UAE + KSA split (separate storefronts, shared catalogue)
    • Mainland Trade Licence vs Free-Zone (DMCC / JAFZA / DIFC) tax architecture
    • Deploy in the AWS UAE region or on Adobe Commerce Cloud
    • PDPL DPO retainer + DSAR automation across both regions
    • Mada cross-border + Arabic-first checkout for KSA buyers
    • 30 days post-launch coverage + GST-aligned retainer option
    Get UAE Enterprise quote

Prices in USD. AED equivalent (~AED 5,500 / AED 12,850) shown for reference at current FX. Pay in AED via wire / Wise / Telr: ask in the booking form. UAE VAT not charged on B2B exports of services to UAE companies (reverse charge applies with valid TRN).

Book your slot

Reserve your UAE Magento project slot

The form takes about two minutes. I reply with a written quote within 24 business hours, usually the same day given how close our time zones are.

Message me on WhatsApp

No form to fill. Send me a quick message and I reply within 4 hours on IST working days, often sooner.

Helpful to mention

  • Company
  • Store URL
  • Magento version
  • Emirate
  • Do you have a TRN (Tax Registration Number)
  • Licence type

These are already in the message for you. Just add your answers.

Message me on WhatsApp

Or save my number: +91 84012 70422

What clients say

What clients say about working with me

Reviews from clients on Upwork, Clutch and LinkedIn, across different countries and store sizes.

Real good guy.

“Real good guy. Where others quoted 10 hours minimum, he did it within 3. All very neat, clear secure and great communication. A+

PV

Pieter Van Hees

Business Branding

As an American, I was hesitant to hire someone from a different country and culture.

“As an American, I was hesitant to hire someone from a different country and culture. Kishan changed my mind. He was very cooperative, easy to work with, and is very bright. He gets things done fast and efficiently, and is available when needed. His English is excellent and is...

DS

Danielle Siso

Kishan knows Magento very well.

“Kishan knows Magento very well. Our project is finished and I'll hire him again for next

HH

Hammad Hassan

This freelancer is the best i've used at Magento.

“This freelancer is the best i've used at Magento. Absolutley brilliant at what they do. Would have no hesitation in recommending them

PS

Peter Stewart

CEO, No79 Design

Kishan is very talented in what he does.

“Kishan is very talented in what he does. He helped me troubleshooting and redirecting a website, and also gave me tips on how to handle future issues. Will definitely work with him

OT

Omar Turmen

Oksygen

Kishan did great job - everything as expected!

“Kishan did great job - everything as expected! I would definitely recommend

JM

Jan Mucic

CEO

Other countries I build Magento stores for

  • United States
  • United Kingdom
  • Canada
  • Australia
  • Germany
  • France
  • Netherlands
  • India
FAQ

Twelve UAE-specific questions, honestly answered

How do I integrate Telr / PayFort / Network International with Magento?

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.

How do I set up an Arabic RTL Magento storefront?

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.

What’s PDPL and how does it differ from GDPR?

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.

How does Tabby / Tamara BNPL integration work in Magento?

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.

What’s the difference between Mainland and Free-Zone licensing for tax?

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
How do I validate TRN for B2B customers in Magento?

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.

What’s the best hosting for UAE Magento, AWS Bahrain or Etisalat Cloud?

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.

Should I add Hindi / Urdu / Tagalog for expat-segment Magento?

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.

How do I integrate Aramex / Quiqup / Careem for Dubai same-day delivery?

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.

What time-zone overlap can I expect working with you from India?

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.

Can I expand my UAE Magento store to KSA / Saudi Arabia?

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
Should I migrate to Hyvä for my Dubai luxury / jewellery store?

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.