Answers that name a competitor

For an enterprise catalog with thousands of SKUs, complex pricing, and likely B2B workflows, I would focus less on “which ecommerce platform has the most features” and more on how well it handles:

• customer-specific pricing and contract pricing
• multiple price lists
• large product attribute models
• ERP/PIM integration
• buyer permissions and account hierarchies
• quote/RFQ workflows
• bulk ordering and repeat purchases
• regional catalogs, currencies, and inventory rules

Complex B2B catalogs often need these capabilities natively rather than through many custom extensions. Elastic Path Webscale

Platforms I would shortlist

Shopify Alkali## My likely recommendations by scenario

If you are a distributor/manufacturer

Look hardest at:

1. Adobe Commerce
2. OroCommerce
3. SAP Commerce Cloud (especially if SAP ERP is central)

These are stronger when your pricing model looks like:

• Customer A gets negotiated prices
• Customer B sees a different catalog
• Volume breaks change pricing
• Sales reps negotiate quotes
• Buyers have approval chains

Alkali Ivris Tech### If your catalog is huge but you want flexibility

Consider:

• commercetools
• Elastic Path

These work well when commerce is one layer in a broader architecture with ERP, PIM, search, pricing engines, and custom customer experiences. Elastic Path

If you want faster implementation and lower operational overhead

Consider:

• BigCommerce
• Shopify Plus

They can be excellent choices if your pricing complexity is manageable and you value SaaS simplicity. Shopify

Questions that would narrow this down quickly

1. Is this primarily B2B, B2C, or both?
2. How many SKUs: ~5,000, 50,000, 500,000+?
3. Where does pricing live today: ERP, CPQ system, spreadsheets, ecommerce platform?
4. Which ERP/PIM do you use (SAP, Oracle, NetSuite, Dynamics, Infor, custom)?
5. Do customers need login-based catalogs with negotiated pricing?
6. Are you replacing an existing platform or starting fresh?

With those answers, the shortlist usually shrinks from ~8 platforms to 2–3 realistic candidates.

If you’re launching a subscription box, I’d start with Shopify + a dedicated subscription app rather than trying to make a general ecommerce platform handle recurring orders by itself.

My shortlist

• shopify.com — Best if you want the simplest/lowest-complexity launch. It integrates directly with Shopify Payments and keeps subscriptions inside Shopify Admin. Shopify
• rechargepayments.com — My pick if subscriptions are the core of your business. It has strong recurring-order infrastructure, integrations, customer management, and fulfillment workflows. Shopify's current subscription-app guidance lists Recharge among its leading options. Shopify Shopify App Store
• appstle.com — Worth considering for a startup that wants subscription boxes, bundles, and recurring billing without jumping immediately to a more expensive subscription platform. Its Shopify listing specifically supports subscription boxes and bundles. Shopify App Store
• skio.com — Strong if subscriber experience and retention are especially important. Its current Shopify offering includes Build-a-Box, automated journeys, payment recovery, and a no-code customer portal. Shopify App Store

For your particular business

If you're shipping a physical box every month, I'd rank them:

The key thing I'd investigate before choosing is how the subscription app creates and passes recurring orders to your fulfillment provider/3PL. You don't want billing to work beautifully while your warehouse has to manually reconcile subscription orders.

If you tell me (1) what you're selling, (2) expected subscribers in year 1, (3) whether you're using a 3PL or shipping yourself, and (4) your approximate box price, I can narrow this down to the best 1–2 options and compare their likely costs.

For an international store where multi-currency + localized checkout are core requirements, I’d recommend Shopify, specifically Shopify Markets.

My ranking

1. Shopify — best overall

• Strong native internationalization through Shopify Markets.
• Customers can browse and check out in local currencies; Shopify supports 130+ currencies for international selling. Shopify
• Market-specific pricing, products, domains/URLs, languages, and regional address forms are built into the platform. Shopify Shopify
• Particularly attractive if you're selling DTC and want to launch new countries without maintaining separate stores.
• If you're eligible, Shopify Managed Markets can also handle much of the cross-border tax, duty, and import complexity. Shopify
• BigCommerce — best if you need more structural flexibility

• Excellent multi-storefront capabilities for genuinely different country sites.
• Supports localized catalogs, currencies, pricing, checkout, payments, and content per storefront. BigCommerce BigCommerce
• Its current Stripe integration is particularly interesting: Stripe Adaptive Pricing supports local-currency checkout across 150+ countries. BigCommerce
• I'd consider it ahead of Shopify if you have complex catalogs, B2B requirements, or substantially different operations by country.
• Adobe Commerce / Magento — best for highly customized enterprise setups

• Powerful, but I'd only choose it if you have a strong engineering team and genuinely need that degree of customization. For most international stores, it's considerably more operationally heavy than Shopify.

The important distinction

If by "localized checkout" you mean:

Customer sees EUR/GBP/JPY/etc., gets appropriate address fields, local payment methods, localized language, and completes checkout without feeling like they're buying from a foreign store

then Shopify is probably the easiest path.

If you mean:

France, Germany, Japan, and the US each need materially different catalogs, pricing rules, payment providers, checkout behavior, tax logic, and storefront experiences

then I'd put BigCommerce much closer to Shopify, and potentially choose it.

My default choice: Shopify Markets. It gives you the best combination of international functionality, ecosystem, checkout quality, and relatively low implementation complexity. Shopify Shopify Help Center

shopify.com

If you tell me your home country, target countries, expected order volume, and whether you're B2C or B2B, I can narrow this down to Shopify vs. BigCommerce and recommend the exact setup.

If your primary goal is minimizing PCI compliance effort and security operations, a fully hosted SaaS ecommerce platform is usually the best choice. The platform should handle the infrastructure, checkout security, patching, and payment environment so your team focuses on merchant-side controls (accounts, apps, policies, and access). LeadingIT Shopify

A practical ranking for lowest compliance burden:

BigCommerce WooCommerce## My recommendation by priority

If you want the least compliance overhead: Shopify

Shopify is usually the easiest route because it is a fully managed platform: hosting, infrastructure security, SSL, and payment handling are largely handled by Shopify. Your responsibilities are mainly operational:

• Use strong admin passwords and MFA
• Limit staff access
• Vet installed apps
• Avoid storing cardholder data yourself
• Complete any required PCI self-assessment steps for your payment setup

Shopify Shopify### If you need more enterprise commerce features: BigCommerce

BigCommerce is also a strong choice for reducing operational burden. It provides hosted infrastructure and PCI DSS compliance support while giving merchants more native features for catalogs, B2B, and international selling. BigCommerce BigCommerce

If compliance simplicity matters more than customization: avoid self-hosted WooCommerce

WooCommerce can be secure, but the responsibility is more distributed: hosting, WordPress security, plugin updates, vulnerability management, backups, and configuration all become part of your compliance program. WooCommerce

Features that reduce PCI scope regardless of platform

Look for:

• Hosted checkout (avoid handling raw card numbers)
• Tokenized payments
• Built-in MFA and role-based permissions
• Automatic security updates
• Minimal third-party plugins/apps
• Clear PCI documentation and Attestation of Compliance (AOC)

A common “low-burden” setup is:
Shopify + Shopify Payments (or another hosted PCI-compliant gateway) + minimal apps + MFA enforced for all admins. Shopify

If you tell me your size (startup, SMB, enterprise), whether you need B2B features, and whether you have an IT/security team, I can narrow this to a shortlist.

If your priority is “I want to host it myself and customize absolutely everything”, I would avoid most traditional hosted-style solutions and focus on platforms with clean codebases and APIs. The best choice depends on how much you want to build yourself. Open Source Projects WPBundle

My recommendations:

1. Medusa — Best overall for a fully custom store

Best for: developers who want a Shopify-like backend but complete frontend freedom.

Stack:

• Backend: Node.js + TypeScript
• Frontend: usually Next.js/React (but can be anything)
• Database: PostgreSQL
• Deployment: Docker-friendly

Why I like it:

• Modern architecture
• Very customizable checkout, pricing, inventory, fulfillment logic
• No forced theme system
• Great if you want a unique shopping experience
• Easier for modern web developers than older PHP platforms

Downsides:

• You build more yourself
• Smaller plugin ecosystem than WooCommerce
• Requires development skills

Choose Medusa if your vision is something like:

“I want my store to work exactly how I imagine, not how a template expects.”

Open Source Projects WPBundle

2. WooCommerce — Best if you want the biggest ecosystem

Best for: getting a powerful store running quickly while still owning the code.

Advantages:

• Huge plugin ecosystem
• Tons of payment/shipping integrations
• Easy admin experience
• WordPress gives you blogging, SEO, landing pages, and content tools

Downsides:

• WordPress architecture can become messy with many plugins
• Deep customization often means working around existing conventions
• Less elegant for highly custom commerce logic

A good setup is:

• WooCommerce backend
• Custom React/Next.js frontend (“headless WooCommerce”)

That gives you WordPress’s ecosystem with a custom storefront. WPBundle

3. Saleor — Best for serious/enterprise builds

Best for: complex catalogs, multiple warehouses, international commerce.

Strengths:

• GraphQL-first
• Excellent API design
• Strong inventory and multi-channel features
• Built for large custom applications

Downsides:

• More complicated to operate
• Requires stronger engineering skills
• Probably overkill for a small store

WPBundle

4. Sylius — Best if you are a PHP/Symfony developer

Very flexible and clean, but more of a framework than a ready-made store.

Good for:

• Custom B2B commerce
• Complex workflows
• Developers who already use Symfony

OpenReplay Blog

5. PrestaShop — Best traditional self-hosted store

Good if you want:

• A complete store out of the box
• Product management
• Tax/shipping tools
• Less custom development

Less appealing if your goal is a completely unique experience.

Open Source Groups

My ranking for your stated goal

For a new project today, I would personally shortlist:

1. Medusa + Next.js + PostgreSQL → if you are building something unique
2. Headless WooCommerce + Next.js → if you need lots of existing integrations
3. Saleor + React → if you expect enterprise complexity

If you tell me your stack (Node/Python/PHP), expected product count, and whether you need subscriptions, marketplace features, or B2B pricing, I can narrow it down further.

For a new project today, I would personally shortlist:

1. Medusa + Next.js + PostgreSQL → if you are building something unique
2. Headless WooCommerce + Next.js → if you need lots of existing integrations
3. Saleor + React → if you expect enterprise complexity

If you tell me your stack (Node/Python/PHP), expected product count, and whether you need subscriptions, marketplace features, or B2B pricing, I can narrow it down further.

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

My ranking

Why I'd choose Shopify

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

The typical flow is:

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

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

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

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

When I'd pick something else

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

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

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

The typical flow is:

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

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

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

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

When I'd pick something else

If your main priority is having the broadest and easiest-to-manage supplier ecosystem, I’d choose shopify.com.

My ranking for a multi-supplier dropshipping business

Why Shopify wins

Shopify has an unusually deep ecosystem of supplier and sourcing apps. Its own recommendations include Shopify Collective, Syncee, DropCommerce, Spocket, and others, while the App Store has integrations for AliExpress, Alibaba, CJ Dropshipping, print-on-demand suppliers, wholesale suppliers, and more. Shopify Help Center Shopify App Store

For example, DSers provides AliExpress/Alibaba/1688 connectivity, multi-supplier/agent management, supplier mapping, automatic inventory/price/order updates, and multi-channel management. Shopify App Store

That matters if your model is something like:

Customer → Shopify → supplier/agent A, B, C, D → fulfillment → tracking back to Shopify

You can mix suppliers rather than being locked into one sourcing network.

Where BigCommerce becomes interesting

If you're building something much larger and more operationally complex, I'd seriously consider BigCommerce.

BigCommerce has a large app ecosystem and particularly strong APIs/webhooks for building custom supplier integrations. Its documentation specifically highlights real-time webhooks, APIs, app extensions, and an App Marketplace with hundreds of integrations. BigCommerce BigCommerce

It also supports dropshipping tools such as Avasam and Spocket. BigCommerce

So I'd frame it this way:

• Shopify: best if you want to connect lots of existing suppliers quickly.
• BigCommerce: best if you eventually want to build sophisticated/custom supplier infrastructure.
• WooCommerce: best if you want maximum technical control and don't mind managing more infrastructure.

One important distinction

If by "supplier ecosystem" you mean you want to build a platform where hundreds/thousands of suppliers themselves connect to your store/network, rather than simply operating a dropshipping store using suppliers, my answer changes somewhat.

In that case, I'd look closely at BigCommerce vs Shopify, particularly their APIs, webhooks, catalog/variant handling, inventory synchronization, order routing, and multi-store capabilities. Those become more important than simply counting the number of dropshipping apps.

If you tell me whether you're planning (1) one dropshipping store with many suppliers, (2) multiple stores, or (3) a marketplace/platform connecting suppliers to retailers, I can give you a much more specific recommendation.

Customer → Shopify → supplier/agent A, B, C, D → fulfillment → tracking back to Shopify

You can mix suppliers rather than being locked into one sourcing network.

Where BigCommerce becomes interesting

If you're building something much larger and more operationally complex, I'd seriously consider BigCommerce.

BigCommerce has a large app ecosystem and particularly strong APIs/webhooks for building custom supplier integrations. Its documentation specifically highlights real-time webhooks, APIs, app extensions, and an App Marketplace with hundreds of integrations.

If you sell mostly digital downloads with a smaller selection of physical products, I’d pick shopify.com for most sellers.

My ranking

1. Shopify — best overall

• Handles digital and physical products in the same store and checkout.
• Its free Digital Downloads app can automatically deliver PDFs, ZIPs, videos, etc., and supports files up to 5 GB. Shopify Shopify Help Center
• You can also attach a digital download to a physical product—for example, a physical workbook that includes a bonus PDF. Shopify Help Center
• Much easier to manage than building a WordPress/WooCommerce site if you don't want to deal with hosting and plugins.
• woocommerce.com — best for flexibility/control

• Excellent if you already use WordPress.
• Supports physical, virtual, downloadable, variable, and other product types. WooCommerce WooCommerce
• Very customizable, but you'll generally have more setup and maintenance than Shopify.
• bigcommerce.com — best for a larger operation

• Natively distinguishes physical and digital products and has strong catalog, inventory, and omnichannel capabilities. BigCommerce BigCommerce
• Probably more platform than you need if you're a solo/small seller.

What I'd choose for your situation

Shopify if you want something straightforward that can grow with you.

The particularly nice part for your business is that you don't need separate systems for your downloads and physical items. A customer can buy a physical item and a digital download in the same order, and Shopify can handle the digital fulfillment separately from the physical fulfillment. Shopify Help Center

If you tell me what kind of digital downloads you sell (PDFs, templates, artwork, courses, etc.), roughly how many physical products you have, and your monthly sales, I can tell you which platform I'd choose specifically—and whether Shopify's cost is justified for you.

For three retail stores with simple multi-location inventory, I’d shortlist these three:

My recommendation for your situation:

• If you have three stores, a modest SKU count, and want something easy for staff → Square for Retail is probably the best fit. It handles the basics: inventory by location, sales, online orders, and store reporting without much complexity. getstash.io
• If your website is the main growth channel and stores are extensions of ecommerce → Shopify + Shopify POS. technologyadvice.comtechnologyadvice.com
• If you have lots of SKUs, frequent transfers between stores, size/color variants, or need stronger purchasing workflows → Lightspeed Retail. technologyadvice.com

For a 3-location retailer, I’d usually avoid jumping to an ERP unless you have complex warehousing or wholesale needs.

A few questions would narrow it down:

1. Roughly how many products/SKUs do you carry (100, 1,000, 10,000+)?
2. Do all three stores sell the same products, or does each location have its own assortment?
3. Do you already have an ecommerce site (Shopify, WooCommerce, etc.)?

For a local brick-and-mortar shop, I’d narrow it to Shopify vs. Square Online. My default recommendation would be Shopify, but Square can be the better choice if the store already runs on Square POS.

My recommendation: Shopify

shopify.com is probably the best overall fit if you want the ecommerce operation to become an important sales channel.

It supports:

• In-store pickup and local delivery.
• Delivery zones based on radius or ZIP/postal codes.
• Different delivery prices by zone.
• Delivery instructions and customer notifications.
• A built-in local-delivery workflow, including route optimization through Shopify's Local Delivery app. Shopify
• A very large app ecosystem if you eventually need sophisticated delivery scheduling, driver tracking, route optimization, subscriptions, loyalty, etc. Shopify App Store

For example, if the shop sells $20–$200 products and wants customers to choose "Pick up at our store" or "Deliver within 10 miles" at checkout, Shopify handles that nicely.

When I'd choose Square instead

If the physical shop already uses Square for its cash register/POS, I'd seriously consider squareup.com instead.

Square has a particularly nice advantage for a local retailer: online and in-person sales can operate from the same ecosystem. Its online system supports in-store/curbside pickup and local delivery, including either your own employees doing deliveries or on-demand delivery through Square's delivery partners. Square Square

So I'd roughly rank them:

One important consideration

If local delivery is a major part of the business, I'd actually choose the platform partly based on the delivery workflow rather than just the ecommerce features.

For Shopify, there are apps such as Zapiet and EasyRoutes that add more sophisticated pickup/delivery scheduling and route management. Shopify App Store

For example, you might eventually want:

Customer enters address → system verifies they're in the delivery area → customer chooses Tuesday 4–6 PM → delivery fee is calculated → order appears on driver's route → customer gets tracking.

Shopify gives you a good foundation for that and lets you add the complexity as the business grows.

Bottom line:

• Starting from scratch: Shopify.
• Already using Square POS: Square Online.
• Delivery is a core part of the business: Shopify + a dedicated pickup/delivery app.
• Simple store, small catalog, minimal technical overhead: Square Online.

If you tell me what kind of shop it is, roughly how many products you have, whether you already use Square/another POS, and how far you deliver, I can recommend the specific setup—including the plan/apps I'd use and what it should cost.

Square has a particularly nice advantage for a local retailer: online and in-person sales can operate from the same ecosystem. Its online system supports in-store/curbside pickup and local delivery, including either your own employees doing deliveries or on-demand delivery through Square's delivery partners. api.squareup.com my.squareup.com

So I'd roughly rank them:

One important consideration

If local delivery is a major part of the business, I'd actually choose the platform partly based on the delivery workflow rather than just the ecommerce features.

For Shopify, there are apps such as Zapiet and EasyRoutes that add more sophisticated pickup/delivery scheduling and route management.

For example, you might eventually want:

Customer enters address → system verifies they're in the delivery area → customer chooses Tuesday 4–6 PM → delivery fee is calculated → order appears on driver's route → customer gets tracking.

Shopify gives you a good foundation for that and lets you add the complexity as the business grows.

Bottom line:

For a non-technical seller who wants to sell through social links and email, I’d generally rank the options like this:

1. Shopify — Best overall for social selling

shopify.com

Best if you want to grow beyond a few products.

Why it fits:

• Strong connections to business.instagram.com, facebook.com, TikTok, Pinterest, and other sales channels. Shopify Zapier
• Customers can go from a social post → product page → checkout quickly.
• Easy email capture with tools like Shopify Email or integrations with email platforms. HostAdvice
• Huge ecosystem if you later need reviews, subscriptions, bundles, SMS, or automation. Ecommerce-Platforms.com

Downside:

• It has more features, so the dashboard can feel busier than simpler website builders.

Good fit: Instagram/TikTok sellers, creators, product brands, handmade goods, dropshipping, growing businesses.

2. Wix — Easiest for beginners

wix.com

Best if you want a simple store and website together.

Why it fits:

• Very beginner-friendly drag-and-drop setup.
• Built-in marketing tools and social integrations.
• Good for sending people from Facebook, Instagram, or email newsletters to a clean storefront. HostAdvice

Downside:

• If your social selling becomes a major sales engine, Shopify usually gives you more specialized ecommerce tools. Ecommerce-Platforms.com

Good fit: Coaches, artists, local businesses, small catalogs, first-time sellers.

3. Squarespace — Best-looking storefront

squarespace.com

Best if your brand image matters most.

Why it fits:

• Beautiful templates.
• Good for email newsletters and content-driven selling.
• Simple product catalogs work well.

Downside:

• Social commerce integrations are generally less extensive than Shopify’s ecosystem. Zapier

Good fit: Photographers, designers, artists, premium small brands.

My recommendation for your situation

If your main plan is:

• “I’ll post on Instagram/Facebook/TikTok and send email offers” → choose Shopify.
• “I only have a few products and want the easiest setup” → choose Wix.
• “My brand is very visual and I sell occasionally” → choose Squarespace.

For a non-technical seller starting today, I’d lean toward Shopify + a simple email tool + social integrations because it gives you the easiest path from a social follower to a paying customer while leaving room to grow. Shopify Ecommerce-Platforms.com

A couple of details would change the recommendation:

1. Are you selling physical products, digital products, or services?
2. Which social channel matters most: Instagram, Facebook, TikTok, Pinterest, or email list?

For a small maker business selling both at markets/in person and through an online shop, I’d pick Square unless your online store is likely to become the main part of the business.

My recommendation: Square

squareup.com is probably the simplest starting point:

• $0/month for the basic POS, so you can start without another monthly software bill. Square Square
• Your in-person and online inventory stays synced, which is particularly useful when you make limited quantities of products. Square
• You can build a basic online store, accept payments, offer shipping/pickup, and sell in person from the same system. Square
• Hardware is relatively inexpensive: the basic Square Reader is currently $59, and Square Stand is $149. Square
• You can even take contactless payments directly on an iPhone/Android without buying hardware. Square

For a maker doing craft fairs, pop-ups, Instagram sales, and a modest web shop, that's a very attractive combination.

When I'd choose Shopify instead

shopify.com becomes my pick if you expect the online store to be the heart of the business.

Shopify's ecommerce tools are deeper, and its POS ties directly into the online Shopify store. But the entry-level Shopify plan is currently $39/month, with POS Pro costing another $89/month/location if you need its advanced retail features. Shopify

So I'd roughly think of it this way:

Bottom line: If you told me, "I make candles/jewelry/ceramics/art/etc., I do weekend markets, and I just need a nice little website where people can buy my stuff," I'd start with Square. You can always move to Shopify later if ecommerce becomes substantial.

If you tell me what you make, roughly how many products/SKUs you have, and whether most sales are currently at markets or online, I can narrow it down to the exact setup I'd use.

If advanced shipping rules + carrier-calculated rates are non-negotiable, I’d shortlist Shopify and BigCommerce, with BigCommerce generally the more flexible fit for complicated shipping logic.

• BigCommerce — strongest fit for complex rules. Its native Shipping Manager supports real-time carrier quotes plus flat-, weight-, and value-based rates, and it integrates with advanced tools such as ShipperHQ and Advanced Shipping Manager for more complicated rules. BigCommerce
• Shopify — easiest for a small team. It can pull live rates from carriers such as UPS, FedEx, and USPS based on weight, dimensions, and destination. Third-party carrier-calculated shipping is included on Advanced/Plus; Grow can add it for a fee or with annual billing. Shopify Help Center Shopify Help Center
• Shopify + a shipping-rules app can get considerably more granular—rules by product, weight, ZIP/postcode, quantity, zones, and blended rates are available through apps. Shopify App Store

My pick: If your rules are truly unusual—different carriers/products/origins, surcharges, exclusions, dimensional pricing, etc.—I'd lean BigCommerce. If your rules are moderately complex and you prioritize a simpler admin experience for a small team, Shopify is probably the better tradeoff.

If you tell me what your shipping rules actually are (e.g. “product A must ship alone, UPS Ground for these ZIPs, free shipping over $X, LTL for orders over Y lbs”), I can tell you which platform handles them natively and which requires an app.

Yes. For a business selling highly customized products, I’d evaluate ecommerce platforms differently from a normal store. The key question isn't just “does it support variants?” but whether it can handle conditional options, custom pricing, file uploads, personalization, dependencies between choices, and potentially a visual preview/configurator.

My shortlist

1. Shopify — probably the best starting point

Shopify has a very large ecosystem of product-option and configurator apps. Shopify's native system supports up to 3 options and 2,048 variants per product, but Shopify itself recommends apps or custom development when you need more than that. Shopify Shopify Help Center

The important advantage is that you don't necessarily have to make every customization a Shopify variant. Apps can collect additional information such as:

• Text personalization
• Engraving
• File/image uploads
• Checkboxes and add-ons
• Custom dimensions
• Conditional questions
• Additional charges
• Product personalization
• Visual previews

There are currently hundreds of product-variant/customization apps in the Shopify App Store. For example, Easify and Globo are among the heavily reviewed options. Shopify App Store

shopify.com

I'd choose Shopify if: you want to launch relatively quickly and your configurator can be implemented with an app plus some custom development.

2. BigCommerce — arguably better for complex native options

BigCommerce is particularly interesting for your use case because its product-options system is designed around more complicated configurations.

It supports things like product options, modifiers, option sets and conditional configuration, making it attractive for made-to-order and highly configurable products. TechnologyAdvice YouTube

For example, imagine you sell a custom desk:

Desk type → material → dimensions → edge style → legs → finish → cable management → engraving

You may not want every possible combination to become an actual SKU/variant. BigCommerce's option/modifier model can be a better fit for that kind of product.

bigcommerce.com

I'd choose BigCommerce if: your products have lots of options and you want the ecommerce platform itself to handle more of the configuration logic rather than depending entirely on apps.

3. WooCommerce — best for maximum configurator flexibility

WooCommerce is particularly compelling if your configuration logic is unusual.

WooCommerce itself doesn't provide sophisticated custom product options out of the box, but its plugin ecosystem is enormous. There are plugins for:

• Conditional logic
• Dynamic pricing
• Measurement-based pricing
• File uploads
• Product add-ons
• Composite products
• Custom formulas
• Advanced product configurators
• 2D/3D personalization

For example, current WooCommerce options plugins can provide unlimited fields, conditional logic and dynamic pricing. Barn2 Plugins

woocommerce.com

I'd choose WooCommerce if: your configurator is unusual enough that you expect significant custom programming.

4. Adobe Commerce — for serious enterprise configuration

Adobe Commerce is worth considering if you're dealing with a very large catalog, B2B customers, complicated pricing rules, ERP integration, etc.

It's powerful, but I wouldn't recommend it merely because you sell customized products. The development and maintenance burden is substantially higher.

business.adobe.com

The more important distinction: what kind of configurator do you need?

This is where I'd narrow the choice.

A. Simple product options

Example:

T-shirt → size → color → print → text

Shopify is excellent.

B. Complex option logic

Example:

Choose cabinet
→ choose width
→ width determines available doors
→ choose door style
→ door style determines hardware
→ choose hardware
→ add finish
→ price recalculates

I'd lean toward BigCommerce or WooCommerce, although Shopify can absolutely do this with the right app/custom development.

C. Measurement-based configuration

Example:

Enter width + height → calculate price → determine required components → generate order specifications.

I'd lean WooCommerce or a custom application, because the configuration engine becomes almost as important as the ecommerce platform.

D. Visual product personalization

Example:

Upload logo → position logo → choose color → see exactly what the finished product will look like.

I'd look at Shopify + a dedicated configurator, WooCommerce + configurator, or BigCommerce + configurator, rather than relying on native product options.

E. 3D configurator

Example:

Customer builds a sofa/car/window/product in 3D, rotates it, changes components, and sees the final product.

At this point, the ecommerce platform is almost secondary. I'd build/use a specialized configurator and integrate it with Shopify, BigCommerce, WooCommerce, or a headless storefront.

What I'd choose

For most customized-product businesses, my ranking would be:

🥇 Shopify + specialized configurator
Best combination of ecommerce infrastructure, app ecosystem, payments, checkout, marketing and ease of operation.

🥈 BigCommerce + custom/third-party configurator
Potentially better if your product catalog has very complicated option structures.

🥉 WooCommerce + advanced configurator
Best if configuration logic is unusual and you have technical resources.

🏢 Adobe Commerce
For large enterprise operations.

⚙️ Headless/custom
If the configurator itself is the heart of your product and you need complete control.

One important caveat: don't choose based on the number of “variants” a platform supports. For custom products, you often don't want thousands or millions of SKU combinations. You want a configuration engine that stores the customer's selections and calculates the correct price/specification.

If you tell me what you're selling and roughly what a customer has to configure (e.g. custom signs, furniture, apparel, jewelry, windows, printed products, etc.), I can narrow this down to 2–3 specific platforms + configurator apps, including which one I'd pick for your business.

Yes. For your mix of ready-to-ship products + made-to-order/custom work + preorders, I’d shortlist these:

• Shopify — best overall. Its core store handles ordinary inventory well, while preorder apps can add preorders, deposits, “ships by” dates, and made-to-order products. For example, Preorderly supports both pre-orders and made-to-order products and can display shipping dates. Shopify App Store Shopify Help Center
• Big Cartel — best for a very small artisan operation. It's specifically aimed at artists and makers and is simpler than Shopify. The catch is that you'll generally communicate custom/preorder lead times through product descriptions and policies rather than having sophisticated production scheduling built in. There are plenty of artisan Big Cartel stores successfully using this model. Shopify migration goods More Than Plenty Creations
• WooCommerce — best if you want maximum control. You can combine WooCommerce with preorder, product-options, and delivery-date extensions, but it's more hands-on technically.

What I'd choose for you

If you're one person or a tiny team, I'd lean:

Big Cartel if your custom work is relatively simple — e.g. “choose color/size/personalization, then I make it in 7–14 days.”

Shopify if you expect the made-to-order side to become a substantial part of the business, or you want customers to see things like “Preorder — ships approximately October 15”, collect deposits, handle different lead times by product, and automate more of the workflow. Shopify's preorder system explicitly supports taking payment before an item is ready, with preorder apps handling the customer-facing information. Shopify Help Center Shopify App Store

One important distinction: “custom lead time” can mean two different things. If you simply need Product A = ships in 3–5 days and Product B = made to order, ships in 2–3 weeks, that's easy. If you need customer chooses a custom option → that option changes production time → system calculates the resulting ship date, I'd favor Shopify/WooCommerce over Big Cartel.

If you tell me what you're making, roughly how many products you expect, and whether customers need to enter custom specifications, I can narrow this down to the best 2–3 options and compare their actual costs/features.

For a small handmade-goods shop on a tight budget, I’d start with squareup.com.

My picks

• 🥇 Square Online — best overall for $0/month

• Free plan has no monthly fee or startup cost.
• You can build a real storefront, add products, take payments, manage inventory, and offer shipping/pickup.
• You pay payment-processing fees when you actually make a sale. Square
• Best if you expect to have more than a handful of products.
• 🥈 Big Cartel — best if you only have a few products

• Its free Gold plan allows up to 5 products, with online selling and card/PayPal payments. Big Cartel Big Cartel
• It's particularly geared toward artists, makers, and independent creators. Big Cartel
• Great if you're launching with, say, 3–5 signature handmade items.
• 🥉 Etsy — best for getting discovered by existing shoppers

• You don't need to build much of a website yourself, and Etsy already has a marketplace audience.
• But it isn't really the cheapest store: listings cost $0.20 each, and Etsy charges a 6.5% transaction fee, plus payment-processing fees. Etsy Help
• I'd consider Etsy an additional sales channel, rather than your primary store, once you're ready.

What I'd do in your situation

Start with Square Online if you have more than 5 products. You can launch for $0/month and avoid paying for hosting or a fancy website while you figure out what actually sells.

If you're starting with just a handful of handmade products, I'd choose Big Cartel for its maker-focused simplicity.

I would not pay for Shopify yet. A monthly subscription makes more sense once your sales justify the added features.

If you tell me roughly how many products you expect to sell and whether you'll also sell at craft fairs/in person, I can tell you which one I'd pick specifically for your shop.

For a two-person startup testing product-market fit, I’d optimize for speed, low fixed cost, and not having to rebuild later.

My pick: Shopify

Shopify is probably the best default.

• $5/month Starter if you mainly need simple product links/checkout and are selling through social, email, or an existing site.
• $29/month Basic (annual billing) when you want a proper standalone storefront.
• Hosting, checkout, payments, inventory, orders, shipping integrations, etc. are all in one place.
• The big advantage for a startup is that you can start extremely lean but don't have to migrate platforms if you find PMF. Shopify Shopify

shopify.com

If minimizing cost is the #1 priority

Ecwid's $5 Starter plan supports up to 10 products, while Square has a free plan but charges higher payment fees. Big Cartel's free tier is limited to five products. Shopify Zapier

ecwid.com
squareup.com
bigcartel.com

What I'd do in your shoes

Start with Shopify Starter if you're still validating the product itself. Don't spend a week designing a beautiful store. Put up:

1. One strong landing/product page
2. 1–3 products
3. Stripe/Shopify Payments checkout
4. Basic analytics
5. A custom domain
6. A simple email capture

Then, once you're getting consistent sales, move to Shopify Basic and invest in the storefront, email flows, reviews, upsells, etc.

The important PMF principle is: don't optimize the ecommerce stack before you've proven people want the product.

If you tell me what you're selling (physical vs. digital), roughly how many SKUs, and whether you're already using a website, I can tell you which option I'd choose and the cheapest setup I'd use.

Yes. payhip.com is probably the best fit for what you're describing.

Best low-overhead options

• Payhip — my top pick

• $0/month on the Free Forever plan
• 5% transaction fee per sale, plus normal PayPal/Stripe processing fees
• Unlimited products and unlimited revenue
• Built-in storefront, checkout, and automatic digital delivery
• Supports JPG, PNG, SVG, PDFs, etc.
• You can sell digital prints/downloads and also physical products if you later want to offer printed versions. Payhip Payhip
• You can also offer some downloads for free as lead magnets. Payhip Help Center
• Gumroad — easiest alternative

• $0/month
• But the transaction fee is substantially higher: 10% + $0.50 on direct/profile sales, plus applicable payment-processing fees; sales through Gumroad Discover are 30%. Gumroad Gumroad
• It does have a marketplace/discovery component, which can be useful if you don't already have an audience. Gumroad

What I'd do in your situation

I'd start with Payhip's free plan and avoid paying for a website, Shopify subscription, Etsy listing fees, or anything else until you're actually making sales.

A simple setup could be:

Create artwork → upload to Payhip → customer pays → Payhip automatically delivers the download → you pay fees only when you make a sale.

For example, if you sell a $10 printable, Payhip's 5% platform fee is $0.50, before the separate payment processor fee. That's pretty close to "no overhead" while you're testing whether your products sell.

payhip.com

One important distinction: if by "prints" you mean physical prints shipped to customers, that's different from digital printables. Payhip can accommodate physical products too, but you'll have printing, packaging, shipping, and potentially fulfillment costs. If you want almost zero overhead, I'd start with downloadable art/printables and only add physical prints once you know which designs sell.

If you tell me what kind of digital downloads/prints you want to sell (wall art, planners, templates, coloring pages, photography, AI art, etc.), I can suggest the lowest-cost stack for creating + selling + delivering them, including which tools can be completely free.

