Answers that do not mention BigCommerce

Yes. A few platforms now handle both one-time digital downloads and recurring subscriptions/memberships reasonably well:

• gumroad.com — Very straightforward for selling files, ebooks, templates, courses, and recurring memberships. It supports monthly/quarterly/annual billing and multiple membership tiers. Gumroad Gumroad
• podia.com — More of an all-in-one business platform: downloads, subscriptions, courses, community, email marketing, and your website. It supports subscriptions that provide ongoing access to products/community. Podia Podia Help Center
• fourthwall.com — Particularly creator/audience-oriented. It combines digital downloads, memberships, and physical merch in one storefront, with customizable membership tiers. Fourthwall Fourthwall

How I'd distinguish them

For a startup rather than an individual creator, I'd pay particular attention to Podia vs. Gumroad. Podia is more of a complete business platform, while Gumroad is more focused on getting products and memberships sold with relatively little setup. Gumroad also says it acts as merchant of record and handles worldwide sales-tax collection/remittance. Gumroad Gumroad

If you tell me roughly what you're selling (e.g. templates, software, ebooks, courses), your subscription model, and your monthly revenue, I can compare the fees and limitations of 3–5 platforms for your specific setup.

For a subscription-box business, I’d focus less on “can it charge customers monthly?”—most established platforms can—and more on batching orders, controlling fulfillment dates, box customization, failed-payment recovery, and integrations with your 3PL/warehouse.

Strong options

• Shopify + Shopify Subscriptions — simplest starting point if you're already on Shopify. It supports weekly/monthly/yearly auto-billing, skips, pauses, cancellations, customer self-service, and subscription analytics directly in Shopify. Shopify Help Center Shopify

help.shopify.com

• Skio — particularly interesting for a true subscription-box operation. It supports recurring and prepaid subscriptions, Build-a-Box, payment retries, and configurable order days. Its order-day functionality is explicitly designed for subscription boxes and batch fulfillment—for example, processing all monthly boxes on a particular day. Skio Skio Skio

skio.com

• Recharge — worth considering if you expect a larger subscription program with a substantial integration ecosystem. Shopify itself lists Recharge among its major subscription-management options. Shopify
• Appstle — a lower-complexity Shopify option worth evaluating. The Shopify App Store currently specifically describes it as supporting subscriptions, subscription boxes, and bundles, with a free plan available. Shopify App Store

For your particular model

If you're sending a fixed/curated box every month, I'd shortlist Shopify + Skio first. Skio's ability to set common processing days is useful operationally: instead of orders trickling into fulfillment every day, you can establish a cutoff and have the month's boxes generated together. Skio

If customers will choose several items to construct their own box, Skio becomes especially relevant because its selling plans include a Build-a-Box model. Skio

If you're just validating the concept and want the fewest moving parts, Shopify Subscriptions is probably enough to launch and test demand before adding a dedicated subscription platform.

One important distinction: billing software isn't necessarily your fulfillment software. I'd verify that whichever subscription layer you choose integrates cleanly with your actual 3PL/warehouse, inventory system, shipping software, and the way you want monthly boxes assembled.

If you tell me (1) Shopify or another ecommerce platform, (2) fixed box vs. build-your-own, and (3) roughly how many subscribers you expect in year 1, I can narrow this to a practical setup and compare the likely costs.

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

My shortlist

1. Medusa — my pick for a custom build

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

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

Choose Medusa if:

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

2. Saleor — excellent for a sophisticated system

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

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

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

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

3. WooCommerce — easiest route to a complete store

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

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

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

What I'd choose

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

Something like:

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

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

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

For a less technical owner: WooCommerce.

For a large, sophisticated custom commerce application: Saleor.

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

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

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

My shortlist

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

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

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

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

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

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

shopify.com

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

Why it’s strong:

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

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

Choose Shopify if:

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

Downside: Monthly cost and app costs can add up.

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

squareup.com

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

Why it’s strong:

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

Choose Square if:

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

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

3. WooCommerce — Best for businesses that already use WordPress

woocommerce.com

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

Why it’s strong:

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

Downside: More maintenance:

• hosting
• updates
• security
• plugin compatibility

My default recommendation

For a typical local retail shop:

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

A few details would change the recommendation:

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

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

A few details would change the recommendation:

If you’re non-technical and your main sales engine will be social links + email, I’d narrow it to Shopify and Wix.

My practical comparison

Shopify is particularly strong if you expect social selling to become a major part of the business. Its sales channels connect products with Facebook, Instagram, TikTok, YouTube and other channels, while orders and inventory can be managed centrally. Shopify Help Center Shopify

Wix may feel more approachable if you're starting from scratch. It combines the website/store, social-media management, email campaigns, analytics and even a link-in-bio storefront in one dashboard. wix.com Wix Help Center

I'd probably start with Shopify if your phrase "sell through social links and email" means people will discover products through Instagram/Facebook/TikTok posts and click through to buy. Shopify's social-commerce infrastructure is more deeply centered around that workflow. Shopify

One important distinction: Squarespace is attractive if design is your priority, and it has email campaigns plus Facebook/Instagram integration, but its current Facebook/Instagram product integration is primarily a catalog/ad link back to your site rather than the same kind of native social checkout experience. support.squarespace.com support.squarespace.com

If you tell me what you're selling (physical products, digital products, services, etc.) and roughly how many products, I can narrow this down to the simplest setup for you.

For a photographer selling both high-resolution digital files and physical prints, I’d look first at Pixieset and Pic-Time.

• Pixieset — best all-around/simple setup. Supports original-resolution downloads, automatic digital delivery, and automatic lab fulfillment for prints. Pixieset Help Center Pixieset Help Center
• Pic-Time — strongest if print sales are a major revenue stream. It supports high-res downloads plus print fulfillment and built-in automated campaigns designed to drive print sales. Pic-Time Help Center Pic-Time
• SmugMug — good for a broader storefront/portfolio. Offers original-resolution downloads and a large print/product catalog. SmugMug Support SmugMug

My practical pick: Pixieset for simplicity; Pic-Time if you specifically want to maximize automated print sales.

For a brick-and-mortar studio that needs both class bookings and merchandise sales, I’d look first at Square, Wix, and Squarespace.

Square

Square is particularly well suited to your setup. Its class-booking system supports one-time and recurring classes, capacity limits, instructors, online booking, payments, cancellations, and reminders. Square Square

At the same time, Square Online lets you sell physical products with shipping, pickup, or local delivery, and its booking site can combine bookings and product purchases. Square Square

That means you could have, for example:

• Classes: Tuesday Ceramics — 6:00 PM — 8 spots
• Merch: Studio T-shirt — $32
• Checkout: A customer books the class and buys the shirt in the same ecosystem
• Studio: The same Square system handles your in-person sales and inventory

One important consideration: class booking is part of Square's higher-tier/advanced booking capabilities, rather than simply the most basic Square setup. Square Square

Wix

Wix is another good all-in-one option. Wix Bookings supports appointments, classes, and courses, while Wix Stores handles physical merchandise. Wix Help Center Wix Help Center

I'd lean toward Wix if the website/branding experience is as important to you as the operational side.

Squarespace

Squarespace can also do both. Its commerce system supports physical merchandise, while its service products can be used for classes and events; for classes at specific times with limited capacity, Squarespace also points users toward its booking functionality. support.squarespace.com support.squarespace.com support.squarespace.com

For your particular brick-and-mortar use case, I'd investigate Square first, especially if you want your online bookings, merch, inventory, payments, and physical studio checkout connected rather than stitching several systems together.

If you tell me what kind of studio you run (yoga, dance, pottery, fitness, art, etc.) and roughly how many classes/customers you have per week, I can compare the actual plans and costs for Square vs. Wix vs. Squarespace.

For a two-person startup testing product-market fit, I’d optimize for:

1. Launch in days, not weeks
2. Spend <$50/month before you have traction
3. Avoid engineering work
4. Be able to migrate or scale later

My default recommendation: start with Shopify unless your product is extremely simple. It is usually the best tradeoff between speed, reliability, checkout quality, and future flexibility. Shopify Shopify

Shortlist

Shopify WooCommerce## What I would choose by scenario

1. Physical consumer product (most startups)

Pick: Shopify

Examples:

• DTC apparel
• skincare
• gadgets
• food products
• accessories

Why:

• Payments, inventory, shipping, taxes, abandoned carts, and analytics are already handled.
• You can get a credible storefront running quickly.
• You won't need to rebuild after your first few hundred orders. Shopify

Minimal stack:

• Shopify
• Free theme
• Stripe/Shopify Payments
• Klaviyo or Shopify Email
• Google Analytics
• Customer support inbox

Avoid installing 20 apps early. They slow you down and obscure whether customers actually want the product.

2. You have 1–5 products and are mostly testing demand

Pick: Big Cartel or Shopify starter setup

Big Cartel is attractive when the goal is simply:

"Can strangers pay money for this?"

It is intentionally simple and has low upfront cost. Shopify

3. You already have a WordPress site

Pick: WooCommerce

WooCommerce can be inexpensive because the core software is free, but you trade money for maintenance: hosting, updates, plugins, security, and configuration. WooCommerce

For a two-person team trying to learn PMF, I would avoid this unless someone on the team already knows WordPress well.

What I would not do for PMF testing

• ❌ Build a custom storefront
• ❌ Hire a developer for checkout flows
• ❌ Spend weeks perfecting branding
• ❌ Add complex subscriptions/loyalty/referral systems before sales exist
• ❌ Optimize SEO before you know the product resonates

A lean validation setup

You could realistically launch with:

• Storefront: Shopify
• Domain: ~$10–20/year
• Theme: free
• Product photos: phone camera + simple editing
• Email capture: Shopify Email
• Analytics: Google Analytics
• Ads/testing: small daily budget

Your first goal is not a perfect ecommerce machine; it is answering:

• Will people click?
• Will they add to cart?
• Will they pay?
• Will they come back?

If you tell me what you’re selling (physical product, digital product, subscription, marketplace, B2B, etc.) and expected first-month order volume, I can narrow this to a specific stack.

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

Other options:

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

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

For a small local bakery with just a handful of products, Square Online is probably the simplest low-cost choice.

My shortlist

• 🥇 Square Online — best fit for a small bakery

• $0/month on the Free plan.
• You can create an ordering page, accept online payments, and offer pickup.
• Square's current Free plan charges 3.3% + $0.30 for online payments. Square Square
• Particularly convenient if you also take payments in person with Square.
• You can start without buying a website/domain or expensive software. Square
• squareup.com
• Toast — worth considering if you're becoming more of a restaurant operation

