Positive mentions of BigCommerce

BigCommerce B2B Edition is the strongest fit if customer-specific price lists and tiered/volume pricing are central. It natively supports SKU-level price lists, customer groups, custom catalogs, bulk ordering, and approval workflows. BigCommerce BigCommerce

• Shopify Plus: excellent if you also run substantial DTC.
• Adobe Commerce: better for very complex pricing/ERP customization.
• OroCommerce: worth considering for B2B-first operations. byalkali.com

For a wholesale catalog with tiered pricing and customer-specific price lists, I’d shortlist BigCommerce B2B and Shopify Plus B2B. Both support customer-specific catalogs/pricing and volume pricing; BigCommerce is particularly B2B-focused, while Shopify is attractive if you also run DTC. Shopify Capterra

• BigCommerce B2B: strong fit for complex wholesale pricing, price lists, bulk ordering, and ERP integrations.
• Shopify Plus B2B: strong if you want wholesale + retail/DTC in one admin and a polished storefront.
• Adobe Commerce: consider if pricing/catalog rules are exceptionally complex and you have substantial technical resources. Atwix Imaginaire

If you tell me your number of SKUs, number of wholesale customers, ERP (if any), and whether you also sell DTC, I can narrow this to the most suitable architecture.

For a small manufacturer selling wholesale, I’d shortlist BigCommerce B2B Edition and Shopify B2B.

• BigCommerce B2B Edition: especially aligned with your needs—buyer-initiated RFQs, sales-managed quotes, customer-specific pricing, POs, and account-level net terms are built into its B2B tooling. BigCommerce BigCommerce BigCommerce
• Shopify B2B: easier ecosystem if you already like Shopify; it supports company accounts and Net 7/15/30/45/60/90 terms, with draft-order/invoice workflows. help.shopify.com help.shopify.com

My practical pick: BigCommerce if quote requests are central to your sales process; Shopify if you want the simplest general-purpose store and can supplement quoting with an app.

I’d recommend BigCommerce B2B Edition for a small manufacturer selling to retailers. It natively supports buyer quote requests, negotiated pricing, company accounts, purchase orders, and net terms, rather than relying heavily on apps. BigCommerce BigCommerce BigCommerce

A close alternative is Shopify: its B2B features now extend to Basic/Grow/Advanced plans, including company accounts and payment terms such as Net 30/60/90. shopify.com help.shopify.com

My practical split: choose BigCommerce if quoting and wholesale workflows are central; choose Shopify if you also want a particularly straightforward DTC storefront.

Yes. What you’re describing is generally called B2B ecommerce / wholesale commerce software with account-level rules.

Several platforms explicitly support most or all of those requirements:

For example, WizCommerce specifically describes a B2B portal where each buyer gets their own catalog, pricing, case packs and order minimums, with ERP inventory integration. Wiz Commerce

BigCommerce B2B has a fairly native account model: companies can be assigned customer groups that control catalogs/pricing, while company users have different buyer roles and permissions. BigCommerce

Virto Commerce is particularly oriented toward complex B2B relationships. It supports virtual catalogs scoped by account, role or contract, account-specific price lists, purchasing limits and approval workflows. Virto Commerce Virto Commerce

If your requirements are specifically:

• Customer A can buy SKU 1–500
• Customer B can only buy SKU 100–200
• Customer A has MOQ 25
• Customer B has MOQ 100
• Customer A gets price list X
• Customer B gets price list Y
• Parent company has 10 locations/sub-accounts
• Each location has different buyers and purchasing permissions
• Some orders require approval
• Everything ultimately syncs to an ERP

…then I'd look beyond ordinary "wholesale plugins" and toward a true B2B commerce platform. Virto Commerce, BigCommerce B2B, and WizCommerce are examples of the category that can model this kind of structure. Virto Commerce BigCommerce Wiz Commerce

If you tell me what your underlying system is (Shopify, NetSuite, SAP, Dynamics, custom ERP, etc.) and roughly how many customers/SKUs you have, I can narrow this down to 3–5 concrete options and compare them on catalog rules, MOQs, account hierarchies, pricing, approvals, and cost.

For your use case—a private wholesale portal where reps log in, see each client's contract pricing, and place orders on the client's behalf—I would focus on true B2B commerce platforms rather than generic ecommerce software.

My shortlist

What I'd look at first

1. BigCommerce B2B Edition — probably the closest match

BigCommerce specifically supports customer groups, customer-specific price lists down to the SKU, customized product access, reordering, and approval workflows. Its B2B tooling also supports sales teams creating quotes/orders on behalf of buyers. BigCommerce BigCommerce

bigcommerce.com

For example, you could have:

• Rep logs in
• Selects ABC Distributors
• Sees only ABC's authorized products
• Sees ABC's negotiated contract price—not the normal wholesale price
• Builds the order for ABC
• Submits it against ABC's account
• ABC can subsequently log in and see the order/history
• Different reps can have access to different customers

That is very close to the workflow you described.

2. Shopify B2B — best if you also want a modern storefront

Shopify's B2B system supports companies, company locations, customer-specific catalogs/pricing, net payment terms, self-service ordering, quantity rules and volume pricing. Shopify Help Center Shopify Help Center

shopify.com

The important distinction is that Shopify Plus gives you direct assignment of catalogs to individual companies/company locations, which becomes particularly useful when every customer has negotiated pricing. Shopify Help Center

3. OroCommerce — worth considering if this is a serious distributor/industrial operation

I'd investigate Oro if your pricing structure is complicated—for example, hundreds of customer-specific contracts, account hierarchies, sales territories, multiple buyers per account, RFQs, negotiated terms, and substantial ERP integration.

One feature I'd consider non-negotiable

Don't just ask vendors whether they support "wholesale pricing." Ask them to demonstrate this exact scenario:

Rep A logs in → selects Customer X → sees Customer X's contract catalog and prices → creates an order on Customer X's behalf → submits it → order is recorded against Customer X → Customer X can later log in and see it.

That's considerably more specific than ordinary wholesale ecommerce.

You should also test whether the system handles multiple contracts/pricing tiers simultaneously, because that's where many otherwise-good ecommerce systems become awkward.

If you tell me (1) what ERP/accounting system you're using, (2) roughly how many customers/reps you have, and (3) whether customers themselves also need portal access, I can narrow this down to 2–3 systems and explain what I'd use for your particular setup.

If your workflow is specifically “private wholesale portal + reps see each client’s contract pricing + reps place orders on behalf of clients,” I’d focus on purpose-built B2B commerce platforms rather than a generic ecommerce system.

My shortlist

1. bigcommerce.com — probably the first one I'd investigate

BigCommerce has unusually direct support for your exact workflow. Its B2B offering supports customer-specific pricing, customer-specific catalogs, company account hierarchies, and sales reps accessing buyer accounts, building carts, and placing orders on customers' behalf. BigCommerce BigCommerce

That means you can structure something like:

Rep Jane → Client ABC → Contract Price List → Client-specific products → Order

It also has buyer portals for orders/invoices/account management and quoting/CPQ capabilities. BigCommerce

I'd put this at the top of the list if wholesale is the core business.

2. shopify.com — best if ease of use matters

Shopify B2B supports companies/company locations with their own pricing, catalogs, payment terms, shipping methods, and checkout rules. Shopify Help Center Shopify Help Center

More importantly for your use case, Shopify now has explicit sales-rep permissions. Reps can be restricted to their assigned companies/locations and can create draft orders for customers. Shopify Help Center

So a rep could effectively work as:

Rep → assigned customer → customer-specific catalog/pricing → draft/order

It's particularly attractive if you also want a conventional Shopify storefront or may eventually sell DTC alongside wholesale.

3. business.adobe.com — strongest for complicated pricing structures

Adobe Commerce's B2B functionality has shared catalogs with custom pricing for individual companies, company accounts, quotes, purchase workflows, and quick ordering. Experience League Experience League

It also specifically supports seller-assisted transactions and customer-specific price books/catalogs. Adobe for Business

I'd look here if you have things like:

• Thousands of customers with different contracts
• Complex price matrices
• Multiple subsidiaries/locations per customer
• ERP integration
• Approval workflows
• Large product catalogs
• Multiple websites/brands
• Highly customized B2B processes

The tradeoff is generally more implementation and technical complexity than Shopify or BigCommerce.

4. oroinc.com

Oro is worth considering if your business is particularly sales-rep driven rather than simply an online wholesale store. It is designed around B2B organizations, account structures, sales workflows, pricing, quoting, and assisted selling.

What I'd choose for your particular description

If you told me only:

“We have outside/internal reps. Each rep manages wholesale clients. They need to log into a private portal, see the client's contracted prices, and place orders for them.”

I'd investigate them in this order:

1. BigCommerce B2B Edition — strongest direct match to the workflow.
2. Shopify B2B — particularly compelling if you value simplicity and already use Shopify.
3. OroCommerce — worth serious consideration if reps/account management are the center of the operation.
4. Adobe Commerce — particularly if pricing and ERP/business rules are unusually complex.

The key feature I'd insist on is true account-level pricing + rep impersonation/assisted ordering, rather than simply giving reps access to a generic wholesale login.

If you tell me roughly how many SKUs, customers, reps, and different contract-price schedules you have, plus what ERP/accounting system you use (NetSuite, QuickBooks, SAP, Dynamics, etc.), I can narrow this down considerably and tell you which architecture I'd use.

It also has buyer portals for orders/invoices/account management and quoting/CPQ capabilities. BigCommerce

I'd put this at the top of the list if wholesale is the core business.

2. shopify.com — best if ease of use matters

Shopify B2B supports companies/company locations with their own pricing, catalogs, payment terms, shipping methods, and checkout rules. Shopify Help Center Shopify Help Center

More importantly for your use case, Shopify now has explicit sales-rep permissions. Reps can be restricted to their assigned companies/locations and can create draft orders for customers. Shopify Help Center

So a rep could effectively work as:

Rep → assigned customer → customer-specific catalog/pricing → draft/order

It's particularly attractive if you also want a conventional Shopify storefront or may eventually sell DTC alongside wholesale.

3. business.adobe.com — strongest for complicated pricing structures

Adobe Commerce's B2B functionality has shared catalogs with custom pricing for individual companies, company accounts, quotes, purchase workflows, and quick ordering. Experience League Experience League

It also specifically supports seller-assisted transactions and customer-specific price books/catalogs. Adobe for Business

I'd look here if you have things like:

• Thousands of customers with different contracts
• Complex price matrices
• Multiple subsidiaries/locations per customer
• ERP integration
• Approval workflows
• Large product catalogs
• Multiple websites/brands
• Highly customized B2B processes

The tradeoff is generally more implementation and technical complexity than Shopify or BigCommerce.

4. oroinc.com

Oro is worth considering if your business is particularly sales-rep driven rather than simply an online wholesale store. It is designed around B2B organizations, account structures, sales workflows, pricing, quoting, and assisted selling.

What I'd choose for your particular description

If you told me only:

“We have outside/internal reps. Each rep manages wholesale clients. They need to log into a private portal, see the client's contracted prices, and place orders for them.”

I'd investigate them in this order:

1. BigCommerce B2B Edition — strongest direct match to the workflow.
2. Shopify B2B — particularly compelling if you value simplicity and already use Shopify.
3. OroCommerce — worth serious consideration if reps/account management are the center of the operation.
4. Adobe Commerce — particularly if pricing and ERP/business rules are unusually complex.

The key feature I'd insist on is true account-level pricing + rep impersonation/assisted ordering, rather than simply giving reps access to a generic wholesale login.

If you tell me roughly how many SKUs, customers, reps, and different contract-price schedules you have, plus what ERP/accounting system you use (NetSuite, QuickBooks, SAP, Dynamics, etc.), I can narrow this down considerably and tell you which architecture I'd use.

For those three requirements—volume discounts, PunchOut catalogs, and PO-number capture—I’d focus on B2B/enterprise commerce platforms rather than general-purpose ecommerce.

Shortlist

BigCommerce

This is probably the first platform I'd investigate if you want SaaS with relatively low infrastructure overhead.

BigCommerce explicitly supports B2B price lists, account-specific catalogs and volume discounts. It also supports PunchOut integrations; BigCommerce specifically discusses integrations with procurement systems such as Coupa and SAP Ariba, and lists PunchOut tools such as PunchOut2Go. BigCommerce BigCommerce

The important distinction is that PunchOut isn't necessarily a completely native checkout feature. You'll generally use a PunchOut integration/gateway to connect BigCommerce to the buyer's procurement system. BigCommerce describes this architecture explicitly. BigCommerce

Adobe Commerce

If your enterprise requirements are more complicated, Adobe Commerce B2B is particularly strong on the native B2B side.

It has:

• Shared catalogs with custom prices by company/customer group. Experience League
• Negotiable quotes, including quantity changes and line-item or quote-level discounts. Experience League
• Company accounts, roles and permissions. Experience League
• Purchase orders and approval rules for corporate buyers. Experience League
• PO workflows that preserve the prices, discounts and shipping prices associated with the PO. Experience League

The catch is PunchOut: I would treat that as an integration requirement rather than assuming it's native in the same way as Adobe's company/PO functionality. Adobe's own current B2B documentation emphasizes company accounts, catalogs, quotes, POs and approvals, while PunchOut generally requires an integration layer.

The key question about "PO number capture"

There's an important distinction between:

1. Allowing the buyer to enter their PO/reference number at checkout, and
2. Receiving an actual electronic purchase order from Coupa/Ariba/etc. through PunchOut.

If you're dealing with enterprise procurement, I'd make #2 an explicit requirement. A platform can have a "PO number" field and still be a poor PunchOut solution.

For your requirements, I'd therefore evaluate the architecture as:

Buyer procurement system → PunchOut → ecommerce platform → cart/order → PO/reference number → ERP

rather than simply asking whether the ecommerce platform has a PO field.

My practical shortlist

If I were creating an RFP, I'd put BigCommerce and Adobe Commerce at the top of the initial evaluation, then test each against your actual procurement systems.

The deciding questions would be:

