A fragrance brand in Riyadh asks three agencies for a quote on a custom online store. The proposals come back with timelines of several months, a separate line for every payment gateway, and a monthly maintenance retainer. The founder asks the obvious question: why not build on an e-commerce platform and start selling this month? This article answers that question honestly. We compare the two routes on cost, launch time, security, updates and Gulf-specific requirements, and we are clear about the situations where custom code is still the right call.
We build both at S-Plus. Our agency has delivered custom websites and systems for clients across Saudi Arabia, the UAE and Egypt for more than fifteen years, and we also built Commera, a SaaS e-commerce platform for Gulf and Egyptian merchants. So this is not a sales pitch for one side; it is the conversation we have with clients every week.
What an e-commerce platform gives you that custom code does not
A SaaS (software as a service) e-commerce platform is a store engine that already exists, runs on the provider's servers, and is shared by many merchants. You subscribe, configure, and sell. A custom store is software written for you alone: your developers own every line, and therefore every bug, upgrade and security patch.
The difference is not only technical. It decides where your team spends its time:
- On a platform, your team spends its time on products, photography, offers, customer service and marketing. The engine is somebody else's job.
- With custom code, a meaningful share of your budget and attention goes to keeping the engine running: hosting, upgrades, fixing integrations when a gateway changes its API, and finding a new developer when the original one leaves.
On Commera, for example, the day-one toolkit already includes simple and variable products and bundles, Excel import and export, stock with low-stock alerts, suppliers and purchase orders, orders from creation to delivery, PDF invoices with VAT, returns and exchanges, staff roles and permissions, a point-of-sale screen for physical branches, and reports. A custom build has to write, test and maintain each of those before the first order arrives.
The real cost of a custom store
Custom quotes usually show the build cost. The true cost appears later. Before you compare numbers, make sure both columns contain the same lines:
| Cost line | Custom-built store | SaaS e-commerce platform |
|---|---|---|
| Initial build | Design, development and testing of every feature | Theme selection and configuration |
| Hosting and servers | Your contract, your responsibility, your scaling | Included in the platform model |
| Payment gateways | Each gateway integrated and maintained separately | Ready integrations activated from the plugin store |
| Shipping carriers | Each carrier API built and maintained | Ready integrations (on Commera: SMSA, Aramex, Bosta) |
| Security patches and upgrades | Ongoing developer time | Handled by the provider |
| New features | A new project each time | Activate a plugin or wait for the next release |
| Key-person risk | High if one developer knows the code | Low: the product has its own team |
| Sales commission | None | Depends on the platform; Commera takes 0% on sales |
That last row matters. Some platforms charge a percentage of every sale on top of the subscription. On Commera the subscription is the only thing you pay the platform; gateway fees stay between you and your gateway. Pricing depends on the plan, so ask for a quote or start with the free trial on commera.co.
The hidden line: maintenance
Industry practice is to budget a yearly maintenance amount on top of the build, because software does not stay still. PHP and JavaScript frameworks reach end of life, browsers change, gateways update their APIs, and tax authorities change invoice formats. With custom code, every one of those changes is a ticket you pay for. On a platform, they arrive as updates.
Time to launch: weeks instead of months
Time is a cost too. A season such as Ramadan, White Friday or back-to-school does not wait for a development sprint. A store that launches three months late misses revenue that no later feature can recover.
On a platform, launch is mostly configuration. Commera's setup wizard walks you through seven steps: language and country, currency, brand and logo, payment methods, shipping and theme. You can load demo content to see how the store will look, and keep the store behind a coming-soon page that collects visitor emails until you are ready. The realistic bottleneck becomes your own content, product photos, descriptions and prices, which you need either way.
A practical launch plan on a platform
- Week 1: run the setup wizard, choose a theme, set brand colours and fonts, upload the catalogue from Excel.
- Week 2: connect a payment gateway with your own merchant account, set up shipping zones and rates per city, enable VAT.
- Week 3: test orders end to end (pay, ship, return, refund), invite staff with the right permissions, then open the store.
Security and payments: who carries the risk?
Security is where custom stores most often cut corners, usually by accident. Storing card data, verifying payment callbacks, protecting the admin panel and keeping dependencies patched are specialist work.
A mature platform removes much of that risk by design. On Commera, card payments run on the gateway's own hosted page, so card details are typed on the gateway's secure page and never pass through your server. Payment status is confirmed with the gateway directly rather than trusting the return link, and gateway notifications (webhooks) can be signed with a secret so forged notifications are rejected. These are exactly the details a rushed custom build tends to miss, and a single missed check can mark an unpaid order as paid.
A useful test for any proposal: ask how a payment is confirmed. If the answer is the customer returning to a success page, the design is not safe.
Updates, plugins and regulations
A store is never finished. Next year you will want instalments, a loyalty programme, a mobile app, a WhatsApp inbox or a second market. With custom code each of those is a new project, a new quote and a new testing cycle.
On a platform, growth is a list of switches. Commera's plugin store has more than 70 plugins that you activate from the dashboard: Tabby, Tamara and Taly instalments, MyFatoorah, Telr, N-Genius and Amazon Payment Services, abandoned cart recovery, loyalty points, a customer wallet, referrals, premium membership, a shared WhatsApp inbox, a mobile app builder for Android, and multi-market selling. You can browse them on the marketing and sales page.
Regulation is the other driver. When Saudi Arabia required QR codes on simplified tax invoices, custom stores had to commission the change. On Commera, simplified tax invoices with a ZATCA-format QR code come from an optional plugin. We explain what it covers, and how S-Plus supports Phase 2 integration, in our guide to ZATCA e-invoicing for online stores.
Gulf requirements that are easy to underestimate
Many international tools were not designed for this region, and many custom builds treat Arabic as a translation file added at the end. Check these requirements before choosing either route:
- True bilingual support: Arabic and English with correct right-to-left and left-to-right layouts in both the storefront and the dashboard, translated product names and descriptions, and optional separate URLs per language for SEO.
- Local payment habits: Mada and Apple Pay through gateways that support them, buy-now-pay-later through Tabby and Tamara, cash on delivery with minimum and maximum order values, and bank transfer with a receipt upload.
- VAT that differs by country: 15% in Saudi Arabia, 10% in Bahrain, 5% in the UAE and Oman, and no VAT in force in Kuwait and Qatar at the time of writing.
- Couriers and city-level shipping: shipping zones by country, region and city, free shipping thresholds, store pickup, and labels printed from the order page.
- WhatsApp: order notifications, order confirmation by reply, and campaigns on the channel Gulf customers actually answer.
- Multiple currencies: SAR, AED, KWD, QAR, BHD and OMR shown correctly, including three-decimal currencies such as the Kuwaiti dinar.
When custom code still makes sense
A platform is not the answer to everything. Custom development is the right choice, or part of it, when:
- The software is the product. If your competitive edge is a unique buying experience, such as a 3D configurator for furniture or a quote engine for industrial parts, you may need to own that code.
- Your process does not fit any standard model. Complex B2B rules tied to an ERP, regulated workflows, or pricing that depends on live external data can outgrow configuration.
- You already have an engineering team. If you employ developers full time and the store is one part of a larger digital product, the maintenance burden is already budgeted.
- Data residency or integration rules require it. Some government or enterprise contracts dictate exactly where and how systems run.
The hybrid route most growing brands take
In practice, most merchants do best with a platform at the core and custom work at the edges. Commera exposes a REST API and webhooks, and offers integration plugins for Zapier, Shopify and WooCommerce sync, and Microsoft stock sync. That lets you keep the store on a maintained engine while S-Plus, or your own team, builds the one custom piece that is genuinely unique to your business, such as a CRM, an ERP connector or a special pricing tool. Our article on ready-made versus custom business systems goes deeper into that decision.
A decision checklist you can use today
| Question | If yes |
|---|---|
| Do you need to sell within weeks, not months? | Platform |
| Is your catalogue standard: products, variants, bundles? | Platform |
| Do you lack a full-time developer? | Platform |
| Do you need Gulf gateways, instalments and couriers now? | Platform |
| Is your core advantage a feature no platform offers? | Custom, or platform plus a custom module |
| Do strict enterprise or data rules dictate your stack? | Custom |
| Do you already run an in-house engineering team? | Either; compare total cost over three years |
If you are weighing specific platforms, our comparison of Commera, Shopify, WordPress, Salla and Zid walks through each one criterion by criterion.
Already on a custom store or WooCommerce?
Many of our clients come to us with an existing store that has become expensive to maintain. Moving does not have to mean starting again. Commera's store sync plugin can run a full one-time migration from WooCommerce (through the API or a .sql file), including categories, brands, attributes, products, customers and orders, and can keep products, stock and prices in sync from Shopify or WooCommerce during the transition. The manual SEO plugin adds 301 redirects with CSV import and a 404 monitor so old URLs keep their rankings. Our guide to migrating a store without losing SEO lists every step.
Frequently asked questions
Is an e-commerce platform cheaper than custom development?
For most merchants, yes, once you count hosting, gateway and courier integrations, security patches and maintenance over several years rather than the build cost alone. Custom code becomes competitive only when you have unique requirements or an in-house team.
Will my store look like everyone else's on a platform?
Not if the platform gives you real design control. Commera offers more than 15 themes for sectors such as food, fashion, electronics, mobile phones, medical and kids, a drag-and-drop page builder with live preview on desktop, tablet and mobile, your own colours and fonts, and the option to mix headers, footers and pages from different themes.
Do I own my data on a SaaS platform?
You should be able to export it. On Commera you can export products to Excel or CSV, export reports to Excel, CSV and PDF, and connect other systems through the REST API. Ask any provider the same question before you sign.
Can a platform handle a large catalogue?
Yes. Bulk import from xlsx or csv, bulk actions on orders and products, and stock per branch or warehouse are standard on Commera. Very unusual workflows are where the hybrid approach helps.
What if I need a feature the platform does not have?
First check the plugin store, which covers most needs. If the feature is truly specific to your business, build it as a separate module connected through the API, so the core store stays on a maintained engine.
Start selling now, customise where it counts
For the large majority of Gulf merchants, the smart route is a strong e-commerce platform for the store itself, and custom work only where it creates a real advantage. Try Commera free, or talk to the S-Plus team about your case: we will tell you plainly whether you need a platform, a custom build, or both. Contact us for a consultation and a quote.