• Toast Online Ordering provides a branded ordering page and says it doesn't charge third-party commission on orders. Toast Support Center Toast POS
• However, for only a few bakery items, its broader restaurant/POS ecosystem may be more than you need.
• Shopify — good if you're planning to grow into a larger online store

• Much more powerful for a traditional ecommerce business, but Shopify's current Basic plan is $29/month when billed annually (or $39 month-to-month), so I'd generally avoid it for a tiny bakery menu. Shopify

What I'd do in your situation

I'd start with Square Free and make the ordering page extremely simple:

Cookies | Bread | Cakes | Pickup date/time → Pay

You don't need a complicated website. Put the Square ordering link in your Instagram/Facebook bio, Google Business Profile, and on a QR code at the bakery.

If you tell me roughly how many items you sell, whether you do pickup/delivery, and whether you already use Square for in-person payments, I can tell you exactly how I'd set it up and what it would cost per $100 of orders.

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

My shortlist:

My picks by indie-maker scenario

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

A simple beginner stack I’d use:

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

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

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

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

1. woocommerce.com — best if you want flexibility

WooCommerce's core plugin is free, with no monthly platform fee or revenue share. You mainly pay your payment processor and only add paid extensions if you need them. WooCommerce

Good for: physical products, shipping, inventory, coupons, lots of products.

Downside: it can become complicated/expensive if you start adding lots of extensions.

2. surecart.com — probably my pick for a simple store

SureCart is particularly attractive if you don't need a giant traditional shopping-cart system. Its Launch plan is $0/month, but charges a 2.9% transaction fee in addition to your payment processor's fees. SureCart SureCart

It handles things like products, checkout, orders, coupons, shipping, taxes, subscriptions, and payments without requiring you to assemble lots of separate WordPress plugins. SureCart

Good for: a small catalog, digital products, services, subscriptions, or a straightforward checkout.

3. ecwid.com — good if you want the store managed separately

Ecwid can be embedded into an existing WordPress site. Its plans support adding a store to an existing website, and it doesn't charge its own transaction fee. Ecwid | E-Commerce Shopping Cart

The tradeoff is that you're paying for an external ecommerce service rather than keeping everything inside WordPress.

What I'd choose

For a small WordPress site with perhaps 5–50 products, I'd start with SureCart if you want the least hassle, or WooCommerce if you want maximum control and expect the store to grow.

If you tell me what you're selling (physical products, digital downloads, services, memberships, etc.), roughly how many products, and whether you need shipping, I can narrow it down to the cheapest practical setup—including the payment fees.

If you're a photographer selling prints + digital downloads + licensing, I’d narrow it to three options:

My recommendation: Pixieset

Pixieset is probably the best fit if you want one inexpensive system for a photography portfolio, galleries, prints and digital sales.

Its free plan includes 3 GB storage, unlimited galleries, an integrated storefront, online payments and automatic fulfillment. The tradeoff is a 15% commission on store sales. The $8/month Basic plan (annual billing) removes the commission and adds 10 GB storage, custom domain support and full-resolution downloads. Pixieset Pixieset

Pixieset specifically supports print products, digital downloads and packages, so you can sell something like:

• $25 — Web-resolution digital image
• $75 — High-resolution personal-use image
• $150 — Print + digital bundle
• $300+ — Commercial/license package

pixieset.com

Pic-Time is an excellent alternative

Pic-Time has a permanent free plan with no monthly fee and includes a print shop, online payments and automatic fulfillment through 30+ print labs. Its free and Beginner plans charge a 15% commission; Beginner is $7/month when billed annually. Pic-Time Pic-Time

It is particularly interesting for photographers because you can create custom digital-download products, packages, volume pricing and different download terms. Pic-Time Help Center Pic-Time Help Center

pic-time.com

Payhip if licensing is a major part of the business

Payhip is less photography-specific, but its economics are attractive for digital products. The free plan is $0/month + 5% transaction fee, with unlimited products and revenue. You could create products such as "Commercial License — Single Image," upload the licensed file, and include your licensing terms with the purchase. Payhip Payhip

payhip.com

For your particular mix, I'd start with Pixieset if prints are important, or Pic-Time if you're especially focused on selling photography through galleries. If licensing becomes a substantial revenue stream, you could use Payhip alongside your photography gallery rather than forcing everything into one platform.

One important distinction: selling a digital image isn't the same as selling a license to use it. I'd set up separate products and clearly specify personal/editorial/commercial usage, permitted media, duration, territory, exclusivity, and whether resale/redistribution is prohibited.

For a tight-budget, headless-first shop, I’d put Medusa at the top of the evaluation list.

Shortlist

Medusa's current cloud plans start at $29/month and explicitly have 0% GMV platform fees, with a $99/month Launch tier adding things like autoscaling, backups, custom storefront domains and Redis-backed infrastructure. Medusa Medusa Docs

Vendure Core is free/open source and can be self-hosted, although its current commercial Platform offering is sold on an annual subscription with pricing quoted per project. Vendure Vendure

Saleor is also open source, but its managed Cloud pricing is dramatically higher: the current Select tier starts at $1,599/month, making it harder to justify for a genuinely budget-constrained launch. Saleor Commerce

Shopify supports custom/headless storefronts and currently lists headless storefront support across its plans, but you're still buying into its SaaS ecosystem rather than running the commerce engine yourself. Shopify

What I'd evaluate first

Medusa + Next.js is probably the stack I'd prototype first if your priorities are:

• low monthly infrastructure cost
• genuinely headless architecture
• TypeScript throughout
• ability to self-host later
• no platform GMV tax
• freedom to customize the storefront and commerce logic

The important caveat is that "free/self-hosted" doesn't mean zero cost: you'll still pay for hosting, database, email, storage, monitoring, and your engineering time. For a small shop, though, that can be quite inexpensive.

I'd run a small proof-of-concept with Medusa and Vendure before committing, using the same requirements: catalog, variants, cart, checkout/payment, discounts, shipping, tax, order management, and your intended CMS/front end. That will tell you much more about total cost than feature checklists. Vendure Medusa

If you tell me your expected monthly orders, catalog size, tech stack (e.g. Next.js), and whether you need B2B/multi-vendor, I can narrow this to a concrete low-cost architecture and estimated monthly bill.

Shopify supports custom/headless storefronts and currently lists headless storefront support across its plans, but you're still buying into its SaaS ecosystem rather than running the commerce engine yourself.

What I'd evaluate first

Medusa + Next.js is probably the stack I'd prototype first if your priorities are:

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

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

Here are the strongest budget options:

Shopify Shopify## My pick by situation

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

Pick: Big Cartel

Good fit if you’re launching:

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

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

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

2. You want to build a serious apparel brand

Pick: Shopify

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

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

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

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

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

Pick: Wix

Wix is strong if your priority is:

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

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

A lean launch setup I’d use

For a first drop:

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

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

Avoid spending heavily on:

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

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

For a small handmade goods shop on a tight budget, I’d pick WooCommerce self-hosted on WordPress. It gives you the most control per dollar: your data, code, hosting, themes, and checkout flow are yours, with a huge ecosystem of extensions. Toolradar

Good options:

• Best overall: WooCommerce — easiest to self-host cheaply, great for handmade catalogs, blogs, SEO, coupons, shipping plugins, and custom themes. Open Source Groups
• Simpler dedicated store: OpenCart — lighter and less tied to a CMS, but a smaller ecosystem. Velocity
• More “pure ecommerce” feel: PrestaShop — stronger built-in store features, but usually more setup and hosting overhead. Open Source Groups
• Developer-focused: Medusa — maximum customization, but you’ll build more yourself; not ideal if you want to spend time making products rather than coding. Open Business Network

For your situation, a practical stack:

• $5–15/month VPS or shared hosting
• WordPress + WooCommerce
• Free theme initially
• Stripe/PayPal for payments
• Regular backups + updates

Avoid Magento unless you expect a large catalog and have technical help; it’s powerful but expensive to maintain. Velocity

For a static/headless storefront where the backend is primarily an API, I’d narrow it to Medusa, Saleor, and Vendure. All three are designed for decoupled storefronts. Vendure

My take

1. Medusa — probably my first choice for your setup

Medusa is particularly well suited if your static site is built with JavaScript/TypeScript.

Its V2 Store API is REST, has an OpenAPI specification, and is explicitly intended for storefronts and mobile apps. It also supports publishable API keys designed for client-side storefronts. Medusa Documentation Medusa Documentation

The architecture is modular—you get products, carts, customers, inventory, orders, payments, promotions, fulfillment, etc., while being able to extend the modules and API. Medusa Documentation

Good architecture:

Static site → Medusa Store API → PostgreSQL

That makes it quite natural for something like Astro, Next.js static export, Gatsby, or a plain JS site.

docs.medusajs.com

2. Saleor — excellent if you want GraphQL

Saleor is very API-centric and GraphQL-native. Its API covers catalog, checkout, channels, promotions, payments, shipping, etc., and it has extensive webhook/app mechanisms for integrations. Saleor Documentation Saleor Commerce

I'd lean toward Saleor if you expect your storefront to make sophisticated, highly tailored GraphQL queries or you expect multi-region/multi-currency, multiple sales channels, marketplaces, or complex commerce integrations.

saleor.io

3. Vendure — great TypeScript alternative

Vendure is built with TypeScript/NestJS and exposes GraphQL Shop and Admin APIs. Its core is explicitly positioned as a framework for developers building custom ecommerce applications. Vendure Vendure

It's attractive if your backend team is already heavily invested in Node.js + TypeScript + GraphQL, especially when you'll be extending the commerce model substantially.

vendure.io

What I'd choose

For the specific phrase "plug into our static site", I'd start with Medusa unless you have a strong reason to prefer GraphQL.

The deciding factors I'd use are:

• Static/Jamstack + REST + TypeScript: Medusa
• GraphQL-first + sophisticated/headless architecture: Saleor
• TypeScript + GraphQL + substantial backend customization: Vendure

One particularly important distinction: don't choose based solely on whether the product has an API. Look closely at checkout, authentication, payments, webhooks, inventory, search, tax/shipping, and how easily you can customize those without modifying/forking the core.

If you tell me your stack (Astro / Next.js / plain HTML+JS / Hugo / etc.) and whether you need Stripe, subscriptions, digital products, or physical shipping, I can narrow this down to an architecture and API choice.

Its V2 Store API is REST, has an OpenAPI specification, and is explicitly intended for storefronts and mobile apps. It also supports publishable API keys designed for client-side storefronts. Medusa Documentation Medusa Documentation

The architecture is modular—you get products, carts, customers, inventory, orders, payments, promotions, fulfillment, etc., while being able to extend the modules and API. Medusa Documentation

Good architecture:

Static site → Medusa Store API → PostgreSQL

That makes it quite natural for something like Astro, Next.js static export, Gatsby, or a plain JS site.

docs.medusajs.com

2. Saleor — excellent if you want GraphQL

Saleor is very API-centric and GraphQL-native. Its API covers catalog, checkout, channels, promotions, payments, shipping, etc., and it has extensive webhook/app mechanisms for integrations. Saleor Documentation Saleor Commerce

I'd lean toward Saleor if you expect your storefront to make sophisticated, highly tailored GraphQL queries or you expect multi-region/multi-currency, multiple sales channels, marketplaces, or complex commerce integrations.

saleor.io

3. Vendure — great TypeScript alternative

Vendure is built with TypeScript/NestJS and exposes GraphQL Shop and Admin APIs. Its core is explicitly positioned as a framework for developers building custom ecommerce applications. Vendure docs.vendure.io

It's attractive if your backend team is already heavily invested in Node.js + TypeScript + GraphQL, especially when you'll be extending the commerce model substantially.

For an enterprise team prioritizing scalability and containerized deployment, I’d shortlist Saleor, Medusa, and Vendure, with the choice driven mainly by your engineering stack and enterprise requirements. Vendure Pawel Owerczuk

• Saleor — Python/Django, GraphQL-first, PostgreSQL; strong fit for multi-channel and enterprise commerce. Vendure
• Medusa — TypeScript/Node.js, modular architecture, MIT core; attractive for teams wanting highly customizable containerized services. Pawel Owerczuk
• Vendure — TypeScript/NestJS, GraphQL, plugin architecture; particularly relevant for complex B2B/omnichannel systems. Vendure

If your team is TypeScript-heavy, Medusa or Vendure are natural candidates; if Python/GraphQL is already strategic, Saleor is worth prioritizing.

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

How they compare

My take: Shopware 6

Shopware is particularly interesting for your priorities.

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

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

developer.shopware.com

PrestaShop 9 is worth considering

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

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

prestashop.com

Don't dismiss WooCommerce

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

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

github.com

What I'd choose based on your priorities

If your requirement is specifically:

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

I'd shortlist Shopware 6 and PrestaShop 9 first.

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

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

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

If inventory and warehouse management are the primary requirements, I’d narrow the open-source ecommerce stack to Odoo, ERPNext, and Medusa. My recommendation depends heavily on whether you want the commerce platform itself to be the operational backbone or whether you want a modern headless storefront.

My shortlist

1. Odoo — my pick for serious warehouse operations

Odoo is the one I'd investigate first if you have multiple warehouses, bins/locations, barcode workflows, replenishment, returns, purchasing, or complex fulfillment rules.

Its Inventory application is explicitly designed as both inventory management and a WMS. It supports warehouses and hierarchical locations, routes, replenishment, serial/lot tracking, cycle counting, reservations, and advanced picking strategies. Odoo Odoo Odoo

The particularly useful part is its route/push/pull-rule system. You can model flows such as:

Receiving → QC → Putaway → Picking → Packing → Shipping

and create different rules for different products or warehouses. Odoo Odoo

It also supports multiple warehouses and transfers between them. Odoo

Caveat: Odoo is open source, but its overall product is dual-licensed; some capabilities are in the commercial edition. So I'd distinguish "open-source Odoo" from "the complete Odoo feature set" when evaluating it. ERP Research

2. ERPNext — best if "fully open source" is important

ERPNext is compelling if you want the ERP and inventory system to be completely open-source rather than primarily an ecommerce framework.

Its warehouse model can go quite deep:

Warehouse → Room → Row → Shelf → Bin

and it maintains stock balances by item and warehouse. Frappe Documentation

It also integrates nicely with a separate storefront because products, orders, invoices, shipments, returns, warehouses, and stock movements are exposed through its REST API. Frappe Documentation

So a stack like:

Next.js storefront → ERPNext → warehouse/inventory/accounting

is quite reasonable.

I'd lean toward ERPNext when inventory + purchasing + accounting + manufacturing/business operations matter more than having the ecommerce engine itself be extremely sophisticated.

3. Medusa — best modern ecommerce architecture

Medusa is interesting if you want a modern headless ecommerce platform rather than an ERP.

Its inventory module supports inventory items, multiple locations/warehouses, reservations, and inventory across locations. Medusa Docs

It also supports more sophisticated ecommerce scenarios such as:

• multi-warehouse inventory
• reservations
• splitting orders across locations
• returns/exchanges
• omnichannel inventory
• custom inventory logic
• connecting to an external WMS

MedusaThat last point is important: Medusa can act as the commerce layer while a dedicated WMS/ERP handles the really complicated warehouse operations.

What I'd choose

If you told me simply:

"I want an open-source ecommerce system, and warehouse/inventory is one of the most important parts."

I'd investigate Odoo first.

If you told me:

"I want everything genuinely open source, including ERP, accounting, purchasing and inventory."

I'd investigate ERPNext.

If you told me:

"I want a modern React/Next.js headless storefront and excellent ecommerce developer experience, but inventory needs to be considerably better than Shopify's basic inventory."

I'd investigate Medusa.

The biggest architectural question is actually how sophisticated your warehouse is. If you need things like barcode scanning, bin-level inventory, receiving/putaway, wave or batch picking, lot/serial tracking, multiple fulfillment centers, cycle counts, replenishment, 3PL integration, and warehouse transfers, I'd favor an ERP/WMS-centric architecture rather than choosing a pure ecommerce platform and trying to bolt WMS functionality onto it. Odoo in particular has dedicated support for wave, cluster, and batch picking. Odoo

If you tell me your number of SKUs, number of warehouses, order volume/day, B2B vs B2C, and whether you need barcode scanners/manufacturing/3PL, I can narrow this down to a specific stack and architecture.

So a stack like:

Next.js storefront → ERPNext → warehouse/inventory/accounting

is quite reasonable.

I'd lean toward ERPNext when inventory + purchasing + accounting + manufacturing/business operations matter more than having the ecommerce engine itself be extremely sophisticated.

3. Medusa — best modern ecommerce architecture

Medusa is interesting if you want a modern headless ecommerce platform rather than an ERP.

Its inventory module supports inventory items, multiple locations/warehouses, reservations, and inventory across locations.

It also supports more sophisticated ecommerce scenarios such as:

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

Why it fits:

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

How I'd compare the main options

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

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

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

For a subscription newsletter with bonus downloadable files, I’d narrow it to Memberful, Ghost, and Podia. The right choice depends mainly on whether the newsletter or the downloadable library is the center of the business.

My practical recommendation: Memberful

Memberful is particularly well suited if you already have a website or want your own branded membership area. It supports recurring plans, gated content, newsletters, and digital downloads, with payments through your own Stripe account. Memberful Memberful

The important advantage for your use case is that you can make the newsletter subscription itself the entitlement: someone pays monthly/yearly → they're a member → they can access the appropriate newsletter content and bonus files. Memberful specifically supports including downloads with subscription plans. Memberful

memberful.com

When I'd choose Podia instead

Podia is compelling if your downloadable content is becoming a substantial product library. It combines memberships, email marketing, digital downloads, website/landing pages, and other digital products. Its download system supports customer accounts, re-downloads, bundles, and granting bonus products alongside purchases. Podia Podia

podia.com

When Ghost makes more sense

Ghost is attractive if the newsletter/publication is the product and downloadable bonuses are secondary. It's built around publishing and paid memberships, whereas Memberful and Podia are more oriented toward membership/product commerce.

For your specific requirement of securely gating downloadable files, I'd lean away from making Ghost the sole storefront: its native membership gating is excellent for content, but file-download protection can require additional implementation. Ghost Forum

ghost.org

Bottom line:

• Newsletter + membership + occasional bonuses → Memberful
• Newsletter + substantial downloadable product library → Podia
• Primarily a paid publication/newsletter → Ghost

If you tell me roughly your subscriber count, monthly price, and whether you already have a website/newsletter platform, I can compare the actual fees and setup complexity for your situation.

Memberful is particularly well suited if you already have a website or want your own branded membership area. It supports recurring plans, gated content, newsletters, and digital downloads, with payments through your own Stripe account. Memberful Memberful

The important advantage for your use case is that you can make the newsletter subscription itself the entitlement: someone pays monthly/yearly → they're a member → they can access the appropriate newsletter content and bonus files. Memberful specifically supports including downloads with subscription plans. Memberful

memberful.com

When I'd choose Podia instead

Podia is compelling if your downloadable content is becoming a substantial product library. It combines memberships, email marketing, digital downloads, website/landing pages, and other digital products. Its download system supports customer accounts, re-downloads, bundles, and granting bonus products alongside purchases. Podia Podia

podia.com

When Ghost makes more sense

Ghost is attractive if the newsletter/publication is the product and downloadable bonuses are secondary. It's built around publishing and paid memberships, whereas Memberful and Podia are more oriented toward membership/product commerce.

For your specific requirement of securely gating downloadable files, I'd lean away from making Ghost the sole storefront: its native membership gating is excellent for content, but file-download protection can require additional implementation.

For a nonprofit selling PDFs, downloadable guides, and training materials, I’d narrow it to three practical options:

My practical recommendation: Payhip

For a very tight budget, I would start with payhip.com.

Its free plan is $0/month + 5% per transaction, with unlimited products and revenue, and it includes the core features rather than putting them behind different tiers. Payment processing fees from Stripe/PayPal are additional. Payhip Payhip

That's particularly attractive for a nonprofit because you don't have to pay for hosting, security updates, ecommerce plugins, or a developer just to get started.

It also supports pay-what-you-want pricing, which could be useful for nonprofit materials—for example, setting a $10 minimum while allowing supporters to contribute more. Payhip Help Center

Payhip also says it can automatically handle EU VAT and UK VAT, which removes another administrative burden if you sell internationally. Payhip

If you want true open source: Easy Digital Downloads

If you already have a WordPress website and are comfortable maintaining it, I'd look at easydigitaldownloads.com.

It's specifically designed around digital products, rather than adapting a physical-product store to PDFs. Its free core is available through WordPress, while more advanced capabilities can require paid extensions. PluginScout Software Advice

This makes more sense if you want:

• Full ownership of your store and customer experience
• Your ecommerce system integrated tightly into your existing nonprofit website
• More control over memberships, recurring payments, licensing, etc.
• The ability to customize things yourself

The downside is that "free/open source" doesn't mean zero cost: you'll still have hosting, payment-processing costs, backups, maintenance, and potentially paid extensions.

What about WooCommerce?

woocommerce.com is also open source and its core platform is free, with no revenue share. WooCommerce

