Answers that name a competitor

For a growing local retailer with limited development resources, I’d generally start with a managed SaaS ecommerce platform, rather than building on WordPress/custom code. The key is choosing one that you won’t outgrow when you add more products, stores, sales channels, integrations, or international customers.

My shortlist

Shopify would be my default starting point. It gives a small team a relatively turnkey storefront while leaving room for APIs, third-party systems, custom apps, and eventually headless commerce. Shopify Plus currently supports online, retail and B2B operations and provides APIs/headless options for more sophisticated architectures. Shopify Shopify

shopify.com

BigCommerce is worth serious consideration if you expect more complicated product catalogs, wholesale/B2B sales, multiple storefronts, or substantial integration requirements. Its current platform emphasizes open APIs, multi-storefront capabilities, and B2B functionality while remaining SaaS-managed. BigCommerce BigCommerce

bigcommerce.com

WooCommerce is attractive if you already have a strong WordPress presence or want control over hosting, code and data. It can scale very substantially, but scaling becomes more of an infrastructure/development responsibility, which is exactly what I'd be cautious about with limited dev resources. WooCommerce The WooCommerce Developer Blog

woocommerce.com

What I'd optimize for in your situation

Don't try to build the "future" architecture on day one. Instead, choose software where the future architecture is available when you need it.

I'd prioritize:

• Strong inventory + order management — especially if your physical and online inventory will share stock.
• POS integration — critical for a retailer moving online.
• Good APIs — so your eventual ERP, CRM, warehouse, loyalty system, etc. aren't blocked.
• Large app/integration ecosystem — lets you buy functionality instead of developing it.
• Multiple sales channels — web, physical stores, marketplaces, social, etc.
• Good admin UX — your staff should be able to manage products, orders and promotions without developers.
• Headless/composable capability later, but don't use it initially unless there's a genuine reason.
• Data portability — make sure you can export customers, orders, products and other important business data.

The architecture I'd use

For a limited-dev team, I'd aim for:

Shopify/BigCommerce → standard theme → managed apps → clean integrations → APIs/custom development only where differentiation matters.

That gives you a fast launch without creating a technical dead end.

If you tell me (1) roughly how many SKUs you have, (2) whether you already use Square/Shopify POS/another POS, (3) whether you sell wholesale, and (4) your approximate annual online sales target, I can narrow this down to the most appropriate platform and architecture for your business.

If your core requirement is a marketplace for many independent artisans, where each seller has their own storefront, products, orders, commissions, and payouts, I’d narrow the choice to WooCommerce + a mature multi-vendor extension or Shopify + a multi-vendor app.

How I’d compare them

WooCommerce has particularly good coverage for an artisan marketplace: vendors can apply, be approved, manage their own products, have vendor-specific commission rates, manage shipping, view sales reports, and receive scheduled payouts. WooCommerce WooCommerce

There are also third-party WooCommerce marketplace solutions such as Dokan, which provide vendor signup, individual vendor dashboards, order management, earnings withdrawals, and vendor statistics. WooCommerce

On Shopify, apps such as Webkul's Multi Vendor Marketplace provide seller onboarding, seller portals, commissions, automated payouts, shipping/order functionality, and other marketplace features. Shopify App Store

My practical recommendation

If you're building something Etsy-like for artisans, I'd seriously consider:

WordPress + WooCommerce + a multi-vendor marketplace extension

rather than trying to force a normal Shopify store into being a marketplace.

That's especially true if you need things like:

• Hundreds/thousands of independent artisans
• Each artisan gets their own shop page
• Seller application + admin approval
• Seller-specific commissions
• Seller-specific shipping
• Seller inventory management
• Automatic/manual seller payouts
• Artisan profiles and stories
• Product approval/moderation
• Reviews and seller ratings
• Multiple artisans in one customer order
• Your own marketplace fee
• Custom categories, filters and discovery
• Custom marketplace design/UX

WooCommerce's official Product Vendors extension supports many of these directly, including vendor-specific commissions, vendor profiles, vendor product management, sales reporting, and payout schedules. WooCommerce

However, if you want the marketplace itself to be the product rather than an ecommerce store with multiple sellers, I'd also look closely at Sharetribe. Its architecture is designed around marketplace interactions rather than simply adding vendors to a conventional store.

If you tell me (1) roughly how many artisans you expect, (2) physical products vs digital/services, (3) whether you need Stripe Connect/automatic payouts, and (4) your budget, I can give you a much more specific platform recommendation and architecture.

For a one-person print-on-demand shop, I’d optimize for low fixed cost + easy POD integration, rather than choosing the most powerful platform.

My shortlist

Big Cartel is particularly interesting for your situation: it explicitly supports print-on-demand, has 0% platform transaction fees, and its current free tier is intended for very small catalogs; its Platinum plan is $15/month. Big Cartel Big Cartel

Shopify Basic is currently $29/month when billed annually ($39 month-to-month), with unlimited products and a large app ecosystem, including POD integrations. Shopify Shopify

WooCommerce itself costs nothing, but WooCommerce estimates typical hosting at roughly $25–$350/month depending on the store, so it's not necessarily the cheapest in practice for a beginner. woocommerce.com

Square has a genuinely $0/month online-store plan, with payment processing as the main cost; however, I'd put it behind Big Cartel for a POD-first business. squareup.com squareup.com

What I'd do in your shoes

Start with Big Cartel if you're testing the business. You can keep your fixed software cost essentially at zero while you figure out whether your designs actually sell. Once you have enough traction that you need more sophisticated marketing, analytics, apps, or automation, move to Shopify.

If you already have a fairly large catalog and you're serious about building a brand from day one, I'd skip the ultra-cheap option and start with Shopify Basic.

One important wrinkle: the POD supplier can matter more to your economics than the storefront software. Product base cost, shipping, fulfillment location, print quality, returns, and integration fees can easily overwhelm a $15–$30/month platform difference.

If you tell me roughly what you're selling (shirts, mugs, posters, stickers, etc.), expected monthly sales, and whether you're starting with Etsy or your own website, I can work out the cheapest setup—including the POD supplier—and estimate your break-even point.

I’d recommend Shopify, especially if you want the simplest path to international DTC.

• Shopify Markets supports localized currencies, languages, domains, pricing, and market-specific catalogs. Shopify Shopify Help Center
• Customers can browse and check out in local currency when using Shopify Payments or Adyen. Shopify Help Center
• Managed Markets can additionally handle cross-border tax/duty and merchant-of-record responsibilities for eligible merchants. Shopify Help Center
• BigCommerce is worth considering if you need more complex multi-storefront architecture or highly customized regional experiences. BigCommerce BigCommerce

Bottom line: Shopify for ease and speed; BigCommerce if sophisticated multi-storefront customization is the priority.

For an agency building and operating multiple client stores, I’d narrow the field to Shopify Plus vs. BigCommerce Multi-Storefront. The key distinction is whether your “multi-store” requirement means many independent client businesses or many storefronts belonging to one merchant.

My take

If you're an agency building stores for lots of unrelated clients: Shopify is probably the better operational fit.

Shopify's Partner infrastructure is explicitly designed around agencies: you can create dev stores and client-transfer stores, build them under your Partner organization, collaborate with clients, and transfer ownership when the project goes live. Shopify Help Center Shopify Help Center

For larger clients using Shopify Plus, organizations give you centralized user management, billing, store administration, and expansion-store functionality. Shopify Help Center Shopify Help Center

The important caveat: Shopify Plus expansion stores aren't a true shared-database multisite system. Each store has its own products, inventory, settings, etc.; synchronization generally requires apps or an ERP. Shopify Help Center

Where BigCommerce gets interesting

If your agency's model is more like:

"We have one client/company with 10 brands, regions, or storefronts, and we want to operate all of them from one backend."

then BigCommerce Multi-Storefront deserves serious consideration.

It lets you manage multiple storefronts from one control panel, with different domains, branding, catalogs, pricing, currencies, and customer experiences. Products can be made available on selected storefronts, while analytics and management remain centralized. BigCommerce BigCommerce

That's a materially different architecture from having 10 completely independent Shopify stores.

The decision I'd use

• Agency → many unrelated clients → Shopify
• One client → many brands/regions/storefronts → BigCommerce Multi-Storefront
• High-end Shopify clients needing international/B2B/brand expansion → Shopify Plus
• Clients needing centralized catalog + multiple distinct storefronts → BigCommerce MSF
• Agency wants maximum ecosystem, talent pool, apps, and client familiarity → Shopify

One other consideration: Shopify Plus currently includes the main store plus 9 expansion stores in the base monthly platform fee, with additional-store pricing beyond that; separate brands can require separate Plus contracts. Shopify

If you tell me roughly how many stores you expect to manage (10 / 50 / 500+) and whether each client needs their own Shopify/BigCommerce account, I can map out the actual agency operating model—store creation, staging, permissions, billing, client handoff, reusable themes, app management, and centralized reporting.

For larger clients using Shopify Plus, organizations give you centralized user management, billing, store administration, and expansion-store functionality. Shopify Help Center Shopify Help Center

The important caveat: Shopify Plus expansion stores aren't a true shared-database multisite system. Each store has its own products, inventory, settings, etc.; synchronization generally requires apps or an ERP. Shopify Help Center

Where BigCommerce gets interesting

If your agency's model is more like:

"We have one client/company with 10 brands, regions, or storefronts, and we want to operate all of them from one backend."

then BigCommerce Multi-Storefront deserves serious consideration.

It lets you manage multiple storefronts from one control panel, with different domains, branding, catalogs, pricing, currencies, and customer experiences. Products can be made available on selected storefronts, while analytics and management remain centralized.

That's a materially different architecture from having 10 completely independent Shopify stores.

The decision I'd use

If your priorities are self-hosting, full source-code access, and deep customization, I’d narrow it to Medusa, Saleor, Vendure, and WooCommerce. The biggest decision is whether you want a traditional store you can customize, or a headless commerce engine where you build the storefront yourself. OpenReplay Blog Toolradar

My shortlist

If I were building a new custom store

I'd look at Medusa first.

It gives you a commerce backend rather than forcing your storefront into a particular theme/CMS. You can build the customer-facing site with Next.js/React, while Medusa handles products, carts, orders, payments, fulfillment, regions, etc. Its Node/TypeScript architecture is particularly attractive if you want to write your own business logic. OpenReplay Blog OpenSourceProjects.cc

A typical architecture would be:

                 ┌─────────────────────┐
                 │   Next.js Storefront│
                 │   Your design/UI    │
                 └──────────┬──────────┘
                            │
                         API/SDK
                            │
                 ┌──────────▼──────────┐
                 │       Medusa        │
                 │                     │
                 │ Products            │
                 │ Cart                 │
                 │ Orders               │
                 │ Customers            │
                 │ Pricing              │
                 │ Promotions           │
                 │ Payments             │
                 │ Fulfillment          │
                 └──────────┬──────────┘
                            │
                    ┌───────▼───────┐
                    │  PostgreSQL   │
                    └───────────────┘

That gives you much more architectural freedom than something like Shopify.

When I'd choose the others

Saleor — I'd investigate this if you have a Python team or need sophisticated multi-channel, multi-region, B2B, or GraphQL-driven commerce. Its documentation specifically covers multi-region commerce, marketplaces, custom shipping, digital products, and dashboard extensions. Saleor Documentation

Vendure — particularly interesting if you're already a TypeScript developer and want a strongly structured plugin architecture with GraphQL. Kryeo

WooCommerce — choose this if you want to get a conventional store running quickly and benefit from the enormous WordPress ecosystem. It's explicitly open-source and customizable, with a large extension ecosystem. WooCommerce The tradeoff is that you're building on WordPress/PHP rather than a clean, modern headless commerce architecture.

The important distinction

I'd divide your options like this:

"I want a store I can install and customize."

→ WooCommerce / PrestaShop

"I want to build my own ecommerce product and control essentially everything."

→ Medusa / Vendure / Saleor

If by "customize fully" you mean things like custom checkout logic, unusual product configurations, subscriptions, custom pricing rules, multiple storefronts, custom customer accounts, integrations with your own backend, mobile apps, etc., I'd lean toward the headless group rather than WooCommerce.

If you tell me what you're selling, your expected scale, and what tech stack you prefer (Node/TypeScript, Python, PHP, etc.), I can narrow this down to 1–2 options and give you a recommended architecture and hosting setup.

For a mobile storefront specifically, Shopify currently has the most turnkey developer experience of the platforms I checked.

Why I'd lean Shopify

Shopify has an explicit mobile commerce stack: the Storefront API handles products, search, carts, and checkout URLs, while Checkout Kit embeds Shopify checkout in iOS, Android, and React Native apps. shopify.dev

It also provides official mobile libraries, including iOS and Android SDKs, and Shopify documents native mobile storefront tutorials end-to-end. shopify.dev

That means your app architecture can be roughly:

Mobile UI → Shopify Storefront API → Cart → Checkout Kit → Shopify payment/order processing

You don't have to build the entire commerce backend or payment/checkout system yourself.

When I'd choose Medusa instead

Medusa is interesting if control and customization matter more than turnkey functionality. Its Store API is REST-based specifically for storefronts including commerce mobile apps, and it supports JWT authentication that's designed for client/mobile applications. docs.medusajs.com

The tradeoff is that you're taking on more of the commerce infrastructure yourself. Medusa gives you the APIs and backend, but Shopify gives you a more complete mobile purchasing path out of the box.

My practical recommendation: if you're building an MVP or want to get a polished iOS/Android storefront shipping quickly, start with Shopify. If you're building a highly customized commerce product where you want ownership of the backend and checkout architecture, evaluate Medusa.

If you tell me whether you're using React Native, Flutter, Swift/Kotlin, or another stack, I can compare the actual API/SDK integration for those three and show what the implementation would look like.

If the priority is tight monthly cost + solid core ecommerce, I’d narrow it to WooCommerce and Shopify, with BigCommerce as a third option if you need more built-in functionality.

*Before payment processing, apps/extensions, themes, and other optional costs.

My practical recommendation

