Neutral mentions of BigCommerce

If your agency’s core offering is custom frontends, I’d make Medusa the default platform you recommend, with Shopify Plus as the managed/SaaS option for clients who prioritize operational simplicity.

My recommendation

Why I'd pick Medusa for an agency

Medusa is particularly well aligned with your business model because the storefront is completely separate from the commerce backend. You can build the frontend in Next.js, Remix, Astro, or essentially whatever stack your agency prefers, and consume Medusa through its Store API and custom APIs. Medusa Docs Medusa Docs

More importantly, Medusa lets a single instance manage multiple stores, although multi-tenancy isn't native in the sense of an enterprise SaaS tenant-management layer—you'd implement the tenant relationships/isolation yourself. Medusa Docs

That distinction matters for an agency:

Client → Tenant → Store/Sales Channel → Products/Pricing/Inventory → Custom Frontend

You can build your own agency "control plane" on top of Medusa rather than forcing every client into the platform's standard storefront model.

It also gives you a lot of room to productize your work: custom checkout, subscriptions, marketplaces, unusual pricing, ERP integrations, custom admin experiences, etc. Medusa explicitly supports custom modules, data models, workflows, API routes, and admin customization. Medusa Docs Medusa Docs

When I'd recommend Shopify Plus instead

For a client saying:

"We want a completely custom frontend, but we don't want our agency maintaining commerce infrastructure."

I'd choose Shopify Plus + custom frontend.

Shopify Plus has a mature multi-store organization model with expansion stores, centralized organization management, and separate storefronts. Shopify Help Center Shopify Help Center

The tradeoff is architectural: those stores are independent data environments. Products, inventory, collections, and settings aren't automatically shared between them. Shopify Help Center

So I wouldn't describe Shopify Plus as a true "multi-tenant commerce backend." It's more like:

Organization → Store A / Store B / Store C → custom frontends

That's fantastic for a brand with regional stores or multiple storefronts, but less ideal if your agency is building a platform where dozens/hundreds of client tenants share a commerce infrastructure.

Saleor is the other one I'd seriously evaluate

If your team likes GraphQL and your clients skew toward B2B, multi-channel, complex catalogs, multiple warehouses, and enterprise requirements, I'd put Saleor very high on the shortlist. Current industry comparisons specifically highlight its GraphQL-first architecture and multi-channel model. Ribbsaeter Systems Naturaily

I'd roughly position the three like this:

• Medusa → "We want to own the architecture and customize everything."
• Shopify Plus → "We want the least operational burden and a proven commerce engine."
• Saleor → "We want an API-first, GraphQL-native commerce platform for sophisticated commerce."

For your agency, I'd standardize the stack

If I were setting up an agency platform today, I'd seriously consider:

Next.js + Medusa + PostgreSQL + Stripe + headless CMS + your own tenant/control plane

Then offer Shopify Plus when the client's requirements make managed SaaS more attractive.

The important thing is that I wouldn't build the commerce engine yourself. Build your agency's differentiation around the frontend, tenant management, integrations, design system, deployment pipeline, and client tooling.

If you tell me roughly how many stores/tenants you expect per deployment (e.g. 10, 100, 1,000+) and whether each tenant needs isolated products/orders/inventory, I can recommend the architecture I'd use for the multi-tenant layer as well.

It also gives you a lot of room to productize your work: custom checkout, subscriptions, marketplaces, unusual pricing, ERP integrations, custom admin experiences, etc. Medusa explicitly supports custom modules, data models, workflows, API routes, and admin customization. Medusa Docs Medusa Docs

When I'd recommend Shopify Plus instead

For a client saying:

"We want a completely custom frontend, but we don't want our agency maintaining commerce infrastructure."

I'd choose Shopify Plus + custom frontend.

Shopify Plus has a mature multi-store organization model with expansion stores, centralized organization management, and separate storefronts. Shopify Help Center Shopify Help Center

The tradeoff is architectural: those stores are independent data environments. Products, inventory, collections, and settings aren't automatically shared between them. Shopify Help Center

So I wouldn't describe Shopify Plus as a true "multi-tenant commerce backend." It's more like:

Organization → Store A / Store B / Store C → custom frontends

That's fantastic for a brand with regional stores or multiple storefronts, but less ideal if your agency is building a platform where dozens/hundreds of client tenants share a commerce infrastructure.

Saleor is the other one I'd seriously evaluate

If your team likes GraphQL and your clients skew toward B2B, multi-channel, complex catalogs, multiple warehouses, and enterprise requirements, I'd put Saleor very high on the shortlist. Current industry comparisons specifically highlight its GraphQL-first architecture and multi-channel model.

I'd roughly position the three like this:

If your team prefers serverless frontends + JAMstack, I’d prioritize commerce platforms that are strongly API-first, work well with static/SSR/edge frameworks, and keep the operational backend managed.

My shortlist

1. Shopify — best default choice

Shopify is probably the safest choice if you want your frontend to live independently on something like Vercel, Netlify, Cloudflare, or another serverless/edge platform.

Its Storefront API is GraphQL-based and explicitly designed for custom storefronts, while Shopify handles products, inventory, carts, checkout, orders, etc. Shopify also says you can bring essentially any frontend framework and hosting stack. Shopify Shopify

It works particularly well with Next.js, Astro, Gatsby, and Hydrogen. Shopify's Hydrogen/Oxygen stack is also an option if you want a more integrated React + edge deployment approach. Shopify

shopify.dev

2. Saleor — best if "API-first" is the architectural priority

Saleor is arguably an even cleaner architectural match. It's GraphQL-only, API-only, headless, and technology-agnostic, with the frontend and backend completely separated. It supports webhooks and API extensions rather than requiring traditional commerce plugins. Saleor Commerce GitHub

That's attractive if your team thinks of the commerce engine as just another backend service in a composable JAMstack architecture.

The tradeoff is that Shopify generally gives you a more mature turnkey commerce ecosystem and less infrastructure/commerce engineering to own.

saleor.io

3. commercetools — best for enterprise composable commerce

commercetools is a strong choice when you're building a large composable architecture rather than simply replacing a traditional storefront. Its APIs expose commerce capabilities independently, making it well suited to multiple frontend channels and independently evolving services. Commercetools

The downside is complexity: I'd choose it when you actually need that enterprise-level composability rather than because "headless" sounds attractive.

commercetools.com

4. BigCommerce — pragmatic SaaS alternative

BigCommerce also supports custom headless storefronts through APIs and SDKs, with official documentation specifically covering headless architectures and custom storefronts. BigCommerce

It's worth evaluating alongside Shopify if you want SaaS commerce but don't want to automatically default to Shopify.

docs.bigcommerce.com

What I'd pick

For a team saying "we want JAMstack/serverless first", my ranking would be:

1. Shopify — best balance of developer freedom, managed commerce, ecosystem, and speed to market.
2. Saleor — best architectural purity and flexibility if your developers are comfortable owning more of the solution.
3. commercetools — best for complex enterprise composable commerce.
4. BigCommerce — good SaaS/headless alternative.

A typical architecture I'd recommend is:

Astro/Next.js → serverless/edge hosting → commerce API → Shopify/Saleor
with a separate headless CMS → content, and optionally separate search/PIM/ERP services.

The important distinction is that JAMstack doesn't mean the entire shopping experience has to be static. Product/category pages can be statically generated or cached at the edge, while cart, customer, inventory-sensitive pricing, and checkout remain dynamic API interactions. Shopify's Storefront API is explicitly designed around this separation. Shopify help.shopify.com

If you tell me B2C vs B2B, approximate SKU count, expected traffic, and whether you're using Next.js/Astro/Gatsby, I can narrow this to a clear winner and give you a reference architecture.

shopify.dev

2. Saleor — best if "API-first" is the architectural priority

Saleor is arguably an even cleaner architectural match. It's GraphQL-only, API-only, headless, and technology-agnostic, with the frontend and backend completely separated. It supports webhooks and API extensions rather than requiring traditional commerce plugins. Saleor Commerce GitHub

That's attractive if your team thinks of the commerce engine as just another backend service in a composable JAMstack architecture.

The tradeoff is that Shopify generally gives you a more mature turnkey commerce ecosystem and less infrastructure/commerce engineering to own.

saleor.io

3. commercetools — best for enterprise composable commerce

commercetools is a strong choice when you're building a large composable architecture rather than simply replacing a traditional storefront. Its APIs expose commerce capabilities independently, making it well suited to multiple frontend channels and independently evolving services. Commercetools