I'd choose it if you expect to sell both digital and physical products, or eventually need a fairly sophisticated ecommerce operation. For a nonprofit whose primary products are PDFs and training downloads, though, it can be more machinery than necessary.

One option I'd put behind Payhip

gumroad.com is extremely easy to use and has no monthly fee, but its current direct-sale fee is 10% + $0.50 per transaction, substantially higher than Payhip's free-plan platform fee. Gumroad also charges 30% for sales originating through its Discover marketplace. Gumroad Gumroad

For a nonprofit operating on thin margins, that difference can become significant.

So my short version: start with Payhip if you want to launch cheaply with almost no technical work; choose Easy Digital Downloads if you already run WordPress and want long-term ownership/control.

If you tell me roughly how many PDFs you sell, your average price, monthly sales, whether you already have WordPress, and whether you need memberships/courses, I can calculate the approximate annual cost of each and show you which setup has the lowest total cost.

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

My practical comparison

🥇 Lemon Squeezy is probably the best fit

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

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

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

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

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

A particularly nice model for a solo developer would be:

$99 perpetual license + 12 months of updates

Then:

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

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

FastSpring is worth considering if licensing is more sophisticated

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

That's attractive if you eventually need things like:

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

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

Paddle

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

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

Gumroad

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

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

What I'd build

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

Lemon Squeezy + your own tiny licensing/update API

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

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

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

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

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

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

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

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

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

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

Yes. For a marketplace where multiple creators sell digital goods and receive automatic payouts, a particularly relevant option is Sharetribe + Stripe Connect.

Strong options

Sharetribe is specifically designed for marketplaces and has a digital-product marketplace setup with digital downloads, seller onboarding/KYC, automatic payouts, and marketplace commissions. Sharetribe Sharetribe

With Stripe Connect underneath, you can have:

• Customer pays $20 for a creator's digital product
• Your marketplace automatically takes, say, a 20% commission
• Creator receives the remaining $16
• Stripe handles seller onboarding, payout information, and payouts
• You can delay the creator payout until the transaction is considered complete Sharetribe Sharetribe

sharetribe.com

If you're building your own platform

I'd look closely at Stripe Connect directly. It is designed specifically for multi-sided marketplaces: it can onboard sellers, split payments between multiple parties, take platform fees, and automate payouts. Stripe Stripe

stripe.com

So the basic architecture would be:

Your marketplace → Stripe Connect → Creator's connected Stripe account → Creator's bank account

If you tell me whether you're looking for no-code, Shopify/WooCommerce, or a custom-built marketplace, I can narrow this down to the most suitable 3–5 platforms and compare their fees and payout mechanics.

For software with frequent releases, look for a software licensing + entitlement platform, not a general ecommerce cart. Strong options:

• Revenera — enterprise-focused; handles licenses, entitlements, download rights, version delivery, and update eligibility. Good for commercial desktop software and complex licensing models. Revenera Revenera
• ChargePanda — built around purchase → entitlement → signed download flows, versioned files, support/update windows, and expiring download links. ChargePanda
• WooCommerce + licensing extensions — flexible if you want to own the storefront; extensions such as Kestrel API Manager add license keys, activations, secure downloads, and update APIs. WooCommerce WooCommerce
• Build-your-own with a payment provider + entitlement service — common for SaaS/dev tools: checkout creates entitlements, your API validates them, and downloads are served through signed URLs or authenticated endpoints.

Minimum architecture to aim for:

1. Order system → creates customer entitlement.
2. License/entitlement API → answers “is this customer allowed version X?”
3. Update manifest endpoint → app checks for new versions.
4. Secure download endpoint → returns short-lived signed URLs or streams files after entitlement validation.
5. Admin tooling → revoke licenses, manage versions, view downloads.

For a small-to-mid software vendor, I’d usually choose a licensing-focused solution rather than trying to make Shopify/WooCommerce alone handle update authorization. For enterprise desktop software, Revenera-style tooling is more typical; for indie apps, a lighter entitlement service is often enough. Revenera

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

My practical comparison

1. Payhip — probably the best fit for you

Payhip is particularly attractive if your goal is simply:

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

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

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

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

payhip.com

2. Gumroad — easiest "just start selling"

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

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

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

gumroad.com

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

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

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

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

ebook → email list → paid course → membership → coaching

What I'd do in your situation

Start with Payhip.

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

A very simple starting setup could be:

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

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

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

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

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

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

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

payhip.com

2. Gumroad — easiest "just start selling"

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

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

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

gumroad.com

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

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

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

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

ebook → email list → paid course → membership → coaching

What I'd do in your situation

Start with Payhip.

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

A very simple starting setup could be:

Yes. If your model is “customer pays → gets access to files for 30 days → access expires”, there are a few tools that fit particularly well.

Best fits

• sendowl.com — probably the closest match. It supports time-limited download links, download limits, PDF stamping, and access management. You can sell files directly or connect it to Shopify/Square. SendOwl SendOwl
• sellfy.com — supports subscriptions where downloads are available only during the subscription period. For a monthly rental, a customer paying for one month gets access during that month and the previous download links are deactivated afterward. Sellfy Help Center Sellfy
• Shopify + SendOwl — useful if you want a full storefront/checkout but want SendOwl handling the protected file delivery. Shopify itself has download limits, but its native Digital Downloads app doesn't provide the same kind of time-based expiration for shared links. SendOwl Shopify Help Center
• Handoff Digital Downloads (Shopify) — a newer Shopify option that specifically provides expiring download links, configurable link duration, and download limits. It's currently listed at $9/month with a 14-day trial, although it has very few/no reviews yet. Shopify App Store Shopify App Store

One important distinction

If you mean:

“The customer can download the files, but the download link expires after 30 days.”

Then SendOwl or Handoff are good matches.

If you mean:

“The customer can view/use the files for 30 days, and then they lose access—even if they already downloaded a copy.”

That's different. An expiring download link cannot accomplish that, because once someone downloads a PDF, ZIP, video, etc., you generally can't make that local copy expire. You'd want a gated/streaming access system rather than ordinary file downloads.

If you tell me what type of files you're renting (PDFs, videos, software, templates, etc.) and whether customers are allowed to download them, I can narrow this down to the best 2–3 options and explain exactly how the 30-day rental would work.

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

Payhip

Payhip explicitly supports pay-what-you-want pricing for digital products. You can enter:

• 0+ → customer can download for free or pay any amount
• 5+ → $5 minimum, but they can pay more

It also supports uploading PDFs, audio, video and other digital files, with automatic delivery after purchase. Payhip Help Center Payhip Help Center

That makes a setup like “Zine #12 — $0+” or “Album — $5+” straightforward. Payhip's free plan currently has a 5% transaction fee; paid plans reduce or eliminate that platform fee. Payhip

Gumroad

gumroad.com also has a proper PWYW feature. You can set a minimum amount and a suggested amount, which is particularly useful if you want to say “$5 suggested, pay what you can.” Gumroad

The tradeoff is cost: Gumroad currently charges 10% + $0.50 on direct/profile sales, before applicable payment-processing costs. Gumroad Gumroad

itch.io

If the zines/music are part of an independent-art/DIY publishing ecosystem, itch.io has unusually good PWYW support. Its pricing system lets you set a minimum—or make something free and explicitly solicit a donation—and users can pay above the minimum. itch.io

My practical shortlist: start with Payhip if you want a conventional storefront for both zines and music; consider Gumroad if you prioritize simplicity and its ecosystem; consider itch.io if the audience is particularly indie/DIY/creative.

One important distinction: if by “optional donations” you mean a separate donation amount in addition to purchasing the zine/music, rather than simply allowing customers to pay more than the listed price, I'd look specifically at the checkout mechanics before choosing. Payhip's PWYW model is fundamentally attached to the product purchase, while Ko-fi is more explicitly built around separate tips/support. Payhip Help Center ko-fi.com

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

How I’d compare the main options

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

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

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

My practical recommendation

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

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

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

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

If the goal is specifically “checkout should be a commerce service, not a frontend feature”, I’d shortlist commercetools, Saleor, Medusa, and Shopify—but they represent very different levels of control.

My architectural take

If checkout is strategically important and you expect unusual flows, I'd start with Saleor or commercetools.

commercetools is particularly interesting if you want checkout to become an independently evolving service. Its Checkout product has a dedicated Checkout API, and the SDKs support it directly; the platform is designed around composable commerce rather than treating headless as primarily a storefront concern. commercetools Documentation commercetools Documentation

Saleor is compelling if you want maximum control without building the entire commerce engine yourself. Its APIs are GraphQL-native, and Saleor explicitly supports decoupling the frontend while extending commerce behavior through APIs/webhooks. Saleor Commerce Saleor Commerce

Medusa makes sense if your team is strongly TypeScript/Node-oriented and wants to own the checkout domain. Its modular architecture is well suited to replacing pieces of the standard checkout rather than fighting a SaaS platform's prescribed flow. PowerGate Software OSSAlt

Shopify is the operationally simpler choice. Its current Storefront API supports custom storefronts, carts and checkout, and Shopify explicitly supports bringing your own frontend/framework. However, there's an important architectural distinction: you're consuming Shopify's checkout infrastructure rather than owning an independently deployable checkout domain. Shopify Shopify

One important Shopify detail: don't architect against the old Checkout API. Shopify deprecated the relevant Checkout APIs and directs headless implementations toward the Storefront Cart API/Checkout Kit. Shopify

The architecture I'd aim for

Rather than:

Frontend → Commerce platform → Checkout

I'd design:

Frontend(s)
→ Checkout API / Checkout BFF
→ Commerce platform
→ Payment provider
→ Tax / fraud / promotions / fulfillment

That gives you a stable checkout contract such as:

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

Your web app, native app, kiosk, marketplace UI, or future AI shopping interface can all consume the same checkout capability.

The key question is therefore how much of that checkout domain you want the commerce vendor to own:

• Vendor owns most of it: Shopify
• Vendor provides composable checkout primitives: commercetools
• You own the domain logic, platform supplies commerce primitives: Saleor / Medusa
• You want checkout to be a genuinely independent business capability: commercetools or Saleor are the first two I'd investigate.

If you tell me your stack (e.g. Next.js/React), B2C vs B2B, payment provider, countries, and whether checkout has bespoke logic, I can narrow this to a concrete architecture and platform choice.

If checkout is strategically important and you expect unusual flows, I'd start with Saleor or commercetools.

commercetools is particularly interesting if you want checkout to become an independently evolving service. Its Checkout product has a dedicated Checkout API, and the SDKs support it directly; the platform is designed around composable commerce rather than treating headless as primarily a storefront concern. commercetools Documentation commercetools Documentation

