Positive mentions of BigCommerce

For a small clothing brand, I’d optimize for the combination of:

1. Low operational burden (you don’t want to babysit servers)
2. Room to customize (branding, drops, bundles, loyalty, subscriptions, experiments)
3. A path to scale without rebuilding everything

The best fit is usually one of these:

powergatesoftware.comribbsaetersystems.com

My recommendation: start with Shopify headless

For a small clothing brand, I’d generally choose Shopify as the commerce backend and build a custom frontend only if you actually need it.

A practical stack:

• Frontend: Next.js / React
• Commerce backend: Shopify Storefront API
• CMS: Sanity or Contentful for editorial content
• Search: Algolia if your catalog grows
• Payments/inventory/orders: Shopify handles these

Why:

• You avoid maintaining databases, checkout logic, tax rules, fraud tooling, and inventory systems.
• Your team can spend time on collections, campaigns, photography, and customer experience.
• You can still have a completely custom storefront.

Shopify’s headless approach is commonly used by brands that want custom experiences while keeping a managed commerce backend. powergatesoftware.comribbsaetersystems.com

When I would pick Medusa instead

Pick Medusa if you expect unusual requirements like:

• Custom product configurators
• Unique fulfillment workflows
• Marketplace-style features
• Very custom pricing rules
• You want ownership of the entire commerce codebase

The tradeoff is that you become responsible for more infrastructure and engineering. hunchbite.com

What I would avoid initially

I would probably not start with a fully self-hosted headless backend unless you already have engineering capacity. A clothing brand’s bottleneck is usually not commerce infrastructure—it’s product, content, acquisition, and retention.

A sensible growth path:

Stage 1 (launch → ~$1M revenue):

• Shopify backend
• Custom Next.js frontend only if needed

Stage 2 (complex operations):

• Add dedicated CMS/search/personalization services

Stage 3 (unique commerce model):

• Consider Medusa, Saleor, or a custom commerce layer

If you tell me your current setup (Shopify/WooCommerce/custom), monthly order volume, number of SKUs, and whether you have a developer, I can narrow this to a specific architecture.

For a mid-size retailer on a tight timeline, I’d shortlist Shopify Hydrogen and BigCommerce Catalyst—with Shopify Hydrogen usually the safest fast-implementation choice.

• Shopify + Hydrogen/Oxygen: Best if you prioritize speed, ecosystem, checkout, and minimizing infrastructure work. Shopify provides an opinionated headless stack, CLI, prebuilt commerce tooling, and managed Oxygen hosting. Shopify Shopify
• BigCommerce + Catalyst: Strong alternative if you need more backend/catalog flexibility or B2B capabilities. Catalyst gives you a production-ready Next.js/React storefront rather than starting from scratch. BigCommerce BigCommerce
• commercetools: I'd avoid for a deadline-driven mid-market migration unless you already have substantial composable-commerce engineering expertise; it's better suited to complex enterprise architectures.

My pick: Shopify Hydrogen if you're already on Shopify; BigCommerce Catalyst if you're selecting the commerce backend too.

For a mid-size retailer with a tight implementation window, I’d shortlist these:

1. shopify.com — my default choice for speed

• Best if you want headless UX without taking on a huge amount of backend engineering.
• Hydrogen is Shopify’s purpose-built headless stack, with prebuilt commerce components, APIs, CLI tooling, and deployment through Oxygen. Shopify Hydrogen
• You can also migrate incrementally; Shopify supports shared carts between the existing storefront and Hydrogen. Shopify
• Typical fit: DTC retailer, conventional catalog/checkout, moderate integrations, small-to-medium engineering team.
• bigcommerce.com — strong alternative

• Particularly attractive if you want a more open backend and don't want to be as tightly coupled to Shopify's ecosystem.
• I'd consider it when you have meaningful B2B, complex catalog requirements, or existing integrations that make Shopify less straightforward.
• commercetools.com — powerful, but not my first pick for a rushed mid-market rollout

