How much does Shopify Plus cost in the UK in 2026?

For UK merchants, Shopify Plus typically starts at around £1,800 per month on a three-year contract, or £1,950 per month on a one-year term. Once your monthly gross merchandise volume exceeds approximately £650,000, the pricing shifts to a revenue-based model, generally charging 0.25% of total sales. You must also account for payment processing fees, which run roughly 1.5% to 1.9% plus 20p for domestic cards on Shopify Payments.

What is the difference between Shopify Advanced and Shopify Plus?

The primary differences are architectural control and multi-store capacity. Shopify Plus provides Checkout Extensibility, allowing custom logic via Shopify Functions, whereas Advanced relies on standard checkout configurations. Plus also includes 9 expansion stores for international or distinct brand architecture, native B2B catalogues, and doubles the GraphQL Admin API rate limit to 80 points per second, which is critical for complex ERP integrations.

When does Shopify Plus make sense for a growing brand?

In our experience, Shopify Plus becomes mathematically viable when your annual GMV crosses £1M to £3M. At this scale, the operational savings from consolidating B2B wholesale orders, automating processes with Shopify Flow, and deprecating expensive third-party apps offset the £1,800 monthly platform fee. If your GMV is under £1M and your only requirement is a custom design, the Advanced plan is usually sufficient.

What is Shopify Plus: UK Engineering Decision Guide (2026)

Shopify Plus is the enterprise tier of Shopify, differing from Standard and Advanced by granting backend codebase access, dedicated B2B catalogues, and multi-store administration. For UK merchants, it typically starts at around £1,800/month, replacing the standard app stack with native Checkout Extensibility, higher API rate limits, and Shopify Functions. It becomes mathematically viable when your annual GMV crosses £1M and the operational cost of managing disparate international stores or manual wholesale orders exceeds the platform fee.

What changes in your codebase when you upgrade to Shopify Plus

The most immediate shock for engineering teams moving to Shopify Plus is the loss of checkout.liquid. For years, agencies hacked the checkout DOM using JavaScript injected into this file to force custom validation or reorder fields. That era is over. Shopify Plus enforces Checkout Extensibility, a locked-down environment where you cannot manipulate the DOM directly. Instead, you build UI Extensions using React-based components that render securely within predefined checkout zones.

This shift fundamentally improves security and reduces the friction of platform upgrades, but it requires a complete rewrite of your checkout customisations. You must adopt the Storefront API and the GraphQL Admin API for complex data fetching. Standard Shopify plans heavily throttle API requests, offering 40 points per second on the GraphQL Admin API. Plus doubles this to 80 points per second, which is critical when your NetSuite integration needs to sync 5,000 inventory updates in a few minutes. Furthermore, Plus provides the Multipass API, allowing direct single sign-on across separate subdomains or external forums. If you have an existing user database, Multipass prevents the friction of forcing customers to create new credentials.

How much Shopify Plus actually costs in the UK (2026)

The base platform fee for UK merchants typically starts at around £1,800/month on a three-year term, or around £1,950/month on a one-year rolling contract. However, that is just the floor. Once your store crosses roughly £650,000 in monthly sales—the GBP equivalent of the $800,000 USD threshold—the pricing shifts to a revenue-based model, typically around 0.25% of your gross merchandise volume. If you process £2,000,000 in a peak month, your platform fee scales accordingly, capped at a maximum ceiling that you negotiate during the sales process.

You also need to model payment processing meticulously. If you use Shopify Payments, domestic UK cards typically process at around 1.5% to 1.9% plus a 20p fixed fee, depending on your exact volume and card mix. If you insist on retaining an external gateway like Adyen or Stripe, Shopify enforces a 0.20% security and compliance fee on every transaction. This penalty adds up quickly on high-volume days like Black Friday. For a detailed breakdown of total cost of ownership, including the hidden tax of maintaining a sprawling app stack, review our guide on Shopify Plus pricing.

Shopify Markets vs Expansion Stores for international growth

Standard Shopify relies on Shopify Markets to handle multi-currency and localised pricing. Markets is excellent for a single-inventory business shipping globally from a central UK warehouse. It handles currency conversion, local pricing rules, and duties calculation within a single admin dashboard. However, it breaks down when your operational reality diverges. If you open a US 3PL, you cannot easily route orders from specific US states to that specific warehouse while maintaining entirely separate product merchandising in a single Markets setup.

This is where the 9 included expansion stores become necessary. An expansion store is a completely separate Shopify instance. You get a dedicated admin, a distinct app stack, and isolated inventory. The trade-off is operational overhead. Running three expansion stores means maintaining three theme codebases and configuring your ERP to handle three separate data streams. We typically advise clients to stretch Shopify Markets as far as it can go, and only spin up an expansion store when the legal entity, inventory pool, or payment gateway strictly requires isolation. The engineering cost of syncing catalogues across multiple instances is non-trivial, even with tools like Matrixify.

