Shopify vs. custom-built ecommerce

We’re Shopify partners, and we build custom web applications. That means we don’t have a horse in this race — and it also means we get asked this question a lot, usually by organisations that have outgrown their current setup and aren’t sure whether the answer is “better Shopify” or “leave Shopify.”

There isn’t a universally right answer. There’s a right answer for your revenue, your margins, your operational complexity, and how much you value speed-to-market versus long-term ownership. Here’s how we’d actually think it through.

Start with what Shopify is genuinely good at

Shopify’s core strength is removing infrastructure risk. You’re not maintaining servers, patching security vulnerabilities, or building a checkout, payment reconciliation and fraud-detection system from nothing. A capable store can be live in days, not months, and the App Store covers the vast majority of standard ecommerce functionality — reviews, email marketing, subscriptions, loyalty — without custom development.

Shopify’s own pricing is straightforward. As of October 2026, UK plans run from £19–£25/month for Basic, £49–£65/month for Grow (their mid-tier) and £259–£344/month for Advanced, depending on whether you pay yearly or monthly, while Shopify Plus starts at £1,800/month for larger merchants. Online card fees with Shopify Payments range from 2% + 25p on Basic down to 1.3% + 25p on Plus, with an additional fee of up to 2% if you use a third-party payment gateway instead. Check Shopify’s pricing page for current figures.

For most organisations under roughly £400,000–£500,000 in annual online revenue, this is very hard to beat on cost and speed. You’re paying for a platform that a huge ecosystem of developers, apps and expertise already understands, and every pound of development budget goes toward your storefront and content rather than plumbing.

Where the maths starts to shift

The economics of Shopify change as revenue and complexity grow, for a few concrete reasons:

Transaction fees compound. At meaningful revenue, percentage-based fees on every transaction stop being a rounding error. An organisation processing £1 million a year on a standard plan can be paying a low-to-mid five-figure sum annually in transaction fees alone — money that a custom build, paying only payment-gateway costs, doesn’t hand over.

App bloat is real. Each additional app is another script loading on your storefront, and stores that lean heavily on apps to cover gaps in Shopify’s native functionality commonly run noticeably slower than a purpose-built storefront with only the functionality it actually needs. Slower pages cost conversions, and — per our Core Web Vitals post — increasingly cost search visibility too.

Some business models don’t fit cleanly. Complex B2B pricing tiers, multi-vendor marketplaces, subscription logic with unusual billing rules, or checkout flows that need to integrate deeply with bespoke inventory or ERP systems can all hit the edges of what Shopify’s checkout and admin will flex to, even on Plus.

Data ownership matters more as you scale. A custom architecture gives you full, structured access to your own customer and order data — which increasingly matters for personalisation, internal AI tooling, and analytics that go beyond what a third-party platform’s dashboards surface.

The middle path a lot of organisations miss: headless Shopify

This is the option that gets skipped in a lot of “Shopify vs custom” framing, and it’s often the right answer for an organisation that’s outgrown vanilla Shopify but isn’t ready to walk away from its backend entirely: keep Shopify as the commerce engine (checkout, inventory, payments, order management) but build a custom, fast, fully-controlled storefront on top using its APIs — which is exactly the kind of build we do on Next.js.

You keep Shopify’s operational simplicity and its checkout compliance, PCI handling and payment infrastructure, while gaining the performance, design freedom and content control of a bespoke frontend. It’s typically a materially smaller project than a fully custom platform, and it’s a sensible staging post for an organisation that isn’t certain a full custom build is worth it yet.

A rough framework for the decision

Stay on standard Shopify if: you’re under roughly £400K–£500K in annual online revenue, your product and checkout needs are largely standard, and your priority is speed and low upfront cost over long-term ownership.

Consider headless Shopify if: you’re seeing real page-speed or design-flexibility limits from apps and themes, but your checkout and backend needs are still well served by Shopify itself.

Consider a fully custom build if: you’re well past the point where transaction fees are material, your business model doesn’t fit standard checkout logic, or your product depends on tight integration with internal systems that off-the-shelf platforms can’t reach.

These are genuinely rough thresholds, not hard rules — an organisation at £300K with an unusually complex B2B pricing model can hit custom-build territory earlier than one at £600K selling straightforward consumer products. The right test isn’t your revenue figure in isolation; it’s whether Shopify’s constraints are currently costing you more, in lost conversion, developer time working around limitations, or fees, than a custom build would cost to build and run.

The takeaway

Shopify isn’t something organisations “graduate from” by default, and custom-built isn’t inherently better — it’s a genuine trade of upfront cost and flexibility against ongoing platform fees and constraints. Most are well served by Shopify for longer than they expect. The ones we’d actually recommend moving away are those where transaction fees, app-driven performance problems, or a business model Shopify wasn’t built for are now costing more, in real terms, than a custom or headless build would.

If you’re at that inflection point and not sure which side of it you’re on, we’re happy to look at your numbers with you — no pressure toward either answer. Get in touch.