Answers that do not mention BigCommerce

For a small handmade-goods shop and no coding experience, I’d look first at Shopify, Wix, and Squarespace.

My practical recommendation

Shopify is a strong default if your primary goal is selling products, rather than simply building a website. It includes hosting, payment processing, inventory/order tools, customizable themes, and an app ecosystem, and its store builder doesn't require coding. Shopify Shopify

If you have a small catalog—say 5–30 handmade products—and want something especially straightforward, Wix is worth considering. Its drag-and-drop editor is designed for non-technical users and includes ecommerce functionality on its paid plans. Shopify

If photography and the visual presentation of your handmade work are especially important, Squarespace is another natural fit; it emphasizes polished templates and straightforward visual editing. Shopify

One other option: Big Cartel is specifically aimed at artists and makers and can be simpler than a full Shopify setup, particularly if you have a small inventory. Shopify

If you tell me roughly how many products you sell and your monthly budget (e.g. under $20, $20–50, or $50+), I can narrow this down to the most suitable option and explain exactly what you'd pay.

If flexibility + API quality are your top criteria, I’d shortlist Medusa, Saleor, commercetools, and Shopify. They make different tradeoffs.

My take

For a developer building a genuinely custom frontend, I'd look hardest at Medusa and Saleor.

• Medusa is particularly attractive if you want the backend itself to be customizable. Its storefront is completely separate from the commerce application, and its Store API is REST-based; you can also add custom API routes/modules. Medusa Docs Medusa Docs Medusa Docs
• Saleor is compelling if you prefer GraphQL everywhere. Its core API is GraphQL, and its architecture emphasizes headless storefronts, channels, checkout, extensions, and custom admin apps. Saleor Documentation Saleor Commerce
• commercetools is probably the strongest choice when you're building a larger composable/enterprise system. It exposes both HTTP and GraphQL APIs and is designed around composing commerce capabilities with other systems. commercetools Documentation commercetools Documentation
• Shopify gives you considerably more out-of-the-box commerce infrastructure. Its Storefront API is GraphQL and supports custom web, mobile, game, and other experiences, while the Admin API handles backend management. Shopify Shopify

If I were choosing based specifically on frontend freedom

I'd think about it this way:

Maximum control → Medusa

You can treat commerce as your backend and build essentially whatever frontend/BFF architecture you want. This is especially attractive if you're comfortable owning infrastructure and commerce logic. Medusa Docs

Best GraphQL-native experience → Saleor

If your frontend is heavily typed and you want clients to request exactly the data they need, Saleor's GraphQL-first approach is very appealing. Saleor Documentation Postman

Enterprise composability → commercetools

If the frontend is only one component of a larger architecture involving ERP/PIM/CMS/search/payments/etc., commercetools is worth serious consideration. commercetools Documentation

Least backend work → Shopify

You sacrifice some backend-level freedom, but you get a mature commerce engine while retaining control over the frontend. Shopify explicitly supports bringing your own stack and using its Storefront API for custom experiences. Shopify Shopify

One important distinction

"Headless" doesn't necessarily mean fully customizable commerce logic.

For example, Shopify is excellent if your architecture is:

Custom React / Next.js frontend
            ↓
       Shopify APIs
            ↓
Products / Cart / Checkout / Orders

Whereas Medusa is more like:

Custom frontend
       ↓
Your BFF / API layer
       ↓
   Medusa backend
       ↓
Custom commerce modules
       ↓
Payments / fulfillment / ERP / etc.

That second model gives you substantially more control over how commerce works, not merely how it is rendered.

So if your phrase "flexibility and APIs" means I want to build unusual commerce behavior and don't want the platform fighting me, I'd start with Medusa and Saleor. If you tell me your stack (e.g. Next.js + TypeScript + Postgres, B2B/B2C, subscriptions, multi-vendor, etc.), I can narrow this down to the architecture I'd use.

For a brick-and-mortar + online business, the right choice depends heavily on where your online store lives and how complex your inventory is. The main platforms I’d put on your shortlist are:

The practical choice

If your website is already on Shopify: I'd generally look at Shopify POS first. Shopify directly connects POS with its admin, so in-store sales update inventory alongside online sales, and it supports separate inventory by location. Shopify Help Center Shopify Help Center

shopify.com

If you're primarily a physical retailer and want a relatively straightforward all-in-one setup: Square for Retail is worth serious consideration. Its inventory system handles multiple locations, transfers, purchase orders, online orders, and in-store sales. Square Square

squareup.com

If you have significant operational complexity—multiple warehouses, marketplaces, wholesale, lots of SKUs, complicated purchasing/fulfillment—I'd investigate Cin7 or Lightspeed rather than relying solely on a basic POS inventory system. Cin7 specifically positions its system around synchronizing inventory across multiple sales channels. Cin7

The biggest thing I'd avoid is having one inventory system for the store and another for e-commerce that merely exchanges periodic updates. You want a genuine inventory source of truth with real-time quantity changes, location-level stock, transfers, returns, reservations, and ideally purchase orders.

If you tell me (1) what your online platform is (Shopify/WooCommerce/etc.), (2) what POS you use today, (3) number of stores/warehouses, and (4) roughly how many SKUs, I can narrow this to the 2–3 platforms that fit your operation and explain the tradeoffs.

If your priorities are self-hosting + full source-code access + deep customization, I’d narrow it to Medusa, Vendure, Saleor, and WooCommerce.

My recommendation: Medusa

medusajs.com is probably the best fit if you’re comfortable developing the store yourself. It’s a developer-oriented commerce engine with an MIT-licensed core, and its architecture is designed around customizing commerce logic rather than fighting a prebuilt storefront. GitHub OSSAlt

A typical stack would be:

• Medusa — products, carts, orders, customers, payments, promotions, etc.
• Next.js/React — completely custom storefront
• PostgreSQL — database
• Redis — caching/background jobs where appropriate
• Docker — deployment
• Your own VPS/cloud — hosting

That gives you essentially complete control over the UI and backend behavior.

The alternatives

vendure.io is particularly interesting if you want TypeScript but expect complicated business rules, B2B, marketplaces, multiple channels, or custom workflows. Its plugin architecture lets you extend or override core behavior without modifying the core itself, and it can be self-hosted. GitHub Vendure

saleor.io is another excellent choice if you like GraphQL and a headless architecture. It explicitly supports self-hosting and provides an open-source commerce engine, dashboard, APIs, and extensibility mechanisms. Saleor Commerce

woocommerce.com makes more sense if you want a ready-to-run traditional website rather than building a commerce application. Its enormous WordPress ecosystem means you can get a store running much faster, but the architecture is less clean if your goal is to build something radically custom. Open Source Groups

What I'd choose

If you told me:

"I want to own the server, own the code, change basically anything, and I'm willing to code."

I'd start with Medusa + Next.js + PostgreSQL + Docker.

If you told me:

"I want maximum customization but expect complicated B2B/marketplace/business workflows."

I'd seriously consider Vendure.

If you told me:

"I want something I can install, configure, add plugins to, and have a conventional ecommerce site without building the whole frontend."

I'd choose WooCommerce.

One important distinction: "open source" doesn't necessarily mean every commercial/enterprise feature of a project is open source, so check the current license and edition boundaries before committing. For example, Vendure's core is GPLv3, while its commercial Platform adds additional capabilities. Vendure

If you tell me what you're selling, approximate number of products, whether you need subscriptions/B2B/marketplace, and your preferred programming language, I can narrow this down to one and give you the exact self-hosted architecture I'd use.

If your priority is “I’m a solo entrepreneur and I never want to manage servers,” I’d narrow it to Shopify vs. Wix.

My pick: Shopify

For a custom T-shirt business, Shopify is probably the better long-term fit if you expect the store to become a serious sales channel.

• No server management: Shopify handles hosting, security, updates, and infrastructure.
• Excellent POD ecosystem: Shopify currently has a large selection of print-on-demand apps, including Printful, Printify, Apliiq, and product-personalizer tools. Shopify App Store Shopify App Store
• Easy fulfillment: POD suppliers can print and ship directly to your customer, so you don't need inventory or a fulfillment operation. Shopify App Store
• Better room to grow: If you later add multiple products, subscriptions, advertising channels, wholesale, or more sophisticated marketing, Shopify is built around ecommerce rather than primarily being a website builder.

shopify.com

When I'd choose Wix instead

Choose Wix if your business is more about your brand/design and a relatively simple catalog than building a sophisticated ecommerce operation.

Wix has built-in ecommerce hosting and supports POD directly; its current POD workflow can connect to Printful, with orders automatically sent for fulfillment. wix.com Wix Support

wix.com

Quick comparison

For your specific situation, I'd start with Shopify + Printful or Printify. That gives you a hosted storefront while the POD company handles printing and shipping—leaving you primarily responsible for designs, marketing, customer service, and growing the brand.

If you tell me roughly how many T-shirt designs you expect to sell and whether customers will customize the shirts themselves, I can also lay out the simplest/cheapest stack for you.

For a small maker business selling both at markets/in person and online, I’d narrow it to Square vs. Shopify.

My practical recommendation

Pick Square if: your business is primarily handmade goods sold at craft fairs, pop-ups, markets, and occasionally online. Square's free plan has no monthly subscription cost, and its POS, online store, catalog, inventory, shipping, and pickup can operate in one system. Square Square

Pick Shopify if: you expect your online store to become a major part of the business—lots of products, collections, online marketing, social selling, or eventually a substantial ecommerce operation. Shopify is particularly focused on connecting ecommerce and in-person POS, though its paid plans start higher. Shopify Shopify

If you told me "I just want something simple that works," I'd start with Square. You can start with its free plan and add hardware later; Square also supports Tap to Pay on iPhone/Android, so you don't necessarily need a dedicated POS terminal at first. Square Square

If you tell me what you make, roughly how many products/SKUs you have, and whether most sales are expected online or at markets, I can give you a more specific Square-vs-Shopify recommendation.

If you’re a small artisan selling a mix of ready-to-ship products, pre-orders, and made-to-order/custom pieces, I’d look first at Shopify.

How the main options compare

• Shopify — strongest fit for your workflow. Shopify has a large ecosystem of pre-order apps specifically supporting made-to-order products, and some can let you specify lead times, availability dates, or future delivery dates. Shopify App Store Shopify App Store

shopify.com

• Big Cartel — simpler artisan-focused option. It’s designed around independent artists and creators and is comparatively straightforward for ordinary products. However, its native product/order functionality is less sophisticated for complex pre-order and lead-time workflows, so you may need workarounds or integrations. Big Cartel Big Cartel

bigcartel.com

• Squarespace — attractive if your priority is the website/brand presentation. It can work well for a relatively simple catalog, but I’d put it behind Shopify if variable production times and pre-orders are central to how you sell.

What I'd look for in your case

You probably want each product to be able to say something like:

Ready to ship: 1–3 business days
Made to order: Ships in 2–3 weeks
Pre-order: Ships approximately November 15

And ideally the store should automatically communicate that information at the product page and checkout rather than you having to manually explain it to every customer.

Shopify can accommodate that particularly well through its pre-order/made-to-order app ecosystem. Shopify App Store Shopify App Store

If you tell me roughly how many products you have, your typical custom lead time (e.g. 1–2 weeks), and your monthly budget, I can narrow this down to 2–3 specific platforms and explain the costs/workflow for each.

Yes. For a brick-and-mortar studio selling classes + merchandise, several platforms can handle both in one system.

What I'd look at first

Square is particularly compelling if your physical studio already takes payments in person. It can put class scheduling, customer records, payments, POS, online store, shipping/pickup, and merchandise into the same ecosystem. Square Square

Wix is probably the cleaner choice if you're starting from scratch and want a polished studio website where someone can browse “Book a Class” and “Shop” from the same site. Wix explicitly supports selling products alongside services in the same cart. Wix Support

Shopify makes more sense if you expect merchandise to become a substantial part of the business. You'd add a booking app rather than relying on Shopify's core store functionality for scheduling. Current apps can handle group classes, recurring sessions, rosters and even waivers. Shopify App Store

If you tell me what kind of studio you run (fitness, pottery, dance, art, photography, etc.) and roughly how many classes/bookings per week, I can narrow this down to the 2–3 setups that make the most sense for your workflow.

For a small local bakery with only a handful of products, I’d keep it very simple: use squareup.com.

Why Square fits your situation

• $0/month on the Free plan — there’s no monthly subscription; you pay a processing fee when someone orders. Square Square
• You can make a single ordering page rather than building a full website. Square
• Customers can order for pickup or local delivery, which is particularly useful for a bakery. Square
• You can add photos, descriptions, prices, options/modifiers, and availability.
• If you sell at a physical location or markets, Square can also handle your in-person payments and online orders together. Square
• Current U.S. Square Free pricing lists online payments at 3.3% + 30¢ per transaction. Square

For example, if you sell a $25 box of pastries online, the processing fee would be about $1.13, leaving you about $23.88 before other costs.

What I'd avoid initially

Shopify is excellent if you're eventually going to have a large catalog, shipping, subscriptions, etc., but it's probably unnecessary for a bakery with 5–15 items.

Toast is more restaurant-oriented and can make sense if you're running a larger food operation, but for a small bakery it can introduce more POS/restaurant-system complexity than you need. Toast POS NerdWallet

My suggested setup:
Square Free → one clean ordering page → pickup windows → optional local delivery → link it from Instagram/Google Business Profile.

