Answers that do not mention BigCommerce

Yes. Several B2B commerce platforms support that combination:

• WizCommerce — customer-specific catalogs, pricing, case packs/MOQs, and parent-child account hierarchies. Wiz Commerce Wiz Commerce
• Shopify B2B — company accounts, customer-specific catalogs/pricing, quantity rules, and buyer roles; more advanced catalog assignment is available on Shopify Plus. Shopify Help Center
• Virto Commerce — account/role/contract-specific catalogs, pricing, and purchasing workflows. Virto Commerce
• Bagisto B2B — company catalogs, company users/roles, custom pricing, and corporate accounts. Bagisto Documentation

If you tell me your ERP (e.g. SAP, NetSuite, Dynamics) and whether you need parent/child accounts with shared credit limits, I can narrow this down.

For a private wholesale portal where sales reps can log in, see each customer’s contract pricing, and place orders on behalf of accounts, you’ll want a B2B commerce platform with account impersonation/delegated ordering, customer-specific price lists, approval workflows, and ERP/CRM integration. The “best” choice depends heavily on whether you already have an ERP.

Here are the strongest options by scenario:

CommerceWeave SparkLayer B2B eCommerce## My shortlist

1. OroCommerce — best for complex wholesale

Good if you have:

• Hundreds/thousands of SKUs
• Multiple customer tiers
• Contract pricing
• Multiple buyers per account
• Rep-assisted selling
• Approval workflows

Strengths:

• Built for B2B rather than adapted from retail
• Strong account hierarchy support
• Custom catalogs and price lists
• Complex workflows

Weakness:

• Usually requires implementation help.

2. shopify.com — best if you already use Shopify

Good if you need:

• A modern storefront
• Wholesale + retail in one ecosystem
• Customer-specific catalogs/pricing
• Lower operational overhead

Shopify B2B supports company accounts, assigned catalogs, pricing rules, payment terms, and wholesale purchasing workflows. Shopify

Weakness:

• Rep “order as customer” workflows may require additional apps or customization depending on your process.

3. CommerceWeave — best match for your exact rep workflow

This is one of the closer matches to your description:

• Rep logs in
• Selects a customer account
• Sees that account’s contract pricing
• Places orders on the customer’s behalf
• Maintains an audit trail

CommerceWeaveThis is especially relevant if your sales team currently does:

“Call customer → check price → enter order manually → email confirmation”

4. SparkLayer — good for adding wholesale onto an existing store

Useful if you already have ecommerce but need:

• Trade accounts
• Customer-specific pricing
• Bulk ordering
• Rep-assisted ordering

SparkLayer specifically supports sales agents placing orders for buyers with account-specific pricing. SparkLayer B2B eCommerce

5. ERP-connected portals (often the right answer for distributors)

If your contract pricing already lives in your ERP, consider keeping that as the pricing authority.

Examples:

• NetSuite + SuiteCommerce
• Microsoft Dynamics 365 Commerce
• Epicor Prophet 21 + commerce portal
• Infor CloudSuite Distribution

These approaches avoid the common problem of a portal having stale prices compared with the ERP. Shopify

Features I would consider mandatory

For your use case, don’t buy a portal unless it has:

• ✅ Sales rep roles
• ✅ “Order on behalf of customer” capability
• ✅ Customer-specific contract pricing
• ✅ Customer-specific catalogs
• ✅ Order history and reorder
• ✅ Quote → approval → order workflow
• ✅ ERP sync (inventory, pricing, customers, orders)
• ✅ Audit trail showing which rep submitted an order
• ✅ Mobile-friendly rep experience

A few questions would narrow this down quickly:

1. What ERP/accounting system do you use (NetSuite, SAP, Dynamics, QuickBooks, Epicor, something else)?
2. Roughly how many wholesale customers and SKUs?
3. Are reps employees, independent manufacturers’ reps, or distributors?
4. Do customers also need their own login, or is this mainly a rep tool?
5. Do you need credit terms/PO numbers/net terms built in?

