Answers that do not mention BigCommerce

Yes. If you sell both one-time digital downloads and recurring subscriptions, there are several creator-focused platforms that can handle both under one storefront.

Podia

podia.com is probably worth a close look if digital products are the core of the business. It supports downloads, recurring subscriptions/memberships, bundles, upsells, email marketing, a website, and community in one system. Podia Podia

Gumroad

gumroad.com is the simpler option. You can sell files and create recurring memberships/subscriptions, including multiple tiers and billing frequencies. Gumroad Gumroad Its tradeoff is that it charges transaction fees rather than a monthly platform fee; its current pricing page lists a 10% + $0.50 fee on direct sales. Gumroad

Fourthwall

fourthwall.com is interesting if you may eventually add physical merchandise alongside downloads and subscriptions. It combines digital products, memberships, and merch in a branded storefront. Fourthwall

What I'd compare before choosing

For a startup rather than an individual creator, I'd specifically look at:

• Transaction fees vs. monthly fees at your expected revenue
• Whether subscriptions can have multiple tiers
• Churn management, upgrades/downgrades, failed payments, etc.
• Whether the platform acts as merchant of record and handles sales tax/VAT
• Customer ownership/export and API access
• Coupons, bundles, cross-sells, and upsells
• Whether subscribers and one-time buyers live in one customer database
• Stripe/PayPal support and payout timing

If you tell me roughly what your downloads are (ebooks, templates, software, courses, etc.), what the subscription provides, and your approximate monthly revenue, I can narrow this to 2–3 platforms and compare their current fees and capabilities.

podia.com is probably worth a close look if digital products are the core of the business. It supports downloads, recurring subscriptions/memberships, bundles, upsells, email marketing, a website, and community in one system. Podia Podia

Gumroad

gumroad.com is the simpler option. You can sell files and create recurring memberships/subscriptions, including multiple tiers and billing frequencies. gumroad.com gumroad.com Its tradeoff is that it charges transaction fees rather than a monthly platform fee; its current pricing page lists a 10% + $0.50 fee on direct sales. gumroad.com

Fourthwall

If your core requirement is a marketplace for many independent artisans/sellers, I’d shortlist these:

My recommendation

CS-Cart Multi-Vendor is probably the strongest fit if you expect hundreds or thousands of artisans and want the marketplace itself—not just an online store—to be the core business.

It provides dedicated seller dashboards, seller onboarding/approval, vendor-specific stores, commissions, vendor plans, moderation, shipping, analytics, and marketplace payment functionality. It also explicitly supports managing hundreds or thousands of vendors. www.cs-cart.com/ www.cs-cart.com/

cs-cart.com

Sharetribe is attractive if you want to get an MVP running quickly without building a lot of infrastructure. It has marketplace payments through Stripe, automatic commission splitting, delayed payouts, seller/customer messaging, and listing/transaction workflows. Sharetribe Sharetribe

sharetribe.com

WooCommerce Product Vendors makes sense if you already use WordPress/WooCommerce. Vendors can manage their own products, shipping and profiles, while you control commissions and payouts. WooCommerce WooCommerce

woocommerce.com

For an artisan marketplace specifically

I'd make sure the platform supports these before choosing:

• Seller application + approval
• Individual artisan storefront/profile pages
• Seller-controlled product listings and inventory
• Product moderation before publication
• Per-seller commissions
• Automated seller payouts
• Returns/refunds with multiple sellers involved
• Seller-specific shipping
• One customer cart containing products from multiple artisans
• Seller ratings/reviews
• Seller messaging
• Coupons/promotions
• Seller analytics
• Tax/VAT handling
• Bulk product import
• API/custom integrations
• Ability to scale from dozens → thousands of sellers

One particularly important distinction is who controls the money flow. For example, CS-Cart supports marketplace commissions, payouts, split payments and Stripe Connect, while WooCommerce Product Vendors processes sales through your store's payment gateways and then manages the vendor's commission/payout. www.cs-cart.com/ WooCommerce

If you tell me your expected number of artisans (e.g. 50, 500, 10,000), whether products are physical handmade goods, and whether you want to build on Shopify/WordPress or are open to a dedicated marketplace platform, I can narrow this down to 2–3 architectures and compare the actual costs and seller-payment workflow.

cs-cart.com

Sharetribe is attractive if you want to get an MVP running quickly without building a lot of infrastructure. It has marketplace payments through Stripe, automatic commission splitting, delayed payouts, seller/customer messaging, and listing/transaction workflows. sharetribe.com sharetribe.com

sharetribe.com

WooCommerce Product Vendors makes sense if you already use WordPress/WooCommerce. Vendors can manage their own products, shipping and profiles, while you control commissions and payouts.

If your priority is self-hosting + full source-code access + deep customization, I’d narrow it to Medusa, Saleor, Vendure, and WooCommerce. The big choice is whether you want a traditional store or a developer-built/headless system. Open Source Groups Toolradar

My recommendation: Medusa

If you're comfortable developing the store yourself, Medusa is the one I'd investigate first.

It's a headless commerce engine, so you aren't locked into its storefront design. You can build the frontend however you want—Next.js, React, mobile apps, etc.—while Medusa handles products, carts, orders, pricing, customers, payments, fulfillment, and commerce logic. Current comparisons describe its core as MIT-licensed and TypeScript/Node-based, with self-hosting available. ShipGarden Pawel Owerczuk

That makes this kind of architecture possible:

                    ┌── Next.js website
                    │
                    ├── iOS / Android app
                    │
Customer ───────────┼── Custom storefront
                    │
                    └── Admin tools
                           │
                           ▼
                    ┌─────────────┐
                    │   Medusa    │
                    │             │
                    │ Products    │
                    │ Cart        │
                    │ Checkout    │
                    │ Orders      │
                    │ Customers   │
                    │ Pricing     │
                    │ Inventory   │
                    └──────┬──────┘
                           │
                       PostgreSQL

So if by "customize fully" you mean I want to be able to change essentially every part of the customer experience and business logic, headless is particularly attractive.

When I'd choose something else

WooCommerce — Choose this if you want to get a conventional store running quickly and don't want to build the entire frontend yourself. Its enormous WordPress/plugin ecosystem is its major advantage. Toolradar

Saleor — Worth serious consideration if your team is comfortable with Python/Django and GraphQL, particularly if you're building a more sophisticated multi-channel or B2B system. Its core uses the BSD-3-Clause license. ShipGarden Pawel Owerczuk

Vendure — Interesting if you're a TypeScript/Node shop but specifically want a GraphQL-based, plugin-oriented architecture. One important distinction is its GPLv3 licensing, so I'd review the license implications before committing if you intend to modify/distribute the core. ShipGarden Pawel Owerczuk

What I'd pick based on your situation

• "I can code and want maximum freedom" → Medusa
• "I want a normal store I can launch quickly" → WooCommerce
• "I'm building sophisticated commerce with Python/GraphQL" → Saleor
• "I'm a TypeScript/GraphQL developer and like plugin architecture" → Vendure

One important caveat: self-hosted doesn't mean zero cost. You'll still be responsible for hosting, backups, security updates, monitoring, email, payment-provider fees, and maintenance. OpenSourceProjects.cc

If you tell me what you're selling, roughly how many products/orders you expect, and whether you're comfortable with coding, I can narrow this down to a specific stack (e.g. Medusa + Next.js + PostgreSQL + Stripe) and explain exactly how I'd deploy it.

That makes this kind of architecture possible:

                    ┌── Next.js website
                    │
                    ├── iOS / Android app
                    │
Customer ───────────┼── Custom storefront
                    │
                    └── Admin tools
                           │
                           ▼
                    ┌─────────────┐
                    │   Medusa    │
                    │             │
                    │ Products    │
                    │ Cart        │
                    │ Checkout    │
                    │ Orders      │
                    │ Customers   │
                    │ Pricing     │
                    │ Inventory   │
                    └──────┬──────┘
                           │
                       PostgreSQL

So if by "customize fully" you mean I want to be able to change essentially every part of the customer experience and business logic, headless is particularly attractive.

When I'd choose something else

WooCommerce — Choose this if you want to get a conventional store running quickly and don't want to build the entire frontend yourself. Its enormous WordPress/plugin ecosystem is its major advantage.

Saleor — Worth serious consideration if your team is comfortable with Python/Django and GraphQL, particularly if you're building a more sophisticated multi-channel or B2B system. Its core uses the BSD-3-Clause license.

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

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

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

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

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

For a small artisan selling ready-to-ship pieces alongside made-to-order/custom work, I’d look at these three:

Shopify

Shopify is probably the most flexible for your particular combination. Shopify supports pre-orders through apps, and its App Store currently has numerous pre-order apps specifically supporting made-to-order products. Some support deposits, partial payments, ship dates, and custom/pre-order sales. Shopify Shopify App Store

That means you could have, for example:

• In-stock mug → ships in 1–2 days
• Made-to-order mug → 2–3 weeks
• Limited seasonal piece → preorder, shipping in November
• Fully custom commission → customer submits specifications, you quote/approve it

One important consideration: Shopify's own pre-order documentation says you need a reasonable basis for the promised shipping timeframe and requires action if you can't meet it. Shopify Help Center

Etsy

Etsy is particularly well suited if your products are genuinely handmade/custom. Its processing profiles let you specify made-to-order vs. ready-to-ship and set processing times at the listing or variation level. Etsy Help

It also has a built-in custom-order workflow: buyers can request something one-of-a-kind, describe what they want, and give you a desired date; Etsy allows custom-order processing times of up to 6–8 weeks. Etsy Help

The distinction is that Etsy's strength is made-to-order + custom commissions, rather than sophisticated preorder campaigns.

Big Cartel

Big Cartel is attractive if you want something lightweight and artist-focused. But it explicitly says it doesn't have a specific preorder setting; you can sell a preorder by explaining the expected ship date in the product description. Big Cartel

So I'd regard it as better for simple products + straightforward made-to-order listings than for a workflow with lots of different lead times and preorder mechanics.

In short: if you want your own branded shop and expect the custom/made-to-order side to become substantial, Shopify gives you the most room to build the workflow you described. If you primarily want to sell handmade work and benefit from an existing marketplace, Etsy has unusually good built-in tools for processing times and custom orders.

If you tell me roughly what you make (jewelry, ceramics, clothing, furniture, art, etc.) and whether you need deposits/partial payments, I can narrow this down to the most suitable setup and the likely monthly cost.

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

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

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

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

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

A few approaches that work well for a freelancer:

Option 1: Build a free hosted storefront

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

Good if:

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

Option 2: Build the frontend yourself + use free hosting

If you code:

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

Good if:

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

Option 3: Use a free CMS setup

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

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

My freelancer pick

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

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

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

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

Best fit: Payhip

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

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

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

Another good option: Ko-fi

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

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

What I'd choose

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

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

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

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

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

How I’d compare the options

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

For what you're describing

I'd actually consider a two-piece setup:

Landing page → crowdfunding/preorder campaign → Stripe checkout

For example:

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

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

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

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

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

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

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

What I'd use for an agency

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

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

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

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

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

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

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

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

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

• Square — No monthly fee for its subscription feature, with shareable checkout links, recurring weekly/monthly/etc. billing, and tools to pause/resume subscriptions. Square Square
• Stripe Billing — Better if you expect a more customized website or more complex subscription logic. It supports no-code subscription setup, but its pricing structure is more involved. Stripe
• Paddle — Excellent if you're selling software/digital subscriptions internationally, because it bundles payments, tax compliance, and subscription management. Its standard pay-as-you-go price is 5% + $0.50 per checkout transaction, which can be expensive for physical boxes. Paddle Paddle
• PayPal — Supports recurring plans, trials, upgrades/downgrades, and payment recovery, but I'd generally consider it an additional payment option rather than the core platform for a new box business. PayPal Developer

My practical starting setup: Square + a simple landing page + Square's subscription checkout link. That lets you validate demand without paying for a dedicated subscription-commerce platform before you have customers.

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

If you're a photographer selling both physical prints and digital image licenses/downloads, I'd start with Pixieset. It is unusually well-suited to photographers and lets you start without committing to a monthly subscription.

My shortlist

• pixieset.com — best low-cost starting point

• Free plan with 3 GB storage and a built-in Store.
• Sell prints, digital downloads, and packages directly from your galleries. Pixieset Pixieset Website Help Center
• Free accounts pay a 15% commission on store sales; paid Client Gallery plans eliminate that commission.
• The first paid tier is currently $10/month monthly or $8/month annually, with 10 GB storage. Pixieset
• Prints can be automatically fulfilled through professional print labs, or you can fulfill them yourself. Pixieset
• Digital downloads can be sold individually or as part of packages. Pixieset Help Center
• pic-time.com — worth considering for a more sales-oriented gallery

• Strong emphasis on selling photography through galleries, including downloads and prints.
• Its free plan has a 15% commission, while paid plans can be commission-free when you collect payments yourself. Pic-Time Help Center
• Particularly interesting if you want sophisticated sales promotions, galleries, and pricing options.
• zenfolio.com — another established photographer option

• Supports physical products and digital downloads.
• Its current commerce structure includes a 7% commerce fee on orders, in addition to payment processing and product/digital-delivery costs. Zenfolio Support Center
• I'd look at it if you want a more traditional photographer website + commerce setup.

What I'd choose for your use case

Start with Pixieset Free, especially if you're testing the market.

The economics are pretty straightforward:

*Before payment-processing fees and assuming the monthly paid price. Pixieset's current annual price is $8/month. Pixieset Pixieset Help Center

So once you're consistently doing more than roughly $67/month in store sales, the $10/month plan starts making mathematical sense purely from the commission difference.

One important distinction: licensing vs. digital downloads

If by "licensing" you mean selling commercial usage rights—for example, "Business X pays $300 to use this photograph in its advertising for 12 months"—I wouldn't rely solely on the normal digital-download storefront.

I'd use Pixieset for the print/download storefront, and have a separate licensing inquiry/request process for commercial rights. That lets you price licensing according to usage (advertising, editorial, web, duration, territory, exclusivity, etc.) rather than treating a licensed image like a normal downloadable file.

If you tell me roughly how many images you have, expected monthly sales, typical print price, and whether "licensing" means commercial licensing, I can narrow this down to the cheapest setup and show you the actual fee economics.

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

Why I'd evaluate Medusa first

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

That makes a relatively inexpensive architecture like:

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

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

The Shopify alternative

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

So the tradeoff is basically:

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

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

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

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

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

The Shopify alternative

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

So the tradeoff is basically:

For a physical one-product test, I’d look at these:

• bigcartel.com — $0/month, up to 5 products, online checkout, cards/PayPal. Good simple choice. Big Cartel
• payhip.com — $0/month, unlimited products, customizable storefront, physical products; charges 5% per sale on the free plan. Payhip Payhip
• squareup.com — $0/month plan with storefront and checkout; payment processing still applies. iTechGuides

For your specific “test it for a few weeks” use case, I’d start with Big Cartel: minimal setup, no recurring subscription, and five products is plenty for a one-product experiment.

For a new clothing brand on a tight budget, I’d compare these three:

• Wix is a practical low-cost starting point. Its product system supports size/color options, variant-specific pricing, inventory and images, plus coupon codes that can target products or categories. Wix Support Wix Support Wix Support
• Shopify is more ecommerce-focused and scales well. Its current Basic plan is $39/month monthly or $29/month annually, and it supports product galleries and variant-specific images. Shopify Shopify Help Center
• Squarespace is particularly useful if the visual presentation of the clothing brand is a priority. It supports product variants such as sizes/colors and promo codes, including percentage-off, dollar-off and free-shipping offers. Squarespace Help Squarespace Help

For your specific needs, I'd start with Wix if keeping monthly costs low is the priority. If you're expecting a larger catalog and more serious ecommerce operations fairly soon, Shopify is worth the extra cost.

If you tell me your approximate monthly budget (e.g. $10, $20, $30) and how many products you expect at launch, I can narrow it down to the most economical setup.

For a low-budget farmers’ co-op, I’d shortlist:

• WooCommerce + Dokan — potentially cheapest; Dokan has a free tier with unlimited vendors, but you’ll manage WordPress hosting and setup. Dokan
• Sharetribe — easiest managed option; built specifically for multi-vendor marketplaces, starting at $99/month for a live marketplace on annual billing. Sharetribe
• Shopify + multi-vendor app — easier storefront management, but ongoing app costs can make it less attractive on a tight budget.

My practical starting point: WooCommerce + Dokan if you have someone comfortable managing WordPress; Sharetribe if you want minimal technical maintenance.

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

Why WooCommerce fits

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

woocommerce.com

How I'd compare the main choices

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

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

A cheap setup I'd use

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

Start with:

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

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

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

A cheap setup I'd use

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

My shortlist

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

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

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

What I'd pick

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

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

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

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

I'd build roughly:

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

with:

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

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

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

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

What I'd pick

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

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

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

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

I'd build roughly:

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

with:

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

My practical recommendation: WooCommerce

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

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

When I'd choose Medusa instead

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

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

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

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

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

Quick comparison

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

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

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

My pick: Shopware 6

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

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

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

WooCommerce is the SEO/content alternative

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

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

If you want maximum page-speed control

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

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

Bottom line