Choose WooCommerce if keeping the monthly bill as low as possible is the dominant constraint and you're comfortable with WordPress/hosting. The core platform itself is free, with hosting typically being the main fixed cost; WooCommerce says most stores spend roughly $25–$350/month on hosting depending on requirements, but a small store can be considerably leaner. WooCommerce woocommerce.com

Choose Shopify Basic if you can afford ~$29/month annually and want the simplest path to a dependable store. Its Basic plan includes a full online store, unlimited products, inventory management, checkout, social/marketplace selling and shipping tools. Shopify shopify.com

Consider BigCommerce if you specifically want more ecommerce functionality built into the platform rather than assembling it from apps. Its Core plan is $29/month when billed annually, but the current plan has a $30K trailing-12-month GMV threshold, and BigCommerce introduced additional fees for some open payment providers in 2026. bigcommerce.com bigcommerce.com

For a small, budget-conscious store selling ordinary physical products, I'd start by pricing out WooCommerce vs. Shopify Basic based on your actual monthly sales and number of products. The payment-processing economics can matter more than the subscription price once you have meaningful revenue.

If you tell me your approximate monthly budget, expected monthly sales, number of products, and whether you already have WordPress/hosting, I can narrow it down to the most economical setup.

For a two-person boutique on a tight budget, I’d start with Square Online if you already use Square for in-person sales, or Big Cartel if you mainly need a simple online catalog/store.

• Square Online: $0/month on the Free plan; you pay payment-processing fees when you sell. It also syncs online and in-person inventory. Square Square
• Big Cartel: Free for up to 5 products; $15/month for up to 50 products on Platinum, with no platform transaction fees. Big Cartel Big Cartel
• Shopify: More powerful, but its standard plan starts substantially higher, so I wouldn't choose it purely for minimizing monthly costs. Shopify

My practical pick: Square if you have a physical shop/POS; Big Cartel if you're primarily selling a small curated collection online.

If you sell mostly digital downloads plus a smaller number of physical products, I’d narrow it to Shopify vs. WooCommerce.

My pick: Shopify

For your mix, Shopify is probably the easiest all-around choice.

• Digital downloads: Shopify’s free Digital Products app can automatically deliver PDFs, ZIPs, videos, templates, etc., with download limits and secure links. Shopify Shopify Help Center
• Physical products: You get inventory, shipping, variants, fulfillment, and the normal ecommerce features in the same store.
• Mixed products: You can sell a physical item with a digital download attached—for example, a physical workbook that also includes a PDF version. Shopify Help Center
• Mixed orders: Shopify separates digital and physical fulfillment, so customers can receive their download immediately while the physical portion is still being shipped. Shopify Help Center
• Growth: It's hosted and relatively low-maintenance, with a large ecosystem of apps if you later need email marketing, bundles, subscriptions, upsells, etc.

shopify.com

When I'd choose WooCommerce instead

WooCommerce is worth considering if you already have a WordPress site or want maximum control over your website.

It natively supports physical, virtual, and downloadable products, including products that combine shipping with a download. WooCommerce WooCommerce

The tradeoff is that you'll generally have more responsibility for hosting, WordPress updates, plugins, security, and maintenance.

woocommerce.com

Quick comparison

I wouldn't make Gumroad your primary store if physical products are an important part of the business; its strength is primarily the digital-product/creator side.

Bottom line: If you want one storefront that can handle both without much technical work, I'd start with Shopify. If you already have a WordPress site and enjoy having more control, WooCommerce is a strong alternative.

If you tell me roughly how many digital products you have, how many physical products, and your monthly sales/revenue, I can also compare the actual costs of Shopify, WooCommerce, Gumroad, and a couple of other options for your situation.

If you’re a solo entrepreneur selling custom T-shirts and your priority is “I don’t want to manage servers, hosting, updates, or infrastructure,” I’d lean toward Shopify.

My practical recommendation

shopify.com + a print-on-demand provider such as Printful or Printify.

Why it fits:

• Fully hosted: Shopify handles the storefront infrastructure, hosting, security, and platform maintenance.
• Built specifically for commerce: You get payments, checkout, inventory, orders, discounts, analytics, etc., without assembling a WordPress/WooCommerce stack.
• Excellent POD ecosystem: Shopify currently supports hundreds of print-on-demand integrations, and its own documentation specifically lists providers such as Printful. Shopify Shopify Help Center
• No inventory required: A POD provider can print and ship each shirt after the customer orders. Shopify
• Room to grow: You can start with a handful of designs and later add personalization, subscriptions, marketplaces, social selling, email marketing, etc.

Shopify vs. Wix

Wix is a perfectly viable alternative: it has built-in e-commerce hosting and POD integrations, including Printful and Printify. wix.com wix.com

I'd choose Wix if your business is primarily a personal/creative brand website with a relatively small shop. I'd choose Shopify if selling T-shirts is the core business.

What I'd actually build

For a one-person T-shirt business, I'd keep the stack simple:

Shopify → Printful/Printify → payment processor → customer

You design the shirts and market them. The platform handles the website/order infrastructure, while the POD supplier handles production and fulfillment. That gets you very close to a zero-server-management business. Shopify Shopify

If you tell me your approximate monthly sales target and whether customers customize the shirt themselves or you're selling pre-designed shirts, I can narrow this down to the most appropriate platform + POD setup.

For a small B2B parts supplier with a handful of wholesale customers, the best choice usually comes down to how complicated your pricing rules are. Customer-specific pricing is one of the areas where B2B platforms differ the most. BigCommerce Commerce Pundit

Here’s how I’d shortlist them:

For your specific description (“small supplier, a few wholesale customers”), I’d lean:

1. BigCommerce — likely the best balance

It fits businesses that need:

• Different prices for different customers
• Customer login portals
• Wholesale-only catalogs
• Quantity discounts
• Reordering of common parts
• Less custom development

BigCommerce specifically supports assigning price lists to customer groups or individual wholesale accounts, including SKU-level pricing. BigCommerce

2. Shopify — if simplicity matters more than deep B2B

Choose this if:

• You already use Shopify
• You expect to add consumer sales later
• Your wholesale pricing is relatively simple (for example, “Customer A gets 20% off all parts”)

It can handle B2B, but unusual pricing matrices (hundreds of negotiated part/customer combinations) can become app-dependent. BigCommerce

3. Avoid overbuilding early

For a few wholesale accounts, you probably don’t need an enterprise platform unless you have things like:

• Thousands of customers with negotiated contracts
• Multiple warehouses
• Complex quoting workflows
• ERP-driven pricing
• Sales reps managing accounts

A few questions would narrow this down a lot:

1. How many SKUs/parts do you sell (50, 500, 50,000+)?
2. Are prices negotiated per customer (Customer A pays $8.25, Customer B pays $7.90) or mostly customer tiers (all wholesalers get 20% off)?
3. Do you need customers to place orders online, or is the site mainly a catalog/reorder tool?
4. What accounting/ERP system do you use (QuickBooks, NetSuite, SAP, something else)?

For a small maker business (handmade goods, crafts, art, candles, jewelry, ceramics, apparel, etc.) that needs a simple POS + an online store, I’d usually narrow it to Shopify vs Square. The right pick depends mostly on where your sales happen. Shopify TechnologyAdvice

My short recommendation

Pick shopify.com if:

• Your goal is to build a brand and grow online
• You expect online sales to become a major part of the business
• You want a polished website, better product pages, email marketing, shipping tools, and room to expand
• You sell at craft fairs/pop-ups but want everything tied together in one inventory system

Shopify’s strength is ecommerce first, with POS added on. It’s generally the better fit for makers who want their website to become their main storefront. Shopify TechnologyAdvice

Pick squareup.com if:

• Most of your sales are in person
• You do farmers markets, craft fairs, pop-ups, studios, or a small physical shop
• You want the simplest setup and lowest upfront cost
• You mainly need a card reader, inventory, receipts, and a basic online presence

Square started as a POS/payment system, so it tends to feel simpler for occasional in-person selling. Fit Small Business TechnologyAdvice

How I’d choose for common maker scenarios

What about Etsy + Square?

That combo can work well early because Etsy provides marketplace discovery while Square handles in-person payments. The downside is that inventory, customer data, and branding are split between systems. Shopify

My default setup for a serious small maker in 2026:

• Starting out / mostly local: Square + Etsy
• Trying to build a long-term brand: Shopify + Shopify POS
• Already getting steady online traffic: Shopify from day one

A few details would change the answer:

1. What do you make (jewelry, food, clothing, art, etc.)?
2. Roughly what % of sales will be in person vs online?
3. Do you already sell on Etsy or are you starting from scratch?

For a neighbourhood gift shop, I’d look for software that lets you keep a simple spreadsheet of SKU, product name, description, price, stock, category, and image URL and upload it without a lot of technical cleanup. These are the strongest options:

For your specific use case, I’d usually narrow it to:

Easiest day-to-day: Shopify

• You can build a spreadsheet, save as CSV, and import products in bulk. Shopify Help Center
• Good for gift shops with lots of one-off items, seasonal collections, and simple variants.
• Less time spent maintaining the website.

Most spreadsheet-friendly/flexible: WooCommerce

• The importer includes column mapping, so it can adapt better if your supplier spreadsheets have unusual columns. WooCommerce
• If you later need custom fields (gift occasions, materials, makers, etc.), WooCommerce has more room to customize. A paid extension can expand CSV handling for larger or more complex catalogs. WooCommerce

A few questions would change the recommendation:

1. Do you already use a checkout system (Square, Clover, Lightspeed, etc.)?
2. Roughly how many products do you carry (100, 1,000, 10,000+)?
3. Do you need the spreadsheet to update stock levels automatically, or just add new products?

For a small artisan selling both ready-made goods and custom items, these are strong fits:

• shopify.com — Best all-around/easiest setup. Use pre-order and made-to-order apps to show production windows, collect deposits, and manage custom items. Shopify supports pre-orders through apps with payment options such as full, partial, or later payment depending on setup. Shopify Help Center Shopify Help Center
• woocommerce.com — Best if you want more control. With WooCommerce Pre-Orders you can set availability dates, charge upfront or on release, and manage handmade or limited-run products. WooCommerce WooCommerce Add a lead-time plugin for “ships in 3–5 weeks” style messaging. Barn2 Plugins
• etsy.com — Good for artisan discovery, but custom lead-time workflows are less flexible than running your own store.

For your use case, I’d lean:

1. Shopify if you want simple operations and growth.
2. WooCommerce if your custom orders need detailed options, forms, or unusual workflows.
3. Etsy + Shopify/WooCommerce if you want marketplace traffic plus a dedicated shop.

Look for features like:

• per-product production times (“made in 2–4 weeks”)
• deposits or partial payments
• custom fields/options
• order notes and customer approvals
• preorder status emails
• ability to mix in-stock and made-to-order items

For a handmade business, avoid platforms that only handle “out of stock preorders” but cannot communicate custom production timelines.

Yes. If the client literally has $0 budget for hosting, you have several workable options.

Best options

• squareup.com — Probably the easiest choice for a normal physical-product store. The Free plan is $0/month, includes hosted ecommerce, SSL, checkout, inventory, and a Square-hosted URL. You pay payment-processing fees when something sells. Square Square
• bigcartel.com — Genuinely free for a tiny catalog: up to 5 products, with a hosted storefront and no monthly fee. Good for artists, merch, or a very small product line. Big Cartel Big Cartel
• ecwid.com — Useful if you're already building a static site and want to embed ecommerce into it. Its free offering is more limited, so I'd check the current product/payment limits before committing.
• pages.github.com + a payment provider — If you're comfortable coding, you can host the storefront itself for free on static hosting and use something like Stripe Checkout/payment links. This gives you much more design control, but you'll have to build more of the ecommerce functionality yourself.

What I'd do as a freelancer

If this is a real client store with products, cart, checkout, orders, etc., I'd lean toward Square Online Free. You can build the client a legitimate hosted store without asking them to pay for hosting, and the platform handles the infrastructure. Square explicitly says its free plan includes hosting and SSL. Square

The catch is that "free hosting" doesn't mean "free ecommerce." Payment processing still costs money when the client makes sales, and custom domains generally require a paid plan. Square

If you tell me what you're building it with (plain HTML/JS, React/Next.js, WordPress, etc.) and roughly how many products, I can suggest a completely $0/month architecture that you can hand off to the client.

If your goal is a storefront that costs $0/month and lets you sell products as preorders/crowdfunding campaigns, I’d narrow it to a few approaches:

My recommendation: Shopify + a free preorder/crowdfunding app

This is probably the best fit if you want something that can grow into a real store.

• Shopify gives you the actual storefront, checkout, product pages, order management, etc.
• Its App Store currently has 100+ preorder apps with crowdfunding functionality, including several with free plans. Shopify App Store Shopify App Store
• For example, Lift: Crowdfunding Presales is currently listed as free and is specifically designed for crowdfunding, presales, and product drops. Shopify App Store
• UpRank: Crowdfund & Preorders also has a free plan and is specifically designed around crowdfunding/preorders. Shopify App Store
• There are also free preorder apps if you don't need sophisticated crowdfunding mechanics. Shopify App Store

The catch: Shopify itself isn't permanently free, so if "$0 platform cost" is an absolute requirement, I'd look at a different setup.

If you mean literally free: I'd consider a simple storefront + payment link

For an initial crowdfunding campaign, you may not actually need a full ecommerce platform. A landing page can explain:

We're making X.
Goal: 500 units
Current commitments: 327
Estimated delivery: March 2027
Preorder — $49

Then send customers through a payment/checkout system.

That can be dramatically cheaper than building a conventional ecommerce store, particularly if you're validating whether people will actually buy.

One important distinction

There are really three different things people call "crowdfunding":

1. Preorder: Customer pays $50 now → you manufacture → ship the product later.
2. Deposit/pledge: Customer pays $10 now → pays the remaining $40 when production is confirmed.
3. True crowdfunding: Campaign has a funding target, deadline, backer tiers/rewards, progress bar, etc.

