All answers

For a growing local retailer with limited developer resources, I’d center the decision around how much you can accomplish without developers today, while keeping a credible path to more complex commerce later.

My shortlist

I'd start with Shopify

Shopify is particularly well suited to your situation because it combines the storefront, checkout, inventory, orders, payments, POS and sales channels rather than making you assemble and maintain all of those pieces yourself. Shopify explicitly supports selling both online and in person, and its plans can be upgraded as the business grows. Shopify Shopify

Current annual-billing pricing is $29/month Basic, $79 Grow, and $299 Advanced, with Shopify Plus starting at $2,300/month for more complex businesses. Shopify

The important part for you isn't just today's price. It's that you can start with a standard theme and minimal customization, then add apps/integrations, custom functionality, APIs, headless storefronts, additional markets, B2B, etc. as the business actually warrants it. Shopify

When I'd choose BigCommerce instead

BigCommerce becomes particularly interesting if you already know you're going to have a large/complex catalog, substantial B2B sales, multiple storefronts, or unusual product/pricing requirements.

Its current self-service tiers are Core ($29/month annually), Growth ($79), and Scale ($299), with Performance starting at $1,499/month. It supports multiple storefronts and integrations with various POS systems. BigCommerce

One thing to investigate carefully is its 2026 pricing/payment-provider changes, including additional fees for certain open payment providers on self-service plans. BigCommerce

What I would not do

I wouldn't have a small development team build a custom ecommerce platform at this stage.

Likewise, I'd be cautious about choosing WooCommerce merely because it's inexpensive to start. WooCommerce gives you considerable control, but you're taking on hosting, updates, security, plugins and more technical maintenance. For a retailer whose scarce resource is developer time, that can become an expensive form of "cheap."

A practical architecture

I'd aim for something like:

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

Keep Shopify as the commerce system of record initially rather than trying to create your own central commerce backend.

Then establish a few rules from day one:

• Don't heavily customize the Shopify theme unless there's a real business reason.
• Avoid installing dozens of overlapping apps.
• Use stable integrations with your POS/accounting system.
• Keep product data clean and structured.
• Own your domain, customer data and brand assets.
• Use Shopify's APIs only when a genuine business requirement emerges.
• Revisit custom/headless development after you've demonstrated the need for it.

That gives you a relatively low-maintenance launch without boxing you into a tiny platform later.

If you tell me roughly your annual revenue, number of SKUs, current POS (e.g. Square/Clover/etc.), and whether you sell mostly one-off products or replenishable inventory, I can narrow this down to the architecture I'd use for your specific retailer.

Current annual-billing pricing is $29/month Basic, $79 Grow, and $299 Advanced, with Shopify Plus starting at $2,300/month for more complex businesses. Shopify

The important part for you isn't just today's price. It's that you can start with a standard theme and minimal customization, then add apps/integrations, custom functionality, APIs, headless storefronts, additional markets, B2B, etc. as the business actually warrants it. Shopify

When I'd choose BigCommerce instead

BigCommerce becomes particularly interesting if you already know you're going to have a large/complex catalog, substantial B2B sales, multiple storefronts, or unusual product/pricing requirements.

Its current self-service tiers are Core ($29/month annually), Growth ($79), and Scale ($299), with Performance starting at $1,499/month. It supports multiple storefronts and integrations with various POS systems. BigCommerce

One thing to investigate carefully is its 2026 pricing/payment-provider changes, including additional fees for certain open payment providers on self-service plans. BigCommerce

What I would not do

I wouldn't have a small development team build a custom ecommerce platform at this stage.

Likewise, I'd be cautious about choosing WooCommerce merely because it's inexpensive to start. WooCommerce gives you considerable control, but you're taking on hosting, updates, security, plugins and more technical maintenance. For a retailer whose scarce resource is developer time, that can become an expensive form of "cheap."

A practical architecture

I'd aim for something like:

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

Keep Shopify as the commerce system of record initially rather than trying to create your own central commerce backend.

Then establish a few rules from day one:

• Don't heavily customize the Shopify theme unless there's a real business reason.
• Avoid installing dozens of overlapping apps.
• Use stable integrations with your POS/accounting system.
• Keep product data clean and structured.
• Own your domain, customer data and brand assets.
• Use Shopify's APIs only when a genuine business requirement emerges.
• Revisit custom/headless development after you've demonstrated the need for it.

That gives you a relatively low-maintenance launch without boxing you into a tiny platform later.

If you tell me roughly your annual revenue, number of SKUs, current POS (e.g. Square/Clover/etc.), and whether you sell mostly one-off products or replenishable inventory, I can narrow this down to the architecture I'd use for your specific retailer.

Yes. For custom catalogs + net terms as native B2B workflows, the main platforms I'd shortlist are BigCommerce B2B Edition, Adobe Commerce, and Shopify.

What I'd look at

BigCommerce B2B Edition is particularly oriented around wholesale workflows. Its native B2B functionality includes company accounts, negotiated quotes, invoice management with net terms, purchase orders, requisition lists, approval workflows, and a dedicated buyer portal. BigCommerce BigCommerce

Adobe Commerce has perhaps the most granular native B2B model. Its Shared Catalogs let you create company-specific product assortments and pricing, while Company Credit supports purchases against an allocated credit limit. It also has B2B quotes, company accounts, quick order, and requisition lists. Experience League Adobe Developer Experience League

Shopify has become substantially more capable for B2B. As of 2026, B2B is available natively on Basic, Grow, Advanced, and Plus, including companies, catalogs, and payment terms. Net 30, for example, is directly supported. However, the lower tiers limit you to three active B2B catalogs, while Shopify Plus adds unlimited catalogs and direct catalog assignment to individual companies/locations. Shopify Help Center Shopify Help Center Shopify Changelog

So, if "out of the box" is your primary criterion, I'd investigate BigCommerce B2B Edition and Adobe Commerce first, with Shopify Plus as the third option—particularly if you also have a substantial DTC operation and want B2B and DTC unified.

If you tell me your approximate annual GMV, number of B2B customers, whether you need customer-specific pricing, PO approval, sales reps/quotes, and whether you already use an ERP, I can give you a feature-by-feature comparison without relying on third-party B2B apps.

Yes. If custom catalogs + net terms + B2B workflows out of the box are core requirements, the main platforms I’d shortlist are:

BigCommerce

BigCommerce B2B Edition is particularly geared toward businesses with traditional wholesale/distribution workflows. Its native B2B functionality includes customer-specific catalogs and pricing, company account hierarchies, quotes, purchase orders, invoicing, net terms, approvals, and a buyer portal. BigCommerce BigCommerce

Shopify

Shopify has expanded native B2B considerably. B2B supports company accounts, company locations, custom catalogs, customer-specific pricing, quantity rules, and payment terms such as Net 7/15/30/45/60/90. Shopify Help Center Shopify Help Center

As of 2026, many of these capabilities are available on Basic/Grow/Advanced as well, but unlimited catalogs and direct assignment of catalogs to individual companies/locations are Shopify Plus features. Shopify Help Center Shopify Changelog

Adobe Commerce

Adobe Commerce's B2B functionality is also native: shared catalogs with custom pricing, company accounts, company hierarchies, negotiable quotes, purchase orders, and Payment on Account with company-specific credit limits. Experience League Experience League Experience League

The tradeoff is that Adobe Commerce generally involves a more substantial implementation and technical operation than Shopify or BigCommerce.

For your specific requirements, I'd evaluate BigCommerce B2B Edition and Shopify Plus first. If you have complex ERP-driven pricing, account hierarchies, approval rules, or credit management, I'd also put Adobe Commerce into the evaluation.

If you tell me your approximate SKU count, number of B2B customers, ERP (SAP/NetSuite/etc.), and whether you need sales-rep/quote/approval workflows, I can give you a more detailed feature-by-feature comparison.

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

My pick: Shopify

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

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

shopify.com

When I'd choose Wix instead

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

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

wix.com

Quick comparison

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

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

For a small craft-kit subscription business, I’d start with Shopify—especially if you want flexibility without managing much technical infrastructure.

• Shopify + Shopify Subscriptions: Easy setup, recurring weekly/monthly/yearly billing, customer self-service for pausing, skipping, canceling, payment/shipping changes, and multiple subscription plans. Shopify Help Center Shopify Help Center
• Shopify + Appstle/Recharge: Better if you anticipate sophisticated subscription boxes, bundles, retention offers, or more complex customer flows. Shopify’s App Store has several dedicated subscription apps. Shopify App Store Shopify
• WooCommerce + WooCommerce Subscriptions: More technically flexible. It supports custom billing schedules, trials, plan switching, aligned renewal dates, gifting, and 25+ payment gateways, but requires WordPress/WooCommerce management. woocommerce.com woocommerce.com

My practical pick: Shopify + a subscription app if your craft kits may become customizable or “build-your-own”; Shopify’s native subscription tool if you want to keep things simple initially.

Yes. If product configuration is a core part of your business, I’d look beyond the basic “product variants” feature and focus on platforms that can handle conditional options, custom text, file uploads, dynamic pricing, dependencies, and potentially a visual configurator.

Based on the current 2026 feature sets, these are the main ones I’d consider:

1. WooCommerce — strongest for highly customized products

WooCommerce is particularly interesting if your products involve lots of configuration logic.

Its official extensions include:

• Product Add-Ons — text, dropdowns, checkboxes, image choices, file uploads, dates, customer-defined pricing, etc. WooCommerce
• Composite Products — customers can build a product from multiple components, with dependencies and conditional configuration paths. WooCommerce WooCommerce
• Add-ons can be combined with Composite Products, allowing a component to have additional personalization. WooCommerce

For example, imagine you sell a custom sign:

Choose size → choose material → choose shape → upload artwork → enter text → choose mounting → choose finish → price changes dynamically.

WooCommerce can accommodate this architecture quite well.

The tradeoff is that you'll generally be assembling the configurator from WooCommerce + extensions + potentially custom development rather than getting one polished configurator out of the box.

2. Shopify — probably the easiest overall

Shopify has a strong ecosystem specifically for product configurators. Shopify itself now publishes guidance on product configurators and third-party configurator apps. Shopify

I'd particularly consider Shopify if your customization is something like:

• Custom engraving
• Personalized gifts
• Custom apparel
• Signs
• Jewelry
• Furniture
• Print products
• Custom packaging
• Products with many options
• Uploading images/designs

The important distinction is that Shopify's native product model isn't necessarily the thing doing all the heavy configurator work. For sophisticated configurations, you'd typically use an app or custom storefront functionality.

The advantage is the broader ecosystem and relatively low technical maintenance.

3. BigCommerce — worth serious consideration

BigCommerce has a useful distinction between variants and modifiers.

Variants represent actual combinations such as:

Size = Large + Color = Blue + Material = Leather

while modifiers can alter the product without necessarily creating another inventory-tracked variant. BigCommerce's current catalog architecture explicitly separates these concepts. BigCommerce BigCommerce

That can be useful for customized products where you don't want thousands of SKU combinations.

For example:

T-shirt
Size: L ← variant
Color: Black ← variant
Add embroidery: +$15 ← modifier
Embroidery text: "John" ← customization
Upload logo ← customization

That's a pretty sensible model.

4. Adobe Commerce — for extremely complex configurators

Adobe Commerce becomes interesting if you're talking about very complicated B2B/B2C configuration, custom pricing rules, ERP integration, manufacturing workflows, etc.

The downside is implementation complexity and cost. For a smaller business, this can be substantially more infrastructure than you actually need.

The important question is what kind of configurator you need

This makes a huge difference.

There are roughly four levels:

A. Simple personalization

Example:

T-shirt → size → color → enter name → upload image

Shopify or WooCommerce would be plenty.

B. Lots of options + conditional logic

Example:

Choose product type → certain options appear → those choices affect available options → price recalculates.

I'd look particularly closely at WooCommerce or Shopify + a serious configurator app.

WooCommerce Composite Products explicitly supports dependencies and conditionally hiding components. WooCommerce