Saleor is compelling if you want maximum control without building the entire commerce engine yourself. Its APIs are GraphQL-native, and Saleor explicitly supports decoupling the frontend while extending commerce behavior through APIs/webhooks. Saleor Commerce Saleor Commerce

Medusa makes sense if your team is strongly TypeScript/Node-oriented and wants to own the checkout domain. Its modular architecture is well suited to replacing pieces of the standard checkout rather than fighting a SaaS platform's prescribed flow. PowerGate Software OSSAlt

Shopify is the operationally simpler choice. Its current Storefront API supports custom storefronts, carts and checkout, and Shopify explicitly supports bringing your own frontend/framework. However, there's an important architectural distinction: you're consuming Shopify's checkout infrastructure rather than owning an independently deployable checkout domain. Shopify Shopify

One important Shopify detail: don't architect against the old Checkout API. Shopify deprecated the relevant Checkout APIs and directs headless implementations toward the Storefront Cart API/Checkout Kit. Shopify

The architecture I'd aim for

Rather than:

Frontend → Commerce platform → Checkout

I'd design:

Frontend(s)
→ Checkout API / Checkout BFF
→ Commerce platform
→ Payment provider
→ Tax / fraud / promotions / fulfillment

That gives you a stable checkout contract such as:

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

Your web app, native app, kiosk, marketplace UI, or future AI shopping interface can all consume the same checkout capability.

The key question is therefore how much of that checkout domain you want the commerce vendor to own:

• Vendor owns most of it: Shopify
• Vendor provides composable checkout primitives: commercetools
• You own the domain logic, platform supplies commerce primitives: Saleor / Medusa
• You want checkout to be a genuinely independent business capability: commercetools or Saleor are the first two I'd investigate.

If you tell me your stack (e.g. Next.js/React), B2C vs B2B, payment provider, countries, and whether checkout has bespoke logic, I can narrow this to a concrete architecture and platform choice.

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

How I’d compare them

The important distinction

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

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

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

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

For your specific requirement

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

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

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

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

For a small agency building dropshipping stores for local clients, I’d avoid trying to run everything through a single “merchant account manager.” You’ll usually want a client operations stack: one layer for store ownership/access, one for reporting, one for fulfillment/apps, and one for internal project management.

A practical stack:

1. Store ownership & access: Shopify Partner account (if you’re mainly on Shopify)

Use shopify.com as your foundation.

Why:

• Create development stores for builds
• Request collaborator access instead of sharing passwords
• Keep clients as store owners
• Transfer ownership when the store launches
• Manage multiple client relationships under your agency

For most Shopify-focused agencies, this should be the backbone.

2. Multi-store dashboard / portfolio management

If you have 5–50+ client stores, add a portfolio dashboard:

• storelyst.com — built specifically around agency-style multi-store management, reporting, and switching between client stores. StoreLyst
• zovik.ai — focuses on multi-store analytics, reporting, and Shopify/WooCommerce portfolio views. Zovik

These are more useful once your team is constantly jumping between merchant dashboards.

3. Client reporting (so you look like an agency, not a freelancer)

For monthly client updates, consider:

• triplewhale.com — popular for ecommerce attribution and reporting
• klaviyo.com — useful if you manage email/SMS marketing
• lookerstudio.google.com — cheaper option for custom dashboards

A simple agency report should show:

• Revenue
• Ad spend
• ROAS
• Conversion rate
• AOV
• Best-selling products
• Refund rate
• Customer acquisition cost

4. Internal agency operations

Don’t manage clients inside Shopify notes. Use:

• clickup.com or asana.com for client workflows
• 1password.com for credentials (never shared spreadsheets)
• slack.com for client/team communication

Create a template per client:

• Store setup checklist
• Theme customization
• Product imports
• Payment setup
• Shipping rules
• Apps installed
• Launch checklist
• Monthly optimization tasks

5. Dropshipping-specific tools

This depends on your suppliers:

General product sourcing/fulfillment

• dsers.com (AliExpress workflows)
• autods.com (automation-heavy)
• spocket.co (supplier marketplace)

Profit tracking

• beprofit.co
• trueprofit.io

What I’d use for a small agency (5–30 clients)

Lean setup:

• Shopify Partner account
• ClickUp
• 1Password
• Looker Studio
• Klaviyo
• BeProfit/TrueProfit

More agency-style setup:

• Shopify Partner account
• StoreLyst or Zovik for portfolio management
• Triple Whale for reporting
• ClickUp
• 1Password
• Klaviyo

One important operational choice: have clients own their Shopify stores and billing whenever possible. Your agency should have collaborator access and manage the build/optimization, rather than becoming the merchant of record for every client. It reduces payment, liability, and account-transfer headaches as you scale.

If you tell me roughly how many stores you manage now (e.g., 5, 20, 100+) and whether you use Shopify, WooCommerce, or both, I can suggest a tighter stack and budget.

For a subscription-focused dropshipping store, I’d build around Shopify, then add dedicated apps for subscriptions and supplier fulfillment rather than trying to make one platform do everything.

Recommended setup

Shopify itself currently lists Shopify Subscriptions, Appstle, Recharge, Bold, Ordergroove, PayWhirl, and Chargebee among its subscription options. Shopify Subscriptions is particularly straightforward because it integrates directly with Shopify Payments and Shopify's admin. Shopify

For supplier management, DSers supports AliExpress/1688/Alibaba and U.S. suppliers, with automated order processing, tracking synchronization, supplier mapping, and multi-supplier/agent management on its higher tier. Shopify App Store Shopify App Store

What I'd use at different stages

• Starting / testing: Shopify + Shopify Subscriptions + DSers
• Growing subscription business: Shopify + Appstle + DSers
• Large subscription-first brand: Shopify + Recharge/Skio + a dedicated fulfillment/supplier system

The important distinction is that your subscription platform and supplier platform don't necessarily need to be the same thing. Your subscription system creates the recurring customer order; the fulfillment integration then needs to reliably send each subsequent order to the correct supplier.

One thing I'd be careful about: AliExpress-style dropshipping can become awkward for subscriptions because supplier stock, shipping times, product availability, and fulfillment consistency can change. For a genuinely subscription-focused business, I'd eventually prioritize a supplier that can provide stable inventory, predictable fulfillment times, recurring-order automation/API access, and preferably private labeling or branded packaging.

If you tell me what type of product you're planning to sell and whether you're targeting the U.S., I can lay out a specific Shopify + subscription app + supplier stack, including approximate monthly costs and how the recurring-order flow would work.

If your goal is a dropshipping store where you own the code, build custom supplier integrations, automate fulfillment, and avoid SaaS limitations, you should look beyond typical Shopify alternatives. The best choices are usually headless commerce platforms or highly extensible open-source carts. Open Business Network Toolradar

Here are the strongest options:

Open Source Groups OpenSourceProjects.cc## 1. Medusa — probably the best fit for a custom dropshipping operation

Medusa is designed more like a commerce engine than a website builder. You build the storefront separately (often with Next.js/React) and use Medusa as the backend. OSSAlt

Good for:

• Custom supplier APIs
• Multiple suppliers per product
• Automated order routing
• Custom pricing rules
• AI product enrichment pipelines
• Custom inventory syncing
• Marketplace-style workflows
• Mobile apps

A possible architecture:

Customer Storefront
        |
     Next.js
        |
     Medusa API
        |
 ----------------------
 |          |          |
Supplier A Supplier B ERP/WMS
 |          |          |
Dropship APIs / Feeds

For example, you could build logic like:

Customer buys Product X → system checks supplier inventory → selects cheapest supplier → sends order → updates tracking → emails customer

without fighting a SaaS platform's limits.

Tradeoff: you need development skills because you are building more of the experience yourself. Toolradar

2. Saleor — best if you want a serious multi-channel platform

Saleor is another API-first platform. It uses GraphQL and is aimed at complex commerce setups. Eryx Innovations Lab

Strong points:

• Multi-channel selling
• Multiple warehouses
• Complex catalogs
• International commerce
• Strong API approach

Good if you eventually want:

• Website
• Mobile app
• Wholesale portal
• Marketplace
• B2B customers

Tradeoff: more enterprise-oriented and heavier operationally than Medusa.

3. WooCommerce — best if you want to move quickly

WooCommerce is still one of the easiest open-source routes because of its ecosystem. Open Source Groups

Advantages:

• Thousands of plugins
• Easy admin interface
• Many dropshipping extensions
• Lots of developers available
• Easy content marketing through WordPress

You can customize:

• Supplier feeds
• Order automation
• Pricing engines
• Product importers
• Custom checkout logic

The downside is architectural: WordPress plugins can become messy at scale. If you expect millions of products or highly automated workflows, a headless system is usually cleaner.

4. PrestaShop — good middle ground

PrestaShop is a traditional ecommerce platform with a mature catalog system. Toolradar

Good for:

• Large product catalogs
• European markets
• Standard dropshipping workflows
• Stores that want a built-in admin

Less ideal for:

• Highly custom application logic
• Building a unique commerce engine

5. Bagisto — underrated if you know Laravel

Bagisto is worth considering if your developers prefer PHP/Laravel. OSSAlt

Good for:

• Custom business logic
• Marketplace features
• Laravel-based integrations

My recommendation by scenario

You want a serious automated dropshipping platform:

Medusa + Next.js

Best architecture for:

• supplier integrations
• custom automation
• scaling beyond basic dropshipping

You want to launch quickly and customize later:

WooCommerce

Best if:

• you are validating products
• you want plugins
• you want less engineering upfront

You want enterprise/multi-channel:

Saleor

Best if:

• you expect complex operations
• you have developers

You are a Laravel shop:

Bagisto

For a dropshipping business specifically, I would avoid choosing based only on "store features." The important question is whether the platform lets you create a product ingestion pipeline + supplier routing engine + fulfillment automation layer. For that, a headless platform like Medusa is usually the strongest foundation. OpenSourceProjects.cc

A modern stack I would consider:

• Frontend: Next.js
• Commerce engine: Medusa
• Database: PostgreSQL
• Queue/jobs: Redis + workers
• Search: Meilisearch or Elasticsearch
• Automation: custom Node services
• Payments: Stripe
• Analytics: your own event pipeline

That gives you something closer to building your own Shopify rather than just running a dropshipping store.

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

My shortlist:

My default recommendation for a SaaS founder

I’d pick one of these two architectures:

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

Stack:

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

Use this if:

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

The key is avoiding two disconnected customer identities.

Option B — Make commerce the center

Stack:

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

Use this if:

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

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

Platforms I’d be cautious about

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

A few questions would change my recommendation:

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

Yes. If you already have an ecommerce site and want to add subscription management without rebuilding the store, there are several established options.

