E-Commerce Platform Cost in Saudi Arabia: 2026 Build Guide

The short answer

A compliant e-commerce platform for the Saudi market typically costs between SAR 90,000 and SAR 450,000 (roughly USD 24,000–120,000) to build, plus SAR 4,000–20,000 a month to run. The spread is not mostly about design or features. It is about how much of the Kingdom-specific work — Arabic and right-to-left handling, ZATCA e-invoicing, a SAMA-licensed payment stack, store registration on the Business Platform, and Personal Data Protection Law (PDPL) obligations — you build properly the first time. Our Saudi Arabia technology hub sets out how we scope this work for founders and enterprise teams.

Stratgik is a technology firm, not a law firm. Everything below is engineering and commercial guidance on how to implement obligations that already exist; please have your own counsel confirm how each rule applies to your entity and category.

Why "just use Shopify" is an incomplete answer

Hosted platforms get you selling quickly, and for a single-category store with modest volume they are often the right call. They become expensive or awkward in three situations that are common in the Kingdom: when you need Phase 2 e-invoicing clearance wired into order flow rather than bolted on monthly; when your catalogue, pricing or fulfilment logic is genuinely unusual (B2B price lists, rental, project-based quotations, multi-branch stock); and when Arabic is a first-class language rather than a translated skin.

The honest framing is a build-versus-buy decision with three outcomes, not two: buy and configure, buy and extend with custom services around it, or build. Most Saudi mid-market companies we scope land on the middle option. You can pressure-test your own case with our free build vs buy tool before you talk to anyone about price.

What actually drives the cost

1. Arabic and right-to-left as a requirement, not a plugin

Mirrored layouts, Arabic numerals and date formats, Hijri dates where relevant, Arabic-aware search and sorting, Arabic product data entry workflows, and transactional messages that read naturally rather than machine-translated. Retrofitting bilingual support into a platform designed English-first is routinely the single most expensive late change we see. Budget for it at the start and it is a modest line item; budget for it in month nine and it is a rebuild of the front end.

2. ZATCA e-invoicing (Fatoora) integration

This is now the item most teams underestimate. ZATCA has rolled the integration phase out in waves by revenue. In its criteria for Wave 25, ZATCA named taxpayers whose VAT-subject revenues exceeded SAR 187,500 in 2022, 2023, 2024 or 2025, with integration to the Fatoora platform required by 1 February 2027 (ZATCA announcement). Practically speaking, almost any VAT-registered online seller should now plan for Phase 2 rather than hope to stay out of scope.

For an e-commerce platform that means generating compliant simplified tax invoices with the required fields and QR code, cryptographic stamping, submission or reporting to the Fatoora platform, and — the part that bites — handling returns, partial refunds and cancellations as credit notes that reconcile. Read the ZATCA detailed e-invoicing guidelines before you accept any vendor's "ZATCA-ready" claim at face value, and ask which of your flows they have actually cleared.

3. Payments

Card acceptance in the Kingdom runs through the domestic mada scheme alongside international schemes, and payment service providers are regulated by the Saudi Central Bank (SAMA), which publishes rules for dealing with e-commerce payment service and support providers in its rulebook. For a merchant, the engineering implication is straightforward: integrate through a SAMA-licensed provider, keep cardholder data out of your own systems wherever possible, and treat 3-D Secure, tokenisation and reconciliation as first-class requirements. Apple Pay, STC Pay-style wallets, instalment providers and cash on delivery each add their own reconciliation and refund paths, and each one you add is real integration and testing work, not a toggle.

4. Registration, disclosure and consumer rules

The E-Commerce Law (Royal Decree No. M/126, 1440/11/07 AH) sets obligations that your platform has to express in software, not just in a policy page. Among them: display of the store's name or distinguishing mark, contact methods and commercial register details (Art. 6); pre-contract disclosure of total price including fees, taxes and delivery (Art. 7); issuing an invoice showing item costs, total and delivery date and place (Art. 8); a seven-day cancellation right for unused goods with specified exclusions (Art. 13); and a right to cancel and recover payment where delivery is delayed more than fifteen days (Art. 14). Penalties under Art. 18 run to warnings, fines of up to SAR 1,000,000, suspension of activity, or blocking of the store. The full text is on the Bureau of Experts site.

On registration, note that the guidance changed: in March 2023 the Ministry of Commerce announced that e-store owners register and document their stores on the Business Platform operated by the Saudi Business Center, rather than on Maroof. A great deal of blog content still tells founders to go to Maroof first. Check the current route on business.sa before you build the badge into your footer.

5. Personal data

