Answers that do not mention BigCommerce

For a small handmade-goods shop, I’d pick shopify.com if your priority is an easy, hosted storefront that can grow with you.

• Shopify — best overall for selling: No coding is required, and it includes hosting, security, product management, payments, themes, and drag-and-drop editing. Shopify Shopify Help Center
• wix.com — best for simplicity/design: Its no-code editor is particularly approachable, with templates and AI tools. Hosting is included, and you can add inventory, checkout, shipping, and other store functions. wix.com wix.com

My recommendation: Start with Shopify if you expect your catalog or sales to grow; choose Wix if you want the easiest visual website-building experience and have a relatively small catalog.

If you tell me roughly how many products you sell and your monthly budget, I can recommend the specific plan and give you a simple setup path.

For a brick-and-mortar + online business, I’d shortlist these:

My recommendation

If you're primarily retail + Shopify: go with Shopify POS. It's simpler and avoids introducing another inventory master system. Shopify specifically supports multi-location inventory and real-time synchronization between POS, online, warehouses, and sales channels. Shopify

If you sell across Shopify + Amazon/eBay/Walmart + physical stores + wholesale, I'd lean toward Cin7 Core. It gives you a centralized inventory/order layer rather than making your ecommerce platform responsible for everything. Cin7 says it synchronizes inventory across ecommerce, marketplaces, POS, and warehouses in real time. Cin7 Cin7

If you're already operationally complex—multiple warehouses, 3PLs, EDI, multiple legal entities, sophisticated fulfillment—look at Cin7 Omni rather than Core. Cin7

The key question is what channels you're actually syncing. If you tell me your stack (e.g. Shopify + physical store + Amazon + eBay + QuickBooks, number of locations, and approximate SKU count), I can narrow this to the best 2–3 options and explain the architecture I'd use.

For an artisan marketplace with many independent sellers (similar to Etsy), the best platform depends on your expected scale, budget, and how much customization you need. The key features you should prioritize are:

• Seller onboarding and approval workflows
• Individual artisan storefronts
• Vendor dashboards for products/orders
• Commission management
• Split payments and seller payouts
• Reviews/ratings
• Inventory management
• Shipping options per seller
• Messaging between buyers and artisans
• Ability to scale to hundreds or thousands of sellers

Here are the strongest options:

Sharetribe Shopify### My recommendations by scenario

1. You are starting an artisan marketplace (10–500 sellers)

• Choose Sharetribe if you want to validate the idea quickly.
• Choose CS-Cart Multi-Vendor if you already know you want a full Etsy-like commerce platform.

G2 Sharetribe2. You expect thousands of artisans

• Start with CS-Cart, custom WooCommerce, or a headless commerce approach.
• Plan for stronger seller tools, automated payouts, seller analytics, and customer support workflows.

3. You want a premium handmade-goods brand
A good architecture would be:

• Frontend: custom storefront experience
• Marketplace engine: CS-Cart / Sharetribe / custom backend
• Payments: Stripe Connect
• Shipping: ShipStation or similar
• Seller onboarding: application + verification workflow

What I would pick for an artisan marketplace

For a new Etsy-style business:

1. CS-Cart Multi-Vendor — best overall fit for a product-based artisan marketplace.
2. Sharetribe — best if you want to launch fast and prove demand.
3. WooCommerce + Dokan/WCFM — best if you want maximum ownership and have WordPress expertise.

Sharetribe twosided.ioIf you tell me:

• expected number of artisans (100, 1,000, 10,000+)
• physical products vs custom commissions/services
• your budget range
• whether you need mobile apps

I can narrow this to the best platform architecture.

For a one-person print-on-demand shop, I’d optimize for low fixed costs + minimal maintenance, rather than choosing the most powerful ecommerce platform.

My recommendation

Start with Etsy + Printful if your priority is getting sales with the least upfront cost.

• Etsy gives you an existing marketplace and doesn't require you to build/market a standalone store from scratch.
• Printful has a $0/month entry plan, and you pay for fulfillment only when you get an order. It integrates directly with Etsy, including product publishing and order fulfillment. Printful Printful Help Center
• Your main costs become Etsy's listing/transaction/payment fees plus Printful's product and shipping costs, rather than another monthly ecommerce subscription.

The downside is that you're building on Etsy's marketplace, rather than owning the customer relationship and storefront as completely as you would with your own site.

If you want your own website

I'd choose Shopify + Printful once you have evidence that people want your products.

Shopify is more expensive, but it's considerably more capable as a long-term branded store. Printful integrates directly with it and automatically sends orders for fulfillment. Printful Help Center Printful

For a one-person operation, though, I wouldn't start there unless you already have an audience. You're paying a monthly platform fee before you've proven the business.

One interesting ultra-cheap option

Printful Quick Stores are worth looking at if you're in the U.S. and primarily want a simple storefront. Printful says Quick Stores let you sell directly through a shareable store without a separate ecommerce platform, and they're aimed specifically at people who want a simple starting point. Printful Help Center

That could make your initial software cost essentially $0/month, although you don't get the marketplace discovery of Etsy or the full capabilities of Shopify.

What I'd do personally

One caveat: Big Cartel looks attractive because of its free/cheap plans, but its Printful integration currently requires a paid Big Cartel plan, so it isn't necessarily the bargain it first appears to be. Big Cartel

Bottom line: If you're literally starting from zero with a handful of POD designs, I'd go Etsy + Printful Free. Don't spend $30–$50/month on ecommerce software until you've demonstrated that customers will actually buy.

If you tell me roughly what you're selling (T-shirts, mugs, posters, stickers, etc.) and whether you already have an audience, I can give you the cheapest setup and estimate the break-even sales/month for Etsy vs. Shopify.

If your priority is developer-friendly mobile commerce integration, I’d put Shopify first for most teams.

My ranking

Why I'd choose Shopify

Shopify has unusually direct support for the exact architecture you're describing: native iOS/Android/React Native UI + Storefront API + embedded checkout. Its current mobile documentation specifically supports product browsing, search, cart management, and checkout in native apps. Shopify Shopify

The typical flow is:

Mobile app → Storefront API → cart → checkoutUrl → Checkout Kit → Shopify payment/order

Checkout Kit handles the checkout experience inside the app, while the Storefront API handles products, search, and carts. Shopify also provides official mobile libraries/examples and recommends Apollo for typed GraphQL queries and caching. Shopify Shopify

That's a big advantage over platforms where you have to assemble the commerce backend, checkout, payments, and mobile integration yourself.

One caveat: Shopify's Storefront API is GraphQL-only, so your team needs to be comfortable with GraphQL. Shopify

When I'd pick something else

• Medusa — choose this if your app is the product and you want maximum control over pricing, checkout, catalog logic, and backend architecture. It's a stronger choice when you're willing to own more infrastructure.
• Saleor — attractive if your team strongly prefers GraphQL and wants an API-first/headless backend.
• CommerceTools — I'd consider it for a large enterprise where composable commerce and complex integrations matter more than implementation simplicity.
• WooCommerce — sensible if the business already runs on WordPress/WooCommerce, but I wouldn't start a new mobile-first commerce product with it solely for its API.

Bottom line: for a new mobile storefront, I'd start with Shopify unless you have a strong reason to own the entire commerce backend. The combination of Storefront API + Checkout Kit is currently one of the cleanest mobile-commerce paths. Shopify Shopify

If you tell me whether you're using React Native, Flutter, Swift/Kotlin, or Expo, I can narrow this down further and compare the actual SDK/API experience between Shopify, Medusa, Saleor, and CommerceTools.

The typical flow is:

Mobile app → Storefront API → cart → checkoutUrl → Checkout Kit → Shopify payment/order

Checkout Kit handles the checkout experience inside the app, while the Storefront API handles products, search, and carts. Shopify also provides official mobile libraries/examples and recommends Apollo for typed GraphQL queries and caching.

That's a big advantage over platforms where you have to assemble the commerce backend, checkout, payments, and mobile integration yourself.

One caveat: Shopify's Storefront API is GraphQL-only, so your team needs to be comfortable with GraphQL.

When I'd pick something else

For a small handmade-goods shop where you’re not tech-savvy, I’d choose Shopify for your first serious store.

shopify.com is built specifically around selling: products, payments, inventory, shipping, orders, marketing, and even in-person sales can all live in one dashboard. You don't need to code, and Shopify currently offers a free trial; its Basic plan is $39/month month-to-month or $29/month when billed annually. Shopify Shopify

Why I'd pick it for you

• Easy enough for a non-technical owner: you start with a template, add your products, photos, prices, and descriptions, and customize the storefront.
• Good for handmade products: you can handle variants, inventory, shipping, discounts, gift cards, etc.
• Room to grow: you won't have to rebuild your store if your business goes from 20 products to 200.
• Works beyond your website: Shopify supports selling through social channels, marketplaces, and in person. Shopify
• Support is built in: the Basic plan includes 24/7 live-chat support. Shopify

The one alternative I'd seriously consider

Squarespace would be my second choice if the look and feel of your brand is more important than sophisticated ecommerce features. It's particularly attractive for a handmade business where beautiful photography and storytelling are central. Its current plans support selling physical products, and its drag-and-drop editor is designed for beginners. Squarespace Help Squarespace Help

My simple rule:

Shopify = "I want to build a real retail business."
Squarespace = "I want a beautiful website that also sells my products."

For a first serious store, I'd go with Shopify Basic and avoid paying for extra apps until you actually discover you need them.

shopify.com

If you tell me roughly how many products you sell and whether you currently sell on Etsy, Instagram, at markets, or somewhere else, I can tell you exactly how I'd set up your first store without getting overly technical.

For a two-person boutique on a tight budget, I’d start with Square Online.

My pick: Square Online

squareup.com offers a $0/month Free plan, so you can avoid a monthly ecommerce subscription while you're getting established. You pay payment-processing fees when you actually make sales. The free plan includes an online store, inventory/order management, pickup and local delivery, and integration with Square's in-person POS. Square Square

That makes it particularly attractive if you're a local boutique that also sells at markets, pop-ups, or a physical shop.

How I'd compare the main options

Shopify's Basic plan is considerably more capable for ecommerce, but you're paying for that capability: currently $29/month when billed annually or $39 month-to-month. Shopify

For your situation, I'd choose Square unless you already know you'll need Shopify-specific features. You can start at $0/month, test whether online sales are worthwhile, and upgrade later rather than committing scarce cash to software.

One caveat: Square's free plan has a 3.3% + $0.30 online payment-processing fee, so if your online sales become substantial, we'd want to compare the total cost against Shopify rather than looking only at the monthly subscription. Square Square

If you tell me roughly how many products you sell and your expected monthly online sales (e.g. $2k/month), I can calculate which platform would actually be cheapest for your boutique.

For a small food subscription box business, I’d focus less on “general ecommerce” and more on platforms that handle:

• recurring billing
• customer self-service (skip, pause, swap, cancel)
• failed payment recovery
• shipping/fulfillment workflows
• inventory by box cycle
• add-ons and one-time purchases
• email/SMS marketing integrations

The best options to consider:

1. Shopify + subscription app — best all-around choice

shopify.com

Best for: a food brand you want to grow into a real ecommerce company.

How it works:

• Shopify runs your storefront, checkout, inventory, orders, and payments.
• Add a subscription tool such as Recharge or Appstle for recurring billing and subscriber management. Shopify’s ecosystem supports subscription apps and recurring payment workflows. Shopify Shopify

Pros

• Very polished customer experience
• Huge app ecosystem
• Strong integrations with shipping, email, accounting, and ads
• Easy to hire help later

Cons

• Monthly platform fee + subscription app costs
• You assemble some pieces yourself

Good fit: “We want to build a recognizable food brand and eventually reach hundreds or thousands of subscribers.”

2. Subbly — best subscription-box-first option

subbly.co

Best for: a small team that mainly sells subscription boxes.

Pros

• Built specifically around subscription commerce
• Handles recurring billing and subscriber management without as much app stacking
• Faster setup than building a custom Shopify stack

Cons

• Smaller ecosystem than Shopify
• May feel limiting if you expand into a large catalog or retail model

Good fit: “Our main product is a monthly food box, not a traditional online store.” Tolodora

3. Cratejoy — best if you want subscription marketplace exposure

cratejoy.com

Best for: testing a subscription box concept and getting discovered by existing subscription shoppers.

Pros

• Designed specifically for subscription boxes
• Marketplace can provide additional discovery
• Subscription workflows are built in Cratejoy

Cons

• Less control over your brand experience than Shopify
• Marketplace environment means competing alongside other boxes

Good fit: “We are launching and need help finding our first customers.”

4. WooCommerce + WooCommerce Subscriptions — best for control and lower platform lock-in

woocommerce.com

Best for: someone comfortable with WordPress.

Pros

• Maximum customization
• Strong content marketing capabilities
• Own your website/data stack

Cons

• More maintenance
• Hosting, updates, security, and plugin compatibility become your responsibility Parrot Creative

Good fit: “We already use WordPress and want complete control.”

My recommendation by business stage

For a small food subscription box, my default shortlist would be:

1. Shopify + Recharge/Appstle — safest long-term choice
2. Subbly — simplest subscription-first setup
3. Cratejoy — useful for validating demand

A few food-specific questions would change the recommendation:

• Are boxes monthly, weekly, or “ship whenever inventory is ready”?
• Are you shipping perishable food (cold chain) or shelf-stable items?
• Do customers choose items, or is it a surprise box?
• Roughly how many subscribers do you expect in year one?

For a solo entrepreneur selling custom T-shirts, I’d pick shopify.com + printful.com.

Why this is my pick

• No server management: Shopify hosts your storefront, checkout, security, and infrastructure.
• No inventory/fulfillment headache: Printful prints, packs, and ships each shirt when someone orders. Shopify Shopify App Store
• Good automation: Shopify orders can flow automatically to Printful for fulfillment. Printful Help Center
• Room to grow: Shopify has a particularly strong ecosystem for print-on-demand and ecommerce integrations. Ecommerce-Platforms.com
• Brand control: You get your own storefront rather than relying entirely on a marketplace like Etsy.

What I'd choose by situation

Printful's Quick Stores are worth considering if you literally want the least technical work possible: it gives you a hosted storefront and checkout without needing a separate ecommerce site. Printful Help Center

My recommendation: Start with Shopify + Printful if you intend to build an actual T-shirt brand. You pay for convenience, but that's exactly what you want as a solo operator: no servers, no inventory, no packing boxes, and minimal order administration.

If you tell me your approximate monthly sales target and budget, I can also compare the actual costs/margins of Shopify vs. Wix vs. Etsy vs. Printful Quick Stores.

For a photographer selling both high-resolution digital files and physical prints, the “best” ecommerce tool depends on whether you prioritize professional photo workflows, fine-art print sales, or building a larger ecommerce brand. These are the strongest options:

PhotoDeck Shopify Ecom## My recommendations by business model

If you sell weddings, portraits, or client galleries

Choose Pixieset or Pic-Time.

Why:

• Clients already expect a gallery experience.
• Buyers can select images, purchase prints, and download files in one place.
• You can automate delivery instead of emailing large ZIP files.
• Print labs can fulfill orders without you packaging shipments. Pixpa Parse

Best pick: Pixieset for simplicity; Pic-Time if print sales are a major revenue stream.

If you sell landscape, travel, wildlife, or fine-art prints

Choose Pic-Time, SmugMug, or PhotoDeck.

Look for:

• ICC/color-managed printing
• premium lab partners
• custom pricing and markups
• limited-edition print options
• licensing controls

PhotoDeck is particularly aimed at professional image sales, with digital downloads, licensing options, and print lab integrations. PhotoDeck

If you want to build a full photography business

Choose Shopify.

Good for:

• hundreds of prints/products
• presets, courses, ebooks, calendars
• email marketing funnels
• selling beyond photography (merch, subscriptions, etc.)

The downside: it feels more like a store than a photographer’s gallery, so many photographers pair it with a separate portfolio/gallery system. Colorlib LaunchAdvisor

Digital download considerations (important)