If you want #3, I'd specifically use a crowdfunding/preorder app rather than trying to fake it with a normal ecommerce product. Shopify's ecosystem now has dedicated apps for exactly this; for example, LaunchMate supports preorder, donation, hybrid, and tiered-backer campaigns, although its current plans are paid after a trial. Shopify App Store

If you tell me what you're selling and whether you need customers to pay 100% upfront or just pledge/deposit, I can give you a specific $0-cost stack and explain exactly how I'd set it up.

That can be dramatically cheaper than building a conventional ecommerce store, particularly if you're validating whether people will actually buy.

One important distinction

There are really three different things people call "crowdfunding":

1. Preorder: Customer pays $50 now → you manufacture → ship the product later.
2. Deposit/pledge: Customer pays $10 now → pays the remaining $40 when production is confirmed.
3. True crowdfunding: Campaign has a funding target, deadline, backer tiers/rewards, progress bar, etc.

If you want #3, I'd specifically use a crowdfunding/preorder app rather than trying to fake it with a normal ecommerce product. Shopify's ecosystem now has dedicated apps for exactly this; for example, LaunchMate supports preorder, donation, hybrid, and tiered-backer campaigns, although its current plans are paid after a trial.

For a tight-budget, headless-first shop, I’d put Medusa at the top of the evaluation list.

• Medusa — particularly compelling if your team is comfortable with TypeScript/Node. Its managed Cloud starts at $29/month, has 0% GMV fees, and includes backend + storefront hosting. You can also self-host, so you retain an escape hatch if infrastructure costs become important. docs.medusajs.com
• Saleor — very capable GraphQL/headless option, with an open-source version you can self-host. However, its managed Cloud pricing is currently much higher, starting at $1,599/month, so it makes more sense if you specifically value its architecture/features or have the engineering resources to self-host. saleor.io
• Shopify + Hydrogen — worth evaluating if minimizing engineering/operations work matters more than minimizing platform cost. It's generally a different tradeoff: managed commerce infrastructure and ecosystem versus greater platform dependence.

My evaluation shortlist

For a small team, I'd prototype the same simple store in Medusa and Shopify/Hydrogen, then compare the actual monthly cost and developer effort. Medusa's $29 Cloud entry point makes that experiment relatively inexpensive. docs.medusajs.com

If you tell me your expected monthly orders, SKU count, and frontend stack (e.g. Next.js), I can narrow this to a concrete low-cost architecture and estimated monthly bill.

If you’re testing one product for a few weeks and want $0/month recurring cost, I’d avoid full Shopify-style setups at first. You mainly need:

• a focused landing page
• checkout/payment link
• basic order handling
• no monthly subscription

Good options:

For a 2–4 week product validation test, I’d probably choose:

1. Physical product: Square Online or Corpus + Stripe
2. Digital product: Payhip
3. Ad-testing landing page first (before building a store): Zoho LandingPage + payment link

A simple test stack could be:

• Landing page: free builder
• Checkout: Stripe Payment Link
• Analytics: Google Analytics or the landing page’s built-in analytics
• Traffic: organic posts or small ad test

I would avoid starting with Shopify unless you already know the product sells, because the monthly subscription becomes a fixed cost before you have proof of demand.

I’d start with itch.io for a budget-friendly indie game storefront. It supports direct game downloads, paid sales, downloadable license/access keys, bulk keys for press/promotions, and optional Steam-key distribution. itch.io itch.io

• itch.io: Best low-cost all-in-one option; no upfront storefront cost, flexible revenue share, hosting included. itch.io
• Gumroad: Simple direct-sales alternative; currently 10% + $0.50 per direct transaction, with tax handling included. Gumroad
• Own store + specialized delivery: More control, but more setup and hosting complexity.

For a solo/indie dev selling downloads + license/Steam keys, itch.io is probably the simplest starting point. itch.io

For a small handmade-goods shop, tight budget, and maximum control, I’d start with WooCommerce on self-hosted WordPress.

Why it fits:

• No platform subscription or per-order fee — WooCommerce itself is open source; you mainly pay for hosting, your domain, payment processing, and any optional extensions. woocommerce.com
• Easy to self-host — unlike headless platforms such as Medusa or Saleor, you get a complete storefront and admin rather than having to build the frontend yourself. www.opensourcegroups.com
• Huge ecosystem for payments, shipping, taxes, product variations, coupons, email, SEO, etc.
• Excellent for handmade products where you might need variants such as size/color, inventory counts, made-to-order products, and custom shipping rules.
• You retain control of your site, database, code, and hosting, and WooCommerce exposes a REST API for further customization. woocommerce.com

The alternatives

PrestaShop is probably the main alternative I'd investigate. Its current open-source version is fully self-hostable and includes catalog, inventory, orders, shipping, payments, SEO, and customization capabilities. prestashop.com

I wouldn't start with Medusa or Saleor for a tiny shop unless you're already comfortable developing software. They're powerful API/headless systems, but you'll generally take on considerably more development and operational work than with WooCommerce. openbusinessnetwork.online

A very cheap setup

I'd aim for:

Your domain → inexpensive Linux hosting/VPS → WordPress → WooCommerce → free/lightweight theme → Stripe/PayPal → automated backups

The important caveat is that open source doesn't mean zero cost. Hosting, payment processing, backups, security updates, and occasional paid plugins can still cost money. www.velsof.com

If you tell me roughly how many products you have, whether they're made-to-order, and whether you're comfortable with Linux/Docker, I can narrow this down to a specific stack and a realistic $/month self-hosting budget.

For a 10-person engineering team building a high-traffic headless storefront, I’d shortlist Medusa, Saleor, and Vendure. I’d lean toward Medusa if your team is primarily TypeScript/React, but the architecture and API preferences matter more than a generic “best platform” label.

Medusa describes its core as a customizable commerce framework with modules for DTC, B2B, marketplaces, etc. GitHub Saleor is GraphQL-first and currently documents a stack designed for composable/headless deployments; its site also reports production deployments handling very large API volumes. Saleor Saleor Vendure is TypeScript/NestJS/GraphQL and explicitly supports self-hosting on Docker/Kubernetes/cloud infrastructure. GitHub

What I'd choose for your situation

1. Medusa — my default shortlist choice

For a 10-person startup, the big advantage is that your storefront and commerce backend can live comfortably in the same TypeScript ecosystem. That reduces context switching and makes it relatively straightforward to implement custom pricing, promotions, checkout logic, integrations, and asynchronous workflows.

It's also modular rather than forcing you into a giant monolithic commerce suite. GitHub

For high traffic, I'd architect it roughly as:

CDN → Next.js/React storefront → cache → Medusa API → PostgreSQL + Redis → async workers → external services

Don't interpret "high traffic" as requiring the commerce API itself to handle every storefront request. Cache aggressively at the storefront/CDN layer and keep the transactional path—cart, checkout, inventory, order creation—much smaller.

2. Saleor — seriously consider it if GraphQL is central

Saleor is attractive if your team likes Python/Django and wants a GraphQL-native commerce API. Its current open-source stack includes the API, dashboard, extensions/apps, and composable storefront tooling. Saleor

One particularly interesting data point for your use case is Saleor's published infrastructure scale: its site currently reports deployments handling 1B+ API requests/month and hundreds of thousands of orders/month. That doesn't mean your deployment automatically scales that way, but it is evidence that the architecture is intended for substantial traffic. Saleor

I'd favor it when GraphQL + sophisticated multi-channel/B2B commerce are more important than having an all-TypeScript stack.

3. Vendure — strong choice for a structured TypeScript team

Vendure is also a very natural fit for a React/TypeScript startup. It uses NestJS and GraphQL and has a plugin-oriented architecture. GitHub

I'd put it especially high on the list if you expect the commerce domain to become complicated—multiple channels, B2B, marketplace functionality, subscriptions, custom business rules—and you want more architectural structure imposed by the framework.

The decision I'd make

If you told me only:

10 engineers + high-traffic + headless + open source + startup

I'd start with Medusa and Vendure, then add Saleor if your team is comfortable with Python/GraphQL.

The more important question is actually what kind of "high traffic" you mean. A storefront getting 100k requests/minute is a very different engineering problem from a catalog with 10 million SKUs or a checkout system processing 1,000 orders/minute.

If you give me your approximate peak requests/minute, SKU count, orders/minute, B2C vs B2B, and whether your team is TypeScript or Python, I can give you a much more concrete architecture comparison—including where I'd put Redis, Postgres replicas, search, CDN caching, queues, and inventory so you don't accidentally make the commerce backend your bottleneck.

If your priorities are solo-founder friendly + modern admin + easy theming, I’d narrow it to Medusa, Vendure, and Saleor rather than the older all-in-one platforms.

My practical shortlist

Medusa

For your particular situation, Medusa is probably the first one I'd investigate.

Its admin is genuinely modern: it has light/dark themes, search, configurable layouts, and can be extended with custom admin pages/widgets. Medusa Docs Medusa Docs Medusa Docs

The storefront is deliberately separate from the commerce backend, so you can use a React/Next.js frontend and essentially make the customer-facing site look however you want. Medusa also provides a Next.js starter with a fairly polished starting design. Medusa Docs Medusa Docs

The catch for a low-code founder is that headless means you're still responsible for the storefront. You don't get the same "pick a theme, change colors, publish" experience that you get from Shopify or WooCommerce.

Vendure

I'd put Vendure very close to Medusa if you're comfortable with TypeScript.

Its current dashboard has a modern theming system based around CSS variables/Tailwind, and you can customize the dashboard's appearance. Vendure Developer Hub

It's particularly interesting if you expect to eventually need sophisticated commerce logic. The tradeoff is that you're still dealing with a developer-oriented headless system rather than a turnkey merchant platform.

Saleor

Saleor has an excellent modern architecture and very capable dashboard/API, with built-in concepts for things like channels, promotions, multi-region selling, and dashboard extensions. Saleor Documentation

But for a solo founder with limited development experience, I'd be cautious about choosing it solely because it looks polished. Its Python/Django + GraphQL architecture introduces a different technical stack, whereas Medusa keeps you in the JavaScript/TypeScript ecosystem. Eryx Innovations Lab

The important distinction

If by "easy theming" you mean:

"I want to install a theme, change fonts/colors/layout, add products, and mostly stay out of code."

Then I would actually look at WooCommerce or Shopware before these headless platforms.

If you mean:

"I want a modern-looking storefront that I can heavily customize without fighting the platform."

Then Medusa is the one I'd prototype first.

The architecture is essentially:

Medusa → products/orders/payments/commerce logic
Next.js → your actual website/design

That separation is what makes the theming flexible, but it's also what makes Medusa more technical than Shopify/WooCommerce. Medusa Docs

For a solo founder, I'd test one thing before committing: take your desired homepage/product page design and try rebuilding it with Medusa's starter. If you can get ~80% of your desired look without needing custom backend code, you've probably found a good fit.

If you tell me what you're selling (physical products, digital products, subscriptions, marketplace, etc.) and whether you want to use a visual builder, I can narrow this down to 2–3 platforms and explain the actual setup effort.

For an enterprise team prioritizing scalability, containerized deployment, and long-term control, I’d shortlist Medusa, Saleor, and Vendure rather than traditional monolithic platforms. Current comparisons consistently identify these as the major open-source headless options. Vendure Pawel Owerczuk

My recommendation: Medusa

For a greenfield enterprise deployment, I'd generally start with Medusa if your engineering organization is already strong in TypeScript/Node.js. Its modular architecture makes it well suited to separating services and scaling workloads horizontally, while its API-first/headless model works naturally with Kubernetes, containers, independent storefronts, and surrounding microservices. Recent production comparisons also report an active ecosystem and substantial contributor base. Pawel Owerczuk

A typical deployment could look like:

                    ┌───────────────┐
                    │ CDN / WAF     │
                    └───────┬───────┘
                            │
                    ┌───────▼───────┐
                    │ Next.js / Web │
                    └───────┬───────┘
                            │
              ┌─────────────▼─────────────┐
              │       Kubernetes          │
              │                           │
              │  Medusa API pods          │
              │  Worker pods              │
              │  Custom commerce modules  │
              └──────┬─────────┬──────────┘
                     │         │
              ┌──────▼───┐ ┌──▼──────┐
              │PostgreSQL│ │ Redis   │
              └──────────┘ └─────────┘

Choose Saleor instead if your organization is predominantly Python/Django and wants a GraphQL-first commerce platform with substantial built-in enterprise/B2B functionality. Pawel Owerczuk Eryx Innovations Lab

Choose Vendure instead if you're a TypeScript/NestJS organization that particularly values its plugin architecture and structured backend. One important consideration is its GPLv3 licensing model, versus the more permissive licensing associated with Medusa's core, so enterprise legal review matters. Pawel Owerczuk

So, assuming TypeScript + Kubernetes + high customization + enterprise scale, my shortlist would start with Medusa, with Saleor as the main alternative for a Python/GraphQL organization. This is a fit-based recommendation rather than a universal ranking—the architecture and team stack should drive the final choice. Vendure

For a technically savvy team selling digital downloads, I’d shortlist these:

• spreecommerce.org — strongest if you want control. It’s API-first, self-hostable, has REST APIs/OpenAPI tooling, and supports digital products, subscriptions, and custom fulfillment flows. Good fit if you’ll build your own download entitlement service. Spree Commerce Spree Commerce
• shopify.dev — best ecosystem. Its Storefront API works well for headless builds, but digital delivery usually relies on apps or your own fulfillment layer rather than a native “digital asset pipeline.” Shopify
• bigcommerce.com — strong catalog/order APIs and mature headless support; good if you want SaaS reliability and less infrastructure ownership. BigCommerce
• business.adobe.com — powerful downloadable-product workflows via REST APIs, but heavier operationally. Experience League

For a developer-centric digital download store (files, licenses, memberships, gated content), I’d lean Spree or a custom backend around Shopify/BigCommerce + object storage (S3/R2) + signed URLs. The key API features to evaluate are: webhook reliability, entitlement modeling, download limits, license-key support, refund/revocation workflows, and CDN delivery.

Lemon Squeezy fits this use case particularly well. It provides license keys/entitlements, subscription-linked access, customer downloads, and securely signed/throttled download links. You can replace uploaded files with each release so existing customers receive the latest version. LemonSqueezy Lemon Squeezy Docs