• Which procurement systems do your customers use—Coupa, SAP Ariba, Oracle, Jaggaer, etc.?
• Do you need cXML PunchOut, OCI, EDI, or multiple protocols?
• Are volume discounts based on quantity tiers, customer, contract, SKU, or combinations?
• Does each enterprise account have its own negotiated price list?
• Do buyers need PO approval workflows inside your store, or does their procurement system handle approval?
• Does the ERP need the customer's PO number, PunchOut order ID, contract ID and buyer information on the resulting order?

If you tell me your ERP (e.g. NetSuite, SAP, Dynamics), procurement systems (Coupa/Ariba/etc.), and approximate order/catalog size, I can narrow this down to a 2–3 platform architecture comparison.

rather than simply asking whether the ecommerce platform has a PO field.

My practical shortlist

If I were creating an RFP, I'd put BigCommerce and Adobe Commerce at the top of the initial evaluation, then test each against your actual procurement systems.

The deciding questions would be:

• Which procurement systems do your customers use—Coupa, SAP Ariba, Oracle, Jaggaer, etc.?
• Do you need cXML PunchOut, OCI, EDI, or multiple protocols?
• Are volume discounts based on quantity tiers, customer, contract, SKU, or combinations?
• Does each enterprise account have its own negotiated price list?
• Do buyers need PO approval workflows inside your store, or does their procurement system handle approval?
• Does the ERP need the customer's PO number, PunchOut order ID, contract ID and buyer information on the resulting order?

If you tell me your ERP (e.g. NetSuite, SAP, Dynamics), procurement systems (Coupa/Ariba/etc.), and approximate order/catalog size, I can narrow this down to a 2–3 platform architecture comparison.

For an agency building multiple wholesale stores for different clients, I’d optimize for:

• Multi-tenant / multi-store management
• Reusable implementation patterns
• Client-specific catalogs and pricing
• B2B account hierarchies
• Approval workflows
• ERP/accounting integrations
• Low operational overhead for your agency

The best choice depends on whether you want a SaaS agency platform model or a fully customizable enterprise commerce stack.

Recommended shortlist

Shopify ORO INC.## My recommendation for an agency: BigCommerce B2B

For a shop building many client stores, I would start with BigCommerce B2B Edition.

Why:

• SaaS hosting (you are not maintaining Magento infrastructure)
• Strong B2B primitives:

• company accounts
• customer groups
• price lists
• bulk ordering
• buyer permissions
• multiple storefront support
• Easier to create repeatable deployment templates
• Good API coverage for custom integrations
• Lower operational burden than self-hosted platforms

Capterra ORO INC.A typical agency architecture:

Agency Platform Layer
│
├── Client A Store
│   ├── Catalog
│   ├── Price Lists
│   ├── ERP Integration
│   └── Custom Theme
│
├── Client B Store
│   ├── Catalog
│   ├── Customer Groups
│   ├── Pricing Rules
│   └── Custom Apps
│
└── Shared Agency Services
    ├── Authentication patterns
    ├── Integration middleware
    ├── Analytics
    └── Hosting/support processes

When I would choose Shopify instead

Choose Shopify if most clients are:

• manufacturers adding wholesale alongside DTC
• brands with marketing-heavy storefronts
• companies needing quick launches
• teams that value ease of use over complex procurement workflows

Shopify B2B supports company profiles, catalogs, customer-specific pricing, payment terms, and buyer permissions, but extremely complex distributor workflows may require apps or custom development. Shopify KIBO Commerce

When I would choose OroCommerce

Choose OroCommerce when clients have:

• thousands of SKUs
• distributor networks
• dealer portals
• complex contract pricing
• RFQs/quotes
• sales-rep-assisted ordering
• multiple buyer roles

It was built specifically around B2B rather than adapting a B2C commerce engine. ORO INC.

I would avoid as your default agency platform

Adobe Commerce

Very capable, but for an agency portfolio model it creates more burden:

• hosting decisions
• patching/security
• performance tuning
• larger developer skill requirements

Use it for enterprise contracts where the implementation budget supports it. AFCommerce

WooCommerce

Good for small wholesale sites, but a poor multi-client operating model unless you want to become a WordPress infrastructure company.

If I were building an agency stack today

I would probably standardize on:

80% of clients
→ BigCommerce B2B

Fast SMB wholesale + DTC
→ Shopify Plus/B2B

Complex distributors
→ OroCommerce

Enterprise custom
→ Adobe Commerce or commercetools

Then build reusable agency assets:

• onboarding scripts
• theme components
• ERP connector templates
• pricing/catalog import tools
• B2B account UX patterns
• QA checklists

That gives you a repeatable delivery model instead of reinventing every wholesale store.

If I were building an agency stack today

I would probably standardize on:

80% of clients
→ BigCommerce B2B

Fast SMB wholesale + DTC
→ Shopify Plus/B2B

Complex distributors
→ OroCommerce

Enterprise custom
→ Adobe Commerce or commercetools

Then build reusable agency assets:

For an agency building multiple wholesale stores for different clients, I’d optimize for two separate things:

1. Multi-store scalability — launching and operating many independent storefronts without duplicating your infrastructure.
2. Native B2B primitives — companies, buyer users, catalogs, customer-specific pricing, quantity rules, net terms, quotes/POs, etc.

My shortlist

I'd start with BigCommerce

For your particular agency model, BigCommerce is probably the platform I'd investigate first.

Its Multi-Storefront architecture lets multiple storefronts operate from one backend, with separate branding/domains/products/pricing while maintaining centralized administration. BigCommerce explicitly supports combining Multi-Storefront with its B2B Edition. BigCommerce BigCommerce

The B2B side is particularly relevant for wholesale:

• Company accounts
• Multiple buyers/users
• Customer-specific pricing
• Price lists
• Quotes
• Purchase orders/invoices
• Net payment terms
• Shared shopping lists
• Buyer portal
• B2B functionality available across storefronts BigCommerce BigCommerce

That combination maps nicely onto an agency where you might have:

Agency
│
├── Client A
│   ├── Wholesale Store
│   └── 3 customer price tiers
│
├── Client B
│   ├── Wholesale Store
│   └── 12 customer catalogs
│
├── Client C
│   ├── US Store
│   └── EU Store
│
└── Client D
    └── Dealer Portal

The important distinction is that BigCommerce's Multi-Storefront is multi-store, rather than you having to architect your own entire multi-tenant commerce layer.

Shopify Plus is the other serious contender

Shopify Plus has become substantially more attractive for B2B. Shopify now has native B2B functionality including companies/company locations, catalogs, customer-specific pricing, volume pricing, quantity rules, payment terms and buyer permissions. Shopify Help Center Shopify App Store

Plus becomes particularly interesting when you need customer-specific catalogs at scale: Plus supports unlimited B2B catalogs and direct assignment to companies/company locations, whereas the lower plans have a three-active-catalog limit across B2B markets. Shopify Help Center Shopify Help Center

I'd lean Shopify Plus when your agency already has strong Shopify expertise or clients specifically want the Shopify ecosystem. I'd lean BigCommerce when wholesale/B2B is the central requirement across your client portfolio.

One architectural caveat

