Commissioning an online shop: a ready-made platform or custom build?
When commissioning an online shop, the right starting point for most businesses is a ready-made platform; once the product range, the sales flow or the integrations move beyond standard patterns, a custom build — or a mix of the two — starts to make more sense. What decides it is your business model, before your budget. Below we compare the three approaches, when each one works, and the questions to ask first.
We are a studio that builds websites and custom software. Which is exactly why we often say in first conversations that, for some shops, the soundest advice is to start on a ready-made platform.
Three approaches, briefly
A ready-made platform. A subscription e-commerce service, or open-source shop software that is installed for you. Product management, the basket, payments and order tracking come built in. You choose a theme, add your products and open the shop.
A custom build. The shop is designed from scratch around your sales flow. The product structure, pricing rules, order process and screens all come from your needs.
A hybrid. A ready-made e-commerce platform runs in the background (products, stock, payments), whilst the storefront customers see is designed for you and connects to that platform through an API. Sometimes it works the other way round: a module specific to your business is added alongside a ready-made shop.
Side by side
| Ready-made platform | Custom build | Hybrid | |
|---|---|---|---|
| Getting started | Fast | Needs a development process | In between |
| Cost structure | Ongoing subscription and commissions | Initial investment plus maintenance | A combination of the two |
| Design freedom | Within the theme’s limits | Complete | Complete in the storefront |
| Business-specific rules | Limited by plug-ins | As far as you need | As far as you need |
| Maintenance | Largely with the platform | With you or your developer | Shared |
| Data and portability | As far as the platform’s export allows | Entirely yours | Largely yours |
There are no figures in the table, because cost depends on scope far more than on the approach. But the structure of the cost differs. On a ready-made platform you pay regularly; with a custom build you invest at the start and then pay for maintenance. Which works out better in the long run depends on the size of your shop and how long you will use it.
When is a ready-made platform the right choice?
- You are opening a new shop and want to see whether the product sells first.
- Your products are standard: a name, photographs, a few options (size, colour) and a price.
- Your sales flow is add to basket, pay, ship.
- Your own team wants to manage products and promotions without technical knowledge.
Here, a ready-made platform gives you the quickest and least risky start. The real effort is better spent on product photography, product descriptions and customer service.
One caution: even on a ready-made platform, the choice of theme, page speed and SEO settings matter. A heavy theme and dozens of plug-ins can slow a shop down. We have gathered the basic checks for search visibility in our technical SEO checklist, and the usual causes of sluggishness in why is my website slow.
When is a custom build needed?
A custom build makes sense when the business model does not fit the ready-made patterns. The situations we see most often:
- Trade and wholesale sales. A different price list for each customer, account balances, payment on terms, minimum order quantities.
- Made-to-measure or made-to-order products. The price is calculated from dimensions, materials or options.
- Complex stock. Several warehouses, stock coming in from production, transfers between branches.
- Subscriptions and repeat orders. Regular deliveries, changing plans, periodic invoicing.
- Deep integration. Orders arriving instantly in the accounting programme, the production plan or the warehouse software.
In these cases you can push a ready-made platform with plug-ins; but beyond a certain point the plug-ins clash with each other, updates break things, and the shop becomes hard to run. You can test this decision against the six questions in off-the-shelf or custom software.
The hybrid: between two worlds
For many growing shops, a hybrid is a balanced path. Standard work such as products, stock and payments stays on a proven platform. The brand’s visible face and the parts specific to the business are built separately.
An example: picture a brand selling its own designed products. It keeps product management and payments on a ready-made platform. But it wants a fast, distinctive storefront that tells the brand’s story, bilingual content pages and collection pages. The storefront is built separately, and product information is pulled from the platform. The result is a look that belongs to the brand, with a back end already proven in payments and stock.
The price of a hybrid is maintaining two systems together. When the platform side updates, the connection needs checking. That makes regular maintenance even more important — we explain why in why website maintenance matters.
A checklist before you decide
Whichever approach you choose, these points should be discussed at the start. Some details below reflect selling in Türkiye; the questions themselves travel well.
- Payments. Which payment provider or bank gateway will be used? Do customers expect to pay in instalments? Does the platform support that payment method?
- Invoicing. If you are required to issue electronic invoices — in Türkiye, e-invoices and e-archive invoices — how each order reaches the invoicing system.
- Shipping. Integration with the courier, and the tracking number reaching the customer automatically.
- Marketplaces. If you also sell on marketplaces, managing stock from a single place.
- Legal texts. Distance-selling terms, pre-contract information, returns policy and privacy notices. We recommend taking legal advice on their content; our part is making sure they sit in the right place and the right step of the flow.
- Customer communication. Order confirmation, shipping notice, abandoned-basket reminder. These flows can be automated over email or messaging; see our automation service for more.
- Ownership. Who will hold the domain, the product data, the customer list and the source code? If you want to change platform, how will you get your data out?
Every item on this list also affects cost. Payment and invoicing integration, courier connections, multiple languages and marketplace syncing all widen the scope. We cover the general factors behind cost in what determines the cost of a website.
Common mistakes
- Wanting everything on day one. Planning a loyalty scheme, subscriptions and a mobile app before the shop has even opened delays the real work. Get the sales flow working first.
- Leaving product content until last. Without photographs and descriptions, even the finest platform will not sell.
- Ignoring speed. A product page that loads slowly on a phone loses the visitor before they ever reach the basket.
- Not thinking about data. Being unable to carry customer and order history across when you change platform is an expensive lesson.
Frequently asked questions
Does a small shop need a custom-built site?
Usually not. For a new shop with standard products, a ready-made platform is quicker and less risky. A custom build should come into the picture when your business model does not fit the ready-made patterns.
Can we move from a ready-made platform to a custom build later?
Yes. Product, customer and order data can be exported and carried into the new structure. Redirecting old product addresses to their new ones is essential for keeping your search visibility; we go into this in redesigning a website without losing SEO.
What determines the cost of an online shop?
The complexity of the product structure, payment and invoicing integrations, courier and marketplace connections, how bespoke the design is, the number of languages and the maintenance you need. We have no price list; we settle the scope in a first conversation and then send a written proposal.
Will we own the source code and the customer data?
With a custom build, the source code is handed over to you at delivery if you wish. On a ready-made platform the code belongs to the platform, but your product and customer data are yours; it is worth checking the export options at the outset.
If you would like to weigh up together which approach suits your shop, see our web design and development service, or write to us with a short description of how you sell.