Two I'd look at first

Chargebee is probably the closest match if "flexible billing intervals" is a major requirement. It supports recurring billing by days, weeks, and months, plus more sophisticated setups such as multiple billing frequencies within a subscription. It also provides subscription lifecycle management, proration, customer portals, and payment integrations. Chargebee Chargebee

chargebee.com

Stripe is a good alternative if you want the subscription engine integrated directly into your existing application. Stripe supports different recurring intervals and billing-cycle anchors, and its newer flexible billing mode supports subscriptions containing items with different billing periods—for example, an annual component plus a monthly component. Stripe Docs Stripe Docs Stripe Docs

stripe.com

If you tell me what ecommerce platform your existing site uses (Shopify, WooCommerce, custom React/Next.js, Magento, etc.) and what intervals you need (e.g. every 2 weeks, 3 months, 6 months, annual, customer-selected dates), I can narrow this down to the most suitable options and explain how the integration would work.

Yes. If by prepaid subscription plans you mean customers pay upfront for a fixed period (e.g., 3, 6, or 12 months) and can then renew with minimal friction, several subscription-billing platforms support this.

• Chargebee — Supports subscription plans, prepaid credit pools, renewals, and self-service customer portals. It also supports charging future renewals in advance, which fits a prepaid model particularly well. Chargebee Chargebee API Documentation
• Recurly — Supports prepaid subscriptions and gift subscriptions, configurable billing terms, automatic renewals, and a hosted subscriber portal. Recurly Recurly Docs
• Stripe — Supports recurring subscriptions, customer self-service, saved payment methods, automatic retries, and customizable subscription schedules. It's a strong option if you want to build a very simple "Renew now" experience into your own website/app. Stripe Stripe

If your goal is specifically "one-click renewal"

A typical setup would be:

Customer buys 12-month prepaid plan → payment method is securely saved → subscription approaches expiration → customer receives "Renew for 12 months" → one click confirms renewal → payment is processed automatically.

For that particular workflow, Stripe Billing is attractive if you want maximum control over the customer experience, while Chargebee/Recurly are more purpose-built subscription-management platforms.

If you tell me what you're selling (SaaS, memberships, physical products, services, etc.) and whether you need automatic renewal or a customer-initiated one-click renewal, I can narrow it down to the most suitable tools.

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

Some common options:

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

1. Payment processor retry engine

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

• Sends emails/SMS like:

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

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

If you tell me:

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

I can suggest the most suitable setup.

Yes. A few tools fit that stack, depending on how much you want subscription billing and retention orchestration to live in one place.

Strong options

• Chargebee + HubSpot — probably the most straightforward if HubSpot is your CRM. Chargebee syncs subscription/customer data—including subscription status, plans, invoices, dues and MRR—into HubSpot, where you can segment customers and trigger marketing workflows. Chargebee HubSpot Marketplace

chargebee.com

• Recurly + Recurly Engage — more focused on subscription businesses and behavioral retention. Recurly Engage can use subscriber behavior to trigger personalized engagement, including retention, renewal and upsell campaigns, and connects with platforms such as Salesforce, Braze, Iterable and ActiveCampaign. Recurly Docs Recurly Docs
• Chargebee + HubSpot + Zapier — useful if you want more customized workflows. For example, a cancellation in Chargebee can automatically create a HubSpot engagement, allowing you to route the customer into a specific save/cancellation campaign. Zapier also supports triggers such as new subscription, cancellation and successful payment. Zapier Zapier

What a retention setup could look like

For example:

Subscription event → CRM profile → customer segment → personalized campaign

• Payment failed → identify high-value customer → send payment-recovery sequence
• Cancellation scheduled → ask cancellation reason → send appropriate save offer
• Usage declining → trigger engagement campaign
• Renewal approaching → personalized renewal messaging
• Long-term customer → upgrade/cross-sell campaign
• Recently downgraded → targeted win-back sequence

If you tell me which CRM and email platform you already use (e.g. HubSpot, Salesforce, Klaviyo, ActiveCampaign, Braze), I can narrow this to the tools that integrate with your existing stack and show you the exact architecture.

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

My practical comparison

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

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

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

What I'd choose for your setup

If your model is something like:

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

I'd start with Payhip.

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

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

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

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

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

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

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

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

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

How the main options compare

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

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

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

If your requirement is one site that sells both physical products and downloadable products without adding a separate plugin/app, the strongest fits are:

My take

Wix is probably the closest match to what you described. Wix explicitly supports physical products and digital downloads in the same store, and says you can sell both without extra platforms or plugins. wix.com Wix Help Center

Squarespace is also a genuine no-plugin option. Its native Commerce system has separate product types for physical goods and downloads; downloads are automatically fulfilled after purchase. Squarespace Help Squarespace Help

Shopify can absolutely handle both, including products combining physical and digital components, but its current documentation says digital delivery uses its free Digital Products app. So it doesn't meet your strict "without plugins" requirement as cleanly. Shopify Shopify Help Center

Bottom line: If avoiding plugins/apps is the priority, I'd narrow it to Wix vs. Squarespace. If you tell me roughly how many physical products vs. downloads you sell and whether you need subscriptions/memberships, I can compare those two specifically.

If your priorities are headless architecture + strong developer control + an editor marketers can actually enjoy, I’d put Storyblok and Sanity at the top of the shortlist.

My practical comparison

I'd lean Storyblok for your description

Storyblok is unusually well aligned with the specific tension you're describing: developers get a genuinely headless, framework-agnostic CMS while marketers get a visual editor that lets them edit the actual page rather than filling out a giant form. Its Visual Editor lets editors click elements in the rendered preview and edit the corresponding content, with changes reflected in real time. Storyblok Storyblok

It also exposes REST and GraphQL APIs and supports frameworks including Next.js, React, Vue, Nuxt, and Svelte. Storyblok

That makes the architecture roughly:

Developer:
Next.js / React → Storyblok API → structured content

Marketer:
Storyblok Visual Editor → click page → edit → preview → publish

That's a particularly nice division of responsibilities.

When I'd choose Sanity instead

Sanity becomes more compelling if you, as the developer, want the CMS itself to be a highly programmable application.

Sanity Studio is open source and React-based; you define content models in JavaScript/TypeScript and can heavily customize the editorial interface. It also supports live previews, click-to-edit and drag-and-drop visual editing. Sanity.io Sanity.io

So I'd characterize the distinction as:

• Storyblok: "Give marketers a great visual website editor, while keeping my frontend completely headless."
• Sanity: "Give me a programmable content platform that I can shape into exactly the editorial experience I want."

That's also broadly consistent with current 2026 comparisons: Storyblok tends to stand out for visual editing, while Sanity stands out for developer flexibility. Unified Platforms Lucky Media

One important consideration

If your site is primarily marketing pages, landing pages, campaigns, and reusable page sections, I'd investigate Storyblok first.

If it's more like a product/content platform with complex relationships—articles, authors, products, events, locations, taxonomies, personalization, multiple consuming applications—I'd investigate Sanity first.

And if you're talking about an enterprise with lots of governance, permissions, localization and organizational processes, I'd also put Contentful into the evaluation. ciopages.com

For your exact wording—"I'm a developer, I want headless capabilities, but marketers need an easy content editor"—Storyblok is probably the platform I'd prototype first. Not because it's universally "best," but because its core product is explicitly designed around that developer/marketer split. Storyblok

If you tell me your stack (e.g. Next.js + Vercel, Astro, Nuxt, etc.) and whether this is primarily marketing sites vs. a content-heavy application, I can narrow it down to Storyblok vs Sanity vs Contentful vs Payload and show what the actual developer architecture would look like.

When I'd choose Sanity instead

Sanity becomes more compelling if you, as the developer, want the CMS itself to be a highly programmable application.

Sanity Studio is open source and React-based; you define content models in JavaScript/TypeScript and can heavily customize the editorial interface. It also supports live previews, click-to-edit and drag-and-drop visual editing.

So I'd characterize the distinction as:

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

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

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

If your business is selling fine-art prints + high-resolution digital files + image licenses, I’d narrow it to SmugMug, Pixieset, and PhotoShelter—but they serve somewhat different business models.

My recommendation: SmugMug

SmugMug is probably the best all-in-one fit for what you described.

Its current Portfolio plan includes unlimited full-resolution JPEG storage, digital download sales, print sales, customizable website templates, watermark/theft protection, and fulfillment. The Pro tier adds multiple pricelists, packages, coupons, download limits, and other sales controls. SmugMug

Where I'd put each one

SmugMug — my pick if prints are a major revenue stream.
You get a proper branded storefront, galleries, unlimited photo storage, print fulfillment, and high-resolution digital delivery without stitching together several services. SmugMug

Pixieset — consider this if presentation/client experience is paramount.
Its Store supports both prints and digital downloads, including high-resolution downloads with automatic delivery, and you can attach digital-image licensing terms to your Store. Pixieset Pixieset Website Help Center

PhotoShelter — consider this if licensing is a major part of your business.
It's much more oriented toward professional image licensing: rights-managed licenses, usage scenarios, quote packs, and delivery of high-res files with licensing information are built into the workflow. PhotoShelter Support

Zenfolio — a strong middle ground.
It supports prints, digital downloads, price lists, automatic fulfillment, and lets you specify the resolution of digital products. It currently charges a 7% commerce fee per order. Zenfolio Support Center Zenfolio Support Center

The key question

If by "licenses" you mean something like:

"Buy this 6000×4000 file for $150 and you get personal/commercial use under these terms"

I'd lean PhotoShelter.

If you mean:

"Buy a high-res file for $75, or buy a framed 24×36 print for $400"

I'd lean SmugMug.

And if you're primarily a fine-art photographer selling beautiful prints through a polished storefront, I'd seriously compare SmugMug vs Pixieset before choosing. Current 2026 comparisons also generally distinguish SmugMug as the more commerce/archive-oriented option and Pixieset as the more delivery/gallery-oriented option. Shut Your Aperture SendPhoto

If you tell me (1) fine-art vs commercial/editorial, (2) typical file size/resolution, (3) approximate print prices, and (4) whether licensing is 10%, 50%, or most of your revenue, I can give you a much more specific platform recommendation and compare the actual fees/margins for your business.

For a creator selling both structured courses and one-off digital products (ebooks, templates, downloads, workshops, etc.), the cleanest options are usually all-in-one creator platforms rather than a general website builder with plugins. Course Profit Lab Webflow

Here’s how I’d compare them:

My practical shortlist:

• You sell a few courses + templates/downloads: choose Podia. It’s probably the closest match to “one clean creator shop.” Course Profit Lab
• Your business is becoming a marketing machine (email sequences, upsells, funnels): choose Kajabi. Course Profit Lab Mighty Networks
• Your courses are the main thing and student experience matters most: choose Thinkific or Teachable. Webflow Listicler
• You’re validating ideas and don’t want much overhead: look at Payhip. Listicler

I’d generally avoid building this on a normal site builder like WordPress/Wix/Squarespace unless you specifically want a content-heavy website and are comfortable stitching together course, checkout, and membership tools.

A good test is: can one customer buy a $29 template today, then later upgrade to a $499 course without creating a second account or entering a separate ecosystem? The platforms above are designed around that product ladder. Course Profit Lab

If you tell me your approximate setup (e.g., one flagship course + downloads, many small products, or course + community + coaching), I can narrow it to one or two choices.

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

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

shopify.com + printful.com

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

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

Example:

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

That's a very flexible catalog structure.

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

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

bigcartel.com

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

It supports:

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

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

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

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

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

fourthwall.com

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

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

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

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

What I'd pick for you

My recommendation

If you're just getting started: Big Cartel.

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

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

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

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

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

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

It’s unusually well matched to your situation because it combines the storefront + print-on-demand + fulfillment + payments + customer support rather than making you stitch several services together. It also has a no-code site builder. Fourthwall Fourthwall

My shortlist

*Etsy and payment/listing fees still apply. Printify itself can connect to Etsy and automatically send orders to production/fulfillment. Printify Printify

Why I'd pick Fourthwall for you

• No inventory: products are made after someone orders. Fourthwall
• No coding: you can build the storefront with its no-code tools. Fourthwall
• No monthly fee: there are no upfront costs or contracts. Fourthwall
• Fulfillment is handled: Fourthwall manufactures and ships products from its catalog. Fourthwall
• You set your retail price: the product's listed base cost is deducted, leaving your markup. Fourthwall
• It can handle more than T-shirts: apparel, mugs, stickers, prints, accessories, etc. Fourthwall
• It can also handle payment processing and sales-tax obligations for its catalog products, reducing the administrative burden on you. Fourthwall

When I'd choose something else

Choose Etsy + Printify if your biggest problem is finding customers, rather than building your own branded store. Etsy gives you access to an established marketplace, while Printify handles production/shipping; the two can be connected without technical experience. Printify

Choose Shopify + Printify/Printful if you already have an audience and want a more conventional ecommerce business that you'll potentially expand substantially. Printify supports Shopify and many other sales channels. Printify

For your specific situation, though, I wouldn't start with Shopify. You're effectively paying for additional flexibility and assembling integrations before you know whether you need them.

My starting stack would be: Fourthwall → your designs → connect your domain → launch 5–10 products → order samples → start selling.

If you tell me what kind of merch you're making (e.g. shirts, art prints, stickers, handmade/custom items) and roughly how many designs you expect to launch with, I can narrow this down further and compare the actual per-sale economics.

Yes. If you already have a website and want merch to feel like a native part of it, there are a few good options.

My shortlist

• shopify.com — probably the best-known option. You keep your existing site, embed products/collections and an embedded cart, while Shopify handles inventory, payments, checkout, orders, etc. Shopify specifically supports adding it to non-Shopify sites. Shopify Shopify Help Center
• ecwid.com — arguably the most purpose-built for your exact situation. You can embed an entire store, individual products, or Buy Buttons into an existing site, with cart and checkout integrated into the experience. Ecwid Help Center Ecwid Help Center
• Fourthwall — worth considering if you're a creator/artist and want merch fulfillment plus a creator-oriented storefront. I'd lean toward Shopify/Ecwid if your priority is making the store feel like a seamless extension of an existing branded site.

What I'd choose

If your requirement is:

“I don't want to rebuild my website. I just want a /shop page where people can browse merch, add multiple things to a cart, and check out without feeling like they've been sent somewhere else.”

I'd look at Ecwid first, then Shopify Buy Button.

Ecwid is particularly interesting because you can embed the whole catalog and shopping cart directly into your existing site, while Shopify's Buy Button gives you a very mature ecommerce backend and lets you embed products/cart on virtually any site. Ecwid Help Center Shopify

If you tell me what your existing site is built with (Webflow, Squarespace, Wix, WordPress, custom React/HTML, etc.) and whether you're making/fulfilling the merch yourself or want print-on-demand, I can tell you which setup I'd use and roughly what the customer checkout flow would look like.

For a small fashion label, I’d separate “storefront” from “production/inventory system.” Your custom tags and production runs make SKU structure and manufacturing tracking more important than simply having a pretty online store.

My shortlist

My recommendation: start with Shopify if you're launching a relatively small collection, but structure your SKUs properly from day one. Shopify can be your customer-facing store, while a dedicated inventory/production layer can be added as your manufacturing gets more complicated.

If you're already dealing with cut-and-sew production, multiple factories, fabric/trims, BOMs, production batches, and work-in-progress, I'd seriously consider Cin7 Core + Shopify from the outset. Cin7 supports size grids, per-size barcodes, ecommerce variants, purchase orders, bills of materials, production, and contract manufacturing. Cin7 Cin7

Why I'd lean Cin7 for your particular use case

Imagine you have:

Jacket — Black — Medium

You may actually need to track:

• Finished-garment SKU
• Size/color variant
• Fabric lot
• Labels/tags
• Zippers/buttons/trims
• Factory
• Production run
• Quantity ordered
• Quantity completed
• WIP
• Finished inventory
• Cost per unit

That's where ordinary ecommerce inventory starts becoming inadequate. Cin7 is designed to track raw materials, WIP and finished goods, and its manufacturing functionality supports BOMs and production scheduling. Cin7 Cin7

Your custom tags are actually important

I'd design your SKU system before choosing the software.

For example:

JKT-01-BLK-S

JKT-01-BLK-M

JKT-01-BLK-L

Then keep production run/batch information separate from the SKU:

• SKU: JKT-01-BLK-M
• Production run: RUN-2026-001
• Quantity: 75
• Factory: Factory A
• Label version: LBL-03
• Cost: $XX
• Production date: September 2026

That way, if you reorder the same jacket six months later, the SKU doesn't change just because it's a new production run.

For apparel specifically, Lightspeed also treats each size/color combination as its own SKU, while Squarespace supports individual SKUs for variants such as size and color. Lightspeed Retail Squarespace Help

What I'd choose at different stages

If you're launching 5–20 styles:
Shopify. Keep it simple and use an inventory/manufacturing app only when necessary.

If you're launching with a real production operation:
Shopify + Cin7 Core. This gives you the polished ecommerce storefront plus a much more serious inventory/production backbone. Cin7 specifically integrates with Shopify and other ecommerce channels. Cin7

If the website itself is the priority and production is extremely simple:
Squarespace Commerce. It supports unlimited SKUs and multidimensional variants, so it's perfectly capable of a small clothing catalog. Squarespace

If you expect boutiques/wholesale + your own physical shop:
I'd look harder at Cin7 or Lightspeed, because inventory across multiple channels becomes increasingly important.

If you tell me roughly how many styles you're launching, how many sizes/colors per style, whether you're manufacturing yourself or using a factory, and whether you'll sell wholesale, I can map out the exact SKU + production-run structure I'd use for your brand.

What I'd choose at different stages

If you're launching 5–20 styles:
Shopify. Keep it simple and use an inventory/manufacturing app only when necessary.

If you mean a creator selling digital products worldwide—courses, ebooks, templates, software, memberships, etc.—the simplest category to look at is a Merchant of Record (MoR). The MoR becomes the seller to the customer and handles indirect-tax collection/remittance, which removes much of the VAT/GST/sales-tax setup from you.

Strong options

Paddle says it supports 200+ countries/territories and handles tax compliance without requiring you to register individually for VAT/GST/sales tax in those markets. Paddle Developer Docs Paddle Developer Docs

Lemon Squeezy similarly acts as the MoR, handles sales tax/VAT, and supports 130+ currencies. One nuance: purchases are ultimately processed in USD, with the displayed local currency converted to USD at checkout. Lemon Squeezy Docs Lemon Squeezy Docs Lemon Squeezy Docs

Gumroad is particularly hands-off: it says it automatically handles worldwide sales-tax collection and remittance. However, physical products are a different story—EU physical shipments can still have import VAT assessed by customs on arrival. Gumroad

What I'd look at first

For a creator who wants “I upload my product, connect my payout account, and don't want to become a part-time international tax administrator,” I'd compare Lemon Squeezy and Paddle first.

One important distinction: VAT/tax ≠ customs. If you're selling physical products and shipping internationally, you need a platform that handles duties/import taxes and shipping/customs workflows; a digital-product MoR isn't automatically a customs solution.

If you tell me whether you're selling digital products, physical products, or both, I can narrow this down to the most appropriate 2–3 platforms and compare fees, payouts, currencies, and customs handling.

For a small merch business selling both at live events and online, I’d narrow the search to Shopify + Shopify POS and Square + Square Online first. They both keep inventory/orders connected across physical and online sales, which is particularly important when you’re moving the same limited stock between events and your web store. Shopify Square

The two I'd seriously evaluate

Shopify explicitly positions its POS around selling at events, in stores, and online, with inventory, orders, customers and payments managed from the same back office. Shopify Square similarly syncs online and in-person orders and inventory, and has inventory tools designed for physical-goods sellers. Square Square

How I'd think about the choice

If your website is going to be a major part of the business → Shopify.

For a merch company, Shopify's ecommerce strength is useful if you eventually want things like collections, product variants, discount campaigns, email/marketing integrations, social selling, sophisticated product pages, and a larger app ecosystem. Its POS is built into the same commerce platform rather than being an unrelated POS bolted onto your website. Shopify Shopify

If most of your revenue currently happens at concerts, festivals, markets, pop-ups, etc. → Square deserves a very close look.

Square has a particularly low-friction POS setup, and its inventory system can keep stock synchronized between your physical and online channels. It also has a free POS tier, which can make experimenting with it relatively inexpensive. Square Square

One important thing for custom merch

I'd pay more attention to inventory and product variants than to flashy POS features.

For example, suppose you have:

Band T-shirt → Black → Small / Medium / Large / XL

and only 50 total shirts.

You want the system to understand those as individual SKUs and automatically reduce the correct size/color inventory when someone buys one at an event or online. You also want to be able to allocate/track inventory between your warehouse, upcoming events, and online sales.

That's one of the first things I'd test in a demo. Shopify specifically supports inventory across locations including temporary/pop-up locations, while Square supports real-time stock across locations and channels. Shopify Square

I'd probably shortlist three

