Best Headless Commerce Platforms for Riyadh & Saudi Retailers (2026 Guide)

A platform comparison should start with the work your store needs to do: sell the catalog, take payment and keep orders aligned with stock. A custom frontend is justified when a hosted storefront cannot meet an important requirement. Write down that requirement before paying for a headless build.

This is Ijjad's implementation-fit assessment, not a market-share ranking or a platform speed benchmark. Ijjad builds custom storefronts and integrations. Hosted platform setup is outside our delivery scope. The comparison includes those alternatives because a retailer may be better served by choosing one directly.

Six commerce options to compare for a Saudi store

These options include hosted platforms and custom architecture choices. Next.js is a frontend framework: it still needs a commerce backend and checkout. Treat each integration cell below as something to confirm for your merchant account and selected plan, not as a promise that a new store is ready to trade.

The facts this comparison rests on

Every item below was read on its primary source on 6 September 2026. Check each one against your own ZATCA notice, your plan and your merchant account before you commit budget.

• ZATCA Phase 1 (Generation) has applied since 4 December 2021 to resident taxpayers issuing tax invoices. Phase 2 (Integration) started on 1 January 2023 and rolls out in waves by taxpayer group, and ZATCA states it notifies each waveat least six months in advance (ZATCA roll-out phases).
• Wave 25 covers taxpayers whose VAT-taxable revenue exceeded SAR 187,500 in 2022, 2023, 2024 or 2025, and sets integration by 1 February 2027 (ZATCA announcement, 24 July 2026).
• Salla's direct ZATCA integration app is free, restricted to the Pro and Special plans, and available only to stores in Saudi Arabia. Activation needs a verified store, a complete default-branch address, an active ZATCA portal account, plus a one-time code thatexpires one hour after it is generated (Salla Help Center, updated 31 August 2026).
• Shopify charges nothing to connect a payment gateway and listsmore than 100 providers filterable by country, with each provider setting its own processing rates (Shopify payment gateways, Saudi Arabia). A plan-dependent Shopify transaction fee applies on top whenever the store uses a third-party provider (Shopify third-party provider documentation). Shopify Payments is not offered in every market, so check Shopify's supported-country list before assuming that route is open to a Saudi-registered store.
• Shopify's own headless stack is Hydrogen deployed on Oxygen. Hydrogen projects are React Router applications, and Oxygen is Shopify's serverless edge hosting (shopify.dev).
• BigCommerce puts company accounts, quotes, invoices, buyer approval workflows, a configure-price-quote tool, plus multi-company hierarchy with role-based access into its B2B Edition rather than every plan (BigCommerce B2B).

1. Shopify Plus: consider it for enterprise features and the app ecosystem

Start with the workflows you need from Shopify, then select the plan. A small catalog alone does not justify Plus. Ask for a working demonstration of the required checkout, app compatibility and order operations before choosing an enterprise contract.

For a custom storefront, Shopify documents Hydrogen and Oxygen as its recommended headless stack. Other frontends can use Shopify APIs. Moving the storefront does not move orders away from Shopify or automatically remove platform transaction fees.

Choose this route when keeping Shopify administration and checkout is an advantage and the team can maintain the frontend. Validate Arabic checkout and the selected Saudi payment methods on the actual merchant account.

2. Custom Next.js (headless) — best for differentiated brands

Choose a custom Next.js frontend when a hosted theme cannot deliver a required shopping experience. Pair it with a backend that meets the order workflow. That may be Saleor, Medusa or Shopify; the frontend framework alone does not supply payments or inventory management.

Where it can win: brand differentiation, page-specific performance budgets, control of checkout flow placement, and bilingual Arabic UX designed from the start. Final PageSpeed and field performance depend on content, integrations, hosting, device, and connection, so no universal score is promised.

The trade-off is ongoing engineering work. If a hosted storefront meets the requirements, spend on improving the catalog and testing checkout before commissioning a replacement.

This build shape can require a larger scope for the storefront, eligible Saudi payment integrations, and project-specific invoicing requirements. In an anonymized first-party Jeddah case, Ijjad reports a 340% conversion-rate lift, monthly orders moving from fewer than 10 to 200+, and mobile load time moving from 4.2s to 1.1s. Underlying analytics are private and the outcome is not a forecast. Read the case methodology.

3. Salla: start here for a hosted Saudi store

A hosted Saudi store is a sensible first option when the owner wants to manage products and orders without maintaining a custom frontend. Test the required catalog and fulfillment workflow in Salla before commissioning a headless build.

Integration is not the same as automatic readiness. Salla's ZATCA setup guide, checked 6 September 2026, limits its direct integration to Pro and Special plans. It requires app installation and activation, a verified store, completed branch details and an eligible ZATCA account. Confirm payment-method activation separately.

If you need an unusual ERP connection or a custom customer journey, ask for a demonstration before committing. A supported hosted workflow may be sufficient; an unmet requirement is the reason to compare custom options.

4. Saleor: compare it when the team wants an API-first commerce backend

