Should You Plan Around Shopify's B2B Company-Size Ceilings?
Shopify's B2B company ceilings are a WAIT for nearly every mid-market Plus merchant. A company can have a maximum of 10,000 company locations and a maximum of 10,000 customers, so the headline numbers almost never bind. The cap that bites is 50 customers per company location, which one head-office buying team can hit on day one. Model the account around that number.
Your profile — see how the verdict shifts
- Confidence
- High — Shopify's creating-companies page states all four limits verbatim, read on 2026-09-05: a company can have a maximum of 10,000 company locations, a company can have a maximum of 10,000 customers, a company location can have a maximum of 50 customers, and a company location can have a maximum of 25 catalogs. No dates or deprecation notices appear on that page. Shopify's sales-staff page adds two more numbers that shape the same model: you can assign up to 10 sales staff to each company location, and the same sales staff can be assigned to multiple company locations. On the app side, we browsed the App Store's selling products and pricing category and read 24 B2B and pricing listings, including BSS B2B Wholesale Pricing, SparkLayer B2B & Wholesale, Wholesale Pricing Discount B2B, B2B Wholesale Hub, Massy B2B, Clay B2B and Wholesale Lock Manager. Every one of them adds pricing, ordering or account-team features on top of Shopify's native company and company location objects. Not one claims to raise or manage the ceiling. SparkLayer comes closest by managing Company Users and wholesale teams, and that is account UX layered above the same object model rather than a lift of the platform cap, because a numeric limit on the Company object is enforced by Shopify itself.
- Reference scenario
- $20M–$100M GMV · Shopify Plus B2B on a blended store · about 400 company accounts · largest account has 30 ship-to locations and 120 named buyers · NetSuite or Dynamics already in finance
- As of
- September 2026
Decision at a Glance
| Your profile | Verdict | Why |
|---|---|---|
| Accounts with fewer than 50 buyers per location | WAIT | The native model fits with room to spare. A company holds 10,000 locations and 10,000 customers, and nothing at this shape comes near either number. |
| A head-office team above 50 named contacts | CUSTOMIZE | The 51st buyer at one location cannot be added. The fix is modeling: give buyers the ship-to locations they actually order for, or split head office into several locations. |
| One location needing more than 25 catalogs | CUSTOMIZE | Plus gives unlimited B2B catalogs at the store level, and a company location still takes a maximum of 25. Assign catalogs by segment rather than one per buyer. |
| A single company above 10,000 customers or locations | BUILD | At genuine enterprise scale the org chart outgrows a two-level model. The ERP holds parents, subsidiaries and buying groups, and Shopify holds a projection of it. |
What B2B Company & Location Ceilings Actually Drives
| Outcome | Impact | How it works |
|---|---|---|
| Customer experience | High | A buyer who cannot be added to their own account location cannot log in and order, so the cap surfaces as a blocked purchase rather than an admin warning. |
| Operational efficiency | High | Modeling a national account correctly the first time avoids re-keying hundreds of buyer records when a location hits 50 contacts halfway through a rollout. |
| Revenue — direct | Medium | An enterprise account that cannot be represented in the data model keeps ordering by email instead, and that revenue never reaches the platform at all. |
| Data & insight | Medium | Company and location structure is the join key for account-level reporting, so splitting one commercial customer into three companies distorts every account metric downstream. |
Spend ceiling: Spend nothing here until an account actually breaks a number. The right investment is an afternoon of account modeling before onboarding rather than software, because no listing on the App Store lifts a cap on the Company object and no ERP changes what Shopify will store.
What buying enables (top apps)
- + Wholesale pricing rules, quick-order pads and quoting that native B2B leaves open
- + Buyer registration and approval workflows for onboarding new company contacts
- + Account-team and Company Users management layered over the native company objects
- + Ordering experiences tuned for repeat wholesale buyers rather than for retail shoppers
What building additionally unlocks
- + An account hierarchy that holds parents, subsidiaries and buying groups Shopify's two levels cannot express
- + A documented org-chart mapping that survives the 50-customers-per-location cap by design
- + Buyer provisioning that puts each contact at the right location automatically instead of by hand
- + Reporting that rolls several Shopify companies back into one commercial account for the sales team
Find Your Verdict in 3 Questions
Does any single company location need more than 50 named buyers?
Yes: Go to question 2.
No: Your verdict: WAIT — the native model holds 10,000 locations and 10,000 customers per company, which is far past your shape.
Can those buyers be attached to the ship-to locations they actually order for?
Yes: Your verdict: CUSTOMIZE — remodel the account so contacts sit at their own locations, and the 50-customer cap stops binding.
No: Go to question 3.
Does the customer's org chart go deeper than company and company location, with parents or buying groups?
Yes: Your verdict: BUILD — the ERP owns the hierarchy and Shopify holds a projection of it through a documented integration.
No: Your verdict: CUSTOMIZE — split head office into several company locations, each under the 50-customer cap.
The TCC Scorecard — 12 Dimensions
TCC — Total Cost of Capability: what it actually costs to have this capability over three years, whichever way you get it. Each dimension is scored 0–5 for both paths. How we score →
| Dimension | Buy | Build | Why |
|---|---|---|---|
| Cost | |||
| Acquisition & implementation | The native company model costs nothing and is already there; an app layer installs in a day, and an ERP-side hierarchy is an estimated 3–8 weeks (Deploi estimate, illustrative). | ||
| Recurring fees | A B2B app is a monthly line forever and lifts no limit; the modeling work is a one-time cost with small upkeep behind it. | ||
| Maintenance & upgrades | Vendors maintain their own app surface, while a hierarchy sync owns both ends and every change to the customer's org chart. | ||
| Switching & exit | Companies, locations and customers stay in Shopify whatever leaves, because neither an app nor an ERP owns those records. | ||
| Risk | |||
| Vendor risk | Buying a B2B app to solve a platform ceiling adds a vendor without removing the constraint, which is the worst version of vendor risk. | ||
| Security & compliance surface | An app layer reads company, buyer and pricing data; a hierarchy sync moves the same data between two systems you already audit. | ||
| Platform-deprecation exposure | The creating-companies page carries no dates or deprecation notices, so these four numbers are as stable as anything on this hub. | ||
| Value | |||
| Fit to requirement | No app changes what Shopify will store, so fit comes from modeling the account correctly rather than from any purchase. | ||
| Time to market | An app installs this week; account modeling takes an afternoon of thinking and a few weeks of provisioning work. | ||
| Performance & scale | Only an ERP-held hierarchy scales past 10,000 customers in one company, and only a modeled account survives the 50-per-location cap. | ||
| Data ownership & AI-readiness | The mapping from a real org chart to Shopify companies and locations is the asset, and it belongs in your documentation and your ERP. | ||
| Focus & opportunity cost | Almost every mid-market merchant should spend nothing here, which makes doing nothing the highest-value option on the page. | ||
The App Landscape
| App | Status | Pricing | Best for |
|---|---|---|---|
| Shopify B2B companies and company locations | Native — First-party Shopify, Plus only, and the reason these numbers exist. A company can have a maximum of 10,000 company locations and a maximum of 10,000 customers; a company location can have a maximum of 50 customers and a maximum of 25 catalogs. You can assign up to 10 sales staff to each company location, and the same sales staff can be assigned to multiple company locations (verified Sep 2026). | Included with Shopify Plus (verified Sep 2026) | Practically every mid-market B2B portfolio, which fits inside these numbers with room to spare |
| B2B pricing and ordering apps | Category — The App Store's selling products and pricing category, where we read 24 B2B and pricing listings including BSS B2B Wholesale Pricing, SparkLayer B2B & Wholesale, Wholesale Pricing Discount B2B, B2B Wholesale Hub, Massy B2B, Clay B2B and Wholesale Lock Manager. Every one adds pricing rules, quick ordering, quoting or account-team features on top of Shopify's native company and location objects. None raises a ceiling. SparkLayer comes closest by managing Company Users and wholesale teams, and that still sits above the same object model. | Subscription tiers published per listing; none of them prices a lift of a Shopify limit | Wholesale pricing, quoting and buyer registration, which are real gaps native B2B leaves open |
| ERP or CRM as the account master | Live — Platform integration; the account hierarchy sits outside Shopify. Shopify documents three routes onto the platform: direct integrations from the Shopify App Store for select ERP, accounting and PIM systems, integrations from iPaaS providers acting as intermediaries, and custom API-based integrations for maximum flexibility. NetSuite, Microsoft Dynamics 365, Fulfil and QuickBooks Online are named on that page. An ERP models parents, subsidiaries and buying groups; it does not change what Shopify will store. | Quote-based licensing plus implementation; confirm current terms with the vendor | Enterprise account structures deeper than Shopify's two-level company and location model |
| Account model and buyer provisioning (custom) | Build lane — A documented mapping from the customer's real org chart to Shopify companies and locations, plus provisioning that assigns each buyer to the right location automatically. Small, cheap, and the only work that actually addresses the 50-customer cap. Extends into an ERP hierarchy sync when one company genuinely passes 10,000 customers. | $8,000–$30,000 one-time plus upkeep (Deploi estimate, illustrative) | National accounts whose buying teams cluster at head office rather than at ship-to sites |
The Build Path
- Model the account before you onboard it: Draw the customer's org chart against Shopify's two levels first. A company location is a place that orders and pays, and it holds a maximum of 50 customers and 25 catalogs. Ten minutes of mapping prevents the migration you would otherwise run in month four.
- Give buyers the locations they order for: The 50-customer cap almost always appears because every named buyer was attached to one head-office location. Spread contacts across the ship-to locations they actually purchase against, and the cap stops binding without a single line of code.
- Assign catalogs by segment, not by buyer: Plus gives unlimited B2B catalogs at the store level and allows direct company catalogs, while a company location still takes a maximum of 25. Group locations into pricing segments and assign a catalog per segment so nobody has to count to 25 during a rollout.
- Let the ERP hold anything deeper than two levels: Parents, subsidiaries and buying groups have no Shopify object, so the ERP owns that hierarchy and Shopify holds a projection of it. Shopify's documented routes are direct App Store integrations, iPaaS intermediaries and custom API-based integrations, and the projection is a sync rather than a rebuild.
- Effort band
- $8,000–$30,000 one-time for the account model, buyer provisioning and, where needed, an ERP-side hierarchy sync — Deploi estimate (illustrative); lands in the $10–25K contact-form band
- Typical timeline
- 3–8 weeks, with the account model itself finished in the first week (Deploi estimate, illustrative)
- Maintenance, honestly
- ~15–20% of build cost per year (Deploi estimate): roughly $1,200–$6,000/yr (Deploi estimate, illustrative) for provisioning changes, new locations and keeping the ERP hierarchy and Shopify's projection of it in step.
- What you own — and what you take on
- You own: the mapping from a real org chart to Shopify companies and locations, and the provisioning that keeps it true. You take on: re-modeling an account when the customer reorganizes, which is a business event rather than a technical one.
3-Year Total Cost of Capability
| Buy (app path) | Build (custom path) | |
|---|---|---|
| Year 0 (setup) | $6,000–$30,000 | $8,000–$30,000 |
| Years 1–3 (recurring) | $10,800–$46,000 | $3,600–$18,000 (maintenance) |
| 3-year total | ≈$16,800–$76,000 | ≈$11,600–$48,000 |
- † All figures illustrative samples for the reference scenario — not quotes, not verified pricing.
- † Buy path: a B2B app layer plus the account-management module of an off-platform system, held flat; neither lifts a Shopify limit.
- † Build path: account modeling, buyer provisioning and an ERP-side hierarchy sync for one Plus B2B store, three-year horizon.
What the Sticker Price Hides
On the buy path
- — A B2B app is a permanent monthly line that lifts no Shopify limit, which is the wrong purchase for this problem
- — Account-team features read as if they extend the model, when they layer UX over the same company and location objects
- — Discovering the 50-customer cap during an enterprise onboarding turns a launch week into a re-modeling exercise
- — Splitting one commercial account into several Shopify companies as a workaround distorts every account-level report afterwards
On the build path
- — Re-modeling an account after buyers are already provisioned means re-keying contacts by hand
- — A location count that looks generous still has 25 catalogs and 10 sales staff attached to each one
- — An ERP-held hierarchy needs a reconciliation path, because Shopify's projection drifts whenever the customer reorganizes
- — ~$1,200–$6,000/yr upkeep for provisioning and hierarchy changes (Deploi estimate, illustrative)
What Merchants Say
The surprise is always the same one: a head-office team quietly grows past fifty named buyers, and the next person simply cannot be added to the account.
B2B listings get read as if they extend the account model, then turn out to sit on top of Shopify's own company and location objects without changing a single limit.
If You Change Your Mind Later
If you bought and outgrow it
A B2B app layer leaves with its subscription, while the companies, locations and customers stay in Shopify because the app never owned them. What you lose is the pricing and ordering experience built on top, which is worth confirming before a sales process is standardized on it.
If you built and want out
The account model is documentation and the provisioning is your code, so both survive a change of ERP or dropping the sync entirely. Shopify's company and location records stay exactly where they are, which makes this one of the cheapest decisions on the hub to reverse.
When This Answer Changes
We're watching for:
- ▸ Any of the four limits changing on Shopify's creating-companies page, which carries no dates or deprecation notices today
- ▸ A third level appearing in Shopify's B2B object model above company and company location
- ▸ The 10-sales-staff-per-company-location limit moving, since it binds before the customer cap for large account teams
Verdict change log:
No changes since first publication (September 2026).
Common Questions
How many company locations and customers can one Shopify B2B company hold?
A company can have a maximum of 10,000 company locations and a maximum of 10,000 customers. A company location can have a maximum of 50 customers and a maximum of 25 catalogs. The 10,000-customer cap binds first in practice: 200 fully populated locations reach it, long before the 10,000-location limit matters.
Which of Shopify's B2B ceilings actually causes problems?
The 50-customers-per-company-location cap causes them. A national account whose buying happens centrally puts every named buyer on one head-office location, and the 51st buyer cannot be added. Spread contacts across the ship-to locations they order for, or split head office into several locations. The 10,000 figures rarely matter at mid-market scale.
Can a Shopify app raise the B2B company or location limits?
No. A review of 24 B2B and pricing listings, including BSS B2B Wholesale Pricing, SparkLayer B2B & Wholesale and Wholesale Pricing Discount B2B, found none that lifts a limit. Every one adds pricing, ordering or account-team features on top of Shopify's native company and location objects. Shopify itself enforces the 50-customer and 10,000-customer caps.
Your Next Steps
If you're going with WAIT(matches your selected profile)
- Count named buyers on your largest account's busiest location and compare it to 50
- Count catalogs assigned to any single location and compare it to 25
- Record both numbers in your onboarding checklist so sales sees them before promising a structure
- Revisit only when an account approaches either number, since the 10,000 figures are far away
If you're going with CUSTOMIZE
- Draw the customer's org chart against Shopify's company and company location levels
- Attach each buyer to the ship-to location they actually order for, not to head office
- Split any location still above 50 contacts into named sub-locations with their own addresses
- Group locations into pricing segments so no location needs more than 25 catalogs
- Automate provisioning so the next 200 buyers land in the right place without a spreadsheet
Official Docs & Sources
- Creating B2B companies — Shopify Help Center
- B2B sales staff — Shopify Help Center
- B2B plan features — Shopify Help Center
Official documentation linked for verification — our verdicts and estimates are our own.
Related Decisions
Should You Build or Buy B2B Deposit Payments on Shopify Plus?
Plus's native B2B deposits collect the percent up front, but the balance is never auto-captured. Both purpose-built B2B deposit apps had 0 reviews when checked.
ERP vs. Shopify: Who Should Own B2B Pricing?
Shopify's B2B integration page names three sanctioned ERP paths and never says which system should own pricing. Channel count decides the answer, not the platform.
Can Shopify's Catalog Model Hold 30+ Price Tiers?
A company location holds a maximum of 25 B2B catalogs (verified Sep 2026). Model 30+ tiers as volume breaks, or split the account across company locations.
Should You Build or Buy Company-Specific B2B Pricing on Plus?
Direct company catalogs give one company or location its own price list natively on Plus; below Plus, an app's per-customer price lists are the workaround.
Should You Build or Buy Your NetSuite Integration on Shopify?
NetSuite integration is the honest DEPENDS: buy a connector for standard flows, build middleware when the flows are the business.
Model the account before it hits the cap
We map a national account's org chart onto Shopify companies and locations before onboarding, so the 51st buyer is never the moment you discover the limit.
Contact us todayVerdict scored for the reference scenario above. Estimates are not quotes; app pricing carries its verification date and gets re-verified quarterly. Full scoring anchors: see the TCC methodology.
Read how we score these decisions (the TCC Framework). No affiliate links, no paid placement — no app vendor pays to appear here.