ChatGPT answers, unedited

For your requirements, I’d shortlist BigCommerce B2B Edition and Shopify Plus, with BigCommerce as the more natural fit if this is a true B2B portal rather than a DTC store with wholesale layered on.

My pick: BigCommerce B2B Edition

BigCommerce is particularly well aligned with what you described. Its B2B Edition has Company accounts, buyer roles, customer groups, customer-specific catalogs, price lists, quotes, invoices and net-term workflows. BigCommerce explicitly supports personalized pricing based on customers, contracts, tiers and account structures. BigCommerce BigCommerce

The important architectural piece is that Company → Customer Group → Catalog/Pricing gives you a clean way to model something like:

Company A
 ├── Buyer 1
 ├── Buyer 2
 └── Buyer 3
       │
       ├── Allowed catalog: Industrial Products
       ├── Contract pricing: 2026-ABC
       ├── Payment terms: Net 30
       └── Account-specific discounts

Company B
 ├── Buyer 1
 └── Buyer 2
       │
       ├── Allowed catalog: Premium Products
       ├── Contract pricing: 2026-XYZ
       └── Payment terms: Net 60

BigCommerce documents that customer groups determine the products and pricing buyers see, while price lists can provide company/currency-specific pricing. BigCommerce BigCommerce

The IP restriction needs a separate security layer

I wouldn't rely on the ecommerce platform itself for IP restriction.

I'd put a WAF/access-control layer in front of the storefront:

Customer
   ↓
WAF / Zero-Trust Access
   ├── Allowed corporate IP?
   └── HTTPS / bot / rate-limit controls
          ↓
   BigCommerce B2B Store
          ↓
   Authenticated Company Account
          ↓
   Customer-specific Catalog + Contract Pricing

That gives you two independent gates:

1. Network gate: request originates from an approved corporate IP/network.
2. Application gate: user has an authenticated account belonging to an authorized company.

That's considerably better than treating an IP whitelist as the authentication mechanism.

Shopify Plus is the alternative I'd seriously consider

Shopify has become substantially more capable for B2B. Its native B2B system supports companies, company locations, catalogs, customer-specific product availability and pricing, volume pricing, payment terms and buyer permissions. Shopify Help Center Shopify Help Center

The particularly relevant distinction is that Shopify Plus allows catalogs to be assigned directly to individual companies/company locations, which is useful when every customer has its own contract assortment and pricing. Shopify Help Center Shopify Help Center

The downside for your use case is that IP-based access control isn't really a core Shopify B2B primitive. Shopify itself suggests third-party mechanisms when you need to lock all or portions of a storefront to logged-in users. Shopify Help Center

Shopify Plus currently starts at $2,500/month on a 1-year term or $2,300/month on a 3-year term in USD, with variable pricing possible for more complex businesses. Shopify Help Center Shopify

What I'd choose based on your situation

• Distributor/manufacturer with lots of negotiated contracts, account hierarchies, RFQs, POs and net terms → BigCommerce B2B Edition
• B2B storefront where design, UX, integrations and potentially DTC are equally important → Shopify Plus
• Extremely complex pricing/catalog rules or highly customized procurement workflows → consider Adobe Commerce/OroCommerce as well
• Security requirement is “only these corporate networks can reach the site” → put Cloudflare/Akamai/Azure Front Door/etc. in front regardless of platform

One important distinction: if by “IP-restricted” you mean each customer has its own fixed IP range, that's straightforward to architect. If you mean the storefront should only be reachable from a company's VPN/private network, I'd design this more like a zero-trust/private B2B application than a conventional ecommerce site.

If you tell me roughly how many customer accounts you have, whether every customer has unique pricing, and whether you need ERP integration (SAP/NetSuite/Dynamics/etc.), I can narrow this down to a specific architecture and estimated implementation complexity.

Shopify Plus currently starts at $2,500/month on a 1-year term or $2,300/month on a 3-year term in USD, with variable pricing possible for more complex businesses.

What I'd choose based on your situation

Shopify has become substantially more capable for B2B. Its native B2B system supports companies, company locations, catalogs, customer-specific product availability and pricing, volume pricing, payment terms and buyer permissions.

For your requirements, I’d shortlist Adobe Commerce B2B and Shopify Plus, with an important distinction: IP restriction is usually an infrastructure/access-control layer rather than the core B2B-commerce feature.

My practical recommendation

Adobe Commerce B2B is probably the better fit if your storefront is genuinely private/enterprise-oriented and you need highly customized account-level behavior.

It natively supports:

• Company accounts and multiple users/roles within each customer organization. Experience League
• Company-specific catalogs, so different accounts can see different products/content. Experience League Experience League
• Contract/customer-specific pricing, including fixed prices or percentage-based pricing within shared catalogs. Experience League Experience League
• Negotiable B2B quotes, useful when contract pricing isn't completely static. Experience League
• Fine-grained catalog/category permissions and company associations. Experience League

You could then put the storefront behind something like a VPN, Zero Trust gateway, corporate SSO/access proxy, or IP allowlist. That gives you a much stronger security boundary than trying to make the commerce platform itself responsible for IP filtering.

Shopify Plus

Shopify Plus is attractive if you want considerably less infrastructure to operate. Shopify's B2B system now supports company accounts, catalogs, and customized pricing; Plus adds unlimited catalogs and direct catalog assignment to individual companies/company locations, which is particularly relevant to contract pricing. Shopify Help Center Shopify Help Center

Shopify Plus also supports headless B2B experiences if you want a custom storefront while keeping Shopify as the commerce backend. Shopify

The catch for your use case is that strict IP-based access control isn't really Shopify's native B2B primitive. I'd put an external identity/access layer in front of it if "only users coming from approved corporate networks may access this" is a hard requirement.

How I'd architect it

Corporate customer
       │
       ▼
DNS / CDN / WAF
       │
       ├── IP allowlist / Zero Trust policy
       ├── SSO / MFA
       └── rate limiting / bot protection
       │
       ▼
Private B2B storefront
       │
       ▼
B2B commerce platform
       │
       ├── Company A → Catalog A → Contract prices A
       ├── Company B → Catalog B → Contract prices B
       └── Company C → Catalog C → Contract prices C

For highly controlled industrial/distributor/wholesale commerce, I'd lean toward Adobe Commerce B2B + an external Zero Trust/WAF layer.

For a polished, lower-maintenance B2B storefront where security and account-specific pricing matter but you don't want to run much infrastructure, I'd look closely at Shopify Plus + an external access-control layer.

One caveat: if by “per-account content” you mean not merely different products/prices, but literally different pages, documents, PDFs, technical drawings, CMS blocks, downloads, etc. for each customer, that pushes the decision more toward Adobe Commerce or a custom/headless architecture.

Adobe Commerce is the strongest fit if security and complex B2B rules are priorities. Its B2B shared catalogs support account-specific product visibility and contract pricing natively. Experience League

For a simpler managed SaaS option, Shopify Plus is easier to operate and supports company-specific catalogs/pricing. Shopify Help Center Shopify Help Center

For IP-restricted access specifically, I’d put the restriction at the CDN/WAF layer (e.g., Cloudflare) rather than relying solely on the commerce platform.

For your requirements, Adobe Commerce (Magento) B2B is probably the strongest fit if IP-restricted access + account-specific catalogs + contract pricing are core requirements.

My ranking

1. Adobe Commerce B2B — best for complex B2B

• Company accounts and gated storefronts
• Shared catalogs assigned to specific companies
• Per-company product visibility
• Fixed or percentage-based custom pricing and tier pricing
• B2B quotes and negotiated pricing
• Strong API/customization options
• You can put the storefront behind a WAF/reverse proxy and enforce IP allowlists at the infrastructure layer. Adobe's native B2B catalog controls handle the account authorization separately. Experience League Experience League

This is the one I'd choose if you're selling to distributors, dealers, enterprise customers, or accounts with genuinely different contractual catalogs/prices.

2. Shopify Plus — best if you want less infrastructure

• Company/company-location accounts
• Customer-specific catalogs and pricing
• Payment terms
• Buyer permissions
• Strong hosted infrastructure and much easier operations
• Direct catalog assignment to companies/locations is a Plus feature. Shopify Help Center Shopify

Shopify Plus currently starts at $2,500/month on a 1-year term or $2,300/month on a 3-year term, before other costs. Shopify

Caveat: I'd treat IP restriction as an edge/security-layer requirement rather than a native Shopify B2B feature. If "only these corporate networks can reach the storefront" is a hard requirement, Adobe/custom architecture is more natural.

3. Custom headless storefront + commerce backend

Worth considering if you need something like:

Corporate IP → SSO → Account → Contract → Catalog → Price → Checkout

You could use a commerce engine for products/orders/pricing and put Cloudflare/Akamai/etc. in front for IP/network controls. This gives maximum control but is considerably more expensive to build and maintain.

What I'd build

For a serious private B2B portal, I'd use:

Cloudflare/WAF → Adobe Commerce B2B → SSO/IdP → company account → shared catalog/contract price

The important distinction is that IP restriction should not be your primary authentication mechanism. Use IP/network restrictions as an additional gate, with SSO/login and company authorization determining what the buyer is actually allowed to see.

Adobe's model maps particularly well to your "per-account content + contract pricing" requirement: a custom shared catalog can be assigned to specific companies, and that catalog controls both product availability and custom prices. Experience League Experience League

Bottom line:

• Complex contracts / many account-specific catalogs → Adobe Commerce B2B
• Simpler B2B + want SaaS/easy operations → Shopify Plus
• Extremely strict network/security requirements → custom/headless architecture

If you tell me roughly how many customer accounts, whether users need SSO, and whether IP restriction means office-IP allowlisting or VPN-only access, I can recommend a concrete stack and architecture.

Adobe's model maps particularly well to your "per-account content + contract pricing" requirement: a custom shared catalog can be assigned to specific companies, and that catalog controls both product availability and custom prices.

Bottom line:

For your requirements, Adobe Commerce (Magento) B2B is probably the strongest fit—especially if the storefront must be genuinely private and highly customized.

Best fit: Adobe Commerce B2B

It natively supports:

• Company accounts with multiple buyers and roles.
• Per-company catalogs — products can be visible only to particular companies.
• Contract/customer-specific pricing through Shared Catalogs, including fixed prices, percentage discounts, and quantity tiers. Experience League Experience League
• Account-specific content/catalog experiences, with catalog and category permissions tied to company access. Experience League Experience League
• Quotes and negotiated pricing, useful when contracts aren't completely fixed. Experience League

For the IP-restricted part, I'd put a WAF/reverse proxy in front of Commerce—e.g. Cloudflare—so the application only accepts traffic from approved corporate IP ranges. I would not treat IP restriction as the primary authentication mechanism; use it as an additional security layer alongside authenticated company accounts.

How I'd compare the main options

BigCommerce B2B is the alternative I'd seriously consider if you don't want to operate a Magento/Adobe Commerce stack. Its company accounts can be mapped to customer groups, with different catalogs and pricing, and Price Lists can provide company/group-specific SKU pricing. BigCommerce BigCommerce

Shopify can restrict a dedicated B2B store to logged-in B2B customers, but a true IP allowlist generally requires additional infrastructure/customization. Shopify Help Center

My recommendation

If your requirement is essentially:

"Each customer gets a private portal, sees only their contracted products/content, gets their negotiated prices, and only approved corporate networks can reach it."

I'd choose Adobe Commerce B2B + Cloudflare/WAF.

If instead you want "same capabilities, but minimize infrastructure and engineering overhead," I'd choose BigCommerce B2B + Cloudflare.

One important architectural point: don't implement the security model as "IP = customer." Corporate IPs can change, users can work remotely, and multiple users may share an egress IP. Use company identity/account → permissions/catalog/pricing, with IP allowlisting as an additional gate. Experience League Experience League

If you tell me roughly number of customer accounts, SKUs, whether each account has unique pricing, and whether the storefront needs to be completely invisible to the public, I can narrow this down to a specific stack and architecture.

For a secure B2B storefront with IP-restricted access, per-account content, and contract pricing, I would not start with a normal ecommerce platform. You’re describing a private commerce portal with identity, authorization, pricing rules, and possibly procurement workflows.

The best choice depends on complexity:

Best overall for complex B2B: Adobe Commerce (Magento)

Best fit if you need:

• Customer-specific catalogs
• Contract price books
• Account hierarchies (parent company → subsidiaries → buyers)
• Role-based permissions
• RFQs/quotes
• ERP integration
• Custom approval workflows
• Deep control over authentication and access rules