The downside is complexity: I'd choose it when you actually need that enterprise-level composability rather than because "headless" sounds attractive.

commercetools.com

4. BigCommerce — pragmatic SaaS alternative

BigCommerce also supports custom headless storefronts through APIs and SDKs, with official documentation specifically covering headless architectures and custom storefronts. docs.bigcommerce.com

It's worth evaluating alongside Shopify if you want SaaS commerce but don't want to automatically default to Shopify.

For a B2B wholesaler with complex customer-specific pricing + a headless/API-first storefront, I’d shortlist Adobe Commerce and commercetools first.

My recommendation: Adobe Commerce B2B

For your specific requirements, Adobe Commerce B2B is probably the safest choice if your pricing model is genuinely complicated.

It has native company accounts, shared catalogs, customer-specific pricing, tier pricing, negotiated quotes, purchase orders/approval rules, requisition lists, quick order, and payment-on-account/credit. developer.adobe.com

The shared-catalog model is particularly relevant for wholesale: you can create custom catalogs assigned to companies and give each company its own product assortment and prices. Custom prices can be fixed amounts, percentages, and quantity-based tiers. experienceleague.adobe.com

It also exposes B2B functionality through REST APIs, including shared-catalog management, making it viable for a headless storefront. developer.adobe.com

Choose Adobe if: your business has lots of customer-specific rules, ERP integration, negotiated pricing, complex catalogs, multiple buyer roles, or workflows that will require customization.

When I'd choose commercetools instead

If headless/API-first architecture is the #1 requirement, I'd seriously consider commercetools.

Its pricing model can scope prices by customer group, channel, country, and currency, and its current B2B offering includes APIs for business-unit hierarchies, granular buyer permissions, approvals, and quote management. docs.commercetools.com

The tradeoff is that you're buying a composable commerce platform rather than an all-in-one B2B application. You'll generally need a stronger engineering team and more surrounding services.

The decision I'd make

Adobe Commerce B2B → best if you want deep B2B functionality out of the box and are willing to customize it.

commercetools → best if you want maximum architectural flexibility and API-first/headless commerce, and you have the engineering capability to assemble the platform.

BigCommerce B2B → worth evaluating if you want something simpler/faster to deploy without going all the way into enterprise composable architecture.

If you tell me roughly how you calculate customer pricing (e.g. customer × SKU × quantity × contract × region) and what ERP you're integrating with, I can narrow this down to the best 2–3 platforms and compare their APIs, pricing engines, quote workflows, and implementation complexity.

Yes. If your goal is one commerce backend powering both web and in-store screens through the same APIs, I’d shortlist these:

My pick: commercetools

For the architecture you're describing, commercetools is probably the strongest fit.

The important distinction is that you don't want:

Web storefront → commerce API
In-store screen → separate POS API
→ synchronize them afterward

You want:

Web UI ─┐
In-store UI ─┼→ shared commerce APIs → catalog / pricing / inventory / customer / cart / order
Mobile UI ─┘

commercetools' model is particularly well suited to that because Stores can represent physical retail locations or regions, while distribution/supply channels let you control assortment, prices and inventory. commercetools Documentation commercetools Documentation

For example, an in-store screen could use the same underlying product/catalog APIs as your website, but be scoped to:

Store = Boston Flagship
Inventory = Boston
Price = Retail
Assortment = Flagship assortment

while the web experience could use:

Store = Online US
Inventory = E-commerce warehouses
Price = Online

That gives you one commerce model with channel-specific context, rather than maintaining separate commerce implementations.

BigCommerce is the better alternative if you prioritize faster implementation and a more conventional SaaS commerce platform. Its headless APIs explicitly support storefronts such as websites, native apps and kiosks, and its channel model is quite mature. BigCommerce BigCommerce

If you tell me whether the in-store screens are POS checkout terminals, associate tablets, customer-facing kiosks, or digital signage, I can narrow this to the best 2–3 architectures and show what the API layer would look like.

Yes. If you mean one subscription platform that supports all three—gifting, pausing, and swapping products—there are several good options.