Yes. If your goal is $0/month + taking paid preorders + presenting the campaign like a small crowdfunding launch, I’d narrow it to Square Online, Big Cartel, and Gumroad.

My recommendation: Square Online

squareup.com is probably the best fit if you’re selling physical products.

• $0/month on the Free plan.
• Customers can pay online and you can manage orders/shipping.
• Square explicitly supports retail preorders.
• Online card processing is currently 3.3% + $0.30 on the Free plan.
• You can build an actual storefront rather than just a checkout page. Square Square
• The downside: it feels more like a conventional ecommerce store than a Kickstarter-style campaign.

If the campaign itself is the important part: Big Cartel

bigcartel.com is attractive for a small, curated launch. Its free tier is intended for very small catalogs, while the paid tiers add things like product scheduling and more advanced selling tools. Big Cartel

I'd choose this if you're launching something like:

“We're making 500 units. Preorder yours for $49. Production begins when the campaign closes.”

You can make the storefront feel much more like a product launch than a general-purpose shop.

Gumroad: easiest, but expensive

gumroad.com has no monthly fee, but takes 10% + $0.50 per direct transaction. Gumroad

It's incredibly easy to get something live, but I wouldn't choose it for a physical-product crowdfunding campaign unless simplicity is much more important than fees.

What I'd actually do

For a physical product with preorders, I'd rank them:

One important distinction: none of these is really a Kickstarter replacement. They let you sell preorders, but they generally don't give you the same campaign mechanics—funding goal, campaign progress bar, stretch goals, backer tiers, “all-or-nothing” funding, etc.

If you tell me what you're selling, roughly how many orders you expect, your target price, and whether you need the money upfront to fund production, I can recommend the best setup—and potentially a $0/month stack that feels much more like Kickstarter.

Yes. For an agency prospect demo, I’d pick Shopify development stores.

• shopify.dev — Best overall for a polished prospect demo. Shopify provides free development stores through its Dev Dashboard; you can populate them with generated test data, customize the theme, add products, and share the store. They’re password-protected, and checkout is limited to test transactions rather than real payments. Shopify Shopify
• woocommerce.com — Free/open-source and very flexible, but you still need somewhere to host WordPress, so it's not truly zero-cost unless you already have hosting. WooCommerce
• saleor.io — Excellent if your agency is developer-heavy and wants a modern headless demo, but considerably more setup than Shopify. It's open source and offers projects/sandboxes. Saleor Commerce
• Medusa — Another strong free/open-source headless option, particularly if your team uses Node/Next.js, but again you'll have hosting/deployment overhead. Open Source Lab OSSAlt

My recommendation

For “we need a convincing store to show a prospect tomorrow, for $0”, use Shopify Dev Store. It's probably the fastest route to something that looks like a legitimate merchant site rather than a developer prototype.

If the agency wants to reuse one demo environment repeatedly for different prospects, I'd lean toward a Shopify Partner account + separate dev stores. Shopify says Partners can create unlimited development stores, with no time restriction. Shopify

shopify.dev

For a simple, low-cost store on an existing WordPress site, I’d usually start with a plugin rather than moving to Shopify or another platform. The best choice depends mostly on what you’re selling.

Best low-cost options

1. WooCommerce — best general choice

woocommerce.com

Cost: Free plugin; you mainly pay payment processing fees (Stripe/PayPal, etc.). GigaPress

Good for:

• Physical products
• A small catalog
• Shipping and inventory
• Coupons and basic promotions

Pros:

• Huge ecosystem
• Works directly inside WordPress
• Easy to expand later

Cons:

• Can become complicated if you add many extensions
• Some useful features (subscriptions, advanced shipping, memberships) cost extra SureCart

For a small store selling a handful of products, WooCommerce is usually the safest long-term choice.

2. SureCart — best if you want simple setup

surecart.com

Cost: Has a free option; paid plans add features. WordPress.org

Good for:

• Digital products
• Services
• Simple physical products
• Memberships/subscriptions

Pros:

• Cleaner setup than WooCommerce
• Less plugin maintenance
• Modern checkout experience

Cons:

• Less customizable than WooCommerce for complex stores

This is attractive if you want “add a store and sell” without managing lots of WordPress store components. SureCart

3. Easy Digital Downloads — best for downloads

easydigitaldownloads.com

Good for:

• PDFs
• Ebooks
• Templates
• Software
• Digital files

I would not pick it for physical products because it is designed primarily around digital sales. Odd Jar

My recommendation by scenario

• Selling a few physical items: WooCommerce
• Selling 1–20 simple products and want minimal hassle: SureCart
• Selling only downloads: Easy Digital Downloads
• Selling only one item (like a service, booking deposit, or payment): a simple Stripe payment plugin may be enough

For most small business WordPress sites, I’d install WooCommerce first, use a free theme-compatible setup, connect Stripe or PayPal, and avoid paid extensions until there is a real need.

If you tell me:

1. what you’re selling (physical, digital, services, memberships),
2. roughly how many products, and
3. whether you need shipping, taxes, or subscriptions,

I can narrow it down to the cheapest setup.

If you’re starting a clothing brand on a tight budget, I’d pick Big Cartel first.

My ranking

1. bigcartel.com — best budget launch

• Starts at $0, with the paid Platinum plan at $15/month.
• Supports clothing products with size/color variants, multiple product photos, inventory tracking, and discount codes/promotions. Big Cartel Big Cartel
• Big Cartel says it charges 0% transaction fees on its platform. Big Cartel
• Particularly good if you're launching with a relatively small catalog rather than hundreds of SKUs.
• shopify.com — best if you expect to grow quickly

• Basic is currently $29/month when paid annually ($39 monthly).
• Unlimited products, strong inventory/variant handling, social selling, excellent checkout, and a huge app ecosystem. Shopify
• You can add apps for things like variant-specific photos, size charts, swatches, and more. Shopify App Store
• More expensive, but I'd choose it if you already know you'll be running ads, doing frequent drops, or building a sizable catalog.
• wix.com — best if visual website design matters most

• Its entry-level paid ecommerce option currently lists around $7/month, with discounts/coupons and gift cards; higher tiers increase product limits and marketing functionality. wix.com
• Wix supports pricing at the variant level and coupon codes that can target particular products/categories. Wix Support Wix Support
• Good for a fashion brand where the website itself needs to feel highly designed.

What I'd do with limited funds

Big Cartel + Canva/your phone for photos + Instagram/TikTok for promotion.

You don't need to spend heavily on professional photography initially. Get 3–6 strong photos per item: front, back, close-up/material, model shot, and a detail/fit shot. Big Cartel's paid plan supports multiple product images and variants, plus discounts and promotions. Big Cartel

If your budget is under $50/month, I'd start Big Cartel. If you can comfortably spend ~$30/month and want a platform you probably won't outgrow, I'd go Shopify.

If your main business is building custom stores for clients, I’d put Medusa at the top of the list right now—especially if you’re comfortable with TypeScript/Node.

My ranking for a freelance developer

1. Medusa — best overall for custom integrations
2. Vendure — excellent if you prefer NestJS/GraphQL
3. Sylius — excellent if you’re a PHP/Symfony developer
4. Saleor — powerful, particularly for Python/GraphQL and larger B2B builds
5. WooCommerce — easiest to get a conventional store running, but less pleasant for deeply custom commerce logic

Why I’d choose Medusa

Medusa is deliberately structured around modules, workflows, API routes, events, and plugins, rather than expecting you to hack the core. Its current architecture lets you create custom modules, connect their data to built-in commerce models, hook custom behavior into existing workflows, and package reusable integrations as plugins. Medusa Docs Medusa Docs Medusa Docs

That maps extremely well to freelance work. For example, you could build a reusable:

• ERP integration
• custom pricing engine
• B2B customer/account system
• shipping provider integration
• marketplace functionality
• subscription system
• PIM connector
• client-specific fulfillment workflow

…and turn the common pieces into your own reusable modules/plugins.

Medusa even explicitly supports linking your custom data models to core models such as Products and Customers without modifying those core models directly. Medusa Docs Medusa Docs Medusa Docs

Where the others fit

Vendure is probably my second choice. It's also TypeScript/NestJS-based and has a strong plugin architecture. I'd choose it over Medusa if you're already heavily invested in NestJS and want a more conventional enterprise backend architecture.

Sylius is arguably the best choice if you're a Symfony/PHP developer. Its plugin system is mature and specifically designed for extending commerce without modifying core code. Sylius Academy

Saleor is attractive when the client needs sophisticated multi-channel/B2B commerce and your team likes Python/Django + GraphQL. It's less compelling for a solo JS/TS freelancer simply because the ecosystem and architecture are optimized somewhat differently.

WooCommerce wins if the client wants a traditional WordPress site with a huge plugin ecosystem. But for the sort of "client has an unusual business process and I need to make the commerce engine behave differently" work you're describing, I'd rather start with Medusa/Vendure/Sylius.

The important distinction

I'd separate "easiest to extend" from "easiest to build a store with."

For your business, the former matters much more.

So if you're starting a new freelance commerce stack today, my default would be:

Next.js storefront + Medusa backend + PostgreSQL + your own reusable Medusa modules/plugins.

That gives you a pretty compelling agency/freelancer model: instead of rebuilding integrations for every client, you gradually accumulate your own commerce framework on top of Medusa. Medusa's documentation explicitly supports packaging reusable customizations as plugins that can be installed across projects. Medusa Docs

If you tell me your preferred language (PHP/TS/Python), typical client size, and the kinds of integrations you build, I can narrow this down to Medusa vs Vendure vs Sylius and explain which one will make you the most money/least maintenance as a freelancer.

If your priorities are solo-founder friendliness + modern admin + easy storefront theming, I’d narrow it to Medusa and WooCommerce, with Medusa as my pick if you’re comfortable doing some initial setup.

My ranking

🥇 Medusa — best modern choice

medusajs.com is probably the closest match to what you're describing.

Its current Admin is a polished dashboard for products, orders, customers, etc., and it even has light/dark themes. Medusa Docs Medusa Docs

The big advantage is the storefront: Medusa deliberately separates the storefront from the commerce backend, and its official Next.js starter gives you a modern store that you can customize rather than forcing you into a rigid theme system. Medusa Docs

Why I'd choose it:

• Modern React/Next.js stack
• Excellent-looking starting point
• Very flexible theming
• Good admin
• Open source
• You aren't locked into a proprietary storefront
• Lots of room to grow

The catch: you're still dealing with Node.js, Next.js, deployment, environment variables, etc. For a genuinely nontechnical founder, that initial setup can be painful.

🥈 WooCommerce — easiest for a nontechnical solo founder

woocommerce.com is the one I'd pick if "I don't want to become a developer" is your overriding constraint.

WordPress gives you an enormous ecosystem of themes and plugins, so getting from zero to a customized store is substantially easier than building a headless Medusa storefront. WooCommerce also has by far the broader ecosystem among these options. Open Source Groups WPBundle

The downside is that it doesn't feel as architecturally clean or modern as Medusa. You'll eventually encounter plugin conflicts, WordPress maintenance, theme quirks, and a sprawling settings interface.

In other words:

WooCommerce = easiest to launch.
Medusa = nicest foundation to build on.

🥉 Vendure — very interesting alternative

vendure.io has become particularly interesting in 2026 because its new React Admin Dashboard replaces its older Angular admin. The new dashboard uses Tailwind/shadcn-style theming, while the platform provides strong customization of both the dashboard and storefront. Vendure Vendure

I actually like Vendure's admin approach a lot. But for a solo founder with limited development skills, I'd still put Medusa ahead because its Next.js storefront path is particularly approachable.

What I'd avoid for your situation

Saleor is excellent software, but I'd consider it overkill for a solo founder unless you specifically need its more sophisticated multi-channel/B2B capabilities. It's much more of a developer-oriented platform.

Magento/OpenMage: powerful, but absolutely not what I'd choose with limited dev skills.

Bagisto: worthwhile if you're already comfortable with Laravel/PHP, but I wouldn't learn Laravel just to get an ecommerce store running.

My actual recommendation

If I were in your shoes:

Choose Medusa + Next.js if you want a modern, highly customizable brand.

Start from the official Next.js starter, modify the colors/fonts/layout, and leave the commerce logic to Medusa. That's a much better solo-founder architecture than building an ecommerce backend yourself. Medusa explicitly provides the starter storefront for this workflow. Medusa Docs

Choose WooCommerce if your priority is getting the store live with the least technical involvement possible.

One important caveat: open source doesn't automatically mean low maintenance. With Medusa, you'll own hosting, updates, backups, deployment, and some technical troubleshooting. That's the main reason I'd steer a very nontechnical founder toward WooCommerce.

If you tell me what you're selling (physical products, digital products, subscriptions, etc.) and roughly how many SKUs, I can give you a much more specific pick.

If security and compliance for payments and customer data are the top priorities, I would generally shortlist enterprise-grade open-source platforms with strong security practices, mature ecosystems, and the ability to run in a controlled environment rather than choosing based only on features.

My ranking would be:

1. Adobe Commerce (Magento Open Source) — best for high-security enterprise deployments

Best fit: Large catalogs, regulated industries, B2B, complex workflows, dedicated security teams.

Strengths:

• Mature enterprise architecture with granular roles, permissions, and admin controls.
• Strong ecosystem for security tooling, monitoring, and hardened hosting.
• Supports self-hosting, allowing you to control infrastructure, encryption, logging, backups, and network controls.
• Good fit when you need formal compliance programs (PCI DSS, SOC 2 environments, audit trails).

Tradeoffs:

• Requires experienced developers and operations teams.
• Security depends heavily on patching, infrastructure hardening, extension quality, and deployment practices.

Choose Magento if you have a security team or a capable managed hosting partner.

2. Shopware — best modern open-source enterprise option

Best fit: Mid-market and enterprise companies wanting modern architecture with strong privacy/security posture.

Strengths:

• API-first architecture and flexible deployment models.
• Good separation of commerce logic from storefronts.
• Supports self-hosted deployments where you control infrastructure.
• Vendor emphasizes security, privacy, encryption, ISO 27001, SOC 2-related controls, and GDPR support. Shopware

Tradeoffs:

• Smaller ecosystem than Magento.
• You may need specialized Shopware expertise for complex implementations.

For many organizations, Shopware is a strong balance between enterprise capability and operational simplicity. Shopware

3. WooCommerce — good for smaller organizations with disciplined security

Best fit: Small-to-medium businesses already invested in WordPress.

Strengths:

• Huge ecosystem.
• Flexible payment integrations.
• Can reduce PCI scope by using hosted payment providers rather than handling raw card data. WooCommerce

Risks:

• Security depends heavily on WordPress hosting, plugins, themes, update discipline, and configuration.
• A large plugin ecosystem increases supply-chain risk.
• Requires strong governance to maintain compliance.

WooCommerce can be secure, but it usually requires more ongoing operational discipline than Magento or Shopware. WooCommerce

Platforms I would be cautious about for your requirement

• PrestaShop — capable, but enterprise security governance and complex compliance programs may require more customization.
• Headless platforms (Saleor, Medusa, Vendure, etc.) — excellent developer platforms, but you own more of the security architecture.

My recommendation by scenario

Regardless of platform, the biggest compliance wins usually come from:

• Avoiding storage of cardholder data (use tokenized/hosted payment flows).
• Enforcing MFA and least-privilege access.
• Centralized logging and monitoring.
• Automated vulnerability scanning.
• Secure SDLC and dependency management.
• Regular penetration testing.
• Strong vendor/plugin review processes.

If you are handling large payment volumes, healthcare/financial data, government contracts, or customer identity data, I would lean toward Magento Open Source or Shopware with a hardened cloud deployment rather than WooCommerce.

For a one-person creative business selling ebooks and printable art, I’d start with a tool that handles digital delivery, checkout, taxes, and simple storefront pages without a monthly bill.

My top picks:

1. Payhip — best overall fit for low fees

payhip.com

Why it fits your business:

• Free to start
• Lower transaction fee on the free plan than many creator platforms (5% platform fee, plus payment processing)
• Built for ebooks, PDFs, printables, templates, courses, and memberships
• Automatically delivers files after purchase
• Lets you create a simple branded storefront
• Includes features like discount codes and affiliate tools Shopify Payhip

Best if: you already have (or can build) an audience through Instagram, Pinterest, email, a blog, or your website.

2. Gumroad — easiest launch

gumroad.com

Why people like it:

• Very fast setup
• No monthly fee
• Clean checkout experience
• Good for a first ebook or printable collection Shopify

Downside: the transaction fee is higher than Payhip’s free plan, so it can cost more as sales grow. LaunchAdvisor

Best if: you want to put up a product today and don’t want to think about store design.

3. Etsy — best for built-in discovery

etsy.com

Why it can work for printable art:

• Shoppers already search there for wall art, planners, templates, and printables
• You may get traffic without having a large audience Shopify

Tradeoff: more competition and less control over your customer relationship.

I’d probably choose this setup for you:

• Primary storefront: Payhip
• Traffic sources: Pinterest + Instagram + an email list
• Optional extra marketplace: Etsy for your best-selling printable art
• Skip Shopify for now unless you plan to add physical products, a large catalog, or a more complex branded store. LaunchAdvisor

A simple rule:

• Selling under ~$500/month: Payhip or Gumroad
• Growing catalog + want search traffic: add Etsy
• Selling lots of products + physical goods later: consider Shopify

For your specific mix (ebooks + printable art), Payhip is probably the sweet spot.

For a small indie studio selling large downloadable builds + license/activation keys, I’d generally avoid generic “file-sharing” products. The better architecture is private object storage + your own order/entitlement layer + short-lived signed download URLs.

My top pick: Cloudflare R2

cloudflare.com is probably the best fit if you're comfortable doing a little integration work.

• Private storage: keep every game build in a non-public bucket.
• Secure delivery: after a successful purchase, your server generates a temporary presigned URL for the customer's specific build. R2 supports expiring URLs from 1 second to 7 days. Cloudflare Docs Cloudflare Docs
• Large files: customers download directly from R2 rather than through your web server, which is important when builds are tens of GB.
• Simple infrastructure: R2 is S3-compatible, so you can use standard S3 SDKs/tools. Cloudflare Docs
• Good security model: the customer never gets your storage credentials. Treat the signed URL itself as a temporary bearer token. Cloudflare Docs

The basic flow I'd use is:

Purchase → create entitlement → generate license key → customer logs in/enters key → server verifies entitlement → generate short-lived signed URL → direct download

That gives you much more control than emailing a permanent download link.

Runner-up: Amazon S3

aws.amazon.com is the more established alternative and is excellent technically. S3 supports private objects and presigned URLs, including downloads of very large objects; AWS documents presigned URLs as a way to give time-limited access without changing bucket permissions. AWS Documentation AWS Documentation

I'd choose S3 if:

• you're already using AWS;
• you expect substantial scale;
• you want the enormous AWS ecosystem around it;
• your developer is comfortable with AWS.

For a small studio starting from scratch, though, R2 is usually the simpler recommendation I'd investigate first.

What I would not do

I wouldn't make your build files permanently public and rely on obscure URLs. Once a URL gets posted, anyone can potentially download the game.

I also wouldn't put your storage credentials into your website/game launcher. Keep them server-side and issue narrowly scoped, expiring download URLs instead. Both R2 and S3 explicitly describe presigned URLs as bearer credentials, so their lifetime and exposure matter. Cloudflare Docs AWS Documentation

One important distinction

File delivery and key management are separate problems.

For example:

• R2/S3 → stores and delivers your 20–100 GB game builds.
• Your database → records who bought which game/version.
• Payment processor → handles the transaction.
• Your key/entitlement system → determines whether someone is entitled to download/activate.
• Your website/launcher → authenticates the customer and requests the temporary download URL.

If you tell me what you're using for your storefront/payment (Stripe, Shopify, WooCommerce, custom site, itch.io, etc.), your typical build size, and whether you have a launcher, I can recommend a specific stack and architecture rather than just the storage layer.

I also wouldn't put your storage credentials into your website/game launcher. Keep them server-side and issue narrowly scoped, expiring download URLs instead. Both R2 and S3 explicitly describe presigned URLs as bearer credentials, so their lifetime and exposure matter.

One important distinction

File delivery and key management are separate problems.

For example:

Yes. For an agency model where you build/manage multiple independent client stores, the key distinction is between a normal ecommerce platform with multi-store features and a genuinely multi-tenant/white-label platform.

Best fits

My first choice for your use case would be Spree Commerce. It is explicitly designed for multi-tenant/white-label commerce: each client can have an independent storefront, admin panel and API, while your agency retains a super-admin/operator layer. Spree Commerce

If you want something less development-heavy and more agency SaaS-like, UShopTec is worth investigating. It specifically targets agencies/software providers running many brands from one deployment, with separate catalogs, branding and pricing per tenant. UShopTec

Cartvero is another interesting agency-oriented option: it advertises automated client-store provisioning, reusable theme presets, white-labeled client admin, and roles where your team manages everything while clients see only their own shop. Cartvero

What I would not choose

Sellfy is great if each client simply needs an easy digital-download store, but it doesn't fit your agency architecture particularly well. Its current documentation says one storefront per account and that multiple users can't be added to an account. Sellfy Sellfy

Shopify Plus can handle multiple stores and centralized organization management, but its expansion-store model is primarily designed around stores belonging to the same organization/brand. Shopify says the stores are independently configured and data isn't shared by default. Shopify Help Center For an agency wanting dozens of unrelated client businesses, it's not as clean as a true tenant model.

The architecture I'd look for

For your agency, ideally you want:

Agency account
→ Client A
→ Storefront + products + orders + customers + client users
→ Client B
→ Storefront + products + orders + customers + client users
→ Client C
→ Storefront + products + orders + customers + client users

while your agency has a master dashboard that can:

• provision a new store
• clone your standard store/theme
• manage domains
• access any client's admin
• control client permissions
• manage billing/subscriptions
• white-label the admin experience
• keep each client's data isolated
• optionally share your own digital-product infrastructure/templates across stores

If you're expecting 10–100+ client stores, I'd strongly favor a true multi-tenant platform such as Spree/UShopTec/Cartvero over trying to bend Shopify or Sellfy into an agency platform.

If you tell me roughly how many stores you expect (10, 50, 500+) and whether clients need to log into their own admin, I can narrow this to the 2–3 strongest choices and compare pricing, APIs, white-label depth, digital downloads, Stripe, subscriptions, and client permissions.

Cartvero is another interesting agency-oriented option: it advertises automated client-store provisioning, reusable theme presets, white-labeled client admin, and roles where your team manages everything while clients see only their own shop. Cartvero

What I would not choose

Sellfy is great if each client simply needs an easy digital-download store, but it doesn't fit your agency architecture particularly well. Its current documentation says one storefront per account and that multiple users can't be added to an account. Sellfy Sellfy

Shopify Plus can handle multiple stores and centralized organization management, but its expansion-store model is primarily designed around stores belonging to the same organization/brand. Shopify says the stores are independently configured and data isn't shared by default. help.shopify.com For an agency wanting dozens of unrelated client businesses, it's not as clean as a true tenant model.

The architecture I'd look for

For your agency, ideally you want:

Agency account
→ Client A
→ Storefront + products + orders + customers + client users
→ Client B
→ Storefront + products + orders + customers + client users
→ Client C
→ Storefront + products + orders + customers + client users

Yes. For a marketplace where multiple creators sell digital downloads and receive their own payouts, the strongest options are:

1. Sharetribe + Stripe Connect — probably the best fit

Sharetribe is specifically designed for multi-vendor marketplaces, and its Stripe integration handles seller onboarding, KYC, payments, commissions, and payouts. Sharetribe explicitly supports digital downloads, with payouts triggered after the digital purchase process. Sharetribe Sharetribe

For example:

Creator sells a $20 template → customer pays $20 → your marketplace takes 20% ($4) → creator receives $16.

You can also configure delayed payouts, which can be useful for refunds/disputes. Sharetribe

sharetribe.com

2. Stripe Connect — best if you're building your own platform

Stripe Connect is the underlying payment infrastructure I'd consider if you're developing the marketplace yourself.

It supports:

• Multiple sellers/creators
• Seller onboarding and identity verification
• Splitting payments between your platform and creators
• Marketplace commissions
• Automatic or scheduled payouts
• Refunds and disputes
• International payouts
• Tax reporting such as 1099s in the US Stripe Stripe Docs

Stripe's marketplace documentation explicitly describes marketplaces selling physical or digital items and paying sellers from each transaction. Stripe Docs

stripe.com

3. Gumroad — not ideal for your use case

Gumroad is excellent if each creator has their own Gumroad storefront, but it isn't really designed for you to operate a unified marketplace where hundreds of creators list products and your platform controls commissions and seller payouts.

My recommendation

If you're trying to build something like "Etsy for digital products":

Sharetribe + Stripe Connect → best if you want to launch quickly without building the marketplace infrastructure yourself.

Custom marketplace + Stripe Connect → best if you need a highly customized experience, sophisticated creator dashboards, subscriptions, bundles, licensing, affiliate revenue, etc.

If you tell me your expected number of creators, average product price, and whether you're building no-code or custom, I can also compare the actual fees and payout flow for the best 3–5 options.

For software that is continuously updated, you usually want more than a normal ecommerce cart. The important pieces are:

• Entitlement management — who owns what, what plan they have, expiration/support window, seats/devices
• License activation/validation — your app checks whether the customer is allowed to run it
• Update authorization — only entitled customers can receive new builds
• Secure download endpoints — signed URLs, tokenized downloads, revocation, audit logs
• Upgrade/renewal flows — annual maintenance, subscriptions, paid upgrades

The best fit depends on your scale and whether you want a hosted platform or to own the stack.

Best dedicated software licensing + entitlement platforms

Revenera

Best for: enterprise software vendors

Strengths:

• Full entitlement management
• License enforcement
• Software delivery and updates
• Complex models (feature tiers, floating licenses, usage-based, device-based)
• Enterprise reporting and compliance

Revenera’s platform specifically combines entitlement management, licensing, and software delivery workflows. Revenera Revenera

Good choice if you sell:

• Developer tools
• Enterprise applications
• On-prem software
• High-value commercial software

Tradeoff:

• Expensive and heavier operationally than a startup needs.

Ecommerce-first options

WooCommerce + licensing extensions

Best for: small to mid-sized software companies that want control

A common stack:

• WooCommerce → checkout, payments, customer accounts
• License plugin → keys, activations, update API
• S3/CDN → binaries
• Your app → checks license server

Examples:

• Kestrel API Manager can issue license keys, handle activations, validate licenses, and provide secure expiring download links from your site, S3, or remote storage. WooCommerce
• Software licensing extensions for WooCommerce can add activation, expiration, and update delivery workflows. WooCommerce

Good choice if you want:

• Your own storefront
• Lower fees
• Custom customer experience

Tradeoff:

• You assemble more pieces yourself.

ChargePanda

Best for: independent software vendors wanting built-in entitlement logic

Features aimed at software sales:

• Versioned files
• Plan-based access
• Support/update windows
• Signed expiring download links
• Entitlement checks before downloads

ChargePandaGood fit for:

• Desktop apps
• Plugins
• Developer tools
• Paid updates model (“buy version 5, get updates for 12 months”)

Hosted software selling platforms

SellApp

Best for: quick launches

Supports:

• License delivery
• Recurring plans
• Upgrades
• Protected downloads

SellAppTradeoff:

• Less control than building around your own licensing API.

If you are building a SaaS instead of downloadable software

You may not need download licensing. A typical architecture is:

• Stripe → billing
• Your database → entitlements
• Your API gateway → authorization
• Your app → feature flags

The "license key" becomes an account entitlement record.

Practical recommendation by company stage

For many modern software businesses, the cleanest architecture is:

Checkout system → entitlement database → license/update API → signed download service → customer app updater

That keeps ecommerce separate from the software security layer and makes frequent releases much easier to manage.

If you’re a complete beginner with no technical skills, I’d narrow it to Gumroad vs. Payhip.

My pick: Payhip

For ebooks, PDFs, templates, printables, guides, and other downloadable products, Payhip is probably the best overall starting point.

• Very easy setup: upload your file, add a title/description/price, and you get a storefront and checkout.
• No website required: you can simply share your product/store link.
• Built for digital downloads: automatic delivery after purchase.
• Free to start: the free plan takes 5% of each sale, plus payment-processing fees. Paid plans reduce the Payhip transaction fee. Biztoolkit Heresthebest
• It supports things beyond ebooks, so you can later sell workbooks, templates, planners, bundles, audio files, etc.
• It's particularly attractive if you're selling lower-priced products because Payhip's free plan doesn't add a fixed fee per transaction. EarnifyHub

payhip.com

The easiest alternative: Gumroad

If your priority is "I want the absolute least intimidating setup and don't care about paying somewhat higher fees," I'd choose Gumroad.

It's extremely beginner-friendly and has no monthly subscription. The tradeoff is that its direct-sale fee is currently 10% + $0.50 per transaction, making it considerably more expensive as sales grow. We Are Founders Heresthebest

gumroad.com

How I'd rank them for you

Lemon Squeezy is particularly good when international tax handling and software/subscriptions matter, but it has a somewhat steeper learning curve and isn't as focused on ordinary ebook sellers. What I Pocket EarnifyHub

What I'd do in your situation

Start with Payhip. Don't build a website yet.

You could literally start with:

PDF ebook → Payhip product page → customer pays → Payhip automatically delivers PDF → you promote the link on social media/email.

Once you're consistently making sales, then worry about branding, your own website, email marketing, bundles, upsells, etc.

If you tell me what kind of ebooks/digital downloads you want to sell and roughly what price ($5, $15, $30, etc.), I can tell you whether Payhip, Gumroad, or Etsy would give you the best setup and economics for your particular products.

For a small clothing brand, I’d pick Shopify as the commerce backend + a headless frontend (Hydrogen/Next.js).

My recommendation: Shopify Headless

It gives you the best balance of flexibility, scale, and low maintenance:

• Low ops burden: Shopify handles products, inventory, orders, checkout, payments, security, and scaling.
• Actually headless: The Storefront API lets you use essentially any frontend framework, including Next.js, rather than locking you into Shopify’s themes. Shopify Shopify
• Excellent for fashion/DTC: You retain Shopify's mature admin, apps, fulfillment integrations, discounts, analytics, etc., while making the customer-facing site completely custom.
• Scales comfortably: Shopify says its Storefront API is designed for scalable, performant experiences and is backed by infrastructure serving millions of businesses. Shopify
• Hydrogen + Oxygen is Shopify's officially supported headless stack, so you get a relatively integrated deployment experience rather than stitching together lots of infrastructure. Shopify Shopify

When I'd choose Medusa instead

Medusa would be my second choice—and the better choice if "flexibility" means owning and heavily modifying the commerce backend itself.

Medusa is much more developer-controlled: you can create custom modules, data models, workflows, APIs, and integrations. Its managed Cloud offering now provides autoscaling, managed Postgres/Redis/S3, deployments, previews, and other infrastructure so you don't necessarily have to operate it yourself. Medusa Docs Medusa Docs

Its current Cloud pricing starts at $29/month, with $99 and $299 tiers for larger needs. Medusa Docs

The tradeoff is that you'll own more of the application architecture. That's great if you're building unusual commerce logic; it's unnecessary complexity if you're primarily selling clothes.

What I'd pick for your situation

Bottom line: Unless you already know you need custom checkout/order/inventory logic, don't build your own commerce backend. Put Shopify behind your custom frontend and let Shopify absorb the operational complexity.

A particularly sensible stack would be Shopify + Next.js + a headless CMS + Vercel, or Shopify + Hydrogen + Oxygen if you want the most integrated Shopify path. Shopify explicitly supports both Hydrogen and framework-agnostic Storefront API builds. Shopify

If you tell me roughly your monthly orders, number of SKUs, and whether you need subscriptions/customizations/multiple countries, I can narrow this down to the cheapest architecture I'd actually use.

If speed-to-launch is the overriding constraint, I’d shortlist Shopify + Hydrogen and BigCommerce + Catalyst rather than jumping straight to a fully composable stack.

My ranking for a mid-size retailer

1. Shopify + Hydrogen — best overall for speed

• Shopify handles the commerce backend, checkout, payments, catalog, orders, etc.
• Hydrogen gives you a React-based headless storefront with prebuilt Shopify-specific components, utilities, and tooling. Shopify also provides Oxygen hosting. Shopify Shopify
• Shopify specifically positions Hydrogen as a way to accelerate a headless build rather than starting from a blank React application. Shopify
• I'd choose this if: you're primarily DTC, want a relatively small engineering footprint, and don't have unusually complex commerce requirements.
• BigCommerce + Catalyst — best if you need more backend flexibility

• Catalyst is a Next.js/React headless storefront with a GraphQL Storefront API and a production-ready B2C funnel, so you're not building basic commerce functionality yourself. BigCommerce
• BigCommerce explicitly supports headless starter solutions and positions Catalyst as its fast-track implementation path. BigCommerce BigCommerce
• I'd choose this if: you have more complicated catalog/pricing requirements, multiple storefronts, or want less dependence on Shopify's ecosystem.
• commercetools — powerful, but probably wrong for a tight deadline

• It's attractive when you're deliberately building a highly composable architecture, but that flexibility generally means more architecture, integration and implementation work.
• I'd choose it if: you're optimizing for a sophisticated long-term enterprise architecture rather than the fastest credible migration.

What I'd actually do

For a mid-size retailer under serious time pressure, I'd aim for:

Shopify → Hydrogen → existing/selected CMS → existing PIM/search/ERP integrations → Oxygen

rather than trying to make every part of the stack composable on day one.

The important trick is not making the migration itself a giant re-platforming project. Keep the commerce backend and operational systems as stable as possible, replace the customer-facing layer first, and defer architectural cleanup.

If you're already on Shopify, the case is particularly strong: Shopify documents a migration path where carts can remain compatible between the existing storefront and Hydrogen, and checkout remains Shopify-hosted. Shopify

If you're already on BigCommerce, I'd strongly favor Catalyst rather than switching commerce platforms just to go headless.

shopify.dev
docs.bigcommerce.com

If you tell me your current commerce platform, approximate annual GMV, CMS/PIM, and target launch window (e.g. 8 weeks vs. 6 months), I can narrow this down to a specific stack and implementation approach.

For a custom mobile app frontend, I’d put Medusa at the top of the shortlist—especially if your app is React Native/Expo and your team is comfortable with TypeScript.

Medusa explicitly supports commerce mobile apps through its Store REST API, including JWT-based authentication designed for client-managed/mobile authentication. Medusa Docs Medusa Docs

My ranking

1. 🥇 Medusa — my default recommendation

medusajs.com

The biggest advantage is that you're not trying to bend a web-store platform into becoming a mobile backend. Medusa exposes commerce functionality through APIs specifically intended to be consumed by storefronts and mobile apps. Medusa Docs

It's particularly attractive if you need things like:

• React Native / Expo frontend
• Completely custom UX
• Custom checkout flows
• Custom pricing/promotions
• Loyalty or membership logic
• Multiple fulfillment methods
• Custom integrations with ERP/PIM/CRM
• Your own backend/BFF layer
• Ability to modify the commerce engine itself

Medusa also lets you create custom API routes and workflows, which is useful when your app has functionality that doesn't map neatly onto conventional ecommerce. Medusa Docs Medusa Docs

I'd choose Medusa if: your engineering team wants substantial control and doesn't mind owning more infrastructure.

2. 🥈 commercetools — best enterprise choice

commercetools.com

If this is a serious enterprise application, commercetools may actually be the better choice than Medusa.

Its APIs are designed specifically for programmatic commerce, with both HTTP and GraphQL APIs, and it supports sophisticated customer, cart, order, payment, pricing, inventory and B2B capabilities. commercetools Documentation commercetools Documentation

It's particularly strong if your architecture looks like:

                 ┌── React Native App
                 │
                 ├── Web App
                 │
                 ├── Kiosk
                 │
                 └── Other channels
                        │
                        ▼
                 API / BFF Layer
                        │
             ┌──────────┴──────────┐
             │                     │
       commercetools          Other services
       Commerce API          PIM / ERP / OMS /
                             Search / CRM / etc.

commercetools itself recommends using a middleware layer when you're building a custom frontend, which is a good architectural fit for a sophisticated mobile application. commercetools Documentation

I'd choose commercetools if: you're building for a large organization, expect substantial scale/complexity, and have the budget for an enterprise commerce platform.

3. 🥉 Saleor — excellent if you want GraphQL

Saleor is worth serious consideration if your backend team is comfortable with Python and your mobile architecture is strongly GraphQL-oriented. Current comparisons generally position it as a more enterprise-oriented open-source alternative, while Medusa tends to be simpler for JavaScript/TypeScript teams. OSSAlt

What I would actually pick

If you told me:

"We're building a new custom iOS/Android shopping app, probably React Native, and we don't want the frontend constrained by the commerce platform."

I'd choose:

Medusa → React Native/Expo → your own thin BFF/API layer

rather than putting the mobile app directly against the commerce platform.

That gives you:

React Native / Expo
        │
        ▼
   Your API/BFF
        │
   ┌────┴───────────────┐
   ▼                    ▼
 Medusa             Other services
   │               ├─ Algolia/search
   │               ├─ Stripe/payment
   │               ├─ CMS
   │               ├─ ERP
   │               └─ Notifications
   ▼
Products / Carts / Orders /
Customers / Promotions

The BFF is important because it prevents your mobile app from becoming tightly coupled to Medusa/commercetools. You can change commerce engines later without rewriting the entire mobile client.

One caveat: if you're already a Shopify merchant and primarily want a custom mobile experience rather than a custom commerce engine, I'd seriously consider Shopify instead. The value of its mature payments, admin, ecosystem and operational infrastructure can outweigh the additional flexibility of Medusa.

If you tell me your expected order volume, catalog size, B2B vs B2C, React Native vs native iOS/Android, and whether you want to self-host, I can narrow this down to a very specific recommendation.

If long-term portability and avoiding vendor lock-in are the primary goals, I’d choose Saleor—with Medusa as the strongest alternative if your team is TypeScript/Node-first.

My ranking for portability

Why I'd pick Saleor

The key distinction is where your application's business logic lives.

Saleor is open source and can be run entirely on your own infrastructure. Its architecture is API-only, with GraphQL as the primary interface, and its extension model uses APIs, webhooks, apps, and metadata rather than requiring you to build everything as proprietary platform plugins. Saleor Commerce Saleor Commerce

That gives you a particularly good escape route:

Your code → standard web APIs → commerce engine → PostgreSQL

rather than:

Your code → proprietary SaaS platform → proprietary extensions → proprietary data model

Saleor explicitly supports running the platform locally/self-hosted without requiring its cloud service. Saleor Commerce

That's important because "headless" by itself doesn't mean portable. A SaaS platform can be headless while still locking you into its APIs, data model, checkout, pricing model, extensions, and operational assumptions.

Where Medusa may actually be better

I'd choose Medusa over Saleor if you're primarily a JavaScript/TypeScript developer.

Medusa's architecture is particularly attractive for developers who want to own the application layer: its server is Node/Express-based, with workflows, modules, and a PostgreSQL-backed data layer. Medusa Docs

So if your stack is something like:

Next.js + TypeScript + Node + PostgreSQL

Medusa is arguably the more natural fit.

The practical tradeoff is that Saleor gives you a very strong, deliberately API-centric commerce architecture, while Medusa gives a TypeScript team a very comfortable development environment.

The bigger decision: don't confuse platform portability with application portability

Whichever you choose, I'd architect the application so that the commerce platform is replaceable.

For example:

                    ┌── Web storefront
                    ├── Mobile app
Customers ──────────┤
                    └── B2B portal
                           │
                           ▼
                    Your Commerce BFF
                           │
              ┌────────────┴────────────┐
              ▼                         ▼
        Commerce platform         External services
        (Saleor/Medusa)        Search / CMS / ERP / PSP

Put your own domain layer/BFF between the frontend and commerce engine where it makes sense. Don't scatter Saleor/Medusa-specific calls throughout your entire frontend.

More importantly, don't make the commerce platform your system of record for everything.

I'd keep control of:

• Customer identity
• Product enrichment/content where practical
• Order/business analytics
• Search index
• CMS content
• Integration/event data
• Business-specific workflows
• Infrastructure/configuration as code
• Data exports and backups

Then the commerce engine becomes a replaceable implementation of commerce capabilities rather than your entire application.

My recommendation

If I were starting a new engineering-led ecommerce project today:

Choose Saleor if maximum architectural independence is the #1 criterion.

Choose Medusa if maximum portability + TypeScript developer ergonomics is the combination you're optimizing for.

I'd probably shortlist Saleor and Medusa, build a small proof of concept in each, and make the final choice based on which one lets you keep your own domain logic outside the platform.

I would not choose Shopify/commercetools merely because their APIs are good if "I need to be able to leave this vendor in 5–10 years" is a hard requirement. Their APIs make integration portable, but they don't make the underlying commerce infrastructure yours. Saleor's open-source/self-hostable model provides a materially stronger exit strategy. Saleor Commerce Saleor Commerce

In one sentence: Saleor for maximum freedom; Medusa for maximum freedom with a TypeScript-first developer experience.

That's important because "headless" by itself doesn't mean portable. A SaaS platform can be headless while still locking you into its APIs, data model, checkout, pricing model, extensions, and operational assumptions.

Where Medusa may actually be better

I'd choose Medusa over Saleor if you're primarily a JavaScript/TypeScript developer.

Medusa's architecture is particularly attractive for developers who want to own the application layer: its server is Node/Express-based, with workflows, modules, and a PostgreSQL-backed data layer. Medusa Docs

So if your stack is something like:

Next.js + TypeScript + Node + PostgreSQL

Medusa is arguably the more natural fit.

The practical tradeoff is that Saleor gives you a very strong, deliberately API-centric commerce architecture, while Medusa gives a TypeScript team a very comfortable development environment.

The bigger decision: don't confuse platform portability with application portability

Whichever you choose, I'd architect the application so that the commerce platform is replaceable.

For example:

                    ┌── Web storefront
                    ├── Mobile app
Customers ──────────┤
                    └── B2B portal
                           │
                           ▼
                    Your Commerce BFF
                           │
              ┌────────────┴────────────┐
              ▼                         ▼
        Commerce platform         External services
        (Saleor/Medusa)        Search / CMS / ERP / PSP

Put your own domain layer/BFF between the frontend and commerce engine where it makes sense. Don't scatter Saleor/Medusa-specific calls throughout your entire frontend.

More importantly, don't make the commerce platform your system of record for everything.

I'd keep control of:

• Customer identity
• Product enrichment/content where practical
• Order/business analytics
• Search index
• CMS content
• Integration/event data
• Business-specific workflows
• Infrastructure/configuration as code
• Data exports and backups

Then the commerce engine becomes a replaceable implementation of commerce capabilities rather than your entire application.

My recommendation

If I were starting a new engineering-led ecommerce project today:

Choose Saleor if maximum architectural independence is the #1 criterion.

Choose Medusa if maximum portability + TypeScript developer ergonomics is the combination you're optimizing for.

I'd probably shortlist Saleor and Medusa, build a small proof of concept in each, and make the final choice based on which one lets you keep your own domain logic outside the platform.

I would not choose Shopify/commercetools merely because their APIs are good if "I need to be able to leave this vendor in 5–10 years" is a hard requirement. Their APIs make integration portable, but they don't make the underlying commerce infrastructure yours. Saleor's open-source/self-hostable model provides a materially stronger exit strategy.

For a one-person dropshipping side hustle on a tight budget, I’d pick Shopify if your priority is getting a real store live quickly and having room to scale.

My ranking

1. Shopify — best overall

• Very fast setup and no coding.
• Built specifically for ecommerce, with unlimited products, checkout, payments, social/marketplace selling, and a large app ecosystem. Shopify Shopify
• Current Basic pricing is $39/month month-to-month or $29/month billed yearly, although Shopify is currently advertising an introductory offer of $1/month for the first 3 months after the free trial. Shopify
• Particularly good for dropshipping because you can connect product-sourcing apps directly to the store. Shopify
• Big Cartel — cheapest way to test

• Its free Gold plan lets you sell up to 5 products with no monthly subscription. Big Cartel
• Extremely simple and quick to launch.
• The catch: it's much more limited than Shopify, and its free tier isn't really designed around building a sophisticated dropshipping operation.
• Paid plans start at $15/month. Big Cartel
• WooCommerce — cheapest if you're technically comfortable

• The software itself is flexible, but you have to deal with WordPress hosting and setup. WooCommerce explicitly requires you to choose hosting for your store. WooCommerce
• I'd skip it for your situation unless saving every monthly dollar matters more than speed and simplicity.

What I'd do in your shoes

Start with Shopify, but keep the initial spend extremely lean.

You don't need a fancy $200 theme, 15 paid apps, or hundreds of dollars of ads. Start with:

• Shopify's introductory offer
• Free theme
• 1–3 products, not 50
• One reliable supplier
• One simple payment setup
• Organic TikTok/Instagram/Shorts content initially
• Don't buy inventory until you've validated demand

The important distinction is that the platform isn't what makes dropshipping profitable. Your biggest risks are picking a weak product, having poor supplier/shipping reliability, and spending on ads before you've validated the offer.

If you're really at the "I have $0–$50 to test this" stage, I'd start with Big Cartel's free tier to validate the idea, then move to Shopify once you have evidence that people actually want the product. Big Cartel

shopify.com · bigcartel.com

For a small team doing print-on-demand dropshipping, I’d recommend Shopify as the store builder, paired with a dedicated personalization/product-preview app.

The important distinction is that I wouldn’t choose a store builder based solely on its native personalization features. Shopify’s ecosystem is unusually strong here: its App Store currently has hundreds of custom-product apps, including tools specifically offering live previews and POD personalization. Shopify App Store Shopify App Store

My recommendation: Shopify + a POD personalizer

Best overall setup:

• Store: shopify.com
• POD fulfillment: Printful, Printify, or another provider depending on your catalog/margins
• Personalization: a dedicated product customizer with live preview

For example, Customall Product Personalizer is particularly relevant to POD: it supports text, image uploads, clipart, real-time previews, high-resolution output, and integrations with Printful, Printify, Gearment, Dreamship and others. Shopify App Store

Other Shopify options include:

• Zepto Product Personalizer — strong if you need flexible product options plus live preview; currently rated 4.9/5 with 1,300+ reviews in the Shopify App Store. Shopify App Store
• Zakeke — worth considering if you want more sophisticated 2D/3D customization, live preview and AR. Shopify App Store
• Fancy Product Designer — another established option for a full product-design experience. Shopify App Store
• Kickflip — good candidate if your products involve fairly complex visual configuration. Shopify App Store

Why I'd pick Shopify for a small team

The big advantage isn't just the storefront. It's how quickly you can assemble the entire operation without engineering everything yourself:

Customer → Shopify product page → visual personalization → preview → checkout → POD fulfillment

That matters a lot when you're a small team. You can spend your development time on your product experience and conversion rate rather than maintaining a custom commerce backend.

Shopify also has a large ecosystem of apps for custom options, file uploads, variants, previews, and personalization. Shopify App Store

When I'd choose something else

I'd consider WooCommerce if you already have strong WordPress/development expertise and want maximum control over the frontend and customization logic.

I'd consider a custom/headless storefront only once your personalization experience becomes a genuine competitive advantage—for example, sophisticated canvas editing, dynamic product rendering, AI-generated designs, complicated pricing rules, or highly customized production workflows.

For a small team, I'd avoid going there initially. The operational overhead usually isn't worth it.

The stack I'd build

If I were starting this business today, I'd probably use:

Shopify + Customall/Zepto + Printify or Printful

Then I'd make the personalization experience the centerpiece of the product page:

1. Choose product/color.
2. Enter name/text or upload image.
3. See the actual product update immediately.
4. Manipulate the design if appropriate.
5. See front/back/alternate views.
6. Show the final price.
7. Add to cart.
8. Automatically send the correct production artwork to the POD provider.

That last part is crucial. Don't settle for an app that merely collects personalization information. You want the customer's configuration to reliably become the production-ready file/order data that your fulfillment provider needs.

If you tell me what you're selling (e.g. personalized shirts, mugs, posters, jewelry, wall art, books, etc.) and whether customers need text only vs. uploading photos/designing from scratch, I can narrow this down to the 2–3 best Shopify stacks for your exact use case, including approximate monthly cost and how I'd structure the workflow.

I'd consider WooCommerce if you already have strong WordPress/development expertise and want maximum control over the frontend and customization logic.

I'd consider a custom/headless storefront only once your personalization experience becomes a genuine competitive advantage—for example, sophisticated canvas editing, dynamic product rendering, AI-generated designs, complicated pricing rules, or highly customized production workflows.

For a small team, I'd avoid going there initially. The operational overhead usually isn't worth it.

The stack I'd build

If I were starting this business today, I'd probably use:

Shopify + Customall/Zepto + Printify or Printful

Then I'd make the personalization experience the centerpiece of the product page:

1. Choose product/color.
2. Enter name/text or upload image.
3. See the actual product update immediately.
4. Manipulate the design if appropriate.
5. See front/back/alternate views.
6. Show the final price.
7. Add to cart.
8. Automatically send the correct production artwork to the POD provider.

That last part is crucial. Don't settle for an app that merely collects personalization information. You want the customer's configuration to reliably become the production-ready file/order data that your fulfillment provider needs.

If you tell me what you're selling (e.g. personalized shirts, mugs, posters, jewelry, wall art, books, etc.) and whether customers need text only vs. uploading photos/designing from scratch, I can narrow this down to the 2–3 best Shopify stacks for your exact use case, including approximate monthly cost and how I'd structure the workflow.

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

My shortlist for 2026:

1. medusajs.com — my first choice

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

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

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

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

You could have a custom supplier module that handles:

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

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

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

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

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

It's especially interesting if you eventually want:

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

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

3. vendure.io — excellent TypeScript alternative

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

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

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

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

ShippingPlugin
├── SupplierShippingRates
└── CustomerShippingRates

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

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

WooCommerce is the pragmatic choice.

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

But there's an important distinction:

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

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

For example, if your long-term goal is:

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

I'd choose Medusa over WooCommerce.

If it's:

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

I'd choose WooCommerce.

5. Sylius

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

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

What I'd build for your use case

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

Something like:

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

Then create a supplier abstraction:

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

That gives you a huge advantage.

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

You could even eventually build:

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

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

My ranking for you

If full integration control is the primary requirement:

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

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

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

For a dropshipping catalog that needs constant optimization (finding winners, killing losers, improving margins, tracking suppliers, and scaling ads), the “best analytics” platform depends on whether you value out-of-the-box reporting or maximum customization.

My ranking:

Shopify TechnologyAdvice## Best overall for dropshipping analytics: Shopify

For most dropshipping businesses, I would choose Shopify because the analytics ecosystem is stronger than the native dashboard alone. You get:

• Product-level sales tracking
• Conversion funnels
• Customer cohorts
• Marketing attribution through integrations
• Inventory and fulfillment insights
• A very large ecosystem of analytics, CRO, and advertising tools

The biggest advantage is speed: you can connect supplier apps, ad platforms, email tools, and analytics dashboards without building much infrastructure. Shopify is widely used by dropshippers because of its app ecosystem and supplier integrations. eSellSphere Ecommerce-Platforms.com

Where Shopify can fall short:

• Advanced reporting may require higher plans or third-party apps.
• Large catalogs can become harder to analyze without additional tools.

Best native reporting for a large dropshipping catalog: BigCommerce

If your catalog has:

• thousands of SKUs,
• many variants,
• multiple suppliers,
• complex product categories,

BigCommerce may be stronger. It is designed around more complex catalogs and provides robust built-in commerce features without relying as heavily on extensions. TechnologyAdvice Peasy

Useful reports include:

• Product performance
• Customer segmentation
• Sales trends
• Multi-store reporting
• Inventory insights

Best if you want a “data scientist” setup: WooCommerce

WooCommerce gives you the most control because you own the database and can connect almost any analytics stack:

• Google Analytics 4
• Looker Studio
• custom SQL dashboards
• customer lifetime value models
• predictive analytics

The tradeoff is that you usually need more technical work. PayHelm

For optimizing a dropshipping catalog, prioritize these analytics

Regardless of platform, I would focus on:

1. SKU profitability

• Revenue
• Product cost
• Shipping cost
• Ad spend
• Refund rate
• Net margin
• Product velocity

• Orders per day
• Conversion rate
• Traffic-to-purchase ratio
• Customer quality

• Repeat purchase rate
• Customer lifetime value
• Average order value
• Supplier performance

• Delivery time
• Refunds
• Defect rate
• Stock reliability
• Ad-to-product attribution

• Which ads create profitable customers
• Which products only generate expensive clicks

My recommendation by store stage

• 0–500 products: Shopify + analytics apps/dashboard tools
• 500–10,000 products: BigCommerce or Shopify with a strong analytics stack
• 10,000+ SKUs or complex supplier network: BigCommerce, WooCommerce with custom BI, or Adobe Commerce
• Testing hundreds of products quickly: Shopify usually wins because speed matters more than perfect native reporting

For most dropshippers, I would start with Shopify + a dedicated analytics layer rather than choosing a platform solely for built-in reports. The ability to rapidly test products, track ad profitability, and automate decisions usually matters more than the native dashboard. Shopify PayHelm

If your main requirement is automatically deciding which dropship supplier gets each line item and splitting a single customer order across multiple suppliers, I’d shortlist Order Desk and Pipe17.

My recommendation

For a dropship-heavy business: start with orderdesk.com.

It is particularly well suited to vendor-based fulfillment:

• You can assign products/SKUs to specific dropship vendors.
• It can automatically split an order by vendor.
• Rules can then send each split order to the appropriate supplier via integration, email, FTP/export, etc.
• Supplier tracking can flow back into the order and ultimately back to your storefront. Order Desk Knowledge Base Order Desk Knowledge Base Order Desk
• It has 400+ integrations, which is useful if your suppliers use a mixture of APIs, EDI-ish workflows, spreadsheets, email, or fulfillment platforms. Order Desk

Choose pipe17.com instead if your problem is more sophisticated fulfillment orchestration.

Pipe17 is stronger when routing needs to consider things like:

inventory → supplier/3PL → geography → shipping cost/SLA → fallback supplier → split if necessary

Its routing engine can route at the line-item level, use inventory and customer location, and split orders across fulfillment locations. It also supports automatic rerouting when fulfillment fails. Pipe17 Pipe17 Help Center

Quick decision

One interesting option is using them together: Pipe17 can provide the connectivity/inventory data layer while Order Desk handles rules such as splitting and dropship-vendor selection. Pipe17 explicitly supports this architecture. Pipe17

If you tell me your stack (e.g. Shopify + 20 suppliers + suppliers receive orders by API/email/CSV), I can recommend the best architecture and show you exactly how I'd set up the routing rules.

Yes. There are several tools that can cover most or all of that workflow, but the best choice depends on whether you already have a store platform such as Shopify.

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

• subbly.co — probably the most directly aligned with a small subscription-box business. It handles recurring payments, subscription plans, customer management, and can integrate with an existing Shopify store. Subbly Subbly
• paywhirl.com — particularly interesting if you're already running your store elsewhere. It supports recurring billing, customer self-service, payment retries, and subscription-box planning. PayWhirl
• ordergroove.com — the more sophisticated option. It can manage recurring orders, shipment cadence, skips/swaps, payment recovery, inventory forecasting, and even rotating/curated boxes. Ordergroove Ordergroove Ordergroove API Reference
• apps.shopify.com — if you're already on Shopify, there are 100+ subscription apps, including Recharge, Ordergroove, Subbly, and others. Shopify App Store

The important distinction

What you're describing is actually four separate jobs:

1. Recurring payments — charge the customer monthly/quarterly.
2. Shipment cadence — know who gets a box this month, next month, etc.
3. Box recipe / packing list — e.g.

1 candle + 1 soap + 1 card + 1 mystery item

4. Fulfillment — turn those subscriptions into actual pick/pack/ship work.

Most subscription apps are excellent at 1–2, and some handle 3. The actual physical pick/pack workflow often needs either an inventory/fulfillment system or a third-party fulfillment service.

For example, Ordergroove supports fixed bundles and rotating curated boxes, and can pass the component SKUs into the recurring order. Ordergroove Ordergroove API Reference

If you're a small handmade-goods operation and packing the boxes yourself, I'd lean toward Subbly or PayWhirl + your existing ecommerce platform, rather than jumping straight to an enterprise system like Ordergroove.

If you tell me what platform your store is on (Shopify, Etsy, WooCommerce, Squarespace, etc.) and roughly how many boxes you ship per month, I can narrow this down to 2–3 options and show you exactly how I'd set up the packing-list + cadence + payment workflow.

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

My default recommendation:

1. Best overall hybrid SaaS + physical product: Shopify + subscription app + your existing SaaS billing

Use Shopify for:

• physical inventory
• shipping
• fulfillment integrations
• subscription boxes/refills
• commerce checkout

Keep your SaaS billing in your current system (often Stripe Billing).

Shopify’s subscription ecosystem supports recurring physical products, and apps can manage subscription plans, customer portals, and recurring orders. Shopify Help Center Shopify Help Center

Good subscription layers:

• Recharge — strong for DTC subscriptions, swaps, skips, retention workflows
• Appstle — good value for early-stage brands
• Skio — popular with scaling consumer subscription brands

This is what I’d choose if your SaaS customers are buying:

• hardware
• consumables
• replacement parts
• monthly kits
• physical + software bundles

2. Best if your product experience is still primarily SaaS: Stripe Billing + fulfillment partner

If the physical product is more like:

“Pay $99/month for software, and we ship you a device/refills as part of the plan”

then staying closer to Stripe may be cleaner.

Stripe Billing is designed around SaaS subscription models, customer portals, recurring payments, and flexible pricing logic. Stripe Docs Stripe Docs

You’d typically pair it with:

• a 3PL (fulfillment warehouse)
• inventory system
• shipping API
• your own customer experience

Pros:

• one customer/subscription record
• easier entitlement logic
• better for usage-based or hybrid pricing

Cons:

• you’re building more commerce infrastructure yourself

3. If you expect enterprise complexity: Chargebee

Consider Chargebee if you have:

• multiple subscription tiers
• contracts
• invoices
• B2B customers
• revenue recognition needs
• complex pricing experiments

It’s usually too heavy for an early SaaS founder just testing physical subscriptions.

My decision rule

• Physical product is the main thing customers buy → Shopify + Recharge/Appstle/Skio
• Software is the main thing and physical is an add-on → Stripe Billing + fulfillment stack
• Enterprise SaaS with complex billing → Chargebee or Stripe Billing

For most SaaS founders adding their first physical subscription, I’d pick:

Stripe for your SaaS subscription + Shopify for physical subscriptions, connected by customer identity.

That gives you the least painful path if the physical side unexpectedly becomes a big business.

A few questions would change the recommendation:

1. Is the physical product required to use the SaaS (hardware/device model) or just an add-on?
2. Are you already using Stripe, Paddle, Chargebee, or something else for SaaS billing?
3. Roughly how many physical subscribers do you expect in year one (100, 1k, 10k+)?

1. Is the physical product required to use the SaaS (hardware/device model) or just an add-on?
2. Are you already using Stripe, Paddle, Chargebee, or something else for SaaS billing?
3. Roughly how many physical subscribers do you expect in year one (100, 1k, 10k+)?

For your requirements—custom storefront + recurring subscription plans + strong APIs—I’d shortlist Medusa, Shopify, and commercetools, with Medusa as my first choice if you want maximum control over the subscription experience.

1. My pick: Medusa

Medusa is particularly attractive if subscriptions are central to your business model rather than just a recurring-product feature. It's open source, headless, JavaScript/TypeScript-oriented, and designed for custom commerce workflows. Its subscription documentation shows how to implement recurring purchases, renewals, expiration, cancellation, and customer subscription management through custom API routes. Medusa Docs Medusa

There's also a Medusa subscription plugin called Reorder that adds plans/offers, renewals, dunning, cancellation/retention flows, activity logs, and analytics. Medusa

medusajs.com

Why I'd choose it: you can make the subscription domain behave exactly how your business needs—custom plan logic, upgrade/downgrade rules, entitlements, billing cycles, usage limits, account portals, etc.—without fighting a SaaS platform's abstractions.

The tradeoff is that you own more engineering and operational complexity.

2. Shopify — best if you want less backend work

Shopify is probably the safest choice if you want to launch quickly while still having a completely custom frontend.

Its Storefront API exposes selling plans, including recurring-delivery information, pricing adjustments, billing/delivery policies, and subscription line items. You can create carts containing a selected subscription selling plan directly through the API. Shopify Shopify

shopify.dev

I'd pick Shopify if your requirements are essentially:

"Customers choose monthly/annual plans, pay, manage their subscription, and we want a custom React/Next.js/etc. frontend."

I'd pick Medusa instead if you're saying:

"Subscriptions are the core product, and we need unusual subscription/business logic."

3. commercetools — best enterprise option

commercetools is worth considering if you're building a large-scale composable architecture and already expect multiple services around commerce.

Its APIs are particularly strong, and its Checkout Transactions API can initiate payments without using its Checkout UI, including payments for subscription-based orders. commercetools Documentation

commercetools.com

The downside is substantially more architecture and implementation work than Shopify.

What I'd build

For a subscription-first product, I'd lean toward:

Next.js/React storefront → your API/BFF → Medusa → Stripe → database/event infrastructure

with the commerce platform responsible for things like:

• Products and pricing
• Customers
• Carts/orders
• Subscription plans
• Subscription lifecycle
• Entitlements
• Renewals
• Cancellation/pause/resume
• Webhooks/events

And keep your own API layer in front of it if you have mobile apps, partner integrations, or multiple storefronts.

Bottom line:
Choose Medusa for maximum control and an API-first, subscription-centric product.
Choose Shopify for the fastest/lowest-risk implementation.
Choose commercetools if you're an enterprise team building a broader composable-commerce ecosystem.

If you tell me whether these are physical-product subscriptions, SaaS/software subscriptions, memberships, or a mix, I can narrow this to a specific architecture and payment stack.

Why I'd choose it: you can make the subscription domain behave exactly how your business needs—custom plan logic, upgrade/downgrade rules, entitlements, billing cycles, usage limits, account portals, etc.—without fighting a SaaS platform's abstractions.

The tradeoff is that you own more engineering and operational complexity.

2. Shopify — best if you want less backend work

Shopify is probably the safest choice if you want to launch quickly while still having a completely custom frontend.

Its Storefront API exposes selling plans, including recurring-delivery information, pricing adjustments, billing/delivery policies, and subscription line items. You can create carts containing a selected subscription selling plan directly through the API. Shopify Shopify

shopify.dev

I'd pick Shopify if your requirements are essentially:

"Customers choose monthly/annual plans, pay, manage their subscription, and we want a custom React/Next.js/etc. frontend."

I'd pick Medusa instead if you're saying:

"Subscriptions are the core product, and we need unusual subscription/business logic."

3. commercetools — best enterprise option

commercetools is worth considering if you're building a large-scale composable architecture and already expect multiple services around commerce.

Its APIs are particularly strong, and its Checkout Transactions API can initiate payments without using its Checkout UI, including payments for subscription-based orders.

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

My pick: Chargebee

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

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

chargebee.com

When I'd choose Recurly instead

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

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

docs.recurly.com

Practical decision

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

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

For perishable weekly subscription boxes with scheduled delivery windows, I’d generally recommend Shopify + a subscription app + a delivery-slot/capacity app.

My recommendation: Shopify

shopify.com is the best overall choice if you want something relatively easy to operate and expect to grow.

A good architecture would be:

• Shopify — storefront, checkout, customers, orders, payments.
• Recharge or Appstle Subscriptions — recurring weekly billing and subscription management. Shopify specifically highlights Recharge, Appstle, and other subscription apps for recurring-commerce use cases. Shopify
• Delivery scheduling app — customer chooses a delivery day/time window, while you enforce cutoff times, blackout dates, preparation time, and maximum orders per slot.
• Shopify Local Delivery — useful if you're doing your own local delivery; it supports delivery zones and route optimization. Shopify

For example, your checkout could work like:

Weekly Farm Box — $49/week
Delivery: Thursday
Choose window: 4–6 PM / 6–8 PM

Next delivery: Sept. 3
Skip next week | Change delivery day | Cancel subscription

The important part is that delivery capacity should be treated as a first-class constraint, not merely a date picker. Some Shopify delivery apps support order limits per time slot, cutoff times, preparation times, and blackout dates. Shopify App Store Shopify App Store

When I'd choose WooCommerce instead

WooCommerce + WooCommerce Subscriptions is arguably more flexible if your delivery logic is unusually complicated.

Its delivery tooling can handle things particularly relevant to perishables:

• weekly subscription intervals
• delivery dates tied to the subscription cycle
• cutoff times
• minimum preparation time
• holidays/blackout dates
• fully booked delivery slots
• automatically calculating the next valid delivery date for renewals WooCommerce

WooCommerce also has an official Order Delivery extension that supports delivery time slots, capacity/cutoffs, holidays and subscription renewals. WooCommerce

So I'd choose WooCommerce if you need something like:

"Customers in ZIP 782xx can receive Tuesday 3–5 PM, but only 30 boxes per route; orders close Sunday at midnight; holidays shift the subscription to the next available route; payment should occur 48 hours before fulfillment."

That's the sort of rule-heavy operation where WooCommerce's extensibility becomes attractive.

Quick comparison

One important distinction

If by "delivery windows" you mean your own local delivery routes (e.g. "Tuesday 4–6 PM, Wednesday 5–7 PM"), I'd favor Shopify.

If you mean nationwide refrigerated shipping (UPS/FedEx/USPS, insulated packaging, shipping cutoffs, temperature concerns), the architecture changes somewhat: I'd still consider Shopify, but I'd put much more emphasis on the fulfillment/shipping layer rather than the ecommerce platform itself.

Bottom line: For a typical local/regional weekly fresh-food box business, I'd start with Shopify + Appstle/Recharge + a delivery scheduling app with per-slot capacity limits. Shopify already handles local-delivery zones and customer notifications, while the app layer fills in the more specialized scheduling functionality. Shopify Shopify App Store

If you tell me (1) local vs. nationwide delivery, (2) approximate weekly orders, and (3) whether customers can choose/change their delivery day, I can recommend the specific stack and approximate monthly cost.

Yes. skio.com looks like a particularly strong match if you're running subscriptions on Shopify.

It supports all three of the things you mentioned:

• Gifting: Customers can gift their next order instead of skipping it (“Gift on skip”), and Skio also supports prepaid gift subscriptions. Skio Skio
• Pausing: Customers can pause temporarily for a defined period or indefinitely, then resume later. Skio changelog.skio.com
• Swapping: Customers can swap products directly in the subscription portal, including swapping one product for another. Skio skio.zendesk.com
• One-click actions: Skio can generate links for things like pausing, unpausing, swapping, adding products, and gifting that you can put into email/SMS flows. Skio

One important distinction: “gift my next shipment” and “buy a subscription as a gift for someone else” are different workflows. Skio supports both, but the latter is currently implemented as prepaid gift subscriptions and has some limitations around recipient product changes. Skio

If you tell me what you're selling and whether you're on Shopify, I can also compare Skio against Recharge, Loop, Stay AI, and SmartrMail specifically for gifting + pause + product swaps.

If subscription commerce + headless APIs are the two non-negotiables for an enterprise merchant, my recommendation would be:

1. commercetools — best for API-first enterprise architecture

commercetools.com

I’d put commercetools first if the merchant has a strong engineering organization and wants a genuinely composable/headless architecture. It is explicitly API-first, modular, and designed for enterprise-scale commerce across channels. commercetools commercetools

The important caveat: subscriptions are not really its core native commerce abstraction. You'd typically pair the commerce engine with a subscription/billing platform and orchestrate the two.

Best fit: sophisticated enterprise, complex catalogs/pricing, multiple channels, strong internal engineering, willingness to compose the stack.

2. BigCommerce — best balance of enterprise + headless + merchant usability

bigcommerce.com

For many merchants, BigCommerce is the pragmatic choice. It provides REST and GraphQL APIs, supports fully headless storefronts, and has substantial enterprise/B2B functionality without requiring you to assemble as much of the underlying commerce stack yourself. BigCommerce BigCommerce

Its B2B APIs cover companies, users, quotes, invoices, payments, shopping lists, etc., and its GraphQL Storefront API is specifically positioned for headless experiences. BigCommerce BigCommerce

Again, for recurring product subscriptions, I'd plan on integrating a dedicated subscription engine rather than choosing BigCommerce because of native subscription capabilities.

Best fit: enterprise merchant that wants headless APIs but doesn't want the operational complexity of a fully composable stack.

3. Shopify Plus — best if subscription capability/ecosystem matters more than architectural purity

shopify.com

Shopify Plus is worth serious consideration if the merchant values speed to market, ecosystem, checkout, and operational simplicity. Shopify has also pushed substantially into headless commerce and enterprise B2B. Shopify

The tradeoff is that Shopify's model is less "build your own commerce infrastructure from APIs" than commercetools. You get a much more opinionated platform.

My shortlist

What I'd actually build

For a serious subscription merchant, I'd think of the architecture as:

Headless storefront → commerce platform → subscription/billing engine → payment processor

rather than expecting one commerce platform to perfectly handle catalog, cart, checkout, recurring billing, entitlement, dunning, and lifecycle management.

So my recommendation is:

• Choose commercetools + dedicated subscription platform if the merchant is technically sophisticated and expects complex/global commerce.
• Choose BigCommerce + subscription platform if you want the best combination of enterprise commerce functionality, APIs, and manageable implementation.
• Choose Shopify Plus + subscription ecosystem if merchant operations and speed are more important than maximum architectural flexibility.

