All answers

For a growing local retailer with limited developer resources, I’d narrow it to Shopify vs. BigCommerce, with Shopify generally fitting the “launch easily now, scale later” model particularly well.

My shortlist

Shopify currently starts at $29/month when billed annually, includes online and in-person selling, inventory management, marketplace/social selling, and an ecosystem of thousands of apps. Its higher tiers add capabilities such as more staff accounts, international selling, greater API capacity, and eventually Shopify Plus. Shopify Shopify Help Center

BigCommerce is particularly interesting if you expect a complicated catalog, multiple storefronts, B2B requirements, or want more functionality built into the platform rather than relying on apps. Its current Core plan is $29/month annually, with Growth at $79 and Scale at $299; the platform automatically moves merchants between plans based on sales thresholds. BigCommerce BigCommerce

What I'd optimize for in your situation

Don't choose based primarily on today's website. Choose based on what you won't have to rebuild later:

• POS + online inventory synchronization
• Multiple physical locations
• Shipping/fulfillment integrations
• Accounting/ERP integration
• Customer accounts and loyalty
• Email/SMS marketing integrations
• Marketplace/social selling
• API access for future custom development
• International sales, if that's plausible
• B2B/wholesale, if that's plausible

For a retailer specifically, Shopify's combination of online commerce and POS is worth paying attention to; Shopify explicitly supports selling online and in person from the same platform. Shopify

One important architectural recommendation

With limited developers, don't build a custom storefront or custom commerce backend yet.

I'd use a managed platform, keep your product/customer/order data clean, and integrate specialized systems around it. That lets you spend scarce engineering time on things that actually differentiate your business rather than maintaining checkout, payments, inventory infrastructure, security, and hosting.

If you tell me roughly how many SKUs you have, annual/current revenue, number of physical stores, POS system, and whether you need B2B/wholesale, I can narrow this to a specific platform + plan and explain what your likely migration path would look like over the next 3–5 years.

If your main goal is to minimize PCI DSS compliance work, choose a fully hosted SaaS ecommerce platform with hosted checkout and a PCI-compliant payment processor. The less your systems touch cardholder data, the smaller your compliance scope usually becomes. LeadingIT BigCommerce

A practical ranking by compliance burden (lowest → higher):

What I would look for if PCI is the priority

Choose a platform/payment setup with:

• Hosted checkout or hosted payment fields (so your server never receives raw card numbers). WooCommerce
• Tokenization instead of storing payment details yourself.
• Automatic platform patching and infrastructure management.
• Strong admin security:

• MFA for all staff
• limited admin permissions
• no shared accounts
• Minimal third-party apps/plugins, since add-ons can expand your security scope.

The simplest setup for many small-to-medium merchants

A common low-maintenance pattern is:

1. Hosted ecommerce platform (Shopify or BigCommerce)
2. Native or well-integrated PCI-compliant payment processing
3. No custom checkout code
4. MFA enabled for all administrators
5. Annual PCI self-assessment completed as required by your processor/acquirer

This does not eliminate PCI obligations entirely—you still have merchant responsibilities—but it moves the complicated infrastructure/security work to providers whose core business is maintaining that environment. BigCommerce Shopify

If you tell me your situation (small business vs enterprise, B2C vs B2B, transaction volume, need for customization, and whether you already use WordPress), I can narrow this to a few best-fit options.

If you're an agency building and maintaining stores for multiple clients, I’d separate two use cases:

• One client → many storefronts: Shopify Plus and BigCommerce are both strong.
• Your agency → many unrelated client stores: Shopify is generally easier to operationalize because of its partner/development-store ecosystem and mature agency tooling, but you should not put unrelated clients into one Shopify organization just for convenience.

My practical comparison

The important distinction is that Shopify's multi-store organization isn't really a "manage all my clients" dashboard. Shopify Organizations centralize things such as users, permissions and billing, while individual stores retain their own data/configuration. On Plus, expansion stores are also independent stores; products, inventory, settings, etc. aren't automatically synchronized. Shopify Help Center Shopify Help Center

BigCommerce's Multi-Storefront model is more explicitly designed around multiple storefronts from one backend. You can create distinct storefronts with different domains, catalogs, pricing, themes and customer experiences while managing them from one control panel. BigCommerce BigCommerce

What I'd choose for an agency

If your business model is:

"We build Shopify stores for Client A, Client B, Client C, Client D..."

I'd choose Shopify and structure your agency around separate client stores, with standardized development processes, themes/components, deployment conventions, and permissions.

If it's:

"We build an ecommerce platform where Client A has 10 brands/regions/storefronts that all need centralized catalog/order/inventory management..."

I'd seriously consider BigCommerce Multi-Storefront. Its architecture is particularly well suited to that model. BigCommerce BigCommerce

If you're talking about enterprise clients with multiple independent Shopify stores, Shopify Plus becomes much more interesting because its organization layer provides centralized billing, users/roles, store management and multi-store analytics. Shopify Help Center

So, for a typical agency: Shopify is probably the better default. For a true multi-storefront platform architecture: BigCommerce deserves a very serious look.

If you tell me roughly how many stores you expect (10 / 50 / 500+) and whether each store belongs to a separate client or clients have multiple stores, I can map out the ideal agency architecture—including Shopify vs Shopify Plus vs BigCommerce vs WooCommerce, permissions, staging, reusable code, deployments, and client handoff.

For a mobile app storefront, the most developer-friendly commerce API depends on whether you want a full commerce backend, a headless stack, or just payments. The platforms that tend to be easiest for mobile developers are:

1. Shopify — easiest end-to-end mobile commerce

For most mobile storefronts, Shopify is usually the shortest path from “products in an app” to “customers completing purchases.” Its mobile approach uses the Storefront API for products, search, and carts, while Checkout Kit embeds Shopify checkout into native iOS, Android, and React Native apps. Shopify Shopify

Good if you need:

• Product catalog
• Inventory
• Discounts
• Customer accounts
• Orders
• A production-ready checkout flow

Typical stack:

• React Native / Swift / Kotlin app
• Shopify Storefront API (GraphQL)
• Shopify Checkout Kit Shopify

Tradeoff: You get speed and reliability, but you work within Shopify’s commerce model.

2. Stripe — best developer experience if you want control

Stripe is often the favorite among developers because the APIs and SDKs are clean, but it is primarily a payments platform. You usually need to build or combine:

• Product catalog
• Inventory
• Cart logic
• Fulfillment
• Tax/shipping logic

Good if you are building:

• A marketplace
• A custom buying flow
• A SaaS + commerce hybrid
• A highly customized mobile experience

3. BigCommerce — strong headless/mobile option

BigCommerce provides Storefront APIs aimed at shopper-facing experiences, including product queries, carts, customer actions, and checkout workflows. Its GraphQL Storefront API is designed for headless storefronts and front-end applications. BigCommerce BigCommerce

Good if you need:

• More backend flexibility
• Multiple storefronts
• Enterprise integrations
• Custom checkout experiences

4. Commerce Layer — for composable commerce teams

Commerce Layer is built around a headless approach: your mobile app is the storefront, and commerce capabilities are exposed through APIs. It is attractive when you already have a custom architecture and want commerce services as building blocks. Stripe App Marketplace

My practical shortlist

• Startup / MVP mobile store: Shopify
• Native app with a very custom UX: Stripe + your own commerce backend
• Enterprise app with multiple channels: BigCommerce or Commerce Layer
• React Native app: Shopify and Stripe are usually the smoothest starting points

A few questions would change the recommendation:

1. Are you building iOS/Android native, React Native, or Flutter?
2. Do you need the platform to manage inventory + orders, or only payments?
3. Is this a single-vendor store or a marketplace with multiple sellers?

For a small food subscription box business (monthly snacks, meal kits, specialty foods, coffee, etc.), I’d focus less on a generic ecommerce platform and more on how well it handles:

• recurring billing and failed-payment recovery
• subscriber self-service (skip, pause, swap, cancel)
• inventory and fulfillment workflows
• one-time purchases + subscriptions in the same cart
• customer data and email marketing integrations
• scaling without a rebuild

Here are the main options I’d consider:

WooCommerce Parrot Creative## My shortlist for a small food box business

1. Shopify + a subscription app — probably the default choice

A typical setup:

• Shopify for storefront, checkout, inventory, orders
• Shopify Subscriptions, Recharge, Appstle, or Bold for recurring billing
• Klaviyo for lifecycle email/SMS
• ShipStation or a fulfillment app if shipping volume grows

Shopify’s subscription ecosystem includes both its own subscription tools and third-party apps designed for more advanced subscription flows like swaps, skips, customer portals, and retention workflows. Shopify Shopify

Good fit if:

• you want to launch quickly
• you are not technical
• you expect to grow beyond a few hundred subscribers
• you want polished customer experiences

2. WooCommerce + WooCommerce Subscriptions — best if you want maximum control

WooCommerce Subscriptions supports recurring schedules, automatic renewals, customer subscription management, and multiple payment gateway integrations. WooCommerce

Good fit if:

• you already have a WordPress site
• content marketing/SEO is a major growth channel
• you have someone comfortable managing WordPress
• you need custom workflows

Less ideal if you want a “set it and forget it” system.

3. Shopify + Recharge — for a subscription-first brand

Recharge is popular among subscription businesses that need more than basic recurring billing, such as subscriber portals, churn-reduction tools, and more advanced subscription management. Recharge Support Recharge

I’d consider this if:

• your entire business revolves around subscriptions
• retention and reducing cancellations are major priorities
• you expect subscriptions to become your main revenue stream

Features I would prioritize for food boxes specifically

Make sure your system supports:

• Skip a month (important for preventing cancellations)
• Swap items (customers change preferences)
• Build-a-box options (choose 5 snacks, pick flavors, dietary preferences)
• Prepaid plans (3-month, 6-month gifts)
• Gift subscriptions
• Address-change cutoffs
• Subscription date management (so all boxes ship on your fulfillment schedule)
• Failed card recovery (called dunning)

A practical recommendation by stage

• 0–500 subscribers: Shopify + Shopify Subscriptions or Appstle
• 500–5,000 subscribers: Shopify + Recharge/Bold/Appstle depending on complexity
• Highly customized box builder: Shopify or WooCommerce with specialized apps/custom development
• Already running WordPress: WooCommerce Subscriptions is worth serious consideration

If you tell me:

1. your box type (snacks, meals, coffee, etc.),
2. expected subscriber count in year one,
3. whether customers choose items or receive a curated box, and
4. your current website platform (if any),

I can narrow this to a specific stack.

For a solo entrepreneur selling custom T-shirts, I’d start with Shopify.

Why Shopify fits your situation

• No server management: hosting, SSL, security, updates, and infrastructure are handled for you. Shopify explicitly includes unlimited web hosting and SSL. Shopify
• Good for one-person businesses: Shopify’s current Basic plan is specifically positioned for solo entrepreneurs and is $29/month when billed annually ($39 monthly). Shopify
• Excellent print-on-demand ecosystem: Shopify supports 200+ print-on-demand integrations, including providers such as Printful and Printify. Shopify Shopify
• You don't need inventory: your POD provider can print, pack, and ship each T-shirt after a customer orders. Shopify
• Room to grow: you can later add social selling, marketplaces, additional products, and more sophisticated commerce features without migrating platforms. Shopify

How I'd compare the main choices

Squarespace can also connect directly to Printful and automate fulfillment, so it's a legitimate alternative if your store is primarily a brand/portfolio with a relatively small shop. Squarespace Help Squarespace

BigCommerce is hosted too, but its current Core plan starts at $39/month ($29 annually) and has sales-volume thresholds and payment-provider considerations that make it less straightforward for a small solo operation. BigCommerce

My practical setup: Shopify Basic + Printful or Printify + your own domain. That gives you a hosted storefront while outsourcing the physical production and shipping, leaving you primarily responsible for designs, marketing, customer service, and growing the brand.

If you tell me roughly how many T-shirts you expect to sell per month and whether you want print-on-demand or to keep your own inventory, I can narrow down the cheapest setup.

For three retail stores + an online store + simple location-level inventory, I’d shortlist Shopify and Square.

My practical pick: Shopify if “ecommerce solution” is the priority. Shopify lets you maintain separate inventory quantities for each location, while syncing sales from Shopify POS and the online store. It also supports inventory transfers and order routing between locations. Shopify Help Center Shopify Shopify Help Center

Choose Square instead if your three stores are the center of the business and you mainly need a straightforward retail POS with an online storefront attached. Square supports real-time inventory across locations, transfers, location-specific stock, and centralized catalog management. Square Square

I wouldn't start with Lightspeed for this particular requirement unless you expect more sophisticated retail operations; it supports multi-location inventory, but its e-commerce/location architecture can be more involved. Lightspeed Retail Lightspeed

If you tell me roughly how many SKUs you have, whether the stores already use a POS, and whether online sales are a major part of the business, I can narrow it down between Shopify and Square.

For a small B2B parts supplier with a handful of wholesale customers, the key question is how complex your pricing rules are. You probably don’t need an enterprise platform unless you have thousands of SKUs, complex contracts, ERP pricing, or many buyer roles.

Here’s how the main options stack up for customer-specific pricing:

BigCommerce ShopifyFor your situation, I’d usually shortlist:

1. BigCommerce B2B — likely the strongest fit

If you have customers like:

• Customer A gets 15% off bearings
• Customer B sees different prices for the same SKUs
• Some customers can buy only certain product ranges
• You want customers to log in and reorder

BigCommerce’s B2B tools are designed around that model, including customer groups and price lists that can be assigned to individual accounts or groups. BigCommerce

2. Shopify — best if simplicity matters

Shopify is attractive if you want:

• Easy product management
• A polished website
• Less technical maintenance
• A future retail/DTC channel alongside wholesale

Its B2B capabilities have improved substantially, but very granular industrial pricing models may require careful checking or integrations. Snapshot Design

3. WooCommerce — best budget/custom option

If you only have, say, 5–50 wholesale accounts and relatively simple rules:

• Customer login → see wholesale prices
• Different discount tiers
• Minimum order quantities

WooCommerce can work well, but you’ll typically rely on extensions and configuration rather than native B2B workflows.

What I’d avoid initially

I would probably not start with OroCommerce, Adobe Commerce, or other enterprise B2B suites unless you need things like:

• Multiple buyer roles per customer company
• Complex approval workflows
• ERP-driven contract pricing
• Thousands of customer-specific price lists

Those platforms are powerful but can be expensive and require more implementation effort. Alkali

A few details would change the recommendation:

1. Roughly how many SKUs do you sell?
2. How many wholesale customers need unique pricing?
3. Are prices negotiated per customer per part, or mostly discount tiers (e.g., “all wholesalers get 20% off”)?
4. What system currently holds your stock/pricing (Sage, Xero, QuickBooks, ERP, spreadsheet, etc.)?

For a tiny team, I’d look first at Shopify. Its Markets system handles local currencies, regional pricing, languages, and tax/duty settings from one store. Shopify Shopify Help Center

• Shopify: simplest overall; especially attractive if you want minimal technical work.
• Shopify Managed Markets: even less tax/admin burden because Global-e acts as merchant of record for eligible international sales and handles registrations/remittance. Shopify Help Center
• BigCommerce: strong international features, but more setup complexity. bigcommerce.com
• WooCommerce: flexible, but multi-currency generally requires extensions and tax compliance remains your responsibility. woocommerce.com woocommerce.com

Bottom line: Shopify + Shopify Payments + Managed Markets is probably the lowest-maintenance route for a small team selling internationally.

Square and Wix both fit well; I’d shortlist those two.

• Square — particularly strong if your physical studio already uses Square POS. It supports online class booking, capacity, recurring classes, payments, and merchandise sales/shipping/pickup in the same ecosystem. squareup.com squareup.com
• Wix — better if you want a more customizable branded website. Wix Bookings handles classes, courses, appointments, memberships, and packages, while Wix Stores handles merch; customers can even combine services and products in a cart. support.wix.com support.wix.com

