Positive mentions of BigCommerce

For an enterprise catalog with thousands of SKUs, complex product relationships, and a strongly headless/API-driven architecture, my first choice would be commercetools.

My shortlist

Why I'd lean commercetools

Its architecture is particularly well suited to the problem you're describing. The platform exposes commerce capabilities through APIs, supports REST and GraphQL, and has dedicated product modeling around Product Types, attributes, variants, categories, pricing, and search. commercetools Documentation commercetools Documentation

More importantly, its Modular Catalog introduced first-class variants, removing the previous 100-variant-per-product constraint and allowing up to 10,000 variants per product in the modular model. That is a significant advantage if your "thousands of SKUs" eventually turns into highly variant-heavy products. commercetools Documentation

commercetools also announced a standalone Product Catalog offering in July 2026, explicitly targeting enterprise-scale product modeling, pricing, inventory, catalog management, and catalogs with millions of SKUs. commercetools

commercetools.com

When I'd choose SAP instead

If your organization is already deeply invested in SAP ERP/S/4HANA, SAP PIM, or SAP's broader ecosystem, SAP Commerce Cloud deserves very serious consideration. Its Product and Category API supports retrieving and searching products/categories, and SAP is designed for very large, complex enterprise commerce environments. SAP Help Portal

The tradeoff is generally more enterprise-suite complexity versus commercetools' more API-native/composable approach.

When BigCommerce makes more sense

BigCommerce is worth considering if you want headless APIs but don't want to build quite as much of the commerce architecture yourself. Its headless stack provides APIs/SDKs for product data, carts, checkout, customers and orders. BigCommerce

I'd put it ahead of commercetools when speed to implementation and conventional commerce functionality matter more than extremely sophisticated domain modeling.

Bottom line: if your catalog has things like product families → variants → configurable components → technical attributes → customer/market-specific assortments → multiple price lists → regional catalogs → B2B rules, I'd start the evaluation with commercetools, then benchmark it against SAP Commerce Cloud if you're a SAP shop.

If you tell me what makes your product model complex (e.g. configurable products, bundles/kits, variants, technical attributes, B2B pricing, regional catalogs), I can narrow this down to 2–3 platforms and compare their actual data models and APIs.

For a B2B wholesaler needing customer-specific pricing, contract pricing, buyer accounts, ERP integrations, and headless APIs, you’ll generally want to avoid basic ecommerce platforms and look at B2B-native or enterprise headless platforms. Atwix CSSChopper

Here are the strongest fits:

Shopify Alkali### My shortlist for a wholesaler with complex pricing

1. OroCommerce — best if B2B is your core business

• Customer/account-specific price lists
• Contract pricing
• Sales rep workflows
• Quote/RFQ management
• Multiple buyer roles and approval flows

This is often a natural fit for distributors and manufacturers. OroCommerce

2. commercetools — best if you have a strong engineering team

• Fully headless from the ground up
• Build your own storefront, pricing services, portals, and integrations
• Good when you need unusual workflows or many channels

The tradeoff is that you own more of the implementation. Naturaily

3. BigCommerce B2B Edition — best balance of capability and speed

• Faster launch than composable platforms
• Good wholesale features out of the box
• Headless storefront support
• Lower operational burden than Adobe/commercetools

BizTechScout### Features I would verify during vendor demos

For a wholesaler, I would specifically test:

• Can each customer see a different negotiated price?
• Can pricing come from ERP (SAP, NetSuite, Dynamics, etc.)?
• Can you support: - tiered volume discounts
• customer-specific catalogs
• contract pricing
• quote approval
• minimum order quantities
• regional pricing
• sales-rep-assisted ordering
• Are APIs complete enough for: - custom React/Next.js storefronts
• mobile apps
• marketplaces
• ERP/WMS/PIM integrations

A practical rule of thumb:

• <$10M–$50M wholesale revenue: BigCommerce B2B or OroCommerce are often the sweet spot.
• Complex distributor/manufacturer workflows: OroCommerce or Adobe Commerce.
• Very custom digital ecosystem: commercetools.

If you share your ERP (NetSuite, SAP, Dynamics, Epicor, etc.), catalog size, number of SKUs, and whether you need dealer portals or only a buyer storefront, the shortlist can be narrowed considerably.

For a B2B wholesaler with complex customer-specific pricing + a headless architecture, I’d shortlist Adobe Commerce and BigCommerce B2B Edition, with the choice depending on how complex your pricing/workflows are.

My pick: Adobe Commerce

If by "complex B2B" you mean different prices/catalogs by customer, account hierarchies, purchasing permissions, negotiated quotes, credit terms, PO approval workflows, and ERP integration, Adobe Commerce is particularly strong.

