ChatGPT answers, unedited

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.