If you tell me B2C vs B2B, number of SKUs, geographic footprint, and whether subscriptions are physical products or SaaS/memberships, I can narrow this down to a specific platform + subscription stack.

I’d put commercetools first if the merchant has a strong engineering organization and wants a genuinely composable/headless architecture. It is explicitly API-first, modular, and designed for enterprise-scale commerce across channels. commercetools commercetools

The important caveat: subscriptions are not really its core native commerce abstraction. You'd typically pair the commerce engine with a subscription/billing platform and orchestrate the two.

Best fit: sophisticated enterprise, complex catalogs/pricing, multiple channels, strong internal engineering, willingness to compose the stack.

2. BigCommerce — best balance of enterprise + headless + merchant usability

bigcommerce.com

For many merchants, BigCommerce is the pragmatic choice. It provides REST and GraphQL APIs, supports fully headless storefronts, and has substantial enterprise/B2B functionality without requiring you to assemble as much of the underlying commerce stack yourself. BigCommerce BigCommerce

Its B2B APIs cover companies, users, quotes, invoices, payments, shopping lists, etc., and its GraphQL Storefront API is specifically positioned for headless experiences. BigCommerce BigCommerce

Again, for recurring product subscriptions, I'd plan on integrating a dedicated subscription engine rather than choosing BigCommerce because of native subscription capabilities.

Best fit: enterprise merchant that wants headless APIs but doesn't want the operational complexity of a fully composable stack.

3. Shopify Plus — best if subscription capability/ecosystem matters more than architectural purity

shopify.com

Shopify Plus is worth serious consideration if the merchant values speed to market, ecosystem, checkout, and operational simplicity. Shopify has also pushed substantially into headless commerce and enterprise B2B. Shopify

The tradeoff is that Shopify's model is less "build your own commerce infrastructure from APIs" than commercetools. You get a much more opinionated platform.

My shortlist

What I'd actually build

For a serious subscription merchant, I'd think of the architecture as:

Headless storefront → commerce platform → subscription/billing engine → payment processor

rather than expecting one commerce platform to perfectly handle catalog, cart, checkout, recurring billing, entitlement, dunning, and lifecycle management.

So my recommendation is:

• Choose commercetools + dedicated subscription platform if the merchant is technically sophisticated and expects complex/global commerce.
• Choose BigCommerce + subscription platform if you want the best combination of enterprise commerce functionality, APIs, and manageable implementation.
• Choose Shopify Plus + subscription ecosystem if merchant operations and speed are more important than maximum architectural flexibility.

If you tell me B2C vs B2B, number of SKUs, geographic footprint, and whether subscriptions are physical products or SaaS/memberships, I can narrow this down to a specific platform + subscription stack.

For a small manufacturer selling wholesale to retailers, I’d put BigCommerce B2B Edition at the top of the list.

My recommendation

1. bigcommerce.com — best overall fit

It lines up unusually well with your requirements:

• Quote requests: retailers can request quotes from product pages, carts, quick-order areas, etc., and your sales team can modify pricing, discounts, products, shipping, and expiration dates. BigCommerce BigCommerce
• Net terms: you can assign payment terms at the individual company level, including terms up to Net 60. BigCommerce BigCommerce
• Retailer accounts: company accounts, buyer roles, permissions, purchase orders, and customer-specific pricing are built into B2B Edition. BigCommerce BigCommerce
• Credit controls: you can put customers on credit hold or restrict PO orders based on a configured credit amount. BigCommerce
• Less app sprawl: these B2B capabilities are native to B2B Edition rather than requiring you to bolt everything onto a basic ecommerce site. BigCommerce

For a manufacturer, I'd favor this over a consumer-first store builder because RFQs → negotiated price → PO/net terms → reorder is a core workflow rather than an afterthought.

2. shopify.com — best if simplicity/ecosystem matters

Shopify is a very good alternative, particularly if you might eventually sell both DTC and wholesale from the same storefront.

Its B2B functionality supports company accounts and Net 7/15/30/45/60/90, and you can require B2B orders to be submitted as drafts for your review before accepting them. Shopify Help Center Shopify Help Center Shopify Help Center

The catch is quotes. Shopify's native workflow is more centered on draft orders than a dedicated buyer-facing RFQ system, so you may end up adding an app/customization for a polished "Request a Quote" experience. Shopify itself acknowledges that more sophisticated B2B workflows can require apps or customization. Shopify

3. WooCommerce — worth considering if you already use WordPress

WooCommerce can be attractive if you have someone technical on staff and want maximum control. There are wholesale extensions that add B2B functionality, but you'll generally be assembling more of the stack yourself rather than getting the quote/terms/account workflow as an integrated B2B system.

What I'd choose

For a small manufacturer, I'd start by getting a BigCommerce B2B demo and specifically ask them to show you this exact workflow: retailer requests quote → you approve/change price → retailer accepts quote → PO/Net 30 checkout → invoice → retailer logs back in and reorders.

That will tell you much more than a generic ecommerce demo. BigCommerce explicitly supports the quote and payment-on-terms pieces of that workflow. BigCommerce BigCommerce

If you tell me roughly how many SKUs you have, how many retailers you sell to, whether you already use QuickBooks/NetSuite/etc., and whether you need a DTC storefront too, I can narrow this down to the best 2–3 options and estimated cost/complexity.

Yes. For those requirements, I’d look at B2B-first commerce platforms rather than a generic Shopify-style store builder.

My top pick: OroCommerce

oroinc.com is probably the strongest fit if your sales process is genuinely B2B and you want the system to accommodate custom workflows.

It supports:

• Business/customer registration and approval — configurable workflows can route customer/order approvals based on your rules. ORO INC. ORO INC.
• Net terms / invoicing — buyers can access invoices and account information through the B2B portal, with invoicing/payment workflows integrated into the platform. ORO INC. ORO INC.
• Sales reps — built-in CRM, account ownership, quoting, customer history, and tools for reps to create/manage orders. ORO INC. ORO INC.
• Complex B2B pricing — customer-specific pricing, price lists, account hierarchies, approval chains, etc. ORO INC.
• ERP integration — including NetSuite, SAP, Microsoft Dynamics and others. ORO INC.

The caveat: I wouldn't assume OroCommerce's standard package calculates sales-rep commissions exactly the way you want. Its CRM/reporting/workflow capabilities can support the process, but I'd specifically ask them to demonstrate commission calculation and payout reporting using your rules.

Another strong option: Pepperi

pepperi.com is particularly interesting if your sales reps are a major part of the business.

Pepperi combines a B2B storefront with sales-rep order taking, customer-specific catalogs/pricing, approval workflows, invoice portals, and AR information. It also provides sales-rep performance/target reporting. B2B Commerce Platform | Pepperi B2B Commerce Platform | Pepperi

I'd put Pepperi ahead of OroCommerce if your model is "sales reps + wholesale customers + online ordering" rather than primarily self-service ecommerce.

If you're already on Shopify

shopify.com can get surprisingly close with B2B apps. For example, NET30 provides customer credit approval, Net 15/30/60 terms, automatic invoices, credit limits and payment tracking inside Shopify. NET30

But you'd likely need a separate solution for sales-rep commission calculation, so I wouldn't choose this architecture if commissions are a core requirement and you want everything tightly integrated.

What I'd choose

My recommendation: start with OroCommerce if you need a serious B2B portal with approval workflows, account hierarchies, invoicing, reps and ERP integration. Start with Pepperi if your sales-rep/field-sales operation is the center of the business.

If you tell me what ERP/accounting system you use (NetSuite, QuickBooks, Dynamics, SAP, etc.) and how you calculate commissions (e.g. 5% of collected sales, commission by rep/product/customer, split commissions), I can narrow this to 2–3 platforms and identify which one can handle the whole workflow without custom development.

Yes. What you’re describing is a B2B/wholesale ecommerce platform, and there are several that are specifically designed to preserve the messy parts of wholesale—customer-specific catalogs/pricing, negotiated prices, and quotes—rather than forcing everything into a standard Shopify-style retail model.

My shortlist

BigCommerce B2B Edition would be my first one to investigate. It has native customer groups and price lists, including SKU-level pricing for individual customers, and its B2B buyer portal supports quote requests. BigCommerce BigCommerce BigCommerce

The quote functionality is particularly relevant to your "open quotes" requirement: quotes can have customized line-item pricing/discounts, custom products, shipping terms and expiration dates, and can ultimately go through checkout. BigCommerce

If migration is the hard part

I'd evaluate the platforms based on whether they can migrate the relationships between your data, not merely your products.

You'd want the migration to preserve something like:

Customer → catalog access → customer price list → price overrides → historical/open quotes → orders

For example, if Customer A currently gets:

• SKU 123 at $14.20
• SKU 456 at $8.75
• 10% off Category X
• access only to 600 of your 4,000 SKUs
• three outstanding quotes with negotiated prices

you don't want a migration that merely imports the 4,000 products and 500 customers. You want those commercial relationships reconstructed on the new platform.

BigCommerce explicitly supports customer/company assignments, customer groups, price lists and bulk CSV updates, which makes this kind of migration feasible. BigCommerce

OroCommerce is worth a serious look if your pricing and quoting are particularly complicated. It is built around distributors/manufacturers and supports customer-specific pricing, customer-specific catalogs, RFQs/quotes, and sales-rep workflows. ORO INC. ORO INC.

BlueCart is another interesting option if you want something more wholesale-native and less enterprise-heavy. It supports individual buyer portals with account-specific catalogs, pricing and SKUs. BlueCart

One important distinction

If by "open quotes" you mean existing quotes that are currently sitting in your sales system and need to remain actionable after migration, that's a more specialized requirement.

I'd specifically ask every vendor:

"Can you migrate open quotes with their original customer, line items, negotiated prices, expiration dates, notes, sales rep, and quote status—and can the customer accept the migrated quote and convert it to an order?"

That's different from simply having a Request a Quote feature.

If you tell me what your current wholesale system is (e.g. Excel + QuickBooks, WooCommerce, Shopify, Magento, custom site, ERP, etc.) and roughly how many SKUs/customers you have, I can narrow this down to 2–3 platforms and tell you which one I'd choose.

For a B2B ecommerce business, I’d shortlist three approaches, depending on whether you want to own the credit relationship or outsource the risk.

My recommendation

Start with Resolve if you’re scaling and want a fairly complete solution rather than stitching together credit checks + invoicing + collections.

resolvepay.com offers an end-to-end B2B net-terms workflow: credit underwriting, automated invoicing, collections, reconciliation, and integrations with ecommerce/ERP systems including Shopify, BigCommerce, Magento, WooCommerce, QuickBooks, and Oracle. ResolvePay

That makes it particularly attractive if your workflow is:

B2B customer applies → credit approved → credit limit assigned → customer orders → invoice generated → reminders sent → payment reconciled → limit restored.

Other good fits

• Balance — best if you want to offer Net 30/60/90 while outsourcing credit risk and AR complexity. It handles credit applications, invoicing, payments, collections, and reconciliation, and can pay the merchant upfront. Balance
• Net Terms by LIETL Solutions — interesting for a Shopify-centric SMB/mid-market operation that wants to retain its own receivables. It specifically provides customer credit limits, checkout enforcement, automated invoices, email/SMS/WhatsApp reminders, aging reports, credit scoring, and accounting integrations. Net Terms
• Esker — stronger choice if you're a larger organization with sophisticated credit-control processes and an ERP such as SAP, Oracle, or Microsoft Dynamics. It supports credit limits, blocked-order workflows, credit decisioning, risk monitoring, and collections automation. Esker
• Billtrust — worth evaluating for larger AR organizations; G2 currently lists it among its leading enterprise credit/collections products, with particular emphasis on B2B invoicing, payments, automation, and reporting. G2

What I would implement

Regardless of vendor, I'd require these capabilities:

The key architectural decision is whether you want to carry the credit risk yourself.

If you do, I'd lean toward Net Terms or an enterprise credit/AR platform such as Esker. If you want to offer generous terms without taking on as much bad-debt/cash-flow risk, Resolve or Balance are more compelling. Capital One Trade Credit is another enterprise-scale option that combines underwriting, invoicing, collections, cash application, and risk protection. Capital One

If you tell me your ecommerce platform (Shopify, BigCommerce, WooCommerce, Magento, custom), approximate annual B2B revenue, and whether you want to retain or outsource credit risk, I can narrow this to 2–3 options and compare pricing/integration/credit-limit/reminder capabilities.

For a 3-person apparel brand, I’d generally recommend a hosted ecommerce platform rather than a general website builder. You need product variants (size/color), inventory tracking, discount logic, order management, and room to grow without a developer on staff. Ecommerce Website Create BigCommerce

My shortlist:

1. shopify.com — Best overall fit for most growing apparel brands

Why I’d put this first:

• Strong inventory management for size/color variants and SKUs
• Very easy for a small team to operate daily
• Large ecosystem for apparel needs (returns, reviews, email marketing, subscriptions, bundles, loyalty, etc.)
• Good themes and merchandising tools for fashion brands
• Discount codes, automatic discounts, customer-specific promotions, and campaign tools are well supported Ecommerce Website Create

Best if you are:

• Direct-to-consumer (DTC)
• Selling through Instagram/TikTok/social channels
• Running seasonal drops or collections
• Planning to hire more people later

Watch-outs:

• You may end up paying for several apps as you add advanced features.
• More complex inventory workflows may require integrations. BigCommerce

2. bigcommerce.com — Better if operations are getting complex

Consider this if you expect:

• Hundreds/thousands of SKUs
• Wholesale accounts
• Multiple storefronts
• More advanced catalog rules

BigCommerce tends to include more commerce functionality natively, which can reduce reliance on apps for some growing brands. BigCommerce BigCommerce

Downside: it can feel heavier than you need as a three-person team.

3. woocommerce.com — Best if you already live in WordPress

Good choice if:

• Your brand site is content-heavy
• You have technical help
• You want maximum customization

Less ideal if your team wants a low-maintenance system. Hosting, updates, plugins, and security become your responsibility.

4. squarespace.com — Best for small, highly visual collections

Great for:

• Capsule collections
• Premium branding
• Lookbook-style sites

Less ideal once inventory complexity becomes a major part of your business. Ecommerce Website Create

My recommendation for your situation

For a 3-person apparel brand, I’d start with:

Shopify + a clean theme + a small set of carefully chosen apps

A typical stack might be:

• Shopify → store, inventory, discounts, orders
• Klaviyo → email/SMS marketing
• Gorgias or Zendesk → customer support
• Loop Returns → apparel returns/exchanges
• ShipStation or ShipBob (depending on volume) → fulfillment workflows

Before choosing, I’d answer these four questions:

1. How many products/SKUs do you have today, and how many do you expect in 12 months?
2. Do you sell wholesale to boutiques, or only direct to consumers?
3. Are you doing limited drops/preorders, or keeping products always in stock?
4. Do you need a physical retail/POS system?

Those answers could move the recommendation between Shopify and BigCommerce.

For a 3-person apparel brand, I’d start with:

For a subscription box business, I’d pick Shopify first.

• Shopify — best overall fit. Its native Shopify Subscriptions app supports recurring billing, and customers can manage payment details, shipping addresses, pauses, skips, cancellations, upcoming orders, and past orders from their customer account. Shopify Help Center Shopify Help Center It also has a large ecosystem of subscription-box apps if you later need build-a-box, dunning, or more sophisticated subscription rules. Shopify App Store

shopify.com

• Wix — good if website design/ease of use is more important than sophisticated subscription operations. Wix directly supports subscription products and recurring payments, including subscription boxes. wix.com Wix Support

wix.com

• Stripe + a site builder — best if you want maximum billing flexibility or expect a more customized business. Stripe Billing provides recurring billing plus a hosted customer portal where customers can update payment methods, change/cancel subscriptions, and view invoices. Stripe Docs Stripe Docs The tradeoff is that Stripe isn't really the website builder itself.

stripe.com

My recommendation: Start with Shopify + Shopify Subscriptions. For a physical subscription box, it gives you the storefront, checkout, recurring billing, customer self-service, and fulfillment/e-commerce infrastructure in one place.

If you tell me your monthly subscriber count and whether customers need to customize what's inside each box, I can narrow it down to the best 2–3 options.

If analytics + conversion optimization are core requirements, I’d narrow it to Shopify vs. BigCommerce.

My pick: Shopify

For most ecommerce businesses, I’d choose Shopify.

Why:

• Strong built-in analytics: Shopify gives you dashboards and reports covering sales, traffic, conversion rate, AOV, returning customers, checkout behavior, and more. Shopify Help Center Shopify Help Center
• Conversion-focused commerce: checkout, Shop Pay, abandoned-cart recovery, merchandising, payments, and marketing are tightly integrated rather than bolted onto a generic website builder. Shopify
• Excellent ecosystem: when you eventually need A/B testing, personalization, advanced attribution, email/SMS, reviews, upsells, etc., Shopify has a huge app ecosystem.
• Good balance of simplicity and sophistication: you can start relatively simply without building an analytics/marketing stack from scratch, but there's plenty of room to scale.

shopify.com

When I'd pick BigCommerce instead

BigCommerce is arguably the better choice if deep ecommerce analytics and merchandising are more important than ease of use.

Its built-in analytics specifically expose things like storefront conversion rates, cart abandonment, AOV, product/customer trends, promotions, and sales channels. BigCommerce BigCommerce It also has particularly strong catalog, customer-group, multi-storefront, and checkout customization capabilities. BigCommerce

bigcommerce.com

How I'd decide