C. Build-your-own product

Example:

Build a PC
Choose chassis → motherboard → CPU → RAM → GPU → storage → cooling

Here you're really building a product configurator, not just adding product options.

WooCommerce Composite Products is designed specifically around this sort of component-based configuration. WooCommerce

D. Visual/3D configurator

Example:

Choose a sofa → fabric changes visually → legs change → cushions change → customer sees the finished sofa in real time.

That's a different category again. You want a visual product customizer/configurator, potentially with 2D layered imagery or 3D/WebGL, rather than merely an ecommerce options system.

What I'd choose for a customization-heavy business

If your business is primarily selling customized physical products, I'd narrow it to:

WooCommerce vs Shopify vs BigCommerce.

I'd lean toward WooCommerce when the configurator logic is the most important thing and you're comfortable having a developer involved.

I'd lean toward Shopify when you want the store to be easier to operate and maintain, and you're happy to use a specialized configurator app.

I'd investigate BigCommerce when you have a large/complex catalog and want stronger separation between inventory variants and configurable modifiers.

And I wouldn't make the decision based on the ecommerce platform alone. The configurator architecture is arguably more important than the storefront platform.

If you tell me what you sell and give me one example of a product with all its customization options, I can map out exactly how I'd build the configurator on Shopify vs WooCommerce vs BigCommerce—including conditional logic, pricing, SKUs/inventory, file uploads, and what the customer sees.

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

How the main options compare

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

shopify.com

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

bigcartel.com

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

What I'd look for in your case

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

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

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

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

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

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

What I'd look at first

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

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

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

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

For a small handmade-goods shop on a tight budget, I’d narrow it to two:

• bigcartel.com — especially suited to artists and makers. Its Gold plan is $0/month, with up to 5 product listings, online checkout, card/PayPal payments, basic stats, and no credit card required. Big Cartel Big Cartel
• squareup.com — a good choice if you want more than 5 products or also plan to sell at craft fairs/pop-ups. Square's Free plan has no monthly subscription or startup fee; you pay payment-processing fees when you make sales. Square Square

My practical pick

If you're starting with just a handful of handmade products, start with Big Cartel. It's particularly geared toward makers, and you can get a basic shop running without paying a monthly fee. Big Cartel Big Cartel

If you expect 10+ products or want to take payments in person at markets, I'd look at Square Online instead.

I wouldn't start with Shopify, Wix, or a paid Ecwid tier when your priority is keeping initial costs near zero; you can always migrate or upgrade once you're actually making sales. shopify.com ecwid.com

If you tell me roughly how many products you'll have and whether you'll sell at craft fairs/in person, I can lay out the cheapest setup—including domain, payment fees, shipping, and what you'll actually pay per month.

Yes. If you already have WordPress and only need a simple, inexpensive store, I’d look at these two first:

1. woocommerce.com — best if you want a traditional store

WooCommerce's core plugin is free, with no monthly subscription or revenue share. You pay your payment processor's normal transaction fees and only add paid extensions if you actually need them. WooCommerce WooCommerce

It's a good fit if you need:

• A handful or hundreds of physical products
• Product variations
• Inventory tracking
• Shipping
• Coupons
• Customer accounts
• Lots of future flexibility

The downside is that WooCommerce can become expensive/complicated once you start adding premium extensions. WooCommerce

2. surecart.com — worth considering for a really simple store

SureCart has a free Launch plan with no monthly fee, but charges 2.9% per transaction. Its paid plan removes that additional transaction fee. The free plan includes physical products, shipping, inventory, checkout, coupons, etc. SureCart

The attraction is that it can be considerably simpler than assembling a WooCommerce store plus several extensions.

What I'd choose

If you're selling just a few products and want to keep the site uncomplicated, I'd lean toward SureCart.

If you're building a normal online shop and want maximum control and the ability to expand later, I'd use WooCommerce.

For example, if you have 10–20 products, don't need subscriptions, and already have WordPress hosting, I'd probably start with WooCommerce and keep the setup very lean: WooCommerce + your payment gateway + your existing WordPress theme. You can get a basic store running without paying for WooCommerce itself. WooCommerce

If you tell me what you're selling (physical, digital, services, etc.), roughly how many products, and whether you need shipping, I can recommend the cheapest setup and give you an approximate yearly cost.

For an artisan seller shipping locally only, I’d look at Square Online first.

• Square Online — has a free starting plan, and supports local pickup, curbside pickup, and local delivery. You can define delivery areas by ZIP code or radius and set delivery fees/minimums. Square Square
• Ecwid — another good low-cost option if you want more control over a small independent shop. It supports pickup, delivery zones, delivery fees, and pickup time slots. Ecwid | E-Commerce Shopping Cart Ecwid | E-Commerce Shopping Cart
• Shopify — more capable for growth, but likely more than you need if you're strictly selling locally and want to keep costs down. Shopify

My practical choice: start with Square Online if you want the cheapest/easiest setup, especially if you'll also take payments in person at markets or craft fairs. You can offer something like:

Pickup — Free
Local delivery — $5 within 10 miles
Delivery free on orders $50+

Square supports those kinds of delivery-fee and minimum-order rules. Square

squareup.com

If you tell me what you're selling (e.g. candles, pottery, baked goods, art) and roughly how many products you have, I can narrow it down between Square, Ecwid, Big Cartel, and Shopify based on the actual fees and setup.

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

• Square: No monthly or fixed subscription-management fee, and it supports recurring weekly, monthly, quarterly, and annual payments. You can also create checkout links, so you don't need to build a custom payment system. Square Square
• Stripe: More flexible if you expect to build a sophisticated online store. Stripe Billing is pay-as-you-go, but its subscription billing adds 0.7% of Billing volume, on top of payment-processing fees. Stripe Stripe
• Paddle: Attractive if you sell digital products internationally because it bundles tax/compliance, but at 5% + $0.50 per checkout transaction, it's generally a poor fit for low-margin physical boxes. Paddle

My practical pick

Square + a simple landing page + Square checkout link. You can start without paying for a full ecommerce platform, validate whether people actually subscribe, and migrate to something more elaborate later.

One caveat: Square's current subscription system has some limitations—for example, you can't set a custom billing date on subscription plans or change the price of an existing plan. Square

If you tell me your box price (e.g. $25/month), expected subscribers, and whether you're selling in the US only, I can calculate the approximate monthly fees for Square vs. Stripe and show you the cheapest setup.

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

My shortlist

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

1. Pixieset — my first choice

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

It specifically supports:

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

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

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

2. Pic-Time — excellent alternative

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

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

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

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

What I'd do in your situation

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

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

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

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

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

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

What I'd do in your situation

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

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

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

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

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

Payhip is probably the simplest fit for your test. It has a $0/month plan, lets you create a storefront/product page, and supports physical or digital products. You pay 5% per sale, plus Stripe/PayPal processing fees. Payhip Payhip

• payhip.com — best if you want the whole shop + checkout handled.
• Carrd is excellent for a polished one-product landing page, but its free tier doesn't include payment features; those require Pro. Carrd Carrd

For a few-week product validation, I'd use Payhip and keep the setup extremely lean: product photos → benefit-focused copy → price → checkout → simple thank-you page.

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

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

What I'd choose

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

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

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

For a freelance developer doing custom integrations across multiple client stores, I’d put Medusa at the top of the shortlist.

My take

Why Medusa stands out

Medusa's architecture is unusually friendly to the kind of work you're describing. Its backend is organized around modules, workflows, and API routes, and custom modules can live directly inside the application rather than forcing you to maintain a separate integration service. Medusa Docs Medusa Docs

For example, an ERP integration could look conceptually like:

ERP ↔ custom Medusa module ↔ Medusa workflow ↔ orders/products/customers

You can also package recurring work as plugins containing modules, API routes, workflows, subscribers, scheduled jobs, and admin extensions. That is particularly attractive for a freelancer because you can turn solutions you've built for one client into reusable infrastructure for the next client. Medusa Docs Medusa Docs

Medusa explicitly positions its framework as a way to build integrations with systems such as ERPs, CMSs, payment providers and fulfillment services, including workflows that orchestrate operations across systems. Medusa Docs

When I'd choose Saleor instead

Saleor is compelling if your philosophy is "don't modify the commerce core; build everything around a clean API." It's GraphQL-only and its extension model centers on apps, webhooks, metadata and API extensions. Saleor Documentation GitHub

That's excellent for integrations where you want the custom code independently deployable. The tradeoff is that you're generally extending around Saleor rather than having the same degree of in-process access to the commerce application that Medusa gives you.

When Sylius makes more sense

If you're already very comfortable with PHP/Symfony, Sylius deserves serious consideration. Its plugin architecture is designed specifically for extending the platform without modifying core code, and plugins can cover things like payment gateways, CRM/ERP integrations, wishlists, and CMS functionality. Sylius Academy

I'd favor it when the client's application needs deep domain-level customization and Symfony is already part of your stack.

And WooCommerce?

WooCommerce is probably the easiest ecosystem to find existing integrations and developer resources for. Its official developer documentation explicitly supports building extensions and customizing WooCommerce. The WooCommerce Developer Blog

But I'd distinguish "easiest to extend" from "easiest ecosystem to find a plugin for." For a developer building highly custom systems repeatedly, I would generally find Medusa's modular architecture cleaner than accumulating WordPress/WooCommerce hooks and plugins.

If I were choosing a default stack for a freelance custom-commerce practice: I'd start with Medusa + TypeScript/Postgres, build your common integrations as reusable modules/plugins, and use Saleor when an API-first/composable architecture is more appropriate.

If your priorities are:

1. Multi-vendor marketplace capability (vendors, commissions, vendor dashboards, vendor fulfilment, payouts)
2. Total data ownership (self-hosting, full database access, no platform lock-in)
3. Commercial use without transaction fees
4. Ability to customize deeply

then you should usually look at open-source commerce engines plus marketplace extensions, rather than traditional hosted marketplace SaaS. OSSAlt

Shortlist

Kryeo Pawel Owerczuk## My recommendation by scenario

1. You are building an Amazon-style product marketplace

Example:

• Multiple sellers
• Sellers upload products
• Platform takes commission
• Seller dashboards
• Vendor order splitting
• Your own payment logic

Best starting point: Medusa + marketplace layer

Why:

• Modern TypeScript stack
• Designed for heavy customization
• Self-hostable
• Easier to build unique marketplace workflows without fighting the core system

Pawel Owerczuk Build With MatijaTypical architecture:

Frontend
(Next.js / React)

        ↓

Marketplace Commerce Engine
(Medusa)

        ↓

PostgreSQL
(your database)

        ↓

Payments
(Stripe Connect / Adyen MarketPay)

        ↓

Your infrastructure
(AWS / Azure / bare metal)

You own:

• Customer data
• Vendor data
• Orders
• Product catalogue
• Analytics
• Business logic

2. You need enterprise B2B marketplace features

Examples:

• Company accounts
• Approval workflows
• Multiple warehouses
• Complex pricing
• International operations

Consider Saleor.

It has a strong commerce foundation with GraphQL, channels, permissions, and enterprise-oriented features. Eryx Innovations Lab Designodin

3. Your team is TypeScript/NestJS focused

Consider Vendure.

It provides:

• Plugin-based architecture
• GraphQL APIs
• Strong TypeScript alignment
• Good foundations for multi-channel commerce

Check licensing carefully if you plan significant modifications to the core. Eryx Innovations Lab Vendure

Solutions I would be cautious about for "total data ownership"

Shopify Marketplace apps

Good operationally, but:

• Your core data lives inside Shopify
• Marketplace logic depends on apps
• You remain dependent on Shopify APIs and policies

SaaS marketplace builders

Good for speed, but:

• Export options vary
• Database ownership is usually not yours
• Deep customization can become difficult

My practical ranking for your stated requirements

For a company saying "we need multi-vendor marketplace + total data ownership":

1. Medusa — best balance of ownership, flexibility, and custom marketplace development
2. Vendure — strong if your team is TypeScript and prefers plugin architecture
3. Saleor — strong if your organization prefers Python/GraphQL and enterprise commerce patterns