Gumroad also supports license verification, but more of the entitlement enforcement is left to your application. gumroad.com

Yes. For digital zines + music with pay-what-you-want pricing and optional extra support, I’d shortlist these:

1. Payhip — probably the simplest fit

payhip.com supports PWYW directly: you can set a product to 0+ for completely optional payment, or 5+ for a $5 minimum with customers free to pay more. It supports digital products and automatically delivers downloads. Payhip Help Center Payhip Help Center Payhip

For example, a zine could be:

Digital Zine — $5 or more
Pay what you can. If you'd like to support the project, you can choose a higher amount.

Payhip's current pricing starts at $0/month + 5% transaction fee, with paid plans reducing or eliminating the platform transaction fee. Payhip

2. Gumroad — particularly good for creator/music sales

gumroad.com also has native PWYW. You can set a minimum amount and a suggested amount, and customers can enter whatever they'd like to pay above the minimum. It also supports a $0 minimum, allowing genuinely free downloads with optional payment. Gumroad

Its current direct-sale fee is 10% + $0.50 per transaction, with a higher fee for sales through its Discover marketplace. Gumroad

3. WooCommerce — best if you want your own storefront

If you already have WordPress, WooCommerce + Name Your Price gives you substantially more control. The official extension supports customer-entered prices, suggested prices, minimums, and donations, and it works with both simple and variable products. WooCommerce WooCommerce

That's attractive if you eventually want something like:

• Zine: $3 minimum / $7 suggested / unlimited maximum
• Album: $5 minimum / $10 suggested
• Free sampler: $0+
• Separate "Support the artist" contribution
• Your own domain and storefront
• More control over branding and checkout

The tradeoff is that you're managing WordPress/WooCommerce and paying for extensions rather than getting the whole system in one hosted package.

My practical take

For a small independent publishing/music project, I'd start with Payhip if the priority is "get this working with minimal technical overhead." Its 0+ / 5+ pricing model maps almost exactly to what you're describing.

I'd choose Gumroad if you particularly value the creator-oriented marketplace/discovery ecosystem.

I'd choose WooCommerce if you want the store to become a substantial part of your own website and want maximum control over the pricing and donation experience.

One important distinction: if by "optional donations" you mean someone can buy a $5 zine and then add an entirely separate $10 donation at checkout, rather than simply letting them pay $15 for the zine, I'd verify that specific checkout flow before choosing. PWYW handles the latter very well; a separate donation field is a slightly different requirement.

Its current direct-sale fee is 10% + $0.50 per transaction, with a higher fee for sales through its Discover marketplace. gumroad.com

3. WooCommerce — best if you want your own storefront

If you already have WordPress, WooCommerce + Name Your Price gives you substantially more control. The official extension supports customer-entered prices, suggested prices, minimums, and donations, and it works with both simple and variable products.

That's attractive if you eventually want something like:

For a startup with limited funding, I’d focus on total cost of ownership rather than raw feature count. Based on current 2026 pricing and capabilities, Medusa is a particularly cost-efficient option if you have some engineering capability. Medusa Docs Medusa

Why I'd look at Medusa first

medusajs.com is open source and can be self-hosted, so the software itself doesn't require a large platform subscription. Its managed Cloud currently starts at $29/month, with Launch at $99/month and Scale at $299/month, and Medusa states that its Cloud plans have 0% GMV platform fees. Medusa Docs Medusa

That gives you a useful progression:

• Very early MVP: self-host Medusa → minimize software costs.
• Launching: Medusa Cloud Develop → $29/month starting point.
• Growing traffic: Launch → $99/month, adding things such as autoscaling, backups, custom domains and Redis-backed KV.
• More complex operation: Scale → $299/month, adding background workers and additional infrastructure. Medusa Docs

The main tradeoff is engineering effort. Headless commerce isn't inherently cheap just because the commerce engine is open source—you still need developers to build the storefront, integrations, deployment, monitoring, etc.

When I'd choose something else

Shopify + Hydrogen makes sense if your startup has limited engineering resources, rather than merely limited cash. You're paying more for a managed commerce backend, but you get Shopify's established commerce infrastructure and ecosystem. Current comparisons describe Hydrogen as the lower-operational-burden route, while Medusa gives you substantially more ownership and customization. Ribbsaeter Systems Ask An Tech

Saleor is worth considering if you specifically need its GraphQL-first architecture, sophisticated multi-channel/international capabilities, or have a Python team. Its managed offering is much more expensive than Medusa's at the current published pricing, so it is harder to justify for a cash-constrained startup unless you need those capabilities. Saleor Eryx Innovations Lab

My practical decision rule

• You have 1–3 capable developers: Medusa
• You have little/no engineering capacity: Shopify + Hydrogen
• You need complex B2B/multi-market capabilities from the outset: investigate Saleor
• You're already operating at enterprise scale: look at commercetools/other enterprise composable platforms

So, for the specific constraint "startup + limited funding + wants headless", I'd put Medusa at the top of the shortlist, provided you have enough engineering capability to own a headless stack. ShipGarden Medusa Docs

If you tell me your monthly budget, expected orders/month, tech stack (Next.js/React/etc.), and whether you need B2B, I can narrow this down to a concrete architecture and estimated monthly cost.

I’d shortlist commercetools, Saleor, and Medusa—with commercetools the strongest fit for an enterprise-grade, highly decoupled checkout.

• commercetools — API-first/composable, with a dedicated Checkout API supporting both fully custom checkout and payment-only flows. Strong choice if checkout needs to evolve independently of the frontend and integrate multiple channels. commercetools Documentation commercetools Documentation
• Saleor — GraphQL-native and fully headless, with checkout, payments, shipping, and extensibility exposed through APIs. Particularly attractive if you want maximum frontend/BFF control and open-source flexibility. Saleor Documentation Saleor Commerce
• Medusa — Very developer/customization-oriented; storefronts are separate applications and commerce operations are exposed through APIs. Good if you want to own more of the checkout implementation. Medusa Docs Medusa Docs

Architecture-wise: I’d put a Checkout BFF/service between your frontend(s) and commerce platform, rather than letting the frontend directly orchestrate carts, payments, shipping, promotions, and order creation. That gives you freedom to swap frontend frameworks/channels—and potentially commerce components—without rewriting checkout.

If you tell me your scale, B2C/B2B, payment provider(s), and whether you want SaaS vs self-hosted, I can narrow this to an architecture recommendation.

For a team that already prefers serverless frontends + JAMstack, I’d generally prioritize headless commerce platforms that have:

• strong APIs (GraphQL preferred)
• CDN-friendly content delivery
• good support for static generation/SSR hybrids (Next.js, Nuxt, Gatsby, Astro, etc.)
• webhooks/events for revalidation
• minimal backend operations work

A shortlist that fits that architecture well:

Naturaily BigCommerce Vendure## My practical grouping

If you want “JAMstack with minimal ops”

Choose:

• Shopify + a Next.js/Astro frontend
• BigCommerce headless

This keeps inventory, payments, orders, tax, and admin workflows managed while your frontend stays serverless. BigCommerce specifically supports custom storefronts through APIs and frameworks such as Next.js and Gatsby. BigCommerce BigCommerce

If your frontend team is the core differentiator

Choose:

• commercetools

This is closer to a true “commerce backend as a set of APIs.” It fits organizations that already think in terms of microservices, serverless functions, and independently deployable systems. Commercetools

If your team wants to own the stack

Choose:

• Medusa
• Saleor

These give developers more control but shift more operational responsibility onto your team. Vendure

A typical JAMstack commerce stack

A common architecture looks like:

Frontend:
Next.js / Astro / Nuxt
        |
        | API calls
        ↓
Commerce:
Shopify / BigCommerce / commercetools
        |
        ↓
Services:
Payments
Search
CMS
Tax
Inventory
ERP

For content-heavy stores, teams often pair commerce with a headless CMS such as Contentful or Sanity, letting marketing manage pages while developers keep the storefront fully decoupled.

My default shortlist for your stated preference

Without more context, I’d start evaluations in this order:

1. BigCommerce — strong balance of API flexibility and managed commerce.
2. Shopify — best if operational simplicity matters most.
3. commercetools — best if you have enterprise-scale engineering needs.
4. Medusa — best if your developers want maximum ownership.

The deciding factor is usually not the frontend architecture—the JAMstack/serverless part is compatible with most of these—but how much commerce infrastructure your team wants to own. Netguru

If you share your rough scale (startup vs enterprise), catalog size, B2B vs B2C, and preferred frontend (Next.js, Astro, Nuxt, etc.), I can narrow this to 2–3 realistic candidates.

If by “best developer tools and SDKs” you mean TypeScript quality, modern React/Next.js integration, composability, CLI/tooling, API ergonomics, and freedom to choose the frontend framework, the landscape in 2026 looks roughly like this:

Shopify

Shopify currently has arguably the most mature overall frontend developer experience.

Its Storefront API is GraphQL, and Shopify provides an official Storefront API client, Node.js libraries, Hydrogen, Hydrogen React, TypeScript tooling, and React Router tooling. Shopify

The particularly interesting development in 2026 is Shopify's new Hydrogen developer preview: Shopify is moving Hydrogen from an opinionated React/React Router framework toward a framework-agnostic SDK/toolkit that can work with different JavaScript frameworks and runtimes. Shopify Hydrogen

That makes Shopify considerably more interesting if your team doesn't want to commit to Hydrogen.

shopify.dev

Medusa

Medusa is particularly compelling if you're a developer-first team.

Its JS SDK is designed specifically for custom storefronts and can be used with Next.js, React, Vue, Angular, or essentially any JavaScript frontend. It also provides TypeScript types and explicit integration guidance for things such as Next.js caching. Medusa Docs Medusa Docs

The big difference from Shopify is architectural: Medusa gives you considerably more control over the commerce backend and business logic. That's attractive when your storefront isn't just a customized version of conventional ecommerce.

docs.medusajs.com

commercetools

commercetools has extremely strong API/SDK infrastructure, particularly for enterprise teams.

Its SDKs include an official TypeScript SDK, and they're generated from the API specifications, giving you typed representations of resources, fields, endpoints, and request builders. commercetools Documentation

The frontend SDK is also designed around editable source code rather than locking you into a proprietary frontend framework. commercetools Documentation

The tradeoff is that its developer experience is more enterprise/composable than “spin up a storefront in an afternoon.”

docs.commercetools.com

Saleor

Saleor is worth serious consideration if your developers strongly prefer GraphQL + TypeScript.

It fits naturally with modern React/Next.js architectures because the frontend can treat the commerce backend as a strongly typed GraphQL service rather than adopting a large proprietary frontend framework.

My practical takeaway

If I were evaluating purely on frontend developer experience, rather than commerce functionality or price:

• Shopify — strongest all-around ecosystem and tooling; especially compelling now that Shopify is pushing toward framework-agnostic Hydrogen.
• Medusa — strongest choice if developer control and customization matter most.
• Saleor — particularly attractive for GraphQL/TypeScript-heavy teams.
• commercetools — strongest fit for large composable/enterprise architectures.
• BigCommerce — good middle ground if you want a managed commerce platform while keeping a modern custom frontend.

One important distinction: “best SDK” and “best headless commerce platform” aren't necessarily the same thing. For example, a Next.js team may prefer Medusa's developer ergonomics while an enterprise team may prefer commercetools because of its broader composable architecture.

If your stack is specifically Next.js + TypeScript + Tailwind, I can also give you a developer-focused comparison of Shopify vs Medusa vs Saleor vs commercetools, including SDK quality, type safety, local development, webhooks, checkout customization, caching, preview environments, and deployment.

That makes Shopify considerably more interesting if your team doesn't want to commit to Hydrogen.

shopify.dev

Medusa

Medusa is particularly compelling if you're a developer-first team.

Its JS SDK is designed specifically for custom storefronts and can be used with Next.js, React, Vue, Angular, or essentially any JavaScript frontend. It also provides TypeScript types and explicit integration guidance for things such as Next.js caching. Medusa Docs Medusa Docs

The big difference from Shopify is architectural: Medusa gives you considerably more control over the commerce backend and business logic. That's attractive when your storefront isn't just a customized version of conventional ecommerce.

docs.medusajs.com

commercetools

commercetools has extremely strong API/SDK infrastructure, particularly for enterprise teams.

Its SDKs include an official TypeScript SDK, and they're generated from the API specifications, giving you typed representations of resources, fields, endpoints, and request builders. docs.commercetools.com

The frontend SDK is also designed around editable source code rather than locking you into a proprietary frontend framework. docs.commercetools.com

The tradeoff is that its developer experience is more enterprise/composable than “spin up a storefront in an afternoon.”

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

Adobe Commerce

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

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

For a wholesaler with rules like:

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

Adobe Commerce is worth serious consideration.

BigCommerce B2B Edition

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

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

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

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

Shopify Plus B2B

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

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

My practical shortlist

If your requirements are primarily:

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

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

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

For a wholesaler with rules like:

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

Adobe Commerce is worth serious consideration.

BigCommerce B2B Edition

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

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

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

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

Shopify Plus B2B

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

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

My practical shortlist

If your requirements are primarily:

For international stores requiring deep multi-currency, localization, regional pricing, tax, catalog, and market rules, the most robust headless commerce platform is usually commercetools. Naturaily Netguru

A practical ranking by scenario:

PowerGate Software Vendure### Why commercetools tends to win for global complexity

• Multiple stores/markets with different catalogs and pricing models
• Region-specific promotions and customer segments
• Flexible currency handling
• Strong API-first architecture for connecting ERP, PIM, OMS, tax, payments, and localization systems
• Designed for composable commerce rather than extending a monolithic storefront Netguru

When I would choose something else

• Under ~$50M GMV, mostly DTC: Shopify Plus is often simpler and faster operationally. Naturaily
• Need full control but have a strong engineering team: Medusa or Saleor can work well. Medusa supports regions with currency, tax, payment, fulfillment, and localized configurations, but more architecture ownership stays with you. Medusa Docs
• Complex B2B + SAP ecosystem: Adobe Commerce, SAP Commerce Cloud, or commercetools are often shortlisted. Netguru