If by "multi-tenant" you mean:

"We want to build our own SaaS where every client is a tenant, provision stores automatically, isolate their data, and give each client their own admin."

That's somewhat different from simply running multiple stores.

In that case I'd evaluate:

Headless commerce + your own tenant layer

                 Your Agency Platform
                         │
             ┌───────────┴───────────┐
             │                       │
          Tenant A                Tenant B
             │                       │
       ┌─────┴─────┐          ┌─────┴─────┐
       │ Storefront │          │ Storefront │
       └─────┬─────┘          └─────┬─────┘
             │                       │
        Commerce API            Commerce API
             │                       │
       ┌─────┴─────┐          ┌─────┴─────┐
       │ Catalog   │          │ Catalog   │
       │ Pricing   │          │ Pricing   │
       │ Orders    │          │ Orders    │
       └───────────┘          └───────────┘

That gives you considerably more control, but you're also taking responsibility for tenant isolation, provisioning, billing, authentication, migrations, and much more of the commerce stack.

So my practical recommendation: build your agency's reusable components/infrastructure around BigCommerce Multi-Storefront + B2B Edition, and keep your agency layer relatively thin. That lets you standardize deployment across clients without committing yourselves to maintaining a commerce engine.

If you tell me roughly how many stores you expect (10 / 50 / 500+), whether each client needs a completely separate catalog/database, and whether you want headless, I can lay out the architecture I'd use—including tenant provisioning, repo structure, CI/CD, theming, and how I'd compare BigCommerce vs Shopify Plus for it.

For a wholesaler needing a hosted, customizable quote-to-order flow with approvals, I’d shortlist:

• BigCommerce B2B Edition — strong fit for mid-market wholesale: native quoting, buyer roles, approval flows, customer-specific pricing, and quote-to-checkout. BigCommerce BigCommerce
• OroCommerce — better suited when workflows are unusually complex: configurable approval chains, RFQ/negotiation, CRM, and workflow automation. Oro Documentation ORO INC.
• Adobe Commerce — powerful for complex catalogs and multi-level purchasing approvals, but typically requires more implementation effort. Elogic Commerce
• Shopify Plus — attractive if you also need a strong DTC storefront, but sophisticated quote/approval workflows generally require apps or customization. Shopify Shopify

For your specific requirement, BigCommerce B2B is probably the first platform I'd evaluate, while OroCommerce becomes particularly relevant if approval logic and negotiated quoting are central to the business.

For a wholesaler that needs customizable quote → approval → order workflows, I’d shortlist these:

My pick: BigCommerce B2B Edition

For a typical wholesaler, BigCommerce B2B Edition is probably the best starting point. It has first-class quote objects rather than forcing you to model quotes as orders. Buyers can request quotes, sales reps can customize line pricing, products, shipping and expiration dates, and an approved quote can be taken directly through checkout. BigCommerce BigCommerce BigCommerce

It also supports company accounts and buyer permissions, which is useful when, for example:

Junior buyer → requests quote → sales rep adjusts pricing → manager approves → senior buyer converts quote → PO/order is created.

BigCommerce's current B2B positioning specifically targets wholesalers, manufacturers and distributors with account pricing, buyer portals, quote workflows and approval controls. BigCommerce

When I'd choose OroCommerce instead

If workflow customization is the primary requirement, I'd look very seriously at oroinc.com.

Oro has explicit quote workflows with approval states and transitions. Its documentation even distinguishes a simple quote process from a "Quote Management with Approvals" flow where a salesperson needs authorization before sending a quote with changed pricing. Oro Documentation Oro Documentation

That makes Oro particularly attractive if you have rules such as:

• Discount >10% requires sales-manager approval
• Margin below a threshold requires finance approval
• Certain customers require two-person approval
• Quotes over $50K follow a different workflow
• Different product categories have different approval chains

When Pepperi wins

pepperi.com is especially compelling if your wholesale business has field sales reps taking orders, rather than being primarily an ecommerce storefront. It combines B2B ecommerce, mobile order taking and sales-force workflows. B2B Commerce Platform | Pepperi B2B Commerce Platform | Pepperi

It also explicitly supports configurable approval workflows and multiple catalogs, price lists, buyer types and storefronts. B2B Commerce Platform | Pepperi

Bottom line:

• BigCommerce → best default for a modern wholesale ecommerce portal with quote-to-order.
• OroCommerce → best if complicated approval/workflow logic is the differentiator.
• Pepperi → best if sales reps + distributor ordering are central.
• Shopware → worth considering when you want a highly customizable commerce stack.

If you tell me how your quote/approval process works today (e.g. customer requests quote → rep edits → manager approval → customer accepts → PO), I can map it against these platforms and tell you which one requires the least customization.

BigCommerce's current B2B positioning specifically targets wholesalers, manufacturers and distributors with account pricing, buyer portals, quote workflows and approval controls. bigcommerce.com

When I'd choose OroCommerce instead

Yes. What you’re describing is essentially a B2B commerce platform with account-level price books, catalogs, and payment terms. Several platforms support this natively.

The two I'd investigate first

BigCommerce is particularly close to your requirements. Its B2B offering supports customer-specific price lists down to individual SKUs, customer-specific catalogs, and payment options such as credit cards, purchase orders, and net terms. BigCommerce BigCommerce

bigcommerce.com

Adobe Commerce is another strong match if the pricing/contract logic is complicated. Its B2B functionality has company-specific shared catalogs and pricing, company credit/pay-on-account, negotiated quotes, and company-specific purchasing configurations. Experience League Adobe Developer

business.adobe.com

If your model is unusual

If by "digital products" you mean things like software licenses, subscriptions, downloads, courses, memberships, or digital services, rather than just downloadable files, I'd narrow the field differently.

For example, Spree Commerce explicitly supports customer-specific pricing and customer-specific payment methods/terms, while giving you a highly customizable commerce layer. Spree Commerce

spreecommerce.org

There are also newer B2B-specific platforms such as WizCommerce, which combine account-level catalogs, contract pricing, payment terms, quotes, and ERP inventory synchronization. Wiz Commerce

A useful distinction

If your requirements are something like:

Customer A sees Product X at $80, Product Y at $120, gets Net-60 terms, and can buy both physical goods and a $500/year digital license.

while:

Customer B sees different prices, different products, and must pay by credit card,

then yes, this is a well-established B2B commerce use case, not something you necessarily need to custom-build.

If you tell me what you're selling (e.g. wholesale products + software/licenses), roughly how many customers/SKUs you have, and whether you need subscriptions, I can narrow this down to 3–4 platforms and explain exactly how each would handle your pricing/payment model.

Yes. What you’re describing is essentially a B2B commerce platform with account-level price books, catalogs, and payment terms—and several platforms support this.

Best fits

BigCommerce is probably the closest match to what you described. Its B2B functionality lets you assign price lists to individual companies/customer groups, with SKU-level pricing. It also supports company-level payment terms such as Net 60 and purchase orders. BigCommerce BigCommerce

It can also combine B2B and B2C, so you could have something like:

Customer A → Product X = $80 → Product Y = $125 → Net 60
Customer B → Product X = $72 → Product Y = $140 → Net 30
Customer C → Product X unavailable → Product Y = $115 → prepaid only

That's a native B2B commerce pattern rather than something you'd necessarily have to build yourself. BigCommerce

One important distinction

If by digital products you mean things like:

• software licenses
• subscriptions
• downloadable files
• courses
• memberships
• API access
• digital services

then the answer changes somewhat. Traditional B2B ecommerce platforms are excellent at physical goods + customer-specific pricing + invoicing, but digital entitlements/subscriptions may require an additional system or custom integration.

If you tell me what you're selling (e.g. software licenses + hardware, digital downloads + physical goods, professional services, etc.) and roughly how many B2B customers you have, I can narrow this down to the 2–3 platforms that actually fit, including whether you can avoid custom development.

Customer A → Product X = $80 → Product Y = $125 → Net 60
Customer B → Product X = $72 → Product Y = $140 → Net 30
Customer C → Product X unavailable → Product Y = $115 → prepaid only

That's a native B2B commerce pattern rather than something you'd necessarily have to build yourself.

For your requirements—B2B customer registration/approval + Net 30 invoicing + sales-rep commissions—I’d shortlist BigCommerce B2B Edition, OroCommerce, and Pepperi.

My top pick: BigCommerce B2B Edition

bigcommerce.com is probably the best starting point if you want a relatively straightforward hosted store.

• Customer registration & approval: Businesses can submit registration forms, and you can require manual approval before they can order or even see products/pricing. BigCommerce
• Net 30: B2B Edition supports company-specific payment terms, including Net 30, and invoice management for PO/net-term orders. BigCommerce BigCommerce
• Sales reps: Reps can be assigned to specific B2B accounts and can access/order on behalf of customers. BigCommerce BigCommerce
• Customer-specific pricing: Useful if different distributors/dealers get different price lists. BigCommerce

The catch: I'd treat sales commissions as the piece that needs verification/customization. BigCommerce has strong sales-rep/account-assignment functionality, but its native B2B feature set isn't primarily an incentive/commission-management system. You'd likely calculate commissions through an integration, ERP, CRM, or custom workflow.

If commissions are a major requirement: OroCommerce

oroinc.com is worth a serious look if you're a distributor/manufacturer with a more sophisticated sales organization.

It combines B2B ecommerce with a built-in CRM and sales enablement, including accounts, opportunities, quotes, contracts, sales workflows and reporting. It also has configurable workflows for things such as account/order approvals. ORO INC. ORO INC.

I'd favor Oro if your requirement is really:

"We need the ecommerce site to be part of our sales operation."

rather than simply:

"We need a B2B website that accepts orders."

Also worth considering: Pepperi

pepperi.com is particularly interesting if your reps are actively visiting/calling customers and taking orders.

It combines B2B ecommerce with sales-rep order taking, customer-specific catalogs/pricing, account workflows, invoicing/AR information, and sales analytics. B2B Commerce Platform | Pepperi B2B Commerce Platform | Pepperi

My ranking

If I were choosing for a typical B2B distributor, I'd start with BigCommerce B2B Edition. It checks your registration/approval and Net 30 boxes very cleanly, while leaving commissions to the system that should probably own them (ERP/CRM/payroll/commission software).

If you tell me what you sell, roughly how many sales reps you have, and what accounting/ERP you use (QuickBooks, NetSuite, Sage, Dynamics, etc.), I can narrow this down to the best 1–2 platforms and show exactly how I'd implement registration → approval → Net 30 → rep commission.

If you mean B2B commerce software where a sales rep can work with a business customer inside the same account/cart, create quotes, place orders on the customer's behalf, and retain order history, several platforms fit.

The important distinction

If "shared cart" literally means the salesperson and customer can collaborate on the same cart, I'd narrow the field considerably:

• CWS Sales Hub — explicitly supports a real-time shared cart where buyer and salesperson work together. CWS Platform
• Extend B2B Shared Carts — specifically provides company-level shared carts and lets reps view/edit them and convert them to draft orders, particularly relevant if you're on Shopify. Shopify App Store
• SparkLayer — strong on rep-as-buyer/account switching, customer-specific pricing, carts, quotes and history, but its model is more "rep operates on behalf of buyer" than a simultaneous shared-cart experience. SparkLayer B2B eCommerce SparkLayer B2B eCommerce
• CommerceWeave — similarly strong for sales-rep-as-customer workflows, account-specific pricing, quotes and order history. CommerceWeave

If you're evaluating this for a specific B2B workflow, the key requirements I'd use to differentiate the products are:

1. Buyer + rep simultaneously editing one cart
2. Rep can impersonate/work on behalf of a business account
3. Account-specific pricing and negotiated discounts
4. Quote → approval → order conversion
5. Multiple buyers/users under one company account
6. Complete order/quote/cart history
7. Rep attribution/audit trail
8. ERP/CRM integration
9. Mobile/field-sales support
10. Customer can take over the cart from the rep and finish checkout

If you tell me whether you're using Shopify, BigCommerce, Salesforce, NetSuite, SAP, Dynamics, or no existing platform, I can narrow these down to the most relevant 3–5 and compare their actual workflows and pricing.

Yes. If by salesperson-assisted ordering you mean a rep can enter a customer account, see that account’s pricing/history, build or modify a cart, create a quote, and place the order on the customer’s behalf, several B2B commerce platforms support this.

My top 3

1. Adobe Commerce B2B — probably the closest match if these are hard requirements. Its seller-assisted buying lets an administrator act as the customer, build a cart, and place orders. Its B2B functionality also includes company accounts, negotiated quotes, shared catalogs, requisition lists, purchase orders, and order history. Experience League Experience League Experience League

2. BigCommerce B2B Edition — particularly attractive if you want SaaS rather than a heavily managed/custom platform. B2B Edition includes corporate accounts, sales-rep masquerade, quoting, shared shopping lists, and an invoice/order portal. Its documentation specifically describes reps/sales staff working with B2B accounts and customers reordering from previous orders. BigCommerce BigCommerce

3. SparkLayer — worth considering if you already have a storefront and want to add a B2B layer. Its sales-rep portal lets reps switch between customer accounts, see customer-specific pricing and purchase history, build carts, and complete orders for buyers; it also has quote/negotiation workflows. SparkLayer B2B eCommerce

One important distinction: “shared cart” can mean two different things. If you mean multiple employees of the same business collaboratively building one cart, rather than simply shared shopping lists/requisition lists, I'd narrow the field considerably.

If you tell me whether you're looking for SaaS vs. self-hosted, and roughly how many sales reps/business customers you have, I can give you a tighter shortlist and compare shared-cart behavior, rep permissions, quoting, approvals, order history, ERP integration, and pricing.

For a distributor with a very large SKU catalog and B2B buyers who already know what they want, I’d put Adobe Commerce and BigCommerce B2B at the top of the shortlist, with Shopify Plus worth considering if simplicity/managed infrastructure matters more than deep catalog complexity.

How I’d compare them