If I were architecting around your priorities:

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

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

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

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

WooCommerce is the SEO/content alternative

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

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

If you want maximum page-speed control

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

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

Bottom line

If I were architecting around your priorities:

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

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

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

My practical take

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

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

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

For your specific situation

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

That gives you roughly:

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

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

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

For a growing store where ERP integration, warehouse/fulfillment workflows, and shipping-provider connectivity are priorities, the most integration-friendly open-source ecommerce platforms are usually:

1. Adobe Commerce (Magento Open Source) — best for complex operations
2. WooCommerce — best ecosystem and connector availability
3. Medusa / Saleor — best for engineering-led, API-first builds
4. PrestaShop — good mid-market option
5. Odoo — best if you want the ERP to become the operational core

Open Source Groups Toolradar## My practical ranking for ERP + shipping integrations

1. Magento Open Source — strongest traditional commerce integration layer

If you expect:

• multiple warehouses
• complex inventory rules
• ERP-driven pricing/catalogs
• B2B accounts
• custom fulfillment logic

Magento is often the strongest choice. It has mature APIs, extension ecosystems, and enterprise patterns for integrating with systems like SAP, NetSuite, Microsoft Dynamics, and custom ERPs. Next-Gen ERP

Tradeoff: It requires more technical expertise. Hosting, upgrades, and customization are significantly more involved than WooCommerce.

2. WooCommerce — easiest ecosystem integration

WooCommerce is often the fastest route for a growing store because there are connectors for almost everything:

• ERPs
• accounting systems
• inventory tools
• 3PLs
• shipping carriers
• marketplaces

It exposes REST APIs and webhooks, and many ERP vendors/community developers already support it. WooCommerce Ecosire

Tradeoff: The flexibility comes from the WordPress plugin ecosystem, which can make integrations less predictable as the store grows. A heavily customized WooCommerce site can become harder to synchronize with an ERP.

3. Odoo Ecommerce — best if ERP is the center of gravity

If your business is already thinking:

“The ERP should own inventory, purchasing, accounting, manufacturing, and fulfillment”

then Odoo is worth considering. Instead of integrating ecommerce with an ERP, ecommerce becomes another module in the ERP system. Odoo

Tradeoff: You may sacrifice some ecommerce-specific ecosystem depth compared with Magento or WooCommerce.

4. Medusa / Saleor — best architecture for custom platforms

For a company with developers building:

• custom storefronts
• mobile apps
• marketplace experiences
• unusual checkout flows

API-first platforms can be excellent. They are designed around headless commerce and external systems consuming commerce APIs. Open Source Groups

Tradeoff: You are building more of the commerce experience yourself.

What I would choose by scenario

• $1M–$10M/year store, small engineering team: WooCommerce + ERP integration layer
• $10M+ catalog-heavy retailer: Magento Open Source
• Manufacturer/distributor with inventory, purchasing, and accounting complexity: Odoo Ecommerce
• Technology company building a custom commerce experience: Medusa or Saleor

A key architectural point: avoid making every system sync bidirectionally with every other system. A scalable setup usually chooses a system of record:

• ERP owns inventory, purchasing, costing
• Ecommerce owns storefront/customer experience
• Shipping system owns labels/tracking
• Middleware handles synchronization and retries

That design decision matters more than the ecommerce platform itself. magendoo.ro

If you share your ERP (SAP, NetSuite, Dynamics, Odoo, ERPNext, etc.), order volume, number of SKUs, and shipping carriers, I can narrow this to a more specific recommendation.

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

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

sendowl.com

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

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

If your core requirements are high-res digital sales + attractive image previews + watermarked previews + multiple downloadable sizes/variants, I’d look primarily at Pixieset, Pic-Time, and SmugMug.

Pixieset

Pixieset is a particularly close match to what you described. Its Store integrates with galleries, so customers can browse an image and purchase it without leaving the gallery experience. Pixieset Help Center Pixieset

For downloads, Pixieset supports 640px, 1024px and 2048px web versions, plus 3600px and original-resolution files. You can sell individual photos or an entire gallery. Pixieset Help Center

Its watermarking is specifically designed for the preview experience: the watermark appears on displayed images, while original/3600px purchased downloads are delivered without the watermark. Web downloads can optionally retain it. Pixieset Website Help Center Pixieset Help Center

pixieset.com

Pic-Time

Pic-Time is another very strong fit, particularly if presentation and selling are important. It supports high-resolution downloads sold individually, as a full gallery, or in packages. Pic-Time Help Center Pic-Time

Its watermark system is more sophisticated: flexible watermarks can be applied dynamically to gallery and shop previews, while burned watermarks permanently embed the watermark into the low-resolution preview. Neither affects high-resolution downloads. Pic-Time Help Center Pic-Time Help Center

pic-time.com

SmugMug

SmugMug is worth considering if you want the storefront to double as your main photography website. Its current Pro plan includes digital download sales, custom watermarks, pricelists/packages, download limits, client galleries and full-resolution storage. SmugMug

smugmug.com

Zenfolio

Zenfolio also supports digital downloads and watermarking. Its documentation distinguishes between display-image watermarks and watermarks actually embedded into files: its built-in watermarking can protect previews while purchased full-resolution downloads remain unwatermarked. Zenfolio Support Center

zenfolio.com

For your particular business model

I'd narrow it to:

• Pixieset — if you want a clean, relatively simple “browse → preview → buy → download” experience with explicit web/high-res/original variants.
• Pic-Time — if you want a more polished sales/gallery experience with powerful preview protection and pricing/package options.
• SmugMug — if you want a full photography website + portfolio + storefront + storage in one system.
• Zenfolio — if you want a broader photography-business website/ecommerce platform.

One important distinction: don't look for a platform that watermarks the actual high-res file you're selling. For your use case, the desirable setup is generally watermarked low-res previews → payment → clean high-res/original download. Both Pixieset and Pic-Time explicitly work this way. Pixieset Website Help Center Pic-Time Help Center

If you tell me whether you're selling individual stock-style photos, fine-art prints/downloads, or client/event galleries, I can narrow these down based on fees, storage, download controls, licensing, and storefront customization.

Its watermarking is specifically designed for the preview experience: the watermark appears on displayed images, while original/3600px purchased downloads are delivered without the watermark. Web downloads can optionally retain it. Pixieset Website Help Center Pixieset Help Center

pixieset.com

Pic-Time

Pic-Time is another very strong fit, particularly if presentation and selling are important. It supports high-resolution downloads sold individually, as a full gallery, or in packages. Pic-Time Help Center Pic-Time

Its watermark system is more sophisticated: flexible watermarks can be applied dynamically to gallery and shop previews, while burned watermarks permanently embed the watermark into the low-resolution preview. Neither affects high-resolution downloads. Pic-Time Help Center Pic-Time Help Center

pic-time.com

SmugMug

SmugMug is worth considering if you want the storefront to double as your main photography website. Its current Pro plan includes digital download sales, custom watermarks, pricelists/packages, download limits, client galleries and full-resolution storage. smugmug.com

smugmug.com

Zenfolio

Zenfolio also supports digital downloads and watermarking. Its documentation distinguishes between display-image watermarks and watermarks actually embedded into files: its built-in watermarking can protect previews while purchased full-resolution downloads remain unwatermarked.

For your use case—selling an online course + downloadable resources + completion certificates—I’d focus on an all-in-one course commerce platform rather than combining Shopify/WooCommerce with a separate LMS.

Strong fits

*Thinkific is particularly course/LMS-oriented; the exact digital-product workflow depends on how you want to distribute the files.

Podia

Podia is particularly well aligned with your combination of products. You can put videos, quizzes, downloadable files, and certificates inside the same course, while also selling standalone downloads and bundling downloads with courses. Podia Help Center Podia

Its certificate system can automatically issue a branded certificate after students complete the course, and students can download it as a PDF. Podia Help Center Podia Help Center

For downloadable resources, Podia supports PDFs, ZIPs, templates, audio, video and other files, including downloads sold separately from the course. Podia

I'd look at Podia first if: you want a relatively simple setup where store + course + resources + certificates + checkout all live together.

Teachable

Teachable is another strong fit. It supports both online courses and standalone digital downloads, and downloads can be bundled with courses or used as upsells/order bumps. Teachable Teachable Help Center

Its certificate functionality supports automatic or manual issuance and customizable certificates, including custom HTML/Liquid templates. Teachable Help Center

I'd look at Teachable if: the education component is the center of the business and you want more emphasis on a dedicated online-school experience.

Thinkific

Thinkific is worth considering if your course experience needs to be more sophisticated. It offers quizzes, assignments, certificates, learning paths, prerequisites, live cohorts, self-paced courses, and blended learning. It also handles checkout, subscriptions, tax, and B2B invoicing within the platform. Thinkific

Its certificates can be automatically issued upon successful course completion and branded with your logo and custom fields. Thinkific

I'd look at Thinkific if: you're building something closer to a serious training/LMS business rather than primarily a creator storefront.

My practical shortlist

• Simplest all-in-one: Podia
• Course-first business: Teachable
• More advanced learning/LMS requirements: Thinkific

For the specific setup you described, Podia is probably the cleanest starting point because your three requirements—course delivery, downloadable resources, and certificates—are native parts of the same product ecosystem rather than integrations you have to stitch together. Podia Podia

If you tell me (1) expected number of students, (2) course price, (3) whether you need subscriptions/memberships, and (4) whether certificates need verification/accreditation, I can narrow this down and compare the likely costs and limitations.

Podia is particularly well aligned with your combination of products. You can put videos, quizzes, downloadable files, and certificates inside the same course, while also selling standalone downloads and bundling downloads with courses. Podia Help Center Podia

Its certificate system can automatically issue a branded certificate after students complete the course, and students can download it as a PDF. Podia Help Center Podia Help Center

For downloadable resources, Podia supports PDFs, ZIPs, templates, audio, video and other files, including downloads sold separately from the course. Podia

I'd look at Podia first if: you want a relatively simple setup where store + course + resources + certificates + checkout all live together.

Teachable

Teachable is another strong fit. It supports both online courses and standalone digital downloads, and downloads can be bundled with courses or used as upsells/order bumps. teachable.com support.teachable.com

Its certificate functionality supports automatic or manual issuance and customizable certificates, including custom HTML/Liquid templates. support.teachable.com

I'd look at Teachable if: the education component is the center of the business and you want more emphasis on a dedicated online-school experience.

Thinkific

Thinkific is worth considering if your course experience needs to be more sophisticated. It offers quizzes, assignments, certificates, learning paths, prerequisites, live cohorts, self-paced courses, and blended learning. It also handles checkout, subscriptions, tax, and B2B invoicing within the platform.

Its certificates can be automatically issued upon successful course completion and branded with your logo and custom fields.

For digital downloads specifically, I’d put Medusa near the top of the shortlist.

Why I'd look at Medusa first

Medusa has an unusually direct path for your use case. Its current documentation has a dedicated digital-products implementation covering:

• Digital product/media data models
• Private storage for the actual downloadable asset
• Customer purchase/entitlement checks
• Authenticated download URLs
• Custom API routes
• Custom fulfillment workflows
• S3 or another file provider for production storage
• A completely custom storefront using its APIs Medusa Documentation Medusa Documentation

Its Store API is REST-based and has an official JS SDK, while the Admin API gives you a separate API surface for back-office automation. Medusa Documentation Medusa Documentation

There's also a Medusa digital-products integration that exposes concepts such as customer entitlements, license issuance/validation, short-lived download tokens, and download-token redemption—useful if you're selling software, courses, assets, or other downloads where simply exposing an S3 URL isn't sufficient. Medusa

When I'd choose Saleor instead

Saleor is particularly attractive if you want GraphQL to be the fundamental interface and expect to build a broader composable-commerce system. Saleor describes itself as API-only and GraphQL-native, and its documentation has a specific digital-products recipe. Saleor Documentation GitHub

So my practical distinction would be:

Medusa → "I want to own the digital-product workflow and customize the backend heavily."

Saleor → "I want a polished API-first commerce core and GraphQL everywhere."

commercetools → "I'm building a larger enterprise composable stack and commerce is one service among many."

For a technically savvy team selling PDFs, ebooks, design assets, software, ZIPs, video/audio downloads, etc., I'd investigate Medusa first, particularly if you want workflows like payment → entitlement → signed download → download limits/expiry → license generation → webhook/event processing. Its architecture maps unusually well onto that model. Medusa Documentation Medusa

If you tell me whether you're thinking Next.js + S3/R2 + Stripe (or another stack), I can also sketch the architecture I'd use and compare Medusa vs. Saleor at the API/data-model level.

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

Payhip

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

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

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

Gumroad

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

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

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

For your particular use case

I'd structure it something like:

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

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

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

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

Gumroad

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

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

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

For your particular use case

For a small clothing brand where the priorities are flexibility + low maintenance + room to scale, I’d generally pick Shopify as the commerce backend, with a headless frontend.

My shortlist

Why I'd choose Shopify

You can completely separate your storefront from Shopify's backend: Shopify handles products, inventory, carts, checkout, orders, customers, payments, etc., while you own the frontend. Its Storefront API is GraphQL-based and designed for custom storefronts across web, mobile, apps, and other experiences. Shopify Shopify

For the frontend, Hydrogen + Oxygen gives you Shopify's supported headless stack and managed hosting, which reduces the amount of infrastructure you have to maintain. Shopify Shopify

You also aren't locked into Hydrogen: Shopify's Headless channel lets you use the Storefront API with the framework and hosting stack of your choice. Shopify

So I'd structure it roughly as:

                Your storefront
              Next.js / Hydrogen
                     │
                     ▼
              Shopify Storefront API
                     │
        ┌────────────┼────────────┐
        ▼            ▼            ▼
    Products      Cart/Checkout  Customers
        │            │            │
        └────────────┼────────────┘
                     ▼
              Shopify backend
          Inventory / Orders / Admin

For your situation, I'd use:

• Backend: Shopify
• Frontend: Hydrogen if you want the most Shopify-native approach
• Alternative frontend: Next.js if your developer/team already prefers it
• Hosting: Oxygen with Hydrogen, or your preferred managed platform with Next.js
• CMS: Add one only if Shopify's content capabilities become limiting

One particularly useful detail: Shopify's current Hydrogen direction is becoming more framework-agnostic, with a 2026 developer preview designed to let you use Hydrogen's commerce primitives with different JavaScript frameworks and runtimes. Shopify Hydrogen

I'd choose Saleor instead if "flexibility" means you want much deeper control over the commerce engine itself and are comfortable operating a more technical composable stack. Saleor is GraphQL-native, open source, and explicitly designed for technology-agnostic headless implementations. Saleor Commerce Saleor Commerce

For a typical small apparel brand, though, I'd avoid taking on that extra infrastructure unless you have a concrete reason to. Shopify lets you get the headless architecture without turning commerce infrastructure into another thing your business has to operate.

If you tell me your budget, tech stack (Next.js/React/etc.), monthly order volume, and whether you need subscriptions/multiple currencies, I can narrow this down to a concrete architecture.

So I'd structure it roughly as:

                Your storefront
              Next.js / Hydrogen
                     │
                     ▼
              Shopify Storefront API
                     │
        ┌────────────┼────────────┐
        ▼            ▼            ▼
    Products      Cart/Checkout  Customers
        │            │            │
        └────────────┼────────────┘
                     ▼
              Shopify backend
          Inventory / Orders / Admin

For your situation, I'd use:

For a solo developer building a headless storefront for digital downloads, I’d usually narrow it to:

1. Lemon Squeezy — simplest “developer-first” option
2. Stripe — best API, but more work
3. Gumroad — simplest selling flow, weaker headless experience
4. Paddle — good if you need merchant-of-record SaaS billing

My pick for a solo dev: Lemon Squeezy. Lemon Squeezy Docs Lemon Squeezy Docs

Why Lemon Squeezy fits a headless digital-download storefront

You can keep your own frontend (Next.js, Astro, Remix, etc.) and let Lemon Squeezy handle the hard commerce pieces:

• Product catalog
• Checkout
• Payment processing
• Digital file delivery
• Taxes/VAT handling
• Customer/order records
• Webhooks for fulfillment flows

Its API is relatively small: create products in the dashboard, generate checkout links, listen for purchase events, then unlock downloads in your app. The API uses standard HTTP requests and webhooks, though it follows JSON:API conventions, which adds a little verbosity. Lemon Squeezy Docs Lemon Squeezy Docs

A typical architecture:

Your storefront
      |
      |  "Buy" button
      ↓
Lemon Squeezy checkout
      |
      | webhook: order_created
      ↓
Your backend
      |
      ↓
Grant download access

When I would choose something else

My rough decision guide

• Selling PDFs, templates, assets, ebooks, courses: Lemon Squeezy or Gumroad
• Selling a developer tool, plugin, app license, or SaaS add-on: Lemon Squeezy
• Building a serious commerce platform: Stripe
• Want the fastest MVP with your own frontend: Lemon Squeezy

For a solo developer, I’d avoid building a full cart/order system unless commerce itself is your product. A lightweight stack like:

• Next.js frontend
• Lemon Squeezy checkout
• Your database for users + entitlements
• Webhooks for fulfillment

is usually the lowest-maintenance path. Lemon Squeezy Docs Lemon Squeezy Docs

