Plans and Shopify Plus

The online and in-person rates below are the euro view of the pricing page on 2026-10-27. Each online rate is a percentage plus a fixed amount per order; the fixed amount is EUR 0.30 for cards, EUR 0.35 for Klarna, EUR 0.25 for Bancontact and iDEAL, EUR 0.20 for Bizum and none for in-person cards.

The Agentic plan charges online card rates from 2.1% plus EUR 0.30 and no monthly fee. Shopify Payments availability, local payment methods and presentment in local currencies depend on the store’s country, and the pricing page marks local currency prices and local payment methods as requiring Shopify Payments.

When a merchant uses a gateway other than Shopify Payments, Shopify charges a fee on every order. The figure on the pricing page is global, not per country.

The Help Center describes this fee on Plus as "a small percentage fee to Shopify for security and compliance". The built-in fraud analysis also requires Shopify Payments, which is a second reason many merchants prefer it.

For a given monthly revenue and order count, the monthly cost of a plan is the subscription plus the percentage rate times the revenue plus the fixed amount times the number of orders. The script below applies that formula to the euro prices above, assumes an average Pocket Coffee order of EUR 28 and computes both the monthly cost and the revenue at which the next plan becomes cheaper. It ignores everything but fees: it does not value staff accounts, locations or features, and it does not model the unpublished Plus variable platform fee.

Running it with Node.js 24 prints:

Source: Shopify pricing

The result for Pocket Coffee: below about EUR 15,000 of monthly revenue paid with Shopify Payments, Basic is the cheapest plan on fees alone, and Grow takes over above that and stays ahead until about EUR 110,000. If Pocket Coffee paid through a third-party gateway instead, the same crossovers move down to EUR 4,500 and EUR 55,000 because the third-party percentages differ more between plans than the card rates do. The second figure plots the gap in monthly cost relative to Grow.

Plus is not a fee-saving move for a shop of this size: on fees alone it needs roughly EUR 600,000 of monthly revenue to beat Advanced. Merchants move to Plus for the capabilities in the next sections, not for the rates.

Checkout UI extensions add components to the checkout, written with Preact and Polaris web components and compiled to a bundle of at most 64 KB. Which targets a store can use depends on the plan:

The branding API is the checkoutBrandingUpsert mutation, which styles a checkout profile, or the newer Checkout and Accounts Configuration API (checkoutAndAccountsConfigurationUpdate), which also covers customer accounts. The Help Center adds that a Plus store can create separate checkout flows for B2B and direct-to-consumer customers in the same store. The mutation below gives the Pocket Coffee checkout a coffee-brown brand colour and an accent. Its two operations were validated against the downloaded 2026-10 Admin schema, but they were not sent to a store.

Source: Shopify developer documentation, About checkout styling and Admin GraphQL API, checkoutBrandingUpsert

History explains why this gate exists. checkout.liquid is unsupported for the information, shipping and payment steps (it was a Plus-only feature on those steps; Shopify’s own pages state only that it is unsupported, without a day). For the Thank you and Order status pages, checkout.liquid and additional scripts were sunset on 2025-08-28, and script tags on those pages were sunset on 2025-08-28 for Plus stores and 2026-08-26 for stores on other plans. Stores on the Pause and build plan are upgraded automatically, and the additional scripts section has been view-only since 2025-08-28. Shopify Scripts themselves stopped running on 2026-06-30, which is why checkout logic now lives in Functions and checkout UI extensions. The checkout extensibility page of this subsection covers the targets and the migration in detail.

Source: Checkout UI extensions API and Help Center, Upgrading Thank you and Order status pages

Functions are small WebAssembly modules that Shopify runs in the middle of key flows: discounts, cart transforms, delivery and payment customisation, validation, fulfilment constraints and order routing. The plan gate depends on how the app is distributed:

A merchant that wants a Function on a non-Plus plan therefore has two options: install a public app that provides it, or move to Plus and have a custom app built. The Pocket Coffee Coffee Club rule (10% off for members) is the classic example; the sample below builds the simplest possible version of it as a Discount Function that gives 10% off the order subtotal.

The app descriptor of a custom-distribution app uses placeholders for the client id and the URLs. Nothing in it is specific to Plus: the plan is checked when the app with a Function is installed or used on a store.

The Function itself is an extension of type function. The file below targets the unified Discount API with the cart.lines.discounts.generate.run target; command = "" selects the built-in JavaScript builder and the compiled module is written to dist/function.wasm.

Source: Shopify Functions overview

The input query asks for the cart lines and the discount classes the merchant enabled. Its cost must stay under the Functions limits (3,000 bytes of query text and a calculated cost of at most 30).

