Shopify vs. a Custom E-commerce Build: How to Decide

"Shopify or custom?" comes up early in almost every e-commerce project, and the honest answer depends on things specific to each business: the catalogue, the pricing, how orders really happen, and the budget for running it afterwards. Here's how to think it through.

When Shopify Wins

Shopify exists for a reason. For most standard retail e-commerce — physical products, standard pricing, normal checkout flows — it's genuinely excellent. The reasons to choose it:

• Time to market. A solid Shopify store with a premium theme and your products can be live in days, not months. For businesses that need to start selling now and iterate later, this is significant.
• The checkout is proven. Shopify's checkout is mature and heavily optimised. Building a custom checkout that beats it is hard, takes time, and isn't worth attempting unless you have very specific requirements.
• The app ecosystem. Email marketing, loyalty programs, inventory management, subscription billing, reviews — there's an app for almost everything, often free or cheap. Building these from scratch is expensive and takes focus away from your core product.
• Hosting, security, and compliance are handled. PCI compliance for payment processing, DDoS protection, automatic scaling during traffic spikes — Shopify handles all of this. Custom builds require you to think about it.

If your business sells products with standard variants (size, color), standard pricing (fixed or on sale), and you want to be up and selling quickly, Shopify is the right choice for your first version. We'd tell you that even though we build custom solutions.

When Custom Wins

Shopify starts showing its limits when your business has requirements that don't fit the standard retail model:

• Complex pricing logic. Tiered pricing, quantity breaks, customer-group pricing, contract-based pricing, dynamic pricing from an external system — Shopify can handle some of these through apps, but it gets hacky quickly. Custom builds handle this cleanly.
• Unusual purchase flows. Configurators, quote requests, multi-step ordering processes, auctions, subscription boxes with customization, B2B ordering portals — these fight against Shopify's assumptions about how a transaction works.
• High-volume B2B. Shopify Plus (the enterprise tier) is solid, but B2B scenarios with complex account hierarchies, purchase order workflows, or deep ERP integration are often cleaner in a custom build that you control entirely.
• Ownership and cost at scale. Shopify adds a transaction fee when you use a third-party payment provider instead of Shopify Payments, on top of the provider's own fees, and app subscriptions add up. At high volume, that can exceed the cost of running a custom platform. Work out the break-even for your own numbers.
• Performance requirements. For very large catalogues, complex faceted filtering or strict performance budgets, a custom Next.js front end with a purpose-built back end can outperform a heavily customised theme.

The Real Cost Comparison

People compare Shopify's monthly plan with the cost of a custom build. That's not the right comparison. Compare the total cost of ownership over two or three years.

Shopify's costs:

• The plan itself (check Shopify's pricing page for current prices in your market)
• A premium theme, or a custom theme
• Apps for email, reviews, loyalty, subscriptions and so on, usually billed monthly
• Payment processing, plus transaction fees if you use a third-party provider
• Developer time for customisation

A custom build's costs:

• The build itself, which is the big upfront number
• Hosting and third-party services (payments, email, search)
• Security, PCI scope and uptime, which become your responsibility
• Ongoing maintenance and updates, with a developer on call

For most stores in their first years, Shopify wins on total cost. As revenue grows and requirements get unusual, the calculation gets closer, so run it with your own figures rather than a rule of thumb.

The Headless Middle Ground

Shopify Hydrogen (or any headless Shopify setup with a custom Next.js frontend) gives you Shopify's checkout, inventory, and payments with full frontend control. It's a legitimate option when you want Shopify's backend reliability but need design and performance freedom that a standard Shopify theme can't provide.

The tradeoff: headless setups are more expensive to build and maintain than standard Shopify. You're effectively paying for both. But for brands where the frontend experience is a differentiator — luxury goods, design-led brands, experience-driven retail — it's often worth it.

Our Recommendation

Start with Shopify if you're in the first few years of an e-commerce business, your catalog follows standard patterns, and you want to focus on growth rather than infrastructure. You can always migrate later when you hit the limits, and you'll have real data about what you actually need.

Go custom from day one if your purchase flow is fundamentally non-standard, you have specific pricing complexity, or you're building a B2B platform rather than direct-to-consumer retail. Retrofitting custom logic onto Shopify is more expensive than building the right thing from the start.

Still not sure which side of the line you're on? Our e-commerce development page covers both routes, and we'll help you choose before anything is built.