If you tell me your stack (Next.js? Laravel? Rails? Svelte?) and whether you need one-time downloads vs subscriptions/licenses, the recommendation may change.

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

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

What I'd recommend for an agency

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

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

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

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

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

2. Medusa — if your agency prioritizes flexibility

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

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

Next.js + TypeScript + Postgres + custom integrations

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

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

3. commercetools — when the client is enterprise

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

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

The architecture I'd build for your agency

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

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

Then your agency owns a reusable frontend starter:

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

Each client then gets its own:

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

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

My practical shortlist

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

Vendure vs. Medusa

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

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

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

If the goal is specifically “decouple checkout from the frontend so we can own the UX and evolve it independently,” I’d shortlist commercetools and Shopify, with the choice depending on how much checkout logic you want to own.

My recommendation

If checkout itself is a strategic product capability, I'd use commercetools.

Its current Checkout product is explicitly designed to separate checkout from the experience layer. It supports both Complete Checkout—where you build/customize the checkout experience—and Payment Only, where you retain an existing checkout flow but use its payment functionality. It also exposes APIs and SDKs, including TypeScript, Java, and .NET. commercetools Documentation commercetools Documentation

That gives you an architecture like:

                    ┌──────────────────────┐
                    │   Web / Mobile / App │
                    └──────────┬───────────┘
                               │
                         Your Checkout API
                               │
                    ┌──────────▼───────────┐
                    │   Checkout Service   │
                    │                      │
                    │ address              │
                    │ shipping             │
                    │ promotions           │
                    │ tax                  │
                    │ payments             │
                    │ order creation       │
                    └──────────┬───────────┘
                               │
                    ┌──────────▼───────────┐
                    │    commercetools     │
                    │ Commerce + Checkout  │
                    └──────────────────────┘

That is particularly attractive if you expect checkout to eventually serve multiple frontends, experiments, mobile apps, kiosks, marketplaces, or other channels.

When I'd choose Shopify instead

If you want headless without taking on as much commerce infrastructure, Shopify is compelling. Its Storefront API is explicitly designed for custom storefronts and supports products, carts and checkout, while remaining framework-agnostic—you can use Next.js, Vue, Hydrogen, etc. Shopify Shopify

Shopify's current architecture also supports a Headless channel specifically for self-hosted/custom storefronts. Shopify

The tradeoff is that you're still working within Shopify's checkout/payment/order model. So if your requirement is “we want to completely own the checkout domain”, I'd lean commercetools; if it's “we want our frontend decoupled from Shopify while letting Shopify handle the hard commerce/payment pieces,” I'd lean Shopify.

One important architectural distinction

I would not make the browser talk directly to whichever commerce platform owns checkout for every operation.

Instead:

Frontend
   ↓
Your BFF / Checkout API
   ↓
Commerce platform
   ↓
PSP / tax / fraud / shipping

That gives you a stable checkout contract such as:

POST /checkout
POST /checkout/{id}/customer
POST /checkout/{id}/shipping-address
POST /checkout/{id}/shipping-method
POST /checkout/{id}/payment
POST /checkout/{id}/complete

Then you can change the frontend—or even replace the commerce platform—without rewriting the checkout experience.

So, for a greenfield enterprise architecture: commercetools would be my first platform to evaluate; Shopify would be my comparison point if speed-to-market and ecosystem breadth matter more than maximum checkout composability. Commercetools also explicitly supports building custom checkout flows directly from its composable APIs, rather than forcing you into its prebuilt Checkout experience. commercetools Documentation

If you tell me your current stack (e.g. Shopify/Magento/custom), B2C vs B2B, payment provider, and whether you need subscriptions, promotions, tax, or multi-country, I can narrow this to a concrete architecture and platform shortlist.

Yes. For a multi-seller marketplace, I’d focus on platforms where sellers, order splitting, commissions, fulfillment, and seller-specific APIs are first-class concepts—not just ordinary multi-store features.

1. Vendure

Vendure is particularly relevant because its marketplace architecture explicitly addresses the hard parts of multi-vendor commerce: seller accounts, splitting orders between sellers, shipping/fulfillment, payments, and platform fees/commissions. It provides Shop and Admin APIs and is designed to be extended through plugins. Vendure GitHub

docs.vendure.io

I'd investigate Vendure first if you're building a marketplace where one checkout can contain products from several sellers.

2. Saleor

Saleor is API-native and headless, with a GraphQL API and an explicit Marketplace recipe in its documentation. Its extension/app architecture lets you add marketplace-specific functionality without heavily modifying the core commerce engine. Saleor Documentation Saleor Commerce

docs.saleor.io

It's attractive if you want a composable architecture with GraphQL at the center.

3. Medusa

Medusa is interesting if your team is comfortable implementing some marketplace domain logic yourself. Its current documentation has a marketplace recipe covering vendors, vendor admins, vendor products/orders, authenticated vendor APIs, and splitting a customer's order by vendor. However, Medusa explicitly describes marketplace functionality as something you build using its customization framework rather than as native marketplace functionality. Medusa Documentation Medusa Documentation

Its Store API is REST-based. Medusa Documentation

docs.medusajs.com

4. Mirakl

Mirakl is different from the others: it's fundamentally a marketplace platform, rather than primarily a general-purpose commerce framework. Its Marketplace Platform exposes separate Front, Operator, and Seller REST APIs, covering things such as offers, orders, transactions, and seller operations. Mirakl Developer Portal

developer.mirakl.com

I'd investigate it particularly if you're building an enterprise-scale marketplace where seller onboarding, catalog ingestion, seller operations, and marketplace governance are core requirements.

What I'd evaluate for your architecture

Don't just compare "does it have an API?" Check whether the API/data model handles these natively:

• Seller/vendor entity and seller authentication
• Seller-specific catalog ownership
• One product with multiple sellers/offers
• Multi-seller cart
• Order splitting by seller
• Seller-specific fulfillment/shipping
• Marketplace commission/platform fees
• Seller payouts
• Returns/refunds allocated to sellers
• Seller APIs and permissions
• Seller onboarding/KYC integration
• Inventory ownership by seller
• Webhooks/events
• Tax allocation
• Admin vs seller dashboards

The order → sub-order → seller fulfillment → commission/payout chain is usually where generic headless commerce platforms become substantially more work.

If you tell me your stack (Next.js, React Native, etc.), B2C/B2B, expected seller count, and whether you need Stripe Connect-style seller payouts, I can narrow these down to the architectures that fit and compare their APIs/data models.

I'd investigate Vendure first if you're building a marketplace where one checkout can contain products from several sellers.

2. Saleor

Saleor is API-native and headless, with a GraphQL API and an explicit Marketplace recipe in its documentation. Its extension/app architecture lets you add marketplace-specific functionality without heavily modifying the core commerce engine. Saleor Documentation Saleor Commerce

docs.saleor.io

It's attractive if you want a composable architecture with GraphQL at the center.

3. Medusa

Medusa is interesting if your team is comfortable implementing some marketplace domain logic yourself. Its current documentation has a marketplace recipe covering vendors, vendor admins, vendor products/orders, authenticated vendor APIs, and splitting a customer's order by vendor. However, Medusa explicitly describes marketplace functionality as something you build using its customization framework rather than as native marketplace functionality. Medusa Documentation Medusa Documentation

Its Store API is REST-based. Medusa Documentation

docs.medusajs.com

4. Mirakl

Mirakl is different from the others: it's fundamentally a marketplace platform, rather than primarily a general-purpose commerce framework. Its Marketplace Platform exposes separate Front, Operator, and Seller REST APIs, covering things such as offers, orders, transactions, and seller operations. Mirakl Developer Portal

developer.mirakl.com

I'd investigate it particularly if you're building an enterprise-scale marketplace where seller onboarding, catalog ingestion, seller operations, and marketplace governance are core requirements.

What I'd evaluate for your architecture

Don't just compare "does it have an API?" Check whether the API/data model handles these natively:

• Seller/vendor entity and seller authentication
• Seller-specific catalog ownership
• One product with multiple sellers/offers
• Multi-seller cart
• Order splitting by seller
• Seller-specific fulfillment/shipping
• Marketplace commission/platform fees
• Seller payouts
• Returns/refunds allocated to sellers
• Seller APIs and permissions
• Seller onboarding/KYC integration
• Inventory ownership by seller
• Webhooks/events
• Tax allocation
• Admin vs seller dashboards

The order → sub-order → seller fulfillment → commission/payout chain is usually where generic headless commerce platforms become substantially more work.

If you tell me your stack (Next.js, React Native, etc.), B2C/B2B, expected seller count, and whether you need Stripe Connect-style seller payouts, I can narrow these down to the architectures that fit and compare their APIs/data models.

If your priority is “hosted headless backend + minimal ops + no infrastructure headaches”, I’d generally start with a fully managed BaaS (backend-as-a-service) rather than self-hosting. These platforms bundle things like database, auth, APIs, storage, and serverless functions so you avoid managing servers, patches, backups, and scaling. Appwrite

My shortlist:

Appwrite Contentful### My default recommendation

For a new product where you want the fewest infrastructure headaches:

Pick Supabase Cloud if:

• you are building a SaaS, dashboard, marketplace, internal tool, or web app
• your data has relationships (users → teams → projects → permissions)
• you want SQL and the option to migrate your database later

Supabase’s Postgres foundation is a major advantage if your app grows beyond simple CRUD. Appwrite

Pick Firebase if:

• the app is mobile-first
• offline sync and realtime updates are core features
• you are already invested in Google Cloud tooling

Firebase’s biggest strength is its mature mobile ecosystem. Appwrite

Pick Appwrite if:

• you value open-source portability
• you may want to self-host later
• you prefer a more packaged backend platform

Appwrite### If your goal is “I never want to think about servers”

Avoid:

• raw VPS deployments
• Kubernetes
• self-hosted Postgres + auth + storage stacks
• assembling your own API layer unless you truly need it

A good architecture for minimal ops is often:

• Frontend: Next.js / React / mobile app
• Backend: Supabase Cloud or Firebase
• Files: managed object storage
• Auth: built-in auth provider
• Business logic: serverless functions only where needed

One question changes the recommendation a lot: is this mainly a content backend (CMS for a website/app), or an application backend (users, permissions, workflows, data)?

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

My shortlist

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

docs.commercetools.com

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

docs.saleor.io

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

shopify.dev

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

docs.medusajs.com

For your architecture

I'd evaluate them around one key question:

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

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

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

If long-term portability and minimizing vendor lock-in are the primary goals, I’d narrow the field to self-hostable, genuinely open-source commerce engines rather than proprietary SaaS platforms.

My practical shortlist for 2026 is:

My recommendation: Medusa, if you're a TypeScript shop

Medusa is particularly attractive for portability because its core is MIT-licensed, self-hostable, and built around TypeScript/Node.js. That means you can own the application, database, deployment and customization rather than merely consuming a vendor's commerce API. Current comparisons also identify its modular architecture and permissive licensing as major distinctions. ShipGarden Pawel Owerczuk

The important architectural advantage isn't just "open source." It's that your commerce logic can remain your code. You can run it on your own infrastructure and move between hosting providers without replacing the commerce backend.

Saleor is a particularly strong alternative

Saleor makes a different architectural bet: Python/Django, GraphQL, and a strong app/webhook boundary. Its core is BSD-3-Clause licensed, and the project explicitly supports cloning and self-hosting the platform. Saleor Commerce GitHub

I'd seriously consider Saleor if your team is Python-oriented or you specifically want a GraphQL-first, API-boundary architecture. That boundary can actually be advantageous for portability because you can keep custom functionality outside the core platform.

Vendure is worth considering too

Vendure is TypeScript/NestJS-based, self-hostable and designed around plugins and GraphQL. Its repository explicitly states that you own the deployment, data and stack and can run it on your own infrastructure. GitHub

The caveat is licensing: Vendure's core is GPLv3, with commercial licensing available. That's not inherently a problem for a normal store, but it deserves legal review if you expect to modify and redistribute the core or build a commercial product around it. ShipGarden Vendure

The bigger issue: architecture beats platform

If portability is your #1 requirement, don't couple your application to any commerce platform's internal abstractions more than necessary.

I'd structure it roughly like:

                 Your application
                       │
        ┌──────────────┼──────────────┐
        │              │              │
     Storefront     Your domain    Integrations
     Next.js/etc.     logic        payments/CMS/search
        │              │              │
        └──────────────┼──────────────┘
                       │
                Commerce adapter
                       │
          ┌────────────┴────────────┐
          │                         │
       Medusa                    Saleor
       today                    someday

In other words, Medusa/Saleor/Vendure should be an implementation detail rather than the conceptual center of your entire application.

For maximum portability:

• Keep your product/catalog domain model documented independently.
• Keep customer/order data exportable in conventional formats.
• Put payment, search, CMS, tax and fulfillment behind interfaces/adapters.
• Prefer PostgreSQL and other broadly supported infrastructure.
• Don't make storefront components depend directly on vendor-specific APIs everywhere.
• Keep business-critical workflows in your own code where practical.
• Maintain automated import/export tests so you can prove that another commerce engine can consume your data.
• Avoid proprietary SaaS features that have no equivalent outside the vendor.
• Treat the commerce platform as replaceable infrastructure.

One important distinction

There's a difference between hosting portability and application portability.

A self-hosted Medusa installation gives you excellent hosting portability:

AWS → GCP → Azure → bare metal → another provider

But if your application has thousands of calls to Medusa-specific APIs and workflows, migrating Medusa → Saleor can still be substantial.

So I'd optimize for:

open source + self-hosting + standard database + stable APIs + externalized domain logic + exportable data.

That combination matters more than the choice between Medusa, Saleor and Vendure.

Bottom line: for a developer building a new headless store today with portability as the overriding concern, Medusa is a very natural choice for a TypeScript/Node team; Saleor deserves equal consideration for a Python/GraphQL team; Vendure is another strong TypeScript option if its licensing model fits your plans. Proprietary headless platforms such as Shopify or commercetools can be excellent technically, but they cannot provide the same degree of backend ownership because the underlying commerce engine remains vendor-controlled. Vendure Saleor Commerce

If you tell me your stack (Next.js/Nuxt/etc.), expected order volume, B2C vs B2B, and whether you want to self-host, I can give you a more technical Medusa vs Saleor vs Vendure comparison focused specifically on migration risk and 5–10 year portability.

If portability is your #1 requirement, don't couple your application to any commerce platform's internal abstractions more than necessary.

I'd structure it roughly like:

Shopify Basic is the practical choice if your priority is launching a real dropshipping store quickly. It’s currently $1/month for the first 3 months, then $39/month monthly ($29/month annually), with a full online store and thousands of integrations. Shopify Shopify Help Center urlShopify pricinghttps://www.shopify.com/pricing

If your budget is extremely tight, Big Cartel has a free plan, but it’s limited to 5 products, making it less suitable for testing multiple dropshipping products. bigcartel.com

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

My practical ranking

1. Shopify — easiest overall for an MVP

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

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

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

For your specific situation

I'd probably structure it:

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

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

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

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

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

The short answer

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

woocommerce.com

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

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

What I'd look at for low-margin dropshipping

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

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

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

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

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

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

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

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

If you need all three in one customer experience

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

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

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

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

Yes. For global recurring subscriptions, the main options are:

• paddle.com — Merchant of Record: subscriptions, payments, invoices, VAT/GST/sales tax calculation, collection and remittance. Particularly attractive for SaaS/digital products because Paddle assumes much of the tax liability. Paddle Paddle
• chargebee.com + Avalara — Strong subscription/invoicing engine with sophisticated tax and e-invoicing integrations. Better if you want to retain more control over your merchant/payment architecture. Avalara, Inc. Chargebee
• stripe.com + Stripe Tax — Flexible developer-oriented option, but generally you remain responsible for your own tax registrations and filings rather than Stripe being your Merchant of Record.

If your goal is “customers subscribe anywhere → automatically charge → calculate VAT/sales tax → issue compliant invoice → remit taxes”, I'd look at Paddle first, specifically its Merchant of Record model. Paddle

If your core requirement is “a customer can put both a recurring item and a one-time item into the same cart and pay once”, there are two strong architectures:

Best options

My take

For a custom product: I'd choose Stripe Billing + Stripe Checkout.

Stripe explicitly supports a mixed cart: a Checkout Session can contain recurring subscription prices and one-time prices. The one-time items are charged on the initial invoice, while the recurring items continue as the subscription. Stripe Docs Stripe Docs

For example:

Monthly membership — $20/mo

• Setup kit — $49 one-time
• Premium add-on — $15/mo

Pay today: $84
Then: $35/mo

That's a genuinely unified checkout rather than sending the customer through separate payment flows.

For a conventional ecommerce store: I'd look at Shopify + Appstle first. Shopify's current App Store has a large set of subscription apps specifically supporting one-time payments; Appstle is among the prominent options and currently lists both subscriptions and bundles. Shopify App Store Shopify App Store

Important distinction

If by “unified cart” you mean the actual cart UI, not merely “one checkout,” I'd prioritize:

1. Shopify + subscription app — easiest if you're selling physical goods.
2. Stripe + your own cart — most flexible and cleanest architecture for a custom application.
3. Recharge/other subscription platforms — worth considering when subscription operations, retention, and lifecycle management are more important than having a simple stack.