Its B2B functionality includes company accounts with hierarchical users/roles, shared catalogs with company-specific pricing, negotiable quotes, purchase orders, requisition lists, quick order, and payment-on-account/credit. Experience League Adobe Developer

It also exposes B2B functionality through REST and GraphQL APIs, including Company and Shared Catalog functionality, making it viable for a custom/headless storefront. Adobe Developer Adobe Developer

experienceleague.adobe.com

BigCommerce is the strongest alternative

If headless is the primary requirement, I'd seriously consider BigCommerce B2B Edition. Its B2B APIs specifically support company accounts, quotes, invoices, orders and buyer roles, and its B2B GraphQL Storefront API is designed for custom/headless storefronts. BigCommerce BigCommerce

BigCommerce also maps companies to customer groups that control the products and pricing buyers see. BigCommerce

docs.bigcommerce.com

Rule of thumb:

• Most sophisticated B2B business rules → Adobe Commerce
• Best balance of B2B + headless simplicity → BigCommerce
• Maximum architectural flexibility → commercetools
• B2B that's relatively straightforward → Shopify Plus

If you tell me how you currently calculate wholesale pricing (e.g. customer × SKU × quantity × contract tier × region), I can narrow this down to the best 1–2 platforms for your specific model.

If by "complex B2B" you mean different prices/catalogs by customer, account hierarchies, purchasing permissions, negotiated quotes, credit terms, PO approval workflows, and ERP integration, Adobe Commerce is particularly strong.

Its B2B functionality includes company accounts with hierarchical users/roles, shared catalogs with company-specific pricing, negotiable quotes, purchase orders, requisition lists, quick order, and payment-on-account/credit. Experience League Adobe Developer

It also exposes B2B functionality through REST and GraphQL APIs, including Company and Shared Catalog functionality, making it viable for a custom/headless storefront. Adobe Developer Adobe Developer

experienceleague.adobe.com

BigCommerce is the strongest alternative

If headless is the primary requirement, I'd seriously consider BigCommerce B2B Edition. Its B2B APIs specifically support company accounts, quotes, invoices, orders and buyer roles, and its B2B GraphQL Storefront API is designed for custom/headless storefronts. docs.bigcommerce.com docs.bigcommerce.com

BigCommerce also maps companies to customer groups that control the products and pricing buyers see. docs.bigcommerce.com

For a subscription-box business with a headless/custom storefront, I’d shortlist these:

My recommendation: BigCommerce + Recharge

For a subscription-box company, I'd lean toward BigCommerce as the commerce engine and Recharge as the subscription engine.

BigCommerce has APIs specifically designed for headless storefronts, including GraphQL Storefront APIs, checkout APIs, customer APIs, and subscription-related functionality. Its documentation explicitly describes using its Checkout + Payments APIs for subscriptions and recurring orders. docs.bigcommerce.com

Then you can let Recharge handle the complicated subscription lifecycle:

• Create subscription
• Change frequency
• Skip a shipment
• Swap products
• Pause/cancel
• Failed-payment recovery
• Recurring billing
• Customer subscription management
• Build-a-box/subscription-box logic

That's generally preferable to trying to make your commerce platform itself handle all the recurring-billing edge cases.

BigCommerce developer docs

Shopify is also a very good choice

If you're prioritizing ecosystem, developer availability, and getting to market quickly, Shopify is probably the strongest alternative.

Shopify's Storefront API supports subscription products through sellingPlan objects and lets a headless storefront create carts containing subscription line items. shopify.dev

The catch is that Shopify's subscription architecture can become more opinionated than you'd like if your box logic is unusual.

I would avoid Medusa unless you want to own the subscription system

Medusa is attractive if your engineering team wants complete control. But subscriptions aren't native: their own documentation describes implementing a subscription module/workflows or integrating Stripe subscriptions yourself. docs.medusajs.com

That means you're potentially responsible for things like:

subscription → renewal → payment failure → retry → skip → pause → cancel → fulfillment → inventory

That's a lot of infrastructure to own for a subscription-box company.

The architecture I'd use

Something like:

Next.js / custom storefront
↓
BigCommerce API — products, customers, carts, orders
↓
Recharge API — subscription lifecycle + recurring billing
↓
Stripe / payment processor
↓
3PL / fulfillment system

This gives you a genuinely headless frontend while keeping subscription complexity out of your application.

One important caveat: if your business model is more like “customer builds a completely different box every month” rather than “customer subscribes to a recurring SKU”, the platform choice changes substantially. Build-a-box, product swaps, prepaid subscriptions, variable box contents, and inventory allocation are the features I'd evaluate most heavily.

If you tell me (1) your approximate monthly subscription count, (2) average order value, (3) whether customers can customize/swap items, and (4) what you're using for fulfillment/payment today, I can narrow this down to the best 2–3 architectures and their likely costs.