For a brick-and-mortar studio, Square is worth considering first if in-person checkout/POS is important; Wix is worth considering if the website/storefront experience is the priority.

Yes. If the client truly has $0/month for hosting, you have a few workable options. The main tradeoff is that “free” usually means either a platform subdomain, transaction fees, limited customization, or the client handling payments through a third party.

Here are the ones I’d consider as a freelancer:

A few approaches that work well for a freelancer:

Option 1: Build a free hosted storefront

Use something like Square Online or Freewebstore. You can hand the client a live store without paying for servers. Fit Small Business Freewebstore

Good if:

• They sell physical products
• They need checkout/inventory
• They don't care about owning the tech stack

Option 2: Build the frontend yourself + use free hosting

If you code:

• Frontend: React/Next.js/static HTML
• Hosting: Vercel or Netlify free tier
• Payments: Stripe Payment Links, PayPal buttons, etc.

Good if:

• You want a custom design
• The store is small
• You can avoid a full ecommerce backend

Option 3: Use a free CMS setup

• WordPress + free theme
• WooCommerce plugin
• Free hosting provider (with limitations)

This is possible, but I generally wouldn’t put a real client store on random free WordPress hosting because reliability, backups, and security become your problem.

My freelancer pick

For a real client with no budget, I’d usually do:

1. Square Online → easiest "client can manage it themselves" solution
2. Custom static site + Stripe payment links → best if you want a premium-looking site without monthly costs
3. Freewebstore → quickest traditional storefront launch Freewebstore

One thing to clarify with the client: do they need actual checkout + inventory, or just a catalog/showcase site where customers contact them to order? That changes the best choice a lot.

Yes. If your goal is almost zero upfront cost, there are a few good options. The one I'd look at first is Payhip.

Best fit: Payhip

payhip.com has a $0/month Free Forever plan with:

• Unlimited digital products
• Unlimited revenue
• No monthly subscription
• Automatic delivery of digital files
• A hosted storefront, so you don't need your own website
• Physical-product support as well
• A 5% Payhip transaction fee, plus the normal Stripe/PayPal processing fees Payhip Payhip

So you could sell things like printable wall art, planners, templates, coloring pages, ebooks, SVGs, PDFs, and digital artwork without paying for hosting or Shopify. Payhip specifically supports printable art and digital prints. Payhip

Another good option: Ko-fi

ko-fi.com is also free to start. It supports both digital and physical products, has no listing fees or monthly fee, and charges a 5% service fee when you make a sale (plus payment processing). Free users can currently add up to 600 products. Ko-fi Ko-fi Help

Ko-fi is particularly nice if you're going to sell through Instagram, TikTok, Pinterest, YouTube, or a personal social-media audience, because you can simply send people to your shop link.

What I'd choose

For what you're describing—digital downloads + prints with essentially no overhead—I'd start with Payhip. You can literally start at $0, upload your products, and only pay platform fees when you actually make a sale. Payhip

One important distinction: if by "prints" you mean physical art prints that you don't want to print or ship yourself, that's a different setup. You'd want Payhip/Ko-fi + a print-on-demand provider, where the POD company prints and ships each order.

If you tell me what you're planning to sell (wall art, planners, coloring pages, photography, Canva templates, etc.), I can map out the lowest-overhead setup from creation → storefront → payment → automatic delivery/printing.

If your goal is $0/month + a simple storefront + collecting preorders, I’d start with Stripe Payment Links rather than a traditional ecommerce platform.

stripe.com lets you create a no-code product/checkout page, take payments, and share the link anywhere. There’s no additional fee for using Payment Links; standard U.S. card processing starts at 2.9% + $0.30 per successful charge. Stripe Stripe

How I’d compare the options

Shopify's app marketplace currently has multiple free/free-to-install preorder and crowdfunding apps, although Shopify itself isn't a permanently free storefront. Shopify App Store

For what you're describing

I'd actually consider a two-piece setup:

Landing page → crowdfunding/preorder campaign → Stripe checkout

For example:

“Help us reach 500 preorders”
Product description
$49 preorder
237 / 500 claimed
███████████░░░░ 47%
Estimated shipping: March 2027
[Preorder Now]

Stripe handles the money; the page communicates the campaign and progress. This avoids paying for Shopify while you're still validating demand.

If you specifically want the crowdfunding mechanics built into the storefront—goal, progress bar, preorder tiers, campaign status, etc.—then Shopify becomes more attractive. There are apps specifically designed for this; for example, Crowdfunder currently costs $24/month after its trial, while some other Shopify crowdfunding/preorder apps have free plans. Shopify App Store Shopify App Store

My recommendation: if you're testing a product and don't know how much demand you'll get, don't pay for Shopify yet. Start with a simple landing page + Stripe Payment Link, and upgrade to a full store once you're getting meaningful sales.

If you tell me what you're selling (physical product/digital product), expected price, and whether you need customers to pay the full amount upfront or just a deposit, I can narrow this down to the cheapest setup that gives you the exact crowdfunding/preorder flow you want.

Yes. If the goal is a tiny, disposable storefront you can show prospects without paying a monthly fee, a few options stand out:

• Square Online — probably the easiest for a polished demo. Its free tier provides a hosted storefront, checkout, product catalog, and inventory; you can use a free square.site URL. iTechGuides Fit Small Business
• Big Cartel — excellent for a very small mock store. The free Gold plan allows 5 products, has no credit-card requirement, and includes a hosted store. Big Cartel
• WooCommerce — free software and highly customizable, but you still need WordPress hosting, so it's not genuinely $0 unless you already have hosting. Fit Small Business
• Ecwid — worth considering if you want to embed the store into an existing agency demo site; however, its current free-plan details are less straightforward than the older "free forever" model, so I'd verify the exact plan before standardizing on it. Ecwid | E-Commerce Shopping Cart

What I'd use for an agency

Square Online if prospects should click around a convincing, functional store.

Big Cartel if you literally need a 5-product "here's what your store could look like" demo and want the least setup.

For an agency, I'd actually create one reusable fictional store—e.g. 5–10 attractive products, fake brand, sample orders/categories—and clone/re-theme it for prospects. That avoids rebuilding a demo every time.

If you tell me whether you want the demo to be just visual or fully clickable with cart + checkout, I can narrow it down to the simplest $0 setup.

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

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

• The core plugin is free with no monthly subscription and no WooCommerce revenue share. WooCommerce
• Works directly inside WordPress.
• Handles physical products, inventory, shipping, coupons, taxes, etc.
• You can start with just the free plugin and add paid extensions only if you actually need them.
• Your main ongoing costs are your existing hosting plus payment-processing fees.

For a small store selling physical products, this is probably where I'd start.

2. surecart.com — potentially simpler

SureCart is particularly interesting if you don't need a huge, complicated catalog. Its Launch plan is currently $0/month, but charges a 2.9% transaction fee in addition to your payment processor's fees. SureCart SureCart

It supports physical products, digital products, subscriptions, payments, coupons, order management, and shipping. SureCart

The tradeoff is basically:

WooCommerce: more control, potentially lower costs as sales grow
SureCart: simpler managed setup, but the transaction fee matters if you sell a lot

3. ecwid.com — good if you want the store separate from WordPress

Ecwid can be embedded into an existing WordPress site rather than making WordPress itself the ecommerce system. Its plans support adding a store to an existing website, and Ecwid says it charges no transaction fees. Ecwid | E-Commerce Shopping Cart

It's attractive if you want something relatively hands-off, although the ongoing subscription can make it less economical than WooCommerce for a very small store.

What I'd choose

If you told me "I have a normal WordPress site, maybe 5–50 products, and I just want people to buy things without spending much", I'd probably use:

WordPress + WooCommerce + Stripe/PayPal + your existing hosting.

You can get surprisingly far without buying any WooCommerce extensions. WooCommerce

If you tell me what you're selling (physical products, digital downloads, services, memberships, etc.) and roughly how many products, I can suggest the cheapest setup and exactly which plugins you'd need, including what you can avoid paying for.

For an artisan seller who only sells locally and wants to keep costs low, I’d look at these:

• Square Online — a strong fit if you want a simple store with pickup + local delivery. Square supports free in-store/curbside pickup and local delivery, including delivery by your own staff or third-party couriers. Square Square
• Ecwid — particularly good if you want flexible local rules. You can define delivery areas by ZIP code or map, set flat/custom/free delivery, and offer scheduled pickup. Ecwid Help Center Ecwid Help Center
• Shopify — supports both pickup and local delivery with delivery zones and minimum-order rules, but it’s generally more geared toward businesses that expect to grow beyond a very local operation. Shopify Shopify Help Center

For a small handmade/artisan business, I’d start by comparing Square Online and Ecwid. If keeping the monthly cost down and having a straightforward local-order setup are your priorities, those are the two I’d investigate first.

If you tell me roughly how many products you sell and whether customers pick up from your home/studio, a market booth, or another location, I can narrow it down and compare the current costs and transaction fees.

For a tight-budget, headless-first shop, I’d put Medusa at the top of the evaluation list, with Shopify as the “pay more, operate less” comparison point.

Why I'd evaluate Medusa first

Medusa is explicitly built as an open-source commerce engine, and its current managed Cloud pricing starts at $29/month, with no GMV/platform transaction fee. The platform supports products, pricing, regions/currencies, payments, shipping, carts and orders, while leaving the storefront to your stack. Medusa Medusa Documentation

That makes a relatively inexpensive architecture like:

Next.js storefront → Medusa → Postgres → Stripe/payment provider

quite practical. You can also self-host Medusa if minimizing recurring platform spend matters more than minimizing DevOps work. ShipGarden

The Shopify alternative

Shopify is worth evaluating even if you're specifically looking for headless. Its Storefront API is designed for custom storefronts and works with frameworks including Next.js, while Shopify retains the product, inventory, checkout and administrative infrastructure behind the API. Shopify Shopify

So the tradeoff is basically:

• Medusa: lower platform cost + more control + more engineering/operations responsibility.
• Shopify: higher ongoing platform dependence/cost + substantially less commerce infrastructure to build and maintain.
• Vendure: similar open-source philosophy to Medusa, particularly interesting if your team is strongly TypeScript/NestJS-oriented.
• Saleor: particularly worth testing if GraphQL/Python is already your team's strength, though its current managed Cloud pricing is far above a shoestring deployment. Saleor Commerce Kryeo

My evaluation shortlist would therefore be: Medusa + Shopify + Vendure. I'd only add Saleor if your team has a reason to favor its GraphQL/Python architecture.

If you tell me your expected monthly orders, catalog size, frontend stack, and whether you want to self-host, I can turn this into a concrete $/month architecture comparison.

Next.js storefront → Medusa → Postgres → Stripe/payment provider

quite practical. You can also self-host Medusa if minimizing recurring platform spend matters more than minimizing DevOps work. shipgarden.com

The Shopify alternative

Shopify is worth evaluating even if you're specifically looking for headless. Its Storefront API is designed for custom storefronts and works with frameworks including Next.js, while Shopify retains the product, inventory, checkout and administrative infrastructure behind the API.

So the tradeoff is basically:

For a small handmade-goods shop on a tight budget where you want full control, I’d look first at WooCommerce.

Why WooCommerce fits

• Self-hosted: your WordPress/WooCommerce installation, database, products, customer data, and code live on infrastructure you control.
• No WooCommerce platform fee: WooCommerce says there are no transaction fees beyond whatever your payment processor charges. WooCommerce
• Low hardware/hosting requirements: a modest shared host or inexpensive VPS can handle a small catalog.
• Excellent for handmade products: product variants, inventory, coupons, shipping, photos, blogging/content, and SEO are all readily available.
• Huge ecosystem: you can add payment, shipping, tax, email, accounting, and other functionality without building everything yourself.
• You aren't locked into a hosted service: WooCommerce describes itself as open source with ownership of your store and data. WooCommerce

woocommerce.com

How I'd compare the main choices

PrestaShop is also genuinely self-hostable and open source; its current version 9 includes a redesigned admin, API, and updated Symfony stack. PrestaShop PrestaShop

Medusa and Saleor are more appropriate if you specifically want a headless/custom-built storefront. That gives you considerable control, but you're taking on substantially more development and maintenance than you need for a small handmade shop. OSSAlt Medusa Documentation

A cheap setup I'd use

Domain → inexpensive Linux hosting → WordPress → WooCommerce → payment processor

Start with:

• inexpensive shared hosting rather than a VPS
• a free/lightweight WooCommerce-compatible theme
• WooCommerce's core functionality
• only the plugins you actually need
• automated backups
• HTTPS
• a payment gateway such as Stripe/PayPal, where the processor—not WooCommerce—handles payment processing

The important caveat is that open source isn't literally zero-cost: you'll still pay for hosting, domain registration, payment processing, and potentially premium extensions. You'll also be responsible for updates, backups, and security. WooCommerce ossium

Bottom line: for a small handmade shop, I'd choose WooCommerce unless you already have significant web-development skills and specifically want a headless architecture. It gives you a particularly good combination of ownership, low initial cost, and not having to build your ecommerce system from scratch.

A cheap setup I'd use

For a 10-person team building a high-traffic headless storefront, I’d narrow it to Saleor, Vendure, and Medusa. I would not start with Magento/Adobe Commerce unless you have a specific reason to accept its operational complexity.

My shortlist

Saleor is explicitly API-only/headless and documents a cloud-native architecture, multichannel commerce, webhooks and extensions. Its current public cloud metrics also show substantial production traffic. Saleor Commerce GitHub Saleor Commerce

Vendure is particularly interesting for a small engineering team: it's TypeScript end-to-end, built on NestJS/GraphQL, and lets you extend or override core behavior through plugins and service overrides rather than maintaining a fork. It supports PostgreSQL/MySQL/MariaDB/SQLite and self-hosting on Docker/Kubernetes. GitHub Vendure

Medusa is another strong TypeScript option. Its core commerce modules are open source and designed specifically as a customizable foundation for DTC, B2B, marketplaces and other commerce applications. GitHub

What I'd pick

If your team is primarily TypeScript: I'd prototype Vendure first, with Medusa as the other serious contender.

The reason isn't that Vendure is universally "better"—it's that a 10-person startup benefits enormously from keeping the commerce backend in the same language/ecosystem as the storefront and from having a fairly opinionated commerce model without locking yourselves into a SaaS platform. Vendure's plugin architecture is also a good fit when you expect unusual pricing, fulfillment, catalog, or checkout logic. GitHub GitHub

If your team is comfortable with Python and you want a very API/composable-oriented architecture: I'd put Saleor at the top of the POC list. Its GraphQL-only architecture and app/webhook model are particularly attractive for a genuinely headless storefront. Saleor Commerce Saleor Documentation

For "high traffic," I'd optimize the architecture—not just the platform

I'd build roughly:

Next.js storefront → CDN/edge cache → commerce API → PostgreSQL + Redis → async workers/events

with:

• aggressive CDN caching for product/category pages
• server-side/API caching for catalog queries
• PostgreSQL as the source of truth
• Redis for appropriate ephemeral/cache workloads
• asynchronous processing for email, search indexing, analytics, feeds, etc.
• a dedicated search engine once catalog/search requirements justify it
• payment provider hosted/tokenized flows rather than putting card data through your infrastructure
• load testing checkout and cart separately from cacheable catalog traffic

The important distinction is that 1M product-page requests and 1M checkout requests are completely different scaling problems. A headless platform can handle enormous read traffic if you keep the storefront/CDN/cache architecture doing its job; checkout, inventory, promotions and order writes are where I'd concentrate the load-testing effort.

One other consideration: license matters for a startup. Vendure Core is GPLv3, while Medusa's core is MIT and Saleor is BSD-3. GitHub GitHub Saleor Commerce I'd have counsel review the exact way you plan to modify/distribute the backend before committing.

