Checkout extensibility, Shopify Functions, B2B on Plus, expansion stores and Markets. The things the tier exists for, built on the supported extension points.
In one paragraph
What can you build on Shopify Plus that you cannot build on Shopify?
Checkout itself. Plus is the tier where checkout stops being fixed: checkout UI extensions add content and fields to the real checkout, and Shopify Functions replace discount, delivery, payment and cart logic server side. It also carries B2B company accounts with catalogues and payment terms, up to nine expansion stores under one contract, Shopify Flow for operational automation, and higher API limits. Everything else, custom themes, private apps, Storefront API work and systems integration, runs perfectly well on standard Shopify, which is why the upgrade decision should be made against that list rather than against revenue.
What this is
Plus is sold on volume and bought for capability, and the two do not always coincide. The useful way to approach it is to write down what the business cannot currently do, then check which of those things the tier actually unlocks. Often it is one: the checkout.
Once the business is on Plus, the engineering changes shape. Scripts are gone and Functions have replaced them, which is a better model and a rewrite. Checkout customisation moves from script injection, which broke on every update, to extension points that Shopify supports and tests against. Work built the old way has to move, and that migration is a large part of current Plus work.
The second half is operational. Flow automates the processes a growing brand is doing by hand, Markets handles currency, duty and localisation per region, and expansion stores let a brand run a separate storefront per market without a separate contract. These pay back quickly and are frequently unconfigured.
What this page is not
This page is for work that needs the tier. Custom themes, private apps and integrations do not, and if that is what you need you should not be upgrading for it.
What usually brings this in
Our checkout customisation was written in Scripts.
Scripts are retired, the logic has to move to Functions, and nobody has documented what the Scripts actually do.
We upgraded to Plus and are not using anything new.
A materially larger monthly bill funding a tier whose distinguishing features are switched off.
B2B customers are handled by a separate wholesale site.
Two storefronts, two catalogues and two sets of inventory truth, reconciled by a person.
Every new market means another store nobody has time to run.
Pricing, duty and translation drift between storefronts, and the brand looks different in each one.
What gets built
- Checkout UI extensions
- Content, fields, upsells and validation inside the real checkout, at the supported extension points, so a Shopify release does not take the checkout down with it.
- Shopify Functions
- Discount, delivery, payment and cart transform logic running server side, including migration of existing Scripts logic with the behaviour documented on the way through.
- B2B on Plus
- Company accounts, locations, catalogues with account-specific pricing and payment terms on the same store as D2C, which removes the second storefront and the reconciliation behind it.
- Expansion stores and Markets
- Per-market storefronts with shared operations, currency and duty handled by Markets, and a content model that does not fork per region.
- Flow and Launchpad automation
- Operational workflows, tagging, fraud and fulfilment rules, and scheduled launches, built so the operations team owns them afterwards rather than me.
- Headless over the Storefront API
- Hydrogen or Next.js against the Storefront API where the storefront genuinely needs it, which is less often than it is proposed and is covered honestly on the headless page.
Technologies
- Platform
- Shopify Plus
- Shopify Functions
- Checkout extensions
- Shopify B2B
- Operations
- Shopify Flow
- Launchpad
- Shopify Markets
- Expansion stores
- APIs
- Storefront API
- Admin API
- GraphQL
- Webhooks
- Frontend
- Liquid
- TypeScript
- Hydrogen
- Next.js
How delivery runs
Scope, in writing
What the work is, and what it explicitly is not. The second half is the one that protects both of us, and it is written before anything is quoted.
Architecture before code
The data model, the integration points and the failure modes, agreed on paper. Most of the expensive mistakes in commerce are made here and discovered six weeks later.
Build in reviewable slices
Work lands in increments you can see running, not in one drop at the end. You find out early if something is going the wrong way, which is when it is still cheap.
Test against the real thing
Production-shaped data, production-shaped traffic. A checkout that works on twelve test products tells you nothing about one carrying a hundred thousand.
Deploy, document, hand over
Release process written down, documentation aimed at your team rather than at me, and a defined window afterwards where fixes are mine.
Relevant builds
- Shopify · D2C
Online plant store
India’s most trusted online plant store on Shopify, with OTP login, GoKwik one-page checkout and custom product pages.
- Shopify
- GoKwik checkout
- Custom PDP
- Headless commerce · Fashion
Headless fashion storefront
High-performance headless commerce architecture for India’s fastest-growing men’s fashion brand.
- Headless
- Storefront API
- Performance
- E-commerce · Health & fitness
Sports nutrition store
Online fitness and supplement store delivering authentic sports nutrition at speed.
- Commerce build
- Catalogue
- Checkout
Questions
- Should we upgrade to Shopify Plus?
- Write down what you cannot do today, then check that list against what the tier unlocks: checkout extensibility, Functions, B2B company accounts, expansion stores, Flow and higher API limits. If nothing on your list is on that list, the upgrade buys you support and a bill. If the checkout is on your list, it is the only route.
- We still run Shopify Scripts. How bad is the migration?
- It is a rewrite rather than a port, because Functions have a different execution model. The hard part is almost never the code: it is establishing what the Scripts currently do, since the edge cases were usually added over years by people who have left. That archaeology is the first phase and it is worth doing carefully.
- Can Plus handle B2B and D2C on one store?
- Yes, and that is the strongest argument for the tier for a brand running both. Company accounts, account-specific catalogues and payment terms sit alongside the consumer storefront, which removes the separate wholesale site and the inventory reconciliation it required.
- Will checkout extensions survive Shopify updates?
- That is precisely why they exist. Extensions and Functions are supported extension points that Shopify tests against; the previous generation of checkout customisation was script injection into a page Shopify kept changing, which is why it kept breaking.
Describe what is in front of you and you get a written scope and a figure, usually within a few days of a short call. No charge for either.