Enterprise Shopify Setup: Why $7M Brands Burn Plus Fees

Enterprise Shopify Setup: Why $7M Brands Burn Plus Fees

Most brands sign the Shopify Plus contract two years too late, then keep the same theme, the same checkout, and the same app stack they ran on the Advanced plan. The badge changes. The architecture does not. That is the quiet failure mode behind every Plus migration that produces no measurable lift.

If you are running a $7M physical product business and your Plus contract has been live for ninety days, ask yourself one question. Which of the six Plus-only capabilities have you deployed end to end? Most operators cannot name two. They are paying enterprise pricing for an Advanced plan with a different logo.

The $27,600 Vanity Tax: Why Plus Without Capability Use Is Money Burned

Shopify Plus runs $2,300 per month at the minimum tier, with variable revenue-based pricing kicking in above $800K monthly GMV. That price covers Functions, Flow, Scripts (sunsetting June 30, 2026), Launchpad, the native B2B suite, expansion stores, and checkout extensibility, per the Plus features guide. The contract carries no requirement to actually use any of them.

That is the source of the failure. Plus is sold as a tier upgrade with marketing language that promises performance, scale, and security. The storefront does not get faster. The platform does not deliver more sales by virtue of you paying more. What changes is the capability set you now have access to, and whether you ship those capabilities into production is entirely a function of internal discipline.

Look at the contract math. $2,300 per month is $27,600 per year at the floor. A brand that signs Plus and does not use Functions, Flow, B2B, or checkout extensibility within ninety days is paying for access to nothing it touches. The badge in the admin panel does not produce revenue. The white-glove account manager does not refactor your theme. The Plus-only apps still need to be installed, configured, and operated by your team.

I have walked into post-migration audits at three different brands in the $5M-$15M band where the Plus contract was eighteen months old and not a single Plus-only feature was running. No B2B portal. No Functions. Flow was installed but the only active workflow was a duplicate of the Email-on-cart-abandonment trigger they had on the previous tier through a third-party app. The Plus contract had cost them $41,400 in those eighteen months. The capability deployment cost them zero, because there had been no capability deployment.

The villain here is the $2,300-a-month Plus upgrade bought without B2B, Flow, Functions, or Scripts planning. It is the most expensive non-decision in the DTC stack. Operators sign because the Account Executive pitched the badge or because their agency told them they had outgrown Advanced. Both pitches collapse on inspection, because growing past the Advanced plan limits is not the same as needing Plus capabilities.

The Scripts deadline tightens this further. The Functions vs Scripts breakdown confirms that Scripts stop running on June 30, 2026, replaced by Functions plus checkout extensibility. Brands signing Plus in 2026 are signing for capabilities that are mid-rebuild. If your migration plan does not include a Functions rewrite of your existing discount, payment, and shipping logic, you are buying a tier whose central customisation engine is being deprecated under your feet.

The Plus Capability Justification Blueprint

I call this The Plus Capability Justification Blueprint. It is a six-row capability ledger that forces the buyer or current Plus operator to map every Plus-only feature against a current operational pain, a named ninety-day deployment owner, and an estimated payback in dollars or hours. If a capability cannot be tied to all three, it is not justified. Three or more empty rows mean the upgrade should be deferred or the contract should be renegotiated.

The six rows are non-negotiable, because they cover the entire span of why a brand would actually need Plus rather than Advanced. The Plus Capability Justification Blueprint is built to be defensible to a CFO, a board member, or a sceptical co-founder, not just an enthusiastic head of ecommerce.

Row 1 is Functions. These are the WebAssembly extensions that let you customise discount, payment, shipping, and cart logic at the platform level. The pain has to be a real merchandising or pricing rule that your current app stack cannot deliver, like tiered freight rules by SKU weight or a non-standard buy-X-get-Y discount logic. The owner has to be a Shopify-certified developer or agency. The payback has to be measured in margin recovery or cart conversion lift.

Row 2 is Flow. The pain has to be a workflow your team executes manually that costs measurable hours per week. Tagging high-LTV customers, escalating fraud-flagged orders, alerting CX on negative reviews, auto-archiving sold-through products. The owner is whichever ops or CX lead currently runs the manual version. The payback is hours saved multiplied by loaded labour cost.

