Shopify B2B Limitations in 2026: The Real Walls You Hit at Scale

You didn't set out to build a wholesale operation on Shopify. It happened the way these things usually happen: a few B2C customers started ordering in bulk, someone asked for net-30 terms, and you said yes because saying yes to revenue is what merchants do. Eighteen months later you have a real wholesale book, a handful of reps quoting custom pricing over email because the storefront can't, and an ops person manually checking outstanding balances before releasing orders. Nothing is broken yet. But you've started noticing the seams, and you're not sure if the fix is an app, a Plus upgrade, or a different platform entirely.

This is the most common way merchants find this article: not through a dramatic outage, but through a slow accumulation of workarounds that quietly become the job. Here is what is actually happening under the hood, and where the walls really sit.

The 3-catalog cap: the wall you hit first

Shopify's native B2B, rolled out to every plan (not just Plus) as of April 2026, is genuinely useful for a merchant with a simple wholesale tier structure. It lets you assign company accounts, set custom pricing, and offer net payment terms without a third-party app. For the first month, it feels like exactly what you asked for.

Then the second wholesale customer wants a different discount structure than the first, and the third wants something in between, and you realize the ceiling: Basic, Grow, and Advanced plans are capped at three active pricing catalogs, full stop, across all markets. Retail, Wholesale, VIP. That's it. If a fourth customer needs a special rate, either you fold them into an existing catalog and eat the margin difference, or you can't onboard them on native pricing at all.

Real wholesale operations rarely settle at three tiers. A distributor selling into independent retailers, regional chains, and a handful of strategic accounts typically needs five to eight pricing structures within the first quarter of taking B2B seriously, before you even get to volume breaks or seasonal terms. Most merchants who go looking at this cap discover it "in week one," in the words of one practitioner writeup on the problem, not after years of growth. It's not an edge case. It's the default shape of a real B2B customer base.

At that point you have two paths: upgrade to Shopify Plus (roughly 2,100 to 2,250 EUR per month depending on contract term, before app spend), or run wholesale logic through a third-party app stack layered on top of a non-Plus plan. Neither is free, and neither is native. We break down what the Plus upgrade actually costs over a full year in our Shopify Plus total cost breakdown, because the sticker price is never the whole number.

Credit limits, PO approval, and dunning: the parts Shopify never built

Even once you're on Plus, native B2B still doesn't do several things that any wholesale operation eventually needs.

Shopify lets you assign net-15, net-30, or net-60 terms to a company location. What it does not do is enforce a credit limit at checkout. There is no native mechanism to block an order when a buyer's outstanding balance crosses a threshold you set. If your accounts-receivable team wants a hard stop at, say, 10,000 EUR outstanding, someone has to build and maintain that logic outside Shopify, usually through a middleware app or a manual check before releasing the order.

Dunning is the same story. Automated payment-due reminders as an invoice approaches its due date aren't part of native B2B. You can build reminder logic through a subscription or invoicing app, or you do it manually, which is what most merchants at this stage are actually doing: someone on the ops team running a report and sending emails.

Purchase order approval is a bigger gap. Multi-level PO approval, where a buyer submits an order that routes through one or more internal approvers before it's confirmed, has no native equivalent in Shopify B2B. Checkout also can't add a required custom field like a PO number without custom development, and tax IDs can't be set per company location out of the box. If your B2B buyers are used to a procurement workflow with sign-off chains, and most mid-size and larger wholesale buyers are, you're building that from scratch on top of Shopify regardless of plan tier.

None of this makes Shopify B2B bad. It makes it a genuinely capable starting point for merchants whose wholesale requirements are simple: a handful of tiers, straightforward net terms, no internal approval chains. The gap opens specifically for operations with procurement-grade requirements, and that gap doesn't close by upgrading plans. It closes by adding apps, middleware, or moving the logic to a platform that ships it natively.

The blended-store problem: one company per customer

Here's a structural limitation that surprises merchants who assumed it was just a configuration issue: in Shopify's "blended store" model, a single customer account can be associated with only one company at a time. A buyer cannot hold both a B2C identity and a B2B (company) identity on the same account.

This sounds abstract until you run a real wholesale-plus-retail business. Think about a regional distributor whose owner also buys personally from your consumer storefront, or a business account where the person managing procurement is also a loyalty-program customer for their own purchases. Under Shopify's blended model, that's not one account with two contexts. It's two separate customer records, with no native link between them, and no unified order history or loyalty tracking across the two identities.