• getrecharge.com — Strong Shopify-focused option. Customers can pause, skip, and swap products, and Recharge also has a gifting feature where recipients can manage their gifted subscription. Recharge
• paywhirl.com — Supports pause/skip/reschedule, product swaps, and gifts, plus one-time add-ons and a self-service customer portal. PayWhirl Shopify Subscriptions
• woocommerce.com — If you're on WooCommerce, it has native subscription gifting plus suspend/reactivate and subscription switching. Product replacement/swapping can be added through its self-service tooling. WooCommerce WooCommerce
• marketing.bcsubs.app — Specifically advertises a portal where subscribers can gift, pause, and swap subscriptions. BC Subscriptions

My shortlist

If you're building a consumer subscription business, I'd start by evaluating Recharge vs. PayWhirl. Recharge looks particularly strong if gifting is a core use case, while PayWhirl has a broad set of customer-management features.

If you tell me what ecommerce platform you're using (Shopify, WooCommerce, BigCommerce, custom, etc.) and what you mean by “gifting” (gift a subscription to someone else vs. send an individual subscription shipment as a gift), I can narrow it down to the best 2–3 options and compare pricing, APIs, gifting flow, pause/swap UX, and integrations.

If customizable subscription bundles + true mix-and-match boxes are the core of your business, I’d rank the options:

🥇 My pick: Shopify + Skio

For a business where the customer says something like:

"Give me 8 products every month, let me choose which ones, let me swap them next month, and charge me a fixed price."

Shopify + Skio is probably the strongest setup.

The important distinction is that you don't want to bolt a generic bundle app onto a subscription system. Skio has a native Build-a-Box system with:

• Static boxes — predetermined products at a fixed price
• Dynamic boxes — customers choose products and the price can change based on selection
• Sectioned boxes — multiple boxes within one subscription
• Subscription management and customer self-service

Skio specifically recommends its Build-a-Box functionality because Shopify's native Bundles aren't compatible with subscription selling plans. help.skio.com

🥈 Shopify + Recharge

I'd consider this if you're building a more established subscription operation and need sophisticated subscription management.

Shopify itself has an enormous ecosystem for bundle customization—there are currently 400+ bundle apps supporting subscription-related functionality in the Shopify App Store. apps.shopify.com

The downside is that you need to be careful about which bundle technology and subscription technology you're combining. Some combinations work beautifully; others create awkward cart, inventory, or subscription-contract behavior.

🥉 BigCommerce

I'd choose BigCommerce if your requirements go beyond subscriptions into very complicated product/configuration/discount logic.

BigCommerce is particularly strong for complex commerce rules: it supports extensive native promotion/discount functionality and emphasizes configurable products, bundles, and configurations. www.bigcommerce.com

Its subscription architecture is more integration-oriented, though—you generally choose a third-party recurring-payment/subscription provider rather than getting something like Skio's deeply integrated Build-a-Box experience. www.bigcommerce.com

What I'd actually build

If your product is something like a "Build Your Own Box" subscription, I'd use:

Shopify → Skio → Build-a-Box

rather than:

Shopify → generic bundle app → generic subscription app

The first architecture keeps the box configuration and subscription contract together, which becomes extremely important when customers want to:

• change individual items
• skip a shipment
• swap products
• change box size
• upgrade/downgrade
• have different prices by product
• add one-time products
• manage multiple boxes
• preserve inventory accuracy
• modify their next shipment

There are also dedicated Shopify bundle builders such as Mix & Match Bundle Builder, Bundly, and Easy Bundles, which can be attractive if your subscription requirements are relatively straightforward. apps.shopify.com

Bottom line: If you tell me what you're selling, how the box works (e.g. "pick any 6 from 30"), whether the box has a fixed or variable price, and your approximate monthly orders, I can narrow this down to the best platform + subscription engine + bundle builder rather than just the ecommerce platform.

For a B2B ecommerce business, I’d recommend using a dedicated B2B credit/AR layer rather than trying to manage trade accounts in the ecommerce platform alone.

My shortlist

What I'd choose

If you're on Shopify: I'd start by evaluating TradeLiq vs. Net Terms Tracker. TradeLiq is broader—it combines quotes, invoicing, credit management, payments and a customer portal—while Net Terms Tracker is more focused on enforcing Net 15/30/60 limits and automating invoice follow-up. TradeLiq Net Terms Tracker

If you're on multiple ecommerce platforms or have a substantial AR operation: Resolve is the stronger strategic choice. It combines B2B net terms, credit intelligence and AR automation and integrates with ecommerce and ERP/accounting systems. ResolvePay

If you're a smaller Shopify wholesaler: Dunly looks particularly simple: it provides a receivables ledger, aging, per-customer credit limits, over-limit alerts, account statements and scheduled pre/post-due reminders. Its current Growth plan is listed at $39/month. Dunly

The workflow I'd implement

The important thing is to make the system enforce the entire lifecycle:

1. Trade-account application → collect company details and credit information.
2. Approval → assign Net-15/30/60 terms and a credit limit.
3. Checkout enforcement → calculate open AR + new order against available credit and block/hold orders that exceed the limit.
4. Invoice generation → automatically create the invoice when the order ships or according to your accounting rules.
5. Automated reminders → e.g. 7 days before due, on due date, 3/7/14 days overdue.
6. Overdue controls → automatically suspend additional purchases on credit after a defined threshold.
7. Payment synchronization → payments update the customer's available credit immediately.
8. ERP/accounting sync → keep the ERP/accounting system as the financial source of truth.

That checkout enforcement piece is especially important. Several solutions can display credit balances, but you want the system to actually prevent a buyer from accumulating additional exposure once their limit is reached. For example, Net Terms Tracker and Trade Credit explicitly support checkout blocking based on available credit. Net Terms Tracker Shopify App Store

If you tell me which ecommerce platform you use (Shopify, BigCommerce, WooCommerce, Magento, custom) and roughly how many trade accounts/invoices you manage, I can narrow this to the best 2–3 options and compare pricing, integrations, credit underwriting, reminders, and ERP/accounting sync.

If you're on multiple ecommerce platforms or have a substantial AR operation: Resolve is the stronger strategic choice. It combines B2B net terms, credit intelligence and AR automation and integrates with ecommerce and ERP/accounting systems. resolvepay.com

If you're a smaller Shopify wholesaler: Dunly looks particularly simple: it provides a receivables ledger, aging, per-customer credit limits, over-limit alerts, account statements and scheduled pre/post-due reminders. Its current Growth plan is listed at $39/month.

The workflow I'd implement

If you want to sell both physical products and digital downloads without adding plugins/apps, look at platforms with native ecommerce + digital delivery built in. The strongest options are:

wix.com Squarespace Help Shopify### My shortlist for your situation

1. Wix — probably the easiest all-in-one choice

• Sell physical items with inventory, shipping, taxes, and checkout.
• Sell digital files (ebooks, templates, audio, courses, etc.) with automatic delivery.
• No ecommerce plugin stack required. wix.com wix.com
• Good if your store is also a brand/content website.
• Squarespace — best-looking storefront

• Strong templates and built-in commerce.
• Supports physical products and digital content sales from the same platform.
• Better fit for designers, artists, photographers, authors, and small catalogs. Squarespace Help Squarespace
• Shopify — best if physical products are the main business

• Excellent inventory, shipping, fulfillment, and scaling.
• The catch: digital downloads commonly require an additional app rather than being as native as Wix/Squarespace. Shopify

Quick recommendation

• 50–500 mixed products (physical + downloads): Wix
• Beautiful brand site + smaller catalog: Squarespace
• Thousands of physical SKUs or serious retail operations: Shopify (accepting that digital may need an add-on)

If you tell me roughly how many physical products you have, what kinds of downloads you sell (PDFs, courses, music, software, etc.), and whether subscriptions/memberships matter, I can narrow it down.

If by “tool” you mean the e-commerce platform, my first choice for your situation would be Shopify Plus.

Why it fits a fast-growing global retail brand:

• Very high traffic: Shopify Plus is a fully managed SaaS platform, so you aren't responsible for scaling servers during viral campaigns or peak events. Shopify says its infrastructure supports 10,000+ checkouts/minute, unlimited bandwidth, and averages 99.99% uptime during major sales events. www.shopify.com
• Multiple countries: Shopify Markets lets you manage country/region markets, localized pricing, catalogs, currencies, domains, languages, and payment methods from the platform. www.shopify.com
• Centralized operations: You can run international storefronts from one admin rather than maintaining completely separate commerce stacks. Plus currently includes 9 expansion stores. help.shopify.com
• Global checkout: Shopify supports local currencies/payment methods and offers Managed Markets for handling parts of cross-border tax, duty, fraud, and currency complexity. www.shopify.com
• Room to customize: If you eventually need a headless storefront or sophisticated integrations, Plus supports APIs, headless commerce, Shopify Functions, and checkout customization. www.shopify.com