Row 3 is B2B. The native B2B suite includes wholesale price lists, customer-specific catalogues, payment terms, draft orders, and quote-to-order flows, per the Plus feature breakdown. The pain has to be active wholesale revenue you are currently routing through a separate platform, manual Excel orders, or a Shopify app that simulates wholesale through tags. The owner is a wholesale or sales lead. The payback is wholesale GMV moved onto the native suite plus reduction in dual-platform tooling cost.

Row 4 is Scripts and Checkout Extensibility. With Scripts sunsetting in June 2026, this row really measures readiness for Functions plus checkout extensibility. The pain has to be a checkout customisation that your current theme cannot deliver, like custom shipping methods at checkout, stacked discount logic, or country-specific compliance text. The payback ties to the Checkout customization lift band of 10-15% on conversion when you actually deploy a tested checkout customisation.

Row 5 is Launchpad. The pain has to be flash sales, promotional events, or product launches that currently require manual price changes, theme swaps, or coordination across timezones. The Plus 2025 guide reports that Launchpad has driven over $3 billion in scheduled-campaign sales since release. If your brand runs three or more such events per quarter, Launchpad has a defensible payback. If you run two flash events per year, it does not.

Row 6 is expansion stores. Plus includes up to nine additional stores in the contract. The pain has to be active multi-region or multi-brand presence that justifies separate storefronts, not a vague desire to launch in three more countries someday. The owner is a country lead or brand GM. The payback is region-specific GMV that the duplicate store will capture beyond what a multi-currency single store would.

If you cannot justify two of these six rows with a real pain, a named owner, and a payback estimate inside ninety days, you are not ready for Plus. The Plus Capability Justification Blueprint protects you from buying capability you will not deploy.

Phase 1: The Capability Audit (Days 1-30)

The first thirty days are an audit, not a migration. Whether you are about to sign Plus or you are ninety days into a Plus contract that is producing no lift, the steps are the same. The work in this phase is honest accounting, not engineering.

Week 1 is the data pull. Get every active app on your store, the monthly cost of each, the function each performs, and the team member who owns it. The average Shopify store runs more than twenty apps. Map each one against the Plus-only capabilities. If you have a workflow app like Mesa, that maps against Flow. If you have a discount or bundle app like Bold, that maps against Functions. If you have a wholesale app like Wholesale Channel or B2B Login, that maps against the native B2B suite. Most brands find that four to seven of their existing paid apps map directly onto Plus-only capabilities they are already paying $27,600 a year to access.

Week 2 is the operational pain inventory. The CFO, head of ecommerce, head of CX, and head of operations each list their three biggest weekly time sinks. The CFO might list manual reconciliation between the Shopify wholesale tag system and Xero. The head of ecommerce might list flash sale theme swaps. The head of CX might list manual order routing for a specific SKU class. Each pain gets logged against the capability ledger row that would address it.

Week 3 is the payback calculation. For each capability row that has both a current operational pain and a candidate owner, estimate the dollar value or hour value of fixing it. The Flow workflow that saves the head of CX six hours per week is worth roughly $7,800 per year at a $25-an-hour loaded cost. The B2B native suite that lets you cancel three wholesale apps is worth their combined annual cost. The Functions rule that recovers the cart abandonment driven by your current discount stacking error is worth a margin lift you can quantify against ninety-day baseline data.

Week 4 is the prioritisation call. The leadership team meets, reviews the six-row ledger, and selects the two highest-payback capabilities to deploy in Phase 2. Two is the cap. Brands that try to deploy four capabilities in ninety days deploy zero. The discipline of choosing two creates the focus that makes deployment actually happen.

If at the end of Phase 1 you cannot identify two capabilities with a real pain, owner, and payback, the audit has done its job. You are not ready for Plus, or your existing Plus contract is genuinely under-utilised and the right move is to renegotiate downward or defer the migration. That is a save of $27,600 a year, which is a real win, not a defeat.

Phase 2: Two-Capability Pilot (Days 31-90)

