Plexi builds Shopify stores for Dubai and UAE businesses from a blank canvas — designed on Shopify’s Online Store 2.0 architecture, wired to the payment methods local shoppers actually reach for, and bilingual where the audience is Arabic-speaking. We do not drop a premium theme on a brief and hand it back; the store is engineered to sell in this market specifically.
If you are still weighing Shopify against WooCommerce and Magento, that comparison lives on the e-commerce development pillar. Here we take the platform as settled and get practical about the decisions that make or break a UAE Shopify store: the plan tier that matches your volume, a payment stack wired to how local shoppers actually check out, an Arabic layer built on Shopify Markets rather than a translation plugin, and an Online Store 2.0 theme your team can run without a developer on call.
Choosing the right Shopify plan for a UAE store
The plan you launch on is a cost and capability decision, not an afterthought. Every tier runs the same checkout and the same app ecosystem; what changes between them is the transaction-fee level, the number of staff accounts, reporting depth, and — at the top — how far you can rewrite the checkout itself.
| Tier | What changes at this level | Typical UAE fit |
|---|---|---|
| Basic | Full store, custom theme, every UAE payment app, one market | New D2C brands validating a catalogue and demand |
| Standard / Grow | Lower card rates, more staff accounts, standard reporting | Growing stores adding team members and campaigns |
| Advanced | Lowest non-Plus transaction fees, advanced reports, third-party calculated shipping | Higher-volume stores needing shipping logic and analytics |
| Plus | Checkout customisation (Checkout Extensibility), B2B wholesale, higher API limits, Shopify Functions | High-GMV, combined B2B+DTC, or bespoke-checkout brands |
Working steer: launch a tier lower than instinct suggests and move up on evidence, because upgrades are instant and downgrades are painless. The jump to Plus earns its higher floor when order volume is large enough that its reduced transaction fees offset the platform cost, when you need checkout logic the standard editor cannot express, or when you sell wholesale and retail from one catalogue. We pressure-test that threshold against your real numbers rather than default anyone onto Plus — the pricing guide sets out how the engagement is structured.
The UAE payment stack on Shopify
This is where a Dubai Shopify build succeeds or quietly leaks revenue. A store that cannot present a familiar card screen, Tabby, and Tamara loses orders it never sees. Here is how the pieces actually fit on Shopify.
| Method | What it is on Shopify | When we reach for it |
|---|---|---|
| Shopify Payments | Native card processing, no third-party gateway fee | Where enabled on the account — simplest, lowest-fee card route |
| PayTabs / Telr | Local UAE acquirers as third-party gateways | When Shopify Payments is unavailable or a local acquirer is preferred |
| Stripe / Checkout.com | International card gateways | Cross-border selling and multi-currency card capture |
| Network International | Regional acquiring | Merchants already banked on an NI relationship |
| Tabby | BNPL — pay in 4 instalments | Fashion, electronics, home; shown on product and cart |
| Tamara | BNPL — pay in 3 or pay in 30 days | Same categories; widens buyer eligibility alongside Tabby |
| Cash on delivery | Offline payment, still widely expected in the UAE | Configured with app-level gating on cart value and emirate |
Two Shopify-specific traps that catch generic builds. First, cash on delivery is not a simple switch — Shopify’s checkout does not natively gate COD by cart value, emirate, or product weight, so we add app logic or checkout rules to keep COD off high-value or hard-to-reach orders where it invites failed deliveries and fraud. Second, BNPL is a theme feature, not just a checkout button: Tabby and Tamara each ship an official Shopify app whose app blocks slot into Online Store 2.0 product and cart templates, so the instalment breakdown renders natively instead of as a bolted-on script. Why that on-store placement drives the conversion lift — and how the gateway work carries across platforms — is set out in our payment gateway integration service.
Bilingual selling with Shopify Markets
A properly built Arabic storefront is a structural decision, not a translation plugin. We use Shopify Markets and locales to run Arabic and English as first-class experiences: each language gets its own indexable URL space with correct hreflang, theme strings and product content are translated and adapted per locale, and the right-to-left behaviour is written into the theme’s locale itself — navigation order, iconography, and Arabic typography set in the Liquid and CSS that render the ar locale, not switched on with a single global flag.
The SEO half of that is owned by our e-commerce SEO team, not the theme build: which Arabic terms UAE shoppers actually reach for, and how the hreflang pairs are structured, is planned into the first content model so the Arabic pages compete on their own terms in Google UAE. Retrofitting that layer after launch means re-crawling, re-indexing, and lost time.
Custom theme architecture on Online Store 2.0
Online Store 2.0 is what makes a Shopify build maintainable after handover, and it is where a considered theme separates from a marketplace template. We build with:
- Sections and blocks on every template, so marketing can reorder, add, and remove content on any page — not just the homepage — from the theme editor.
- JSON templates that keep layout data out of the code and let non-developers restructure pages safely.
- Metafields and metaobjects for structured product data — size charts, ingredient tables, spec sheets, warranty terms — rendered natively instead of pasted into description HTML.
- App blocks so third-party features drop into defined slots and can be removed cleanly, which keeps the store from accumulating orphaned scripts over time.
The payoff is operational independence: your team runs day-to-day merchandising, campaigns, and content without a developer ticket, and the theme stays clean enough that the next feature is cheap to add rather than a rebuild.
Keeping a Shopify store fast
Shopify hosts on its own CDN and serves images through transform parameters that deliver correctly sized WebP automatically — a strong baseline most stores then squander by stacking apps. Every app that injects JavaScript into the storefront is a tax on your Core Web Vitals, so we audit each addition against its Lighthouse impact before it ships, defer or lazy-load what is not needed on first paint, and prefer native theme features over an app wherever the trade is even.
Product, breadcrumb, and organisation schema go into the theme so rich results are available from launch, not retrofitted. A fast, well-marked-up store is the groundwork that lets SEO compound instead of fighting a slow storefront.
Migrating to Shopify
Moving from WooCommerce, Magento, or a custom system, the data itself — products, variants, collections, customers, and order history — is the routine part; apps and integrations then get re-pointed to the new store rather than assumed to carry over. The Shopify-specific catch is its fixed /products/ and /collections/ URL structure, which rarely maps one-to-one to the source platform, so the old-to-new redirect map is where the organic risk concentrates and where the work has to be exact.
We hand that redirect-and-reindex methodology — the full crawl, the URL mapping, staged 301s tested before cutover, and post-launch index monitoring — to the team that owns it end to end: our e-commerce SEO practice runs the same playbook on every platform migration. Where a store genuinely needs more custom checkout or pricing logic than Shopify allows, WooCommerce or Magento / Adobe Commerce may be the better destination, and we will say so before you commit.
The app stack we run for UAE stores
The Shopify app store runs to thousands of apps; the skill is restraint. We configure a lean stack that covers the business need without dragging the storefront down — typically email and SMS automation (Klaviyo), reviews (Judge.me or Loox), loyalty and referrals (Smile.io), shipping rates and rules (Intuitive Shipping or Parcelify), and returns management, alongside the Tabby, Tamara, and gateway apps above. Each one is justified by a job it does better than the theme could, and each is measured against store speed before it goes live.
Start your Shopify build
Whether this is a first D2C launch, a move off WooCommerce or Magento, or a step up toward Shopify Plus, the answer turns on your catalogue, your payment mix, and whether Arabic is part of the audience. Send us your current store URL — or the catalogue you plan to launch — and the plan tier you are weighing, and start your Shopify build with us; we will tell you which tier and theme approach actually fit. The pricing guide shows what sits inside a themed launch versus a custom bilingual build with a migration.