Answers that name a competitor

For a growing local retailer with limited developer resources, I’d focus less on maximum customization today and more on how much infrastructure you won’t have to build or maintain later.

My shortlist

For your particular situation, Shopify is probably the architecture I'd investigate first. That's not a claim that it's universally "best"; it's because your constraint is limited development capacity. Shopify is managed SaaS, includes hosting and infrastructure, supports online and in-person selling, and has a progression from its lower plans through Shopify Plus as requirements become more complex. Its current plans include unlimited products and bandwidth. Shopify Shopify Help Center

The important part is that you don't need to build your future platform now. You can start with a standard theme and apps, then introduce custom integrations/API work only when the business actually needs them. Shopify currently supports custom apps, headless storefronts, additional staff accounts, international selling, and more advanced checkout/API capabilities on higher tiers. Shopify

When I'd choose BigCommerce instead

I'd look particularly closely at BigCommerce if you expect things like:

• A very large or complicated product catalog
• Multiple storefronts/brands
• B2B pricing and purchasing
• More complex integrations
• A desire to avoid platform transaction fees when using supported payment providers

BigCommerce's current plans explicitly support multiple storefronts and multiple retail/POS integrations, and its higher tiers are designed around substantial sales volumes. BigCommerce

One thing to factor into a 2026 evaluation: BigCommerce changed its pricing structure on June 1, 2026, including fees for some orders processed through "Open Payment Providers" on self-service plans. BigCommerce BigCommerce

When I'd choose WooCommerce

WooCommerce becomes more compelling if your website is already WordPress-centric or you need unusually deep control over the site and data.

It's open source, has a REST API and a large extension ecosystem, and WooCommerce itself says it can scale to very large order volumes. But that flexibility also means you're responsible for more of the hosting, security, performance, plugin and development stack. WooCommerce WooCommerce

What I'd build

For a small retailer, I'd aim for this rather than commissioning a custom ecommerce system:

Shopify → POS/inventory → accounting → email/SMS → shipping → analytics

Keep your product/customer/order data portable, use APIs for anything that becomes strategically important, and avoid putting business-critical logic into obscure theme hacks or one-off apps.

That gives you a relatively simple launch while preserving an upgrade path when you eventually have developers.

If you tell me roughly how many SKUs you have, current annual revenue, whether you already use a POS (Square, Lightspeed, Clover, etc.), and whether you sell B2B, I can narrow this down to a concrete platform + stack and estimated monthly cost.

For a developer building a custom frontend, the “best” headless commerce platform depends mostly on how much of the commerce engine you want to own. The strongest options today fall into a few categories. vendure.ionaturaily.com

ribbsaetersystems.com

My shortlist for a developer-first custom frontend

1. Medusa — probably the best balance of freedom + developer experience

Choose Medusa if you want:

• A Next.js/React frontend
• Full control over checkout, pricing, promotions, fulfillment
• A Node/TypeScript stack end-to-end
• The ability to modify the backend instead of fighting platform constraints

Architecture is closer to “commerce primitives you assemble” than a traditional SaaS store. It’s a strong choice when your product is not a standard Shopify-style catalog. hunchbite.comossalt.com

Typical stack:

Next.js frontend
        |
        |
Medusa API
        |
Postgres + payment/shipping integrations

2. Saleor — best if you love GraphQL

Choose Saleor if:

• Your frontend team prefers GraphQL
• You have complex product models
• You need multi-region, multi-channel, B2B capabilities
• You’re comfortable with Python/Django

Its API model is very clean for frontend developers because the storefront consumes a strongly structured GraphQL API. hunchbite.comossalt.com

3. commercetools — best for enterprise-scale composable commerce

Choose this when:

• You have many systems (ERP, PIM, CMS, loyalty, pricing engines)
• Commerce is one service in a larger architecture
• You have enterprise engineering resources

It gives enormous flexibility but usually requires more architecture work. vendure.ionaturaily.com

4. Shopify headless — best when you want to ship, not build commerce infrastructure

A custom frontend on Shopify gives you:

• Excellent checkout reliability
• Payments, tax, fraud, inventory, admin tooling
• Huge ecosystem

The tradeoff is that your backend customization is constrained by Shopify’s model. vendure.ionaturaily.comwww.askantech.com

If I were choosing for a new custom frontend project:

• Solo developer / small engineering team: Medusa
• GraphQL-first team: Saleor
• Enterprise architecture: commercetools
• Brand wants custom UX but doesn’t want commerce ops headaches: Shopify headless
• Marketplace or unusual checkout flows: Medusa or Saleor

For a modern stack like Next.js + React + TypeScript, I’d start by evaluating Medusa vs Saleor vs Shopify Storefront API. The deciding question is:

“Do I want to customize the commerce engine itself, or only customize the customer experience?”

If you need to rewrite commerce behavior → Medusa/Saleor.
If you mainly need a custom storefront → Shopify headless is often enough. ribbsaetersystems.com

I can also give you a developer-focused comparison of APIs, auth models, webhooks, checkout flows, and Next.js integration patterns if that’s the direction you’re building.

If your core requirement is a marketplace where many independent artisans each have their own seller account, products, orders, commissions, and payouts, I’d narrow the field to CS-Cart Multi-Vendor, Sharetribe, and Mirakl.

My practical shortlist

1. CS-Cart Multi-Vendor — strong fit for an artisan marketplace

cs-cart.com

This is particularly well suited if you're envisioning something like Etsy-style commerce, but want to own the platform.

It provides:

• Individual seller dashboards
• Vendor onboarding and approval
• Vendor-specific storefronts
• Seller commissions and payouts
• Split payments
• Vendor subscriptions/plans
• Vendor ratings
• Product moderation
• Vendor-specific promotions
• Separate vendor checkout
• Inventory management
• Shipping integrations
• API/customization capabilities
• No vendor/product limits according to CS-Cart's current product information www.cs-cart.com/ www.cs-cart.com/

The seller experience is important for artisans: each artisan can manage their own products, orders, inventory and marketplace activity without getting access to another seller's information. www.cs-cart.com/

I'd seriously consider this if your marketplace is primarily physical handmade products.

2. Sharetribe — best if you want to launch/test quickly

sharetribe.com

Sharetribe is designed specifically around marketplace businesses. Sellers can create profiles and listings, and you can configure different transaction/listing types without building everything from scratch. Sharetribe Sharetribe

It's attractive if your priority is:

• Getting an MVP live quickly
• Testing whether artisans and customers will use the marketplace
• Seller profiles/listings
• Messaging
• Payments/transactions
• Different types of marketplace transactions
• Later extending the platform through its APIs/headless architecture

I'd lean toward Sharetribe if you're still validating the business model rather than already planning thousands of sellers.

3. Mirakl — for a much larger operation

mirakl.com

Mirakl is aimed much more at enterprise marketplaces. It has sophisticated seller onboarding, catalog management, order routing, commissions, payouts, KYC, multi-currency and multi-region functionality. Mirakl

It's a very different proposition from a lightweight marketplace builder: Mirakl says most customers go live in 3–6 months, and its current customer base includes large retailers and enterprises. Mirakl

For a startup artisan marketplace, I'd investigate it only if you're expecting enterprise-level complexity and scale from the outset.

What I'd choose for your use case

If you mean:

"I want to build a marketplace where 100s or 1,000s of independent artisans can sign up, create their own shops, upload handmade products, receive orders, and get paid while I take a commission."

Then CS-Cart Multi-Vendor is the platform I'd investigate first.

The key reason isn't simply that it supports multiple sellers; it has marketplace-specific functionality around vendor accounts, commissions, payouts, seller dashboards, moderation, vendor storefronts, inventory, shipping and multi-vendor orders. www.cs-cart.com/ www.cs-cart.com/

If instead your priority is "get an MVP running in weeks and see whether the concept works," I'd look closely at Sharetribe.

If you're building something intended to become a very large, enterprise-grade marketplace, investigate Mirakl.

If you tell me your expected number of artisans (e.g. 100 / 1,000 / 10,000), country, whether products are physical, and whether you need Shopify/WooCommerce integration, I can narrow this down and compare CS-Cart vs Sharetribe vs Shopify + multi-vendor app vs WooCommerce vs Mirakl, including approximate costs and seller payout architecture.

For a one-person print-on-demand shop, I’d start with Etsy if you need customers immediately, or WooCommerce if minimizing ongoing software costs is the priority.

• Etsy: $0.20/listing + 6.5% transaction fee, but you get access to Etsy’s existing marketplace traffic. Tee Verdict
• WooCommerce: Free core software; hosting is typically the main expense, with WooCommerce estimating $25–$350/month depending on the store. WooCommerce
• Shopify: Easiest all-in-one option, but Basic is $29/month annually ($39 monthly) plus payment processing. Shopify

My practical starting setup: Etsy + your POD supplier. Once you're getting consistent sales, add Shopify/WooCommerce rather than paying for a standalone store before you've validated demand.

For B2B workflows like custom catalogs, customer-specific pricing, company accounts, and net terms, you’ll want a platform with native B2B capabilities rather than a DTC platform patched with wholesale apps. The strongest options are: Elogic Commerce Alkali

Elogic Commerce Alkali### How I’d narrow it down

• You are a manufacturer/distributor with complex pricing, thousands of SKUs, dealer networks, RFQs, approvals, or ERP-heavy operations:

→ Adobe Commerce, OroCommerce, or Salesforce Commerce Cloud are usually the category to evaluate. Elogic Commerce Alkali

• You sell DTC today and want wholesale/B2B on the same platform:

→ Shopify B2B is attractive because B2B companies, catalogs, payment terms, buyer permissions, and B2B checkout can live alongside the consumer store. Shopify Help Center

• You need solid B2B but want SaaS simplicity and lower operational overhead:

→ BigCommerce B2B is commonly considered for mid-market teams needing native B2B functionality without building a large commerce stack. TechRepublic Profitvora

A few questions would determine the best fit:

1. Roughly how many SKUs and customer accounts do you manage?
2. Do you need sales rep ordering, RFQ/quote workflows, or just self-service ordering?
3. What ERP/accounting system do you use (NetSuite, SAP, Dynamics, QuickBooks, etc.)?
4. Are you running B2B only, or B2B + DTC in the same storefront?

For an international DTC store where multi-currency + localized checkout are core requirements, I’d generally recommend shopify.com, specifically Shopify Markets.

Why Shopify

• Native multi-currency: Customers can browse and pay in their local currency; Shopify Payments supports multi-currency checkout. Shopify Help Center Shopify Help Center
• Market-specific localization: You can configure currency, language, products, pricing, domains/subfolders, and other experiences by country or region. Shopify Help Center Shopify Help Center
• Localized checkout: Shopify supports regional address forms, local payment methods, and duties/import-tax calculations as part of its international tools. Shopify App Store
• More sophisticated cross-border option: Shopify Managed Markets can use Global-e as the merchant of record, handling things such as foreign tax registration, duties, and import taxes. Shopify Help Center
• Single-store management: You can manage multiple international markets rather than maintaining entirely separate stores. Shopify

How I'd compare the main options

BigCommerce is a serious alternative: its international platform supports localized storefronts, checkout, payment methods, and 100+ currencies. BigCommerce BigCommerce WooCommerce can do international selling too, but multi-currency and multilingual functionality commonly involves additional extensions. WooCommerce

My practical recommendation: if you're starting from scratch and want to sell, say, US + Canada + UK + EU + Australia, I'd choose Shopify + Shopify Markets + Shopify Payments, then consider Managed Markets if you want to offload cross-border tax/duty complexity.

If you tell me your countries/regions, approximate annual revenue, product type, and whether you're B2C or B2B, I can narrow this down between Shopify, BigCommerce, WooCommerce, and a headless setup.

For a dropshipping business where supplier integrations are the priority, Shopify generally offers the strongest ecosystem. Its App Store has a large selection of supplier/sourcing integrations, including DSers, Syncee, Spocket, AutoDS, CJdropshipping, and Shopify Collective. Shopify Help Center Shopify App Store

• Shopify: broadest managed ecosystem; easiest multi-supplier setup.
• WooCommerce: highly flexible, but integrations are more plugin-dependent. WooCommerce
• BigCommerce: worth considering for more complex B2B/catalog requirements.

If you're specifically planning dozens or hundreds of different suppliers, I'd lean toward Shopify + a supplier-sync/automation layer such as Syncee, AutoDS, or custom API/feed integrations, rather than relying on one dropshipping app. eaglelytics.com

For a small handmade-goods shop and a first serious online store, I’d start with shopify.com.

Why it fits someone who isn’t tech-savvy:

• No coding required. You choose a theme, add your products, photos, prices, and shipping information, and Shopify handles the underlying hosting and checkout. Shopify Shopify Help Center
• It can grow with you. The Basic plan is specifically aimed at new businesses launching an online store; you can add more sophisticated features later rather than rebuilding the shop. Shopify Help Center
• Good for handmade sellers who also sell in person. Shopify supports online sales plus in-person selling at markets, craft fairs, and other events through its POS tools. Shopify
• Current Basic pricing: $29/month when billed annually, or $39/month month-to-month, with Shopify Payments' standard online card rate listed as 2.9% + 30¢ in the U.S. Shopify

The alternatives I'd consider

Squarespace offers a 14-day trial and lets you sell products on its paid plans. Squarespace Wix also offers a visual editor and ecommerce plans, with payment acceptance requiring a paid plan. wix.com

My practical recommendation: start with Shopify Basic, keep the design simple, and launch with perhaps 10–20 of your best products rather than trying to build a huge website immediately.

If you tell me what kind of handmade goods you sell, roughly how many products you have, and whether you already sell on Etsy/in person, I can narrow this down to the simplest setup for you.

For a two-person boutique on a tight budget, I’d narrow it to three:

• Square Online — best if you already sell in person with Square. You can start at $0/month, and it connects online orders, inventory, payments, pickup, and local delivery with your Square setup. Square Square
• Big Cartel — best if you have a small catalog and want the lowest possible ongoing cost. It has a free tier for up to 5 products, with paid plans starting around $12–$15/month depending on billing. Shopify Shopify
• Shopify Basic — best if you expect the store to become a significant part of the business. It's $29/month when billed annually ($39 month-to-month) and includes unlimited products, hosting, checkout, inventory, and in-person selling. Shopify

What I'd do in your shoes

If you're already using Square at the boutique, I'd start with Square Online to avoid paying for another system.

If you have fewer than ~50 products and mostly want a simple, attractive web storefront, I'd look seriously at Big Cartel.

If you have dozens/hundreds of products, frequent inventory changes, or plans to grow online, I'd spend the extra ~$15–30/month on Shopify rather than having to migrate later.

One important point: monthly subscription isn't the whole cost. Payment-processing fees, apps, shipping tools, and add-ons can matter more than the headline monthly price. TechnologyAdvice