Phase 2 deploys exactly the two capabilities selected in Phase 1, end to end, before any other migration work begins. This is the rule that breaks the most Plus rollouts. Operators sign Plus, then immediately commission a theme refresh, an apps cleanup, a headless project, and a CX redesign in parallel. None of the Plus-only capabilities ship in the first quarter. The brand has a new Plus admin panel and the same operational shape it had before.

The ninety-day window is consistent with the Plus migration timing breakdown, which puts standard migrations at four to twelve weeks for the platform move itself. The Plus Capability Justification Blueprint adds the Phase 2 discipline that the platform move alone is not the migration. Capability deployment is the migration. Without it, you have a re-platform, not a Plus rollout.

Days 31-45 are scoping and resourcing. Each of the two selected capabilities gets a one-page scope document with the current state, the target state, the owner, the supporting team, and the success metric. If you selected Flow as one of the two, the scope might read: current state is the head of CX manually tagging high-LTV customers daily; target state is an automated Flow workflow tagging customers above a $250 LTV threshold; owner is the head of CX; supporting team is one developer for two days; success metric is hours saved per week, measured at day 60 and day 90.

Days 46-75 are the build. Standard build cycles for a single Flow workflow, a single Function, a B2B portal pilot with one wholesale customer cohort, or a Launchpad-scheduled campaign sit comfortably in three to four weeks. Anything longer than four weeks for a single Plus capability suggests scope creep, missing requirements, or an attempt to build the platform-perfect version when the goal is the operational-payback version.

Days 76-90 are validation. Each of the two capabilities runs in production, with measurement against the day-30 baseline. The Flow workflow has saved the documented hours. The B2B portal has processed real wholesale orders against the named customer list. The Function has applied the rule cleanly across the volume range you specified. The Launchpad campaign has run end to end without manual intervention.

The Allbirds case study on Shopify Plus illustrates the pattern at scale. Allbirds rebuilt store operations on Plus to support multi-region launches and complex inventory, using expansion stores and Functions where their previous platform forced custom backend work. The point for a $7M operator is not to build the Allbirds version. It is to deploy two capabilities to a real operational depth before adding a third. The independent Loyalty case Allbirds write-up reinforces that the lift came from operational deployment of new capability, not from the tier change itself.

For brands that selected B2B as one of the two capabilities, the named comparable is the Filtrous deployment, which launched the native B2B suite in 63 days and reported twelve hours per week saved across the wholesale ops function. That is a defensible payback against any line-item review of the Plus contract. The Plus enterprise tools catalogue explains why: the native B2B suite collapses what was previously three or four wholesale apps into one platform layer, and the collapse alone saves recurring tooling spend on top of the labour saving.

The New Question Every Plus Operator Should Ask

The wrong question is "should we move to Shopify Plus." That question turns the migration into a tier decision and lets operators answer it on revenue band, agency advice, or the quality of the Account Executive pitch. The right question is "which two Plus-only capabilities will we have shipped to production within ninety days, with a named owner, a measured pain, and a payback we are willing to defend at the next board meeting."

That question is harder to answer. It exposes the gap between what brands buy and what brands deploy. It is also the question that turns a $27,600-per-year contract into a defensible operational investment instead of a tier-inflation tax.

Going forward, the metric to track on every Plus contract is the capability-utilisation rate. Out of the six Plus-only capabilities, how many are running in production with a measurable operational outcome at the end of Quarter 1, Quarter 2, and Quarter 3 post-migration. A brand that finishes Quarter 1 with two capabilities live, ships a third by end of Quarter 2, and a fourth by end of Quarter 3 has a healthy 67% capability-utilisation rate by month 9, with two capabilities still in reserve to deploy as the business grows. A brand that finishes Quarter 3 still at zero or one is paying enterprise pricing for an Advanced experience.

If you are about to sign Plus, run the Plus Capability Justification Blueprint before the contract. If you are already on Plus and producing no measurable lift from the move, run it now. The blueprint either gives you a green-light migration plan with two named feature owners, or it gives you the honest evidence that you are not ready, which saves you twenty-thousand dollars a year of tier inflation. Either outcome is better than the silent default, which is paying for capability you never use and calling it an upgrade.