Shopify or custom build — an honest framework for ecommerce founders.

It is the question we hear from ecommerce founders more than any other. Usually framed as a binary: Shopify or custom? The framing is wrong, and it leads to wrong decisions in both directions — founders who dismiss Shopify out of hand because they want something “bespoke”, and founders who choose it by default without understanding what a well-built Shopify store actually requires.

The real question is not about the platform. It is about what your business actually needs from its website — what the purchase flow requires, what the performance requirements are, what the brand demands — and then choosing the architecture that serves those needs with the least overhead.

When Shopify is the right answer (most of the time)

Shopify is mature, well-supported, and built specifically for businesses that sell physical products. Its checkout converts. Its ecosystem of apps covers the majority of use cases. Its infrastructure handles traffic, payment processing, and fraud detection at a level that would take significant engineering effort to replicate from scratch.

For a business selling a range of physical products — homewares, apparel, consumables, supplements, pet supplies — Shopify is almost certainly the right foundation. Not because it is the only option, but because the marginal gain from a different platform rarely justifies the additional cost and maintenance burden.

The question, for most product founders, is not Shopify versus something else. It is how well you build on Shopify. A thoughtfully built, custom-coded Shopify store and a template store share a platform and almost nothing else.

The difference between a good Shopify build and a template

A premium Shopify build does not start with theme selection. It starts with a product photography brief, a performance budget, and custom Liquid code written specifically for the brand and its catalogue.

Our Fetch & Form build is an example of what this looks like in practice. Fetch & Form is a custom dog breeding platform — a product catalogue where each listing is a breeding pair, and the purchase flow is a multi-step commission enquiry with breed filtering, waitlist management, and a structured intake form. None of that exists in any Shopify theme. It was built in Liquid from scratch, within a Shopify architecture, and the store achieved a 96 Lighthouse performance score on mobile.

That score is not a default Shopify outcome. It requires deliberate engineering decisions made throughout the build — image optimisation, font loading strategy, script management, render-blocking elimination — none of which happen automatically on any platform.

The gap between a template Shopify store and a considered custom build is significant, and it is measured in conversion rate, performance, and brand expression — not in platform features.

When custom makes sense

There are genuine scenarios where custom development — or a headless Shopify architecture — is the right call. They are less common than the enthusiasm for “bespoke” solutions suggests, but they are real.

Custom is warranted when the purchase flow is genuinely non-standard and cannot be achieved within Shopify's existing architecture. A product configurator with complex conditional logic, a subscription model with branching renewal rules, a B2B portal with account-level pricing — these are cases where the limitations of Shopify's standard checkout become actual constraints rather than theoretical ones.

It is also warranted when performance requirements exceed what a well-built Shopify theme can achieve. For most ecommerce businesses, a well-built Shopify theme is fast enough. For a brand whose performance target is sub-1-second LCP across all devices, or whose catalogue is large enough to create rendering complexity, a headless approach may be justified.

Finally, it is warranted when the brand's design requirements cannot be satisfied within Shopify's template system — when the visual experience the brand demands requires a level of layout and interaction control that Shopify Liquid cannot support. This is rare, but it is real for certain premium or luxury brands.

What headless Shopify actually is

The term gets used loosely, so a plain-language explanation: a headless Shopify setup separates the front-end (what customers see and interact with) from the back-end (where products, orders, and checkout are managed). The front-end is custom-built in React or Next.js and talks to Shopify's APIs. The back-end remains Shopify.

The result is maximum design and performance flexibility at the front, with Shopify's proven commerce infrastructure at the back. The tradeoffs: meaningfully higher build cost, a more complex technical architecture to maintain, and a development process that requires experience with both React and Shopify's Storefront API. It is worth those tradeoffs in the specific scenarios above. It is not worth them for most product businesses.

For most ecommerce founders, the answer is Shopify, built well. The variable is the quality of the build — and the difference between a template and a considered custom build is the difference between a site that functions and one that performs. If you are based in Brisbane and want to understand what a premium Shopify build involves, our Shopify development practice is a good place to start.