If you tell me roughly how many products you carry, whether you already use Square for in-store checkout, and your monthly online sales target, I can give you a simple cost comparison for the three.

For a small food subscription-box business, I’d focus less on generic ecommerce features and more on: recurring billing, easy customer self-service, shipping/fulfillment, inventory, failed-payment recovery, and the ability to handle changing box contents.

Here are the main options I’d consider:

1. Shopify — probably the first one I'd investigate

shopify.com is a particularly straightforward starting point. Its free Shopify Subscriptions app supports recurring weekly, monthly, or yearly billing, and customers can pause, skip, cancel, update payment methods, and change shipping information themselves. Shopify Help Center Shopify Help Center

For a food box, you could have something like:

• Monthly Snack Box — $39/month
• Family Box — $59/month
• Premium Box — $79/month
• One-time box — $45

Then later add a specialized subscription app if you need more sophisticated functionality. Shopify itself currently highlights apps such as Recharge and Appstle for more complex subscription models. Shopify

I'd lean this way if you want to launch quickly without having to manage much technology.

2. WooCommerce + WooCommerce Subscriptions

woocommerce.com is worth considering if you already use WordPress or want substantially more control over the store.

WooCommerce Subscriptions supports weekly, monthly, and annual billing, automatic recurring payments through 25+ gateways, failed-payment rebilling, and customer self-service for upgrades, downgrades, suspension and cancellation. WooCommerce

The tradeoff is that you're managing WordPress, WooCommerce, hosting, plugins, updates, etc. The subscription functionality itself is currently a paid extension ($279/year on the official site). WooCommerce

I'd consider it if customization is important enough to justify the extra maintenance.

3. Square

squareup.com is interesting if you're already using Square for POS, payments, or a physical food business.

Square Subscriptions supports recurring weekly, biweekly, monthly, quarterly, semiannual, and annual billing, along with things like trials, pause/resume, checkout links and QR codes. Square

There are some meaningful limitations for a subscription-box model, though—for example, Square currently doesn't support swapping an item on an active subscription, and subscription pickup isn't available as a fulfillment option. Square

I'd favor it when the business is very small and Square is already at the center of your operation.

What I'd choose for a food box

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

Shopify → specialized Shopify subscription app → WooCommerce

The key question is actually how your boxes work.

For example, there's a big difference between:

"Every month I charge $40 and send the same type of box."

and:

"Every month I charge $40, customers can choose 3 items from 12, they can skip months, change their box by a cutoff date, and I need to batch all orders for fulfillment every Tuesday."

The second model puts much more emphasis on subscription management and fulfillment workflows.

If you tell me (1) your expected number of subscribers, (2) monthly price, (3) whether customers choose what's in the box, and (4) whether you're already using Stripe/Square/PayPal, I can narrow this down to a practical 2–3 platform setup and estimate the software/payment costs.

For three retail stores + one ecommerce site + simple location-level inventory, I’d shortlist these:

My pick: Shopify

For your relatively simple requirement, Shopify is probably the cleanest fit. It lets you create the three stores as separate locations, maintain quantities independently at each location, and connect those locations to Shopify POS. Online and in-store sales can update the same inventory system. Shopify Help Center Shopify Shopify Help Center

For example:

• Store A: 12 units
• Store B: 7 units
• Store C: 4 units
• Online availability: determined according to your inventory/fulfillment configuration
• A sale in Store B reduces Store B's inventory.
• You can transfer stock between locations and configure online order routing. Shopify Help Center Shopify

Square is worth considering if your three physical stores are the center of the business. Its multi-store functionality specifically supports location-level stock, transfers, centralized catalog management, and location reporting. Square

BigCommerce makes more sense if the ecommerce side is more sophisticated or you anticipate custom integrations. It supports multi-location inventory, but some location-aware storefront/fulfillment capabilities are more API/integration-oriented. BigCommerce BigCommerce

Bottom line: if you want “three stores, one website, one inventory system, minimal complexity,” I'd start by evaluating Shopify + Shopify POS.

If you tell me roughly how many SKUs you have, whether you already use Square/Shopify/POS hardware, and whether customers need in-store pickup, I can narrow it down further.

For your setup, BigCommerce is worth a close look. Its built-in B2B price lists can set SKU-level prices for individual wholesale accounts or customer groups, which maps well to negotiated customer pricing. BigCommerce BigCommerce

Shopify also handles customer-specific catalogs/pricing, but the most granular direct company-location assignment is on Shopify Plus. Shopify Help Center Shopify Help Center

For a small parts supplier with only a few wholesale customers, I’d compare BigCommerce vs Shopify Plus primarily on pricing complexity, ERP integration, and total cost.

For a small craft-kit subscription business, Shopify is probably the best starting point for flexible subscription management. Its free Shopify Subscriptions app supports weekly/monthly/yearly billing, skipping, pausing, canceling, discounts, and customer self-service. Shopify Help Center Shopify Help Center

• Shopify: easiest all-around; add more advanced subscription apps later. Shopify
• WooCommerce: more customizable if you're comfortable with WordPress; supports custom schedules, plan switching, gifting, and 25+ payment gateways. WooCommerce
• BigCommerce: worth considering if you anticipate a more complex catalog or larger operation. BigCommerce

My practical pick: Shopify if you want to launch quickly without much technical overhead; WooCommerce if maximum customization matters more than simplicity.

For a small team with complex shipping rules + carrier-calculated rates, the strongest options are usually:

How I’d match the platform to your situation

• You need many “if/then” shipping rules (SKU-based rules, regions, exclusions, freight rules, special products):

• Consider WooCommerce or BigCommerce + ShipperHQ. BigCommerce WooCommerce
• You need live carrier quotes but want a small team to operate it easily:

• Shopify + a shipping rules app is often the simplest operational setup. Shopify supports carrier/app-calculated rates and shipping profiles; third-party carrier-calculated shipping may require specific plans or fees. Shopify Help Center Shopify Help Center
• You have unusual fulfillment logic (multiple warehouses, dimensional rules, special handling, mixed carts):

• Look closely at BigCommerce or WooCommerce, where more custom shipping logic is typically exposed. BigCommerce WooCommerce

A few questions would narrow this down:

1. Which carriers do you need (UPS, FedEx, USPS, DHL, freight/LTL, local delivery)?
2. Are your rules mostly based on product/SKU, weight/dimensions, destination, or customer type?
3. Are you starting a new store, or migrating from another platform?

For a free storefront focused on preorders and crowdfunding-style sales, I’d choose based on whether you want a true “campaign” experience or just a normal store that accepts early orders.

My shortlist

My recommendation

If you are selling a physical product:

Start with Shopify + a free preorder app.

You can make a “campaign” page:

• Product story/video
• Funding goal or minimum order quantity
• Early-bird pricing tiers
• Estimated delivery date
• Email waitlist
• Preorder checkout

Shopify’s app ecosystem includes many preorder tools, including apps that add crowdfunding-style features, deposits, waitlists, and presale campaigns. Shopify App Store Shopify App Store

A low-cost launch stack:

• Storefront: Shopify
• Theme: free Shopify theme
• Preorder tool: a free-plan preorder app
• Payments: Shopify Payments/PayPal
• Marketing: email waitlist + social media

If you need $0/month and are testing an idea:

Use Gumroad or Ko-fi first. You can validate demand before investing in a full ecommerce setup.

If the campaign itself is the product:

Use a crowdfunding platform such as BackerKit or a Kickstarter-style platform rather than a normal store. Those are better when you need:

• funding milestones
• backer updates
• reward tiers
• surveys
• community management

A few questions would change my recommendation:

1. Are you selling physical products, digital products, or services?
2. Do you need to collect payment immediately or just collect pledges/waitlist signups?
3. Are you expecting 10 customers or 10,000+ backers?

For an artisan seller who only wants to sell locally, I’d narrow it to Square Online and Ecwid.

My practical shortlist

• Square Online — simplest low-cost starting point. Square has a $0/month entry plan, and its online store supports both in-store/curbside pickup and local delivery. You can define delivery areas by ZIP code or radius, set delivery fees, minimum orders, and delivery timing. Square Square

squareup.com

• Ecwid — good if you want a more flexible little storefront. It supports pickup, delivery zones, ZIP-code restrictions, delivery fees, pickup times, and delivery minimums. Ecwid | E-Commerce Shopping Cart Ecwid | E-Commerce Shopping Cart

ecwid.com

• Shopify — more capable, but probably more than you need initially. It supports pickup and local delivery by radius or postal code, but its broader feature set makes more sense if you expect the shop to grow substantially. Shopify Help Center

shopify.com

What I'd choose

If your model is something like “I make candles/jewelry/baked goods/artisan products, customers order online, and I either deliver nearby or they pick up”, I'd start with Square Online.

You can set up:

Product → customer orders → choose Pickup OR Local Delivery → pay online → you fulfill it.

You don't need to deal with conventional shipping at all. Square also lets you use your own delivery or third-party couriers. Square

If you tell me roughly how many products you sell and whether you already use Square for payments, I can tell you which of Square vs. Ecwid would likely cost you less.

For a shoestring subscription box launch, I’d usually avoid building a custom system and pick a platform that already handles:

• recurring card charges
• failed payment retries (“dunning”)
• customer self-service (skip, pause, cancel)
• subscription changes
• basic inventory/order workflows

Here are the strongest low-cost options:

Subbly Shopify## My recommendation for a lean launch

1. Best “just launch the box” choice: Subbly

For a true subscription box (monthly coffee, snacks, beauty items, pet products, etc.), Subbly is purpose-built. Its lower-tier plans are aimed at getting subscription checkout running without custom development, and it supports payment integrations such as Stripe. Subbly

A typical lean stack:

• Subbly for subscriptions + customer management
• Stripe for payments
• Simple landing page (or Subbly site)
• ShipStation/Shippo later when volume grows

2. Best if you expect a bigger ecommerce brand: Shopify

If the box is only one part of the business (you’ll also sell one-off products, bundles, gifts, etc.), Shopify is often the better foundation. Shopify offers subscription tools, including its own Shopify Subscriptions app, plus third-party subscription apps. Shopify

3. Cheapest if you have technical help: Stripe Billing

If you already have a website and someone can build checkout/customer flows, Stripe can be very cost-efficient. It gives you the billing engine, but you’ll need to create more of the subscription experience yourself. Shopify

What I would avoid at the beginning

• Enterprise subscription tools like Chargebee/Recurly unless you already have significant revenue.
• Building your own recurring billing logic.
• Paying for advanced analytics/CRM features before you have subscribers.

For a first 100–500 subscribers, I’d lean Subbly if the product is a pure subscription box, or Shopify + subscriptions if you want a full ecommerce brand. Subbly Shopify

If you tell me your box type (physical goods vs digital, expected monthly price, and whether you already have a website), I can narrow it down to the cheapest stack.

Yes. If your goal is “test one product for 2–4 weeks without committing to Shopify or another monthly subscription,” there are a few good options.

My shortlist

Payhip's free plan is genuinely $0/month, includes all features and unlimited products, and takes 5% per sale on top of payment-processor fees. It also supports physical products. Payhip Payhip

Big Cartel's Gold plan is also $0 and lets you list up to 5 products, accept cards/PayPal, and run a basic storefront. Big Cartel

Gumroad has no monthly fee, but its direct-sale fee is currently 10% + $0.50 per transaction, before applicable processing/other fees. Gumroad Gumroad

What I'd use for your experiment

If you're selling a physical product, I'd start with Big Cartel if you want it to feel like a tiny conventional ecommerce store.

If you want a landing-page-style sales page → checkout, I'd lean toward Payhip. You can essentially make the whole experiment:

Ad/social post → product page → checkout → payment → order fulfillment

with $0/month while you're testing.

One important distinction: “free” doesn't mean zero cost per sale. Payment processing and, depending on the platform, transaction fees still apply. Payhip Big Cartel

If you tell me what the product is, its selling price, and whether it's physical or digital, I can tell you which of these makes the most sense and what I'd use for the landing page.

For a freelance developer doing custom integrations across many client stores, I’d look hardest at Medusa and WooCommerce, with Saleor as a strong option if you prefer an API-first/headless architecture.

My practical breakdown

🥇 Medusa — probably the most interesting for your use case

Medusa is specifically designed around customization. You can create modules, data models, API routes, workflows, event subscribers, scheduled jobs, admin extensions, and plugins rather than having to bolt everything onto an existing monolith. Medusa Docs Medusa Docs

The particularly useful part for client work is that integrations can become reusable modules/plugins. For example, you could build an ERP connector once and reuse it across multiple client projects. Medusa's plugins can package modules, workflows, API routes, hooks, subscribers, scheduled jobs, and admin extensions. Medusa Docs

Its architecture also explicitly supports third-party integrations through modules and workflows, including cross-system operations such as ERP synchronization. Medusa Docs

If you're comfortable with TypeScript/Node, I'd seriously consider making Medusa your default custom-commerce stack.

🥈 WooCommerce — easiest if clients want conventional WordPress stores

WooCommerce is extremely extensible from a developer's perspective. You have PHP hooks, filters, APIs, custom payment gateways, shipping methods, REST APIs, webhooks, and the entire WordPress ecosystem. The WooCommerce Developer Blog The WooCommerce Developer Blog

Its REST API covers things like products, orders, customers, coupons, and shipping zones, while webhooks can notify external systems about store events. The WooCommerce Developer Blog The WooCommerce Developer Blog

The advantage for a freelancer is client familiarity: many businesses already have WordPress hosting, WordPress skills, and WooCommerce experience.

The downside is architectural complexity. A heavily customized WooCommerce installation can eventually become a collection of plugins, hooks, theme overrides, and WordPress-specific behavior that you have to maintain.

🥉 Saleor — excellent for API-first/headless projects

Saleor takes a different approach: instead of modifying the core, you extend it with apps and APIs. Its backend is API-only, and its extensibility model includes webhooks, metadata, apps, API extensions, and dashboard extensions. GitHub Saleor Commerce

That makes it attractive when your typical client says:

"We have an ERP, PIM, CRM, custom frontend, warehouse system and several external services. Make them all work together."

Saleor also supports self-hosting and lets you build integrations in essentially any language because you're interacting through GraphQL rather than directly with its Python core. Saleor Commerce

What I'd choose as a freelancer

If your business is primarily "I build custom commerce systems and integrations", rather than "I build WordPress websites that happen to sell things," I'd lean toward:

Medusa → default custom-commerce stack
WooCommerce → clients who specifically want WordPress
Saleor → clients wanting sophisticated headless/API-first commerce

The biggest reason I'd put Medusa first is reuse. You can turn solutions you build for client A into modules/plugins/workflows that accelerate client B, rather than repeatedly fighting the platform's extension points. Medusa Docs Medusa Docs

If you tell me your preferred stack (TypeScript, PHP, Python, etc.) and the kinds of integrations you usually build (ERP, Shopify migration, marketplaces, subscriptions, fulfillment, custom pricing, etc.), I can narrow this down considerably.