For a truly global setup (20+ countries, multiple currencies, localized assortments, regional warehouses, different tax rules), I would shortlist:

1. commercetools
2. Shopify Plus + a strong localization stack
3. Adobe Commerce headless

The deciding factor is usually whether you need maximum business-rule flexibility (commercetools) or lower operational complexity (Shopify Plus).

Yes. If multi-seller marketplace behavior is a core requirement, I’d narrow the field to a few API-first platforms rather than generic headless commerce engines.

1. Mirakl — most marketplace-native

Mirakl is somewhat different from the others: marketplaces are its primary use case, rather than something you construct on top of a commerce engine.

Its Marketplace Platform exposes separate Front, Operator, and Seller APIs, covering things such as offers, orders, seller operations, and marketplace interactions. Mirakl Developer Portal Mirakl Developer Portal

It also supports seller onboarding/management and seller portals, and its current platform supports integrations through API, CSV, XML, and EDI. Mirakl

Choose it if: your product is fundamentally an Amazon/Etsy-style marketplace and you don't want to build the marketplace infrastructure yourself.

2. Saleor — strong headless/API option

Saleor has an explicit marketplace implementation recipe. Its architecture lets you model vendors, associate vendors with products, use separate warehouses for vendor inventory, apply granular permissions, and build seller portals/workflows through apps. Its entire marketplace layer can be built around its GraphQL API. Saleor Commerce Saleor Documentation

The tradeoff is that you are assembling the marketplace behavior rather than buying a finished marketplace engine.

Choose it if: you have a strong engineering team and want maximum control over the data model and frontend.

3. Medusa — particularly flexible for custom marketplaces

Medusa has an official marketplace recipe that demonstrates:

• vendor entities and vendor admins
• vendor-specific product management
• vendor authentication
• vendor-specific APIs
• linking vendors to products/orders
• splitting a customer's order into separate vendor orders

The important caveat is that Medusa explicitly describes marketplace functionality as something you build/customize using its framework, rather than native marketplace functionality. Medusa Docs Medusa Docs

Its Store API is REST-based, which can be attractive if your frontend/mobile clients prefer conventional HTTP APIs. Medusa Docs

Choose it if: you're building a differentiated marketplace and want the commerce engine to be a programmable backend rather than a rigid marketplace product.

4. Vendure — good TypeScript/GraphQL route

Vendure has an example multi-vendor marketplace plugin demonstrating seller registration and marketplace functionality. GitHub

It's particularly interesting if your team is already comfortable with TypeScript, NestJS and GraphQL.

Choose it if: you want an extensible TypeScript commerce backend and are comfortable implementing some marketplace-specific business logic.

The key distinction

I'd separate the options into two groups:

Marketplace infrastructure

• Mirakl → marketplace functionality is the product.

Composable commerce engines you turn into a marketplace

• Saleor
• Medusa
• Vendure

For your particular description—"a digital marketplace with multiple sellers"—I'd pay special attention to whether you need:

1. Seller onboarding/KYC
2. Seller-specific catalog management
3. Seller-specific inventory
4. Multi-seller cart
5. Automatic order splitting
6. Commissions
7. Seller payouts
8. Seller shipping/fulfillment
9. Seller permissions and dashboards
10. Refunds/returns allocated across sellers

Those requirements change the recommendation substantially. Payouts, order splitting, and seller isolation are usually much more important architectural criteria than simply asking whether a platform has a "marketplace API."

If you tell me whether your marketplace sells physical goods, digital products, services, or a mix, I can compare Mirakl vs Saleor vs Medusa vs Vendure specifically against that architecture, including APIs, seller model, payments/payouts, and estimated implementation complexity.

Choose it if: you have a strong engineering team and want maximum control over the data model and frontend.

3. Medusa — particularly flexible for custom marketplaces

Medusa has an official marketplace recipe that demonstrates:

If long-term portability and minimizing vendor lock-in are the primary criteria, I’d narrow the field to open-source, self-hostable commerce engines rather than SaaS platforms.

My shortlist

Medusa's architecture, for example, puts API routes, workflows, modules, and PostgreSQL underneath the application, and it can be self-hosted rather than requiring its cloud service. Medusa Docs

What I'd choose for a developer prioritizing portability

Medusa is probably the most straightforward choice if you're a TypeScript/Node developer.

The important distinction isn't merely "headless." It's whether you can take the entire commerce backend with you.

With an open-source/self-hostable system, you can potentially move:

Medusa → your PostgreSQL database → your infrastructure

without having to replace the underlying commerce engine. Medusa's MIT licensing is particularly attractive if you want maximum freedom to fork, modify, or operate the software independently. Current comparisons also put Medusa, Saleor, and Vendure in the strongest category for ownership/self-hosting. ShipGarden Pawel Owerczuk

Saleor is the alternative I'd examine closely if you prefer Python/Django or deliberately want a GraphQL-first architecture. Its core is BSD-3-Clause licensed and it explicitly supports self-hosting. Saleor Commerce

Vendure is another strong TypeScript option, particularly if its plugin architecture and commerce capabilities fit your application, but its GPLv3 licensing makes the legal implications different from Medusa's permissive MIT model. ShipGarden

The bigger issue: don't confuse "headless" with "portable"

You can build a beautifully decoupled Next.js frontend on top of Shopify, BigCommerce, or commercetools and still have substantial backend lock-in. The frontend is portable; your commerce model isn't necessarily.

For maximum portability, I'd design the system around these principles:

• Own the database/data exports.
• Keep your product/catalog/order/customer data in conventional formats you can export.
• Put business-specific logic in your application layer rather than proprietary platform extensions.
• Use standard payment providers rather than platform-specific payment abstractions where practical.
• Keep search, CMS, tax, shipping, email, and analytics replaceable behind interfaces.
• Don't let your frontend directly depend on hundreds of platform-specific API calls.
• Create your own domain interfaces such as ProductRepository, CheckoutService, OrderService, etc.
• Keep the commerce engine behind that boundary so replacing it becomes an implementation change rather than a rewrite.
• Prefer PostgreSQL, REST/GraphQL, webhooks, object storage, and standard infrastructure over proprietary data formats.

That last point is especially important. The architecture you put around the commerce platform can create more lock-in than the platform itself.

My practical decision rule

If I were building a new system today with portability as a first-class requirement:

TypeScript/Node team → Medusa
Python/GraphQL team → Saleor
TypeScript/NestJS team with a strong plugin-oriented architecture → Vendure
Enterprise team that wants managed infrastructure and accepts proprietary SaaS → commercetools
Already deeply invested in Shopify → Shopify headless may be rational, but it isn't the maximum-portability choice.

I wouldn't choose based on feature-count comparisons. I'd prototype catalog → cart → checkout → order → fulfillment → refund → data export, then attempt to recreate the application against a second commerce backend. The platform where that exercise requires the least application-level rewriting is the one that is actually least coupled to your architecture.

Medusa → your PostgreSQL database → your infrastructure

without having to replace the underlying commerce engine. Medusa's MIT licensing is particularly attractive if you want maximum freedom to fork, modify, or operate the software independently. Current comparisons also put Medusa, Saleor, and Vendure in the strongest category for ownership/self-hosting. shipgarden.com owerczuk.dev

Saleor is the alternative I'd examine closely if you prefer Python/Django or deliberately want a GraphQL-first architecture. Its core is BSD-3-Clause licensed and it explicitly supports self-hosting. saleor.io

Vendure is another strong TypeScript option, particularly if its plugin architecture and commerce capabilities fit your application, but its GPLv3 licensing makes the legal implications different from Medusa's permissive MIT model.

The bigger issue: don't confuse "headless" with "portable"

For a small agency, I’d build around Shopify + Shopify Partner accounts, rather than trying to put all clients into one merchant account. Shopify’s Partner Dashboard is designed for agencies managing multiple client stores, and development stores are supported. Check Charm - the best things and places

A practical stack:

• Shopify Partner Dashboard — manage client stores and development builds.
• Shopify — each client owns their own merchant/payment account.
• Klaviyo — email/SMS when clients need it.
• Triple Whale — centralized analytics across stores. Check Charm - the best things and places
• Veeqo — worth considering if clients have multiple sales channels and need centralized orders/inventory/shipping. The Retail Exec
• Shopify Plus — only when a client genuinely needs organization-level multi-store management; Plus can centrally manage multiple expansion stores. Shopify

Important: don't pool unrelated clients' payment processing under your agency. Keep each merchant's Shopify Payments/Stripe/etc. account under the client's legal entity and give your agency delegated access.

For a high-volume dropshipping business with multiple warehouses, the “best” platform is usually not just a storefront. You typically need a stack that handles:

• Multi-warehouse inventory visibility
• Automated order routing (which warehouse/vendor fulfills)
• Supplier feeds and purchase orders
• Marketplace/store integrations
• Returns and tracking
• ERP/WMS connectivity
• High API throughput

The strongest options depend on your scale:

Shopify BigCommerce## My shortlist for a serious scaling operation

1. Shopify Plus + ERP/OMS — best for most fast-growing brands

Good when your priority is:

• High-converting storefronts
• Many SKUs
• DTC + wholesale
• Rapid scaling

Typical architecture:

Shopify Plus → OMS → ERP → Warehouses/3PLs → Suppliers

Add tools for:

• Inventory synchronization
• Automated fulfillment routing
• Supplier integrations
• Forecasting

Shopify supports enterprise integrations with ERP systems and can serve as the commerce layer while specialized systems handle inventory and operations. Shopify Shopify

2. Oracle NetSuite — best when operations become complex

Choose this if you have:

• Multiple warehouses
• Multiple legal entities
• International fulfillment
• Large supplier network
• Accounting and inventory complexity

NetSuite is often used as the operational “source of truth” because it combines ERP functions with inventory, order, and financial management. Shopify BigCommerce

3. BigCommerce + ERP — strong for complex catalogs

Good for:

• Large catalogs
• Multiple storefronts
• B2B + B2C combinations
• Headless commerce setups

BigCommerce emphasizes integrations with ERP systems for orders, inventory, and customer data flows. BigCommerce

For a high-volume dropshipping model, I would avoid:

• Running everything inside a basic Shopify/WooCommerce install with dozens of inventory apps
• Spreadsheet-based supplier syncing
• Treating the ecommerce platform as the inventory system
• Having separate inventory counts per warehouse without a central inventory layer

A scalable “best practice” architecture

Storefront:
Shopify Plus / BigCommerce

        ↓

Order Management System:
routing + split shipments + supplier rules

        ↓

ERP:
NetSuite / Dynamics / Acumatica

        ↓

Warehouses + 3PLs + Dropship Suppliers

BigCommerce ShopifyIf you are doing 10k+ orders/month, I would generally evaluate Shopify Plus + OMS + NetSuite (or similar ERP) rather than trying to make a single platform do everything. The right choice depends heavily on your monthly order volume, SKU count, number of suppliers, and whether warehouses are owned or 3PL.

For a subscription-focused dropshipping store, I’d build around Shopify rather than trying to make the supplier platform itself handle subscriptions.

Recommended setup

Shopify + subscription app + dropshipping/fulfillment supplier

• Storefront & orders: Shopify
• Recurring billing: Appstle, Recharge, or another Shopify subscription app
• Supplier/fulfillment: Zendrop, DSers, AutoDS, Spocket, or a direct supplier
• Automation: Have each subscription renewal create a normal Shopify order that gets passed to your fulfillment system.

Shopify currently has a large ecosystem of subscription apps. For example, Appstle supports subscriptions, subscription boxes and bundles, while Recharge supports recurring purchases and automatic order creation. Shopify App Store Shopify App Store

For suppliers, Shopify's own 2026 supplier guide lists options including Shopify Collective, Syncee, DropCommerce, DSers, CJDropshipping, Zendrop, AutoDS and Spocket. Shopify

The key issue with dropshipping subscriptions

The subscription software isn't actually the hardest part. Supplier synchronization is.

Suppose you sell a $39/month skincare subscription:

1. Customer subscribes on Shopify.
2. Subscription app charges them every 30 days.
3. A new Shopify order is generated.
4. Your fulfillment app sends the order to the supplier.
5. Supplier ships it and returns tracking.
6. Customer's subscription continues until they pause/cancel.

You want the supplier system to handle inventory changes, order submission, tracking, SKU mapping, and ideally automatic fulfillment rather than manually recreating every renewal.

What I'd choose

BigCommerce can certainly handle recurring commerce, and its SubscriptionFlow integration can automatically turn paid subscription renewals into BigCommerce orders. BigCommerce BigCommerce But for a new subscription-focused dropshipping operation, Shopify's combination of storefront, subscription apps, and supplier integrations is generally the simpler architecture.

If you're starting from scratch, my default stack would be Shopify + Appstle + a supplier with reliable US fulfillment. The important part is choosing a supplier whose inventory and fulfillment API/integration works reliably with recurring orders—not merely one that supports ordinary dropshipping.

If you tell me what type of product you want to sell (supplements, skincare, pet products, coffee, household consumables, etc.) and your target monthly price, I can narrow this down to a specific platform + supplier + subscription stack.

If your priority is mobile performance + a low-friction checkout for a dropshipping store, I’d put Shopify first, particularly if you want to launch quickly and spend your time on products/marketing rather than infrastructure.

How I’d compare them

Shopify: Its checkout is responsive/mobile-first, and Shop Pay can save returning customers from re-entering shipping and payment information. Shopify reports up to a 50% checkout-conversion improvement versus guest checkout for Shop Pay. Shopify Shopify

Shopify also gives you real-user Core Web Vitals reporting, so you can monitor mobile performance after installing your theme/apps. Shopify Help Center Shopify Help Center

BigCommerce: A strong alternative if you want more built-in flexibility. Its default checkout is one-page and responsive, with support for wallets such as Apple Pay and PayPal. BigCommerce BigCommerce

