Home>Shopify Plus vs Alternatives>Shopify Plus vs Advanced>Do Staff Seats Really Drive Plus Upgrades?

Is the Advanced-plan staff cap of 15 accounts the real reason mid-market brands upgrade to Plus, or is it usually the checkout features?

Checkout features drive the upgrade, not the seat cap. Advanced includes 15 additional staff accounts and Plus includes unlimited (shopify.com/pricing, September 2026), but collaborator accounts for agencies and partners "don't count towards your store's user limit" (help.shopify.com, September 2026). The seat ceiling is soft. The checkout ceiling has no workaround.

Why the seat cap looks binding and is not

The 15 is real. What makes it soft is the account type sitting beside it. Shopify's help centre defines collaborators as "Shopify Partners who you've allowed to access your store or organization" and states that "Collaborators don't count towards your store's user limit" (September 2026). The pricing page says the same thing in its own tooltip on the "Invite third-party collaborators" row: "Provide limited access to your store. Doesn't count toward staff account limits."

For a mid-market brand, that covers most of the population that was about to push you over the line. Your agency, your freelance developer, your Klaviyo contractor, your accountant's Shopify Partner account. None of them consume one of the 15.

What does consume the 15 is your own payroll: merchandisers, customer service, warehouse staff who need admin access, finance. That population grows, and at $10M to $30M it can genuinely cross 15. When it does, the constraint is real. It is also an access-governance problem before it is a plan problem, and most stores that hit 15 discover on audit that three of the seats belong to people who left.

Why checkout is the constraint that actually forces the decision

A seat cap has a workaround. The checkout gate does not.

  • Checkout UI extensions on the information, shipping and payment steps are "available only to stores on a Shopify Plus plan" (shopify.dev, September 2026).
  • "Only stores on a Shopify Plus plan can use custom apps that contain Shopify Function APIs" (shopify.dev, September 2026).
  • The pricing comparison table rates checkout customization as "Limited" on Basic, Grow and Advanced, and "Full" on Plus (shopify.com/pricing, September 2026).

You cannot buy your way around any of those three on Advanced. You can install a public App Store app that contains functions, because "stores on any plan can use public apps that are distributed through the Shopify App Store and contain functions" (shopify.dev, September 2026). What you cannot do is write your own.

The ranking, as we see it in scoping calls

TriggerHow often it is the stated reasonHow often it is the actual reason
A checkout requirement nobody can ship as an appSometimesMost of the time
Custom function logic (discounts, shipping rules, validation)SometimesOften, and usually discovered mid-project
Third-party payment processor economicsRarelyOften, once the 0.6% to 0.2% line is priced
Staff seatsOftenRarely, and usually a stale-seat problem
Expansion stores for a new marketSometimesSometimes, and it is a legitimate reason

This table is Deploi's read of our own scoping conversations, not a survey. We have not run one and we will not present it as one.

What to do before you count seats

  1. Audit the 15. Pull the list. Deactivate departed staff. This is free and it frequently ends the conversation.
  2. Reclassify your partners. Anyone with a Shopify Partner account should be a collaborator, not staff.
  3. Write the checkout requirement down. One paragraph, specific: what has to appear, on which step, driven by which data. Then ask whether any App Store app ships it.
  4. Only then price the plans.

The Deploi point of view

Our own position, from building on Shopify. Separate from the facts above.

  • Our take: The seat cap is a symptom, not a cause. A store that has genuinely outgrown 15 payrolled admin users has usually also outgrown Advanced's checkout, and the checkout is what should be on the business case because it is the constraint with no workaround.
  • What we’ve seen: Seat-cap urgency almost always softens after an access audit. Checkout urgency never softens, because the requirement came from a customer or a finance team and it does not go away when you look at it harder.
  • Where we disagree: Plus sales conversations lead with unlimited staff accounts because it is the easiest row in the comparison table to understand. It is also the row with a free workaround sitting one line below it. Leading with it trains buyers to evaluate the plan on the wrong axis.
  • What this page adds: that collaborator accounts are excluded from the 15, which is the specific fact that dissolves the seat argument, and the sequence to run before you let a seat count into a business case.

Reviewed by Martin Dejnicki, Director of SEO & AI Search. Facts verified 2026-09-14.