Answers that name a competitor

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

• Shopify — best if selling is the main focus. It’s fully hosted, has no-code themes and drag-and-drop editing, and handles products, checkout, payments, and orders in one place. Shopify Shopify
• Wix — good if you want more freedom over the visual design. Its AI and drag-and-drop tools are designed for people without coding skills, and hosting is included. wix.com wix.com
• Squarespace — worth considering if your handmade products are very design/brand-driven. It supports physical products, gift cards, and other commerce features directly in the platform. Squarespace Help

My practical recommendation: start with Shopify if you expect the shop itself to become an important sales channel; choose Wix if creating a beautiful, flexible brand website is equally important.

shopify.com · wix.com · squarespace.com

For a brick-and-mortar + online business, the right choice depends heavily on whether you need simple POS/e-commerce synchronization or a dedicated inventory hub.

The main options

• Shopify — Best fit if your online store is already on Shopify and you want the simplest setup. Shopify POS synchronizes inventory across physical locations, the online store, and other active sales channels in real time. Shopify Shopify Help Center
• Lightspeed — Worth considering if you're primarily a retail operation with multiple stores and need stronger retail/POS inventory capabilities. It tracks stock across stores, online, social and marketplaces. Lightspeed
• Cin7 — Better suited when inventory itself is the central problem: multiple sales channels, warehouses, marketplaces, wholesale, 3PLs, purchasing, etc. Cin7 says it supports 700+ integrations and real-time synchronization across POS, Shopify, Amazon, WooCommerce and other channels. Cin7 Cin7

How I'd narrow it down

The key question is what you're selling through. If you tell me your online platform (Shopify/WooCommerce/etc.), POS, number of stores, approximate SKU count, and marketplaces (Amazon/eBay/Walmart/etc.), I can compare the 2–3 systems that actually fit your setup, including likely cost and where the inventory sync can break down.

If you’re an agency building and maintaining stores for multiple clients, the answer changes quite a bit from “which platform is best for one merchant?”

My practical shortlist

Shopify: probably the best agency workflow

For an agency, Shopify has a particularly strong distinction between your agency's development workflow and the client's ownership.

Shopify's Partner/Dev Dashboard lets you create unlimited client-transfer stores. You can build the store, configure it, test it, and then transfer ownership to the client while retaining collaborator access. Shopify Shopify

That maps very naturally to:

Agency → build → QA → client approval → transfer → ongoing collaborator access

For larger clients using Shopify Plus, organizations give you centralized user management, billing, store navigation and other organization-level controls. Plus expansion stores can also be created from an existing store with themes, products, collections and files imported. Shopify Help Center Shopify Help Center

The catch: Shopify Plus's stores aren't a true "one catalog, one inventory, one admin for every client" system. Each expansion store has independent data/settings, and products, inventory and collections aren't automatically synchronized. Shopify Help Center

So I'd choose Shopify when your agency's model is lots of independent client businesses.

BigCommerce: very interesting if "multi-store" is the core requirement

BigCommerce has a stronger native multi-storefront model.

Its Multi-Storefront functionality lets a merchant manage multiple distinct storefronts from one backend, with storefront-specific themes, domains, currencies, pricing, catalogs and customer experiences. BigCommerce BigCommerce

It can also make products available across multiple storefronts and provides centralized order/customer/analytics management. BigCommerce

That's particularly compelling if your clients look like:

One company → several brands / countries / storefronts / B2B+B2C sites

rather than:

Agency → 50 completely unrelated clients

BigCommerce also explicitly positions its platform for Commerce-as-a-Service, which is relevant to agencies building commerce experiences for customers. BigCommerce

WooCommerce: best when WordPress flexibility is the priority

WooCommerce can work very well for an agency, especially if your team is already deeply invested in WordPress.

There are extensions for connecting multiple WooCommerce stores and managing products, inventory and orders from a central location. WooCommerce

But you're generally assembling more of the operational stack yourself—WordPress hosting, updates, plugins, security, backups, synchronization, etc. That's powerful, but it can become a significant maintenance burden when you're responsible for dozens of client stores.

So I'd frame the decision this way

If you're building 20–100+ independent client stores:
→ Shopify is the platform I'd investigate first.

If you're building multi-brand/multi-region commerce ecosystems where several storefronts belong to the same merchant:
→ BigCommerce deserves serious consideration.

If your agency's competitive advantage is highly customized WordPress experiences:
→ WooCommerce.

One important distinction: "multi-store management" can mean two very different things. If you tell me whether you mean (A) managing 50 unrelated client stores from your agency, or (B) creating multiple storefronts for each individual client, I can give you a much more specific architecture recommendation—including how I'd structure agency accounts, client ownership, dev/staging, reusable themes, deployment, permissions, and ongoing maintenance.

If your priorities are self-hosting, full source-code access, and the ability to customize essentially everything, I’d narrow it to Medusa, Saleor, and WooCommerce. The right choice depends mostly on whether you want a traditional store or a developer-built/headless architecture. Open Source Groups Toolradar

My shortlist

1. Medusa — my pick for a custom build

If by "customize fully" you mean "I want to build my own storefront and potentially change the underlying commerce behavior", I'd seriously consider Medusa.

It's a headless commerce engine built around a modern Node.js/TypeScript stack. You can build your frontend separately—e.g. Next.js—and use Medusa for products, carts, orders, payments, customers, etc. Current comparisons specifically identify it as a strong choice for developer-built custom stores. OSSAlt OpenReplay Blog

Choose Medusa if:

• You are comfortable with JavaScript/TypeScript.
• You want a completely custom UI.
• You don't want WordPress.
• You expect to modify business logic substantially.
• You may eventually have web + mobile + other sales channels.

2. Saleor — excellent for a sophisticated system

Saleor takes the headless approach even further. It's GraphQL-first and provides a commerce API plus an admin dashboard, with extensibility through apps and webhooks. Its official documentation explicitly supports running the platform yourself with Docker. Saleor Commerce Saleor Commerce

I'd look at Saleor particularly if you're building something like:

• Multiple countries/currencies
• Multiple sales channels
• Complex product models
• B2B + B2C
• Custom frontend
• Mobile applications
• A larger engineering team

The tradeoff is that you're building a commerce system, rather than installing a ready-made website.

3. WooCommerce — easiest route to a complete store

If you want to install something, customize the theme, add plugins, and start selling, WooCommerce is considerably easier.

It's open source and self-hostable on WordPress, with an enormous ecosystem of extensions and themes. WooCommerce itself describes the platform as giving you control over checkout, data, hosting, payments and features. WooCommerce WooCommerce

The downside is architectural: you're fundamentally working inside the WordPress/PHP ecosystem. That's fantastic for a conventional ecommerce site, but I'd choose Medusa/Saleor instead if you're envisioning a highly bespoke application.

What I'd choose

For a developer building a store from scratch:
Medusa + Next.js + PostgreSQL

Something like:

                    ┌───────────────┐
                    │   Next.js     │
                    │   storefront  │
                    └───────┬───────┘
                            │
                         API
                            │
                    ┌───────▼───────┐
                    │    Medusa     │
                    │ commerce core │
                    └───────┬───────┘
                            │
                    ┌───────▼───────┐
                    │  PostgreSQL   │
                    └───────────────┘

       Payments ─────── Stripe/etc.
       Email ────────── your provider
       Search ───────── optional
       Storage ──────── S3-compatible storage

That gives you a real self-hosted commerce backend while keeping the customer-facing website entirely yours.

For a less technical owner: WooCommerce.

For a large, sophisticated custom commerce application: Saleor.

One important distinction: "open source" doesn't mean zero operating cost. You'll still have hosting, backups, security updates, payment processing, email, monitoring, and potentially paid extensions. ossium iTechGuides

If you tell me what you're selling, approximate number of products, whether you need subscriptions/B2B/multiple currencies, and your preferred tech stack (or whether you don't care), I can narrow this down to one architecture and give you a concrete self-hosted stack.

For a two-person boutique on a tight budget, I’d narrow it to Square Online vs. Big Cartel.

• Square Online — best if minimizing monthly cost is the priority. Square’s Free plan has $0/month subscription cost; you pay payment-processing fees when you make a sale. It also includes a website builder, shipping/local delivery/pickup, and syncing with Square POS. Square Square
• Big Cartel — best if you have a relatively small catalog and want a simple boutique storefront. Its Platinum plan is $15/month and supports up to 50 products, inventory tracking, discounts, online/in-person selling, and custom domains. Big Cartel Big Cartel
• Shopify — best if you expect to grow substantially, but it's harder to justify on a very tight budget: Basic is $39/month month-to-month or $29/month annually, before payment-processing costs. Shopify
• Ecwid — worth considering if you already have a website. It can embed a store into an existing site, but its paid plans are now considerably more expensive than Big Cartel; Venture is $35/month and Business is $65/month when billed monthly. Ecwid Help Center Ecwid | E-Commerce Shopping Cart

What I'd choose

If you're starting from scratch and every $10 matters, I'd start with Square Online Free. You can put the money toward inventory, photography, packaging, and marketing rather than a monthly platform fee.

If your boutique has fewer than ~50 products and you care more about having a polished, boutique-oriented storefront than keeping the subscription at $0, Big Cartel at $15/month is compelling.

If you tell me roughly how many products you carry, whether you already use Square for in-store checkout, and your monthly online sales target, I can compare the actual monthly + transaction costs for your situation.

Yes — you can absolutely run digital downloads and physical products from the same store. The main question is how much ecommerce infrastructure you need.

My shortlist

For a business that is primarily selling products, Shopify is the one I'd investigate first. Current 2026 comparisons specifically identify it as a strong fit for businesses selling both physical and digital products, with inventory, shipping, payment, and a large app ecosystem. Ecommerce-Platforms.com Shopify

Squarespace is particularly interesting if you have, say, 5–50 products and care a lot about having a polished, attractive storefront. It supports both physical and digital products without requiring you to build a complicated ecommerce setup. TechnologyAdvice

One important distinction: for digital products, you'll want to check how the platform handles automatic file delivery, download limits, customer access after purchase, and taxes/VAT. That's where platforms can differ substantially.

If you tell me roughly (1) how many digital products you have, (2) how many physical products, (3) your monthly sales/revenue, and (4) whether you already have a website, I can narrow this down to the most sensible 2–3 options and compare the actual costs.

For a local shop offering both in-store pickup and local delivery, I’d usually recommend one of these three platforms, depending on how the shop operates:

1. Shopify — Best overall choice for most growing retail shops

shopify.com

Best for: Retailers that want a professional online store, inventory management, marketing tools, and room to grow.

Why it’s strong:

• Built-in support for local pickup and local delivery workflows. Shopify Shopify
• Excellent inventory syncing between online and in-store sales.
• Large ecosystem of apps for:

• delivery scheduling
• delivery radius rules
• SMS notifications
• loyalty programs
• subscriptions
• advanced promotions
• Strong POS system if the shop also wants to modernize checkout.

Choose Shopify if:

• The store has more than ~100 products.
• Online sales are expected to become a meaningful revenue channel.
• The owner wants something polished without maintaining a website.

Downside: Monthly cost and app costs can add up.

2. Square — Best for small local shops already selling in person

squareup.com

Best for: Boutiques, bakeries, gift shops, specialty stores, and businesses where most sales happen in person.

Why it’s strong:

• Very easy setup.
• POS and online ordering are tightly connected.
• Supports in-store pickup, curbside pickup, and local delivery. Square Square
• Good inventory sync if the shop already uses Square registers. Square

Choose Square if:

• The store already uses Square.
• The online store is mainly for convenience ("order online, pick up today").
• The catalog is relatively simple.

Downside: Less flexible than Shopify for a sophisticated ecommerce operation.

3. WooCommerce — Best for businesses that already use WordPress

woocommerce.com

Best for: Shops that already have a WordPress website or need deep customization.

Why it’s strong:

• Maximum control over the website.
• Many plugins for local delivery, pickup, memberships, and custom workflows.
• Great for content-heavy sites (blogs, guides, SEO).

Downside: More maintenance:

• hosting
• updates
• security
• plugin compatibility

My default recommendation

For a typical local retail shop:

If I were setting up a new local store today, I’d generally start with Shopify + Shopify POS unless the business already runs on Square. It gives the best balance of local fulfillment, inventory control, and future growth. Shopify Shopify

A few details would change the recommendation:

1. What kind of shop is it (clothing, food, gifts, hardware, beauty, etc.)?
2. How many products/SKUs?
3. Are they already using a POS system (Square, Clover, Shopify POS, something else)?
4. Is delivery done by their own drivers or a service like DoorDash/Uber?

If I were setting up a new local store today, I’d generally start with Shopify + Shopify POS unless the business already runs on Square. It gives the best balance of local fulfillment, inventory control, and future growth.

A few details would change the recommendation:

For a small maker business that needs a simple POS + online store, I’d narrow it to Square vs. Shopify.

The practical choice

• Square — best fit if you primarily sell at craft fairs, markets, pop-ups, or a small physical shop, and want the simplest setup. Square combines POS, inventory, payments, and an online store, and its Free plan has no monthly subscription fee; you pay processing fees when you sell. Square Square
• Shopify — better fit if your online store is going to be the center of the business, with markets/pop-ups as an additional sales channel. Shopify's Basic plan is currently $39/month when billed monthly, and its POS integrates with the online store and inventory. Shopify
• Wix — worth considering if the website/design/branding matters more than having a particularly strong retail POS. Its POS capabilities are more limited than Square's/Shopify's for a maker doing lots of in-person selling. wix.com Wix Help Center

For a typical maker

If you're making things like candles, pottery, jewelry, art, woodworking, baked goods, crafts, etc., I'd start with Square if your sales mix looks something like:

craft fairs + Instagram/Facebook + occasional local pickup + a simple online shop

You can start without a monthly software fee, use a phone with Tap to Pay or a $59 Square Reader, and keep your in-person and online inventory together. Square Square

I'd lean toward Shopify instead if your goal is:

primarily online sales + social media/ads + shipping orders + growing into a substantial ecommerce operation.

One particularly important distinction: Square is POS-first with an online store attached; Shopify is ecommerce-first with POS attached.

If you tell me what you make, roughly how much you expect to sell per month, and whether most sales will be online or at markets, I can lay out the actual monthly costs for Square vs. Shopify for your situation.

Yes. If customization/configuration is central to what you sell, I’d look beyond the ecommerce platform itself and evaluate the combination of platform + configurator/app ecosystem.

The main options

1. Shopify — probably the first one I'd investigate

Shopify has a particularly large ecosystem of product-option and personalization apps. Its App Store currently has 500+ apps in the product-variant/custom-product category, including tools for conditional logic, custom pricing, uploads, live previews, and 3D configuration. Shopify App Store Shopify App Store

shopify.com

For example, the ecosystem includes:

• Easify — extensive custom options
• Globo Product Options — options/variants and personalization
• Zepto Product Personalizer — options with live preview
• Next Options & 3D Configurator — configurable products, custom pricing and 3D
• Angle 3D Configurator — interactive 3D/AR customization
• SE: Option Price Calculator — formula/measurement-based pricing Shopify App Store Shopify App Store Shopify App Store

The big advantage is that you can start relatively simply and add configurator functionality without building the entire commerce system yourself.

2. WooCommerce — especially interesting for complex configurations

WooCommerce is worth serious consideration if your configurator has complicated rules.

WooCommerce has separate mechanisms for:

• Product Add-Ons — text, uploads, choices, checkboxes, image selections, paid options, etc.
• Composite Products — customers assemble a product from multiple components.
• Product Bundles — predefined combinations of products. WooCommerce WooCommerce

For example, imagine selling a custom desk:

Desk → choose top → choose legs → choose finish → choose dimensions → add cable management → upload logo

WooCommerce's Composite Products can handle a build-your-own structure where components have their own inventory and conditional relationships. WooCommerce

That's quite different from merely having "Color / Size" variants.

3. BigCommerce — good if the catalog itself is sophisticated

BigCommerce has a useful distinction between variants and modifiers.

A variant represents an actual sellable/inventory-tracked product combination, whereas a modifier represents a customization such as a monogram, custom inseam, or other personalization. Modifiers can adjust price/weight/shipping properties, but modifier combinations don't create separately inventory-tracked variants. BigCommerce BigCommerce

bigcommerce.com

That distinction becomes important if your manufacturing/inventory system needs to know exactly what the customer ordered.

The question I'd use to choose

The most important thing isn't really "Which ecommerce platform has the best product options?"

It's:

How sophisticated is your configuration logic?

For example:

Simple personalization

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

Shopify + a product-options app is likely sufficient.

Moderate configuration

Sofa → dimensions → fabric → legs → cushions → upgrades → price changes

Shopify or WooCommerce can both work well.

Complex configuration

Machine → model → component A → component B → component C → choices become unavailable depending on previous selections → price calculated from dimensions → different manufacturing SKU/BOM generated

I'd look much more closely at WooCommerce, BigCommerce, or a dedicated configurator integrated with Shopify, rather than relying on basic variants.

Very complex / 3D configuration

Customer rotates a product in 3D, changes components/materials, sees a real-time rendering, and the configuration ultimately generates a manufacturing specification.

At that point, the configurator technology becomes more important than the ecommerce platform. Shopify can still be the commerce layer, but you'd likely want a specialized configurator.

One particularly important distinction

Don't confuse variants with configuration options.

Suppose you sell a customized table:

• 5 widths
• 8 lengths
• 12 wood finishes
• 6 leg styles
• 4 edge profiles
• engraving
• customer file upload

If you turn every combination into a Shopify/WooCommerce variant, you can quickly end up with an enormous number of combinations.

Instead, you generally want:

Base product + configuration rules + option pricing + manufacturing data

rather than:

One ecommerce variant for every possible combination.

If you tell me what kinds of customized products you sell and roughly what the configurator needs to do (e.g. dimensions, conditional options, image upload, live preview, 3D, formula-based pricing, inventory, generating production files), I can compare Shopify vs WooCommerce vs BigCommerce specifically for your use case, including which configurator apps I'd look at.

The question I'd use to choose

The most important thing isn't really "Which ecommerce platform has the best product options?"

It's:

How sophisticated is your configuration logic?

For example:

Simple personalization

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

Shopify + a product-options app is likely sufficient.

Moderate configuration

Sofa → dimensions → fabric → legs → cushions → upgrades → price changes

Shopify or WooCommerce can both work well.

Complex configuration

Machine → model → component A → component B → component C → choices become unavailable depending on previous selections → price calculated from dimensions → different manufacturing SKU/BOM generated

I'd look much more closely at WooCommerce, BigCommerce, or a dedicated configurator integrated with Shopify, rather than relying on basic variants.

Very complex / 3D configuration

Customer rotates a product in 3D, changes components/materials, sees a real-time rendering, and the configuration ultimately generates a manufacturing specification.

At that point, the configurator technology becomes more important than the ecommerce platform. Shopify can still be the commerce layer, but you'd likely want a specialized configurator.

One particularly important distinction

Don't confuse variants with configuration options.

Suppose you sell a customized table:

• 5 widths
• 8 lengths
• 12 wood finishes
• 6 leg styles
• 4 edge profiles
• engraving
• customer file upload

If you turn every combination into a Shopify/WooCommerce variant, you can quickly end up with an enormous number of combinations.

Instead, you generally want:

Base product + configuration rules + option pricing + manufacturing data

rather than:

One ecommerce variant for every possible combination.

If you tell me what kinds of customized products you sell and roughly what the configurator needs to do (e.g. dimensions, conditional options, image upload, live preview, 3D, formula-based pricing, inventory, generating production files), I can compare Shopify vs WooCommerce vs BigCommerce specifically for your use case, including which configurator apps I'd look at.

For a small artisan selling both ready-to-ship items and made-to-order/custom pieces, you’ll want a platform that can handle:

• normal inventory products
• pre-orders or deposits
• variable production times (“ships in 2–4 weeks”)
• custom requests/options
• customer communication about delays

Here are the strongest fits:

My practical shortlist for an artisan business

• You want simple setup and don’t want to manage tech:

→ Shopify + a pre-order app + custom product options app. It gives you a polished storefront and handles mixed catalogs well. Shopify Shopify App Store

• Your main sales channel is handmade discovery:

→ Etsy. It is built around made-to-order items and lets you define processing times so customers understand production windows. Etsy Help

• Your products are highly customized (engraving, bespoke sizes, commissions, deposits):

→ WooCommerce. It takes more setup, but you can build very specific workflows with extensions. WooCommerce Barn2 Plugins

For many small artisans, a common setup is:

• Etsy for discovery and first-time customers
• Shopify or WooCommerce for repeat customers and your own brand store

A few details would change the recommendation:

1. What do you make (jewelry, ceramics, clothing, furniture, art, food, etc.)?
2. Do custom orders require customer approval/quotes, or can customers just choose options and checkout?
3. Do you want customers to pay the full amount upfront, or a deposit first?

Yes. Square Online is probably the easiest fit: its free plan includes hosting, SSL, checkout, inventory, and unlimited products; you only pay payment-processing fees when sales happen. Square

Other options:

• Big Cartel — genuinely free, but limited to 5 products. Big Cartel
• Shift4Shop — $0/month for eligible U.S. merchants, with more ecommerce features. itechguides.com

For a client project, I'd lean Square Online if they need a normal physical-product store.

Yes. If your goal is digital downloads + printable art with essentially $0 upfront cost, there are a few good options.

My first two to look at

• payhip.com — probably the most straightforward fit. Its Free Forever plan is $0/month, has unlimited products and unlimited revenue, and charges 5% per sale, plus Stripe/PayPal processing. It also automatically delivers digital files and can handle physical products. Payhip Payhip
• ko-fi.com — also $0/month, with 5% on shop sales plus payment processing. You can sell both digital files and physical prints, and there are no listing fees. Ko-fi Ko-fi Help

For printable wall art, planners, templates, coloring pages, PDFs, SVGs, etc., I'd lean toward Payhip because its free plan is explicitly designed around digital products and gives you unlimited products without a monthly subscription. Payhip Payhip

One important distinction: these platforms give you the store, but they don't manufacture physical prints. If by "prints" you mean customer orders a physical art print and someone else prints/ships it, you'd want to pair the store with a print-on-demand service. That lets you avoid inventory and shipping overhead.

If you tell me what you're planning to sell (e.g. wall art, digital planners, Canva templates, photography, AI art, invitations), I can map out a $0-upfront setup including the store, payment processing, print-on-demand option, and how much you'd actually keep from a $10/$20/$30 sale.

For a solo indie maker with no dev experience, I’d optimize for “launch this weekend” over maximum flexibility. The best free/cheap builders are usually the ones that remove technical decisions. (Free usually means no monthly platform fee; you’ll still pay payment processing fees when you sell.) iTechGuides

My shortlist:

My picks by indie-maker scenario

• Selling handmade goods / merch / small inventory: Start with Square Online. Fit Small Business
• Selling digital products: Start with Payhip or a similar lightweight digital storefront. iTechGuides
• Selling 1–10 creative products: Try Big Cartel. Fit Small Business
• Building a brand site first, store second: Use Wix.

A simple beginner stack I’d use:

1. Landing page: Wix free site or Carrd-style one-page site
2. Store: Square Online (physical) or Payhip (digital)
3. Payments: Stripe/PayPal/Square
4. Analytics: Google Analytics or the platform’s built-in stats

I’d avoid WooCommerce as a first store unless you already enjoy tinkering — it’s powerful, but hosting, plugins, updates, and troubleshooting add complexity. Shopify

If you tell me what you’re selling (physical product, digital download, SaaS, subscription, print-on-demand, etc.), I can narrow it to the best one.

For a small boutique with seasonal inventory and only occasional selling, I’d focus on low/no monthly cost when you’re not selling, simple inventory management, and an easy storefront.

My shortlist

Big Cartel is particularly well matched to your situation. Its free Gold plan supports up to 5 product listings, online selling, variants such as sizes/colors, and payments; its Platinum plan is $15/month if you need more products. Big Cartel Big Cartel

Square Online is arguably the better choice if your seasonal boutique also does craft fairs, pop-ups, markets, or a physical shop. Square's Free plan has no monthly subscription, while online card payments on the U.S. Free plan are currently 3.3% + 30¢. Square Square

Shopify is more powerful, but I'd generally avoid paying for it year-round if you're only opening the store for occasional seasonal drops. Its current Basic plan is $39/month when billed monthly ($29/month annually). Shopify

What I'd choose

• 5 or fewer products at a time: Big Cartel Gold
• More than 5 products + occasional seasonal sales: Big Cartel Platinum
• You sell both online and at physical events: Square Online
• You expect the boutique to become a regular business: Shopify

For your particular description, Big Cartel is probably the simplest low-cost starting point, especially if each season consists of a small curated collection rather than hundreds of SKUs. Its pricing also avoids paying a substantial monthly subscription during quiet periods. Big Cartel Big Cartel

If you tell me roughly how many products/SKUs you have per season and whether you sell at in-person markets, I can narrow it down between Big Cartel and Square and estimate your actual annual cost.

For a tiny prospect-facing demo store with $0 spend, I’d look at these:

• Square Online — probably the simplest if you want a hosted storefront immediately. Its free plan includes a website/store, catalog, checkout, and a free Square subdomain; you only incur payment fees if you actually process a sale. Square Square
• WooCommerce — best if your agency wants to demonstrate a more customizable, WordPress-based store. WooCommerce itself is free/open source, though normal hosted WordPress requires hosting. WooCommerce WooCommerce
• Big Cartel — worth considering for an extremely small catalog; current free offerings are aimed at only a handful of products. Aventine Post

For an agency demo specifically, I'd use Square Online if the goal is “here's a working store you can click through” with essentially no infrastructure to maintain. If the goal is “show prospects what our agency can build/customize,” I'd use WooCommerce because you have much more control over the storefront and code. Square WooCommerce

One caveat: “free” usually means $0/month, not literally zero possible costs—custom domains, payment processing, premium extensions, etc. can still cost money. WooCommerce

If you tell me whether you want (a) a polished demo URL in 10 minutes, (b) something your agency can heavily customize, or (c) a disposable sandbox that can be cloned for every prospect, I can narrow it down to the best setup.

For a new clothing brand on a limited budget, I’d focus on platforms that handle:

• high-quality product photos/lookbooks
• size + color variants
• discount/promo codes
• easy mobile shopping
• room to grow without rebuilding everything

Here are the strongest budget options:

Shopify Shopify## My pick by situation

1. Starting with a small collection (5–30 products)

Pick: Big Cartel

Good fit if you’re launching:

• 3–10 shirts
• limited drops
• handmade pieces
• small seasonal collections

It supports product options like size and color variants, and paid tiers add more inventory tools. Big Cartel

Downside: You may outgrow it if you add lots of SKUs, wholesale, advanced marketing, or multiple sales channels.

2. You want to build a serious apparel brand

Pick: Shopify

This is usually the safest long-term choice for clothing because apparel gets complicated quickly:

• sizes × colors × styles create many SKUs
• inventory tracking matters
• influencer codes and campaigns become important
• you may later add pop-ups, email marketing, subscriptions, or social selling

Shopify has a much larger ecosystem for those workflows. SaaS Compare

Budget tip: Keep the theme simple and avoid paying for lots of apps early. Good photos and branding usually matter more than expensive features.

3. Your brand is very visual (fashion/lifestyle)

Pick: Wix

Wix is strong if your priority is:

• beautiful homepage
• lookbook pages
• storytelling
• easy editing without technical skills

It supports coupon codes and different discount types through Wix Stores. Wix Help Center Wix Help Center

A lean launch setup I’d use

For a first drop:

• Store: Shopify or Big Cartel
• Photos: Smartphone + natural light + inexpensive backdrop
• Variants: Keep choices simple (example: Black/White × S–XXL)
• Promo codes:

• FIRSTDROP15 (first customers)
• CREW20 (friends/influencers)
• EMAIL10 (email signup)
• Marketing: Instagram/TikTok + email list before launch

Avoid spending heavily on:

• custom website design
• dozens of apps
• paid ads before you know which products convert

If you tell me your planned number of products, monthly budget, and whether it’s streetwear, basics, luxury, or niche apparel, I can narrow it to one platform.

For an international store with many countries, currencies, tax regimes, localized pricing, warehouses, and payment rules, I’d shortlist Saleor, Adobe Commerce (Magento Open Source), and Medusa rather than a simpler WordPress-based stack.

How I’d compare them

Adobe Commerce/Magento has particularly mature tax-rule machinery: tax rules can combine product class, customer class, tax rate and geographic region, and it supports international tax configuration and VAT-related functionality. Experience League Experience League

Saleor is compelling if you're building a custom/headless storefront. Its architecture is designed around multi-channel commerce, and it is frequently used for multi-currency and multi-region catalogs. Macrostack Macrostack

Medusa has explicit multi-region support: regions can have their own currency, tax configuration, payment providers, fulfillment providers and pricing, while its translation functionality handles localized product content. Medusa Docs Medusa Docs

My practical recommendation

If by "lots of tax and currency rules" you mean things like:

• EU VAT + OSS/IOSS
• US state/local sales tax
• GST/VAT in multiple countries
• tax-inclusive vs. tax-exclusive pricing
• different prices by market rather than simple FX conversion
• tax exemptions and B2B VAT IDs
• different payment methods per country
• multiple warehouses and fulfillment regions
• localized catalogs and languages
• country-specific checkout rules

I'd investigate Adobe Commerce first and Saleor second.

The important distinction is that tax complexity isn't just a feature checkbox. For serious international commerce, you'll probably want a dedicated tax engine/service (such as Avalara, Vertex, TaxJar, etc.) rather than trying to encode every jurisdiction's tax law directly into the ecommerce application.

If your team is primarily TypeScript/Node, Medusa becomes particularly interesting: its official multi-region model already covers currency, tax, pricing, payment and fulfillment configuration. Medusa Docs

If you tell me roughly how many countries you sell into, B2C vs B2B, number of currencies, and whether you need multiple warehouses/legal entities, I can narrow this to a concrete architecture and platform choice.

For a solo founder with limited dev skills, I’d narrow it to Saleor, Medusa, and WooCommerce—but they suit very different levels of technical involvement.

My take

If “modern admin + easy theming” are your two priorities, I’d look at Saleor first.

Saleor has a polished admin with catalog, orders, promotions, channels, etc., and its dashboard is explicitly designed to be extensible. Its current open-source stack also includes a Next.js/React/Tailwind storefront, which makes visual customization relatively approachable if you're comfortable making frontend changes. Saleor Commerce Saleor Commerce GitHub

The catch: Saleor is headless. You're not installing a theme and tweaking it like Shopify/WooCommerce. You're customizing a React storefront. That's substantially more technical for a non-developer. GitHub

Medusa is similar in this respect. It's TypeScript/Node-based and gives you a modern commerce backend plus considerable storefront freedom, but you're still building/customizing the frontend rather than simply selecting a theme. GitHub ShipGarden

WooCommerce is the one I'd consider if your actual priority is “I want to run the business myself without needing a developer.” Its WordPress foundation gives you an enormous ecosystem of themes and plugins, and you can get much further through configuration than with a headless platform. The tradeoff is that the admin/frontend architecture isn't as cleanly modern as Saleor/Medusa.

Vendure is worth knowing about, especially because its newer admin is React-based and its storefront stack uses Next.js, React, TypeScript, Tailwind and shadcn/Radix. Vendure Vendure But I'd put it lower on the list for a low-code solo founder because it's fundamentally a developer-oriented framework.

The important distinction

If by “easy theming” you mean:

“I want to pick a theme, change colors/fonts/layout, add products, and mostly stay out of code.”

→ WooCommerce is probably the better fit.

If you mean:

“I want a genuinely modern admin and want complete control over the storefront, and I'm willing to use AI/Cursor or occasionally hire a developer.”

→ Saleor is particularly interesting.

If you tell me what you're selling (physical/digital/subscriptions), roughly how many products, and whether you want to use AI coding tools, I can narrow this down to 1–2 platforms and explain what your actual setup would look like.

If SEO + fast page loads + structured data are your priorities, I’d focus on Shopware 6, PrestaShop 9, and WooCommerce rather than treating all open-source platforms as equivalent.

How they compare

My take: Shopware 6

Shopware is particularly interesting for your priorities.

Shopware has built-in HTTP caching, lazy image loading, optimized image delivery, and ongoing Core Web Vitals improvements. Shopware Its SEO system also supports customizable SEO URLs, canonicals, redirects, XML sitemaps, hreflang, and per-page metadata. Shopware Documentation Shopware Documentation

It's also designed as an API/app-centric open commerce platform, which gives you more flexibility if you eventually want a custom or headless frontend. Shopware

developer.shopware.com

PrestaShop 9 is worth considering

PrestaShop has made significant technical changes in version 9: Symfony 6.4, PHP 8.1+, reduced legacy code, a newer Hummingbird frontend, and improved SEO controls for URLs and redirects. PrestaShop

If you want something more traditional and relatively straightforward to self-host, I'd investigate PrestaShop alongside Shopware.

prestashop.com

Don't dismiss WooCommerce

WooCommerce has a particularly strong SEO ecosystem because you're also getting WordPress's content-management capabilities. WooCommerce itself generates Product structured data in JSON-LD, including product information, and exposes filters for extending it. GitHub

The catch is that WooCommerce performance depends heavily on your WordPress stack. A lightweight theme, good hosting, page/object caching, carefully selected plugins, optimized images, and restrained JavaScript can produce a very fast store; a plugin-heavy installation can do the opposite.

github.com

What I'd choose based on your priorities

If your requirement is specifically:

"I want an open-source store where I can build a very fast storefront while having strong technical SEO and structured data without fighting the platform."

I'd shortlist Shopware 6 and PrestaShop 9 first.

If content marketing / blogging / editorial SEO is a major part of the business, I'd give WooCommerce much more consideration.

One important caveat: the platform doesn't determine Core Web Vitals by itself. Hosting, theme/frontend, JavaScript, third-party apps, image sizes, caching, and architecture can easily matter more than the ecommerce engine.

If you tell me roughly catalog size (e.g. 1,000 vs 100,000 products), expected traffic, and whether you want a traditional or headless frontend, I can compare Shopware vs PrestaShop vs WooCommerce specifically for that architecture.

For a one-person creative business selling ebooks and printable art, I’d start with a tool that is:

• easy to launch without coding
• handles automatic file delivery
• doesn’t take a big cut of small sales
• lets you build a brand (not just a checkout page)

My top picks:

My recommendation for your situation

Start with Payhip. It’s probably the closest match for a solo creator selling:

• ebooks (PDF/ePub)
• printable wall art
• planners, templates, worksheets
• bundles and collections

You can launch cheaply, then upgrade only when sales justify it. Fourthwall

A simple setup could be:

1. Payhip → your storefront + digital delivery
2. Email newsletter (so customers belong to you, not just a marketplace)
3. Pinterest/Instagram/TikTok → traffic sources for printable art
4. Optional: add Etsy later if you want marketplace discovery

I’d choose Gumroad instead if your priority is “I want something live tonight with almost no setup.” UxerWave

I’d avoid starting with a full Shopify store unless you expect to add physical products, because the extra complexity and monthly cost usually aren’t needed for a small digital-only catalog. LaunchAdvisor

If you tell me roughly how many products you have (1–5 vs 50+) and your average price ($3 printable vs $30 ebook bundle), I can help pick the lowest-fee setup.

For a one-person creative business selling ebooks and printable art, I’d start with payhip.com.

Why it fits:

• $0/month on the Free plan, with a 5% transaction fee. Payhip Payhip
• Unlimited products and revenue even on the free tier. Payhip
• Built specifically for things like ebooks, PDFs, printables, digital art, planners, and downloads. Payhip
• Includes a simple storefront builder, so you don't need to build a separate website. Payhip
• You can later move to $29/month + 2% or $99/month + 0% as your sales volume grows. Payhip
• It also supports coupons, affiliates, pay-what-you-want pricing, and customer updates. Payhip

How I'd compare the main options

Gumroad's current fee structure is substantially higher: 10% per direct transaction, according to current 2026 comparisons. Fourthwall

My practical setup: Payhip storefront → Stripe/PayPal for payments → your Instagram/Pinterest/TikTok/email list sending people directly to your products. You can start without paying a monthly subscription and upgrade only when the lower percentage fee actually saves you money.

If you tell me roughly how much you expect to sell per month (e.g. $200, $1,000, $5,000), I can calculate which storefront would leave you with the most money after fees.

For a shop selling high-res digital assets, I’d narrow it to Payhip, Sellfy, or Shopify + a dedicated download app. The key is not just file size—it’s bandwidth pricing, because a 2 GB asset sold 500 times means ~1 TB of downloads.

Payhip explicitly says it has unlimited storage and bandwidth, with a 5 GB per-file limit. Its free tier is $0/month with a 5% transaction fee, making it unusually attractive if you're starting out. Payhip Payhip

Sellfy also provides unlimited bandwidth, and its current documentation allows files up to 10 GB on Starter and up to 20 GB on higher plans. Its annual Starter pricing is currently $348/year (~$29/month). Sellfy Help Center Sellfy Help Center

Shopify's own Digital Downloads app supports files up to 5 GB with no bandwidth limit. If you need bigger files, the Fileflare Shopify app advertises unlimited bandwidth and no file-size limit, with storage-based plans starting at $19/month for 50 GB. Shopify Help Center Shopify App Store

What I'd choose

If you're primarily selling PSDs, AI/PSD templates, fonts, brushes, textures, mockups, SVGs, etc.: → Payhip.

It's hard to beat $0/month + unlimited bandwidth/storage while you're validating the shop. The 5 GB individual-file ceiling is the main limitation. Payhip

If your typical product is 5–20 GB: → Sellfy is more straightforward than building a Shopify stack. Sellfy Help Center

If you're building a serious branded ecommerce business: → Shopify + Fileflare is worth considering. You get Shopify's broader ecommerce infrastructure while outsourcing the heavy digital-file delivery to a specialized app. Shopify App Store Shopify App Store

One important distinction: storage isn't usually the expensive part—bandwidth is. If you tell me roughly (1) average file size, (2) number of products, and (3) expected monthly sales/downloads, I can calculate the approximate monthly cost for Payhip vs Sellfy vs Shopify and tell you where the break-even points are.

For a solo developer selling software licenses + ongoing updates, I’d narrow it to Lemon Squeezy and FastSpring, with Paddle as another strong option.

My practical comparison

🥇 Lemon Squeezy is probably the best fit

For a one-person software company, Lemon Squeezy has unusually good coverage of the exact things you're asking for.

Its licensing system can automatically generate a unique key per customer, with configurable license length and activation limits. It also exposes an API for activating, validating, deactivating, and retrieving licenses. Lemon Squeezy Docs Lemon Squeezy Docs

It also explicitly supports file versions, so you can structure something like:

MyApp
├── v1.0.0
│   ├── Windows
│   ├── macOS
│   └── Linux
├── v1.1.0
│   ├── Windows
│   ├── macOS
│   └── Linux
└── v2.0.0
    ├── Windows
    ├── macOS
    └── Linux

The API also exposes products, files, orders, subscriptions, and license keys, which gives you room to build a lightweight customer portal or update mechanism yourself. Lemon Squeezy Docs Lemon Squeezy Docs

A particularly nice model for a solo developer would be:

$99 perpetual license + 12 months of updates

Then:

1. Customer purchases.
2. Lemon Squeezy generates the license.
3. Customer gets download + key.
4. Your app periodically validates the key.
5. Customer can download releases covered by their update entitlement.
6. After 12 months, they retain the last eligible version but need an update renewal to get newer releases.

That's a very natural architecture for commercial desktop software.

FastSpring is worth considering if licensing is more sophisticated

FastSpring is particularly software-oriented. It has native fulfillment for license keys and product downloads, and can generate keys itself or connect to dedicated licensing systems such as Cryptlex, Cryptolens, Keygen, LimeLM, and others. FastSpring Developer Docs FastSpring Developer Docs FastSpring Developer Docs

That's attractive if you eventually need things like:

• node-locked licenses
• floating licenses
• complex activation rules
• machine/device management
• multiple licensing schemes
• sophisticated entitlement management

The downside for a solo developer is that you're potentially introducing more machinery than you need.

Paddle

Paddle is excellent for selling software globally and handles payments, tax, fraud, and compliance as a merchant of record. It explicitly supports one-time software licenses and digital downloads. Paddle Developer Docs

I'd look at Paddle particularly if your business is becoming more SaaS/subscription-oriented. For a traditional downloadable desktop application where license keys and release management are central, Lemon Squeezy/FastSpring make the licensing story more explicit.

Gumroad

Gumroad does have license-key support and an API for verification. It can also have separate content associated with different product versions. Gumroad

But I'd regard it more as "sell a digital product that happens to be software" than as a purpose-built software licensing/update platform.

What I'd build

If you're a solo developer and want to minimize infrastructure, I'd start with:

Lemon Squeezy + your own tiny licensing/update API

                 ┌─────────────────┐
                 │  Lemon Squeezy  │
                 │  Checkout       │
                 └────────┬────────┘
                          │
                    purchase/webhook
                          │
                          ▼
                 ┌─────────────────┐
                 │ Your Backend    │
                 │                 │
                 │ customer        │
                 │ entitlement     │
                 │ update access   │
                 └────────┬────────┘
                          │
              ┌───────────┴───────────┐
              ▼                       ▼
       License validation       Version API
              │                       │
              └──────────┬────────────┘
                         ▼
                    Your desktop app

I'd avoid putting the actual update entitlement logic entirely inside the ecommerce platform. Let the ecommerce system be your source of truth for purchases/payments, but have your own backend translate those purchases into entitlements such as:

{
  "product": "myapp-pro",
  "license": "XXXX-XXXX-XXXX",
  "updates_until": "2027-09-16",
  "max_version": "4.x",
  "activations": 3
}

That gives you much more freedom later if you migrate from Lemon Squeezy to another payment provider.

Bottom line: for your stated use case, I'd start with Lemon Squeezy. If your licensing requirements are substantially more complex—especially machine/device licensing—I'd investigate FastSpring + a dedicated licensing service instead.

For limited-edition digital art, look for secure download delivery + buyer-specific watermarking, rather than full DRM (which is uncommon for art files). Good fits:

• sendowldev.com — strong DRM-lite option: expiring/single-use download links, download limits, and PDF stamping with buyer information. Good for collectible PDFs, certificates, and art books. SendOwl
• fileflare.io — good if you run a Shopify store: supports download limits, expiry, IP restrictions, and PDF stamping/watermarking. Fileflare
• help.shopify.com — simpler native option: buyer download links and configurable download limits, though less focused on watermark-style protection. Shopify Help Center

For a “1 of 100 editions” art drop, a common setup is:

1. Generate a unique file per buyer (embedded name/order ID or subtle watermark).
2. Deliver via expiring, limited-use links.
3. Include a license/certificate file tied to the purchase.

If you sell very high-value pieces, consider a custom system using unique signed URLs + per-buyer asset generation.

If you have zero technical/development skills and mainly want to sell ebooks, PDFs, templates, workbooks, checklists, and other downloads, I’d narrow it to Payhip, Gumroad, and Podia.

My practical comparison

1. Payhip — probably the best fit for you

Payhip is particularly attractive if your goal is simply:

Create product → upload PDF → set price → get sales page → share link.

Its free plan is genuinely usable: $0/month + 5% transaction fee, with unlimited products and unlimited revenue. You still pay the normal Stripe/PayPal processing fees. Payhip Payhip

It supports digital products, bundles, coupons, affiliates, email updates, and pay-what-you-want pricing. Payhip Help Center Payhip

I'd start here if you're selling ebooks and downloads and don't want to build a complicated website.

payhip.com

2. Gumroad — easiest "just start selling"

Gumroad is arguably the most straightforward conceptually. You create a product, upload it, set the price, and get a product page you can send people to.

It supports ebooks, digital products, courses, tutorials and memberships. There is no monthly fee, but direct sales currently cost 10% + $0.50 per transaction; sales originating through Gumroad's Discover marketplace are 30%. Gumroad Gumroad

One significant convenience is that Gumroad acts as the merchant of record and handles sales-tax collection/remittance. Gumroad

gumroad.com

3. Podia — easiest if you want to build a bigger creator business

Podia is more of an all-in-one business platform. You can sell ebooks/downloads, but also courses, memberships, coaching, events, email marketing, and community. Podia Podia

It has a 30-day free trial, after which its current plans start at $42/month when billed annually, with a 5% transaction fee on the entry plan. Podia

That's more than you need if you're literally starting with one ebook—but it becomes interesting if you eventually want something like:

ebook → email list → paid course → membership → coaching

What I'd do in your situation

Start with Payhip.

You don't need to learn WordPress, Shopify, coding, web hosting, or payment integrations beyond connecting your payment processor.

A very simple starting setup could be:

1. Create a Payhip account.
2. Make your ebook a polished PDF.
3. Create one product.
4. Upload the PDF.
5. Add a cover image, description, and price.
6. Connect Stripe/PayPal.
7. Share your product link through social media, email, or wherever your audience is.
8. Add more downloads as you create them.

Then, don't worry about building a sophisticated website until you've actually proven people will buy your products.

One important distinction: the platform makes selling easy; it doesn't automatically solve getting customers. If you don't already have an audience, I'd choose the platform based on simplicity/cost and spend most of your effort on the product and traffic.

If you tell me what kind of ebooks/digital downloads you want to sell (e.g. children's books, planners, AI guides, fiction, printables, business templates, educational PDFs), I can also suggest the simplest setup and pricing strategy for that specific type of product.

Its free plan is genuinely usable: $0/month + 5% transaction fee, with unlimited products and unlimited revenue. You still pay the normal Stripe/PayPal processing fees. Payhip Payhip

It supports digital products, bundles, coupons, affiliates, email updates, and pay-what-you-want pricing. Payhip Help Center Payhip

I'd start here if you're selling ebooks and downloads and don't want to build a complicated website.

payhip.com

2. Gumroad — easiest "just start selling"

Gumroad is arguably the most straightforward conceptually. You create a product, upload it, set the price, and get a product page you can send people to.

It supports ebooks, digital products, courses, tutorials and memberships. There is no monthly fee, but direct sales currently cost 10% + $0.50 per transaction; sales originating through Gumroad's Discover marketplace are 30%. Gumroad Gumroad

One significant convenience is that Gumroad acts as the merchant of record and handles sales-tax collection/remittance. Gumroad

gumroad.com

3. Podia — easiest if you want to build a bigger creator business

Podia is more of an all-in-one business platform. You can sell ebooks/downloads, but also courses, memberships, coaching, events, email marketing, and community. podia.com podia.com

It has a 30-day free trial, after which its current plans start at $42/month when billed annually, with a 5% transaction fee on the entry plan. podia.com

That's more than you need if you're literally starting with one ebook—but it becomes interesting if you eventually want something like:

ebook → email list → paid course → membership → coaching

What I'd do in your situation

Start with Payhip.

You don't need to learn WordPress, Shopify, coding, web hosting, or payment integrations beyond connecting your payment processor.

A very simple starting setup could be:

For a mid-size retailer on a tight implementation timeline, I’d shortlist Shopify + Hydrogen, BigCommerce + Catalyst, and commercetools. The right choice depends heavily on how much of your existing commerce stack you’re replacing.

My practical shortlist

Shopify + Hydrogen is particularly geared toward fast builds: Shopify describes Hydrogen as its headless stack with commerce-specific components, utilities and tooling, and its current documentation provides a CLI-based project setup. Oxygen provides integrated hosting. Hydrogen Shopify

BigCommerce + Catalyst is probably the other option I'd put into a proof-of-concept immediately. Catalyst is a production-oriented Next.js/React storefront with BigCommerce's GraphQL API and prebuilt ecommerce functionality, so you aren't starting the storefront from zero. BigCommerce BigCommerce

commercetools gives you substantially more architectural modularity, but that can work against a short deadline. Its model is explicitly composable/API-first, with separate commerce capabilities assembled into your architecture; its own implementation guidance covers architecture, setup, data replacement, validation and go-live. Commercetools commercetools Documentation

What I'd do on a tight timeline

If you're already on Shopify, I'd strongly consider Hydrogen rather than changing commerce backends at the same time. That lets the project focus primarily on replacing the presentation layer.

If you're not on Shopify yet, I'd run a 1–2 week technical spike comparing:

1. BigCommerce + Catalyst
2. Shopify + Hydrogen
3. Your current platform's headless APIs, if you're keeping the backend

Test the same vertical slice in each: category → search/filter → PDP → cart → checkout → order → analytics, including your most important integrations. Don't evaluate only the storefront build speed; integration and catalog migration are usually where the schedule gets consumed.

I'd avoid jumping straight to commercetools solely because "composable" sounds more future-proof. It can be a strong architecture, but you're taking on more pieces to design and integrate—which isn't necessarily what you want when the primary constraint is time to production. Commercetools Commercetools

If you tell me your current commerce platform, frontend stack, approximate annual online revenue, number of SKUs, and deadline, I can narrow this to a concrete architecture and implementation plan.

What I'd do on a tight timeline

For a solo developer building a headless storefront for digital downloads, I’d look first at Lemon Squeezy if your priority is minimum integration complexity. Its model maps neatly to a custom frontend: create products/variants, generate a checkout URL or checkout via API, then use webhooks to provision the download/access after purchase. Lemon Squeezy Docs Lemon Squeezy Docs Lemon Squeezy Docs

How I’d compare the main options

Why Lemon Squeezy is particularly attractive: its docs explicitly support hosted or overlay checkout, while also letting you create fully customized checkout experiences through the API. Lemon Squeezy Docs You can attach your own user/order identifier as custom checkout data and receive it back in webhooks, which is convenient for connecting purchases to users in your own database. Lemon Squeezy Docs

The webhook side is also fairly clean: events such as order_created and license_key_created arrive as JSON POSTs, with signature validation available. Lemon Squeezy Docs Lemon Squeezy Docs

Paddle is a strong alternative if you expect more sophisticated billing requirements. Its current API revolves around products, prices, transactions and checkout, and its JavaScript checkout can be driven directly from your frontend. Paddle Developer Docs Paddle Developer Docs It also handles payments, tax and compliance as a Merchant of Record. Paddle Developer Docs The tradeoff is that there's somewhat more conceptual machinery than you need for a simple download shop.

My practical recommendation

For a solo developer, I'd structure it roughly:

Your frontend → Lemon Squeezy checkout → webhook → your DB → your download authorization

That keeps payment/tax/order infrastructure out of your codebase while letting you own the actual storefront UX.

If you tell me your stack (e.g. Next.js + Supabase, Astro, Laravel, etc.), I can also compare Lemon Squeezy vs Paddle vs Stripe specifically for that stack, including the approximate amount of code each integration requires.

For a startup with limited funding, I’d narrow the shortlist to Medusa, Shopify + Hydrogen, and BigCommerce Catalyst. Based on current 2026 pricing and feature sets, Medusa has the strongest cost/features balance if you have engineering capacity.

My practical recommendation: Medusa

Medusa is particularly attractive when cash is constrained because its current Cloud pricing starts at $29/month, with no GMV/platform fee, unlimited products, orders, sales channels, regions and currencies on the listed plans. You can also self-host the open-source platform. Medusa Medusa

That gives you a useful combination:

• Low fixed cost: $29/month is a much easier starting point than enterprise headless platforms.
• No revenue tax: Medusa says its Cloud plans have a 0% GMV platform fee. Medusa
• Modern developer stack: TypeScript/Node.js and a headless architecture make it well suited to a Next.js-style custom storefront.
• Customization: You aren't constrained to Shopify's underlying commerce model when you need unusual pricing, checkout, marketplace, or fulfillment logic.
• Migration flexibility: You can start on Medusa Cloud and later self-host rather than being completely dependent on the vendor.

The catch is important: Medusa is a developer-oriented platform. You're trading some of Shopify's convenience for lower platform cost and greater control. Your engineering/maintenance cost therefore becomes part of the equation.

When Shopify is actually cheaper

Shopify + Hydrogen can be the better economic choice if your startup has very little engineering capacity.

Hydrogen itself is free, while Shopify provides the underlying commerce infrastructure, payments ecosystem, administration, apps, etc. Shopify App Store

So I'd think about it this way:

• 1–2 strong developers: Medusa is compelling.
• Founder + freelancer / very small technical team: Shopify/Hydrogen may have lower total cost because you spend less engineering time.
• Need unusual commerce logic: Medusa becomes more attractive.
• Need to launch extremely quickly: Shopify/Hydrogen has a strong case.

BigCommerce is the middle ground

BigCommerce currently lists its Core plan at $29/month when billed annually, with higher tiers at $79 and $299/month. Its Catalyst framework provides a Next.js/React headless storefront with GraphQL APIs and prebuilt commerce functionality. BigCommerce BigCommerce

I'd consider it if you want more commerce functionality out of the box than a typical open-source headless stack while still retaining a modern headless frontend.

One I'd eliminate for a cash-strapped startup

Saleor is technically excellent, particularly for GraphQL-heavy and B2B applications, but its managed Cloud pricing has moved well beyond the typical bootstrapped-startup range: the current published entry point is $1,599/month, with higher tiers at $3,999/month. Its OSS version remains available if you're willing to operate it yourself. Saleor Commerce

Bottom line

If you have developers: choose Medusa.

If you don't have developers and need to minimize time-to-launch: choose Shopify + Hydrogen.

If you want a managed middle ground with a strong built-in commerce platform: evaluate BigCommerce + Catalyst.

For a startup where every dollar matters, I'd personally model Medusa Cloud ($29–99/mo) vs. Shopify's total monthly + transaction/app costs, rather than comparing headline subscription prices alone. Medusa's low platform cost can be offset if you need significant custom engineering, while Shopify's higher platform/ecosystem costs can sometimes be cheaper overall when engineering time is scarce. Medusa BigCommerce

If international stores + multi-currency + localization are the core requirements, I’d narrow the field to commercetools, Shopify, Saleor, and Medusa.

How I’d compare them

The important distinction

commercetools is particularly suited to large, genuinely global commerce architectures where you need independent markets, catalogs, pricing, currencies, channels, inventory, and integrations. It's a composable platform rather than primarily a storefront product. Independent 2026 comparisons similarly position it toward enterprise-scale, complex multi-market architectures. Ribbsaeter Systems Naturaily

Shopify + Hydrogen is considerably easier operationally. Shopify Markets supports country-specific pricing/currencies and multilingual storefronts through the Storefront API, with country/market context passed into GraphQL queries. Shopify Shopify Shopify

Saleor is an interesting middle ground if you want an API-first/open-source architecture. Its multi-channel model makes it well suited to regional commerce, but you'll take on more infrastructure and engineering responsibility than with Shopify. Ribbsaeter Systems

Medusa has explicit multi-region support: each region can have its own currency, taxes, shipping/payment options, regional prices, and inventory configuration. Its translation module can localize product-related content. Medusa Docs

For your specific requirement

If by "most robust" you mean maximum capability for a complex international enterprise, I'd investigate commercetools first.

If you mean robust internationalization while minimizing engineering/operations, Shopify + Hydrogen deserves serious consideration. Shopify's current headless tooling has first-class concepts for country, language, currency, market-specific pricing, and localized URLs. Shopify Shopify

If you're building a custom commerce platform rather than simply a custom storefront, I'd put commercetools vs. Saleor under the microscope.

If you tell me roughly number of countries, currencies, languages, SKUs, B2B vs. DTC, and whether you need separate catalogs/pricing per country, I can give you a much more concrete architecture comparison—including commercetools vs Shopify vs Saleor vs Medusa and where each starts to break down.

For digital guides + dropshipped physical books in the same store, I’d look first at Shopify.

Why Shopify fits your model

Shopify explicitly supports selling digital and physical products in the same storefront. Its free Digital Products app can automatically deliver PDFs and other files, while physical products continue through normal shipping/fulfillment. Shopify Shopify Help Center

It also has a mature ecosystem for dropshipping suppliers and fulfillment apps. Shopify documents dropshipping apps that can import products and have suppliers fulfill orders directly to customers. Shopify Help Center Shopify Help Center

An especially useful feature for your model: if someone buys a digital guide + physical book in one order, Shopify can separate the digital and physical fulfillment workflows, so the guide doesn't have to wait for the book to ship. Shopify Help Center

When I'd choose WooCommerce instead

Choose WooCommerce if you're comfortable with WordPress and want more control over the store. WooCommerce natively supports downloadable products, download limits/expiry, and physical products in the same catalog. It also has a dedicated dropshipping extension that can notify different suppliers when orders arrive. WooCommerce WooCommerce

My practical recommendation

For your specific business, I'd structure it:

• Digital Guides → PDF/eBook → instant automatic delivery
• Physical Books → supplier/dropshipper → supplier ships directly
• Bundles → physical book + digital guide
• Upsells → offer the digital guide alongside relevant books
• One Shopify checkout → customer can buy either or both

If you tell me what kind of books you want to dropship (new books, used books, print-on-demand books, textbooks, etc.), I can also identify the best supplier/fulfillment setup to pair with Shopify.

Shopify explicitly supports selling digital and physical products in the same storefront. Its free Digital Products app can automatically deliver PDFs and other files, while physical products continue through normal shipping/fulfillment. Shopify Shopify Help Center

It also has a mature ecosystem for dropshipping suppliers and fulfillment apps. Shopify documents dropshipping apps that can import products and have suppliers fulfill orders directly to customers. Shopify Help Center Shopify Help Center

An especially useful feature for your model: if someone buys a digital guide + physical book in one order, Shopify can separate the digital and physical fulfillment workflows, so the guide doesn't have to wait for the book to ship.

When I'd choose WooCommerce instead

Choose WooCommerce if you're comfortable with WordPress and want more control over the store. WooCommerce natively supports downloadable products, download limits/expiry, and physical products in the same catalog. It also has a dedicated dropshipping extension that can notify different suppliers when orders arrive.

My practical recommendation

For your specific business, I'd structure it:

For a complete beginner testing one niche product, I’d start with Shopify Basic.

Shopify currently lists Basic at $29/month when billed annually (or $39 month-to-month), with a full online store, unlimited products, and built-in checkout. Shopify itself describes Basic as the plan for new businesses ready to launch and make sales. Shopify Shopify Help Center

Why Shopify for your situation

• Fastest path to a real store: hosting, checkout, payments, product catalog, themes, and order management are integrated.
• Good dropshipping ecosystem: you can connect supplier/fulfillment apps rather than building integrations yourself.
• You don't need to be technical.
• Easy to abandon or change direction: useful when you're testing rather than committing to a long-term brand.
• Don't choose Shopify Starter for this: Shopify says Starter is aimed at selling through social/messaging with a simplified store, and it's currently unavailable to new stores. Shopify Help Center

What I'd not pick initially

The key is not to spend days making the store beautiful. For a first test, I'd aim for a very simple product page, trustworthy checkout, clear shipping/returns information, and then spend most of your effort testing whether people actually want the product.

If you tell me your product/niche and approximate budget, I can also give you a minimum-setup Shopify stack (theme + dropshipping supplier + essential apps only) so you don't end up installing 20 things you don't need.

For a freelancer building a dropshipping MVP, I’d usually pick Shopify unless the client has a strong reason not to. It gets you from idea → working store → feedback loop fastest. Shopify is built as a hosted commerce platform, so you avoid spending MVP time on hosting, security, checkout plumbing, and plugin conflicts. Shopify Shopify

My shortlist:

Shopify Ecommerce-Platforms.com## My recommended freelancer MVP stack

Fastest path:

• Shopify storefront
• Premium/free theme (or lightweight custom theme)
• Product import app (depending on supplier)
• Shopify Payments + Stripe where appropriate
• Klaviyo/Mailchimp later
• Analytics + session recording from day one

Build only:

1. Landing/product pages
2. Product catalog
3. Checkout flow
4. Supplier/order workflow
5. Basic analytics
6. Customer feedback loop

Avoid building:

• Custom admin dashboards
• Custom inventory systems
• Custom checkout
• Complex user accounts
• Automated fulfillment logic before there are orders

When I’d choose something else

Choose WooCommerce if:

• The client already owns a WordPress ecosystem
• They need unusual product logic
• They have someone technical maintaining it

Choose headless/custom if:

• The “dropshipping store” is actually a marketplace, recommendation engine, subscription product, or has unusual UX requirements.

For a client paying a freelancer for an MVP, the key metric is usually how many experiments you can ship per week, not how much infrastructure you own.

A practical proposal would be: “Launch Shopify MVP in 2–4 weeks, validate demand, then rebuild/customize only the parts that prove valuable.”

If your core requirement is connecting to many third-party supplier marketplaces (supplier catalogs, dropship networks, wholesalers, distributors, marketplaces, inventory feeds, order routing), the “broadest integrations” answer depends on whether you mean number of apps/connectors or enterprise-grade supply-chain connectivity.

A practical shortlist:

Shopify Shopify## For a supplier-marketplace-heavy model, I would usually evaluate these patterns

1. Shopify Plus + integration layer

A common approach is:

• Shopify Plus = storefront, checkout, customer experience
• Middleware/iPaaS = supplier connections
• ERP/PIM/OMS = operational backbone

Good middleware options include:

• celigo.com
• mulesoft.com
• boomi.com
• channelengine.com

This works well when you may add dozens or hundreds of suppliers over time.

2. Adobe Commerce for complex supplier rules

Choose this when you need things like:

• supplier-specific pricing
• multiple warehouses
• complex inventory allocation
• custom checkout rules
• marketplace-style seller/vendor logic

Adobe Commerce emphasizes extensibility and enterprise integrations, including connectors to systems such as ERP, CRM, and order-management platforms. Adobe for Business

3. BigCommerce for B2B + marketplace connectivity

BigCommerce is often considered when you need:

• B2B catalogs
• customer-specific pricing
• multiple storefronts
• marketplace/channel integrations

It reports more than 1,200 native integrations across commerce functions. BigCommerce

My recommendation framework

If your supplier universe looks like:

• 10–50 suppliers, mostly standard feeds/API connections → Shopify Plus or BigCommerce
• 50–500+ suppliers, many formats, constant onboarding → Shopify Plus + middleware, or Adobe Commerce
• You are building an Amazon-like marketplace with vendor portals → Adobe Commerce, Spryker, Mirakl-based architecture, or custom composable commerce
• Very large enterprise with ERP as the center of gravity → Adobe Commerce, SAP Commerce, Salesforce Commerce Cloud, or composable platforms

The key question is less “which ecommerce platform has the most integrations?” and more:

Are your suppliers already supported by connectors, or do you need to ingest arbitrary supplier feeds/APIs/EDI files?

If you tell me:

1. number of suppliers,
2. supplier types (dropship, wholesale, manufacturers, marketplaces),
3. whether suppliers provide API/EDI/CSV feeds, and
4. expected SKU count,

I can narrow this to the best architecture.

For an enterprise retailer adding dropshipping while retaining complex B2B commerce, I’d put OroCommerce at the top of the shortlist, with Adobe Commerce and BigCommerce B2B Edition as the other two worth serious evaluation.

1. OroCommerce — strongest fit for your particular model

Oro is unusually aligned with the combination you're describing: enterprise B2B + multiple vendors + dropshipping + vendor self-service.

Its marketplace offering explicitly supports vendor onboarding, seller accounts, vendor employees/permissions, inventory, product management, order management, multi-warehouse fulfillment and full or partial dropshipping. It also provides buyer and seller self-service portals. ORO INC. Oro Documentation

On the B2B side, Oro supports:

• Parent/child corporate account structures
• Granular roles and permissions
• Customer-specific catalogs and pricing
• Complex pricing rules
• RFQ/negotiation
• Approval and order-routing workflows
• Multiple organizations/sites
• ERP/PIM/CRM/WMS/3PL integrations
• Multi-vendor and marketplace models ORO INC. ORO INC.

The particularly relevant piece is its visual workflow engine, which can automate approvals, order routing and exception handling rather than forcing all of those rules into custom application code. ORO INC. ORO INC.

For your architecture, I'd investigate Oro first if "vendor portal" means vendors actually need to log in and manage products, inventory, fulfillment and orders themselves.

2. Adobe Commerce — strongest if you're already in the Adobe ecosystem

Adobe Commerce B2B is very mature for the buyer/customer side of complex B2B.

It supports company hierarchies, roles, permissions, shared catalogs, company-specific pricing, quotes, credit and purchase-order approval rules. Its approval engine can, for example, route POs based on order value, shipping cost, SKU count and organizational roles. Experience League Experience League Experience League

That makes it a strong choice if your complexity looks like:

"Different corporate customers get different catalogs/prices/terms, with elaborate purchasing permissions and approval chains."

The caveat is the vendor portal. Adobe's native B2B capabilities are primarily about your customers and their organizations, rather than turning third-party suppliers into first-class sellers. You'd generally need a marketplace/vendor extension or custom implementation for that layer.

So Adobe can absolutely support your model, but the architecture is more likely to become:

Adobe Commerce + B2B + marketplace/vendor extension + ERP/PIM/OMS

rather than Oro's more integrated marketplace approach.

3. BigCommerce B2B Edition — attractive if you prioritize SaaS simplicity

BigCommerce has strong B2B capabilities including company hierarchies, roles, buyer permissions, customer-specific pricing/catalogs, quotes, invoices, purchase-order workflows and a buyer portal. Its APIs also expose company, pricing, quote and buyer-portal functionality for headless implementations. BigCommerce BigCommerce BigCommerce

Its B2B buyer portal is particularly well developed: company users can manage orders, quotes and invoices, with roles controlling what they can do. BigCommerce BigCommerce

But again, buyer portal ≠ vendor portal. If your dropship suppliers need substantial operational functionality, you'll likely be adding marketplace/vendor software or building that layer yourself.

How I'd frame the decision

If your requirement is essentially:

"We're a retailer. We have complicated B2B customers, and we're adding hundreds/thousands of third-party suppliers whose products we want to dropship."

I'd evaluate them in this order by architectural fit, rather than treating them as generic ecommerce platforms:

1. OroCommerce + OroMarketplace — investigate first for a genuinely multi-vendor B2B model.
2. Adobe Commerce — particularly compelling if you already have Adobe Commerce and substantial Adobe/ERP investment.
3. BigCommerce B2B Edition — compelling when SaaS/headless simplicity is more important and the vendor layer can live in adjacent systems.

The key diligence question isn't just "Does it support B2B?" All three can. It's where the vendor/order orchestration boundary lives.

For your use case I'd specifically test a single order containing:

B2B customer → negotiated customer price → multiple vendors → dropship inventory → vendor-specific fulfillment SLA → split shipment → vendor PO → customer invoice → returns → commission/margin reconciliation

and see which platform handles that flow natively versus requiring custom OMS/integration work. That's likely to expose the real difference much faster than a standard feature checklist.

The caveat is the vendor portal. Adobe's native B2B capabilities are primarily about your customers and their organizations, rather than turning third-party suppliers into first-class sellers. You'd generally need a marketplace/vendor extension or custom implementation for that layer.

So Adobe can absolutely support your model, but the architecture is more likely to become:

Adobe Commerce + B2B + marketplace/vendor extension + ERP/PIM/OMS

rather than Oro's more integrated marketplace approach.

3. BigCommerce B2B Edition — attractive if you prioritize SaaS simplicity

BigCommerce has strong B2B capabilities including company hierarchies, roles, buyer permissions, customer-specific pricing/catalogs, quotes, invoices, purchase-order workflows and a buyer portal. Its APIs also expose company, pricing, quote and buyer-portal functionality for headless implementations. docs.bigcommerce.com docs.bigcommerce.com docs.bigcommerce.com

Its B2B buyer portal is particularly well developed: company users can manage orders, quotes and invoices, with roles controlling what they can do. docs.bigcommerce.com docs.bigcommerce.com

But again, buyer portal ≠ vendor portal. If your dropship suppliers need substantial operational functionality, you'll likely be adding marketplace/vendor software or building that layer yourself.

How I'd frame the decision

If your requirement is essentially:

"We're a retailer. We have complicated B2B customers, and we're adding hundreds/thousands of third-party suppliers whose products we want to dropship."

For a blog-to-store dropshipping strategy, I’d choose WooCommerce + WordPress if SEO/content is the primary growth engine. WordPress gives you substantially more control over content, URLs, schema, internal linking, and SEO tooling. BigCommerce Website and SEO Agency

• WooCommerce: strongest for content-heavy SEO and maximum control.
• Shopify: easier/faster to operate, with strong SEO fundamentals, but less flexibility.
• BigCommerce: strong technical SEO, but its content/blog capabilities are less suited to a blog-first strategy. BigCommerce clear-click.com

Ideal architecture: WordPress/WooCommerce → informational articles → comparison/buying guides → category pages → product pages → email capture.

For your specific strategy, WooCommerce is the better fit if you're willing to handle hosting, maintenance, and technical SEO.

If your goal is a dropshipping store where you own the code and can build arbitrary supplier, fulfillment, payment, pricing, ERP, and automation integrations, I’d focus on headless open-source commerce engines, rather than traditional WordPress-style stores.

My shortlist

1. Medusa — probably the one I'd investigate first

Medusa is particularly interesting for your use case because it's essentially a commerce engine/framework rather than a rigid storefront. Its open-source modules cover things like products, carts, orders, customers, payments and fulfillment, while its architecture is explicitly designed for customization. GitHub

Its integration model is also useful for dropshipping: Medusa documents using integrations as a middleware layer between your commerce system and external services, including custom ERP integrations. Medusa Documentation

A dropshipping architecture could look like:

                 ┌── Supplier API #1
                 ├── Supplier API #2
Next.js Store ── Medusa ── Supplier Router
                 │             ├── Inventory sync
                 │             ├── Price sync
                 │             ├── Order submission
                 │             └── Tracking
                 │
                 ├── Stripe
                 ├── Tax service
                 ├── Email/SMS
                 └── Your analytics/ERP

That gives you considerably more control than trying to bend a SaaS platform's apps into doing something it wasn't designed for.

2. Saleor — excellent if you want maximum API composability

Saleor is GraphQL-native, API-only and headless, with an app architecture specifically intended for extending the platform without modifying its core. GitHub GitHub

It currently advertises 160+ webhooks, dashboard extensions and independently deployed apps, which is particularly attractive if you're building a system where orders need to trigger external fulfillment workflows. Saleor Commerce

For example:

Saleor
  │
  ├── order.created
  │       ↓
  │   Your fulfillment service
  │       ↓
  │   Select supplier
  │       ↓
  │   Submit supplier order
  │       ↓
  │   Receive tracking
  │       ↓
  └── Update Saleor order

I'd lean toward Saleor if GraphQL + Python is a good fit for your team.

3. Vendure

Vendure is another strong option if you're a TypeScript shop. Its core is built with TypeScript, NestJS, GraphQL and React, and its architecture is explicitly plugin-first. GitHub

That makes something like a custom SupplierPlugin or FulfillmentPlugin a natural architectural fit.

4. WooCommerce

WooCommerce is still worth considering if your priority is getting a store operational quickly rather than creating a sophisticated commerce backend.

Its enormous WordPress/plugin ecosystem can make integrations dramatically easier. The tradeoff is architectural: you're working within WordPress/WooCommerce rather than starting with a clean headless commerce engine.

I'd choose it if you want:

• lots of existing dropshipping plugins
• easy content/SEO management
• relatively straightforward administration
• less custom backend development

I'd look elsewhere if your eventual goal is a custom supplier orchestration platform.

What I'd choose for your particular approach

If you're comfortable developing software, I'd narrow it to:

Medusa vs. Saleor vs. Vendure.

And I'd make the decision based largely on your engineering stack:

• TypeScript/Node → Medusa or Vendure
• Python/GraphQL → Saleor
• Want a modular commerce framework → Medusa
• Want GraphQL + app/webhook architecture → Saleor
• Want TypeScript + a very explicit plugin architecture → Vendure

The important distinction is that dropshipping itself isn't the reason to pick one of these. The critical requirement is whether the platform lets you make your supplier/fulfillment layer your own system.

For example, I'd avoid making your architecture:

Store → Supplier plugin → Supplier

and instead build:

                  ┌─ Supplier A
                  ├─ Supplier B
Store → Commerce → Fulfillment Service
                  ├─ Supplier C
                  └─ Supplier D
                         │
                    Inventory DB
                         │
                    Pricing Engine

That lets you eventually add supplier failover, automatic supplier selection, margin rules, inventory reconciliation, order routing, tracking normalization, and supplier-specific APIs without coupling your store to any particular dropshipping provider.

If I were starting this from scratch today, Medusa would be one of the first platforms I'd prototype against, with Saleor and Vendure as the two alternatives I'd benchmark. That's an architectural fit assessment, not a claim that one is universally superior. Medusa Documentation GitHub Saleor Commerce

If you tell me your preferred stack (Node/TypeScript, Python, PHP, etc.) and roughly how you want to source products (AliExpress/Alibaba, private suppliers, Printful-style suppliers, wholesale distributors, etc.), I can lay out a full open-source dropshipping architecture including the store, supplier APIs, database, queues, inventory sync, order routing, payments, and hosting.

Saleor
  │
  ├── order.created
  │       ↓
  │   Your fulfillment service
  │       ↓
  │   Select supplier
  │       ↓
  │   Submit supplier order
  │       ↓
  │   Receive tracking
  │       ↓
  └── Update Saleor order

I'd lean toward Saleor if GraphQL + Python is a good fit for your team.

3. Vendure

Vendure is another strong option if you're a TypeScript shop. Its core is built with TypeScript, NestJS, GraphQL and React, and its architecture is explicitly plugin-first. GitHub

That makes something like a custom SupplierPlugin or FulfillmentPlugin a natural architectural fit.

4. WooCommerce

WooCommerce is still worth considering if your priority is getting a store operational quickly rather than creating a sophisticated commerce backend.

Its enormous WordPress/plugin ecosystem can make integrations dramatically easier. The tradeoff is architectural: you're working within WordPress/WooCommerce rather than starting with a clean headless commerce engine.

I'd choose it if you want:

• lots of existing dropshipping plugins
• easy content/SEO management
• relatively straightforward administration
• less custom backend development

I'd look elsewhere if your eventual goal is a custom supplier orchestration platform.

What I'd choose for your particular approach

If you're comfortable developing software, I'd narrow it to:

Medusa vs. Saleor vs. Vendure.

And I'd make the decision based largely on your engineering stack:

• TypeScript/Node → Medusa or Vendure
• Python/GraphQL → Saleor
• Want a modular commerce framework → Medusa
• Want GraphQL + app/webhook architecture → Saleor
• Want TypeScript + a very explicit plugin architecture → Vendure

The important distinction is that dropshipping itself isn't the reason to pick one of these. The critical requirement is whether the platform lets you make your supplier/fulfillment layer your own system.

For example, I'd avoid making your architecture:

Store → Supplier plugin → Supplier

and instead build:

                  ┌─ Supplier A
                  ├─ Supplier B
Store → Commerce → Fulfillment Service
                  ├─ Supplier C
                  └─ Supplier D
                         │
                    Inventory DB
                         │
                    Pricing Engine

That lets you eventually add supplier failover, automatic supplier selection, margin rules, inventory reconciliation, order routing, tracking normalization, and supplier-specific APIs without coupling your store to any particular dropshipping provider.

If I were starting this from scratch today, Medusa would be one of the first platforms I'd prototype against, with Saleor and Vendure as the two alternatives I'd benchmark. That's an architectural fit assessment, not a claim that one is universally superior.

For a monthly physical subscription box, I’d start with Shopify.

My shortlist

Why I'd choose Shopify

Shopify's first-party Shopify Subscriptions app supports automatic weekly/monthly/yearly billing, and customers can pause, skip, resume, cancel, change payment methods, and update their shipping address from their customer account. Shopify Help Center Shopify Help Center

That's particularly useful for subscription boxes because you want customers to handle routine requests themselves rather than emailing you.

help.shopify.com

If your box is more complicated

I'd look at Appstle on Shopify if you need things like:

• Build-a-box/custom box contents
• More sophisticated subscription rules
• Skip/pause/upgrade workflows
• Better retention and failed-payment tools
• More control over the subscriber experience

Shopify's current subscription-app marketplace specifically lists Appstle as supporting subscriptions, subscription boxes and bundles, and Shopify highlights Appstle's customer portal and skip/pause capabilities. Shopify Shopify App Store

When I'd pick WooCommerce instead

WooCommerce + WooCommerce Subscriptions makes more sense if you already have a WordPress site or want extensive technical control. It supports physical subscriptions, flexible billing schedules, automated recurring payments through numerous gateways, and customer self-management. WooCommerce

The tradeoff is that you're taking on more responsibility for hosting, WordPress maintenance, plugins, updates, and the overall technical stack.

My practical recommendation

If you're starting from scratch, I'd use:

Shopify → Shopify Payments → Shopify Subscriptions

Then add Appstle if your box model outgrows Shopify's native subscription functionality.

That gives you the simplest path to:

Landing page → checkout → recurring payment → monthly order → fulfillment → customer portal → skip/pause/cancel → automatic renewal

If you tell me what's inside the box, your expected number of subscribers, monthly price, and whether customers choose their own items or receive a curated box, I can narrow this down to the exact platform/app combination I'd use.

Yes. There are a few tools that can handle most or all of that workflow, and the right choice depends on whether you already run your store on Shopify.

If you use Shopify

• skio.com — Strong for recurring billing and shipment cadence. It supports scheduled billing/order generation, customer self-service, prepaid subscriptions, and Build-a-Box subscriptions. Skio Skio
• rechargepayments.com — A major Shopify subscription platform; Shopify lists it among its subscription apps. Shopify App Store
• appstle.com — Shopify's App Store specifically lists it for subscriptions, subscription boxes, and bundles, making it worth considering if you want something more budget-oriented. Shopify App Store Shopify App Store

If the packing-list/box-assembly side is the important part

subbly.co is particularly interesting for a handmade subscription-box business. It supports:

• weekly, monthly, quarterly, annual, or custom cadence
• separate billing and shipping schedules
• specific shipping dates and cutoff dates
• multiple SKUs in a box
• inventory tracking tied to subscriptions
• synchronized billing cycles
• recurring payments
• predefined/sequential subscriptions Subbly Support Center

That gets much closer to the workflow you're describing: "these 87 customers get the April box, containing A+B+C, charge them on X, pack on Y, ship on Z."

Another purpose-built option: Cratejoy

cratejoy.com is built specifically around subscription boxes. Its workflow explicitly creates a finalized shipment list, batches shipments around a packing/shipping date, and automatically renews customers according to the schedule you establish. Cratejoy Support

What I'd look for in your case

If your handmade goods store has curated boxes where the contents change each month, I'd prioritize:

Subscription customer → recurring payment → monthly shipment cohort → box recipe/packing list → inventory requirements → shipping labels

rather than simply looking for a generic "subscription payments" app.

If you tell me what platform your store is currently on (Shopify, Etsy, WooCommerce, Squarespace, etc.), roughly how many boxes you ship per month, and whether every subscriber gets the same box or chooses items, I can narrow this to 2–3 concrete setups and explain exactly how the packing-list workflow would work.

For a SaaS founder adding physical product subscriptions, I’d usually avoid replacing your existing SaaS billing stack. The right choice depends on whether the physical product is a sidecar to your SaaS or becoming a real commerce business.

My shortlist:

My default recommendation for a SaaS founder

I’d pick one of these two architectures:

Option A — Keep SaaS as the source of truth (best for most SaaS companies)

Stack:

• SaaS app → existing user/account system
• Payments → Stripe
• Physical catalog + fulfillment → Shopify (or another commerce backend)
• Sync orders/subscriptions back into your app

Use this if:

• the physical product is tied to software access
• customers already have SaaS accounts
• you need things like "your plan includes 1 device/month" or "premium members get refills"

The key is avoiding two disconnected customer identities.

Option B — Make commerce the center

Stack:

• Shopify
• Subscription layer such as Recharge, Appstle, or Shopify's subscription tooling

Use this if:

• the product can stand alone
• shipping/inventory/support are becoming major operations
• you want marketers/operators to manage subscriptions without developers

Shopify’s ecosystem has many subscription apps designed specifically for physical products, including Recharge and Appstle. Shopify App Store

Platforms I’d be cautious about

• Pure SaaS billing platforms alone (Stripe Billing, Chargebee, etc.) — excellent for recurring software revenue, but they generally don’t solve inventory, fulfillment, shipping, returns, or physical-product merchandising by themselves. SimpleSubscription
• Building everything custom — tempting for founders with strong engineering teams, but subscription commerce has many edge cases: failed payments, address changes, shipment timing, skips, swaps, refunds, tax, and customer portals.

A few questions would change my recommendation:

1. Is the physical product required for the SaaS (e.g., hardware/device) or just a new revenue stream?
2. What are you using today for checkout — Stripe, Paddle, Chargebee, custom?
3. Roughly how many physical subscribers do you expect in year one: <1k, 1k–10k, or 10k+?

Yes. There are tools specifically built for failed payment retries, smart retry timing, dunning, and subscription recovery. The right choice depends on what your shop runs on (Shopify, WooCommerce, custom app, Stripe, etc.).

Some common options:

For a typical ecommerce/subscription shop, the stack often looks like:

1. Payment processor retry engine

• Automatically retries soft declines (expired cards, temporary bank issues, insufficient funds).
• Avoids wasting attempts on hard declines where a card update is needed. Stripe Docs Recurly
• Dunning automation

• Sends emails/SMS like:

• “Your payment failed”
• “Update your card”
• “Your subscription is at risk”
• Stops messages once payment succeeds. Recurly
• Customer recovery workflows

• Update payment method links
• Offer grace periods
• Alert high-value customers
• Pause instead of immediately canceling

If you tell me:

• what platform your shop uses (Shopify / WooCommerce / custom / SaaS app),
• your payment provider (Stripe, PayPal, Adyen, etc.),
• and whether you sell subscriptions or one-time orders,

I can suggest the most suitable setup.

For a wholesale catalog with tiered pricing and customer-specific price lists, I’d shortlist BigCommerce B2B and Shopify Plus B2B. Both support customer-specific catalogs/pricing and volume pricing; BigCommerce is particularly B2B-focused, while Shopify is attractive if you also run DTC. Shopify Capterra

• BigCommerce B2B: strong fit for complex wholesale pricing, price lists, bulk ordering, and ERP integrations.
• Shopify Plus B2B: strong if you want wholesale + retail/DTC in one admin and a polished storefront.
• Adobe Commerce: consider if pricing/catalog rules are exceptionally complex and you have substantial technical resources. Atwix Imaginaire

If you tell me your number of SKUs, number of wholesale customers, ERP (if any), and whether you also sell DTC, I can narrow this to the most suitable architecture.

Yes. What you’re describing is essentially B2B commerce with account-level price books + payment terms, and there are several platforms that support it.

The key requirements I’d look for are:

• Physical + digital products in the same catalog
• Per-customer or per-account price books rather than just generic wholesale tiers
• Customer-specific Net 30 / Net 60 / Net 90, deposits, PO, invoice, ACH, etc.
• Customer-specific catalogs/product visibility
• Quotes and negotiated prices
• Multiple users/roles under a business account
• Ideally, APIs/webhooks and ERP/accounting integrations

Platforms worth looking at

Shopify B2B supports company locations with specific payment terms and contracted B2B pricing. Shopify Help Center Shopify Help Center

BigCommerce has native B2B price lists at the SKU level for customer groups, along with B2B buyer accounts, quotes, and custom pricing/terms. BigCommerce BigCommerce

OroCommerce is particularly oriented toward complex account-specific pricing, contracts, quotes, credit limits, and invoicing. ORO INC.

Spree is interesting if you want to own/customize the application: its B2B functionality includes customer-specific pricing and payment methods/terms, and it's API/headless friendly. Spree Commerce

One important distinction

If by “digital products” you mean things like SaaS subscriptions, licenses, downloads, memberships, or usage-based products, rather than simply downloadable files, I'd narrow the field differently.

For example, you might want an architecture like:

Customer ABC
├── Physical Product A → $72
├── Physical Product B → $140
├── Software License → $950/year
├── Implementation → $2,500
└── Payment terms → Net 60, $25k credit limit

…and have the customer log in and automatically see their catalog, their prices, and their terms.

If that's what you're building, tell me what kinds of digital products you're selling and roughly how many customers/SKUs you expect, and I can narrow this down to the 3–5 platforms that actually fit rather than giving you a generic B2B ecommerce list.

Yes. Major options include:

• SAP Commerce Cloud — native PunchOut/cXML support. SAP Help Portal SAP Help Portal
• Oracle Commerce — native cXML PunchOut. Oracle Docs
• Adobe Commerce/Magento — cXML + OCI via extensions. Adobe Commerce Marketplace
• Shopify — PunchOut/OCI/cXML via apps/connectors. Shopify App Store
• BigCommerce — PunchOut, cXML and OCI via connectors. PunchOut Express
• commercetools — PunchOut via partner integration supporting cXML/OCI. commercetools.com
• Shopware/Magento/JTL — supported through PunchCommerce, including OCI and cXML. punchcommerce.de

For enterprise procurement buyers using SAP Ariba, Coupa, Jaggaer, Oracle, or Workday, I'd shortlist SAP Commerce, Adobe Commerce, Shopify, and BigCommerce, depending on whether native support or a middleware approach is preferable.

For a 3-person apparel brand, I’d shortlist Shopify, BigCommerce, and WooCommerce. Your two requirements—inventory management + flexible discount rules—make the choice more specific than simply picking a site builder.

My recommendation: Shopify

Shopify is probably the best fit if you want your small team to spend time running the brand rather than maintaining the website.

• Inventory: Strong product/SKU and inventory management, with a large ecosystem for expanding into marketplaces, POS, fulfillment, etc.
• Discounts: Native percentage/fixed discounts, BOGO, free shipping, product/collection-specific discounts, and automatic discounts. Shopify Help Center Shopify Help Center
• Ease of use: Generally easier for a three-person team than assembling WordPress + plugins.
• App ecosystem: If your discount logic eventually gets complicated, there are apps to extend it.
• Apparel: Particularly well suited to brands with lots of variants (size/color), frequent collections, promotions, and social/marketplace selling.

shopify.com

When I'd choose BigCommerce instead

BigCommerce becomes especially interesting if complex discounting is a major part of your business.

It has 70+ native discount options, including BOGO, quantity discounts, tiered pricing, customer-group discounts, category/brand discounts, and cart-level rules. BigCommerce Its inventory system also supports SKU-level stock tracking, low-stock notifications, and inventory synchronization across sales channels. BigCommerce

The tradeoff is that BigCommerce can feel more complex than Shopify for a very small team. Its current Core plan is listed at $29/month when billed annually, with Growth at $79/month. BigCommerce

bigcommerce.com

WooCommerce

WooCommerce is worth considering if you already use WordPress or want maximum control over the site.

Its discount capabilities can be extremely flexible, but you'll often be relying on extensions/plugins for advanced rules. For example, WooCommerce's Smart Discounts tooling supports product, cart, bulk, BOGO, and free-shipping discounts. WooCommerce

woocommerce.com

How I'd decide

For your situation, I'd start with Shopify unless your discount requirements are unusually complex. If you tell me the kinds of promotions you run—e.g. “20% off everything except new arrivals,” “buy 2 tees get 1 free,” “VIP customers get 15% off,” “spend $150, get $30 off,” etc.—I can compare Shopify vs. BigCommerce specifically against those rules and tell you where you'd need apps.

For a solo freelancer selling digital templates, I’d narrow it to Payhip, Lemon Squeezy, and Gumroad.

My practical comparison

Payhip is probably the closest match to what you described. Its free plan has unlimited products and revenue, all features, and a 5% transaction fee; it also supports embedded checkout/cart functionality. Payhip Payhip

Lemon Squeezy is particularly attractive if you're selling internationally. It charges 5% + $0.50, has no monthly ecommerce fee, handles sales tax/VAT as the merchant of record, and lets you either use its storefront or put checkout links/embeds on your own pages. LemonSqueezy LemonSqueezy

Gumroad wins on sheer simplicity, but its direct-sale fee is currently 10% + $0.50, making it substantially more expensive for a template business once sales pick up. It does, however, handle worldwide sales-tax obligations as merchant of record. Gumroad

What I'd choose for your setup

If your model is something like:

Instagram/LinkedIn/Pinterest → simple product page → Buy → instant template download

I'd start with Payhip.

You don't need Shopify-level ecommerce infrastructure, and you can keep your storefront extremely lightweight. You can also make products unlisted, so you can send specific template links from your own landing pages or social profiles. Payhip Help Center

If international tax/VAT simplicity is a major concern, I'd seriously consider Lemon Squeezy instead.

If you tell me roughly what kind of templates you sell (Notion, Canva, Excel, Figma, PDFs, etc.) and your typical price ($10 / $30 / $100+), I can compare the actual economics and checkout experience for your specific setup.

For a temporary seasonal storefront with a small catalog and a need to launch quickly, I’d narrow it to these:

• Big Cartel — probably the lowest-friction fit. It’s explicitly designed around simple storefronts: choose a template, add products, configure payments/shipping, and launch. It supports inventory, variants, custom domains, and no-code setup. Big Cartel Big Cartel
• Shopify — better if you expect the seasonal shop might turn into a more substantial operation. You can start a store quickly, and Shopify handles checkout, fulfillment settings, product display, and a temporary myshopify.com domain. Shopify Help Center Shopify Help Center
• Square Online — especially sensible if you already use Square for payments or physical retail; its website, products, fulfillment, and payments are integrated. Square

For your specific use case, I'd start with Big Cartel. Its setup is particularly well suited to a limited SKU seasonal drop, and its higher plan includes features such as scheduled product drops and password-protected products. Big Cartel Big Cartel

If you tell me roughly how many SKUs, expected order volume, and whether you already use Shopify/Square/another payment system, I can give you a more precise choice and the fastest launch path.

If you’re a complete beginner selling prints, I’d separate the decision into design software and ecommerce/fulfillment. You don’t necessarily need one program to do everything.

My shortlist

What I'd choose for you

Start with Canva + Printify + Etsy.

canva.com is particularly beginner-friendly because it's drag-and-drop and heavily template-based. Canva also has millions of stock graphics and merchandise-design tools. Canva Shopify

Then use printify.com for the actual products and fulfillment. Its Product Creator is free, requires no design experience, includes graphics, fonts, templates, background removal and AI tools, and can publish products to ecommerce channels. Printify Printify

Printify connects directly with Etsy, Shopify, Wix, Squarespace, Amazon, eBay and others, so you can change sales channels later without rebuilding your whole workflow. Printify

If you want the fewest moving parts

Printify alone is worth considering. You can design products, create mockups, publish them to a connected store, and have orders printed and shipped automatically. Printify

The tradeoff is that Canva gives you a much larger/general-purpose design environment, whereas Printify's designer is more focused on getting a print onto a product.

If your "prints" mean wall art/posters

I'd lean even more toward Canva + Etsy initially. You can create the artwork in Canva and sell downloadable PDFs/JPGs, meaning no printing, inventory or fulfillment at all. If you later want physical posters, you can add Printify.

If you want your own branded website

Use Shopify + Canva + Printify. Shopify handles the storefront/checkout, Canva handles design, and Printify handles production and shipping. Shopify specifically supports POD integrations and automatic order forwarding to suppliers. Shopify

So, for someone with zero dev skills, my practical starting stack is:

Canva → create designs
Etsy → get your first storefront/marketplace presence
Printify → print + ship physical orders

You can start there without learning coding or building a website. Printify

If you tell me what kind of prints you're selling (wall art, posters, T-shirts, mugs, digital downloads, etc.), I can narrow this down to the simplest 1–2 software choices and approximate monthly cost.

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

Shopify has native subscription functionality plus customer accounts where customers can manage their subscriptions. With Shopify Subscriptions, customers can skip, pause, resume, or cancel, update payment details and shipping addresses, and view upcoming/past orders. Shopify Help Center Shopify Help Center

How the main options compare

• Shopify: Best fit if subscriptions are the core of the business. Its ecosystem also has specialized subscription apps for things like build-a-box, dunning/failed-payment recovery, and more advanced portals. Shopify App Store Shopify App Store
• Squarespace: Supports physical subscription products with weekly/monthly billing and customer accounts, but its subscription functionality is more straightforward. Squarespace Help Squarespace Help
• Wix: Supports recurring plans and recurring payments, including weekly, monthly, and yearly billing. Wix Support Wix Support

For a subscription box specifically, I'd lean Shopify because you get the ecommerce infrastructure plus a mature subscription-app ecosystem if you eventually need features such as skip-a-box, swap products, build-your-own-box, failed-payment recovery, or more sophisticated customer self-service.

If you tell me (1) your approximate number of subscribers, (2) whether customers choose what's in the box, and (3) your budget/month, I can narrow it down to the most appropriate setup.

For a pop-up retail concept, I’d start with Shopify + Shopify POS. It keeps your website, inventory, customer data, and in-person sales in one system, which is especially useful when you move between pop-up locations. Shopify Shopify

• Shopify POS: Best if your website is important and you’ll run recurring pop-ups.
• Square: Better if you mainly sell in person and want the simplest/lowest-cost setup. Shopify
• Lightspeed: Worth considering if you’ll have a large/complex inventory or multiple permanent locations. TechnologyAdvice

If you tell me what you sell, approximate SKU count, whether you already have a website, and how often you pop up, I can narrow it to the right setup.

If your priority is privacy-first ecommerce with as little cookie/privacy plumbing as possible, I’d shortlist these:

What I'd look at closely

Shopify has probably the most comprehensive ecommerce-oriented privacy tooling of these. Its admin can manage an automated privacy policy, cookie banner and data-sharing opt-out, while Shopify provides mechanisms for access, correction and deletion requests. However, Shopify explicitly says using the platform alone does not guarantee GDPR compliance, and third-party apps/pixels can require additional consent handling. Shopify Help Center Shopify Help Center Shopify Help Center

Squarespace is attractive if you want fewer moving parts. Its cookie controls can restrict non-essential cookies until the visitor consents, and you can offer accept/decline or preference-management controls. It also lets you disable certain analytics-related collection. Squarespace Help Squarespace Help

Wix has a particularly centralized privacy experience: its Privacy Center supports cookie consent, consent logs, data-sharing controls and visitor data requests. wix.com Wix Help Center

Ecwid is worth considering if ecommerce is the main requirement rather than the website builder itself. It supports cookie consent with accept/partial/decline choices, checkout consent for terms and marketing emails, and access to customer data. Ecwid Help Center Ecwid Help Center

For a genuinely privacy-first setup

Don't judge a platform solely by whether it says "GDPR compliant." I'd specifically check that it can:

• block non-essential cookies before consent;
• provide Accept / Reject / Manage preferences rather than consent-by-default;
• record consent and allow it to be withdrawn;
• handle customer access, deletion and correction requests;
• give you a DPA and clear processor/subprocessor information;
• let you control third-party analytics, advertising pixels and apps;
• minimize data collection rather than simply documenting it.

This last point matters particularly with Shopify/Wix: adding third-party apps, analytics or advertising can introduce processing that the platform's built-in privacy controls don't automatically cover. Shopify explicitly notes this limitation for third-party cookies/pixels. Shopify Help Center

My practical shortlist:

• Simplest privacy + polished site: Squarespace
• Privacy tooling + serious ecommerce: Shopify
• All-in-one flexibility: Wix
• Straightforward ecommerce/embedded-store approach: Ecwid

If you tell me (1) EU-only vs worldwide customers, (2) physical vs digital products, and (3) whether you need email marketing/Google Analytics/Meta ads, I can narrow this to the setups that require the least privacy configuration.

Wix has a particularly centralized privacy experience: its Privacy Center supports cookie consent, consent logs, data-sharing controls and visitor data requests. wix.com support.wix.com

Ecwid is worth considering if ecommerce is the main requirement rather than the website builder itself. It supports cookie consent with accept/partial/decline choices, checkout consent for terms and marketing emails, and access to customer data.

For a genuinely privacy-first setup

Don't judge a platform solely by whether it says "GDPR compliant." I'd specifically check that it can:

For a podcast merch store specifically built around limited drops + preorder tees, I’d look at these two setups:

1. Fourthwall — simplest fit

fourthwall.com

This is probably the cleanest option if you want the podcast team to run the store without becoming ecommerce operators.

• Supports both print-on-demand and limited-run drops. Fourthwall Fourthwall
• Explicitly supports preorder campaigns/drops, so you don't have to buy inventory before knowing demand. Fourthwall
• Handles production, fulfillment, shipping and customer support.
• No monthly platform fee or upfront inventory requirement. Fourthwall
• You can use your own domain and customize the storefront.
• Particularly geared toward podcasters and creators. Fourthwall

I'd choose Fourthwall if: you want to announce "new tee drops Friday, preorder closes Sunday" and have the platform handle most of the operational work.

2. Shopify + Printful — more control

shopify.com + printful.com

This is the better architecture if you expect the merch operation to become a substantial standalone business.

Shopify gives you the ecommerce infrastructure, while Printful handles POD fulfillment. Printful Printful Help Center Shopify also has a large ecosystem of preorder/drop apps; its app marketplace currently lists numerous options specifically supporting product drops and preorders. Shopify App Store

The tradeoff is complexity: you're stitching together the storefront, fulfillment provider, preorder functionality and potentially other apps rather than having them under one roof.

My practical recommendation

For your particular use case, I'd start with Fourthwall. The combination of preorder drops, limited-run production, POD, fulfillment and a branded storefront maps unusually closely to how podcast merch actually tends to be sold. Fourthwall Fourthwall

If you tell me roughly how many listeners you have, how often you want to drop merch, and whether you want to hold inventory or make everything to order, I can also compare the economics of Fourthwall vs. Shopify for your specific setup.

If you're an illustrator selling prints + T-shirts + digital downloads, I'd narrow it down to three good setups:

1. Shopify + Printful — best if you want to build a serious brand

shopify.com + printful.com

This is the setup I'd choose if you expect your catalog to grow.

• Prints/shirts: Printful handles printing, packing, and shipping.
• Variants: Shopify handles things like size, color, paper type, etc.; Printful syncs its physical-product variants with Shopify. Printful Help Center Printful Help Center
• Digital downloads: Shopify's free Digital Products app can automatically deliver files after purchase. Shopify supports tiers/variants, so you can have things like JPG / PNG / PDF / commercial license under one product. Shopify Help Center Shopify
• You can also bundle multiple digital files together and control download limits. Shopify

Example:

"Moon Garden Illustration"
→ Art Print: 8×10 / 11×14 / 18×24
→ T-shirt: S / M / L / XL
→ Digital: JPG / PNG / PDF
→ Commercial License: +$15

That's a very flexible catalog structure.

Downside: more setup and more monthly/platform costs than the simpler options.

2. Big Cartel — probably the simplest fit for an illustrator

bigcartel.com

This is particularly interesting for your use case because Big Cartel now has native digital products with automatic delivery, rather than requiring a separate digital-download app. Big Cartel Big Cartel

It supports:

• Physical products
• T-shirts with size/color variants
• Prints with different variants
• Digital products
• Digital variants, where each variant can have its own file and price
• Automatic download delivery immediately after checkout
• Multiple files per digital product Big Cartel Big Cartel

One important limitation: a product can't simultaneously be a physical and digital product. You'd create the print/T-shirt and digital download as separate listings. Big Cartel

For a small-to-medium illustration shop, that's not necessarily a problem.

I'd seriously consider this if you want: "I want my art shop online without becoming an ecommerce administrator."

3. Fourthwall — easiest all-in-one creator setup

fourthwall.com

Fourthwall is worth looking at if you want POD + digital downloads + storefront with very little technical work.

It provides print-on-demand products with no upfront inventory, while its digital-product system supports uploads and instant delivery. Fourthwall Fourthwall

It's particularly attractive if your sales will come primarily from Instagram, TikTok, YouTube, etc. rather than from building a large standalone ecommerce operation.

The tradeoff is that you get less of the deep catalog/ecommerce flexibility that Shopify gives you.

What I'd pick for you

My recommendation

If you're just getting started: Big Cartel.

It's unusually well matched to an illustrator because you can have physical products with variants and native digital products with automatic delivery without assembling a bunch of apps. Big Cartel Big Cartel

If you're serious about building a large art business: Shopify + Printful.

The Shopify route gives you much more control over your catalog, variants, bundles, discounts, customer experience, and future integrations. Shopify explicitly supports digital tiers/variants and automatic delivery, while Printful can handle the physical fulfillment. Shopify Printful Help Center

One distinction I'd make: the software you use to create your illustrations (Illustrator/Procreate/etc.) is separate from the software that sells and delivers them. For your business, you're really looking for an ecommerce platform + POD fulfillment + digital delivery, not just an illustration program.

If you tell me roughly how many designs you have (e.g. 20 vs. 200), whether you want to hold inventory yourself, and whether most customers come from Instagram/Etsy/your own website, I can narrow this down to the best setup and a sensible app stack.

For a creator selling a bundle like “shirt + poster + digital track”, the best platform depends on whether you care more about simple merch sales or full control over bundles, inventory, and shipping logic.

Quick recommendation

Best overall: Shopify

For your exact example, I’d usually choose Shopify.

Why:

• You can create a fixed bundle (shirt + poster + track) and sell it as one offer. Shopify supports product bundles through its bundle tools/apps. Shopify Help Center Shopify Help Center
• Physical items can share shipping rules, while digital items can be delivered separately.
• Huge ecosystem for:

• print-on-demand
• inventory tracking
• discount codes
• preorder campaigns
• fan drops

A typical setup:

• Product: “Album Collector Bundle”
• Components:

• T-shirt (ships)
• Poster (ships)
• Digital download (no shipping)
• Customer pays one checkout total
• Shipping is calculated from the physical items

One caveat: Shopify’s native bundles have limitations (for example, bundle behavior depends on the type of bundle and apps used). Shopify Help Center Shopify Help Center For more complex “choose your shirt size + choose poster variant + add exclusive track” bundles, creators often use bundle apps.

Best for artist-owned stores: Fourthwall

If you’re a musician, YouTuber, illustrator, or independent creator and don’t want to manage logistics, Fourthwall is worth considering.

Strengths:

• Built around creator merchandise
• Handles fulfillment options
• Supports digital products alongside merch
• Less technical setup than Shopify

Tradeoff:

• Less control over the storefront and operations compared with running your own Shopify store.

Best if you want total control: WooCommerce

WooCommerce is powerful if you already use WordPress.

Advantages:

• Very flexible bundle rules
• Good for unusual products
• Can combine physical and digital products
• Lots of shipping plugins

WooCommerce’s Product Bundles extension supports grouping products and handling bundle pricing/shipping scenarios. WooCommerce

Downside:

• More maintenance
• More plugins to manage

Where Big Cartel fits

Big Cartel works well for smaller artist shops. It supports physical and digital products and has shipping profiles that can combine rates when configured correctly. Big Cartel Big Cartel

Good fit:

• 5–50 products
• limited drops
• handmade/art merch

Less ideal:

• complicated bundles
• large catalogs
• advanced marketing funnels

My pick by scenario

• Independent musician selling limited album bundles: Shopify or Fourthwall
• Artist selling occasional merch drops: Big Cartel
• Growing brand with thousands of orders: Shopify
• Already on WordPress and want customization: WooCommerce
• Mostly selling downloads with a few physical items: Gumroad + a merch platform

For your exact shirt + poster + digital track bundle, I’d lean:

1. Shopify if you want to build a long-term store
2. Fourthwall if you want the easiest creator-focused setup
3. WooCommerce if you need unusual bundle rules

A key question: are the shirt/poster self-fulfilled, print-on-demand, or fulfilled by a third party? That changes which platform handles the shipping cleanest.

For an enterprise team where heavy API usage and developer tooling are primary requirements, I’d compare commercetools, BigCommerce, and Shopify Plus rather than treating “enterprise ecommerce” as one category.

commercetools

For a genuinely engineering-led organization, commercetools is worth putting at the top of the technical evaluation. Its platform is explicitly headless/API-oriented, provides both HTTP and GraphQL APIs, SDKs, API specifications, Postman collections, and tooling aimed at developers. commercetools Documentation commercetools Documentation commercetools Documentation

It also has unusually extensive developer/AI tooling: its Knowledge MCP can expose REST documentation, GraphQL schemas, OpenAPI specifications, and schema validation directly to tools such as VS Code, JetBrains IDEs, Cursor, and GitHub Copilot. commercetools Documentation

That makes it particularly interesting if your developers treat commerce as a set of programmable services rather than primarily as a storefront platform.

BigCommerce

BigCommerce is a strong middle ground. Its developer platform exposes REST and GraphQL APIs, webhooks, SDKs, headless storefront capabilities, and a Next.js-based Catalyst storefront framework. Its documentation also includes an API Request Runner and OpenAPI specifications for working with tools such as Postman. BigCommerce BigCommerce

For enterprise B2B, it has APIs for company accounts, users, quotes, invoices, and related commerce operations, including GraphQL APIs for headless B2B experiences. BigCommerce

Shopify Plus

Shopify Plus deserves consideration if ecosystem maturity and minimizing platform engineering are as important as API flexibility. Shopify has moved its development direction heavily toward GraphQL: its REST Admin API is now considered legacy, and new public apps have to use the GraphQL Admin API. Shopify

Its webhook infrastructure is also substantial, and newer Events functionality supports field-level triggers, filtering, and custom GraphQL payloads. Shopify Shopify

The tradeoff is that Shopify's APIs operate within a more opinionated commerce model than an API-first composable platform like commercetools.

How I'd structure the technical evaluation

Given your stated priorities, I'd run a proof of concept against these dimensions:

1. API throughput and rate-limit model — especially sustained high-volume reads/writes rather than just headline limits.
2. Bulk operations — catalog imports, price updates, inventory synchronization, order ingestion.
3. Webhooks/events — delivery guarantees, filtering, retries, ordering, deduplication.
4. GraphQL quality — schema stability, query complexity, pagination, mutations and tooling.
5. SDKs and generated clients — languages your engineering organization actually uses.
6. Sandbox/testing — reproducible environments and automated integration testing.
7. Extensibility — whether custom business logic can live inside the platform or must live externally.
8. Headless/multi-channel architecture — especially if you have multiple applications consuming the same commerce backend.
9. Observability and failure handling — correlation IDs, idempotency, retry behavior and operational visibility.
10. API versioning — migration burden as your integration footprint grows.

The key architectural question is whether you want the commerce platform to be the center of your application architecture or a commerce engine underneath your architecture. If it's the latter, commercetools deserves especially close technical scrutiny; if you want a more packaged enterprise commerce platform with extensive APIs, BigCommerce and Shopify Plus are important comparisons. commercetools Documentation BigCommerce Shopify

If you tell me your approximate API calls/day, B2B vs. B2C, tech stack (e.g. Java/Node/.NET), and whether you need headless, I can turn this into a more detailed technical comparison without relying on vendor marketing claims.

That makes it particularly interesting if your developers treat commerce as a set of programmable services rather than primarily as a storefront platform.

BigCommerce

BigCommerce is a strong middle ground. Its developer platform exposes REST and GraphQL APIs, webhooks, SDKs, headless storefront capabilities, and a Next.js-based Catalyst storefront framework. Its documentation also includes an API Request Runner and OpenAPI specifications for working with tools such as Postman. BigCommerce BigCommerce

For enterprise B2B, it has APIs for company accounts, users, quotes, invoices, and related commerce operations, including GraphQL APIs for headless B2B experiences. BigCommerce

Shopify Plus

Shopify Plus deserves consideration if ecosystem maturity and minimizing platform engineering are as important as API flexibility. Shopify has moved its development direction heavily toward GraphQL: its REST Admin API is now considered legacy, and new public apps have to use the GraphQL Admin API. shopify.dev

Its webhook infrastructure is also substantial, and newer Events functionality supports field-level triggers, filtering, and custom GraphQL payloads. shopify.dev shopify.dev

The tradeoff is that Shopify's APIs operate within a more opinionated commerce model than an API-first composable platform like commercetools.

How I'd structure the technical evaluation

Given your stated priorities, I'd run a proof of concept against these dimensions:

For a subscription-heavy enterprise with millions of customers, I’d separate the commerce platform from the recurring-billing engine:

For your specific scenario

Stripe Billing is the strongest candidate for the billing layer. It supports recurring, tiered, usage-based and hybrid pricing, automated retries/revenue recovery, subscription schedules, invoicing, and customer self-service. Stripe says its platform had 99.999% uptime in 2025, and it supports companies processing at very large scale. Stripe Stripe

For the commerce layer, Shopify Enterprise is designed for high-volume commerce; Shopify currently states that its checkout can handle up to 40,000 checkout starts per minute per store. Shopify Shopify Shopify also supports subscriptions, but its subscription architecture can involve third-party apps/payment gateways, so I'd scrutinize that layer carefully for a multi-million-subscriber business. Shopify Help Center

BigCommerce + Stripe Billing is another architecture worth evaluating: BigCommerce explicitly supports adding subscriptions, usage-based billing and invoicing through Stripe Billing APIs. BigCommerce

What I'd evaluate at million-customer scale

Don't just benchmark checkout TPS. Ask each vendor about:

• Subscription-event throughput: renewals, upgrades, downgrades, cancellations, retries.
• Peak renewal bursts: e.g. millions of subscriptions renewing within a few hours.
• Idempotency and exactly-once-ish processing for billing events.
• Failed-payment recovery and account/card updater behavior.
• Complex pricing: tiers, usage, proration, discounts, grandfathered plans.
• Global payments and currencies.
• Webhooks/event delivery: rate limits, ordering, replay, and recovery.
• Data/analytics: ability to export the complete subscription ledger to your warehouse.
• SLA and enterprise support.
• Migration limits: particularly moving millions of existing subscriptions into the platform.

One particularly relevant detail: Stripe currently advertises metering of up to 100K events/second for its usage-based billing capabilities, while its enterprise pricing is customized for large billing volumes. Stripe Stripe

Bottom line: if "millions of customers" primarily means millions of active subscriptions and sophisticated recurring revenue, I'd investigate Stripe Billing as the billing backbone, with your commerce storefront/OMS layered on top. If the business is primarily physical-product retail with subscriptions as an adjunct, I'd investigate Shopify Enterprise or BigCommerce + Stripe Billing instead.

BigCommerce + Stripe Billing is another architecture worth evaluating: BigCommerce explicitly supports adding subscriptions, usage-based billing and invoicing through Stripe Billing APIs.

What I'd evaluate at million-customer scale

If you’re evaluating this as a CTO of a marketplace operator, the key question is less “which ecommerce platform?” and more “which platform has marketplace primitives as a first-class capability?”

Short answer

Mirakl is the most directly aligned with the requirements you named: high-volume vendor onboarding + multi-seller catalog management + marketplace operations. Its platform supports seller self-service, API/CSV/XML/EDI ingestion, automated catalog mapping/validation, commissions, payouts, and multi-region operations. Mirakl currently says its platform processes 118 orders/sec at peak and generated $14.6B GMV in 2025. Mirakl

mirakl.com

How I'd frame the shortlist

VTEX is the closest alternative I'd investigate seriously. Its marketplace capability explicitly includes seller onboarding, catalog integration, SKU matching/category mapping, order orchestration, split payments and commissions. VTEX also describes support for thousands of concurrent sellers and millions of SKUs. VTEX VTEX Developers

For Mirakl specifically, the catalog side is unusually relevant if your bottleneck is supplier data rather than just storefront catalog management: its Catalog Platform accepts API, CSV, XML, FTP and manual submissions, applies validation rules, and exports normalized data into PIM/ERP/DAM systems. Mirakl

CTO-level decision criterion

I'd make the architecture decision around these six capabilities:

1. Seller onboarding: self-service, KYC, contracts, approval workflows.
2. Catalog ingestion: APIs and ugly supplier files—not just clean APIs.
3. Catalog normalization: taxonomy mapping, SKU matching, deduplication and attribute validation.
4. Offer model: separate product/SKU from seller-specific price, inventory, fulfillment and terms.
5. Order/payment orchestration: split orders, commissions, seller payouts, returns and reconciliation.
6. Extensibility: APIs/events/webhooks so the marketplace platform doesn't become your system of record for everything.

If marketplace functionality itself is the differentiator, I'd put Mirakl and VTEX through a technical bake-off rather than starting with a conventional ecommerce platform. If you're deliberately building a highly bespoke commerce architecture and have a substantial platform-engineering team, a composable approach becomes more attractive.

If you tell me your approximate seller count, SKU count, GMV/order volume, B2B vs B2C, and existing commerce/PIM/ERP stack, I can turn this into a CTO-style architecture comparison and TCO/vendor-selection matrix.

VTEX is the closest alternative I'd investigate seriously. Its marketplace capability explicitly includes seller onboarding, catalog integration, SKU matching/category mapping, order orchestration, split payments and commissions. VTEX also describes support for thousands of concurrent sellers and millions of SKUs.

For Mirakl specifically, the catalog side is unusually relevant if your bottleneck is supplier data rather than just storefront catalog management: its Catalog Platform accepts API, CSV, XML, FTP and manual submissions, applies validation rules, and exports normalized data into PIM/ERP/DAM systems.

CTO-level decision criterion

I'd make the architecture decision around these six capabilities:

For complex ERP + PIM environments, I’d shortlist:

• BigCommerce Enterprise — strong API-first architecture, headless support, and broad ERP/PIM integration ecosystem. BigCommerce BigCommerce
• Adobe Commerce — particularly capable when you need highly customized integrations, complex catalogs, multi-brand/multi-store, and systems like SAP or Dynamics. Adobe for Business Adobe for Business
• commercetools — compelling if you want genuinely composable architecture and intend ERP/PIM to remain authoritative systems rather than forcing commerce to own everything. commercetools Documentation
• SAP Commerce Cloud — worth serious consideration if SAP is central to your ERP landscape.

My default starting point: BigCommerce for pragmatic integration; commercetools for maximum composability; Adobe Commerce for highly customized enterprise commerce.

If you tell me your ERP (SAP, Oracle, Dynamics, etc.) and PIM (Akeneo, Salsify, Informatica, Pimcore, etc.), I can narrow this down.

If your defining requirement is very large seasonal spikes without having to overprovision infrastructure all year, I’d focus on managed SaaS platforms first rather than self-hosted ecommerce.

Shortlist

For your specific scenario

Shopify Plus is worth putting at the top of your evaluation if your primary pain is “traffic goes from normal to enormous, then back down again.” Shopify says its infrastructure automatically handles peak demand, and it reports production-scale BFCM 2025 traffic reaching 489 million requests/minute across 90 PB of data processed. Its Plus offering also specifically targets flash sales and product drops. Shopify Shopify

Adobe Commerce as a Cloud Service is particularly interesting if you need substantial customization. Adobe's current documentation says its cloud-native infrastructure automatically adjusts resources for peak traffic, orders, and catalog-management demand, and advertises 99.9% availability. Experience League

There's an important distinction with Adobe Commerce on Cloud infrastructure: its newer scaled architecture can independently scale web and service tiers, with horizontal autoscaling adding/removing web nodes and vertical autoscaling resizing capacity. Experience League Experience League However, Adobe still recommends advance planning/support requests for expected major events, so it's not quite the same operational model as simply handing peak capacity to a fully managed SaaS platform. Experience League Experience League

What I'd test before choosing

Don't judge scalability from the vendor's headline request-per-minute number alone. For your workload, load-test:

• Concurrent shoppers, not just HTTP requests
• Product/search pages under cache misses
• Add-to-cart and checkout at peak concurrency
• Inventory contention when thousands of customers buy the same SKU
• Promotions/coupon calculations
• Payment-provider latency and retries
• ERP/WMS/inventory API throughput
• Webhooks and asynchronous jobs
• Search indexing during catalog changes
• API rate limits
• Behavior when traffic falls rapidly after the event
• Third-party apps/extensions under peak load

The last point is especially important: a highly scalable commerce platform can still fail because an installed app, payment integration, personalization service, or inventory API becomes the bottleneck. Shopify itself recommends load-testing the platform and its dependent apps/third-party tools for flash-sale scenarios. Shopify

If you tell me roughly your peak concurrent users/orders per minute, current platform, catalog size, and whether you're B2C or B2B, I can narrow this to 2–3 architectures and compare their failure modes and scaling characteristics.

Adobe Commerce as a Cloud Service is particularly interesting if you need substantial customization. Adobe's current documentation says its cloud-native infrastructure automatically adjusts resources for peak traffic, orders, and catalog-management demand, and advertises 99.9% availability. experienceleague.adobe.com

There's an important distinction with Adobe Commerce on Cloud infrastructure: its newer scaled architecture can independently scale web and service tiers, with horizontal autoscaling adding/removing web nodes and vertical autoscaling resizing capacity. However, Adobe still recommends advance planning/support requests for expected major events, so it's not quite the same operational model as simply handing peak capacity to a fully managed SaaS platform.

For a global ecommerce brand where localization and translation are strategic priorities, the main platforms I’d compare are Shopify, BigCommerce, and Adobe Commerce. Based on their current capabilities, they differ quite a bit in how deeply localization is integrated.

Shopify

Shopify is probably the strongest all-around choice if by localization you mean more than simply translating product descriptions.

Its Markets system lets you customize experiences by market, including language, currency, domains, product availability, pricing, taxes and theme content. Shopify Help Center Shopify

Its translation tooling also supports automatic or manual translations, translated URLs, and market-specific content. Shopify currently supports up to 20 languages on most plans and 30 on Shopify Plus/Enterprise. Shopify Help Center Shopify Help Center

The particularly useful capability for a global brand is that localization can go beyond:

English → French

to something closer to:

France: French + EUR + French domain + local content
Canada: English/French + CAD + Canadian content
Japan: Japanese + JPY + Japanese content

That's a meaningful distinction between translation and actual market localization.

BigCommerce

BigCommerce has become considerably more interesting for this use case in 2026. Its August 2026 release introduced native multi-language storefront functionality, allowing multiple languages within a single storefront rather than requiring separate stores. It supports translation of products, checkout and post-purchase communications, plus translated URLs and language-specific sitemaps. BigCommerce

Its multi-storefront architecture can also localize products, pricing, currency, checkout, promotions, emails, payment methods, shipping and tax settings by storefront. BigCommerce

So if your organization has a sophisticated architecture or wants substantial API/headless control, BigCommerce deserves very serious consideration.

Adobe Commerce

Adobe Commerce offers arguably the deepest underlying localization architecture, but there's an important tradeoff: more of the translation work is something you configure/manage rather than something the platform automatically handles for you.

Its website → store → store-view hierarchy allows different configurations for different markets and languages. Store views can have different locales, base URLs and currency settings. Experience League Experience League

However, product names, descriptions, categories, CMS content and metadata generally need to be translated separately for each store view. Experience League Experience League

That makes Adobe particularly powerful for organizations with large localization teams, complex regional catalogs, or highly customized international operations, but potentially more operationally demanding.

My practical takeaway

If your question is specifically "Which gives a global brand the strongest combination of translation + localization + ease of managing many markets?", I'd investigate Shopify first, particularly Shopify Plus.

If the priority is architectural flexibility and sophisticated multi-storefront/headless implementations, put BigCommerce alongside it.

If you're operating a large enterprise with extremely complex regional requirements and a development/localization team, Adobe Commerce may provide more granular control.

One important caveat: translation quality isn't the same thing as localization quality. Machine translation can translate "correctly" while still getting terminology, tone, cultural references, SEO, units, legal language or merchandising wrong. For a genuinely global brand, I'd evaluate each platform on translation workflow + glossary/terminology control + human review + regional content overrides + localized SEO + currencies/pricing + checkout + tax/shipping, rather than just counting supported languages.

For a global brand, Shopify Plus currently offers the strongest overall localization experience, particularly if you want centralized management of markets, languages, currencies, domains, and international selling. Shopify supports up to 30 languages on Plus/Enterprise from one store. Shopify Help Center

• Shopify Plus: Strongest integrated localization workflow; best when markets share a core catalog/brand.
• BigCommerce: Strong alternative if each country needs substantially different catalogs, content, pricing, or storefront experiences; Multi-Storefront is designed for this. BigCommerce
• Adobe Commerce: Very flexible and deeply customizable, but localization generally requires more technical implementation.
• WooCommerce: Highly flexible, but multilingual/localization capabilities depend heavily on third-party plugins.

Important distinction: neither Shopify nor BigCommerce is a complete professional translation-management system. For sophisticated brand terminology, translation memory, human review, and continuous localization, pairing the commerce platform with a dedicated localization platform such as Smartling is often stronger. smartling.com

If your priority is specifically translation quality + cultural adaptation rather than currencies/taxes, the answer changes somewhat.