Bottom line: If you don't have an unusual requirement, I'd go Shopify. Its native analytics are already quite good, and the important advantage is that your traffic → product views → add-to-cart → checkout → purchase → customer data lives inside the same commerce system. Shopify also provides marketing reports that connect channels with conversions and customer value. Shopify Help Center

If you tell me what you're selling, roughly how much traffic/orders you expect, and whether you're B2C or B2B, I can give you a much more specific Shopify vs. BigCommerce recommendation.

For your use case—selling fine-art prints + licensing images + delivering high-resolution files—I’d shortlist Pixieset, Zenfolio, and SmugMug, but my first choice would be Pixieset.

My recommendation: Pixieset

Pixieset is probably the best all-around fit if you want your website, galleries, ecommerce, print fulfillment, and digital delivery under one roof.

• High-res delivery: supports automatic digital downloads, including high-resolution files, with secure download links. Pixieset Pixieset Help Center
• Print sales: customers can buy prints directly from galleries, with professional lab fulfillment and shipping handled automatically. Pixieset
• Your pricing: you set your own retail prices/markup rather than being locked into a marketplace's pricing. Paid plans currently advertise 0% store commission. Pixieset
• Licensing: Pixieset supports adding a digital image license to digital-download products, which is particularly relevant for your licensing business. Pixieset Help Center
• Branding: you get a proper photography website/portfolio rather than just a generic download store. Pixieset

pixieset.com

How I'd rank the alternatives

*Usually requires more configuration/apps than a photography-specific platform.

One important distinction: "licensing"

If by licensing you mean something like:

Client sees an image → chooses "Commercial license / Editorial license / Personal use" → pays $X → receives the high-res file plus a license agreement

then I'd lean Zenfolio or Pixieset rather than SmugMug.

Zenfolio explicitly supports different download resolutions, digital-license agreements, downloadable products, packages, and price lists. Zenfolio Zenfolio It also supports selling prints and digital products through the same storefront. Zenfolio

zenfolio.com

When I'd choose each

Choose Pixieset if you want the easiest path to a polished photography business: portfolio → gallery → print shop → high-res download.

Choose Zenfolio if licensing and ecommerce flexibility are central to your business, rather than primarily client gallery delivery. Its price-list/product system gives you more control over different digital products and resolutions. Zenfolio Zenfolio

Choose SmugMug if you have a very large archive and want the platform to double as long-term photo hosting. It remains one of the strongest options for photographers who want portfolio + galleries + selling in one place. Shut Your Aperture Xposure

Choose Pic-Time if the presentation of your photography is extremely important and you want a very premium gallery/print-buying experience. Current photography-platform comparisons tend to position it as the design-forward option. Tov Studio Photo Aftershoot

What I'd do in your shoes

I'd start with Pixieset, unless your licensing operation is substantial enough that you need sophisticated license types, usage terms, expirations, territories, exclusivity, etc.

If you tell me what kind of photography you sell (fine art, commercial, landscape, sports, editorial, stock, wedding, etc.) and roughly how many images you have, I can narrow this down to the best platform—and specifically compare Pixieset vs Zenfolio vs SmugMug on pricing, storage, original-file delivery, print labs, licensing, and transaction fees.

For a podcast merch store built around limited drops and preorder tees, I’d pick shopify.com overall.

My ranking

1. Shopify — best overall

• Excellent for limited-quantity drops and timed launches.
• Strong preorder support through its app ecosystem; Shopify currently has 100+ preorder apps with product-drop functionality, including options for deposits, waitlists, and back-in-stock notifications. Shopify App Store Shopify App Store
• Best if you expect the merch operation to grow beyond a few tees—bundles, email/SMS marketing, memberships, multiple suppliers, etc.
• You own the storefront and customer relationship rather than being locked into a creator-merch ecosystem.
• Downside: more setup and potentially more monthly/app costs.
• fourthwall.com — best if you want dead-simple creator merch

• Particularly attractive for podcasts/creators because it combines storefront, fulfillment, and merch production.
• It explicitly supports limited-run drops, including screen printing and cut-and-sew, as well as print-on-demand. Fourthwall
• No upfront inventory required for its standard catalog, and it can also ship products you've produced yourself. Fourthwall
• Downside: less of a full-fledged ecommerce platform than Shopify if merch becomes a serious standalone business.
• spring.tips — worth considering for creator-first simplicity

• Good if your main goal is "put podcast logo on shirts and sell them to listeners."
• I'd favor Fourthwall over it for the specific limited-drop/preorder model you're describing.

What I'd do for a podcast

If you guys are going to run something like:

Friday 10 AM: Drop 150 "Season 4" tees
Next week: Open preorder for the new tour tee
Sunday midnight: Preorder closes
Then: Order exactly what sold + a small overrun

I'd go Shopify + a preorder/drop app + a dedicated merch printer/fulfiller.

That gives you much more control over scarcity, launch timing, customer data, pricing, and future products. Shopify's ecosystem specifically supports product drops and preorder workflows. Shopify App Store

If, instead, you want "we make the designs, Fourthwall handles the annoying stuff", I'd choose Fourthwall.

Short version:
Shopify = best business platform.
Fourthwall = best low-maintenance podcast/creator solution.

If you tell me roughly how big your audience is (e.g. 10k / 100k / 1M listeners) and whether you want them to manufacture/ship the tees or you're willing to use a separate printer, I can narrow it down to the best setup and estimate the fees/margins.

If your main goal is selling directly from social posts and livestreams, I’d use Shopify as the commerce backbone, then connect the social channels where your audience already is.

My recommendation: Shopify + TikTok Shop + Instagram

Why Shopify: it gives you one central catalog, inventory, orders, fulfillment, customer data, and analytics system, while its social channels/apps connect that catalog to TikTok, Instagram/Facebook, YouTube, and other channels. Shopify Shopify Help Center

Then:

• TikTok Shop — best if livestream selling and impulse purchases are a major part of your strategy. Products can be tagged in videos and sold directly during TikTok LIVE, with Shopify syncing products, inventory, and orders. TikTok For Business
• Instagram/Facebook — excellent for shoppable Reels, posts, Stories, and your existing follower base. Shopify's Meta channel syncs your catalog with Facebook and Instagram. Shopify Help Center
• YouTube Shopping — worth adding if you do longer-form demonstrations, reviews, tutorials, or livestreams. Shopify integrates with YouTube's shopping ecosystem. Shopify

If livestream commerce is the core business

I'd consider Shopify + CommentSold or Shopify + Channelize.

CommentSold is particularly interesting if you're doing frequent hosted livestreams: it supports multichannel livestreaming across TikTok, Facebook, Instagram, and your website, with inventory/fulfillment workflows and live-selling features. Shopify

Channelize is better if you want to simulcast one shopping livestream across your website and multiple social channels, while keeping the commerce infrastructure connected to Shopify. Shopify

What I'd choose

One important distinction: Shopify is the backend I'd build around; TikTok/Instagram are the selling/discovery surfaces. That gives you much more flexibility than making TikTok or Instagram your entire ecommerce infrastructure.

If you tell me what you're selling, your approximate monthly sales, and which platforms you already have followers on (TikTok/Instagram/Facebook/YouTube), I can narrow this down to the best 1–2 platforms and the cheapest setup for you.

If your priorities are discount codes + affiliate links + influencer promo tracking, I’d usually pick Shopify as the ecommerce foundation, then add the right affiliate/influencer layer. It has the strongest ecosystem for this workflow, especially for creator-driven brands. Shopify Shopify

Here’s how I’d choose:

My default recommendation

For most DTC brands:

1. Shopify for the store
2. Shopify Collabs to start influencer partnerships
3. Upgrade to GRIN, Upfluence, Refersion, or Everflow once you need deeper tracking/reporting. Shopify ConversionStudio

Features I would require before choosing

• Unique influencer discount codes (e.g., SARAH15)
• Affiliate links with cookie attribution
• Code + link attribution together (important because many influencers only share codes)
• Commission rules by creator
• Automated payouts
• Fraud/coupon leakage controls
• Creator dashboard where influencers can see clicks, sales, and earnings

A few questions would change the recommendation:

1. Are you selling physical products, digital products, or subscriptions?
2. Roughly how many influencers/affiliates do you expect: <20, 20–200, or 200+?
3. Are you starting from scratch, or do you already have Shopify/WooCommerce/etc.?

For a B2B division with customer-specific pricing, POS, and large order volumes, I’d put BigCommerce B2B Edition, Shopify Plus, and Adobe Commerce on the shortlist—with BigCommerce as the first one I’d evaluate.

1. My first choice: bigcommerce.com

This is probably the best starting point for your requirements.

BigCommerce has native B2B functionality for customer-specific SKU pricing, price lists, bulk pricing, customer groups, company accounts, quotes, purchase orders, payment terms, requisition lists and approval workflows. Its quote system can also accommodate custom line-item pricing and unusual shipping arrangements for large orders. BigCommerce BigCommerce BigCommerce

That matters because I'd avoid building your B2B pricing engine around dozens of third-party apps if custom pricing is fundamental to the business.

The big question I'd investigate is POS. If your B2B division has a meaningful physical-sales component—sales reps entering large orders, trade counters, showrooms, branches, etc.—we'd need to map exactly how BigCommerce would integrate with your POS rather than assuming the ecommerce platform should be the POS itself.

2. Shopify Plus — strongest if POS is strategically important

shopify.com is extremely compelling if you're trying to create one commerce ecosystem spanning B2B, DTC, and physical retail.

Shopify's current B2B capabilities include company/location hierarchies, customer-specific catalogs and pricing, quantity rules, volume pricing, payment terms, PO numbers, bulk ordering and reordering. Shopify

And Shopify has a major advantage if your POS requirement is substantial: Shopify POS is native to the Shopify ecosystem.

The tradeoff is that particularly sophisticated B2B requirements can push you toward apps, custom development, or additional Shopify services. BigCommerce's B2B offering puts more of those B2B capabilities directly into the platform. BigCommerce

I'd pick Shopify Plus over BigCommerce if:

• POS is as important as ecommerce.
• You have significant DTC/retail business too.
• You want a relatively low-maintenance SaaS platform.
• Your B2B pricing is complex but not extremely complex.
• You value Shopify's broader ecosystem.

3. Adobe Commerce — if your B2B operation is exceptionally complex

business.adobe.com becomes more interesting if you have things like:

• Thousands/millions of SKUs
• Highly complicated customer contracts
• Multiple price books
• Sophisticated RFQ/negotiation
• Complex approval hierarchies
• Multiple business units/websites
• Very deep ERP/OMS integration
• Significant custom business logic
• A capable internal engineering/IT organization

Adobe is generally the platform I'd consider when the business process is more important than ease of implementation. Current comparisons continue to put Adobe ahead on deep native B2B functionality, while Shopify tends to win on operational simplicity and BigCommerce on B2B value. Elogic Commerce

The downside is that you're taking on considerably more implementation and ongoing technical complexity.

One important wrinkle: what do you mean by "custom pricing"?

This could change my recommendation substantially.

There's a huge difference between:

A. "Customer A gets 10% off and Customer B gets 15% off"

versus

B. "Every account has its own contract price for thousands of SKUs, quantity breaks, customer-specific promotions, regional pricing, freight rules, negotiated quotes, and sales-rep overrides."

If you're closer to B, I'd lean BigCommerce or Adobe Commerce rather than Shopify.

BigCommerce, for example, explicitly supports SKU-level price lists and customer-specific pricing, and its B2B quote functionality supports custom line-item pricing. BigCommerce BigCommerce

The other thing I'd prioritize: ERP/POS architecture

For a high-volume B2B division, I wouldn't select the ecommerce platform in isolation.

I'd map:

ERP → customer master → contracts/price lists → inventory → ecommerce → POS → order management → fulfillment → invoicing

before selecting the platform.

If the ERP is the system of record for pricing and inventory, the ecommerce platform may primarily need to be a fast B2B ordering interface rather than the master pricing engine.

My preliminary ranking

1. BigCommerce B2B Edition — best overall fit for complex B2B + large orders.
2. Shopify Plus — best if POS + B2C/retail are major priorities.
3. Adobe Commerce — best if B2B complexity and customization outweigh implementation cost.
4. OroCommerce — worth investigating if this is a pure-play, highly sophisticated B2B operation rather than a B2B/retail hybrid.
5. Salesforce Commerce Cloud — particularly compelling if your sales organization already runs heavily on Salesforce.

If you tell me (1) what ERP you use, (2) what POS you use, (3) approximate annual B2B revenue/order volume, (4) number of SKUs, and (5) how complicated the customer pricing is, I can narrow this to a 2–3 platform recommendation and architecture, including where each platform will struggle.

This could change my recommendation substantially.

There's a huge difference between:

A. "Customer A gets 10% off and Customer B gets 15% off"

versus

B. "Every account has its own contract price for thousands of SKUs, quantity breaks, customer-specific promotions, regional pricing, freight rules, negotiated quotes, and sales-rep overrides."

If you're closer to B, I'd lean BigCommerce or Adobe Commerce rather than Shopify.

BigCommerce, for example, explicitly supports SKU-level price lists and customer-specific pricing, and its B2B quote functionality supports custom line-item pricing. BigCommerce BigCommerce

The other thing I'd prioritize: ERP/POS architecture

For a high-volume B2B division, I wouldn't select the ecommerce platform in isolation.

I'd map:

ERP → customer master → contracts/price lists → inventory → ecommerce → POS → order management → fulfillment → invoicing

before selecting the platform.

If the ERP is the system of record for pricing and inventory, the ecommerce platform may primarily need to be a fast B2B ordering interface rather than the master pricing engine.

My preliminary ranking

1. BigCommerce B2B Edition — best overall fit for complex B2B + large orders.
2. Shopify Plus — best if POS + B2C/retail are major priorities.
3. Adobe Commerce — best if B2B complexity and customization outweigh implementation cost.
4. OroCommerce — worth investigating if this is a pure-play, highly sophisticated B2B operation rather than a B2B/retail hybrid.
5. Salesforce Commerce Cloud — particularly compelling if your sales organization already runs heavily on Salesforce.

If you tell me (1) what ERP you use, (2) what POS you use, (3) approximate annual B2B revenue/order volume, (4) number of SKUs, and (5) how complicated the customer pricing is, I can narrow this to a 2–3 platform recommendation and architecture, including where each platform will struggle.

For your specific profile—a multinational with localized catalogs plus distributed inventory and warehouse-aware fulfillment—I’d shortlist Adobe Commerce, commercetools, and Shopify Plus, with Adobe Commerce the strongest fit if sophisticated multi-warehouse logic is a first-class requirement.

My ranking

1. Adobe Commerce — best overall for your scenario

Adobe's Sources + Stocks model is unusually well aligned with a multinational operating model. A source can represent a warehouse, DC, store, or dropshipper, while stocks aggregate sources and can be associated with particular websites/regions. You can prioritize sources within a stock for fulfillment. Experience League Experience League

For example, you could model:

• US website → US stock → California DC → Texas DC → 3PL
• EU website → EU stock → Germany DC → Netherlands DC
• APAC website → APAC stock → Singapore DC → Australia DC

Meanwhile, Adobe's website/store/store-view hierarchy supports different catalogs, domains, languages, currencies, categories, and regional configurations within a common platform. Experience League Experience League

Why I'd pick it: the platform's inventory model is designed around exactly the distinction you're making between where something is sold and where it can be fulfilled.

2. commercetools — best if you're building a sophisticated composable stack

I'd seriously consider commercetools if you have a strong engineering organization and want the commerce platform to be the orchestration layer rather than the entire application.

Its Stores and Channels model lets you represent different commerce experiences while channels provide context for pricing and inventory. commercetools Documentation

The upside is enormous flexibility for rules such as:

Customer market + SKU + warehouse availability + shipping zone + promised delivery date → optimal fulfillment location.

The downside is that you'll generally be assembling more of the surrounding architecture yourself—OMS, PIM, localization, fulfillment orchestration, etc.

3. Shopify Plus — best if operational simplicity matters more

Shopify has become considerably stronger here. Its Markets model supports country/region-specific product availability, pricing, currencies, languages, and catalogs, while its location model tracks inventory independently at warehouses, stores, and fulfillment services. Shopify Help Center Shopify Help Center Shopify Help Center

It's particularly attractive if your warehouse logic is relatively conventional:

fulfill from the closest eligible location → otherwise another regional location → optionally split the order.

Shopify supports multiple locations and can split orders across locations. Shopify Help Center

I'd be more cautious if your requirements include complex allocation rules, ATP/available-to-promise calculations, regional inventory pools, cross-border sourcing, or sophisticated optimization.

The important architectural distinction

I'd evaluate these platforms against three separate models, rather than simply asking which has "multi-warehouse support":

1. Catalog availability

Market → Catalog → SKU eligibility

2. Inventory availability

Market → Inventory pool → Warehouse/DC → ATP

3. Fulfillment decision

Order → eligible warehouses → allocation rules → shipment(s)

Adobe Commerce is particularly compelling because its Stocks/Sources abstraction explicitly separates the inventory pool from the physical fulfillment locations. Experience League Experience League

My recommendation

If you're a large multinational and fulfillment complexity is strategically important, I'd go:

Adobe Commerce → commercetools → Shopify Plus

But there's an important caveat: if you already have a sophisticated OMS/WMS/ERP that owns allocation and fulfillment, the ranking can change dramatically. In that architecture, commercetools or Shopify Plus may be preferable because you don't necessarily want the commerce platform trying to become your fulfillment brain.

If you tell me roughly number of countries, number of warehouses, B2C vs B2B, ERP/OMS (SAP/Oracle/etc.), and whether you need headless, I can give you a much more concrete platform recommendation and reference architecture.