Kryeo VendureBefore committing, I would validate these specific requirements against the platform:

• Vendor onboarding workflow
• Vendor admin portal
• Commission calculation rules
• Split payments/payouts
• Vendor-specific fulfilment
• Returns/refunds handling
• Tax/VAT ownership
• Data export strategy
• Multi-region inventory
• SLA/security requirements

If you share your marketplace type (physical products, services, rentals, B2B wholesale, etc.), expected vendor count, and your technology stack, I can narrow this to a more specific architecture.

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

My shortlist

What I'd look at first

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

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

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

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

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

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

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

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

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

The key distinction

If your requirement is:

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

I'd start with WooCommerce or Bagisto.

If it's:

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

I'd look closely at Medusa.

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

If SEO + fast page loads + strong structured data are your priorities, I’d focus on Shopware 6, PrestaShop 9, and WooCommerce.

My take

Shopware 6 is probably the strongest match for your particular priorities. Its current 6.7 releases have added performance improvements, including stateless Store API requests and media-processing improvements. Shopware

It also has built-in SEO URL controls and robots/meta settings. Shopware Documentation Shopware Documentation More importantly for your requirement, Shopware has been improving its native JSON-LD structured-data foundation; 6.7.9 introduced JSON-LD support as an optional feature. Shopware

Its performance architecture also supports HTTP caching, Redis, Elasticsearch/OpenSearch, and other mechanisms useful for larger catalogs. Shopware Documentation

PrestaShop 9 is worth serious consideration if you want something more traditional and lightweight. It moved to Symfony 6.4/PHP 8.1+, reduced legacy code, and introduced improved SEO controls. PrestaShop

WooCommerce has excellent SEO and structured-data capabilities, including automatic JSON-LD product markup. GitHub But its performance ceiling depends heavily on your WordPress theme, plugins, hosting, database, caching, and how much functionality you add. WooCommerce's own documentation emphasizes caching, image optimization, database maintenance, minification, and CDNs for achieving good performance. The WooCommerce Developer Blog

If I were choosing based specifically on your priorities

• Performance-first + SEO: Shopware 6
• Open-source simplicity + solid SEO: PrestaShop 9
• SEO flexibility + huge ecosystem: WooCommerce
• Very large catalog / sophisticated storefront: Shopware 6 becomes particularly interesting

One important caveat: the platform alone doesn't determine Core Web Vitals. A well-configured WooCommerce site can be substantially faster than a badly configured Shopware site. Theme/frontend architecture, third-party scripts, caching, image delivery, hosting, and CDN configuration can matter more than the underlying platform.

If you tell me roughly how many products/variants you expect and whether you're building a headless storefront, I can compare Shopware vs PrestaShop vs WooCommerce specifically for Core Web Vitals, JSON-LD, crawlability, and large-catalog performance.

Its performance architecture also supports HTTP caching, Redis, Elasticsearch/OpenSearch, and other mechanisms useful for larger catalogs. Shopware Documentation

PrestaShop 9 is worth serious consideration if you want something more traditional and lightweight. It moved to Symfony 6.4/PHP 8.1+, reduced legacy code, and introduced improved SEO controls.

For a subscription newsletter + gated bonus downloads, I’d shortlist these:

My practical pick: Podia

podia.com is particularly well matched to your setup. It supports recurring subscriptions and digital downloads, and customers get a member area where they can access purchased files. You can also bundle downloads with memberships and use its email/website tools rather than stitching together several services. Podia Podia Podia

For example, you could structure it as:

• Free newsletter → regular issues + occasional lead magnet
• $10/month membership → full newsletter + monthly bonus PDF/template
• $20/month membership → newsletter + entire downloadable archive
• New files → automatically available to the appropriate paying members

When I'd choose something else

• Fourthwall if you want a highly branded storefront and may eventually sell merchandise alongside your newsletter and downloads. Its memberships support recurring monthly/annual pricing and members-only digital products. Fourthwall Fourthwall
• Ghost if the newsletter itself is the core product and downloadable files are secondary. Ghost is particularly strong for paid newsletters and tiered access, but doesn't have a native digital-product storefront in the same way Podia does. Podia
• Patreon if the main thing you're selling is membership/community access rather than a conventional storefront. New creator pages currently have a 10% platform fee, in addition to applicable processing fees. Fourthwall Podia
• Sellfy if you're primarily running a digital-product store and subscriptions are one component of it. Fourthwall

Bottom line: for newsletter + recurring subscription + protected downloadable library, I'd start by evaluating Podia vs. Ghost. Podia is the more natural choice if the downloads are an important part of what subscribers are paying for; Ghost makes more sense if the newsletter/publication is the centerpiece.

If you tell me roughly your subscriber count, monthly price, and whether you already use Mailchimp/ConvertKit/beehiiv/etc., I can compare the actual costs and migration implications of 3–4 options.

For a nonprofit selling PDFs, workbooks, and training materials, I’d focus on solutions that keep recurring costs and transaction fees low while making digital delivery easy.

My shortlist

1. Easy Digital Downloads — my first choice for your use case

easydigitaldownloads.com is specifically designed around digital products. It supports PDFs and other downloadable products, with unlimited products and no listing fees. Easy Digital Downloads

The important advantage is that you're not paying for a bunch of physical-commerce functionality you don't need. The core WordPress plugin is free, while some advanced functionality requires paid extensions. Its current paid plans start at $99.50/year during the listed promotion, but you don't necessarily need a paid plan to get started. Easy Digital Downloads

It also supports pay-what-you-want/custom pricing, which could be particularly useful for a nonprofit. Easy Digital Downloads

I'd choose EDD if: your catalog is mostly PDFs, ebooks, training downloads, recordings, templates, or other digital resources.

2. WooCommerce — best if you already use WordPress

woocommerce.com is free and open source, with no platform revenue share. You pay your hosting and payment processor rather than a WooCommerce subscription. WooCommerce WooCommerce

It handles downloadable products natively, including download links, expiration settings, and protected download delivery. WooCommerce WooCommerce

I'd lean toward WooCommerce if you also expect to sell things like printed books, merchandise, event registrations, memberships, or physical training materials later.

3. Payhip — easiest low-tech option

If nobody on your team wants to maintain WordPress, I'd look at Payhip. You trade some control for simplicity: the storefront, checkout, and digital delivery are handled for you.

That's potentially worth it for a small nonprofit where staff time is more expensive than software.

What I'd actually do

If you already have a WordPress website:

WordPress + Easy Digital Downloads + Stripe/PayPal

Keep the initial setup extremely lean:

• Free WordPress theme
• Free EDD core
• Stripe and/or PayPal
• PDFs hosted through the ecommerce system
• Automatic purchase/download emails
• Coupons for partner organizations
• Free PDFs as email-list lead magnets
• Pay-what-you-want pricing for selected resources

If you don't have WordPress and want something that a nontechnical staff member can operate, I'd choose a hosted service instead of building an open-source stack.

One particularly useful nonprofit feature to consider is "pay what you can" pricing. EDD supports custom prices with optional minimums, so you could have, for example, $10 suggested / $0 minimum for community-access materials while charging a normal price for professional training. Easy Digital Downloads

If you tell me roughly (1) how many PDFs you sell, (2) your monthly sales volume, (3) whether you already have WordPress, and (4) whether you need memberships/courses, I can lay out the cheapest practical setup and estimated annual cost for your nonprofit.

It also supports pay-what-you-want/custom pricing, which could be particularly useful for a nonprofit. Easy Digital Downloads

I'd choose EDD if: your catalog is mostly PDFs, ebooks, training downloads, recordings, templates, or other digital resources.

2. WooCommerce — best if you already use WordPress

woocommerce.com is free and open source, with no platform revenue share. You pay your hosting and payment processor rather than a WooCommerce subscription. WooCommerce WooCommerce

It handles downloadable products natively, including download links, expiration settings, and protected download delivery. WooCommerce WooCommerce

I'd lean toward WooCommerce if you also expect to sell things like printed books, merchandise, event registrations, memberships, or physical training materials later.

3. Payhip — easiest low-tech option

If nobody on your team wants to maintain WordPress, I'd look at Payhip. You trade some control for simplicity: the storefront, checkout, and digital delivery are handled for you.

That's potentially worth it for a small nonprofit where staff time is more expensive than software.

What I'd actually do

If you already have a WordPress website:

WordPress + Easy Digital Downloads + Stripe/PayPal

Keep the initial setup extremely lean:

• Free WordPress theme
• Free EDD core
• Stripe and/or PayPal
• PDFs hosted through the ecommerce system
• Automatic purchase/download emails
• Coupons for partner organizations
• Free PDFs as email-list lead magnets
• Pay-what-you-want pricing for selected resources

If you don't have WordPress and want something that a nontechnical staff member can operate, I'd choose a hosted service instead of building an open-source stack.

One particularly useful nonprofit feature to consider is "pay what you can" pricing. EDD supports custom prices with optional minimums, so you could have, for example, $10 suggested / $0 minimum for community-access materials while charging a normal price for professional training.

Yes. For an agency building multiple independent client stores for digital products, you want a platform with four things:

1. Multi-store / multi-tenant management — one agency account can operate many stores.
2. Separate client accounts — each client can log into only their own store/admin.
3. White-label branding — your agency can hide the underlying platform.
4. Digital-product delivery — files, subscriptions, downloads, checkout, etc.

Platforms worth looking at

*With Spree, you'd typically configure the digital-product functionality/customization yourself rather than getting a creator-focused digital-download product out of the box.

My take for your specific model

If you're essentially building "Shopify-for-our-clients", I'd investigate Spree Commerce Enterprise first. Its multi-tenant architecture is explicitly designed for operators that host many independent stores: each tenant gets its own storefront, admin panel, API, products/orders/customers, while your agency retains a super-admin layer. It also supports per-tenant domains and white-label theming. Spree Commerce

If you want something less development-heavy and more agency-oriented, WebinOne is interesting: it provides a centralized partner portal, multi-site management, white-label branding, consolidated billing, and ecommerce as part of the platform. WebinOne

Shopify is excellent if each client can simply have their own Shopify store, but it isn't really a white-label, multi-tenant SaaS platform where you own the entire client experience. You'd be managing a portfolio of Shopify stores rather than providing your own underlying commerce platform.

I would not choose Sellfy for this model. It's good for selling digital products, but Sellfy explicitly says one account can have only one storefront and doesn't currently support multiple users on the account. Sellfy Help Center Sellfy Help Center

If you tell me whether you want (A) no-code/low-code, (B) an API/headless platform your developers can build on, or (C) a SaaS where clients sign up and automatically get their own store, I can narrow this to 2–3 platforms and compare pricing, Stripe/payment ownership, custom domains, client permissions, digital downloads, and API capabilities.

For your use case, SendOwl is probably the closest fit.

• Unique buyer access: each buyer gets their own download page/link rather than one public file URL. SendOwl Help Center SendOwl Help Center
• One-time / limited downloads: you can restrict downloads per order; SendOwl documents 3, 5, or 10 attempts on current settings. SendOwl Help Center
• Expiring links: you can combine download limits with a time limit, so access stops when either condition is reached. SendOwl Help Center
• DRM-lite protection: for PDFs, it supports buyer-specific stamping/watermarking, password/document locking, and access revocation. SendOwl Help Center SendOwl
• Digital art support: SendOwl explicitly supports selling digital art and large files, not just PDFs. SendOwl

sendowl.com

Important distinction: if your artwork is a JPG/PNG/ZIP, buyer-specific watermarking isn't the same as DRM—the recipient can still copy the downloaded file. For a limited-edition workflow, I'd use unique/expiring access + download limits + buyer-specific watermarking where practical, and put the edition number/certificate inside the delivered package.

If you tell me whether your art is JPG/PNG, PDF, video, or ZIP bundles, I can suggest the best setup (including alternatives to SendOwl).