When I'd choose something else

The key distinction is that high traffic alone doesn't mean you need the most technically complex platform. If your priority is reliable scaling + international expansion + relatively low infrastructure burden, Shopify Plus is particularly compelling. Current platform comparisons also generally position Shopify Plus as the lower-overhead option, while Adobe/Salesforce make more sense when enterprise complexity justifies the additional implementation burden. www.shopify.com

My default architecture for you: Shopify Plus + Shopify Markets/Managed Markets + CDN/edge delivery + your ERP/PIM/OMS integrations, with headless only where there is a concrete reason to use it.

If you tell me your approximate annual revenue/GMV, number of countries, monthly traffic, SKU count, and whether you have B2B, I can narrow this down to Shopify Plus vs. Salesforce vs. Adobe vs. BigCommerce for your specific scale.

For a B2B division with custom pricing, POS requirements, and large order volumes, I would focus less on a standard ecommerce platform and more on a B2B commerce platform that can handle account-level pricing, ERP/POS integration, sales-assisted ordering, and complex workflows. The best fit depends heavily on your operating model. Atwix BigCommerce

Shortlist to consider

Wise SoftwareXP## My likely recommendation by scenario

1. Wholesale/distribution business with negotiated pricing

Look hardest at: BigCommerce B2B Edition or Adobe Commerce

You likely need:

• Customer-specific price books
• Contract pricing
• Quantity breaks
• Purchase orders
• Quote → approval → order workflows
• Sales rep ordering
• ERP inventory sync
• Large SKU catalogs

BigCommerce is attractive if you want SaaS simplicity; Adobe Commerce is stronger if your pricing rules and workflows are highly customized. BigCommerce Netguru

2. Retail business adding a B2B channel

Look at: Shopify Plus

Good fit if you have:

• Existing Shopify retail operations
• Stores/POS
• Wholesale accounts
• A desire to unify consumer and business commerce

It is usually faster to operate, but I would validate complex B2B requirements before committing. Wise

3. Enterprise sales organization with ERP-driven pricing

Look at: Adobe Commerce, SAP Commerce Cloud, or a composable architecture

If pricing comes from:

• SAP
• Oracle
• Microsoft Dynamics
• NetSuite
• Custom quoting systems

then the commerce platform should probably act as the customer experience layer rather than the pricing source of truth. Atwix

POS considerations

POS changes the decision. You should evaluate:

• Does the B2B customer buy in-store, online, and through sales reps?
• Do stores need the same customer pricing as ecommerce?
• Does inventory need to be shared in real time?
• Do sales reps need to create orders on behalf of customers?

If you already have a POS system, I would prioritize platforms with strong APIs and integration ecosystems rather than choosing based only on storefront features.

A practical architecture I often see work well

ERP (pricing, inventory, customer master)
↓
Commerce platform (catalog, ordering experience, self-service)
↓
POS + sales tools + customer portals

The commerce platform should not necessarily own all B2B logic.

My ranking for your description

1. Adobe Commerce — if you are a large distributor/manufacturer with complex pricing
2. BigCommerce B2B Edition — if you want strong B2B capability without running a heavy platform
3. Shopify Plus — if B2B is an extension of a strong retail/DTC business
4. SAP Commerce Cloud — if you are already deeply invested in SAP
5. OroCommerce — if you are purely B2B and want B2B workflows first

A few details would change the recommendation significantly:

• Annual B2B revenue/GMV range?
• Number of SKUs?
• ERP (SAP, NetSuite, Dynamics, Oracle, other)?
• Current POS system?
• Do customers need negotiated contracts/quotes, or just volume discounts?
• Are you replacing an existing ecommerce platform or starting fresh?

A few details would change the recommendation significantly:

• Annual B2B revenue/GMV range?
• Number of SKUs?
• ERP (SAP, NetSuite, Dynamics, Oracle, other)?
• Current POS system?
• Do customers need negotiated contracts/quotes, or just volume discounts?
• Are you replacing an existing ecommerce platform or starting fresh?