Adobe Commerce’s B2B capabilities are designed around company accounts, shared catalogs, negotiated pricing, and complex purchasing workflows. Shopify

How I’d implement IP restriction:

• Put the storefront behind a zero-trust access layer: - cloudflare.com
• okta.com
• microsoft.com
• Require SSO + MFA
• Add IP allowlists for corporate networks/VPNs
• Enforce authorization at the application layer (not just firewall rules)

Best SaaS option: Shopify Plus B2B

Good if you want faster deployment and your B2B rules are relatively straightforward:

• Customer login required for B2B pricing
• Company accounts
• Customer-specific catalogs
• Assigned pricing
• Volume pricing
• Wholesale-only products

Shopify B2B supports company accounts and restricts B2B-specific products/pricing to authenticated customers. Shopify Help Center Its catalogs can control product availability and pricing by company/customer group. Shopify Help Center

Where it may fall short:

• Very complex contract pricing formulas
• Thousands of negotiated price agreements
• Heavy procurement workflows
• Advanced approval chains

Best B2B-native platforms to evaluate

OroCommerce

Strong choice for distributors/manufacturers:

• Account-based pricing
• Customer-specific catalogs
• Sales workflows
• B2B-first architecture

commercetools

Best if you want a custom/headless architecture:

• Build your own storefront
• Plug into enterprise identity systems
• Maximum flexibility
• More engineering effort

Virto Commerce

Worth considering for highly customized B2B:

• Contract pricing
• Account-specific catalogs
• Personalized buyer experiences at the data layer Virto Commerce

Recommended architecture for your requirements

A strong enterprise pattern would be:

Users
  |
  | MFA / SSO
  |
Identity Provider
(Okta / Entra ID)
  |
  | IP + device + user policy
  |
Zero Trust Gateway
(Cloudflare Access)
  |
  |
B2B Commerce Platform
(Adobe Commerce / Oro / Shopify Plus)
  |
  |
ERP + CRM
(SAP / NetSuite / Dynamics)

Your authorization model should look something like:

Account: Acme Corp

Allowed IP ranges:
- Corporate VPN
- Headquarters network

Users:
- Buyer A: view + order
- Manager B: approve orders
- Admin C: manage users

Catalog:
- Product group X only

Pricing:
- Contract #12345 pricing
- Net 60 terms
- Minimum order quantities

My shortlist

If your storefront is for hundreds/thousands of customer accounts with negotiated pricing, I would lean toward Adobe Commerce + SSO/Zero Trust access control. If it is more like 50–500 wholesale customers with simpler pricing, Shopify Plus is likely the better operational choice.

For those requirements, I’d shortlist Adobe Commerce (Magento) first, with BigCommerce B2B as the easier-to-operate alternative.

My pick: Adobe Commerce B2B

Adobe Commerce is particularly strong when security and account-level isolation matter as much as storefront UX.

• Per-account content/catalogs: B2B Shared Catalogs can be assigned to specific companies, controlling which products/categories they can see. Experience League Adobe Developer
• Contract/customer-specific pricing: Shared Catalogs support custom prices for different companies. Experience League Experience League
• Company accounts: Multiple buyers can belong to a company account, with roles and permissions. Experience League
• Negotiated pricing: Built-in B2B Quotes support price negotiation. Experience League
• Security/IP restrictions: IP allowlisting isn't the core B2B feature, but Adobe Commerce is much more suitable for putting the storefront behind an application/WAF/access-control layer where you can enforce corporate IP allowlists, VPN access, SSO/MFA, etc.
• Complexity: This is the tradeoff—it generally requires a capable implementation/infrastructure team.

BigCommerce B2B is probably the best simpler option

BigCommerce has a very good native B2B model: company accounts, customer groups, catalogs, and price lists. Customer groups can determine both the catalog and pricing a company sees, while price lists can provide company-specific pricing. BigCommerce BigCommerce

I'd choose it if you want less custom development and operational overhead than Adobe Commerce.

Shopify Plus

Shopify Plus is attractive if storefront usability and speed of implementation are priorities. Its B2B catalogs can control products and pricing at the company/company-location level, with unlimited catalogs on Plus. Shopify Help Center Shopify Help Center

The caveat is your IP-restricted/private-store requirement. Shopify's native B2B capabilities are excellent for account-based catalogs and pricing, but I'd be less inclined to choose it if "only users coming from these corporate networks may access this storefront" is a hard security boundary.

What I'd use for your architecture

For a genuinely private B2B portal, I'd build:

Cloudflare Access/WAF → Adobe Commerce → B2B company accounts → Shared Catalogs → contract pricing

with:

• corporate IP allowlists at the edge
• SSO + MFA for buyers
• company-level authorization inside the application
• separate catalog/content assignments per customer
• contract/price-list data tied to the company account
• audit logging
• no reliance on IP address alone for authorization

Bottom line:
If the requirement is "secure private portal + strict customer isolation + sophisticated contract pricing", I'd pick Adobe Commerce B2B. If you want 80–90% of that capability with substantially less implementation complexity, I'd pick BigCommerce B2B. Shopify Plus would be my choice primarily when ease of commerce operations outweighs the need for a heavily restricted network-access model. Experience League BigCommerce Shopify Help Center

The caveat is your IP-restricted/private-store requirement. Shopify's native B2B capabilities are excellent for account-based catalogs and pricing, but I'd be less inclined to choose it if "only users coming from these corporate networks may access this storefront" is a hard security boundary.

What I'd use for your architecture

For a genuinely private B2B portal, I'd build:

For your requirements, Adobe Commerce (Magento) is probably the strongest fit if security and account-level customization matter more than ease of implementation.

My ranking

Why Adobe Commerce: its native B2B model has company accounts, company hierarchies/users, gated shared catalogs, company-specific pricing, permissions, payment methods, and negotiated quotes. Custom shared catalogs can be visible only to specific company accounts, which maps very closely to “Account A sees this content and these prices; Account B sees something else.” Experience League Experience League Experience League

Shopify Plus is the better choice if you want substantially less engineering. Shopify now supports company accounts, catalogs, customer-specific product availability and pricing, and direct catalog assignment to company locations. Plus removes the catalog limitations of the lower plans. Shopify Help Center Shopify Help Center Shopify Help Center

The architecture I'd use

For a genuinely secure B2B storefront, I wouldn't make IP restriction the primary authentication mechanism. I'd use:

Cloudflare/WAF → IP allowlist → authenticated storefront → account/company authorization → account-specific catalog/pricing

That gives you defense in depth:

• IP restriction: only corporate/VPN egress IPs can reach the storefront.
• Authentication: individual buyer accounts still authenticate.
• Authorization: the account is associated with a specific company/customer.
• Content: company-specific catalog determines what they can see.
• Pricing: company/catalog determines their contract prices.
• Admin controls: sales/admin users can manage accounts without exposing another customer's data.

For Adobe Commerce, the native B2B shared-catalog model is particularly well suited to this: custom catalogs can contain custom prices and be assigned to specific companies. Experience League Experience League

My recommendation

If you have dozens/hundreds of customer accounts, negotiated contracts, complex permissions, ERP integration, or highly sensitive pricing, I'd choose Adobe Commerce + Cloudflare/WAF.

If you have a relatively straightforward wholesale operation and want to launch quickly, I'd choose Shopify Plus + Cloudflare/access-control layer. Shopify's native B2B functionality is now considerably stronger than it used to be. shopify.com shopify.com

If you tell me roughly how many customer accounts you have, whether each account has unique pricing, and whether the storefront needs to be completely invisible from the public internet, I can recommend the exact architecture and platform.

For your requirements, I’d shortlist Adobe Commerce B2B first, with BigCommerce B2B Edition as the simpler alternative.

My pick: Adobe Commerce B2B

It maps unusually well to your requirements:

Adobe's Shared Catalog system lets you create catalogs that are visible only to assigned company accounts, with custom pricing for those companies. Experience League Experience League You can also control which products/categories are exposed and assign fixed or percentage-based custom prices. Experience League

It also supports company accounts, multiple users/roles, B2B quotes, and customer-specific catalogs/pricing. Experience League Experience League

Where I'd use something else

BigCommerce B2B Edition is probably the better choice if you want less engineering/operations overhead. Its company accounts can be associated with customer groups and price lists, allowing individualized company pricing. BigCommerce

The main distinction I'd make:

• Adobe Commerce B2B → best for a highly customized, complex B2B portal where account-specific catalogs, permissions, content, pricing, ERP integration, and business rules are central.
• BigCommerce B2B → best if you want a managed SaaS storefront and want to minimize infrastructure and maintenance.
• Shopify Plus + B2B → worth considering for a modern, relatively straightforward B2B operation, but I'd be more cautious if your per-account content/access rules are unusually granular.
• commercetools → best if you're building a headless commerce platform rather than looking for an out-of-the-box storefront.

Important point about IP restriction

I would not make the commerce platform itself responsible for IP allowlisting.

For a genuinely secure B2B storefront, I'd architect it roughly as:

Customer → CDN/WAF → IP allowlist/VPN/Zero Trust → storefront → B2B commerce backend

Then use the commerce platform for identity + company/account authorization + catalog + pricing.

That gives you two independent controls:

1. Network-level: only approved corporate networks/IPs can reach the portal.
2. Application-level: even an approved IP only gets the products, content, and prices belonging to that customer's account.

That second layer is particularly important—IP restriction by itself shouldn't determine which customer's contract pricing somebody sees.

If I were building this today: I'd choose Adobe Commerce B2B + Cloudflare/AWS WAF-style network controls for a complex enterprise storefront. If the business rules are relatively simple and you want SaaS rather than a heavily managed Magento stack, I'd choose BigCommerce B2B.

If you tell me roughly number of B2B accounts, whether each account has unique pricing/catalogs, and whether you need ERP/CRM integration, I can narrow this to 2–3 architectures and give you an estimated implementation complexity/cost comparison.

That second layer is particularly important—IP restriction by itself shouldn't determine which customer's contract pricing somebody sees.

If I were building this today: I'd choose Adobe Commerce B2B + Cloudflare/AWS WAF-style network controls for a complex enterprise storefront. If the business rules are relatively simple and you want SaaS rather than a heavily managed Magento stack, I'd choose BigCommerce B2B.

If you tell me roughly number of B2B accounts, whether each account has unique pricing/catalogs, and whether you need ERP/CRM integration, I can narrow this to 2–3 architectures and give you an estimated implementation complexity/cost comparison.

For your requirements, I’d shortlist Adobe Commerce, Shopify Plus, and BigCommerce B2B—but Adobe Commerce is the strongest fit if IP restriction is a hard security requirement.

My ranking

1. Adobe Commerce B2B — my pick

Adobe's B2B functionality has company accounts, shared catalogs, company-specific product visibility, and custom pricing. A custom shared catalog can be assigned to particular companies, so different customers can effectively see different products and prices. Experience League Experience League

It also has APIs and a highly customizable architecture, which makes it much easier to put a WAF/reverse proxy/IP allowlist/SSO layer in front of the storefront. Adobe Developer

The important distinction: IP restriction isn't really the ecommerce platform's B2B feature. I'd implement it at the edge—for example:

Customer → WAF/IP allowlist → SSO/auth → Adobe Commerce → account-specific catalog/pricing

That gives you a much stronger security model than trying to make IP addresses themselves represent customer authorization.

2. Shopify Plus — best if ease of use matters more

Shopify B2B now supports company profiles, catalogs, company locations and customer-specific pricing. On Plus, catalogs can be assigned directly to specific company locations, with unlimited catalogs. Shopify Help Center Shopify Help Center

It's probably the best choice if you want a polished storefront and minimal custom development. However, hard IP-gated access + highly customized account-specific content will generally require an additional edge/authentication layer and potentially custom development.

3. BigCommerce B2B — good middle ground

BigCommerce B2B has company accounts, customer groups and price lists, allowing company-specific pricing and product access. BigCommerce BigCommerce

It's attractive if you want robust B2B commerce without going as deep into Adobe's enterprise ecosystem.

What I'd build

If the requirement is literally:

"Only users coming from approved corporate IP ranges can access this storefront, and once authenticated they see only their company's products/content and negotiated contract prices."

I'd choose Adobe Commerce B2B + Cloudflare/Akamai-type edge security + SSO/IdP.

Use:

• IP allowlists at the WAF/network edge
• SSO + MFA for actual user authentication
• Company accounts for authorization
• Shared catalogs for product/content visibility
• Contract/customer pricing for negotiated prices
• Role-based permissions for buyers/admins
• Audit logging for sensitive B2B activity