The module exports run, which returns an orderDiscountsAdd operation with one candidate. In the build that was executed, src/index.js re-exports the function from src/run_impl.js.

Source: Shopify Functions overview

The extension package.json carries the GraphQL code generation settings and the runtime package. The schema file schema.graphql is the Discount API schema from the public Shopify/extensions-templates repository.

Building and running the Function does not need a store or a login. The commands below were executed with Shopify CLI 5.0.0 on 2026-10-27 in a project made of the files above; --no-input avoids interactive prompts.

The build prints Building GraphQL types, Bundling JS function, Running javy and pocket-coffee-app built!, and produces dist/function.wasm of 1,561 bytes. The run uses the bundled function runner and, for an input with one cart line, prints the orderDiscountsAdd output above together with the benchmark: 184.462 thousand instructions against the 11 million limit, 1,280 KB of linear memory and a 164-byte output. The --input path has to be absolute, because it is resolved relative to the extension directory.

Deploying this app, installing it on a store and activating the discount in the admin need a Shopify account and a Plus store, so they were not executed. What was not verified is therefore the exact behaviour of the installation or of shopify app deploy when the target store is not on Plus.

Functions have fixed and dynamic limits that apply on every plan. The fixed limits are a compiled binary of 256 kB, 10,000 kB of linear memory, a 512 kB stack, four tables with 10,000 elements in total and 1 kB of logs. The dynamic limits for carts of up to 200 lines are 11 million instructions, 128 kB of input and 20 kB of output, scaling proportionally above 200 lines.

Source: Shopify Functions overview, Functions API and Shopify/extensions-templates

Shopify Flow is an optional app, available to merchants on any paid plan, that automates tasks with triggers, conditions and actions. Flow features differ by plan. For developers the difference is narrow and precise: an app can ship Flow app extensions (triggers, actions and templates; the CLI templates are flow_trigger, flow_action, flow_template and flow_trigger_lifecycle_callback), and if that app is a custom app, its Flow extensions are available only to a Shopify Plus store that has the app installed. A public app that ships the same extensions works for any paid-plan store that has Flow.

Recent changes to Flow extensions include relative paths for action endpoint URLs (2026-06-18), automatic updates of action runtime URLs and changes that make action extension edits less likely to break existing workflows (both 2026-07-07), and relative paths for trigger lifecycle callback URLs (2026-10-08).

Source: Shopify developer documentation, Flow and Shopify developer changelog

Shopify B2B is available on Basic, Grow, Advanced and Plus. A merchant creates companies with contacts and locations, assigns catalogs and payment terms, and company contacts check out with company accounts. The plan changes how far it can go:

For developers, the Admin API restricts who may call the B2B resources. Apps with B2B features need a plan that supports them, and only dev stores, Shopify Plus Partners and Shopify affiliates can access the GraphQL Admin API’s B2B resources; Plus Partners must test on a dev store created on the Plus plan. B2B also does not support purchase options such as subscriptions, pre-orders or try before you buy.

The query in the next section reads directConnectionCatalogAssignmentEnabled, the feature flag that tells an app whether direct catalog assignment is enabled on the shop.

Source: Shopify developer documentation, B2B and Help Center, Shopify Plus plan

Inventory locations are the places where stock is held and orders are fulfilled: warehouses, shops, popup stands and suppliers that dropship. Every plan except Plus allows 10 locations, and Plus allows up to 200. Pocket Coffee needs two: a Madrid roastery and a returns shelf. A company with a large retail footprint is the case the limit exists for: POS Pro locations are tied to locations, with 20 included in Plus and up to 200 covered when Shopify Payments is the primary retail provider.

The Admin API reports the number with the locationsCount query, which is limited to a maximum of 10,000 by default and returns a precision (EXACT or AT_LEAST).

Source: Admin GraphQL API, locationsCount

The GraphQL Admin API uses a cost-based leaky bucket per app and store. The published restore rates grow with the plan:

The ratios match the "up to 2x" and "up to 10x on select APIs" wording of the pricing page. The bucket sizes are not documented, so a job can only be bounded from below: it cannot finish faster than its total cost divided by the restore rate. A single query is capped at 1,000 points on every plan, and input arrays are capped at 250 items. The script below computes that lower bound for a Pocket Coffee catalogue sync of 2,000 productUpdate mutations at the default mutation cost of 10 points.

Output with Node.js 24:

Source: Shopify developer documentation, GraphQL Admin API rate limits

Other API-level differences by plan:

Source: Shopify developer documentation, API limits and Access scopes