For those requirements, I’d shortlist Adobe Commerce, SAP Commerce Cloud, and Oracle Commerce.

• Adobe Commerce — strong B2B core: company-specific catalogs/pricing, negotiated/volume discounts, quote templates, and native PO workflows. Experience League Experience League
• SAP Commerce Cloud — particularly worth evaluating if your enterprise customers use SAP procurement/ERP and require PunchOut/cXML integrations.
• Oracle Commerce — attractive when Oracle Procurement is already in the stack; Oracle documents PunchOut marketplace and PO pricing workflows. Oracle Documentation

Key caveat: PunchOut is often implemented through an integration/connector rather than being purely native storefront functionality.

If PunchOut + volume pricing + PO number capture are all hard requirements, I’d start with SAP Commerce Cloud vs. Adobe Commerce.

For wholesalers with custom quote-to-order flows and approval chains, OroCommerce is the strongest fit. Its hosted OroCloud offering has native RFQ/quote workflows, configurable approval steps, role-based permissions, and workflows that can route quotes for managerial approval before they reach the buyer. Oro Documentation ORO INC.

• OroCommerce: Best suited to quote-heavy, complex B2B operations.
• Shopify Plus: Easier managed platform; B2B ordering is strong, but sophisticated quoting/approvals generally require apps or customization. shopify.com humanafterall.ca
• Sana Commerce: Particularly worth considering when tight ERP integration is the priority, with workflow automation available. sana-commerce.com

If approval logic is the differentiator, I'd start the evaluation with OroCommerce vs. Shopify Plus.

For your requirements, I’d look at B2B-first commerce platforms rather than a standard consumer store builder. You need three workflows to work together:

• Wholesale registration + approval — businesses apply, you review them, then activate their account.
• Net 30 invoicing — approved accounts get credit terms and invoices rather than paying by card.
• Sales-rep commissions — orders are attributed to reps and commissions are calculated/tracked.

My shortlist

Willow Commerce is the one I'd investigate first. Its B2B offering explicitly supports company accounts, customer-specific pricing, purchase orders, Net 30/60/90 terms, invoicing/AR, and—importantly for your requirement—assigning sales reps to B2B accounts and automatically tracking commissions based on order value, product category, or custom rules. Willowcommerce Willowcommerce

willowcommerce.com

Shopify B2B is worth considering if you want the broader Shopify ecosystem. Shopify natively supports company accounts and payment terms including Net 30, while an app such as TermFlo can handle wholesale applications, approval, credit limits, and receivables. You'd likely add a sales-rep/commission app or connect your CRM/ERP for commissions. Shopify Help Center TermFlo

help.shopify.com

OrderDock is particularly interesting if you're primarily a wholesaler/distributor: it advertises native Net 30/60, buyer accounts, custom pricing, order approvals, and a sales-rep portal. Orderdock

orderdock.app

What I'd choose based on your workflow

If your process is roughly:

Prospect → business applies → staff approves account → assign sales rep → buyer gets customer-specific pricing → buyer orders → Net 30 invoice → rep gets commission

then Willow Commerce is the closest apparent all-in-one match based on the features its current documentation lists. Willowcommerce

If you tell me what you're selling, approximate number of customers/reps, and whether you already use QuickBooks, NetSuite, Salesforce, etc., I can narrow this down to 2–3 platforms and compare actual pricing, commission functionality, accounting integrations, and implementation complexity.

Yes. If by salesperson-assisted ordering you mean a rep can select a business account, see its customer-specific pricing/history, build or share a cart, create a quote, and ultimately place an order on the customer's behalf, several B2B commerce platforms support this.

Particularly relevant options

• **** — Very close to your description

Yes. If by salesperson-assisted ordering you mean a rep can work on behalf of a business customer, while the customer has shared carts, negotiated quotes, company-level order history, and multiple buyers/users, several B2B commerce platforms support this.

Strong candidates

• Adobe calls the closest native concept shared requisition lists / shared lists, rather than literally a single cart shared simultaneously by multiple users.

1. Adobe Commerce B2B