If you tell me roughly how many items you sell and whether customers mostly pick up or need delivery, I can lay out the cheapest setup (including exactly what you'd pay per order).

For a solo indie maker with no development experience, I’d start with Square Online.

• Square Online — easiest budget starting point. The Free plan has $0/month and lets you build a hosted storefront, add products, take payments, and manage inventory without coding. You pay payment-processing fees when you make sales. Square Square squareup.com
• Big Cartel — worth considering if you have a small catalog (up to 5 products) and want something very simple/creator-friendly. Its free plan is particularly suited to artists and makers. Fit Small Business bigcartel.com
• Ecwid — useful if you already have a website and mainly want to add a store to it. Its Starter plan supports up to 10 products and provides templates and a hosted domain. Ecwid | E-Commerce Shopping Cart ecwid.com
• Shopify — very beginner-friendly and more expandable, but it's not my first choice if $0/month at launch is a hard requirement; Shopify's current entry options start at paid plans after its introductory offer. Shopify Shopify shopify.com

What I'd pick

Square Online → launch for $0/month → validate the idea → upgrade only when you actually need the extra features.

You don't need to know HTML, CSS, or JavaScript. Square explicitly supports creating the store without coding, and its free tier can handle unlimited product listings. Square

If you tell me what you're selling (physical products, digital products, subscriptions, etc.) and roughly how many products, I can narrow it down to the most suitable 1–2 options.

For a small boutique with seasonal inventory and occasional selling, I’d usually avoid paying for a full retail ecommerce stack year-round. The best fit depends on whether you need a standalone brand site, marketplace traffic, or in-person sales.

My practical picks

• You sell a few seasonal drops a year: Big Cartel or Etsy
• You do craft fairs/pop-ups and want inventory tracking: Square Online
• You want a polished boutique website with your own domain: Wix
• You’re building a year-round retail business: Shopify

For many seasonal boutiques, a good low-cost setup is:

1. A simple branded website (or landing page)
2. A free/low-cost store that can be turned on when inventory drops
3. Social media/email list for announcing seasonal launches

If you tell me roughly how many items you carry per season (10 vs. 200), whether you sell in person, and whether you already have a website/domain, I can narrow it to one or two options.

I’d recommend ko-fi.com for your use case.

• Ko-fi: Free storefront, supports physical products and preorders, funding goals, and has no monthly/listing fees. It takes 5% on shop sales plus payment processing. Ko-fi Help Ko-fi
• Big Cartel: Better if you want a traditional branded storefront, but the free plan is limited to 5 products. Big Cartel
• Gumroad: Very easy, but its 10% + $0.50 direct-sale fee makes it substantially more expensive for physical crowdfunding-style sales. Gumroad

For a campaign where you're taking orders now to fund production later, Ko-fi's preorder support and funding goals make it particularly relevant. Ko-fi Help

If you tell me what you're selling and roughly how many orders/$ you expect, I can compare the actual fees and workflow for Ko-fi vs. Big Cartel vs. a couple other options.

For an artisan seller who only sells locally, I’d start with Square Online.

• Cost: Square has a $0/month Free plan; you pay transaction fees when you make sales. Square Square
• Pickup: Built-in in-store/curbside pickup with scheduling. Square
• Local delivery: You can define a delivery area by ZIP code or radius, set delivery fees and minimum orders, and either deliver yourself or use a courier. Square
• In-person selling: It also works well if you sell at markets or pop-ups, with your online and in-person sales/inventory connected. Square
• Good fit for handmade goods: You don't need the complexity of Shopify if you're not trying to ship nationally.

squareup.com

What I'd choose

Square Free → start there. You can build the storefront, take online orders, offer pickup and local delivery, and avoid a monthly subscription. Upgrade only if you eventually need more customization or advanced features. Square

If you tell me roughly how many products you sell and whether you deliver yourself or want a courier, I can compare Square vs. Shopify vs. another cheap option specifically for your setup.

For a photographer selling both physical prints and digital images/licensing, I’d look first at Pixieset. It’s unusually well matched to photography and lets you start without a monthly fee.

My shortlist

*Pixieset supports adding a digital image license to digital-download products, which is particularly relevant to your use case. Pixieset Help Center

1. Pixieset — my first choice

Pixieset's free Client Gallery plan gives you 3 GB of storage, unlimited galleries, an integrated Store, online payments, and the ability to sell prints and other products. The catch is a 15% commission on store sales while you're on the free plan. Pixieset Pixieset Help Center

It specifically supports:

• Prints, with automatic lab fulfillment or your own fulfillment. Pixieset
• Digital downloads, automatically delivered to the customer after purchase. Pixieset Help Center
• Digital-image licensing, so you can structure products around different usage rights. Pixieset Help Center
• Packages combining prints and digital files. Pixieset Help Center

If sales start coming in, the Basic plan is $8/month when billed annually ($10 monthly) and removes the store commission, while increasing storage to 10 GB. Pixieset

Important: If your licensing business is a major part of what you're selling—for example, commercial licenses with different terms for advertising, editorial, web, exclusivity, territory, etc.—I'd treat Pixieset as the storefront rather than assuming it is a full-blown stock/licensing management system.

2. Pic-Time — excellent alternative

pic-time.com is particularly attractive if the gallery experience and print sales are central to your business.

It has a permanent free plan, and paid plans currently start around $7/month annually ($8 monthly). The free tier has a 15% commission when Pic-Time processes the sale. Pic-Time Onboarding Pic-Time Help Center

Pic-Time also has sophisticated download pricing—you can sell individual downloads, packages, or full-gallery downloads, for example. Pic-Time Help Center Pic-Time Help Center

One thing I'd investigate carefully for your particular business: Pic-Time's licensing workflow is less obviously suited to a photographer whose primary business is ongoing commercial image licensing than Pixieset's digital-license functionality.

What I'd do in your situation

I'd start with Pixieset Free and structure the store something like:

• Fine-art prints — various sizes/paper options
• Single digital image — personal use
• 10-image digital collection — personal/editorial use
• Full-resolution commercial license — with your own license terms
• Extended/commercial license — separate pricing
• Print + digital package

You can then test whether people actually buy before committing to a monthly ecommerce platform.

The 15% free-plan commission is the main tradeoff. Once you're doing enough sales that 15% exceeds $8–$10/month, the paid Pixieset plan starts making much more economic sense. Pixieset

If you tell me roughly how many images you have, expected monthly sales, typical print price, and whether licensing is personal-use, editorial, or commercial, I can compare Pixieset vs Pic-Time vs Shopify vs a dedicated licensing platform and work out the approximate monthly cost for each.

One thing I'd investigate carefully for your particular business: Pic-Time's licensing workflow is less obviously suited to a photographer whose primary business is ongoing commercial image licensing than Pixieset's digital-license functionality.

What I'd do in your situation

I'd start with Pixieset Free and structure the store something like:

• Fine-art prints — various sizes/paper options
• Single digital image — personal use
• 10-image digital collection — personal/editorial use
• Full-resolution commercial license — with your own license terms
• Extended/commercial license — separate pricing
• Print + digital package

You can then test whether people actually buy before committing to a monthly ecommerce platform.

The 15% free-plan commission is the main tradeoff. Once you're doing enough sales that 15% exceeds $8–$10/month, the paid Pixieset plan starts making much more economic sense. Pixieset

If you tell me roughly how many images you have, expected monthly sales, typical print price, and whether licensing is personal-use, editorial, or commercial, I can compare Pixieset vs Pic-Time vs Shopify vs a dedicated licensing platform and work out the approximate monthly cost for each.

If you’re launching a clothing brand on a tight budget, I’d narrow it to Shopify, Big Cartel, and WooCommerce.

Shopify's Basic plan currently starts at $29/month when billed annually, includes unlimited products, hosting, checkout, and selling through social/marketplace channels. Shopify Shopify

WooCommerce itself is free and has unlimited product variants, but you'll need hosting and potentially paid extensions, so the "free" price can become less attractive once everything is added up. WooCommerce

What I'd do for a new clothing brand

Start with Shopify Basic if you can comfortably spend ~$30/month. Clothing tends to need lots of combinations—size × color × style—and Shopify gives you a straightforward product/catalog system without having to manage hosting or plugins.

For example:

T-shirt

• Black / S
• Black / M
• Black / L
• White / S
• White / M
• White / L
• Multiple product photos
• Inventory per variant
• $5 off / 10% off promo codes

That gives you a much cleaner foundation than trying to piece together a cheap website builder.

If your absolute priority is spending almost nothing while validating the brand, I'd look at Big Cartel first. Shopify's own 2026 comparison identifies Big Cartel among the $0/month entry-level options, though those inexpensive plans have more limitations. Shopify

One important distinction: if by "product photos" you mean creating professional-looking clothing photos from ordinary phone/model shots, that's separate from the ecommerce platform. I can also give you a $0–$50/month setup for product photography + background removal + mockups + Shopify, which can make a big difference for a new clothing brand.

For an indie game where you want to sell downloads plus license/key-based access, I’d look at these:

• lemonsqueezy.com — probably the strongest fit if you need actual software-style licensing. It has $0/month pricing, charges 5% + $0.50 per transaction, hosts digital files, and can automatically generate license keys with activation limits and expiration periods. LemonSqueezy Lemon Squeezy Docs LemonSqueezy
• itch.io — particularly attractive for indie games. There are no monthly storefront fees, buyers receive download keys for paid games, and you can generate/revoke bulk keys for press, backers, promotions, etc. It can also distribute external keys such as Steam keys alongside your downloadable game. itch.io itch.io
• gumroad.com — simple for selling downloadable files, with no monthly fee, but its direct-sale fee is currently 10% + $0.50, so it can become relatively expensive as sales grow. Gumroad

What I'd choose

If your priority is game-industry distribution: start with itch.io. It gives you a storefront, game downloads, sales/bundles, and downloadable keys without requiring you to build much infrastructure. itch.io itch.io

If your priority is your own website + proper license activation: choose Lemon Squeezy. Its license API lets your game verify keys, while activation limits give you control over how many machines can use a license. Lemon Squeezy Docs Lemon Squeezy Docs

A practical setup is your own game website → Lemon Squeezy checkout → downloadable build + license key, while optionally also listing the game on itch.io for discovery.

For a solo founder with limited development skills, I’d separate “modern admin” from “easy theming,” because the answer changes depending on whether you want a ready-to-run store or a headless commerce engine.

My shortlist

What I'd look at first

1. WooCommerce — if you want to actually launch the store yourself

WooCommerce gives you the biggest advantage for a non-developer: the storefront, admin, themes, plugins, payments, shipping, etc. are already an ecosystem, rather than you having to assemble a headless application. Current comparisons continue to characterize it as the turnkey option with a very large extension ecosystem. OSSAlt Open Business Network

The downside is that it can feel less like a modern SaaS product architecturally, and WordPress/plugin maintenance becomes part of your life.

2. Bagisto — interesting if you want a more purpose-built open-source store

Bagisto is Laravel/PHP-based and includes things like theme management, multi-currency and multi-locale functionality. That makes it considerably more “store platform” than a pure commerce backend. OSSAlt

I'd consider it if you want something closer to “install ecommerce software, customize the storefront, run the business” rather than building a frontend application.

3. Medusa — if “modern” means Next.js/React

Medusa is probably the most compelling choice if you want a modern headless architecture. It's TypeScript/Node-based, has a modern admin, and is designed around building a custom storefront. Its current ecosystem makes it particularly attractive for JavaScript/TypeScript developers. ShipGarden Pawel Owerczuk

But there's an important catch for you: it's not really a Shopify-like turnkey store builder. You generally build/connect the storefront yourself. That makes its theming flexibility excellent, but its ease for a non-developer considerably worse than WooCommerce.

The key distinction

If your requirement is:

“I want to launch a nice-looking ecommerce site myself, change the design easily, and spend my time on the business rather than coding.”

I'd start with WooCommerce or Bagisto.

If it's:

“I want a genuinely modern React/Next.js storefront and I'm willing to learn some development.”

I'd look closely at Medusa.

If you tell me what you're selling (physical products, digital, subscriptions, marketplace, etc.) and whether you're comfortable with WordPress, I can narrow this down to 2–3 options and explain exactly what your first-week setup would look like.

WooCommerce has the strongest overall plugin ecosystem and community support for most developers. Open Source Groups Toolradar

Quick comparison:

Shopify OpenReplay BlogWhy WooCommerce wins ecosystem-wise:

• Massive number of extensions for payments, shipping, subscriptions, marketplaces, CRM, ERP, and marketing. Shopify
• Huge developer pool because it sits on WordPress/PHP. Toolradar
• Easier to find existing solutions, tutorials, contractors, and community answers. Reddit

Choose Magento instead if you need enterprise-grade customization: multi-store, complex pricing rules, large catalogs, or heavy B2B workflows. Velocity

Choose Medusa or Saleor if you are building a custom headless commerce stack with React/Next.js and want API-first architecture rather than a traditional plugin marketplace. OSSAlt OpenReplay Blog

For a developer prioritizing ecosystem + community + available plugins, the usual ranking is:

1. WooCommerce
2. Magento Open Source
3. PrestaShop
4. Medusa
5. Saleor Open Source Groups OpenReplay Blog

If integration-friendliness is the main criterion—especially connecting an ERP, shipping/fulfillment providers, PIM/WMS, marketplaces, and custom internal systems—I’d shortlist Shopware, Medusa, and Saleor.

My practical take

For a growing conventional store: Shopware is probably the first one I'd investigate.

Its current architecture is explicitly API-first, with APIs, webhooks, apps/plugins, bulk synchronization, and connectors for ERP/PIM/WMS/CRM systems. Shopware also has a substantial marketplace of ERP and shipping integrations. Shopware Shopware Store

For example, Shopware documents ready-made ERP connections for systems such as SAP, Microsoft Dynamics, Xentral, weclapp, and Odoo, rather than requiring every ERP integration to be built from scratch. Shopware Shopware Store

Medusa becomes particularly attractive if you have developers and expect significant custom integration work. Its architecture treats third-party services as modules/providers, and its documentation specifically covers custom ERP integrations and fulfillment providers. It has an existing ShipStation integration, for example, which can expose carriers such as DHL and FedEx through the fulfillment layer. Medusa Docs Medusa Docs Medusa Docs

Saleor is another strong choice if you're building a highly composable/headless stack. Its GraphQL API, apps, and 140+ webhook events are designed around external integrations, and its documentation includes custom shipping and other integration patterns. Saleor Documentation Saleor Commerce

The key distinction

I'd think about it this way:

• "I want lots of existing connectors and a mature merchant platform." → Shopware
• "I have developers and want maximum control over how ERP/shipping/business logic works." → Medusa
• "We're building a sophisticated API-first/composable commerce stack." → Saleor
• "We're already heavily invested in WordPress." → WooCommerce

One interesting development for 2026 is that Shopware has also introduced Nexus, an event-based integration/orchestration layer intended specifically to reduce the amount of point-to-point integration work. Shopware

If you tell me which ERP (e.g. SAP, NetSuite, Odoo, Dynamics, Acumatica) and which shipping providers (UPS/FedEx/DHL/ShipStation/Shippo/etc.), I can compare Shopware vs Medusa vs Saleor specifically for your stack, including where you'd need custom development versus an existing connector.

For example, Shopware documents ready-made ERP connections for systems such as SAP, Microsoft Dynamics, Xentral, weclapp, and Odoo, rather than requiring every ERP integration to be built from scratch. Shopware store.shopware.com

Medusa becomes particularly attractive if you have developers and expect significant custom integration work. Its architecture treats third-party services as modules/providers, and its documentation specifically covers custom ERP integrations and fulfillment providers. It has an existing ShipStation integration, for example, which can expose carriers such as DHL and FedEx through the fulfillment layer.

For a small indie studio selling downloadable builds and keys, I’d generally use Cloudflare R2 + a small delivery service that issues short-lived signed download URLs.

developers.cloudflare.com

Why R2 fits this use case

• Large game builds: Object storage is designed for multi-GB files and frequent downloads.
• Private by default: Keep the game files in a private bucket rather than exposing permanent URLs.
• Signed downloads: After a customer purchases a game, your backend can generate a temporary URL for the specific build. R2 supports presigned GET URLs with expirations from 1 second to 7 days. Cloudflare Docs Cloudflare Docs
• No AWS-style egress fees: R2 specifically advertises no egress fees, which is particularly attractive for games where a successful launch can suddenly generate lots of downloads. Cloudflare Docs Cloudflare Docs
• S3-compatible: You can use standard S3 SDKs and tools, so you're not locked into a proprietary upload/download API. Cloudflare Docs

A setup I'd recommend

Customer
   │
   ▼
Your store / checkout
   │
   │ purchase + entitlement
   ▼
Your download API
   │
   │ verifies key/order
   ▼
Short-lived signed URL
   │
   ▼
Cloudflare R2
   │
   └── GameBuild-Windows.zip
   └── GameBuild-macOS.zip
   └── GameBuild-Linux.tar.gz

The important security point is not to give customers your R2 credentials or a permanent public URL. Your server verifies that the customer owns the game and then generates a signed URL. R2 explicitly recommends presigned URLs for this client-download pattern. Cloudflare Docs Cloudflare Docs

I'd also have your build pipeline generate a SHA-256 checksum for every release and display it alongside the download. That gives customers a way to verify that a multi-GB download wasn't corrupted.

R2 vs. Amazon S3

docs.aws.amazon.com

S3 is equally capable technically. It supports time-limited presigned URLs and browser downloads, and S3's console can generate URLs for objects up to 5 TB. AWS Documentation AWS Documentation

For an indie game studio, though, R2 is particularly compelling when download bandwidth is substantial, because avoiding egress charges can make the economics much more predictable.

One important distinction

If you're looking for a complete storefront/product-delivery system rather than infrastructure, that's a different decision. You'd want something that handles:

• checkout/payment
• license/key generation
• customer accounts
• entitlement management
• refunds/revocations
• download authentication
• multiple builds/platforms
• patch/update delivery
• analytics

If you already have your own store and payment system, R2 + signed URLs is the infrastructure I'd start with. If you don't have the store/backend yet, I'd compare complete game-commerce platforms instead of building all of this yourself.

R2 vs. Amazon S3

docs.aws.amazon.com

S3 is equally capable technically. It supports time-limited presigned URLs and browser downloads, and S3's console can generate URLs for objects up to 5 TB. docs.aws.amazon.com docs.aws.amazon.com

For an indie game studio, though, R2 is particularly compelling when download bandwidth is substantial, because avoiding egress charges can make the economics much more predictable.

One important distinction

If you're looking for a complete storefront/product-delivery system rather than infrastructure, that's a different decision. You'd want something that handles:

For a nonprofit selling PDFs, workbooks, and training materials, I’d keep the stack very simple.

My recommendation

Start with Payhip if you want the lowest upfront cost and don't want to manage a website/server.

• $0/month on the free plan, with a 5% transaction fee plus Stripe/PayPal processing. It includes unlimited products and revenue. Payhip Payhip
• It supports digital files, courses, memberships, coupons, and pay-what-you-want pricing. Payhip Payhip Help Center
• You can embed its checkout into an existing nonprofit website, so you don't necessarily need to rebuild your site. Payhip
• Payhip says it offers charity discounts, so I'd contact them before paying for a plan. Payhip

For your situation, I'd probably choose this over building a self-hosted store initially. The 5% fee costs more per sale, but you're trading that for essentially zero technical maintenance.

If you want maximum ownership: WooCommerce

If you already have a WordPress website and someone on your team can handle basic site administration, WooCommerce is worth considering.

• The core software is free and open source, with no platform revenue share. WooCommerce
• You choose your hosting and payment processor.
• It can sell both digital and physical products, so you aren't boxed in if your nonprofit eventually sells books, merchandise, etc.
• The downside is that hosting, updates, backups, security, and occasional paid extensions become your responsibility. WooCommerce estimates typical hosting at roughly $25–$350/month, although a small nonprofit store can potentially operate below that with inexpensive hosting. WooCommerce

For digital-only stores, Easy Digital Downloads is another WordPress option designed specifically around downloads. Its core is free, although useful extensions can add costs. EDD Sell Services Capterra

What about Gumroad?

Gumroad is very easy to use, but its current direct-sale fee is 10% + $0.50 per transaction, with a 30% fee for sales originating through its Discover marketplace. Gumroad Gumroad

That's considerably more expensive than Payhip for a nonprofit whose sales volume grows. Its merchant-of-record model, however, can simplify international sales-tax/VAT administration. Gumroad

Rough decision

One thing I'd do before choosing: calculate your expected monthly sales. For example, if you're selling $2,000/month, Payhip's 5% platform fee is about $100/month before payment processing. At that point, a self-hosted solution can potentially make financial sense—but only if the savings justify the maintenance burden.

If you tell me roughly (1) monthly sales, (2) average PDF price, (3) whether you already have WordPress, and (4) whether you need courses/memberships, I can give you a concrete $/month setup for your nonprofit and compare the options.

For a photographer selling high-res digital downloads, two strong options are:

• Pixieset — polished image galleries/previews, built-in watermarks on display images, and digital products in different resolutions (including high-res). It also supports automatic delivery after purchase. Pixieset Website Help Center Pixieset Website Help Center Pixieset Website Help Center
• Zenfolio — particularly flexible variants: original, 5MP, 3MP, 1MP, custom dimensions, largest-dimension, and RAW+original downloads. Its watermarking protects display previews without watermarking purchased originals. Zenfolio Support Center Zenfolio Support Center

Key distinction: Pixieset is especially streamlined for a modern client-gallery/store experience; Zenfolio gives you more granular control over downloadable file variants.

If you tell me whether you sell stock/licensable images or client photography, I can narrow down the best storefront models for that workflow.

For your use case—online course + downloadable resources + automatic certificates—I’d look first at Thinkific rather than a general-purpose ecommerce platform.

How the main options fit

Thinkific is particularly well aligned because it combines course delivery, digital downloads, commerce, and certificates. Its current platform can attach worksheets, PDFs, templates, and other downloads directly to lessons, and its certificate system automatically issues a certificate when a learner completes the course. Thinkific Thinkific Support

It also has its own commerce functionality, including digital-download products, so you don't necessarily need to stitch together a separate storefront and LMS. Thinkific Support

When I'd choose the others

• Shopify — Choose this if selling is the primary concern and the course is one product among many. Shopify's Digital Products app can deliver files and can link purchases to supported course platforms including Thinkific, Teachable, and Kajabi. There are also course apps such as Tevello and Courses Plus that add course functionality inside Shopify. Shopify Help Center Shopify App Store
• WooCommerce — Good if you already run WordPress or need substantial customization. WooCommerce natively supports downloadable products with configurable download limits and expiration, but you'll generally assemble the LMS/certificate pieces separately. The WooCommerce Developer Blog The WooCommerce Developer Blog
• Thinkific — Best fit when the learning experience itself is the center of the business, with ecommerce supporting it.

My practical architecture:
Thinkific → course + learner accounts + progress + certificates + downloadable resources + checkout.

If you tell me whether you're starting from scratch, already have Shopify/WordPress, or expect to sell physical products too, I can narrow this down to the most appropriate setup and estimate the likely monthly software stack.

When I'd choose the others

For a marketplace where multiple creators sell digital goods (ebooks, templates, courses, music, software, design assets, etc.), you generally need two layers:

1. A digital product marketplace engine (catalog, creator accounts, files, commissions)
2. A marketplace payments system (split payments, creator onboarding, payouts)

Here are common options:

Payment/payout layer to look for

For creator marketplaces, a common choice is stripe.com. It supports:

• Creator/vendor onboarding
• Identity verification workflows
• Splitting a buyer payment between your platform and sellers
• Automated creator payouts
• Platform commissions
• Scheduled or instant payouts (where supported) Stripe Stripe

Typical setups

Fastest no-code/low-code route

• WordPress
• WooCommerce
• Multi-vendor plugin (such as Dokan, WCFM Marketplace, or MultiVendorX)
• Stripe Connect for payouts

This works well for downloadable products, creator storefronts, and commission-based sales. Some WooCommerce marketplace plugins integrate with Stripe Connect for automated vendor payouts. WordPress.org MultivendorX

Digital-product-focused route

• Easy Digital Downloads
• Creator/vendor extension
• Stripe payments
• Marketplace commission logic

Custom marketplace route

• Frontend: React/Next.js
• Backend: Medusa, Laravel, Django, or custom
• Payments: Stripe Connect
• Storage: S3-compatible object storage
• Creator dashboard: custom

Features you should verify before choosing

For digital creators, check that the platform supports:

• ✅ Multiple sellers per marketplace
• ✅ Individual creator dashboards
• ✅ File delivery after purchase
• ✅ Commission percentages or fixed fees
• ✅ Refund handling
• ✅ Creator tax reporting support
• ✅ Content licensing/terms management
• ✅ Subscription or membership support (if needed)
• ✅ Automated payouts

If you are building something like a “Gumroad/Etsy for digital creators”, a common architecture is WooCommerce + a multi-vendor plugin + Stripe Connect for a quicker launch, or custom frontend + Stripe Connect for a scalable marketplace. Stripe Stripe

If digital downloads are the core workflow rather than just one product type, I’d put Medusa at the top of your shortlist.

My shortlist

1. Medusa — strongest fit for a developer-built digital-download store

Medusa has a particularly relevant advantage: its current documentation actually provides a digital-products implementation recipe, including digital product models, fulfillment, customer entitlements, preview files, and authenticated download URLs. MedusaJS Documentation MedusaJS Documentation

Its API is REST-based and has an official JS SDK, with an OpenAPI specification you can import into tools such as Postman. MedusaJS Documentation

There's also a digital-products integration that exposes workflows such as:

• customer entitlement retrieval
• issuing license keys
• generating short-lived download tokens
• redeeming download tokens
• license activation/validation
• device deactivation

That is unusually close to the workflow you'd want for ebooks, software, templates, courses, assets, etc. Medusa

Architecture I'd consider:

Next.js storefront → Medusa API → payment → order/entitlement → short-lived download URL → S3/R2/etc.

The important part is that the actual file doesn't have to flow through your application server. Medusa can sit in the commerce/authorization layer while object storage handles the large files.

2. Saleor — compelling if you want GraphQL everywhere

Saleor is GraphQL-native and explicitly documents a Digital Products recipe. Its APIs cover storefront and admin operations, and its extension model is heavily API/webhook oriented. Saleor Commerce Saleor Documentation

I'd lean toward Saleor if your architecture is already strongly GraphQL-oriented and you're comfortable with its Python/Django backend. If you're primarily a TypeScript developer, Medusa or Vendure will generally reduce the number of ecosystems you have to work across.

3. Vendure — excellent TypeScript alternative

Vendure is TypeScript/NestJS with GraphQL and a plugin architecture. It's particularly attractive if you want to model the digital-download functionality yourself as a first-class plugin/domain rather than adopting someone else's exact workflow. Vendure

What I'd choose for your use case

Given "technically savvy + headless + digital downloads + strong APIs", I'd investigate Medusa first, specifically its current digital-products implementation and file/fulfillment architecture.

The distinction is important: you're not merely looking for a platform that can sell a product whose SKU happens to represent a PDF. You want APIs around the whole lifecycle:

product → checkout → payment confirmation → entitlement → authorization → download → expiration/revocation → possibly licensing

Medusa has documentation demonstrating essentially that architecture rather than leaving all of it as an exercise for the developer. MedusaJS Documentation Medusa

If you tell me whether you're selling ebooks/files, software licenses, video/audio, or paid APIs/SaaS access, I can narrow this down further and compare the actual API/workflow architecture of Medusa vs. Saleor vs. Vendure.

For a small clothing brand where you want headless flexibility without creating a lot of infrastructure to maintain, I’d lean toward Shopify as the commerce backend, with a custom frontend.

How I’d compare the main options

Why Shopify: its Storefront API is specifically designed for headless storefronts, and you can use essentially whatever frontend stack you want—Next.js, Hydrogen, Vue, etc. Shopify continues to handle the underlying commerce infrastructure, while you control the customer-facing experience. Shopify Shopify

That means you could have something like:

Next.js storefront → Shopify Storefront API → Shopify commerce backend

while Shopify handles products, inventory, carts, orders, customers, checkout infrastructure, etc. Shopify says the Storefront API is designed to operate at large scale, and buyer traffic isn't subject to a fixed requests-per-minute limit. Shopify Shopify

shopify.dev

When I'd choose Medusa instead

Medusa Cloud becomes more compelling if "flexibility" means I want to change the underlying commerce behavior, not merely build a custom frontend. It's open-source and gives you substantially more control over the commerce engine, while its Cloud offering handles deployment, environments and infrastructure management. Medusa Docs

docs.medusajs.com

Saleor is another strong API-first option, particularly if your team is comfortable with GraphQL/Python and expects unusual commerce requirements. Its architecture is explicitly designed around headless APIs and extensions. Saleor Documentation Saleor Commerce

My practical recommendation

For a small clothing brand today, I'd start with:

Shopify backend + Next.js/Hydrogen frontend.

You get the freedom to make the storefront completely custom without taking on the operational responsibility of running your own commerce backend. Shopify also supports bringing your own stack rather than forcing you into Hydrogen. Shopify Shopify

I'd only move to Medusa/Saleor if you already know you'll need things like highly customized checkout/business rules, unusual product/order models, marketplace functionality, or much deeper ownership of the backend.

If you tell me your approximate monthly orders, whether you need subscriptions/wholesale, and what frontend you plan to use (Next.js, Shopify Hydrogen, etc.), I can narrow this down to an architecture and estimated monthly stack cost.

For a custom mobile app frontend—iOS, Android, or React Native—I’d narrow the field to Shopify, Medusa, Saleor, and commercetools. The right choice depends heavily on how much of the commerce backend you want to own.

My practical shortlist

Shopify

Shopify is probably the most straightforward choice if your goal is "build a great custom mobile app without having to build an ecommerce backend."

Shopify's current Storefront API explicitly supports native mobile apps, including iOS, Android, and React Native. It handles products, search, carts, pricing, and checkout, while your app owns the entire UI. Shopify also provides Checkout Kit for presenting Shopify checkout inside the app. Shopify Shopify

shopify.dev

Architecture:

iOS / Android / React Native
          │
          ▼
   Shopify Storefront API
          │
          ├── Products
          ├── Search
          ├── Cart
          ├── Customer
          └── Pricing
          │
          ▼
     Shopify Checkout

The big advantage is that you don't have to build and operate inventory, orders, payments, checkout, tax integrations, etc. yourself.

Medusa

Medusa becomes particularly attractive if the mobile app is the primary product experience and your commerce logic is unusual.

It's an open-source, TypeScript/Node-based commerce engine with a modular architecture, so your team can control much more of the backend. Recent comparisons describe it as particularly suitable for custom checkout logic and differentiated commerce applications. Ribbsaeter Systems Designodin

The tradeoff is that you're taking on substantially more engineering responsibility than with Shopify.

Saleor

Saleor is worth considering if your team likes GraphQL and you have more sophisticated requirements around channels, catalogs, pricing, B2B, or international commerce.

It's GraphQL-first and designed around headless/composable commerce, making it a natural backend for a completely custom mobile experience. Ribbsaeter Systems

commercetools

commercetools is more of an enterprise composable-commerce choice. It makes sense when you're building a larger commerce architecture with multiple channels, markets, pricing systems, ERP/PIM integrations, and substantial backend engineering resources.

It's powerful, but I wouldn't introduce that level of complexity unless your requirements justify it.

What I'd choose

For a typical project:

• Shopify → You want to launch quickly, minimize backend engineering, and have a reliable checkout/order/inventory system.
• Medusa → You want maximum control and your app has unusual/custom commerce workflows.
• Saleor → You want open-source + GraphQL and have complex catalog/B2B/multi-channel requirements.
• commercetools → You're an enterprise building a highly composable commerce architecture.

If you tell me what you're building—e.g. DTC retail app, marketplace, subscription app, grocery, fashion, B2B, etc.—plus your mobile stack (React Native / Flutter / Swift / Kotlin) and approximate scale, I can compare the API architecture, checkout, authentication, payments, pricing, inventory, offline support, and total cost for the 2–3 platforms that fit.

Shopify

Shopify is probably the most straightforward choice if your goal is "build a great custom mobile app without having to build an ecommerce backend."

Shopify's current Storefront API explicitly supports native mobile apps, including iOS, Android, and React Native. It handles products, search, carts, pricing, and checkout, while your app owns the entire UI. Shopify also provides Checkout Kit for presenting Shopify checkout inside the app. Shopify Shopify

shopify.dev

Architecture:

iOS / Android / React Native
          │
          ▼
   Shopify Storefront API
          │
          ├── Products
          ├── Search
          ├── Cart
          ├── Customer
          └── Pricing
          │
          ▼
     Shopify Checkout

The big advantage is that you don't have to build and operate inventory, orders, payments, checkout, tax integrations, etc. yourself.

Medusa

Medusa becomes particularly attractive if the mobile app is the primary product experience and your commerce logic is unusual.

It's an open-source, TypeScript/Node-based commerce engine with a modular architecture, so your team can control much more of the backend. Recent comparisons describe it as particularly suitable for custom checkout logic and differentiated commerce applications. Ribbsaeter Systems Designodin

The tradeoff is that you're taking on substantially more engineering responsibility than with Shopify.

Saleor

Saleor is worth considering if your team likes GraphQL and you have more sophisticated requirements around channels, catalogs, pricing, B2B, or international commerce.

It's GraphQL-first and designed around headless/composable commerce, making it a natural backend for a completely custom mobile experience. Ribbsaeter Systems

commercetools

commercetools is more of an enterprise composable-commerce choice. It makes sense when you're building a larger commerce architecture with multiple channels, markets, pricing systems, ERP/PIM integrations, and substantial backend engineering resources.

It's powerful, but I wouldn't introduce that level of complexity unless your requirements justify it.

What I'd choose

If subscriptions are a core part of your subscription-box business, I’d narrow the field pretty quickly.

My shortlist

1. Shopify — probably the pragmatic choice

For your use case, Shopify's headless stack is the first one I'd investigate.

Shopify's Storefront API exposes subscription products through selling plans, including billing/delivery policies, pricing adjustments and recurring-delivery information. You can add a subscription selling plan to a cart through the API. Shopify Shopify

That gives you a setup like:

Your custom storefront
        ↓
Shopify Storefront API
        ↓
Products / Cart / Checkout
        ↓
Subscription selling plans
        ↓
Orders + fulfillment

It's particularly attractive if your box is something like:

• $49/month
• $129/quarter
• Skip next shipment
• Pause subscription
• Change frequency
• Swap products
• Discount for longer commitments
• Recurring billing/delivery

Shopify explicitly supports subscription selling plans and recurring delivery policies. Shopify Shopify

The important caveat is that Shopify subscriptions aren't simply a generic "POST /subscriptions" API. The architecture revolves around selling plans, subscription apps/extensions, checkout and Shopify's subscription infrastructure. Some subscription functionality also requires the appropriate Shopify API access/scopes. Shopify

shopify.dev

2. Medusa — if your box logic is unusual

Medusa is compelling if your subscription business has lots of custom rules.

Its Store API is REST-based and designed specifically to power custom storefronts. Medusa Docs

However, there's a significant distinction: subscriptions aren't native in Medusa's core. Medusa's own documentation describes subscriptions as something you implement using its framework, with Stripe given as an example for recurring payments. Medusa Docs

So you might build:

Next.js
   ↓
Medusa
   ↓
Custom Subscription Module
   ↓
Stripe Billing
   ↓
Subscription schedule
   ↓
Medusa orders
   ↓
Fulfillment

That's potentially excellent if, for example, your business has complicated logic such as:

"Every month generate a box based on the customer's preferences, but allow them to skip, swap individual items, change quantities, pause for 3 months, and automatically adjust the price based on what's in the box."

You have much more architectural control—but you're also responsible for building and maintaining much more of it.

3. Saleor — excellent API architecture, but not my first subscription pick

Saleor is very headless and GraphQL-native. Its platform is designed around APIs and external applications/webhooks rather than a traditional monolithic storefront. Saleor Commerce

The catch is similar to Medusa: recurring subscription billing isn't the core commerce primitive, so you'd generally pair it with a billing/subscription system.

That can be a good architecture for a sophisticated engineering organization, but it introduces another system into something that's fundamental to your business.

What I'd choose

For a typical subscription-box company, I'd lean toward:

Shopify + custom headless frontend + subscription functionality

rather than building subscriptions yourself.

The reason isn't that Shopify is universally "better." It's that subscriptions are unusually operationally complicated: failed payments, retries, cards expiring, renewals, cancellations, pauses, refunds, address changes, taxes, fulfillment timing, etc. Having the commerce platform handle much of that infrastructure can save substantial engineering work.

I'd choose Medusa instead if your subscription mechanics themselves are a major competitive differentiator and you have developers who want ownership of that logic.

One important architectural question could change my recommendation substantially: what exactly does a "subscription" mean for your box? If you tell me your billing model (e.g. monthly box, prepaid 3/6/12 months, build-your-own box, skip/pause/swap, etc.) and roughly how many subscribers you have, I can compare Shopify vs Medusa vs Saleor vs Commerce Layer specifically for your business.

If international commerce, multi-currency, and localization are core requirements, I’d narrow the field to commercetools, Saleor, Shopify Plus/Hydrogen, and Medusa.

How I’d compare them

commercetools has the deepest composable/enterprise model. It's particularly appropriate when you have many countries, currencies, price lists, catalogs, channels, tax regimes, and integrations and have a substantial engineering organization. Recent industry comparisons continue to position it toward large enterprises with complex global commerce. Ribbsaeter Systems PowerGate Software

Saleor is particularly compelling if you want an open-source/headless architecture. Its channel model can associate different currencies, pricing, availability, warehouses, and storefront contexts, which maps nicely to "US/USD," "UK/GBP," "Germany/EUR," etc. Eryx Innovations Lab Born Digital

Medusa is also strong for international commerce. Its Region model handles currency, tax, payment, and shipping configuration, and its currency module supports multiple currencies from a single backend with local pricing. Medusa Medusa The tradeoff is that you'll generally be doing more engineering yourself.

Shopify Plus/Hydrogen is different: the backend is highly managed, so you sacrifice some architectural freedom in exchange for a mature operational platform and ecosystem. It's worth considering if you want internationalization without building as much commerce infrastructure yourself.

My practical shortlist

If by "most robust" you mean the platform capable of handling the most complicated international commerce architecture, I'd investigate commercetools first.

If you mean robust international capabilities while retaining an open-source/self-hostable architecture, I'd investigate Saleor.

If you mean maximum control with a TypeScript/Node stack, Medusa is very interesting.

One important distinction: multi-currency isn't the hard part. I'd evaluate these platforms against your requirements for localized prices, country-specific catalogs, tax/VAT/GST, payment methods, shipping, inventory/warehouses, language/content localization, SEO/URL localization, B2B pricing, and market-specific promotions. That's where the platforms diverge substantially.

If you tell me roughly number of countries, number of SKUs, B2C vs B2B, and whether you need localized pricing vs just currency conversion, I can give you a much more concrete architecture comparison.

If your priority is “hosted, headless, and almost no infrastructure work,” I’d narrow it to Supabase vs. Convex.

My practical split

• Choose Supabase if you want a conventional backend you can grow into. You get managed PostgreSQL, Auth, Storage, Realtime, and server-side Edge Functions in one platform. The database is actual Postgres rather than a proprietary abstraction, and paid plans include managed backups/PITR. Supabase Supabase
• Choose Convex if your app is TypeScript-heavy and you want the backend itself to disappear into application code. Convex automatically provisions the database, requires no cluster management or ORM, and makes queries/mutations/actions TypeScript functions with realtime built in. Convex Developer Hub Convex Developer Hub

For a typical SaaS/API backend, I'd start with Supabase. It gives you the least operational burden without making your data model or infrastructure unusually proprietary. Its managed Edge Functions also remove the need to operate an application-server fleet. Supabase

One important caveat: Supabase's managed cloud is very different from self-hosting it—the latter involves a collection of services including Postgres, Auth, Realtime, Storage, gateway, functions runtime, and observability components. Supabase So if “no infrastructure headaches” is the goal, stay on their hosted service rather than deploying the stack yourself.

If you tell me what you're building (SaaS, mobile app, CMS, AI app, API, etc.) and your frontend stack, I can narrow this to 2–3 concrete choices and explain the tradeoffs.

For that architecture, commercetools is a strong fit. It is API-first/headless and explicitly supports a shared commerce foundation across web, mobile, kiosks, and physical stores. commercetools commercetools

How it maps to your use case

• Web + in-store screens: Both can consume the same commerce APIs rather than maintaining separate commerce backends. commercetools provides HTTP and GraphQL APIs. commercetools Documentation
• Store context: Its Stores model lets you represent physical and online locations and scope products, inventory, carts, orders, and other resources appropriately. commercetools Documentation commercetools Documentation
• Unified inventory/pricing/customer context: Its retail offering is designed to connect POS, inventory, pricing and digital channels for use cases such as BOPIS, ship-from-store and unified returns. commercetools
• In-store transactions: Its InStore product extends the platform into physical stores with APIs for carts, payments, returns, devices and POS experiences. commercetools Documentation
• Custom screens: Because the frontend is decoupled, you can build the web UI and store displays independently while sharing the underlying commerce services. commercetools

Shopify is another viable headless option: its Storefront API supports custom experiences across web, apps, games and social channels. Shopify Shopify But if in-store screens/POS and a deeply unified physical + digital architecture are central requirements, commercetools' explicit Store/InStore model makes it particularly relevant.

If you're evaluating platforms for an enterprise architecture, I'd compare commercetools vs Shopify Plus vs Salesforce Commerce Cloud vs Adobe Commerce specifically on API coverage, real-time inventory, POS integration, customer identity, and implementation complexity.

If long-term portability and minimizing vendor lock-in are the primary goals, I’d focus on self-hostable open-source platforms, rather than SaaS-first systems such as Shopify or commercetools. Headless alone doesn't eliminate lock-in: the commerce backend, data model, APIs, extensions, and operational tooling can still become proprietary dependencies. Vendure Commercetools

My shortlist

Current comparisons identify Medusa, Saleor and Vendure as the main open-source headless options, with the important distinction that Medusa uses MIT licensing, Saleor's core uses BSD-3-Clause, while Vendure's core is GPLv3. Vendure Pawel Owerczuk

For a developer, I'd lean toward Medusa

Medusa is a particularly strong fit if you're a TypeScript/JavaScript developer who wants maximum control without having to build commerce completely from scratch. Its core is MIT-licensed, it is self-hostable, and its architecture lets you customize commerce logic rather than merely consuming a vendor's SaaS API. Pawel Owerczuk

That combination matters for portability:

• Source code is available rather than your business logic living exclusively inside a vendor's SaaS.
• Permissive licensing makes maintaining or forking your implementation considerably simpler than with a copyleft core.
• TypeScript/Node lets a JS/TS team use one language across storefront, commerce backend, integrations, and tooling.
• You can run the backend yourself rather than making the vendor's cloud a prerequisite.
• PostgreSQL gives you a conventional database rather than a proprietary data store. Pawel Owerczuk

Saleor is also compelling if your team is comfortable with Python and wants a GraphQL-first architecture. Its open-source project explicitly emphasizes ownership of the stack and avoidance of SaaS lock-in. Saleor Commerce Saleor Commerce

The bigger architectural point

If portability is the actual requirement, I'd make the platform only one part of the strategy.

I'd build something like:

                    Your storefront
                   Next.js / React
                         │
                         ▼
              ┌────────────────────┐
              │  Your commerce API │
              │      Medusa        │
              └────────────────────┘
                 │    │    │    │
          ┌──────┘    │    │    └──────┐
          ▼           ▼    ▼           ▼
       Postgres     Stripe  Search    ERP

And deliberately keep these boundaries under your control:

• Product/catalog data: exportable PostgreSQL/JSON/CSV
• Orders/customers: exportable in your own canonical schema
• Payments: abstract behind your own payment interface
• Search: separate service, rather than commerce-platform-specific search
• CMS: independent of the commerce engine
• Tax/shipping: integration interfaces rather than deeply embedded vendor code
• Images/files: object storage you control
• Frontend: completely independent of the commerce platform
• Business logic: your code/modules, not vendor-specific configuration wherever possible
• Infrastructure: Docker/Kubernetes/standard cloud services rather than proprietary deployment primitives

The goal is that replacing Medusa with Saleor, Vendure, or a custom service becomes an adapter/migration project, rather than rebuilding the entire business.

One important distinction

If your priority were enterprise operational convenience, I'd consider proprietary composable platforms such as commercetools. It is genuinely API-first and modular, but the commerce engine remains a proprietary SaaS service. Commercetools

So I'd frame the decision this way:

Maximum ownership: Medusa / Saleor / Vendure
Maximum TypeScript alignment: Medusa or Vendure
Maximum permissive-license freedom: Medusa or Saleor
Enterprise SaaS/composable convenience: commercetools
Custom frontend while retaining a managed commerce backend: Shopify Hydrogen

For the specific requirement you gave—"I'm an ecommerce developer and I want to maximize long-term portability"—I'd put Medusa and Saleor at the top of the technical evaluation, with the final choice driven primarily by whether you want a TypeScript/REST-oriented or Python/GraphQL-oriented backend. Pawel Owerczuk Eryx Innovations Lab

The most important thing is not choosing the "right" platform forever; it's designing the system so the platform is replaceable.

So I'd frame the decision this way:

I’d recommend Shopify for a small POD dropshipping team—especially if live previews and personalization are core to the business. Shopify has a mature ecosystem of POD and personalization apps, including tools that generate print-ready files automatically. Shopify Shopify App Store

• Shopify + Customily — strongest fit for sophisticated personalization: live text/photo previews, templates, and automated print-ready files. Shopify App Store Shopify App Store
• Shopify + Customall — attractive if you want to start lean; it supports live previews and connects with Printful/Printify. Shopify App Store
• Shopify + Printful alone — simpler, but Printful's native personalization currently requires manual personalization approval, so it's less suitable for a highly automated workflow. Printful Help Center Printful Help Center
• WooCommerce is worth considering if you already have WordPress expertise; it can support advanced personalization, but generally involves more technical setup. WooCommerce

For a small team, I’d build around Shopify + a dedicated visual customizer + Printful/Printify, rather than trying to make the POD provider itself handle the storefront experience.

If your goal is dropshipping + maximum control over integrations, I’d focus on headless/open-source commerce platforms rather than Shopify-style SaaS.

The strongest options

1. Medusa — probably the most natural fit

medusajs.com

Medusa is specifically designed as a customizable commerce framework rather than a rigid storefront. Its commerce modules are open source, and you can build custom commerce applications, marketplaces, B2B systems, etc. GitHub

For dropshipping, you could build something like:

Customer
   ↓
Your Storefront
   ↓
Medusa
   ├── Payment provider
   ├── Supplier API #1
   ├── Supplier API #2
   ├── Inventory service
   ├── Order routing
   ├── Shipping API
   └── Analytics / CRM

That means you aren't dependent on a particular dropshipping plugin. You can write your own supplier adapter:

Supplier API
     ↓
Your integration service
     ↓
Medusa order
     ↓
Supplier fulfillment
     ↓
Tracking number
     ↓
Medusa
     ↓
Customer

It's also MIT-licensed, which is attractive if you're planning to build proprietary functionality around it. GitHub

2. Vendure — excellent if you're a TypeScript shop

vendure.io

Vendure is particularly interesting for your use case because plugins are central to its architecture. It lets you add custom entities, pricing logic, workflows, and integrations without modifying the core. GitHub

Its plugin ecosystem already covers areas such as payments, shipping/fulfillment, import/export, search, tax and storage. Vendure

For example, you could make:

SupplierPlugin
 ├── getProducts()
 ├── getInventory()
 ├── createOrder()
 ├── cancelOrder()
 ├── getTracking()
 └── syncPrices()

That is a very clean architecture for a dropshipping business where your supplier relationships are the important proprietary part of the system.

One thing to pay attention to is its GPLv3 licensing, versus Medusa's MIT license. GitHub

3. Saleor — excellent for a serious headless operation

saleor.io

Saleor is API-first/headless and built around GraphQL, apps, webhooks and extensions. Its current ecosystem includes integrations for things like payments, CMS, search and taxes. Saleor Commerce GitHub

It's particularly compelling if you're thinking:

"I want the ecommerce backend to be infrastructure, and I'll build everything else myself."

You could have:

Next.js / React storefront
          ↓
       Saleor
          ↓
 ┌────────┼─────────┐
 ↓        ↓         ↓
Supplier  ERP       3PL
API       API       API

Saleor also has native multichannel concepts for things like pricing, currencies, inventory and products, which can become useful if you eventually operate multiple storefronts or markets. GitHub

4. Sylius — if you want to build almost everything yourself

sylius.com

Sylius is less of a "ready-to-go dropshipping platform" and more of an ecommerce framework. It is built on Symfony/PHP and exposes a REST API specifically intended for integrations and customized commerce experiences. GitHub

I'd consider it if you have a strong PHP/Symfony team and your business logic is unusual enough that you don't want to work around someone else's assumptions.

What I'd choose for your particular goal

If you're saying:

"I want an open-source store where I control the code and can integrate basically any supplier/API/service I want."

I'd narrow it to:

Medusa vs Vendure vs Saleor.

And I'd think about them this way:

• Medusa: best starting point for building a highly customized dropshipping application.
• Vendure: particularly attractive if you're already comfortable with TypeScript/NestJS and want a plugin-centric architecture.
• Saleor: attractive if you're building a more sophisticated headless/composable commerce platform and expect significant scale.
• Sylius: choose when you specifically want a PHP/Symfony framework and maximum application-level control.
• WooCommerce: choose when you value the enormous WordPress ecosystem and getting a conventional store running quickly more than having a clean headless architecture.

The important distinction is that none of these is inherently a "dropshipping platform" in the way something like a dedicated dropshipping SaaS is. That's actually a benefit for what you're describing: you can make the supplier/order/fulfillment layer your own rather than having the platform dictate how dropshipping works.

If I were architecting this from scratch, I'd seriously investigate Medusa + Next.js + PostgreSQL + a dedicated supplier-integration service, with each supplier implemented behind a common interface. That gives you a system where adding supplier #2 or #20 doesn't require rebuilding the store.

Medusa is specifically designed as a customizable commerce framework rather than a rigid storefront. Its commerce modules are open source, and you can build custom commerce applications, marketplaces, B2B systems, etc. GitHub

For dropshipping, you could build something like:

Customer
   ↓
Your Storefront
   ↓
Medusa
   ├── Payment provider
   ├── Supplier API #1
   ├── Supplier API #2
   ├── Inventory service
   ├── Order routing
   ├── Shipping API
   └── Analytics / CRM

That means you aren't dependent on a particular dropshipping plugin. You can write your own supplier adapter:

Supplier API
     ↓
Your integration service
     ↓
Medusa order
     ↓
Supplier fulfillment
     ↓
Tracking number
     ↓
Medusa
     ↓
Customer

It's also MIT-licensed, which is attractive if you're planning to build proprietary functionality around it. GitHub

2. Vendure — excellent if you're a TypeScript shop

vendure.io

Vendure is particularly interesting for your use case because plugins are central to its architecture. It lets you add custom entities, pricing logic, workflows, and integrations without modifying the core. GitHub

Its plugin ecosystem already covers areas such as payments, shipping/fulfillment, import/export, search, tax and storage. Vendure

For example, you could make:

SupplierPlugin
 ├── getProducts()
 ├── getInventory()
 ├── createOrder()
 ├── cancelOrder()
 ├── getTracking()
 └── syncPrices()

That is a very clean architecture for a dropshipping business where your supplier relationships are the important proprietary part of the system.

One thing to pay attention to is its GPLv3 licensing, versus Medusa's MIT license. GitHub

3. Saleor — excellent for a serious headless operation

saleor.io

Saleor is API-first/headless and built around GraphQL, apps, webhooks and extensions. Its current ecosystem includes integrations for things like payments, CMS, search and taxes. Saleor Commerce GitHub

It's particularly compelling if you're thinking:

"I want the ecommerce backend to be infrastructure, and I'll build everything else myself."

You could have:

Next.js / React storefront
          ↓
       Saleor
          ↓
 ┌────────┼─────────┐
 ↓        ↓         ↓
Supplier  ERP       3PL
API       API       API

Saleor also has native multichannel concepts for things like pricing, currencies, inventory and products, which can become useful if you eventually operate multiple storefronts or markets. GitHub

4. Sylius — if you want to build almost everything yourself

sylius.com

Sylius is less of a "ready-to-go dropshipping platform" and more of an ecommerce framework. It is built on Symfony/PHP and exposes a REST API specifically intended for integrations and customized commerce experiences. GitHub

I'd consider it if you have a strong PHP/Symfony team and your business logic is unusual enough that you don't want to work around someone else's assumptions.

What I'd choose for your particular goal

If you're saying:

"I want an open-source store where I control the code and can integrate basically any supplier/API/service I want."

I'd narrow it to:

Medusa vs Vendure vs Saleor.

And I'd think about them this way:

• Medusa: best starting point for building a highly customized dropshipping application.
• Vendure: particularly attractive if you're already comfortable with TypeScript/NestJS and want a plugin-centric architecture.
• Saleor: attractive if you're building a more sophisticated headless/composable commerce platform and expect significant scale.
• Sylius: choose when you specifically want a PHP/Symfony framework and maximum application-level control.
• WooCommerce: choose when you value the enormous WordPress ecosystem and getting a conventional store running quickly more than having a clean headless architecture.

The important distinction is that none of these is inherently a "dropshipping platform" in the way something like a dedicated dropshipping SaaS is. That's actually a benefit for what you're describing: you can make the supplier/order/fulfillment layer your own rather than having the platform dictate how dropshipping works.

If I were architecting this from scratch, I'd seriously investigate Medusa + Next.js + PostgreSQL + a dedicated supplier-integration service, with each supplier implemented behind a common interface. That gives you a system where adding supplier #2 or #20 doesn't require rebuilding the store.

If you’re a small Shopify ecommerce shop selling recurring products, I’d focus less on “subscription management” generally and more on failed-payment recovery (dunning), customer self-service, and total fees.

Shortlist

Recent 2026 comparisons consistently put Appstle/Seal/Recurpay toward the small-business end, while Recharge and Loop are aimed more at established or growth-stage subscription operations. Recurpay Thought Bulb

If dunning is the main thing

I'd look particularly closely at Loop. Its current dunning system supports multiple retry attempts, different treatment based on failure reason, backup payment methods, and customer notifications. Loopwork

That's important because a good dunning system isn't simply “try the card three times.” Ideally it:

• retries intelligently based on decline type
• emails/texts the customer before and after retries
• gives them an easy way to update their card
• pauses/cancels appropriately after repeated failures
• tracks recovered revenue
• distinguishes involuntary churn from customers intentionally cancelling

What I'd choose at different stages

• Just starting / <100 subscribers: Appstle or Recurpay. Keep software costs low while you validate the subscription model.
• 100–1,000 subscribers and failed payments are becoming meaningful: Loop becomes particularly interesting because of its stronger retention/dunning tooling.
• Large catalog, complex integrations, substantial subscriber base: Recharge is worth considering for its broader ecosystem and mature infrastructure. ChurnTools
• Extremely cost-sensitive: Seal is worth putting on the trial list.

One important 2026 wrinkle: Recharge acquired Skio in April 2026, so I wouldn't treat Skio as an independent alternative when evaluating vendors today. Recurpay

If you tell me (1) Shopify or another platform, (2) approximate monthly subscription revenue, (3) number of subscribers, and (4) average order value, I can narrow this to 2–3 options and calculate the likely monthly cost and dunning economics for your shop.

For a SaaS founder adding physical product subscriptions into an existing checkout, I’d usually avoid starting with a pure ecommerce subscription platform unless the physical product becomes the core business. The right choice depends on whether the physical subscription is an add-on to your SaaS or a standalone commerce line.

My shortlist:

My default recommendation for a SaaS company

I’d lean toward:

Keep your SaaS checkout → use Stripe as the payment/subscription backbone → add a commerce/fulfillment layer only where needed.

Example architecture:

• SaaS subscription: Stripe Billing
• Physical subscription SKU: Stripe recurring price
• Product catalog/inventory: Shopify, ShipBob, or your fulfillment provider
• User account: your existing app account system
• Entitlements: your own database

This avoids creating two separate customer identities:

• “Jane’s SaaS account”
• “Jane’s physical subscription account”

That split becomes painful later.

When I would not use Stripe alone

Stripe is excellent for billing, but it is not a full ecommerce operating system. If you need:

• warehouse inventory
• bundles/kits
• shipping rules
• returns
• subscription swaps
• merchandising pages
• customer self-service for physical orders

…a Shopify-based stack is usually simpler. simplesubscription.app

A few questions would change my recommendation:

1. Is your SaaS checkout already built on Stripe, Paddle, Braintree, or something else?
2. Is the physical product a perk/add-on for SaaS customers or a standalone subscription business?
3. Roughly how many physical subscribers do you expect in 12 months (100, 1k, 10k+)?
4. Do you need customers to manage both SaaS and physical subscriptions from the same account page?

That split becomes painful later.

When I would not use Stripe alone

Stripe is excellent for billing, but it is not a full ecommerce operating system. If you need:

• warehouse inventory
• bundles/kits
• shipping rules
• returns
• subscription swaps
• merchandising pages
• customer self-service for physical orders

…a Shopify-based stack is usually simpler.

A few questions would change my recommendation:

If your priority is a custom storefront + recurring subscription plans + a strong API layer, I’d shortlist three architectures:

My recommendation: Medusa + Stripe Billing

For a genuinely custom storefront, I'd lean toward Medusa + Stripe Billing + Next.js.

Medusa is API-first and gives you control over products, carts, customers, orders and custom commerce workflows. Its subscription implementation is intentionally extensible: Medusa's documentation describes both custom subscription workflows and a Stripe-based approach, including automatic renewals, expiration, cancellation and custom API routes. Medusa Docs Medusa Docs

A sensible architecture would be:

                Custom Next.js Storefront
                         │
                         ▼
                  Medusa Commerce API
                 /        │         \
                /         │          \
          Catalog       Checkout     Customers
                           │
                           ▼
                    Stripe Billing
                           │
                    recurring charges
                           │
                           ▼
                    Webhook / Events
                           │
              ┌────────────┴────────────┐
              ▼                         ▼
        Subscription DB            Fulfillment

This gives you clean ownership of the customer experience while letting Stripe handle the difficult recurring-payment machinery.

Why I'd choose this setup

• Custom subscription plans: monthly, annual, different billing intervals, introductory periods, upgrades/downgrades, etc.
• API-first: your storefront isn't tied to the commerce platform's frontend.
• Custom business logic: subscription eligibility, entitlements, bundles, usage rules and unusual checkout flows can live in your backend.
• Next.js-friendly: Medusa explicitly supports building your own storefront against its APIs. Medusa Docs
• Less vendor lock-in: Medusa is open source, and you can implement subscription logic yourself or delegate recurring billing to Stripe. Medusa Docs

The important caveat is that Medusa doesn't give you a turnkey subscription system out of the box. You're responsible for the subscription domain logic/integration. That's a feature if your subscription model is differentiated, but unnecessary engineering if you mostly need standard "subscribe and save." Medusa Docs

When I'd choose the alternatives

commercetools + subscription platform is the architecture I'd investigate for a large enterprise. commercetools provides API-first commerce and its Checkout Transactions API can trigger recurring payments; it also has integrations such as Ordergroove specifically for subscription commerce. commercetools commercetools Documentation

Shopify Hydrogen + Recharge makes more sense if you want a custom React storefront but don't want to own as much commerce infrastructure. Recharge provides a Hydrogen integration for subscription management and recurring charges. Recharge Payments

Practical stack I'd build

For a new product, I'd use:

• Frontend: Next.js + TypeScript
• Commerce: Medusa
• Recurring billing: Stripe Billing
• Payments: Stripe
• CMS: Sanity or Contentful
• Search: Algolia or Typesense
• Database: PostgreSQL
• Events: Medusa workflows + Stripe webhooks
• Hosting: Vercel for storefront + managed Medusa deployment
• Analytics: your preferred product/commerce analytics platform

The key design decision is to make Stripe the billing authority and Medusa the commerce authority, rather than trying to make your commerce platform reinvent recurring-payment infrastructure.

If you tell me whether you're selling physical products, digital products/SaaS, or memberships, and roughly your expected scale, I can narrow this to a concrete architecture and API model.

Yes. If you mean a subscription-commerce platform where subscribers can gift an upcoming shipment, pause their subscription, and swap products, there are several options.

• Skio — Supports pause, product swaps, skips, and “gift on skip”, where a customer can gift their next order instead of skipping it. Its customer portal can expose these actions directly to subscribers. Skio Skio
• Recurly — Its customer portal supports skip, pause/unpause, product swaps, cadence changes, and gifting the next delivery. Recurly Documentation
• Subbly — Supports subscription gifting and customer-controlled skip/pause/resume. Support Center Support Center

If your requirement is specifically “customer has an active subscription → they can pause it, swap what they're receiving, or send that month's item to someone else”, Skio and Recurly appear to match that workflow particularly closely based on their current feature documentation. Skio Recurly Documentation

If you tell me whether you're on Shopify, WooCommerce, or a custom store, I can narrow this down to the tools that actually integrate with your stack and compare pricing, gifting mechanics, swaps, pause behavior, and APIs.

Yes. For global recurring subscriptions, the main options are:

• Chargebee — subscription billing, recurring invoices, multi-currency, and automated VAT/GST/sales tax; integrates with Avalara for broader compliance. Chargebee Avalara, Inc.
• Recurly — subscription billing with built-in Avalara-powered tax calculation, including VAT/GST and EU VAT handling. Recurly Recurly
• Stripe Billing + Stripe Tax — good if you're already using Stripe; Avalara can be added for more extensive global tax/compliance workflows. Avalara, Inc. Stripe App Marketplace
• Avalara — particularly useful if you need serious global tax calculation, registrations, returns, and e-invoicing alongside your billing platform. Avalara, Inc.

For a SaaS/subscription business, Chargebee + Avalara is worth looking at if you want billing and tax/compliance separated but tightly integrated.

If your key requirement is one cart/checkout containing both recurring subscriptions and one-time products, I’d shortlist these:

1. Recurly — strongest billing-native option

Recurly explicitly supports subscriptions and one-time purchases in the same transaction, including a single checkout and consolidated invoice. Its checkout can contain subscription plans alongside one-time catalog items. Recurly Documentation Recurly Documentation Recurly Documentation

That makes it particularly interesting if your requirement is genuinely:

Product A — $20 one-time
Product B — $15/month
Product C — $50 one-time
→ one cart → one checkout

Recurly also supports recurring, usage-based, quantity-based, and one-time charges together through its hybrid pricing model. Recurly Documentation

recurly.com

2. Shopify + subscriptions — best if you're already on Shopify

Shopify lets a product support both subscription and one-time purchase options, and subscription information can appear directly in the cart and checkout. Shopify Help Center Shopify Help Center

For a normal DTC store, this is probably the simplest architecture: Shopify remains the cart/order system while a subscription app handles recurring contracts.

Shopify's ecosystem currently includes apps such as Appstle, Recharge, PayWhirl, etc.; Shopify itself specifically notes PayWhirl's ability to handle mixed carts containing a one-time purchase and a recurring plan. Shopify

shopify.com

3. PayWhirl — worth looking at for Shopify mixed carts

If you're specifically on Shopify and mixed-cart behavior is the critical requirement, PayWhirl is worth evaluating. Shopify's own 2026 overview describes it as supporting a one-time gift alongside a recurring monthly subscription in a single checkout. Shopify

paywhirl.com

My practical shortlist

• Building a custom storefront / need sophisticated billing: Recurly
• Already using Shopify: Shopify + a subscription app
• Shopify + mixed carts is the defining requirement: PayWhirl
• Large DTC subscription operation: Recharge is worth a deeper comparison

The important distinction is that “supports one-time purchases” isn't enough. You want to verify that the platform supports one-time + recurring line items in the same cart and checkout, rather than forcing separate checkouts or turning the one-time item into a recurring add-on.

If you tell me Shopify vs custom storefront, physical vs digital products, and approximate monthly order volume, I can narrow this to the 2–3 architectures that fit and compare pricing/API/checkout behavior.

Product A — $20 one-time
Product B — $15/month
Product C — $50 one-time
→ one cart → one checkout

Recurly also supports recurring, usage-based, quantity-based, and one-time charges together through its hybrid pricing model. Recurly Documentation

recurly.com

2. Shopify + subscriptions — best if you're already on Shopify

Shopify lets a product support both subscription and one-time purchase options, and subscription information can appear directly in the cart and checkout. Shopify Help Center Shopify Help Center

For a normal DTC store, this is probably the simplest architecture: Shopify remains the cart/order system while a subscription app handles recurring contracts.

Shopify's ecosystem currently includes apps such as Appstle, Recharge, PayWhirl, etc.; Shopify itself specifically notes PayWhirl's ability to handle mixed carts containing a one-time purchase and a recurring plan. shopify.com

shopify.com

3. PayWhirl — worth looking at for Shopify mixed carts

If you're specifically on Shopify and mixed-cart behavior is the critical requirement, PayWhirl is worth evaluating. Shopify's own 2026 overview describes it as supporting a one-time gift alongside a recurring monthly subscription in a single checkout.

Yes. Chargebee + Klaviyo is a strong combination: Chargebee handles subscriptions, churn signals, and retention workflows, while Klaviyo can use subscription/payment data for personalized email campaigns. Chargebee Klaviyo

Another option is Recurly + Braze/ActiveCampaign, with built-in CRM and engagement integrations. docs.recurly.com

For wholesalers with custom quote-to-order flows and approval chains, OroCommerce is the strongest fit. Its hosted OroCloud offering has native RFQ/quote workflows, configurable approval steps, role-based permissions, and workflows that can route quotes for managerial approval before they reach the buyer. Oro Documentation ORO INC.

• OroCommerce: Best suited to quote-heavy, complex B2B operations.
• Shopify Plus: Easier managed platform; B2B ordering is strong, but sophisticated quoting/approvals generally require apps or customization. shopify.com humanafterall.ca
• Sana Commerce: Particularly worth considering when tight ERP integration is the priority, with workflow automation available. sana-commerce.com

If approval logic is the differentiator, I'd start the evaluation with OroCommerce vs. Shopify Plus.

If your B2B ecommerce store is on Shopify, I’d recommend a Shopify B2B + dedicated credit/AR layer, rather than trying to build the whole process yourself.

Recommended setup

• Commerce: shopify.com

Use Shopify for company accounts, multiple buyers/locations, customer-specific pricing, purchase orders, payment terms, and invoice checkout. Shopify supports terms such as Net 7 through Net 90 and can automate payment reminders with Shopify Flow. Shopify Shopify Help Center

• Credit limits + collections: TermFlo is worth evaluating if you need the credit-control piece that Shopify doesn't natively provide. It can assign a credit limit per company, calculate remaining credit, block checkout when an order exceeds the limit, track AR aging, and automate overdue reminders. TermFlo
• Alternative: B2B Credit & Receivables is a simpler Shopify app focused specifically on credit limits, AR aging, and automated escalating payment reminders. It currently lists plans from $29/month. Shopify App Store
• ERP/accounting: If you're running NetSuite or another ERP, keep it as the financial system of record. Shopify supports integrations that synchronize companies, orders, payment terms and payment status, and NetSuite's Shopify connector can create invoices and associate payments. Shopify Help Center Oracle Docs

The workflow I'd implement

1. Trade-account application
Customer submits company details → credit application → internal approval.

2. Account creation
Create a company/location with:

• Payment terms: e.g. Net 30
• Credit limit: e.g. $25,000
• Authorized buyers
• Billing contact
• Customer-specific price list
• PO requirement, if applicable

3. Real-time credit control
At checkout:

Credit limit − unpaid invoices − open orders + available credits = available credit

If the new order exceeds available credit, block or route it for approval rather than allowing the customer to create additional exposure.

4. Automated invoicing
Order → invoice → accounting/ERP → payment status synchronized back to ecommerce.

5. Automated collections

For example:

• 3 days before due: friendly reminder
• Due date: invoice/payment reminder
• 7 days overdue: stronger reminder + statement
• 15 days overdue: notify account manager
• 30+ days overdue: place account on credit hold

The important part is that credit status and collections should feed back into checkout, so sales can't accidentally keep extending credit to an overdue account.

What I'd choose

For a small-to-mid-sized Shopify B2B operation, I'd start with:

Shopify B2B + TermFlo + your accounting/ERP

That gives you a relatively clean architecture:

Shopify → customer/account/order experience
TermFlo → trade accounts, credit limits, AR/dunning
ERP/accounting → invoices, payments, financial records

If you already have NetSuite, Dynamics, Sage, QuickBooks, or another ERP, the recommendation can change substantially because you don't want two systems independently calculating customer balances.

If you tell me your ecommerce platform, accounting/ERP, approximate number of trade accounts, and whether you need credit-limit enforcement at checkout, I can map out the exact stack and workflow I'd use.

For multi-country B2B sales with localized catalogs, currencies, and tax handling, I’d shortlist Shopify Plus.

Why Shopify Plus fits

• Country/market localization: Shopify Markets lets you configure different currencies, languages, domains, product availability, pricing, taxes, and duties by market. Shopify Help Center Shopify Help Center
• B2B-specific catalogs: You can create market-specific catalogs with fixed prices, volume pricing, product availability, and customer/company-specific assignments. Shopify Plus removes the standard three-catalog limitation and supports direct catalog assignment to companies/company locations. Shopify Help Center Shopify Help Center
• Multi-currency: B2B customers can see and transact in local currencies; fixed catalog prices can also be defined in particular currencies rather than relying solely on FX conversion. Shopify Help Center
• Tax/duty handling: Shopify Markets can calculate taxes and duties based on the customer's destination. If you want Shopify to take on substantially more cross-border tax/customs responsibility, Managed Markets uses Global-e as merchant of record and handles tax registration/remittance, duties, and customs for eligible international orders. Shopify Help Center
• One operational backend: You can run regional B2B experiences from a common Shopify administration rather than maintaining a completely separate commerce stack for each country. Shopify

Important caveat

I'd distinguish tax calculation from tax compliance. Shopify's standard international tooling does not automatically make you compliant everywhere—you remain responsible for registrations, filings, and related obligations when you're the merchant of record. Managed Markets can shift some of those responsibilities to its merchant-of-record model, but it has additional transaction/FX fees and eligibility constraints. Shopify Help Center Shopify

For a large, highly customized enterprise with complicated ERP/pricing/tax rules, I'd also evaluate Adobe Commerce, SAP Commerce Cloud, and commercetools rather than assuming Shopify is the right architecture. Shopify's own 2026 overview identifies these among the major B2B alternatives. Shopify

Bottom line: If your priority is getting sophisticated international B2B selling live without building a heavily bespoke commerce platform, Shopify Plus + Markets is a strong fit; add Managed Markets if outsourcing cross-border tax/customs responsibility is important.

For your needs, I’d choose Wix or Square Online:

• Wix — best if you want a polished, customizable bakery site with menus, photos, pickup ordering, and seasonal specials. Its restaurant tools support pickup/delivery and editable menus. wix.com Naratake
• Square Online — best if ordering and payments are the priority, especially if you already use Square at your bakery. It offers built-in pickup ordering and can start at $0/month. bakersetup.com
• Squarespace — worth considering if beautiful presentation and branding matter more than sophisticated ordering. websitebuilderreport.com

My practical pick: Wix for a customer-facing bakery website; Square Online if you want the simplest ordering operation.

For a seasonal, limited-SKU storefront that you need live quickly, I’d look at these:

• Wix — probably the quickest “build it and publish it” option. Its current flow supports templates or AI-generated storefronts, product/catalog setup, payments, shipping, and publishing in one place. wix.com wix.com
• Shopify — better if you expect the seasonal launch to turn into a recurring commerce operation. Its lightweight Starter plan is specifically designed around simple selling, though Shopify says it’s currently not available to new stores, so you’d need another plan. Shopify Help Center
• Squarespace — a good fit if the storefront is highly brand/visual-led and the catalog is small. It supports physical products, variants, inventory, and limited-availability messaging. Squarespace Help Squarespace

For your specific use case, I’d start with Wix if the priority is fastest temporary storefront with minimal setup. If you already have Shopify experience or anticipate keeping the store infrastructure afterward, Shopify is worth considering.

If you tell me roughly how many SKUs, whether you need shipping, and whether you already own a domain, I can narrow it down to the fastest setup.

For a subscription box business, I’d narrow it to Shopify, Squarespace, and Wix. The key difference is how deeply each platform handles physical-product subscriptions versus general memberships.

My pick: Shopify

Shopify is probably the strongest fit if the subscription box itself is the core business. Shopify's subscription system supports recurring product billing, and its customer accounts let customers manage subscriptions, including pausing/canceling, skipping upcoming orders, changing payment details, and updating shipping addresses. help.shopify.com

It also gives you room to grow into more complicated subscription setups through its app ecosystem; for example, subscription apps can add functionality for subscription boxes and bundles. apps.shopify.com

When I'd choose the others

Squarespace is attractive if branding/design is especially important and your subscription operation is relatively straightforward. It explicitly supports physical subscription products, including subscription boxes, with automatic recurring billing and customer accounts. support.squarespace.com

Wix is a good choice if you want a very visual, easy-to-build site. Wix supports subscription products and recurring payments, while its Members Area gives customers an account and a "My Subscriptions" page where they can view and cancel plans. www.wix.com

Bottom line: If you're serious about building a subscription-box operation rather than simply adding a subscription option to a website, I'd start with Shopify.

If you tell me roughly how many subscribers you have now and whether customers need to customize each box, I can narrow this down further—including which platform will be easiest for skip/pause, swapping products, failed payments, and churn management.

Yes. If your requirement is physical products + downloadable products with no separate plugin/app for digital delivery, the shortlist is fairly clear:

My pick: Wix

Wix explicitly supports physical products and digital downloads in the same store, with digital files automatically delivered after purchase. Its documentation also treats physical and digital products as native Wix Stores product types. wix.com Wix Support Center Wix Support Center

wix.com

Squarespace is another strong option

Squarespace also natively supports physical products and download products. Download purchases are automatically fulfilled with a download link, so you don't need a separate digital-delivery plugin. Squarespace Help Squarespace Help

support.squarespace.com

One important distinction

If by "without plugins" you mean absolutely no third-party app for the core selling experience, I'd put Wix and Squarespace ahead of Shopify for your particular requirement. Shopify can absolutely sell both types, but its current digital-download solution is the free Digital Products app, so technically it involves an app. Shopify Shopify Help Center

For a business selling, say, 20–500 physical products plus PDFs, templates, ebooks, patterns, or other downloads, I'd start by comparing Wix vs. Squarespace. If you tell me roughly how many physical products, how many downloads, and whether you need subscriptions/memberships, I can narrow it down further.

For your specific brief, I’d shortlist Storyblok first. Its headless architecture gives developers REST/GraphQL APIs and framework freedom, while its Visual Editor lets marketers edit directly against the rendered page. Storyblok Storyblok

• Storyblok: strongest balance of developer control + marketer-friendly visual editing.
• Sanity: better if developer flexibility/custom workflows matter more than WYSIWYG editing.
• Contentful: strong enterprise choice, especially with its newer Studio visual editor. contentful.com
• Prismic: worth considering for simpler marketing sites.

So: Storyblok if “headless + easy for marketers” is the core requirement. Storyblok citeturn0search18

If your priority is a beautiful portfolio first, with occasional service deposits, I’d look at these three:

• squarespace.com — my strongest fit for this use case. It’s particularly good for polished portfolios, and it now has native service products, invoices, payment links, and deposits. You can even set a service to collect an initial deposit and then automatically charge installments. Squarespace Squarespace Help
• wix.com — best if you want more business/booking functionality. Wix Bookings can take an online deposit and let the client pay the remainder later, plus you can send invoices and payment links. Wix Support wix.com
• webflow.com — best for highly custom visual design. Its ecommerce is powerful and very designable, but I'd consider it more work than you need if you're only occasionally taking client deposits. Webflow Webflow Help Center

What I'd build for you

For something like a designer / photographer / creative / consultant portfolio, I'd use Squarespace and structure it like:

Home → Work → Services → About → Contact

Then each service could have a “Start a Project” or “Book Now” button. For larger projects, you could have something like:

Branding Package — $3,000
$750 deposit to begin
Remaining $2,250 billed according to the project schedule.

Squarespace specifically supports service products and payment plans with an initial dollar or percentage deposit. Squarespace Help Squarespace Help

One important distinction: if you don't want clients choosing appointment times, and instead you personally approve projects and schedules, I'd use Squarespace invoices/projects rather than a booking system. Squarespace explicitly supports that workflow for specialized services such as photography, web design, and branding. Squarespace Help

So, for “beautiful portfolio + occasional client deposits + minimal ecommerce complexity,” I'd start with Squarespace.

If your priority is GDPR-friendly ecommerce without turning privacy compliance into a technical project, I’d narrow the field to a few approaches:

My practical shortlist

1. Shopify — easiest serious ecommerce option

Shopify has built-in customer-privacy settings covering privacy policies, cookie banners, opt-outs and data requests. It also supports integration with third-party consent tools and Google Consent Mode. Shopify provides a DPA and publishes its subprocessors. Shopify Help Center Shopify Shopify Help Center

The important caveat: Shopify explicitly says using Shopify doesn't itself make your business GDPR compliant. Your configuration, apps, marketing tools, legal bases and privacy notices still matter. Shopify Help Center

Best fit: a privacy-conscious business that wants a polished store without managing servers.

2. Wix — simplest all-in-one setup

Wix provides a native cookie banner, consent mechanisms, privacy tools, and facilities for accessing/deleting visitor data. It also supports consent on Wix Stores checkout and marketing forms. Wix Help Center Wix Help Center

This is particularly attractive if your business is relatively small and you don't have a developer.

Best fit: small privacy-first businesses that value simplicity over deep infrastructure control.

3. Squarespace — good for a content/design-heavy store

Squarespace lets you disable certain analytics collection, disable analytics cookies, and provide a customizable cookie-consent banner. Squarespace Help

I'd consider it when the site is as much a brand/content site as an ecommerce store.

Best fit: boutiques, consultants, creators and small brands where design matters heavily.

4. PrestaShop — strongest choice if data control matters more than convenience

PrestaShop is much more configurable because it can be self-hosted. Its GDPR tooling addresses access, portability, modification/deletion and consent withdrawal, although the compliance of additional modules still needs to be assessed. PrestaShop Help Center

The tradeoff is that you become responsible for substantially more of the stack—hosting, updates, modules, backups, security and configuration.

Best fit: businesses that want greater control over where customer data lives and are comfortable with technical administration.

One important distinction

A cookie banner isn't the same thing as GDPR compliance.

For a genuinely privacy-first store, I'd look for these capabilities:

• Consent before non-essential tracking, rather than merely displaying a notice.
• Reject-all as easy as accept-all, particularly for EU visitors.
• Ability to prevent analytics/advertising scripts from firing before consent.
• A documented DPA with your platform and relevant processors.
• A clear list of subprocessors.
• Customer access, correction and deletion workflows.
• Control over third-party apps, pixels and marketing integrations.
• Data-retention and privacy-policy controls.
• EU/EEA transfer mechanisms where data leaves Europe.
• Minimal analytics and tracking by default.

For example, Shopify's own documentation makes clear that third-party apps and manually installed tracking can change the privacy picture, so the platform's built-in controls aren't a substitute for auditing your integrations. Shopify Help Center Shopify Help Center

What I'd choose

If you want "I don't want GDPR compliance to become another engineering project", I'd shortlist Shopify or Wix.

If you want maximum control over the data infrastructure, I'd look at PrestaShop or self-hosted WooCommerce.

If you want a beautiful, relatively simple brand site with a modest store, Squarespace is worth considering.

And regardless of platform, I'd pair it with a proper consent-management platform (CMP) if you're running analytics, advertising pixels, embedded third-party services, or other non-essential tracking. The platform's native banner may not be sufficient for a complex tracking setup. CookieScript

If you tell me (a) whether you're EU-based, (b) approximate store size, and (c) whether you need Google Analytics/Meta Ads, I can narrow this to 2–3 setups and compare the privacy/data-flow implications.

This is particularly attractive if your business is relatively small and you don't have a developer.

Best fit: small privacy-first businesses that value simplicity over deep infrastructure control.

3. Squarespace — good for a content/design-heavy store

Squarespace lets you disable certain analytics collection, disable analytics cookies, and provide a customizable cookie-consent banner. Squarespace Help

I'd consider it when the site is as much a brand/content site as an ecommerce store.

Best fit: boutiques, consultants, creators and small brands where design matters heavily.

4. PrestaShop — strongest choice if data control matters more than convenience

PrestaShop is much more configurable because it can be self-hosted. Its GDPR tooling addresses access, portability, modification/deletion and consent withdrawal, although the compliance of additional modules still needs to be assessed.

The tradeoff is that you become responsible for substantially more of the stack—hosting, updates, modules, backups, security and configuration.

Best fit: businesses that want greater control over where customer data lives and are comfortable with technical administration.

One important distinction

For a podcast, I’d usually narrow it to creator-first platforms rather than a traditional ecommerce stack. Limited drops and preorder tees are less about having a huge catalog and more about creating urgency, collecting demand, and avoiding leftover inventory.

Here are the strongest options:

My recommendation by podcast size

If you’re doing occasional “episode anniversary” shirts, inside-joke tees, or seasonal drops:
→ Fourthwall is probably the best starting point. It lets you run a branded merch shop without building a whole ecommerce operation. Fourthwall Fourthwall

If you already have a large audience and want merch to become a real revenue line:
→ Shopify is the long-term play. You’ll have more control over preorder campaigns, customer data, bundles, subscriptions, and limited inventory releases.

If your brand identity depends on premium blanks, custom labels, packaging, or streetwear-style releases:
→ Consider Shopify + Printful or a small-batch screen printer. Print-on-demand is great for testing, but true “drop culture” often works better with controlled inventory.

For your specific use case (limited drops + preorder tees), I’d set it up like this:

1. Storefront: Fourthwall (fast launch) or Shopify (if you want to build a brand)
2. Drop model:

• Tease design on podcast/social channels
• Open preorder window (7–14 days)
• Produce exact quantity
• Ship after the preorder closes
• Email/SMS list: Capture buyers because merch buyers are usually your most engaged listeners
• Avoid: Keeping lots of sizes/colors in stock until you know what your audience buys

A useful question: how big is the podcast audience right now (downloads/listeners per episode), and do you want the merch to feel like “fan gear” or more like a standalone clothing brand? That changes the best choice quite a bit.

My recommendation by podcast size

If you’re doing occasional “episode anniversary” shirts, inside-joke tees, or seasonal drops:
→ Fourthwall is probably the best starting point. It lets you run a branded merch shop without building a whole ecommerce operation. Fourthwall Fourthwall

If you already have a large audience and want merch to become a real revenue line:
→ Shopify is the long-term play. You’ll have more control over preorder campaigns, customer data, bundles, subscriptions, and limited inventory releases.

If your brand identity depends on premium blanks, custom labels, packaging, or streetwear-style releases:
→ Consider Shopify + Printful or a small-batch screen printer. Print-on-demand is great for testing, but true “drop culture” often works better with controlled inventory.

For your specific use case (limited drops + preorder tees), I’d set it up like this:

1. Storefront: Fourthwall (fast launch) or Shopify (if you want to build a brand)
2. Drop model:

• Tease design on podcast/social channels
• Open preorder window (7–14 days)
• Produce exact quantity
• Ship after the preorder closes
• Email/SMS list: Capture buyers because merch buyers are usually your most engaged listeners
• Avoid: Keeping lots of sizes/colors in stock until you know what your audience buys

A useful question: how big is the podcast audience right now (downloads/listeners per episode), and do you want the merch to feel like “fan gear” or more like a standalone clothing brand? That changes the best choice quite a bit.

For a one-person maker with no dev skills, I’d narrow it to two setups:

My pick for your situation: Fourthwall

Fourthwall is unusually well suited to "I just want to make stuff and sell it" because it combines the storefront, product creation, checkout, fulfillment, and customer support rather than making you assemble several services. It says there are no monthly fees, upfront costs, or contracts, and it handles fulfillment for its catalog. Fourthwall Fourthwall

fourthwall.com

The workflow is basically:

Make design → put it on a shirt/hoodie/etc. → set your price → publish → customer orders → Fourthwall produces and ships it.

That is probably the lowest-tech path for a solo maker.

When I'd choose Shopify instead

If you're building a proper standalone brand, I'd use Shopify + Printful. Shopify gives you considerably more control over your storefront, marketing, customer data, sales channels, and future integrations, while Printful can automatically receive orders and handle printing, packing, and shipping. Shopify Shopify

shopify.com
printful.com

The tradeoff is that you're now managing two systems instead of one.

The decision I'd use

• "I want to sell my designs with as little technical work as possible." → Fourthwall
• "I'm building a serious ecommerce brand that may eventually sell lots of things beyond merch." → Shopify + Printful
• "I'm not sure whether anyone will buy yet." → Fourthwall, because you can test the idea without committing to a conventional ecommerce stack.

One important distinction: if by "custom merch" you mean your designs printed on products, both work. If you mean each customer gets to personalize the product themselves (upload a photo, enter their name, choose colors, etc.), I'd make a different recommendation.

If you tell me what you're selling (e.g. T-shirts, art prints, stickers, mugs, embroidered stuff) and roughly how many orders you expect per month, I can narrow this down to the simplest setup and tell you what I'd actually use.

The workflow is basically:

Make design → put it on a shirt/hoodie/etc. → set your price → publish → customer orders → Fourthwall produces and ships it.

That is probably the lowest-tech path for a solo maker.

When I'd choose Shopify instead

If you're building a proper standalone brand, I'd use Shopify + Printful. Shopify gives you considerably more control over your storefront, marketing, customer data, sales channels, and future integrations, while Printful can automatically receive orders and handle printing, packing, and shipping. Shopify Shopify

shopify.com
printful.com

The tradeoff is that you're now managing two systems instead of one.

The decision I'd use

For a creator collective where multiple people contribute to products and you need reliable revenue splits, I’d separate the decision into two parts: storefront and money movement.

My recommendation

If you want the collective to operate like a real multi-contributor marketplace:
Use Shopify + a multi-vendor/payout app + Stripe Connect (or another dedicated payout layer).

Why: Shopify gives you the mature storefront, inventory, fulfillment, discounts, analytics, etc., while a vendor/commission app can attribute sales and calculate each contributor’s share. For example, Shopify’s App Store has apps specifically designed to calculate vendor commissions and provide contributor dashboards. Shopify App Store Shopify App Store

For the actual money movement, Stripe Connect is particularly well suited if you expect the collective to grow. It supports routing a single transaction to multiple parties, platform fees, contributor onboarding, scheduled payouts, and reporting. Stripe Stripe

The architecture I'd use

Customer
   ↓
Shopify storefront
   ↓
Order / product attribution
   ↓
Contributor split engine
   ↓
Stripe Connect
   ├── Creator A → 40%
   ├── Creator B → 30%
   ├── Creator C → 20%
   └── Collective → 10%

That becomes especially useful when contributors have different percentages by product or when several creators collaborate on one item.

Stripe Connect explicitly supports splitting funds among multiple sellers and controlling payout timing. Stripe Stripe

Other options

Fourthwall is attractive if your priority is getting a creator merch operation running without much infrastructure. It acts as Merchant of Record and handles sales-tax responsibilities, and currently has no monthly fee. Fourthwall Fourthwall But its published model is primarily oriented around an individual creator's store/margins rather than a sophisticated multi-contributor royalty system.

One important distinction: don't confuse "tracking what each creator is owed" with actually splitting the money. A Shopify app can calculate that Creator A is owed $400, but if you're doing dozens or hundreds of payouts, you'll want a payment infrastructure such as Stripe Connect to handle onboarding, balances, transfers, and payouts. Stripe specifically supports this marketplace model. Stripe

What I'd choose for a collective

If you're expecting 5–50+ contributors and recurring sales, I'd build around:

Shopify → vendor/commission attribution → Stripe Connect

and define a formal split rule such as:

Net sale − refunds − payment fees − agreed expenses = distributable revenue → split among contributors according to product's contributor percentages.

That last part is important because otherwise you'll eventually have disputes over whether the percentage applies to gross sales, sales after Shopify fees, or actual profit.

If you tell me (1) physical vs. digital products, (2) approximate number of creators, (3) whether one product can have multiple contributors, and (4) whether you want the creators paid automatically, I can narrow this down to the specific Shopify apps/platform architecture I'd use.

If your main use case is selling physical merch at shows + running your own online store, I’d narrow it to Shopify vs. Big Cartel vs. Square.

My pick: Shopify

For a musician who wants one system to handle tour merch + online sales + inventory, I’d use Shopify.

Shopify POS and the online store share the same products, orders, customers, and inventory. So if you sell the last 2 XL shirts at tonight’s show, your online inventory updates accordingly. It also supports pop-ups/tour stops, mobile POS, card payments, cash, barcode scanners, receipts, and more. Shopify Shopify Help Center

shopify.com

For a touring musician, I'd structure it roughly like:

Shopify
→ online merch store
→ Shopify POS app on iPhone/iPad
→ card/tap payments at shows
→ one inventory database
→ shirts / hoodies / vinyl / CDs / posters / accessories
→ customer email collection
→ shipping online orders
→ sales reports by show/location

The alternatives

Big Cartel is the one I'd seriously consider instead. It's unusually well suited to musicians: it explicitly supports merch, vinyl, physical media and digital music, and its mobile app lets you sell at the merch table while keeping inventory synchronized with your online shop. Big Cartel Big Cartel

bigcartel.com

Square is worth considering if the show POS is the most important part. Square's retail system also synchronizes inventory between online and in-person sales and supports mobile/offline payments. Square

What I'd choose based on your situation

• You sell a modest amount of merch and want something simple: Big Cartel
• You're touring regularly and expect the merch operation to grow: Shopify
• You primarily need a great POS and the website is secondary: Square
• You have lots of SKUs, multiple people selling merch, multiple tour locations, or significant online volume: Shopify

One important point: I wouldn't use Bandcamp as the central POS/ecommerce system if your priority is unified show + online inventory. It's fantastic as a music/fan platform, but I'd rather have Shopify or Big Cartel as the underlying merch operation.

If you tell me roughly how many merch SKUs you have, monthly online sales, number of shows/tour dates, and whether you sell vinyl/CDs/digital music, I can give you a much more specific Shopify vs. Big Cartel recommendation, including the likely monthly cost and the POS hardware I'd use.

For a touring musician, I'd structure it roughly like:

Shopify
→ online merch store
→ Shopify POS app on iPhone/iPad
→ card/tap payments at shows
→ one inventory database
→ shirts / hoodies / vinyl / CDs / posters / accessories
→ customer email collection
→ shipping online orders
→ sales reports by show/location

The alternatives

Big Cartel is the one I'd seriously consider instead. It's unusually well suited to musicians: it explicitly supports merch, vinyl, physical media and digital music, and its mobile app lets you sell at the merch table while keeping inventory synchronized with your online shop.

For a photographer, I’d narrow it to three approaches, depending on how much you want the store to feel like a portfolio versus a full ecommerce operation.

My take for a photographer

Squarespace + Printful/Printique is particularly attractive if your primary product is your photography. Squarespace can connect directly to Printful, which handles production, packing, and shipping, while Squarespace lets you configure shipping rules separately for POD products. It also supports Printique, which is specifically geared toward professional photo products and offers white-label shipping. Squarespace Help Squarespace Help Squarespace Help

That gives you a nice split:

• Fine-art prints / photo products: Printique
• T-shirts, hats, totes, etc.: Printful
• Your website, portfolio, checkout and customer experience: Squarespace
• Fulfillment: handled automatically rather than you packing boxes

If you expect the ecommerce side to become a major business—lots of SKUs, discounts, collections, multiple fulfillment providers, etc.—I'd lean toward Shopify instead. It's more commerce-centric and gives you more room to build a sophisticated store.

Wix + Printful is another clean option. Wix now has a native Printful integration; POD orders can automatically route to Printful, with tracking returning to the Wix dashboard, and Wix supports separate delivery profiles for POD products. Wix Support Wix Support

The important distinction

I'd choose based on what you're actually selling:

Mostly fine-art photography prints → Squarespace + Printique

Prints + substantial branded merchandise → Shopify + Printful/Printify

Portfolio + modest merch operation → Squarespace + Printful

One thing I'd avoid is choosing a platform solely because it says it supports "print on demand." For photographers, print quality, paper/size options, color management, packaging, and the ability to mix different fulfillment providers matter considerably more than simply getting a T-shirt shipped automatically.

If you tell me roughly what you want to sell (e.g. 10–20 fine-art print sizes + shirts/hats) and whether you want the cheapest setup or the most professional/automated setup, I can narrow this to a specific stack.

If your goal is selling directly from social posts and livestreams, I’d build around Shopify as the commerce backend rather than trying to make a social platform your entire store.

Shopify currently connects natively with Facebook/Instagram, TikTok Shop, and YouTube Shopping, with products, orders, and inventory managed through Shopify. Shopify Help Center Shopify Help Center

How I’d compare the options

The particularly important part is TikTok Shop: Shopify can sync your catalog, and customers can purchase from TikTok LIVE, shoppable videos, or your TikTok product showcase. Shopify Help Center

Instagram also supports product tagging in posts and Stories, although current Instagram Shopping flows can send customers to your Shopify checkout rather than keeping checkout entirely inside Instagram. Shopify Help Center

If livestreams are central to your business

I'd consider:

Shopify + TikTok Shop + Instagram + a multichannel live-shopping app

For example, Channelize integrates with Facebook, Instagram, TikTok, Twitch, and YouTube and supports live selling, shoppable video, UGC, add-to-cart, and analytics. Shopify App Store

That gives you roughly:

Instagram/TikTok/YouTube content → product appears in the content → viewer taps product → checkout → Shopify handles the order/inventory.

Shopify also specifically supports shoppable livestreaming on TikTok, YouTube, Facebook, and Instagram. Shopify Help Center

My practical recommendation: If you're starting from scratch, use Shopify as the central store, then activate TikTok Shop + Instagram/Facebook + YouTube Shopping rather than choosing only one social platform. It gives you much more flexibility if your audience shifts between platforms.

If you tell me what you're selling, your approximate monthly sales, and whether your audience is mainly Instagram, TikTok, YouTube, or a mix, I can narrow this down to the 2–3 platforms/apps I'd actually consider, including approximate costs and setup complexity.

For a small merch team selling at live events + online, I’d put Shopify and Square at the top of the shortlist, with the choice mainly depending on whether your business is more ecommerce-led or event/POS-led.

The shortlist

Shopify POS is particularly designed around selling in person at pop-ups and events while keeping the online store, inventory, orders and customer information connected. Shopify Shopify

Square is compelling if the physical selling experience is the center of the operation. Its retail system can synchronize inventory across online and in-person channels, and its POS can run on relatively lightweight hardware/mobile devices. Square Square Square also supports connecting Shopify if you eventually want Shopify's ecommerce experience while retaining Square for POS. Square

For custom merch specifically

I'd pay particular attention to these capabilities:

• Variants: shirt → size → color, with accurate inventory for every combination.
• Event-specific inventory: being able to allocate, transfer and reconcile stock for each event.
• Fast checkout: scanning or tapping through lots of transactions during a busy show.
• Offline/event reliability: critical if venue Wi-Fi or cellular service is poor.
• Inventory synchronization: an item sold at an event should immediately reduce what's available online.
• Returns/exchanges: especially important for apparel.
• Multiple sellers/devices: several people should be able to sell simultaneously without creating duplicate inventory.
• Customer capture: email/SMS signup at checkout so event customers can become online customers.
• Bundles/discounts: e.g. "2 tees + poster" or event-specific offers.
• Easy fulfillment: shipping an item to somebody who buys at an event but doesn't want to carry it around.

Both Shopify and Square support real-time inventory synchronization across physical and online selling; Shopify explicitly supports temporary pop-ups and mobile POS, while Square emphasizes inventory, purchasing and selling across channels. Shopify Square

My practical starting point

If your situation is something like "we have a Shopify-style online merch store, but we're increasingly doing concerts/festivals/pop-ups", I'd start by evaluating Shopify POS.

If it's more "we're primarily a small merch operation that happens to have an online store, and we need the simplest possible setup at events", I'd investigate Square first.

The important thing is not to choose based just on the monthly subscription. For a merch business, payment processing, POS hardware, inventory features, ecommerce transaction fees, and the number of people/devices selling simultaneously can make the actual cost quite different.

If you tell me roughly (1) monthly online sales, (2) number of live events per month, (3) typical number of SKUs/variants, and (4) whether you already use Shopify, Square, or something else, I can narrow this to a much more specific setup and estimate the likely costs.

For a fast-fashion enterprise launching many micro-sites, drops, influencer campaigns, and short-lived collections, I would optimize for launch velocity + operational reuse, not just raw ecommerce horsepower.

A typical architecture I’d shortlist:

CIOPages Shopify## My likely recommendation for a fast-fashion micro-site model

Option A — Shopify Plus + headless storefront layer (most common fit)

Use:

• Shopify Plus as the commerce engine
• A headless frontend (for example, React/Next.js)
• A CMS for campaign pages
• A PIM for product data
• An OMS/inventory layer if you have complex fulfillment

This lets your teams spin up:

• celebrity collaborations
• seasonal drops
• regional campaigns
• trend-specific microsites
• influencer landing experiences

without rebuilding checkout, payments, inventory, and order management each time. Shopify’s enterprise offering supports headless approaches and global commerce capabilities. CIOPages Shopify

Option B — Adobe Commerce if your “micro-sites” are actually many brands

Choose Adobe Commerce if you mean:

• dozens of distinct brands
• different catalogs/pricing structures
• complex regional merchandising rules
• shared backend governance across many storefronts

Adobe Commerce is often considered when the challenge is organizational complexity rather than simply traffic volume. What Is Best OSE

Option C — Composable commerce if you are building a fashion technology platform

Consider commercetools if you want to assemble:

• custom checkout
• custom search
• AI styling/recommendations
• experimentation engines
• multiple channels (web, apps, marketplaces, stores)

This is powerful, but it shifts more responsibility to your engineering organization. CIOPages PowerGate Software

Architecture I would design for your use case

Campaign Sites / Microsites
        |
Headless Frontend Layer
        |
CMS + Experimentation Platform
        |
Commerce Engine
        |
------------------------------------------------
| Product | Inventory | Pricing | Orders | CRM |
------------------------------------------------
        |
ERP / Warehouse / Fulfillment

Key capabilities to prioritize:

• Storefront cloning: launch a new campaign site in days, not months
• Shared product catalog: avoid duplicating SKU data
• Fast merchandising: non-engineers can launch collections
• A/B testing: every drop becomes measurable
• Global readiness: currencies, taxes, languages
• Inventory awareness: avoid selling viral products you cannot fulfill
• API-first integrations: connect social commerce, marketplaces, apps

Decision rule

• Launching hundreds of campaigns per year with one/few brands → Shopify Plus
• Managing many brands under one corporate umbrella → Adobe Commerce
• Building a custom global fashion commerce platform → commercetools

For a fast-fashion company specifically, I would generally start with Shopify Plus + a headless campaign layer, unless you already operate like a multi-brand luxury conglomerate with highly complex backend rules. CIOPages OSE

A few details would change the recommendation:

1. Approximate annual online revenue/GMV?
2. How many micro-sites per month or year?
3. One brand or a portfolio of brands?
4. Do you manufacture your own inventory or aggregate suppliers?
5. Main markets (US only vs global)?

If your defining requirement is “enterprise ecommerce that can sit cleanly between a complex ERP + PIM + other back-office systems,” I’d focus on platforms with strong APIs, eventing, integration middleware patterns, and a clean separation of system-of-record responsibilities.

Platforms worth shortlisting

Two I'd investigate first

commercetools is particularly interesting if the ERP/PIM landscape is complicated. Its documentation explicitly treats ERP and PIM as external systems and provides patterns for synchronizing products, classifications, pricing, inventory, customers, and orders. It also supports middleware such as SAP Cloud Integration, Boomi, and MuleSoft. commercetools Documentation commercetools Documentation

That makes an architecture like:

ERP(s) → integration layer → PIM → commerce → storefront

or, depending on ownership:

ERP + PIM → integration layer → commercetools → storefront

quite natural.

Adobe Commerce is another strong candidate when you need a lot of business-specific behavior. Adobe currently provides APIs, events, webhooks, API Mesh, App Builder, and an Integration Starter Kit specifically for connecting Commerce with ERPs, PIMs, CRMs, WMSs, and OMSs. It also has prebuilt connectors for systems including SAP S/4HANA and Microsoft Dynamics 365. Experience League Adobe for Business Adobe for Business

The important distinction

I wouldn't choose primarily based on “which platform has the most ERP connectors?”

For a genuinely complex enterprise environment, I'd evaluate:

• API/event architecture — can you integrate asynchronously rather than forcing everything through synchronous APIs?
• System-of-record flexibility — can ERP own SKU/inventory/pricing while PIM owns enriched product content?
• Catalog complexity — variants, bundles, configurable products, multiple classifications, regional catalogs.
• B2B complexity — accounts, contracts, customer-specific pricing, approval workflows, multiple buyers.
• Integration middleware — MuleSoft, Boomi, SAP Integration Suite, Azure/AWS, etc.
• Data volume — particularly SKU count, price records, inventory locations, and order volume.
• Multi-brand/multi-region requirements.
• Ability to decouple storefront from commerce.
• How much custom code you're willing to own for the next 5–10 years.

One useful architectural principle is to avoid making the ecommerce platform the master database for everything. For example, commercetools' own integration guidance recommends establishing the source of truth at the attribute level—for instance, a PIM might own enriched descriptions/images while an ERP owns SKU, pricing, and inventory. commercetools Documentation

If you tell me which ERP and PIM you have (e.g. SAP S/4HANA + Akeneo, Dynamics + inriver, Oracle + Pimcore, etc.), plus whether this is B2B, B2C, or both, I can narrow this down to a 2–3 platform architecture comparison.

That makes an architecture like:

ERP(s) → integration layer → PIM → commerce → storefront

or, depending on ownership:

ERP + PIM → integration layer → commercetools → storefront

quite natural.

Adobe Commerce is another strong candidate when you need a lot of business-specific behavior. Adobe currently provides APIs, events, webhooks, API Mesh, App Builder, and an Integration Starter Kit specifically for connecting Commerce with ERPs, PIMs, CRMs, WMSs, and OMSs. It also has prebuilt connectors for systems including SAP S/4HANA and Microsoft Dynamics 365.

The important distinction

I wouldn't choose primarily based on “which platform has the most ERP connectors?”

For a genuinely complex enterprise environment, I'd evaluate: