Shopify to Shopify Plus: What the Upgrade Involves
On this page
Here is the good news, and the reason this article is different from every other one in this cluster: upgrading from Shopify to Shopify Plus is not a migration.
Your store stays where it is. Same URLs, same products, same customers, same orders, same theme, same apps. No redirect map, no data transfer, no SEO risk, no launch day. Commercially it is a plan change, and technically your store is the same store with more capability unlocked.
So why does this article exist, and why do Plus upgrades still disappoint people?
Because nothing about upgrading makes anything better on its own. Plus gives you access to capability. Realising value from it requires building things, and stores that upgrade expecting improvement rather than expecting to build are the ones who find themselves six months in, paying considerably more, with a store that works exactly as it did before.
What you actually get
Worth being precise, because the marketing is vaguer than the reality.
Checkout customisation through Checkout Extensibility. The largest single reason most stores upgrade. Below Plus, checkout is essentially fixed. On Plus you can add content, fields, custom logic, and branding within defined boundaries. For stores where checkout conversion or a specific checkout requirement matters, this is the feature that justifies the cost.
Shopify Functions. Custom server-side logic for discounts, shipping rates, payment method visibility, cart validation, and delivery customisation. This is how you reproduce business rules that native features cannot express — tiered pricing, complex promotion stacking, conditional shipping, restricting payment methods by cart contents. Genuinely powerful, and it requires development work.
Native B2B. Company accounts, customer-specific catalogues and price lists, payment terms, quantity rules, and a separate B2B buying experience. For stores with a real wholesale operation this frequently justifies the upgrade by itself, and it removes app dependencies that were never quite right.
Higher API limits. Matters if you have substantial integrations or high order volume, and occasionally this alone is the reason — an integration that keeps hitting rate limits is a genuine operational problem.
Expansion stores. Additional stores included in your plan, useful for distinct regional or brand operations that Markets does not adequately serve.
More staff accounts. Mundane and occasionally the actual constraint for a growing team.
Organisation-level admin. Managing multiple stores from one place, with consolidated user management.
Dedicated support and an account manager. Value varies. Some stores find it useful, others rarely engage. Do not let it carry the decision.
Lower transaction rates. At sufficient volume the reduced rates offset a meaningful portion of the higher platform fee, which is why the decision has a volume threshold rather than being purely about features.
What you do not get
Anything automatically better. No speed improvement, no conversion improvement, no SEO benefit. Your store on day one of Plus performs precisely as it did on the last day before.
A rebuilt store. Your theme, apps, and configuration are unchanged. If your store has accumulated problems, they come with you.
Unlimited checkout control. Extensibility has boundaries. If you have a specific unusual checkout requirement, verify it is achievable before upgrading on the assumption that it is.
Escape from apps. Some app dependencies can be replaced with Functions or native B2B. Many cannot.
A performance fix. If your store is slow because of thirty apps and a heavy theme, Plus changes nothing. That is optimisation work, not a plan.
When to upgrade
The genuine triggers, each of which is a specific capability need rather than a growth milestone.
You need checkout customisation for a real business reason — a required field, a compliance step, custom messaging, a particular upsell placement, or checkout conversion work you cannot otherwise do.
You have business logic native features cannot express. Complex discount stacking, tiered or segment pricing, conditional shipping rules, payment method restrictions by cart contents. Functions are the answer and Functions need Plus.
You have a real B2B operation and are working around it with apps and manual processes. Native B2B is materially better than most app-based approaches, and this is one of the clearest cases for upgrading.
You are hitting API rate limits and it is affecting operations.
Your volume makes the maths work. At sufficient revenue, lower transaction rates recover much of the fee difference. Run the actual numbers at your actual volume rather than relying on a rule of thumb.
You need several storefronts and the included expansion stores change the economics.
Do not upgrade because: revenue crossed a threshold someone mentioned; you want to seem more established; you assume performance will improve; an account manager sounds appealing; or a competitor is on Plus. None of those return anything.
The test: write down the specific thing you will build in the first ninety days after upgrading, and what it will change. If you cannot complete that sentence, wait. The fee starts immediately and the value starts when you build something.
What the work actually involves
The upgrade itself is administrative. The work is what follows, and it needs planning before you commit.
Checkout work, if that is your reason. Design what you want the checkout to do, then build it with Checkout Extensibility — UI extensions for interface changes, Functions for logic. Scope this properly; “we will improve checkout” is not a plan, and checkout is the one place where a mistake costs money immediately.
Functions development for business logic. Each rule needs specifying precisely, building, and testing against edge cases. Discount logic in particular deserves careful testing, because a Function that misbehaves on an unusual cart combination can either lose you margin or block legitimate orders.
B2B setup, if applicable. Company accounts, catalogues, price lists, payment terms, and the buying experience. This is a configuration and process project as much as a technical one, and your sales team needs involving. Migrating existing wholesale customers off whatever app or spreadsheet arrangement you currently use is its own piece of work.
App rationalisation. Some apps exist only to do what Functions or native B2B now handle. Identify them and remove them — this is where some of the fee difference comes back, and it is routinely forgotten. Stores often pay for Plus and keep paying for the apps it replaced.
Integration review. Higher API limits may let you improve integrations that were previously constrained. Worth revisiting the ones you compromised on, and occasionally rebuilding an integration properly now becomes viable when it was not before.
Team enablement. Your team needs to know what is newly possible. Plus capability sitting unused because nobody knew it existed is common.
None of this carries migration risk. All of it carries the risk of not happening, which is the characteristic Plus failure.
A worked example: the upgrade that did nothing for eight months
A supplements brand upgraded to Plus on the strength of a conversation about growth. Their reasoning was that they had passed a revenue level where Plus seemed appropriate, and their agency agreed.
Eight months later they were paying considerably more per month and their store was identical. No checkout work, no Functions, no B2B. The account manager relationship amounted to two calls. Their conversion, speed, and operations were exactly as before.
When they came to us they were considering downgrading, and it was a reasonable thought.
We looked at what Plus could actually do for them specifically. Three things stood out.
Their wholesale operation — about 18% of revenue — ran on a combination of a discount-code app, a spreadsheet, and manual invoicing. Native B2B replaced all of it, removed two app subscriptions, and eliminated roughly six hours a week of administration.
Their subscription discount structure had been approximated with a stack of automatic discounts that behaved inconsistently when combined with promotions, producing occasional margin leakage and occasional customer complaints. A Function expressed the intended logic exactly.
And their checkout had no way to capture a required delivery instruction for certain regulated products, which had been handled by a post-order email and a support process. A checkout extension captured it properly.
Those three pieces of work took about five weeks. Afterwards, Plus was clearly worth its cost — the administrative saving alone covered a good share of the difference.
The point is that all three were available from the day they upgraded. They had bought capability and never used it, because nobody had planned what to build. The upgrade was not the mistake; treating it as an achievement rather than a starting point was.
The decision, reduced
Upgrade if you have named, specific capability needs — checkout customisation, Functions logic, native B2B, API headroom, expansion stores — and a plan to build them within a quarter. Or if your volume makes the transaction-rate maths favourable on its own.
Wait if your reasons are about status, assumed improvement, or a revenue threshold. Spend the money on your store instead: speed, product pages, content, merchandising, retention. Those return more than a plan change, reliably.
And if you are already on Plus and not using it, the answer is not necessarily to downgrade. It is to spend a day identifying what Plus could do for your specific operation. Most stores in that position find two or three things worth building, and afterwards the fee makes sense.
Alternatives worth considering first
Before upgrading, it is worth checking whether the thing you want can be had more cheaply. Sometimes it can.
If you want better conversion, the highest-return work is almost never checkout. It is product pages, site speed, photography, product copy, reviews, and reducing friction before the cart. Stores frequently upgrade for checkout customisation while carrying a six-second product page, which is optimising the last five percent of the journey while ignoring the first ninety.
If you want complex discounts, check what native discounting and automatic discounts now cover before assuming you need Functions. Shopify’s native capability has expanded, and a structure that needed custom logic two years ago may be expressible today. Test it on a staging store.
If you want B2B, apps can serve a straightforward wholesale operation adequately — customer-specific pricing, quantity breaks, a gated catalogue. Native B2B is better, particularly for company accounts, payment terms, and multi-buyer organisations, but if your wholesale is a dozen accounts with simple pricing, an app is a fraction of the cost. The case for Plus strengthens with account volume and workflow complexity.
If you are hitting API limits, check whether your integration is well built first. A significant share of rate limit problems come from integrations polling inefficiently rather than from genuine volume — fetching everything on a schedule instead of using webhooks, or requesting more data than needed. Fixing the integration is cheaper than raising the ceiling.
If you want multiple storefronts, Markets handles a great deal of international requirement without additional stores. Expansion stores are for truly distinct operations — different catalogues, different brands, different operational models — rather than for selling in another currency.
If you want a dedicated account manager, be honest about whether you will use it. Some teams engage regularly and find real value; others have two calls a year. It is a poor primary reason to change plans.
None of this is an argument against Plus. It is an argument for checking that you need it, because the fee difference over a year funds a substantial amount of development work on the store you already have.
Planning the first ninety days
If you do upgrade, the difference between a good decision and a wasted one is having this planned before you commit.
Week one: audit what Plus changes for you specifically. Go through your app list and identify anything that exists only to do what Functions or native B2B now handle. Go through your manual processes and identify which existed because of platform limitations. Go through your list of “we cannot do that” items and recheck each one.
Weeks two and three: specify the work. Not “improve checkout” — the actual field, the actual logic, the actual rule, with edge cases. Functions in particular need precise specification, because discount logic that behaves oddly on an unusual cart is worse than no custom logic at all.
Weeks three to eight: build, starting with whatever removes cost or manual work. B2B setup replacing an app and a spreadsheet pays back immediately and visibly, which also helps internally when someone asks what the fee is buying. Checkout work is usually higher value but takes longer to demonstrate.
Throughout: remove the apps you have replaced. Set a reminder, because this is the step that reliably gets forgotten. Paying for Plus and for the apps it superseded is the most common quiet waste in this whole exercise.
Week eight onward: tell your team what is now possible. Merchandising, marketing, customer service, and sales all have workarounds they have stopped noticing. Ask each team what they currently do by hand, then check which of those Plus now solves.
Week twelve: review. What did you build, what did it change, and what is still on the list. If the answer is nothing, that is worth knowing early rather than at the eight-month mark.
The bottom line
This is the one item in this cluster that carries no migration risk at all. No redirects, no data transfer, no SEO exposure, no launch day. Your store simply continues.
Which means the entire question is whether you will use what you are paying for. Plus unlocks checkout customisation, Functions, native B2B, and API headroom — all valuable, and none of it self-executing.
Decide by writing down what you will build in the first ninety days. If that list is concrete, upgrade and build it. If it is empty, the money is better spent on the store you already have.
Frequently asked questions
Is upgrading to Shopify Plus a migration?
No, and this is the most useful thing to understand about it. Your store stays exactly where it is — same URLs, products, customers, orders, theme, and apps. There is no data transfer, no redirect map, no SEO risk, and no launch day. Commercially it is a plan change that unlocks additional capability on the store you already have. The work comes afterwards, in building the things Plus makes possible, and that work is optional in a way that catches people out: nothing improves automatically, so a store that upgrades without a build plan gets a larger bill and an unchanged store.
At what revenue should I upgrade to Shopify Plus?
Revenue is the wrong trigger, though it affects the maths. The right trigger is a specific capability you need: checkout customisation for a real business reason, Shopify Functions to express business logic native features cannot handle, native B2B for a genuine wholesale operation, or API headroom because rate limits are affecting operations. Revenue matters because at sufficient volume the lower transaction rates offset a meaningful share of the higher platform fee — so run that calculation at your actual volume. But crossing a revenue threshold with no capability need returns nothing.
Will Shopify Plus make my store faster or convert better?
Not by itself, and this is the most common misconception. On day one of Plus your store performs exactly as it did on the last day before: same speed, same conversion, same SEO. What Plus gives you is the ability to work on checkout, which is often where meaningful conversion gains sit, and to express business logic you previously could not. If your store is slow because of an accumulated app stack and a heavy theme, Plus changes nothing about that — that is optimisation work, and it is considerably cheaper than the fee difference.
What is the main reason stores upgrade to Shopify Plus?
Checkout customisation, followed closely by native B2B and Shopify Functions. Below Plus the checkout is essentially fixed, so any store needing a custom field, a compliance step, particular messaging, or checkout conversion work has to upgrade to do it. Native B2B is frequently decisive on its own for stores running wholesale through apps, spreadsheets, and manual invoicing — it usually replaces several app subscriptions and a good deal of administration. Functions cover business rules like tiered pricing, complex discount stacking, and conditional shipping that native features cannot express.
Can I downgrade from Shopify Plus if it is not worth it?
Generally yes, subject to your contract terms, but before doing that spend a day identifying what Plus could do for your specific operation — most stores in that position find two or three worthwhile projects they simply never scoped. The usual candidates are replacing an app-based wholesale arrangement with native B2B, expressing an approximated discount structure properly with a Function, and fixing a checkout limitation that has been handled with a manual process. If after that exercise there is nothing, downgrading is sensible and the money is better spent on your store.
Do I need a new theme or a rebuild when I move to Plus?
No. Your theme carries over untouched, along with your apps, settings, and content — nothing about your storefront changes when the plan changes. Whether you want theme work is a separate question with a separate answer: if your store has accumulated performance problems or your product pages are weak, those issues follow you onto Plus unchanged and are worth fixing on their own merits. Keep the two decisions apart. Upgrading because you want a better store is the wrong reason; upgrading for a capability you need and separately investing in the store is the right shape.
Will upgrading to Plus affect my SEO or rankings?
Not at all. Your URLs, content, theme, structure, and site speed are all unchanged, so there is nothing for search engines to reprocess — this is the one item in this whole cluster with zero SEO exposure. That also means no upside: Plus confers no ranking benefit, no crawl advantage, and no speed improvement. If organic traffic is your concern, the money is better directed at content, technical fixes, and page speed than at a plan change, which is precisely the trade to weigh when the fee difference over a year would fund a meaningful amount of that work.