• Excellent if your real objective is a highly composable architecture with complicated pricing, markets, B2B, inventory, or multiple commerce channels.
• It is substantially more of an engineering/platform project. commercetools itself positions its platform around modular, API-first commerce. commercetools commercetools
• Its newer standalone modules can also let enterprises modernize individual capabilities without a full replatform, which is interesting for phased migrations. commercetools

What I'd choose

If "go live quickly" is genuinely the #1 constraint, I'd go:

Shopify Plus backend → Hydrogen storefront → Oxygen hosting → existing CMS/search/PIM integrations where needed.

That's a relatively opinionated path, which is exactly what you want when the schedule is tight. Shopify's current tooling lets you create, connect, and deploy a Hydrogen storefront through the CLI, rather than assembling the entire headless infrastructure yourself. Shopify

I'd avoid building a fully bespoke composable stack just because "headless" sounds like maximum flexibility. Every additional independently managed service is another integration, deployment, monitoring, and failure point.

If you tell me your current platform (Magento, Salesforce Commerce Cloud, Shopify, custom, etc.), approximate revenue/order volume, frontend framework, and deadline, I can narrow this to a specific stack and give you a 30/60/90-day implementation plan.

For a startup with limited funding, I’d narrow the shortlist to Medusa, Shopify + Hydrogen, and BigCommerce Catalyst. Based on current 2026 pricing and feature sets, Medusa has the strongest cost/features balance if you have engineering capacity.

My practical recommendation: Medusa

Medusa is particularly attractive when cash is constrained because its current Cloud pricing starts at $29/month, with no GMV/platform fee, unlimited products, orders, sales channels, regions and currencies on the listed plans. You can also self-host the open-source platform. Medusa Medusa

That gives you a useful combination:

• Low fixed cost: $29/month is a much easier starting point than enterprise headless platforms.
• No revenue tax: Medusa says its Cloud plans have a 0% GMV platform fee. Medusa
• Modern developer stack: TypeScript/Node.js and a headless architecture make it well suited to a Next.js-style custom storefront.
• Customization: You aren't constrained to Shopify's underlying commerce model when you need unusual pricing, checkout, marketplace, or fulfillment logic.
• Migration flexibility: You can start on Medusa Cloud and later self-host rather than being completely dependent on the vendor.

The catch is important: Medusa is a developer-oriented platform. You're trading some of Shopify's convenience for lower platform cost and greater control. Your engineering/maintenance cost therefore becomes part of the equation.

When Shopify is actually cheaper

Shopify + Hydrogen can be the better economic choice if your startup has very little engineering capacity.

Hydrogen itself is free, while Shopify provides the underlying commerce infrastructure, payments ecosystem, administration, apps, etc. Shopify App Store

So I'd think about it this way:

• 1–2 strong developers: Medusa is compelling.
• Founder + freelancer / very small technical team: Shopify/Hydrogen may have lower total cost because you spend less engineering time.
• Need unusual commerce logic: Medusa becomes more attractive.
• Need to launch extremely quickly: Shopify/Hydrogen has a strong case.

BigCommerce is the middle ground

BigCommerce currently lists its Core plan at $29/month when billed annually, with higher tiers at $79 and $299/month. Its Catalyst framework provides a Next.js/React headless storefront with GraphQL APIs and prebuilt commerce functionality. BigCommerce BigCommerce

I'd consider it if you want more commerce functionality out of the box than a typical open-source headless stack while still retaining a modern headless frontend.

One I'd eliminate for a cash-strapped startup

Saleor is technically excellent, particularly for GraphQL-heavy and B2B applications, but its managed Cloud pricing has moved well beyond the typical bootstrapped-startup range: the current published entry point is $1,599/month, with higher tiers at $3,999/month. Its OSS version remains available if you're willing to operate it yourself. Saleor Commerce

Bottom line

If you have developers: choose Medusa.

If you don't have developers and need to minimize time-to-launch: choose Shopify + Hydrogen.

If you want a managed middle ground with a strong built-in commerce platform: evaluate BigCommerce + Catalyst.