Saleor's documentation describes a GraphQL commerce API with products, checkout, channels and extensibility. Assess it against your catalog relationships and the systems that must exchange order data. A custom storefront still needs implementation and ongoing maintenance.

Before estimating Saudi payments or invoicing, check whether a maintained integration supports the chosen provider and Saleor version. Identify who owns any missing integration, updates and failed-order recovery. Open source does not make that operational work free.

5. Medusa: compare it for a team building modular commerce workflows

Medusa is another candidate when a team needs to shape backend commerce workflows. Its payment-provider interface allows a provider integration to be implemented and configured. That extension point is not a ready Saudi payment contract.

Choose between Medusa and Saleor by implementing one difficult workflow in a small technical trial: for example, an order with a partial refund and a stock adjustment. Review the code your team will maintain before committing to either backend.

6. BigCommerce: compare B2B Edition for company purchasing workflows

BigCommerce B2B Edition is worth evaluating when business buyers need company accounts with quote and invoice workflows. Confirm the required edition and purchasing workflow rather than assuming those capabilities are included in every plan.

For a Saudi rollout, also demonstrate the selected payment provider, invoicing handoff and Arabic experience. A useful B2B feature list does not establish those local integrations.

The Saudi checkout checks to run before launch

• Payment availability: confirm the methods your customers need, including mada and eligible wallets, on the merchant account and chosen checkout.
• Order recovery: test payment failure, a repeated callback and a partial refund. Confirm that inventory and the order record remain correct.
• Invoicing: establish the taxpayer's notified integration date and invoice types with the finance team.
• Arabic checkout: test mixed Arabic and English product names, addresses and validation messages. Check the payment provider's screen as well as the storefront.
• Mobile usability: complete a purchase on a real phone with a slower connection. Record where buyers encounter delays or confusing instructions.

Payment fees and integration work in a headless setup

Headless does not automatically remove Shopify transaction fees. Shopify's third-party payment documentation says additional transaction fees depend on the plan, alongside the payment provider's processing fees. Confirm the applicable terms for the merchant account. A Next.js frontend using Shopify still uses Shopify as its commerce backend.

For a separate backend, compare the complete operating cost, including processing and maintenance. Keep the required checkout features in the comparison. A lower platform fee is not useful if refunds or reconciliation need manual repair.

For mada, wallets or BNPL, use a supported integration where it meets the requirements. Estimate custom work only after reviewing the provider's current API and onboarding conditions. Include authorization, capture and refunds in the acceptance criteria, along with duplicate callbacks and interrupted payments. There is no reliable universal two-day integration estimate.

Use the Saudi payment gateway comparison to build a shortlist, then confirm account eligibility and the payment methods offered for your integration.

ZATCA Phase 2: check the notified wave, then specify the integration

Phase 2 obligations follow ZATCA's phased rollout and taxpayer notifications. A store's choice of headless architecture does not determine its deadline.

Current wave example, checked 6 September 2026: ZATCA's Wave 25 announcement of 24 July 2026 covers taxpayers with VAT-taxable revenues exceeding SAR 187,500 in any of 2022, 2023, 2024 or 2025, with integration by 1 February 2027. This does not extend an earlier notified deadline. Confirm which notice applies to the business.

The official detailed guidelines distinguish standard tax invoices, normally cleared before sharing with the buyer, from simplified tax invoices, reported within 24 hours of issuance. The integration must implement the applicable invoice flow; sending every invoice in real time is not an accurate description of both models.

Have the finance team approve the invoice model and reconciliation process. Scope integration with the existing accounting system before building another invoice engine. Test rejected submissions and credit notes, and assign responsibility for monitoring failures.

Arabic RTL: control is useful only when it is tested

A custom frontend lets the team design the Arabic experience around the store's content. That control creates work: the implementation must handle text direction and mixed-language values correctly, including product codes, phone numbers and addresses.

Compare the hosted theme and custom prototype using the same shopping task. Check the cart, delivery form and payment screen in both languages. Choose a custom build when it solves an observed problem. See our Saudi web design service for Ijjad's delivery scope.

Anonymous proof — Jeddah lifestyle retail

In Ijjad's anonymized first-party account, six months after the rebuild the store reached 200+ monthly orders, a reported 340% conversion-rate lift, and mobile load time moving from 4.2s to 1.1s. Underlying analytics are private and this is not a forecast. Read the case methodology.

How to actually pick

Use these as starting recommendations. A demonstration of your actual workflow should decide the platform.

Before signing, ask for one complete demonstration: an Arabic mobile order, payment confirmation and the correct invoice, followed by a partial refund. Record which parts work now and which need implementation.

Where to read next

• Top 10 e-commerce development companies in Saudi Arabia (2026)
• Web development in Jeddah — Mada, STC Pay, ZATCA in detail
• Jeddah e-commerce case study and methodology
• Saudi website scope guide 2026
• Riyadh vs Jeddah vs Amman scope comparison

Frequently asked questions