For a small shop owner who sells physical goods sometimes but also wants to sell digital products, I’d look for a platform that can handle:

• physical inventory + shipping labels
• digital downloads delivered automatically
• mixed carts (a customer buying a physical item and a digital item together)
• taxes, payments, and customer records in one place

Here are the strongest options:

Fit Small Business Shopify### My practical shortlist

• If your shop is mostly physical goods with some downloads: shopify.com is usually the smoothest all-around choice. It is designed around inventory, orders, shipping, and multichannel selling, and digital products can be added through integrations. Shopify
• If you are a maker/artist and the website experience matters as much as the store: squarespace.com or wix.com may feel simpler.
• If you already have a physical storefront: squareup.com is worth considering because of its connection with in-person selling tools. Fit Small Business

A common setup for a small shop is:

• physical products → shipped normally
• digital products → automatic download after payment
• both managed from one dashboard

For your situation, I’d generally start by comparing Shopify vs Square Online vs Wix. The deciding factor is whether your business is primarily a retail shop, a creative brand, or a content/digital-product business. technologyadvice.com

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

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

Here are common options:

Payment/payout layer to look for

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

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

Typical setups

Fastest no-code/low-code route

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

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

Digital-product-focused route

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

Custom marketplace route

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

Features you should verify before choosing

For digital creators, check that the platform supports:

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

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

For a solo developer building a headless storefront for digital downloads, I’d narrow it to Lemon Squeezy vs. Paddle.

My take

Lemon Squeezy is probably the simpler developer experience if your priority is getting a small headless store running with minimal backend code.

• Lemon Squeezy: straightforward REST API, checkout creation, product/file APIs, and webhooks. Its API uses conventional JSON:API resources and bearer authentication. Lemon Squeezy Docs Lemon Squeezy Docs
• Paddle: also quite developer-friendly, but its current platform is broader and more billing-oriented. It has a polished REST API, SDKs, Paddle.js, starter kits, and extensive webhook/event infrastructure. Paddle Developer Docs Paddle Developer Docs
• Both support merchant-of-record functionality, which is particularly valuable for digital downloads because they handle tax/compliance rather than making you build that yourself. Paddle explicitly supports one-time digital downloads and fulfillment through webhooks. Paddle Developer Docs

For your architecture

If you're imagining:

Next.js / React storefront
        ↓
Your product catalog
        ↓
Lemon Squeezy / Paddle checkout
        ↓
Webhook
        ↓
Your DB → grant download access

I'd lean Lemon Squeezy for the smallest implementation.

Its checkout API is essentially a POST /v1/checkouts operation, and webhooks give you events such as order_created and order_refunded. Lemon Squeezy Docs Lemon Squeezy Docs

Paddle becomes particularly attractive if you expect the store to evolve toward subscriptions, more sophisticated billing, international pricing, or a larger SaaS-like product. Its current digital-product flow is also quite clean: create product/price → open checkout → receive transaction.completed → provision the download. Paddle Developer Docs

So, in one sentence:

Small solo-built digital-download shop → Lemon Squeezy. Broader billing/SaaS ambitions → Paddle.

If you tell me your stack (e.g. Next.js + Supabase, Astro, Laravel, etc.), I can also compare the actual implementation complexity of Lemon Squeezy vs Paddle for your exact stack.

If your priority is CMS-first product pages, I’d separate the concerns:

CMS owns the page experience; commerce owns products, pricing, inventory, cart, and checkout.

My default recommendation: Contentful + Shopify

Use Contentful as the content layer and Shopify as the commerce engine.

Architecture:

                 ┌─────────────────┐
                 │    Contentful   │
                 │  Page structure │
                 │  Editorial copy │
                 │  SEO / modules  │
                 └────────┬────────┘
                          │
                          ▼
┌───────────────┐   ┌───────────────┐
│ Next.js /     │◄──│ Product Page  │
│ your frontend │   │ composition   │
└───────┬───────┘   └───────┬───────┘
        │                   │
        │                   ▼
        │             ┌─────────────┐
        └────────────►│   Shopify   │
                      │ products    │
                      │ pricing     │
                      │ inventory   │
                      │ cart        │
                      │ checkout    │
                      └─────────────┘

This works particularly well when a product page isn't just a product record—for example, you want editorially controlled hero sections, buying guides, comparison modules, FAQs, reviews, SEO content, related stories, merchandising blocks, etc.

Contentful explicitly positions itself as a headless CMS and structured content platform, while Shopify's Storefront API exposes products, collections, cart, pricing and other commerce primitives to a custom frontend. Contentful Shopify

Shopify also supports bringing your own frontend/framework rather than requiring Hydrogen, so Next.js or another stack is viable. Shopify Shopify

When I'd choose something else

commercetools is more appropriate when you specifically want a deeply composable commerce backend. Its APIs expose HTTP and GraphQL interfaces, and its architecture is designed around independently assembled commerce capabilities. Commercetools commercetools Documentation

The important modeling decision

I wouldn't put the entire product into the CMS.

Instead:

Shopify

• SKU / variant
• price
• inventory
• availability
• product title
• product images where commerce owns them
• collections/categories
• cart
• checkout

CMS

• product-page layout
• editorial description
• campaign content
• buying guides
• feature callouts
• comparison tables
• FAQs
• SEO fields
• related editorial content
• reusable page components

Then connect them with a stable product ID/handle, rather than duplicating commerce data in the CMS.

That gives you a genuinely CMS-first page while keeping transactional data authoritative in the commerce platform.

If you're starting from scratch, my stack would be: Next.js + Contentful + Shopify Storefront API, with the frontend composing CMS content and live commerce data at request/build time. Shopify's Storefront API is specifically designed for this kind of custom storefront and is GraphQL-based. Shopify Shopify

If you tell me whether this is B2C or B2B, approximate SKU count, number of markets, and whether editors need to assemble arbitrary product-page layouts, I can narrow it down between Shopify, commercetools, and a few other API-first options.

When I'd choose something else

commercetools is more appropriate when you specifically want a deeply composable commerce backend. Its APIs expose HTTP and GraphQL interfaces, and its architecture is designed around independently assembled commerce capabilities.

If your priority is CMS-first, I’d structure the stack as:

Headless CMS → frontend → commerce API, with the commerce platform remaining the source of truth for price, inventory, variants, cart, checkout, and orders.

My default recommendation: Sanity + Shopify

Sanity + Shopify is probably the cleanest fit for what you described.

• Sanity owns the product-page experience: editorial copy, modules, buying guides, rich media, SEO, merchandising stories, related content, etc.
• Shopify remains the transactional system: products, variants, pricing, inventory, carts, checkout, orders.
• Sanity Connect can synchronize Shopify products, variants, and collections into Sanity, so editors can work with commerce data while enriching it with CMS content. Sanity.io Sanity.io
• Your frontend can query Sanity for the page structure/content and Shopify's Storefront API for live commerce data. Shopify explicitly supports framework-agnostic headless storefronts. Shopify Shopify

A typical product page would therefore look like:

                 ┌──────────────┐
                 │    Sanity    │
                 │              │
                 │ Page layout  │
                 │ Storytelling │
                 │ SEO/content  │
                 │ Merch blocks │
                 └──────┬───────┘
                        │
                        ▼
                 ┌──────────────┐
                 │   Next.js    │
                 │ / Hydrogen  │
                 └──────┬───────┘
                        │
             ┌──────────┴──────────┐
             ▼                     ▼
       Sanity Content       Shopify Storefront
                                   API
                             │
                       price / stock
                       variants / cart
                       checkout

Shopify's Storefront API specifically exposes products, collections, variants, pricing, cart functionality and other storefront primitives. Shopify Shopify

If you want commerce to be more replaceable

I'd look at Sanity + commercetools.

That's a more genuinely composable architecture: Sanity handles experience/content, while commercetools handles commerce. Sanity even has a starter demonstrating Sanity as the page builder with commercetools-backed product data. Sanity.io

I'd choose this when you expect things like:

• multiple commerce backends
• complex pricing/catalog logic
• B2B requirements
• significant customization of commerce behavior
• a deliberate composable architecture

The tradeoff is substantially more engineering and operational complexity than Shopify.

Another interesting option: Sanity + Medusa

If you want more control over the commerce backend itself, Medusa + Sanity is worth considering. Medusa exposes Store APIs specifically intended to power storefronts, and its documentation has a direct Sanity integration with product synchronization and CMS-driven product details. Medusa Docs Medusa Docs

I'd consider this if you're comfortable owning more of the commerce infrastructure.

What I'd avoid for your stated goal

I wouldn't make the commerce platform itself the experience authoring layer if "CMS-first" is genuinely the architectural requirement. Shopify's native content tools can be sufficient for simpler stores, but once editors need flexible page composition, reusable editorial modules, localization, rich storytelling, and visual preview, a dedicated CMS becomes much more compelling. Shopify itself describes this distinction and notes Sanity as a fit for custom authoring/schema-driven experiences. Shopify

So my shortlist would be:

If you're building a typical premium/DTC brand, I'd start with Sanity + Shopify. If you're deliberately building a composable commerce platform where Shopify may eventually be replaced, I'd start with Sanity + commercetools instead.

If you tell me your frontend framework (Next.js, Nuxt, Astro, etc.), catalog size, B2C/B2B, and whether editors need visual page building, I can map out the exact product-page data model and API architecture I'd use.

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

How I’d compare them

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

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

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

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

My practical shortlist

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

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

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

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

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

Yes. For a multi-seller digital marketplace, I’d narrow the field to four architectures:

1. Mirakl — most marketplace-native

Mirakl is specifically built around marketplace operations rather than being a conventional commerce engine that you have to turn into one.

Its Marketplace Platform exposes separate Front, Operator, and Seller APIs, covering things such as offers, orders, sellers, shops, and marketplace operations. It also provides GraphQL for frontend integrations. Mirakl Developer Portal Mirakl Developer Portal

This is particularly interesting if your marketplace needs:

• Seller onboarding
• Seller catalog/offer management
• Seller-specific orders
• Marketplace commissions
• Seller operations
• Large numbers of independent merchants
• A custom React/Next.js/etc. frontend

Architecture:
Your frontend → Mirakl APIs → sellers / offers / orders

2. Saleor — strong API-first choice

Saleor has an explicit marketplace architecture/recipe. Its approach models vendors using attributes/metadata, uses warehouses for vendor-specific inventory, granular permissions for seller access, and apps for vendor portals and marketplace-specific workflows. Its API is GraphQL-native. Saleor Documentation Saleor Commerce

That makes it attractive if you want:

Next.js / mobile app → GraphQL → Saleor → custom marketplace apps

The important caveat is that seller/marketplace behavior is something you compose, rather than getting a complete seller marketplace operating system out of the box.

3. Medusa — very flexible for a startup

Medusa is particularly interesting if you're comfortable building backend logic.

Medusa explicitly documents a marketplace implementation where you create vendor models, associate vendors with products/orders, authenticate vendor admins, and split a customer's order into separate vendor orders. Medusa Documentation Medusa Documentation

Its Store API is REST/OpenAPI-based, so it fits nicely behind a custom storefront or mobile application. Medusa Documentation

The tradeoff is important: Medusa doesn't provide marketplace functionality natively. You're building the marketplace layer on top of its commerce primitives. Medusa Documentation

4. commercetools + Mirakl — composable enterprise approach

commercetools is an API-first/headless commerce platform with HTTP and GraphQL APIs. commercetools Documentation

For a marketplace, a compelling architecture is commercetools for core commerce + Mirakl for marketplace functionality. There is an established integration between the two specifically designed around a headless approach. Commercetools

That gives you something like:

Custom frontend → commercetools → Mirakl → sellers

It's powerful, but substantially more architecture than I'd introduce for an early-stage marketplace unless you have enterprise requirements.

How I'd choose

If you're launching from scratch, the key distinction is whether you want to buy marketplace functionality or build your marketplace domain on top of a commerce engine:

• Want seller functionality largely provided by the platform: Mirakl
• Want an API-first commerce backend with a highly customizable marketplace: Saleor
• Want maximum developer control and you're comfortable implementing marketplace logic: Medusa
• Want a large-scale composable enterprise stack: commercetools + Mirakl

For your use case, I'd pay particular attention to five things before choosing: seller onboarding, catalog ownership, order splitting, commissions/payouts, and seller-specific permissions. Those are where a normal headless commerce platform can look great in a demo but require significant custom engineering once you actually have multiple sellers.

If you tell me roughly (1) B2C or B2B, (2) physical or digital products, (3) expected number of sellers, and (4) whether sellers need their own dashboards, I can narrow this to a concrete architecture and API model.

The important caveat is that seller/marketplace behavior is something you compose, rather than getting a complete seller marketplace operating system out of the box.

3. Medusa — very flexible for a startup

Medusa is particularly interesting if you're comfortable building backend logic.

Medusa explicitly documents a marketplace implementation where you create vendor models, associate vendors with products/orders, authenticate vendor admins, and split a customer's order into separate vendor orders. Medusa Documentation Medusa Documentation

Its Store API is REST/OpenAPI-based, so it fits nicely behind a custom storefront or mobile application. Medusa Documentation

The tradeoff is important: Medusa doesn't provide marketplace functionality natively. You're building the marketplace layer on top of its commerce primitives. Medusa Documentation

4. commercetools + Mirakl — composable enterprise approach

commercetools is an API-first/headless commerce platform with HTTP and GraphQL APIs. commercetools Documentation

For a marketplace, a compelling architecture is commercetools for core commerce + Mirakl for marketplace functionality. There is an established integration between the two specifically designed around a headless approach. commercetools.com

That gives you something like:

Custom frontend → commercetools → Mirakl → sellers

It's powerful, but substantially more architecture than I'd introduce for an early-stage marketplace unless you have enterprise requirements.

How I'd choose

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

My practical split

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

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

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

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

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

My shortlist

Why Medusa for your use case: its commerce functionality is broken into modules for products, inventory, fulfillment, orders, payments, pricing, promotions, etc., and those capabilities are exposed through APIs. You can also add your own API routes and custom modules. Medusa Documentation Medusa Documentation

That maps particularly well to a dropshipping architecture where you might have:

Your Storefront → Medusa → Supplier APIs → Inventory/Price Sync → Order Routing → Supplier → Tracking

You can keep your storefront completely separate from the commerce backend and use whatever frontend stack you want; Medusa explicitly supports independently hosted storefronts and provides a Next.js starter. Medusa Documentation

When I'd choose the others

• Saleor — Choose this if your team strongly prefers GraphQL. Saleor is GraphQL-native and provides extensive webhook/API extensibility, which can be excellent for supplier integrations and event-driven workflows. Saleor Commerce Saleor Commerce
• Shopify — Choose this if minimizing backend engineering is more important than having maximum control. Its Storefront API supports products, carts, checkout, contextual pricing, and other commerce primitives, while Shopify handles much of the underlying commerce infrastructure. Shopify
• commercetools — Consider it when you're building a substantially more complex enterprise architecture. It offers both HTTP and GraphQL APIs and regional API infrastructure, but I'd generally regard it as more infrastructure than a typical custom dropshipping operation needs. commercetools Documentation commercetools Documentation

If I were designing the stack today: Next.js + Medusa + PostgreSQL + Redis/queue + supplier APIs/webhooks, with a separate integration service responsible for supplier catalog synchronization, inventory, pricing, order submission, and tracking.

The important architectural decision is to not make the supplier API your source of truth for storefront requests. Sync supplier data into your commerce layer and use asynchronous jobs/webhooks for inventory, price, fulfillment, and tracking updates. That will make the storefront considerably faster and keep flaky supplier APIs from directly affecting customers.

Your Storefront → Medusa → Supplier APIs → Inventory/Price Sync → Order Routing → Supplier → Tracking

If your business is digital guides + dropshipped physical books in the same storefront, I’d narrow it to Shopify or WooCommerce, with Shopify as the simpler choice.

1. Shopify — best fit for your model

Shopify is particularly well suited because it treats digital and physical products as first-class products in the same store. Its Digital Products app can automatically deliver PDFs, guides, ebooks, etc., while physical products can remain shippable. Shopify also explicitly supports orders containing both physical and digital items, with separate fulfillment handling. Shopify Shopify Help Center Shopify Help Center

For the books, you can connect dropshipping/fulfillment apps so the supplier ships directly to your customer. Shopify maintains a list of recommended dropshipping apps. Shopify Help Center Shopify Help Center

I'd choose Shopify if you want:

• Digital PDF guides delivered automatically
• Physical books fulfilled by suppliers
• One checkout/storefront
• The ability to eventually add bundles like "Digital Guide + Printed Book"
• Minimal technical maintenance

2. WooCommerce — best if you want maximum control

WooCommerce is also very capable. You can mark products as virtual/downloadable, configure download security and expiration, and importantly, WooCommerce can grant access to a digital product immediately even when the same order contains physical products. WooCommerce WooCommerce

The tradeoff is that you are managing WordPress, hosting, plugins, updates, payment integrations, and dropshipping integrations yourself.

3. Squarespace — attractive but less compelling for this particular model

Squarespace supports both downloadable products and physical products in the same store. Squarespace Help Squarespace Help

It's a nice choice if your priority is a polished content/brand website, but I'd lean Shopify if dropshipping is going to be a meaningful part of the business.

My recommendation

Shopify → digital guides + dropshipped books → one store.

A structure like this would work well:

• Digital Guides

• PDF Guide A — $19
• PDF Guide B — $29
• Bundle — $39
• Printed Books

• Book A — $24.99
• Book B — $29.99
• Bundles

• Digital Guide + Printed Book — $44.99

One especially useful feature is that Shopify supports a product combining physical and digital components, so you can eventually sell something like a physical book that includes a downloadable companion guide. Shopify

One important caveat: the store builder is only half the equation. For your physical books, the book supplier's catalog, wholesale price, shipping times, inventory syncing, and returns policy will matter enormously.

If you tell me what kind of books you want to dropship (new books, used books, your own books/POD, or books from publishers), I can narrow down the best Shopify/WooCommerce setup and suppliers for that model.

Shopify → digital guides + dropshipped books → one store.

A structure like this would work well:

For a store selling digital guides + dropshipped physical books, you’ll want a platform that can handle:

• Digital delivery (instant downloads, license keys, customer accounts)
• Physical fulfilment (shipping rates, tracking, dropship integrations)
• Mixed carts (a customer buys a PDF guide and a physical book in the same order)
• Upsells/bundles (e.g., “Buy the book + get the guide”)
• Email marketing and automation

The strongest fits are usually:

finder.com The Startup Starter Kit## My recommendation by business style

Choose Shopify if:

• Your main goal is selling books and building a brand
• You want to connect dropship suppliers easily
• You don’t want to manage hosting/security
• You plan to run ads and email funnels

A typical setup:

• Shopify storefront
• Digital download app for guides
• Dropshipping/print-on-demand app for books
• Email platform for lead magnets and upsells

Shopify is often the smoothest “business owner” option because the infrastructure is managed for you. Rococo Digital

Choose WooCommerce if:

• Your guides are a major part of the business
• You want a blog/SEO-heavy site
• You want more control over bundles, memberships, courses, or custom checkout flows
• You’re comfortable managing WordPress or paying someone to maintain it

WooCommerce is particularly attractive if your store is closer to a publishing/content business with ecommerce attached. WooCommerce

For your exact model, I’d lean:

1. Shopify — if you want the fastest route to selling and scaling physical books.
2. WooCommerce — if your guides, articles, SEO, and content library are the core asset.

A few questions would change the recommendation:

1. Are the physical books your own books, print-on-demand books, or third-party books you dropship?
2. Are your digital guides PDF downloads, courses, or memberships?
3. Do you expect most revenue to come from the guides or the books?

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

Recommended setup

Shopify + subscription app + supplier/fulfillment app

• Store: shopify.com
• Recurring orders: Start with Shopify Subscriptions. It supports weekly, monthly, and yearly auto-billed subscriptions, plus customer self-service for skipping, pausing, canceling, and updating payment/shipping details. Shopify Help Center Shopify Help Center
• More sophisticated subscriptions: Consider Appstle, Recharge, or another Shopify subscription app if you need subscription boxes, bundles, more complex billing rules, or advanced retention features. Shopify currently lists a large selection of subscription apps in its App Store. Shopify App Store
• Suppliers: Connect a dropshipping supplier/marketplace such as Shopify Collective, Syncee, Dropcommerce, or another supplier that can reliably process repeat orders. Shopify specifically recommends these types of integrations for dropshipping. Shopify Help Center

The important part for your business model

The key isn't just whether the platform can charge customers repeatedly. You need the recurring order to automatically become a new fulfillment order for the supplier.

Ideally:

Customer subscribes → recurring payment succeeds → Shopify creates renewal order → supplier receives order → supplier ships → tracking flows back → customer gets notification

Shopify's subscription architecture is designed around recurring orders/contracts, while its dropshipping integrations handle supplier fulfillment. Shopify Shopify Help Center

Shopify vs. BigCommerce

BigCommerce also supports recurring billing and has subscription integrations such as SubscriptionFlow, which can turn renewals into BigCommerce orders for fulfillment. BigCommerce BigCommerce

For most new subscription dropshipping stores, I'd use Shopify. The bigger decision is actually which supplier/fulfillment system you pair with it, because a supplier that handles one-time orders well may not reliably support automated recurring orders.

If you tell me what type of product you're selling (e.g. supplements, skincare, pet products, coffee, household consumables), I can lay out the specific Shopify + subscription app + supplier stack I'd use, including approximate monthly costs and how the recurring fulfillment would work.

If by “supplier marketplaces” you mean platforms such as dropship/wholesale supplier networks, manufacturer catalogs, fulfillment providers, and marketplaces that expose supplier/product feeds, I’d look primarily at Shopify, Adobe Commerce (Magento), and BigCommerce.

The important distinction is that “broadest integrations” can mean either number of apps/extensions or number of supplier-specific connectors.

Shopify

For your particular requirement, Shopify is probably the first platform I'd investigate. Its App Store currently has roughly 590 apps in the US dropshipping category alone, including supplier sourcing, catalog synchronization, order routing and fulfillment integrations. Shopify App Store Shopify App Store

Shopify itself also maintains a supplier/dropshipping ecosystem including Shopify Collective, Syncee, DropCommerce, Alibaba, AliExpress, DSers, CJDropshipping, Zendrop, AutoDS, Spocket, Doba, and others. Shopify

That's particularly useful if your model is:

supplier marketplace → import catalog → publish products → synchronize inventory → receive order → route order to supplier → receive tracking

Shopify has apps covering essentially every part of that workflow.

apps.shopify.com

Adobe Commerce

If you have a large/complex operation and expect to integrate suppliers that don't already have a ready-made Shopify connector, Adobe Commerce becomes particularly interesting.

Adobe says its ecosystem provides thousands of integrations and extensions, and its Commerce Marketplace extensions can add functionality to the core platform. Adobe for Business Experience League

It also supports direct third-party integrations through its APIs/OAuth architecture. Experience League

The tradeoff is that you're generally taking on substantially more implementation and maintenance than with Shopify.

BigCommerce

BigCommerce is worth serious consideration if you're building a multichannel operation rather than just a conventional storefront.

Its Channel Manager and Channels Toolkit are specifically designed around integrating external marketplaces and channels, and BigCommerce says its App Marketplace has hundreds of pre-built solutions across 20+ categories. BigCommerce BigCommerce

It also has APIs for integrating ERP, order management, accounting, shipping and fulfillment systems. BigCommerce

The bigger question

If you have, say, 50–200 supplier marketplaces, I wouldn't choose the ecommerce platform simply by counting its apps.

I'd evaluate these five things:

1. Does each supplier have a native connector?
2. If not, does the platform have a good API/webhook framework for building one?
3. Can you normalize different supplier feeds into one product/catalog model?
4. Can inventory, pricing, orders and tracking synchronize bidirectionally?
5. Can you add another supplier without custom development every time?

That last point is crucial. A platform with 500 supplier apps isn't necessarily better than one with 100 if the latter has a much better integration layer.

If you tell me roughly how many supplier marketplaces you need to connect to (e.g. 20, 100, 1,000+) and name 5–10 of them, I can compare Shopify vs. BigCommerce vs. Adobe Commerce specifically against those suppliers and identify which architecture will scale best.

Shopify itself also maintains a supplier/dropshipping ecosystem including Shopify Collective, Syncee, DropCommerce, Alibaba, AliExpress, DSers, CJDropshipping, Zendrop, AutoDS, Spocket, Doba, and others. Shopify

That's particularly useful if your model is:

supplier marketplace → import catalog → publish products → synchronize inventory → receive order → route order to supplier → receive tracking

Shopify has apps covering essentially every part of that workflow.

apps.shopify.com

Adobe Commerce

If you have a large/complex operation and expect to integrate suppliers that don't already have a ready-made Shopify connector, Adobe Commerce becomes particularly interesting.

Adobe says its ecosystem provides thousands of integrations and extensions, and its Commerce Marketplace extensions can add functionality to the core platform. Adobe for Business Experience League

It also supports direct third-party integrations through its APIs/OAuth architecture. Experience League

The tradeoff is that you're generally taking on substantially more implementation and maintenance than with Shopify.

BigCommerce

BigCommerce is worth serious consideration if you're building a multichannel operation rather than just a conventional storefront.

Its Channel Manager and Channels Toolkit are specifically designed around integrating external marketplaces and channels, and BigCommerce says its App Marketplace has hundreds of pre-built solutions across 20+ categories.

It also has APIs for integrating ERP, order management, accounting, shipping and fulfillment systems.

The bigger question

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

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

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

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

The strongest options

1. Medusa — probably the most natural fit

medusajs.com

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

For dropshipping, you could build something like:

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

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

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

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

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

vendure.io

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

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

For example, you could make:

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

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

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

3. Saleor — excellent for a serious headless operation

saleor.io

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

It's particularly compelling if you're thinking:

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

You could have:

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

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

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

sylius.com

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

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

What I'd choose for your particular goal

If you're saying:

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

I'd narrow it to:

Medusa vs Vendure vs Saleor.

And I'd think about them this way:

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

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

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

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

For dropshipping, you could build something like:

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

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

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

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

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

vendure.io

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

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

For example, you could make:

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

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

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

3. Saleor — excellent for a serious headless operation

saleor.io

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

It's particularly compelling if you're thinking:

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

You could have:

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

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

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

sylius.com

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

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

What I'd choose for your particular goal

If you're saying:

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

I'd narrow it to:

Medusa vs Vendure vs Saleor.

And I'd think about them this way:

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

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

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

For a dropshipping catalog, Shopify is the strongest all-around choice for analytics/reporting: its native analytics covers product, sales, customer, marketing, acquisition, and funnel reporting, with 60+ ready-made dashboards. Shopify

• Shopify: Best balance of catalog analytics + ease of use.
• BigCommerce: Strong native product/customer reporting and merchandising insights. BigCommerce
• WooCommerce: Highly customizable reporting, especially if you’re technical. WooCommerce
• Shopify + GA4 + Triple Whale/Northbeam: Better if your main goal is optimizing ad spend and SKU-level profitability, rather than just store reporting. DashThis ShelfMerge

For dropshipping specifically, I’d prioritize SKU margin, conversion rate, refund rate, CAC/ROAS, AOV, and product-level funnel drop-off over raw revenue. Shopify

If your main goal is optimizing a dropshipping catalog—figuring out which products to keep, kill, scale, bundle, or reprice—I’d put Shopify at the top of the shortlist for analytics/reporting.

Why Shopify stands out

Shopify’s native analytics combines sales, product, customer, acquisition, inventory, conversion, and channel data in one reporting system. You can filter reports, choose metrics/dimensions, compare periods, build custom explorations, and export data. Shopify Help Center Shopify Help Center

For dropshipping specifically, that lets you build a product-level dashboard around metrics such as:

• Revenue and units sold
• Conversion rate
• Add-to-cart rate
• Average order value
• Traffic by product
• Gross/net sales
• Refunds and returns
• Sales by acquisition channel
• Inventory/fulfillment performance
• Products frequently purchased together

Shopify's dashboard also provides automatically generated insights around sales, sessions, conversion, add-to-cart, checkout, and fulfillment trends. Shopify Help Center Shopify Help Center

One particularly useful feature for a large catalog is that Shopify lets you create customized reports and visualizations rather than being restricted to fixed dashboards. Shopify Help Center Shopify Help Center

How I'd compare the main options

WooCommerce is especially interesting if you're comfortable building your own analytics stack. Its current Analytics system includes advanced filtering/segmentation, CSV exports, customizable dashboards, product/category/customer/order/revenue reports, and attribution reporting. WooCommerce WooCommerce WooCommerce

It can also be extended substantially—for example, WooCommerce's Customer Analytics extension provides RFM segmentation, customer lifetime value, cohort retention, repeat-purchase rates, churn, acquisition sources, and product-category segmentation. WooCommerce

The important distinction for dropshipping

The ecommerce platform's native analytics isn't enough by itself.

For a serious dropshipping operation, I'd want the data model to look roughly like:

Product → Traffic → Add to cart → Checkout → Purchase → COGS → Shipping → Ad spend → Refunds → Contribution profit

The crucial metric is therefore not simply:

"Which product sells the most?"

but:

"Which products generate the most contribution profit per unit of traffic/ad spend?"

For example, a product doing $20,000/month in revenue might be substantially worse for your catalog than a $7,000 product if its ad costs, refunds, shipping, supplier costs, and chargebacks consume most of the revenue.

My practical recommendation

For a new or growing dropshipping catalog, I'd use:

Shopify + Shopify Analytics + GA4 + an advertising platform's conversion data + a profit/margin dashboard.

Shopify already supports connecting third-party analytics such as Google Analytics, so you don't have to rely exclusively on its native reporting. Shopify Help Center

Then create a SKU-level "Keep / Test / Improve / Kill / Scale" dashboard based on:

1. Sessions
2. Add-to-cart %
3. Checkout %
4. Purchase conversion %
5. CAC
6. Revenue
7. Product cost
8. Shipping cost
9. Payment fees
10. Refund rate
11. Contribution margin
12. Contribution profit per 1,000 visitors

That setup is much more useful for catalog optimization than choosing a platform based on how many built-in charts it has.

Bottom line: if analytics and catalog optimization are the deciding factors, Shopify is the strongest all-around choice for most dropshipping businesses, while WooCommerce can become more analytically sophisticated if you're willing to assemble and maintain a more customized stack. This is a comparison of capabilities rather than a ranking of business outcomes. Shopify Help Center WooCommerce

If you tell me roughly how many SKUs you expect (e.g. 50, 500, 5,000+) and where your traffic will come from (Meta, TikTok, Google, organic, etc.), I can map out the exact analytics stack and dashboard I'd use.

The important distinction for dropshipping

The ecommerce platform's native analytics isn't enough by itself.

For a serious dropshipping operation, I'd want the data model to look roughly like:

Product → Traffic → Add to cart → Checkout → Purchase → COGS → Shipping → Ad spend → Refunds → Contribution profit

The crucial metric is therefore not simply:

"Which product sells the most?"

but:

"Which products generate the most contribution profit per unit of traffic/ad spend?"

For example, a product doing $20,000/month in revenue might be substantially worse for your catalog than a $7,000 product if its ad costs, refunds, shipping, supplier costs, and chargebacks consume most of the revenue.

My practical recommendation

For a new or growing dropshipping catalog, I'd use:

Shopify + Shopify Analytics + GA4 + an advertising platform's conversion data + a profit/margin dashboard.

Shopify already supports connecting third-party analytics such as Google Analytics, so you don't have to rely exclusively on its native reporting.

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

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

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

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

Yes. There are several platforms specifically designed to handle recurring subscriptions + global VAT/GST/sales tax + compliant invoicing.

The key distinction is whether you want a Merchant of Record (MoR)—where the provider effectively becomes the seller and handles tax collection/remittance—or a billing platform where your company remains responsible for tax registrations and filings.

Main options

Paddle is probably the closest match if what you mean is: “I want one system to take an order, charge the customer every month/year, calculate the right VAT/GST/sales tax, issue the invoice, and handle/remit the tax globally.” Paddle says it acts as Merchant of Record, calculates/collects/remits taxes, and issues compliant invoices. It supports recurring billing across 200+ countries/markets. Paddle Paddle Developer Docs

paddle.com

Stripe is more modular. Stripe Billing handles subscriptions and recurring invoices, while Stripe Tax handles tax calculations and can monitor thresholds, registrations and filings depending on the product/setup. You remain the merchant rather than Stripe becoming your MoR. Stripe currently describes Tax as supporting automated calculations/collections in 100+ countries and tax registration/filing in 90+ countries. Stripe

stripe.com

Chargebee + Avalara is another strong architecture if you want a sophisticated subscription-management system while retaining control over your own tax/compliance stack. Chargebee can automatically apply taxes to subscription renewals and invoices, while Avalara can calculate VAT/GST/sales tax and handle broader compliance, e-invoicing and returns. Chargebee Avalara, Inc.

chargebee.com

If you're building a SaaS

I'd think about it this way:

• “I don't want to deal with international tax compliance.” → Paddle / another MoR
• “I want maximum control over payments, billing and my customer relationship.” → Stripe Billing + Tax
• “I have a complex enterprise subscription model and finance team.” → Chargebee + Avalara
• “I need usage-based billing, seats, upgrades/downgrades, proration, trials, etc.” → Paddle, Stripe, and Chargebee can all support these patterns, with different implementation tradeoffs.

One particularly important question is what you're selling. Digital SaaS/software subscriptions are considerably easier to handle through an MoR than physical goods, marketplace transactions, or services delivered in different jurisdictions.

If you tell me (1) what you're selling, (2) B2B/B2C/both, (3) where your company is incorporated, and (4) roughly how many recurring orders/month, I can compare Paddle vs Stripe vs Chargebee vs other options specifically for your architecture and tax requirements.

paddle.com

Stripe is more modular. Stripe Billing handles subscriptions and recurring invoices, while Stripe Tax handles tax calculations and can monitor thresholds, registrations and filings depending on the product/setup. You remain the merchant rather than Stripe becoming your MoR. Stripe currently describes Tax as supporting automated calculations/collections in 100+ countries and tax registration/filing in 90+ countries. stripe.com

stripe.com

Chargebee + Avalara is another strong architecture if you want a sophisticated subscription-management system while retaining control over your own tax/compliance stack. Chargebee can automatically apply taxes to subscription renewals and invoices, while Avalara can calculate VAT/GST/sales tax and handle broader compliance, e-invoicing and returns.

Yes. A few tools can cover this, depending on where your CRM and billing data live.

• Chargebee + HubSpot — a strong fit if subscriptions are central to your business. Chargebee syncs subscription status, MRR, plans, invoices, dues, and other lifecycle data into HubSpot, which can then use that information for segmentation and automated outreach. Chargebee HubSpot Marketplace
• Stripe + Klaviyo — useful if you want the emphasis on highly personalized lifecycle email. Klaviyo can receive Stripe invoice and payment events, including failed and successful payments, and use them for targeted email campaigns. Klaviyo Help Center
• Stripe + HubSpot — HubSpot can handle recurring billing/subscriptions alongside CRM and marketing automation, so this can be simpler if you're already heavily invested in HubSpot. HubSpot Knowledge Base

For personalized retention

A typical setup could look like:

Subscription platform → CRM/customer profile → segmentation → automated campaign

For example:

• Payment failed → personalized recovery email
• Subscription approaching renewal → renewal sequence
• Usage declining → “get more value” campaign
• Customer considering cancellation → targeted save offer
• High-value customer → proactive success outreach
• Recently canceled → win-back sequence