If your priority is one self-hosted open-source store that handles physical + digital products in the same catalog and checkout, I’d put WooCommerce at the top of the shortlist.

How I’d compare them

Why WooCommerce stands out for your use case: its core product model explicitly supports physical, virtual, and downloadable products. A downloadable product can still require shipping, so you can sell something like physical book + PDF, while purely digital products can bypass shipping. WooCommerce WooCommerce

It also handles mixed orders naturally: a cart can contain physical and digital products, with shipping calculated only for the shippable items. WooCommerce can grant digital access after payment even when the physical portion of the order hasn't shipped yet. WooCommerce

For products with variations, downloads can be attached to individual variations and physical inventory can be managed alongside them. WooCommerce

My practical recommendation

Go with WooCommerce if you want:

• One catalog for physical and digital goods
• Physical + digital products in the same order
• Straightforward inventory/shipping for physical items
• Secure downloadable-file delivery
• A mature self-hosted ecosystem
• The option to add subscriptions, memberships, bundles, licenses, etc. later

woocommerce.com

I'd choose Medusa or Saleor instead if you're specifically building a custom/headless commerce application and have developers who want an API-first architecture. A recent comparison, for example, describes Medusa as TypeScript/REST-oriented and Saleor as Python/GraphQL-oriented, with different customization approaches. Eryx Innovations Lab

Bottom line: for a normal merchant who wants to self-host and sell both physical and digital products without engineering a lot of commerce behavior themselves, WooCommerce is probably the most straightforward fit.

If you tell me roughly how many products/orders you expect and what kinds of digital products you sell (PDFs, software licenses, courses, audio/video, etc.), I can narrow this down between WooCommerce, Medusa, Saleor, and Sylius.

Go with WooCommerce if you want:

WooCommerce is the strongest choice if your priorities are plugin ecosystem + developer/community support. It inherits WordPress’s enormous plugin and developer ecosystem and has extensive third-party integrations. Open Source Groups AFCommerce

For a modern, developer-first/headless stack, Medusa is a strong alternative, especially with TypeScript/React. OSSAlt Open Source Projects

For strong security and compliance controls around payments and customer data, I would shortlist platforms based less on “features” and more on your ability to operate a secure environment: patching, access control, audit logging, payment architecture, hosting model, and compliance ownership.

A practical ranking by security/compliance needs:

My recommendation by scenario

1. Enterprise payments + sensitive customer data

Choose Magento Open Source / Adobe Commerce architecture if you have:

• dedicated security engineering or DevOps
• formal vulnerability management
• SIEM/log monitoring
• strict IAM requirements
• multiple integrations (ERP, CRM, fraud systems)
• large product catalogs or B2B workflows

The tradeoff: you need strong operational maturity. A poorly maintained Magento deployment can still be risky.

2. Strong compliance with lower operational burden

Consider Shopware if you want:

• open-source flexibility
• enterprise features
• modern extensibility
• a vendor ecosystem with documented security practices

Shopware states that its security program includes measures such as ISO 27001 certification and SOC 2 Type II alignment for hosted environments. Shopware

3. Cost-conscious teams

WooCommerce can work if you design it securely:

• never store raw card data
• use hosted payment fields/tokenization
• minimize plugins
• enforce MFA and least privilege
• use managed hosting with patching/WAF capabilities
• maintain vulnerability scanning and backups

WooCommerce notes that PCI DSS responsibility depends on the entire environment, including hosting, plugins, access controls, and payment integrations. WooCommerce

Controls I would require regardless of platform

For a payment/customer-data environment, I would require:

Payment security

• Use a PCI-compliant payment provider with hosted checkout/tokenization
• Do not store card numbers or CVV data
• Separate payment systems from customer-data systems where possible

Identity and access

• MFA for all admin users
• Role-based access control
• Separate developer/staging/production accounts
• Quarterly access reviews

Application security

• Automated security updates and patch SLAs
• Dependency scanning (SCA)
• Web application firewall
• Secure code review for custom modules
• Penetration testing before launch and periodically

Data protection

• Encryption in transit and at rest
• Database encryption/backups
• Customer-data retention policies
• Audit logs for customer-data access

Operations

• Centralized logging/SIEM
• Incident response plan
• Disaster recovery testing
• Vendor/security review process for plugins/extensions

Short answer

If you are a regulated or enterprise retailer, I would start with Magento Open Source/Adobe Commerce or Shopware.

If you are a smaller company, WooCommerce can meet strong security requirements, but only with disciplined hosting, payment architecture, and governance.

If you share:

• annual order volume,
• number of SKUs,
• countries served,
• compliance targets (PCI DSS, SOC 2, HIPAA, GDPR, etc.),
• cloud preference (AWS/Azure/GCP/self-hosted),

I can narrow this to a specific platform and deployment architecture.

Medusa is particularly well-suited if digital downloads are central. Its current docs provide workflows, custom REST APIs, private file storage, authenticated download URLs, and digital-product fulfillment; there’s also a dedicated digital-products plugin with entitlements and expiring download tokens. docs.medusajs.com medusajs.com

Saleor is the main alternative if you prefer GraphQL and a more API-first architecture; it also has a digital-products recipe. saleor.io docs.saleor.io

For a TypeScript-heavy stack, I’d investigate Medusa first.

For an agency building custom frontends for multiple clients, I’d avoid choosing a platform based only on “headless support.” The key question is whether it gives you a repeatable multi-tenant delivery model: one commerce backend strategy, isolated client stores, APIs your frontend team can consume, and operational tooling for non-developers.

Here are the platforms I’d shortlist:

My recommendation by agency model

1. You build 5–50 custom sites/year for different brands
→ Shopify headless is probably the safest default.

Architecture:

Next.js / Remix frontend
        |
Shopify Storefront API
        |
Shopify Admin + apps + integrations

Pros:

• Fast client onboarding
• Merchants already understand Shopify
• Huge app ecosystem
• Lower maintenance burden

Tradeoff:

• Each client is its own Shopify instance; you’re not really operating a multi-tenant SaaS platform.

2. You want “one platform, many client stores”
→ Look at Medusa, Saleor, Spree, or a dedicated multi-tenant commerce backend.

Architecture:

Client Store A ─┐
Client Store B ─┼── Custom Frontend Layer
Client Store C ─┘
                 |
          Multi-tenant Commerce API
                 |
       Catalog / Orders / Customers

This lets your agency build:

• shared frontend components
• tenant-specific branding
• centralized deployments
• reusable integrations
• subscription revenue around hosting/maintenance

3. You serve enterprise clients
→ Consider BigCommerce headless or composable commerce stacks.

Good when clients need:

• multiple regions
• B2B pricing
• ERP integrations
• complex catalogs
• multiple storefront experiences

A stack I’d standardize for a modern frontend agency

Frontend

• Next.js
• React Server Components
• Tailwind/design system
• Vercel or similar hosting

Commerce

• Shopify for standard merchants
• Saleor/Medusa/Spree for platform-style builds

Content

• Contentful, Sanity, or another headless CMS

Search

• Algolia or Elasticsearch/OpenSearch

Payments

• Stripe where possible

If your agency’s goal is “we launch a branded storefront for a new client every month from the same codebase”, I would lean toward a multi-tenant commerce backend (Medusa/Saleor/Spree-style).

If your goal is “we make premium custom storefronts for established brands”, I would standardize on Shopify headless and build your own reusable frontend framework around it.

If your frontend is a custom iOS/Android app, I’d narrow the field to Shopify, Medusa, Saleor, and commercetools. The right choice depends mostly on how much commerce infrastructure you want to build yourself.

Quick comparison

My practical recommendation: Shopify

For a custom mobile app, Shopify is probably the strongest default choice unless you have unusual commerce requirements.

Shopify's Storefront API is explicitly designed for apps, including native iOS, Android, and React Native applications. It handles products, collections, search, carts, pricing, etc., while Shopify's Checkout Kit can present checkout inside the mobile app. Shopify Shopify

The architecture can look like:

┌─────────────────────────────┐
│     Custom Mobile App       │
│                             │
│  iOS / Android / React Native│
└──────────────┬──────────────┘
               │
        Storefront API
               │
               ▼
┌─────────────────────────────┐
│          Shopify            │
│                             │
│ Products                    │
│ Customers                   │
│ Cart                        │
│ Pricing                     │
│ Inventory                   │
│ Orders                      │
│ Checkout / Payments         │
└─────────────────────────────┘

Shopify also provides official mobile libraries and documentation for iOS, Android, and React Native. Shopify Shopify

shopify.dev

When I'd choose Medusa instead

I'd seriously consider Medusa if your app has commerce logic that doesn't fit naturally into Shopify—for example, highly customized checkout, marketplace/multi-vendor behavior, or unusual product/order workflows.

Medusa's Store API is explicitly intended for storefronts including commerce mobile apps, and its APIs are REST-based. Medusa Docs

The tradeoff is that you take on more responsibility for your commerce infrastructure.

When Saleor makes sense

Saleor is particularly interesting if your engineering team prefers GraphQL and a highly API-driven architecture. Saleor describes itself as GraphQL-native and technology-agnostic, with headless storefront and admin APIs. Saleor Commerce Saleor Commerce

I'd investigate it if your app is more of a custom commerce product than a conventional ecommerce storefront.

The key distinction

I'd use this rule:

• "I want to build a great mobile shopping experience without reinventing ecommerce." → Shopify
• "I want to own and heavily customize the commerce engine." → Medusa
• "I want a GraphQL-native, composable commerce backend." → Saleor
• "We're a large enterprise with complex composable commerce requirements." → commercetools

One particularly important point: don't choose based merely on whether a platform has an API. For a mobile app, evaluate the APIs for authentication, customer accounts, cart persistence, checkout, payments, inventory, webhooks, order management, discounts, and offline/poor-connectivity behavior. Checkout is often the part that determines whether an otherwise-good headless platform is actually pleasant to integrate.

If you tell me (1) iOS/Android/React Native, (2) B2C or B2B, (3) approximate catalog size, and (4) whether you need subscriptions/marketplace/multi-vendor, I can give you a much more specific architecture and platform comparison.

Shopify's Storefront API is explicitly designed for apps, including native iOS, Android, and React Native applications. It handles products, collections, search, carts, pricing, etc., while Shopify's Checkout Kit can present checkout inside the mobile app. Shopify Shopify

The architecture can look like:

┌─────────────────────────────┐
│     Custom Mobile App       │
│                             │
│  iOS / Android / React Native│
└──────────────┬──────────────┘
               │
        Storefront API
               │
               ▼
┌─────────────────────────────┐
│          Shopify            │
│                             │
│ Products                    │
│ Customers                   │
│ Cart                        │
│ Pricing                     │
│ Inventory                   │
│ Orders                      │
│ Checkout / Payments         │
└─────────────────────────────┘

Shopify also provides official mobile libraries and documentation for iOS, Android, and React Native. Shopify Shopify

shopify.dev

When I'd choose Medusa instead

I'd seriously consider Medusa if your app has commerce logic that doesn't fit naturally into Shopify—for example, highly customized checkout, marketplace/multi-vendor behavior, or unusual product/order workflows.

Medusa's Store API is explicitly intended for storefronts including commerce mobile apps, and its APIs are REST-based.

The tradeoff is that you take on more responsibility for your commerce infrastructure.

When Saleor makes sense

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.

If your team strongly prefers serverless frontends + Jamstack, I’d shortlist these:

My practical recommendation

1. Shopify Storefront API — probably the easiest fit.

Shopify's Storefront API is framework-agnostic, so your frontend can be built with Next.js, Astro, Gatsby, etc., and deployed independently on serverless/edge infrastructure. Shopify also provides Hydrogen/Oxygen if you want its more integrated serverless approach. Shopify Shopify

This gives you roughly:

Astro / Next.js → Storefront API → Shopify

while Shopify handles catalog, checkout, orders, payments, inventory, etc.

2. BigCommerce — particularly compelling if you want a conventional Jamstack frontend.

BigCommerce explicitly supports headless builds with Next.js, Gatsby, and Nuxt, and exposes REST and GraphQL APIs. Its Catalyst stack is specifically built around Next.js, React Server Components and its GraphQL Storefront API. BigCommerce BigCommerce

Next.js / Astro / Gatsby → GraphQL → BigCommerce

3. Saleor — I'd look closely at this if your developers want an API-native architecture.

Saleor is GraphQL-native and designed so the storefront and commerce backend are completely decoupled. It supports arbitrary frontend/BFF stacks and uses APIs/webhooks rather than requiring platform-specific frontend plugins. Saleor Commerce

4. commercetools — excellent architectural fit, but usually justified by more complex commerce requirements.

It's explicitly API-first/headless and designed around composable commerce, so it works very naturally with independently deployed frontend applications. commercetools

5. Medusa — attractive if "serverless frontend" is more important than having a fully managed commerce backend. It's open source and highly customizable, but you're taking on substantially more infrastructure responsibility than with Shopify or BigCommerce. Vendure

How I'd choose

• Want the least operational work: Shopify
• Want SaaS + strong headless/Jamstack support: BigCommerce
• Want GraphQL/open architecture: Saleor
• Want maximum composability at enterprise scale: commercetools
• Want open-source/custom commerce logic: Medusa

One important distinction: Jamstack doesn't require the commerce backend itself to be serverless. Your storefront can be statically generated/edge-rendered and call commerce APIs for dynamic operations such as cart and checkout. That's generally the architecture I'd recommend rather than trying to make the entire commerce system serverless.

If you tell me your frontend framework (Next.js, Astro, Gatsby, etc.), approximate SKU/order volume, B2B vs B2C, and whether you need custom checkout, I can narrow this to 2–3 architectures and show what the stack would look like.

This gives you roughly:

Astro / Next.js → Storefront API → Shopify

while Shopify handles catalog, checkout, orders, payments, inventory, etc.

2. BigCommerce — particularly compelling if you want a conventional Jamstack frontend.

BigCommerce explicitly supports headless builds with Next.js, Gatsby, and Nuxt, and exposes REST and GraphQL APIs. Its Catalyst stack is specifically built around Next.js, React Server Components and its GraphQL Storefront API. bigcommerce.com docs.bigcommerce.com

Next.js / Astro / Gatsby → GraphQL → BigCommerce

3. Saleor — I'd look closely at this if your developers want an API-native architecture.

Saleor is GraphQL-native and designed so the storefront and commerce backend are completely decoupled. It supports arbitrary frontend/BFF stacks and uses APIs/webhooks rather than requiring platform-specific frontend plugins.

4. commercetools — excellent architectural fit, but usually justified by more complex commerce requirements.

It's explicitly API-first/headless and designed around composable commerce, so it works very naturally with independently deployed frontend applications.

5. Medusa — attractive if "serverless frontend" is more important than having a fully managed commerce backend. It's open source and highly customizable, but you're taking on substantially more infrastructure responsibility than with Shopify or BigCommerce.

