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

Custom storefronts for retailers who need control over checkout and order operations. We design the buying journey around your catalog, then build the agreed payment and fulfilment workflows for your markets.

Share your current store or launch brief. We'll clarify fit and provider access before proposing a build.

Quick answer

When is a custom e-commerce build a good fit?

Consider custom development when your required checkout or operating workflow cannot be handled well by your current store. Start with the workflow that needs to change: wholesale ordering, vendor roles, a tailored buying journey or an integration. Ijjad scopes a custom build around those requirements. A standard store does not need custom development just because its catalog is growing.

  • 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.

Start with the work your store needs to do

Choose the situation closest to yours. These are starting points for a conversation; the proposal defines what is included.

Launch a custom store

You have a product range and need a buying journey shaped around how your business sells.

Define product discovery through checkout, then how your team will manage orders. Confirm the content and provider access needed for launch.

Useful to share: Your catalog or sample products, target markets and who will fulfil orders.

Rebuild an existing store

Your current platform or checkout limits how your business needs to sell.

Review the current buying journey before deciding what to rebuild as a custom store. Map migration needs and the search URLs that must be preserved.

Useful to share: Your store URL, the problem to solve and any available checkout or order data.

Build B2B or marketplace workflows

Your sales model needs wholesale ordering, buyer approvals or several vendors.

Map buyer and vendor roles, pricing rules and order handling. Confirm inventory and settlement dependencies before committing to integrations.

Useful to share: A sample order from start to finish, the people involved and systems it touches.

Know what you are agreeing to before the build

The proposal records the critical customer flows and integration dependencies. It also sets acceptance checks, ownership and handover, with support boundaries and responsibilities agreed before work begins.

A store URL or a short launch brief is enough to start. Add the workflow you need to change; you do not need a finished technical specification.

Get Started

Custom scope decision

Which build path fits which retailer

Compare your required buying and operating workflow with what an existing platform supports. Ijjad delivers the custom-build paths.

Build pathBest forMada / STC PayZATCA Phase 2Ijjad delivery scope
Salla / Zid hosted storeMerchants whose required buying flow fits the platformCheck provider coverageCheck applicable requirementsNot an Ijjad service
Shopify / WooCommerceMerchants whose required workflow fits the platform and available extensionsCheck provider coverageCheck applicable requirementsNot an Ijjad service
Custom Next.js commerceRetailers needing a tailored storefront or checkout workflowAfter provider accessIf applicableCustom scope
Custom marketplace / B2B systemWholesale or vendor workflows with distinct operating rulesAfter provider accessIf applicableCustom scope

Related first-party work

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.

If you are considering a decoupled storefront and 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

    Defined after the initial review

    Review the catalog and target markets alongside the buying journey. For an existing store, identify what needs to change and what must survive a migration.

    Deliverable: Written scope, dependencies and proposed milestones.

  2. 2

    Architecture + design

    Defined in the proposal

    Design the agreed storefront and checkout flows, including Arabic and English where required. Review those flows before development.

    Deliverable: Architecture plan and approved designs.

  3. 3

    Build + provider integration

    Confirmed after access review

    Build the agreed catalog, checkout and admin workflows. Integrations require approved provider accounts and suitable technical access.

    Deliverable: Preview builds plus an agreed staging environment.

  4. 4

    QA + acceptance

    Defined in the delivery plan

    Test the agreed checkout and order scenarios in available provider environments. Record limitations and untested scenarios before acceptance. Production approval remains with the provider.

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

  5. 5

    Launch + handover

    Defined in the proposal

    Agree the launch checks and account handover. Document who operates the store, what support covers and how post-launch performance will be reviewed.

    Deliverable: Handover record and agreed support plan.

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

First-party testimonials

First-party client accounts

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. The proposal sets milestones and preview cadence, identifies who owns staging, and records dependencies and acceptance checks. SKU count alone does not set the schedule.

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.

Let's scope the next step for your store

Send your store URL or launch brief and tell us what customers or your team need to do differently.

In an anonymized first-party Jeddah case, Ijjad describes a mobile storefront and checkout rebuild. Read the approach and reported results. The underlying client analytics are private.