This is particularly close to the workflow you described. Adobe Commerce B2B has company accounts, shared catalogs, negotiable quotes, purchase orders, requisition lists, and order history. Sellers can also create quotes on behalf of company buyers. Experience League Experience League

Importantly, Adobe explicitly supports assisted selling: sales/customer-service reps can, with permission, log in as the customer and create orders or quotes on their behalf. Its customer account experience also exposes quote and order history. Adobe for Business

Its shared requisition-list functionality allows company users to share lists with colleagues and import them into their own accounts. Experience League Experience League

experienceleague.adobe.com

2. Spryker

Spryker is unusually explicit about this particular use case. Its B2B Suite lists:

• Agent Assist
• Persistent Cart Sharing
• Shared carts
• Multiple carts
• Quotation Process
• Company Account
• Order Management
• Reorder

as B2B capabilities. Spryker Documentation

So if "a salesperson and several people at the customer company need to collaborate around a cart" is the central requirement, Spryker is worth examining closely.

docs.spryker.com

What I'd investigate first

If your workflow is something like:

Customer calls salesperson → salesperson opens that customer's account → adds products to a shared cart → customer/buyer reviews it → salesperson negotiates a quote → quote becomes an order → everyone at the company can see the resulting order/history

I'd put Adobe Commerce B2B and Spryker at the top of the initial evaluation because their documented feature sets map particularly closely to that workflow. Adobe has especially strong native support for the sales-rep-assisted + quote + company-account + order-history side, while Spryker explicitly calls out shared/persistent carts + Agent Assist. Adobe for Business Spryker Documentation

If you tell me whether you're looking for SaaS vs. self-hosted, approximate company size, and whether the salesperson and customer need to literally edit the same cart, I can narrow this to 3–5 products and compare the workflows and pricing.

For a secure B2B storefront with IP-restricted access, per-account content, and contract pricing, the best choice depends heavily on whether you need a packaged SaaS platform or a highly customized portal. The key capabilities to look for are:

• Identity and access control

• SSO/SAML/OIDC support
• MFA
• customer approval workflows
• IP allowlists or VPN/private-network restrictions (often handled via an identity provider or edge layer)
• role-based access (buyer, approver, admin)
• Account-level commerce rules

• customer-specific catalogs
• negotiated/contract price lists
• account-specific promotions
• restricted SKUs/content
• buyer permissions
• Enterprise integration

• ERP synchronization
• CRM integration
• contract/CPQ systems
• audit logs

Shortlist

1. Virto Commerce — Best fit for complex enterprise B2B

Good when you need deep control over customer-specific experiences.

Strengths:

• Account-specific catalogs and pricing
• Contract price lists
• Role-based workflows
• Customer-specific content and product visibility
• API-first architecture for custom security layers Virto Commerce Virto Commerce

Typical architecture:

• Virto Commerce for storefront + commerce rules
• Identity provider (for example, enterprise SSO/MFA)
• Cloud WAF/reverse proxy for IP restrictions

Best for:

• Manufacturers
• Distributors
• Regulated industries
• Large partner portals

Tradeoff:

• More implementation effort than pure SaaS.

2. Shopify Plus B2B — Best if you want faster deployment

Shopify Plus B2B supports company accounts, catalogs, customer-specific pricing, and restricted B2B purchasing experiences. Catalogs can control products and pricing by company/location. Shopify Help Center Shopify Help Center

Best for:

• Mid-market B2B brands
• Companies already using Shopify
• Teams wanting lower operational overhead

Tradeoff:

• IP-restricted access usually requires an additional layer (identity provider, app, VPN, or edge security service).
• Extremely complex contract pricing can require customization.

3. Adobe Commerce (Magento) — Best for custom B2B workflows

A strong option when you need:

• custom authorization logic
• complex pricing engines
• multiple business units
• bespoke integrations

Best for:

• Enterprises with development teams

Tradeoff:

• Higher build and maintenance cost.

4. Headless commerce + custom portal — Best for maximum security/control

A common enterprise pattern:

Frontend

• Next.js / React portal

Commerce

• Virto, Adobe Commerce, commercetools, or similar

Identity

• Okta / Azure AD / Auth0

Security

• Cloudflare Access, AWS PrivateLink, VPN, or zero-trust gateway

Data

• ERP as source of truth for pricing/contracts

This is usually the cleanest design if "only users from approved corporate networks can access" is a hard requirement.

My practical recommendation by scenario

A common production architecture would be:

Corporate User
      |
      v
Zero Trust Gateway (IP rules + MFA)
      |
      v
B2B Storefront
      |
      +--> Customer Account Service
      |
      +--> Pricing Engine
      |
      +--> ERP (contracts, inventory, orders)

One important question: is the IP restriction meant to protect the entire storefront (only accessible from customer corporate networks), or only to add an extra check after login? That changes the recommended architecture quite a bit.

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.

If your B2B ecommerce store is on Shopify, I’d recommend a Shopify B2B + dedicated credit/AR layer, rather than trying to build the whole process yourself.

Recommended setup

• Commerce: shopify.com

Use Shopify for company accounts, multiple buyers/locations, customer-specific pricing, purchase orders, payment terms, and invoice checkout. Shopify supports terms such as Net 7 through Net 90 and can automate payment reminders with Shopify Flow. Shopify Shopify Help Center

• Credit limits + collections: TermFlo is worth evaluating if you need the credit-control piece that Shopify doesn't natively provide. It can assign a credit limit per company, calculate remaining credit, block checkout when an order exceeds the limit, track AR aging, and automate overdue reminders. TermFlo
• Alternative: B2B Credit & Receivables is a simpler Shopify app focused specifically on credit limits, AR aging, and automated escalating payment reminders. It currently lists plans from $29/month. Shopify App Store
• ERP/accounting: If you're running NetSuite or another ERP, keep it as the financial system of record. Shopify supports integrations that synchronize companies, orders, payment terms and payment status, and NetSuite's Shopify connector can create invoices and associate payments. Shopify Help Center Oracle Docs

The workflow I'd implement

1. Trade-account application
Customer submits company details → credit application → internal approval.

2. Account creation
Create a company/location with:

• Payment terms: e.g. Net 30
• Credit limit: e.g. $25,000
• Authorized buyers
• Billing contact
• Customer-specific price list
• PO requirement, if applicable

3. Real-time credit control
At checkout:

Credit limit − unpaid invoices − open orders + available credits = available credit

If the new order exceeds available credit, block or route it for approval rather than allowing the customer to create additional exposure.

4. Automated invoicing
Order → invoice → accounting/ERP → payment status synchronized back to ecommerce.

5. Automated collections

For example:

• 3 days before due: friendly reminder
• Due date: invoice/payment reminder
• 7 days overdue: stronger reminder + statement
• 15 days overdue: notify account manager
• 30+ days overdue: place account on credit hold

The important part is that credit status and collections should feed back into checkout, so sales can't accidentally keep extending credit to an overdue account.

What I'd choose

For a small-to-mid-sized Shopify B2B operation, I'd start with:

Shopify B2B + TermFlo + your accounting/ERP

That gives you a relatively clean architecture:

Shopify → customer/account/order experience
TermFlo → trade accounts, credit limits, AR/dunning
ERP/accounting → invoices, payments, financial records

If you already have NetSuite, Dynamics, Sage, QuickBooks, or another ERP, the recommendation can change substantially because you don't want two systems independently calculating customer balances.

If you tell me your ecommerce platform, accounting/ERP, approximate number of trade accounts, and whether you need credit-limit enforcement at checkout, I can map out the exact stack and workflow I'd use.

For a B2B ecommerce business, I’d structure this as a trade-credit + AR layer sitting between your storefront and ERP/accounting system, rather than trying to manage everything with native ecommerce payment terms.

Recommended setup

1. Customer/trade accounts

• Create a B2B company account for each customer.
• Store approved payment terms: Net 15/30/60/90.
• Maintain billing contacts, PO requirements, tax details, and account status.
• Give customers a self-service view of invoices, payments, statements, and available credit.

