Decision guide
There are two expensive mistakes in e-commerce. One is building custom because it feels more serious, spending months and a large budget reinventing order management, inventory and checkout that Shopify would have given you on day one. The other is forcing a business into Shopify that the platform genuinely can't accommodate, then paying the price in workarounds, apps and limitations for years.
We build both — classic Shopify shops and custom headless e-commerce — so we don't have a platform to sell you. This is the framework we use ourselves to settle the question before anyone writes code.
TL;DR
Key takeaways
- Standard B2C with physical products: pick Shopify with a tailored theme. It's fastest to launch, cheapest to run, and marketing can work in it directly.
- Headless (Shopify as engine, Next.js as frontend) makes sense when brand, performance or multi-language demands more than a theme can deliver — not before.
- Custom e-commerce is for complex B2B pricing, deep ERP integrations, and business models that don't look like a classic webshop.
- You can start on Shopify and go headless later without throwing anything away — orders, inventory and payments stay in Shopify Admin.
- More apps is not a strategy. A Shopify shop with twenty apps is often a sign the needs have outgrown the theme.
Why the question comes up at all
Shopify won standard e-commerce for a good reason: orders, inventory, payments, shipping and an admin panel non-technical people can use, out of the box. For a business selling physical products in a recognisable B2C pattern, it's hard to argue for anything else as the first choice.
But "Shopify" in practice covers three very different architectures. An Online Store with a theme is one thing. Shopify as a commerce backend with a custom frontend is another. And then there are the solutions where Shopify isn't the engine at all — where the pricing, flows or integrations demand something else. The confusion arises because all three get called "a webshop".
So the question isn't "Shopify or not". It's: where on the scale from standard to custom does your business actually sit — and where will it sit in two years?
Shopify theme vs. headless/custom storefront
Shopify with a tailored theme
Fastest to launch, cheapest to run, and daily operations live entirely in Shopify Admin.
- Live in weeks, not months
- Marketing builds pages, campaigns and collections themselves
- Checkout, payments and shipping solved and PCI-compliant from day one
- Low running cost: a theme plus a few well-chosen apps
- Design is good — but within the theme's boundaries
Headless or custom storefront
Full design control and top-tier performance — against a bigger investment in build and operations.
- Frontend in Next.js: the brand decides, not the theme
- Edge-cached product pages and green Core Web Vitals
- Content and commerce blend freely (magazine + shop, configurators)
- Multi-language and multi-market controlled tightly in one codebase
- Requires developers in the loop — after launch too
When is which the right call?
Read the left column as your situation — the right column is what we typically recommend in that situation.
Your situation
You sell physical products B2C in a standard pattern and need to launch fast
Our recommendation
Shopify with a tailored theme. Spend the money on product data, photography and marketing instead of architecture.
Your situation
The theme constrains the design, or the site needs to be both magazine and shop
Our recommendation
Headless: Shopify as engine, Next.js as frontend. Day-to-day admin continues unchanged.
Your situation
You're selling into multiple markets with different languages, currencies and VAT rules
Our recommendation
Headless with i18n designed in from the start — or custom if the market logic is complex enough.
Your situation
You have per-customer B2B pricing, credit limits or order-approval flows
Our recommendation
Custom e-commerce or Commerce Layer — this is where Shopify starts fighting back.
Your situation
Your product data lives in an ERP/PIM and must stay authoritative
Our recommendation
Headless or custom with the ERP as source of truth — Shopify inventory alone won't cut it.
Your situation
You're not sure
Our recommendation
Start on Shopify. It's the reversible decision — headless can be built on top later.
The signals you've outgrown standard Shopify
The clearest signal is the app list. When a shop runs fifteen to twenty overlapping apps, you pay both in monthly licences and in speed — each app typically injects its own script into the storefront. A long app list is rarely an app problem; it's a sign the business's needs have grown past what the theme and platform solve naturally.
The second signal is workarounds in pricing and flows. If you maintain customer-specific price lists in spreadsheets next to Shopify, approve B2B orders manually over email, or have built a forest of metafields to represent your product structure — you're already spending custom-level effort, just without the custom-level benefits.
The third is performance and SEO. Shopify can absolutely rank and score green on Core Web Vitals — but a heavy theme with many app scripts can't. If mobile speed has become a real conversion problem and cleaning up the theme and apps doesn't move enough, a headless frontend is the next honest answer.
Questions we get again and again
Can a Shopify shop rank as well on Google as a custom build?
Yes, if it's set up right. Structured data for products, correct canonical handling of variants and collections, and a fast theme without app bloat go a long way. A custom frontend gives more control over rendering, but that's rarely what decides rankings — content and technical hygiene matter more.
Do we lose SEO by migrating to Shopify from WooCommerce or Magento?
Not if the migration is planned properly. What matters is redirects from every single old URL to its new counterpart, preserved titles and descriptions, and verification in Search Console after the move. Losses typically happen when redirects are skipped or only cover the homepage and categories.
Isn't headless just more expensive Shopify?
During the build: yes. You give up the theme's "free" frontend and build your own. The gain is full design control, performance, and the freedom to blend content and commerce. If those gains aren't concrete for your business, headless is the wrong expense — and we say so when asked.
What about Shopify Plus?
Plus solves some of the limits — checkout customisation, more markets, B2B features — at a significantly higher platform cost. It's the right answer for some. But if your complexity lives in pricing, integrations or the data model, Plus doesn't move the problem; then it's the architecture that needs to change, not the subscription.
Can we run the shop ourselves afterwards?
That should be the requirement regardless of vendor. A healthy Shopify setup means the theme is version-controlled in Git, apps are documented, and shop, domain and accounts live with you. Then you can bring the work in-house or switch agencies without starting over.
Facing the choice right now?
Have a no-strings conversation about your webshop.
We'll help you settle whether the answer is a tailored theme, headless on Shopify, or custom — and sometimes the answer is to stay where you are. We say that too.