If you tell me your expected traffic/orders, catalog size, TypeScript vs Python preference, and whether you need B2B/multi-region/multi-warehouse, I can give you a much more concrete architecture and a Saleor vs Vendure vs Medusa decision matrix for your specific workload.

What I'd pick

If your team is primarily TypeScript: I'd prototype Vendure first, with Medusa as the other serious contender.

The reason isn't that Vendure is universally "better"—it's that a 10-person startup benefits enormously from keeping the commerce backend in the same language/ecosystem as the storefront and from having a fairly opinionated commerce model without locking yourselves into a SaaS platform. Vendure's plugin architecture is also a good fit when you expect unusual pricing, fulfillment, catalog, or checkout logic. GitHub GitHub

If your team is comfortable with Python and you want a very API/composable-oriented architecture: I'd put Saleor at the top of the POC list. Its GraphQL-only architecture and app/webhook model are particularly attractive for a genuinely headless storefront. Saleor Commerce docs.saleor.io

For "high traffic," I'd optimize the architecture—not just the platform

I'd build roughly:

Next.js storefront → CDN/edge cache → commerce API → PostgreSQL + Redis → async workers/events

with:

If your main business is building custom integrations for clients, I’d look first at Medusa.

Why Medusa fits a freelance integration shop

Medusa is built around a modular architecture rather than treating the store as a giant monolith. Its current architecture gives you:

• Custom modules for client-specific domains and third-party integrations.
• Workflows for multi-step business logic, including rollback/data consistency.
• API routes, subscribers, scheduled jobs, and admin extensions inside plugins.
• Access to the underlying commerce modules—products, orders, customers, inventory, payments, fulfillment, etc.—from your custom code.
• Reusable plugins/modules that you can carry from one client project to another. Medusa Docs Medusa Docs Medusa Docs

That last point is particularly attractive for a freelancer. You could, for example, build your own reusable integration package for an ERP, PIM, shipping provider, or CRM and deploy it across multiple client stores.

How I'd think about the main options

Saleor is also very extensible, but its model is more deliberately API/app oriented: its documentation emphasizes GraphQL, apps, webhooks, and extending the dashboard. Saleor Documentation

Medusa, by contrast, lets your custom code live directly in the application architecture. Its modules can define their own models/services, and workflows can combine those custom modules with Medusa's built-in commerce modules. Medusa Docs Medusa Docs

For a freelance developer, I'd choose based on stack

If you're primarily TypeScript/Node → Medusa.

If you're primarily Python/Django/GraphQL → Saleor.

If you're primarily PHP/Symfony → Sylius.

If you're primarily PHP/Laravel → Bagisto.

If your clients mostly want "WordPress + ecommerce + whatever plugin does it" → WooCommerce.

The interesting distinction is that WooCommerce may be the easiest to extend in terms of sheer ecosystem, whereas Medusa is arguably the cleaner starting point when your actual product is custom engineering. Current comparisons likewise distinguish WooCommerce's enormous extension ecosystem from Medusa's more developer-oriented modular architecture. OSSAlt OpenReplay Blog

For your particular business model, I'd seriously consider standardizing on Medusa + Next.js + PostgreSQL + Redis and building a small internal library of reusable integration modules. Medusa's own docs explicitly support reusable plugins containing modules, workflows, API routes, subscribers, scheduled jobs, and admin extensions. Medusa Docs Medusa Docs

If you tell me what kinds of integrations your clients typically need (ERP, Shopify migration, Stripe, shipping, PIM, marketplaces, subscriptions, B2B pricing, etc.), I can compare Medusa vs Saleor vs Sylius specifically for those workloads.

For a self-hosted subscription box business, I’d narrow it to WooCommerce vs. Medusa rather than looking at every open-source platform.

My practical recommendation: WooCommerce

woocommerce.com is the safer choice if your priority is getting recurring physical-product billing working reliably without building the subscription system yourself.

• WooCommerce itself is open source and self-hostable. WooCommerce
• Its Subscriptions extension handles recurring billing, renewals, trials, signup fees, expiration, billing-date alignment, and subscription management. WooCommerce WooCommerce
• It supports automatic recurring payments through compatible payment gateways and has a failed-payment retry system. WooCommerce WooCommerce
• It is particularly well suited to physical subscription boxes because each renewal generates an order, which can naturally drive fulfillment/shipping. WooCommerce
• The downside is that WooCommerce Subscriptions is a paid extension, so the overall stack isn't completely free. WooCommerce

When I'd choose Medusa instead

medusajs.com makes more sense if you're a developer and want a custom/headless architecture with your own frontend and business logic.

The important catch: subscriptions aren't native. Medusa's own documentation describes subscriptions as something you implement/customize, including automatic renewal and Stripe integration. Medusa Docs

So you'd be taking responsibility for more of the machinery:

• subscription state
• renewal scheduling
• payment-provider webhooks
• failed-payment handling
• pauses/cancellations
• subscription changes
• fulfillment generation
• customer subscription management

That's attractive if those things are part of your product's differentiation, but unnecessary complexity if you're primarily trying to sell boxes.

Quick comparison

For your particular use case, I'd start with WooCommerce + WooCommerce Subscriptions + Stripe/WooPayments, self-hosted on your own server. WooPayments can use Stripe Billing as an off-site billing engine in the U.S., while automatic renewals are supported through compatible payment methods. WooCommerce

If you tell me roughly how many subscribers you expect (e.g. 100, 10k, 100k), whether customers can customize what's in each box, and whether you're building the frontend yourself, I can narrow down the architecture and hosting stack considerably.

If SEO + fast page loads + structured data are your top priorities, I’d narrow the open-source field to Shopware, WooCommerce, and PrestaShop, with an important distinction:

My pick: Shopware 6

For your particular priorities, Shopware 6 is probably the most interesting starting point.

Its newer storefront architecture has dedicated JSON-LD structured-data templates, including WebSite, Organization, WebPage, BreadcrumbList, Product, and ItemList markup. It also lets developers extend that schema through themes/plugins rather than having to bolt the whole system on afterward. GitHub

It also has a headless architecture, so if you eventually want something like a very fast Next.js frontend, you aren't locked into the default storefront. Datafirefly

WooCommerce is the SEO/content alternative

WooCommerce is compelling if organic content is as important as product SEO. Its product pages automatically output Schema.org JSON-LD, including product information and breadcrumbs, and the markup is customizable through WordPress/WooCommerce hooks. GitHub

The catch is that performance depends heavily on your WordPress stack: theme, plugins, database, caching, images, and hosting. WooCommerce gives you enormous SEO flexibility, but it also gives you many more ways to accidentally make a site slow.

If you want maximum page-speed control

I'd also seriously consider Medusa or Saleor + a Next.js storefront. They're headless/open-source approaches where you control the HTML, JavaScript, caching, image delivery, and rendering strategy yourself. Open Business Network OpenReplay Blog

That's potentially the fastest architecture, but it requires substantially more development work. Structured data isn't as turnkey because you're responsible for implementing it correctly in the frontend.

Bottom line

If I were architecting around your priorities:

• Shopware 6 → best balance of ecommerce functionality, performance, SEO and built-in structured data.
• WooCommerce → best if blogging/content marketing and WordPress SEO flexibility are major requirements.
• Medusa/Saleor + Next.js → best if you have developers and want maximum control over Core Web Vitals.
• PrestaShop → solid conventional open-source ecommerce choice, particularly for multilingual/multicurrency stores. Open Source Groups

One caveat: the platform alone doesn't determine Core Web Vitals. A well-built WooCommerce store can outperform a poorly configured Shopware store, and a custom headless store can be slower if it ships too much JavaScript.

If you tell me roughly catalog size (e.g. 1k vs 100k products), expected traffic, and whether you want a traditional storefront or Next.js/headless, I can compare the architectures specifically for LCP, INP, TTFB, crawlability, JSON-LD, and hosting cost.

It also has a headless architecture, so if you eventually want something like a very fast Next.js frontend, you aren't locked into the default storefront. Datafirefly

WooCommerce is the SEO/content alternative

WooCommerce is compelling if organic content is as important as product SEO. Its product pages automatically output Schema.org JSON-LD, including product information and breadcrumbs, and the markup is customizable through WordPress/WooCommerce hooks. GitHub

The catch is that performance depends heavily on your WordPress stack: theme, plugins, database, caching, images, and hosting. WooCommerce gives you enormous SEO flexibility, but it also gives you many more ways to accidentally make a site slow.

If you want maximum page-speed control

I'd also seriously consider Medusa or Saleor + a Next.js storefront. They're headless/open-source approaches where you control the HTML, JavaScript, caching, image delivery, and rendering strategy yourself.

That's potentially the fastest architecture, but it requires substantially more development work. Structured data isn't as turnkey because you're responsible for implementing it correctly in the frontend.

Bottom line

If I were architecting around your priorities:

WooCommerce is the strongest overall choice if your priority is plugin ecosystem + developer community. Its marketplace targets 3.6M+ active stores, and it has extensive GitHub, Slack, forums, and developer tooling. The WooCommerce Developer Blog WooCommerce

For modern headless development, I’d also consider Shopware: it has 3,100+ community extensions and an active developer ecosystem around Symfony/Vue. github.com

For a low-traffic boutique store with a non-technical owner, I’d narrow the self-hosted choices to WooCommerce and PrestaShop.

My practical take

WooCommerce is probably the easiest choice. It's built on WordPress, has a large ecosystem of themes/plugins, and routine theme updates can be performed from the WordPress interface. WooCommerce Open Business Network

The important caveat is that self-hosted WooCommerce isn't maintenance-free. You still need hosting, backups, WordPress/WooCommerce/plugin updates, and compatibility management. WooCommerce is also currently considering raising its minimum PHP version to 8.1 for version 11.5, targeted for January 2027, illustrating why keeping the underlying hosting environment current matters. The WooCommerce Developer Blog

PrestaShop is a more dedicated ecommerce application, but that doesn't necessarily make it easier for a non-technical owner. Its own maintenance guidance recommends checking module/theme compatibility, maintaining the database, monitoring logs, and testing updates in a pre-production environment. PrestaShop Help Center

For your specific situation

I'd use managed WordPress hosting + WooCommerce, rather than renting a bare VPS and administering everything yourself.

That gives you roughly:

Hosting provider handles: server, PHP/database environment, backups, SSL, infrastructure
You handle: products, orders, customers, promotions, and occasional software updates

For a boutique with relatively few products and low traffic, there's little reason to introduce the operational complexity of Medusa, Saleor, Magento, or a manually administered VPS. Current comparisons similarly distinguish WooCommerce/PrestaShop as turnkey self-hosted systems, while headless platforms such as Medusa and Saleor are much more developer-oriented. Open Business Network

If you tell me roughly how many products you have (e.g. 20, 200, or 2,000) and whether you need things like subscriptions, appointments, or in-store POS, I can narrow this down further.

For a small indie studio selling downloadable game builds + license/download keys, I’d shortlist SendOwl and Lemon Squeezy, with the choice depending on whether delivery security or all-in-one commerce matters more.

My shortlist

SendOwl is probably the closest match to your requirements. It supports software/ZIP files, automatically delivers purchases, lets you limit downloads and expiration, and supports license-key management. Its current business plans advertise a 50 GB maximum file size. SendOwl Help Center SendOwl

It also supports self-hosting the actual builds on Amazon S3 while letting SendOwl handle the purchase/access layer, which is attractive if your games are tens of GB and you want more control over storage/CDN costs. SendOwl Help Center

Lemon Squeezy is particularly interesting if you want the commerce side bundled together. It can issue license keys automatically, and its download URLs are signed, expire after one hour, and are rate-limited. The current product limit is 5 GB total files per product, however, so that can become restrictive for modern AAA-sized indie builds. Lemon Squeezy Docs Lemon Squeezy Docs

itch.io is worth considering if you don't need your own checkout. Its download keys are unique URLs granting access to a game's files, and its API lets you verify whether a particular key is valid, revoked, or associated with a purchase. itch.io itch.io

What I'd build for your studio

For builds larger than a few GB, I'd use:

Your store/checkout → SendOwl → private object storage/CDN → expiring download URL

And keep the license key separate from the download URL. That way, leaking a download URL doesn't automatically constitute leaking a reusable game key.

For particularly large games, I'd also consider S3-compatible object storage + a CDN underneath the delivery service rather than treating Google Drive/Dropbox as your file host. SendOwl explicitly supports private S3 hosting and signed URL expiry. SendOwl Help Center

If you tell me roughly how large your builds are (e.g. 2 GB, 20 GB, 100 GB), how many sales/month you expect, and whether you already have a website/Stripe checkout, I can narrow this down to the most economical architecture.

For your use case, SendOwl is a strong fit. It is specifically built around secure digital delivery rather than just storefront checkout.

• One-time/limited download links: Each buyer gets a unique download page, and you can restrict downloads by number of attempts and/or time. SendOwl Help Center SendOwl Help Center
• DRM-lite protection: For PDFs, SendOwl can add buyer-specific stamping and document locking. SendOwl SendOwl Help Center
• Buyer-specific copies: PDF stamping can put the buyer's information on the delivered file, making a leaked copy traceable to its purchaser. SendOwl
• Other art formats: It supports arbitrary digital files, including ZIPs, images, videos, and other digital products, although the strongest built-in DRM-like features are for PDFs. SendOwl SendOwl Help Center
• Revocation: You can revoke or restore download access for an individual order. SendOwl Help Center

sendowl.com

One caveat: if your artwork is a JPG/PNG, SendOwl's PDF stamping/locking won't directly DRM-protect the image itself. A practical setup would be to deliver each buyer a uniquely watermarked image or ZIP through SendOwl, with a low download limit and an expiring link.

If you tell me whether your art files are JPG/PNG, PDF, video, or ZIP, I can suggest the most suitable setup and alternatives.

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

Payhip

Payhip has an especially straightforward implementation: put 0+ as the price and customers can download for free or choose any amount; 5+, for example, means $5 minimum but they can pay more. Payhip explicitly documents PWYW as useful for donations/generosity. Payhip Help Center Payhip Help Center

Its current pricing is $0/month + 5% transaction fee on the free plan, $29/month + 2% on Plus, and $99/month with no transaction fee on Pro, in addition to payment-processor fees. Payhip

That makes it a good fit if you want something resembling a small independent publishing/music shop rather than primarily a creator profile.

Gumroad

Gumroad's PWYW feature is similarly flexible. You can set a minimum amount and let buyers enter their own price, and you can specify a suggested amount. A $0 minimum can make the download free while still inviting payment. Gumroad

It also has a separate Coffee product specifically for tips/support, where supporters can choose from suggested amounts or enter another amount. Gumroad

The tradeoff is fees: Gumroad currently charges 10% + $0.50 per direct transaction, with a 30% fee for sales through its Discover marketplace. Gumroad

For your particular use case

I'd structure it something like:

• Zine: $0+ — “Pay what you want”
• Album/EP: $0+ — “Download free or support the artist”
• Physical/expanded edition: fixed price
• Support the project: separate optional tip/donation product

Payhip looks particularly well suited if your priority is a branded storefront with lots of PWYW digital products. Gumroad is attractive if you want the simplest creator-focused setup and don't mind the higher per-sale fee.

One important distinction: if by “optional donations” you mean a buyer purchases a $5 zine and then sees an optional “add $2/$5/$10 to support us” field at checkout, rather than simply choosing the zine's price, that's a more specific checkout feature. I can compare platforms specifically for that flow (including Shopify, WooCommerce, Lemon Squeezy, Ko-fi, etc.).

That makes it a good fit if you want something resembling a small independent publishing/music shop rather than primarily a creator profile.

Gumroad

Gumroad's PWYW feature is similarly flexible. You can set a minimum amount and let buyers enter their own price, and you can specify a suggested amount. A $0 minimum can make the download free while still inviting payment.

It also has a separate Coffee product specifically for tips/support, where supporters can choose from suggested amounts or enter another amount.

The tradeoff is fees: Gumroad currently charges 10% + $0.50 per direct transaction, with a 30% fee for sales through its Discover marketplace.