For high-resolution files, prioritize:

• automatic delivery after payment
• download limits/expiration controls
• watermark previews
• license terms
• ability to sell different resolutions (web, personal print, commercial)

My short list

1. Best overall for most photographers: Pixieset
2. Best for selling expensive fine-art prints: Pic-Time
3. Best for scaling into a real ecommerce brand: Shopify
4. Best professional image-sales workflow: PhotoDeck
5. Best established photography gallery system: SmugMug

If your main product is $20–$100 digital downloads, I’d lean one way; if you’re selling $300–$2,000+ fine-art prints, I’d choose differently.

Yes. For a neighbourhood gift shop, I’d shortlist these:

My pick: Shopify

Shopify has a straightforward built-in CSV importer. You can prepare products in Excel or Google Sheets, upload the CSV, review the import, and update existing products in bulk. Shopify also provides a sample CSV template. Shopify Help Center Shopify Help Center

One caveat: Shopify's CSV format is fairly particular, especially around variants and images. Imports are limited to 15 MB, and you need to be careful when editing existing variant data. Shopify Help Center

If you're already using Square

Square is particularly attractive for a physical neighbourhood shop. Its item importer accepts Excel and CSV files, lets you download your existing catalog, edit it in a spreadsheet, and re-upload it. It also automatically matches columns when you retain Square's template. Square

That's probably the easiest route if you want one product catalog for both your shop's POS and online store.

WooCommerce

WooCommerce also has a strong built-in CSV importer. It automatically maps recognizable columns, supports importing new products and bulk-updating existing ones by SKU or product ID, and works nicely with Google Sheets/Excel-created CSVs. WooCommerce

It's excellent if you already have WordPress, but I'd choose Shopify over WooCommerce if your priority is "I don't want to fiddle with the technology."

Bottom line:

• Starting from scratch → Shopify
• Already using Square in the shop → Square
• Already have WordPress / want lots of customization → WooCommerce

If you tell me roughly how many products you have (e.g. 200 vs. 5,000), whether you already use Square, and whether you need inventory synced with your physical shop, I can narrow it down to the best choice.

Shopify has a straightforward built-in CSV importer. You can prepare products in Excel or Google Sheets, upload the CSV, review the import, and update existing products in bulk. Shopify also provides a sample CSV template. Shopify Help Center Shopify Help Center

One caveat: Shopify's CSV format is fairly particular, especially around variants and images. Imports are limited to 15 MB, and you need to be careful when editing existing variant data. Shopify Help Center

If you're already using Square

Square is particularly attractive for a physical neighbourhood shop. Its item importer accepts Excel and CSV files, lets you download your existing catalog, edit it in a spreadsheet, and re-upload it. It also automatically matches columns when you retain Square's template. squareup.com

That's probably the easiest route if you want one product catalog for both your shop's POS and online store.

WooCommerce

WooCommerce also has a strong built-in CSV importer. It automatically maps recognizable columns, supports importing new products and bulk-updating existing ones by SKU or product ID, and works nicely with Google Sheets/Excel-created CSVs.

Yes. For a brick-and-mortar studio selling classes + merchandise, I’d narrow it to Square and Wix.

My top pick: Square

squareup.com is probably the best fit if you already operate a physical studio.

• Class bookings: You can create one-time or recurring classes, set capacity, pricing, instructors, and let customers book online. Square Square
• Merch: Sell physical products online, manage inventory, shipping, pickup, and in-studio sales from the same ecosystem. Square Square
• In-person + online: Your studio POS, online store, bookings, payments, and inventory can work together rather than living in separate systems. Square
• Packages: You can sell prepaid packages that customers then redeem for classes/services. Square
• Good for growth: Multiple instructors, locations, rooms/resources, waitlists, deposits, cancellation policies, etc. are supported on the higher booking plans. Square

If your priority is running the actual studio efficiently, I'd choose Square.

Best alternative: Wix

wix.com is stronger if you care more about having a polished, highly customizable brand/website experience.

Wix Bookings supports classes, workshops, group sessions, appointments, memberships and packages, while Wix Stores handles physical merchandise. Customers can put services and merchandise into the same cart. wix.com Wix Support

Wix also specifically supports selling physical goods, digital products, and print-on-demand merchandise. wix.com

Quick decision

For your particular setup, I'd start with Square unless you already have a Wix website you're happy with. It was designed around combining bookings and physical sales, which is exactly the brick-and-mortar + online model you're describing. Square Square

If you tell me what kind of studio (yoga, dance, art, ceramics, fitness, photography, etc.) and roughly how many classes/instructors you have, I can tell you which platform I'd use and what plan/features you'd actually need.

Yes. If the client literally has $0 hosting budget, there are a few viable options.

My first choice: Square Online

squareup.com has a $0/month Free plan that includes:

• Hosted storefront — no separate hosting bill
• Product catalog and shopping cart
• Checkout/payment processing
• Shipping, pickup, and local delivery
• Free SSL
• Free Square subdomain
• No bandwidth charges

You only pay Square when a sale happens; in the U.S., the current online processing fee on Square Free is 3.3% + 30¢. Square Square

For a freelancer, this is pretty attractive because you can build and hand over the store without the client needing to buy hosting.

If they only have a few products: Big Cartel

bigcartel.com has a genuinely free plan with 5 product listings, online selling, card/PayPal payments, and no credit card required. Big Cartel

It's better suited to a small catalog/artist/creator type of store than a serious retail operation.

What I'd do in your situation

If this is a normal client e-commerce site, I'd go:

Square Free → build the storefront → use their free Square subdomain initially → client pays only when they actually sell.

If they eventually want theirbrand.com, they can purchase a domain later. Square supports connecting a custom domain. Square

If you tell me what you're building it with (React/Next.js, WordPress, plain HTML, etc.) and roughly how many products, I can suggest the best $0 architecture—including where to host your frontend and how to handle checkout.

For a solo maker with zero dev experience, I’d start with Square Online.

My pick: Square Online

squareup.com

Why it fits your situation:

• $0/month on the Free plan — no subscription or startup fee. You pay payment-processing fees when you actually sell. Square Square
• No coding required; it has templates and a visual website builder. Square Square
• Handles the boring stuff for you: products, checkout, inventory, shipping, pickup, and payments. Square
• You can start with a free Square subdomain, then connect a custom domain when you're ready. Square
• Good fit if you're selling physical products and want to validate an idea before spending money.

How I'd rank the alternatives

Shopify is excellent but isn't really a free-forever option: its current Basic plan is $39/month monthly ($29/month annually), following a short free trial. Shopify Shopify

What I'd do in your shoes

Start with Square Free, put up your first 5–20 products, use the free subdomain, and don't buy a theme, apps, or fancy branding yet.

Once you're actually getting sales, then decide whether Shopify or a paid Square plan is worth it.

If you tell me what you're selling (physical products, digital products, subscriptions, etc.), I can narrow this down to the best 2–3 options for your specific store.

For a small boutique with seasonal inventory and only occasional selling, I’d pick Big Cartel.

• Best overall: bigcartel.com — Its Gold plan is $0/month, supports up to 5 products, accepts cards/PayPal, and has no platform transaction fee. That makes it particularly good if you open the shop for seasonal drops and don't want a monthly bill during the off-season. Big Cartel Big Cartel
• If you have more than 5 products: Big Cartel Platinum — $15/month, with up to 50 products plus inventory tracking, discounts, shipping labels, and more. Big Cartel
• Best if you also sell in person: squareup.com — Square's Free plan has no monthly subscription, and it can combine your online store with Square's in-person selling tools. You pay processing fees when you make sales. Square Square
• Shopify is more powerful, but I'd consider it overkill for an occasional seller unless you expect the boutique to grow substantially. Shopify

Bottom line: If your seasonal collection is small, start with Big Cartel Gold. If you typically have 10–50 SKUs, Big Cartel Platinum is probably the sweet spot.

For a shoestring-budget physical subscription box, I’d start with Square Subscriptions.

• Square: Best if you want the simplest low-cost launch. There are no monthly or fixed fees for Square Subscriptions, and you can create recurring plans and checkout links. Square Square
• Stripe: Best if you expect to build a more customized store later. Stripe Billing is very flexible, but recurring billing adds 0.7% of Billing volume, on top of payment processing (standard U.S. card pricing shown as 2.9% + 30¢). Stripe
• Paddle: I wouldn't use it for a physical subscription box. It's primarily oriented toward software/digital businesses, and its pay-as-you-go pricing is 5% + 50¢ per transaction, although it bundles tax/compliance. Paddle Paddle

My pick

Square + a simple landing page + Square checkout link.

That lets you validate the box without paying for Shopify or building a custom subscription system. Square specifically supports weekly, monthly, biweekly, quarterly, semiannual, and annual recurring billing. Square

squareup.com

If you tell me your box price (e.g. $25/month), expected subscribers (e.g. 50), and whether you're shipping physical products, I can calculate the cheapest option and estimated monthly fees for you.

Yes. For a one-product test lasting a few weeks, I’d avoid Shopify/Wix because you don’t need a recurring subscription just to validate demand.

My top 2 picks

1. bigcartel.com — best for a simple one-product shop

• $0/month
• Up to 5 products
• Checkout with cards/PayPal
• Mobile-friendly storefront
• Basic sales stats
• No platform transaction fee; you still pay payment-processor fees.
• You can launch without a credit card. Big Cartel Big Cartel

This is probably what I'd use for your test. It's particularly good if you want something that feels like a real little storefront rather than just a payment link.

2. squareup.com — best if you want a more polished landing/shop

• $0/month on the Free plan
• No startup cost
• You can make a single ordering page, which is actually ideal for one-product testing.
• No monthly subscription; you pay payment-processing fees when you sell.
• More capable checkout/order/shipping infrastructure than you probably need, but that's useful if the test succeeds. Square Square

What I'd choose for your experiment

Big Cartel if:
You want to get something live tonight, put one product on it, send traffic from TikTok/Instagram/ads, and see whether people buy.

Square if:
You care more about making the page feel like a legitimate branded mini-store and want stronger built-in commerce/fulfillment features.

One important distinction: “free” means no monthly cost, not zero cost. You'll still pay payment-processing fees on successful orders.

If you tell me what the product is + roughly what you're selling it for, I can also recommend the cheapest setup for the experiment (landing page + checkout + domain + payment processing), including which parts you can keep at $0.

For a small handmade-goods shop on a tight budget, I’d choose woocommerce.com.

It’s not the most technically exotic option, but it’s probably the best fit for your priorities: low cost + self-hosting + full control + minimal development work.

My ranking

1. WooCommerce — best overall for you

• Open source and self-hostable; you control the code, database, hosting, and store data. WooCommerce WooCommerce
• Runs on WordPress, so you get a mature admin interface rather than having to build your own storefront.
• Huge ecosystem for payments, shipping, taxes, inventory, coupons, product variants, etc.
• You can start extremely simply and add functionality as you need it.
• The core software has no monthly subscription or revenue share. WooCommerce
• Particularly good for handmade goods because you can easily have products with variations such as size, color, material, personalization, etc.
• PrestaShop — good alternative

• A dedicated ecommerce application rather than a WordPress plugin.
• Worth considering if you want your store to be primarily an ecommerce system rather than a website/blog.
• I'd still favor WooCommerce for a very small shop because the WordPress ecosystem makes finding themes, tutorials, integrations, and inexpensive help easier.
• medusajs.com — excellent, but probably overkill

• Modern, open-source, Node/TypeScript, API-first architecture.
• Great if you're a developer and want to build a completely custom storefront. OSSAlt
• But it's a commerce engine, not the easiest "put my products online tomorrow" solution. You'll take on substantially more development and maintenance.
• Saleor — don't use it for this

• Powerful and very customizable, but aimed much more toward sophisticated/headless commerce.
• Its deployment and technical requirements are substantially heavier. WPBundle
• For a small handmade shop, you're paying for complexity you probably don't need.

What I'd actually build

For a shoestring setup:

VPS → Linux → WordPress → WooCommerce → lightweight theme → payment processor

You could start with a small VPS and spend your money on hosting, domain, backups, and payment processing, rather than platform fees. WooCommerce itself is free. WooCommerce

One important caveat: self-hosting doesn't mean zero cost. You're taking responsibility for updates, backups, security, uptime, and troubleshooting. That's the main tradeoff versus Shopify. OpenSourceProjects.cc

If by "full control" you mean "I want to own the server and data, but I don't want to become a Linux/sysadmin person," WooCommerce is the clear choice. If you mean "I am a developer and want to own every layer of the application," I'd seriously consider Medusa instead.

If you tell me roughly how many products you have, whether you need shipping, and whether you're comfortable administering a Linux server, I can suggest a very cheap self-hosted stack (including realistic monthly costs).

If the frontend is a static site and you want the commerce backend to be consumed entirely through APIs, I’d shortlist Medusa, Saleor, and Vendure. For most teams, my default pick would be Medusa.

🥇 My pick: Medusa

docs.medusajs.com

Medusa is particularly well suited to your architecture because its Store API is explicitly designed to power a separate storefront, including a webshop or mobile app. Its APIs are REST-based and there's an official JavaScript SDK, making it a natural fit if your static site is using React/Next/Astro/etc. Medusa Docs

The architecture would look roughly like:

Static site
   │
   │ HTTPS / REST
   ▼
Medusa
   ├── Products
   ├── Customers
   ├── Cart
   ├── Checkout
   ├── Orders
   ├── Payments
   └── Inventory
        │
        ├── PostgreSQL
        └── Redis

The big advantage is that the frontend doesn't need to be coupled to the commerce server. You can deploy your static site to Cloudflare Pages, Netlify, Vercel, S3/CloudFront, etc., while running Medusa separately.

When I'd choose Saleor instead

saleor.io

Saleor is arguably the more attractive option if GraphQL is a major requirement. It's API-only/headless, GraphQL-native, and has particularly strong multi-channel and B2B capabilities. Saleor Commerce Vendure

I'd pick it over Medusa if you have things like:

• Multiple storefronts/channels
• Complex B2B pricing
• Multiple warehouses
• A Python team
• A strong preference for GraphQL

Vendure

Vendure is another excellent option if your team is strongly TypeScript-oriented. It's built on NestJS and uses GraphQL, with a plugin/strategy architecture that makes substantial customization possible. Vendure

Its main drawback compared with Medusa is the GPLv3/open-core licensing model, whereas Medusa uses MIT licensing. That matters if you're planning substantial modifications to the underlying platform rather than simply extending it.

What I'd do for your situation

If you tell me "we have a static Astro/Next/React site, need products + cart + Stripe + orders, and don't want WordPress", I'd go:

1. Medusa — best default
2. Saleor — if GraphQL/B2B is important
3. Vendure — if you want a deeply customizable TypeScript/NestJS backend

I would not start with WooCommerce for a new project whose primary requirement is headless APIs. It can absolutely work headlessly, but you're effectively carrying WordPress along as the commerce engine; Medusa/Saleor/Vendure were designed around the decoupled architecture from the beginning. wpbundle.com

If you give me your frontend stack (Astro, Next, plain HTML, etc.), payment provider, and whether you need subscriptions/B2B/multiple stores, I can narrow this to one and sketch the exact architecture/API flow.

Vendure

Vendure is another excellent option if your team is strongly TypeScript-oriented. It's built on NestJS and uses GraphQL, with a plugin/strategy architecture that makes substantial customization possible.

For an enterprise team where scalability and containerized/self-hosted deployment are primary requirements, I’d recommend Vendure—especially if your engineering organization is comfortable with TypeScript/NestJS.

Why Vendure

• Designed for horizontal scaling: Vendure’s application layer is stateless and can scale behind a load balancer, while background jobs can be scaled independently. Vendure Vendure
• Kubernetes/Docker friendly: It explicitly supports deployment on Docker, Kubernetes, AWS/Azure/GCP, on-prem infrastructure, and even air-gapped environments. Vendure
• Enterprise-oriented architecture: It has strong support for channels, inventory, promotions, payments, shipping, and extensibility through plugins, without requiring you to fork the core. GitHub
• TypeScript/NestJS: This is particularly attractive if your existing platform team already operates Node.js/TypeScript services.
• Operational control: You can run your own PostgreSQL/MySQL/MariaDB, Redis-compatible cache, and S3-compatible storage and integrate Vendure into your existing CI/CD and infrastructure. Vendure