How I'd choose

If your main criterion is developer experience for modern frontend frameworks, the shortlist I’d focus on is Shopify Hydrogen, Medusa, Saleor, and commercetools. There isn't a single objective "best," because they optimize for different kinds of frontend/backend flexibility.

Developer-tooling comparison

Shopify/Hydrogen

For a React/modern-JavaScript frontend, Shopify currently has one of the most mature developer experiences.

Its Storefront API is GraphQL, and Shopify provides official libraries for working with it. Hydrogen React provides components, hooks, utilities, and a Storefront API client that can also be used outside Hydrogen in other React applications. Shopify Shopify

The TypeScript experience is particularly good: Shopify publishes generated Storefront API types and a GraphQL schema that can be plugged into IDE tooling for autocomplete and validation. Shopify Shopify

Hydrogen itself also provides CLI tooling, commerce primitives, caching/SEO infrastructure, and deployment integration with Oxygen. Shopify Shopify

An interesting 2026 development is Shopify's Hydrogen developer preview, which decouples Hydrogen's commerce SDK/primitives from React Router so they can be used with other JavaScript frameworks and runtimes, including Next.js. Shopify

Best fit: React/TypeScript teams that want a highly polished SDK ecosystem and don't mind Shopify being the commerce backend.

Medusa

Medusa is particularly compelling if you want Next.js + TypeScript + control over the commerce backend.

Its current JS SDK is explicitly designed for custom storefronts and admin customizations, with a separate @medusajs/types package for TypeScript. Medusa Documentation Its Store API is REST-based and has an OpenAPI specification, which makes it straightforward to integrate with other tooling. Medusa Documentation

Medusa also explicitly separates the storefront from the commerce server, allowing you to choose the frontend technology you're comfortable with. Medusa Documentation

Best fit: developers who want a JavaScript/TypeScript-native, open-source commerce engine that they can heavily customize.

Saleor

Saleor is especially attractive if your team prefers GraphQL-first development.

You can build the storefront independently of the commerce backend, which makes Next.js/React/Astro/etc. viable frontend choices. Its architecture is particularly well suited to teams that want strongly typed GraphQL workflows and a clean API boundary.

The tradeoff is that backend customization moves you into Saleor's Python/Django ecosystem rather than staying entirely in JavaScript/TypeScript. That's an important consideration for a JS-heavy team.

Best fit: GraphQL-oriented teams, especially where multi-channel/B2B requirements and backend API design matter heavily.

commercetools

commercetools is worth considering if you're building a large enterprise composable-commerce architecture. Its API-first approach gives frontend teams considerable freedom, but the overall platform is more enterprise-oriented than developer-friendly in the "spin up a Next.js project this afternoon" sense.

It's generally more appropriate when you're deliberately assembling commerce from multiple services rather than looking for an integrated developer experience.

My practical take

If I were evaluating them specifically on frontend developer tooling, I'd think about them this way:

• React/TypeScript + fastest polished developer experience: Shopify Hydrogen
• Next.js + maximum backend customization: Medusa
• Next.js/React + GraphQL-centric architecture: Saleor
• Enterprise composable architecture: commercetools

One important distinction: "best SDK" and "best headless commerce backend" aren't necessarily the same thing. Shopify's frontend tooling is exceptionally mature, but you're accepting Shopify's underlying commerce model. Medusa gives you substantially more ownership of the commerce domain, while Saleor gives you a very clean GraphQL-centric boundary.

If you're specifically building with Next.js + React + TypeScript, I'd narrow the decision to Shopify vs. Medusa vs. Saleor and compare them on SDK ergonomics, generated types, cart/checkout APIs, caching, webhooks, local development, testing, and how painful custom business logic is.

Its Storefront API is GraphQL, and Shopify provides official libraries for working with it. Hydrogen React provides components, hooks, utilities, and a Storefront API client that can also be used outside Hydrogen in other React applications. Shopify Shopify

The TypeScript experience is particularly good: Shopify publishes generated Storefront API types and a GraphQL schema that can be plugged into IDE tooling for autocomplete and validation. Shopify Shopify

Hydrogen itself also provides CLI tooling, commerce primitives, caching/SEO infrastructure, and deployment integration with Oxygen. Shopify Shopify

An interesting 2026 development is Shopify's Hydrogen developer preview, which decouples Hydrogen's commerce SDK/primitives from React Router so they can be used with other JavaScript frameworks and runtimes, including Next.js. Shopify

Best fit: React/TypeScript teams that want a highly polished SDK ecosystem and don't mind Shopify being the commerce backend.

Medusa

Medusa is particularly compelling if you want Next.js + TypeScript + control over the commerce backend.

Its current JS SDK is explicitly designed for custom storefronts and admin customizations, with a separate @medusajs/types package for TypeScript. Medusa Documentation Its Store API is REST-based and has an OpenAPI specification, which makes it straightforward to integrate with other tooling. Medusa Documentation

Medusa also explicitly separates the storefront from the commerce server, allowing you to choose the frontend technology you're comfortable with. Medusa Documentation

Best fit: developers who want a JavaScript/TypeScript-native, open-source commerce engine that they can heavily customize.

Saleor

Saleor is especially attractive if your team prefers GraphQL-first development.

You can build the storefront independently of the commerce backend, which makes Next.js/React/Astro/etc. viable frontend choices. Its architecture is particularly well suited to teams that want strongly typed GraphQL workflows and a clean API boundary.

The tradeoff is that backend customization moves you into Saleor's Python/Django ecosystem rather than staying entirely in JavaScript/TypeScript. That's an important consideration for a JS-heavy team.

Best fit: GraphQL-oriented teams, especially where multi-channel/B2B requirements and backend API design matter heavily.

commercetools

commercetools is worth considering if you're building a large enterprise composable-commerce architecture. Its API-first approach gives frontend teams considerable freedom, but the overall platform is more enterprise-oriented than developer-friendly in the "spin up a Next.js project this afternoon" sense.

It's generally more appropriate when you're deliberately assembling commerce from multiple services rather than looking for an integrated developer experience.

My practical take

If I were evaluating them specifically on frontend developer tooling, I'd think about them this way:

• React/TypeScript + fastest polished developer experience: Shopify Hydrogen
• Next.js + maximum backend customization: Medusa
• Next.js/React + GraphQL-centric architecture: Saleor
• Enterprise composable architecture: commercetools

One important distinction: "best SDK" and "best headless commerce backend" aren't necessarily the same thing. Shopify's frontend tooling is exceptionally mature, but you're accepting Shopify's underlying commerce model. Medusa gives you substantially more ownership of the commerce domain, while Saleor gives you a very clean GraphQL-centric boundary.

If you're specifically building with Next.js + React + TypeScript, I'd narrow the decision to Shopify vs. Medusa vs. Saleor and compare them on SDK ergonomics, generated types, cart/checkout APIs, caching, webhooks, local development, testing, and how painful custom business logic is.

Yes. For a headless, API-first marketplace with multiple independent sellers, the strongest options I’d investigate are:

How I'd distinguish them

Vendure is interesting if your marketplace is central to the product rather than an ecommerce store that happens to have sellers. Vendure explicitly added marketplace APIs for things such as order splitting, shipping, payments and platform fees, and provides a reference multi-vendor implementation. Vendure GitHub

Medusa is attractive if you have a strong TypeScript team and want maximum control over the marketplace domain. Its architecture lets you create a custom vendor module, associate vendors with products/orders, expose vendor-specific APIs, and implement order-splitting workflows. Medusa Docs Medusa Docs

Saleor is particularly compelling if you prefer GraphQL and want to model the marketplace using its flexible data model, warehouses, permissions and app framework. Saleor's own marketplace solution specifically describes vendor portals, commission tracking and payment splitting as extensible components. Saleor Commerce

One important architectural distinction

For a marketplace, I'd make sure the platform can represent this flow natively or cleanly:

Customer → Cart → Seller A + Seller B → split orders → seller-specific fulfillment → seller payouts/commission

That's substantially different from ordinary multi-store commerce. You also need to decide whether the platform handles seller onboarding, KYC, commissions, split payments, refunds, shipping, taxes and payouts, or whether you'll layer something like Stripe Connect around the commerce engine.

If you tell me your stack (e.g. Next.js/TypeScript), physical vs digital goods, expected number of sellers, and whether sellers need their own dashboards, I can narrow these down and compare the APIs/data models for your exact marketplace architecture.

For maximum long-term portability, I’d choose an open-source, self-hostable platform—with Saleor as a particularly strong fit. It is API-only, open source, self-hostable, and designed around external apps/extensions rather than proprietary plugins. Saleor Commerce Saleor Commerce

If your team is primarily TypeScript/Node.js, Medusa is another strong option; its core modules are open source and its framework is designed for custom commerce applications. github.com

The bigger portability rules are: own your data, keep the storefront separate, avoid proprietary extensions, use standard payment/search/PIM/ERP integrations, and make your business logic independently deployable.

If you’re solo, cash-constrained, and want to get a dropshipping store live quickly, I’d narrow it to two choices:

1. Shopify — fastest path to a conventional store

Shopify is probably the simplest option if you want a proper storefront, checkout, product catalog, order management, and integrations without dealing with hosting or technical setup.

• Shopify’s Basic plan is currently $29/month when billed annually ($39 month-to-month). Shopify
• Shopify currently advertises 3 days free, then $1/month for 3 months. Shopify
• Basic supports a full online store, unlimited products, themes, payments, and selling through social channels. Shopify Help Center
• There are also lots of third-party dropshipping integrations, which can reduce manual order processing.

Best fit if: you can afford roughly $30/month and value speed and simplicity.

shopify.com

2. Big Cartel — cheapest way to test the idea

Big Cartel has a genuinely free plan, making it interesting if your budget is extremely tight.

• Its Gold plan costs $0 and supports up to 5 product listings. Big Cartel
• Big Cartel says you can launch in about 30 minutes or less. Big Cartel
• Its paid Platinum plan starts at $15/month and adds features such as more products, custom domains, shipping labels, and integrations. Big Cartel

Catch: the free plan's 5-product limit and smaller ecosystem can become restrictive for a typical dropshipping operation.

bigcartel.com

What about WooCommerce?

WooCommerce itself is free, but you need WordPress hosting and potentially paid extensions. WooCommerce estimates hosting at roughly $25–$350/month for most stores, depending on requirements. WooCommerce

So although the software is free, I wouldn't choose it for your specific "start fast with little money" requirement unless you're already comfortable with WordPress.

woocommerce.com

My practical setup for you

I'd do Shopify Basic + one product (or a very small catalog) + free/cheap theme + organic TikTok/Instagram/Reels traffic initially. Don't spend your limited cash on a fancy theme, logo package, or a pile of apps before you've demonstrated that someone actually wants the product.

If your budget is literally $0–$20 to start, test with Big Cartel first. If you have ~$30–$50 available, Shopify gives you a much more complete starting environment.

If you tell me your starting budget (e.g. $50, $100, $250) and whether you plan to sell through TikTok, Instagram, paid ads, or a standalone website, I can map out the cheapest launch stack for you.

For a custom dropshipping site where API-driven integrations are the priority, I’d lean toward Medusa.

Why Medusa fits

Medusa is particularly well suited when you expect to build your own supplier, inventory, fulfillment, pricing, and automation logic rather than simply put a custom frontend on top of an existing commerce platform.

• API-first: Medusa exposes Store and Admin REST APIs, plus a JS SDK and OpenAPI specs. Medusa Docs Medusa Docs
• Highly customizable: You can create your own modules, workflows, data models, and API routes inside the commerce backend. Medusa Docs Medusa Docs
• Good for supplier integrations: Its module/workflow architecture is designed for integrating third-party systems and orchestrating operations across them. Medusa Docs Medusa Docs
• Dropshipping/marketplace-friendly: Medusa explicitly documents marketplace architectures involving vendors, vendor-specific products, and splitting orders across vendors. Medusa Docs
• You control the stack: PostgreSQL, Node/TypeScript, your frontend, integrations, and deployment can all be customized rather than fitting everything into a SaaS platform's constraints. Medusa Docs

How I'd compare the main choices

Shopify + Hydrogen is compelling if you want to outsource more of the commerce infrastructure. Hydrogen provides Shopify-specific API clients and an optimized React Router stack, while Shopify's Storefront API exposes products, carts, checkout, and other commerce functionality through GraphQL. Shopify Shopify Shopify

For your specific architecture, I'd probably use:

Next.js/React storefront → Medusa API → PostgreSQL

with integrations such as:

Supplier APIs → custom Medusa modules/workflows → inventory/products

and

Order → supplier routing → fulfillment API → tracking → customer

That gives you a clean place to implement things like supplier failover, product syncing, dynamic margins, inventory reconciliation, automated order routing, and multi-supplier fulfillment without fighting the platform.

If your goal is "I want to build the commerce engine itself around supplier APIs", Medusa is the direction I'd investigate first. If your goal is "I want a custom frontend but don't want to operate much commerce infrastructure," Shopify becomes more attractive.

For a high-volume dropshipping business with multiple warehouses/3PLs, I’d generally structure the stack as:

Shopify (or another storefront) + Cin7 Core as the inventory/order-management layer.

How I’d compare the main options

My pick for your situation: Cin7 Core

Cin7 Core is specifically designed to act as the centralized inventory/order layer. It supports multiple warehouse locations, inventory transfers, purchase orders, order management, and integrations with platforms such as Shopify, Amazon, WooCommerce, BigCommerce, eBay and Walmart. Cin7 Core Cin7 Core

Its multi-warehouse functionality is particularly relevant: Cin7 describes centralized visibility across warehouses and 3PLs, automatic inventory updates, transfers between locations, and routing orders toward appropriate fulfillment locations. Cin7

It also supports substantial order volumes: its current Core plans list up to 120,000 sales orders/year on Advanced, with additional order volume available, while inventory locations are listed as unlimited. Cin7

Where Shopify fits

Shopify is excellent as the customer-facing ecommerce platform, and its native location system can track inventory separately across warehouses, dropshippers and fulfillment services. Shopify can also route orders based on inventory availability and proximity. Shopify Help Center Shopify Help Center

But once you have many SKUs + several warehouses/3PLs + multiple sales channels + high order volume, I'd avoid making Shopify your only inventory-management system. I'd let Shopify handle the storefront/customer experience and have a dedicated inventory/order-management system serve as the operational source of truth.

A scalable architecture

Shopify stores
Amazon
eBay
Walmart
Other sales channels
        ↓
     Cin7 Core
        ↓
 ┌──────┼────────┐
 ↓      ↓        ↓
WH #1  WH #2    3PLs
        ↓
   Shipping systems

This becomes especially valuable if you're doing something like 10,000+ orders/month, hundreds/thousands of SKUs, multiple suppliers, and geographically distributed fulfillment.

If you tell me roughly monthly orders, number of SKUs, number of warehouses/3PLs, and sales channels (Shopify/Amazon/eBay/Walmart/etc.), I can compare Cin7 vs Linnworks vs Shopify vs BigCommerce specifically for your scale, including likely architecture and where each one starts becoming a bottleneck.

If your main requirement is connecting to lots of third-party supplier marketplaces, I’d separate “broadest integrations” into two things: the ecommerce platform itself, and the supplier/multichannel middleware sitting between it and suppliers.

Based on the current integration ecosystems, the main contenders are:

If supplier marketplaces are the core requirement

Shopify is probably the first platform I'd investigate. Its App Store currently has hundreds of apps just in the sourcing/dropshipping category, including apps that synchronize supplier catalogs, inventory, orders and fulfillment. Shopify App Store Shopify App Store

apps.shopify.com

However, if you're talking about dozens or hundreds of suppliers, I'd seriously consider an architecture like:

Shopify / BigCommerce / Adobe Commerce → integration hub → supplier marketplaces

rather than building a separate direct integration for every supplier.

Adobe Commerce is particularly strong if you expect unusual supplier APIs or complicated catalog/order transformations: it has REST/GraphQL APIs, webhooks, App Builder and API Mesh specifically designed for connecting third-party systems. Adobe says its ecosystem includes “thousands of integrations and extensions.” Adobe Developer Adobe for Business

BigCommerce is also unusually integration-friendly: its Channels Toolkit is explicitly designed for connecting external marketplaces, while its APIs support integrations with ERP, order management, accounting, shipping and fulfillment systems. BigCommerce BigCommerce

My practical shortlist

If you tell me which supplier marketplaces you need to connect to (e.g. Faire, Alibaba, Ankorstore, Amazon, eBay, Walmart, Spocket, Syncee, etc.), I can make a supplier-by-supplier integration matrix for Shopify vs BigCommerce vs Adobe Commerce and identify which one gives you the fewest custom integrations.

For a small POD dropshipping team where custom previews and personalization are core to the product, I’d lean toward Shopify.

The important distinction is that the store builder itself isn’t what gives you the best personalization experience—you’ll generally pair Shopify with a dedicated product-personalizer app.

My recommendation: Shopify + a personalization app

Why it fits a small team:

• Strong POD ecosystem. Shopify currently has hundreds of POD apps with personalization capabilities, including Printful, Printify, Customily, Teeinblue, and others. Shopify App Store Shopify App Store
• Excellent live previews. Apps such as Customily, Teeinblue, and Zepto can provide real-time previews while customers add names, text, images, colors, etc. Shopify
• Good automation potential. You can have the personalization data/design flow through to your POD supplier rather than having your team manually recreate every order.
• Large ecosystem. If your requirements become more sophisticated—conditional options, multiple print areas, dynamic pricing, customer-uploaded images, etc.—there are specialized apps rather than needing to rebuild the store.
• Relatively easy for a small team to operate. You can keep the storefront, checkout, products, payments, analytics, and apps in one ecosystem.

One caveat: Printful's native personalization isn't a complete customer-facing designer. For example, Printful says its native Shopify personalization currently focuses on text and requires the customer-input portion to be handled separately; Printful specifically documents using Zepto for this. Printful Help Center Printful Help Center

How I'd structure the stack

If your products are things like "upload your photo → position it → add text → see exactly what the mug/shirt/poster will look like," I'd investigate Customily or Teeinblue first. Shopify's own 2026 guide specifically highlights Customily, Teeinblue, and Zepto for different types of customization. Shopify

What about WooCommerce?

WooCommerce is the main alternative I'd consider.

It can produce very sophisticated customization experiences, including live previews and print-ready customer designs. Its 2026 documentation describes product designers that generate print-ready designs directly with orders. WooCommerce

I'd choose WooCommerce if your team is comfortable managing WordPress, plugins, hosting, and technical maintenance. For a small team that primarily wants to sell rather than maintain infrastructure, Shopify is generally a simpler operating model.

What I'd avoid

I wouldn't make Wix my first choice if advanced personalization is central to the business. Wix gives you considerable control over product-page design, but the POD/personalization ecosystem is less compelling for this particular use case. Wix's own documentation focuses heavily on customizing the product-page presentation rather than providing the specialized POD personalization ecosystem Shopify has. Wix Help Center

Bottom line:
Shopify + a serious personalization app + Printful/Printify is the stack I'd start with for a small team. If personalization is the main selling point, I'd spend more time choosing the personalization engine than choosing between Shopify and other store builders.

If you tell me what products you're selling (shirts, mugs, jewelry, wall art, etc.) and exactly what customers need to customize, I can narrow this down to a specific Shopify + personalization + POD stack and compare the likely monthly costs.

For a solo founder selling low-margin dropship products, the fee structure matters a lot more than it does for a high-margin brand. Based on current U.S. pricing, I’d look at these first:

Big Cartel explicitly charges 0% transaction fees, with payment processing charged separately by Stripe/PayPal. Big Cartel Big Cartel WooCommerce likewise has no platform/revenue share, although you have to pay for hosting and potentially extensions. WooCommerce Shopify Basic is currently $29/month when billed annually, with card rates starting at 2.9% + $0.30. Shopify Square's free online plan currently charges 3.3% + $0.30 for online payments. Square

For your particular business

If minimizing fixed + transaction costs is the priority:

1. WooCommerce — potentially the lowest total cost once you're doing meaningful volume, particularly if you can get inexpensive hosting and use WooPayments/Stripe. There is no platform transaction fee. WooCommerce
2. Big Cartel — very attractive if your catalog is relatively small and you want simplicity. 0% platform transaction fees is especially useful for low-margin products. Big Cartel
3. Shopify — considerably more expensive on fixed costs, but you get a much more mature dropshipping ecosystem and easier operations. Its Basic plan is $29/mo annually and $39/mo month-to-month. Shopify
4. Square — inexpensive to start, but its 3.3% + $0.30 online processing on the Free plan makes it less attractive for a low-margin dropshipping store. Square

One important wrinkle: with low-priced dropship products, the $0.30 fixed payment fee can hurt more than the percentage. A $15 sale at 2.9% + $0.30 costs about $0.74, or 4.9% of revenue, before your product/shipping/advertising costs.

So if, for example, you're selling $15–$30 products at 10–20% gross margins, I'd optimize around total cost per order, not just monthly subscription price.

If you tell me your average selling price, product cost, monthly order volume, and whether you're using AliExpress/DSers, CJ, Zendrop, etc., I can calculate the actual monthly profit difference between WooCommerce, Big Cartel, Shopify, and the other realistic options.

For a dropshipping niche blog → store strategy, I’d generally choose Shopify—not because its raw SEO is necessarily superior to every competitor, but because it gives you a strong combination of blogging, ecommerce, technical SEO, conversion infrastructure, and relatively low maintenance.

How I’d compare the main options

Shopify: probably the best balance

Shopify has a native blogging system, lets you edit SEO titles, descriptions and URLs, automatically generates things such as sitemap.xml, robots.txt, and canonical tags, and gives you control over SEO for products, collections, pages and blog posts. Shopify Help Center Shopify Help Center

That makes this architecture straightforward:

Domain → topical blog → informational articles → comparison/buying guides → collections → products

For example, imagine your niche is ergonomic desk accessories:

• /blog/best-desk-setup-for-back-pain
• /blog/monitor-height-guide
• /blog/standing-desk-vs-sitting-desk
• /blog/best-desk-accessories-for-small-spaces
• /collections/ergonomic-desk-accessories
• /products/ergonomic-foot-rest

The important part is that the blog isn't a separate SEO property. It can build topical relevance and internal links toward the commercial pages on the same domain.

Shopify itself recommends mapping informational/question-based queries to blog content and broader commercial/category terms to collection pages. Shopify

Where WordPress + WooCommerce can beat Shopify

If your strategy is 70–80% content/SEO and 20–30% ecommerce, I'd seriously consider WordPress + WooCommerce.

WordPress gives you considerably more control over the publishing environment, information architecture, content templates, internal linking, taxonomies, schema implementations, and SEO tooling.

That's useful if you intend to build something closer to:

"authority publication that happens to sell products"

rather than:

"store that has a large blog."

The tradeoff is operational complexity: hosting, updates, plugins, security, performance and technical SEO become much more your responsibility.

The distinction I'd make

Choose Shopify if:

• You're actually going to dropship products.
• You want to launch quickly.
• You want the store and content on one domain.
• You don't want to spend much time maintaining WordPress.
• Your blog is an important acquisition channel but isn't the entire business.

Choose WooCommerce/WordPress if:

• Organic search is your primary acquisition strategy.
• You're planning hundreds/thousands of genuinely useful articles.
• You want maximum control over content architecture.
• You're comfortable managing a more technical stack.
• You may eventually turn the site into a large niche publication/affiliate + ecommerce property.

BigCommerce is also a legitimate option; its current SEO guidance emphasizes metadata control, customizable URLs, content optimization, indexation controls, rich content and optimized landing pages. BigCommerce

For your specific strategy

I'd lean Shopify + serious content architecture, rather than trying to find an ecommerce platform with a theoretical SEO advantage.

The bigger SEO opportunity is how you structure the site, not whether the platform is Shopify vs. WooCommerce.

A good funnel would be:

Informational search
→ educational article
→ related comparison/buying guide
→ collection/category
→ product
→ email capture
→ sale

For example:

"how to choose a camping pillow"
↓
"best camping pillows for side sleepers"
↓
/collections/camping-pillows
↓
specific products

That approach gives you multiple search-intent entry points rather than expecting product pages alone to rank. Shopify's own SEO guidance similarly emphasizes matching pages to search intent and creating original content rather than relying on manufacturer descriptions. Shopify

Bottom line: If you're a solo operator or small team doing dropshipping, Shopify is probably the practical choice. If you're deliberately building an SEO-first niche media site with commerce attached, WordPress + WooCommerce gives you more content control.

If you tell me the niche you're considering, I can also map out the ideal blog → category → product SEO architecture, including the types of keywords I'd target at each stage.

If your main requirement is automatically deciding which dropship supplier gets each line item, splitting mixed-supplier orders, and sending each supplier the appropriate fulfillment request, I’d look at these three:

My take

Order Desk is probably the first platform I'd evaluate for your use case. Its rules engine can split orders, filter them, and automatically send the resulting orders to different fulfillment services. It also specifically supports splitting Shopify orders by vendor, which maps closely to a dropship-partner model. OrderDesk Help Order Desk Order Desk

Extensiv becomes particularly interesting if your routing logic is more sophisticated—for example:

Customer order → determine supplier based on SKU → check availability → split order → choose supplier/warehouse → send PO → receive tracking → update storefront.

Its orderbots can split line items based on availability or product rules and then route the resulting orders to particular warehouses/vendors. Extensiv also explicitly supports dropship vendors and inventory/order imports from them. Extensiv Extensiv Extensiv

ShipStation is a good choice if shipping operations are a major part of what you're trying to automate. Its current Order Routing can choose fulfillment locations based on inventory and destination and split an order when different items need different locations. Its Dropship Manager can also delegate orders to different vendor accounts. ShipStation Help ShipStation Help

If you're already on Shopify, its native routing can prioritize locations based on inventory, destination, minimizing splits, or custom location attributes. But for a network of independent dropship suppliers with different rules and integrations, I'd generally investigate a dedicated OMS such as Order Desk or Extensiv rather than relying solely on Shopify's native routing. Shopify Help Center

The key question

The best choice depends heavily on how your suppliers receive orders. For example, if you have:

• 20 suppliers
• each supplier carries different SKUs
• some suppliers have overlapping SKUs
• you want fallback supplier logic when Supplier A is out of stock
• orders can contain products from 2–4 suppliers
• suppliers receive orders through API, email, FTP, EDI, etc.
• tracking needs to flow back automatically to Shopify

…then I'd narrow the comparison to Order Desk vs. Extensiv.

If you tell me your storefront (Shopify, WooCommerce, Amazon, etc.), number of suppliers, approximate monthly orders, and how suppliers accept orders (API/EDI/email/CSV), I can map out exactly how I'd implement the routing workflow on each platform.

Customer order → determine supplier based on SKU → check availability → split order → choose supplier/warehouse → send PO → receive tracking → update storefront.

Its orderbots can split line items based on availability or product rules and then route the resulting orders to particular warehouses/vendors. Extensiv also explicitly supports dropship vendors and inventory/order imports from them. extensiv.com help.extensiv.com extensiv.com

ShipStation is a good choice if shipping operations are a major part of what you're trying to automate. Its current Order Routing can choose fulfillment locations based on inventory and destination and split an order when different items need different locations. Its Dropship Manager can also delegate orders to different vendor accounts. help.shipstation.com help.shipstation.com

If you're already on Shopify, its native routing can prioritize locations based on inventory, destination, minimizing splits, or custom location attributes. But for a network of independent dropship suppliers with different rules and integrations, I'd generally investigate a dedicated OMS such as Order Desk or Extensiv rather than relying solely on Shopify's native routing.

The key question

The best choice depends heavily on how your suppliers receive orders. For example, if you have:

For a custom storefront centered on recurring subscription plans and APIs, I’d put Shopify + Hydrogen/Storefront API at the top of the shortlist, with Saleor and Medusa as alternatives if you want more backend control.

My recommendation: Shopify headless

Shopify is particularly compelling if recurring subscriptions are a core business feature rather than something you want to build from scratch.

Its Storefront API is GraphQL-based and explicitly supports products, carts, checkout, and selling plans for subscriptions. You can use it with Hydrogen, Next.js, or essentially any frontend framework. Shopify Shopify

For subscriptions, Shopify has a useful underlying model:

• SellingPlanGroup — groups subscription options such as weekly/monthly plans.
• SellingPlan — defines billing, delivery, pricing, and recurring behavior.
• SellingPlanAllocation — connects a variant to a particular subscription plan and exposes the resulting pricing. Shopify Shopify Shopify
• The Storefront API can retrieve subscription products and create carts containing subscription line items. Shopify
• Hydrogen has an official subscription implementation pattern, including displaying plans, adding subscription products to carts, and building subscription-management UI. Shopify

A typical architecture would be:

                 ┌──────────────────────┐
                 │  Custom Storefront   │
                 │ Next.js / Hydrogen   │
                 └──────────┬───────────┘
                            │
                       GraphQL API
                            │
                 ┌──────────▼───────────┐
                 │       Shopify        │
                 │ Products / Cart      │
                 │ Customers / Orders    │
                 │ Selling Plans         │
                 └──────────┬───────────┘
                            │
                 ┌──────────▼───────────┐
                 │ Subscription App     │
                 │ Billing / Lifecycle  │
                 └──────────────────────┘

The important distinction is that Shopify's selling-plan infrastructure handles the commerce representation of subscriptions, while a subscription app/integration generally handles the subscription lifecycle. Shopify's own Hydrogen documentation explicitly requires installing a subscriptions app for this implementation. Shopify

