We build custom commerce backends for a living. You'd expect us to tell everyone to leave Shopify.

We don't. For most stores, "just use Shopify" is correct. It's fast to launch, it's reliable, the app ecosystem is huge, and you don't need a developer to change a banner.

But there's a point where the platform stops saving you time and starts costing it. Here's how we tell the difference.

5 signs a store has actually outgrown Shopify

1. Your core logic is fighting the platform.
Custom B2B pricing per customer, quote-based ordering, unusual fulfilment, subscriptions with complicated rules, digital goods with their own delivery logic. If the thing that makes your business different needs three apps and a workaround to exist, that's a signal.

2. Your app stack has become your architecture.
When the store depends on a dozen apps that each own a piece of the data, with their own billing, their own scripts on your storefront and their own failure modes, you already have a custom system. It's just one you don't control.

3. Revenue-based fees are starting to hurt.
Platform plans plus transaction-based fees scale with your GMV. At some revenue level, the money you pay for the platform's convenience is larger than what it would cost to own the stack. Do the actual maths with your own numbers before deciding.

4. You need more than one frontend.
A web store, a mobile app, a B2B portal and in-store screens, all from one catalogue. Headless Shopify can do this, but if you're going headless anyway, the backend choice becomes open again.

5. You need to own your data and your code.
Some businesses need full control over where data lives, how it's modelled and who can access it, for compliance, integrations or simply because the store is the company.

Two or more of these, and it's worth a serious look. Zero or one, and stay.

3 bad reasons to leave

  • "Our site is slow." That's almost always the theme, the images and the app scripts. Fix those first. A custom build can be slow too.
  • "We want a unique design." A custom theme or a headless frontend on Shopify gets you that without replacing the backend.
  • "A developer told us custom is better." Ask them who maintains it after launch, and what it costs per year. (Yes, we're aware of the irony.)

What leaving actually costs

Self-hosting means everything Shopify did invisibly becomes your code: payment retries, multi-currency, inventory logic, admin tooling, uptime. That's not a reason not to do it. It's a reason to budget for it honestly.

The middle path people forget

You don't have to choose all or nothing:

  • Shopify + headless frontend: keep the backend, own the storefront.
  • Shopify + a custom service for the one thing it can't do, like a pricing engine or a fulfilment service.
  • Full replatform only when the core business logic itself has outgrown it.

If you've moved off Shopify, or seriously considered it and stayed, what tipped the decision? I'm genuinely curious where other devs draw the line.

We put the numbers side by side in what a headless commerce build actually costs, and wrote a checklist for when to replatform. For a real example of a store that did leave, here's how we moved one off Shopify without touching its frontend.

We're Kryeo, two founders building headless commerce on Medusa, Directus and Next.js.