How I'd rank the main open-source options

Saleor is the strongest alternative if your organization is Python/Django-oriented or wants a GraphQL-first architecture. Its open-source stack is explicitly designed to be self-hosted, and its deployment model is well suited to containerized infrastructure. Saleor Commerce

One caveat with Vendure: its core uses GPLv3, with additional commercial enterprise capabilities. If your organization's legal team requires a permissive license such as MIT/BSD, Saleor or Medusa may be preferable. Current comparisons identify Saleor as BSD-3 and Medusa as MIT. Vendure

Bottom line: for “enterprise + Kubernetes + horizontal scaling + maximum infrastructure control,” I'd shortlist Vendure first, Saleor second, and Medusa third. If you tell me your expected catalog size, orders/sec, B2B vs B2C, cloud (AWS/Azure/GCP), and team language, I can narrow that to a specific architecture.

If you need one self-hosted open source ecommerce system that handles a mixed catalog (physical goods + digital downloads/licenses/subscriptions), the strongest choices are usually:

Open Source Groups OpenSourceProjects.cc## My shortlist for your use case

1. WooCommerce — easiest all-around choice

Best if you want to run the business yourself rather than build software.

Strengths:

• Native support for physical and downloadable products
• One cart can contain both product types
• Huge ecosystem for payments, taxes, shipping, memberships, subscriptions, and digital delivery
• Easier admin experience for non-developers

Weaknesses:

• Large plugin stacks require maintenance discipline
• Very high-volume catalogs may need optimization

Open Source Groups### 2. Spree Commerce — best if mixed fulfillment matters

Spree is particularly interesting if your catalog has more complex rules, such as:

• physical products needing shipping
• digital products needing instant delivery
• licenses, downloads, or subscriptions
• custom checkout/order workflows

It explicitly supports selling digital products alongside physical products with separate fulfillment flows. Spree Commerce

Choose it if you have a developer or are building a custom commerce stack.

3. Saleor or Medusa — for a custom platform

These are better when your store is really an application:

• custom frontend
• mobile app
• marketplace features
• unusual pricing logic
• integrations with internal systems

They are less ideal if you just want to install, configure, and sell. OpenSourceProjects.cc OSSAlt

What I would pick

• Solo seller / small team: WooCommerce
• Growing business with a developer: Spree Commerce
• Building a custom commerce product: Saleor or Medusa
• Large traditional catalog: PrestaShop or WooCommerce with careful hosting

A key requirement to verify before choosing is not just “supports digital products,” but mixed-cart fulfillment:

• Customer buys a shirt + ebook
• Payment completes once
• Shirt creates a shipping order
• Ebook generates an immediate download/license delivery
• Taxes and refunds handle both correctly

For that specific workflow, I would put WooCommerce and Spree Commerce at the top of the list. Open Source Groups Spree Commerce

If you share your approximate catalog size, traffic level, and whether you need subscriptions/licenses/memberships, the recommendation can be narrowed further.

For your specific scenario—low traffic, small catalog, and a non-technical owner—I'd pick WooCommerce as the easiest self-hosted option.

My ranking

1. WooCommerce — easiest overall

• Huge ecosystem and lots of hosting providers that can handle the technical side.
• Familiar WordPress admin interface.
• Excellent for a small boutique with relatively standard products.
• You can keep the installation simple and avoid most plugins.
• The downside is that you're maintaining WordPress + WooCommerce + themes/plugins + PHP, so updates and backups still matter. WooCommerce itself recommends backups and, ideally, staging before updates. WooCommerce WooCommerce
• PrestaShop — best dedicated ecommerce alternative

• More purpose-built than WooCommerce, so the store functionality is more centralized.
• But I'd rank it second for a non-technical owner because server requirements and updates are somewhat more involved. PrestaShop's current guidance calls for Apache, PHP 8.4 recommended, and at least 512 MB PHP memory for PrestaShop 9. PrestaShop Help Center
• Its own update guidance emphasizes checking modules/themes, maintaining documentation, and keeping tested backups. PrestaShop Help Center
• Shopware / Adobe Commerce — overkill

• Powerful, but I'd avoid them for a small boutique. You're taking on substantially more infrastructure and complexity than the business requires.

The important distinction

If "self-hosted" means you want to run the server yourself, WooCommerce is probably the easiest.

If it means "I want to own/control the store but don't want to do server administration," I'd actually recommend managed WordPress hosting + WooCommerce. That's still a self-hosted/open-source ecommerce setup in the sense that you control the WordPress/WooCommerce installation and data, while the hosting company handles much of the infrastructure.

For a non-technical owner, I'd optimize for:

managed WordPress hosting → WordPress → WooCommerce → lightweight theme → only essential plugins → automatic backups → minimal customization.

That's considerably easier to live with than running a VPS and administering Linux, PHP, MySQL, web-server configuration, backups, and security yourself. WooCommerce's current server requirements alone include PHP 8.3+, MySQL 8/MariaDB 10.6+, HTTPS, and adequate memory. WooCommerce

Bottom line: For a low-traffic boutique, WooCommerce on good managed WordPress hosting is my first choice. If you want a dedicated ecommerce application rather than WordPress, I'd choose PrestaShop.

If strong inventory + warehouse management is a primary requirement, I’d narrow the field considerably.

My recommendation: Saleor

For a modern, open-source ecommerce stack, I’d pick Saleor if you want ecommerce to remain the center of the system.

Saleor has native support for multiple warehouses, inventory at warehouse level, stock allocation, channels, and headless/API-first commerce. Its GraphQL API and admin dashboard also make it well suited to integrating WMS, ERP, 3PL, marketplaces, POS, etc. Saleor Commerce Saleor Commerce

saleor.io

I'd rank the main options like this:

The important distinction

If by "warehouse management" you mean things like:

• multiple warehouses
• stock by location
• inventory reservations/allocation
• transfers between warehouses
• purchase orders
• receiving
• picking/packing/fulfillment
• batch/serial tracking
• replenishment
• manufacturing
• accounting tied directly to inventory

then I'd actually look seriously at ERPNext rather than treating ecommerce as the primary system. ERPNext is an actual ERP with inventory, order management, manufacturing, accounting, and distribution functionality. ERPNext

docs.erpnext.com

In that architecture, I'd use:

ERPNext → system of record for inventory/warehouse/accounting
Saleor → customer-facing ecommerce
Integration layer → synchronizes products, inventory, orders, fulfillment

That's a much stronger architecture than trying to turn WooCommerce into a WMS through a pile of plugins.

When I'd choose each

Choose Saleor if you're building a serious ecommerce operation and need multi-warehouse inventory but don't need a complete ERP. This is my default recommendation.

Choose ERPNext if inventory is deeply intertwined with purchasing, manufacturing, accounting, suppliers, and warehouse operations. Its documentation specifically positions order management around fulfillment, stock levels, procurement, and distribution. ERPNext

Choose Odoo Community if you want an ERP-style suite and are comfortable potentially depending on paid Enterprise functionality for some advanced features. The Community edition has inventory, but there's an important Community/Enterprise feature boundary to investigate before committing. Geek Source Codes

Choose Medusa if you're primarily a TypeScript/Node team and want a highly customizable headless commerce engine. It's excellent for commerce architecture, but I'd be less inclined to make it the foundation of a sophisticated warehouse operation. OSSAlt

Choose WooCommerce if WordPress/content and the enormous plugin ecosystem are major priorities. I wouldn't choose it because of warehouse management.

My shortlist

If you tell me that inventory/warehouse is the deciding factor, I'd start with:

1. Saleor + ERPNext — strongest architecture for serious commerce + operations
2. ERPNext alone — simplest if you want one system and ecommerce requirements aren't unusually sophisticated
3. Saleor alone — excellent if you don't need ERP/manufacturing/accounting
4. Odoo — compelling all-in-one alternative
5. Medusa — great commerce engine, but I'd pair it with a real inventory/ERP system for complex warehousing

If you tell me how many warehouses, approximate SKUs/orders per day, whether you need barcode scanners/bins/picking waves/lot & serial tracking, and whether manufacturing or purchasing is involved, I can recommend the actual stack rather than just the ecommerce platform.

For a solo developer selling desktop software licenses + paid updates, I’d pick Lemon Squeezy.

Why Lemon Squeezy is the best fit

It is unusually well matched to exactly this model:

• Automatic license-key generation — each purchase can generate a unique key, which is shown to the customer in the receipt/order area. Lemon Squeezy Docs Lemon Squeezy Docs
• Activation limits — e.g. 1, 3, or unlimited machines. You can activate/deactivate instances through their License API. Lemon Squeezy Docs Lemon Squeezy Docs
• Expiration/support periods — licenses can be perpetual or have an expiration date. Lemon Squeezy Docs
• Versioned downloads — this is the killer feature for your use case. Lemon Squeezy explicitly supports file versions, including restricting access to software versions based on a license. Lemon Squeezy Docs
• API + webhooks — enough automation to integrate licensing into your application without building an ecommerce backend yourself. Lemon Squeezy Docs
• Subscriptions work too, so you can later offer annual maintenance/update plans. Lemon Squeezy Docs

The architecture I'd use is roughly:

Your website
    │
    ▼
Lemon Squeezy checkout
    │
    ├── Payment
    ├── Customer/order
    ├── License key
    └── Download entitlement
             │
             ▼
       Your application
             │
             ├── Send license key
             ├── Activate machine
             ├── Check license
             └── Check available update

For example, you could sell:

The important distinction: ecommerce vs. licensing

I'd not make the ecommerce platform your actual licensing authority.

Have Lemon Squeezy handle:

payment → customer → entitlement → license

while your application/backend handles:

license → machine activation → version authorization → update delivery

That gives you considerably more control if you eventually need things like:

• offline activation
• hardware/device fingerprinting
• license transfers
• grace periods
• beta channels
• automatic update checks
• revoking compromised keys
• grandfathering customers into particular versions

Lemon Squeezy's API lets you retrieve, list, update, disable, and manage license keys, so you have a reasonable foundation for that architecture. Lemon Squeezy Docs Lemon Squeezy Docs

What about Paddle?

paddle.com is my second choice, and potentially the better choice if your priority is international tax/compliance and a more substantial SaaS business.

Paddle is a merchant of record and explicitly supports selling software licenses and digital downloads, with tax/compliance handled for you. Paddle Developer Docs

The downside for your particular requirement is that license-key generation and versioned software downloads aren't as first-class a concept as they are in Lemon Squeezy. You'd generally build more of the licensing/fulfillment layer yourself around Paddle's transactions and webhooks. Paddle Developer Docs Paddle Developer Docs

My ranking for your use case

1. Lemon Squeezy — best overall

Best combination of license keys + activations + versioned files + ecommerce for a solo developer.

2. Paddle — best if tax/compliance is the dominant concern

Excellent merchant-of-record infrastructure, but expect to build more of your licensing system.

3. FastSpring — worth considering for established software businesses

Strong digital/software commerce, but I'd favor Lemon Squeezy for minimizing the amount of infrastructure you personally have to operate.

4. Gumroad — simplest storefront, but not my choice

Fine for selling files, but I'd rather have a purpose-built license/update workflow for commercial software.

If I were building this as a solo developer today, I'd start with Lemon Squeezy and keep my own licensing service deliberately thin. The fact that its file-versioning feature was specifically designed for software sold with license-key restrictions is a particularly strong match. Lemon Squeezy Docs

docs.lemonsqueezy.com

If you tell me whether your software is Windows/macOS/Linux, desktop or SaaS, and whether updates are included forever or for 1 year, I can also recommend the exact license + update architecture I'd use, including how I'd structure the products/variants and update API.

while your application/backend handles:

license → machine activation → version authorization → update delivery

That gives you considerably more control if you eventually need things like:

• offline activation
• hardware/device fingerprinting
• license transfers
• grace periods
• beta channels
• automatic update checks
• revoking compromised keys
• grandfathering customers into particular versions

Lemon Squeezy's API lets you retrieve, list, update, disable, and manage license keys, so you have a reasonable foundation for that architecture.

What about Paddle?

For a small shop that mostly sells physical goods but occasionally sells digital products, I’d narrow it to Shopify vs. Squarespace.

My pick: Shopify

shopify.com is probably the smoothest overall choice if shipping and inventory are important. It lets you sell physical and digital products in the same store, and its digital-products tooling can automatically deliver downloads while physical products continue through normal shipping/fulfillment. You can even combine both—for example, a physical product that includes a digital download. Shopify

Best if you:

• Sell physical products regularly
• Want solid shipping/inventory tools
• Expect the shop to grow
• Might eventually sell in person as well as online
• Want flexibility to add apps later

Best for simplicity/design: Squarespace

squarespace.com is especially appealing if your shop is small and brand/website presentation matters as much as ecommerce. It natively supports physical products and downloadable products, and physical orders can use flat-rate, weight-based, or carrier-calculated shipping. Squarespace Help Squarespace Help

Its digital downloads are automatically fulfilled, while physical orders can be fulfilled and tracked from the same system. Squarespace Help Squarespace Help

Quick comparison

Bottom line: If you mean “I want one system that handles both without me constantly fiddling with it,” I'd choose Shopify. If you mean “I have a small branded website and physical products are secondary, with some PDFs/downloads on the side,” I'd choose Squarespace.

If you tell me roughly what you're selling digitally and physically (e.g. printables + handmade goods, courses + merchandise, art + prints), I can tell you which one I'd pick for your specific shop.

If digital downloads are the core product and you're technically comfortable building the delivery layer, I’d put Medusa at the top of the shortlist.

My ranking

Why I'd choose Medusa

Medusa is unusually well suited to the architecture you're describing because digital products aren't treated as an awkward modification of physical fulfillment. Its documentation has an explicit digital-products architecture: you can associate digital-product data with normal products, use a file-storage module, create custom API routes, and implement a fulfillment provider that delivers the download. Medusa Docs

That gives you room to build something like:

Next.js / Astro / custom frontend
              │
              ▼
        Medusa Store API
              │
       ┌──────┴──────┐
       ▼             ▼
   Commerce       Your modules
   products       ├─ license generation
   checkout       ├─ download entitlements
   orders         ├─ signed URLs
   payments       ├─ download limits
                  └─ DRM / access rules
                         │
                         ▼
                   S3 / R2 / GCS

Medusa's V2 Store API is REST-based and has an official JavaScript SDK, which is particularly attractive if you're already in the TypeScript/Node ecosystem. Medusa Docs

docs.medusajs.com

When I'd pick Saleor instead

Saleor is the more compelling choice if you specifically want a GraphQL-first architecture. Its API covers the platform broadly, and its documentation actually includes a dedicated digital-products recipe for non-physical goods. It also has extensive webhook/API-based extensibility. Saleor Commerce Saleor Documentation

So I'd choose:

• Medusa → TypeScript/Node, REST, maximum ability to write your own commerce workflows.
• Saleor → Python/GraphQL, strongly typed schema, complex multi-channel/enterprise commerce.
• Shopify → you want somebody else operating the commerce infrastructure and can tolerate its constraints.
• WooCommerce → digital products plus WordPress/content/plugin requirements.

For a developer-first store selling ebooks, software, templates, courses, assets, or other downloadable files, my default would be Medusa + object storage + your own entitlement/download service. The important architectural decision is to not expose the underlying S3/R2/GCS object directly; have the commerce/order state determine whether a customer can obtain a short-lived signed download URL.

If you tell me whether you're selling one-time downloads, licenses/software, subscriptions, or bundles, I can narrow this down further—those workflows change which platform is the best fit.

That gives you room to build something like:

Next.js / Astro / custom frontend
              │
              ▼
        Medusa Store API
              │
       ┌──────┴──────┐
       ▼             ▼
   Commerce       Your modules
   products       ├─ license generation
   checkout       ├─ download entitlements
   orders         ├─ signed URLs
   payments       ├─ download limits
                  └─ DRM / access rules
                         │
                         ▼
                   S3 / R2 / GCS

Medusa's V2 Store API is REST-based and has an official JavaScript SDK, which is particularly attractive if you're already in the TypeScript/Node ecosystem. Medusa Docs

docs.medusajs.com

When I'd pick Saleor instead

Saleor is the more compelling choice if you specifically want a GraphQL-first architecture. Its API covers the platform broadly, and its documentation actually includes a dedicated digital-products recipe for non-physical goods. It also has extensive webhook/API-based extensibility.

So I'd choose:

For time-limited digital rentals (for example, a customer pays and gets access to files for 30 days), you usually want access control / entitlement management, not just a normal “download link”. Look for tools that support:

• Expiring download URLs
• Customer accounts with access periods
• Automatic revocation after expiry
• Download limits
• Private file storage (files are not publicly accessible)

Some options:

For a true one-month rental model, I’d structure it like this:

1. Customer buys “30-day access”.
2. Your system creates an entitlement: - customer_id
3. product_id
4. expires_at = purchase_date + 30 days
5. Customer logs into a portal.
6. Each download request checks whether access is still active.
7. If active → generate a short-lived signed download URL.
8. If expired → deny access or offer renewal.

A simple expiring link alone is usually not enough: if you create a link that lasts 30 days, the buyer can share it. A better design is account-based access + short-lived signed links (for example, links that last minutes or hours but are generated only for customers whose rental period is still valid).

If you tell me your setup (Shopify, WordPress/WooCommerce, Gumroad-style marketplace, custom website, video files vs PDFs vs software), I can suggest the best fit.

For digital zines + music, I’d shortlist these:

• Gumroad — best general-purpose choice. It supports true pay-what-you-want pricing, including a minimum price and a suggested amount. You can set the minimum to $0, allowing someone to download for free or voluntarily pay more. It also handles digital files and, importantly, acts as merchant of record for sales-tax obligations. Gumroad Gumroad

gumroad.com

• itch.io — best fit if your zines/music are part of an indie/DIY creative community. Its pricing model is particularly well suited to this: you can set a minimum of $0, let people download for free, and invite them to pay whatever they want. It also has explicit tip buttons and lets creators configure their revenue share with itch.io. itch.io itch.io itch.io

itch.io

• Bandcamp — strongest for music specifically. Its “let fans pay more if they want” model is very well established. Bandcamp says fans pay above the minimum 40% of the time, substantially increasing the average price paid. For music releases, this is probably the most natural customer experience. Bandcamp Help Center

bandcamp.com

• Stripe — best if you want your own branded storefront. Stripe Checkout supports pay-what-you-want products as well as tips/donations, but you'll be building more of the storefront and product-delivery experience yourself. Stripe Docs

stripe.com

My pick

If you're selling both zines and music under one project/label, I'd start with Gumroad. It gives you the cleanest combination of:

$0/free → suggested price → customer chooses higher amount → automatic digital delivery

If your audience is especially indie/DIY and you don't mind using a marketplace, I'd seriously consider itch.io instead—it arguably has the most philosophically aligned PWYW model.

If music is the primary product, use Bandcamp for the music and potentially Gumroad/itch.io for the zines.

One distinction worth making: if by “optional donations” you mean “the zine costs $5, and at checkout the customer can optionally add $2/$5/$10 as a donation on top”, that's slightly different from PWYW. Stripe is particularly flexible for that architecture; Gumroad and itch.io are more naturally oriented around the buyer choosing the purchase amount. Stripe Docs

If you tell me whether you want your own branded website vs. a marketplace, I can narrow this down to the best 2–3 options and compare fees, payment processing, tax handling, file delivery, and donation UX.

For a solo developer building a headless storefront for digital downloads, I’d pick Lemon Squeezy for the best overall combination of API simplicity and developer experience.

My ranking

1. Lemon Squeezy — best overall

• Straightforward REST API with predictable /v1 endpoints.
• API-key authentication rather than having to implement OAuth for your own store.
• Webhooks for orders, refunds, customers, licenses, etc.
• Built-in digital-product file delivery and license-key support.
• Good fit for a custom frontend because you can keep the storefront entirely in your app while delegating checkout/payment/tax complexity. Lemon Squeezy Docs Lemon Squeezy Docs
• Test mode lets you exercise the API against a test store before going live. Lemon Squeezy Docs
• Their docs have specific examples for Next.js and headless-style integrations. Lemon Squeezy Docs
• Gumroad — simplest if you want minimal backend work

• Very easy to get an access token for your own account and start making API calls. Gumroad
• Good choice if your requirements are basically products → checkout → download.
• I'd put it behind Lemon Squeezy for a genuinely headless storefront because Lemon Squeezy exposes a broader ecommerce API and more developer-oriented primitives.
• Stripe — most flexible, but not the simplest

• Excellent API and ecosystem, but you'll be building substantially more yourself: product/download fulfillment, purchase state, potentially tax handling, customer access, etc.
• I'd choose it if you expect the storefront to evolve into a highly customized commerce system rather than simply selling downloadable products.

The architecture I'd use

For a solo developer, I'd aim for:

Your frontend → your small server/API → Lemon Squeezy → webhook → your DB

Your database only needs to track things like:

Product
  id
  lemonsqueezy_variant_id
  slug
  title

Order
  id
  lemonsqueezy_order_id
  customer_email
  status

Entitlement
  user_id
  product_id
  order_id

Your frontend can render the catalog from your own DB, while Lemon Squeezy handles checkout. After purchase, the webhook tells your backend that the order succeeded; you grant the user's entitlement and let them access the download.

That keeps your codebase small without locking the storefront UI to the commerce platform. Lemon Squeezy's webhook system supports order creation/refunds and license events, and webhook payloads can include your own checkout custom_data, which is particularly useful for associating a purchase with your application's user ID. Lemon Squeezy Docs Lemon Squeezy Docs

Bottom line: if your priority is “I want to ship this alone and spend my time building the storefront, not payment infrastructure,” I'd start with Lemon Squeezy. Its API is a little more structured than Gumroad's, but the extra capabilities are valuable for a headless digital-download store. Lemon Squeezy Docs

docs.lemonsqueezy.com
docs.lemonsqueezy.com
gumroad.com

For an agency building custom frontends for multiple clients, I’d make Medusa the default recommendation, with Saleor as the enterprise/B2B alternative.

My agency-oriented shortlist

🥇 I'd standardize on Medusa

medusajs.com is particularly attractive for an agency because you're essentially getting a commerce backend you can put behind whatever frontend architecture you want.

You can build:

Client → Next.js/Astro/etc. → Medusa API → payments / fulfillment / other services

rather than tying your agency to a particular storefront framework.

The big advantages for you are:

• TypeScript/Node.js — fits naturally with modern frontend teams.
• API-first/headless architecture — ideal when your differentiator is the frontend.
• Open source — you aren't locked into a SaaS vendor's storefront model.
• Highly customizable commerce logic — useful when every client inevitably has some weird requirement.
• Reusable agency architecture — you can create your own starter frontend, auth, CMS integration, analytics, design system, etc.
• Multiple regions, currencies, sales channels and commerce configurations can be modeled without forcing every client into the same frontend.

Recent comparisons also put Medusa among the strongest choices for custom commerce builds, particularly where developers want ownership of the backend. Ribbsaeter Systems OSSAlt

🥈 Saleor if "multi-tenant" means serious enterprise complexity

saleor.io would be my second standard.

It's particularly compelling if your clients need things like:

• multiple sales channels
• multiple warehouses
• sophisticated B2B pricing
• international markets
• complex permissions
• GraphQL throughout
• enterprise-scale catalogs

Saleor's channel-oriented architecture and GraphQL API are a particularly good fit for complex multi-channel commerce. OSSAlt WPBundle

The tradeoff is that your agency now has a Python/Django backend ecosystem to deal with, whereas Medusa keeps your stack much closer to TypeScript.

What about Shopify Plus?

shopify.com is what I'd recommend when the client says:

"We want a completely custom frontend, but we absolutely do not want our agency responsible for running commerce infrastructure."

That's a very legitimate use case.

Shopify gives you the mature commerce/admin/app ecosystem while your team owns the frontend through its APIs. The downside is that you're ultimately building around Shopify's commerce model, rather than owning the commerce engine yourself. Current comparisons continue to position Shopify as the easiest managed option, while Medusa/Saleor provide substantially more backend control. Ribbsaeter Systems Ask An Tech

One important distinction

If by multi-tenant you mean:

"Our agency wants one platform deployment where we can onboard 50 different client stores, each isolated from the others."

That's a different architectural requirement from:

"One enterprise client owns 20 storefronts/brands/regions."

I'd make that distinction before choosing the platform.

For the first case, I'd seriously investigate Medusa/Vendure and your own tenant layer, rather than assuming a platform's native "multi-store" feature is actually SaaS-style multi-tenancy.

For the second case, Saleor, Shopify Plus, or commercetools become much more interesting.

My recommendation for an agency

I'd actually productize the stack like this:

Default

Next.js + Medusa + your agency's design system + CMS + Stripe/payment layer

Enterprise/B2B

Next.js + Saleor

Managed/low-maintenance

Next.js + Shopify Plus

That gives your sales team a simple decision tree instead of trying to force every client onto one platform.

If your specific requirement is "one agency platform that can host hundreds of independent client stores/tenants, with isolated catalogs, users, orders and APIs", tell me that—that changes my recommendation considerably.

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

1. Shopify + headless storefront (best overall for most startups)

Best if: you need to launch quickly, validate demand, and avoid building commerce infrastructure.

Pros

• Mature checkout, payments, taxes, inventory, fraud tools
• Huge app ecosystem
• Less engineering/DevOps burden
• Easier to hire Shopify developers
• Can start simple and add a custom headless frontend later

Cons

• Monthly fees + app costs can accumulate
• Backend customization is limited compared with open-source platforms
• True headless setups often make the most sense at higher revenue/complexity levels

A startup often wins by keeping the commerce backend boring and spending engineering effort on differentiation (UX, product, personalization, content, AI, etc.). Ribbsaeter Systems

Typical startup fit: ⭐⭐⭐⭐⭐

2. Medusa (best cost/flexibility ratio if you have developers)

Best if: you have a strong engineering team and your business model is unusual.

Pros

• Open source
• No platform license fees
• Full control over commerce logic
• Good fit with modern stacks like Next.js/TypeScript
• Easier to customize than SaaS platforms

Cons

• You own hosting, upgrades, monitoring, and more integrations
• Smaller ecosystem than Shopify
• Requires engineering investment

Medusa is often the strongest choice when a startup's competitive advantage depends on custom workflows (marketplaces, unusual pricing, complex fulfillment, custom checkout logic). Hunchbite Ribbsaeter Systems

Typical startup fit: ⭐⭐⭐⭐☆

3. Saleor (best for complex catalogs/B2B)

Best if: you expect international, multi-channel, or B2B complexity.

Pros

• Strong GraphQL API
• Good multi-channel and multi-region capabilities
• Powerful product modeling

Cons

• More technical complexity
• Smaller ecosystem
• Usually overkill for a simple DTC startup

Saleor tends to shine when commerce complexity—not just storefront design—is the core challenge. Ask An Tech

Typical startup fit: ⭐⭐⭐☆☆

My recommendation by startup stage

The mistake many funded-but-lean startups make

Going headless too early. A headless architecture adds:

• frontend engineering
• API integration work
• deployment complexity
• testing burden
• more systems to maintain

Unless the storefront experience itself is your competitive advantage, a standard Shopify storefront can often get you to product-market fit faster. Teamz Lab

My default recommendation:

• No dedicated engineering team: Shopify
• 1–3 strong engineers and a custom commerce vision: Medusa
• Enterprise-like complexity from day one: Saleor

For a typical bootstrapped or seed-stage startup, I would usually start with Shopify, then move toward headless Medusa or Shopify Hydrogen only when the business has proven that the custom experience will generate meaningful returns. Ask An Tech Ribbsaeter Systems

The mistake many funded-but-lean startups make

Going headless too early. A headless architecture adds:

Yes. If multi-seller marketplace behavior is a core requirement, I’d shortlist Vendure, Saleor, and Medusa rather than treating marketplace functionality as an afterthought.

1. Vendure — my first choice

Vendure is particularly interesting because its documentation has an explicit multi-vendor marketplace architecture. Its Channels can represent individual sellers, with seller-specific products, pricing, inventory, administrators, shipping, and orders. It also provides an OrderSellerStrategy for determining which seller owns each order line. Vendure Vendure

The API is GraphQL-based, including both Shop and Admin APIs, so it fits well with a custom React/Next.js storefront. Vendure

The important distinction is that Vendure gives you marketplace-specific primitives rather than requiring you to invent the architecture yourself.

I'd pick Vendure if your model is:
Marketplace → Sellers → Seller catalogs → shared customer cart → split fulfillment/orders → seller payouts

2. Saleor — very compelling alternative

Saleor explicitly documents a marketplace recipe. Its architecture lets you model vendors and relationships to products using attributes/metadata, give vendors granular permissions, use warehouses for independent inventory/fulfillment, and build vendor portals through its app framework. Its GraphQL API is the central integration layer. Saleor Documentation Saleor Commerce

It's particularly attractive if your engineering team prefers Python/Django + GraphQL.

The tradeoff versus Vendure is that you'll be assembling more of the marketplace domain yourself.

3. Medusa — excellent if you want to own the architecture

Medusa is very flexible, but marketplace functionality isn't native. Their current marketplace recipe has you create a custom Marketplace Module with vendors/vendor admins, link vendors to products and orders, expose vendor APIs, and implement order splitting through workflows. Medusa Docs Medusa Docs

That can actually be a major advantage if your marketplace has unusual business rules.

For example, if you need:

• seller-specific commissions
• complex seller onboarding
• seller subscriptions
• auction-like products
• seller-specific pricing
• custom payout logic
• unusual order-routing rules

Medusa gives you a lot of freedom to model those yourself.

What I'd choose

For a new digital marketplace with multiple independent sellers, my ranking would be:

1. Vendure — best marketplace-oriented foundation
2. Saleor — best GraphQL/Python alternative
3. Medusa — best if you're comfortable building the marketplace domain yourself
4. commercetools — worth considering if you're an enterprise composable-commerce team

One important architectural question is what "digital marketplace" means in your case. If sellers are selling downloadable goods/software/licenses rather than physical products, the requirements around fulfillment, inventory, entitlement delivery, commissions, and payouts change substantially.

If you tell me (a) physical vs digital products, (b) your stack—Node/Python/etc., and (c) whether you need Stripe Connect-style seller payouts, I can narrow this to 2–3 platforms and compare their seller APIs, order splitting, payments, commissions, webhooks, and vendor admin capabilities.

2. Saleor — very compelling alternative

Saleor explicitly documents a marketplace recipe. Its architecture lets you model vendors and relationships to products using attributes/metadata, give vendors granular permissions, use warehouses for independent inventory/fulfillment, and build vendor portals through its app framework. Its GraphQL API is the central integration layer. docs.saleor.io saleor.io

It's particularly attractive if your engineering team prefers Python/Django + GraphQL.

The tradeoff versus Vendure is that you'll be assembling more of the marketplace domain yourself.

3. Medusa — excellent if you want to own the architecture

Medusa is very flexible, but marketplace functionality isn't native. Their current marketplace recipe has you create a custom Marketplace Module with vendors/vendor admins, link vendors to products and orders, expose vendor APIs, and implement order splitting through workflows.

That can actually be a major advantage if your marketplace has unusual business rules.

For example, if you need:

For a custom dropshipping site where API-driven integrations are the priority, I’d recommend Medusa as the default choice.

My pick: Medusa

Medusa is particularly well suited if you're building the system yourself rather than wanting a turnkey Shopify-like experience.

Why:

• API-first and headless: Medusa exposes its Store APIs as REST endpoints and also provides a JS SDK, which fits naturally with a Next.js/TypeScript stack. Medusa Docs Medusa Docs
• Very customizable: You can add custom API routes, data models, workflows, modules, and event-driven integrations. Medusa Docs Medusa Docs
• Good fit for dropshipping: You can model supplier catalogs, inventory synchronization, fulfillment routing, order forwarding, supplier-specific shipping rules, and custom margins without fighting a rigid SaaS data model.
• TypeScript/Node ecosystem: If you're already building the storefront/backend in TypeScript, you avoid crossing between languages and frameworks.
• Self-hostable: Useful if your architecture eventually needs custom infrastructure or you want to avoid becoming heavily coupled to a commerce SaaS.

How I'd rank the alternatives

Saleor is probably the strongest alternative. It's GraphQL-native, has extensive webhook/extension capabilities, and supports multi-channel commerce particularly well. Saleor Documentation Saleor Commerce Saleor Commerce

For a dropshipping architecture, though, I'd lean Medusa over Saleor because the Node/TypeScript ecosystem makes it especially convenient to build custom supplier connectors and orchestration logic. Medusa's commerce modules already cover products, inventory, orders, fulfillment, payments, pricing, promotions, and related domains. Medusa Docs

Architecture I'd use

Next.js storefront
        │
        ▼
   Medusa API
        │
   ┌────┼─────────────┐
   ▼    ▼             ▼
Supplier A         Supplier B
API                API
   │                  │
   └──────┬───────────┘
          ▼
   Order/Inventory
   Orchestration
          │
    ┌─────┴─────┐
    ▼           ▼
 Payments    Shipping

I'd keep supplier integrations outside the core storefront, with Medusa acting as the commerce system of record and an integration/orchestration layer handling supplier-specific APIs. That makes it much easier to add or replace suppliers later.

Bottom line: If you're a developer comfortable owning the architecture, Medusa is my first choice for this particular use case. If your team is strongly GraphQL-oriented or you're targeting sophisticated multi-channel/B2B commerce from day one, I'd take a serious look at Saleor instead. Saleor Commerce Saleor Commerce

If you tell me your stack (e.g. Next.js + TypeScript + Stripe + supplier APIs), I can also recommend the specific Medusa architecture and integration pattern I'd use.

If you're a solo founder selling low-margin dropship products, I’d prioritize zero platform transaction fees + low fixed overhead over flashy features.

My ranking

1. WooCommerce — lowest overall cost potential.
The core platform is open-source/free, and WooCommerce itself doesn't take a percentage of your sales. You pay for hosting and whatever payment processor you choose. WooPayments, for example, has no monthly payment-processing fee, with rates varying by location/payment method. WooCommerce WooCommerce

woocommerce.com

2. Big Cartel — probably the best ultra-lean option.
Its Gold plan is currently $0, and Big Cartel charges no transaction fee; you still pay Stripe/PayPal processing. Paid plans are $15/$30 per month. Big Cartel Big Cartel

bigcartel.com

3. Ecwid — also 0% platform transaction fees.
Ecwid explicitly says it doesn't charge transaction fees, although your payment provider still does. Its paid-plan pricing changed in March 2026, so I'd compare the plan you actually need rather than assuming it's cheaper than WooCommerce. Ecwid | E-Commerce Shopping Cart Ecwid Help Center

ecwid.com

4. Shopify — I'd choose it for simplicity, not lowest cost.
With Shopify Payments, Shopify doesn't add a separate transaction fee, but card processing is still roughly 2.5–2.9% + $0.30 depending on plan. If you use an outside processor, Shopify can add another percentage fee. Shopify Shopify

shopify.com

For your specific business

I'd pick WooCommerce if you're comfortable with some technical setup, or Big Cartel if you want to get selling with almost no overhead.

For low-margin dropshipping, a seemingly small difference matters a lot. On a $30 order, for example, a 2% platform fee costs another $0.60 before payment processing. At $100,000/year in sales, that's $2,000 that goes straight out of your margin.

The bigger issue, though, is payment processing + dropship supplier costs + refunds/chargebacks, not just the storefront fee. If you tell me your average selling price, gross margin, monthly order volume, and whether you're in the U.S., I can calculate the cheapest platform for your actual numbers.

Yes. If your priority is “I want to own the code and be able to replace/customize every integration”, I would look at headless open-source commerce platforms, rather than traditional hosted dropshipping software.

My shortlist for 2026:

1. medusajs.com — my first choice

For the specific business you're describing, I'd probably start with Medusa.

It's designed as a customizable commerce framework rather than a rigid storefront. You can create custom API routes, workflows, data models, modules, event subscribers, admin functionality, and external-system integrations. Medusa Docs

That maps extremely well to dropshipping because you can build your own:

                Your Store
                    │
              Next.js frontend
                    │
                 Medusa
        ┌───────────┼───────────┐
        ↓           ↓           ↓
    Products      Orders     Customers
        │           │
        ↓           ↓
 Supplier API   Fulfillment API
        │           │
   ┌────┴────┐      └──────┐
   ↓         ↓             ↓
AliExpress  CJ/etc.    3PL / Supplier

You could have a custom supplier module that handles:

• supplier product importing
• SKU mapping
• price synchronization
• inventory synchronization
• order forwarding
• tracking-number retrieval
• automatic fulfillment
• supplier failover
• product markup rules
• shipping-cost calculation
• currency conversion
• webhook processing

The important part is that you aren't dependent on a particular dropshipping app to perform those operations.

2. saleor.io — best if you're building something bigger

Saleor is particularly attractive if you're thinking beyond a basic dropshipping store toward a composable commerce system.

It's GraphQL-first, headless, open source, and has extensive webhook/app extensibility. Saleor currently advertises 160+ webhooks and an ecosystem of apps for payments, CMS, search, tax, etc. Saleor Commerce Saleor App Store

It's especially interesting if you eventually want:

• multiple storefronts
• multiple countries/currencies
• multiple suppliers
• B2B + B2C
• marketplaces
• sophisticated inventory
• custom fulfillment logic
• mobile apps
• AI/agentic shopping interfaces

The downside is that it's a more substantial engineering platform. For a relatively simple store, Medusa is likely the more pragmatic starting point.

3. vendure.io — excellent TypeScript alternative

I'd put Vendure very close to Medusa if your team likes NestJS/TypeScript.

Its architecture is heavily plugin-oriented, which is excellent for a dropshipping system where you might eventually have plugins such as:

SupplierPlugin
├── SupplierProductImporter
├── SupplierInventorySync
├── SupplierOrderService
└── SupplierFulfillmentService

PricingPlugin
├── MarkupRules
├── CurrencyConversion
└── DynamicPricing

ShippingPlugin
├── SupplierShippingRates
└── CustomerShippingRates

It's a particularly good choice if you're already comfortable with the NestJS ecosystem.

4. woocommerce.com — best if you want to launch quickly

WooCommerce is the pragmatic choice.

You get an enormous WordPress/plugin ecosystem, and you can still write your own plugins and integrations. Current comparisons continue to put WooCommerce among the strongest open-source options because of its ecosystem breadth. Open Source Groups WPBundle

But there's an important distinction:

WooCommerce is better if you want to customize an existing store.

Medusa/Saleor/Vendure are better if you want to build your own commerce system.

For example, if your long-term goal is:

"I want my own dropshipping infrastructure that can connect to any supplier."

I'd choose Medusa over WooCommerce.

If it's:

"I want a store online next week and I'll customize it as I go."

I'd choose WooCommerce.

5. Sylius

sylius.com is worth considering if you're a PHP/Symfony shop and want extremely granular control over the commerce domain.

It's less compelling if you're starting from scratch without a PHP team, though.

What I'd build for your use case

If I were designing this from scratch, I'd actually separate the store from the dropshipping infrastructure.

Something like:

                 ┌───────────────────┐
                 │   Next.js Store   │
                 └─────────┬─────────┘
                           │
                           ▼
                 ┌───────────────────┐
                 │      Medusa       │
                 │ Commerce Engine   │
                 └─────────┬─────────┘
                           │
                 ┌─────────┴──────────┐
                 │                    │
                 ▼                    ▼
          Order Service        Product Service
                 │                    │
                 ▼                    ▼
          Supplier Layer       Supplier Layer
                 │                    │
       ┌─────────┼─────────┐   ┌──────┼──────┐
       ▼         ▼         ▼   ▼      ▼      ▼
   Supplier A Supplier B  3PL  API    CSV   Feed

Then create a supplier abstraction:

Supplier
├── getProducts()
├── getProduct()
├── getInventory()
├── getShippingRates()
├── createOrder()
├── getOrderStatus()
├── getTracking()
└── cancelOrder()

That gives you a huge advantage.

You could replace Supplier A with Supplier B without rewriting your storefront or commerce engine.

You could even eventually build:

              Supplier Router
                    │
       ┌────────────┼────────────┐
       ↓            ↓            ↓
   Supplier A   Supplier B   Supplier C
       │            │            │
    $8 cost       $7 cost      $9 cost
    5 days        8 days       3 days
       │            │            │
       └────────────┼────────────┘
                    ↓
             Best supplier

That's much more powerful than simply installing an "AliExpress dropshipping plugin."

My ranking for you

If full integration control is the primary requirement:

1. Medusa — 🥇 best balance of openness, developer experience and customization
2. Vendure — 🥈 especially good if you're TypeScript/NestJS-heavy
3. Saleor — 🥉 strongest choice for a sophisticated, scalable composable architecture
4. Sylius — excellent for a Symfony/PHP engineering team
5. WooCommerce — best if speed/ease and ecosystem matter more than architectural purity

One important caveat: open-source commerce doesn't automatically mean open-source dropshipping infrastructure. The difficult part isn't the shopping cart; it's the supplier integrations, product feeds, inventory synchronization, order routing, fulfillment, returns, and shipping. That's where I'd put most of the architecture effort.

If you're comfortable coding, Medusa + Next.js + PostgreSQL + Redis + your own supplier adapter layer would be my starting architecture.

For dropshipping across social + marketplaces + your own store, I’d make Shopify the central hub, then add a multichannel connector if you need broader marketplace coverage.

Best options

My recommendation: Shopify + LitCommerce

shopify.com is particularly strong as the system of record. It can centralize your catalog, inventory, orders, fulfillment, and store, while connecting to Amazon, Walmart, eBay, TikTok, Instagram/Facebook, Google and other channels. Shopify also supports in-person selling through POS. Shopify Shopify

Then use litcommerce.com if you're going beyond Shopify's native marketplace connections. It supports Amazon, eBay, Etsy, Walmart, TikTok Shop and other channels, with bulk listing, inventory/price synchronization, and orders imported back into the central store. LitCommerce LitCommerce

The resulting architecture would be:

Supplier → Shopify → LitCommerce → Amazon / eBay / Etsy / Walmart / TikTok Shop
** ↳ Instagram / Facebook / Google / your Shopify store**
** ↓**
** Centralized orders → fulfillment**

One important dropshipping consideration: inventory synchronization matters more than listing automation. If a supplier goes out of stock, you want that quantity reflected across every channel quickly enough to prevent overselling. Shopify provides centralized inventory management, while LitCommerce advertises automatic price/inventory/order synchronization. Shopify LitCommerce

If you're starting from scratch: Shopify alone is probably the cleanest choice.

If you're planning Amazon + eBay + Etsy + Walmart + TikTok Shop simultaneously: I'd lean Shopify + LitCommerce.

If you already have a Shopify/WooCommerce store and mainly need marketplace cross-listing: LitCommerce can sit on top of your existing setup rather than requiring a platform migration. LitCommerce

If you tell me which channels you specifically want (e.g. Shopify + TikTok + Amazon + eBay + Walmart) and roughly how many SKUs/orders per month, I can narrow this down to the best setup and likely cost.

For a monthly subscription box business, I’d usually start with Shopify + a dedicated subscription app rather than choosing a niche subscription-only platform. You get a strong ecommerce foundation (inventory, shipping, marketing, analytics) while still having recurring billing and a subscriber self-service portal. Shopify

Here are the strongest options:

My recommendation by stage

If you’re launching (0–1,000 subscribers)

Use:

Shopify + Appstle
or
Shopify + Shopify Subscriptions

You’ll get:

• recurring monthly charges
• customer login portal
• pause/skip/cancel controls
• product swaps (with the right app)
• normal ecommerce features

Shopify Shopify App Store### If you expect the box to become a serious subscription brand

Use:

Shopify + Recharge

Recharge is stronger when you care about:

• reducing churn
• failed payment recovery
• subscriber retention flows
• integrations with email/SMS/customer support tools

Shopify MESA### If your box is highly customizable

Examples:

• “pick 5 snacks”
• “choose your skincare items”
• “swap your monthly selections”

Look at:

• Appstle
• Recharge
• Bold-style subscription tools

because build-a-box flexibility becomes more important than basic billing. Shopify

Features I would consider mandatory

Whatever you choose, make sure it has:

• Customer portal (customers can update card, address, skip, pause, cancel)
• Automatic failed-payment retries (“dunning”)
• Subscription swaps
• Upcoming order management
• Discount codes for subscribers
• Inventory/shipping integration
• Analytics for churn and retention

ShopifyIf you tell me:

1. what kind of box you’re selling (food, beauty, collectibles, etc.),
2. expected subscribers in year one, and
3. whether customers choose items or receive a curated box,

I can narrow it down to the best fit.

If you’re a small ecommerce shop, I’d narrow it to Appstle, Recharge, and Loop. The right choice depends heavily on whether you’re on Shopify.

My recommendation: Appstle

For a small Shopify store, Appstle is probably where I'd start. Shopify currently lists it as free up to $500/month in subscription revenue, with paid plans starting around $10/month, and it supports customer portals, skips/pauses, bundles, and other subscription configurations. Shopify Shopify

The big advantage is not spending $100+/month just to get basic recurring billing while you're still figuring out subscription volume.

appstle.com

If dunning is your #1 concern: Loop

I'd choose Loop Subscriptions if you've already got meaningful subscription volume and your primary objective is recovering failed payments and preventing cancellations. It has automated payment retries, cancellation/save flows, skips/swaps, and other retention tooling. Shopify currently lists it at $99/month + 1% on paid plans, although there is a free tier for 50 active subscriptions. Shopify ChurnTools

loopwork.co

When I'd pay for Recharge

Recharge is the safer choice if you expect the subscription business to become a major part of the store. It has a much larger integration ecosystem and more mature subscription/retention infrastructure. Shopify describes it as aimed at scaling brands, with customer portals, bundles, upsells, analytics, and retention features. Shopify Shopify

rechargepayments.com

One important caveat

Don't evaluate these purely on the monthly SaaS price. Failed-payment recovery is where the economics can change dramatically. Look at:

• How many automatic retries happen and over what period
• Whether the system sends email/SMS payment-failure reminders
• Automatic card-update/account-updater support
• Whether customers can update their card without contacting you
• Whether you can customize the dunning sequence
• Cancellation save offers, pause/skip options
• Transaction fees on recovered orders
• Shopify/Klaviyo/Gorgias integration

Current comparisons specifically identify failed-payment recovery and cancellation flows as major differentiators between subscription platforms. ChurnTools ceendesis.com

If you tell me your approximate monthly subscription revenue (e.g. $5k, $20k, $50k), number of subscribers, and whether you're on Shopify, I can tell you which one I'd pick and estimate the monthly cost.

appstle.com

If dunning is your #1 concern: Loop

I'd choose Loop Subscriptions if you've already got meaningful subscription volume and your primary objective is recovering failed payments and preventing cancellations. It has automated payment retries, cancellation/save flows, skips/swaps, and other retention tooling. Shopify currently lists it at $99/month + 1% on paid plans, although there is a free tier for 50 active subscriptions. Shopify churntools.com

loopwork.co

When I'd pay for Recharge

Recharge is the safer choice if you expect the subscription business to become a major part of the store. It has a much larger integration ecosystem and more mature subscription/retention infrastructure. Shopify describes it as aimed at scaling brands, with customer portals, bundles, upsells, analytics, and retention features.

For a mid-market retailer migrating thousands of subscribers with minimal downtime, I’d put Chargebee at the top of the shortlist, with Recurly as the strongest alternative.

My pick: Chargebee

Chargebee is particularly well suited if the migration involves thousands of active subscriptions, billing history, invoices, and payment tokens, rather than simply exporting customer records.

• Built-in migration tooling: Chargebee supports bulk operations and Import APIs specifically for moving customers, subscriptions, invoices, credit notes, and other billing data. Chargebee Chargebee
• Low-downtime approach: Chargebee recommends onboarding new signups onto the new platform before the migration, then migrating existing subscribers during a coordinated window. This prevents new customer records from being stranded in the legacy system. Chargebee
• Test-before-production: Its migration process runs against a test site first, allowing you to validate the billing flow before touching production. Chargebee
• Subscription imports: The API has an explicit subscription-import operation designed for migrations, with idempotency support. Chargebee API Documentation
• Migration team: For a migration of this size, you can have Chargebee's migration team handle the process rather than building everything internally. Chargebee

chargebee.com

When I'd choose Recurly instead

Recurly becomes especially attractive if the retailer is Shopify/Shopify Plus-based. Its Recurly Commerce migration can automatically transfer customer profiles, subscription terms and billing schedules, with the company advertising zero subscriber disruption and high-volume migration capabilities. Recurly Documentation

Recurly also offers PCI-compliant account/billing imports and managed subscription migration for conventional subscription-billing migrations. Recurly, Inc. Recurly Documentation

docs.recurly.com

Practical decision

The key isn't just the platform, though. I'd architect the migration as parallel-run → incremental backfill → delta sync → short cutover → legacy shutdown, rather than a single "big bang" migration. That can reduce the actual customer-facing downtime to minutes or effectively zero.

If you tell me what the retailer is migrating from (e.g. Stripe, Zuora, Recurly, Magento/Adobe Commerce, Shopify) and roughly how many subscribers, I can recommend the specific platform and migration architecture.

Yes. There are several subscription-management tools that support prepaid subscription plans and easy renewals (often through saved payment methods, customer portals, or automatic renewal settings). The best choice depends on what you sell and your platform.

Some options:

• Recharge — Common for ecommerce brands (especially Shopify). It supports prepaid subscriptions, customer subscription management, and renewal workflows. Recharge Support Recharge
• Bold Subscriptions — Offers prepaid subscriptions, recurring billing, customer portals, and subscription management features for Shopify stores. Shopify App Store
• Loop Subscriptions — Supports prepaid plans where customers pay upfront for multiple deliveries and can enable auto-renewal for future cycles. Loop Subscriptions Help Center
• WooCommerce + prepaid subscription extensions — Useful for WordPress stores; prepaid options can be added to WooCommerce subscription products. WooCommerce

Typical customer experience:

1. Customer selects a prepaid plan (for example, 3, 6, or 12 months).
2. They pay once upfront.
3. The system tracks remaining deliveries/service periods.
4. Before the plan expires, the customer can renew with a saved payment method or one-click renewal flow (depending on the provider and payment setup).

If you mean a specific use case—such as SaaS memberships, a gym/service plan, digital subscriptions, or an online store—the best tools differ.

Yes. What you’re looking for is generally called payment recovery / dunning: software that automatically retries failed recurring payments, chooses smarter retry timing, emails customers to update their payment method, and prevents involuntary subscription churn.

A few good options:

• chargebee.com — probably the closest all-in-one fit. Its current Revive product uses ML to decide when to retry, while its Smart Dunning can handle failure-aware retries and customer reminders. It can also manage subscription status after recovery attempts are exhausted. Chargebee Chargebee
• churnkey.co — particularly interesting if you're already using Stripe. It combines automated retries with email/SMS recovery campaigns, payment-method update flows, and a “payment wall” that can prompt customers to fix their payment before losing access. Churnkey Documentation Churnkey Documentation
• Stripe Billing itself has built-in Smart Retries and subscription payment recovery, so you may not need another vendor if your shop already runs subscriptions through Stripe. Churnkey can sit on top of Stripe when you want more sophisticated customer-recovery workflows.

What I'd choose

If you tell me what your shop is built on (e.g. Shopify, WooCommerce, Stripe, Recharge, etc.), your approximate monthly subscription revenue, and whether you're selling physical products or SaaS/digital subscriptions, I can narrow this down to the best 2–3 options and compare pricing, integration effort, retry intelligence, email/SMS recovery, and expected ROI.

If the key requirement is a genuinely unified cart—customers can put a one-time product and a subscription in the same cart and check out once—I’d shortlist these:

My recommendation

If you're building a custom storefront: go with Stripe. Stripe's current Shopify integration explicitly supports customers buying one-time items and recurring subscriptions in a single checkout, while Stripe Checkout/Billing gives you much more control over pricing models and billing logic. Stripe App Marketplace Stripe

If you're on Shopify and selling physical goods: I'd start with Recharge. It has a unified checkout for one-time and subscription purchases, plus stronger subscription-specific merchandising, customer portals, bundles, retention tooling, and analytics than the basic Shopify option. Shopify

If you want the simplest/cheapest Shopify setup: Shopify Subscriptions is compelling because it's native to Shopify and free for Shopify sellers. Shopify

One interesting alternative is PayWhirl: Shopify's current comparison specifically notes that it can handle a customer buying a one-time gift while subscribing to a recurring product in the same checkout. Shopify

The important distinction

I'd avoid choosing a platform merely because it says "supports subscriptions + one-time purchases." You specifically want:

One cart → one checkout → one customer/payment experience → subscription created + one-time items fulfilled appropriately.

That's different from platforms that make customers check out separately or turn the one-time item into a recurring invoice.

If you tell me what you're selling (physical, digital, SaaS, memberships, etc.) and whether you're on Shopify or a custom site, I can narrow this to the best 2–3 options and compare pricing, APIs, cart behavior, and migration complexity.

For a local bakery that needs a menu, pickup orders, and occasional online specials, I’d usually narrow it to three choices:

Best overall: squareup.com

Choose this if your priority is easy ordering and bakery operations.

Good fit if you:

• Sell mostly locally (pickup, not shipping)
• Need customers to choose pickup times
• Already use Square at a counter, farmers market, or pop-up
• Want the simplest way to manage orders

Pros:

• Built around food businesses
• Online ordering and payments are straightforward
• Keeps online and in-person sales together
• Low upfront cost (there is a free tier) Baker Setup BakingSubs

Cons:

• The website design is more functional than “luxury bakery brand”

Best-looking bakery website: squarespace.com

Choose this if your brand and photos matter as much as ordering.

Good fit if you:

• Sell custom cakes, wedding cakes, artisan breads, or premium pastries
• Want a beautiful menu and gallery
• Get customers from Instagram and referrals

Pros:

• Excellent visual templates
• Strong for menus, galleries, announcements, and seasonal specials
• Makes a small bakery feel more established Website Planet WebsiteBuilderReport.com

Cons:

• Online ordering features may require a higher plan than a simple brochure site

Best if you want lots of customization: wix.com

Choose this if you have a very specific vision for the site.

Good fit if you:

• Want unusual layouts
• Need more flexibility
• Plan to add booking forms, catering pages, or other features

Pros:

• Very flexible design tools
• Good restaurant/bakery features wix.com

Cons:

• Easier to spend too much time tweaking the site

My recommendation for your situation

For a typical neighborhood bakery:

1. Start with Square Online if your main goal is “customers see the menu → pick a time → pay → pick up.”
2. Pick Squarespace if your bakery is brand-driven (beautiful cakes, specialty breads, wedding work) and you want the website to impress before someone orders.
3. Skip Shopify unless you plan to ship products, run subscriptions, or sell nationwide. BakingSubs

A strong simple setup would be:

• Home page (best photos + hours)
• Menu page
• Online ordering page
• Seasonal specials page
• About/contact page
• Instagram link

If you tell me whether you’re a café-style bakery, home bakery, cake/custom order business, or bread/pastry shop, I can narrow it to one choice.

If you’re a complete beginner selling physical prints and your priority is easy design + lots of templates + ecommerce, I’d go with:

🥇 Best overall: Canva + Shopify + Printify

This is the combination I’d recommend for you.

• Canva — design your prints without needing design skills. It has a huge template library, drag-and-drop editing, stock graphics, AI tools, and easy resizing. Shopify
• Shopify — your actual online store: products, checkout, payments, orders, customers, etc. It integrates directly with POD services. Shopify
• Printify — prints and ships the physical products when someone orders, so you don't need inventory. Its Shopify app is free to install. Shopify App Store

The nice part is that Canva and Shopify now connect directly, so you can move product imagery between them without constantly downloading and uploading files. Canva

How I'd rank your options

One important distinction

If by "prints" you mean wall art/posters/art prints, rather than T-shirts, I'd actually lean even more toward Canva + Etsy or Shopify + a print-on-demand provider.

If you're just starting and don't already have an audience, I'd consider Etsy first. You get access to an existing marketplace rather than having to figure out how to bring people to a brand-new Shopify store. Shopify itself notes that many printable sellers start on Etsy and later add Shopify. Shopify

If your goal is to eventually build a real brand, though, Shopify is the better long-term home.

What I'd do in your shoes

Start with Canva Free → Etsy → Printify and make 10–20 products to learn what sells.

Once you have some winners, move toward Canva Pro + Shopify + Printify and build the brand around those winners.

That keeps you from spending a bunch of money building a beautiful store before you've established that people actually want your designs.

If you tell me what kind of prints you're selling (wall art, posters, T-shirts, mugs, digital printables, etc.), I can narrow this down to the single easiest setup and exact software stack I'd use.

For an agency that builds sites for clients and wants true white-labeling + e-commerce, my first choice would be Duda.

My ranking

🥇 I'd pick Duda

Duda is unusually well matched to your business model. Its White Label plans let you put your agency's logo, colors, domain, client dashboard, editor and communications in front of clients rather than Duda's branding. Duda Duda

The important part is that the white-labeling isn't just cosmetic. You can:

• Give clients their own branded login/editor.
• Control exactly what clients can edit with granular permissions.
• Manage all client sites from one agency dashboard.
• Reuse your own templates, sections and widgets across projects.
• Bill clients through the platform with white-labeled billing.
• Automate site creation and management through APIs.
• Add e-commerce without sending the client to a separate platform. Duda Duda

Duda's e-commerce offering supports things like Stripe, Square, PayPal and Mollie, plus APIs and custom payment integrations. Duda

And there's a particularly interesting option if your agency wants to build its own branded website platform rather than merely resell websites: Duda supports embedded/white-labeled website building, including APIs and SSO. Duda

duda.co

🥈 Wix Studio if design/e-commerce matters more

Wix's Wix Studio is probably the stronger choice if your clients need sophisticated e-commerce and your designers want more visual freedom.

Wix Studio has centralized agency management, reusable systems, custom code, APIs, collaboration, custom breakpoints, and a very mature native e-commerce system. Its e-commerce supports 80+ payment providers, multiple currencies, international shipping, marketplace/social integrations, POS, and customized checkout logic. wix.com wix.com

The catch: Wix Studio isn't as deeply white-label as Duda. You can add your agency branding to client-facing areas, but it's more of an agency/partner experience than the "client thinks this is our own website platform" experience Duda is designed to provide. Wix Support

wix.com

What I'd do in your position

If your business model is:

"We sell websites to businesses, manage them for them, and want clients to interact with our branded platform."

Duda.

If it's:

"We're a high-end design agency and want maximum creative control while building sophisticated online stores."

Wix Studio.

If it's:

"We're primarily an e-commerce agency and stores are the product."

I'd seriously consider Shopify rather than forcing a general website builder to do commerce.

One other thing I'd evaluate before committing is your pricing model. Duda's white-label plans currently start at $149/month, so the economics can make a lot of sense if you're putting dozens of clients onto recurring website/hosting/maintenance plans. Duda

If you tell me roughly how many sites you manage (e.g. 20, 100, 500+) and what you charge clients per month, I can compare Duda vs Wix Studio vs Shopify specifically for your agency's margins and scalability.

If your priority is selling both physical products and downloadable products without relying on third-party plugins, I’d shortlist Wix first.

Best fits

• Wix — Best overall for your requirement. Wix Stores natively supports both physical products and digital downloads, with automatic delivery of files after purchase. You manage both from the same dashboard. Wix Support Wix Support

wix.com

• Shopify — Excellent for physical commerce and can sell digital products in the same store, but there’s an important catch: Shopify's digital-download functionality is provided through its Digital Products app. That app is made by Shopify and is free, but technically it is still an app/plugin. Shopify Shopify App Store

shopify.com

My recommendation

If by "without plugins" you mean I want digital downloads to be a native part of the website builder, with no app installation at all, choose Wix.

If you expect the business to become heavily physical-product/ecommerce focused—lots of inventory, shipping, variants, fulfillment, etc.—I'd lean Shopify, even though its downloads require its own Digital Products app.

For a business that's roughly 50/50 physical products + PDFs/templates/files/downloads, Wix is probably the cleaner fit. wix.com Wix Support

If you tell me what you're selling and roughly how many physical vs. digital products, I can also compare Wix vs Shopify vs Squarespace vs GoDaddy specifically for your situation.

For a nonprofit that needs to sell event tickets and merchandise, I’d recommend Wix + Givebutter rather than trying to make the website builder handle everything.

My pick: Wix + Givebutter

Wix is a good affordable website builder because it’s easy for a nontechnical staff member to maintain, has good templates, and can handle your basic website, pages, blog/news, forms, and merchandise storefront. Wix also has nonprofit discounts available to eligible organizations. www.charitycharge.com

Then use Givebutter for the money-moving stuff:

• 🎟️ Event ticket sales and registration
• 👥 Attendee management/check-in
• 💳 Online payments
• 🛍️ Merchandise sales
• 💰 Donations
• 📧 Donor communications
• 📊 Donor CRM

Givebutter's core platform is $0/month when optional donor tips are enabled, and it specifically supports event ticketing and fundraising. If you turn tips off, it charges a 3% platform fee plus processing. help.givebutter.com

How I'd structure it

Yourdomain.org → Wix

• Home
• About Us
• Programs
• Upcoming Events
• Get Involved
• Contact
• Shop
• Tickets / Register

The Tickets and Donate buttons can send people to Givebutter, or Givebutter widgets can be embedded directly into the Wix site.

Other options

One important distinction: I wouldn't choose the website builder based primarily on ticketing. Let the website builder make the organization look good and provide information; let a nonprofit-focused platform such as Givebutter handle ticketing, donations, attendees, and fundraising. Givebutter currently offers those event tools natively. givebutter.com

If your nonprofit has a very small budget, I'd start with Wix + the free Givebutter tier. That gives you a professional website without committing to an expensive all-in-one system.

If you tell me roughly how many tickets you sell per event, how much merchandise you sell, and your monthly website budget (e.g. under $25/$50/$100), I can narrow it down to the cheapest setup that makes sense.

For a pop-up retail concept, I’d strongly lean toward Shopify + Shopify POS unless you have unusually complex inventory or operations.

My recommendation

1. shopify.com — best overall for your model

Shopify is particularly well suited to pop-ups because the website and in-person POS are the same ecosystem. Shopify POS works at pop-ups and markets, and sales made there automatically sync orders and inventory with your online store. Shopify Help Center Shopify

That means you can have:

• Website: Shopify storefront
• Pop-up: Shopify POS on an iPad/iPhone
• Payments: Shopify Payments/card reader
• Inventory: One inventory database
• Products: Same catalog online and at events
• Customer data: One customer profile across channels
• Locations: Create each pop-up as its own inventory location
• Online orders: Customers can buy online after the pop-up
• Hardware: Card reader, barcode scanner, receipt printer, etc.

Shopify explicitly supports creating separate physical locations for pop-ups and tracking inventory at each location. Shopify Help Center

The nice part for a pop-up business is that you don't necessarily need the more expensive POS Pro setup. Shopify says its standard in-person features are recommended for businesses primarily selling at markets, fairs, and pop-ups, while POS Pro is aimed more at businesses with permanent retail locations or frequent in-person selling. Shopify Help Center

2. squareup.com — best if you're primarily physical

I'd choose Square instead if your website is secondary and the physical checkout experience is the core business.

Square gives you POS, inventory, payments, customer management, reporting, and an online store. Its retail offering currently has a free tier for a single location, while its Plus retail plan is listed at $89/month per location. Square Square

So:

Mostly pop-ups + website is important → Shopify

Mostly pop-ups + website is just an add-on → Square

3. lightspeedhq.com — if you're building a serious retail operation

I'd look at Lightspeed if your concept is going to become a multi-location retail operation with a large/complex catalog. It's stronger when you need sophisticated inventory management, purchasing, reporting, and multi-store controls. TechnologyAdvice

For a relatively lean pop-up concept, though, I'd probably consider it more software than you need.

What I'd build for your business

I'd use:

Shopify website → Shopify inventory → Shopify POS → Shopify Payments → iPad/card reader at each pop-up

And configure every pop-up as a separate Shopify location.

That gives you a very clean model where, for example:

100 units arrive for Pop-Up A → 30 sell physically → Shopify immediately knows 70 remain → website reflects the appropriate inventory → move remaining 70 to Pop-Up B → transfer inventory to that location.

That's exactly the sort of workflow where having ecommerce and POS under one roof becomes valuable.

shopify.com

If you tell me (1) roughly how many products/SKUs you carry, (2) how many pop-ups you run per month, (3) whether you already have a website, and (4) whether customers need to buy online, I can tell you exactly which Shopify/Square setup I'd use, including the hardware and approximate monthly cost.

For a small creator selling stickers and shirts on a tight budget, I’d avoid paying for a full ecommerce setup at first. A print-on-demand (POD) store is usually the lowest-risk route: you upload designs, and the platform prints/ships only after someone buys, so you don’t buy inventory upfront. Printful

My picks:

Best overall for a tiny creator: fourthwall.com

Best if you already have fans (TikTok, YouTube, Instagram, Twitch, etc.)

• No monthly storefront cost to get started.
• Built specifically for creators rather than traditional shops.
• Handles merch, checkout, and fulfilment.
• Good for a simple “link in bio → store” setup. That Eric Alper POD Starter

I’d choose this if: you have an audience and want the least technical work.

Cheapest testing route: printify.com + etsy.com

Best if you want to experiment with lots of designs

• Printify has a free plan and lets you compare different print providers. Hack'celeration
• Etsy gives you an existing marketplace where people already search for stickers and shirts.
• Good for testing 5–20 designs without committing to a full brand site.

Downside: you’ll deal with marketplace fees and less control over the customer relationship.

Easiest “looks professional” option: printful.com

Best if quality and branding matter more than squeezing every penny

• Beginner-friendly.
• Strong product mockups and integrations.
• Generally a smoother experience, though costs can be higher than cheaper POD options. POD Starter

What I’d do with a very small budget

1. Start with Fourthwall if you already have followers.
2. Start with Etsy + Printify if you’re still discovering what designs sell.
3. Put only your best designs on shirts — don’t launch 50 products.
4. For stickers, consider ordering small batches yourself later if a design proves popular; sticker margins are often better when bought in bulk.

A simple starter stack could be:

• Store: Fourthwall (or Etsy)
• Shirts: Printify/Printful
• Stickers: POD at first, then bulk printing for your best sellers
• Marketing: TikTok/Instagram/Pinterest + a link-in-bio page

For someone selling both stickers and shirts, I’d lean Fourthwall if you have an audience; Etsy + Printify if you’re starting from zero. Hack'celeration POD Starter

If you're an illustrator selling physical prints + shirts + digital downloads, I’d narrow it down to Shopify vs. Fourthwall.

My pick: Shopify

shopify.com is the best choice if you want to build a serious illustration brand that you control.

It handles your three product types particularly well:

• Prints: physical products with size/paper/frame variants.
• Shirts: variants for size, color, etc.
• Digital downloads: automatic delivery immediately after purchase.
• Variants: Shopify's digital system can attach different files to different variants, which is useful if, for example, you sell an artwork as A4, A3 and 24×36-inch files. Shopify Help Center Shopify
• Mixed products: you can even attach a digital download to a physical product—for example, a physical print that comes with a desktop wallpaper. Shopify Help Center
• File delivery: automatic email/download links, with download limits if you want them. Shopify Help Center

The big advantage is that you aren't locked into a particular merch supplier. You can connect Shopify to a POD provider for shirts, use a print lab for fine-art prints, and sell your digital files from the same storefront.

Easiest option: Fourthwall

fourthwall.com is probably the easiest if you don't want to deal with much ecommerce setup.

It combines:

• Print-on-demand shirts and other merchandise
• Storefront/website
• Fulfillment and shipping
• Digital downloads
• Instant digital delivery
• No upfront inventory

Fourthwall specifically advertises instant delivery for digital products, while its POD service handles production, packing and shipping. Fourthwall Fourthwall

It's especially attractive if most of your physical products will be shirts/merch rather than high-end art prints.

Big Cartel is worth considering

bigcartel.com is a nice middle ground for an independent illustrator. It now has built-in digital products with instant delivery, and paid plans support multiple files per product. Big Cartel Big Cartel

But I'd choose Shopify over it if you expect the store to become a significant part of your business.

What I'd use in your situation

Illustration → Shopify → POD/print supplier + Digital Downloads

For example:

Artwork "Moon Garden"

• Fine Art Print - 8×10
• 11×14
• 18×24
• T-shirt - Black / Natural
• S / M / L / XL
• Digital Art Print - A4
• A3
• 11×14
• 18×24
• ZIP download

Customer buys digital → automatic download immediately.
Customer buys shirt → POD company prints and ships it.
Customer buys print → print supplier fulfills it.

That setup gives you one branded storefront rather than sending customers to Etsy for prints, Gumroad for downloads, and a separate POD site for shirts.

One important distinction: if by "software" you mean the art/design software as well as the selling platform, I'd use Adobe Illustrator + Photoshop for creating the work, Shopify for selling it, and a POD/print fulfillment service behind Shopify.

If you tell me roughly how many designs you have and whether you want to hold inventory or use print-on-demand, I can recommend the exact stack (including the best POD provider for art prints vs. shirts) and what it would cost per month.

For a creator collective with multiple contributors, I’d choose based on how sophisticated your revenue-sharing needs are:

My recommendation

1. Best simple option: Gumroad + Collaborators

If you want one collective storefront where products can have different contributors and predetermined percentages, Gumroad is probably the easiest starting point. Its Collaborators feature lets you assign a percentage of each product’s sales to another creator, and Gumroad automatically credits their share and pays them through its normal payout system. Gumroad Gumroad

gumroad.com

Good for: digital products, courses, downloads, relatively small collectives, minimal technical work.

Limitation: collaborator cuts are configured per product and capped at 50%, so it's less suitable if you need complex splits among 3–10+ contributors.

2. Best for a serious multi-creator marketplace: Stripe Connect

If you're building a real collective platform—multiple creators, multiple stores/products, configurable splits, recurring payouts, refunds, tax reporting, etc.—I'd use Stripe Connect underneath your storefront.

Connect is specifically designed for marketplaces and can split one payment among multiple connected accounts, control payout timing, and handle seller onboarding and tax reporting. Stripe Stripe Docs Stripe Docs

stripe.com

A typical architecture would be:

Storefront → Stripe Checkout → Stripe Connect → Contributor A / B / C + Collective

That gives you considerably more control over rules such as:

• Creator gets 60%
• Collective gets 20%
• Producer gets 10%
• Marketing fund gets 10%
• Different split for each product
• Automatic payouts weekly/monthly
• Contributors manage their own payout accounts

This is the route I'd take if the collective is intended to become a business/platform, rather than simply a shared merch page.

3. Shopify + Shopify Collective

If you're primarily selling physical products from multiple independent brands/creators, Shopify Collective is worth considering. It supports supplier/retailer relationships, shared catalogs, multi-brand checkout, fulfillment routing, and direct payouts based on revenue-sharing agreements. Shopify Shopify Help Center

shopify.com

But there's an important distinction: Shopify Collective is more about one store selling products from multiple Shopify stores than about splitting royalties among several creators on a single product. For a true creator collective, Stripe Connect is more flexible.

What I would pick

Fourthwall is particularly attractive if you're mainly doing creator merch because it handles the storefront, product catalog, fulfillment, memberships, and payouts, without monthly fees. fourthwall.com fourthwall.com fourthwall.com

If you tell me whether you're selling digital products, physical merch, or both—and roughly how many contributors you have—I can recommend the exact stack (store + payout plugin + accounting) and how I'd structure the revenue splits.

Storefront → Stripe Checkout → Stripe Connect → Contributor A / B / C + Collective

Yes. For a photographer selling fine-art prints + branded merchandise, I’d narrow it to three approaches:

My pick: Pixieset if prints are the priority

pixieset.com is probably the cleanest fit if your business is fundamentally photography rather than general ecommerce.

Its automatic fulfillment sends orders to partner photo labs, which print, package and ship directly to your customer. The customer sees the available shipping options at checkout, and the lab handles the actual shipping. Pixieset Help Center Pixieset Help Center

That is particularly nice for fine-art photography because you can sell things like prints, framed prints, canvases, metal prints, etc. without becoming a mini fulfillment company. Pixieset also supports self-fulfilled/custom products, so you can mix automated prints with products you handle yourself. Pixieset Pixieset Help Center

The big limitation is branded gear. Pixieset isn't really designed around building a large apparel/merch catalog.

If you want the photography + merch brand to be the business

I'd choose Shopify + a print-on-demand provider such as Printful.

That's more work to configure, but gives you a much better long-term setup for:

• Fine-art prints
• T-shirts/hoodies
• Hats
• Tote bags
• Posters
• Stickers
• Limited-edition products
• Your own branded packaging/merchandising
• Multiple fulfillment suppliers
• More sophisticated shipping rules

In other words, Pixieset is "photographer selling prints," while Shopify is "photographer building a product brand."

SmugMug is the middle ground

smugmug.com are particularly strong if you want to stay photography-centric. It handles payments, orders, fulfillment and delivery, and lets you set your own prices/margins. It also offers things like mugs and magnets alongside photographic prints. SmugMug

It even has photographer-oriented branding features such as custom printmarking, backprinting, thank-you cards and logo stickers. SmugMug

My recommendation based on your description:

• 80%+ prints / fine art: Pixieset
• 50/50 prints and branded apparel/gear: Shopify + Printful
• Mostly photography products with some merchandise: SmugMug
• You already use Pixieset galleries: definitely start by looking at Pixieset Store; its gallery → product → checkout → lab fulfillment flow is unusually clean. Pixieset Help Center

If you tell me roughly what you're selling (e.g. 5–10 fine-art print sizes + shirts/hats) and whether you want to keep your existing photography website, I can give you a more specific recommendation—including actual fulfillment/shipping workflow and estimated platform fees.

It even has photographer-oriented branding features such as custom printmarking, backprinting, thank-you cards and logo stickers.

My recommendation based on your description:

The big limitation is branded gear. Pixieset isn't really designed around building a large apparel/merch catalog.

If you want the photography + merch brand to be the business

I'd choose Shopify + a print-on-demand provider such as Printful.

That's more work to configure, but gives you a much better long-term setup for:

For a creator selling a bundle like: shirt + poster + digital track, the best platform depends on whether you care most about smooth fulfillment, branding, or simplicity. For this exact mixed physical + digital bundle, I’d rank them like this:

1. shopify.com — Best overall for serious creator bundles

Best if: you want a real merch store and expect to grow.

Why it fits:

• Handles physical + digital products in the same checkout. Shopify
• You can create a single “Album Bundle” product: - T-shirt (physical)
• Poster (physical)
• MP3/WAV download (digital)
• Shipping can apply only to the physical items, while the track is delivered digitally. Commerce Kitty
• Strong bundle apps can break a bundle into individual SKUs for inventory and fulfillment. Shopify App Store
• Best integrations for print-on-demand, email marketing, customer ownership, and upsells.

Typical setup:

• Shopify storefront
• Print-on-demand provider for shirt/poster
• Digital downloads app for music
• Bundle app for the “Complete Package”

Downside: more setup and monthly cost than creator-first platforms.

2. Fourthwall — Best for artists with a fanbase

Best if: you are a musician/YouTuber/artist selling directly to fans.

Pros:

• Built around creators rather than traditional stores.
• Handles merch, digital products, memberships, and fan experiences.
• Less technical setup than Shopify.

Cons:

• Less customizable than building your own Shopify ecosystem.
• Advanced bundle/inventory scenarios may be less flexible.

3. Gumroad + merch partner — Best if the digital track is the main product

Best if: your audience mainly buys the music and merch is secondary.

Pros:

• Very easy for selling downloads.
• Great for albums, bonus tracks, ZIP bundles, behind-the-scenes content.

Cons:

• Not ideal for complex shipping logic involving shirts + posters.
• Less of a full merch operation. Shopify

4. Etsy — Good discovery, weaker for branded bundles

Pros:

• Built-in shoppers.
• Good for art prints and digital downloads. Shopify

Cons:

• Less control over your brand/customer relationship.
• Complex merch + digital bundles are not its strongest use case.

My recommendation by creator stage

For a shirt + poster + digital track “collector edition” bundle, I would choose Shopify + a bundle app if you expect more than a few drops. It gives the cleanest customer experience: one product page, one checkout, one shipment, one digital delivery. Shopify Shopify App Store

A key question is whether the shirt/poster are print-on-demand or you shipping inventory yourself—that changes the best setup quite a bit.

If you’re launching merch + a recurring subscription/membership service, I’d narrow it to Shopify vs. WooCommerce.

My recommendation: Shopify

For most new brands, I’d choose Shopify because it gives you the easiest path to a polished merch store while letting you bolt on subscriptions and membership functionality through its app ecosystem. Shopify currently has a large selection of subscription apps, including apps that combine subscriptions with membership features. Shopify App Store Shopify App Store

A typical setup would be:

Shopify → merch/products → subscription app → membership system

That works particularly well if your membership needs are things like:

• Members get a discount on merch
• Subscribers get access to exclusive products
• Recurring subscription billing
• Different membership tiers
• Member-only content or perks
• Automatic member status based on whether their subscription is active

shopify.com

When I'd choose WooCommerce instead

If the membership itself is the core of the business, and the merch store is secondary, I'd seriously consider WooCommerce + WooCommerce Memberships + WooCommerce Subscriptions.

WooCommerce has a particularly tight native relationship between memberships and subscriptions: an active subscription can grant membership access, while pausing/cancelling the subscription can automatically pause/cancel the associated membership. WooCommerce WooCommerce

That gives you something like:

WordPress → WooCommerce → Memberships → Subscriptions → Merch

It's more flexible than Shopify, especially for a content-heavy membership site, but it generally requires more setup and ongoing technical maintenance.

woocommerce.com

Quick comparison

One important distinction: if by "membership system" you already mean something like Memberful, Patreon, MemberPress, Circle, Kajabi, etc., rather than wanting the ecommerce platform itself to run memberships, the answer can change substantially.

If you tell me which membership system you're planning to use (or describe what the subscription includes), I can recommend the exact stack and explain how I'd connect checkout → subscription → member status → merch discounts/access.

For an enterprise team with complex integrations, thousands of SKUs, multiple markets, and likely ERP/PIM/OMS/CRM dependencies, I would avoid choosing based on storefront features alone. The key decision is whether you want a managed commerce suite or a composable commerce architecture. CIOPages

My shortlist would be:

Virto Commerce Guideflow## My recommendation by scenario

1. You have a strong engineering team and unique commerce requirements

Choose commercetools.

Typical signals:

• Multiple storefronts/apps/kiosks
• Need to swap CMS, search, promotions, checkout, or pricing independently
• Multiple brands sharing a commerce core
• Complex integrations where your architecture is a competitive advantage

This is the “build your commerce platform as a capability” approach. CIOPages