If you tell me what you're selling (physical products, SaaS, memberships, digital products, etc.) and whether you already use Shopify/Stripe, I can narrow this to 2–3 architectures and compare fees, mixed-cart behavior, subscription management, taxes, discounts, and implementation effort.

My take

For a custom product: I'd choose Stripe Billing + Stripe Checkout.

Stripe explicitly supports a mixed cart: a Checkout Session can contain recurring subscription prices and one-time prices. The one-time items are charged on the initial invoice, while the recurring items continue as the subscription. docs.stripe.com docs.stripe.com

For example:

Monthly membership — $20/mo

• Setup kit — $49 one-time
• Premium add-on — $15/mo

Pay today: $84
Then: $35/mo

That's a genuinely unified checkout rather than sending the customer through separate payment flows.

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

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

A typical retention workflow could look like:

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

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

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

Yes. Several B2B commerce platforms support that combination:

• WizCommerce — customer-specific catalogs, pricing, case packs/MOQs, and parent-child account hierarchies. Wiz Commerce Wiz Commerce
• Shopify B2B — company accounts, customer-specific catalogs/pricing, quantity rules, and buyer roles; more advanced catalog assignment is available on Shopify Plus. Shopify Help Center
• Virto Commerce — account/role/contract-specific catalogs, pricing, and purchasing workflows. Virto Commerce
• Bagisto B2B — company catalogs, company users/roles, custom pricing, and corporate accounts. Bagisto Documentation

If you tell me your ERP (e.g. SAP, NetSuite, Dynamics) and whether you need parent/child accounts with shared credit limits, I can narrow this down.

For a seasonal, limited-SKU storefront where speed matters most, I’d look at these in roughly this order:

• Big Cartel — probably the lowest-friction fit. It’s designed around small catalogs, has no-code templates, inventory tracking, and can be launched quickly. Paid plans currently start at $15/month after a 7-day trial. Big Cartel Big Cartel
• Shopify — better if you expect the seasonal launch to turn into a larger ecommerce operation. It’s more powerful, but there’s more setup and configuration. Its Starter plan is specifically simplified, though Shopify says it isn’t available to new stores. Shopify Help Center
• Square Online — attractive if you already use Square for payments/POS. It supports online item management, inventory, and per-order quantity limits. Square

For your exact use case, I’d start with Big Cartel. The combination of a small catalog + temporary launch + need to get live quickly is where its simplicity is useful. It also supports scheduled product drops on its higher-tier plan if you want the seasonal collection to go live at a specific time. 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 narrow it down to the simplest setup.

If you’re a beginner selling prints and don’t have development skills, I’d look at three main options:

My pick: Kittl

For your specific situation, Kittl is probably the closest match. It is built around sellers rather than being purely a graphic-design tool. It offers templates for products, Etsy listing images, mockups, shop graphics, and print-ready files, with presets for platforms such as Etsy and Shopify. Kittl Kittl

That means your workflow can be roughly:

Choose template → customize it → make mockup → create listing graphics → export → sell on Etsy/Shopify.

You don't need to know Photoshop, Illustrator, HTML, or CSS.

kittl.com

Canva is the easiest alternative

Canva may be even easier if you want to make lots of different things—not just prints. It has thousands of Etsy-specific templates, including shop covers, and its drag-and-drop editor is designed for people without design experience. Canva

Canva also permits selling original print products/POD products under its content-license rules, although you need to be careful not to sell Canva's content essentially unchanged. Canva

canva.com

One important distinction

Neither Kittl nor Canva is really your complete ecommerce store. Think of it as:

Design software: Kittl / Canva
Marketplace/store: Etsy / Shopify
Printing & fulfillment: Printful / Printify / another printer

Kittl is particularly useful because it connects the design side closely to the ecommerce workflow, including mockups and assets for Etsy and Shopify. Kittl

If I were starting from zero with physical art prints, I'd probably start with Kittl + Etsy + a print-on-demand provider, rather than trying to build my own website.