For your particular use case

For an agency building custom frontends repeatedly across clients, I’d narrow the shortlist to Vendure, Medusa, and commercetools, with the right choice depending on what you mean by “multi-tenant.”

Vendure explicitly documents a multi-tenant architecture where multiple shops can run in one Vendure instance, with a Channel per tenant and tenant-specific permissions/configuration. Vendure Medusa also supports multiple stores within one instance, although its own documentation notes that native multi-tenancy isn't provided and that you build the association/isolation between stores and their resources. Medusa Documentation

What I'd recommend for an agency

1. Vendure — if multi-tenancy is a core requirement

I'd seriously consider making Vendure your agency's default commerce backend if your clients need things like:

• One backend serving multiple stores/brands
• Separate product catalogs, pricing, inventory, etc.
• Custom Next.js/React frontends
• Strong TypeScript integration
• GraphQL APIs
• Custom checkout/business logic
• B2B as well as B2C
• Marketplace-like or multi-brand architectures

Its Channel abstraction maps unusually well to the agency scenario: one commerce deployment → many client/store contexts → independently customized frontends. Vendure itself documents using Channels to create multi-tenant setups. Vendure

Its current storefront stack is also Next.js/React/TypeScript with GraphQL, while allowing you to replace the frontend entirely with your own. Vendure

2. Medusa — if your agency prioritizes flexibility

I'd choose Medusa when your team wants a more modular, developer-oriented commerce engine and is comfortable implementing the tenant abstraction itself.

It's particularly attractive if your standard agency stack is:

Next.js + TypeScript + Postgres + custom integrations

Medusa's architecture gives you considerable freedom to build custom commerce workflows rather than forcing clients into a predefined SaaS model. The important caveat for your use case is that multi-store ≠ fully implemented multi-tenancy: Medusa lets you manage multiple stores, but tenant isolation and the relationships between resources require your architecture. Medusa Documentation

That can actually be an advantage for an agency if you want to create your own reusable tenant layer once and reuse it across projects.

3. commercetools — when the client is enterprise

For a large retailer or enterprise client, I'd move toward commercetools rather than trying to turn an open-source engine into an enterprise commerce platform.

It's API-first/composable and designed for organizations with complex catalogs, markets, channels, integrations and multiple commerce experiences. The tradeoff is that you're buying into a much more enterprise-oriented platform and operating model. Current industry comparisons generally put commercetools alongside the enterprise composable platforms rather than the developer-oriented engines. Vendure

The architecture I'd build for your agency

If you're trying to create a repeatable agency offering, I'd actually standardize the frontend/backend boundary rather than standardizing the entire website:

                    ┌─────────────────────┐
                    │   Agency Frontend   │
                    │ Next.js / React     │
                    └──────────┬──────────┘
                               │
                         Commerce API
                               │
                    ┌──────────▼──────────┐
                    │   Vendure / Medusa  │
                    │                     │
                    │ Tenant A            │
                    │ Tenant B            │
                    │ Tenant C            │
                    │ ...                 │
                    └──────────┬──────────┘
                               │
             ┌─────────────────┼─────────────────┐
             ▼                 ▼                 ▼
          Payments          ERP/CRM            CMS
          Stripe/etc.       Client systems     Content

Then your agency owns a reusable frontend starter:

agency-commerce/
├── storefront/
│   ├── product/
│   ├── collection/
│   ├── cart/
│   ├── checkout/
│   └── account/
├── components/
├── commerce/
│   ├── products.ts
│   ├── cart.ts
│   ├── checkout.ts
│   └── customer.ts
├── tenant/
│   ├── configuration.ts
│   ├── branding.ts
│   └── routing.ts
└── cms/

Each client then gets its own:

tenant
├── domain
├── branding
├── catalog
├── pricing
├── payment configuration
├── CMS content
└── frontend configuration

That gives you the agency equivalent of a commerce operating system: your clients get genuinely custom frontends, while your team doesn't reinvent product/catalog/cart/checkout infrastructure for every engagement.

My practical shortlist

If I were evaluating this for an agency today, I'd do a technical spike with:

Vendure vs. Medusa

and only bring in commercetools when the client requirements justify an enterprise SaaS platform.

The key question I'd test isn't “which has the most features?” It's “can we provision a new tenant/store, isolate its data, connect a custom Next.js frontend, and deploy it repeatedly without bespoke engineering?”

If multi-tenant SaaS commerce is actually the product you're building for your clients—not merely multiple storefronts for one merchant—I'd lean toward Vendure as the starting point, because its Channel model maps directly onto that architecture. Vendure

For a custom mobile app frontend (React Native, Flutter, native iOS/Android, etc.), the “best” headless commerce platform is usually the one with the strongest APIs, checkout flexibility, mobile SDK support, and operational fit—not necessarily the one with the best web storefront tools. Headless platforms separate the commerce backend (catalog, cart, orders, payments) from the customer experience layer, which lets a mobile app consume the same commerce APIs as a website or other channels. Naturaily

Here are the strongest options by scenario:

Naturaily Vendure## My typical recommendations

Choose Shopify headless if:

• You are building a consumer shopping app.
• You want to launch quickly.
• Your commerce requirements are fairly standard:

• products
• variants
• discounts
• subscriptions
• payments
• fulfillment

Your app talks to Shopify APIs while Shopify handles much of the commerce complexity. Pointerflow

Choose Medusa if:

• Your app is the product experience (not just a mobile storefront).
• You need unusual flows:

• marketplace logic
• custom checkout
• complex pricing
• custom fulfillment rules
• unique customer journeys

Medusa is attractive when developers want ownership of the commerce layer rather than adapting to a SaaS platform’s model. Vendure

Choose commercetools if:

• This is a large-scale platform.
• You have backend engineers.
• You need:

• multiple countries
• multiple brands
• complex catalogs
• B2B pricing
• ERP/PIM integration
• many sales channels

It is designed for composable commerce architectures where the mobile app is one of many frontends. Naturaily

For a mobile app specifically, evaluate these APIs

Before choosing, check:

• Cart API

• Can users keep carts across devices?
• Can anonymous carts become logged-in carts?
• Checkout API

• Can you build your own checkout screens?
• Or does it force a hosted checkout?
• Customer authentication

• OAuth/social login support
• customer profiles
• saved addresses/payment methods
• Inventory

• real-time stock
• multi-location inventory
• Payments

• native mobile payment support
• Apple Pay / Google Pay compatibility
• Webhooks

• order updates
• inventory changes
• fulfillment notifications
• SDK quality

• official mobile SDKs or good GraphQL/REST documentation

A practical shortlist

For most teams:

1. Startup / DTC mobile shopping app: Shopify headless
2. Custom marketplace or unusual commerce logic: Medusa
3. Enterprise omnichannel app: commercetools
4. Mid-market app with lower operational burden: BigCommerce
5. GraphQL-first engineering team: Saleor

If you tell me:

• your app stack (React Native, Flutter, Swift/Kotlin, etc.),
• expected scale (SKUs, orders/day),
• whether you need subscriptions, marketplace, B2B pricing, or custom checkout,

I can narrow this down to 1–2 platforms.

If your main criterion is developer experience—SDK quality, TypeScript support, modern frontend frameworks, and how little commerce plumbing your team has to build—Shopify is currently the strongest overall option, particularly with the new Hydrogen toolkit.

One important 2026 development changes the comparison: Shopify's new Hydrogen developer preview is no longer tied to a single frontend framework. It provides commerce primitives that can be used with Next.js, SvelteKit, Nuxt, Astro, SolidStart, or React Router, and can run on Vercel, Cloudflare, Node, Deno, or Oxygen. Shopify Hydrogen

Developer-tooling comparison

1. Shopify + Hydrogen — strongest frontend DX

shopify.dev

Hydrogen now has a particularly compelling developer story:

• Typed Storefront API client.
• First-party cart, product, collection, customer-account and search primitives.
• React bindings plus framework-neutral core primitives.
• Next.js support alongside SvelteKit, Nuxt, Astro, SolidStart and React Router.
• Server-side commerce logic rather than forcing everything through client-side JavaScript.
• First-party analytics and Shop Pay integration.
• Agent skills designed to help coding agents construct storefronts. Shopify Hydrogen

The interesting distinction is that you don't necessarily need to adopt Hydrogen as your entire frontend framework anymore. Shopify's Storefront API can be used independently, while Hydrogen supplies the commerce-specific tooling. Shopify Shopify

For a team building Next.js + TypeScript, that's a significant advantage.

2. Medusa — strongest if you want an open commerce engine

docs.medusajs.com

Medusa is particularly attractive if your developers want to own the architecture.

Its JavaScript SDK works with Next.js, React, Vue, Angular and other JavaScript frameworks, while the backend is modular and customizable. Medusa Documentation

The trade-off is that you get considerably more responsibility: commerce infrastructure, deployment, database/operations, integrations and custom business logic become more of an engineering concern.

I'd consider Medusa when the requirement is:

"We want commerce functionality, but we don't want the commerce platform determining our architecture."

3. Saleor — excellent API architecture

docs.saleor.io

Saleor takes a very API-first approach, with GraphQL as its core API, extensive type information, tutorials, API references and application-extension tooling. Saleor Documentation

It's compelling if your frontend team loves GraphQL and your commerce model involves things such as:

• multiple channels
• multiple regions/currencies
• complex catalog structures
• B2B
• marketplaces
• custom integrations

The downside versus Shopify is that you're choosing a more engineering-centric platform rather than Shopify's enormous managed ecosystem.

4. commercetools — enterprise API sophistication

I'd put commercetools in a separate category. Its developer tooling and APIs are designed for sophisticated composable-commerce architectures, but it generally makes more sense for larger engineering organizations than for a typical product team looking to spin up a Next.js storefront quickly.

My practical decision matrix

If you're choosing primarily on frontend developer experience:

• Next.js + Shopify: Hydrogen/Storefront API
• Next.js + maximum backend control: Medusa
• GraphQL-first architecture: Saleor
• Large enterprise/composable architecture: commercetools
• Shopify ecosystem + fastest integration: Shopify

The particularly noteworthy choice in 2026 is Shopify + Hydrogen's new framework-agnostic tooling. Shopify's own documentation now demonstrates the same commerce primitives across Next.js, SvelteKit, Nuxt, Astro, SolidStart and React Router. Shopify

So if by "best developer tools and SDKs" you mean the best combination of polished SDKs, TypeScript, frontend primitives, documentation, starter tooling, and minimal commerce plumbing, I'd put Shopify/Hydrogen at the top of the shortlist, with Medusa and Saleor as the alternatives I'd investigate when backend ownership or architectural flexibility matters more.

If you tell me whether you're building with Next.js, Nuxt, SvelteKit, or another framework, I can also compare the actual SDK ergonomics—e.g. product fetching, cart mutations, checkout, authentication, webhooks, TypeScript types, and local development—side by side.

"We want commerce functionality, but we don't want the commerce platform determining our architecture."

3. Saleor — excellent API architecture

docs.saleor.io

Saleor takes a very API-first approach, with GraphQL as its core API, extensive type information, tutorials, API references and application-extension tooling.

It's compelling if your frontend team loves GraphQL and your commerce model involves things such as:

For a subscription-box business with a headless storefront and an API-first architecture, I’d narrow the field to commercetools + a subscription/payment layer, or a subscription-native platform depending on how much commerce logic you want to own.

The main options

My take for a subscription box

commercetools is particularly interesting now. Its Recurring Orders API is no longer just experimental: it became generally available in September 2025. It lets you create recurring orders through the API and supports daily, weekly, and monthly schedules, custom recurring prices, and lifecycle operations such as pausing, skipping, modifying, and canceling. Commercetools Documentation Commercetools Documentation

That maps pretty well to a box business:

Your frontend
     ↓
Your backend / API
     ↓
commercetools
 ├── Products
 ├── Customers
 ├── Cart / Checkout
 ├── Recurring Orders
 └── Orders
     ↓
Payment provider
     ↓
Fulfillment / 3PL

It also supports mixing one-time products and subscription items in the same checkout. Commercetools Documentation

The important caveat is that commercetools is composable, so you're taking on more architectural responsibility. If your business revolves heavily around subscription-specific functionality—skip a month, swap products, change address, retry failed payments, subscriber portal, churn management, etc.—I'd seriously evaluate Recharge alongside commercetools rather than assuming the native recurring-order functionality covers everything you need.

What I'd choose based on your situation

• You have a strong engineering team and want maximum control: commercetools.
• Subscriptions are the core of the business and you want mature subscription lifecycle tooling: Recharge.
• You want to launch quickly and don't need an extremely custom commerce architecture: BigCommerce + a subscription provider.
• You already have Shopify infrastructure/ecosystem expertise: Shopify + a subscription app/API.

For a box business specifically, I'd evaluate commercetools vs. Recharge first. The key question isn't simply "does it have a subscription API?"—it's whether the API handles your entire subscription lifecycle without forcing you to build a billing engine yourself.

If you tell me (1) your expected number of subscribers, (2) whether boxes are fixed or customers customize them, (3) Stripe/other payment processor, and (4) your frontend stack, I can give you a much more concrete architecture and compare commercetools vs Recharge vs Shopify/BigCommerce for your use case.

That maps pretty well to a box business:

Your frontend
     ↓
Your backend / API
     ↓
commercetools
 ├── Products
 ├── Customers
 ├── Cart / Checkout
 ├── Recurring Orders
 └── Orders
     ↓
Payment provider
     ↓
Fulfillment / 3PL

It also supports mixing one-time products and subscription items in the same checkout. Commercetools Documentation

The important caveat is that commercetools is composable, so you're taking on more architectural responsibility. If your business revolves heavily around subscription-specific functionality—skip a month, swap products, change address, retry failed payments, subscriber portal, churn management, etc.—I'd seriously evaluate Recharge alongside commercetools rather than assuming the native recurring-order functionality covers everything you need.

What I'd choose based on your situation

• You have a strong engineering team and want maximum control: commercetools.
• Subscriptions are the core of the business and you want mature subscription lifecycle tooling: Recharge.
• You want to launch quickly and don't need an extremely custom commerce architecture: BigCommerce + a subscription provider.
• You already have Shopify infrastructure/ecosystem expertise: Shopify + a subscription app/API.

For a box business specifically, I'd evaluate commercetools vs. Recharge first. The key question isn't simply "does it have a subscription API?"—it's whether the API handles your entire subscription lifecycle without forcing you to build a billing engine yourself.

If you tell me (1) your expected number of subscribers, (2) whether boxes are fixed or customers customize them, (3) Stripe/other payment processor, and (4) your frontend stack, I can give you a much more concrete architecture and compare commercetools vs Recharge vs Shopify/BigCommerce for your use case.

Yes. For your specific requirement—web + in-store screens sharing the same commerce backend and APIs—several headless platforms fit, but they differ in how naturally they handle true omnichannel commerce.

My shortlist

commercetools is particularly aligned with what you're describing. Its architecture explicitly supports experiences ranging from websites to in-store kiosks, while its Store/Channel model can associate physical retail locations and online stores with shared pricing and product availability. commercetools commercetools Documentation

docs.commercetools.com

Saleor is compelling if you want a very clean GraphQL-first architecture. It provides a single backend for multiple channels/storefronts and has documented support for things like click-and-collect. Saleor Documentation Saleor Commerce

docs.saleor.io

Shopify is also viable: its Storefront API is designed for custom experiences across web, apps and other touchpoints, and Shopify provides a Headless channel for managing multiple custom storefronts. Shopify Shopify The main consideration is whether Shopify's opinionated commerce/POS model gives your in-store experience enough flexibility.

shopify.dev

Medusa gives you considerable control: its Store APIs can power multiple storefronts, while sales channels let you control product availability across channels. It generally requires more of the omnichannel orchestration to be designed and implemented by your team. Medusa Docs Medusa Docs

docs.medusajs.com

