When does it make sense to move to Shopify Plus?

"Should we be on Plus?" usually arrives wrapped in something else: a checkout you can't customise the way you want, a wholesale channel held together with discount codes, or a Black Friday that nearly fell over. Plus is a real step up in capability, and a real step up in cost. The question worth answering isn't "is Plus better" (it is), it's "are you actually hitting the ceiling of the plan you're on?"

Here's how we work that out with a merchant.

What you're really paying for

Plus is roughly a £1,800+/month commitment, so it only makes sense if you'll use the things it unlocks. The ones that actually move the needle:

• Checkout extensibility. Custom checkout UI, more Shopify Functions, and the headroom to do things the standard checkout won't.
• B2B / wholesale at scale. Since April 2026, native B2B comes with every plan, with up to three catalogues. Plus adds unlimited catalogues, catalogues assigned to each company and location, and deposits and partial payments. If you have many trade accounts on their own pricing, this is where Plus earns its fee.
• Multiple stores. Up to ten storefronts under one plan, which is where international and multi-brand setups stop being a tax.
• Higher API limits and Flow. More automation, fewer rate-limit walls, and the room to build the integrations that a busy operation leans on.

If none of those map to a problem you have right now, you're paying for a tier you won't use.

The signals that say yes

We lean towards recommending Plus when we see:

• Checkout is the blocker. You need fields, logic, or branding at checkout that only Plus allows, and it's costing you conversions or operations time.
• B2B has outgrown three catalogues. Native B2B on Advanced handles a few trade price levels well. When larger accounts each need their own catalogue, assigned to their company and locations, or pay deposits on big orders, that's a Plus job.
• You're running, or about to run, multiple storefronts. Separate regions, currencies, or brands. Ten stores on one plan beats ten plans.
• Volume is straining the limits. Webhook throughput, API calls, or sales spikes that the current tier throttles.
• The Plus cost is small next to the revenue it protects. At the right volume, the fee is rounding error against a single peak-season day.

The signals that say not yet

Just as often, the honest answer is stay where you are and spend the money on the store itself. Hold off when:

• The pain is theme or app shaped, not platform shaped. A lot of "we need Plus" turns out to be "we need the theme fixing" or "we need one custom app." Both are far cheaper.
• You want Plus mainly for checkout branding vanity rather than a measured conversion problem.
• Your volume is comfortably inside standard plan limits.
• Nobody on the team will actually use Flow, B2B, or the extra stores. Unused capability is just cost.

A rough decision table

The shorthand we use:

The pattern: if the problem lives in your theme or an app, Plus is the expensive way to solve it. If it lives in the platform's own ceiling, that's exactly what Plus is for.

A concrete example

A merchant came to us certain they needed Plus because wholesale was "a mess." Digging in, two different problems were tangled together.

• The retail checkout was fine. No Plus-only feature was actually required there.
• The wholesale side genuinely needed company accounts, its own pricing for each of its larger trade accounts, and net-30 terms. Native B2B on the standard plans now covers company accounts and terms, but it tops out at three catalogues, so a separate price list for every big account is squarely Plus territory, and no amount of theme work fakes it cleanly.

So the move was justified, but for one specific reason, not the vague sense that a bigger store needs a bigger plan. Naming the real driver is what turns it from a £22k/year guess into a decision.

The honest trade-off

Plus buys you capability and headroom. It does not, on its own, make you more money. The merchants who get value from it are the ones who had a concrete platform ceiling and a plan to use what's on the other side of it. The ones who regret it upgraded on a feeling and kept the same store.

So our default is: prove the ceiling first. If the thing you want is genuinely Plus-only and it's costing you real revenue or real hours, the upgrade pays for itself quickly. If it's a theme, an app, or a tidy-up, do that and keep the cash.

If you're weighing it up, send us what's pushing you towards Plus and we'll tell you straight whether it's a platform problem or a build problem. Working out which one it is usually saves more than the call costs.