That separates network-level security from business-level authorization, which is the architecture I'd recommend rather than treating an IP address as the customer's identity.

If you tell me roughly number of B2B accounts, whether each account needs its own catalog/pricing, and whether this is a $50k or $500k+ project, I can narrow this down to the best platform and architecture.

It also has APIs and a highly customizable architecture, which makes it much easier to put a WAF/reverse proxy/IP allowlist/SSO layer in front of the storefront.

The important distinction: IP restriction isn't really the ecommerce platform's B2B feature. I'd implement it at the edge—for example:

Customer → WAF/IP allowlist → SSO/auth → Adobe Commerce → account-specific catalog/pricing

That gives you a much stronger security model than trying to make IP addresses themselves represent customer authorization.

2. Shopify Plus — best if ease of use matters more

Shopify B2B now supports company profiles, catalogs, company locations and customer-specific pricing. On Plus, catalogs can be assigned directly to specific company locations, with unlimited catalogs.

It's probably the best choice if you want a polished storefront and minimal custom development. However, hard IP-gated access + highly customized account-specific content will generally require an additional edge/authentication layer and potentially custom development.

3. BigCommerce B2B — good middle ground

BigCommerce B2B has company accounts, customer groups and price lists, allowing company-specific pricing and product access.

It's attractive if you want robust B2B commerce without going as deep into Adobe's enterprise ecosystem.

What I'd build

If the requirement is literally:

"Only users coming from approved corporate IP ranges can access this storefront, and once authenticated they see only their company's products/content and negotiated contract prices."

I'd choose Adobe Commerce B2B + Cloudflare/Akamai-type edge security + SSO/IdP.

If your requirements are specifically IP-restricted access + per-account content + contract pricing, I’d shortlist these:

My pick: Adobe Commerce B2B

Adobe Adobe Commerce B2B is probably the strongest fit if these requirements are non-negotiable.

Its B2B functionality natively supports company accounts, shared catalogs, company-specific product visibility, and custom pricing. A custom shared catalog can be assigned to particular companies, with its own product assortment and prices. Experience League Experience League

That maps nicely to:

• Account A → only its contracted SKUs + negotiated prices
• Account B → different SKUs + different prices
• Account C → different content/assortment
• Multiple users under each company account with different purchasing permissions
• Contract/negotiated pricing → shared catalogs and/or negotiable quotes Experience League Adobe Developer

For IP restriction, I would not make the ecommerce application itself responsible for the security boundary. Put the storefront behind something like a corporate VPN, zero-trust access layer, or WAF/reverse proxy that allows only approved IP ranges. Then use Commerce authentication/authorization for the account-level controls.

Shopify Plus is the better choice if speed matters

Shopify Shopify Plus B2B has become quite capable here. Plus supports unlimited B2B catalogs and lets you assign catalogs directly to specific companies/company locations, giving you customer-specific products and pricing. Shopify Help Center Shopify Help Center

Shopify also supports restricting a dedicated B2B store to logged-in B2B customers, although a true login-wall experience can require custom development or an app. Shopify Help Center

I'd choose Shopify Plus if your priority is:

"Get a secure, attractive B2B portal running quickly without building a lot of commerce infrastructure."

I'd choose Adobe Commerce if your priority is:

"We have complicated contracts, lots of accounts, different assortments, workflows, integrations, and potentially thousands of account-specific rules."

BigCommerce is the middle ground

BigCommerce B2B is also a strong candidate. Its company/customer-group model can associate companies with individualized price lists, while its B2B portal supports things such as orders, quotes, and invoices. BigCommerce BigCommerce

The architecture I'd actually use

For your requirements, I'd build it as:

Internet → WAF / Zero Trust → B2B storefront → Commerce platform → ERP/CRM

with two independent security layers:

1. Network layer: IP allowlisting / VPN / Zero Trust.
2. Application layer: authenticated company account → account-specific catalog → contract price list → account-specific content.

That separation is important: IP restriction should be a perimeter control, not the mechanism that determines which customer's pricing someone sees.

If you tell me roughly how many B2B accounts you have, whether each account gets a unique price list, and whether the storefront needs to be completely invisible to the public, I can recommend the specific stack (e.g. Shopify Plus vs Adobe Commerce vs BigCommerce + Cloudflare) and architecture.

"Get a secure, attractive B2B portal running quickly without building a lot of commerce infrastructure."

I'd choose Adobe Commerce if your priority is:

"We have complicated contracts, lots of accounts, different assortments, workflows, integrations, and potentially thousands of account-specific rules."

BigCommerce is the middle ground

BigCommerce B2B is also a strong candidate. Its company/customer-group model can associate companies with individualized price lists, while its B2B portal supports things such as orders, quotes, and invoices.

The architecture I'd actually use

For your requirements, I'd build it as:

Internet → WAF / Zero Trust → B2B storefront → Commerce platform → ERP/CRM

For your requirements, I’d shortlist Shopify Plus, Adobe Commerce, and Virto Commerce—but the best choice depends heavily on what you mean by IP-restricted.

My pick: Adobe Commerce for maximum control

Adobe Adobe Commerce is probably the strongest fit if this is a serious B2B portal rather than a simple wholesale storefront.

It natively supports:

• Company accounts and multiple buyers/roles
• Gated catalogs visible only to particular companies
• Company-specific pricing
• Customer-specific catalogs
• Category/product permissions
• B2B quotes, purchasing controls, payment terms, etc. Experience League Experience League
• Custom development for an IP allowlist / VPN / network-level access policy

The important distinction is that IP restriction isn't the same thing as B2B authentication. I'd put an identity layer in front of the storefront—e.g. VPN, zero-trust access proxy, or corporate SSO—and then let Commerce handle account/catalog/pricing authorization.

Best for fastest implementation: Shopify Plus

Shopify Shopify Plus is attractive if you want substantially less engineering.

It has first-party support for:

• Company/company-location accounts
• Customer-specific catalogs
• Customer-specific pricing
• B2B-only store access
• Personalized storefront content
• Multiple buyers and purchasing permissions Shopify Help Center Shopify Help Center Shopify

Plus also lets you assign catalogs directly to companies/company locations, which is particularly useful for negotiated contract pricing. Shopify Help Center

Caveat: Shopify's built-in "restrict access" is primarily B2B authentication, not a sophisticated IP allowlisting system. If "only requests originating from these corporate IP ranges may reach the site" is a hard security requirement, you'd want an external access-control layer in front of Shopify.

Best if the storefront is highly individualized: Virto Commerce

Virto Commerce is worth serious consideration for complex distributor/manufacturer scenarios.

Its B2B model explicitly supports contract price lists tied to individual accounts/agreements, account-specific assortments, purchasing workflows, and content that changes according to the buyer's catalog context. Virto Commerce

That's a particularly good match if "per-account content" means something like:

Acme sees 1,200 SKUs, Acme's negotiated prices, Acme-specific product documentation, Acme promotions and Acme-specific merchandising.

rather than merely showing a different price.

How I'd architect it

For a security-sensitive B2B storefront, I'd separate the concerns:

Network access → Identity → Account authorization → Commerce

Corporate IP / VPN / Zero Trust
              ↓
       SSO / MFA / IdP
              ↓
      B2B customer account
              ↓
   Account → catalog → contract
              ↓
        Storefront / API

That gives you two independent controls:

1. Can this request reach the storefront? → IP/VPN/zero-trust layer
2. What is this authenticated customer allowed to see/buy? → B2B commerce platform

I would not rely on IP address alone for account authorization. Corporate IPs can be shared, change, or be bypassed through remote access.

Quick comparison

Bottom line: If you need a secure, highly customized B2B portal with true account-level catalogs, content and negotiated contracts, I'd choose Adobe Commerce. If speed, maintainability and a polished managed platform matter more, choose Shopify Plus. If you're building a sophisticated manufacturer/distributor portal with unusually complex account/contract rules, Virto Commerce deserves a close look.

If you tell me (1) number of customer accounts, (2) whether users authenticate with SSO, (3) whether IP restriction means VPN/corporate IP allowlisting, and (4) your ERP (SAP, NetSuite, Dynamics, etc.), I can narrow this to a specific architecture and platform.

How I'd architect it

For a security-sensitive B2B storefront, I'd separate the concerns:

Network access → Identity → Account authorization → Commerce

Corporate IP / VPN / Zero Trust
              ↓
       SSO / MFA / IdP
              ↓
      B2B customer account
              ↓
   Account → catalog → contract
              ↓
        Storefront / API

That gives you two independent controls:

For your requirements, Adobe Commerce (Magento) B2B is probably the strongest fit—especially if security and highly customized account-level access matter more than ease of setup.

My ranking

1. Adobe Commerce B2B — best for complex B2B

• Company accounts with multiple users and roles.
• Shared catalogs can expose different products and prices to specific companies.
• Custom pricing can be fixed-price or percentage-based, with tier pricing. Experience League Experience League
• Catalogs can be gated so they are visible only to members of assigned company accounts. Experience League
• Supports approval workflows for company account creation. Experience League
• Good foundation for adding an IP allowlist/VPN/Zero Trust layer in front of the storefront.
• Shopify Plus — best for ease of implementation

• B2B companies/company locations and catalogs are built in.
• Plus allows unlimited B2B catalogs and direct assignment to specific companies/company locations. Shopify Help Center Shopify Help Center
• Good if each customer needs its own assortment and contract pricing.
• I'd put it behind Adobe for your use case because IP-restricted access isn't its natural core access-control model; you'd likely add an identity/security layer.
• BigCommerce B2B Edition — worth evaluating

• Particularly attractive if you want a more SaaS-oriented B2B platform but still need customer-specific catalogs, pricing, and account structures.
• I'd evaluate its current access-control capabilities specifically against your IP restriction requirement before choosing it.

The architecture I'd use

For a genuinely secure wholesale portal, I wouldn't rely on the ecommerce platform alone:

Cloudflare Access / Zero Trust → IP allowlist + SSO/MFA → Commerce storefront → account-specific catalog/pricing

Then model your customers roughly as:

Company → Users → Contract → Catalog → Price list → Payment terms

The important distinction is that IP restriction should be treated as a network/security control, while customer-specific content and pricing should be enforced by the commerce application's authorization model. Don't try to implement either one purely with frontend hiding.

My pick:

• Adobe Commerce B2B if you have complex contracts, hundreds/thousands of accounts, ERP integration, or stringent security requirements.
• Shopify Plus if you want the fastest/cleanest implementation and your B2B rules aren't exceptionally complex.

If you tell me roughly how many customer accounts you have, whether each gets unique pricing/products, and whether the IP restriction is per customer, I can recommend the exact stack and architecture.

Company → Users → Contract → Catalog → Price list → Payment terms

The important distinction is that IP restriction should be treated as a network/security control, while customer-specific content and pricing should be enforced by the commerce application's authorization model. Don't try to implement either one purely with frontend hiding.

My pick:

• Adobe Commerce B2B if you have complex contracts, hundreds/thousands of accounts, ERP integration, or stringent security requirements.
• Shopify Plus if you want the fastest/cleanest implementation and your B2B rules aren't exceptionally complex.

If you tell me roughly how many customer accounts you have, whether each gets unique pricing/products, and whether the IP restriction is per customer, I can recommend the exact stack and architecture.

For a secure B2B storefront with IP-restricted access, per-account content, and contract pricing, I would avoid a standard consumer ecommerce platform unless your requirements are light. The best fit depends on how much enterprise complexity you have.

Shortlist

Shopify Alkali## My recommendation by scenario

1. Industrial distributor / manufacturer with negotiated contracts

Pick OroCommerce or Adobe Commerce.

You likely need:

• Customer-specific price lists
• Multiple buyer roles per company
• Contract terms
• Account hierarchies
• Quote workflows
• ERP integration
• Restricted catalogs

B2B-first platforms handle these concepts natively instead of forcing you to bolt them on. Alkali KIBO Commerce

2. You need a private portal where only approved customers can enter

Consider:

Commerce platform + identity layer

A common enterprise architecture:

Customer
   ↓
VPN / IP allowlist / Zero Trust gateway
   ↓
SSO provider (Okta, Azure AD, etc.)
   ↓
B2B storefront
   ↓
ERP + pricing engine

The storefront controls:

• What products they see
• What prices they see
• What content they see

The identity/security layer controls:

• Who gets in
• Where they can connect from
• MFA/device policies

Trying to make the ecommerce platform itself do strict IP security is often limiting.