• Shopify + Shopify POS — if you're building an ecommerce-led merch brand.
• Square + Square Online — if you're a lean team where event selling and simplicity are paramount.
• Lightspeed Retail — worth investigating if your catalog/inventory becomes substantially more complicated, although it's generally a heavier retail system. Current comparisons describe it as stronger for complex inventory and established multi-location retail. Shopify Shopify

I wouldn't start with WooCommerce + a separate POS unless you already have a strong reason to be on WordPress. The additional integration/maintenance burden isn't especially attractive for a small team when Shopify and Square can keep the core commerce data unified. Shopify

If you tell me roughly (1) annual sales, (2) number of SKUs/variants, (3) how many live events you do per month, (4) whether you already have a website, and (5) whether you need preorder/customization for merch, I can give you a much more specific Shopify-vs-Square comparison, including actual monthly costs and event hardware.

How I'd think about the choice

If your website is going to be a major part of the business → Shopify.

For a merch company, Shopify's ecommerce strength is useful if you eventually want things like collections, product variants, discount campaigns, email/marketing integrations, social selling, sophisticated product pages, and a larger app ecosystem. Its POS is built into the same commerce platform rather than being an unrelated POS bolted onto your website. Shopify Shopify

If most of your revenue currently happens at concerts, festivals, markets, pop-ups, etc. → Square deserves a very close look.

Square has a particularly low-friction POS setup, and its inventory system can keep stock synchronized between your physical and online channels. It also has a free POS tier, which can make experimenting with it relatively inexpensive. Square Square

One important thing for custom merch

I'd pay more attention to inventory and product variants than to flashy POS features.

For example, suppose you have:

Band T-shirt → Black → Small / Medium / Large / XL

and only 50 total shirts.

You want the system to understand those as individual SKUs and automatically reduce the correct size/color inventory when someone buys one at an event or online. You also want to be able to allocate/track inventory between your warehouse, upcoming events, and online sales.

That's one of the first things I'd test in a demo. Shopify specifically supports inventory across locations including temporary/pop-up locations, while Square supports real-time stock across locations and channels.

I'd probably shortlist three

For an enterprise team with complex integrations, thousands of SKUs, multiple markets, and likely ERP/PIM/CRM dependencies, I would avoid choosing based on storefront features alone. The key decision is whether you need a composable commerce architecture or a more integrated enterprise suite. Enterprise platforms differ significantly in how they handle catalogs, pricing engines, integrations, localization, and operational governance. CIOPages

My shortlist would be:

Based on your description, I would typically evaluate in this order

1. commercetools — if you have a mature engineering/platform team and want maximum flexibility across markets, brands, channels, and integrations. Shopify
2. SAP Commerce Cloud — if your backbone is SAP ERP and commerce needs to closely mirror enterprise product, pricing, inventory, and customer processes. Shopify
3. Adobe Commerce — if you need deep customization and own a lot of unique commerce logic. CIOPages
4. Salesforce Commerce Cloud — if customer data, CRM workflows, and Salesforce ecosystem integration are central. CIOPages
5. Shopify Plus — if your complexity is more operational scale than unusual business logic. Shopify

For a thousand-SKU-plus enterprise stack, I would specifically check:

• Catalog model

• Can it handle variants, bundles, configurable products, regional assortments, and multiple catalogs?
• Pricing

• Contract pricing, customer-specific pricing, currencies, promotions, rebates, and negotiated terms.
• Integration architecture

• ERP (SAP/Oracle/Dynamics/NetSuite), PIM, OMS, WMS, tax, payments, marketplaces.
• Multi-market operations

• Languages, currencies, taxes, compliance, inventory allocation, localized checkout.
• Deployment model

• SaaS convenience vs. composable flexibility.
• Governance

• Roles, approvals, audit trails, release processes, environment management.

A common enterprise pattern today is:

• PIM for product truth (e.g., product data)
• ERP for inventory/financial truth
• Commerce platform for transactions, pricing, and customer experience
• CMS/search/personalization as separate services in a composable stack

If you share:

1. B2B, B2C, or both
2. Current ERP/PIM (SAP, Oracle, Dynamics, NetSuite, Akeneo, etc.)
3. Approximate SKU count (5k vs 500k changes the answer)
4. Number of markets/storefronts
5. Whether you have an internal engineering team

…I can narrow this to a more realistic 2–3 platform shortlist.

For a large omnichannel retailer with complex promotions and pricing rules across multiple countries, channels, currencies, and customer segments, the platform choice usually depends on your existing retail stack. The main enterprise-grade options are:

From a product management perspective, the shortlist usually looks like this:

If you operate 10+ markets with thousands of SKUs and need one global pricing brain:

• SAP Omnichannel Promotion Pricing is often considered when SAP is the system of record. It provides a central repository and calculation service so web, POS, and other channels can apply the same promotion logic. SAP Help Portal

If pricing strategy is a competitive advantage (frequent repricing, elasticity, optimization):

• Consider a dedicated pricing optimization platform such as Competera or Oracle Retail, often integrated with commerce and ERP systems. Competera Oracle

If you need a composable/headless architecture:
Look for:

• API-first price calculation
• Real-time promotion evaluation
• Market-specific rule inheritance
• Currency/tax localization
• Customer segmentation
• Coupon and loyalty integration
• Promotion conflict resolution
• Experimentation/simulation before launch

Key capabilities I would require in an RFP

1. Promotion rule engine

• Buy X get Y
• Mix-and-match bundles
• Threshold discounts
• Basket-level promotions
• Loyalty/member pricing
• Personalized offers
• Global governance

• Global templates with local overrides
• Market-specific calendars
• Regional approval workflows
• Audit history/versioning
• Real-time calculation

• Same price outcome in:

• ecommerce
• mobile app
• POS
• marketplace channels
• customer service tools
• Commercial controls

• Margin protection
• Promotion stacking rules
• Funding attribution
• Supplier-funded promotions
• Forecasting and simulation

For a large omnichannel retailer, my initial evaluation would typically put SAP Omnichannel Promotion Pricing, Oracle Retail, and Dynamics 365 Commerce into the enterprise shortlist, then decide based on the existing ERP, commerce platform, and pricing operating model. SAP Microsoft Learn Oracle

For an enterprise with highly diverse product types and a need for flexible catalog modeling, I’d shortlist commercetools first, particularly if you’re comfortable with a composable/headless architecture.

Why commercetools fits

• Flexible product types: Product Types act as reusable templates of attributes, and you can create different structures for fundamentally different products. commercetools Documentation commercetools Documentation
• Rich variants: Products can have variants representing actual SKUs, with attributes that can live at either product or variant level. commercetools Documentation commercetools Documentation
• Complex catalogs: Its current Product Catalog offering explicitly supports complex assortments including variants, bundles, configurable products, and both digital and physical products. Commercetools Commercetools
• Extensibility: Product Types can define custom attributes, while Custom Objects can represent related business data that doesn't naturally fit the standard model. commercetools Documentation
• Multi-brand/channel use: The catalog is designed to reuse product information across brands, regions and channels rather than duplicating it. Commercetools

How I'd compare the main options

Adobe Commerce is also quite flexible: it supports arbitrary product attributes and attribute sets, configurable products, and multiple product types. Experience League Experience League

The key architectural distinction: if your catalog is essentially the product-data model itself—for example, you sell apparel, industrial equipment, subscriptions, spare parts, and digital products with very different schemas—I would investigate commercetools first. If you want a more all-in-one commerce platform and the catalog is primarily variations of conventional retail products, Adobe Commerce may be a more natural fit.

If you tell me whether you're B2B, B2C, or both, and roughly how many product types/SKUs you have, I can give you a more concrete comparison of commercetools vs. Adobe Commerce vs. Salesforce Commerce Cloud.

For a retail chain with many stores and complex fulfillment rules, I’d focus on platforms that have a strong OMS + distributed inventory + store fulfillment layer, not just basic “pickup in store.”

The two I’d investigate first

Salesforce Commerce + Order Management is particularly relevant if you need sophisticated orchestration across stores, DCs and digital channels. Salesforce supports location-level inventory, BOPIS, ship-from-store and other fulfillment modes; its POS architecture also supports different fulfillment methods at the individual line-item level. Salesforce Salesforce

Adobe Commerce + Store Fulfillment is another strong option. Adobe's tooling supports pickup-location selection, split orders, automated inventory sourcing and store-associate workflows covering picking, staging and customer handoff. Adobe for Business Experience League

Shopify Plus has become considerably more capable for omnichannel retail. It supports store transfers, custom order-routing rules and, as of 2026, a Shopify Plus/Enterprise capability allowing customers to combine shipped and store-pickup items in one checkout. Shopify Help Center Shopify Shopify Changelog However, for unusually complex allocation/orchestration requirements, I'd scrutinize whether Shopify's native model plus apps is sufficient before committing.

Manhattan Active is worth considering when fulfillment complexity itself is a primary requirement. Its store-fulfillment offering combines real-time store inventory, mobile associate workflows and intelligent orchestration. Manhattan

What I'd test in an RFP

Don't just demo “Buy Online, Pick Up In Store.” Give each vendor scenarios such as:

• Customer orders 8 items; 3 are available at Store A, 2 at Store B and 3 at a DC.
• One item becomes unavailable after checkout.
• Customer wants pickup for some items and shipping for others.
• Inventory needs to be reserved while another order is being processed.
• Store A can fulfill an order, but Store B is closer to the customer.
• Customer changes pickup store after ordering.
• Curbside pickup vs. in-store pickup.
• Partial pickup, partial cancellation and substitutions.
• Returns at a different store from the fulfillment location.
• Ship-from-store competing with BOPIS for the same inventory.
• Transfers between stores when the designated pickup store is out of stock.

Those scenarios will reveal much more than a standard BOPIS demo.

If your chain is enterprise-scale and fulfillment complexity is the primary criterion, Salesforce Commerce/Order Management and Adobe Commerce are the two I'd put through the deepest technical evaluation; Shopify Plus is particularly worth evaluating if implementation speed and ecosystem flexibility are major considerations. That's a description of their documented capabilities rather than an overall ranking.

Shopify Plus has become considerably more capable for omnichannel retail. It supports store transfers, custom order-routing rules and, as of 2026, a Shopify Plus/Enterprise capability allowing customers to combine shipped and store-pickup items in one checkout. help.shopify.com shopify.dev changelog.shopify.com However, for unusually complex allocation/orchestration requirements, I'd scrutinize whether Shopify's native model plus apps is sufficient before committing.

Manhattan Active is worth considering when fulfillment complexity itself is a primary requirement. Its store-fulfillment offering combines real-time store inventory, mobile associate workflows and intelligent orchestration.

What I'd test in an RFP

Don't just demo “Buy Online, Pick Up In Store.” Give each vendor scenarios such as: