Online store: when Shopify is enough and when a custom build pays off
An honest comparison between a platform like Shopify and a custom-built store, based on volume, margins and the integrations you actually need.

What you’ll take away
- Shopify wins on launch speed and upfront cost.
- A custom checkout wins once transaction fees start eating into margin.
- The key question is how many external systems the store has to touch.
When someone asks us “can you build me an online store?”, the honest first answer is another question: how many sales a month do you expect, and how unusual is your sales process? The answer decides whether Shopify is enough or a custom build pays off.
When Shopify (or similar) is the right call
If you are launching a new store with a standard catalog (clothing, accessories, physical products without complex configuration) and want to sell as soon as possible, a platform like Shopify is hard to beat on speed: catalog, payments, shipping and taxes already solved, with a reasonable learning curve for whoever runs it day to day.
Upfront cost is low and predictable: a fixed monthly fee instead of a development investment. To validate a business idea or launch fast, it is the sensible choice.
When the transaction fee starts to hurt
Shopify (and similar platforms) charge a transaction fee on top of the monthly subscription. At low volumes, it is a marginal cost. But past a certain sales volume, that fee — paid on every single sale, forever — can far exceed what a custom build would cost, amortized over two or three years.
Data point: at €300,000/year in sales, an extra 2% fee is €6,000 a year that never comes back, every year, indefinitely.
Beyond cost, there is a control question: on a closed platform, changes to policy, pricing or features depend on a third party, not on you.
When the catalog or process does not fit the mold
Complex product configurators (variants with cross rules, dynamically calculated pricing), deep integrations with an existing ERP, or a B2B buying process with different prices per client are cases where a standard platform starts forcing the business to fit its mold, instead of the other way around.
The question that actually decides it
It is not “how many sales do I make” in the abstract, but “how many external systems does each sale have to touch?” A store that just charges a card and sends a confirmation email can live comfortably on Shopify for years. One that has to sync stock with an ERP, apply different rates per customer type and generate an automatic invoice needs logic that standard platforms only handle halfway, through third-party apps that break with every update.
How we do it at Bitora
If your case fits a standard platform, we tell you directly — we do not sell custom development where it is not needed. Once volume or complexity already justify a custom build, we build the checkout, catalog and integrations without the limits of a closed platform, with the fee margin back in your account.
If you are unsure what fits your case, see the details on custom web development.
Does this fit your company?
Custom web development →You may also like

September 10, 20261 min read
Shipping an AI-built app without production surprises
From localhost or v0 to production: domain, SSL, secrets, backups — and why “works on my machine” is not a launch plan.

September 7, 20261 min read
What to ask for in a website quote (so you are not surprised later)
Implementation vs maintenance, exclusions and deliverables: how to read a corporate website quote without fine print.

September 2, 20263 min read
Packaged solution or custom build: how to choose without overpaying either way
When a fixed-scope product fits an SME, when you need owned code and integrations, and how to tell if a cheap package will cost more within a year.
Ready to digitize your business?
Request a free diagnostic and we will return a prioritized opportunity map, not a pitch.Free · Reply in 24h · No commitment
Request a free diagnosticNo commitment · Reply in 24h · support@bitora.es