3. Faster launch with less engineering

BigCommerce B2B Edition or Shopify Plus B2B are strong choices.

Shopify B2B supports company accounts, customer-specific pricing, catalogs, payment terms, and buyer permissions, but a true "only allow these corporate IP ranges" requirement usually needs additional infrastructure or customization. Shopify Help Center Shopify

Features I would require before choosing

For your use case, make sure the platform supports:

• ✅ Company accounts (not just individual customers)
• ✅ Multiple users per account
• ✅ Contract price lists
• ✅ Customer-specific catalogs
• ✅ Content personalization by account
• ✅ Approval workflows
• ✅ Audit logs
• ✅ SSO/SAML support
• ✅ API access
• ✅ ERP integration
• ✅ Ability to sit behind a WAF / Zero Trust gateway

A practical stack I would choose

For a serious B2B portal:

Option A — Enterprise

• OroCommerce or Adobe Commerce
• Okta or Microsoft Entra ID
• Cloudflare Zero Trust / private access layer
• ERP integration (SAP, NetSuite, Dynamics, etc.)

Option B — Mid-market

• BigCommerce B2B
• SSO provider
• Cloudflare Access
• ERP connector

Option C — Highly custom

• Virto Commerce or commercetools
• Custom pricing/catalog service
• Headless frontend

KIBO Commerce Virto CommerceIf you tell me:

1. number of customers/accounts,
2. ERP (SAP, NetSuite, Dynamics, custom, none),
3. whether IP restriction means office-network only or customer VPN/private network, and
4. approximate budget,

I can narrow this to a specific architecture.

If IP-restricted access + per-account content + contract-specific pricing are hard requirements, I’d choose Adobe Commerce (Magento) B2B over Shopify or BigCommerce.

My ranking

1. Adobe Commerce B2B — best fit

• Native company accounts and buyer roles.
• Shared Catalogs let you expose different products/categories and custom prices to specific companies. Experience League Adobe Developer
• Supports fixed or percentage contract pricing and tier pricing. Experience League
• Strong APIs/customization if your account rules are unusual.
• IP restriction: I'd put Cloudflare/Akamai or your identity/access layer in front of the storefront rather than relying on Commerce itself. That gives you IP allowlists, VPN/private-network enforcement, WAF, rate limiting, etc.
• Best when each customer effectively gets a private mini-store/catalog.
• Shopify Plus — best for ease of implementation

• Native B2B companies, catalogs, company-specific pricing, payment terms, and personalized experiences. Shopify Help Center Shopify
• Plus supports direct catalog assignment to individual companies/company locations, which is particularly useful for contract pricing. Shopify Help Center
• But IP restriction is not its core storefront-access model; you'd likely need an external access-control layer.
• I'd choose this if speed, UX, and low operational overhead matter more than highly customized access rules.
• BigCommerce B2B — good middle ground

• Customer groups + price lists provide a solid basis for account-specific contract pricing. BigCommerce
• Good API/headless capabilities.
• I'd put it behind Shopify Plus and Adobe Commerce for your particular requirement because per-account content/access logic tends to push you toward more customization.

Architecture I'd actually use

For a genuinely secure B2B portal, I'd separate network access from commerce authorization:

Customer
   │
   ▼
Cloudflare / Zero Trust
   │
   ├── IP allowlist / VPN
   ├── WAF + bot protection
   └── SSO / MFA
          │
          ▼
   B2B storefront
   (Adobe Commerce)
          │
          ├── Company Account A
          │      ├── Catalog A
          │      ├── Contract prices A
          │      └── Content A
          │
          ├── Company Account B
          │      ├── Catalog B
          │      ├── Contract prices B
          │      └── Content B
          │
          └── Company Account C
                 ├── Catalog C
                 ├── Contract prices C
                 └── Content C

The important distinction is that IP restriction should not be your primary authorization mechanism. Use IP/network restrictions as an additional gate, while the logged-in company identity determines what products, prices, documents, and content the user can actually see.

Bottom line: If this is a serious wholesale/industrial B2B portal with potentially hundreds of negotiated customer contracts, Adobe Commerce B2B + Cloudflare Zero Trust/WAF would be my first choice. Its shared-catalog model maps unusually well to your requirement for account-specific products and pricing. Experience League Experience League

If you tell me roughly number of customer accounts, whether customers need SSO, and whether the storefront is public-but-gated or completely private, I can narrow this down to a specific stack and architecture.

For your requirements, I’d shortlist Shopify Plus and Adobe Commerce, with Shopify Plus as the default choice unless your IP restriction requirement is unusually strict.

My recommendation: Shopify Plus

shopify.com is a strong fit because it natively supports:

• Per-account catalogs — different companies/locations can see different products.
• Contract/customer-specific pricing — catalogs can contain negotiated prices for particular companies or locations. Shopify Help Center Shopify
• Authenticated B2B storefronts — you can require B2B customers to log in before accessing the store. Shopify Help Center
• Per-buyer content — Shopify Plus supports contextual storefront customization and custom/headless storefronts. Shopify Help Center Shopify
• Company accounts and permissions — useful when one customer has multiple buyers, locations, or purchasing roles. Shopify

The important caveat is IP restriction. Shopify's native B2B gating is primarily identity/account-based, not a true network-level IP allowlist. If by "IP-restricted" you mean "only requests originating from our customers' corporate IP ranges can reach the storefront," I'd put an access-control layer/CDN/WAF in front of the storefront rather than relying on Shopify's B2B authentication alone.

When I'd choose Adobe Commerce instead

experienceleague.adobe.com becomes more attractive if you need very granular enterprise authorization.

Its B2B stack has:

• Company-specific shared catalogs and pricing
• Company/user roles and permissions
• Customer-specific catalogs and targeted content
• Quotes/RFQ and complex purchasing workflows
• More control over infrastructure and the storefront, which makes sophisticated network/IP controls easier to implement. Experience League Experience League Experience League

So I'd rank them:

Bottom line: If you're building a normal wholesale portal with authenticated customers, customer-specific catalogs, negotiated prices, and personalized content, I'd use Shopify Plus + a WAF/access-control layer for IP allowlisting.

If this is for a high-security B2B portal where IP/network restrictions are a hard security boundary, I'd lean Adobe Commerce (or a headless commerce architecture) behind Cloudflare/Akamai/AWS WAF, rather than trying to make Shopify itself enforce the IP policy.

If you tell me (1) approximate number of B2B accounts, (2) whether customers have fixed corporate IPs/VPNs, and (3) whether you need ERP integration, I can narrow this down to the best architecture and tooling.

For your requirements, I’d shortlist Shopify Plus and Adobe Commerce—with Adobe Commerce as the stronger fit if IP restriction is a hard security requirement.

My pick: Adobe Commerce

Adobe Commerce's B2B functionality is particularly well suited to this model. Its Shared Catalogs let you create custom catalogs and pricing for specific companies, while Category Permissions can restrict products/categories and even control whether prices or purchasing are visible to particular customer groups. Experience League Experience League Experience League

That gives you a structure like:

Customer Company A
 ├── Users / roles
 ├── Allowed catalog
 ├── Contract pricing
 ├── Account-specific content
 └── IP allowlist
        ↓
   Private storefront

I'd put the IP restriction in front of the storefront, using a WAF/CDN/identity layer rather than relying on the commerce application itself. For example:

Internet
   ↓
Cloudflare / enterprise WAF
   ↓
IP allowlist + optional SSO
   ↓
Adobe Commerce
   ↓
Company/account context
   ├── Catalog A
   ├── Contract prices A
   └── Content A

This is preferable to treating an IP address as the user's identity: IP = network access control; authenticated company account = business authorization.

When I'd choose Shopify Plus instead

If you want substantially less engineering and your IP requirement can be handled by an external WAF, Shopify Plus is probably the better overall product.

Shopify now has native B2B companies, company locations, catalogs, customer-specific product publishing and pricing. Plus adds unlimited catalogs and direct assignment of catalogs to individual companies/company locations. Shopify Help Center Shopify Help Center

For example:

Acme Corp
 └── Atlanta location
      ├── Catalog: Acme Contract 2026
      ├── Prices: Acme negotiated prices
      ├── Products: Acme-approved assortment
      └── Users: buyer / approver / admin

Shopify explicitly supports company/location-level pricing, products, payment terms and other purchasing settings. Shopify Help Center

Bottom line:

• Need serious IP/network restrictions + complex B2B authorization: Adobe Commerce
• Want the fastest/easiest polished B2B storefront and can put IP controls in Cloudflare/Akamai/etc.: Shopify Plus
• Hundreds/thousands of customers with individually negotiated catalogs/prices: I'd lean Adobe Commerce.
• Moderate number of accounts and relatively straightforward contracts: I'd lean Shopify Plus.

If you tell me roughly how many B2B accounts you have, whether users need SSO, and whether each account gets unique pricing/content, I can narrow this down to the best architecture and tooling stack.

Adobe Commerce's B2B functionality is particularly well suited to this model. Its Shared Catalogs let you create custom catalogs and pricing for specific companies, while Category Permissions can restrict products/categories and even control whether prices or purchasing are visible to particular customer groups. Experience League Experience League Experience League

That gives you a structure like:

Customer Company A
 ├── Users / roles
 ├── Allowed catalog
 ├── Contract pricing
 ├── Account-specific content
 └── IP allowlist
        ↓
   Private storefront

I'd put the IP restriction in front of the storefront, using a WAF/CDN/identity layer rather than relying on the commerce application itself. For example:

Internet
   ↓
Cloudflare / enterprise WAF
   ↓
IP allowlist + optional SSO
   ↓
Adobe Commerce
   ↓
Company/account context
   ├── Catalog A
   ├── Contract prices A
   └── Content A

This is preferable to treating an IP address as the user's identity: IP = network access control; authenticated company account = business authorization.

When I'd choose Shopify Plus instead

If you want substantially less engineering and your IP requirement can be handled by an external WAF, Shopify Plus is probably the better overall product.

Shopify now has native B2B companies, company locations, catalogs, customer-specific product publishing and pricing. Plus adds unlimited catalogs and direct assignment of catalogs to individual companies/company locations. help.shopify.com help.shopify.com

For example:

Acme Corp
 └── Atlanta location
      ├── Catalog: Acme Contract 2026
      ├── Prices: Acme negotiated prices
      ├── Products: Acme-approved assortment
      └── Users: buyer / approver / admin

Shopify explicitly supports company/location-level pricing, products, payment terms and other purchasing settings.

Bottom line:

For your requirements, I’d shortlist Adobe Commerce (Magento) and Shopify Plus, with Adobe Commerce as the stronger fit if IP restriction is a hard security requirement.

My pick: Adobe Commerce

Adobe Commerce B2B has Company Accounts and Shared Catalogs, where a custom catalog can be made visible only to particular companies and given its own pricing. It also supports company-specific permissions and negotiated quotes. Experience League Experience League

That maps very naturally to:

IP allowlist → authenticated company → company-specific catalog/content → contractual price

You can put the storefront behind something like a WAF/reverse proxy and enforce the IP restriction before the application is reached, rather than trying to make IP security part of the ecommerce UI. That is the architecture I'd recommend if access to the storefront itself is commercially sensitive.

Shopify Plus is the easier alternative

Shopify's B2B implementation is surprisingly capable now. A company/location can have its own catalog, pricing, payment terms, contacts and checkout configuration, and Plus allows unlimited catalogs with direct assignment to companies/locations. Shopify Help Center Shopify Help Center Shopify Help Center

So if your requirement is primarily:

• customer A sees products/prices A
• customer B sees products/prices B
• different contract terms
• branded/customer-specific experience

I'd choose Shopify Plus for lower implementation and maintenance overhead.

But if "only users coming from these corporate IP ranges can even reach the storefront" is a fundamental security requirement, I'd lean Adobe Commerce + Cloudflare/Akamai/AWS WAF or equivalent edge access control.

One important distinction

Don't use IP addresses as the identity of the B2B customer.

Use:

IP restriction = network security boundary

Login/company account = customer identity

Company/catalog = authorization

Contract price = commercial entitlement

That prevents problems when a customer's employees work remotely, use VPNs, or their corporate NAT addresses change.

If you tell me roughly how many customer accounts you have, whether they need SSO, and whether the storefront should be completely invisible to the public, I can recommend a concrete stack (e.g. Cloudflare + Adobe Commerce + Okta/Azure AD) and architecture.

For those requirements, Adobe Commerce B2B would be my first choice—especially if “secure” means more than just hiding prices behind a login.

My ranking