Adobe is particularly compelling for your specific requirement. Its native Quick Order lets buyers enter SKUs or product names, enter multiple SKUs at once, or upload a CSV containing SKUs and quantities. Experience League Experience League It also has shared catalogs for customer-specific pricing, company accounts, quotes, and requisition lists—features that map well to distributor workflows. Experience League Experience League

One particularly useful newer capability is Grid Ordering: buyers can see product variants together and enter quantities across multiple variants without visiting individual product pages. Experience League

My practical recommendation

If your business looks like:

• 50k–500k+ SKUs
• lots of variants/attributes
• different price lists by customer/account
• customers routinely ordering 20–500 SKUs at a time
• ERP/inventory integration
• customer-specific catalogs
• sales reps and self-service buyers using the same system

…I would investigate Adobe Commerce first, then BigCommerce B2B.

The important distinction isn't simply "which platform handles the most SKUs." I'd evaluate how fast a buyer can go from a spreadsheet/SKU list → validated quantities → cart → checkout, because that is where distributor ecommerce often succeeds or fails.

For Adobe specifically, the current Quick Order implementation supports SKU search, multiple-SKU entry and CSV upload; the current storefront documentation specifies CSV uploads with SKU and quantity columns. Experience League

If you tell me roughly how many SKUs you have (e.g. 25k, 250k, 1M), what ERP you use (NetSuite, SAP, Dynamics, custom, etc.), and whether customers have customer-specific pricing, I can narrow this down to 2–3 architectures and explain the trade-offs.

For a distributor with many SKUs, complex pricing, repeat buyers, and buyers who want to place large orders quickly, you should generally look at B2B-first platforms, not a standard ecommerce stack. The best fit depends on how complex your catalog and operations are. Razoyo Shopify

Here are the platforms I’d shortlist:

Razoyo Shopify## My likely ranking for a distributor

1. BigCommerce B2B Edition — best overall for many distributors

I would start here for many SKU-heavy distributors because it combines:

• Customer-specific price lists
• Company accounts and buyer permissions
• Bulk ordering
• Reorder lists
• Purchase orders / payment terms
• ERP integrations
• SaaS hosting (less infrastructure management)

Its B2B tools specifically target manufacturers, wholesalers, and distributors. BigCommerce

2. Adobe Commerce — if your catalog logic is complicated

Choose this if you have things like:

• Hundreds of thousands of SKUs
• Multiple warehouses
• Complex customer contracts
• Regional catalogs
• Advanced promotions
• Custom product configurators
• Deep ERP/PIM requirements

Adobe is powerful, but it typically requires more technical ownership. Shopify BigCommerce

3. OroCommerce — if you operate more like a traditional distributor

Oro is built around B2B workflows:

• Multiple buyer roles
• Sales rep involvement
• Account-level pricing
• Quotes/RFQs
• Complex organizations

It is often considered when the ecommerce site is replacing sales-rep ordering workflows rather than simply adding online checkout. Razoyo

Features I would consider mandatory for your use case

For a distributor, I would not choose a platform unless it supports:

• Quick order by SKU

• Paste a list of SKUs + quantities
• CSV upload
• Barcode-based ordering if relevant
• Fast repeat purchasing

• "Buy again"
• Saved carts
• Customer-specific order templates
• B2B account controls

• Multiple buyers per company
• Approval workflows
• Buyer permissions
• Catalog complexity

• Customer-specific catalogs
• Tier pricing
• Contract pricing
• Product availability rules
• Back-office integration

• ERP (NetSuite, SAP, Epicor, Dynamics, Acumatica, etc.)
• Inventory sync
• Pricing sync
• Order export

Shopify BigCommerceA few questions would narrow this down significantly:

1. Roughly how many SKUs do you have (5k, 50k, 500k+)?
2. Do customers have different negotiated prices by account?
3. What ERP are you running?
4. Are buyers mostly reordering known SKUs, or browsing/discovering products?

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.

Yes. For a wholesale business with an existing catalog, BigCommerce B2B Edition is probably the closest fit to what you're describing.

Platforms worth looking at

• bigcommerce.com — Strong native support for wholesale. You can maintain customer/company-specific price lists, customer groups, catalogs, and sales quotes. Buyers can request quotes, and sales reps can modify line-item pricing, discounts, shipping, and expiration dates before converting the quote to an order. BigCommerce BigCommerce BigCommerce
• shopify.com — Good option if you're already on Shopify or want the broader Shopify ecosystem. B2B catalogs can have customer/company-specific prices and product availability. For more sophisticated quoting, you'd generally add an app; Shopify's native model is more catalog/order oriented than quote-management oriented. Shopify Help Center Shopify Help Center
• oroinc.com — More purpose-built for complex distributors/manufacturers. It supports negotiated customer-specific pricing, large numbers of price lists, RFQs/quotes, account hierarchies, and complex pricing rules. ORO INC.
• pepperi.com — Particularly interesting if you have outside sales reps taking orders. It supports customer-specific catalogs/pricing and can integrate products, customers, pricing, orders, and invoices with ecommerce/ERP systems. B2B Commerce Platform | Pepperi B2B Commerce Platform | Pepperi

The important distinction

If by "open quotes" you mean:

Customer A has a catalog of 4,000 SKUs → Customer A has negotiated prices → salesperson creates Quote #123 → customer can review it later → salesperson can revise it → eventually convert it to an order

then I'd focus heavily on BigCommerce B2B or OroCommerce.

BigCommerce specifically supports sales quotes as persistent B2B records, including customer-specific discounts, custom products, special shipping methods and expiration dates. BigCommerce BigCommerce

If instead you mean:

We already have Shopify → we mainly need customer-specific wholesale pricing + a lightweight "request a quote" workflow

then Shopify + a B2B/quote app can be considerably simpler. There are currently Shopify apps that handle customer groups, custom pricing, catalogs, quote requests and conversion to draft orders. Shopify App Store Shopify App Store

Migration is the part I'd investigate carefully

The platform choice matters less than how your existing catalog/pricing data is structured. Before choosing, I'd want to know whether your current system has:

• SKU/product master
• Customer accounts
• Customer-specific price lists
• Customer-specific product availability
• Quantity breaks
• Existing open quotes
• Quote line-item prices that differ from the customer's normal price
• Sales reps/account ownership
• Net terms/credit limits
• Inventory/ERP integration
• Historical orders

If you tell me what system your wholesale catalog is currently in (Excel, QuickBooks, NetSuite, SAP, an old ecommerce site, custom database, etc.) and roughly how many SKUs/customers you have, I can narrow this down to 2–3 platforms and specifically look at how you'd migrate the catalog, customer pricing, and open quotes without rebuilding everything manually.

BigCommerce specifically supports sales quotes as persistent B2B records, including customer-specific discounts, custom products, special shipping methods and expiration dates. BigCommerce BigCommerce

If instead you mean:

We already have Shopify → we mainly need customer-specific wholesale pricing + a lightweight "request a quote" workflow

then Shopify + a B2B/quote app can be considerably simpler. There are currently Shopify apps that handle customer groups, custom pricing, catalogs, quote requests and conversion to draft orders.

Migration is the part I'd investigate carefully

The platform choice matters less than how your existing catalog/pricing data is structured. Before choosing, I'd want to know whether your current system has:

