The comparison is not ready-made versus better; it is two models of ownership and responsibility. This article puts Shopify and a custom build on the same lines: catalogue, payments, Arabic, integrations, three-year cost, and exit.
When you compare Shopify with a custom build in Saudi Arabia, the comparison is not between “ready-made” and “better”. It is between two different models of ownership and responsibility. Shopify sells you a platform that runs, paid for through a subscription, apps and themes, while a custom build sells you a system you own and pay to operate and change. Either can succeed, either can fail, and the difference shows up in details that never appear in the first demo.
The decision comes down to four things: the shape of the catalogue, the purchase path, the local integrations, and who will operate the store after launch. If all four are standard, Shopify is often cheaper and faster. If one of them sits outside the norm, customisation starts to earn its place. This article puts both options on the same lines and explains what to ask before you pay a subscription or sign a build contract.
What the subscription actually buys
A Shopify subscription buys hosting, an admin, a checkout, an order system, and an ecosystem of themes and apps. That is not a small thing. The store works from day one, security updates and backups are part of the service, and you do not need a server team to start. For many small and mid-sized brands, that is the real advantage: turning an operations problem into a known monthly fee.
The subscription does not buy fit. Every behaviour outside the default becomes an app, a customisation or manual work. A shipping address that needs an extra field, a B2B account with different prices, discount rules tied to specific stock, or a tax invoice in a particular format all get solved somehow. The question is at what cost and who maintains it. The platform does not remove complexity; it moves it to another layer.
Where each option wins
| Line | Shopify | Custom build |
|---|---|---|
| Standard catalogue | Fast; themes cover display, filtering and checkout | Needs building and testing even when simple |
| Large catalogue or complex variants | Possible, but it strains theme and app limits | A data model designed for the actual shape |
| B2B prices and order minimums | Usually an external app or limited customisation | Native to the account and the order |
| Local payments and invoicing | Through providers and apps; every method must be verified | Direct integration with the gateway and invoicing |
| Arabic and RTL | Depends on the theme and apps; needs real testing | Built in both directions from the first screen |
| ERP or PIM | Integration through an app or middleware, with field limits | Integration as deep as the system allows |
| Time to launch | Shorter when the scope is standard | Longer, but it follows scope rather than platform limits |
| Ownership and exit | Data is exportable; the storefront lives on the platform | Code, data and configuration are yours |
| Cost after launch | Subscription, apps and recurring upgrades | Hosting, care and changes with defined scope |
The local layer is not a checkbox
In Saudi Arabia it is not enough for the store to work. It has to accept Mada, issue a correct tax invoice, calculate shipping the way you actually ship, and handle addresses that do not follow the Western form. Local platforms such as Salla and Zid give you some of this ready-made; Shopify gives you wider flexibility but you assemble the local layer through providers and apps. The difference is not capability; it is the number of parties that have to agree.
Test the local layer before launch, not after. Test a successful Mada card, a declined card, a full refund, a partial refund, an order to an address without a postal code, and an order above the supported weight. Test the invoice on a mobile browser, in Arabic. If you offer cash on delivery, test its accounting state. These tests are the difference between a store that works and a store that appears to work.
There is a commercial reason this layer deserves the time: payment is where the order is lost. Baymard's 50-study average puts cart abandonment at 70.19%, 22% of users have abandoned because checkout was too long or complex, and the average form has 11.3 fields. No platform removes those numbers, but the wrong customisation of the payment path multiplies them. Saudi checkout conversion fixes lists the ten issues we see before any platform decision.
The three-year cost shape
Do not compare a monthly subscription with a build price. Compare the three-year total across seven lines: subscription or hosting, apps or licences, theme or design, customisation, local integrations, care after launch, and the cost of change when the business model changes. The subscription looks cheaper in year one because much of the cost sits in the other lines.
From reading to shipping
Want this built, not just explained?
Bring us the problem behind the article. We will tell you what it takes, what it costs, and whether we are the right team.
Rasad's published band for an ecommerce build is SAR 5,000 to 15,000 over 10 to 16 weeks. That band does not cover everything, but it gives you a reference for what “building a store” means here: a bounded catalogue, one purchase path, payment and shipping configured, Arabic and English, analytics, and handover. If a Shopify proposal is lower, ask what it excludes; if it is higher, ask which line sets the difference.
The largest hidden cost is change. When you discover a year later that you need different prices for wholesale customers, a monthly subscription, or an integration with a new warehouse, the question is not “does the platform support it?” but “what will it cost to add, who will build it, and will it survive the next upgrade?”. A custom build makes that question part of the design from the start. Shopify makes it an addition to an existing system.
The decision checklist before you sign
Get these answers before you choose. If any line has no clear answer, price is not the problem yet.
Catalogue: how many product families and variants, and does each category need its own fields?
Selling model: retail, wholesale or both, and do you need tiered prices or a minimum order?
Payments: which methods will you actually support, and who owns settlement and refunds when something fails?
Invoicing: do you need a tax invoice in a specific format, and who guarantees it after a platform change?
Shipping: how many warehouses, what weight, city and pickup rules, and is cash on delivery required?
Arabic: is the Arabic version original content or a translation, who reviews it, and has RTL been tested on mobile?
Integration: which systems must the store know from day one, and what can be deferred?
Operations: who adds a product, changes a shipping rate, and answers when payment breaks on a holiday?
Exit: if you move after two years, how do data, URLs and customer accounts leave with you?
How to leave without losing what you built
Portability is not a legal clause at the end of the contract. It is a design decision. If product and category URLs can be exported, customer accounts can move, and order history is complete, you can leave. If data is spread across the platform and its apps, leaving becomes a project of its own. Ask about data export before you ask about price, and ask who owns the content, images and domain.
On a custom build, ask about the repository, the database and the deployment configuration. On Shopify, ask which apps hold customer data and what happens to them when the subscription ends. In both cases, ask for a written exit plan before you sign. A good agency is not afraid of the exit question, because a system you can leave is a system you can trust.
Frequently asked questions
Is Shopify always cheaper? No. It is cheaper when the scope is standard, because the subscription covers hosting, checkout and order management. When you need heavy customisation or several integrations, apps and upgrades start to close the gap.
Does Shopify support Mada and ZATCA? It depends on the payment provider and the apps available under your contract. Do not assume support; ask for a real test of a Mada card and a tax invoice before launch.
Can you build a good Arabic store on Shopify? Yes, but RTL quality depends on the theme and the apps. Test menus, forms and invoices in Arabic on mobile, and do not rely on the theme preview.
When is a custom build justified? When the selling model, the integration or the content is your advantage, and when platform limits become part of operating cost rather than a detail.
How long does a custom build take? Ten to sixteen weeks inside the published band, provided the catalogue and content are ready. Delay usually comes from content, not code.
Do you help choose the platform? Yes. We start with the catalogue, the selling model and the integrations, then compare the options. Sometimes the recommendation is not to build custom.
Sources
- Baymard: cart abandonment rate — the 50-study 70.19% average.
- Baymard: checkout usability — 11.3 fields on average, and 22% who abandoned because checkout was too long.
- web.dev: Milliseconds make millions — 0.1 seconds and 8.4% higher retail conversions.
- Rasad's published price bands — the figures this article works from.
- Ecommerce development — scope, process, and delivery.
Cover image: Shixart1985, CC BY 2.0, via Wikimedia Commons.