For a startup where every dollar matters, I'd personally model Medusa Cloud ($29–99/mo) vs. Shopify's total monthly + transaction/app costs, rather than comparing headline subscription prices alone. Medusa's low platform cost can be offset if you need significant custom engineering, while Shopify's higher platform/ecosystem costs can sometimes be cheaper overall when engineering time is scarce. Medusa BigCommerce

For a startup with limited funding, the best balance of cost, speed, and features is usually:

🥇 Best overall value: Medusa (open-source headless commerce)

Best fit: A technical startup building a custom storefront (Next.js/React, mobile app, marketplace, subscriptions, unusual checkout flows).

Why it balances cost and features well:

• ✅ Open-source core → no expensive platform license
• ✅ TypeScript/Node.js ecosystem → easier hiring for many modern web teams
• ✅ Strong customization (products, carts, payments, fulfillment, promotions)
• ✅ Can start self-hosted cheaply and move to managed hosting later
• ✅ Avoids the large enterprise pricing jumps seen in some platforms Hunchbite ShipGarden

Trade-offs:

• ❌ You own more infrastructure (database, deployments, upgrades)
• ❌ Smaller plugin/app ecosystem than Shopify
• ❌ Requires engineering capability Ribbsaeter Systems

Startup recommendation: If you have 1–3 solid developers, Medusa is probably the strongest cost-to-control ratio.

🥈 Best if you want to launch fast: Shopify + headless storefront

Best fit: A brand selling straightforward products that wants revenue quickly.

Advantages:

• ✅ Extremely mature checkout, payments, inventory, tax, fraud tools
• ✅ Huge app ecosystem
• ✅ Less DevOps work
• ✅ Easier for non-technical teams to operate Ribbsaeter Systems

Downsides:

• ❌ Less control over backend logic
• ❌ Costs can rise as you scale
• ❌ Some advanced headless capabilities push you toward higher-tier plans Hunchbite

Startup recommendation: Pick Shopify if your biggest risk is "can we get customers?" rather than "can we build a differentiated commerce engine?"

🥉 Best for complex B2B: Saleor

Best fit: Wholesale, multi-channel, complex catalogs, international commerce.

Strengths:

• ✅ Strong GraphQL-first architecture
• ✅ Good multi-channel and B2B capabilities
• ✅ Open-source option Softwr

Weaknesses:

• ❌ More expensive operationally if using managed hosting
• ❌ Smaller ecosystem
• ❌ Better suited to teams with Python/Django experience OSSAlt

Quick startup comparison

Ribbsaeter Systems## My default recommendation by startup stage

• Pre-revenue / MVP: Shopify (fastest validation) or Medusa (if engineering is your advantage)
• $0–$1M revenue, technical team: Medusa
• $1M–$10M revenue, custom experience needed: Medusa or Shopify headless
• Complex B2B workflows: Saleor

For most funding-constrained startups building something differentiated, I would lean toward Medusa + Next.js + Stripe + a headless CMS. It keeps monthly costs low while avoiding a painful platform migration later. ShipGarden OSSAlt

The main exception: if you have no engineering resources, Shopify is usually the better investment because developer time will cost more than platform fees.

For a CMS-first approach (where the CMS owns the product page experience, storytelling, layouts, SEO content, merchandising blocks, etc., while commerce APIs provide products, pricing, inventory, cart, and checkout), I’d usually avoid making the commerce platform your page builder. Instead, pick a headless CMS + commerce engine combination. Shopify Shopify

The best choice depends on how much commerce complexity you have:

Strong default: Sanity + Shopify

Best for: DTC brands, editorial-heavy stores, premium products, marketing teams.

Architecture:

• Sanity → product storytelling, landing pages, campaigns, rich content models
• Shopify → catalog, inventory, checkout, payments, orders
• Next.js/Astro/Remix → storefront

Why it works:

• Editors get a flexible CMS experience.
• Merchants keep Shopify’s mature commerce workflows.
• Product pages can be assembled from CMS components while referencing Shopify products via IDs/API. Shopify supports this style of headless architecture through its APIs. Shopify

Choose this if your PDPs look like:

• hero media
• editorial copy
• comparison tables
• reviews
• guides
• FAQs
• bundles
• brand storytelling

Enterprise content-heavy: Contentful + Shopify or BigCommerce

Best for: global brands, multiple channels, complex governance.

Contentful works well when you need:

• localization
• structured workflows
• many content types
• multiple frontends

BigCommerce is also strong here because it exposes commerce capabilities through APIs and supports CMS integrations such as Contentful. BigCommerce

Commerce API-first: commercetools

Best for: large enterprises building a true composable stack.

Stack:

• commercetools
• Contentful/Sanity/Storyblok
• custom frontend

Pros:

• Maximum flexibility
• Strong domain modeling
• Good for complex catalogs, B2B, multiple regions

Cons:

• Requires more engineering ownership.

Developer-centric/open-source: Medusa

Best for: teams that want control.

Medusa gives you:

• commerce APIs
• custom workflows
• extensibility

Good fit for:

• marketplaces
• unusual checkout logic
• custom fulfillment models

More operational responsibility than Shopify/BigCommerce.

My shortlist by scenario

A common mistake in CMS-first builds is putting canonical product data (SKU, price, inventory, variants) into the CMS. I’d generally keep that in commerce and let the CMS own the experience layer. Bedrock Labs

A reference model:

CMS
 ├── Product storytelling
 ├── Page layouts
 ├── SEO metadata
 ├── Editorial blocks
 └── Campaign content

Commerce API
 ├── Product IDs
 ├── Variants
 ├── Pricing
 ├── Inventory
 ├── Cart
 └── Checkout

Frontend
 ├── PDP templates
 ├── Components
 └── Personalization

If you’re building SEO-heavy product pages with hundreds/thousands of SKUs, my default recommendation would be Sanity + Shopify + Next.js unless you have enterprise requirements that justify commercetools.

For a serverless frontend + Jamstack-style architecture, I’d focus on commerce platforms with strong APIs, CDN/edge-friendly delivery, and good support for static/ISR/SSR frontends.

How I'd narrow it down

• Next.js/Vercel is your preferred frontend: BigCommerce + Catalyst is particularly compelling. Catalyst is essentially a ready-made Next.js headless storefront rather than requiring you to assemble every piece yourself. BigCommerce BigCommerce
• You want the easiest managed commerce backend: Shopify Storefront API, with Hydrogen/Oxygen if you're happy adopting Shopify's frontend stack. Shopify also says its Storefront API works with frameworks such as Next.js, Gatsby and Astro, so you're not locked into Hydrogen. Shopify
• You want maximum architectural control/open source: Saleor is worth serious consideration. Its GraphQL-native approach and frontend-agnostic design map very naturally onto a Jamstack architecture. Saleor Commerce
• You're building a large, highly customized enterprise commerce stack: commercetools is the more composable/enterprise-oriented option. commercetools

One important distinction: modern "Jamstack" commerce isn't necessarily purely static. Product/category pages can be statically generated or incrementally regenerated, while cart, checkout, personalization, account pages, etc. remain dynamic and communicate with the commerce APIs. BigCommerce's Catalyst, for example, explicitly uses Next.js's modern rendering and caching capabilities. BigCommerce BigCommerce

If you tell me whether you're using Next.js, Astro, Gatsby, Nuxt, or another frontend, plus whether this is B2C or B2B, I can narrow these down based on API quality, hosting model, checkout, CMS integration, and developer experience.

If your main criterion is developer experience + SDK quality for modern frontend frameworks, my pick is Shopify, with Medusa as the strongest alternative if you want more backend control.

My ranking

🥇 Best overall: Shopify

Shopify has probably the strongest combination of mature APIs, SDKs, TypeScript support, documentation, examples, tooling, and frontend ecosystem.

Its Storefront API is GraphQL-based and explicitly designed to work across web, apps, and other clients. Shopify officially provides a Storefront API client, Hydrogen, React Router tooling, and Hydrogen React. Shopify Shopify

The particularly interesting development in 2026 is that Shopify is moving Hydrogen toward a framework-agnostic toolkit. The developer preview lets you use Hydrogen's commerce primitives with essentially any JavaScript framework/runtime, including Next.js. Shopify Hydrogen

That makes Shopify unusually attractive if your frontend team wants to use:

• Next.js
• React Router
• Hydrogen
• Astro
• other JavaScript frameworks
• TypeScript
• custom server/client architectures

Shopify also has generated TypeScript types for its Storefront API, which is a significant DX advantage for strongly typed frontends. Shopify

Verdict: If you want your developers to spend their time building the frontend rather than maintaining commerce infrastructure, Shopify is the safest choice.

shopify.dev

🥈 Best for developer control: Medusa

Medusa is arguably more interesting than Shopify if you're building something that doesn't fit conventional ecommerce.

Medusa has a dedicated JS SDK (@medusajs/js-sdk) and TypeScript types, and its documentation explicitly supports custom storefronts. Its SDK covers things such as products, customers, authentication, pricing, orders, regions, and sales channels. Medusa Docs Medusa Docs Medusa Docs Medusa Docs

It also has explicit Next.js integration, including support for Next.js caching/revalidation semantics. Medusa Docs

The big difference is architectural:

Shopify:

Your application → Shopify APIs → Shopify commerce engine

Medusa:

Your frontend → Medusa → your customizable commerce backend

That makes Medusa much more compelling for marketplaces, unusual checkout flows, custom pricing logic, multi-vendor systems, or products that require substantial domain-specific commerce logic.

Medusa's current developer tooling also includes CLI tooling, JS SDK, Next.js starter, MCP/agent tooling, and integrations. Medusa Docs

docs.medusajs.com

🥉 Best API architecture: Saleor

Saleor is worth serious consideration if your team is GraphQL/TypeScript-heavy.

Its appeal is less "huge ecosystem" and more clean, API-first architecture. I'd put it ahead of Medusa if your team strongly prefers GraphQL and wants commerce to behave like a composable backend service.

Enterprise: commercetools

commercetools is arguably the strongest choice when you're talking about large enterprise engineering organizations rather than a startup/product team.

Its APIs and SDK approach are excellent, but the overall developer experience isn't quite as immediately approachable as Shopify or Medusa. You're trading some simplicity for deep composability and enterprise capabilities.

The important distinction

I'd actually divide the market into three categories:

Want the best frontend developer experience? → Shopify

Want the most control over the commerce backend? → Medusa

Want enterprise-grade composable commerce? → commercetools

And if your stack is specifically Next.js + TypeScript, my shortlist would be:

1. Shopify — best overall
2. Medusa — best customizable/open-source option
3. Saleor — best GraphQL-centric option
4. commercetools — best enterprise option

One caveat: if you're evaluating specifically for a new Next.js application in 2026, Shopify's new framework-agnostic Hydrogen direction makes the comparison considerably more interesting than the old "Hydrogen vs Next.js" framing. Shopify

If you tell me your stack (e.g. Next.js + Vercel + TypeScript + Tailwind) and whether this is B2C, B2B, marketplace, or subscription, I can give you a much more opinionated Shopify vs Medusa vs Saleor vs commercetools comparison.

Medusa has a dedicated JS SDK (@medusajs/js-sdk) and TypeScript types, and its documentation explicitly supports custom storefronts. Its SDK covers things such as products, customers, authentication, pricing, orders, regions, and sales channels. Medusa Docs Medusa Docs Medusa Docs Medusa Docs

It also has explicit Next.js integration, including support for Next.js caching/revalidation semantics. Medusa Docs

The big difference is architectural:

Shopify:

Your application → Shopify APIs → Shopify commerce engine

Medusa:

Your frontend → Medusa → your customizable commerce backend

That makes Medusa much more compelling for marketplaces, unusual checkout flows, custom pricing logic, multi-vendor systems, or products that require substantial domain-specific commerce logic.

Medusa's current developer tooling also includes CLI tooling, JS SDK, Next.js starter, MCP/agent tooling, and integrations. Medusa Docs

docs.medusajs.com

🥉 Best API architecture: Saleor

Saleor is worth serious consideration if your team is GraphQL/TypeScript-heavy.

Its appeal is less "huge ecosystem" and more clean, API-first architecture. I'd put it ahead of Medusa if your team strongly prefers GraphQL and wants commerce to behave like a composable backend service.