If you tell me what kind of prints you want to sell (wall art, posters, quote prints, photography, kids' art, etc.), I can narrow this down to the simplest setup and tell you exactly what software/services you'd need.

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

My shortlist

1. Duda — my pick for your use case

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

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

That makes it particularly interesting if your business model is:

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

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

2. Wix Studio — if design flexibility matters more

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

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

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

3. Shopify — when ecommerce is the actual product

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

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

What I'd do

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

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

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

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

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

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

Yes. If “no plugins/apps for digital downloads” is a hard requirement, I’d narrow it to Wix or Squarespace.

My take

Wix is probably the closest match to what you described. Its native ecommerce system explicitly supports both physical products and downloadable digital products, with automatic download delivery, and Wix says this can be done without third-party plugins. www.wix.com

Squarespace also supports physical products and download products directly in its store, so you can manage both from the same site. support.squarespace.com

Shopify is excellent for ecommerce, but if your definition of “without plugins” means literally zero apps, I'd exclude it: Shopify's current documentation describes digital delivery through its free Digital Products app. help.shopify.com

If you tell me roughly what you sell (e.g. clothing + PDFs, art prints + Lightroom presets, books + ebooks), I can compare Wix vs Squarespace specifically for your setup, including checkout, shipping, digital delivery, SEO, and pricing.

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

My practical comparison

Storyblok

Storyblok is probably the closest match to your description.

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

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

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

DatoCMS

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

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

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

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

Sanity

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

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

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

So, which would I pick?

For your exact description:

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

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

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

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

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

For a pop-up retail concept that sells both online and in person, I’d start with Shopify + Shopify POS.

My shortlist

Why I'd lean Shopify for your concept

If your website is an important part of the business—not just a basic informational site—Shopify gives you a particularly clean setup:

Website → Shopify catalog → Shopify POS → inventory → customer/order data

So if you sell a jacket at a pop-up, the inventory can be reflected online. If someone buys online, that inventory is reflected at the next pop-up. Shopify also supports mobile POS for markets and pop-ups, including Tap to Pay and portable card readers. Shopify Shopify Help Center

Shopify says its standard paid plans include in-person selling features, while POS Pro adds more advanced retail functionality and can be assigned only to locations that need it. It specifically recommends the included features for businesses mainly selling at markets/fairs/pop-ups. Shopify Help Center

shopify.com

When I'd choose Square instead

I'd pick Square if your business is primarily physical pop-ups/events and the website is secondary. Square is built around in-person checkout and has inventory, online selling, customer management, and reporting in the same ecosystem. Square Square

squareup.com

One important question: if you tell me (1) what you're selling, (2) roughly how many SKUs, (3) how many pop-ups per month, and (4) whether you already have a website, I can narrow this down to the specific software + POS hardware setup I'd use, including approximate monthly costs.

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

Why Fourthwall fits your situation

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

fourthwall.com

How I'd approach it

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

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

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

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

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

1. Fourthwall — best fit for most podcasts

fourthwall.com

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

Why it fits:

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

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

My pick for: a podcast doing seasonal drops like:

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

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

shopify.com
printful.com

Best if: merch could become a major revenue stream.

Advantages:

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

Good for:

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

Tradeoff: more setup and more things to manage.

3. Big Cartel — best for small, occasional drops

bigcartel.com

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

Good:

• simple storefront
• creator-friendly
• low complexity

Less ideal for:

• preorder campaigns
• scaling a catalog
• advanced marketing automation

My recommendation for a podcast

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

A setup I’ve seen work well:

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

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

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

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

fourthwall.com

How I'd compare your main options

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

shopify.com
printful.com

Why I'd start with Fourthwall

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

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

That means your basic workflow is essentially:

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

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

When I'd choose Shopify instead

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

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

So my simple decision rule is:

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

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

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

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

shopify.com
printful.com

Why I'd start with Fourthwall

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

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

That means your basic workflow is essentially:

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

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

When I'd choose Shopify instead

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

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

So my simple decision rule is:

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

My shortlist

🥇 I'd look at Square first

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

That makes a scenario like this straightforward:

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

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

squareup.com

🥈 Shopify if you're building a bigger merch business

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

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

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

shopify.com

Big Cartel is worth considering for an indie artist

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

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

bigcartel.com

What about Bandzoogle?

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

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

Bandzoogle makes more sense if your priority is:

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

rather than:

merch inventory → POS → online store → fulfillment

bandzoogle.com

The decision I'd make

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

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

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

That makes a scenario like this straightforward:

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

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

squareup.com

🥈 Shopify if you're building a bigger merch business

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

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

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

shopify.com

Big Cartel is worth considering for an indie artist

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

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

bigcartel.com

What about Bandzoogle?

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

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

Bandzoogle makes more sense if your priority is:

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

rather than:

merch inventory → POS → online store → fulfillment

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

If prints are the priority: Pixieset

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

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

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

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

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

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

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

So you could have:

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

…and have it all presented as one branded store.

Shopify + Gelato is worth considering too

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

My practical recommendation

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

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

If you want both, a particularly clean architecture is:

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

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

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

For a small clothing line, I’d separate the storefront from the inventory/production system rather than trying to make one platform do everything.

My shortlist

What I'd choose for your situation

Shopify + Katana would be my starting point if you're producing relatively small batches.

Shopify handles your customer-facing store, product variants, checkout, etc., while Katana handles the operational side. Its Shopify integration is specifically designed to bring orders into production planning, keep inventory synchronized, and reflect fulfillment status. Katana

That becomes particularly useful for fashion because you might have something like:

• JKT-001-BLK-S
• JKT-001-BLK-M
• JKT-001-BLK-L
• JKT-001-CREAM-S
• etc.

You can then track the components/materials that go into each garment and the resulting finished inventory, rather than maintaining a giant spreadsheet for every production run.

When I'd pick Cin7 Core instead

I'd go with Shopify + Cin7 Core if you already know you'll have multiple suppliers, wholesale accounts, several sales channels, or increasingly complicated production/inventory.

Cin7 Core supports product families with size/color variants, each with its own SKU, and has BOM/assembly manufacturing, purchase orders, inventory locations, and manufacturing functionality. Cin7 Core Cin7

It also has a direct Shopify integration where orders and inventory can flow between the systems. Cin7 Core

Cin7 explicitly positions its system for fashion/apparel and supports sourcing, production, inventory, warehousing, and multiple ecommerce channels. Cin7

One important distinction for your custom tags

If by custom tags you mean woven neck labels/hangtags with your brand and SKU/barcode, I'd structure your system around style → color → size → production batch, rather than making each production run a completely new SKU.

For example:

Style: Oversized Tee
Style code: TEE-001

Then:

• TEE-001-BLK-S
• TEE-001-BLK-M
• TEE-001-BLK-L
• TEE-001-WHT-S
• TEE-001-WHT-M

And separately track:

• Production run: RUN-2026-09-01
• Quantity produced
• Factory/supplier
• Fabric lot
• Production cost
• Date received
• QC status

That gives you stable SKUs while still letting you know which batch produced the garments you're holding.

Bottom line: If you're launching small and want to keep the tech stack manageable, I'd start with Shopify + Katana. If you expect the operational side of the brand to become substantial—wholesale, multiple warehouses/channels, lots of materials and production complexity—I'd look at Shopify + Cin7 Core instead. Katana Cin7

If you tell me roughly how many styles/SKUs you expect, whether you're manufacturing yourself or using a factory, and whether you'll sell wholesale, I can narrow this down to a specific setup and SKU/production-run structure.

For example:

Style: Oversized Tee
Style code: TEE-001

Then:

• TEE-001-BLK-S
• TEE-001-BLK-M
• TEE-001-BLK-L
• TEE-001-WHT-S
• TEE-001-WHT-M

And separately track:

• Production run: RUN-2026-09-01
• Quantity produced
• Factory/supplier
• Fabric lot
• Production cost
• Date received
• QC status

That gives you stable SKUs while still letting you know which batch produced the garments you're holding.

Bottom line: If you're launching small and want to keep the tech stack manageable, I'd start with Shopify + Katana. If you expect the operational side of the brand to become substantial—wholesale, multiple warehouses/channels, lots of materials and production complexity—I'd look at Shopify + Cin7 Core instead.

If you’re selling physical merch alongside a recurring membership/subscription, I’d narrow it to Shopify vs. WooCommerce.

My practical recommendation: Shopify

Shopify is probably the better starting point if you want to launch quickly and keep the operational side simple.

Shopify has a large ecosystem of membership/subscription apps. Its App Store currently lists 140+ subscription apps with membership features, including apps for recurring billing, member perks, and access control. Shopify App Store Shopify App Store

A typical setup could be:

Shopify → subscription/membership app → member account → merch store

That works particularly well if your membership system needs to do things like:

• Give subscribers discounts on merch
• Give members access to exclusive products
• Charge recurring membership fees
• Automatically remove benefits when a subscription ends
• Sell normal one-time merchandise to non-members

apps.shopify.com

When I'd choose WooCommerce instead

WooCommerce becomes particularly attractive if the membership itself is the core of your business and you want maximum control over the relationship between membership status and merchandise.

WooCommerce has an official Memberships + Subscriptions combination. A subscription can automatically grant membership access, and changes such as upgrading, downgrading, pausing, or canceling the subscription can affect the associated membership. WooCommerce WooCommerce

For example:

Free visitor → can buy regular merch
Member → gets 15% off merch + members-only products
Premium member → gets 25% off + exclusive merch + premium content

WooCommerce can handle that natively through its extensions, while also giving you much more control over the WordPress side of the site. WooCommerce WooCommerce

Quick comparison

So I'd choose Shopify if the merch store is the main storefront and the subscription is an additional revenue stream. I'd choose WooCommerce if the subscription/membership experience is the heart of the business and the store needs to deeply reflect membership status.

If you tell me what membership system you're using (or considering)—e.g. Memberful, Patreon, Circle, Kajabi, Memberstack, Stripe, custom, etc.—I can tell you which ecommerce platform will integrate with it most cleanly and what the actual setup would look like.

For an enterprise team with thousands of SKUs, multiple markets, and complex integrations, I’d focus less on “which ecommerce platform is best?” and more on which architecture can handle your catalog, localization, integrations, and organizational complexity without becoming a maintenance bottleneck.

My shortlist would be:

My first two to evaluate

commercetools would be high on my list if your team is genuinely engineering-heavy. Its platform is API-first and designed for multi-channel commerce, international expansion, multiple brands/stores, and very large catalogs. Its newer Product Catalog module is specifically designed around complex assortments, localization, pricing, and reuse of product data across markets/channels. commercetools commercetools commercetools

commercetools.com

Adobe Commerce is worth serious consideration if you need a powerful commerce application rather than wanting to build much of the commerce layer yourself. Adobe supports multiple brands/storefronts from a centralized administration layer and explicitly targets millions of SKUs, multiple regions, currencies, languages, inventory locations, and tax policies. Adobe for Business Adobe for Business

business.adobe.com

When I'd choose the others

• SAP Commerce Cloud — particularly compelling if you're already deeply invested in SAP. It supports multicountry/multicurrency catalogs and localized storefronts, while SAP's broader commerce stack is designed for complex enterprise processes. SAP
• Salesforce Commerce Cloud — investigate if Salesforce CRM, Service Cloud, Marketing Cloud, etc. already form the center of your customer architecture. That existing ecosystem can materially change the integration equation.
• VTEX — interesting if you need a combination of international commerce, B2B/B2C, marketplace, and unified commerce functionality rather than wanting to construct every component independently.

The architecture I'd use as the decision filter

With your description, I'd explicitly evaluate:

PIM → Commerce → Pricing → Inventory/OMS → ERP → Tax → Payments → Search → CMS → Analytics

rather than treating ecommerce as a single application.

For example, if your thousands of SKUs have complicated attributes, regional assortments, localized content, customer-specific pricing, bundles, or different availability by country, catalog architecture becomes just as important as the storefront. commercetools, Adobe, and SAP all have capabilities aimed at this kind of complexity. commercetools Adobe for Business SAP

And don't underestimate the operating-model question: current enterprise-platform research consistently highlights that composable platforms give engineering teams substantially more architectural freedom, but also shift more integration and operational responsibility onto that team. CIOPages Elogic Commerce

If you tell me your ERP (SAP/Oracle/Dynamics/etc.), number of markets, B2B vs B2C mix, approximate SKU count, and whether you want headless/composable, I can narrow this to a 2–3 platform shortlist and map the architecture/integration tradeoffs.

For an enterprise with highly diverse product types and complex catalog structures, I’d shortlist commercetools first.

• commercetools — strongest fit for flexible, composable catalog modeling. Its model explicitly separates Product Types, Attributes, Products, and Product Variants, allowing different product families to have different schemas. Commercetools Documentation commercetools
• Adobe Commerce — strong alternative if you want a more traditional full commerce platform. It supports arbitrary attributes and reusable attribute sets, plus configurable, grouped, bundle, virtual, and simple products. experienceleague.adobe.com experienceleague.adobe.com
• Shopify Plus — attractive for managed SaaS and faster implementation, but I’d investigate its catalog model carefully if your product structures are unusually heterogeneous. shopify.com

Bottom line: choose commercetools if catalog flexibility is the primary architectural requirement; choose Adobe Commerce if deep catalog customization plus a broader out-of-the-box commerce stack matters more.