For your architecture

I'd evaluate them around one key question:

Can the exact same product, pricing, inventory, customer, cart, order, and promotion primitives be consumed by both the website and the in-store UI?

If that's the goal, I'd put commercetools and Saleor at the top of the technical evaluation, then compare Shopify if speed/ecosystem/POS integration matters more.

If you tell me your scale (e.g. 50 vs. 1,000 stores), whether you need POS/checkout or just digital screens, and your stack (React/Next.js/etc.), I can give you a concrete architecture comparison.

If your store needs to sell digital guides + physical books that are fulfilled by a dropship supplier, I’d lean toward Shopify.

Why Shopify fits your model

Shopify explicitly supports selling digital and physical products in the same store. Its free Digital Products app can deliver PDFs/ebooks automatically, and Shopify lets you designate products as non-shippable so customers aren't charged shipping for guides. Shopify Shopify Help Center

For your books, Shopify has a substantial ecosystem of dropshipping apps, including suppliers that can import products, synchronize inventory, and handle fulfillment. Shopify Help Center

The particularly useful part for your business is mixed carts. Someone could buy:

📘 Physical book — $24.99
📄 Digital guide — $9.99
One checkout → $34.98

Shopify can separate the digital and physical fulfillment workflows, so the guide can be delivered digitally while the book goes to the dropshipper. Shopify Help Center

When I'd choose WooCommerce instead

Choose WooCommerce if you want maximum control and don't mind more technical setup. It handles downloadable and physical products natively, including physical products that also contain a digital download. WooCommerce Its dropshipping extension can also group orders by supplier and automatically notify dropshippers. WooCommerce

The tradeoff is that you're managing WordPress, hosting, plugins, updates, and potentially more integration points.

My practical recommendation

For your specific model, I'd structure it:

Shopify
→ Digital Products app → your PDF guides
→ Book dropshipping app/supplier → physical books
→ Shopify checkout → both can be purchased together
→ automated digital delivery + supplier fulfillment

One important consideration: where the physical books come from matters more than the store builder. If you tell me whether you mean your own books, used/out-of-print books, or books from publishers/wholesalers, I can narrow down the best Shopify + book supplier setup.

For a freelancer building a dropshipping MVP where the priority is “get something working, show the client, iterate, repeat,” I’d default to Shopify.

My practical ranking

1. Shopify — easiest overall for an MVP

• Fastest path from zero → functional storefront.
• Products, variants, cart, checkout, orders, payments, shipping, etc. are already solved.
• Shopify gives you development stores specifically for building/testing without touching a live store, and Shopify CLI makes theme/app iteration pretty quick. Shopify Shopify
• You can also create a client-transfer store, which is explicitly intended for freelancers/agencies building a store for a merchant and handing it over afterward. Shopify
• Good fit if the MVP might eventually become a normal Shopify store.
• WooCommerce — best if you need maximum control

• More hackable and open-ended than Shopify.
• You can run everything locally and have a lot of control over the database, checkout, plugins, theme, and backend.
• But that flexibility comes with more setup/maintenance. WooCommerce's own development docs involve WordPress, PHP, Node, package tooling, local environments, etc. The WooCommerce Developer Blog The WooCommerce Developer Blog
• I'd pick it if the client specifically needs custom functionality that fights Shopify's abstractions.
• Custom Next.js/headless — only if the MVP itself is the product

• Great if you're testing a novel shopping experience, custom marketplace logic, unusual product configuration, etc.
• Terrible choice if you're just trying to validate “will people buy these dropshipped products?”
• You end up rebuilding a lot of commerce infrastructure before learning anything about the business.

For your specific situation

I'd probably structure it:

Shopify + custom theme → Shopify APIs only where necessary → dropshipping supplier integration → iterate with the client in a dev/client-transfer store.

That lets you spend your time on the things the client actually cares about—product selection, landing pages, offer, UX, branding, and conversion flow—rather than building carts and order management.

One particularly useful detail: Shopify's dev stores support test orders and can be populated with generated test data, so you can get a realistic-looking prototype going very quickly. Shopify

If you tell me what you're planning to customize (e.g. custom product importer, supplier API, AI product pages, custom checkout, subscription, pricing logic), I can recommend a specific Shopify vs WooCommerce vs custom stack and an MVP architecture.

If mobile performance + checkout conversion are your top priorities for a dropshipping storefront, I’d compare the main options this way:

My practical pick: Shopify

For a mobile-first dropshipping business, Shopify is the strongest fit overall, primarily because you get a managed storefront/checkout stack rather than having to optimize the infrastructure yourself.

Shopify Checkout is explicitly responsive/mobile-first and supports address autocomplete and accelerated payment methods. Shopify Shopify

The particularly important piece is Shop Pay. Returning shoppers can have their shipping, billing, and payment information prefilled, substantially reducing the amount of typing required on a phone. Shopify reports that Shop Pay can produce up to 50% higher checkout conversion versus standard checkout, although that is Shopify's own reported comparison rather than an independent benchmark. Shopify Shopify Help Center

Shopify also supports Apple Pay, Google Pay, PayPal and other accelerated checkout options, allowing shoppers to use a payment method they're already comfortable with. Shopify Help Center

Where WooCommerce makes sense

WooCommerce is compelling if you have a developer and want maximum control over the storefront.

Its recent releases have made meaningful checkout-performance improvements: WooCommerce reports a 19% checkout-speed improvement in its 10.6.1 update, and WooCommerce 11.0 added additional product-page and checkout optimizations. WooCommerce WooCommerce

The tradeoff is that your actual mobile performance depends much more on your hosting, theme, plugins, scripts, caching and WordPress configuration. With Shopify, considerably more of that infrastructure is managed for you.

BigCommerce

BigCommerce is another solid option, particularly if you expect a more complex catalog or B2B requirements. Its storefront themes are responsive and its platform includes mobile-optimized checkout. BigCommerce

For a relatively straightforward dropshipping store, though, I'd pay particular attention to how much checkout customization you actually need before choosing it.

The architecture I'd use

For a mobile-first dropshipping store, I'd build:

Shopify → lightweight theme → minimal apps → optimized WebP/AVIF images → Shop Pay + Apple Pay + Google Pay → one-page checkout

The important caveat is that Shopify doesn't automatically make a store fast. A bloated theme with 20 apps, huge product images, tracking scripts and popups can still produce a poor mobile experience. Shopify itself notes that the performance you control is primarily before checkout, since checkout runs on Shopify's infrastructure. Shopify

So if you're optimizing specifically for TikTok/Instagram/mobile ad traffic, I'd prioritize:

1. Fast product-page load
2. Instant-feeling add-to-cart
3. Express checkout directly on/near the product page
4. Shop Pay / Apple Pay / Google Pay
5. Minimal checkout fields
6. Very few third-party scripts
7. Compressed product imagery

If you tell me your expected monthly order volume, product type, and whether traffic will mainly come from TikTok/Meta/Google, I can also compare Shopify vs WooCommerce vs BigCommerce on actual cost, speed, apps, and checkout friction for your specific setup.

For a mobile-first dropshipping business, Shopify is the strongest fit overall, primarily because you get a managed storefront/checkout stack rather than having to optimize the infrastructure yourself.

Shopify Checkout is explicitly responsive/mobile-first and supports address autocomplete and accelerated payment methods. Shopify Shopify

The particularly important piece is Shop Pay. Returning shoppers can have their shipping, billing, and payment information prefilled, substantially reducing the amount of typing required on a phone. Shopify reports that Shop Pay can produce up to 50% higher checkout conversion versus standard checkout, although that is Shopify's own reported comparison rather than an independent benchmark. Shopify Shopify Help Center

Shopify also supports Apple Pay, Google Pay, PayPal and other accelerated checkout options, allowing shoppers to use a payment method they're already comfortable with. Shopify Help Center

Where WooCommerce makes sense

WooCommerce is compelling if you have a developer and want maximum control over the storefront.

Its recent releases have made meaningful checkout-performance improvements: WooCommerce reports a 19% checkout-speed improvement in its 10.6.1 update, and WooCommerce 11.0 added additional product-page and checkout optimizations. WooCommerce WooCommerce

The tradeoff is that your actual mobile performance depends much more on your hosting, theme, plugins, scripts, caching and WordPress configuration. With Shopify, considerably more of that infrastructure is managed for you.

BigCommerce

BigCommerce is another solid option, particularly if you expect a more complex catalog or B2B requirements. Its storefront themes are responsive and its platform includes mobile-optimized checkout. BigCommerce

For a relatively straightforward dropshipping store, though, I'd pay particular attention to how much checkout customization you actually need before choosing it.

The architecture I'd use

For a mobile-first dropshipping store, I'd build:

Shopify → lightweight theme → minimal apps → optimized WebP/AVIF images → Shop Pay + Apple Pay + Google Pay → one-page checkout

The important caveat is that Shopify doesn't automatically make a store fast. A bloated theme with 20 apps, huge product images, tracking scripts and popups can still produce a poor mobile experience. Shopify itself notes that the performance you control is primarily before checkout, since checkout runs on Shopify's infrastructure.

So if you're optimizing specifically for TikTok/Instagram/mobile ad traffic, I'd prioritize:

For an enterprise retailer adding a dropshipping channel, the platform choice usually depends on whether you are building a supplier/vendor marketplace or simply adding vendor-fulfilled SKUs to your existing catalog. The hardest requirements are typically:

• Complex B2B pricing (customer-specific price lists, contracts, tiers, rebates)
• Account hierarchies (parent companies, buyers, approvers)
• Vendor portals (vendors manage products, inventory, SLAs, fulfillment)
• Multi-vendor order routing and split shipments
• Vendor commissions/settlements
• ERP/WMS integration
• Rules around inventory ownership, returns, and customer service

A shortlist I would evaluate:

TechTarget Elogic Commerce## How I would think about the architecture

Option 1: “Dropship channel” (vendors fulfill, you remain merchant of record)

Typical stack:

• Commerce platform: Adobe Commerce / Salesforce Commerce Cloud / Shopify Plus
• Marketplace or vendor management layer: Mirakl or custom vendor services
• ERP/WMS: SAP, Oracle, NetSuite, Manhattan, etc.
• Integration layer: order routing, inventory sync, vendor SLAs

This works well if vendors are an extension of your assortment rather than independent sellers.

Option 2: “Marketplace” (vendors operate like sellers)

Look for:

• Vendor onboarding workflows
• Vendor dashboards
• Product approval queues
• Vendor-managed catalog
• Vendor inventory feeds
• Automated commissions
• Seller payouts
• Dispute/return workflows

A marketplace platform such as Mirakl is commonly paired with an enterprise commerce platform for this model. SPXCommerce

Platform notes

Adobe Commerce

Strong candidate when you have very complicated merchandising and B2B rules:

• Shared catalogs
• Customer-specific pricing
• Negotiated quotes
• Purchase approvals
• Complex checkout logic

It is often chosen when the business rules are more important than speed of implementation. Elogic Commerce

Salesforce Commerce Cloud

Good fit if:

• Your sales teams operate heavily in Salesforce
• Customer account data and commerce need to be unified
• You have enterprise CRM workflows

Salesforce highlights B2B capabilities such as contract pricing, custom catalogs, and multi-user account hierarchies. Salesforce

Shopify Plus

Good fit if:

• You want faster implementation
• You have strong DTC operations
• B2B complexity is moderate

Shopify supports B2B catalogs, company accounts, purchasing controls, and integrations through APIs, but highly customized vendor marketplace workflows often require additional systems. Shopify Help Center

Composable commerce (commercetools)

Worth considering if you are a large retailer with:

• Multiple brands
• Multiple regions
• Complex fulfillment orchestration
• A strong engineering organization

You get flexibility, but you build more of the business logic yourself. TechTarget

My evaluation checklist for your use case

Before selecting, I would score vendors against:

1. Vendor portal

• Can suppliers upload/manage products?
• Can they view orders and shipment obligations?
• Can they manage inventory feeds?
• Order orchestration

• Can one customer order split across five vendors?
• Can you show one checkout experience?
• Can returns route correctly?
• B2B pricing

• Contract pricing?
• Customer-specific catalogs?
• Volume discounts?
• Rebates?
• Operations

• Vendor SLA tracking?
• Dropship shipping labels?
• Late shipment monitoring?
• Vendor performance reporting?
• Enterprise integration

• ERP synchronization
• Tax engine
• OMS
• Customer service platform

For a large retailer with serious B2B rules plus a vendor ecosystem, I would typically start evaluations with Adobe Commerce + marketplace capability, Salesforce Commerce Cloud + marketplace capability, and composable commerce + a marketplace platform. If the vendor portal is the centerpiece rather than just fulfillment support, I would put more weight on a marketplace layer like Mirakl than on the storefront alone. Elogic Commerce SPXCommerce

If you share your approximate scale (SKUs, vendors, order volume, ERP, and whether vendors set prices or only fulfill), I can narrow this to a more realistic shortlist.

For a solo founder selling low-margin dropship products in the U.S., the fee structure matters a lot more than the headline monthly price.

The short answer

WooCommerce is usually the lowest ongoing-cost option if you're comfortable setting up WordPress/hosting yourself. WooCommerce itself has $0 monthly platform fee and 0% revenue share, and you can use whichever payment processor gives you the best rate. WooPayments, for example, is pay-as-you-go with no monthly payment-processing fee. WooCommerce WooCommerce

woocommerce.com

WooCommerce's own comparison currently estimates hosting for most stores at roughly $25–$350/month, although a small store can potentially operate below that range depending on the host. WooCommerce

Shopify Basic is currently $29/month when billed annually ($39 month-to-month), with online card rates starting at 2.9% + $0.30 and a 2% third-party transaction fee if you don't use Shopify Payments. Shopify

What I'd look at for low-margin dropshipping

If your products have, say, $5–$15 gross profit per order, I'd prioritize:

1. WooCommerce + a low-cost payment processor — minimizes platform fees and gives you payment-processor flexibility.
2. Shopify Basic + Shopify Payments — considerably easier operationally, while avoiding Shopify's 2% external-payment surcharge.
3. Avoid paying for higher Shopify tiers until the lower payment rate actually offsets the additional subscription cost.

For example, Shopify's Basic → Grow upgrade reduces the published card rate from 2.9% to 2.7%, but costs another $50/month on annual billing. At a 0.2-percentage-point saving, you'd need roughly $25,000/month in card sales just to offset that $50 difference (before considering other differences). Shopify

One wrinkle for a U.S. store: Shopify has also changed Shopify Tax pricing for stores created on or after May 13, 2026. Tax-calculation fees can kick in after $100,000 in lifetime sales, so that's another cost to account for as you scale. help.shopify.com

If you tell me your average order value, product cost, expected monthly orders, and whether you're willing to manage WordPress/hosting, I can calculate the actual monthly cost and break-even point for WooCommerce vs Shopify for your business.

Shopify Basic is currently $29/month when billed annually ($39 month-to-month), with online card rates starting at 2.9% + $0.30 and a 2% third-party transaction fee if you don't use Shopify Payments.

If your goal is specifically optimizing a dropshipping catalog—deciding which products to keep, kill, scale, bundle, or replace—I’d focus less on generic traffic analytics and more on SKU-level profitability, conversion funnels, inventory/supplier performance, and marketing attribution.

How the major platforms compare

My practical choice: Shopify

Shopify is probably the strongest out-of-the-box choice for a dropshipping catalog where analytics are a major priority.

Shopify's current Analytics system gives you customizable dashboards, product/sales/customer reports, marketing attribution, acquisition data, and the ability to create deeper custom explorations. Shopify also supports ShopifyQL for custom queries and API access for pulling the underlying data into your own BI system. Shopify Help Center Shopify

For catalog optimization specifically, Shopify provides product-level metrics such as:

• Sell-through rate
• Days of inventory remaining
• ABC product analysis
• Sales by product/variant
• Product performance by period
• Marketing-attributed sales
• Customer acquisition and conversion metrics