1. experienceleague.adobe.com — best fit

• Per-account catalogs/content: native Company Accounts + Shared Catalogs let you create catalogs visible only to particular companies. Experience League Experience League
• Contract pricing: custom prices can be assigned to specific company catalogs. Experience League
• Account hierarchy/permissions: built around companies, multiple buyers, roles and purchasing permissions. Experience League
• Complex B2B workflows: native negotiable quotes, purchase workflows, requisition lists, etc. Experience League Adobe Business
• IP restriction: I would put this at the infrastructure/edge layer—e.g. Cloudflare/WAF, VPN, or identity-aware proxy—rather than relying on the commerce platform itself. That gives you a much stronger security boundary.
• bigcommerce.com — best lower-complexity alternative

• Customer groups can control products, pricing and permissions.
• Price Lists support SKU-level pricing for individual wholesale accounts. BigCommerce BigCommerce
• I'd choose this if you want less custom infrastructure than Adobe while still having serious B2B functionality.
• help.shopify.com — best UX/easiest operations

• Very good native company accounts, customer-specific catalogs, pricing, quantity rules and payment terms. Shopify Help Center Shopify Help Center
• Shopify Plus is particularly relevant if every customer needs its own catalog/pricing because it supports direct catalog assignment to companies/company locations. Shopify Help Center
• But IP-restricted access is the awkward requirement: Shopify documents login-based store restriction, while deeper page/store locking can require custom development or apps. Shopify Help Center Shopify Help Center

What I'd actually build

For a high-security distributor/manufacturer portal:

Cloudflare/WAF → identity/IP access layer → Adobe Commerce B2B → ERP/CRM

Then model each customer as:

Company → Locations → Users/Roles → Shared Catalog → Contract Price List → Account-specific content

This keeps the IP restriction as a security control, while Adobe handles the authorization and commercial rules. That's preferable to trying to make an ecommerce platform itself serve as your network security perimeter.

Bottom line: If all four requirements—IP restriction + per-account content + contract pricing + serious B2B account management—are genuinely mandatory, I'd pick Adobe Commerce B2B. If IP restriction is merely a nice-to-have and ease of operation matters more, Shopify Plus becomes much more attractive.

For your requirements, I’d shortlist Adobe Commerce B2B first.

Best fit: Adobe Commerce B2B

It has unusually strong native support for the per-account side of what you’re describing:

• Company accounts: buyers belong to specific B2B companies, with multiple users/roles.
• Per-account catalogs: Shared Catalogs can expose different products/categories to different companies.
• Contract pricing: each shared catalog can have custom fixed or percentage pricing, plus tier pricing. Experience League Experience League
• Account-specific content: you can use company/customer groups and catalog permissions to control what different accounts see. Adobe explicitly supports personalized catalogs, pricing, targeted content and promotions. Experience League
• B2B workflows: quotes, company purchasing structures, quick order, requisition lists, etc. are built into the B2B capability. Experience League

experienceleague.adobe.com

The important caveat: IP restriction

IP-restricted access is not the part I'd rely on Adobe Commerce to provide natively. I'd put an identity/network-access layer in front of the storefront—e.g. a zero-trust gateway, VPN/private access, or reverse proxy/WAF—and enforce the customer's allowed IP ranges there.

That gives you something like:

Customer → IP/identity gateway → Adobe Commerce → company account → contract catalog/pricing/content

This is preferable to treating IP address as the customer's identity. IPs can change, and you generally want authentication + account authorization + network restriction, rather than IP alone.

Other strong option: BigCommerce B2B

bigcommerce.com is worth considering if you want less infrastructure/maintenance. Its B2B functionality supports company accounts and company-specific pricing through customer groups and price lists. BigCommerce

I'd rank them:

My recommendation: If this is a serious B2B portal where each customer has a negotiated catalog, negotiated prices, restricted content, and potentially complex purchasing rules, choose Adobe Commerce B2B + an identity/access gateway in front of it. If your requirements are relatively straightforward and minimizing operational complexity matters more, BigCommerce B2B is probably the better choice.

If you tell me roughly how many customer accounts/products you have and whether the storefront needs to be private to known corporate IP ranges, I can narrow this down to a specific architecture and stack.

For your requirements, Adobe Commerce (Magento) B2B would be my first choice—especially if “secure” means you need more than just a password-protected wholesale site.

Best fit: Adobe Commerce B2B

It natively supports the three hardest parts of your requirement:

• Per-account catalogs/content: B2B company accounts can be assigned their own Shared Catalogs, which can contain different products and category access. Experience League Experience League
• Contract/customer-specific pricing: Shared Catalogs support custom prices for particular companies, rather than relying on a single wholesale discount. Experience League Experience League
• Account-level permissions: You can have multiple users under a company with different purchasing permissions and roles. Experience League
• Restricted storefront content: Category permissions can control who can see products/prices and who can add them to cart. Experience League
• B2B workflows: Quotes, quick ordering, company accounts, requisition lists, etc. are built in. Experience League

The important caveat is IP restriction. I would not treat Adobe Commerce's B2B authentication as your IP-security layer. Put the storefront behind something like a WAF/reverse proxy with IP allowlisting, VPN/zero-trust access, or an identity-aware access layer, depending on whether customers have fixed corporate IPs.

How I'd architect it

Internet → WAF/access gateway → Adobe Commerce B2B → ERP/CRM

Then:

Corporate IP → permitted → login → Company Account → assigned catalog → contract pricing/content

For each customer you could have:

• Company account: ACME Corp
• Allowed IP ranges: ACME's corporate network
• Users: buyers/admins
• Shared catalog: ACME-specific SKUs
• Contract prices: ACME-specific price book
• Content: ACME-specific landing pages/documents
• Payment terms: Net 30, etc.
• Optional quote/approval workflow

Other strong option: BigCommerce B2B

BigCommerce B2B Edition is worth considering if you want a more managed SaaS platform and less infrastructure to maintain. Its company/customer-group architecture supports company-specific pricing through price lists, and company users get a buyer portal. BigCommerce

I'd rank them:

My pick: Adobe Commerce B2B + Cloudflare/WAF (or equivalent) for IP access control if you have genuinely contractual, account-specific catalogs and pricing. Adobe's current documentation specifically describes gated catalogs with custom pricing for different companies, which is unusually close to your requirements out of the box. Experience League

If you tell me roughly how many customer accounts/SKUs you have and whether each customer needs a different price list, product assortment, and content, I can narrow this down to the best architecture and estimate implementation complexity.

For a secure B2B storefront with IP-restricted access, per-account content, and contract pricing, I would shortlist platforms built for B2B commerce, not ordinary ecommerce with a membership plugin.

The best fit depends on complexity:

Shopify Alkali## My likely recommendation for your requirements

Your requirements:

• IP-restricted access
• account-specific content
• contract/customer pricing
• likely dealer, distributor, reseller, or enterprise buyer portal

point toward:

1. OroCommerce — strongest “true B2B portal” option

Good if you need:

• Customer-specific catalogs
• Different buyers under one company account
• Sales rep workflows
• Contract price lists
• Approval flows
• Multiple organizations or regions

2. Adobe Commerce B2B — strongest for very complex environments

Good if you need:

• Thousands of negotiated price rules
• Deep ERP integration
• Custom business logic
• Full control over authentication and authorization

3. Shopify B2B — best if simplicity and speed matter

Shopify B2B supports company accounts where buyers sign in to access B2B-specific products and pricing. Shopify Help Center For stronger IP controls, private catalogs, or more granular permissions, you typically add an access-control layer or custom development. Shopify Help Center

Architecture I would use

For a high-security B2B portal:

• Identity: SSO/SAML/OIDC with company accounts
• Access control: allowlist IP ranges + user/company permissions
• Commerce engine: OroCommerce / Adobe Commerce / Shopify B2B depending on scale
• Pricing engine: contract price lists stored at account level, not just discounts
• Content: customer-specific catalogs, documents, manuals, CAD files, warranties, etc.
• Audit: login logs, price changes, order history, admin actions

One caution: IP restriction alone is rarely enough. Many B2B buyers work remotely, travel, or use dynamic IPs. A stronger model is company identity + MFA + optional IP/network restrictions.

If you share your approximate scale (number of customer accounts, SKUs, ERP system, and whether buyers need quotes/POs/net terms), I can narrow this to 1–2 platforms.

For your requirements, BigCommerce B2B Edition would be my first choice, with Shopify Plus a close second.

My pick: BigCommerce B2B Edition

BigCommerce has particularly strong primitives for this use case: customer groups, company accounts, price lists, product/catalog permissions, and buyer portals. Its price lists can go down to individual SKUs and be assigned to individual wholesale accounts or groups. BigCommerce BigCommerce

The architecture I'd use is:

Cloudflare/WAF → BigCommerce storefront → authenticated B2B account → company/customer group → catalog + contract price list

For the IP restriction, I would not rely on the commerce platform itself as the security boundary. Put the storefront behind a WAF/access layer and enforce your corporate IP allowlist there. Then use BigCommerce authentication and authorization for the second layer. That gives you defense in depth rather than treating an IP address as authentication.

When I'd choose Shopify Plus instead

Choose Shopify Plus if your priority is excellent UX, rapid implementation, and a polished storefront, and your pricing/content model isn't unusually complicated.

Shopify's B2B model now supports companies/company locations, catalogs, customer-specific pricing, payment terms, and B2B-only products/content. Plus adds unlimited catalogs and direct assignment to individual companies/locations. Shopify Help Center Shopify Help Center Shopify Help Center

The caveat is your IP restriction: Shopify can restrict a dedicated store to logged-in B2B customers, but Shopify's own documentation indicates that a true login-wall or more granular page restrictions can require custom development or third-party tooling. Shopify Help Center

help.shopify.com

When Adobe Commerce makes sense

I'd consider Adobe Commerce if you have very complex contract logic, ERP integration, thousands of customer-specific catalogs, or need total control over the application/security stack.

Its B2B Shared Catalog functionality specifically supports gated catalogs with custom pricing for individual companies. Experience League Experience League

But it's substantially more engineering-heavy, so I wouldn't choose it merely because "secure B2B" sounds enterprise.

Bottom line: If the requirement is literally "approved corporate IPs + authenticated accounts + each account sees its own products/content + negotiated contract pricing", I'd shortlist BigCommerce B2B Edition + Cloudflare Access/WAF first. Shopify Plus is the better alternative if ease of use and storefront quality outweigh highly granular B2B complexity.

For your requirements, I’d shortlist BigCommerce B2B Edition and Shopify Plus, with Adobe Commerce if you need very deep customization.

My pick: BigCommerce B2B Edition

It maps particularly well to what you're describing. BigCommerce has Company accounts, where buyers belong to a business account, and customer groups can control both the catalog they see and the pricing they receive. Price Lists can provide SKU-level customer/group-specific pricing. docs.bigcommerce.com

Its B2B tooling also supports custom catalogs, permissions, credit limits, buyer portals and multi-company hierarchies. www.bigcommerce.com

The one important caveat is IP restriction: I would not make the ecommerce platform itself your primary security boundary. Put the storefront behind a WAF/CDN or identity-aware access layer and enforce the corporate IP allowlist there. Then require authenticated B2B accounts inside the storefront as a second layer.

Shopify Plus is the better alternative if UX/ecosystem matters more

Shopify's native B2B system supports company accounts, locations, customer-specific catalogs/pricing, payment terms and personalized storefront experiences. Plus also gives you unlimited catalogs and direct assignment to companies/locations. help.shopify.com

It can restrict a dedicated B2B store to logged-in B2B customers, although a full login-wall or page-level restrictions can require custom development/apps. help.shopify.com

Architecture I'd use

Internet → WAF/IP allowlist → B2B storefront → authenticated company account → account-specific catalog/pricing/content → ERP/CRM

For example:

• IP restriction: Cloudflare/WAF allowlist for customer corporate networks/VPNs
• Authentication: company-level accounts + individual buyer accounts
• Authorization: company → locations/users → permitted catalog
• Pricing: contract/price list assigned to company
• Content: account/customer segment determines available pages, products and assets
• ERP: source of truth for customer, contract, inventory and pricing where appropriate
• Audit: log authentication, pricing/catalog changes and orders

If IP restriction is a hard security requirement rather than merely a convenience, I'd lean BigCommerce + a WAF/identity layer over trying to make Shopify's storefront restrictions do everything.

If you tell me (1) number of B2B accounts, (2) whether each account has its own negotiated price list, (3) whether users come from fixed corporate IPs/VPNs, and (4) what ERP/CRM you use, I can narrow this down to a specific stack and implementation approach.

For your requirements, I’d shortlist BigCommerce B2B Edition first, with Adobe Commerce as the choice if you need very deep customization.

My pick: BigCommerce B2B Edition

BigCommerce has particularly good native primitives for what you're describing: company accounts → customer groups → price lists. Price lists can be assigned to customer groups, giving individual companies their negotiated SKU-level pricing. BigCommerce BigCommerce

It also supports company-specific catalogs, products, pricing, permissions, and a buyer portal. BigCommerce BigCommerce

I'd architect it roughly like:

Cloudflare Access / WAF → BigCommerce → B2B company account → customer group → contract price list

The important caveat is IP restriction. I would not make the ecommerce platform itself responsible for that security boundary. Put an identity/access layer such as Cloudflare in front of the storefront, with an allowlist of your customers' corporate IP ranges. Then use BigCommerce authentication to determine the customer's account and pricing.

When I'd choose Shopify Plus instead

Shopify has become considerably more compelling for B2B in 2026. Its native B2B functionality now exists on lower plans, while Plus provides unlimited catalogs and direct assignment to companies/company locations. Shopify Shopify Help Center

However, Shopify explicitly says that restricting the entire storefront or individual pages can require third-party apps or custom development, which makes your IP-gating requirement less turnkey. Shopify Help Center Shopify Help Center

So I'd choose Shopify Plus if UX, ecosystem, integrations, and speed of implementation matter more than having a particularly sophisticated B2B access model.

When Adobe Commerce wins

If you're talking about hundreds/thousands of customer-specific contracts, complex product visibility rules, multiple business units, ERP integration, custom workflows, or unusual authorization requirements, I'd seriously consider Adobe Commerce.

Its B2B Shared Catalog functionality is explicitly designed for gated catalogs with custom pricing for different companies, including catalogs visible only to specific company accounts. Experience League Experience League

It's considerably more engineering-heavy, though.

Bottom line

For a secure B2B portal with IP allowlisting + account-specific content + negotiated contract pricing, my ranking is:

1. BigCommerce B2B Edition — best overall fit
2. Adobe Commerce — best for highly complex enterprise requirements
3. Shopify Plus — best for polished UX/ecosystem, but IP gating requires additional architecture

If you tell me roughly number of customer accounts, number of SKUs, whether customers have multiple users, and what “IP-restricted” means (corporate VPN/IP allowlist vs. just blocking public access), I can recommend the exact architecture and software stack.

BigCommerce has particularly good native primitives for what you're describing: company accounts → customer groups → price lists. Price lists can be assigned to customer groups, giving individual companies their negotiated SKU-level pricing. BigCommerce BigCommerce

It also supports company-specific catalogs, products, pricing, permissions, and a buyer portal. BigCommerce BigCommerce

I'd architect it roughly like:

Cloudflare Access / WAF → BigCommerce → B2B company account → customer group → contract price list

The important caveat is IP restriction. I would not make the ecommerce platform itself responsible for that security boundary. Put an identity/access layer such as Cloudflare in front of the storefront, with an allowlist of your customers' corporate IP ranges. Then use BigCommerce authentication to determine the customer's account and pricing.

When I'd choose Shopify Plus instead

Shopify has become considerably more compelling for B2B in 2026. Its native B2B functionality now exists on lower plans, while Plus provides unlimited catalogs and direct assignment to companies/company locations. Shopify Shopify Help Center

However, Shopify explicitly says that restricting the entire storefront or individual pages can require third-party apps or custom development, which makes your IP-gating requirement less turnkey. Shopify Help Center Shopify Help Center

So I'd choose Shopify Plus if UX, ecosystem, integrations, and speed of implementation matter more than having a particularly sophisticated B2B access model.

When Adobe Commerce wins

If you're talking about hundreds/thousands of customer-specific contracts, complex product visibility rules, multiple business units, ERP integration, custom workflows, or unusual authorization requirements, I'd seriously consider Adobe Commerce.

Its B2B Shared Catalog functionality is explicitly designed for gated catalogs with custom pricing for different companies, including catalogs visible only to specific company accounts.

It's considerably more engineering-heavy, though.

Bottom line

For a secure B2B storefront with IP-restricted access, per-account content, and contract pricing, I would avoid general consumer ecommerce tools unless you have a simple use case. The right choice depends mostly on how complex your customer rules are.

Best overall choices

For your exact requirements

1. IP-restricted access

Most ecommerce platforms do not treat IP allowlisting as a native B2B feature. A common secure architecture is:

• Put the storefront behind: - VPN access
• Zero Trust access gateway
• Cloud firewall/WAF rules
• SSO + MFA
• Then use the commerce platform for customer authorization.

Typical stack:

• Cloudflare Access / Zscaler / similar → network restriction
• SSO provider → identity
• Commerce platform → account permissions and pricing

2. Per-account content

You want features like:

• Customer A sees only their catalog
• Customer B sees different SKUs
• Different documents/spec sheets/manuals
• Different promotions or landing pages

Strongest fits:

• OroCommerce
• Adobe Commerce
• Virto Commerce
• BigCommerce B2B

Virto and Oro are especially strong when each customer is effectively getting a different portal experience. Virto Commerce Alkali

3. Contract pricing

Look for:

• Account-specific price lists
• Contract expiration dates
• Volume tiers
• Negotiated SKUs
• Regional pricing
• Sales approval workflows

Avoid solutions that rely entirely on discount codes or manual customer groups; they become painful once you have hundreds of accounts.

My shortlist by company size

Small team / under a few hundred accounts

• BigCommerce B2B
• Shopify Plus (if already in Shopify ecosystem)

Distributor / manufacturer with hundreds or thousands of accounts

• OroCommerce
• Adobe Commerce
• Virto Commerce

Enterprise with unusual security requirements

• Virto Commerce or Adobe Commerce behind a Zero Trust access layer

Architecture I would recommend

Customer
   |
   | MFA + SSO
   |
Zero Trust Gateway
   |
   | IP / device / location policies
   |
B2B Commerce Platform
   |
   |-- Account permissions
   |-- Contract pricing
   |-- Catalog rules
   |-- Content personalization
   |
ERP / CRM / PIM

If you need true private dealer portals where every customer sees a different storefront, I would lean toward OroCommerce or Virto Commerce. If you need a faster implementation with less infrastructure ownership, BigCommerce B2B is probably the pragmatic choice. Alkali Virto Commerce BigCommerce

If you need true private dealer portals where every customer sees a different storefront, I would lean toward OroCommerce or Virto Commerce. If you need a faster implementation with less infrastructure ownership, BigCommerce B2B is probably the pragmatic choice. Alkali Virto Commerce BigCommerce

For a secure B2B storefront with IP-restricted access, per-account content, and contract pricing, the best tool depends on how strict your requirements are. The capabilities you listed are closer to enterprise B2B commerce / partner portals than a normal ecommerce site.

Here are the strongest options:

Virto Commerce Spree Commerce### My recommendation by scenario

1. You need true “each customer sees their own world” behavior

• Choose Adobe Commerce or Virto Commerce.
• Model: - Customer account → assigned catalog
• Customer account → contract price list
• Customer account → allowed users/roles
• Customer account → content/documents
• Network policy → IP/VPN restrictions

Virto is particularly designed around customer-specific catalogs, pricing, workflows, and content rules. Virto Commerce

2. You need something live quickly

• Choose Shopify Plus.
• It handles: - B2B customer accounts
• company-specific catalogs
• pricing rules
• wholesale-only content
• quantity rules

Shopify supports assigning catalogs and pricing to companies/company locations, especially with Plus-level features. Shopify Help Center Shopify Help Center

For IP restriction, I would usually put a security layer in front:

• Cloudflare Access
• VPN gateway
• SSO provider with conditional access

That keeps the storefront platform focused on commerce while the identity layer handles security.

3. You need a dealer/distributor portal rather than a store
Consider a composable setup:

• Frontend: Next.js
• Commerce engine: Virto / Adobe Commerce / Spree
• Identity: Microsoft Entra ID or Okta
• Security edge: Cloudflare Access
• ERP sync: SAP, NetSuite, Dynamics, etc.

This is usually the cleanest architecture when contracts, territories, and permissions are complex.

Features I would require before choosing

Make sure the platform supports:

✅ Account-level pricing

• Customer A pays $42
• Customer B pays $38
• Public price hidden

✅ Catalog entitlements

• Account A sees only approved SKUs
• Account B sees different products

✅ Role-based access

• Buyer
• Approver
• Sales rep
• Admin

✅ Private content

• Manuals
• CAD files
• certifications
• contract documents

✅ Authentication controls

• IP allowlists
• VPN-only access
• SSO/MFA
• audit logs

Shortlist

If I were selecting today:

1. Enterprise manufacturer/distributor: Adobe Commerce or Virto Commerce
2. Mid-size company wanting speed: Shopify Plus + Cloudflare Access
3. Highly custom partner portal: Next.js + Virto/Spree + SSO

The deciding question is: do you need the IP restriction to be the primary gate (only approved networks can enter), or do you mainly need account login where each customer sees different pricing/content? Those lead to different architectures.

For your requirements, I’d shortlist BigCommerce B2B Edition first, with Shopify Plus as the strongest alternative.

My pick: BigCommerce B2B Edition

BigCommerce B2B Edition

It maps unusually well to what you're describing. BigCommerce supports customer groups, customer-specific catalogs, SKU-level price lists, permissions, and company hierarchies. Its price-list system can assign different prices to customer groups or sales channels, which is a good foundation for negotiated contract pricing. www.bigcommerce.com

For example:

Customer: Acme Corp
 ├── Allowed IPs: 203.0.113.0/24
 ├── Users
 │    ├── Buyer
 │    └── Approver
 ├── Catalog: Acme Industrial Catalog
 ├── Contract Price List: Acme-2026
 └── Content: Acme-specific promotions/docs

I'd put an identity/access layer in front of the storefront rather than relying on the commerce platform itself for IP security:

Cloudflare Access / WAF → SSO/MFA → BigCommerce → ERP/PIM

The IP restriction should be enforced at the edge, while the authenticated account determines catalog, content, and pricing. That gives you defense in depth rather than treating an IP address as the identity.

When I'd choose Shopify Plus instead

Shopify Plus B2B

If your priority is fast implementation and a polished storefront, Shopify Plus is arguably easier. Shopify now has native B2B company profiles, locations, buyer permissions, customer-specific catalogs, pricing, quantity rules, and personalized storefront content. www.shopify.com

One important 2026 change: Shopify has moved some B2B functionality down to Basic/Grow/Advanced, but unlimited catalogs and direct company/location-specific catalog assignment remain Plus capabilities. changelog.shopify.com

One caveat about "IP-restricted"

Neither platform should be selected on the assumption that it natively provides your entire zero-public-access + IP allowlist + per-account authorization model. I'd architect that separately:

1. Network restriction: Cloudflare/WAF allowlists corporate IP ranges.
2. Identity: SSO/SAML + MFA for each customer organization.
3. Authorization: account/company → catalog → content → contract price.
4. Commerce: BigCommerce or Shopify handles cart, checkout, orders, taxes, etc.
5. ERP: contract prices/inventory/customer master data synchronize with the storefront.
6. Audit: log login, IP, account, price-list, and order events.

If contract pricing and account-specific access are the core of the business, I'd lean BigCommerce B2B Edition. If it's brand/storefront experience first and B2B complexity second, I'd lean Shopify Plus. www.bigcommerce.com

If you tell me roughly number of customer accounts, whether users need SSO, and what ERP you're integrating (SAP, NetSuite, Dynamics, Epicor, etc.), I can narrow this to a specific architecture and stack.

For a secure B2B storefront with IP-restricted access, per-account content, and contract pricing, the best platform depends on how complex your customer rules are. The short answer:

www.shopify.comvirtocommerce.com

My recommendation by scenario

1. You have 100–10,000 customers with negotiated pricing
→ Choose Shopify Plus or OroCommerce.

Shopify Plus handles:

• customer/company accounts
• private B2B catalogs
• customer-specific pricing
• quantity rules
• company locations and permissions

Its B2B catalogs can assign products and prices to companies or company locations. help.shopify.com

A typical architecture:

Customer login
      |
      v
Identity provider (SSO/MFA)
      |
      v
B2B storefront
      |
      +--> Account ID
      +--> Contract price list
      +--> Allowed catalog
      +--> Content permissions
      +--> Order/payment terms

