We get the same question every few weeks from founders running e-commerce brands above the small-business threshold. They're on Shopify Standard or Advanced, doing somewhere between AUD $500K and $10M annually, and they're running into platform constraints that didn't exist when they launched. The question is always some version of "should we go custom, and if so, on what?"

The answer almost everyone gives them is wrong in one direction or the other. The Shopify partner agencies pitch Shopify Plus as the answer to everything. The custom-build agencies pitch a full Stripe-native rebuild as the answer to everything. Both pitches are biased by what the agency can sell. Neither is the honest architectural assessment.

The opinion up front: Shopify is the right answer for more brands than custom evangelists admit, and the wrong answer for more brands than Shopify partners admit. The decision turns on five specific questions, not on platform fandom. Most of the brands asking us this question can stay on Shopify with discipline. A minority should go custom on Stripe — and when they should, the upside is large.

The nuance: there's a third option most pitches skip — Shopify backend with a custom Stripe-native checkout. We'll cover when that's the right answer, which is more often than the all-in pitches suggest.

What "Shopify-managed" and "Stripe-native" actually mean

Let's get the terms tight before the trade-offs.

Shopify-managed means Shopify hosts the storefront, manages the product catalogue, runs the checkout, handles payments (via Shopify Payments or a configured gateway), and supplies the admin interface. The merchant configures, customises and integrates — but the core architecture is Shopify's. This includes Shopify Plus, Shopify Hydrogen (their headless storefront framework), and Shopify-managed checkout on a custom frontend.

Stripe-native means Stripe is the payments layer and everything else — catalogue, cart, checkout flow, order management — is built by the merchant or their dev team. The site runs on whatever framework the team prefers (usually Next.js for a custom Australian build), Stripe Checkout or Stripe Elements handles the payment, and the merchant owns the customer database, the order data, and the admin tooling.

There are hybrids. Shopify with custom Stripe Checkout is one. Headless Shopify (storefront API + custom frontend, still using Shopify's checkout) is another. We'll come to those.

The five questions that drive the decision

After running this analysis a few dozen times, the variables that matter are these. Not aesthetics. Not "future-proofing." These specific operational questions.

1. How weird is your product?

Standard products with sizes, colours, variants, and inventory? Shopify is built for you. The catalogue model is mature, the variant logic works, the apps ecosystem covers almost everything you'd want.

Custom-configured products with hundreds of options? Made-to-order with options that drive price? Bundles where the price is a function of customer-supplied data? Subscriptions with multiple frequencies and product swaps? B2B with negotiated pricing per customer? At each of these, Shopify gets harder. You're stacking apps to model the complexity. Each app costs money, adds latency, and represents a place the build can break when Shopify updates.

A rule of thumb: if your product can be described by Shopify's standard variant model with no apps, stay on Shopify. If you've stacked three or more apps to model the product, custom starts to look better.

2. How custom is your checkout?

This is the hidden constraint that surprises a lot of brands. Standard Shopify (not Plus) gives you essentially no checkout customisation. Plus gives you Checkout Extensibility — limited custom logic via extensions, no full layout control. Hydrogen with the checkout still on Shopify Plus gives you the same checkout. Full checkout customisation only exists on Shopify Plus with the Checkout API, which has real limits.

If your checkout needs are conventional — cart, address, shipping, payment, confirmation — Shopify is fine. If you need a multi-step configurator built into checkout, conditional product additions, split shipments handled at checkout, multi-currency with locale-specific tax math, or pre-authorisation flows for high-value items — custom Stripe is more flexible.

The data from Swell's 2025 custom checkout report shows fully-optimised custom checkouts run with 7 form fields versus a 14.88-field industry average, and stores in the top 20% of conversion hit 3.2%+. Shopify's standard checkout is closer to the industry average than the top quintile.

3. What's your monthly GMV?

Money matters. The break-even economics of Shopify Plus versus custom are tightly bounded.

Shopify Plus starts at USD $2,300/month on a 3-year commitment, USD $2,500 on a 1-year. Above roughly USD $800K monthly GMV the flat fee converts to a variable fee that scales with revenue. Add the apps you'll need — typically USD $500-2,500/month for a real Plus deployment — and the realistic monthly Shopify Plus bill for a mid-sized brand is USD $4,000-10,000.

A custom Stripe-native build has a different cost shape. The build itself is a one-time capital expense — say AUD $80,000-250,000 for a serious build with admin tooling. Monthly running costs are low: Stripe fees (essentially the same as Shopify Payments), hosting on Vercel ($200-2,000 depending on traffic), database ($50-500), and ongoing dev work ($0-5,000 depending on the team).

For a brand doing AUD $5M annual revenue, the five-year cost of Shopify Plus is roughly $300K-$600K. The five-year cost of custom is roughly $200K-$400K including build and run. The numbers tilt toward custom as GMV scales, but not as dramatically as the custom evangelists claim. Below AUD $2M annual revenue, Shopify is almost always cheaper net of all costs. Above AUD $20M, custom is almost always cheaper. The middle is where the analysis matters.

4. How many people on your team can use developer tooling?

This is the question custom-build agencies don't ask. Shopify's value is the admin interface — your CEO, your customer service team, your warehouse manager can all use it. A custom build means custom admin tooling, which means the people who run the business need to be comfortable with whatever interface your devs build.

If you have a non-technical team and a small dev capacity, Shopify's standard interface is a real asset. If you have a technical team that builds their own internal tools, custom gives you the freedom to build admin exactly to your workflow. We've seen custom builds fail not because the codebase was bad but because the warehouse manager hated the admin interface and went back to spreadsheets.

5. What's your three-year product roadmap?

Shopify is built for a class of e-commerce that hasn't changed much in a decade — products with variants, sold to consumers, with conventional checkout. If your roadmap stays inside that model, Shopify scales fine.

If your roadmap includes things like marketplace functionality (multi-vendor), white-label B2B, complex usage-based pricing, integrated services alongside products, or any model that diverges from "buy this thing at this price" — custom architecture lets you build what you actually need. Trying to force Shopify into a marketplace model has burned more brands than custom architecture has.

When Shopify (standard or Plus) is the right answer

The honest "stay on Shopify" cases:

Annual revenue under AUD $2M and growing
Product model fits standard variant logic
Checkout requirements are conventional
Small team without dedicated dev capacity
Roadmap stays inside standard e-commerce
Heavy dependence on Shopify-specific apps (Klaviyo, Recharge, Postscript, Shop Pay)

For these brands, the right move is to use Shopify well. Optimise the theme, trim the apps, get the page speed up, fix the conversion-killers in the conventional checkout. There's plenty of upside available without changing platforms.

When custom Stripe-native makes sense

The cases where custom genuinely pays off:

Annual revenue above AUD $5M with high gross margin to fund the build
Non-standard product model that's costing 3+ apps to support
Need full control of checkout for conversion or compliance reasons
Technical team capable of running the platform
Roadmap includes features Shopify can't support cleanly
Multi-region or multi-currency complexity that Shopify's tax/shipping models don't handle well

In this case, the architecture typically looks like Next.js frontend, headless CMS for content (Sanity, Payload, Contentful), Postgres database for products and orders, Stripe for payments, Vercel or similar for hosting. The build is meaningful — six months and AUD $150K+ for a competent execution. The payoff is full ownership of the architecture and dramatically lower per-transaction friction over time.

We covered some of the alternatives in a previous piece. Saleor and Medusa are credible open-source backends if you don't want to build the product/order layer yourself. Vercel Commerce is a reference implementation that supports multiple backends.

The hybrid that nobody pitches

The architecture pattern almost nobody talks about and that genuinely works for a meaningful subset of brands: keep Shopify as the backend (catalogue, inventory, fulfilment) and build a custom Stripe-native checkout for the conversion-critical flow.

This works because:

The product, inventory, and order management piece is what Shopify is genuinely good at, and the apps ecosystem around it is mature
The checkout is where conversion is won or lost and where Shopify's customisation limits hurt most
Stripe's Payment Intents API lets you build a checkout that handles complex flows Shopify can't

The integration cost is real — you're maintaining a Shopify storefront and a custom checkout, with sync logic between them — but the build is smaller than a full custom rebuild and the operational benefits show up in the conversion data. We've seen this architecture deliver 15-30% checkout completion lifts over standard Shopify Plus on the same traffic.

The caveat: this only works for Shopify Plus or with Shopify's Checkout API access. Standard Shopify locks the checkout entirely.

The decision framework, distilled

If you're staring at this and trying to figure out which way to go, the short version:

Stay on standard Shopify if revenue is under AUD $2M, product model is conventional, team is small.

Move to Shopify Plus if you've outgrown standard but the product model still fits, you need the throughput, and you can absorb the USD $2,500/month plus apps. We covered some of the Plus-specific tradeoffs in our headless commerce explainer.

Go custom Stripe-native if the product or checkout model is the real constraint, revenue justifies the AUD $150K+ build, and you have technical capacity to run the platform.

Consider the hybrid if you're on Shopify Plus, the catalogue is fine but the checkout is costing you conversion, and you can budget a smaller custom checkout build alongside the existing storefront.

The trap to watch for

The most expensive mistake we see is brands going custom for the wrong reason — usually because a custom-build agency pitched it as inevitable, or because a Shopify constraint felt more important than it actually was. Custom is a real commitment. You're hiring a team to maintain a platform. If the brand can't sustain that team — through revenue, through hiring, through ongoing investment — the custom build becomes legacy code in three years and the next agency pitches you a Shopify migration.

The cleanest custom builds we've seen come from brands that knew exactly which Shopify constraint they were escaping, had quantified the cost of that constraint, and had budget for a real team. The painful custom builds came from brands that wanted to look modern or were sold a custom build by a consultant.

If you're trying to figure out where your brand actually sits — what your Shopify cost looks like fully loaded, what a custom build would actually take, what the hybrid would buy you — book a free audit. We'll give you the honest assessment, not a pitch for whichever architecture we'd prefer to build.

Stripe-Native vs Shopify: Real E-commerce Trade-Offs