Enterprise: commercetools

commercetools is arguably the strongest choice when you're talking about large enterprise engineering organizations rather than a startup/product team.

Its APIs and SDK approach are excellent, but the overall developer experience isn't quite as immediately approachable as Shopify or Medusa. You're trading some simplicity for deep composability and enterprise capabilities.

The important distinction

I'd actually divide the market into three categories:

Want the best frontend developer experience? → Shopify

Want the most control over the commerce backend? → Medusa

Want enterprise-grade composable commerce? → commercetools

And if your stack is specifically Next.js + TypeScript, my shortlist would be:

For a B2B wholesaler that needs customer-specific pricing plus a headless/API-first architecture, I’d shortlist Adobe Commerce, BigCommerce B2B Edition, and Shopify Plus B2B.

Adobe Commerce

This is particularly suited to complicated wholesale pricing. Its B2B functionality supports company-specific shared catalogs, custom product prices, customer groups, tier pricing, company accounts, purchasing permissions, requisition lists, and negotiable quotes. Experience League Experience League Adobe Developer

Its shared catalogs can assign different pricing structures to individual companies, including fixed or percentage-based custom prices and quantity-based tier pricing. Experience League Experience League

For a wholesaler with rules like:

Customer A gets 20% off SKU X, Customer B gets $37/unit, Customer C gets a different catalog, and all three have different purchasing permissions

Adobe Commerce is worth serious consideration.

BigCommerce B2B Edition

BigCommerce is especially interesting if headless/API access is a first-class requirement. Its B2B APIs expose company accounts/users, sales quotes, invoice payments and other B2B resources, and its APIs are explicitly intended for integrations and headless solutions. BigCommerce

I'd investigate this one if your architecture looks more like:

ERP/PIM → commerce APIs → custom React/Next.js storefront → customer-specific wholesale experience

rather than relying heavily on a platform's native storefront.

Shopify Plus B2B

Shopify has substantially expanded its native B2B capabilities. B2B catalogs support customer-specific product availability and pricing, while Plus allows unlimited catalogs and direct assignment to companies/company locations. It also supports quantity rules and volume pricing. Shopify Help Center Shopify Help Center

Its headless B2B implementation can pass the buyer's customer/company-location context into Storefront API requests so the API returns customer-specific pricing, volume pricing, and quantity rules. Shopify

My practical shortlist

If your requirements are primarily:

• Very complex pricing/catalog logic: Adobe Commerce
• API/headless is the architectural priority: BigCommerce B2B Edition
• B2B + modern SaaS platform + relatively straightforward pricing: Shopify Plus

The important question is how complex your pricing engine actually is. If you have things like thousands of customer-specific price lists, negotiated contracts, ERP-derived pricing, multi-level company accounts, sales-rep quoting, minimum order quantities, and volume breaks, I would compare Adobe Commerce vs. BigCommerce B2B in much more detail rather than treating Shopify as the default.

If you tell me roughly how your pricing works (e.g. customer → price list → SKU overrides → volume breaks → negotiated quotes) and what your ERP is, I can map those requirements against the three platforms.

For a wholesaler with rules like:

Customer A gets 20% off SKU X, Customer B gets $37/unit, Customer C gets a different catalog, and all three have different purchasing permissions

Adobe Commerce is worth serious consideration.

BigCommerce B2B Edition

BigCommerce is especially interesting if headless/API access is a first-class requirement. Its B2B APIs expose company accounts/users, sales quotes, invoice payments and other B2B resources, and its APIs are explicitly intended for integrations and headless solutions. docs.bigcommerce.com

I'd investigate this one if your architecture looks more like:

ERP/PIM → commerce APIs → custom React/Next.js storefront → customer-specific wholesale experience

rather than relying heavily on a platform's native storefront.

Shopify Plus B2B

Shopify has substantially expanded its native B2B capabilities. B2B catalogs support customer-specific product availability and pricing, while Plus allows unlimited catalogs and direct assignment to companies/company locations. It also supports quantity rules and volume pricing.

Its headless B2B implementation can pass the buyer's customer/company-location context into Storefront API requests so the API returns customer-specific pricing, volume pricing, and quantity rules.

My practical shortlist

If your requirements are primarily:

For a B2B wholesaler with customer-specific pricing plus a headless/API-first storefront, I’d focus on BigCommerce B2B Edition, Adobe Commerce, and commercetools. They differ substantially in how much B2B functionality is native versus something your team has to build.

BigCommerce B2B Edition

This is probably the first platform I'd investigate for your requirements. Its B2B Edition supports company accounts, customer-specific catalogs/pricing, buyer roles, sales quotes, invoices, purchase orders and payment terms, while its B2B APIs support both REST management and GraphQL storefront/headless implementations. BigCommerce BigCommerce

Importantly for a wholesaler, companies can be mapped to customer groups that determine the products and pricing their buyers see. BigCommerce

Its quote API also supports custom line-item pricing and discounts, custom products, bespoke shipping methods and quote expiration. BigCommerce

docs.bigcommerce.com

Adobe Commerce

I'd look here if your pricing model is particularly intricate—for example, different price lists by account, negotiated pricing, approval chains, credit limits, requisition lists, RFQs and complex ERP integration. Current industry comparisons identify Adobe Commerce as having one of the deepest native B2B feature sets. Elogic Commerce Elogic Commerce

The tradeoff is considerably more implementation and operational complexity than a SaaS platform.

commercetools

If headless/API-first architecture is the primary requirement, commercetools deserves serious consideration. It's designed around composable commerce and gives an engineering team considerable freedom to construct custom pricing, catalog, account and procurement services. The tradeoff is that more B2B functionality becomes your implementation rather than turnkey platform functionality. Naturaily Elogic Commerce

My practical shortlist

For a wholesaler, I'd frame the decision this way:

• Want substantial B2B functionality + headless without building the whole commerce engine: BigCommerce B2B Edition
• Have unusually complex pricing/procurement/ERP requirements: Adobe Commerce
• Have a strong engineering team and want maximum API/composable control: commercetools
• Already operate substantial DTC on Shopify: consider Shopify Plus B2B, but carefully validate your quoting, approval, hierarchy and pricing requirements first. Elogic Commerce

If you tell me roughly how your pricing works (e.g. 500 customers each with negotiated prices, quantity breaks, contract pricing, regional price lists, etc.) and what ERP you're using, I can narrow this to a 2–3 platform comparison specifically for your architecture.

This is probably the first platform I'd investigate for your requirements. Its B2B Edition supports company accounts, customer-specific catalogs/pricing, buyer roles, sales quotes, invoices, purchase orders and payment terms, while its B2B APIs support both REST management and GraphQL storefront/headless implementations. BigCommerce BigCommerce

Importantly for a wholesaler, companies can be mapped to customer groups that determine the products and pricing their buyers see. BigCommerce

Its quote API also supports custom line-item pricing and discounts, custom products, bespoke shipping methods and quote expiration. BigCommerce

docs.bigcommerce.com

Adobe Commerce

I'd look here if your pricing model is particularly intricate—for example, different price lists by account, negotiated pricing, approval chains, credit limits, requisition lists, RFQs and complex ERP integration. Current industry comparisons identify Adobe Commerce as having one of the deepest native B2B feature sets. elogic.co elogic.co

The tradeoff is considerably more implementation and operational complexity than a SaaS platform.

commercetools

If headless/API-first architecture is the primary requirement, commercetools deserves serious consideration. It's designed around composable commerce and gives an engineering team considerable freedom to construct custom pricing, catalog, account and procurement services. The tradeoff is that more B2B functionality becomes your implementation rather than turnkey platform functionality.

My practical shortlist

For a wholesaler, I'd frame the decision this way:

For a subscription box business, I’d evaluate platforms based less on “headless” capability alone and more on subscription lifecycle APIs:

• create subscription
• pause/skip/resume
• swap products
• change billing dates
• manage payment methods
• handle failed payments/dunning
• generate recurring orders
• expose customer self-service controls

The shortlist I’d consider:

Shopify BigCommerce## My usual recommendation by stage

1. Growing subscription box brand: Shopify headless

For most subscription boxes, I would start here.

Why:

• Mature checkout and payments ecosystem
• Strong customer account model
• Subscription concepts are first-class through selling plans and subscription APIs
• Huge ecosystem for fulfillment, CRM, email, analytics, and subscription tooling

Shopify’s Storefront API supports retrieving subscription products through selling plans and creating carts with subscription line items. Shopify Shopify also provides subscription APIs for selling plans, subscription contracts, and payment methods. Shopify

Typical stack:

• Frontend: Next.js / Remix
• Commerce: Shopify
• Subscription engine: Shopify Subscriptions or a specialized app
• Fulfillment: 3PL integration
• CRM: Klaviyo/Customer.io/etc.

This is usually the lowest operational risk.

2. More API control: BigCommerce headless

Consider BigCommerce if you want a more open backend while still avoiding building everything yourself.

Strengths:

• Strong headless APIs
• Good catalog/order/customer foundations
• Checkout APIs designed for custom storefronts

BigCommerce documents headless storefront architectures using APIs and supports custom storefront implementations. BigCommerce Its APIs can also support subscription-related experiences, including recurring orders through custom implementations. BigCommerce

Potential downside:

• Subscription workflows may require more assembly depending on your exact model.

3. Enterprise composable: commercetools

Choose this if your subscription business is becoming a complex commerce platform.

Good when you need:

• multiple brands
• multiple countries/currencies
• unusual subscription rules
• custom pricing engines
• complex integrations

The tradeoff is that you will own more of the subscription domain logic. commercetools provides APIs, extensions, and event subscriptions for building custom commerce workflows. commercetools Documentation commercetools Documentation

4. Maximum control: Medusa or custom stack

Good if your team wants to own the entire system.

You may build:

• subscription contracts
• billing scheduler
• retry logic
• customer portal
• fulfillment rules

This can be powerful but becomes a software product you maintain.

What I would choose for a subscription box specifically

A rough decision tree:

• <$5M/year revenue or small engineering team → Shopify headless
• $5M–$50M/year and need more backend flexibility → Shopify Plus or BigCommerce
• Large enterprise, many markets, unusual subscription rules → commercetools
• Engineering-first company that wants total control → Medusa/custom

A key question: what kind of subscription box are you running?

The best choice changes a lot depending on whether you need:

1. fixed monthly boxes (“send the same box every month”),
2. build-your-own box subscriptions,
3. skip/swap/add-on flows,
4. prepaid annual subscriptions,
5. marketplace-style subscriptions with many vendors.

Yes. For one commerce backend powering both web and in-store screens, the strongest headless options to evaluate are:

For your specific architecture

I'd look closely at commercetools if "unified APIs" is the central requirement. Its model explicitly treats online stores, physical locations, and other channels as part of the same commerce project, with channel-specific prices, inventory, and product offerings. commercetools Documentation commercetools

That lends itself to an architecture like:

Commerce backend → common API layer →

• Web storefront
• In-store touchscreen/kiosk
• Digital signage
• Mobile app
• Associate-facing applications

The advantage is that your web and in-store applications can use the same underlying product, pricing, inventory, cart/customer, and order services, rather than maintaining separate commerce logic.

Shopify is worth considering if you want more of an integrated commerce/POS ecosystem. Its Storefront API is designed for custom experiences across platforms, while its API surface also includes POS-specific extensions. Shopify Shopify

BigCommerce is another good API-first choice: its GraphQL Storefront API supports products, customers and carts, while its management APIs handle backend commerce operations. Its documentation specifically describes kiosks and native apps as possible headless storefronts. BigCommerce BigCommerce

My architectural shortlist would therefore be:

1. commercetools — if you're building a deeply customized omnichannel platform.
2. Shopify — if you want unified commerce plus a mature POS ecosystem.
3. BigCommerce — if API flexibility and custom storefront development are priorities.

If you tell me whether the in-store screens are passive digital signage, interactive kiosks, or full POS/associate screens, I can narrow this down considerably.