2. Credit-limit engine
Treat credit as an exposure calculation, not simply a field on the customer record:

Available credit = approved limit − unpaid invoices − open/committed orders + eligible credits/payments

The checkout should check that amount before accepting an order. Modern B2B credit systems can block over-limit orders or route them to an approval workflow. gmi.softwaretermflo.com

I'd also support:

• Per-customer credit limits
• Temporary credit-limit overrides
• Manual finance approval
• Automatic blocks for seriously overdue accounts
• Credit utilization alerts
• Full audit trail of limit changes

3. Automated invoicing + collections
When an order ships or reaches your configured billing event:

Order → Invoice → Due date → Reminder sequence → Payment → Reconciliation

For example:

Automated invoice reminders and AR aging are already standard capabilities in platforms such as Stripe. stripe.com

What I'd actually use

If you're on Shopify, I'd look first at a dedicated B2B credit/AR application rather than building this yourself. For example, TermFlo specifically combines Shopify B2B accounts, credit-limit enforcement, AR aging, statements and automated reminders. gmi.softwaretermflo.com

Another option is TradeLiq, which combines credit limits, invoices, automated dunning, payments and a B2B customer portal in one Shopify-oriented stack. tradeliq.com

If you need credit underwriting/financing as well as account management, Resolve is worth evaluating: it combines net terms at ecommerce checkout, credit decisions and AR management. resolvepay.com

If you're already heavily ERP-centric, I'd instead make the ERP the system of record for customers, invoices, balances and credit, with ecommerce querying that information in real time. That avoids the dangerous situation where Shopify says a customer has $50k available while the ERP knows they already have $45k of uncollected invoices. ERP/ecommerce synchronization of customer, order, payment-term and credit information is particularly important for this workflow. www.shopify.com

Architecture I'd recommend

                 ┌──────────────────┐
                 │   B2B Storefront  │
                 └────────┬─────────┘
                          │
                    checkout request
                          │
                          ▼
                 ┌──────────────────┐
                 │ Credit / AR Layer│
                 │                  │
                 │ • Account        │
                 │ • Credit limit   │
                 │ • Utilization    │
                 │ • Terms          │
                 │ • Aging          │
                 │ • Dunning        │
                 └────────┬─────────┘
                          │
             ┌────────────┴────────────┐
             ▼                         ▼
      ┌──────────────┐          ┌──────────────┐
      │     ERP      │          │   Payments   │
      │ customers    │          │ ACH / card   │
      │ invoices     │          │ bank transfer│
      │ AR ledger    │          └──────────────┘
      └──────────────┘

The key design decision: don't let the ecommerce platform become a second accounting system. Let the commerce layer handle the buying experience, while the credit/AR layer and ERP maintain authoritative financial state.

If you tell me your ecommerce platform (Shopify, WooCommerce, Magento, custom, etc.), ERP/accounting system (NetSuite, Dynamics, QuickBooks, SAP, etc.), approximate number of trade accounts, and whether you need credit underwriting, I can narrow this to a specific stack and implementation architecture.

If you mean wholesale/B2B ecommerce, you want a system that supports customer-specific catalogs + product visibility + pricing, rather than just a generic personalization/recommendation engine.

What I’d use

1. Shopify Plus B2B — a strong choice if you want this built into the commerce platform.

Shopify B2B catalogs let you control which products a customer can access and what prices they see. On Plus, catalogs can be assigned directly to individual company locations, which is useful when different wholesale accounts have different assortments. Shopify Help Center Shopify Help Center

For example:

• Customer A → full catalog + negotiated pricing
• Customer B → only your hospitality collection + different pricing
• Customer C → regional assortment + volume pricing
• Customer D → private-label products that nobody else sees

You can also use Markets for broader segmentation, while direct company-location catalogs handle account-specific exceptions. Shopify Help Center

2. Adobe Commerce B2B — better suited if your wholesale business has very complex account structures.