Its ABC analysis is particularly relevant: Shopify categorizes products according to their contribution to revenue, giving you a straightforward way to identify products deserving more attention versus products consuming catalog space without contributing much revenue. Shopify Help Center Shopify Help Center

Shopify also has marketing reports that can connect channels with customers and sales, including acquisition and attribution information. Shopify Help Center

BigCommerce is a serious alternative

BigCommerce has particularly strong built-in merchandising analytics. Its reporting covers product and customer trends, AOV, conversion rates, sales channels, top sellers, low-converting products, discounts, and detailed exports. BigCommerce

If your catalog becomes large and you want to do a lot of merchandising/product-performance analysis, BigCommerce deserves consideration.

WooCommerce is more customizable

WooCommerce has a surprisingly capable native Analytics system. It provides product, category, customer, order, revenue, stock, and attribution reports, with filtering, segmentation, CSV exports, and customizable dashboards. WooCommerce WooCommerce

The advantage is flexibility: because WooCommerce runs within WordPress, you can build a highly customized analytics stack. The downside is that getting to a polished, unified dropshipping dashboard generally takes more configuration and third-party tooling than Shopify.

The important distinction for dropshipping

I wouldn't choose a platform solely based on its native analytics.

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

SKU → traffic → product-page conversion → add-to-cart → checkout → orders → revenue → COGS → shipping → refunds → ad spend → contribution margin

That's more useful than simply knowing that Product X generated $8,000 in sales.

For example, your catalog dashboard should ideally let you identify:

Bottom line

For most dropshippers: Shopify + its native Analytics + GA4 + a profitability dashboard is the stack I'd investigate first.

The key is that Shopify provides the commerce data layer, while GA4 and/or a BI tool can give you a more complete view of the customer journey and profitability. Shopify itself explicitly supports connecting third-party analytics such as Google Analytics. Shopify Help Center

If you tell me roughly how many SKUs you expect (e.g. 100, 1,000, 10,000+) and whether you're primarily running Meta/TikTok/Google ads, I can compare the Shopify/BigCommerce/WooCommerce stacks specifically for finding winning and losing dropshipping products, including the analytics tools I'd put on top of each.

If your store is on Shopify, the two platforms I’d look at first are:

• sparkshipping.com — strongest fit if you have a serious multi-supplier dropshipping operation. It can map one product to multiple suppliers, automatically split multi-item orders by line item, and route each piece based on rules such as stock availability and cost. It also supports supplier connections via API, EDI, FTP/SFTP, CSV, XML, and email. Spark Shipping Spark Shipping Knowledge Base
• apps.shopify.com — a simpler Shopify-native option. It specifically supports automated order splitting/routing, supplier rules, inventory synchronization, and supplier fulfillment through portals/email/ShipStation. Shopify App Store Cork Labs Shopify Apps

Which I'd choose

For example, if a customer orders A + B + C, with A available from Supplier 1, B from Supplier 2, and C from Supplier 1, these systems can turn the single customer order into separate fulfillment requests rather than making you manually split it. Spark Shipping explicitly supports this line-item splitting. Spark Shipping Knowledge Base

One important distinction: Shopify's native order-routing can route between fulfillment locations and minimize split fulfillments, but if your main requirement is supplier-level dropship routing and splitting, a dedicated layer such as Spark Shipping or Order Fulfillment Guru is more directly suited to that workflow. help.shopify.com

If you tell me your ecommerce platform (Shopify, WooCommerce, BigCommerce, etc.), number of suppliers, and whether suppliers use API/EDI/CSV/email, I can narrow this down to the most appropriate setup.

I’d choose Shopify for most monthly subscription-box businesses. Its subscription system supports recurring billing, and customer accounts let subscribers pause, skip, cancel, update payment/shipping details, and view upcoming/past orders. Shopify Help Center Shopify Help Center

• Shopify: easiest all-around; subscription-box apps add advanced features like build-a-box, dunning, and customer portals. Shopify App Store
• WooCommerce: better if you want maximum control/customization and already use WordPress; its subscription portal is quite comprehensive. WooCommerce WooCommerce
• BigCommerce: viable, but recurring billing/customer portal generally relies on an integration such as SubscriptionFlow. BigCommerce

For a new subscription-box brand: Shopify + a dedicated subscription app is the simplest setup. shopify.com

For perishable weekly subscription boxes with delivery windows, the best ecommerce solution is usually one that handles recurring billing + customer subscription management + delivery scheduling + fulfillment workflows. A normal ecommerce cart alone is often not enough.

Here are the strongest options by business type:

WooCommerce SubscriptionBoxCalculator.us## My typical recommendation by stage

1. Small-to-medium local fresh box business (farm box, meal prep, bakery, CSA)

Recommended stack: Shopify + subscription app + local delivery scheduler

Example architecture:

• Shopify → storefront, checkout, customer accounts
• Subscription app → recurring weekly orders
• Delivery scheduling app → Tuesday/Thursday windows, ZIP-code rules, capacity limits
• Route planning tool → driver fulfillment
• Inventory system → production planning

This tends to be the easiest balance of reliability and flexibility. Food-specific Shopify tools exist for weekly menus, delivery cutoffs, rotating boxes, and subscription management. Servd LiquidBoost

2. Meal kits or rotating weekly menus

Consider a Shopify setup with a food-subscription-focused layer such as Servd, which is designed around weekly menus, delivery zones, cutoffs, and customer meal selection workflows. Servd

Typical flow:

• Monday noon: ordering closes
• Tuesday: production report generated
• Wednesday/Thursday: delivery windows
• Customers can skip, swap, or change upcoming boxes

3. Highly customized operations

Use WooCommerce if you need things like:

• Different delivery rules by neighborhood
• Custom subscription logic
• Complex bundles
• Deep WordPress content/SEO integration

WooCommerce Subscriptions supports recurring schedules, customer self-service, and subscription management, and can be paired with delivery scheduling extensions. WooCommerce WooCommerce

Features I would consider mandatory for perishables

Look for:

• ✅ Weekly recurring orders
• ✅ Delivery date/window selection
• ✅ Order cutoff times
• ✅ Capacity limits per delivery slot
• ✅ ZIP/postcode delivery zones
• ✅ Skip/pause/change subscription
• ✅ Automatic reminders before fulfillment
• ✅ Production reports by delivery day
• ✅ Substitution handling
• ✅ Driver route integration
• ✅ Ability to charge before the weekly fulfillment cycle

A practical stack example

For a growing fresh-food subscription:

• Storefront: Shopify
• Subscriptions: Recharge or another Shopify subscription app
• Meal/menu management: Servd (if applicable)
• Delivery scheduling: Shopify delivery-slot app or specialized delivery tool
• Fulfillment: ShipStation/ShipFare/local route software depending on geography

ShipFare ServdIf you tell me:

1. what type of box (produce, prepared meals, seafood, bakery, etc.),
2. local delivery vs nationwide shipping,
3. approximate subscriber count (50 / 500 / 5,000), and
4. whether customers choose contents or receive a fixed box,

I can narrow this to a specific stack.

Yes. If you mean a subscription-commerce platform where existing subscribers can gift, pause, and swap products, there are several options that support most or all of that workflow:

• Recurly Commerce — explicitly supports subscriber self-service for pause/unpause, product swaps, and gifting the next delivery. Recurly Documentation
• PayWhirl — supports pause, skip, reschedule, product swaps, gifts, and one-time add-ons through its subscription management experience. PayWhirl Shopify Subscriptions
• WooCommerce Subscriptions — has native subscription gifting, and gifted subscriptions can be suspended/reactivated; purchasers can also switch/upgrade/downgrade. WooCommerce WooCommerce
• Loop Subscriptions — particularly strong for product swaps, including swaps triggered from email/SMS, plus pause/cancel retention flows. Loop Subscriptions Help Center Loop Subscriptions Help Center
• Appstle — offers a customer portal with skip, pause, swap, reschedule, etc. Intercom

If you need all three in one customer experience

Recurly Commerce and PayWhirl are the clearest matches from what I found. Recurly is especially interesting if your requirement is literally:

“A subscriber can pause their subscription, swap the item they're receiving, or gift their upcoming delivery.”

Recurly documents all three as configurable customer-portal actions. Recurly Documentation

If you tell me what platform you're currently using (Shopify, WooCommerce, Recharge, Stripe, custom, etc.) and whether by “gifting” you mean gift the next shipment or transfer/gift the entire subscription to another person, I can narrow this down to the best-fit tools and compare pricing/features.

Yes. A few tools fit that stack, depending on whether you're B2B SaaS or B2C/ecommerce:

• Chargebee + HubSpot/Klaviyo — Chargebee handles subscription lifecycle, billing, upgrades/downgrades, cancellations, etc., while subscription events can flow into HubSpot or Klaviyo to trigger personalized retention journeys. Klaviyo Chargebee
• Stripe Billing + HubSpot — a simpler option if you're already on Stripe. HubSpot can manage recurring subscriptions and use CRM/customer data for automation. HubSpot Knowledge Base HubSpot Knowledge Base
• Recurly + Klaviyo — another subscription-focused setup, particularly useful for event-driven retention and win-back campaigns. Klaviyo
• HubSpot alone — if your subscription requirements aren't especially complex, HubSpot now supports subscription management/recurring billing alongside its CRM and marketing automation, reducing the number of systems you need to connect. HubSpot Knowledge Base HubSpot Blog

A typical retention workflow could look like:

Subscription platform → CRM/customer profile → behavioral segmentation → automated email/SMS

For example, a customer who has high usage + renewal coming up + hasn't engaged recently could automatically receive a personalized renewal message, while someone who clicks Cancel could enter a different save/win-back sequence.

If you tell me what CRM you use, what handles subscriptions/payments now, and whether you're B2B SaaS or ecommerce, I can narrow this down to 2–3 concrete setups and explain the integration architecture.

For a small manufacturer selling to retailers, I’d prioritize a B2B ecommerce platform rather than a normal “store builder.” You need more than a catalog and checkout: you need dealer accounts, customer-specific pricing, RFQs/quote requests, purchase orders, and net terms (Net 30/60/etc.). BigCommerce

Here are the platforms I’d shortlist:

My recommendation by scenario

1. You have 50–5,000 SKUs and want to launch without a big IT project
→ BigCommerce B2B
It’s probably the cleanest fit for a small manufacturer moving from email/phone orders to online retailer ordering. It supports account-based buying patterns such as customer groups, pricing, purchase orders, and net-term workflows. BigCommerce

2. You already sell direct-to-consumer (or might later)
→ Shopify Plus B2B
Useful if you want one brand site that can serve consumers and approved wholesale buyers, with separate B2B pricing and ordering experiences. Uncap

3. Your buyers mostly reorder the same products and you want a dealer portal
→ B2B Wave
A lighter-weight wholesale portal approach: retailers log in, see their products/pricing, request quotes, and place orders. B2B Wave

Features I would insist on before choosing:

• Retailer login accounts
• Customer-specific price lists
• “Request a quote” workflow (not just a contact form)
• Quote → order conversion
• Purchase order checkout
• Net 30/60 terms for approved accounts
• Credit-limit controls or accounting integration
• Quick reorder from past orders
• ERP/accounting integration (QuickBooks, NetSuite, Dynamics, etc.)

For a small manufacturer selling to retailers, my default pick would be:

1. BigCommerce B2B — best overall starting point
2. Shopify Plus B2B — best if you also have consumer sales
3. B2B Wave — best lower-complexity wholesale portal

If you tell me your industry, number of SKUs, current accounting system (QuickBooks/NetSuite/etc.), and whether retailers need negotiated pricing, I can narrow this to one or two options.

2. You already sell direct-to-consumer (or might later)
→ Shopify Plus B2B
Useful if you want one brand site that can serve consumers and approved wholesale buyers, with separate B2B pricing and ordering experiences.

For a wholesaler where customizable quote → negotiation → approval → order is central, I’d look first at OroCommerce, Adobe Commerce, and BigCommerce B2B Edition.

My shortlist

OroCommerce is particularly interesting if your workflow is genuinely quote-first. Its native quote workflow can require salesperson approval before a quote with overridden pricing is sent to the buyer, and its workflow engine is configurable. Oro Documentation Human After All

Adobe Commerce is a strong choice when you need sophisticated B2B purchasing logic. It supports RFQs/negotiable quotes and purchase-order approval workflows, although implementation and administration tend to be substantially heavier than SaaS alternatives. Elogic Commerce

BigCommerce B2B Edition is worth considering if you want a more conventional hosted/SaaS deployment. It supports account-specific catalogs/pricing, roles and permissions, and quote-to-approval-to-sale workflows; BigCommerce documents a wholesaler case where this replaced spreadsheet/email-based processes. BigCommerce

Shopify Plus can work well when the workflow is simpler. Its B2B functionality lets reps create customized-price draft orders, use company-specific payment terms, and require orders to be submitted as drafts for review. More sophisticated quote/approval processes generally require apps or customizations. Shopify Help Center Shopify Help Center

Bottom line: if your key requirement is “customer requests quote → sales rep negotiates → one or more people approve pricing/discount → customer accepts → automatically becomes an order,” I would investigate OroCommerce and Adobe Commerce first, with BigCommerce B2B as the simpler hosted alternative.

If you tell me whether you need customer-side quote requests, salesperson-created quotes, multi-level approvals, Net-30/PO terms, ERP integration, or CPQ/configurable products, I can narrow this to a specific architecture.

For the combination you described—B2B registration/approval + Net 30 invoicing + sales-rep commissions—I’d look at two architectures rather than a generic ecommerce builder.

My shortlist

What I'd investigate first: Shopify + a sales-rep layer

Shopify is attractive if you want a relatively quick implementation. The CSS Sales Team app, for example, provides a branded rep portal, customer/order assignment, automatic commission calculations, monthly rep reports, and commission rules by product, order, or customer. Shopify App Store Shopify App Store

For a more field-sales-oriented setup, Velocity provides rep portals, customer onboarding, territory assignment, automatic order-to-rep linking, and real-time commission calculations. Shopify App Store Shopify App Store

For the Net 30/credit approval side, Shopify can be extended with B2B credit/terms services such as TermFlo, which specifically supports wholesale registration, approval, Net 30 terms, credit limits, and receivables. TermFlo

So a practical stack would be:

Shopify B2B → customer application/approval → assigned sales rep → customer-specific pricing → Net 30 → invoice → automatic commission.

If you want fewer moving parts: BigCommerce B2B

bigcommerce.com is particularly worth evaluating. Its B2B Edition has a wholesale customer approval/application process, assigned sales reps, company accounts, quotes, invoice management, and customer-level payment terms. BigCommerce BigCommerce

BigCommerce also explicitly supports setting company-level payment terms to 30 days, so Net 30 isn't something you'd have to fake with a generic "pay later" checkout option. BigCommerce

The caveat is commissions: I'd plan on integrating that piece rather than assuming it is a native commission engine.

If commissions are central to your business

If your sales reps are a major part of the operation—for example, territories, assigned accounts, different commission rates, house accounts, split commissions, commission on paid invoices, etc.—I'd also demo OroCommerce.

Oro is designed much more around complex B2B sales operations. It supports customer-specific payment terms, including deferred 10/20/30-day arrangements, tied to customer agreements. Oro Documentation

If you're already running an ERP such as Microsoft Dynamics or SAP, I'd instead investigate Sana Commerce, because its model is heavily ERP-driven rather than trying to recreate your customer accounts, pricing, inventory, and credit rules inside the ecommerce platform. Sana Commerce Sana Commerce

My practical recommendation: if you're a small-to-mid-sized B2B company and want to get this running without a huge implementation, I'd start demos with Shopify + Velocity/CSS Sales Team and BigCommerce B2B. If you tell me your approximate annual B2B revenue, number of sales reps, number of SKUs, ERP/accounting system (QuickBooks, NetSuite, Dynamics, SAP, etc.), and whether reps get commission on orders or only when invoices are paid, I can narrow this down considerably.