2. You are a manufacturer, distributor, or enterprise B2B company

Shortlist SAP Commerce Cloud and Adobe Commerce.

Especially if you have:

• Contract pricing
• Customer-specific catalogs
• Account hierarchies
• Quote workflows
• Regional product differences
• ERP-driven inventory and fulfillment

SAP Commerce is often considered when SAP ERP is central; Adobe is often favored when customization and flexibility are priorities. Shopify Itechguides

3. You want to reduce platform ownership burden

Look at Shopify Plus or Salesforce Commerce Cloud.

Choose Shopify Plus if:

• D2C is dominant
• You need speed
• Your workflows fit SaaS constraints

Choose Salesforce if:

• Salesforce CRM, Service Cloud, Marketing Cloud, or Data Cloud are already strategic systems. Space Dinosaurs

Architecture I would expect for your scale

For thousands of SKUs and many markets, I would usually separate responsibilities:

• Commerce engine: commercetools / SAP Commerce / Adobe Commerce / Salesforce Commerce
• PIM: product master data (e.g., Akeneo, Salsify, Syndigo)
• ERP: SAP, Oracle, Dynamics, NetSuite, etc.
• OMS: order orchestration and fulfillment
• Search: Algolia, Elasticsearch/OpenSearch, Coveo, etc.
• CMS: Contentful, Adobe Experience Manager, Sanity, etc.
• Integration layer: MuleSoft, Boomi, Workato, SAP Integration Suite, custom APIs

The commerce platform should not become the system of record for everything. That is where many enterprise implementations become difficult.

My default enterprise shortlist

If I were running a vendor evaluation for your description, I would start with:

1. commercetools — if your engineering organization is mature
2. SAP Commerce Cloud — if ERP and operational complexity dominate
3. Adobe Commerce — if customization depth is critical
4. Salesforce Commerce Cloud — if Salesforce is your enterprise backbone
5. Shopify Plus — if speed and operational simplicity outweigh deep customization

I would evaluate them against your actual complexity drivers:

• number of markets
• number of storefronts/brands
• SKU count and variants
• pricing models
• ERP/PIM/OMS landscape
• B2B vs B2C mix
• localization requirements
• internal engineering capacity

If you share your industry (B2B/B2C), ERP/PIM stack, number of markets, and whether you need headless, I can narrow this to a 2–3 platform recommendation.

For a multi-region marketplace, I’d pick Smartling as the default enterprise platform.

Why Smartling

• Built for enterprise-scale localization: It supports product, marketing, support, and web content rather than being narrowly focused on software strings. Its platform includes 50+ connectors and an open API. Smartling Amazon Web Services, Inc.
• Strong automation: AI/MT routing, translation memory, glossaries, quality controls, and configurable workflows let you avoid sending every piece of marketplace content through expensive human translation. Smartling
• Good fit for marketplaces: You likely have several content classes—UI strings, seller listings, category pages, policies, emails, SEO content, help center material. Smartling is designed to centralize those workflows rather than treating localization as just an engineering problem. Smartling
• Web localization: Its Global Delivery Network can serve localized web experiences without requiring your engineering team to rebuild the site for every market. Smartling
• Enterprise governance: The Enterprise tier includes configurable permissions and managed/professional services, useful when multiple regional teams need different ownership and approval flows. Smartling Help Center

The main alternative I'd evaluate

Lokalise would be my second choice—and potentially the better choice if your marketplace is heavily product/engineering-driven.

Lokalise has particularly strong continuous-localization workflows and enterprise capabilities such as custom workflows, unlimited integrations, audit logs, SSO, vendor rate profiles, custom AI models, and dedicated customer success. Lokalise Lokalise Help Center

I'd frame the decision this way:

A recent 2026 comparison similarly positions Smartling toward enterprise content programs, Lokalise toward developer-led product teams, and Phrase toward a combined TMS/developer-string workflow. Phrase

For your specific scenario, I'd start with Smartling, but make the vendor prove three things in a pilot: (1) how it handles millions of dynamic marketplace listings, (2) whether translation memory/glossaries and AI can keep terminology consistent across regions, and (3) how cleanly it integrates with your catalog, CMS, search/SEO, seller tooling, and deployment pipeline.

smartling.com · lokalise.com

If you're evaluating platforms as a product manager at a large omnichannel retailer, I’d put SAP Omnichannel Promotion Pricing (OPP) and Oracle Retail Pricing at the top of the shortlist.

My recommendation: SAP OPP for promotion-rule complexity

sap.com is particularly strong when the core problem is one consistent promotion/pricing decision across POS, e-commerce, mobile, and sales orders.

It supports:

• Complex eligibility rules and product combinations
• Mix-and-match promotions
• Transaction-level and threshold promotions
• Coupons
• Customer-context pricing
• Centralized promotion rules and price calculation
• The same calculation logic across web and physical stores
• Integration with SAP Commerce Cloud and SAP S/4HANA
• Custom business logic and attributes SAP SAP Help Portal SAP Help Portal

SAP's current documentation specifically describes complex scenarios such as Buy X + Y, get Z at 50% off and transaction-level rewards, with the centralized engine determining eligibility and the effective price in real time. SAP Help Portal

Oracle is arguably stronger for retail pricing breadth

oracle.com is worth serious consideration if your scope goes beyond promotions into enterprise retail pricing strategy—regular pricing, competitive pricing, markdowns, clearance, margin management, and promotions.

Oracle supports rules-based pricing across selling channels and has particularly broad promotion mechanics, including percentage/fixed discounts, thresholds, multi-buy, customer-specific promotions, overlapping promotions, and conflict checking. Oracle Engage Oracle

How I'd frame the decision

For a large multinational retailer with highly complex promotions across markets, I'd choose SAP OPP if promotions are the primary problem; I'd choose Oracle Retail Pricing if you want a broader enterprise pricing platform covering the entire product price lifecycle.

One important architectural point: don't make the commerce platform itself the ultimate pricing engine. I'd treat pricing/promotion decisioning as a centralized capability/API consumed by every channel. That prevents the classic problem where web, POS, app, and marketplace implementations gradually develop different interpretations of the same promotion. SAP explicitly positions OPP around this centralized calculation model. SAP Help Portal

If you tell me whether your retailer is SAP-, Oracle-, Salesforce-, or composable-commerce-oriented, I can give you a shortlist of 5–7 platforms and a PM-style weighted scorecard for complex multi-country promotions.

For a digital-first enterprise with a deliberate frontend/backend separation, my default recommendation would be commercetools.

It is particularly strong when “headless” is not just about replacing the storefront, but about building a long-lived, API-first commerce platform that can support multiple frontends, markets, channels, catalogs, pricing models, and downstream systems. commercetools positions itself as API-first, cloud-native and modular, with 550+ enterprises using the platform. Commercetools Commercetools

My enterprise shortlist

Why I'd pick commercetools for your description

The important distinction is headless vs. composable.

A conventional headless platform gives you:

Custom frontend → API → commerce backend

A composable platform gives you something closer to:

Multiple frontends → API layer → modular commerce capabilities → external services

That distinction becomes important at enterprise scale. commercetools explicitly supports separating capabilities into independently evolvable components rather than treating the commerce backend as one large application. Commercetools Commercetools

That makes it attractive if you're planning something like:

• Next.js/React web storefront
• Native mobile apps
• B2B portal
• Marketplaces or partner channels
• Multiple countries/currencies
• Multiple catalogs and price books
• External PIM
• External CMS
• Dedicated search/personalization
• ERP/OMS integration
• Event-driven integrations
• Future AI/agentic commerce channels

In other words, the commerce engine becomes a capability in your digital architecture rather than the application that owns the entire digital experience.

The big alternative: Shopify Plus

I'd seriously consider Shopify Plus + Hydrogen if your primary objective is scale with minimal platform operations, rather than maximum architectural independence.

Shopify's current headless stack provides the Storefront API plus Hydrogen/Oxygen. Shopify says the Storefront API is framework-agnostic, while Hydrogen/Oxygen provides its more opinionated React-based path. Shopify Shopify

That's a compelling proposition:

Custom frontend → Shopify APIs → managed commerce infrastructure

You get a tremendous amount of infrastructure and commerce functionality without your team having to operate the underlying commerce platform.

I'd choose Shopify over commercetools if:

• You're primarily DTC.
• Shopify's checkout/payment ecosystem is a major advantage.
• You want the smallest possible commerce operations team.
• Your differentiation is primarily in the experience layer, not custom commerce logic.
• Speed-to-market matters more than architectural purity.

Shopify's own current guidance also acknowledges that headless introduces additional development and operational complexity, so there is a real trade-off here. Shopify

Where Saleor fits

Saleor is the one I'd put on the shortlist if your engineering organization strongly prefers open source and GraphQL.

It is particularly interesting for enterprises with sophisticated B2B requirements and a willingness to own more of the platform. Recent industry comparisons highlight its GraphQL-first architecture, multi-channel capabilities and B2B-oriented modeling. Ribbsaeter Systems

The trade-off is that you're taking on more responsibility for the platform than you would with Shopify, and you don't get quite the same enterprise ecosystem as commercetools.

My recommendation

If I were designing the architecture for a large digital-first enterprise today, I'd rank them:

1. commercetools — if architectural flexibility and long-term composability are strategic requirements.

2. Shopify Plus + Hydrogen — if operational simplicity, ecosystem and speed are more important than deep backend composability.

3. Saleor — if you're an engineering-heavy organization that wants open source/API-first commerce and is prepared to own more infrastructure.

4. Salesforce Commerce Cloud — particularly compelling if Salesforce is already your enterprise customer/data ecosystem.

5. Adobe Commerce — strongest when Adobe and complex B2B requirements drive the decision, but I'd be reluctant to choose it solely because you want headless.

One architectural point I'd emphasize: don't choose the platform based primarily on frontend performance. With a genuinely decoupled architecture, your frontend can be Next.js, React, Astro, etc. independently of the commerce engine. The more consequential decision is whether the commerce backend's data model, APIs, extensibility, integration model, deployment model and operational boundaries will still fit your organization five years from now.

If you tell me your approximate GMV/order volume, B2B vs. B2C mix, number of countries, SKU count, existing ERP/PIM/CMS, and preferred frontend stack, I can narrow this to a commercetools vs. Shopify Plus vs. Saleor architecture recommendation and show what the target stack would look like.

If global shopper latency and edge delivery are the primary criteria, my short answer is:

My ranking for enterprise ecommerce

For your stated priority, I'd put Shopify Plus first if you want the platform to handle the edge infrastructure for you. Shopify's storefront CDN is backed by Cloudflare, uses HTTP/3 and TLS 1.3, and Shopify says its enterprise infrastructure spans 300 global points of presence. Shopify Shopify

The particularly interesting part is that Shopify says its enterprise architecture serves storefronts and checkout from the edge, rather than merely putting static assets behind a CDN. That's a meaningful distinction if you're optimizing actual shopping journeys rather than just Lighthouse scores. Shopify

Where Salesforce gets interesting

Salesforce Commerce Cloud is arguably the stronger choice if you're a very large multinational with complicated commerce architecture.

B2C Commerce has an embedded geographically distributed CDN (eCDN), and Salesforce explicitly supports putting a third-party CDN such as Akamai in front of it. Salesforce Salesforce

That gives you a powerful architecture:

Shopper → Akamai/Cloudflare → Salesforce eCDN → Commerce Cloud

rather than being locked into whatever edge architecture the commerce platform happens to provide. Salesforce also documents global-network testing specifically around eCDN and third-party CDN configurations. Developer

If absolute latency is the #1 requirement

I'd actually separate commerce platform from edge platform.

A high-performance enterprise architecture could be:

Shopper → Cloudflare/Akamai/Fastly → composable storefront → commerce APIs

That's where you get the greatest control over:

• Edge caching and cache keys
• Edge-side personalization
• Bot/WAF processing
• Image optimization
• API acceleration
• Geographic routing
• Origin shielding
• Edge compute
• Regional failover
• Cache invalidation
• China-specific delivery strategy

For example, Fastly currently advertises a 622 Tbps global edge network and sub-150 ms average regional purge time, although vendor-reported benchmark numbers shouldn't be treated as directly comparable without your own testing. Fastly

One important caveat: China

If "global" includes mainland China, don't simply compare global POP counts. The network architecture and regulatory environment are materially different.

Salesforce, for example, explicitly says its standard Salesforce CDN isn't recommended for Chinese users and recommends a local China CDN strategy. Salesforce

So I'd evaluate US/EU/APAC/India/China separately, rather than using a single global latency number.

What I'd choose

If I were designing an enterprise storefront today:

• Want lowest operational complexity + excellent global performance: Shopify Plus
• Large enterprise with complex Salesforce ecosystem: Salesforce Commerce Cloud + edge CDN
• Need maximum control/customization: Adobe Commerce + Fastly/Akamai
• Performance is the overriding architectural objective and you have strong engineering: Composable commerce + Fastly/Akamai/Cloudflare

For most enterprises, I'd choose Shopify Plus for the best performance-to-complexity ratio. For a performance-obsessed engineering organization, I'd choose composable commerce with a first-class edge layer rather than letting the ecommerce platform dictate the edge architecture.

If you tell me your approximate monthly traffic, countries/regions, storefront architecture (monolith vs headless), and whether checkout also needs edge acceleration, I can give you a much more concrete Shopify vs Salesforce vs Adobe vs composable latency architecture comparison.

B2C Commerce has an embedded geographically distributed CDN (eCDN), and Salesforce explicitly supports putting a third-party CDN such as Akamai in front of it. help.salesforce.com help.salesforce.com

That gives you a powerful architecture:

Shopper → Akamai/Cloudflare → Salesforce eCDN → Commerce Cloud

rather than being locked into whatever edge architecture the commerce platform happens to provide. Salesforce also documents global-network testing specifically around eCDN and third-party CDN configurations.

If absolute latency is the #1 requirement

I'd actually separate commerce platform from edge platform.

A high-performance enterprise architecture could be:

Shopper → Cloudflare/Akamai/Fastly → composable storefront → commerce APIs

For a retail chain where store pickup and complex omnichannel fulfillment are core requirements, I’d shortlist these:

My recommendation

If fulfillment complexity is the deciding factor, Salesforce is probably the strongest all-around ecommerce platform. Its unified B2C Commerce + POS + Order Management architecture explicitly supports BOPIS, BOFIS, BORIS, ROFIS, ship-from-store and mixed carts where different items in one order can use different fulfillment methods. Salesforce Salesforce

If you're a very large retail chain with sophisticated inventory and fulfillment rules, I'd also seriously evaluate Manhattan Active Omni. It is more of an enterprise commerce/OMS architecture than simply an ecommerce storefront, and its strength is precisely the complex fulfillment problem you're describing. Manhattan

If you want faster implementation and a more ecommerce-first experience, Shopify Plus paired with Manhattan Active Omni is an interesting combination: Shopify handles the storefront/conversion experience while Manhattan supplies deeper multi-node fulfillment orchestration. Shopify says the integration was designed specifically for retailers needing complex fulfillment, returns and real-time multi-location inventory. Shopify

In short:

• Most balanced enterprise choice: Salesforce
• Most sophisticated fulfillment: Manhattan
• Best modern ecommerce + enterprise OMS combination: Shopify Plus + Manhattan

If you tell me roughly how many stores/SKUs you have and whether you need ship-from-store, curbside, split orders, or cross-store transfers, I can narrow this to the best 2–3 architectures.

If fulfillment complexity is the deciding factor, Salesforce is probably the strongest all-around ecommerce platform. Its unified B2C Commerce + POS + Order Management architecture explicitly supports BOPIS, BOFIS, BORIS, ROFIS, ship-from-store and mixed carts where different items in one order can use different fulfillment methods. Salesforce Salesforce

If you're a very large retail chain with sophisticated inventory and fulfillment rules, I'd also seriously evaluate Manhattan Active Omni. It is more of an enterprise commerce/OMS architecture than simply an ecommerce storefront, and its strength is precisely the complex fulfillment problem you're describing.