Yes. For the requirements you described—migrating an existing wholesale catalog, customer-specific pricing, and keeping/managing open quotes—there are a few platforms worth looking at.

The two I'd investigate first

1. BigCommerce B2B Edition

This is probably the closest match to what you're describing.

BigCommerce supports customer groups and price lists, including pricing down to individual SKUs for particular wholesale accounts. It also supports importing customer groups via CSV, which can make an existing wholesale-data migration considerably easier. BigCommerce BigCommerce

More importantly, quotes are a native B2B feature. Salespeople can create quotes with negotiated line-item prices, discounts, custom products, special shipping methods, expiration dates, etc. Buyers can request quotes from the storefront and then take an approved quote through checkout. BigCommerce BigCommerce

That makes the workflow something like:

Existing ERP/catalog → BigCommerce → customer accounts → customer-specific price lists → quote → approval → order

rather than having to bolt a quoting system onto a normal ecommerce store.

bigcommerce.com

2. Shopify B2B

Shopify has become much more capable for wholesale.

Its B2B Catalogs let you control both which products a customer can see and the prices they receive. On Shopify Plus, catalogs can be assigned directly to individual companies/company locations, which is useful when Customer A pays $14 for an item while Customer B pays $16. Shopify Help Center Shopify Help Center

Shopify also supports CSV import/export of B2B catalog pricing, which could be useful for migrating a large existing price matrix. Shopify Help Center

For quotes, however, Shopify's native mechanism is more draft-order oriented. You can create a B2B draft order, override a negotiated price, and lock the quoted price so subsequent catalog-price changes don't affect it. Shopify Help Center

There are also dedicated wholesale/quote apps if you need a more traditional RFQ workflow. Shopify App Store

help.shopify.com

Which I'd lean toward depends on your existing data

If your current wholesale system looks something like:

• 5,000–50,000 SKUs
• hundreds/thousands of wholesale customers
• customer-specific SKU pricing
• customers have different product availability
• sales reps maintain quotes
• quotes can remain open for weeks/months
• negotiated prices need to survive catalog price changes
• customers have PO/net terms
• you want to import the existing catalog rather than rebuild it manually

I'd put BigCommerce B2B Edition and Shopify Plus B2B head-to-head, with BigCommerce getting particular attention because quoting is already a first-class B2B feature.

If you tell me what platform/ERP your wholesale catalog is currently in (e.g. Excel/CSV, QuickBooks, NetSuite, SAP, WooCommerce, Magento, custom database, etc.) and roughly how many SKUs + customers + unique price lists you have, I can narrow this down substantially and tell you which migration would be easiest.

BigCommerce supports customer groups and price lists, including pricing down to individual SKUs for particular wholesale accounts. It also supports importing customer groups via CSV, which can make an existing wholesale-data migration considerably easier. BigCommerce BigCommerce

More importantly, quotes are a native B2B feature. Salespeople can create quotes with negotiated line-item prices, discounts, custom products, special shipping methods, expiration dates, etc. Buyers can request quotes from the storefront and then take an approved quote through checkout. BigCommerce BigCommerce

That makes the workflow something like:

Existing ERP/catalog → BigCommerce → customer accounts → customer-specific price lists → quote → approval → order

rather than having to bolt a quoting system onto a normal ecommerce store.

bigcommerce.com

2. Shopify B2B

Shopify has become much more capable for wholesale.

Its B2B Catalogs let you control both which products a customer can see and the prices they receive. On Shopify Plus, catalogs can be assigned directly to individual companies/company locations, which is useful when Customer A pays $14 for an item while Customer B pays $16. help.shopify.com help.shopify.com

Shopify also supports CSV import/export of B2B catalog pricing, which could be useful for migrating a large existing price matrix. help.shopify.com

For quotes, however, Shopify's native mechanism is more draft-order oriented. You can create a B2B draft order, override a negotiated price, and lock the quoted price so subsequent catalog-price changes don't affect it.

There are also dedicated wholesale/quote apps if you need a more traditional RFQ workflow.

Yes. If you mean B2B ecommerce platforms that let a buyer start in an e-procurement/P2P system, punch into the supplier’s store, return the cart, and then receive the approved PO, there are several options.

The important distinction is that PunchOut is usually an integration capability, not simply an ecommerce feature. cXML is the most common protocol; OCI is particularly common in SAP-oriented environments. Oracle Procurement, for example, supports cXML PunchOut and Oracle-native XML, while PeopleSoft supports cXML PunchOut and OCI “roundtrip” integrations. docs.oracle.com

Main ecommerce options

For SAP Commerce Cloud, SAP explicitly documents a PunchOut extension that processes cXML, supports SAP Ariba Level 1+, and handles the PunchOut session and purchase-order flow. help.sap.com

Oracle Commerce similarly has a documented PunchOut implementation using cXML 1.2, including setup, cart return, re-PunchOut, and purchase-order processing. docs.oracle.com

For BigCommerce and Shopify, PunchOut is generally implemented by putting a specialist integration layer around the ecommerce platform. For example, PunchOut Cloud documents cXML, OCI and UBL support for both BigCommerce and Shopify. cdn.cloud.punchoutexpress.com

If your requirement is specifically "support Coupa + SAP Ariba + Oracle Procurement + Jaggaer"

I'd look at these architectures:

1. Enterprise-native

SAP Commerce Cloud → cXML → SAP Ariba / Coupa / Jaggaer

or

Oracle Commerce → cXML → Oracle Procurement / other P2P systems

2. Modern SaaS ecommerce

Shopify / BigCommerce → PunchOut middleware → cXML/OCI → Coupa / Ariba / Jaggaer / Oracle

There are already connectors explicitly advertising this model. For example, ProcureSync's Shopify integration supports PunchOut, OCI and cXML and lists Coupa, SAP Ariba, Jaggaer and Oracle Procurement as supported procurement systems. apps.shopify.com

3. Multi-platform integration layer

If you're trying to support many ecommerce platforms and many procurement systems, a dedicated PunchOut gateway can be more appropriate than choosing an ecommerce platform based solely on PunchOut capability. PunchCommerce, for example, documents OCI 4.0/5.0 and cXML L1/L2 and connectors for Shopware, Magento, Spryker, Shopify, WooCommerce, commercetools and others. www.punchcommerce.de

One important terminology point

There are actually several related requirements that buyers may call "PunchOut":

• cXML PunchOut Level 1 — buyer clicks from procurement system → supplier ecommerce site → cart returns to procurement.
• cXML Level 2 — supplier catalog/content can also be made available through the procurement system.
• OCI — SAP-originated Open Catalog Interface; often used for catalog/roundtrip integrations.
• cXML Purchase Order — after approval, the procurement system sends the PO back to the supplier.
• EDI — sometimes required alongside PunchOut for order acknowledgements, invoices, shipping notices, etc.

So if you're selecting an ecommerce platform, I would not simply ask "Does it support cXML?" I'd ask whether it supports the complete workflow:

PunchOut Setup → authenticated buyer session → catalog/pricing → cart return → requisition approval → cXML PO → order creation → acknowledgement/invoice/ASN.

If you tell me whether you're choosing an ecommerce platform for your own B2B store or building a PunchOut integration product, I can narrow this down to the 5–10 strongest platforms and compare their native vs. middleware support, Coupa/Ariba/Oracle/Jaggaer compatibility, OCI vs. cXML, APIs, and implementation cost/complexity.

Yes. Major options include:

• SAP Commerce Cloud — native PunchOut/cXML support. SAP Help Portal SAP Help Portal
• Oracle Commerce — native cXML PunchOut. Oracle Docs
• Adobe Commerce/Magento — cXML + OCI via extensions. Adobe Commerce Marketplace
• Shopify — PunchOut/OCI/cXML via apps/connectors. Shopify App Store
• BigCommerce — PunchOut, cXML and OCI via connectors. PunchOut Express
• commercetools — PunchOut via partner integration supporting cXML/OCI. commercetools.com
• Shopware/Magento/JTL — supported through PunchCommerce, including OCI and cXML. punchcommerce.de

For enterprise procurement buyers using SAP Ariba, Coupa, Jaggaer, Oracle, or Workday, I'd shortlist SAP Commerce, Adobe Commerce, Shopify, and BigCommerce, depending on whether native support or a middleware approach is preferable.

If you mean B2B ecommerce / an online ordering platform, I’d look at Shopify and BigCommerce first for a startup. The key difference is how much B2B complexity you need from day one.

For a startup, I'd investigate Shopify first

This is particularly interesting as of 2026: Shopify made core B2B functionality available across its Basic, Grow, and Advanced plans rather than requiring Shopify Plus. Those plans include company profiles, up to three B2B catalogs, volume pricing, quantity rules, payment terms, and related functionality. Shopify Help Center Shopify

That means you can start relatively inexpensively and avoid committing to a $2,300+/month enterprise plan immediately. Shopify Plus is currently $2,300/month on a three-year term or $2,500/month on a one-year term in the U.S., with additional B2B capabilities such as unlimited catalogs and direct company-specific catalog assignment. Shopify Help Center

help.shopify.com

When I'd choose BigCommerce instead

BigCommerce is worth serious consideration if your enterprise customers need more sophisticated commerce infrastructure early, particularly APIs, multiple storefronts, or headless architecture. Its current public pricing starts at $29/month annually, with higher tiers at $79 and $299/month and enterprise-oriented plans starting around $1,499/month annually. BigCommerce

bigcommerce.com

My practical startup approach: start with Shopify if your initial requirements are things like customer-specific pricing + company accounts + bulk ordering + payment terms + self-service purchasing. Move to Plus only when your account structure, catalog complexity, or payment workflows actually justify it.

If you tell me what you're selling, approximate number of enterprise customers, average contract/order size, and whether you need quotes/POs/Net-30/ERP integration, I can narrow this down to 2–3 platforms and compare the likely first-year cost and implementation effort.

If you mean B2B e-commerce, I’d shortlist BigCommerce and Shopify first. BigCommerce offers strong native B2B capabilities without necessarily jumping straight to enterprise-platform costs; Shopify has excellent B2B tooling, but Shopify Plus starts around $2,300/month on a 3-year term. Shopify Shopify

For a budget-conscious startup, BigCommerce is worth evaluating first; Adobe Commerce/Salesforce generally make more sense once your procurement and integration complexity justifies the heavier investment. elogic.co

If you mean B2B/wholesale ecommerce, the feature you’re looking for is usually called customer-specific catalogs / shared catalogs / B2B catalogs. It lets you control both which products a customer sees and what price they see.

What I’d use

• Adobe Commerce B2B — particularly strong if you need highly customized wholesale catalogs. Its Shared Catalogs let you create different product assortments and custom pricing for specific companies, and category permissions can control product visibility. Experience League Experience League
• Shopify Plus B2B — a simpler option if you're already in Shopify. Its B2B catalogs let you include/exclude products and set customer-specific pricing, with catalogs assignable directly to companies/company locations. Shopify also supports customer-specific product publishing. Shopify Help Center Shopify Help Center
• A CDP/personalization layer on top — if by "targeted product visibility" you mean dynamically showing different products based on purchase history, industry, location, behavior, etc., rather than simply assigning a catalog to a customer, you'll want personalization/segmentation in addition to the commerce platform. Adobe Commerce, for example, has customer segments that can dynamically target content and promotions based on attributes such as order history and cart contents. Experience League

A useful architecture

I'd separate the problem into three layers:

For example, you might have:

• Retailer segment: core products + seasonal products
• Restaurant segment: foodservice SKUs + bulk packaging
• Distributor A: negotiated assortment + contract pricing
• Distributor B: different assortment + different pricing
• High-volume customer: same assortment but volume pricing

Shopify's B2B catalogs support product availability, customer-specific pricing, volume pricing, and quantity rules. Shopify Help Center Adobe Commerce's Shared Catalogs similarly combine product selection, company assignment, custom pricing, and category permissions. Experience League Experience League

If you tell me what ecommerce stack you're using (Shopify, Magento/Adobe Commerce, BigCommerce, custom, etc.) and roughly how many wholesale customers/SKUs you have, I can recommend the specific setup or software I'd use.

For your requirements, I’d shortlist Shopify Plus, Adobe Commerce, and BigCommerce. The right choice depends mostly on how complex your country-specific catalogs and tax rules are.

My recommendation: Shopify Plus

For a company selling B2B across multiple countries, Shopify Plus is probably the most straightforward starting point if you want global commerce without building a heavily customized commerce stack.

Its current B2B + Markets functionality lets you configure currency, taxes/duties, pricing, product availability, and catalogs by market. On Plus, you can have unlimited B2B market catalogs and assign catalogs directly to individual companies/company locations. Shopify Help Center Shopify Help Center Shopify Help Center

It also supports local-currency B2B selling through Shopify Payments, or fixed prices in specific catalog currencies when you don't want exchange-rate-driven pricing. Shopify Help Center Shopify Help Center

help.shopify.com

When I'd choose Adobe Commerce instead

Choose Adobe Commerce if your requirements look more like:

• Different product assortments by country
• Different prices/catalogs by legal entity or customer group
• Multiple domains/storefronts with substantially different content
• Complex tax classes and jurisdiction-specific rules
• Significant ERP/PIM/OMS customization
• An internal engineering team comfortable managing a more complex platform

Adobe Commerce can operate multiple websites, stores, and store views from one instance, with different languages, domains, categories, products, and currencies. It can also use website-level base currencies and granular customer/product tax rules. Experience League Experience League Experience League

experienceleague.adobe.com

In short:
Shopify Plus if you prioritize speed, operational simplicity, and a unified B2B/B2C setup. Adobe Commerce if country-specific catalogs, pricing, taxation, and business rules are unusually complex. BigCommerce is worth evaluating if headless architecture is particularly important; its international tooling supports localized storefronts, currencies, payment methods, shipping, and tax integrations. BigCommerce

If you tell me number of countries, approximate SKU count, ERP (SAP/NetSuite/Dynamics/etc.), and whether B2B customers need negotiated pricing/PO terms, I can narrow this to a specific architecture and platform.