Shopify vs Custom Next.js Store: Which Should You Pick?

Choosing between Shopify and a custom website is the first real technology decision most ecommerce brands make, so here is the short version. If you are starting out or doing under roughly $500k a year in revenue, Shopify is almost always the right answer: it is fast to launch, secure by default, and its checkout converts well. A custom Next.js store starts to earn its price when the platform begins to squeeze, through app subscription stacks, checkout restrictions, template sameness or speed ceilings you cannot tune your way past. And there is a middle path, headless Shopify behind a custom front end, that gets you most of both. This guide walks through all three honestly, with costs.

What Shopify does brilliantly

Credit where it is due, and we say this as people who get paid to build the alternative: Shopify solved ecommerce infrastructure. On current pricing, a Basic plan runs about $29 to $39 a month and gives you hosting, a PCI compliant checkout, inventory, tax handling, fraud tooling and an enormous app ecosystem. You can be selling this week. The checkout is trusted by shoppers, which matters: familiarity at the payment step is worth real conversion. For a new brand, every hour spent building infrastructure instead of finding customers is an hour wasted, and Shopify removes almost all of those hours.

• Launch speed: days, not months, from idea to first sale.
• Security and compliance handled: PCI, SSL, fraud analysis, all included.
• A checkout shoppers recognise, with Shop Pay accelerating repeat purchases.
• Apps for almost everything, from reviews to subscriptions to bundles.
• No servers to babysit. Traffic spikes on launch day are Shopify's problem, not yours.

Where Shopify starts to squeeze

Brands do not leave Shopify because it stops working. They leave, or go headless, because of accumulating friction that shows up somewhere between the first $10k month and the first $100k month:

• The app stack bill. Reviews, subscriptions, search, bundles, loyalty, translations: each is a monthly fee, and $300 to $800 a month in apps is common for a scaling store.
• Checkout and theme limits. Deep checkout customisation is largely gated behind Shopify Plus, and theme code (Liquid) puts a ceiling on how different your store can feel from every other store using the same theme.
• Speed ceilings. Themes plus a dozen app scripts add JavaScript you cannot remove. You can optimise images all day and still lose the speed argument to code you do not control. Google's own benchmarks showed bounce probability climbing 32% as mobile load time goes from one second to three, which is why this ceiling costs money.
• Content is an afterthought. If your growth depends on editorial, SEO landing pages or rich storytelling around products, Shopify's content tooling feels thin.
• Transaction fees apply on most plans if you use an outside payment provider instead of Shopify Payments.

What a custom Next.js store gets you

A custom store built on Next.js flips the trade. Everything is yours: the design, the page speed budget, the URL structure, the checkout flow, the content system. There is no theme underneath, so the site can look and feel like your brand and nobody else's, and there is no app tax, because features are built once and owned rather than rented monthly. It is also the route to the technical SEO details that compound: clean structured data on every product, exactly the internal linking you want, and pages that ship only the code they need.

• Total design freedom, down to the last interaction.
• Speed as a feature: static rendering and image optimisation tuned to your catalogue, not to a theme's lowest common denominator.
• Payments on your terms through Stripe, whose standard card pricing is 2.9% plus 30 cents in the US, with no platform fee stacked on top.
• Content and commerce together: editorial, landing pages and product pages in one system, which is where organic growth lives.
• Own the code. No platform migration risk, no rented features.

The honest costs of custom: you are now responsible for hosting, for building the admin workflows Shopify gives you free, and for engineering time whenever you want a new capability. Fraud tooling, tax calculation and the trust halo of a familiar checkout all need deliberate work to match. Custom is a commitment, which is exactly why it should be a response to real friction, not a default.

What each path honestly costs

• Shopify template store: $29 to $299 per month for the platform, $0 to $500 a month in apps, and typically $1,500 to $10,000 if you hire help for setup and theme customisation.
• Custom Next.js store: from quotes we prepare, typically $8,000 to $40,000 to design and build for a small to mid-size brand, then modest hosting (often under $100 a month) and a maintenance arrangement. Larger agencies quote the same scope from $20,000 up, sometimes far up, which is worth knowing before assuming custom is out of reach.
• Headless Shopify + Next.js: platform fees as above, plus typically $10,000 to $50,000 for the custom front end, depending on catalogue complexity.

The middle path: headless Shopify with a Next.js front end

One practical requirement people miss: headless makes you responsible for the front end forever. You will want a development partner on call, because there is no theme store to fall back on when you need a new landing page template, and your marketing team's workflow for publishing content needs designing on purpose rather than inheriting whatever the theme allowed. Brands that go headless with that support in place love it; brands that go headless and then let the retainer lapse end up with a beautiful site nobody can safely change.

Headless means Shopify keeps doing what it is best at, products, inventory, orders, the checkout itself, while a custom Next.js front end replaces the theme entirely. Shoppers browse a site that is completely yours, then pay through the Shopify checkout they already trust. You keep the admin your team knows and shed the theme and app-script ceilings. The trade is cost and coordination: two systems, one more thing to maintain. It is our favourite recommendation for brands doing serious revenue who want brand distinctiveness and speed without rebuilding commerce plumbing from scratch.

Three real-world scenarios

The new apparel brand doing $3k a month

Stay on Shopify, without hesitation. At this stage the constraint is attention, not the platform: every dollar and hour should chase product-market fit and customer acquisition. A clean theme, good photography and fast shipping settings beat any replatforming conversation. Revisit when the app bill or the sameness starts costing real money.

The supplements brand doing $80k a month

This is headless territory. The brand lives on subscriptions and content: education pages, ingredient explainers, comparison articles that rank and convert. The theme is the bottleneck, page speed is capped by app scripts, and the app stack bill has crept past $600 a month. Keeping Shopify as the commerce engine while a Next.js front end takes over storytelling, speed and SEO is the move that pays for itself here.

The B2B manufacturer with quote-based pricing

Custom, and honestly it was never really a Shopify project. Account-specific pricing, quote requests instead of carts, integration with an ERP: modelling that inside a B2C cart platform means fighting the tool daily. A custom build that matches how the business actually sells will be cheaper over two years than the workaround stack, and the sales team will stop apologising for the website.

A note on switching costs: whichever direction you move, budget for migration itself. Product data, redirects for every URL that ranks, analytics continuity and a launch-day plan are part of the project, and skipping them is how stores lose their Google standing in a weekend.

Shopify vs custom website: a decision checklist

• Under $500k revenue, standard catalogue, no unusual flows: stay on Shopify and spend the difference on marketing.
• Growth blocked by template sameness, app bills or page speed: consider headless.
• Selling something Shopify models badly (configurators, quotes, subscriptions with odd rules, B2B pricing): custom is likely cheaper than fighting the platform.
• Checkout conversion is your bottleneck and you are not on Plus: test everything else first; the checkout is rarely the real problem.
• Cart abandonment worries you: it is universal, Baymard's research puts average abandonment around seven in ten carts, so fix speed, shipping surprises and trust signals before changing platform.

Our take as builders

We build both, so we have no platform religion. What we care about is that the money you spend shows up in revenue, which is why our advice is usually boring: start on Shopify, move to headless when specific friction justifies it, and go fully custom when your product demands it. If you want a second opinion on where your store sits on that curve, tell us about it and we will give you a straight answer within 24 to 48 hours, including the option that makes us the least money. Budget context lives on our pricing page, and our small business website cost guide covers the non-ecommerce side.