The PDPL and its implementing regulations, published by SDAIA, govern how you collect, use, transfer and secure customer data. The obligations that most directly shape platform architecture are lawful basis and consent capture, a privacy notice that matches what the code actually does, data subject rights (access, correction, deletion) that someone can service without a developer, and breach handling — controllers are expected to notify SDAIA within 72 hours of becoming aware of a breach, per DLA Piper's Saudi Arabia summary. Cross-border transfer is the one to settle early, because it decides where your database, backups, logs and analytics live. Our Saudi PDPL compliance implementation page sets out how we fold this into a build rather than audit it afterwards.

Indicative cost ranges

These are Stratgik's indicative engagement ranges for the Saudi market as of November 2026, not market averages. They assume a competent team, Arabic and English from day one, and compliance work done inside the build rather than as a later project.

Run costs usually land between SAR 4,000 and SAR 20,000 a month across hosting, e-invoicing service fees, monitoring, security patching and a small change budget, before payment processing fees and marketing. For a quick independent sanity check on your own feature list, use our app cost estimator, then compare it to whatever quote you have in hand.

Where budgets usually go wrong

• E-invoicing priced as an add-on. The invoice is easy; refunds, partial returns, cancelled orders and reconciliation are where the effort sits.
• Arabic treated as translation. Layout mirroring, fonts, search behaviour and content operations are the real cost, and they are structural.
• Data residency decided late. Moving a live database and its backups between regions after launch is a project in itself, and it affects your transfer position.
• No operations budget. A store with no owner for catalogue quality, refund exceptions and failed-payment follow-up loses more money than the build saved.
• Paying for a rebuild of something buyable. If your requirements are ordinary, the differentiation is in merchandising and logistics, not in your cart code. See custom software for where bespoke work does pay back.

A practical pre-build checklist

• Confirm with your advisers which VAT and e-invoicing wave your entity falls into, and the integration date you must meet.
• Decide Arabic-first or bilingual-parity before any design work starts, and write it into the acceptance criteria.
• Choose a SAMA-licensed payment provider and list every method you will support at launch, with its refund path.
• Settle hosting region, backup region and analytics destination, and record the reasoning.
• Map the E-Commerce Law disclosure, invoice, cancellation and delay obligations to specific screens and emails.
• Confirm your store's registration route on the Business Platform and what documentation it needs.
• Appoint an internal owner for data subject requests and breach escalation, with a target well inside 72 hours.
• Ask every vendor for a named reference flow they have already cleared with Fatoora, not a compliance claim.
• Agree who owns the code, the cloud accounts and the domain on day one, in writing.
• Budget twelve months of run cost alongside the build, or you will cut the wrong corner in month three.

Frequently asked questions

How much does an e-commerce website cost in Saudi Arabia?

Our indicative ranges run from about SAR 90,000 for a well-configured hosted store with Arabic parity and compliant invoicing, to SAR 300,000–450,000 and beyond for a bespoke platform with native Phase 2 e-invoicing, B2B accounts and in-Kingdom hosting. Quotes materially below that range usually exclude e-invoicing, Arabic parity or data protection work; ask what has been left out rather than assuming it is cheaper.

Do I need ZATCA e-invoicing integration for an online store?

If you are VAT registered, plan on it. ZATCA's Wave 25 criteria named taxpayers with VAT-subject revenues above SAR 187,500 in any of 2022 to 2025, with integration due by 1 February 2027. Confirm your specific wave and deadline with your tax adviser, then treat the integration as part of order management rather than a reporting afterthought.

Can I host my Saudi store outside the Kingdom?

Sometimes, depending on your data, your sector and the transfer basis you can rely on under the PDPL and its implementing regulations. It is a decision to take deliberately and document, not to inherit from a hosting default. We cover the engineering side on our Saudi PDPL compliance page and the market context on the Saudi Arabia hub; the legal position should come from your counsel.

Is Maroof registration still required for e-stores?

The Ministry of Commerce announced in March 2023 that e-store registration and documentation moved to the Business Platform run by the Saudi Business Center. Verify the current requirement on business.sa for your activity before you rely on older guidance.

How long does a compliant build take?

Six to ten weeks for a configured hosted store, ten to eighteen weeks when you add meaningful custom services or ERP integration, and eighteen to thirty weeks for a bespoke platform. Compliance work does not usually extend the timeline if it is in scope from the start; it extends it badly when it arrives in user acceptance testing.

Should we build or buy?

Buy and configure if your requirements are ordinary and speed matters. Extend a hosted platform if your pricing, fulfilment or integration logic is unusual but your storefront is not. Build when the commercial model itself is the product. Our free build vs buy tool walks through the trade-offs in a few minutes.

If you are scoping an e-commerce build or fixing one that is already live, we are happy to look at it with you. Book a free 30-minute session through contact us and we will tell you plainly which parts of your plan are priced sensibly and which parts will come back later as a retrofit. Author: the Stratgik team.