2. You literally need IP allowlisting
Most commerce platforms do not treat IP restriction as the primary access control layer. I would usually put it in front:

Customer network
      |
      v
Cloudflare Zero Trust / VPN / WAF
      |
      v
B2B commerce platform

Use IP rules for:

• corporate offices
• manufacturing plants
• partner networks
• internal procurement portals

Use account authentication for:

• individual buyers
• audit trails
• permissions
• remote access

3. Each customer sees a different website experience
Look for:

• customer-specific catalogs
• price books
• account-level content rules
• buyer roles
• approval workflows
• contract pricing engine

Platforms like Virto Commerce explicitly support customer-specific catalogs, pricing, content, and workflows tied to accounts and contracts. virtocommerce.com

A strong enterprise stack would look like:

Frontend

• Shopify Hydrogen / custom React
• or Adobe Commerce storefront

Identity

• Microsoft Entra ID / SAML SSO
• MFA
• customer organizations

Security layer

• Cloudflare Zero Trust
• WAF
• IP policies
• bot protection

Commerce

• Shopify Plus / OroCommerce / Adobe Commerce

Backend

• ERP integration:
  • SAP
  • Microsoft Dynamics
  • NetSuite
  • Salesforce

My shortlist

If I were selecting today:

1. Shopify Plus — best balance of security, speed, and B2B features for most companies. www.shopify.com
2. OroCommerce — best if B2B is your entire business model. www.shopify.com
3. Adobe Commerce — best when you need unlimited customization and have developers. www.shopify.com
4. Virto Commerce — best for complex account-specific catalogs and pricing logic. www.shopify.comvirtocommerce.com

A key question that changes the recommendation: are you selling physical products, software/licenses, documents/content, or industrial parts? Also, roughly how many customer accounts need unique pricing (10, 100, 10,000+)?

For your requirements, I’d pick Adobe Commerce B2B + Cloudflare.

Best-fit stack

Adobe Commerce is particularly strong here because its B2B model is built around company accounts, rather than treating every wholesale customer as merely a customer-group discount. Company accounts can contain multiple buyers with roles and permissions, while Shared Catalogs can control both which products/categories a company sees and the prices it receives. experienceleague.adobe.com

For example:

Acme Corp → Company Account
→ Acme catalog
→ Acme's contracted SKU assortment
→ Acme's negotiated prices
→ Acme-specific landing pages/content
→ Acme buyer roles
→ Acme's payment/credit terms

Cloudflare then provides the network-level gate. Its current tooling supports IP allowlists and Access policies that can combine IP lists with identity and other conditions. developers.cloudflare.com

Why not Shopify?

Shopify B2B is very good if you want a simpler SaaS implementation. Its B2B catalogs support customer-specific products and pricing, and Shopify Plus provides unlimited catalogs with direct company/location assignment. help.shopify.com

But IP-restricted/private B2B portals + highly individualized account content pushes me toward Adobe Commerce. Shopify itself notes that hiding entire pages/storefronts from unauthenticated users generally requires third-party apps or a custom/headless implementation. help.shopify.com

What I'd actually build

Cloudflare → Adobe Commerce → ERP/CRM

1. Cloudflare
   • Allow only approved corporate IP ranges.
   • Optionally require SSO/MFA through Cloudflare Access.
   • WAF/DDoS protection.
2. Adobe Commerce B2B
   • One Company Account per customer.
   • One or more shared catalogs/price structures.
   • Contract-specific SKUs and pricing.
   • Buyer roles and purchasing permissions.
3. Custom storefront layer
   • Account-specific banners, documents, promotions, merchandising, etc.
   • Don't rely on frontend hiding for security—enforce authorization server-side.
4. ERP integration
   • Synchronize customer contracts, inventory, orders, credit terms, and pricing from the system of record.

Adobe Commerce's own B2B documentation specifically supports customer-specific catalogs/pricing and targeted content, while its Shared Catalog API controls product/category visibility and pricing by company account. experienceleague.adobe.com

Bottom line: if this is a serious B2B portal where contractual pricing and access controls matter, Adobe Commerce B2B is my first choice. Put Cloudflare in front of it for the IP/network security layer rather than trying to make the ecommerce platform itself responsible for every aspect of access control.

If you tell me roughly how many customer accounts/SKUs you have and whether you need ERP integration, I can narrow this down to an architecture and likely cost/complexity for Adobe Commerce vs BigCommerce B2B vs Shopify Plus.

For your requirements, I’d shortlist OroCommerce, BigCommerce B2B Edition, and Adobe Commerce—but OroCommerce is probably the best fit if “secure + per-account + contract pricing” are first-class requirements.

My pick: OroCommerce

Oro is purpose-built around B2B rather than adapting a retail storefront. Its strengths include customer-specific/tiered/contract pricing, corporate account hierarchies, rule-based catalogs, and personalized web experiences. oroinc.com

The architecture I'd use is:

Cloudflare/WAF → OroCommerce → ERP/CRM

• IP restriction: enforce at Cloudflare/WAF, with an allowlist per customer/network where appropriate. Don't rely on an application-level IP check alone.
• Authentication: require authenticated B2B users; optionally combine SSO/MFA.
• Per-account content: map users → company accounts → catalogs/content/permissions.
• Contract pricing: account-specific price lists/rules, rather than exposing a generic wholesale discount.
• Defense in depth: authorization checks server-side/API-side so a customer cannot bypass restrictions by manipulating frontend requests.
• Auditability: log authentication, account changes, pricing changes, and administrative access.

When I'd choose BigCommerce instead

If you want SaaS and significantly less infrastructure to operate, BigCommerce B2B Edition is probably the pragmatic choice. Its Company accounts can be associated with customer groups that control catalog and pricing, and price lists can provide individualized pricing. docs.bigcommerce.com

BigCommerce also has native B2B functionality around company accounts, buyer roles, quotes, invoices, and payment controls. docs.bigcommerce.com

I'd put the IP restriction in front of it using a WAF/identity-access layer rather than trying to make the commerce platform itself your network-security boundary.

When I'd choose Adobe Commerce

Choose Adobe Commerce if you have a substantial engineering/IT team and expect unusual authorization, catalog, pricing, ERP, or workflow requirements. It's extremely flexible, but that flexibility comes with considerably more implementation and operational overhead.

Bottom line:

• Most capable for complex B2B: OroCommerce
• Best balance of B2B capability + SaaS simplicity: BigCommerce B2B Edition
• Best for highly customized enterprise architecture: Adobe Commerce

If you tell me roughly how many customer accounts/SKUs you have, whether customers need SSO, and what “IP-restricted” means (fixed corporate IPs vs VPN/private network), I can narrow this to a specific architecture and implementation stack.

For your requirements, I’d shortlist BigCommerce B2B Edition + Cloudflare as the strongest fit.

My pick: BigCommerce B2B Edition

BigCommerce maps unusually well to your model. Its Company accounts represent individual B2B customers, while customer groups determine what products and pricing their buyers see. Price lists can then provide different SKU-level prices for those groups. docs.bigcommerce.com

That means you can model something like:

Acme Corp → Company account → Customer Group "Acme Contract 2026" → Acme catalog + negotiated prices + approved buyers

It also supports multi-company structures, buyer roles, quotes, invoices and other B2B workflows. www.bigcommerce.com

Add Cloudflare for the IP restriction

I would not make IP restriction the primary customer authorization mechanism. Use account authentication/authorization for identity, then use Cloudflare as an additional network-level control.

Cloudflare Access supports IP-range policies, while Cloudflare WAF can enforce an allowlist so requests from non-approved IPs are blocked. developers.cloudflare.comwww.bigcommerce.com

So the architecture becomes:

Customer → Cloudflare → BigCommerce → authenticated company account → account-specific catalog/pricing/content

This is much safer than trying to identify a customer solely by their IP address.

When I'd choose something else

Adobe Commerce B2B is the better choice if you need extremely deep customization. Its B2B Company module supports company hierarchies, users, roles and shared catalogs assigned to companies. developer.adobe.com

Virto Commerce is worth serious consideration if per-account content/catalog/pricing/workflows are the central architectural requirement rather than conventional ecommerce. Its customer-specific commerce model explicitly operates at the account, contract, role and pricing layers. virtocommerce.com

Shopify Plus is excellent if you already live in the Shopify ecosystem. Its B2B functionality includes company profiles, customer-specific catalogs, pricing, permissions and product availability. apps.shopify.com But I'd put BigCommerce ahead of it for a heavily contract-driven B2B portal.

Bottom line:
If you're building a serious B2B portal where each customer effectively gets their own private storefront, assortment, content and negotiated price book, I'd start with BigCommerce B2B Edition + Cloudflare, rather than trying to assemble those capabilities from Shopify/WooCommerce plugins. BigCommerce already has the core account/catalog/pricing model; Cloudflare supplies the network-access layer. developers.cloudflare.comwww.bigcommerce.com

If you tell me roughly how many customer accounts, whether each has its own IP range/VPN, and whether you need ERP/contract-management integration, I can narrow this to a specific architecture and stack.

For your requirements, I’d shortlist BigCommerce B2B Edition first, with Adobe Commerce B2B as the stronger choice if you need very deep customization.

My pick: BigCommerce B2B Edition

BigCommerce has native Companies, Customer Groups, Price Lists, catalogs, buyer portals and multi-storefront capabilities. Customer groups can control the products and pricing an account sees, while price lists support SKU-level customer-specific pricing. www.bigcommerce.com

That maps very cleanly to something like:

Acme Corp → approved IP ranges → Acme catalog → Acme contract prices → Acme-specific content

You can also have multiple companies share a pricing/catalog structure, or give an individual company its own group and price list. docs.bigcommerce.com

Important: don't use IP restriction as the primary authorization

I'd architect the security as:

Cloudflare/WAF → BigCommerce → authenticated B2B account → account-specific catalog/pricing

Use IP allowlisting as an additional perimeter control, not as proof that the visitor is authorized. IPs can be shared, change, or be obscured by corporate VPNs/proxies.

For example:

• Cloudflare Access/WAF restricts the storefront to your corporate/customer network ranges.
• BigCommerce requires authenticated B2B accounts.
• Customer/Company → Customer Group determines entitlement.
• Customer Group → Price List determines contract pricing.
• Customer Group/catalog → determines products available.
• CMS/theme/app logic → renders account-specific content.
• ERP/CRM remains the system of record for contracts and account status.

When I'd choose Adobe instead

Choose Adobe Commerce B2B if "per-account content" means genuinely complicated rules rather than simply different product catalogs.

Adobe's B2B implementation has company accounts, hierarchical users/permissions, shared catalogs, custom company pricing, quotes, payment terms, and targeted content/promotions. Custom shared catalogs can be visible only to members of assigned companies. experienceleague.adobe.com

That's probably the better platform if you're building something closer to a private procurement portal than a conventional wholesale ecommerce site.

Shopify?

Shopify is viable, particularly if your team already knows Shopify. Its B2B catalogs can associate specific products and price lists with B2B company locations, and its storefront can conditionally render content for authenticated B2B customers. shopify.dev

But for contract-heavy B2B + account-specific entitlements + IP restrictions, I'd put BigCommerce ahead of Shopify. Shopify's B2B capabilities have also expanded substantially in 2026, including on non-Plus plans, while some of the more useful catalog capabilities remain Plus-only. docs.bigcommerce.comshopify.devchangelog.shopify.com

Bottom line:
BigCommerce B2B Edition + Cloudflare/WAF is my default recommendation.
Adobe Commerce B2B + Cloudflare/WAF if the business rules are unusually complex.

If you tell me roughly number of customer accounts, number of unique contract price lists, whether users need SSO, and whether the storefront should be completely invisible to the public, I can narrow this to a specific architecture and stack.

For your requirements, I’d shortlist BigCommerce B2B Edition first, with Adobe Commerce as the heavier-duty alternative.

My pick: BigCommerce B2B Edition

It maps unusually well to your requirements. Its customer groups can control product access, pricing and promotions, while price lists support SKU-level pricing for particular customer groups. It also supports company hierarchies, buyer roles/permissions, and customer-specific catalogs. www.bigcommerce.com

More importantly, BigCommerce explicitly supports account-specific catalogs and pricing, so you can have:

• Customer A → products A/B/C + negotiated contract prices
• Customer B → different products + different negotiated prices
• Customer C → another catalog and price schedule
• Individual users → permissions within their company account

without maintaining separate stores. www.bigcommerce.com

BigCommerce B2B Edition

The one caveat: IP restriction