When I'd choose Saleor instead

Saleor makes more sense if API ownership and architectural control are more important than minimizing operational work. Saleor is GraphQL-native and designed around headless/composable commerce, with storefront and admin APIs intended to be decoupled from the frontend. Saleor Commerce Saleor Commerce

I'd investigate Saleor particularly if you need:

• Your own subscription/billing domain model
• Heavy customization of checkout/order logic
• Multiple commerce channels
• An open-source foundation
• A GraphQL-first architecture
• Your own services sitting between the storefront and commerce engine

The tradeoff is that you should expect to design more of the subscription system yourself.

When I'd choose Medusa

Medusa is worth considering if your engineering team is strongly TypeScript/Node.js-oriented and wants to own the commerce backend. Its modular architecture is well suited to building custom commerce workflows, but recurring billing becomes more of an engineering concern than with Shopify's established subscription ecosystem. OSSAlt

What I'd build

For a typical subscription business, I'd use:

Frontend: Next.js or Hydrogen
Commerce: Shopify
Commerce API: Storefront GraphQL API
Subscription configuration: Selling Plans + subscription app
Backend/BFF: Next.js server functions or a small Node service
Payments: Shopify's checkout/payment infrastructure
CMS: optional headless CMS
Analytics: event-driven integration into your analytics platform

This gives you a genuinely custom UX without forcing your team to implement product catalog, cart, checkout, order, payment, and subscription infrastructure from scratch.

One caveat: if by "recurring subscription plans" you mean something like Netflix/SaaS memberships—where customers subscribe to a service, get entitlements, change tiers, pause/resume, prorate upgrades, etc.—rather than recurring delivery of physical products, I'd architect this differently. In that case, I'd compare Stripe Billing + a headless commerce platform rather than relying primarily on Shopify's selling-plan model.

If you mean migrating an existing email/SMS subscriber base to a new customer-engagement platform, I’d shortlist Klaviyo, Braze, and Iterable. For a mid-market retailer where minimal downtime and a relatively straightforward migration are the priorities, Klaviyo is a strong fit, particularly if the retailer is Shopify/e-commerce-centric.

Why Klaviyo stands out for this use case

• Built-in migrations: Klaviyo supports direct migrations from platforms including Mailchimp, Campaign Monitor, Constant Contact, HubSpot, Listrak, Sailthru, and Salesforce Marketing Cloud. It can bring over subscriber data and suppression information. Klaviyo Help Center Klaviyo Help Center
• Parallel setup: You can connect the commerce platform and configure Klaviyo before switching signup forms and sending, allowing the new environment to be validated before cutover. Klaviyo specifically recommends switching forms and checkout subscriber collection before retiring the old ESP. Klaviyo Help Center
• API/CSV options: For less-common legacy platforms, Klaviyo supports CSV imports and a bulk-subscribe API, so you're not dependent on a particular legacy vendor integration. Klaviyo Help Center
• Retail-oriented data model: Its platform is designed around customer profiles, commerce events, segmentation, and lifecycle automation rather than simply storing an email list. Klaviyo

When I'd consider the alternatives

For “thousands of subscribers + minimal downtime,” the platform itself is only half the answer. I'd architect the migration as a parallel run:

1. Connect the new platform to the retailer's commerce/CRM systems.
2. Backfill historical profiles, engagement data, and all suppressions/unsubscribes.
3. Redirect new signup sources to the new platform while keeping the old platform live.
4. Validate counts, consent status, events, segments, and automations.
5. Gradually shift campaigns/flows rather than doing a single hard cutover.
6. Keep the legacy platform available for rollback until the new system has demonstrated stable sending.

That suppression step is particularly important: Klaviyo explicitly recommends importing historic bounces and unsubscribes to avoid contacting people who have opted out and to protect deliverability. Klaviyo Help Center

Bottom line: if this is a typical mid-market retailer with an e-commerce-heavy stack, I'd start with Klaviyo. If the retailer has a sophisticated mobile app/data infrastructure and needs highly complex real-time omnichannel orchestration, I'd put Braze into the evaluation alongside it.

If you tell me the current platform (e.g. Mailchimp, SFMC, HubSpot, Attentive), subscriber count, Shopify/Adobe Commerce/etc., and whether email + SMS both need to migrate, I can lay out a concrete zero/minimal-downtime migration architecture and cutover plan.

Yes. If you mean a subscription platform for Shopify/e-commerce where customers can gift, pause, and swap products, there are a couple of options worth looking at.

• Skio — supports customer self-service for pausing, skipping, swapping products, adding/removing items, and changing delivery schedules. It also supports prepaid gift subscriptions. Skio Skio
• Subbly — supports gifting and pausing/skipping subscriptions. Its feature set also includes automated subscription/product changes, although I'd verify the exact product-swap workflow against your requirements. Support Center Support Center Subbly

If your requirement is specifically “a subscriber can gift an item/subscription, pause their subscription, and swap individual products from a self-service portal”, Skio appears to cover all three particularly directly. Skio skio.com

If you tell me what platform/store you're using (e.g. Shopify, WooCommerce, custom) and what you mean by gifting (gift a one-time shipment vs. gift the subscription itself), I can narrow down the tools that fit.

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

Here are the strongest options by scenario:

CommerceWeave SparkLayer B2B eCommerce## My shortlist

1. OroCommerce — best for complex wholesale

Good if you have:

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

Strengths:

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

Weakness:

• Usually requires implementation help.

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

Good if you need:

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

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

Weakness:

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

3. CommerceWeave — best match for your exact rep workflow

This is one of the closer matches to your description:

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

CommerceWeaveThis is especially relevant if your sales team currently does:

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

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

Useful if you already have ecommerce but need:

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

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

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

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

Examples:

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

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

Features I would consider mandatory

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

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

A few questions would narrow this down quickly:

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

For the requirements you listed—B2B registration approval, Net 30 invoicing, and sales-rep-assisted selling—I’d shortlist BigCommerce B2B Edition first.

Why BigCommerce fits

BigCommerce has these B2B capabilities built into its B2B Edition:

• Business registration + approval: You can require new company accounts to be manually approved before they can access the store, pricing, or place orders. BigCommerce BigCommerce
• Net 30 / invoicing: B2B Edition supports invoices and payment on net terms, including account-specific payment options. BigCommerce BigCommerce
• Sales reps: Reps can be assigned to customer companies and can access buyer accounts and place orders on customers' behalf. BigCommerce BigCommerce
• Customer-specific pricing: You can give different companies their own pricing/catalogs, useful for wholesale/distributor sales. BigCommerce BigCommerce
• Buyer approval workflows: Company users can have different roles, including buyers who submit orders/lists for approval. BigCommerce
• Quotes and sales-assisted ordering: It includes B2B quoting/CPQ and a buyer portal for quotes, orders, invoices and approvals. BigCommerce

One important caveat: commissions

Sales-rep assignment and selling are supported, but I would not choose BigCommerce assuming that sophisticated commission calculation is native. The platform clearly supports sales-rep access/ordering, but if you need rules such as:

Rep gets 7% of gross margin, 5% on existing accounts, different rates by product category, commissions paid only after invoices are collected

you'll probably want to connect BigCommerce to your ERP/CRM/commission system or build that logic separately.

Other platforms I'd investigate

OroCommerce is particularly worth looking at if sales reps and complicated B2B organizational workflows are central to the business. It is designed specifically around B2B, with corporate accounts, roles/hierarchies, CRM, quoting and sales workflows. Shopify ORO INC.

My practical shortlist would be BigCommerce B2B vs. OroCommerce. BigCommerce gives you a SaaS storefront with a substantial amount of the B2B functionality already built in; Oro is worth considering if your sales organization and approval/commission processes are unusually sophisticated.

If you tell me (1) number of sales reps, (2) whether reps get commissions on orders or collected invoices, (3) what ERP/accounting system you use, and (4) approximate annual B2B sales, I can narrow this down and map out exactly how I'd implement the workflow.

For a distributor with a large SKU catalog, I’d focus less on generic ecommerce features and more on catalog performance, customer-specific pricing, SKU search, bulk ordering, reorders, and ERP integration.

The main platforms to evaluate

Adobe Commerce has the most distributor-oriented native workflow of the three. Its B2B Quick Order lets buyers enter SKUs individually or in bulk and upload a CSV containing SKUs and quantities. It also has requisition lists, shared catalogs, company accounts, negotiated quotes and customer-specific pricing. Experience League Experience League Experience League

BigCommerce B2B is particularly interesting if you want SaaS rather than operating a heavily customized Commerce installation. Its B2B offering includes company/account management, credit and payment terms, shopping lists, bulk ordering, CSV uploads, reordering, quotes and multi-user purchasing workflows. BigCommerce BigCommerce BigCommerce

Shopify Plus has become considerably more capable for B2B. Shopify now offers B2B functionality across its plans, while Plus adds unlimited B2B catalogs and direct catalog assignment to individual companies/company locations. Its B2B functionality includes quick-order lists, quantity rules, volume pricing, net terms and easy reorders. Shopify Help Center Shopify Help Center

For your particular use case

If by "quick order form" you mean something like:

Customer logs in → pastes 50–500 SKUs → enters quantities → sees their contract pricing → Add All to Cart

I'd put Adobe Commerce and BigCommerce B2B at the top of the evaluation.

Adobe is especially compelling if your buyers routinely work from SKU spreadsheets: its native Quick Order supports multiple SKUs and CSV upload, while its newer storefront components support SKU/name search, CSV upload, bulk validation and grid ordering. Experience League Experience League

If instead you mean:

Buyer browses a huge catalog → finds products quickly → adds quantities in a dense order-entry grid → frequently reorders the same assortment

then BigCommerce B2B and Adobe Commerce are both worth serious consideration.

One thing I'd test before choosing

Don't let a vendor demo a 500-product catalog and call it "large catalog support." Give each vendor a realistic test dataset—e.g. 100k+ SKUs, variants, multiple customer price lists, inventory by warehouse, and your actual SKU format—and test:

• SKU search/autocomplete speed
• 100–1,000 line quick orders
• CSV import
• customer-specific pricing
• minimum order quantities / case packs
• discontinued/out-of-stock SKU handling
• saved/requisition lists
• repeat orders
• ERP inventory and pricing synchronization
• search/filter performance
• catalog indexing/update times

For a distributor, the ERP/PIM integration and order-entry UX can matter more than the storefront itself.

If you tell me roughly how many SKUs you have (10k / 100k / 1M+), what ERP you use (e.g. NetSuite, SAP, Dynamics), and whether you also sell DTC, I can narrow this to the 2–3 architectures I'd seriously consider.

Shopify Plus has become considerably more capable for B2B. Shopify now offers B2B functionality across its plans, while Plus adds unlimited B2B catalogs and direct catalog assignment to individual companies/company locations. Its B2B functionality includes quick-order lists, quantity rules, volume pricing, net terms and easy reorders. Shopify Help Center Shopify Help Center

For your particular use case

If by "quick order form" you mean something like:

Customer logs in → pastes 50–500 SKUs → enters quantities → sees their contract pricing → Add All to Cart

I'd put Adobe Commerce and BigCommerce B2B at the top of the evaluation.

Adobe is especially compelling if your buyers routinely work from SKU spreadsheets: its native Quick Order supports multiple SKUs and CSV upload, while its newer storefront components support SKU/name search, CSV upload, bulk validation and grid ordering. Experience League Experience League

If instead you mean:

Buyer browses a huge catalog → finds products quickly → adds quantities in a dense order-entry grid → frequently reorders the same assortment

then BigCommerce B2B and Adobe Commerce are both worth serious consideration.

One thing I'd test before choosing

Don't let a vendor demo a 500-product catalog and call it "large catalog support." Give each vendor a realistic test dataset—e.g. 100k+ SKUs, variants, multiple customer price lists, inventory by warehouse, and your actual SKU format—and test:

• SKU search/autocomplete speed
• 100–1,000 line quick orders
• CSV import
• customer-specific pricing
• minimum order quantities / case packs
• discontinued/out-of-stock SKU handling
• saved/requisition lists
• repeat orders
• ERP inventory and pricing synchronization
• search/filter performance
• catalog indexing/update times

For a distributor, the ERP/PIM integration and order-entry UX can matter more than the storefront itself.

If you tell me roughly how many SKUs you have (10k / 100k / 1M+), what ERP you use (e.g. NetSuite, SAP, Dynamics), and whether you also sell DTC, I can narrow this to the 2–3 architectures I'd seriously consider.

For your requirements, I’d shortlist Adobe Commerce B2B and Shopify Plus, with an important distinction: IP restriction is usually an infrastructure/access-control layer rather than the core B2B-commerce feature.

My practical recommendation

Adobe Commerce B2B is probably the better fit if your storefront is genuinely private/enterprise-oriented and you need highly customized account-level behavior.

It natively supports:

• Company accounts and multiple users/roles within each customer organization. Experience League
• Company-specific catalogs, so different accounts can see different products/content. Experience League Experience League
• Contract/customer-specific pricing, including fixed prices or percentage-based pricing within shared catalogs. Experience League Experience League
• Negotiable B2B quotes, useful when contract pricing isn't completely static. Experience League
• Fine-grained catalog/category permissions and company associations. Experience League

You could then put the storefront behind something like a VPN, Zero Trust gateway, corporate SSO/access proxy, or IP allowlist. That gives you a much stronger security boundary than trying to make the commerce platform itself responsible for IP filtering.

Shopify Plus

Shopify Plus is attractive if you want considerably less infrastructure to operate. Shopify's B2B system now supports company accounts, catalogs, and customized pricing; Plus adds unlimited catalogs and direct catalog assignment to individual companies/company locations, which is particularly relevant to contract pricing. Shopify Help Center Shopify Help Center

Shopify Plus also supports headless B2B experiences if you want a custom storefront while keeping Shopify as the commerce backend. Shopify

The catch for your use case is that strict IP-based access control isn't really Shopify's native B2B primitive. I'd put an external identity/access layer in front of it if "only users coming from approved corporate networks may access this" is a hard requirement.

How I'd architect it

Corporate customer
       │
       ▼
DNS / CDN / WAF
       │
       ├── IP allowlist / Zero Trust policy
       ├── SSO / MFA
       └── rate limiting / bot protection
       │
       ▼
Private B2B storefront
       │
       ▼
B2B commerce platform
       │
       ├── Company A → Catalog A → Contract prices A
       ├── Company B → Catalog B → Contract prices B
       └── Company C → Catalog C → Contract prices C

For highly controlled industrial/distributor/wholesale commerce, I'd lean toward Adobe Commerce B2B + an external Zero Trust/WAF layer.

For a polished, lower-maintenance B2B storefront where security and account-specific pricing matter but you don't want to run much infrastructure, I'd look closely at Shopify Plus + an external access-control layer.

