E-commerce development across Jordan, Saudi Arabia & the GCC

Custom, Arabic-first commerce for one market or several. Payment rails, courier automation and the invoicing and compliance controls are scoped only once three things are confirmed: which routes the merchant is eligible for, which provider access exists, and which obligations apply.

Discovery first · dependencies documented · delivery plan confirmed after access review.

Quick answer

What decides how a regional e-commerce store gets built?

Payment and invoicing rails decide a Gulf store's build more than its theme does. Selling into Saudi Arabia means mada acceptance and ZATCA-compliant e-invoicing from launch, not as a later retrofit, and each additional market adds its own courier and tax obligations on top. Ijjad builds custom, Arabic-first e-commerce sites for SMEs, founders and multi-country retailers across Jordan, Saudi Arabia, Iraq and the GCC. Integrations are selected after discovery and depend on merchant eligibility, provider coverage, approved accounts and technical access.

  • Payment routes selected from buyer demand, merchant eligibility, and provider access.
  • Tax and invoicing requirements validated with qualified advisers before implementation.
  • Custom stack only: Next.js storefronts with purpose-built checkout, CMS, payment, and operations integrations.
  • Staging and acceptance tests defined around the provider environments actually available.

Custom scope decision

Which build path fits which retailer

Pick by scale, integration depth, and country. Ijjad only delivers the custom-build paths.

Build pathBest forSKUsMada / STC PayZATCA Phase 2Ijjad delivery scope
Salla / Zid hosted storeMerchants who need a hosted platform and can work within templates<1,000Platform settingsPlatform settingsNo
Shopify / WooCommerceMerchants who want a hosted or plugin-based platform<2,000App or pluginApp or pluginNo
Custom Next.js commerceBrands needing custom UX, performance, SEO, and checkout controlAnyAfter provider accessIf applicableYes, scoped
Custom marketplace / B2B systemMulti-vendor, wholesale, ERP-heavy, or unusual workflowsAnyAfter provider accessIf applicableYes, scoped

E-commerce results

First-party, anonymized project figures reported by Ijjad. Client identities and underlying analytics are not public; the linked cases explain the project context and method.

E-commerce scope tiers

Pick the tier that matches your catalog and market mix

Final scope and dependencies are documented before integration work begins; provider production approval remains outside Ijjad's control.

Starter store

SMEs launching their first online store across one market.

After scope review

Confirmed after discovery

  • Up to 50 SKUs
  • One eligible payment route or COD workflow
  • Arabic-first checkout
  • Order management
  • One supported courier workflow
  • Mobile-first responsive
  • Multi-vendor
  • ERP integration
Get Started
Most popular

Mid-market

Established retailers across Jordan, Saudi Arabia, or Iraq.

After scope review

Confirmed after access review

  • Up to 500 SKUs
  • Eligible payment routes confirmed in discovery
  • Supported courier integrations
  • Scoped retention workflow
  • GA4 + e-commerce events
  • Applicable Saudi invoicing controls
Get Started

B2B / multi-vendor

Marketplaces, B2B catalogs, distributor portals.

After scope review

10-16 weeks

  • Up to 5000 SKUs
  • Vendor onboarding + dashboards
  • Per-vendor commission rules
  • B2B price tiers + bulk pricing
  • Custom inventory & warehouse logic
Get Started

Enterprise

Regulated enterprises and multi-region GCC retail.

After scope review

Confirmed after discovery

  • Multi-region storefront
  • Hosting selected for approved requirements
  • ERP / WMS integration where access permits
  • Privacy controls mapped with qualified advisers
  • Headless storefront (Saleor / Medusa)
  • Support plan agreed in scope
Get Started

Every tier includes Arabic + English with RTL parity, mobile-first checkout, GA4 + e-commerce events, and 30 days post-launch monitoring.

The Enterprise tier above is where a decoupled storefront usually comes up. If you are weighing that decision for a Riyadh or wider Saudi store, the platform-by-platform comparison and the custom-build scope live on their own page: headless commerce development for Riyadh and Saudi retailers. It sets hosted platforms (Shopify Plus, Salla), open-source engines (Saleor, Medusa) and a custom Next.js build against Mada, STC Pay and ZATCA Phase 2.

How we ship stores

From catalog to a tested launch workflow

Provider access, staging availability, acceptance scenarios, and manual fallbacks are confirmed in the delivery plan.

  1. 1

    Discovery + catalog audit

    3-5 days

    We map catalog scale, target markets, payment rails (Mada / STC Pay / Tabby / ZainCash / COD), and ERP/courier integrations. If you have an existing store, we audit the catalog data quality first.

    Deliverable: Discovery doc + 24-hour proposal.

  2. 2

    Architecture + design

    1-2 weeks

    Custom architecture, design tokens, Arabic-first checkout UX, and per-country trust signals. Hosted platforms are not part of Ijjad delivery scope.

    Deliverable: Architecture plan + approved design.

  3. 3

    Build + provider integration

    Confirmed after access review

    Build the catalog, the checkout and the admin, then only those payment, invoicing, courier or operations integrations approved in discovery. Provider onboarding is a tracked dependency, and so is everything it produces before build can finish: the credentials, the documentation, the test environments.

    Deliverable: Preview builds plus an agreed staging environment.

  4. 4

    QA + acceptance

    Defined in the delivery plan

    Test the agreed scenarios in whatever provider environments are available: checkout, invoicing, refunds, failure cases, courier hand-off and reconciliation. Provider certification or production approval remains controlled by that provider and is not promised by Ijjad.

    Deliverable: QA evidence, known limitations, and client acceptance record.

  5. 5

    Launch + 30-day ops

    1 week + ongoing

    DNS cutover, GA4 + e-commerce events live, daily WhatsApp during first 2 weeks, 30-day post-launch conversion baseline. Optional growth retainer stacks on top.

    Deliverable: Live store + 30-day delta report.

Typical end-to-end timeline: Confirmed after discovery and provider-access review

First-party testimonials

What retailers say after launch

These anonymized quotes are published by Ijjad. They are not native reviews from Google, Clutch, or another independent platform.

“Ijjad replaced an unclear website with a focused experience that gives prospects a much clearer path to contact us. The team understood our regional market and kept the work tied to the business goal.”
Business Owner, Riyadh
“We needed a website and mobile app on a tight scope. Ijjad gave us a practical plan that made sense for a startup, and Karam stayed directly involved through the important decisions.”
Startup Founder, Amman
“Ijjad rebuilt the storefront around Mada checkout and a mobile-first customer flow. The result is easier for our team to manage and clearer for customers to use.”
E-Commerce Manager, Jeddah
“We launched our online catalog with cash-on-delivery and ZainCash in one checkout. The reconciliation dashboard gives our team a clearer way to manage orders, and the Arabic checkout feels native rather than translated.”
Retail Founder, Baghdad
“The trilingual MVP treated Sorani Kurdish as a first-class language from the start rather than an afterthought. Ijjad also kept the page weight small for customers accessing it outside Iraq.”
SaaS Founder, Erbil
“We needed governorate-level shipping rules, RFP-friendly service pages, and a site that loads well on mobile connections in southern Iraq. Ijjad delivered those requirements and walked our team through the cash-on-delivery operations before launch.”
Logistics Operator, Basra

FAQ

E-commerce — the questions retailers actually ask

Which e-commerce stack does Ijjad build?

Ijjad only builds custom e-commerce websites and custom e-commerce systems. We do not build or configure Salla, Zid, Shopify, or WooCommerce stores. Hosted platforms can be useful for some merchants, but Ijjad is the fit when performance, ownership, SEO, checkout control, and integrations matter.

Can the store accept Mada and STC Pay, offer Tabby and Tamara installments, and issue ZATCA-compliant invoices?

Those payment and invoicing flows can be scoped when they fit the merchant and market. Delivery depends on merchant eligibility, provider coverage, approved accounts, documentation, credentials, sandbox access, and the applicable tax and invoicing requirements. The merchant should validate legal and tax obligations with qualified advisers; Ijjad implements the approved technical requirements.

What about ZainCash, FastPay, COD for Iraqi e-commerce?

Whether a store offers wallets, cards, cash on delivery or a mix of them depends on buyer demand, merchant eligibility, provider availability, settlement requirements and courier operations. A named provider or real-time automation is included only after we confirm its current coverage, its API, and the credentials plus test access it needs.

How long does an e-commerce build take?

Timeline depends on the size of the catalog and any migration work, on which checkout and payment providers are involved, and on the shipping rules of each market together with its tax and invoicing requirements. Integrations and additional languages add time. So do late content, the test cycle and the approvals. Rather than promising a date from SKU count alone, the proposal should set out milestones, preview cadence, who owns staging, the named dependencies and the acceptance checks.

How does this page differ from the country-specific e-commerce pages?

This page is the multi-market hub. The Saudi page covers local checkout and invoicing dependencies, the Jordan page covers local and regional payment and courier access, and the Iraq page provides a payment-route discovery matrix. Use the country page when the launch is single-market.

Can you build a multi-vendor marketplace?

Yes, when discovery supports a custom marketplace. Scope can include vendor onboarding, commission rules, dashboards, customer-facing vendor pages and order routing, along with catalog governance, dispute handling and settlement logic. The architecture follows from the catalog, the operating model, the integrations, the risk profile and the ownership requirements.

What about post-launch — cart abandonment, retention, ad campaigns?

Abandoned-cart recovery, email or SMS journeys, and loyalty and retention workflows are added only when they fit the scope, the consent requirements, provider access and the operating plan. Paid media is handled by specialist partners; Ijjad focuses on the storefront and measured on-site journey.

Do you handle inventory, warehouse management and logistics integrations?

Yes, when discovery supports them and the merchant or provider can supply suitable documentation with the credentials, sample data and test access we need. What an ERP, a warehouse system or a courier can actually do varies by account and by geography, so rates, labels, tracking, returns, inventory sync and the manual fallbacks are confirmed before any integration is promised.

Ready to start selling online?

Start with discovery, provider-access review, and a custom scope with named dependencies.