A focused Saudi online store can reach launch in 5–10 weeks after the entity, products and content are ready. Controlled-scope technical delivery starts at SAR 7,990; broader custom builds commonly require SAR 10,000–40,000 before inventory, marketing and third-party charges. Complete seven stages: business basis, verification, platform, payments, shipping, compliance and one real production order.
Budget and schedule the whole launch
Separate business-formation expenses from ecommerce delivery. A developer cannot quote a government, bank, gateway or courier fee as if it were fixed, and provider pricing changes by contract and volume. The figures below are planning allowances, not official fee statements or binding third-party offers.
Stage | Typical time after inputs are ready | Planning cost in SAR |
| 1–10 business days, case dependent | Variable official and professional fees; verify at |
| 1–5 business days with complete data | SAR 0–500 for preparation; check the current official charge |
| 3–8 weeks | SAR 7,990–40,000 for custom work; hosted subscriptions separate |
| 1–4 weeks in parallel | SAR 990–5,000 for integration, excluding provider charges |
| 1–3 weeks in parallel | SAR 500–3,000 setup, excluding per-shipment costs |
| 1–4 weeks in parallel | SAR 1,500–12,000 depending on review and integrations |
| 3–10 business days | SAR 1,000–8,000 if outside the build contract |
Stages 3–6 overlap, so do not add every row. The fastest safe project collects documents and decisions early; it does not omit compliance or postpone provider onboarding until launch week.
1. Establish the seller and licensed activity
Choose the entity that accepts the order, issues the invoice and receives settlement. Its licensed activity must cover the actual products or services, and the commercial bank-account holder should match the establishment. A placeholder brand cannot substitute for a confirmed legal seller during gateway underwriting.
Use the Saudi Business Center and Ministry of Commerce services to determine the route for the owner's status and activity. Some authentication cases may use a valid freelance document instead of a commercial registration, subject to the activity and current service rules. Regulated goods can require sector approvals beyond the basic business record.
Build a controlled data pack: CR or valid document, national address, authorised person, commercial bank confirmation, VAT information where applicable, domains and social accounts. Reuse approved values in the footer, invoice, gateway and courier files. Small spelling differences across records create avoidable compliance questions.
Details are in our specialist article: commercial setup and ecommerce authentication through the Saudi Business Center; add the internal link at publication.
2. Authenticate through the Business Platform
People still search for “Maroof verification,” but the live route changed. The Ministry of Commerce announcement moved ecommerce authentication from Maroof to the Saudi Business Center's Business Platform. It also states that a valid CR or freelance document and a commercial bank account are required.
Submit the final store URL, not a staging address that will disappear. Match the name, activity, contact details and bank account to the official records. After approval, expose a verifiable reference in the store so a buyer can follow it to the government inquiry service. Do not draw a lookalike badge or link to an unrelated profile.
The Ministry describes the Business Platform as the authorised channel and provides an inquiry service for authenticated stores. Remove legacy instructions telling users to open a new Maroof account. Save the certificate, verification number, approved URL and review date; update the record when the domain or business details change.
Details are in our specialist article: why Maroof was replaced, current prerequisites and common authentication errors; add the internal link at publication.
3. Select hosted commerce or a custom build
A hosted platform works well for a conventional catalogue, standard checkout and rapid release. Review Arabic quality, product limits, checkout control, data export, app charges, ERP connectors and support before committing. The advertised monthly plan rarely represents the complete three-year cost.
Custom development is justified by customer-specific pricing, multiple warehouses, marketplace settlement, subscriptions, approval flows, specialised booking, advanced ERP connections or an Arabic experience templates cannot deliver. It buys control, not freedom from maintenance. Require specifications, test cases, security updates and a support boundary.
Compare candidates consistently:
- Compare ownership of source code, content and customer data.
- Compare three-year cost rather than the first subscription payment.
- Compare native Arabic RTL across catalogue, checkout and invoices.
- Compare proven payment, courier and accounting integrations.
- Compare written response times, exclusions and support limits.
- Compare implementation of Saudi policy and compliance requirements.
CloudTopia handles stages 3–7 under one technical scope: native Arabic RTL, ecommerce development, payment and shipping integrations, invoice connection and release testing. A controlled build starts at SAR 7,990, additional work is itemised, and the client owns the source code under the contract.
4. Add mada, Apple Pay and BNPL deliberately
Choose a payment service that can lawfully onboard Saudi merchants, then complete underwriting before assuming an integration date. Providers normally examine the entity, bank account, domain, products, fulfilment and refund policies. Technical integration cannot override a declined or incomplete merchant application.
Treat mada as a core requirement for a broad Saudi audience. The Saudi Central Bank's mada page describes ecommerce acceptance using 3-D Secure and support for adding mada cards to Apple Pay. Confirm which methods the specific gateway enables for your merchant account, currency and product category.
Tabby and Tamara can add buy-now-pay-later, subject to their onboarding and commercial terms. Model the order states carefully: pending approval, authorised, captured, cancelled, partially refunded and fully refunded. Do not release stock because the browser reached a success URL; verify the transaction server-side and validate signed webhooks.
Send the store scope to CloudTopia on WhatsApp for a clear payment-and-shipping quote. Integration of one gateway and two methods into an existing store starts at SAR 990, excluding provider and BNPL charges; new-store packages allocate it according to the agreed scope.
Details are in our specialist article: mada, Apple Pay, Tabby and Tamara integration, including declines, callbacks and refunds; add the internal link at publication.
5. Design fulfilment before promising delivery
Shipping begins with inventory and service decisions: served regions, warehouse locations, package weights and dimensions, fragile or controlled goods, cut-off times, working days, collection, and cash on delivery if offered. These inputs determine checkout rates and credible delivery estimates.
Request proposals from at least two carriers or use an aggregator when it improves coverage. Compare remote-area fees, return-to-origin charges, delivery attempts, COD settlement, claims and tracking events. A lower outbound label can be more expensive after failed deliveries and slow returns.
Connect label creation, tracking reference, order-status updates and proof of delivery. “Label created” is not “shipped,” and “shipped” is not “delivered.” Give operations distinct states for ready to ship, collected, in transit, out for delivery, delivered, delivery failed and returned.
Publish a shipping policy that names territories, timing, charge calculation, address responsibilities and the damaged-or-lost parcel process. Test light, heavy, remote-area and returned orders. Ensure Arabic status messages are meaningful rather than raw carrier codes.
Details are in our specialist article: comparing Saudi carriers, mapping tracking events and handling returns; add the internal link at publication.
6. Implement PDPL, Fatoora and store policies
Compliance belongs in software behaviour as well as legal pages. Minimise collected personal data, document its purpose and legal basis, separate marketing choices, control staff access and define retention and deletion. A single pre-ticked consent box should not cover fulfilment, advertising and analytics indiscriminately.
Review the Saudi Personal Data Protection Law and the competent authority's current guidance with an adviser. The privacy notice should state what is collected, why, who receives it and how people exercise their rights. The system needs consent evidence, request handling, access logs and an incident process.
For invoicing, use a ZATCA-compliant electronic solution. The official explanation confirms that Phase 2 is applied in waves and requires integration with ZATCA systems and the prescribed format. Check the taxpayer's notice and current specification rather than embedding an old revenue threshold or deadline.
The Ministry of Commerce ecommerce page links the law, executive regulations, store guide and compliance checklist. Published evaluation criteria cover commercial and tax details where applicable, privacy, returns, complaints, shipping, contact options and website security. Make final price and material conditions visible before payment.
Details are in our specialist articles: Saudi PDPL for websites, ZATCA Phase 2, and ecommerce policy requirements; add internal links at publication.
7. Launch by completing one live order
Production release is not the first time the components should meet. Complete test orders, then process a small agreed live payment. Inspect mobile Arabic, catalogue, search, cart, coupon, VAT, delivery, payment, invoice, notifications, tracking, cancellation and refund.
Use a single acceptance list:
- Test an account and a guest order on a real phone.
- Test successful, declined, abandoned and repeated payments.
- Test stock contention without allowing a negative quantity.
- Test a compliant invoice, refund and linked adjustment.
- Test a shipping label, tracking update, delivery and return.
- Test a data-subject request and staff access boundaries.
- Test backup restoration, alerting and diagnostic logs.
Manually watch the first 20 orders even when workflows are automated. Track checkout exits, payment-decline reasons, fulfilment time, inventory accuracy, courier exceptions and support contacts. Fix the largest blockage before increasing advertising spend; traffic multiplies both a good process and a broken one.
Details are in our specialist article: the pre-launch acceptance checklist and first-order monitoring; add the internal link at publication.
Assign responsibility across the project
The business owner decides assortment, price, margin, operations and approved policies. An accountant or tax adviser sets registration and treatment. Legal counsel reviews terms when risk warrants it. The gateway and courier approve their accounts. The technical partner implements those decisions and tests the connected customer experience.
Avoid five disconnected suppliers without an integration owner. Keep a decision register, credential inventory, dependency schedule, test environment and named approver for each gate. Store certificates, contracts, policy versions and acceptance evidence in a controlled project space.
Choose a platform that handles the next one or two years of credible demand. Do not add a marketplace, loyalty programme or mobile app before repeat purchasing supports the investment. First fund fast mobile pages, useful Arabic content, trusted local payments, accurate delivery promises and responsive customer service.
Control the budget after go-live
Divide spending into formation, build, integrations, operation and acquisition. A development price does not automatically include stock, photography, branding, advertising, payment fees, tax advice or delivery. The proposal should list exclusions, code and data ownership, renewals, support and acceptance criteria.
For hosted commerce, total the subscription, apps, premium theme, transaction charges, custom work and eventual migration. For a custom store, include hosting, maintenance, security updates, backups and integration monitoring. Compare both over three years in SAR.
Release the smallest version that can sell responsibly: persuasive product pages, necessary search and filters, payment, shipping, invoice, policies and baseline analytics. Defer features that do not affect the first 100 orders. A low starting price remains valuable only when the deliverables are measurable and future charges are visible.
The launch decision
Opening an online store in Saudi Arabia is a regulated operating project, not a theme installation. Confirm the seller and authentication, select technology around the operating model, connect local payment and shipping, implement compliance, then prove the whole flow with a real order.
Parallel work can shorten the schedule once the data pack is ready. It should not put payment before merchant-name alignment or launch before refund and invoice tests. Verify fees, dates and current rules with the Saudi Business Center, Ministry of Commerce, ZATCA and any sector regulator at implementation time.
Message the CloudTopia team on WhatsApp to plan the platform through the first order. The scope is quoted in SAR, the Arabic experience is native RTL, stages 3–7 have one technical owner, and source-code ownership is transferred under the contract.
Frequently asked questions
How much does it cost to open an online store in Saudi Arabia?
A controlled technical package starts at SAR 7,990, while custom stores commonly require SAR 10,000–40,000 depending on design, catalogue, payments, shipping, invoicing and integrations. Add business, platform, provider, inventory and marketing costs. Demand an itemised proposal that separates setup, development, recurring operation and optional growth work.
Do I need a commercial registration for a Saudi online store?
You need a valid legal basis covering the activity. Saudi Business Center ecommerce authentication requires a valid commercial registration or an eligible valid freelance document, plus a commercial bank account. Regulated products can require additional sector licences. Check the current service conditions at business.sa and with the relevant authority before accepting orders.
What is the best ecommerce platform in Saudi Arabia?
There is no universal winner. Use a hosted platform for a standard catalogue and rapid release; choose custom development for complex pricing, multiple warehouses, ERP integration or an advanced Arabic experience. Compare data and code ownership, three-year cost, mada and courier support, compliance controls, migration options and written support terms.
How long does it take to launch a Saudi online store?
A focused store typically takes 5–10 weeks once the entity, catalogue and content are ready. Payment, shipping and compliance can proceed in parallel, but bank and provider approvals can extend the schedule. A complete data pack, early applications and defined acceptance tests save time without omitting authentication, invoicing or refund work.
Read also
Need a website, dashboard, or business system like this?
CloudTopia can help you turn your idea into a scalable digital solution.
Share this article
Written by
Mohamad Shahm | محمد شـهم
Mohamad Shahm founded CloudTopia after a decade building web platforms, e-commerce systems, and bilingual (Arabic + English) experiences for Gulf businesses. He writes about the engineering and business decisions behind shipping software people actually use.