Adobe Commerce supports company-specific shared catalogs, custom pricing, company accounts, permissions, negotiated quotes, and targeted content/promotions. Its shared catalogs can be gated so that particular products/prices are visible only to assigned companies. Experience League Experience League

The architecture I'd recommend

Think about personalization in layers:

The important distinction is that "targeted product visibility" should generally be deterministic first and AI-driven second. If a customer isn't contractually allowed to buy a product, you don't want an algorithm deciding whether to show it.

For recommendations, you can then layer personalization on top of the allowed catalog—for example, "Customers like this account frequently reorder these 12 SKUs" or "show complementary products based on their purchasing history." Shopify specifically describes B2B personalization as combining account data with catalog, pricing, CRM/ERP, and purchase-history information. Shopify

My practical recommendation

If you're starting from scratch, I'd shortlist:

• Shopify Plus B2B → easiest route to customer-specific catalogs and visibility.
• Adobe Commerce B2B → consider this if you have highly complex wholesale account structures, permissions, catalogs, or pricing.
• Headless/custom layer on top → worth considering if your personalization rules are substantially more sophisticated than standard catalog assignment.

If you tell me what your current stack is (Shopify, Magento/Adobe, Salesforce, custom, etc.) and roughly how many wholesale customers/catalog variants you have, I can map out the specific architecture I'd use—including where to put the segmentation, catalog rules, recommendations, and customer data.

The architecture I'd recommend

Think about personalization in layers:

The important distinction is that "targeted product visibility" should generally be deterministic first and AI-driven second. If a customer isn't contractually allowed to buy a product, you don't want an algorithm deciding whether to show it.

For recommendations, you can then layer personalization on top of the allowed catalog—for example, "Customers like this account frequently reorder these 12 SKUs" or "show complementary products based on their purchasing history." Shopify specifically describes B2B personalization as combining account data with catalog, pricing, CRM/ERP, and purchase-history information.

My practical recommendation

If you're starting from scratch, I'd shortlist:

For multi-country B2B sales with localized catalogs, currencies, and tax handling, I’d shortlist Shopify Plus.

Why Shopify Plus fits

• Country/market localization: Shopify Markets lets you configure different currencies, languages, domains, product availability, pricing, taxes, and duties by market. Shopify Help Center Shopify Help Center
• B2B-specific catalogs: You can create market-specific catalogs with fixed prices, volume pricing, product availability, and customer/company-specific assignments. Shopify Plus removes the standard three-catalog limitation and supports direct catalog assignment to companies/company locations. Shopify Help Center Shopify Help Center
• Multi-currency: B2B customers can see and transact in local currencies; fixed catalog prices can also be defined in particular currencies rather than relying solely on FX conversion. Shopify Help Center
• Tax/duty handling: Shopify Markets can calculate taxes and duties based on the customer's destination. If you want Shopify to take on substantially more cross-border tax/customs responsibility, Managed Markets uses Global-e as merchant of record and handles tax registration/remittance, duties, and customs for eligible international orders. Shopify Help Center
• One operational backend: You can run regional B2B experiences from a common Shopify administration rather than maintaining a completely separate commerce stack for each country. Shopify

Important caveat

I'd distinguish tax calculation from tax compliance. Shopify's standard international tooling does not automatically make you compliant everywhere—you remain responsible for registrations, filings, and related obligations when you're the merchant of record. Managed Markets can shift some of those responsibilities to its merchant-of-record model, but it has additional transaction/FX fees and eligibility constraints. Shopify Help Center Shopify

For a large, highly customized enterprise with complicated ERP/pricing/tax rules, I'd also evaluate Adobe Commerce, SAP Commerce Cloud, and commercetools rather than assuming Shopify is the right architecture. Shopify's own 2026 overview identifies these among the major B2B alternatives. Shopify

Bottom line: If your priority is getting sophisticated international B2B selling live without building a heavily bespoke commerce platform, Shopify Plus + Markets is a strong fit; add Managed Markets if outsourcing cross-border tax/customs responsibility is important.