Blog Overview
The ready platform is the right start for most stores. Custom earns its place with subscriptions, B2B, complex pricing, and portal operations, and how to compare cost over three years.
The question most store owners ask us is not “should we pick Salla or Zid?” It is a harder one: when does the best off-the-shelf platform stop fitting? The owner started on a platform because speed mattered, then operations grew until the platform became the ceiling. The catalogue is no longer a handful of products, orders are no longer individuals paying instantly, and fulfilment is no longer one person packing parcels at the end of the day.
This article marks that moment with four tests: the business model you actually run, the cost direction over three years, your control over the checkout experience, and what a migration would require if you choose one. We do not quote either vendor's prices, because price alone does not settle the question. The shape of operations settles it: if your operations assume things a ready platform does not support, the custom route serves them. If your operations really are simple, the ready platform is the smarter choice. We will be plain about both cases.
Where the ready platform is the right start
A ready platform fits the direct-to-customer store: a bounded catalogue, a short sales cycle, instant payment, and a small team or sales team with no developer of its own. In that shape, the platform carries the build, hosting, security, and updates, and you carry the catalogue, marketing, and customer service. That is a sane division of labour, and building custom there means paying for capabilities you will never use.
The practical test is simple: write your operation in two sentences. “We sell a fixed set of products to customers who pay instantly, and we ship the orders” means the platform is enough. If it takes three sentences to describe how you work, you are in the grey zone, and each extra sentence is a candidate reason to move. See our e-commerce service for where your operation sits relative to that line before you sign anything.
When custom pays for itself
Five shapes make custom clearly worth it. First, subscriptions: recurring charges, pauses and resumes, and repeated payment failures handled automatically, a cycle that does not fit instant-cart logic. Second, B2B: accounts with different permissions, contract-based pricing, and approved-buyer purchase orders. Third, complex pricing: multiple units of measure, bundled packs, and discounts tied to tenure or volume. In all three, a ready platform squeezes you into manual workarounds that eat team hours every week.
Fourth, portal-like operations: a customer tracks a shipment, downloads invoices, reorders an item, and uploads a document from one account instead of email threads. That portal is the same one our article on client portal development cost describes, and the difference from an ordinary store is the number of steps the customer completes alone. Fifth, multi-market: several markets, each with its own currency, shipping rules, and checkout page. Combine these shapes and you get the custom store; separate them and you get the ready-platform store.
The three-year cost comparison
Platform cost moves with your sales; custom cost moves with maintenance. Any fee tied to gross merchandise volume grows as you grow, and any fixed subscription has to be summed over all three years, not read month by month. In custom, you pay the build once and maintenance and hosting over time, but you do not pay for each extra sale. The table below sets the two side by side without quoting either side's prices.
| Line | Ready platform | Custom store |
|---|---|---|
| Build | Starts with no code, and setup is much faster | A full build; our published band is SAR 5,000 to 15,000 over 10 to 16 weeks |
| Variable fees | Fees may track gross merchandise volume on the platform | Do not scale with sales volume; they follow the scope you build |
| Maintenance and hosting | Included in the subscription | Paid directly for hosting, monitoring, and maintenance |
| Change cost | May need a workaround or a higher subscription tier | Quoted after discovery, and owned by you |
| Exit value | Data leaves with you, but custom logic stays on the platform | Code, data, and structure are yours, and exit is free |
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.
The comparison ends in two opposite directions, not one number. If sales are flat or slow-growing, the platform is usually cheaper. If sales grow and operations get more complex, the fixed custom cost overtakes the platform's variable fees. Our published e-commerce band is SAR 5,000 to 15,000 over 10 to 16 weeks for a complete core build, and anything beyond that is quoted after discovery, not guessed on a call.
Checkout and UX control
Control of the checkout experience is the most measurable difference between the two routes. The average cart abandonment rate across fifty studies is 70.19%, and most abandonment happens at checkout, not on the product page. The average checkout carries 11.3 form fields, and 22% of users abandoned an order because checkout was too long or complex. Whoever owns the checkout page owns these numbers; whoever does not relies on the platform's templates and limits.
Speed is part of the same control. A 0.1 second improvement in mobile site speed was associated with 8.4% higher retail conversions and 9.2% higher average order value across 37 brands. A custom store makes those improvements a design decision: field count, order, step count, and load speed. On a ready platform you can improve copy, images, and pricing, but the page itself is built within the platform's limits. If your growth depends on a precise checkout experience, that ownership is the tool you work with every day.
Migration triggers: what to check before you leave
Migration is not a single decision; it is a list of accumulating signs. A weekly count of manual workarounds, repeated failures of requests the platform cannot serve, and a gap between the pricing you need and what the platform supports. As long as these signs are recorded, you can compare cost safely. If they are not recorded, the migration decision is a guess. The checklist below is what we ask of any store before migrating, in either direction.
The real catalogue versus the platform catalogue. Write the actual count of products, units, and bundles you sell, and compare it with what your current tier supports.
The manual workaround log. Record every task done in spreadsheets or messages after the platform promised to handle it.
A real pricing file. Put your current prices, including discounts and bundles, in one document and map them against the new scope.
The integration list. Collect every payment, shipping, invoicing, and accounting system the store connects to today.
Customer records at risk. Identify which customer records cannot be exported from the current platform, and whether they must be re-collected.
The order and invoice history. Confirm the full order history and invoice status migrate, and that accounting stays continuous.
The payment decision. Settle who owns the payment gateway account, who holds the keys, and whether the same gateway survives the move.
Storage and retention requirements. Review the personal-data retention policy and in-Kingdom storage duties before moving any data.
Frequently asked questions
Are Salla and Zid a mistake from the start? No. They are the right start for most new stores, because fast launch beats perfection. The choice turns wrong when operations change and the platform does not.
Is there a number that says “leave now”? No single number. The sign is accumulating manual workarounds, failing requests, and a pricing gap. If they show up weekly, it is time to compare.
Is custom always more expensive? Over three years, not necessarily. Fees tied to sales grow with growth, while custom costs stay flat and move only with maintenance. Our published band is SAR 5,000 to 15,000 over 10 to 16 weeks, and the rest is quoted after discovery.
What is lost when you leave? Usually not the products, but the records attached to them: order history, invoice status, customer history, and custom pricing logic. Verify all of them before the decision.
Does a portal need a custom build? If customers complete more than one step without an employee, yes. Every step a customer completes alone cuts cost and raises satisfaction. At Rasad we have delivered 45+ projects for 3 government entities over 5+ years, most of them operational systems sharing this portal shape.
Sources
- Baymard: Cart Abandonment Rate — average abandonment of 70.19% across fifty studies.
- Baymard: Checkout Usability — an average of 11.3 fields, and 22% abandoning because checkout was complex.
- web.dev: Milliseconds Make Millions — a 0.1 second improvement linked to 8.4% higher conversion and 9.2% higher order value.
- web.dev: Core Web Vitals — the performance thresholds we test checkout pages against.