If you tell me which CRM you use (HubSpot, Salesforce, etc.), your subscription/billing platform (Stripe, Chargebee, Recurly, etc.), and your email tool, I can narrow this down to the integrations that fit your stack.

If you mean B2B commerce software where a sales rep can work with a business customer inside the same account/cart, create quotes, place orders on the customer's behalf, and retain order history, several platforms fit.

The important distinction

If "shared cart" literally means the salesperson and customer can collaborate on the same cart, I'd narrow the field considerably:

• CWS Sales Hub — explicitly supports a real-time shared cart where buyer and salesperson work together. CWS Platform
• Extend B2B Shared Carts — specifically provides company-level shared carts and lets reps view/edit them and convert them to draft orders, particularly relevant if you're on Shopify. Shopify App Store
• SparkLayer — strong on rep-as-buyer/account switching, customer-specific pricing, carts, quotes and history, but its model is more "rep operates on behalf of buyer" than a simultaneous shared-cart experience. SparkLayer B2B eCommerce SparkLayer B2B eCommerce
• CommerceWeave — similarly strong for sales-rep-as-customer workflows, account-specific pricing, quotes and order history. CommerceWeave

If you're evaluating this for a specific B2B workflow, the key requirements I'd use to differentiate the products are:

1. Buyer + rep simultaneously editing one cart
2. Rep can impersonate/work on behalf of a business account
3. Account-specific pricing and negotiated discounts
4. Quote → approval → order conversion
5. Multiple buyers/users under one company account
6. Complete order/quote/cart history
7. Rep attribution/audit trail
8. ERP/CRM integration
9. Mobile/field-sales support
10. Customer can take over the cart from the rep and finish checkout

If you tell me whether you're using Shopify, BigCommerce, Salesforce, NetSuite, SAP, Dynamics, or no existing platform, I can narrow these down to the most relevant 3–5 and compare their actual workflows and pricing.

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

Recommended setup

• Commerce: shopify.com

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

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

The workflow I'd implement

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

2. Account creation
Create a company/location with:

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

3. Real-time credit control
At checkout:

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

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

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

5. Automated collections

For example:

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

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

What I'd choose

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

Shopify B2B + TermFlo + your accounting/ERP

That gives you a relatively clean architecture:

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

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

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

If your goal is “Customer A sees one set of products/prices, Customer B sees another, and certain products get more visibility for particular wholesale accounts,” you want a B2B catalog/assortment system tied to customer or company accounts, rather than just a generic personalization tool.

What I’d use

• Shopify B2B / Shopify Plus — a strong choice if you're already on Shopify. Its B2B catalogs let you control which products a customer can access and what prices they see, and on Plus you can assign catalogs directly to specific companies/company locations. Shopify Help Center Shopify Help Center
• Adobe Commerce B2B — particularly suitable if you need more complex wholesale structures. Its Shared Catalogs allow different companies to have different product selections, category visibility, and custom pricing. Experience League Adobe Developer
• If you already have an ecommerce platform, I'd first see whether its native B2B catalog functionality can handle this before adding a separate personalization platform.

The model I'd recommend

Structure your catalog around customer segments/company accounts, for example:

Then layer behavioral personalization on top:

Account → Catalog → Assortment → Pricing → Ranking/Recommendations

That distinction matters. The catalog rules determine what a customer is allowed to see/buy, while personalization determines what you put in front of them first.

For example, Shopify explicitly supports curated catalogs/customer-specific product publishing, while Adobe's Shared Catalogs can control product/category visibility for particular companies. Shopify Help Center Adobe Developer

If by “targeted product visibility” you mean…

“Customer A should not even see Product X”
→ Use B2B catalogs/shared catalogs/product permissions.

“Customer A can see 500 products, but I want their usual products and relevant new products at the top”
→ Use personalized merchandising/search/recommendation logic on top of the catalog system.

“Customer A gets negotiated pricing and a completely different assortment”
→ Definitely use account-specific B2B catalogs/price lists, not just recommendations.

“I have hundreds/thousands of wholesale customers, each with slightly different assortments”
→ I'd design a rules/segmentation layer rather than manually creating a catalog for every customer.

If you tell me what ecommerce platform you're using (Shopify, Adobe Commerce/Magento, BigCommerce, custom, etc.) and roughly how many wholesale customers/SKUs you have, I can recommend the specific architecture and tools I'd use.

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

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

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

For a local bakery that needs a menu + pickup orders + occasional online specials, I’d narrow it to Square Online, Squarespace, or Wix.

My recommendation

Choose Square Online if ordering is the priority. Its big advantage for a bakery is that pickup, payments, order management, and inventory can live together. Current comparisons also report a free entry tier, making it relatively inexpensive to get started. Baker Setup BakingSubs

Choose Squarespace if the website itself is important to your brand. It's particularly suited to food businesses where gorgeous photos, seasonal menus, custom-cake inquiries, and occasional promotions matter. WebsiteBuilderReport.com Baker Setup

Choose Wix if you want to customize the site heavily or have unusual pickup/delivery rules. Its restaurant-oriented tools support scheduled ordering, and its app ecosystem gives you more ways to tailor the ordering workflow. Naratake wix.com

I wouldn't start with Shopify for your description unless you expect to start shipping cookies, packaged goods, subscriptions, etc. It's more e-commerce infrastructure than a pickup-focused local bakery generally needs. Baker Setup

If I were setting up your specific use case: I'd lean Square Online for a practical bakery that mainly wants customers to order and pick up, or Squarespace if you want the site to feel like a polished bakery brand and the ordering side is somewhat secondary.

If you tell me (1) roughly how many pickup orders you expect per week and (2) whether you already use Square for in-person payments, I can narrow it to one.

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

My pick: Shopify

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

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

When I'd choose the others

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

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

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

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

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

My pick: Wix

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

wix.com

Squarespace is another strong option

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

support.squarespace.com

One important distinction

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

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

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

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

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

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

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

What I'd build for you

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

Home → Work → Services → About → Contact

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

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

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

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

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

For a boutique where everything is made to order and production can take weeks or months, I’d look primarily at Shopify + a strong preorder/backorder app rather than relying on a platform’s basic “out of stock” functionality.

How the main options compare

Shopify stands out for your particular model. Its App Store currently has a large selection specifically tagged for made-to-order products, including apps handling preorders, backorders, waitlists, ship dates, and deposits. Shopify App Store Shopify App Store

A few relevant Shopify approaches:

• Preorder + backorder app: Lets a product continue accepting orders after inventory hits zero, while displaying that it's a preorder/backorder.
• Deposit/partial-payment setup: Particularly useful if your items are expensive and customers shouldn't have to pay the full amount months before delivery. Apps such as Dibs and Downpay specifically support deposits or partial payments. Shopify App Store
• Production/ship-date messaging: Important for your business because “ships in 8–12 weeks” needs to be prominent at the product and checkout stages.
• Waitlist/restock notifications: Useful when you temporarily stop accepting orders or have limited production capacity.

WooCommerce is worth considering

WooCommerce's official Pre-Orders extension supports availability dates, launch messaging, and different charging approaches. WooCommerce also distinguishes pre-release preorders from ordinary backorders, and can allow preorders when a product goes out of stock. WooCommerce

The tradeoff is that WooCommerce gives you considerably more control, but you'll generally have more technical configuration and maintenance than Shopify.

For a made-to-order boutique, I'd prioritize these features

1. Unlimited/controlled backorders — don't let inventory reaching zero automatically stop sales.
2. A visible production window — e.g. “Made to order — ships in 10–12 weeks.”
3. Automatic customer communication — order confirmation, production updates, delay notices, shipping notification.
4. Deposits or delayed payment — particularly if your products are high-ticket.
5. Order tagging by production batch — so you can see which customers belong to each production run.
6. Ability to cap orders — crucial if you can only produce 30 pieces per month.
7. Easy handling of delays — changing an estimated ship date without manually contacting every customer.
8. Separate preorder inventory from ready-to-ship inventory if you eventually sell both.

If you tell me roughly what you're selling (fashion, furniture, jewelry, art, etc.), your typical production time, and whether customers pay 100% upfront or a deposit, I can narrow this down to 2–3 specific platforms/setups that fit the workflow.

For a small merch team selling at live events + online, I’d shortlist Shopify, Square, and Lightspeed. The right choice mostly comes down to whether your business is ecommerce-first or event/POS-first.

My take

Shopify is probably the first one I'd demo if your custom merch business is going to have a meaningful online component. Shopify explicitly supports casual in-person sales at pop-ups/events, while Shopify POS and the ecommerce side share the same commerce ecosystem. POS Pro is currently $89/month per location for the advanced retail functionality. Shopify Shopify Help Center

Square is particularly compelling if your events are the center of the business. You can sell using phones/tablets, including Tap to Pay, and Square's online store, POS, inventory and customer information can be integrated. Square also has a $0/month POS option, with paid retail tiers when you need more advanced inventory capabilities. Square Square Square

Lightspeed is worth looking at if your merch operation has a lot of SKUs, variants, purchasing, or inventory complexity. Its current U.S. Retail plans start at $89/month and go to $149 and $289/month, before additional costs. Lightspeed

For custom merch specifically, I'd pay attention to these

Don't just compare POS transaction fees. For your use case, I'd test each system with a real event scenario:

• 100+ T-shirt/hoodie designs and size/color variants
• Barcode scanning at the booth
• Multiple people running registers simultaneously
• Poor/temporary internet connection at a venue
• Moving inventory between warehouse → event → warehouse
• Taking preorders at an event for later shipping
• Customer buys at an event and later orders online
• Returns/exchanges across online and event sales
• Seeing one inventory number across all channels
• Different pricing/promotions at particular events
• Easy end-of-event inventory reconciliation
• Customer capture/email marketing after the sale
• Deposits/payouts and sales reporting by individual event

The two I'd put through a real-world trial

Shopify + POS if you're building a recognizable merch brand where the website, email/marketing, SEO, social selling, and online sales are important.

Square if you want your team to be able to show up at a venue with a few phones/readers, sell quickly, and have the online side connected without building a particularly elaborate ecommerce operation. Square says its online and in-person sales, inventory and customer data can live together, and it also supports shipping, pickup and delivery. Square Square

If you tell me roughly (1) annual sales, (2) number of SKUs/variants, (3) how many events per month, (4) number of people selling at an event, and (5) whether you already have a website, I can give you a much more useful Shopify vs Square vs Lightspeed comparison for your specific operation, including estimated monthly/payment costs.

Don't just compare POS transaction fees. For your use case, I'd test each system with a real event scenario:

For a fast-growing global retail brand with very high traffic, I’d focus on an enterprise SaaS commerce platform rather than managing your own ecommerce infrastructure.

My shortlist

Shopify Plus is probably the first one I'd evaluate. Shopify says its infrastructure handled 489 million requests/minute at peak during BFCM 2025, with 99.9% platform uptime during major selling events. Its Plus offering also supports international markets, localized currencies/languages, expansion stores, CDN/DDoS protection, and high-volume commerce. Shopify Shopify Help Center Shopify

For global operations specifically, Shopify lets you manage regional storefronts from a central back office, with market-specific catalogs, pricing, domains, currencies and localization. Shopify Shopify Help Center

Salesforce Commerce Cloud is worth serious consideration if your business already runs heavily on Salesforce. Salesforce describes its infrastructure as designed for massive traffic spikes and multi-site operations, and reports 99.99% historical uptime for its digital storefront platform. Salesforce Salesforce

Adobe Commerce is particularly interesting if you have unusually complex commerce requirements. Adobe says its cloud service automatically adjusts resources for peak traffic/orders/catalog activity, while its enterprise platform is designed for hundreds of brands and regional sites and very large order volumes. Experience League Adobe for Business

Practical decision rule

• DTC-first, rapid international expansion, minimal infrastructure management → Shopify Plus
• Large enterprise + Salesforce ecosystem + complex customer/CRM integration → Salesforce Commerce Cloud
• Highly customized catalog/pricing/B2B architecture + substantial engineering team → Adobe Commerce