B2B on Shopify Plus: Handling complex wholesale catalogues

Historically, running a wholesale channel on Shopify meant relying on clunky third-party apps that duplicated variants or used complex discount scripts. Shopify Plus solves this natively with its B2B primitives. You can assign company profiles, configure distinct price lists, and set net-30 or net-60 payment terms directly in the admin.

However, it is not a silver bullet for every legacy setup. We recently handled a Plus migration for a UK DTC brand in the £3M-£8M GMV band, moving them off Magento 2 with a Black Friday hard deadline six weeks out. The legacy platform relied on a heavily customised cartridge layer for variant-bundled products. The test catalogue passed perfectly because the bundles were under 10 variants. However, the real catalogue had bundles with 40+ child SKUs, and the line-item splitter timed out in the cart. Instead of forcing the native checkout to handle the load, we moved the bundle expansion from a cart-time Function to a post-purchase webhook that splits the order into child line items downstream in NetSuite. The storefront stayed fast, we hit the soft cutover date, and the webhook still runs in production. When a migration has a hard cutover, the wrong question is whether you can replicate every legacy feature. The right question is where you can move the legacy complexity so the storefront stays clean. For more on structuring wholesale, see our Shopify Plus B2B guide.

Shopify Functions in production: Managing WebAssembly limits

Shopify Functions replace legacy Ruby scripts with WebAssembly. You write them in Rust, JavaScript, or AssemblyScript, compile them to Wasm, and Shopify executes them at the edge. This provides sub-millisecond execution for custom discounts, delivery customisations, and cart transformations. But performance is not infinite. Shopify caps each invocation at 11 million WebAssembly instructions. If you run complex discount logic over a cart with 150 line items, you will hit this ceiling.

Chaining four Shopify Functions on cart-transform is the engineering equivalent of stacking three fridges on a wheelie chair. You have to be strategic. With recent platform updates like metaobject access in Functions and local binary testing, you can shift some reference data out of the payload, but the instruction budget remains the ultimate arbiter of what you can build. We have found that moving non-critical calculations to asynchronous webhooks is the safest way to protect checkout latency. For a deeper dive into managing these limits, read our notes on Shopify Functions in production.

When Shopify Plus is overkill vs when it mathematically pays off

The most common mistake we see is merchants upgrading to Plus solely for design control. If your annual GMV is under £1M and the only reason to go Plus is to tweak the checkout aesthetic, it does not pay off. A well-optimised Dawn theme on the Advanced plan will serve you perfectly well.

However, there is a clear inflection point where the platform fee becomes a rounding error compared to the operational savings.

When Shopify Plus mathematically pays off

Annual GMV exceeds £3M: At this scale, the native B2B features and API limits prevent your app stack tax from exceeding the platform fee.
Complex B2B requirements: If your wholesale channel requires distinct company profiles, net payment terms, and custom price lists, the native B2B primitives replace fragile third-party apps.
Multi-region warehousing: When you need entirely separate inventory pools and localised 3PL routing for the US versus the UK, the 9 included expansion stores become necessary infrastructure.

Once you cross £3M in annual GMV, the native automation tools like Shopify Flow (with Plus-exclusive B2B triggers) and the removal of staff account limits usually justify the cost. You are no longer paying for a shopping cart; you are paying for an enterprise orchestration layer.

What to do next: Auditing your migration readiness

Upgrading to Shopify Plus or migrating from a legacy platform is not merely a licensing change; it is an architectural reset. The platform provides the primitives to build a highly scalable, globally distributed commerce stack, but it will not prevent you from building a slow, app-heavy monolith if you lack engineering discipline. Running an app stack with no review process is gardening with no gardener — eventually you cannot see the patio.

Before you sign a three-year contract, you need to validate that your existing data models and checkout dependencies can survive the transition.

Map your checkout dependencies. Audit every third-party script currently loading in your legacy checkout. Because Checkout Extensibility locks down the DOM, any app relying on DOM manipulation will fail.
Audit your variant structures. Export your product catalogue and flag any product exceeding 100 variants. You will need to build custom grouping logic or rely on the native combined listings API to handle these on Plus.
Calculate the total cost of ownership. Model your peak trading month against the 0.25% revenue share and the 0.20% external gateway penalty to understand your true platform fee ceiling.
Prototype the data migration. Run a test import of 1,000 complex orders into a sandbox Plus environment. Validate that your downstream ERP correctly maps the Shopify order IDs and tax lines before committing to the cutover.

If you are evaluating whether your current GMV justifies the move, map your app spend against the native Plus features. Often, deprecating six redundant third-party apps pays for the platform fee difference entirely. If you need an engineering partner to handle the technical heavy lifting of a migration, we can help you model the exact architecture required.