WooCommerce: It has made substantial recent performance improvements—WooCommerce reports a 19% faster checkout from its 2026 cart/checkout work, and further performance improvements landed in WooCommerce 11.0. WooCommerce WooCommerce But your actual mobile speed depends much more heavily on your WordPress hosting, theme, plugins, caching, and payment setup.

My recommendation for your use case

Shopify + a lightweight theme + minimal apps + Shop Pay/Apple Pay/Google Pay is the combination I'd investigate first.

The important caveat is that platform choice isn't the whole performance equation. Shopify itself notes that apps, third-party scripts, analytics, theme code, and image/video sizes can materially affect storefront performance. Shopify Help Center

For a dropshipping storefront, I'd specifically optimize for:

• LCP ≤ 2.5s
• INP ≤ 200ms
• CLS ≤ 0.1
• Very lightweight product pages
• WebP/AVIF product imagery
• Minimal tracking/upsell apps
• Express checkout visible early
• Guest checkout
• Apple Pay / Google Pay / Shop Pay
• Address autocomplete
• No intrusive popups on the first mobile visit

Those are Google's "good" Core Web Vitals thresholds, and Shopify exposes them in its performance reporting. Shopify Help Center

If you're deciding between Shopify, WooCommerce, BigCommerce, and a headless/custom stack specifically for a high-converting mobile dropshipping store, I can also break down expected speed, checkout friction, costs, app ecosystem, and scalability side-by-side.

BigCommerce: A strong alternative if you want more built-in flexibility. Its default checkout is one-page and responsive, with support for wallets such as Apple Pay and PayPal. bigcommerce.com bigcommerce.com

WooCommerce: It has made substantial recent performance improvements—WooCommerce reports a 19% faster checkout from its 2026 cart/checkout work, and further performance improvements landed in WooCommerce 11.0. woocommerce.com woocommerce.com But your actual mobile speed depends much more heavily on your WordPress hosting, theme, plugins, caching, and payment setup.

My recommendation for your use case

Shopify + a lightweight theme + minimal apps + Shop Pay/Apple Pay/Google Pay is the combination I'd investigate first.

For a fully customizable dropshipping store, I’d focus on headless open-source commerce rather than traditional store builders.

• Medusa — strongest fit if you want TypeScript/Node.js and maximum control over supplier APIs, fulfillment workflows, pricing, webhooks, and a custom Next.js storefront. OSSAlt Toolradar
• Saleor — excellent if you prefer Python/GraphQL and expect multi-channel, multi-currency, or more complex operations. OSSAlt
• Vendure — another strong TypeScript/Node option, particularly if you want a highly programmable commerce backend. OpenReplay Blog
• WooCommerce — easiest to launch and has a huge plugin ecosystem, but less architecturally clean for a deeply customized integration-heavy system. Toolradar

For your specific goal, I'd shortlist Medusa vs. Saleor. If you're building custom supplier/product-import APIs, automated order routing, inventory synchronization, and custom fulfillment logic, Medusa is particularly well suited. OSSAlt

If you tell me your tech stack and suppliers (AliExpress, CJ, Printful, private suppliers, etc.), I can map out the ideal architecture.

For a small ecommerce shop, the “best” subscription + dunning software usually depends on your platform (Shopify, WooCommerce, custom store), monthly subscription volume, and how much you need beyond charging cards. The biggest differentiator is often failed payment recovery (dunning) and subscriber self-service, not the recurring billing itself. ChurnTools

Here are the strongest options:

Shopify Shopify## My shortlist by shop size

If you have <500–1,000 subscribers

Start with:

• Appstle — likely the best balance of cost and capability for a small Shopify merchant. Shopify OneCart
• Shopify Subscriptions — if you only need basic “subscribe & save.” Shopify

If subscriptions are becoming a major revenue channel

Consider:

• Recharge — especially if you need many integrations (email, support, loyalty, analytics). Shopify
• Loop Subscriptions — if churn reduction and cancellation-save flows are a priority. ChurnTools

If you are not on Shopify

• Stripe Billing is often the cleanest foundation for a custom ecommerce stack. Shopify
• Chargebee is worth evaluating if you have multiple pricing models, plans, invoices, or B2B-style subscriptions. Shopify

Features I would prioritize for dunning

Make sure the tool supports:

• Automatic retry schedules after failed cards
• Email/SMS payment update reminders
• Customer self-service card updates
• Pause/skip options (to prevent cancellations)
• Cancellation surveys and save offers
• Subscription analytics (failed payment rate, churn, recovery rate)

A cheap subscription app that only retries payments may cost more in lost revenue than a slightly more expensive one with better recovery flows.

If you tell me:

1. your ecommerce platform (Shopify/WooCommerce/custom),
2. number of subscribers, and
3. whether you sell physical products, memberships, or digital goods,

I can narrow this to 2–3 choices.

Yes. There are tools that cover most of that workflow, although packing-list/kit management is usually the part that requires the most attention.

For a handmade-goods subscription business, I’d look at these:

• subbly.co — Built specifically around subscription businesses. It supports recurring billing, subscription schedules, inventory/order management, order lists, and batching orders into regular shipping cycles. Subbly Subbly
• sell.cratejoy.com — Particularly focused on subscription boxes. It provides subscription management, payment collection, fulfillment/shipping workflows, shipping exports, and integrations with fulfillment services. Cratejoy
• shopify.com + Recharge — A good approach if you already sell through Shopify. Shopify handles the store/orders while Recharge handles subscriptions, recurring billing, customer subscription management, etc. Shopify Shopify
• Shopify + Appstle — Another Shopify option, with subscription boxes and bundle functionality; Shopify's current app marketplace lists it among the subscription-box apps. Shopify App Store

For your specific workflow

If by "packing lists" you mean something like:

"For the September box, I have 47 subscribers. Pack 1 candle, 2 soaps, 1 thank-you card and 1 sample into each box, then generate the exact quantities I need."

That's an important distinction. Subscription billing software doesn't necessarily equal a proper kitting/packing system. Subbly, for example, can generate order lists and help batch fulfillment, but it doesn't physically fulfill the boxes itself. Subbly

A more sophisticated setup can connect a subscription platform to a fulfillment/inventory system that treats each monthly box as a kit/BOM (bill of materials). That's useful when you're making the products yourself and need to know exactly how many components to produce before the next shipment. Matrix Fulfillment

If you tell me what platform your handmade store currently uses (Shopify, Etsy, Squarespace, WooCommerce, etc.) and roughly how many subscription boxes you ship per month, I can narrow this down to the tools that can handle recurring payments + shipment cadence + automatic packing/component lists without building an unnecessarily complicated system.

For a SaaS founder adding physical product subscriptions, I’d usually avoid replacing your SaaS billing stack. The best choice depends on whether the physical product is a sidecar to the SaaS or becoming a DTC commerce business.

My default recommendation:

1. If physical products are an add-on to your SaaS: use Stripe + a commerce layer

Best fit: SaaS app + hardware, kits, consumables, onboarding boxes, replenishment products.

Stack:

• stripe.com for SaaS subscriptions and payments
• shopify.com (or a headless commerce layer) for physical inventory, fulfillment, shipping, returns
• Connect the customer identity between the two

Why:

• Your SaaS billing logic stays clean (plans, seats, usage, upgrades).
• Physical products get proper ecommerce workflows: SKUs, inventory, shipping, taxes, fulfillment.
• You avoid forcing a DTC subscription platform to handle SaaS concepts. Stripe Billing is designed for flexible subscription models, while ecommerce subscription tools tend to focus on physical-product workflows. SimpleSubscription Shopify

Example:

Customer pays $99/mo SaaS plan → adds a $20/mo refill kit → SaaS stays in Stripe, product subscription runs through Shopify.

2. If the physical subscription is becoming a major revenue stream: use Shopify + Recharge (or similar)

Best fit: coffee, supplements, skincare, pet products, consumables, subscription boxes.

Stack:

• shopify.com
• rechargepayments.com or another Shopify subscription app

Advantages:

• Better customer self-service: skip, pause, swap, change address.
• Better fulfillment ecosystem.
• Less engineering work. Shopify Swell

The tradeoff: you now have two customer systems (SaaS account + commerce account) unless you build a sync layer.

3. If you need one unified checkout experience

Consider a headless commerce approach:

• Frontend: your SaaS app
• Billing: Stripe
• Commerce: Shopify APIs or another commerce backend

This gives you:

• One login
• One checkout flow
• SaaS + physical product bundles

But it requires engineering investment.

My decision rule

One thing I’d avoid: putting your entire SaaS business into Shopify just because you’re adding a physical subscription. Shopify is excellent for commerce, but SaaS billing models (usage, seats, metered pricing, entitlements) usually fit better in a billing-native system. SimpleSubscription ToolStackChoice

If you tell me:

1. your SaaS stack (Stripe? Paddle? Chargebee? custom?),
2. the physical product (hardware/refill/box/etc.), and
3. whether customers should manage everything from one account,

I can suggest a more specific architecture.

One thing I’d avoid: putting your entire SaaS business into Shopify just because you’re adding a physical subscription. Shopify is excellent for commerce, but SaaS billing models (usage, seats, metered pricing, entitlements) usually fit better in a billing-native system.

If you tell me:

For a custom storefront with recurring subscription plans and API-first architecture, I’d narrow the field to a few strong options depending on whether you’re building SaaS, digital subscriptions, or physical recurring commerce.

My shortlist

SimpleSubscription Crystallize## My recommendation by scenario

1. You are building a SaaS-like subscription product

Pick: Stripe Billing + custom frontend

Architecture:

Next.js / React storefront
        |
Your API layer
        |
Stripe Billing
        |
Webhooks → database → entitlements/access control

Good for:

• monthly/annual plans
• usage-based pricing
• seat-based billing
• trials
• coupons
• customer portals
• metered billing

Stripe’s APIs are designed around subscriptions, invoices, payment methods, and lifecycle events, making it a common foundation for custom subscription products. SimpleSubscription

2. You are building a subscription ecommerce brand

Examples:

• coffee subscriptions
• supplements
• recurring boxes
• replenishment products

Pick: Swell, Recharge Headless, or Crystallize

You need more than billing:

• product catalog
• variants
• inventory
• bundles
• shipping cadence
• customer self-service
• subscription changes

A pure billing system often becomes painful here because you end up rebuilding commerce primitives. Crystallize

3. You need enterprise subscription operations

Pick: Chargebee

Better when you need:

• complex plans
• invoicing workflows
• finance integrations
• revenue recognition
• B2B contracts
• sales-assisted subscriptions

A stack I would build today

For a modern custom storefront:

SaaS / digital subscription stack

• Frontend: Next.js
• Commerce UI: custom React components
• Payments: Stripe Checkout or Elements
• Subscription engine: Stripe Billing
• Database: PostgreSQL
• Auth: Auth.js / Clerk / custom OAuth
• Events: Stripe webhooks → queue → backend services
• CMS: Sanity or Contentful

Physical subscription stack

• Frontend: Next.js
• Commerce backend: Swell or Crystallize
• Subscription engine: native subscriptions or Recharge Headless
• Payments: Stripe
• Fulfillment: custom integrations
• CMS/PIM: integrated headless commerce CMS

What I would avoid

• Building recurring billing from scratch unless subscriptions are your core product.
• Using a traditional monolithic ecommerce platform if your storefront UX is a major differentiator.
• Using only a payment API for physical subscriptions; you’ll eventually need catalog, fulfillment, and customer lifecycle tooling.

If you tell me what kind of subscription you’re selling (SaaS, memberships, digital content, or physical products) and your expected scale (e.g., 1k vs 100k subscribers), I can narrow this to a specific architecture.

If your key requirement is subscriptions + one-time purchases in the same cart/checkout, I’d narrow the field considerably.

Best options

My recommendation by use case

If you're on Shopify: I'd start with shopify.com + Appstle. Shopify's native infrastructure supports both one-time and subscription purchase options, and customers can manage both types of purchases through their account. Shopify Help Center Shopify App Store

If you're building a custom site/app: stripe.com + Stripe Checkout is the architecture I'd investigate first. It gives you much more control over how the cart, payment, subscription lifecycle, and customer experience work, but requires more engineering than Shopify.

If subscriptions are the core of the business: Recharge or Loop are worth evaluating alongside Shopify. The important distinction is that you're buying into a more sophisticated subscription-management layer rather than just adding recurring pricing to products.

One important caveat: "supports one-time purchases" isn't necessarily the same as "allows arbitrary one-time + recurring line items in one checkout." That's the capability I'd test in a demo. For example, your target flow should be:

Product A — $49 one-time
Product B — $19/month subscription
Product C — $12 one-time
Checkout → one payment → subscription created + one-time items fulfilled

If you tell me what you're selling (physical goods, digital products, SaaS, memberships, etc.) and whether you're already on Shopify, I can give you a much tighter 3-option comparison, including fees, checkout behavior, taxes, failed-payment handling, and customer portal capabilities.

Shopify supports multiple subscription cadences on the same product—e.g. customers can choose weekly, monthly, or quarterly options. Shopify’s subscription architecture supports separate selling plans with different billing/delivery intervals. Shopify Shopify

For more sophisticated subscription management, Appstle, Recharge, and Skio are also options on Shopify. Shopify help.skio.com

If you specifically need weekly + monthly + quarterly choices on one SKU, I can compare Shopify + Appstle vs Recharge vs Skio.

For a wholesale catalog with tiered pricing and customer-specific price lists, the “best” ecommerce platform depends mainly on how complex your pricing rules are, how many SKUs/customers you manage, and whether you need ERP integration. There is no single winner for every wholesale operation. RMG

Here are the strongest options:

My typical recommendations by scenario

1. You have a manufacturer/distributor catalog with thousands of SKUs

Choose:

• Adobe Commerce if you need:

• multiple customer price books
• negotiated contract pricing
• complex product configurations
• ERP-driven pricing
• multiple brands/storefronts

It is often used when ecommerce becomes an extension of a sophisticated sales operation rather than just an online ordering portal. Atwix

2. You have a wholesale business with customer tiers like:

• Dealer: 20% discount
• Distributor: 35% discount
• Strategic accounts: custom pricing

Choose:

• BigCommerce B2B or Shopify Plus B2B

Both can handle customer groups and differentiated catalogs without the complexity of a fully custom enterprise build. Shopify Wise

3. You also sell direct-to-consumer

Choose:

• Shopify Plus

A common setup is:

• consumer storefront → retail pricing
• wholesale portal → approved customers only
• customer login → assigned catalog and pricing

This avoids running separate retail and wholesale systems. Shopify

4. Your pricing comes from an ERP

Example:

• SAP customer pricing
• NetSuite price levels
• custom dealer agreements

Prioritize platforms with strong ERP integration:

• Adobe Commerce
• Sana Commerce Cloud
• BigCommerce
• Salesforce B2B Commerce

The ecommerce platform should usually display pricing from the system of record rather than forcing sales teams to maintain duplicate price lists. Shopify Netguru

Features I would require before choosing

For a serious wholesale catalog, look for:

• Customer-specific price lists
• Customer groups/accounts
• Quantity breaks (e.g., 1–99 units = $10, 100–499 = $8)
• Minimum order quantities
• Hidden wholesale-only products
• Approval workflows for new accounts
• Quick order / SKU entry
• Reorder lists
• Quote requests
• Multiple buyers per company account
• ERP/PIM integration
• Sales rep ordering tools

Short answer

• Most complex wholesale operations: Adobe Commerce
• Best balance of B2B capability and usability: BigCommerce B2B
• Best if you also run a consumer brand: Shopify Plus
• Most B2B-native: OroCommerce

If you tell me your number of SKUs, number of wholesale customers, ERP (if any), and whether you also sell retail, I can narrow this to 1–2 platforms.

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

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

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

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

My shortlist

What I'd look at first

1. BigCommerce B2B Edition — probably the closest match

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

bigcommerce.com

For example, you could have:

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

That is very close to the workflow you described.

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

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

shopify.com

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

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

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

One feature I'd consider non-negotiable

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

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

That's considerably more specific than ordinary wholesale ecommerce.

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

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

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

Strong fits

My first look would be at BigCommerce

BigCommerce specifically supports price lists at the SKU level, which can be assigned to customer groups or individual wholesale accounts. It also supports account-level payment options including POs, credit cards, and net terms. BigCommerce BigCommerce

For example, you could have:

• Customer A

• Product X → $85
• Product Y → $120
• Net 30
• Can buy physical + digital products
• Customer B

• Product X → $72
• Product Y → $110
• Net 60
• Different catalog
• Customer C

• Product X → $95
• Pay by card
• No access to Product Y

BigCommerce can also handle quotes, buyer accounts, approval workflows, and customer-specific catalogs. BigCommerce BigCommerce

Shopify is also worth considering

Shopify B2B supports catalogs assigned to particular companies/locations, customer-specific pricing, quantity rules, and payment terms such as Net 7 through Net 90. Shopify Shopify

The distinction I'd make is:

• Shopify → great if you also care heavily about consumer/DTC commerce, apps, storefront design, and ecosystem.
• BigCommerce → particularly attractive if B2B pricing, accounts, terms, catalogs and wholesale workflows are central.
• OroCommerce → worth looking at if you have very complicated customer contracts, price books, account hierarchies, ERP integration, etc. Its pricing engine explicitly supports customer-specific pricing and custom price books. ORO INC.
• Spree → interesting if you want an open-source foundation and expect to build a highly customized system. Spree Commerce

One important question: if by "digital products" you mean things like SaaS licenses, downloadable files, subscriptions, courses, API credits, or software licenses, rather than simply downloadable files, that changes which platform I'd recommend.

If you tell me what you're selling + roughly how many customers/products you expect + whether customers need invoices/net-30, I can narrow this down to 2–3 platforms and explain exactly how I'd structure the price books and payment terms.

For a distributor with a large SKU catalog and B2B buyers who want to type SKUs/quantities and place orders quickly, I’d put Adobe Commerce and Shopify Plus at the top of the shortlist.

Adobe Commerce

For your particular use case, Adobe Commerce is worth serious consideration. Its B2B functionality has a native Quick Order interface where buyers can enter multiple SKUs/product names, and they can also import multiple SKUs into the order form. Experience League Experience League

It also has requisition lists, essentially persistent saved order lists for frequently purchased products. Buyers can maintain up to 999 lists per account, configurable by the merchant. Experience League Experience League

That maps very naturally to distribution workflows:

Customer logs in → enters 20–100 SKUs/quantities → submits PO → sees their negotiated pricing → reuses the same list next month.

Adobe also supports company-specific catalogs/pricing and B2B workflows such as quotes and purchasing controls. Experience League Adobe Business

Shopify Plus

Shopify Plus is compelling if you want a more modern/easier-to-operate platform and don't have extremely complicated B2B rules.

Shopify's native B2B now supports company accounts, customer-specific catalogs, quantity rules, volume pricing, payment terms, and self-service purchasing. Plus removes the three-catalog limitation on lower plans and allows unlimited B2B catalogs plus direct assignment to companies/company locations. Shopify Help Center Shopify Help Center

It also has Quick Order Lists, allowing buyers to add multiple product variants to the cart from an order-oriented interface. Shopify specifically markets this as quick bulk ordering with a list of products and variants. Shopify Help Center Shopify

The important distinction is that Shopify's native B2B experience is somewhat more catalog/storefront-centric, whereas Adobe's B2B tooling is particularly well suited to the industrial distributor / customer portal / SKU-order-entry model.

How I'd decide

If you have something like:

• 50k–500k+ SKUs
• lots of customer-specific price lists
• customers who already know SKU numbers
• buyers ordering replenishment by the hundreds of lines
• multiple warehouses/UOMs/MOQs
• sales reps managing accounts
• ERP integration being central to the project

I'd investigate Adobe Commerce first.

If instead you have:

• a few thousand to tens of thousands of SKUs
• relatively straightforward pricing rules
• strong need for a polished storefront
• DTC + B2B on the same platform
• preference for simpler implementation/administration

I'd investigate Shopify Plus first.

One other important point: don't evaluate these platforms primarily on maximum SKU count. For a distributor, the harder scaling problem is usually the combination of SKU count × customer-specific pricing × inventory locations × search performance × ERP synchronization × large order-line counts.

If you tell me roughly how many SKUs you have, number of B2B customers, ERP (e.g. NetSuite, SAP, Epicor, Dynamics), and typical order size (e.g. 20 vs. 500 lines), I can give you a much more specific Adobe vs. Shopify Plus vs. BigCommerce comparison.

Shopify Plus

Shopify Plus is compelling if you want a more modern/easier-to-operate platform and don't have extremely complicated B2B rules.

Shopify's native B2B now supports company accounts, customer-specific catalogs, quantity rules, volume pricing, payment terms, and self-service purchasing. Plus removes the three-catalog limitation on lower plans and allows unlimited B2B catalogs plus direct assignment to companies/company locations. help.shopify.com help.shopify.com

It also has Quick Order Lists, allowing buyers to add multiple product variants to the cart from an order-oriented interface. Shopify specifically markets this as quick bulk ordering with a list of products and variants. help.shopify.com shopify.com

The important distinction is that Shopify's native B2B experience is somewhat more catalog/storefront-centric, whereas Adobe's B2B tooling is particularly well suited to the industrial distributor / customer portal / SKU-order-entry model.

How I'd decide

If you have something like:

For a beginner selling prints (especially if you have no design or coding skills), the best balance is usually a simple design tool + easy ecommerce platform, rather than an all-in-one “do everything” app.

My shortlist:

Ecommerce-Platforms.com Bootstrapping Ecommerce## My recommendation for your situation

Start with: Canva + Etsy + Printify/Printful

Workflow:

1. Create designs in Canva
2. Upload products through Printify or Printful
3. Sell through Etsy
4. Let the print provider handle production and shipping

This avoids:

• learning web development
• buying inventory
• managing fulfilment
• building a website before you know what sells

Printful and Printify both support integrations with marketplaces and ecommerce platforms, making them common beginner choices for print-on-demand sellers. Printful

If you want the easiest “everything in one place”

Choose Wix.

Why:

• drag-and-drop store builder
• lots of templates
• no coding
• good for a small catalogue
• easier than Shopify for a complete beginner

Ecommerce-Platforms.com## If your goal is to grow into a real brand

Choose Shopify later.

It is more powerful for:

• email marketing
• customer accounts
• upsells
• larger product ranges
• owning your customer relationship

But it has more setup decisions, so I wouldn’t make it your first step unless you already know you want a full ecommerce business. Bootstrapping Ecommerce

For selling prints specifically, I’d rank them:

1. 🥇 Canva + Etsy + Printify — easiest beginner route
2. 🥈 Canva + Etsy + Printful — slightly more premium/quality-focused
3. 🥉 Wix + Printify/Printful — best if you want your own website immediately
4. Shopify + POD app — best once sales are proven

One thing to watch: Canva templates are a great starting point, but many sellers use the same templates, so adding your own style, niche, and original elements matters if you want your prints to stand out.

If you mean wall art prints/posters specifically (rather than t-shirts, mugs, etc.), the best setup changes slightly.

For a boutique selling made-to-order products with long production times, I’d look primarily at Shopify, WooCommerce, and BigCommerce. The key distinction is whether you need a true pre-order workflow or simply want to let customers order while an item is being produced.

My practical take

Shopify — probably the easiest fit

Shopify is particularly strong if you want the customer experience to be polished without building much yourself. Its App Store has a substantial ecosystem specifically for pre-orders, backorders, and made-to-order products. Current Shopify listings include apps supporting made-to-order products, backorders, restock notifications, deposits, and partial payments. Shopify App Store Shopify App Store

For example, you can have a product say:

Made to order — ships in 6–8 weeks
Order today to reserve yours.
$150 deposit due today; balance charged when production begins.

That sort of workflow is much closer to what a boutique with long production times needs than simply marking inventory as "out of stock."

apps.shopify.com

WooCommerce — best if you want maximum control

WooCommerce is particularly flexible. Its official pre-order extension supports setting an availability date and either charging customers immediately or when the item becomes available. WooCommerce WooCommerce

There's also an official extension specifically covering both pre-orders and backorders, with configurable payment options, order rules, and notifications. WooCommerce

I'd consider WooCommerce if your production process is unusual—for example, different lead times based on fabric, personalization, size, or production batch—and you're comfortable with a little more technical administration.

One important distinction for your business

If your products are always made after the customer orders, I wouldn't necessarily structure them as conventional "pre-orders."

I'd look for a platform/app combination that supports:

• Made-to-order status rather than "out of stock"
• A visible production/ship timeframe
• Orders accepted without inventory being available
• Deposits or partial payments, if appropriate
• Automatic customer emails when production starts/completes
• Ability to update an estimated ship date
• Handling of delays without accidentally triggering refunds/cancellations
• Backorders when production capacity is temporarily full
• Separate fulfillment dates for different products/variants

For a boutique, I'd lean Shopify if you want simplicity; WooCommerce if your ordering/production logic is unusually complex. The platform itself is only half the decision—the particular pre-order/made-to-order app can make a very large difference.

If you tell me (1) your typical production time, (2) whether you take full payment or a deposit, (3) whether every item is made-to-order or only some, and (4) your approximate monthly order volume, I can narrow this down to the specific setup I'd use.

For example, you can have a product say:

Made to order — ships in 6–8 weeks
Order today to reserve yours.
$150 deposit due today; balance charged when production begins.

That sort of workflow is much closer to what a boutique with long production times needs than simply marking inventory as "out of stock."

apps.shopify.com

WooCommerce — best if you want maximum control

WooCommerce is particularly flexible. Its official pre-order extension supports setting an availability date and either charging customers immediately or when the item becomes available. woocommerce.com woocommerce.com

There's also an official extension specifically covering both pre-orders and backorders, with configurable payment options, order rules, and notifications.

I'd consider WooCommerce if your production process is unusual—for example, different lead times based on fabric, personalization, size, or production batch—and you're comfortable with a little more technical administration.

One important distinction for your business

For a privacy-first ecommerce business, I’d narrow the field to Wix, Shopify, and Webflow, with different trade-offs:

• Wix — simplest privacy setup. Its Privacy Center provides a cookie-consent banner, consent logs, controls for third-party data sharing, and tools for handling visitor data-access/deletion requests. Wix also supports ecommerce checkout consent mechanisms. wix.com Wix Support Center Wix Support Center

Best fit: a small business that wants ecommerce + privacy controls without much technical work.

• Shopify — strongest ecommerce/privacy integration. Shopify has built-in customer-privacy settings, regional cookie-banner controls, opt-out mechanisms, data-access/deletion tooling, and a Customer Privacy API that can propagate consent choices to Shopify's own systems. Shopify Help Center Shopify Help Center

Best fit: a serious online store where ecommerce functionality is the priority. Be aware that Shopify explicitly says using Shopify alone doesn't automatically make your business GDPR compliant—you remain responsible for your processing practices and third-party apps. Shopify Help Center

• Webflow — strongest design/control, more privacy work. Webflow supports full ecommerce, but its native platform doesn't provide a complete consent-management layer. You'll generally need a CMP or custom implementation to handle consent logging and prevent analytics/marketing scripts from firing before consent. Webflow Help Center Webflow

Best fit: a privacy-conscious brand with a designer/developer who wants greater control over the site.

A practical privacy-first stack

If your priority is "make GDPR handling as painless as possible", I'd look at:

Wix + its built-in Privacy Center → least additional infrastructure.

Shopify + its native privacy controls + a properly integrated CMP if you use lots of third-party marketing apps → particularly appropriate for a larger store.

Webflow + a dedicated CMP → good when design flexibility matters more and you're comfortable managing the technical privacy layer.

One important distinction: a cookie banner isn't the same thing as GDPR compliance. You also need to consider your lawful bases, privacy notice, processor/DPA arrangements, retention, international transfers, data-subject requests, and every third-party app that receives customer data. Wix and Shopify both explicitly put responsibility for the site's overall compliance on the site owner/merchant. Wix Support Center Shopify Help Center