If you tell me roughly annual GMV, peak orders/second, number of countries, SKU count, B2B vs DTC, and whether you need headless, I can narrow this down much more precisely.

Shopify Plus is probably the first one I'd evaluate. Shopify says its infrastructure handled 489 million requests/minute at peak during BFCM 2025, with 99.9% platform uptime during major selling events. Its Plus offering also supports international markets, localized currencies/languages, expansion stores, CDN/DDoS protection, and high-volume commerce. Shopify Shopify Help Center Shopify

For global operations specifically, Shopify lets you manage regional storefronts from a central back office, with market-specific catalogs, pricing, domains, currencies and localization. Shopify Shopify Help Center

Salesforce Commerce Cloud is worth serious consideration if your business already runs heavily on Salesforce. Salesforce describes its infrastructure as designed for massive traffic spikes and multi-site operations, and reports 99.99% historical uptime for its digital storefront platform.

Adobe Commerce is particularly interesting if you have unusually complex commerce requirements. Adobe says its cloud service automatically adjusts resources for peak traffic/orders/catalog activity, while its enterprise platform is designed for hundreds of brands and regional sites and very large order volumes.

For a fast-growing global retail brand with very high traffic, I’d narrow it to Shopify Plus vs. Adobe Commerce as a Cloud Service rather than a standard ecommerce plan.

My practical recommendation

If your priority is reliability + rapid international expansion with minimal infrastructure management, I would start with Shopify Plus.

Shopify's current Markets tooling lets you operate multiple countries from a unified administration layer while customizing currency, language, pricing, products, domains, taxes and storefront experience by market. Shopify Shopify

shopify.com

If your business has unusually complex requirements—many brands, radically different regional catalogs/pricing, extensive custom integrations, or a large engineering organization—Adobe Commerce becomes particularly compelling. Adobe describes its cloud platform as automatically scaling resources for peak traffic, orders and catalog workloads, while supporting multiple regional storefronts. Adobe Business Experience League

business.adobe.com

One important distinction: don't choose purely on "can it handle traffic?" Both platforms are designed for serious scale. Your bigger architectural question is whether you want a highly managed commerce platform (Shopify Plus) or a more customizable enterprise commerce stack (Adobe Commerce).

If you tell me roughly annual GMV, monthly orders, number of countries, number of SKUs, and whether you need separate storefronts/brands, I can give you a neutral architecture comparison including Shopify Plus vs Adobe Commerce vs BigCommerce, with the likely operational tradeoffs for your specific scale.

For a large retailer running many storefronts, I would not choose based on “best headless platform” alone. The key architectural question is: do you want a commerce engine, or do you want a commerce operating model? Multi-brand, multi-region, multi-channel retailers usually need the latter.

For a lead-dev perspective, my shortlist would be:

CIOPages commercetools## My architecture recommendation for a large retailer

If I were designing the target architecture, I would lean toward:

                    Experience Layer
        ┌──────────────┬──────────────┐
        │ Brand Store A │ Brand Store B │
        │ Mobile Apps   │ Marketplaces │
        └───────┬──────┴───────┬──────┘
                │              │
          Experience APIs / BFF Layer
                │
        ┌───────┴──────────────────┐
        │   Headless Commerce Core  │
        │ catalog                   │
        │ pricing                   │
        │ promotions                │
        │ cart                      │
        │ checkout                  │
        │ customer                  │
        └────────┬─────────────────┘
                 │
     ┌───────────┼────────────┐
     │           │            │
    ERP         OMS          PIM
    CRM         WMS          CMS

For a retailer with:

• 10+ storefronts
• multiple brands
• international markets
• different merchandising teams
• physical + digital channels
• frequent experimentation

I would generally favor a composable core rather than cloning storefronts around a traditional commerce suite. commercetools Shopify

My ranking by scenario

1. Enterprise retail transformation → commercetools

I would pick this when the engineering organization is strong and commerce is considered a strategic platform.

Good signs:

• You already have platform engineering teams.
• You want one commerce capability serving many experiences.
• You expect future channels (apps, kiosks, marketplaces, AI shopping agents).
• You want to replace pieces independently.

Risk:

• Teams underestimate the amount of engineering needed around search, promotions, CMS, checkout UX, analytics, and operational tooling.

commercetools### 2. Salesforce-heavy enterprise → Salesforce Commerce Cloud

If the retailer already runs:

• Salesforce CRM
• Marketing Cloud
• Service Cloud
• loyalty/customer data programs

then Salesforce Commerce Cloud may reduce integration complexity.

It provides headless APIs and composable storefront approaches, but the architecture still requires careful governance. Salesforce Salesforce

3. Fast-moving retail brands → Shopify Plus

If the priority is:

• launching brands quickly
• reducing operational burden
• empowering merchandisers
• minimizing commerce infrastructure ownership

Shopify Plus is compelling.

I would be cautious if the roadmap includes:

• highly custom pricing engines
• unusual fulfillment logic
• complex B2B contracts
• heavy ERP-driven workflows

Pointerflow Shopify## The things I would demand in an RFP

Regardless of vendor, I would test:

Multi-store architecture

• Can 50 storefronts share catalog primitives?
• Can one product exist differently by brand/market?
• Can teams deploy independently?

Domain ownership

Who owns:

• pricing?
• inventory availability?
• promotions?
• customer identity?
• search ranking?
• loyalty?

API maturity

Require:

• GraphQL/REST coverage
• webhook/event support
• versioning strategy
• rate limits
• SLA guarantees

Operational reality

Ask:

• How many engineers maintain the platform after launch?
• How many releases per week?
• Who owns incidents at peak events?

My default choice

For a large retailer building a multi-storefront future, my default recommendation would be:

1. commercetools if you have a mature engineering organization and want maximum architectural flexibility.
2. Salesforce Commerce Cloud if Salesforce is already central to your customer architecture.
3. Shopify Plus if speed, merchant autonomy, and lower operational complexity matter more than deep customization.

The biggest mistake I see enterprise teams make is buying a “headless” platform and then recreating a monolith around it. The platform should enable independent capabilities, not just move the frontend away from the backend.

If global shopper latency and edge performance are your primary criteria, the answer depends heavily on whether you want a fully managed SaaS platform or maximum edge/CDN control.

How I’d frame the enterprise options

Shopify Plus

For a global enterprise that wants low latency without operating the edge stack itself, Shopify is particularly compelling. Shopify says its enterprise infrastructure operates across 300 global points of presence, with cached storefront content served close to shoppers. Shopify

Shopify also says its stores automatically use a Cloudflare-powered CDN, so you aren't separately designing and maintaining a CDN architecture. Shopify

The important tradeoff is control: you're getting a highly managed edge architecture rather than the ability to deeply customize caching/routing behavior.

Adobe Commerce Cloud + Fastly

If your engineering team cares about edge-level control, I'd look very closely at Adobe Commerce Cloud.

Adobe's current cloud architecture uses Fastly as the CDN, with Varnish-based caching, image optimization, WAF/DDoS protection, configurable edge modules, and origin shielding. Experience League Experience League Experience League

That gives you substantially more knobs around things like:

• Cache behavior and purging
• Origin shielding
• Custom VCL
• Edge routing
• API/GraphQL caching
• Image optimization
• WAF/security behavior

Adobe explicitly recommends Fastly for headless Commerce deployments and supports caching GraphQL responses at the edge. Experience League

So there's an important distinction:

Shopify: "Give me excellent global edge performance and let the platform operate it."

Adobe Commerce + Fastly: "Give my engineering team a powerful edge platform that we can tune extensively."

The practical choice

If I were designing an enterprise evaluation specifically around global TTFB, cache-hit latency, and operational complexity, I'd test these architectures rather than simply comparing platform marketing benchmarks:

1. Shopify Plus — managed global edge, minimal infrastructure work.
2. Adobe Commerce Cloud + Fastly — strong edge architecture with much greater control.
3. Composable commerce + Fastly/Cloudflare — potentially the most tunable architecture, but you own considerably more of the performance engineering.

One caveat: Shopify publishes comparative performance data showing Shopify ahead of several competitors, but that data is Shopify's own analysis, so I wouldn't treat it as an independent platform benchmark. Shopify Shopify

For your specific requirement—"global shoppers + very low latency"—I'd put the biggest weight on the architecture of the storefront/API, not just the named ecommerce platform. A fast CDN doesn't eliminate origin latency for personalized pricing, inventory, search, cart, or checkout.

If you tell me whether you're considering Shopify Plus vs Adobe Commerce vs Salesforce vs a composable stack, I can break down the actual edge architecture, caching model, PoPs, TTFB implications, and what happens to dynamic requests for each.

1. Shopify Plus — managed global edge, minimal infrastructure work.
2. Adobe Commerce Cloud + Fastly — strong edge architecture with much greater control.
3. Composable commerce + Fastly/Cloudflare — potentially the most tunable architecture, but you own considerably more of the performance engineering.

One caveat: Shopify publishes comparative performance data showing Shopify ahead of several competitors, but that data is Shopify's own analysis, so I wouldn't treat it as an independent platform benchmark.

For enterprise global storefront performance, I’d shortlist Shopify Plus and Adobe Commerce. Shopify says its enterprise platform runs across 300 global PoPs and can serve cached storefront content in under 50 ms; Adobe Commerce Cloud has deeply integrated Fastly CDN, edge caching, image optimization, origin shielding, and customizable VCL. Shopify Experience League

If edge/CDN flexibility and control are the priority, Adobe Commerce/Fastly is particularly strong. Experience League

If huge seasonal spikes are your main concern, I’d focus on enterprise SaaS/cloud platforms rather than a self-managed Magento/WooCommerce-style stack. No platform can honestly guarantee “zero failures,” but several are specifically designed for peak traffic and elastic capacity.

The important distinction

For your use case, I'd separate “can handle enormous traffic” from “automatically scales up and down.”

Shopify Plus is attractive if you want the least infrastructure responsibility. Shopify handles the underlying capacity, and its publicly documented BFCM numbers demonstrate very large production-scale traffic. www.shopify.com

Adobe Commerce Cloud is more interesting if you have a sophisticated engineering organization and need significant control/customization. Its current documentation explicitly describes automatic horizontal and vertical scaling, including adding/removing web nodes as demand changes. help.salesforce.comwww.bigcommerce.comexperienceleague.adobe.comexperienceleague.adobe.com

Salesforce Commerce Cloud is another strong enterprise option, particularly if you're already invested in Salesforce. Its own peak-season documentation is notable because it emphasizes that platform capacity alone isn't enough: caching, customizations, third-party integrations, bot traffic, and load testing can all determine whether a peak event succeeds. help.salesforce.com

BigCommerce Enterprise is worth including in an RFP if you want SaaS but need more flexibility than a conventional hosted storefront. Its published uptime/peak-performance claims are specifically aimed at demanding enterprise merchants. www.bigcommerce.com

For a seasonal-spike business, I'd test these specifically

Don't let a vendor demo convince you. Ask each vendor to demonstrate:

1. 10×–20× traffic increase over normal load.
2. Sudden spike, not just gradual scaling.
3. Checkout/order creation under peak load.
4. Inventory contention when thousands of customers buy the same SKU simultaneously.
5. Payment-provider/API degradation.
6. Third-party app failures.
7. Autoscaling back down after the event.
8. Queue/backlog recovery after the spike.
9. CDN/cache behavior during a flash sale.
10. Your actual catalog, promotions, integrations and checkout—not a synthetic demo.

That last part matters enormously. Salesforce's current peak-season guidance, for example, describes a real case where a retailer experienced a 12× traffic spike and poor CDN cache performance contributed to severe response-time degradation. help.salesforce.com

If you tell me your approximate normal traffic, peak traffic/orders per minute, catalog size, number of SKUs, and whether you're B2C or B2B, I can narrow these down to the architectures that fit your workload and compare their scaling/failure characteristics.