From an operations manager's perspective, does the tier decision hinge more on staff-account limits or on B2B catalog capacity?
B2B catalog capacity decides it, by a wide margin. Advanced allows 15 staff users and collaborator accounts do not count against that limit, so agencies and freelancers consume none of it (help.shopify.com, September 2026). B2B catalogs cap at 3 with no workaround inside the platform. One limit has an exit; the other has a price tag.
The asymmetry in one line: one limit has an escape hatch
An operations manager feels staff seats every week and catalogs once a quarter, so the seat limit feels more urgent. Frequency is not the same as severity, and on this pair they point opposite ways.
| Staff accounts | B2B catalogs | |
|---|---|---|
| Advanced limit | 15 users (Grow 5, Basic 0 beyond the owner) | 3 active across all B2B markets |
| Same on lower plans? | No. Grow is 5 | Yes. Basic, Grow and Advanced are all 3 |
| Escape hatch inside the platform | Yes. Collaborator accounts do not count toward the user limit, and are unlimited | None. No setting, no app-free workaround |
| Escape hatch outside the platform | Shared operational tooling, a helpdesk that does not need admin access | A third-party pricing app, or a custom pricing layer |
| What exceeding it costs | Process friction and some access hygiene risk | Wholesale pricing you cannot express |
| Reversible? | Yes, instantly | Yes, but only by removing a price structure customers are already quoted on |
All figures per help.shopify.com and shopify.com/pricing, September 2026.
Why the staff limit is softer than it feels
Three reasons, and operations managers are usually surprised by at least one.
Collaborators are free and uncapped. "You can grant access to Shopify Partners or other freelancers with collaborator accounts," and these do not count toward the store's user limit (help.shopify.com, September 2026). Every agency, freelance developer and external contractor on your store is outside the 15.
B2B customers are not staff. Company contacts at your wholesale accounts are customers, not users. A brand with 300 wholesale buyers placing self-serve orders consumes zero staff seats. "Sales staff permissions" are available on every paid plan, so assigning internal reps to companies does not change the maths either.
Most people who "need admin access" need one report. The honest audit here usually finds three or four seats held by people who look at one dashboard weekly. That is a reporting problem wearing a licensing problem's clothes, and it is cheaper to solve than a plan upgrade.
Where the seat limit is genuinely binding: a large in-house merchandising and CX team all needing real admin permissions, plus multiple warehouse locations, plus finance. That is a real shape. It is also a shape that usually arrives with other Plus triggers attached.
Why the catalog limit is harder than it feels
Because there is no version of it you can negotiate around internally. Three is three, it is identical on Basic, Grow and Advanced, and catalogs are counted "across all your B2B markets" rather than per market (help.shopify.com, September 2026). A price list carries exactly one currency, so multi-currency wholesale multiplies rather than adds.
The only non-Plus routes are a third-party pricing app or a custom layer. Both create a second system of record for price, and for an operations manager that is the worst outcome on this page: two places where a customer's price is defined, one of which is not in Shopify, reconciled by a person, forever.
How an operations manager should actually run this decision
- Audit the 15 seats and mark each as admin-required or report-only. Move the report-only people to a reporting tool or a collaborator account.
- Count catalogs as tiers times currencies. Not tiers.
- Recount, excluding volume breaks. Quantity price breaks nest inside a catalog on every plan and consume nothing.
- Ask whether any customer has a negotiated price. If yes, note that direct company catalog assignment is Plus-only.
- If seats are the only pressure, do not upgrade. Fix access hygiene, which you should do regardless.
- If catalogs are at 3 with demand for a fourth, price the app route against the Plus route using the record linked below, and include the cost of maintaining a second pricing system rather than only its subscription.
When the answer flips to staff accounts
- When you are on Grow, not Advanced. Five seats is a genuine operational ceiling and Advanced at $399 per month fixes it for far less than Plus.
- When access hygiene is a compliance requirement. Shared logins to stay under a cap are a real risk, and the cheapest fix may be the plan.
- When your wholesale is one price list in one currency. Then catalogs are not binding, and seats are the only live constraint.
The Deploi point of view
Our own position, from building on Shopify. Separate from the facts above.
- Our take: Catalog capacity, decisively. We treat the staff-seat limit as an access-hygiene finding rather than an upgrade trigger, because collaborator accounts are free and uncapped and most seat pressure is really reporting access. The catalog cap has no in-platform workaround, which makes it the only one of the two that can force a plan change on its own.
- What we’ve seen: Seat pressure is raised in the meeting and catalog pressure is discovered in the configuration. The first is loud and cheap to fix; the second is quiet and expensive, and it is usually already present by the time anyone asks about seats.
- Where we disagree: Upgrade checklists put staff accounts near the top because it is the row every reader understands. It is close to the softest constraint on the list once you know collaborators do not count. We would rather lose the easy row and point at the one with no escape hatch.
- What this page adds: that the two constraints differ in kind rather than degree, because collaborator accounts are unlimited and do not count toward the staff cap while the 3-catalog cap has no in-platform workaround at all, and that the staff cap differs across plans while the catalog cap does not.
Reviewed by Martin Dejnicki, Director of SEO & AI Search. Facts verified 2026-09-14.