If you tell me your store size, whether you sell to EU customers, and which tools you need (Stripe, Klaviyo, Google Analytics, Meta Ads, etc.), I can make a concrete privacy-stack comparison including approximate costs and how much configuration each requires.

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

My pick: Fourthwall

fourthwall.com is particularly well suited to what you described:

• $0/month and $0 upfront — you don't have to pay for a Shopify-style subscription before you've made sales. Fourthwall Fourthwall
• Print-on-demand — you don't buy shirts or stickers in advance. They manufacture and ship after someone orders. Fourthwall
• Stickers and shirts are both supported. Current listed examples include stickers from about $2.29 and T-shirts from about $9.50, before your markup and applicable costs. Fourthwall
• You get an actual customizable storefront, rather than merely listing products on a marketplace. Fourthwall
• For physical products, Fourthwall says its platform fee is 0%, though payment processing still applies. Fourthwall

That makes it a good way to test whether your audience actually buys merch without risking a pile of inventory or a monthly store bill.

Two alternatives worth knowing

Printful has a free plan and its Quick Stores are completely free, with Printful charging you for fulfillment after a customer orders. Printful Printful Help Center

printful.com

Printify also has a $0/month plan and a large catalog, but it becomes more useful when you want to compare different print providers or connect to another storefront such as Etsy, Shopify, or Wix. Printify Printify

printify.com

What I'd do in your situation

Start with Fourthwall + 3–5 products, rather than building a huge catalog. For example:

• 2–3 sticker designs
• 1–2 shirts using your strongest design
• Free Fourthwall storefront
• Promote the shop through your existing social channels
• Don't buy inventory until you know which designs sell

You can always move to Shopify/Printify or another setup later if your sales justify the extra complexity and monthly costs.

If you tell me roughly how many followers you have and whether your audience is mainly on TikTok, Instagram, YouTube, or somewhere else, I can also compare Fourthwall vs Etsy vs Shopify vs Printify specifically for your situation, including the fees you'd actually encounter.

Printify also has a $0/month plan and a large catalog, but it becomes more useful when you want to compare different print providers or connect to another storefront such as Etsy, Shopify, or Wix. Printify Printify

printify.com

What I'd do in your situation

Start with Fourthwall + 3–5 products, rather than building a huge catalog. For example:

• 2–3 sticker designs
• 1–2 shirts using your strongest design
• Free Fourthwall storefront
• Promote the shop through your existing social channels
• Don't buy inventory until you know which designs sell

You can always move to Shopify/Printify or another setup later if your sales justify the extra complexity and monthly costs.

If you tell me roughly how many followers you have and whether your audience is mainly on TikTok, Instagram, YouTube, or somewhere else, I can also compare Fourthwall vs Etsy vs Shopify vs Printify specifically for your situation, including the fees you'd actually encounter.

For a streamer selling lots of limited-edition drops, I’d use Shopify.

Why it fits your requirements:

• Scarcity: You can set finite inventory and prevent sales when stock runs out. Shopify also has tooling specifically for flash sales and high-demand drops. help.shopify.com
• Variants: Each product can have variants such as size, color, or edition, with inventory tracked separately. Shopify currently supports up to 2,048 variants per product in its standard product model. help.shopify.comhelp.shopify.comhelp.shopify.com
• Fast checkout: Shopify Checkout handles payment and inventory checks, and Shopify supports accelerated checkout options. help.shopify.com
• Drop protection: You can impose per-product quantity limits, useful when you want to prevent one buyer from clearing out a limited drop. help.shopify.com
• Streamer-friendly: You can link directly from your stream/social profiles to specific products or variants, rather than forcing viewers through a marketplace.

My practical setup: Shopify store + a dedicated "Drops" collection + each drop as a product with variants for size/color/edition + strict inventory quantities + purchase limits + an accelerated checkout option.

If you're expecting thousands of viewers hitting "buy" simultaneously, Shopify is particularly worth considering because it has dedicated guidance and infrastructure for flash-sale traffic. help.shopify.com

Shopify

If your goal is selling directly from Instagram/TikTok posts and livestreams, I’d look at the ecommerce platform first rather than choosing a standalone livestream tool.

The main options

Shopify is probably the simplest starting point if social commerce is central to your business. Its official channels can sync your catalog with Facebook/Instagram and TikTok, while TikTok supports both shoppable videos and LIVE shopping. Shopify Help Center Shopify Help Center

For Instagram, Shopify lets you tag products in posts and Stories, with customers ultimately completing checkout through your Shopify store. Shopify Help Center

Shopify also has a large ecosystem of livestream/shoppable-video apps, including tools specifically designed to turn Instagram Reels and TikToks into shoppable content. Shopify App Store Shopify App Store

What I'd build

Shopify → product catalog/inventory → Instagram + TikTok + YouTube

Then:

• Instagram: shoppable posts, Stories, Reels and live content
• TikTok: TikTok Shop, shoppable videos and LIVE shopping
• YouTube: product tagging and shopping integrations
• Shopify: central inventory, orders, fulfillment, customers and analytics

This is particularly useful if you want a customer to see a product in a creator post or livestream, tap the product, and buy without having to manually search your website. Shopify Help Center

BigCommerce is worth considering if you already have a more complex omnichannel operation; it emphasizes centralized catalog/inventory management across social channels and marketplaces. BigCommerce

If you tell me what you're selling, your approximate monthly sales, and whether Instagram or TikTok is your main audience, I can compare Shopify vs BigCommerce vs a dedicated live-shopping platform specifically for your setup.

For an ecommerce store where discount codes + affiliate links + influencer promo tracking are core requirements, I’d usually narrow it to these choices:

Shopify Influencer Marketing Blog by HypeAuditor## My default recommendation

Pick: Shopify + Shopify Collabs (start here)

For most ecommerce brands, this is the cleanest starting point:

• Create unique influencer discount codes (e.g., JANE15)
• Generate affiliate links
• Track creator-driven sales
• Manage commissions
• Recruit creators through the Shopify ecosystem

Shopify Collabs supports creator partnerships, affiliate links, discount codes, and performance tracking inside the Shopify workflow. Shopify

Add a dedicated affiliate tool later if you outgrow it.

When to upgrade beyond Shopify Collabs

Choose a more advanced influencer platform if you need:

1. Dozens/hundreds of creators

Use:

• GRIN — stronger for DTC brands managing ongoing influencer relationships, product seeding, and creator workflows. ConversionStudio
• Upfluence — combines creator discovery, ecommerce integrations, promo codes, affiliate links, and sales tracking. Influencer Marketing Blog by HypeAuditor Upfluence

2. A true affiliate program

Use:

• Refersion
• Everflow
• Tapfiliate

These are better if you have many affiliates, different commission rules, publishers, coupon partners, or agencies managing campaigns. Shopify

My shortlist by business stage

New brand (<50 creators, testing influencer marketing)

Shopify + Shopify Collabs

Growing DTC brand (50–500 creators)

Shopify + GRIN or Upfluence

Affiliate-heavy business (blogs, deal sites, ambassadors)

Shopify + Refersion/Everflow

Custom business with developers

WooCommerce + AffiliateWP/custom integrations

A few questions would change the recommendation:

1. Are you selling physical products, digital products, or subscriptions?
2. Roughly how many influencers/affiliates do you expect (10, 100, 1,000+)?
3. Are you already on Shopify, WooCommerce, Amazon, or starting from scratch?

Growing DTC brand (50–500 creators)

Shopify + GRIN or Upfluence

Affiliate-heavy business (blogs, deal sites, ambassadors)

Shopify + Refersion/Everflow

Custom business with developers

WooCommerce + AffiliateWP/custom integrations

A few questions would change the recommendation:

1. Are you selling physical products, digital products, or subscriptions?
2. Roughly how many influencers/affiliates do you expect (10, 100, 1,000+)?
3. Are you already on Shopify, WooCommerce, Amazon, or starting from scratch?

For a large omnichannel retailer where promotion logic is genuinely complex and must stay consistent across countries/channels, I’d evaluate the platforms less as “e-commerce engines” and more as pricing/promotion decision engines.

SAP Omnichannel Promotion Pricing

For the particular requirement you described, SAP Omnichannel Promotion Pricing (OPP) is worth putting at the top of the shortlist for evaluation—not because it's universally better, but because its architecture directly addresses the problem.

SAP positions OPP as a centralized service for calculating promotional prices across sales channels, with a common repository for prices/promotions and a calculation service that applies promotional rules. It explicitly supports retail scenarios such as mix-and-match promotions, transaction-level rewards, coupons, and complex promotion rules. SAP SAP Help Portal

It can also integrate with SAP Commerce Cloud and SAP S/4HANA, and SAP documents using the same calculation logic across web, POS, and sales-order channels. SAP Help Portal SAP Help Portal

That makes it particularly interesting if your requirements look like:

• “Buy A + B, get C 50% off”
• Spend thresholds combined with SKU/category conditions
• Customer-segment-specific promotions
• Country/currency/channel-specific pricing
• Coupons and promotion stacking
• Different rules by market while maintaining a common pricing model
• Identical promotional outcomes in store, web, app, and order-management flows

Where commercetools differs

commercetools is compelling if your organization wants a more composable architecture. Its discount model supports product and cart discounts, predicates, ranking, stacking controls, discount codes, and price dimensions such as country, customer group, channel, currency, and validity period. Commercetools Documentation Commercetools Documentation Commercetools Documentation

The architectural trade-off is important: you may get substantial flexibility, but you'll generally be assembling more of the overall retail pricing ecosystem yourself rather than buying a retail-specific promotion-pricing capability.

Salesforce

Salesforce Commerce provides separate pricing and promotion APIs for product and cart evaluation. Its promotion evaluation can consider store, buyer group, coupons, cart contents, and promotion priority. Developer

I'd investigate it particularly where Salesforce CRM/loyalty/customer data is central to promotion eligibility.

The key product-management question

Rather than asking “Which platform has the most promotion features?”, I'd run vendors through a common rule corpus. For example:

Market: US / UK / Germany
Channel: store / web / app
Customer: loyalty tier + geography
Basket: 2 × category A + 1 × category B
Promotion: cheapest B 50% off
Additional: $10 off over $100, but not combinable with promotion X
Pricing: market-specific base price + currency + VAT/tax treatment
Constraints: inventory/channel restrictions and coupon eligibility

Then measure each platform on rule expressiveness, conflict resolution/stacking, explainability, latency, authoring experience, market localization, versioning, simulation, and operational governance.

For a large retailer, those last few—particularly promotion conflict resolution, simulation, auditability, and consistent execution across POS and digital—can matter more than the raw number of promotion types supported.

For a global ecommerce brand where localization means more than simply translating product copy, I’d put Shopify at the top of the shortlist today—particularly for a brand that wants one commerce platform with market-specific language, domains, currencies, pricing, products, and content.

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

Why Shopify stands out

Shopify's Markets architecture treats localization as a market-level problem rather than just a language problem. You can configure language, currency, pricing, product availability, domains, taxes and theme/content customizations for different markets. Shopify Help Center Shopify Help Center

For example, the same brand could have:

• US → English / USD
• France → French / EUR
• Canada → English + French / CAD
• Japan → Japanese / JPY
• Germany → German / EUR

And those markets can have different domains, subdomains, or URL structures. Shopify also automatically generates appropriate hreflang signals for configured market/language combinations, which is valuable for international SEO. Shopify Help Center Shopify Help Center Shopify Help Center

The particularly useful distinction is between translation and adaptation. Shopify allows you to create market-specific content rather than merely translating English literally—for example, changing promotional messaging, product descriptions or legal information for a particular region. Shopify Help Center Shopify Help Center

Shopify currently supports up to 20 languages on standard plans and up to 30 on Shopify Plus/Enterprise Commerce, with translated storefront and checkout experiences. Shopify Help Center

Where Adobe Commerce can be stronger

If by "strongest localization" you mean maximum control over highly complex regional storefronts, I'd seriously consider Adobe Commerce.

It has deep localization infrastructure, including language packs, translation dictionaries, locale-specific configurations, and the ability to translate product names, descriptions, categories and metadata separately for different store views. Experience League Experience League

The trade-off is complexity: Adobe Commerce gives an enterprise team substantially more control, but requires considerably more technical/operational investment than Shopify.

BigCommerce is worth watching

BigCommerce has recently strengthened this area substantially. Its current multi-language storefront functionality supports multiple languages from a single storefront, with localized URLs and translation of shopper-facing content including products, SEO, categories, brands and navigation. BigCommerce

Its newer localization settings also bring country, storefront language, dimensions, date and timezone configuration into one place. BigCommerce

So if you're evaluating platforms today, I wouldn't dismiss BigCommerce based on its older localization capabilities.

My practical recommendation

I'd frame it this way:

• Best overall global localization experience: Shopify
• Best for extremely complex enterprise localization: Adobe Commerce
• Best flexible alternative: BigCommerce
• Best if WordPress is already central to the business: WooCommerce

One important caveat: translation quality and localization capability aren't exactly the same thing. If your requirement is sophisticated linguistic localization—brand terminology, translation memory, human review, cultural adaptation, automated workflows across hundreds of thousands of SKUs—you may want to pair the ecommerce platform with a dedicated translation/localization system such as a TMS rather than relying entirely on the ecommerce platform's native translation functionality.

If you tell me your number of markets/languages, approximate SKU count, and whether you're B2C or B2B, I can give you a much more useful Shopify vs. Adobe Commerce vs. BigCommerce localization architecture comparison.

It has deep localization infrastructure, including language packs, translation dictionaries, locale-specific configurations, and the ability to translate product names, descriptions, categories and metadata separately for different store views. experienceleague.adobe.com experienceleague.adobe.com

The trade-off is complexity: Adobe Commerce gives an enterprise team substantially more control, but requires considerably more technical/operational investment than Shopify.

BigCommerce is worth watching

BigCommerce has recently strengthened this area substantially. Its current multi-language storefront functionality supports multiple languages from a single storefront, with localized URLs and translation of shopper-facing content including products, SEO, categories, brands and navigation.

Its newer localization settings also bring country, storefront language, dimensions, date and timezone configuration into one place.