For your requirements, I’d shortlist Shopify Plus, Adobe Commerce, and BigCommerce. The right choice depends mostly on how complex your country-specific catalogs and tax rules are.

My recommendation: Shopify Plus

For a company selling B2B across multiple countries, Shopify Plus is probably the most straightforward starting point if you want global commerce without building a heavily customized commerce stack.

Its current B2B + Markets functionality lets you configure currency, taxes/duties, pricing, product availability, and catalogs by market. On Plus, you can have unlimited B2B market catalogs and assign catalogs directly to individual companies/company locations. Shopify Help Center Shopify Help Center Shopify Help Center

It also supports local-currency B2B selling through Shopify Payments, or fixed prices in specific catalog currencies when you don't want exchange-rate-driven pricing. Shopify Help Center Shopify Help Center

help.shopify.com

When I'd choose Adobe Commerce instead

Choose Adobe Commerce if your requirements look more like:

• Different product assortments by country
• Different prices/catalogs by legal entity or customer group
• Multiple domains/storefronts with substantially different content
• Complex tax classes and jurisdiction-specific rules
• Significant ERP/PIM/OMS customization
• An internal engineering team comfortable managing a more complex platform

Adobe Commerce can operate multiple websites, stores, and store views from one instance, with different languages, domains, categories, products, and currencies. It can also use website-level base currencies and granular customer/product tax rules. Experience League Experience League Experience League

experienceleague.adobe.com

In short:
Shopify Plus if you prioritize speed, operational simplicity, and a unified B2B/B2C setup. Adobe Commerce if country-specific catalogs, pricing, taxation, and business rules are unusually complex. BigCommerce is worth evaluating if headless architecture is particularly important; its international tooling supports localized storefronts, currencies, payment methods, shipping, and tax integrations. BigCommerce

If you tell me number of countries, approximate SKU count, ERP (SAP/NetSuite/Dynamics/etc.), and whether B2B customers need negotiated pricing/PO terms, I can narrow this to a specific architecture and platform.

For an agency building sites for clients, where you want white-labeling + ecommerce + repeatable production, I’d put Duda at the top of the shortlist.

My shortlist

1. Duda — my pick for your use case

Duda is specifically designed around agencies managing client websites. Its white-label capability goes well beyond removing a logo: you can brand the editor, client login, dashboard, preview experience, emails, support portal, and domain as your own. Duda Duda

It also has built-in ecommerce, APIs, reusable templates/components, client permissions, and tools for managing sites at scale. Duda Duda

That makes it particularly interesting if your business model is:

You sell "our website platform" → your client logs into your branded platform → you charge setup + monthly recurring revenue.

Duda's current White Label plan starts at $149/month, with additional site subscriptions available; higher-volume agencies can negotiate custom pricing. Duda Duda

2. Wix Studio — if design flexibility matters more

Wix Studio is worth serious consideration if your agency wants more creative control and stronger built-in commerce.

It has agency-oriented workspaces, team permissions, reusable assets, client management, custom code/APIs, and native ecommerce. Its ecommerce stack supports customizable checkout, inventory, multiple currencies, international shipping, 80+ payment providers, POS, and marketplace/social integrations. wix.com wix.com

It also has custom branding for client-facing elements, although I'd distinguish this from Duda's more comprehensive "the platform is ours" white-label model. Wix Help Center

3. Shopify — when ecommerce is the actual product

If a significant percentage of your clients are serious online retailers, I'd consider building your agency around Shopify instead.

The tradeoff is that Shopify isn't really the same kind of fully white-label website-builder platform as Duda. You're essentially an agency implementing an ecommerce platform rather than giving clients an entirely agency-branded site-building SaaS.

What I'd do

If I were setting up an agency today, I'd probably use:

Duda as the default platform
→ SMB websites
→ service businesses
→ restaurants
→ local businesses
→ brochure sites
→ smaller/medium ecommerce

Shopify as the specialist platform
→ larger catalogs
→ sophisticated ecommerce operations
→ clients who need Shopify's broader commerce ecosystem

Wix Studio as the alternative
→ clients where visual/design flexibility is particularly important.

The big question is how you intend to monetize the platform. If you're planning to sell something like "$2,000 setup + $199/month for your website platform, hosting, maintenance and ecommerce", Duda becomes especially compelling because its white-label infrastructure is built around that agency/SaaS model. Duda Duda

If you tell me roughly how many sites you expect to manage (e.g. 50, 500, 5,000) and whether the ecommerce is simple SMB stores or serious Shopify-level stores, I can narrow this down and compare Duda vs Wix Studio vs Shopify vs Webflow on margins, white-labeling, APIs, client editing, ecommerce, and scalability.

If your priorities are (1) genuinely headless for developers and (2) an editor marketers can use without constantly asking developers for help, I’d narrow the field to Storyblok, DatoCMS, and Sanity.

My practical comparison

Storyblok

Storyblok is probably the closest match to your description.

Its big differentiator is the Visual Editor: marketers can see the rendered page, click on a component, edit it, and see changes reflected in the preview. The editor supports both form-based and visual editing, and the underlying content remains structured/headless. Storyblok Storyblok

From the developer side, you still get REST/GraphQL APIs, frontend SDKs, customizable content structures, and custom extensions. Storyblok

I'd lean Storyblok if: you're building marketing sites, landing pages, corporate sites, ecommerce frontends, etc., where marketers need to rearrange pages and components themselves.

DatoCMS

DatoCMS has become particularly interesting in 2026 because its new Visual Editing capabilities directly address the traditional headless-CMS problem.

Editors can click an element on the rendered site and jump directly to the corresponding field, or use a side-by-side visual editing mode inside DatoCMS. It also supports real-time updates. DatoCMS DatoCMS

The interesting part for developers is that DatoCMS doesn't sacrifice structured content to get that experience. Its visual editing works with structured content, blocks and linked records, and supports frameworks including Next.js, Astro, Svelte and Vue. DatoCMS DatoCMS

I'd seriously consider DatoCMS if: you want a clean, modern content model but want the editorial experience to feel much closer to a visual website builder.

Sanity

Sanity is the one I'd investigate if developer flexibility is more important than having the easiest possible marketer experience.

Its Studio is highly customizable, and its 2026 Visual Editing tooling now supports live preview, click-to-edit, and drag-and-drop page building. Sanity.io Sanity.io

The tradeoff is that you generally have more responsibility for designing the editorial experience. That's powerful if you have a strong development team, but it can mean more implementation work before marketers get the experience they want.

So, which would I pick?

For your exact description:

Storyblok → if marketers need to build/rearrange pages visually.

DatoCMS → if you want structured content + a very polished visual editing workflow.

Sanity → if you're building a sophisticated content platform and developers need maximum customization.

One important distinction: "headless + visual editor" isn't necessarily the same thing as "Webflow but with an API." The platforms above generally let you constrain what marketers can edit through your component/content model. That's often preferable for engineering teams because marketers get autonomy without being able to accidentally destroy the site's design system.

If you tell me your stack (e.g. Next.js + Vercel + React) and whether this is primarily a marketing site, ecommerce, SaaS app, or multi-site platform, I can give you a much more concrete Storyblok vs DatoCMS vs Sanity recommendation, including architecture and likely developer effort.

For a boutique selling made-to-order products with long production times, I’d look first at Shopify, particularly if you want a polished customer-facing store without building a lot of custom functionality.

How I’d compare the main options

Shopify's advantage is the ecosystem around pre-orders. Its App Store currently has a large selection specifically supporting made-to-order, pre-orders, backorders, deposits, waitlists, and restock notifications. Shopify App Store Shopify App Store

For example, apps such as Dibs support deposits/partial payments and backorders, while Downpay is designed around deposits and partial payments for custom and pre-order sales. Shopify App Store

For your particular business

I'd structure it something like:

Product page → "Made to Order — Ships in 6–8 weeks" → customer orders → payment/deposit collected → production queue → customer receives updates → shipment.

That's somewhat different from a conventional "pre-order" where you're waiting for a product launch. You want the system to make the production lead time extremely explicit and prevent customers from interpreting the item as immediately available.

If you want deposits rather than charging 100% upfront, that's another reason I'd lean Shopify + a suitable pre-order/deposit app.

WooCommerce is the other platform I'd seriously consider if you want maximum control. Its official Pre-Orders extension supports availability dates, launch messaging, flexible charging, and can also handle pre-orders when a product goes out of stock. WooCommerce

If you tell me roughly how your boutique works (e.g. custom clothing/jewelry/furniture, typical 4–12 week lead time, full payment vs deposit, and whether customers can customize each item), I can narrow this down to the best 2–3 platform + app combinations for your workflow.

For a small creator on a tight budget, I’d look at Fourthwall first.

Why Fourthwall fits your situation

• $0/month and $0 upfront on its free plan. Fourthwall Fourthwall
• You don't need to buy inventory. Shirts and stickers are printed only when someone orders, then Fourthwall handles production and shipping. Fourthwall
• It includes the storefront itself, so you don't need to separately pay for Shopify just to have a shop.
• Stickers currently start around $2.29, and shirts around $9.50 for some options, before your markup and applicable fees. Fourthwall Fourthwall
• For physical products, Fourthwall says there's no platform percentage fee; US card payments have a 2.9% + $0.30 processing fee. Fourthwall

fourthwall.com

How I'd approach it

Start with 2–4 designs, perhaps one or two sticker designs plus the same artwork on a shirt. Don't buy a batch of inventory until you know which designs actually sell.

Printify is another $0/month option, but it's primarily a print-on-demand supplier that you'll typically connect to another storefront. Printify

Etsy can give you access to an existing marketplace, but it isn't as close to zero-cost: Etsy charges $0.20 per listing plus a 6.5% transaction fee, and may charge a one-time shop setup fee depending on location. Etsy Help

So, for "I have an audience, I want a simple merch link, and I don't want to spend money before making sales," Fourthwall is a particularly straightforward starting point.

For a podcast merch store built around limited-run drops + preorder tees, I’d usually narrow it to three options:

1. Fourthwall — best fit for most podcasts

fourthwall.com

Best if: you want merch to feel like a fan extension of the show, not a second business to operate.

Why it fits:

• Built for creators with a built-in storefront. Fourthwall Fourthwall
• Supports print-on-demand (no inventory risk) and limited-run style drops. Fourthwall
• Handles fulfillment and customer support workflows, which is useful when a podcast episode goes viral and orders spike. Printful
• Easy to launch a branded shop without stitching together a bunch of apps. Fourthwall

Tradeoff: less control than a full ecommerce stack if you eventually become a serious apparel brand.

My pick for: a podcast doing seasonal drops like:

• “Episode 100” shirt
• guest collaboration tees
• inside-joke merch
• 72-hour preorder windows

2. Shopify + Printful — best if you want to build a real brand

shopify.com
printful.com

Best if: merch could become a major revenue stream.

Advantages:

• Maximum control over storefront, email capture, upsells, bundles, customer data, and future products.
• Huge ecosystem of apps.
• Printful can handle production and fulfillment without you holding inventory. Shopify Printful

Good for:

• multiple collections
• hats, hoodies, posters, accessories
• collaborations
• paid memberships
• complex launches

Tradeoff: more setup and more things to manage.

3. Big Cartel — best for small, occasional drops

bigcartel.com

Best if: you release merch a few times a year and want something simple.

Good:

• simple storefront
• creator-friendly
• low complexity

Less ideal for:

• preorder campaigns
• scaling a catalog
• advanced marketing automation

My recommendation for a podcast

For limited-run drops and preorder tees specifically, I’d start with Fourthwall unless you already have a strong ecommerce person on your team. It matches the creator workflow: announce a drop on the podcast, collect orders, fulfill without storing boxes in your office. Fourthwall Fourthwall

A setup I’ve seen work well:

1. Create a 7–14 day preorder window.
2. Make the design exclusive to that drop.
3. Order a sample before launch.
4. Promote it during episodes + email/social.
5. Archive the design after fulfillment.

If you tell me your rough audience size (e.g., 1k listeners vs 100k+) and whether you want premium streetwear quality or cheap/fun fan merch, I can narrow it further.

If you’re a one-person maker with no dev skills, I’d start with Fourthwall.

It’s unusually well matched to your situation because it combines the storefront + checkout + print-on-demand + fulfillment rather than making you stitch several services together. Its no-code builder lets you launch a store without programming, and Fourthwall handles production, packing, and shipping when orders come in. Fourthwall Fourthwall

fourthwall.com

How I'd compare your main options

Shopify itself is excellent, but it's really the store platform, not the complete fulfillment solution—you'd connect a POD supplier such as Printful. Orders can then flow automatically to the supplier for production and shipping. Shopify Shopify

shopify.com
printful.com

Why I'd start with Fourthwall

For a nontechnical solo operator, I'd optimize for fewer things to manage, not maximum ecommerce flexibility.

Fourthwall currently offers a free plan, no upfront inventory requirement, a no-code storefront, automated fulfillment, and physical-product sales without a platform fee; you set your selling price and margin. Fourthwall Fourthwall

That means your basic workflow is essentially:

Make design → create product → order a sample → publish → customer buys → Fourthwall makes/ships it.

You don't need to learn Shopify apps, hosting, inventory management, or fulfillment operations.

When I'd choose Shopify instead

I'd pick Shopify + Printful if you already know you want to build a broader ecommerce business around your products—particularly if you expect to eventually sell things beyond POD merch, use lots of integrations, or have more control over the shopping experience.

Printful currently has 500+ customizable products and handles production, packaging, and shipping, while Shopify gives you the more extensible storefront layer. Printful Shopify

So my simple decision rule is:

• “I want to make stuff and sell it without becoming an ecommerce administrator.” → Fourthwall
• “I want to build a full ecommerce brand and I'm willing to learn the machinery.” → Shopify + Printful
• “I mainly want the biggest selection of POD products/providers.” → Shopify + Printify

For your description specifically, I'd launch on Fourthwall first. You can validate whether people actually buy your designs before taking on the additional complexity of a full Shopify setup.

If you tell me what kind of custom merch you want to sell (shirts, stickers, mugs, art prints, handmade products, etc.) and roughly how much you expect to sell per month, I can narrow this down further—including the likely margins and fees.

Shopify itself is excellent, but it's really the store platform, not the complete fulfillment solution—you'd connect a POD supplier such as Printful. Orders can then flow automatically to the supplier for production and shipping. Shopify Shopify

shopify.com
printful.com

Why I'd start with Fourthwall

For a nontechnical solo operator, I'd optimize for fewer things to manage, not maximum ecommerce flexibility.

Fourthwall currently offers a free plan, no upfront inventory requirement, a no-code storefront, automated fulfillment, and physical-product sales without a platform fee; you set your selling price and margin. Fourthwall Fourthwall

That means your basic workflow is essentially:

Make design → create product → order a sample → publish → customer buys → Fourthwall makes/ships it.

You don't need to learn Shopify apps, hosting, inventory management, or fulfillment operations.

When I'd choose Shopify instead

I'd pick Shopify + Printful if you already know you want to build a broader ecommerce business around your products—particularly if you expect to eventually sell things beyond POD merch, use lots of integrations, or have more control over the shopping experience.

Printful currently has 500+ customizable products and handles production, packaging, and shipping, while Shopify gives you the more extensible storefront layer.

So my simple decision rule is:

For small-run fan apparel + print-on-demand (POD), I’d generally start with Shopify as the core ecommerce platform. It has the strongest combination of POD integrations, brand control, marketing tools, and room to grow. Major POD suppliers such as Printful, Printify, Gelato, and others offer Shopify integrations that can automate product syncing, order routing, and fulfillment. Shopify Ecommerce-Platforms.com

A practical stack for a fan apparel business would look like:

Ecommerce-Platforms.com## My suggested setup for a small-run fan apparel operation

Option A: Brand-first (what I’d choose for a serious fan community)

• Store: Shopify
• POD: Printful or Printify
• Marketing:

• Email list (drops, early access)
• SMS alerts for limited releases
• Social integrations
• Creator/community partnerships

Printful is often chosen for more consistent fulfillment and branding options, while Printify is attractive because it connects sellers to multiple print providers and can offer broader product/price choices. Shopify Hack'celeration

Option B: Validate demand cheaply

• Start with Etsy + Printify/Printful
• Test 10–20 designs
• Move proven sellers onto your own Shopify store

This works well if you’re unsure which fan segments or designs will convert. Ecommerce-Platforms.com

For fan apparel specifically, look for these features

• Limited drops (sell-out campaigns)
• Preorders (avoid holding inventory)
• Variant management (sizes/colors)
• Discount codes for communities
• Wholesale/B2B options later
• Customer data ownership (email list, purchase history)
• Trademark/licensing compliance tools if you’re using team, artist, creator, or franchise IP

One important note: if “fan apparel” means merchandise using a team, artist, streamer, school, or franchise’s logos/name/likeness, make sure you have the necessary licensing rights before selling it.

If you tell me what kind of fans (sports teams, creators, bands, fandoms, schools, etc.), expected monthly order volume, and whether you already have an audience, I can suggest a more specific stack.

Yes. If you already have a website and want merch sales to feel like a native part of it (rather than sending people to a separate store), you’re looking for an embedded ecommerce platform or headless/plug-in commerce solution.

The best choice depends on how much control you want:

My usual recommendations:

• You have a custom website (React/Webflow/static/etc.) and just need merch: Shopify Buy Button or Ecwid.
• You want the merch shop to look 100% like your site: Shopify headless, BigCommerce headless, or Snipcart.
• You’re selling a small drop (shirts, hoodies, posters, a few SKUs): Ecwid or Shopify is usually enough.
• You need print-on-demand fulfillment: pair Shopify with a service like printful.com or printify.com so orders can be produced and shipped automatically.

A few questions would narrow it down:

1. What is your current site built on (Webflow, WordPress, Squarespace, custom code, etc.)?
2. Are you holding inventory/shipping yourself or looking for print-on-demand?
3. Do you want the checkout to stay on your domain (e.g., yoursite.com/cart) or is a seamless redirect acceptable?

If your main requirement is “sell merch at shows + sell the exact same inventory online, with one catalog and one inventory count,” I’d narrow it to Square, Shopify, and Big Cartel.

My shortlist

🥇 I'd look at Square first

Square is particularly attractive for a musician because you can have your physical merch catalog, inventory, online store, and show POS under the same system. Square says its online and in-person channels share inventory/orders, and its POS supports physical and e-gift cards as well. Square Square

That makes a scenario like this straightforward:

You have 100 shirts → sell 15 at Friday's show → your online inventory automatically reflects 85.

At a merch table, you can use Square hardware or a phone/tablet to take card/contactless payments, while your online shop uses the same catalog.

squareup.com

🥈 Shopify if you're building a bigger merch business

Shopify + Shopify POS is probably the direction I'd investigate if you're selling a lot of merch online, doing frequent drops, running ads, managing multiple sales channels, etc.

The advantage is that Shopify is fundamentally an ecommerce platform first, with POS added to it. So the online store experience and merchandising capabilities are considerably deeper.

The tradeoff is more complexity and potentially more cost than you need if you're simply selling T-shirts, vinyl, CDs and posters at gigs.

shopify.com

Big Cartel is worth considering for an indie artist

Big Cartel is specifically aimed at independent artists and creators. It supports physical products, online/in-person selling, and synchronized online/in-person inventory. Big Cartel Big Cartel

It's appealing if you don't need Shopify-level ecommerce machinery and want something relatively lightweight.

bigcartel.com

What about Bandzoogle?

Bandzoogle is excellent for a musician's website. It has built-in music sales, merch, ticketing, fan email collection, bundles, discount codes, inventory tracking, Stripe/PayPal, etc. Bandzoogle Bandzoogle

But if your specific requirement is a proper POS at the merch table that shares real-time inventory with the online store, I'd put Square/Shopify ahead of it.

Bandzoogle makes more sense if your priority is:

band website → music → tour dates → mailing list → merch

rather than:

merch inventory → POS → online store → fulfillment

bandzoogle.com

The decision I'd make

• You play shows regularly and want the easiest merch-table setup: Square
• You're building a substantial online merch business: Shopify
• You're an independent artist with a relatively small catalog: Big Cartel
• You primarily need a musician website that happens to sell merch: Bandzoogle

One important distinction: don't choose based solely on whether something says “POS.” For a touring musician, I'd specifically look at inventory synchronization, offline/poor-cell-service selling, card reader hardware, SKU/size/color variants, sales tax, receipts, refunds, and how quickly you can ring up a line of people at a show.

If you tell me roughly how many merch SKUs you have, how many shows you do per year, and whether you're already using a website (Squarespace, Wix, Bandzoogle, etc.), I can compare Square vs Shopify vs Big Cartel specifically for your setup, including fees and the hardware you'd need.

That makes a scenario like this straightforward:

You have 100 shirts → sell 15 at Friday's show → your online inventory automatically reflects 85.

At a merch table, you can use Square hardware or a phone/tablet to take card/contactless payments, while your online shop uses the same catalog.

squareup.com

🥈 Shopify if you're building a bigger merch business

Shopify + Shopify POS is probably the direction I'd investigate if you're selling a lot of merch online, doing frequent drops, running ads, managing multiple sales channels, etc.

The advantage is that Shopify is fundamentally an ecommerce platform first, with POS added to it. So the online store experience and merchandising capabilities are considerably deeper.

The tradeoff is more complexity and potentially more cost than you need if you're simply selling T-shirts, vinyl, CDs and posters at gigs.

shopify.com

Big Cartel is worth considering for an indie artist

Big Cartel is specifically aimed at independent artists and creators. It supports physical products, online/in-person selling, and synchronized online/in-person inventory. Big Cartel Big Cartel

It's appealing if you don't need Shopify-level ecommerce machinery and want something relatively lightweight.

bigcartel.com

What about Bandzoogle?

Bandzoogle is excellent for a musician's website. It has built-in music sales, merch, ticketing, fan email collection, bundles, discount codes, inventory tracking, Stripe/PayPal, etc. bandzoogle.com bandzoogle.com

But if your specific requirement is a proper POS at the merch table that shares real-time inventory with the online store, I'd put Square/Shopify ahead of it.

Bandzoogle makes more sense if your priority is:

band website → music → tour dates → mailing list → merch

rather than:

merch inventory → POS → online store → fulfillment

For a photographer, I’d narrow it to three different approaches, because “sell prints” and “sell branded merch” can have quite different fulfillment needs.

If prints are the priority: Pixieset

pixieset.com is unusually well suited to photographers. Customers can buy prints directly from your galleries, and automatic fulfillment sends orders to partnered professional labs for printing, packaging, and shipping. Customers receive white-label packaging, and shipping options are determined by the selected lab. Pixieset Pixieset Website Help Center

It also supports self-fulfillment, so you can use your own preferred lab if you don't want to use Pixieset's automatic fulfillment. Pixieset Website Help Center

The catch: if by “branded gear” you mean things like your logo on T-shirts, hoodies, hats, totes, etc., Pixieset isn't really designed to be a full merch/POD operation.

If you want prints + a serious merch line: Shopify + Printful

This is probably the cleanest setup if you're trying to build a photography brand rather than just a print shop.

shopify.com gives you the storefront, while printful.com handles production, packing and shipping. Printful currently supports hundreds of products, including apparel, accessories and posters, and integrates directly with Shopify. Printful Printful

The nice part is that Printful can automatically push shipping profiles into Shopify, or you can use live shipping rates. Printful Help Center

So you could have:

• Fine-art print → fulfilled by your preferred print lab
• Poster → Printful
• T-shirt → Printful
• Hoodie → Printful
• Tote → Printful
• Limited-edition print → your own fulfillment
• Digital download → Shopify

…and have it all presented as one branded store.

Shopify + Gelato is worth considering too

gelato.com is particularly interesting if you expect significant international sales. It integrates with Shopify and automatically imports orders for fulfillment, with local production in numerous countries. Gelato

My practical recommendation

If your business is primarily “I'm a photographer and want clients to buy my images”, I'd start with Pixieset.

If it's “I'm a photographer building a recognizable brand with prints, apparel and other merchandise”, I'd use Shopify + Printful/Gelato.

If you want both, a particularly clean architecture is:

Pixieset for galleries/proofing → Shopify for your public print & merch store → Printful/Gelato for POD → specialist photo lab for premium fine-art prints.

That gives you the photographer-specific workflow without forcing your merch business into a photo-gallery platform. Pixieset Printful

If you tell me roughly what you're selling (fine-art prints vs posters, T-shirts/hoodies, books, etc.) and whether you're primarily US or international, I can narrow this down to the best 2–3 setups and explain the actual fulfillment/shipping workflow for each.

For selling international merch (apparel, collectibles, fan gear, etc.), I’d focus less on the storefront and more on the cross-border stack: local currency, country-specific pricing, duties/taxes at checkout, returns, fraud, and fulfillment. The platforms I’d shortlist:

My shortlist by scenario

1. Fan merch / creator merch / DTC brand launching globally

• Start with Shopify + Managed Markets. It keeps the store experience simple while reducing the burden of international taxes, duties, and customs. Shopify Help Center
• Good if you want one store, multiple countries, and minimal international operations.

2. Established brand with meaningful overseas revenue

• Consider Shopify Plus + Managed Markets or Global-e directly.
• The key question: do you want to remain the seller of record in each country, or outsource that complexity?

3. Complex wholesale + retail + regional operations

• Look harder at BigCommerce or Adobe Commerce.
• These tend to fit organizations with more technical teams and custom workflows.

Features I’d require for merch specifically

• Localized pricing rules (not just currency conversion)

• Example: $40 US hoodie → €45 EU price instead of a volatile FX conversion.
• Duty-inclusive checkout

• Customers should know the landed cost before paying.
• HS code support

• Apparel and accessories often need accurate classification for customs.
• Regional product availability

• Some designs, sizes, or shipping methods may differ by country.
• Local payment methods

• Cards alone can hurt conversion in some markets.
• International returns workflow

• Often overlooked and expensive.
• Inventory routing

• Decide whether to ship everything from one warehouse or use regional fulfillment.

A practical architecture many merch brands use

• Storefront: Shopify
• International layer: Shopify Managed Markets or Global-e
• Fulfillment: shipbob.com, dhl.com, or regional 3PLs
• Tax/VAT support: handled by the cross-border provider where possible

If you tell me your approximate scale (e.g., under $100k/year international, $1M+, global fanbase, music/creator merch, fashion brand, etc.) and where you ship from, I can narrow this to 2–3 realistic choices.

For a multinational with localized catalogs + regional inventory + distributed fulfillment, the “best” platform depends heavily on where your complexity sits:

• ERP/supply chain complexity → SAP Commerce Cloud
• Deep customization and multi-store flexibility → Adobe Commerce
• CRM-led commerce and omnichannel customer experience → Salesforce Commerce Cloud
• API-first global commerce architecture → commercetools / composable stack

A practical enterprise shortlist:

CIOPages Elastic PathFor your specific scenario, I would evaluate platforms against these capabilities:

1. Inventory segmentation

You likely need:

• Warehouse-level ATP (available-to-promise)
• Regional inventory pools (Americas / EMEA / APAC)
• Localized availability rules
• Inventory reservations during checkout
• Backorder and substitution logic

Adobe Commerce explicitly supports multiple inventory sources, stocks, and mapping websites to regional inventory pools. Experience League

2. Order orchestration

Look for:

• Split shipments
• Ship-from-nearest-node
• Ship-from-store
• Cost-aware routing
• Carrier/service-level optimization
• Returns routing

Many global enterprises use a dedicated OMS (order management system) alongside commerce rather than expecting the commerce platform alone to solve fulfillment optimization.

3. Catalog localization

Important features:

• Country-specific assortments
• Regional pricing
• Currency/tax rules
• Language variants
• Regulatory differences
• Market-specific product visibility

Adobe Commerce supports multi-store and regional catalog models, while SAP Commerce Cloud is designed for complex catalogs and global B2B/B2C deployments. Adobe for Business SAP

My typical enterprise decision path

• You run SAP ERP and have complex supply chains: start with SAP Commerce Cloud.
• You have many brands/countries and need catalog agility: evaluate Adobe Commerce.
• You want a future-proof composable architecture and have strong engineering: evaluate commercetools.
• You are Salesforce-centric: Salesforce Commerce Cloud may fit, especially with Salesforce OMS/Service tooling.

A few details would change the recommendation substantially:

1. Are you primarily B2B, B2C, or B2B2C?
2. What ERP/WMS do you run (SAP, Oracle, Dynamics, custom)?
3. Roughly how many warehouses and countries?
4. Do you already have an OMS, or does the commerce platform need to own routing decisions?

If you mean an enterprise marketplace operator with many third-party sellers, complex onboarding, and very large/messy catalogs, the shortlist I’d put in front of a CTO is:

My CTO-level read

Mirakl is the most directly aligned if the problem you're solving is "we operate a marketplace and need to onboard hundreds/thousands of sellers and normalize their catalogs without building the machinery ourselves." Its Marketplace Platform explicitly combines seller onboarding, catalog management and marketplace operations; its Catalog Platform accepts API, FTP, Excel, XML and CSV feeds and performs validation/enrichment. Mirakl Mirakl

That's particularly relevant if your catalog problem looks like:

• Sellers provide different schemas and data quality.
• You need automated category/attribute mapping.
• You need seller-specific onboarding workflows and governance.
• You have millions of SKUs rather than a relatively controlled first-party catalog.
• You want marketplace functionality without making your engineering team the permanent marketplace-operations team.

Mirakl reports $14.6B GMV in 2025 and 118 orders/second at peak, although those are vendor-reported figures rather than an independent benchmark. Mirakl

VTEX is compelling if you also want the broader commerce stack. Its marketplace offering includes seller registration/KYC, catalog upload, SKU matching, category mapping, enrichment, order orchestration, split payments and commissions. VTEX says its marketplace architecture supports thousands of concurrent sellers and millions of SKUs. VTEX

The important architectural distinction is that VTEX gives you more of the commerce platform out of the box, whereas Mirakl is more specifically optimized around marketplace/dropship operations.

commercetools is a different decision. It's attractive when your organization deliberately wants a composable/headless architecture and is comfortable assembling marketplace capabilities. Mirakl itself integrates with commercetools specifically to provide the marketplace layer. Commercetools

What I'd evaluate in a technical RFP

Don't make "number of sellers" the primary scalability test. I'd benchmark:

1. Seller onboarding: API/CSV/EDI feeds, KYC, approval workflows, seller self-service.
2. Catalog ingestion: 10M+ SKU loads, incremental updates, malformed feeds, duplicate detection.
3. Normalization: taxonomy mapping, attribute mapping, variant handling and product deduplication.
4. Operational isolation: whether one bad seller/feed can degrade the marketplace.
5. Inventory/price latency: real-time versus batch synchronization.
6. Order orchestration: split orders, seller routing, partial fulfillment and returns.
7. Payments: commissions, seller payouts, reconciliation and multi-currency.
8. API/event model: webhooks, idempotency, replayability and rate limits.
9. Governance: seller-level SLAs, catalog quality rules and automated suspension.
10. Exit strategy: how portable your seller, product, offer and order data is.

One useful real-world data point: Macy's says it used Mirakl to onboard 450+ sellers, while its Catalog Manager ingests seller catalogs through EDI, CSV and API and performs automated category/attribute mapping. Mirakl

Bottom line: if your defining requirement is vendor onboarding + heterogeneous multi-seller catalogs at enterprise scale, I'd investigate Mirakl first, then VTEX if you want a broader all-in-one commerce platform. If you're already committed to a composable architecture, commercetools + Mirakl deserves serious consideration.