I wouldn't make the ecommerce platform itself responsible for the IP security boundary.

I'd put Cloudflare Access / Zero Trust or an equivalent identity/network layer in front of the storefront, with something like:

Customer → allowed corporate IP → authentication → BigCommerce storefront → account-specific catalog/pricing

That gives you a much stronger security model than simply hiding pages based on an IP address. If IP allowlisting is a hard requirement, I'd have the implementation team explicitly test that unauthenticated users cannot retrieve product/content/pricing data through APIs, search indexes, cached pages, or alternate storefront URLs.

When I'd choose Adobe Commerce instead

Choose Adobe Commerce if this is an enterprise implementation where the access rules are unusually complex—for example, dozens of customer organizations, multiple subsidiaries, sophisticated contract hierarchies, ERP-driven entitlements, extensive custom workflows, or very fine-grained authorization.

The tradeoff is considerably more implementation and engineering overhead.

Shopify Plus?

I'd put Shopify Plus third for this particular brief. Shopify's B2B functionality is strong: company profiles, customer-specific catalogs, pricing, payment terms, quantity rules and personalized storefront content are all supported. www.shopify.com

But IP-restricted/private B2B access plus highly customized account-level content pushes you toward custom infrastructure/apps, whereas BigCommerce's B2B model feels closer to your requirements out of the box.

Bottom line:
BigCommerce B2B Edition + Cloudflare Zero Trust would be my default architecture. It's the best balance of secure/private access, account-specific merchandising, contract pricing, and implementation complexity. BigCommerce's current enterprise tier is called Performance and is custom-priced; its 2026 pricing update lists it starting at $1,499/month, although a real B2B deployment should be quoted based on requirements. www.bigcommerce.com

If you tell me roughly how many customer accounts/users you have, whether the storefront is completely private, and whether pricing comes from an ERP/CRM, I can narrow this to a concrete architecture and platform recommendation.

For your requirements, I’d choose Adobe Commerce B2B + Cloudflare in front of it.

Why this fits

Adobe Commerce B2B lets you create company accounts and assign company-specific shared catalogs containing different products and prices. experienceleague.adobe.com It also supports customer segments and dynamic content, which is useful when "per-account content" means more than simply hiding products. experienceleague.adobe.com

For the IP requirement, I'd put Cloudflare WAF ahead of the storefront and maintain an allowlist of customer/company IP ranges. Cloudflare supports IP/CIDR allowlists and rules that block anything outside the allowlist, including applying the rule only to particular URL paths. experienceleague.adobe.comdevelopers.cloudflare.com

Runner-ups

BigCommerce B2B Edition would be my second choice. It has strong native customer groups, customer-specific catalogs, SKU-level pricing, company hierarchies, buyer portals, quoting and purchasing workflows. www.bigcommerce.com You'd still want Cloudflare or another network layer for the IP restriction.

Shopify Plus B2B is attractive if ease of administration and storefront UX are the priorities. Its B2B companies/company locations support catalogs, pricing, payment terms and customized experiences. help.shopify.com But I'd put it behind Adobe/BigCommerce for your particular requirement because IP-gated access + highly account-specific content pushes you toward a more customizable architecture.

My recommendation

Cloudflare → Adobe Commerce B2B → ERP/CRM

I would model each customer as an Adobe Company, give it its own contract/shared catalog where necessary, use customer segments/dynamic blocks for account-specific content, and maintain the customer's corporate IP ranges in Cloudflare.

One important security point: don't treat IP restriction as the authentication mechanism. Use IP allowlisting as an additional network control, with proper user/company authentication underneath it. That way a compromised corporate network doesn't automatically expose the account, and remote employees/VPN users can be handled deliberately.

If you tell me roughly how many B2B accounts you have, whether each account needs a unique price list, and whether customers are remote/VPN-based, I can narrow this down to a concrete architecture and implementation stack.

For your requirements, I’d shortlist BigCommerce B2B Edition + Cloudflare as the best fit.

My pick: BigCommerce B2B Edition

BigCommerce's model maps unusually well to what you're describing:

• Company accounts represent each B2B customer.
• Customer groups control what products and pricing an account sees.
• Price Lists let you assign SKU-level prices to customer groups.
• Company users can have different buyer roles and permissions.
• You can have different catalogs/content for different customer segments without maintaining separate stores. docs.bigcommerce.com
• BigCommerce specifically supports negotiated/contract pricing and customer-specific catalogs. www.bigcommerce.com

That gives you a clean model like:

Customer A
→ approved IP ranges
→ Company A
→ Buyer users
→ Catalog A
→ Contract Price List A
→ Account-specific content

Customer B
→ different IP ranges
→ Company B
→ Buyer users
→ Catalog B
→ Contract Price List B
→ different content

Put Cloudflare in front of it

I would not try to make the ecommerce platform itself responsible for your IP security boundary.

Use Cloudflare in front of the storefront and maintain an IP allowlist per customer. Cloudflare supports IP/CIDR matching and policies, and its Access layer can enforce policies on every request. developers.cloudflare.com

For example:

Internet
   │
   ▼
Cloudflare
   │
   ├── Customer A IP range ──┐
   ├── Customer B IP range ──┤
   └── Other traffic ────────┴── DENY
                │
                ▼
       BigCommerce B2B
                │
        ┌───────┴────────┐
        ▼                ▼
   Company A         Company B
   Catalog A         Catalog B
   Price List A      Price List B

Cloudflare's policies support IP ranges/CIDRs as selectors and can be configured deny-by-default. developers.cloudflare.comdocs.bigcommerce.com

Important caveat: IP restriction alone isn't sufficient authentication. I'd require IP + individual buyer authentication, ideally SSO/MFA for higher-value accounts. Otherwise anyone operating from an approved corporate network potentially has access.

When I'd choose Shopify Plus instead

Shopify Plus is arguably the better choice if your organization already lives in Shopify or you care more about storefront UX/ecosystem than deeply customized B2B workflows.

Shopify now has strong native B2B functionality: company profiles, multiple locations/buyers, customer-specific catalogs, pricing, payment terms and quantity rules. Plus provides unlimited catalogs and direct catalog assignment to companies/locations. apps.shopify.com

But IP restriction still belongs at the edge/security layer, rather than being the reason to choose Shopify.

If this is a highly regulated/enterprise portal

Then I'd consider Adobe Commerce or a headless architecture, particularly if you need:

• extremely complicated contract/pricing rules
• ERP-driven pricing in real time
• custom approval workflows
• sophisticated organization hierarchies
• procurement/EDI/punchout
• multiple authentication schemes
• very fine-grained authorization

The downside is substantially more implementation and ongoing engineering.

Bottom line: For a secure B2B storefront where the key requirements are IP allowlisting + account-specific content + contract pricing, I'd start with BigCommerce B2B Edition + Cloudflare + SSO/MFA, rather than building the commerce layer yourself. BigCommerce already gives you the company/catalog/pricing primitives; Cloudflare supplies the network-access boundary. developers.cloudflare.comdocs.bigcommerce.com

If you tell me roughly how many B2B accounts, whether each account has its own IP range, and whether you need ERP/EDI integration, I can narrow this down to a specific architecture and estimated implementation complexity.

For your requirements, Adobe Commerce B2B + an edge access layer is the strongest fit.

My ranking

1. Adobe Commerce B2B — my pick

Adobe's B2B model maps unusually well to what you're describing:

• Company accounts give each customer organization its own account structure.
• Shared Catalogs let you expose different products/content and custom prices to particular companies. experienceleague.adobe.com
• Negotiable Quotes support actual contract/negotiated pricing workflows. experienceleague.adobe.com
• Category permissions can control who can browse, see prices, and add products to cart. experienceleague.adobe.com
• Adobe Commerce also has a Private Sales: Login Only mode for making the storefront non-public. experienceleague.adobe.com
• For IP restriction, Adobe's security guidance explicitly supports using Fastly Edge ACLs/custom VCL to restrict site access to specified IPs/networks. experienceleague.adobe.com

So the architecture I'd use is:

Customer's corporate IP → Fastly/WAF allowlist → Adobe Commerce → authenticated company account → company-specific catalog/content/pricing

That gives you two independent security controls: network-level restriction and account-level authorization.

2. BigCommerce B2B Edition

This would be my second choice, particularly if you want a somewhat less infrastructure-heavy implementation.

BigCommerce has first-class Company accounts, with buyers belonging to companies, and customer groups control the products/pricing they see. docs.bigcommerce.com Its price lists can provide company/group-specific SKU pricing. docs.bigcommerce.com

I'd still put an IP-aware WAF/CDN in front of it for your security requirement rather than trying to make IP address the primary authorization mechanism.

3. Shopify Plus

Shopify has become considerably more capable for B2B. Its catalogs support customer-specific products and pricing, and Plus allows unlimited catalogs with direct assignment to company locations. help.shopify.com

It's attractive if you prioritize ease of implementation and polished commerce UX, but I wouldn't choose it primarily for a highly restricted B2B portal where IP/network authorization is a fundamental requirement.

One important architectural point

I would not make IP restriction the only security mechanism.

Use:

IP/network restriction → SSO/login → company authorization → catalog/content authorization → contract price

IP addresses identify a network, not a customer. A customer's employee working remotely, using cellular internet, or behind a changed corporate VPN could legitimately have a different IP. Conversely, multiple people can share the same corporate IP.

For a genuinely sensitive B2B portal, I'd consider Cloudflare Access/Zero Trust or Fastly at the edge, with identity-based controls in addition to IP allowlisting. Cloudflare supports IP-based allow/block rules and deny-by-default Access protection. developers.cloudflare.com

Bottom line: If you have complex contracts, dozens/hundreds of customer-specific catalogs, customer-specific content, and strict network access requirements, I'd choose Adobe Commerce B2B + Fastly/edge ACLs. If you want lower implementation complexity, BigCommerce B2B Edition + an edge WAF is probably the better alternative.

For your requirements, I’d shortlist Adobe Commerce B2B first, with BigCommerce B2B Edition as the simpler alternative.

My pick: Adobe Commerce B2B + edge IP controls

It maps unusually well to your requirements:

Adobe's Shared Catalog functionality lets you create catalogs that are visible only to particular company accounts, with custom product visibility and pricing. experienceleague.adobe.com It also has company accounts, buyer roles, negotiable quotes, and account-based payment options built into its B2B functionality. experienceleague.adobe.com

For the IP restriction, don't try to make IP address the actual authorization mechanism. Put the storefront behind an edge security layer and use IP allowlisting as an additional control. Adobe Commerce Cloud's Fastly integration supports ACLs and custom VCL that can allow/block requests based on client IP. experienceleague.adobe.com

A good architecture would be:

Customer → Fastly/WAF IP + security rules → Adobe Commerce → authenticated company account → company-specific catalog/pricing/content

That gives you two independent gates:

1. Network gate: request must originate from an approved corporate IP/range.
2. Application gate: authenticated user must belong to the appropriate B2B company.

That's considerably safer than simply hiding the storefront behind an IP whitelist.

Strong alternative: BigCommerce B2B Edition

BigCommerce B2B Edition is probably the better choice if you want less platform engineering.

It has company accounts, customer groups, SKU-level price lists, custom catalogs, buyer roles, quotes, and account hierarchies. www.bigcommerce.com

I'd choose it when your model is relatively straightforward:

Customer A → catalog A → price list A
Customer B → catalog B → price list B

Adobe becomes more attractive when you're building a sophisticated distributor/manufacturer portal with complicated contract rules, multiple websites, ERP integration, custom workflows, and highly personalized content.

What about Shopify Plus?

Shopify Plus B2B is excellent for conventional B2B commerce. Its B2B catalogs support customer-specific products and pricing, and Plus allows catalogs to be assigned directly to companies/company locations. help.shopify.com

But I wouldn't make it my first choice for your specific requirement if IP-restricted access is a hard security requirement. You'd likely be building more of the access-control architecture around Shopify rather than getting the whole model naturally from the platform.

Bottom line

If security + account isolation are paramount:
Adobe Commerce B2B + Fastly/WAF

If ease of implementation is paramount:
BigCommerce B2B Edition + edge/WAF IP allowlisting

If polished storefront/DTC + B2B coexistence is paramount:
Shopify Plus

One important nuance: IP restriction and account authorization should be separate controls. IP addresses are useful for restricting corporate networks, but they shouldn't substitute for identity, because users can work remotely, use VPNs, or share a corporate network.

If you tell me roughly how many customer accounts, SKUs, and ERP/CRM integrations you have, I can narrow this down to a specific stack and architecture.