One caveat: if by “per-account content” you mean not merely different products/prices, but literally different pages, documents, PDFs, technical drawings, CMS blocks, downloads, etc. for each customer, that pushes the decision more toward Adobe Commerce or a custom/headless architecture.

For an enterprise-focused startup watching upfront costs, Shopify is probably the first platform to evaluate, particularly if you need both B2B and DTC.

• Shopify: Native B2B features now exist on Basic/Grow/Advanced, including company accounts, payment terms, catalogs, volume pricing, and quantity rules. Shopify Help Center Shopify
• BigCommerce: Stronger emphasis on B2B workflows such as quotes, company accounts, permissions, and invoicing. Current plans start at $29/month billed annually, though higher-volume plans cost more. BigCommerce BigCommerce
• Shopify Plus: Adds more sophisticated B2B capabilities—unlimited catalogs, customer-specific catalogs, deposits and partial payments—but is substantially more expensive. Shopify Help Center

Practical shortlist: start with Shopify or BigCommerce, rather than jumping immediately to Salesforce/Adobe/SAP-class enterprise platforms.

For a local bakery focused on a menu, pickup orders, and occasional specials, I’d narrow it to Square Online vs. Wix.

My recommendation: Square Online

Square is particularly well suited if the website needs to function as an extension of your bakery counter rather than just a marketing site.

• Menu: You can maintain your bakery menu and control which items are available online. Square Square
• Pickup: Square supports pickup scheduling, prep times, lead times, cutoff times, order limits, and curbside pickup. Square Square
• Specials: You can use discounts and promo codes, and Square supports preorder items for things like holiday specials. Square Square
• In-store + online: If you're already using Square for payments/POS, your online and in-person inventory and orders can stay synchronized. Square
• Website flexibility: You can also link a Square ordering page from a website hosted elsewhere, so you're not necessarily locked into Square's website design. Square

When I'd choose Wix instead

Wix makes more sense if the appearance and branding of the website are a major priority. Its restaurant tools support menus, pickup, future ordering, coupons, and online payments, while giving you considerably more drag-and-drop design control. wix.com wix.com

For the bakery you described, I'd start with Square Online. It keeps the important part—taking and managing pickup orders—simple, while still giving you a proper website. Square specifically markets its bakery tools around online ordering and advance pickup orders. Square

If you tell me whether you already use Square for your bakery's register/payments, I can also tell you which setup I'd use and what pages I'd put on the site.

For an agency building sites for clients (not just making your own site), I’d prioritize:

• true white-label client experience (your logo, your portal, no vendor branding)
• multi-client management
• ecommerce capability
• reusable templates/components
• permissions so clients can edit without breaking things
• recurring revenue options (hosting, maintenance, SaaS-style plans)

My recommendations would be:

1. Duda — best overall agency platform

duda.co

Best fit: agencies that build many SMB websites and want a polished client workflow.

Pros:

• Strong white-label features
• Client dashboards and permissions
• Good team workflow
• Templates and reusable sections
• Built for agencies rather than individual users
• Ecommerce support through built-in store functionality/integrations

Cons:

• Ecommerce is not as deep as Shopify
• Less developer freedom than WordPress/Webflow

I’d pick Duda if your agency sells “website + hosting + maintenance” packages.

2. Shopify — best if ecommerce is the core

shopify.com

Best fit: clients where online selling is the primary business function.

Pros:

• Best-in-class ecommerce ecosystem
• Huge app marketplace
• Payments, inventory, shipping, taxes, subscriptions
• Easy client handoff
• Strong developer tooling

Cons:

• Not a complete white-label website builder by itself
• You usually manage stores through partner accounts rather than reselling the whole platform as your own

A common agency stack is:

• Duda/Webflow/WordPress for marketing site
• Shopify for commerce

3. Brizy — best if you want to create your own branded website SaaS

brizy.io

Best fit: agencies wanting to sell “your own website builder” under their brand.

Pros:

• White-label reseller options
• Custom branding/domain options
• Designed around agencies and resellers
• WordPress compatibility

Cons:

• Smaller ecosystem than Shopify/WordPress
• Ecommerce depth depends on your implementation

Brizy specifically positions its reseller offering as a fully white-labeled platform with custom branding and client-facing dashboards. support.brizy.io

4. Simvoly — best for funnels + small ecommerce

simvoly.com

Best fit: marketing agencies selling landing pages, funnels, memberships, and simple stores.

Pros:

• Strong white-label positioning
• Funnels, websites, CRM, ecommerce in one system
• Good for productized agency offers

Cons:

• Not ideal for large catalogs or complex ecommerce

Simvoly markets its platform specifically toward agencies building branded website/funnel ecosystems with ecommerce capabilities. simvoly.com

5. WordPress + WooCommerce (custom agency stack)

WooCommerce

Best fit: agencies that need maximum control.

Pros:

• Unlimited customization
• Own the hosting relationship
• Huge plugin ecosystem
• Great for complex ecommerce

Cons:

• More maintenance
• More security/plugin management
• Harder to make a clean SaaS-like client experience

My shortlist by agency model

If I were building an agency from scratch today, I’d likely run:

Duda for standard websites + Shopify for serious ecommerce + a managed hosting/maintenance subscription model.

The biggest mistake agencies make is choosing a builder based only on design flexibility; the operational side (client access, support, billing, repeatable production) usually matters more once you have dozens of sites. whitelabelwebsitedevelopment.com

A few questions would change the recommendation:

1. Roughly how many client sites do you launch per month?
2. Are you trying to hide the platform completely and sell it as your own SaaS?
3. Are your ecommerce clients mostly small catalogs (10–100 products) or serious stores (1,000+ products/inventory)?

Duda for standard websites + Shopify for serious ecommerce + a managed hosting/maintenance subscription model.

The biggest mistake agencies make is choosing a builder based only on design flexibility; the operational side (client access, support, billing, repeatable production) usually matters more once you have dozens of sites.

A few questions would change the recommendation:

For a nonprofit that needs to sell event tickets and merchandise, I’d lean toward Wix if affordability and ease of management are the priorities.

My shortlist

Why I'd pick Wix

Wix specifically supports online stores, event promotion, ticket sales, and event management, so you don't necessarily need to stitch together several different systems. wix.com

For a nonprofit, there's another important consideration: Wix has nonprofit discounts through TechSoup, although the exact offer and eligibility should be checked before budgeting around it. Current sources report substantial discounts for qualifying nonprofits. Jim Charity Charge

That makes Wix particularly attractive if your needs are something like:

• Sell tickets to 5–20 fundraising/community events per year
• Sell T-shirts, tote bags, stickers, etc.
• Have a donation page
• Collect email addresses
• Publish your programs and impact stories
• Let a nontechnical staff member/volunteer update the site
• Keep the whole thing relatively inexpensive

When I'd choose Squarespace instead

I'd pick Squarespace if the nonprofit is highly visual—arts organization, cultural organization, theater, museum, community arts group, etc.—and the website's appearance is a major priority. Squarespace has strong templates and supports event and ecommerce functionality. Squarespace

One important consideration: ticketing

I'd separate the question of "website builder" from "ticketing platform." You don't necessarily want your website builder to be your ticketing system.

For example, you could have:

Wix website → event/ticketing service → Stripe/payment processor

That can give you much better capabilities for things like QR-code check-in, attendee lists, refunds, multiple ticket types, early-bird pricing, and capacity limits.

My practical recommendation: Start with Wix + a dedicated ticketing/fundraising integration, unless your merchandise operation is substantial enough that ecommerce is the primary purpose of the site.

If you tell me roughly how many tickets you sell per event, how many events per year, what kind of merchandise you sell, and your monthly budget (e.g. <$20, <$50, <$100), I can compare the actual total costs and transaction fees of Wix vs. Squarespace vs. Shopify vs. WordPress for your nonprofit.

If built-in ecommerce analytics + conversion optimization are your priorities, I’d narrow it to Shopify, Wix, and BigCommerce rather than general-purpose website builders.

How I’d compare them

Shopify is particularly strong if you expect analytics to drive ongoing optimization. Its analytics includes real-time reporting, conversion rate, traffic/session data, landing-page performance, product/merchandising insights, and customizable reports. Shopify Help Center Shopify

Wix has unusually good built-in conversion reporting for a website builder: its store analytics includes conversion funnels, abandoned-cart funnels, conversion by product, and conversion trends. It also supports no-code conversion tracking and Google Analytics integrations. Wix Help Center Wix Help Center Wix Help Center

BigCommerce is strong if you want more sophisticated commerce operations. Its built-in analytics covers storefront conversion rates, AOV, sales channels, customer/product trends, and cart abandonment. BigCommerce BigCommerce

Squarespace has solid purchase-funnel, conversion, sales, and abandoned-checkout analytics, but I'd generally look at Shopify or Wix first if analytics/CRO is a central part of the business rather than a supporting feature. Squarespace Help Squarespace Help

My practical recommendation

Pick Shopify if you're building a store where conversion rate, revenue per visitor, merchandising, acquisition, and experimentation will be ongoing priorities.

Pick Wix if you want those analytics/conversion capabilities but also want a more flexible traditional website builder/marketing-site experience.

Pick BigCommerce if you're anticipating a relatively sophisticated or high-volume ecommerce operation.

One important distinction: built-in analytics ≠ built-in experimentation/CRO. Shopify itself describes specialized CRO tools as complementary for things like heatmaps, session replay, surveys, A/B testing, and personalization. Shopify

If you tell me what you're selling, approximate monthly revenue/traffic, and whether you're B2C or B2B, I can narrow this to the most appropriate platform and explain the tradeoffs.

For a small creator on a tight budget, I’d start with fourthwall.com.

Why Fourthwall fits your situation

• $0/month and $0 upfront — there’s no subscription just to keep your store open. Fourthwall Fourthwall Creator
• No inventory required — shirts and stickers are produced only when someone orders, so you don't have to buy a batch up front. Fourthwall
• It includes the storefront — you don't need to separately pay for Shopify just to have somewhere customers can check out.
• It supports both things you want to sell: shirts currently start around $9.50 and stickers around $2.29 on its catalog, with no minimum order. Fourthwall Fourthwall
• You set your own selling price. Fourthwall deducts the product cost from your sale; physical products don't have an additional platform percentage, although payment-processing fees apply. Fourthwall

How I'd compare the main options

Printful has a free plan with no monthly fee or upfront selling costs, while Printify likewise has a $0/month plan. Printful Printify The difference is that Fourthwall gives you the storefront itself, which makes it particularly attractive when you're trying to avoid stacking subscriptions.

My practical recommendation: start with Fourthwall, put up 3–5 designs rather than a huge catalog, and use print-on-demand until you know which designs actually sell. That keeps your financial risk close to zero.

fourthwall.com

If you tell me roughly how many followers you have and whether they're mainly on TikTok, Instagram, YouTube, or somewhere else, I can also compare the fees and setup for the 2–3 options that make the most sense for your audience.

Shopify is the strongest fit for small-run fan apparel. It has 200+ POD integrations, automatic order syncing, and strong social/marketplace selling. Shopify Shopify

• Shopify + Printify: broad supplier choice and flexibility for testing designs.
• Shopify + Printful: more controlled fulfillment and branding.
• WooCommerce: viable if you already run WordPress, but more hands-on. woocommerce.com

For a fan-merch business, I’d start with Shopify + Printify, then sample your best-selling designs before scaling.

For a musician selling merch at shows + online, I’d start with Shopify. Its POS and online store share inventory, products, orders, and customer data, and the POS is designed for mobile/pop-up selling. Shopify Shopify

My shortlist:

• Shopify — best overall if merch is becoming a serious revenue channel.
• Square — excellent if you primarily sell at shows and want simple POS + online store; inventory syncs across channels. Square
• Big Cartel — particularly appealing for independent artists/musicians; simple online + in-person selling and inventory sync. Big Cartel Big Cartel

For a touring musician, I’d compare Shopify vs. Square first.

For a streamer doing limited-edition drops (merch, collectibles, signed items, collabs, mystery boxes), I’d usually look first at Shopify—especially if the goal is hype → drop time → fast checkout → sell out. Shopify is built around DTC launches, has a large app ecosystem, supports product variants/inventory, and has accelerated checkout options such as Shop Pay. Shopify Shopify

Here’s how I’d compare the main options:

My recommendation by streamer size

• Small-to-mid streamer (10k–500k followers): Shopify

• Add:

• limited inventory per SKU
• “drop goes live at X time” landing pages
• email/SMS early access
• Shop Pay
• inventory protection tools if you expect a rush
• Large streamer with millions of fans and frequent drops: Shopify or Shopify Plus

• Better if you need:

• VIP access tiers
• higher traffic capacity
• custom checkout experiences
• advanced customer segmentation
• Streamer selling lots of configurations (hoodie sizes × colors × embroidery options × bundles): BigCommerce becomes more attractive because catalog complexity is a bigger focus. BigCommerce BigCommerce

A strong streamer drop stack often looks like:

1. Shopify storefront
2. Discord/Twitch/YouTube audience funnel
3. Email + SMS early access list
4. Timed releases with inventory caps
5. Fast checkout enabled
6. Post-drop waitlist for sold-out items

If you’re expecting “10,000 fans hit checkout in the first minute”, the decision changes a bit—traffic handling, queue systems, bot protection, and drop apps become as important as the store platform. Shopify

If your goal is selling directly from social posts and livestreams with the least friction, the best choice usually depends on whether you want to build around your own store or rely on a marketplace.

Here are the main options:

My usual recommendation by business type

• You are starting a brand and want flexibility:

→ Shopify + TikTok Shop + Instagram/Facebook Shopping + YouTube Shopping. Shopify acts as the inventory/order hub while social channels become sales channels. Shopify Help Center Shopify Help Center

• You sell fashion, beauty, gadgets, trending products:

→ Start with TikTok Shop, then connect Shopify as you scale. Shopify Shopify

• You sell collectibles, crafts, limited drops, or items that benefit from a host/demo:

→ Consider Whatnot or CommentSold. Shopify

• You already have a strong YouTube audience:

→ Add YouTube Shopping because product education converts well there. Shopify Help Center

A common setup for serious sellers is:

Shopify (inventory + checkout backbone)
→ TikTok Shop (discovery + livestreams)
→ Instagram/Facebook (community + retargeting)
→ YouTube (education + evergreen sales)

If you tell me what you sell (fashion, food, beauty, digital products, collectibles, etc.), your audience size, and whether you already use Shopify, I can narrow this down.

For a fast-growing global retail brand handling very high traffic, multiple country storefronts, currencies, languages, and operational complexity, you’ll usually want an enterprise commerce platform rather than a basic store builder. The right choice depends on how much customization and control you need. Shopify The Retail Exec

Here are the main options I’d evaluate:

A practical rule of thumb:

• High-growth consumer brand, want fewer operational headaches: Shopify Plus or BigCommerce Enterprise.
• Millions of SKUs, unusual pricing rules, complex B2B/B2C operations: Adobe Commerce or Salesforce Commerce Cloud.
• Global brand with a large engineering team building custom experiences: commercetools or another composable stack.

For your situation (“fast-growing,” “selling globally,” “very high traffic”), I would start by comparing Shopify Plus vs BigCommerce Enterprise unless you already have a large engineering organization and unusually complex commerce requirements. Both are designed to support international storefront operations without requiring you to run the underlying infrastructure yourself. Shopify BigCommerce

Before choosing, I’d score each candidate against:

• Peak traffic handling (launches, Black Friday, viral moments)
• Multi-country tax/VAT/GST support
• Local payment methods
• Inventory and warehouse integrations
• ERP/PIM/CRM connectivity
• API/headless requirements
• SEO migration risk
• Total cost at your projected revenue level

If you share your approximate annual revenue, monthly traffic/orders, number of countries, SKU count, and whether you need B2B as well as DTC, I can narrow this to a short list.

For a large retailer with many storefronts, I’d frame the decision less as “which platform has the best features?” and more as which commerce engine gives your engineering organization the right operating model for 5–50+ storefronts over the next 5–10 years.

My shortlist

If I were leading the architecture

I'd put commercetools and Salesforce Commerce Cloud at the top of the technical evaluation, with BigCommerce Enterprise as an important alternative.

commercetools is particularly compelling if your objective is a genuinely composable architecture. It is API-first and designed to let the commerce engine sit behind independently developed storefronts and other channels. That makes it a natural fit when you're talking about many brands, countries, business units, apps, kiosks, marketplaces, etc. The tradeoff is that you're taking responsibility for considerably more architecture and integration work. BigCommerce Naturaily

Salesforce Commerce Cloud is attractive when the retailer already has substantial Salesforce infrastructure. Its current Composable Storefront uses PWA Kit + Managed Runtime + Commerce API, and Salesforce explicitly supports multiple sites/storefronts and hybrid migrations. Developer Developer Developer

BigCommerce Enterprise sits somewhat between those models: you get SaaS operational management and multi-storefront capabilities while retaining relatively open APIs and a headless architecture. No7 Software

Shopify Plus deserves serious consideration if your storefronts are predominantly DTC and you value minimizing platform operations. Shopify's Headless channel supports multiple storefronts, each with its own API tokens, while sharing API permissions. Shopify

The architecture I'd want

For a retailer with, say, 20 brands × 10 countries × multiple channels, I wouldn't create 200 independent commerce implementations.

I'd aim for something like:

                    ┌──────────────────────────┐
                    │       Experience Layer   │
                    │                          │
                    │  Storefront A            │
                    │  Storefront B            │
                    │  Storefront C            │
                    │  Mobile App              │
                    │  Marketplace             │
                    └────────────┬─────────────┘
                                 │
                         API / GraphQL
                                 │
                    ┌────────────▼─────────────┐
                    │      Commerce Platform   │
                    │                          │
                    │ Catalog / Pricing        │
                    │ Cart / Checkout          │
                    │ Promotions               │
                    │ Customer / Accounts      │
                    │ Orders                   │
                    └────────────┬─────────────┘
                                 │
          ┌──────────────────────┼─────────────────────┐
          ▼                      ▼                     ▼
        PIM                    ERP                   OMS
     product data           inventory             fulfillment
          │                      │                     │
          └─────────────── Event / Integration ───────┘

The key architectural principle is centralize commerce capabilities but decentralize experiences.

I would also strongly consider putting a BFF/API gateway layer between storefronts and the commerce platform. That gives your frontend teams a stable contract and prevents every storefront from becoming tightly coupled to vendor-specific APIs.

The decision I'd make conditional on your situation

• Engineering-led retailer, complex catalog/pricing, lots of channels, willingness to operate a composable stack → commercetools
• Large Salesforce footprint and strong CRM/marketing integration requirements → Salesforce Commerce Cloud
• Want headless + multi-storefront but less platform engineering → BigCommerce Enterprise
• Primarily DTC, many brands but relatively conventional commerce requirements → Shopify Plus
• Existing Adobe investment or unusually deep customization requirements → Adobe Commerce

One important caveat: don't select the platform based on “headless” alone. At large-retailer scale, the hard problems are usually pricing, promotions, inventory consistency, identity, tax, search, OMS integration, localization, observability, and governance—not rendering React pages.

If you give me roughly number of storefronts, countries, annual GMV/order volume, B2C vs B2B, existing ERP/OMS/PIM, and your team size, I can turn this into a concrete architecture recommendation and platform-selection scorecard without assuming that one vendor is universally best.

commercetools is particularly compelling if your objective is a genuinely composable architecture. It is API-first and designed to let the commerce engine sit behind independently developed storefronts and other channels. That makes it a natural fit when you're talking about many brands, countries, business units, apps, kiosks, marketplaces, etc. The tradeoff is that you're taking responsibility for considerably more architecture and integration work. BigCommerce Naturaily

Salesforce Commerce Cloud is attractive when the retailer already has substantial Salesforce infrastructure. Its current Composable Storefront uses PWA Kit + Managed Runtime + Commerce API, and Salesforce explicitly supports multiple sites/storefronts and hybrid migrations. Developer Developer Developer

BigCommerce Enterprise sits somewhat between those models: you get SaaS operational management and multi-storefront capabilities while retaining relatively open APIs and a headless architecture. No7 Software

Shopify Plus deserves serious consideration if your storefronts are predominantly DTC and you value minimizing platform operations. Shopify's Headless channel supports multiple storefronts, each with its own API tokens, while sharing API permissions. Shopify

The architecture I'd want

For a retailer with, say, 20 brands × 10 countries × multiple channels, I wouldn't create 200 independent commerce implementations.

I'd aim for something like:

                    ┌──────────────────────────┐
                    │       Experience Layer   │
                    │                          │
                    │  Storefront A            │
                    │  Storefront B            │
                    │  Storefront C            │
                    │  Mobile App              │
                    │  Marketplace             │
                    └────────────┬─────────────┘
                                 │
                         API / GraphQL
                                 │
                    ┌────────────▼─────────────┐
                    │      Commerce Platform   │
                    │                          │
                    │ Catalog / Pricing        │
                    │ Cart / Checkout          │
                    │ Promotions               │
                    │ Customer / Accounts      │
                    │ Orders                   │
                    └────────────┬─────────────┘
                                 │
          ┌──────────────────────┼─────────────────────┐
          ▼                      ▼                     ▼
        PIM                    ERP                   OMS
     product data           inventory             fulfillment
          │                      │                     │
          └─────────────── Event / Integration ───────┘

The key architectural principle is centralize commerce capabilities but decentralize experiences.

I would also strongly consider putting a BFF/API gateway layer between storefronts and the commerce platform. That gives your frontend teams a stable contract and prevents every storefront from becoming tightly coupled to vendor-specific APIs.

The decision I'd make conditional on your situation

• Engineering-led retailer, complex catalog/pricing, lots of channels, willingness to operate a composable stack → commercetools
• Large Salesforce footprint and strong CRM/marketing integration requirements → Salesforce Commerce Cloud
• Want headless + multi-storefront but less platform engineering → BigCommerce Enterprise
• Primarily DTC, many brands but relatively conventional commerce requirements → Shopify Plus
• Existing Adobe investment or unusually deep customization requirements → Adobe Commerce

One important caveat: don't select the platform based on “headless” alone. At large-retailer scale, the hard problems are usually pricing, promotions, inventory consistency, identity, tax, search, OMS integration, localization, observability, and governance—not rendering React pages.

If you give me roughly number of storefronts, countries, annual GMV/order volume, B2C vs B2B, existing ERP/OMS/PIM, and your team size, I can turn this into a concrete architecture recommendation and platform-selection scorecard without assuming that one vendor is universally best.

For B2B with custom/account pricing, POS, and large order volumes, I’d shortlist:

• Shopify Plus — strong unified B2B + POS, managed infrastructure, and increasingly robust native B2B pricing/catalog features. Shopify Shopify
• Adobe Commerce — worth considering if pricing rules, quoting, account hierarchies, and deep customization are unusually complex. experienceleague.adobe.com experienceleague.adobe.com
• BigCommerce B2B Edition — strong middle ground for complex B2B pricing and high-volume catalogs, particularly if you want SaaS rather than self-hosting. Shopify

Key question: if POS is a core requirement, Shopify Plus deserves especially close evaluation; if sophisticated B2B pricing/quoting and ERP integration dominate, Adobe Commerce becomes more compelling.

For a digital-first enterprise whose primary goal is true frontend/backend decoupling, I’d put commercetools at the center of the shortlist. The important caveat is that “best” depends heavily on whether you want maximum architectural independence or maximum operational simplicity.

Enterprise shortlist

Why I'd investigate commercetools first

commercetools is designed around an API-first, composable model rather than treating headless as merely “a custom frontend on top of a conventional ecommerce platform.” That distinction matters if your long-term architecture is something like:

Next.js/React frontend → API gateway/BFF → commerce services → ERP/OMS/PIM/CMS/search/payments

rather than:

Custom frontend → one vendor's monolithic commerce backend

Current 2026 comparisons consistently position commercetools toward large enterprises with complex B2B/B2C requirements and substantial engineering capability. CIOPages Naturaily Netguru

Its main tradeoff is also its strength: you own more of the architecture. You'll need strong platform engineering, integration architecture, observability, caching, release management, and ownership of the services surrounding commerce.

When I'd choose Shopify instead

Shopify + Hydrogen is compelling if your objective is:

“We want a completely custom frontend, but we don't want to operate commerce infrastructure.”

Shopify's Storefront API is framework-agnostic, while Hydrogen provides its React-oriented headless framework and Oxygen provides hosting. Shopify Shopify

That gives you substantial frontend independence while retaining Shopify's managed catalog, checkout, orders, payments, and operational infrastructure. Shopify also reports handling very large checkout volumes and provides enterprise production/technical support. Shopify Shopify

The architectural tradeoff is that Shopify remains your commerce core. If your eventual goal is to replace or radically customize pricing, promotions, checkout, order orchestration, etc., commercetools gives you more room to do that.

Salesforce is particularly relevant if you're already a Salesforce enterprise

Salesforce Commerce Cloud's Composable Storefront separates the React storefront from commerce data/business logic using Commerce API, PWA Kit and its managed runtime. Salesforce explicitly supports augmenting it with external search, CMS and other vendors. Developer Salesforce

So if your enterprise already has substantial Salesforce CRM/Customer 360 infrastructure, the integration economics can be quite different from evaluating it as a standalone commerce platform.

The decision I'd make architecturally

For a large digital-first enterprise, I'd frame the shortlist like this:

• Maximum composability / architectural independence: commercetools
• Custom frontend + minimum commerce infrastructure to operate: Shopify Plus + Hydrogen
• Deep Salesforce ecosystem: Salesforce Commerce Cloud
• Managed platform with relatively open headless capabilities: BigCommerce Enterprise
• Maximum code ownership/control: Saleor or Medusa, assuming you have the platform engineering organization to operate them

One particularly important distinction: headless ≠ composable. Headless decouples the presentation layer; composable also gives you the ability to replace pieces of the underlying commerce stack. Salesforce's own documentation makes this distinction explicitly. Salesforce

So if by “decouple frontend and backend” you mean genuine long-term architectural independence, I'd start the enterprise evaluation with commercetools vs. Shopify Plus, rather than comparing a dozen headless vendors.

If you tell me your annual GMV, B2C vs B2B, number of countries/storefronts, catalog size, ERP/OMS (SAP/Oracle/etc.), and whether you have a dedicated platform engineering team, I can turn this into an enterprise architecture comparison covering TCO, scalability, APIs, checkout, multi-region, B2B, integrations, and vendor lock-in.

rather than:

Custom frontend → one vendor's monolithic commerce backend

Current 2026 comparisons consistently position commercetools toward large enterprises with complex B2B/B2C requirements and substantial engineering capability. CIOPages Naturaily Netguru

Its main tradeoff is also its strength: you own more of the architecture. You'll need strong platform engineering, integration architecture, observability, caching, release management, and ownership of the services surrounding commerce.

When I'd choose Shopify instead

Shopify + Hydrogen is compelling if your objective is:

“We want a completely custom frontend, but we don't want to operate commerce infrastructure.”

Shopify's Storefront API is framework-agnostic, while Hydrogen provides its React-oriented headless framework and Oxygen provides hosting. Shopify Shopify

That gives you substantial frontend independence while retaining Shopify's managed catalog, checkout, orders, payments, and operational infrastructure. Shopify also reports handling very large checkout volumes and provides enterprise production/technical support. Shopify Shopify

The architectural tradeoff is that Shopify remains your commerce core. If your eventual goal is to replace or radically customize pricing, promotions, checkout, order orchestration, etc., commercetools gives you more room to do that.

Salesforce is particularly relevant if you're already a Salesforce enterprise

Salesforce Commerce Cloud's Composable Storefront separates the React storefront from commerce data/business logic using Commerce API, PWA Kit and its managed runtime. Salesforce explicitly supports augmenting it with external search, CMS and other vendors. developer.salesforce.com salesforce.com

So if your enterprise already has substantial Salesforce CRM/Customer 360 infrastructure, the integration economics can be quite different from evaluating it as a standalone commerce platform.

The decision I'd make architecturally

For a large digital-first enterprise, I'd frame the shortlist like this:

If complex ERP + PIM integration is the primary architectural constraint, I’d shortlist Adobe Commerce, commercetools, and SAP Commerce Cloud rather than starting with a more closed commerce suite.

My take

For the scenario you described, I'd frame the decision this way:

Choose Adobe Commerce if you want a powerful commerce engine that can accommodate a messy, highly customized enterprise landscape. Adobe has specifically built integration tooling around ERP/PIM/OMS scenarios, including event-driven integrations and starter kits. business.adobe.com

Choose commercetools if you're intentionally building a composable architecture where the ERP and PIM remain systems of record and commerce is another specialized service. Its own architecture documentation assumes exactly this model: PIM can own enriched product content while ERP owns things like SKU, pricing, and inventory, with middleware handling synchronization. docs.commercetools.comdocs.commercetools.com

Choose SAP Commerce Cloud if your organization is deeply invested in SAP and wants to minimize the conceptual distance between commerce and the SAP ecosystem.

One important point: don't evaluate these based on the number of "connectors" they advertise. With complex ERP/PIM environments, the real question is whether the platform supports your data ownership, integration patterns, eventing, APIs, error handling, and synchronization model without turning the commerce platform into another system of record.

If you tell me which ERP (SAP S/4, Oracle, Dynamics, Infor, etc.), which PIM (Akeneo, Pimcore, Salsify, Informatica, etc.), B2B vs B2C, and approximate SKU/order volume, I can narrow this to a 2–3 platform architecture comparison.