The standard workaround the Shopify community has settled on is exactly what it sounds like: create two accounts per person and manage the split manually. It works, in the sense that duct tape works. It also means your customer data is fractured by design, your marketing segmentation double-counts or under-counts real people, and your support team has to ask "which account are you on" before they can help. The alternative, a dedicated B2B storefront instead of a blended one, solves the identity conflict but means running an entirely separate Shopify instance, with its own catalog, checkout, and admin, doubling your operational surface instead of unifying it.

If your B2B and B2C customer bases genuinely overlap, and for most wholesale-plus-retail merchants they do, this isn't a minor annoyance. It's a data model mismatch that no app fully resolves, because it's baked into how Shopify defines a customer.

What Magento does natively that closes these gaps

This is the part where the platform argument gets concrete rather than philosophical. Adobe Commerce (the B2B module ships as core, not a paid add-on, and works the same on Magento Open Source builds using the community B2B extension) handles the exact set of problems above as first-class, unlimited features:

Shared catalogs, no cap. You create as many custom shared catalogs as your business needs, tied to company or customer group, with no artificial ceiling at three, five, or twenty. A distributor with twelve regional pricing structures configures twelve catalogs. This alone removes the single most common trigger that forces Shopify merchants toward a Plus upgrade they didn't otherwise need.

Negotiable quotes. Buyers can request a quote directly from the cart, sales reps can counter with adjusted pricing or terms, and the negotiation lives inside the platform as an audit trail, not in an email thread. This is the RFQ workflow that Shopify has no native equivalent for at any plan tier.

Multi-level PO approval. Company accounts support hierarchies with defined approval roles, so a buyer submitting an order above a threshold routes to the right approver automatically, with the whole chain logged. This is core functionality, not a bolt-on.

Company-account structure that actually models real organizations. A company account can have multiple users with different permission levels, multiple shipping addresses, and its own credit and payment terms, all under one company record. A person can belong to a company account for wholesale purchasing and still have an independent retail identity, because Magento's customer and company models aren't fused the way Shopify's blended-store model is.

Tax matrix per customer group and region. Combined with proper tax configuration, B2B pricing and tax exemption status can be set per company location and customer group, closing the gap that Shopify B2B leaves to per-order manual handling.

None of this is exotic. It's the same B2B logic that mid-market wholesale operations have run for over a decade, it's just native to the platform rather than something you assemble from apps and workarounds.

The Plus-upgrade math you should actually run

Here's the uncomfortable arithmetic. The 3-catalog cap is what forces most growing wholesale operations toward Shopify Plus, and Plus is not a small line item. Beyond the monthly platform fee, B2B on Plus carries its own additional variable platform fee, and you're still paying for the app stack that covers the parts native B2B never built (credit limits, dunning, PO workflows). Add implementation time for the upgrade itself, and the first-year cost of "solving" the catalog cap by upgrading is a meaningfully larger number than the headline monthly fee suggests. We walk through that full-year math, apples to apples against a self-hosted Magento setup, in our Shopify Plus total cost teardown. If you're staring at a Plus quote right now, that's the number to run before you sign.

When Magento B2B is not the answer

Honesty matters more than a tidy narrative here. If your wholesale operation genuinely fits inside three pricing tiers, your payment terms are standard net-30 with no credit-limit enforcement needed, and you don't have multi-level procurement approval chains to support, Shopify's native B2B (or Shopify Plus B2B with a modest app layer) may well be the right answer, and migrating to a new platform to solve a problem you don't actually have would be an expensive mistake. Shopify's B2B business is also growing fast, with real enterprise wins, so this isn't a platform in decline. The wall is specific: it's depth of B2B logic at real operational complexity, not B2B as a category. Know which side of that line your business sits on before you commit to a migration.

Where to go from here

If you've read this far and recognized your own operation in the catalog cap, the manual credit checks, or the two-accounts-per-customer workaround, the next honest question is whether a migration is worth the disruption, and what it would actually involve. Our migration playbook covers the mechanics and timeline in detail, and our pillar guide lays out the full strategic comparison if you're still weighing the decision itself.

If you'd rather talk it through with someone who has actually done this migration, book a free strategy call with LIQUIDLAB. We'll look at your actual catalog structure, your actual B2B workflows, and tell you honestly whether the wall you've hit is a Plus upgrade, an app, or a platform change, before you spend a euro on any of them.