Forget the revenue threshold
There's a persistent belief that Plus becomes correct at some specific annual revenue. Revenue is a rough proxy at best. Two brands at identical volume can have completely different needs: one sells fifteen SKUs direct to consumer with simple shipping, the other runs wholesale, subscriptions, three regions and a promotion calendar with overlapping mechanics.
The second brand needs Plus long before the first one does — and might need it at half the revenue.
The right question isn't "are we big enough?" It's "what are we currently working around?"
Reasons that hold up
- Checkout requirements. Customized checkout logic, validation rules or checkout-level personalization that the standard plan can't express.
- Complex promotions. Scripted or stacked discount mechanics, gift-with- purchase logic and tiered rules that would otherwise need an app pile.
- B2B and wholesale. Company accounts, price lists, payment terms and separate catalogs running alongside DTC.
- Automation at scale. Order, fulfillment and inventory workflows that currently rely on someone doing them by hand every day.
- Multi-store or international. Several storefronts, markets, currencies or languages that need to be managed coherently.
- Peak-period risk. Launches or promotional spikes where checkout throughput and support response genuinely matter to the business.
- Organizational needs. More staff accounts, tighter permissions, and controlled access as the team grows.
Reasons that don't
| Stated reason | What's usually true |
|---|---|
| We want better performance | Speed is dominated by theme, apps and media — not the plan tier |
| We need a better-looking store | Design and theme quality are independent of Plus |
| We want better support | Real value, but rarely enough on its own to justify the cost |
| Our competitors are on Plus | Their requirements are not automatically yours |
| We want to look enterprise | Customers cannot tell which plan you're on |
A test you can run this week
- Write down the three things you can't currently do that you want to do.
- For each one, confirm it's actually a plan limitation, not a build decision.
- Price the workaround: apps, hours, error rate, risk during peak.
- Ask who internally would own the new capability once it exists.
If step two eliminates all three items — which happens often — the answer is a better implementation, not a bigger plan.
What changes after you upgrade
Plus is capability, not outcome. Upgrading gives you access to checkout customization, automation tooling, B2B functionality, additional environments and higher limits. It does not merchandise the store, fix the data or make the promotion strategy coherent.
Brands that get value from Plus tend to have one thing in common: they knew exactly what they were going to build with it before they signed.
