Answers that do not mention BigCommerce

Yes. If you sell both one-time digital downloads and recurring subscriptions, there are a few good fits, but they optimize for different kinds of businesses.

My shortlist

• Lemon Squeezy — best if your startup is software/SaaS or sells sophisticated digital products. It supports one-time downloads, monthly/yearly subscriptions, trials, upgrades/downgrades, license keys, and secure file delivery. It also acts as a merchant of record, handling sales tax/VAT and related compliance. LemonSqueezy LemonSqueezy
• Podia — best for a traditional creator business. It combines downloads, memberships/subscriptions, courses, coaching, community, email marketing, storefronts, bundles and upsells. Podia
• Patreon — best if recurring fan membership is the core business. It now supports one-time digital products alongside memberships, so you can sell downloads to non-members and give products to members as a perk. Patreon Patreon Help Center
• Gumroad — best for simplicity. It's easy to start selling digital products and memberships, but I'd look at the economics carefully as revenue grows. Podia

What I'd pick for a startup

If by "startup" you mean you're building a real product business rather than primarily a personality/fan business, I'd put Lemon Squeezy at #1.

The particularly attractive combination is:

one-time download → subscription → automatic recurring billing → tax handling → secure delivery

That means you don't necessarily need separate systems for your $29 downloadable product and your $15/month subscription. Lemon Squeezy explicitly supports both one-time and recurring charges within its product/payment infrastructure. LemonSqueezy LemonSqueezy

If your downloads are things like ebooks, templates, presets, courses, or educational material and you want a polished creator storefront/community/email ecosystem, I'd lean Podia instead. Podia

If you tell me what you're selling (e.g. templates, software, courses, AI prompts, design assets, etc.) and roughly your monthly revenue, I can narrow it down to the best 2–3 and compare fees, subscriptions, tax handling, customer accounts, affiliates, and API flexibility.

For a one-person print-on-demand (POD) shop, the most cost-effective choice is usually not the platform with the lowest monthly fee—it’s the one that minimizes your time, setup headaches, and wasted costs while you test whether your designs sell.

My ranking for a solo beginner:

Tee Verdict WooCommerce## My recommendation for a one-person POD business

Stage 1: Start with Etsy + a POD supplier

Use:

• Etsy storefront
• Printify or Printful for fulfillment

Why:

• No monthly store bill while you’re validating ideas
• Etsy already has shoppers searching for products
• You avoid spending weeks building a website before knowing if anyone buys

The downside: you pay marketplace fees and you don’t fully own the customer relationship. Tee Verdict

A realistic lean setup:

• Etsy: $0 upfront
• POD account: $0 upfront
• Design tools: $0–$15/month
• Domain/email: optional later

You can test dozens of designs without committing to a monthly ecommerce subscription.

Stage 2: Move winners to Shopify

Once you have:

• repeat buyers,
• proven designs,
• roughly consistent monthly sales,

then a Shopify store starts making more sense because you control branding, email marketing, upsells, and customer data. Shopify’s advantage is simplicity: hosting, checkout, security, and POD integrations are handled for you. Bootstrapping Ecommerce Merch Titans

When WooCommerce makes sense

Choose WooCommerce if:

• you already know WordPress,
• you enjoy tinkering,
• you want maximum control.

The software itself is free, but you’ll pay for hosting, themes, plugins, and maintenance. WooCommerce For a solo creator whose time is limited, the hidden cost is often your hours.

What I would avoid at the beginning

• ❌ Paying $100+/month for ecommerce apps before you have sales
• ❌ Building a custom website
• ❌ Buying large quantities of inventory (defeats the POD advantage)
• ❌ Running paid ads before you know which designs convert

Simple beginner stack I’d choose

First 90 days:

• Etsy
• Printify or Printful
• Canva (or another design tool)
• Google Sheets for tracking products/profits

After traction:

• Shopify + POD integration
• Email list
• Your own domain

For a solo POD seller starting from zero, I’d put Etsy first for validation, Shopify second for scaling.

If you tell me what you’re selling (shirts, mugs, posters, stickers, niche gifts, etc.) and whether you already have an audience, I can suggest a more specific setup.

If your priorities are self-hosting + open source + full control over the code + deep customization, I’d shortlist these:

My recommendation: Medusa

Medusa would be my first choice if you're comfortable developing the store yourself.

It's built specifically as a customizable commerce engine rather than a rigid "store builder." Its core commerce modules are open source under the MIT license, and you can self-host them. GitHub GitHub

You can build something like:

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

and customize essentially every layer:

• Product/catalog model
• Pricing and promotions
• Cart and checkout
• Customer accounts
• Orders
• Inventory
• Shipping
• Payments
• Admin functionality
• Custom APIs
• Marketplace functionality
• B2B functionality
• Integrations with your own systems

The big advantage is that you're not fighting against WordPress or a prebuilt theme architecture. Medusa gives you commerce primitives and lets you build the experience you actually want.

medusajs.com · github.com

When I'd choose something else

Saleor is probably my #2. It's particularly attractive if you want a headless, API-first architecture and like GraphQL. Saleor provides the commerce API, dashboard, and an open-source Next.js/React storefront, and can be run locally/self-hosted. Saleor GitHub

saleor.io · github.com

Bagisto is a great choice if you're a Laravel/PHP developer. It's MIT-licensed, self-hostable, has a conventional admin/store setup, and supports headless storefronts with Vue/React/Next.js. GitHub GitHub

bagisto.com · github.com

Sylius is the one I'd investigate for a highly specialized business where the commerce rules themselves are unusual. It's a Symfony-based framework rather than merely a finished store, and is MIT licensed. GitHub

sylius.com · github.com

WooCommerce is still the pragmatic option if you want to get a normal store running quickly and take advantage of the enormous WordPress/plugin ecosystem. But if by "customize fully" you mean I want to fundamentally control the architecture, I'd prefer Medusa/Saleor/Sylius.

What I'd pick

If I were starting a new project today:

• Custom React/Next.js store: Medusa
• GraphQL/API-first architecture: Saleor
• Laravel developer: Bagisto
• Complex/unique business rules: Sylius
• Normal store, minimal development: WooCommerce

For your wording specifically — "host myself and customize fully" — I'd start with Medusa.

If you tell me what you're selling, expected number of products/orders, and your preferred tech stack (or whether you're non-technical), I can narrow this down to one and give you a recommended architecture/hosting setup.

Bagisto is a great choice if you're a Laravel/PHP developer. It's MIT-licensed, self-hostable, has a conventional admin/store setup, and supports headless storefronts with Vue/React/Next.js. GitHub GitHub

bagisto.com · github.com

Sylius is the one I'd investigate for a highly specialized business where the commerce rules themselves are unusual. It's a Symfony-based framework rather than merely a finished store, and is MIT licensed.

For a mobile app storefront, the “most developer-friendly” commerce API depends on whether you want a full commerce backend, a headless storefront, or just payments. The strongest options today are usually:

My shortlist by app type

1. Consumer shopping app (Amazon-style storefront)

Pick Shopify.

Why:

• Product catalog, search, collections, carts are already modeled.
• Checkout is handled securely through Shopify’s checkout stack.
• You avoid building tax, payment, order, and fulfillment flows from scratch. Shopify Shopify

Typical stack:

• iOS: Swift + Shopify Storefront API
• Android: Kotlin + Shopify Storefront API
• Cross-platform: React Native + Shopify APIs

2. Marketplace app (many sellers)

Consider Stripe Connect + a commerce backend.

Why:

• Strong payment routing and seller payouts.
• Better fit when you need your own seller model, commissions, onboarding, and custom workflows.

3. Retail app tied to physical stores

Pick Square.

Why:

• Catalog, inventory, orders, payments, and customer APIs are already connected.
• Good fit for omnichannel apps where stores already use Square. Square Square

4. You want maximum control

Pick Medusa (or another headless commerce backend).

Why:

• Your mobile app becomes the primary experience.
• You own the data model and integrations.
• More engineering effort, but fewer platform constraints. Medusa Docs

If I were choosing for a new mobile storefront

• Fastest MVP: Shopify
• Best developer ergonomics: Shopify or Stripe (depending on whether you need commerce vs payments)
• Most customizable long-term: Medusa
• Best retail/POS integration: Square

A few details would change the recommendation: are you building a single-brand store, a marketplace with multiple sellers, or a platform where merchants plug their own stores into your app? Also, are you using native iOS/Android, React Native, or Flutter?

If your priority is “I’m a solo entrepreneur and I never want to manage servers”, I’d pick Shopify + a print-on-demand provider such as Printful.

Why Shopify is my pick

• Fully hosted: Shopify handles the servers, updates, security, SSL, bandwidth, and infrastructure. Shopify Shopify
• Good for a one-person business: Shopify specifically positions its Basic plan for solo entrepreneurs. It's currently $29/month when billed annually ($39 month-to-month). Shopify
• Excellent POD integration: Printful can automatically receive Shopify orders, produce the shirt, package it, and ship it to the customer. Printful Printful Help Center
• You keep control of your brand: Your own domain, storefront, pricing, customer experience, and marketing rather than being dependent on a marketplace.
• Scales without a rewrite: You can start with a handful of shirts and add products, sales channels, apps, and staff later.

The setup I'd use

Customer → Shopify → Printful → customer

You create the designs and listings. Shopify handles the storefront and checkout. Printful handles production and fulfillment. You concentrate on designs, marketing, and customer relationships.

shopify.com
printful.com

What about Etsy?

I'd consider Etsy + Printful if your biggest problem is getting your first customers, because Etsy has an existing buyer audience. But if you're trying to build a recognizable t-shirt brand rather than just sell designs, I'd choose Shopify. Printful

What I'd avoid

WooCommerce would not be my first choice for you. It's powerful, but compared with Shopify you're taking on more hosting/plugin/update/maintenance decisions—the opposite of your stated goal.

Bottom line:
Shopify Basic + Printful is probably the cleanest “solo founder, no servers, minimal technical maintenance” setup.

If you tell me your monthly budget and whether you're printing the shirts yourself or using print-on-demand, I can narrow it down to the best 2–3 platforms for your exact situation.

For a small subscription-based craft kit business, I’d prioritize platforms that handle:

• recurring billing and failed payments
• skipping/pausing/swapping subscriptions
• build-your-own or themed kit options
• customer portals
• inventory timing (monthly drops, seasonal kits)
• email/retention integrations

The “best” choice depends on how subscription-first your business is.

Best overall: Shopify + a subscription app

Best for: a craft brand that wants strong branding, marketing, and room to grow.

shopify.com is usually the safest starting point because it has a large ecosystem for themes, payments, fulfillment, analytics, and apps. For subscriptions, many merchants add specialized tools rather than relying only on basic built-in options. Shopify Parrot Creative

Pros

• Excellent storefront design for visually appealing craft products
• Strong inventory and order management
• Lots of integrations (email marketing, shipping, reviews, loyalty)
• Easy to expand from subscriptions into one-off kits, gifts, and wholesale

Cons

• Advanced subscription features may require paid apps
• App costs can add up as your subscriber base grows Parrot Creative

Good fit if: your vision is “a craft brand with subscriptions,” not just a subscription box.

Best subscription-first option: Subbly

Best for: a business where the subscription itself is the main product.

subbly.co is built specifically around subscription commerce, with subscription management, billing tools, and subscription-focused workflows included rather than assembled through multiple plugins. Subbly

Pros

• Subscription features are core, not an add-on
• Better suited for monthly craft boxes, memberships, and recurring plans
• Easier management of subscriber changes and recurring orders
• Less plugin juggling Subbly

Cons

• Smaller general ecommerce ecosystem than Shopify
• May be less ideal if you later become a large multi-channel retail brand

Good fit if: “Every month we ship a curated craft kit” is the heart of your business.

Best for maximum customization: WooCommerce

Best for: someone comfortable with WordPress or who wants full control.

woocommerce.com gives you deep flexibility, but subscriptions usually require extensions and more hands-on maintenance. Shopify

Pros

• Highly customizable
• Full ownership of your site and data
• Great for unusual subscription models

Cons

• More technical setup
• More responsibility for hosting, updates, and plugin compatibility

Good fit if: you already have a WordPress site or have technical help.

My recommendation for a craft kit startup

I’d choose:

1. Shopify + subscription app → if you want a polished brand, Instagram/TikTok marketing, and future growth.
2. Subbly → if your entire business is a monthly craft kit subscription and you want the simplest subscription operations.
3. WooCommerce → if customization matters more than ease of management.

For a craft kit specifically, I’d lean slightly toward Shopify unless your model is purely “monthly box only.” Craft businesses often benefit from selling:

• individual kits
• gift subscriptions
• seasonal collections
• add-ons (tools, supplies, refills)
• limited-edition drops

A couple of questions would narrow this down:

• Are you planning monthly recurring boxes only, or also one-time craft kits?
• Will customers choose their own kits (“build your box”) or receive a curated surprise box?
• Roughly how many subscribers do you expect in your first year (50, 500, 5,000+)?

If your priority is selling high-resolution digital files + physical prints with automated fulfillment, I’d shortlist Pic-Time, Pixieset, and SmugMug. For most photographers, my pick would be Pic-Time.

My ranking

1. Pic-Time — best overall for a print-focused photographer

• Strong high-resolution download selling, including individual files, tiered/volume pricing, and downloadable packages. Pic-Time Help Center Pic-Time Help Center
• Particularly good if you want to combine digital downloads + prints in the same product/package. Pic-Time Help Center
• Offers automated print fulfillment and is designed around turning galleries into sales.
• Its sales/marketing automation is a major differentiator if you want the platform to actively encourage repeat print purchases. FindMe Photo
• Pixieset — best for simplicity and an easy client experience

• Excellent native digital downloads: you can sell single images or entire galleries at your chosen resolution. Pixieset Help Center
• Digital files are delivered automatically after payment, and high-resolution downloads aren't watermarked. Pixieset Help Center
• Automatic print fulfillment sends orders to partner labs for printing, packaging, and shipping. Pixieset Help Center
• Particularly attractive if you're already using Pixieset galleries.
• Paid plans currently advertise 0% store commission; free accounts have a 15% commission. Pixieset
• SmugMug — best if you're building a broader photography storefront

• Worth considering if you want a more customizable public-facing photography site and print business.
• It's especially compelling when print sales are a major revenue stream, rather than simply an add-on to client galleries.

What I'd choose for your business

If you're selling fine-art/landscape prints plus downloadable high-res files to the general public, I'd lean:

Pic-Time → best fit

If you're primarily a portrait/wedding/event photographer selling galleries, downloads, and occasional prints:

Pixieset → probably the easiest choice

If you're building a large photography portfolio/store with prints as a substantial business line:

SmugMug → worth the extra consideration

One important distinction: if by "high-resolution downloads" you mean selling the actual full-resolution master/JPEG files, rather than client-sized exports, both Pic-Time and Pixieset can handle that. Pic-Time also lets you define different resolution products and terms, while Pixieset lets you select the download resolution for each digital product. Pic-Time Help Center Pixieset Help Center

For a photographer selling both $20–$100 digital files and $100–$1,000+ wall art/prints, I'd start with Pic-Time. It has the strongest combination of digital-product flexibility, print sales, fulfillment, and sales automation.

If you tell me what kind of photography you sell (landscape, wedding, sports, fine art, etc.) and your typical print price, I can also compare Pic-Time vs Pixieset vs SmugMug on fees, lab quality, margins, storage, download limits, and print fulfillment and give you a concrete recommendation.

If easy spreadsheet/CSV importing is a major priority for a neighborhood gift shop, I’d shortlist these:

• Shopify — best overall. Its built-in product importer handles CSV files, including bulk product details, variants, inventory, and images. You can also use Google Sheets or Excel to prepare the file. Shopify Help Center Shopify Help Center
• Square Online — best if you also run a physical shop with Square POS. Square lets you bulk-add or update your item catalog using Excel or CSV spreadsheets, and it has column-matching during import. Square
• WooCommerce — best for flexibility. It has a built-in CSV importer/exporter and works well with Google Sheets, Excel, Numbers, etc. It's particularly powerful if you have unusual product fields, although setting up WordPress/WooCommerce is more involved. WooCommerce WooCommerce

My pick for your shop

Shopify if you're primarily looking for a simple online store and want importing to be painless.

Square Online if you already use Square at the physical checkout. Keeping your in-store and online catalog connected can be more valuable than having the absolute best standalone ecommerce importer.

One caveat: Shopify's native CSV format is fairly structured, so if your current spreadsheet is something informal like:

Product | Price | Cost | SKU | Category | Stock

you'll probably need to rearrange the columns before importing. Shopify does provide a sample/template CSV. Shopify Help Center

If you tell me what your current spreadsheet columns look like (or paste 5–10 sample rows), I can tell you which of Shopify, Square, or WooCommerce would require the least cleanup.

Yes. For an artisan selling a mix of ready-to-ship products, pre-orders, and genuinely made-to-order/custom pieces, I’d lean toward Shopify rather than a very simple artist-focused platform.

Best fit: Shopify

Shopify is particularly strong because you can combine ordinary inventory with pre-orders and made-to-order products. Shopify supports pre-orders through apps, including options for full, partial, or no payment up front. Shopify Help Center

Its App Store currently has 100+ pre-order apps specifically supporting made-to-order products, so you have quite a bit of flexibility around how you communicate production/fulfillment timing. Shopify App Store Shopify App Store

A typical setup could be:

• Ready-made item: "In stock — ships in 1–2 business days"
• Made-to-order item: "Made especially for you — ships in 2–3 weeks"
• Pre-order: "Pre-order now — estimated shipping November 15"
• Custom item: customer selects options such as color, size, engraving, etc., with a longer production window.
• Limited release: accept orders until a particular date, then make the batch.

That makes Shopify a good choice if your business is going to grow beyond a small catalog.

Simpler option: Big Cartel

Big Cartel is appealing for a small artisan because it's deliberately aimed at independent makers and has a much simpler storefront experience. Big Cartel

But there's an important catch: Big Cartel doesn't have a dedicated pre-order product setting. Its own documentation says you can essentially handle pre-orders by putting the pre-order status and expected ship date in the product description. Big Cartel

So I'd choose Big Cartel if your needs are mostly:

"Buy this handmade item; it takes me 2–3 weeks to make it."

I'd choose Shopify if you need:

"Buy this normally stocked item, pre-order this upcoming item, or configure this custom item—and each has different fulfillment rules."

My recommendation

One thing I'd not optimize for is a generic "delivery date" feature. For an artisan, what you really want is production/processing lead time attached to the product or variant, because shipping time is separate from the time you need to actually make the thing.

If you tell me roughly what you make (jewelry, ceramics, furniture, clothing, art, etc.), how many products you expect, and whether customers need to customize them, I can narrow this down to 2–3 platforms and tell you which one I'd personally pick.

For a small handmade goods shop on a tight budget, I’d start with one of these:

Best overall free/cheap choices

1. squareup.com — best “just get selling” option

Cost: Free plan available (you pay payment processing fees when you make sales). Shopify
Best for: Handmade sellers with a small catalog, local customers, craft fairs, markets, or anyone who wants the simplest setup.

Pros

• No monthly fee to start
• Easy product photos, inventory, checkout, shipping/pickup options
• Works well if you also sell in person using Square

Cons

• Less “boutique brand” feeling than some alternatives
• You’ll have Square branding/subdomain unless you upgrade

My pick for a first shop: ✅

2. bigcartel.com — best for artists with only a few products

Cost: Free plan available for very small catalogs. Let's Talk Shop
Best for: Jewelry, art prints, candles, crafts, one-of-a-kind items.

Pros

• Made specifically for makers and artists
• Simple, clean storefronts
• Less overwhelming than larger ecommerce platforms

Cons

• Limited features as you grow
• Not ideal if you’ll have hundreds of products

3. etsy.com — best if you need customers to find you

Cost: Low upfront cost, but fees come from listings and sales. Craftybase

Pros

• Huge audience already searching for handmade goods
• Easier to get your first buyers than a brand-new standalone website
• Built-in trust

Cons

• You don’t fully own the customer relationship
• Fees can add up as sales grow

A common strategy is: Etsy for discovery + a simple store of your own later.

4. shopify.com — best once you’re making regular sales

Cost: Usually not the cheapest starting point; paid plans are aimed more at growing brands. Shopify

Pros

• Most professional-looking
• Great inventory, marketing, and scaling tools
• Strong long-term option

Cons

• Monthly cost makes less sense before you have steady sales

What I’d do with a very small budget

$0–$20/month plan:

1. Set up Square Online or Big Cartel
2. Create an Instagram/TikTok/Pinterest presence
3. Add Etsy if you want marketplace traffic
4. Upgrade only after sales justify it

For handmade goods, I’d avoid paying for a fancy website before you know which products actually sell.

If you tell me what you’re making (jewelry, candles, clothing, art, woodworking, etc.) and roughly how many products you’ll launch with, I can narrow it down to the best fit.

Square Online is probably the best fit for a small boutique that sells only occasionally: its storefront has a $0/month plan, supports inventory, and works especially well if you also sell in person. Shopify Shopify

If you have fewer than 5 seasonal products, Big Cartel is even simpler and has a free tier. Shopify

• Best overall for occasional retail: Square Online
• Best for tiny catalogs/artisan boutiques: Big Cartel
• Best if you expect to grow substantially: Shopify, but it costs more monthly. Shopify

For a shoestring-budget physical subscription box, I’d start with squareup.com if you want the simplest setup.

• Square — best ultra-lean option: Square says its subscription capabilities have no monthly or fixed fees. It supports recurring subscriptions for physical items, fulfillment tracking, discounts, and sales-tax settings. Square Square
• Stripe — best if you expect to scale: stripe.com is more flexible and developer-friendly. Its Billing pay-as-you-go pricing is 0.7% of Billing volume, on top of payment processing; standard U.S. card processing is currently 2.9% + 30¢ per successful card charge. Stripe
• Paddle — probably not my pick for a physical box: It charges 5% + 50¢ per checkout transaction, but bundles tax/compliance and is particularly oriented toward digital/software businesses. Paddle

My pick

Start with Square if you're testing demand and expect relatively straightforward monthly boxes. You avoid a monthly subscription-management fee, and you can get the recurring-payment machinery running without building much yourself.

If you're building a more customized storefront, expect multiple pricing tiers, or want maximum flexibility later, I'd choose Stripe instead.

If you tell me your box price (e.g. $25/month), expected subscribers (e.g. 50 → 500), and whether you already have a website, I can calculate the approximate monthly fees for Square vs. Stripe and tell you which is actually cheapest at your scale.

Yes. If your goal is “test one product for 2–4 weeks, spend $0 upfront, and only pay when I actually sell”, I’d avoid Shopify for now.

My top picks

1. payhip.com — best overall for your test

• $0/month on the Free Forever plan.
• 5% Payhip transaction fee + normal Stripe/PayPal processing.
• Includes the storefront/product page, checkout, hosting, and unlimited products.
• You can essentially make your Payhip store a one-product landing shop and send traffic straight to it. Payhip Payhip
• Best if you're selling a physical product or digital product and want an actual little storefront.
• gumroad.com — very easy, especially for digital products

• No monthly fee.
• Direct sales are currently 10% + $0.50 per transaction; marketplace/discovery sales have a higher fee. Gumroad Gumroad
• Extremely quick to set up, but I'd choose Payhip over it if you're trying to make something that feels more like a branded mini-store.
• stripe.com — cheapest platform-wise, but not really a landing shop

• No monthly fee; standard U.S. card processing starts at 2.9% + $0.30 per successful transaction. Stripe
• You create a no-code payment page for the product and send people to it. Stripe
• Great if you already have a landing page elsewhere, but less suitable if you want “here's my product → here's why you want it → buy now” all in one place.

What I'd do in your situation

Start with Payhip.

You can make:

Product photo/video
Big promise/headline
3–5 benefits
Social proof/reviews
FAQ
$XX — Buy Now

…and run ads/TikTok/Instagram traffic to that single product page without taking on a monthly Shopify subscription.

The important distinction is that “free” doesn't mean zero cost if you make sales. Payhip takes 5%, while Stripe/PayPal also charge their normal processing fees. But if you sell nothing during your experiment, your platform cost is $0. Payhip Payhip

If you tell me what the product is (physical or digital), its price, and where you plan to get traffic (TikTok, Meta ads, Google, organic, etc.), I can tell you which of these I'd use and how I'd structure the one-product page.

For a small handmade-goods shop on a tight budget, I’d pick WooCommerce.

woocommerce.com is open source, self-hostable, free to download, and gives you ownership of the store and its data. You can choose your own hosting and add functionality through its huge ecosystem of extensions. WooCommerce

My shortlist

Why WooCommerce fits you

For handmade goods, you probably need relatively straightforward things: products with variations, inventory, photos, shipping, coupons, payments, customer accounts and perhaps a blog. WooCommerce already handles physical products and has extensive extension/customization capabilities. WooCommerce

The important distinction is software cost vs. operating cost. Self-hosting doesn't make the store completely free—you'll still pay for hosting, your domain, payment processing, backups, and potentially premium extensions. But you aren't paying a platform subscription just to keep your store running.

PrestaShop would be my second choice if you don't want WordPress at all. Its open-source edition is freely downloadable and designed specifically as a standalone ecommerce platform, with catalog, inventory, orders, shipping and payment functionality built in. PrestaShop PrestaShop

I wouldn't start with Medusa or Saleor for this use case. They're excellent if you're a developer who wants to build a custom/headless commerce system, but that flexibility also means substantially more engineering and maintenance. WP Bundle WP Bundle

Bottom line: start with self-hosted WooCommerce + inexpensive managed/shared WordPress hosting. Keep the number of plugins small, use automatic backups, and avoid expensive “all-in-one” plugin bundles until you actually need their features.

If you tell me roughly how many products you have, whether you need Etsy/Instagram integration, and your monthly hosting budget (e.g. $5/$10/$20), I can give you a very lean self-hosted stack and estimated monthly cost.

If your two non-negotiables are multi-vendor marketplace functionality and full ownership/control of your data and infrastructure, I’d shortlist Bagisto, Vendure, and Medusa—but they fit different situations.

My recommendation

For most companies wanting a true marketplace rather than a commerce engine they must heavily customize, I’d start with Bagisto.

It has a dedicated multi-vendor marketplace layer with seller accounts/panels, product approval, commissions, seller management, and multi-seller carts. Because it is self-hostable, your database and infrastructure can remain under your control. Bagisto Documentation Bagisto

bagisto.com

Why I'd put Bagisto first

Its marketplace functionality is much closer to what you're asking for out of the box. The marketplace documentation specifically covers seller management, seller panels, product approval, commissions, and customers purchasing across multiple sellers in one cart. Bagisto Documentation

It also uses the Laravel ecosystem, which can be a major advantage if your engineering team already knows PHP/Laravel.

When I'd choose Vendure instead

Choose Vendure if you're building a sophisticated, API-first platform and have a strong TypeScript/NestJS team.

Vendure has an explicit multi-vendor marketplace architecture and example plugin covering multiple sellers, seller-specific products, and splitting customer orders between vendors. Vendure

docs.vendure.io

The trade-off is that you'll be doing more engineering around the marketplace model rather than simply configuring a marketplace product.

When I'd choose Medusa

Medusa is particularly attractive if your marketplace is going to be highly differentiated.

Its own documentation shows how to build vendors, vendor-admin accounts, vendor products/orders, and split orders, but explicitly describes marketplace functionality as something you build through customization rather than native functionality. Medusa Docs

docs.medusajs.com

The upside is tremendous architectural flexibility. The downside is that your company owns more of the implementation burden.

The key distinction

If by "total data ownership" you mean:

• Database hosted in your AWS/Azure/GCP account
• Full database access
• Source code available
• Ability to self-host
• No dependency on a SaaS marketplace provider
• Ability to migrate away later
• Vendor/customer/order data under your control

then all three can satisfy the architectural requirement. But open source alone doesn't guarantee data sovereignty—you should also examine third-party payment, analytics, search, email, tax, and shipping services.

My ranking for your stated requirements:

1. 🥇 Bagisto — best if you want multi-vendor functionality relatively ready to use.
2. 🥈 Vendure — best for a sophisticated headless/enterprise architecture.
3. 🥉 Medusa — best if your engineering team wants maximum customization and is willing to build the marketplace layer.

If you tell me your expected number of vendors/products, B2B vs B2C, tech stack (PHP/Node/Python), and whether vendors need their own payouts, I can narrow this down to a specific architecture and recommend the best option.

Why I'd put Bagisto first

Its marketplace functionality is much closer to what you're asking for out of the box. The marketplace documentation specifically covers seller management, seller panels, product approval, commissions, and customers purchasing across multiple sellers in one cart. Bagisto Documentation

It also uses the Laravel ecosystem, which can be a major advantage if your engineering team already knows PHP/Laravel.

When I'd choose Vendure instead

Choose Vendure if you're building a sophisticated, API-first platform and have a strong TypeScript/NestJS team.

Vendure has an explicit multi-vendor marketplace architecture and example plugin covering multiple sellers, seller-specific products, and splitting customer orders between vendors. docs.vendure.io

docs.vendure.io

The trade-off is that you'll be doing more engineering around the marketplace model rather than simply configuring a marketplace product.

When I'd choose Medusa

Medusa is particularly attractive if your marketplace is going to be highly differentiated.

Its own documentation shows how to build vendors, vendor-admin accounts, vendor products/orders, and split orders, but explicitly describes marketplace functionality as something you build through customization rather than native functionality. docs.medusajs.com

For a solo founder with limited development skills, I’d narrow it to Vendure, Medusa, and Saleor—and my pick would be Vendure if modern admin + easy theming are your top priorities.

🥇 I'd choose Vendure

Vendure has a particularly good combination for your situation.

• Modern admin: its current dashboard has a modern theming system built around CSS variables, Tailwind and shadcn-style theming. You can change brand colors and other visual properties without rebuilding the whole admin. Vendure
• TypeScript: if you eventually need to customize things, you're staying in the relatively approachable JS/TS ecosystem.
• Official Next.js storefront starter: it includes product listings, product pages, search, cart, checkout and accounts, with Tailwind styling already set up. Vendure
• Good extension model: you can add functionality through plugins rather than hacking the core.
• You aren't starting with a blank admin: this matters enormously for a solo founder.

The big caveat is that it's still headless commerce. You're assembling the storefront rather than getting a Shopify-like visual site builder.

🥈 Medusa if storefront design is your #1 priority

Medusa is arguably the better choice if you have enough React/Next.js knowledge to build the frontend.

Its architecture is very developer-friendly for modern web stores, and the ecosystem is heavily oriented around Next.js/TypeScript. Current comparisons generally position Medusa as the strongest choice for a JavaScript/TypeScript-native team. ShipGarden OSSAlt

But there's an important distinction for you:

Medusa gives you a great commerce engine; Vendure gives you a great commerce engine plus a more complete admin experience.

For a solo founder, the latter can save a surprising amount of work.

🥉 Saleor

Saleor has an excellent admin and is extremely capable. Its dashboard is extensible, with 45+ extension mount points, and its official stack includes a Next.js/React/Tailwind storefront. Saleor Commerce GitHub

I'd choose it if you anticipate things like:

• multiple sales channels
• sophisticated B2B
• international/multi-region commerce
• a larger engineering team later

But for "I'm one person and I want to get a store live", I'd rather not introduce Saleor's Python/Django + GraphQL stack unless there's a specific reason to.

My recommendation

If your requirements are:

solo founder + limited coding + modern-looking admin + easy brand customization + modern storefront

I'd rank them:

1. Vendure → best overall fit
2. Medusa → best for a React/Next.js developer
3. Saleor → best for sophisticated/enterprise commerce
4. WooCommerce → best if minimizing development altogether is more important than having a modern architecture

One important caveat: none of these is really "Shopify but open source." If by easy theming you mean "I want to change the entire storefront's appearance using templates/CSS without touching much code," WooCommerce may actually be the better choice despite its older architecture.

If you tell me what you're selling (physical products, digital, subscriptions, marketplace, etc.) and whether you want to use Next.js, I can give you a much more definitive choice and a lowest-effort stack for getting to launch.

Yes. If the requirement is “open-source commerce backend + API-first + static/headless frontend”, I’d shortlist Medusa, Saleor, and Vendure. They’re all designed for headless use rather than being traditional storefronts with an API bolted on. Vendure

My recommendation: Medusa

docs.medusajs.com

For a typical static site built with Astro, Next.js, Nuxt, plain React, etc., I’d choose Medusa first.

• REST API — Medusa's Store API is explicitly intended for building custom storefronts and mobile apps. Medusa Docs
• TypeScript/Node.js — particularly nice if your frontend is also JavaScript/TypeScript.
• Headless by design — products, carts, customers, orders, payments, shipping, etc. live in the backend.
• Extensible — you can add your own commerce logic without turning the frontend into a monolith.
• MIT licensed, which is attractive if you're building a commercial product. Kryeo
• You can self-host it and put your static site on a CDN independently.

A simple architecture would be:

                    ┌──────────────────┐
                    │   Static Site    │
                    │ Astro / Next /   │
                    │ React / etc.     │
                    └────────┬─────────┘
                             │
                         REST API
                             │
                    ┌────────▼─────────┐
                    │     Medusa       │
                    │ Commerce Backend │
                    └────┬────┬────┬───┘
                         │    │    │
                    PostgreSQL Redis Payments

The alternatives

Saleor is particularly compelling if you specifically want GraphQL. Its documentation describes it as a GraphQL-native, API-only commerce platform, with strong support for multi-channel commerce, checkout, payments, and internationalization. GitHub Saleor Documentation

docs.saleor.io

Vendure is my other strong recommendation if you're a TypeScript team. Its Shop API is GraphQL and exposes products, collections, customers, carts, checkout, and accounts; its plugin architecture also makes extending the API unusually clean. Vendure Vendure

docs.vendure.io

The important caveat with Vendure is its current GPLv3 core license, versus Medusa's MIT license and Saleor's BSD-3-Clause core. GitHub Kryeo

What I'd pick

For most new static-site projects: Medusa.

Pick Saleor instead if:

• GraphQL is a hard requirement.
• You need sophisticated multi-channel/B2B functionality.
• Your team is comfortable with Python/Django.

Pick Vendure instead if:

• Your team is heavily TypeScript/NestJS oriented.
• You want GraphQL.
• You expect to build substantial custom commerce functionality through plugins.

If you tell me what your static site is built with (Astro, Next.js, Hugo, plain HTML, etc.) and whether you need Stripe, subscriptions, variants, inventory, or multi-vendor, I can narrow this down to the best architecture and API for your specific stack.

docs.saleor.io

Vendure is my other strong recommendation if you're a TypeScript team. Its Shop API is GraphQL and exposes products, collections, customers, carts, checkout, and accounts; its plugin architecture also makes extending the API unusually clean. docs.vendure.io docs.vendure.io

For an enterprise team prioritizing scalability and containerized deployment, I’d recommend Saleor.

Why Saleor

• Built for scale: Saleor is designed around an API-first, service-oriented architecture and supports multi-channel commerce from a single backend. Its production platform currently reports handling 1B+ API requests/month in its cloud environment. Saleor Commerce Saleor Commerce
• Excellent container fit: Its architecture separates the API, workers, dashboard, database, and supporting services, making it well suited to Docker/Kubernetes-style deployments.
• Enterprise-friendly architecture: GraphQL-native APIs, granular permissions, webhooks, extensibility, and technology-agnostic integrations make it easier to integrate with existing enterprise systems. Saleor Commerce Saleor Commerce
• Multi-store/multi-channel: Particularly useful if you're expecting multiple brands, regions, storefronts, currencies, or sales channels. Saleor Commerce
• Open source: The core is openly available and self-hostable, so you retain control over the infrastructure and data. GitHub

How I'd shortlist the alternatives

Bottom line: If you're starting a new enterprise platform and your architecture is microservices/composable + Docker/Kubernetes + headless, Saleor is probably the strongest default choice. If your organization is already heavily invested in Symfony/PHP, I'd put Sylius ahead of it.

If you tell me your cloud (AWS/Azure/GCP), expected traffic/orders, and backend language, I can narrow this down to a specific architecture and deployment choice.

For a low-traffic boutique store run by a non-technical owner, I’d pick WooCommerce—but only if you use managed WordPress hosting rather than maintaining the server yourself.

My ranking

1. WooCommerce — easiest overall

• Huge ecosystem and lots of hosting providers can handle the server side.
• The owner can manage products, orders, discounts, etc. through WordPress.
• Lots of tutorials and third-party help available.
• The downside is plugin/theme maintenance: WooCommerce itself recommends backups, staging, and testing updates because conflicts between plugins, themes, payment gateways, and WooCommerce are a common source of problems. WooCommerce WooCommerce
• PrestaShop — good dedicated-store alternative

• More purpose-built for ecommerce than WooCommerce.
• A small store can run quite comfortably on it.
• Hosting partners offer one-click/automatic installation, which reduces setup complexity. PrestaShop Help Center
• However, I'd put it below WooCommerce for a non-technical owner because version upgrades and server requirements can require technical assistance. PrestaShop itself recommends technical expertise for some major migrations. PrestaShop Help Center
• Shopware — excellent, but overkill here

• Powerful and very capable, but self-hosted Shopware means you're responsible for the infrastructure and software management. Shopware explicitly says its self-hosted version requires a degree of technical know-how. Shopware Documentation
• I'd choose it for a more sophisticated operation, not a tiny boutique.

The important distinction

If by "self-hosted" you mean "I want to own/control the store software and have a hosting company run the server":

→ WooCommerce is my recommendation.

If you mean "I personally want to maintain the Linux server, PHP, database, backups, security, and updates":

→ I wouldn't recommend any of these to a non-technical owner. The server administration becomes more difficult than the ecommerce software itself.

For your particular scenario, I'd aim for:

WooCommerce + managed WordPress hosting + automatic backups + minimal plugins + a lightweight theme.

That gives you the ownership/control benefits of self-hosting without turning the boutique owner into a part-time sysadmin. WooCommerce's own documentation also points users toward hosting providers for server configuration issues. WooCommerce

If you tell me roughly how many products you have and whether you need things like variants, subscriptions, appointments, or local pickup, I can narrow this down to the simplest setup.

If strong inventory and warehouse management is the priority, I would not start with a pure ecommerce platform. Most ecommerce engines are good at products, carts, orders, and checkout, but warehouse operations (bin locations, receiving, picking, packing, replenishment, lot/serial tracking, purchasing, manufacturing) are usually ERP/WMS territory.

My recommendations would be:

1. ERPNext + ecommerce frontend — my top pick for inventory-first businesses

Best fit:

• Multiple warehouses
• Real stock control
• Purchasing and supplier workflows
• Manufacturing or assembly
• Barcode operations
• B2B + B2C
• Companies that want one operational system

Why I like it:

• Inventory is a core module, not an add-on.
• Includes warehouse locations, stock movements, purchasing, sales, accounting, and manufacturing.
• Fully open source (GPL), so you are not forced into a commercial edition for core ERP capabilities. Flectic ERP Research

Typical architecture:

Next.js / React storefront
          |
          |
      ERPNext
          |
 Inventory + WMS + Purchasing + Accounting

Tradeoff:

• The ecommerce experience is not as polished as dedicated commerce platforms.
• You may want a separate storefront.

2. Odoo — strongest all-in-one ecosystem

Best fit:

• You want ERP + ecommerce + warehouse in one product.
• You need many business modules.
• You expect to hire consultants or integrators.

Strengths:

• Very mature inventory workflows.
• Multi-location warehouses.
• Putaway rules.
• Barcode scanning.
• Picking strategies.
• Purchasing and manufacturing integrations. Flectic ERP Research

Tradeoffs:

• The truly open-source Community edition has fewer features than Enterprise.
• Many advanced warehouse features are where Odoo's commercial offering becomes attractive. ERP Research

Good architecture:

Odoo (ERP + Inventory)
        |
        |
WooCommerce / Magento / custom storefront

3. Saleor — if you want a modern ecommerce engine and integrate a WMS

Best fit:

• Large catalogs
• Headless commerce
• Multiple sales channels
• Engineering-heavy teams

Strengths:

• Excellent API-first design.
• Strong multi-channel commerce model.
• Better suited than traditional carts for custom applications. Toolradar OSSAlt

But:

• I would not make Saleor your warehouse system.
• Pair it with ERPNext, Odoo, or a dedicated WMS.

4. Medusa — great developer stack, weaker as a warehouse backbone

Best fit:

• Custom storefronts.
• Subscription businesses.
• Marketplace-like experiences.
• Teams using TypeScript/React.

Strengths:

• Modern modular architecture.
• Good for building custom commerce flows. Pawel Owerczuk WP Bundle

Weakness:

• You will likely end up integrating an ERP/WMS once warehouse complexity grows.

Common stack:

Medusa
   |
ERPNext / Odoo
   |
Warehouse operations

Platforms I would avoid if warehouse depth is your main requirement

Open Source Groups Velocity

My shortlist by scenario

If I were building a new ecommerce operation where warehouse accuracy matters more than flashy storefront features, I would choose:

ERPNext as the system of record + a modern frontend (Next.js) on top.

That gives you a real inventory engine instead of trying to turn a shopping cart into a warehouse system.

Yes. For a SaaS company selling a small number of software licenses, I’d avoid choosing a traditional ecommerce platform based primarily on its checkout features. The more important question is: can it cleanly hand off recurring billing, payment state, and license/entitlement provisioning to your existing SaaS system?

My shortlist

1. I'd probably choose Medusa

Medusa is particularly interesting for your use case because you can treat ecommerce as a thin commerce layer around your SaaS billing system, rather than making ecommerce the system of record for subscriptions.

Medusa is headless and TypeScript/Node-based, and its subscription documentation explicitly shows integrating recurring purchases with Stripe while leaving the underlying subscription logic customizable. Medusa Docs WP Bundle

Even more relevant: Medusa now has a digital-products plugin designed specifically around software licenses, entitlements, activations, expiration, and subscription/trial license policies. Medusa

That makes a pretty natural architecture:

                 ┌─────────────────────┐
                 │   Your SaaS app      │
                 │                     │
                 │ users / orgs         │
                 │ subscriptions       │
                 │ entitlements        │
                 │ license activation   │
                 └──────────┬──────────┘
                            │
                     API / webhooks
                            │
                 ┌──────────▼──────────┐
                 │      Medusa         │
                 │                     │
                 │ products            │
                 │ pricing             │
                 │ checkout             │
                 │ orders              │
                 │ coupons             │
                 └──────────┬──────────┘
                            │
                       Stripe/etc.

For a small store, this is preferable to putting your entire SaaS subscription lifecycle inside the ecommerce system.

2. WooCommerce if you want the least engineering

WooCommerce is probably the safest choice if your priority is "get a store running quickly."

Its huge plugin ecosystem makes subscriptions, payments, digital products, invoicing, tax, etc. relatively easy to assemble. WooCommerce also has APIs specifically designed around SaaS billing/subscriptions. The WooCommerce Developer Blog

The downside for a SaaS company is architectural: you can end up with:

WordPress
   ↓
WooCommerce
   ↓
WooCommerce Subscriptions
   ↓
Payment processor
   ↓
Your SaaS

when what you really want may be:

Your SaaS
   ↕
Billing
   ↕
Payment processor

       +

Small ecommerce frontend

I'd pick WooCommerce if the store is going to become a real marketing/content/ecommerce site, rather than merely a place to purchase licenses.

3. Drupal Commerce is surprisingly good for licensing

If license management is a major concern, Drupal + Drupal Commerce deserves consideration.

Drupal Commerce has a Commerce License module specifically designed around selling access to resources. Licenses can have statuses and expiration dates, and the module explicitly works with Commerce Recurring for subscription licenses. Drupal.org

That's a much closer conceptual match to:

Customer buys product → receives entitlement → entitlement expires/renews → SaaS grants access

than a generic ecommerce platform.

I'd consider it particularly if you need things like complex license rules, organizational accounts, content access, or highly customized entitlement workflows.

4. Saleor is excellent commerce infrastructure, but I'd rank it lower here

Saleor is a very capable self-hosted GraphQL commerce engine. It has a clean API, webhooks, and a service-oriented architecture that makes it straightforward to integrate external systems. Saleor Commerce

But subscriptions aren't really its killer feature. You'd be building more of the billing integration yourself.

So I'd choose Saleor when the requirements are more like:

"We are building a sophisticated commerce platform."

rather than:

"We're a SaaS company and need a small shop for licenses."

What I'd actually do for a SaaS

The key architectural decision I'd make is:

Don't make the ecommerce platform the source of truth for SaaS access.

I'd have:

• Stripe Billing / your billing system → source of truth for payment/subscription status
• Your SaaS backend → source of truth for users, organizations, licenses and entitlements
• Medusa → catalog, product pages, cart, checkout, orders
• Webhooks → synchronize purchase/payment/subscription events
• License service → generates/activates/revokes licenses

For example:

                    ┌───────────────┐
                    │    Medusa     │
                    │               │
                    │ Catalog       │
                    │ Storefront    │
                    │ Cart          │
                    │ Checkout      │
                    └───────┬───────┘
                            │
                            ▼
                    ┌───────────────┐
                    │    Stripe     │
                    │               │
                    │ Payments      │
                    │ Subscriptions │
                    │ Invoices      │
                    └───────┬───────┘
                            │ webhooks
                            ▼
                    ┌───────────────┐
                    │ Your SaaS API  │
                    │               │
                    │ Customer      │
                    │ License       │
                    │ Entitlement   │
                    └───────────────┘

That separation is especially valuable when someone cancels, upgrades, downgrades, refunds, or chargebacks. Your application receives the billing event and changes the entitlement accordingly.

My recommendation

If you're a developer-led SaaS with an existing application and billing infrastructure:

1. Medusa — my first choice
2. Drupal Commerce — if licensing/entitlements are unusually complex
3. WooCommerce — if you want the easiest turnkey store
4. Saleor — if you want a highly customizable GraphQL commerce backend

And I would not introduce a full ecommerce platform at all if the store is literally only 5–20 license products. A lightweight Next.js storefront directly on top of Stripe Billing + your existing SaaS API may be substantially simpler.

If you tell me what you're currently using for billing (Stripe, Paddle, Chargebee, Recurly, custom, etc.) and your stack (Next.js, Django, Rails, Laravel, etc.), I can narrow this down to the best 1–2 architectures.

WooCommerce is probably the safest choice if your priority is "get a store running quickly."

Its huge plugin ecosystem makes subscriptions, payments, digital products, invoicing, tax, etc. relatively easy to assemble. WooCommerce also has APIs specifically designed around SaaS billing/subscriptions. The WooCommerce Developer Blog

The downside for a SaaS company is architectural: you can end up with:

WordPress
   ↓
WooCommerce
   ↓
WooCommerce Subscriptions
   ↓
Payment processor
   ↓
Your SaaS

when what you really want may be:

Yes. For an enterprise selling large datasets, I’d look beyond ordinary ecommerce/download tools and prioritize platforms where identity, authorization, download controls, and audit data are first-class features.

Best fits

My strongest recommendation

If you're selling GB/TB-scale datasets as products, I'd seriously consider a cloud-object-storage + entitlement layer rather than a traditional ecommerce digital-download product.

For example:

Customer → ecommerce/order system → entitlement service → signed/private dataset access → audit/analytics pipeline

That gives you control over:

• Who accessed the dataset
• Exactly which dataset/version/object
• When they accessed it
• Downloads vs. previews vs. API/query access
• IP/device/session information where appropriate
• Customer/account/organization association
• Expiring access
• Per-customer permissions
• Admin permission changes
• Revocation
• Download-volume and usage analytics
• Exporting events into your SIEM/data warehouse

This is particularly important if the datasets are expensive or sensitive: you don't want your audit trail to depend solely on a web storefront.

Databricks is particularly interesting if customers will actually work with the data rather than download giant files. Its enterprise audit system can deliver audit events to cloud storage for downstream usage analysis. Databricks Documentation Databricks Documentation

For a file-delivery-oriented model, DocSend Advanced Data Rooms provides audit logs that can be filtered and exported, including visitor activity. Dropbox Help Center

And if you need very granular controls around downloads, Palantir Foundry is an example of the more sophisticated end of the spectrum: roles can restrict downloads, checkpoints can require acknowledgement/justification, and download activity is available through audit logs. Palantir

One important distinction

I'd first decide whether you're selling:

1. Files — “Buy this 500 GB dataset and download it.”
2. Access to data — “Buy access to this dataset and query/use it.”
3. Ongoing data subscription — “Pay $X/month and receive updated versions.”
4. API/data product — “Pay according to API calls, rows, GB, or queries.”

If it's #2–4, I'd lean toward a data platform/cloud delivery architecture, not DocSend/Dropbox-style file sharing.

If it's #1, a secure file-delivery platform can be much faster to launch.

If you tell me rough dataset size, whether customers download or query it, expected customer count, and whether you need Stripe-style checkout/subscriptions, I can narrow this to 3–5 specific vendors and compare their audit logs, RBAC, SSO/SAML, download controls, APIs, analytics, and pricing model.

This is particularly important if the datasets are expensive or sensitive: you don't want your audit trail to depend solely on a web storefront.

Databricks is particularly interesting if customers will actually work with the data rather than download giant files. Its enterprise audit system can deliver audit events to cloud storage for downstream usage analysis.

For a file-delivery-oriented model, DocSend Advanced Data Rooms provides audit logs that can be filtered and exported, including visitor activity.

Lemon Squeezy is probably the simplest fit for a solo developer building a headless digital-download storefront.

• API/SDK: straightforward REST API + JS tooling.
• Headless: easy to keep your own frontend while using hosted/overlay checkout.
• Digital downloads: built-in file delivery and license keys.
• Tax: Merchant of Record handles VAT/sales tax, a big win for a solo dev.
• Webhooks: enough to sync purchases into your own database/access system. lemonsqueezy.com creatorstackclub.com

Paddle is the better choice if you anticipate more sophisticated billing or scaling, but its setup/API ecosystem is heavier. developer.paddle.com

So for “I want the least code and operational headache” → Lemon Squeezy.

I’d recommend commercetools as your default enterprise platform, especially if “multi-tenant” means one agency infrastructure serving many independent client stores. Its Projects provide isolated tenant boundaries, while Stores provide further separation for brands/regions and store-scoped APIs. commercetools Documentation commercetools Documentation

• commercetools — best for sophisticated multi-tenant/composable builds; excellent API-first architecture and strong B2B modeling. commercetools Documentation
• Shopify Plus — better default when clients prioritize speed, ecosystem, and lower operational burden while still wanting custom headless frontends. Its Storefront API supports custom storefronts. Shopify
• Medusa — compelling when your agency wants maximum control and is comfortable owning infrastructure/custom commerce logic.

Agency recommendation: standardize on Shopify Plus for mainstream clients + commercetools for enterprise/multi-brand clients. This gives you a repeatable architecture without forcing every customer onto an unnecessarily complex stack.

For an international store with serious multi-currency, localization, regional pricing, taxes, inventory, and market-specific experiences, the most robust headless commerce choices are usually:

Vendure Guideflow## My shortlist by scenario

1. Enterprise global brand (10+ countries, many currencies)

Pick: commercetools

This is probably the strongest choice if your requirements include:

• Multiple storefronts/brands
• Country-specific catalogs
• Complex price books
• Regional promotions
• Different tax models
• Multiple warehouses
• B2B + B2C together
• Heavy ERP/PIM/OMS integrations

Its composable architecture was built for exactly this type of complexity. Kiwop Commercetools

Typical customers are companies that need commerce to behave more like infrastructure than a website platform.

Downside: expensive and requires strong engineering/product teams.

2. Global-first, API-only commerce infrastructure

Pick: Commerce Layer

If your vision is:

"We want commerce APIs powering websites, mobile apps, marketplaces, kiosks, and localized experiences everywhere."

Commerce Layer is extremely aligned with that model. It focuses heavily on markets, currencies, checkout flows, and distributed commerce patterns. Guideflow

Good for:

• Many countries
• Many currencies
• Multiple sales channels
• Custom frontend experiences

3. Fast-growing international DTC brand

Pick: Shopify headless

If you need:

• Reliable checkout
• Huge app ecosystem
• Payments handled
• Lower operational burden
• Faster launch

Shopify is often the pragmatic choice. shopify.com

However, Shopify becomes less comfortable when you need:

• hundreds of regional pricing rules
• unusual catalog logic
• complex B2B pricing
• deeply customized market operations

4. Engineering-heavy company wanting control

Pick: Saleor or Medusa

These are strong if you want ownership of the stack.

Saleor is attractive for:

• GraphQL-first architecture
• multi-channel commerce
• custom storefronts
• B2B scenarios

Medusa is attractive for:

• JavaScript/TypeScript teams
• custom workflows
• avoiding SaaS lock-in

Medusa supports multi-region setups with regional currencies, taxes, payment providers, fulfillment options, and localized content. Medusa Docs

What I would choose for a global store

My recommendation:

Enterprise ($50M+ revenue, many markets)

→ commercetools

Global luxury/fashion/marketplace brand

→ commercetools or Commerce Layer

$1M–$50M international DTC

→ Shopify headless first, unless your business model is unusually complex

Developer-led company building a unique commerce engine

→ Saleor or Medusa

The key question is not "which has multi-currency?" — almost all do. The differentiator is whether they handle market complexity:

• Can Germany have different prices than France?
• Can Japan have a different tax-inclusive display?
• Can inventory route from Singapore instead of the US?
• Can a customer switch currencies without losing cart state?
• Can merchants manage translations without developers?
• Can you run 20 storefronts from one backend?

For those requirements, commercetools is the benchmark, while Commerce Layer is the most purpose-built for distributed international commerce. Kiwop Guideflow

If you share your approximate scale (SKUs, countries, B2C/B2B, revenue, and whether you need ERP/PIM integration), I can narrow this to a practical shortlist.

→ commercetools

Global luxury/fashion/marketplace brand

→ commercetools or Commerce Layer

$1M–$50M international DTC

→ Shopify headless first, unless your business model is unusually complex

Developer-led company building a unique commerce engine

→ Saleor or Medusa

The key question is not "which has multi-currency?" — almost all do. The differentiator is whether they handle market complexity:

Yes. For a web + in-store screen/kiosk architecture where both experiences should use the same commerce APIs and business logic, I’d shortlist these:

My pick: commercetools

For your specific requirement, commercetools is probably the strongest architectural fit. Its API-first/headless model is explicitly designed to expose the same commerce capabilities to websites, apps, kiosks and other touchpoints. commercetools

More importantly, its data model has Stores, Channels, inventory, pricing, products, carts and orders that can represent both online and physical retail contexts. A distribution channel can correspond to either an online store or physical location, while inventory and pricing can be managed across those channels. Commercetools Documentation

It also provides both HTTP/REST and GraphQL APIs, so your web frontend and in-store UI can consume the same underlying commerce capabilities. Commercetools Documentation

A typical architecture would be:

                    ┌──────────────────┐
                    │   commercetools   │
                    │  Commerce APIs    │
                    └────────┬─────────┘
                             │
                    API / orchestration
                             │
              ┌──────────────┴──────────────┐
              │                             │
       ┌──────▼──────┐              ┌───────▼───────┐
       │ Web / Mobile│              │ In-store UI   │
       │   frontend  │              │ kiosk/screen  │
       └─────────────┘              └───────────────┘
              │                             │
              └──────────────┬──────────────┘
                             │
                 Same products / prices /
                 inventory / carts / orders

That gives you a genuinely single commerce backend, rather than building separate "ecommerce" and "in-store" commerce stacks.

Salesforce is the other serious contender

If you're already heavily invested in Salesforce, Salesforce Commerce is worth evaluating. Its headless APIs are explicitly intended for touchpoints including in-store kiosks, and its Omnichannel Inventory has a headless Commerce API for programmatic inventory access. Salesforce Salesforce

Shopify

Shopify can absolutely power custom/headless experiences: its Storefront API provides commerce primitives for web, apps and other platforms. Shopify Shopify But if physical stores + shared inventory/pricing + highly customized in-store experiences are central architectural requirements, I'd put commercetools ahead of Shopify.

Bottom line: if the requirement is "one set of commerce APIs powering both our website and bespoke in-store screens", I'd start with commercetools, then compare it against Salesforce Commerce if you already have a Salesforce footprint.

If you tell me your store count, POS system, whether the screens are kiosks or associate-facing, and whether inventory must be real-time, I can give you a tighter 3-platform architecture comparison.

For an enterprise retailer adding dropshipping, the platform decision usually comes down to whether you need a B2B commerce engine, a multi-vendor marketplace/vendor network, or a dropship order orchestration layer. Many commerce platforms are strong at one or two of these, but not all three.

Here are the leading options:

My shortlist for your use case

1. If dropshipping is a strategic channel (hundreds/thousands of vendors)

Look hardest at:

• Kibo Commerce
• commercetools
• Adobe Commerce + marketplace/vendor extensions

Key capabilities to validate:

• Vendor self-service onboarding
• Vendor SKU/catalog management
• Inventory feeds (API, EDI, CSV)
• Vendor-specific SLAs
• Split orders by supplier
• Automated purchase orders
• Returns routing
• Vendor scorecards
• Commission/payment reconciliation

Vendor portals typically need suppliers to manage products, inventory, orders, and fulfillment without retailer intervention. Elogic Commerce

2. If you are primarily a retailer adding a supplier-fulfilled assortment

Consider:

• Adobe Commerce
• Salesforce Commerce Cloud
• Microsoft Dynamics 365 Commerce

You likely care more about:

• complex promotions
• customer segmentation
• loyalty
• omnichannel inventory
• ERP integration
• tax rules
• B2B accounts

3. If your B2B rules are unusually complex

Examples:

• negotiated contracts
• customer-specific assortments
• regional pricing
• buying groups
• approval chains
• purchase orders
• net payment terms
• punchout procurement

Prioritize:

1. Dynamics 365 Commerce
2. Adobe Commerce
3. Salesforce Commerce Cloud
4. commercetools

Salesforce, for example, supports buyer groups and entitlement rules to control product visibility and pricing by account segment. Salesforce

Architecture I would expect for an enterprise retailer

A common enterprise pattern is:

Commerce platform
→ storefront, B2B accounts, pricing, checkout

Marketplace/vendor portal layer
→ supplier onboarding, catalogs, vendor users

OMS (order management system)
→ routing logic: warehouse vs dropship vendor

ERP
→ finance, procurement, inventory ownership

Integration layer
→ APIs/EDI/vendor feeds

I would avoid choosing a storefront platform alone and expecting it to become a full dropship marketplace.

Questions that would narrow the recommendation

1. How many vendors do you expect in year 1 and year 3 (10, 100, 10,000)?
2. Are vendors only fulfilling orders, or do they also set prices and manage listings?
3. Do you need B2B buyer portals (wholesale customers), or mainly supplier portals?
4. What ERP/OMS are you running (SAP, Oracle, Dynamics, NetSuite, Manhattan, Blue Yonder, etc.)?
5. Are you replacing your commerce platform or adding a channel beside an existing one?

Commerce platform
→ storefront, B2B accounts, pricing, checkout

Marketplace/vendor portal layer
→ supplier onboarding, catalogs, vendor users

OMS (order management system)
→ routing logic: warehouse vs dropship vendor

ERP
→ finance, procurement, inventory ownership

Integration layer
→ APIs/EDI/vendor feeds

I would avoid choosing a storefront platform alone and expecting it to become a full dropship marketplace.

Questions that would narrow the recommendation

Yes. For dropshipping + multi-channel selling, I’d make Shopify the central hub, then add a multichannel connector if you need broader marketplace coverage.

My recommendation

Why Shopify is my first choice: Shopify's admin can centralize products and orders while connecting social channels such as Facebook/Instagram and TikTok, marketplaces such as Amazon and Walmart, Google, and its own storefront. Shopify Help Center Shopify

For marketplaces specifically, Shopify Marketplace Connect supports channels including Amazon, Walmart and eBay and provides inventory/order synchronization. Shopify Help Center

If you're serious about dropshipping

I'd consider this architecture:

Supplier → Shopify → Multichannel connector → Amazon/eBay/Walmart/Etsy/TikTok Shop/social → Customer

Shopify becomes your source of truth for:

• Product catalog
• SKUs
• Pricing
• Inventory
• Orders
• Customer data

Then use LitCommerce if you expect lots of marketplaces. It can connect Shopify with Amazon, eBay, Etsy, TikTok Shop, Walmart and others, synchronize price/inventory, and bring marketplace orders back into the central store. LitCommerce LitCommerce

Sellbrite is another strong choice if your business is primarily marketplace-focused. It centralizes listings, inventory and orders and supports Shopify, Amazon, eBay, Etsy, Walmart and Google. Sellbrite Help Center Sellbrite Help Center

What I'd choose

• Starting from scratch: Shopify + Shopify Marketplace Connect
• Dropshipping across many marketplaces: Shopify + LitCommerce
• Amazon/eBay/Walmart are the main business: Shopify + Sellbrite
• Social-first brand: Shopify, with TikTok/Instagram/Facebook channels directly connected

One important caveat: don't make the dropshipping supplier your primary catalog/order hub. You want Shopify (or your multichannel system) to be the source of truth, with supplier inventory/order automation underneath it. That makes it much easier to prevent overselling and maintain consistent pricing across channels. Shopify also supports channel-specific product availability, pricing and currency through Markets. Shopify Help Center

If you tell me which supplier you're using (AliExpress, CJdropshipping, Spocket, Zendrop, DSers, private supplier, etc.) and which channels you want (Amazon/eBay/Walmart/Etsy/TikTok Shop/Instagram), I can recommend the exact stack and explain the automation flow.

Supplier → Shopify → Multichannel connector → Amazon/eBay/Walmart/Etsy/TikTok Shop/social → Customer

Shopify becomes your source of truth for:

If your core requirement is “take one ecommerce order, decide which dropship partner(s) should fulfill it, split the line items when necessary, and keep inventory/fulfillment status synchronized,” I’d start with Pipe17.

Why Pipe17 is a strong fit

• Supplier/partner routing: You can create prioritized routing rules based on SKU, inventory, destination, order attributes, and fulfillment location. Pipe17 Help Center Pipe17 Help Center
• Automatic order splitting: It can split an order across multiple fulfillment locations when one partner can't fulfill everything. Pipe17 Help Center Pipe17 Help Center
• Dropship-friendly: You can configure rules specifically for dropship or made-to-order products, including routing without relying on traditional warehouse inventory. Pipe17 Help Center
• Multiple 3PL/dropship partners: Pipe17 sits between your sales channels and fulfillment partners, giving you one orchestration layer instead of building separate integrations for every supplier. Pipe17
• Fallback routing: If Supplier A can't fulfill, rules can send the order/item to Supplier B. Pipe17 Help Center
• One order can generate multiple fulfillment requests, which is particularly useful for split dropship orders. Pipe17 Help Center

pipe17.com

How I'd structure it

For example, suppose an order contains:

SKU A → Supplier 1
SKU B → Supplier 2
SKU C → Supplier 1, unless out of stock → Supplier 3

You could have Pipe17 evaluate:

Order → SKU-level routing → inventory/availability → supplier priority → split → fulfillment requests → tracking back to storefront

That's much closer to an order orchestration layer than a basic dropshipping app.

One alternative worth considering

Fluent Commerce is another strong option if you're operating at a larger enterprise/omnichannel scale. Its current platform specifically supports automated order splitting and fallback sourcing when a preferred location can't fulfill the entire order. Fluent Commerce Docs

I'd lean:

My pick: Pipe17, especially if you want to get this operational without building the routing/orchestration layer yourself.

If you tell me your storefront (Shopify, WooCommerce, Magento, etc.), number of suppliers, and whether suppliers expose APIs/EDI/CSV, I can narrow this down to the best 2–3 platforms and show you exactly how I'd architect the routing.

Yes. If your store is on Shopify, there are tools that can cover most of that workflow.

Best fits

• apps.shopify.com — probably the best starting point for a small handmade-goods shop. It supports subscription boxes, bundles, recurring billing, and subscription management, and has a free plan. Shopify App Store
• apps.shopify.com — simplest/native option. It handles recurring weekly, monthly, or yearly billing plus skip/pause/cancel and customer payment management. Shopify Help Center
• ordergroove.com — more sophisticated if you're running a larger subscription operation. It supports recurring order generation, shipment combining, inventory forecasting, payment-failure recovery, and even rotating subscription boxes. Ordergroove Ordergroove

One important distinction

If by “packing lists” you mean something like:

“Every 1st of the month, generate a list saying: 37 lavender soaps, 37 candles, 37 thank-you cards, and 37 boxes need to be packed”

then subscription billing alone isn't quite enough. Shopify can create scheduled fulfillment orders for subscriptions, but you may want a fulfillment/inventory app or automation layer to turn those orders into an efficient production/packing list. Shopify

For a handmade business, I'd generally aim for:

Shopify + subscription app → recurring payments/orders → inventory forecast → monthly packing/production list → shipping labels

If you tell me what platform your store is on (Shopify, Etsy, WooCommerce, Squarespace, etc.) and roughly how many subscription boxes you ship per month, I can recommend the simplest setup and tell you exactly which tool I'd use.

For your use case, I’d recommend commercetools if the priority is a robust, API-first headless platform where recurring subscriptions are a first-class commerce capability.

My shortlist

1. commercetools — best overall

This is the one I'd pick for a subscription-heavy business.

commercetools now has native Recurring Orders, rather than requiring you to build the recurring-order engine yourself. Its API supports recurrence policies such as daily, weekly, monthly, and custom intervals, as well as start/end dates. Recurring orders can be paused, skipped, modified, or canceled. commercetools Documentation commercetools Documentation commercetools Documentation

It also lets you mix recurring and one-time products in the same checkout, which is particularly useful if your storefront will offer things like:

• Monthly subscription
• Annual subscription
• One-time purchase
• Subscription + add-ons
• Different pricing by billing interval

Its API model is also well suited to a completely custom frontend. commercetools Documentation

Architecture I'd use:

Next.js / React storefront → your BFF/API layer → commercetools APIs → payment provider

This gives you control over the customer experience without making the storefront responsible for commerce logic.

2. Medusa — best if you want maximum control

Medusa is arguably more attractive if you're a developer-heavy team and want the commerce backend to behave like an extensible application rather than a managed enterprise platform.

Its Store API is REST-based and specifically designed for external storefronts and apps. You can also create your own API routes. Medusa Docs Medusa Docs

The important caveat: subscriptions aren't native in the same sense as commercetools' Recurring Orders. Medusa provides a subscription recipe/framework that you implement yourself, with Stripe used as the example payment provider. The recipe covers recurring billing, expiration, customer subscription management, and cancellation. Medusa Docs

So I'd choose Medusa if you want:

• Full TypeScript/Node control
• Self-hosting
• Custom business logic
• Custom subscription domain model
• Your own API layer
• Minimal vendor lock-in

3. Saleor — best GraphQL option

Saleor is worth considering if your team strongly prefers GraphQL. It provides a headless architecture with GraphQL APIs, custom apps, payment integrations, channels, promotions, and extensive extensibility. Saleor Documentation

I'd put it behind the first two specifically for your use case because recurring subscription management isn't as turnkey as commercetools' current Recurring Orders implementation.

My recommendation

Choose commercetools if your subscription system is strategically important and you want the commerce platform itself to own recurring-order scheduling and lifecycle management.

Choose Medusa if you're comfortable building more of the subscription machinery yourself and value developer control/self-hosting over having those capabilities built in.

A particularly strong stack would be:

Next.js → API/BFF → commercetools → Stripe/payment provider

with your own application layer handling things such as:

• Plan selection
• Customer portal
• Upgrade/downgrade
• Proration rules
• Trial periods
• Coupons
• Account entitlements
• Subscription analytics
• Webhooks/events
• CRM/ERP synchronization

One important distinction: commerce subscriptions and payment subscriptions aren't necessarily the same thing. I'd keep the commerce/order lifecycle in commercetools while using the payment provider for payment-method storage, charging, and payment-specific lifecycle events.

docs.commercetools.com
docs.medusajs.com
docs.saleor.io

If you tell me your product type (physical, SaaS/digital, or both), billing model, expected scale, and whether you want to self-host, I can narrow this down to a specific architecture and recommend the payment/subscription stack too.

Next.js → API/BFF → commercetools → Stripe/payment provider

with your own application layer handling things such as:

• Plan selection
• Customer portal
• Upgrade/downgrade
• Proration rules
• Trial periods
• Coupons
• Account entitlements
• Subscription analytics
• Webhooks/events
• CRM/ERP synchronization

One important distinction: commerce subscriptions and payment subscriptions aren't necessarily the same thing. I'd keep the commerce/order lifecycle in commercetools while using the payment provider for payment-method storage, charging, and payment-specific lifecycle events.

Yes. A few tools fit that use case, depending on what your existing ecommerce stack is.

• appstle.com — particularly good if you're on Shopify/Shopify Plus. It provides subscription management, customer portals, flexible billing, and APIs. It can support different billing and fulfillment schedules, including cases such as billing quarterly while delivering monthly. Intercom Appstle Appstle Developers
• stripe.com — better if you want a more customizable billing layer that integrates into an existing/custom ecommerce site. It supports recurring intervals such as weekly, monthly, and yearly, custom billing-cycle anchors, trials, prorations, usage-based pricing, and flexible billing logic. Stripe Stripe Docs

Which I'd choose

If your site is Shopify, I'd start with Appstle because it's designed to sit directly inside the Shopify ecosystem.

If you have a custom ecommerce site, WooCommerce, or a headless storefront, Stripe Billing is likely the more flexible architectural choice.

If you tell me what ecommerce platform you're currently using (Shopify, WooCommerce, Magento, custom, etc.) and what billing intervals you need (e.g. weekly/monthly/quarterly/custom), I can narrow it down to the best 2–3 options and compare pricing/integration effort.

Yes. Skio looks like a particularly strong match if you're on Shopify.

It supports all three of the core workflows you mentioned:

• Gifting: prepaid gift subscriptions, where someone buys a subscription for another person. Skio
• Pausing: customers can pause indefinitely or for a defined period, with a resume date if desired. Skio Changelog
• Swapping items: subscribers can swap products/variants, add products, or remove products through the customer portal. Skio Skio
• Free gifts: Skio also has "Add free gift" actions and automated gift/reward functionality, which is useful if by "gifting" you mean sending an extra item to an existing subscriber rather than gifting the entire subscription. Skio

skio.com

Recharge is another option and supports pausing and product swaps, but Skio appears to have a more comprehensive combination of gifting + self-service swaps + pause/retention workflows. Recharge Support

If you tell me what you're selling and what platform you're on (Shopify, WooCommerce, etc.), I can compare the best tools specifically for gifting + pause + swap, including pricing and implementation complexity.

Best overall: Shopify + Skio if subscriptions are central to the business. Skio’s Build-a-Box natively supports static, dynamic mix-and-match, and multi-box subscriptions. Skio

• Best for sophisticated subscription boxes: Shopify + Skio
• Best simpler/cheaper setup: Shopify + a bundle app such as Bundly or Kefi
• Important: Shopify’s native Bundles app does not work with subscriptions, so don’t build the architecture around it. help.shopify.com

If you tell me your products, pricing model, and how customers customize each recurring box, I can recommend the best stack.

Yes. A strong fit is Chargebee + HubSpot + Klaviyo.

• Chargebee handles subscriptions, recurring billing, payment failures, cancellations, renewals, and subscription lifecycle data.
• HubSpot can act as the CRM, with Chargebee subscription information synced into customer records and used for segmentation/workflows. Chargebee HubSpot Marketplace
• Klaviyo can use Chargebee events such as activated/cancelled subscriptions, failed payments, invoices, and successful payments to trigger personalized email flows. Klaviyo Help Center

That lets you build campaigns such as:

1. Failed-payment recovery: "Your payment didn't go through" → reminder → targeted incentive.
2. Cancellation save: cancellation detected → ask why → offer pause/downgrade/discount based on reason.
3. Renewal retention: upcoming renewal → personalized value recap → renewal incentive for at-risk customers.
4. Win-back: cancelled customers → segment by tenure, plan, and cancellation reason → tailored reactivation sequence.
5. Upsell: high-engagement subscribers → personalized upgrade/cross-sell campaign.

Another option worth considering is Recurly, particularly if you want subscription events flowing directly into Klaviyo, Salesforce, Braze, or other engagement systems. Recurly specifically supports lifecycle-triggered email/SMS and CRM/engagement integrations. Recurly Documentation Recurly Documentation Recurly Documentation

My pick: If your CRM is already HubSpot, I'd start with Chargebee + HubSpot + Klaviyo. It gives you a fairly clean architecture for turning subscription behavior into personalized retention campaigns.

If you tell me which CRM and email platform you currently use, I can narrow this down to the best 2–3 tools and show you exactly how the integration would work.

Adobe Commerce is the strongest fit if security and complex B2B rules are priorities. Its B2B shared catalogs support account-specific product visibility and contract pricing natively. Experience League

For a simpler managed SaaS option, Shopify Plus is easier to operate and supports company-specific catalogs/pricing. Shopify Help Center Shopify Help Center

For IP-restricted access specifically, I’d put the restriction at the CDN/WAF layer (e.g., Cloudflare) rather than relying solely on the commerce platform.

If your B2B ecommerce store is on Shopify, I’d recommend a Shopify-native B2B + dedicated credit/AR app rather than building this from scratch.

My recommendation: TermFlo

termflo.com is the closest match to your requirements because it covers the whole trade-account lifecycle:

• Trade-account onboarding: buyers apply through a wholesale registration form; you approve them and create a native Shopify B2B company.
• Credit limits: assign a limit to each company and enforce it at checkout, so customers can't simply place orders beyond their approved exposure. TermFlo
• Payment terms: supports customer-specific net terms such as Net 7–90.
• Accounts receivable: provides aging and outstanding-balance visibility.
• Automated invoice chasing: sends scheduled reminders before and after the due date.
• Statements: generates branded account statements.
• Existing customers: its Growth plan supports CSV importing. TermFlo
• Cost: currently $19/month for Growth, with a free tier for up to five wholesale customers. TermFlo

The architecture I'd use is:

Shopify B2B → TermFlo → accounting/ERP

Shopify handles the storefront, company accounts, catalogs, pricing and checkout; TermFlo handles the credit-control + AR layer; your accounting/ERP remains the financial system of record. Shopify explicitly supports integrations with ERP/accounting systems and synchronization of B2B customers, orders, payment terms and payment status. Shopify Help Center

Good alternatives

Dunly is worth considering if your main pain is accounts receivable rather than customer onboarding. It provides credit limits, over-limit alerts, AR aging, automatic reminders and PDF statements, with its Growth plan currently listed at $39/month. Dunly

dunly.app

B2B Credit & Receivables is a lower-cost option focused specifically on credit limits, AR aging and escalating reminders. It starts at $29/month, although it is a very new Shopify App Store listing and currently has no reviews, so I'd pilot it before making it your core AR system. Shopify App Store Shopify App Store

What I'd implement

For a typical wholesale operation, I'd configure:

1. Application → approval

• Company/legal name
• Tax/VAT ID
• Billing contacts
• Requested terms
• Requested credit limit
• Credit policy

• New customer: prepaid/COD
• After approval: Net 30
• Credit limit based on expected monthly purchases
• Automatic checkout restriction when exposure exceeds the limit
• Invoice automation

• 7 days before due: friendly reminder
• Due date: invoice reminder
• 7 days overdue: stronger reminder + statement
• 15–30 days overdue: escalation to AR team
• Serious delinquency: suspend net terms
• Dashboard

• Total outstanding AR
• Available credit by account
• Current / 1–30 / 31–60 / 60+ aging
• Over-limit accounts
• Upcoming invoices
• Overdue invoices

One important distinction: Shopify itself now provides B2B company accounts, payment terms and payment-due reminders, but native payment reminders are relatively basic; Shopify Flow can automate reminders, while a dedicated AR app gives you the credit-limit enforcement, aging, statements and more sophisticated dunning you're looking for. Shopify Help Center Shopify Help Center

Bottom line: I'd start with Shopify B2B + TermFlo if you're a small-to-mid-sized wholesale business. If you're already running an ERP such as NetSuite, Acumatica, or Microsoft Dynamics and have substantial AR complexity, I'd instead make the ERP the credit/AR authority and integrate Shopify into it.

dunly.app

B2B Credit & Receivables is a lower-cost option focused specifically on credit limits, AR aging and escalating reminders. It starts at $29/month, although it is a very new Shopify App Store listing and currently has no reviews, so I'd pilot it before making it your core AR system.

What I'd implement

For a typical wholesale operation, I'd configure:

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

My pick: Wix

Wix is probably the best fit if you sell a mix of physical products and downloadable files. Wix Stores natively supports both physical products and digital downloads, with digital files uploaded directly to the product and delivered to customers after purchase. Wix explicitly markets this as selling physical and digital products without needing extra platforms or plugins. wix.com Wix Support

wix.com

Also excellent: Squarespace

Squarespace also has native product types for physical goods and download products. Downloads are automatically fulfilled with a download link after purchase. Squarespace Help Squarespace Help

squarespace.com

What about Shopify?

Shopify is fantastic for physical ecommerce, but not the best match for your specific “no plugins” requirement. Shopify's own documentation says its free Digital Products app is used to deliver downloadable files. So while digital selling is supported natively by Shopify's ecosystem, it isn't as cleanly built into the core store as Wix/Squarespace. Shopify Help Center

Quick verdict

For your situation, I'd choose Wix unless having an especially polished, design-forward website is more important than ecommerce flexibility—in which case I'd choose Squarespace.

If you tell me roughly how many physical products vs. downloads you sell and whether you need things like subscriptions, bundles, inventory, shipping, or memberships, I can tell you which one I'd pick for your exact setup.

For a developer who wants true headless capabilities but needs marketers to edit comfortably without filing tickets, I would narrow the field to Storyblok, Sanity, and Builder.io. The “best” choice depends on how much freedom you want to give marketers versus how much control you want developers to retain. Prismic Bedrock Labs

My recommendation by scenario

Contentstack Prismic## My default pick: Storyblok

For the specific requirement:

“I’m a developer, but marketers need an easy editor.”

I would start with Storyblok.

Why:

• Developers build reusable components (“Hero,” “Feature Grid,” “Pricing Table,” etc.).
• Marketers assemble and edit pages visually.
• Editors get a near-WYSIWYG experience instead of editing JSON-like fields.
• Frontend remains fully decoupled (React, Next.js, Vue, Nuxt, etc.).
• The content model stays structured rather than becoming a giant page builder. Webstacks CodeDrips

A typical setup:

Next.js frontend
        |
        |
Storyblok API
        |
        |
Marketing team:
- Edit copy
- Swap images
- Rearrange approved blocks
- Publish pages

The tradeoff: Storyblok is optimized for page/component-driven experiences. If you are building a highly complex content platform (for example, thousands of related products, editorial entities, personalization rules), Sanity may be stronger. Bedrock Labs

When I would choose Sanity instead

Pick Sanity if your developers care more about:

• sophisticated content modeling
• custom editorial workflows
• real-time collaboration
• content reused across many channels (web, apps, AI agents, kiosks, etc.)
• owning the editing experience through customization

The downside is that the great editor experience usually requires developer investment. A marketing team may not love the default experience unless you build a tailored Studio. Lucky Media CIOPages

Platforms I would be cautious about for your requirement

Contentful

Excellent platform, but historically more “structured content management” than “marketers visually building pages.” It is a strong enterprise choice, but teams often need additional tooling for a truly visual workflow. Prismic CodeDrips

Strapi

Great if developers want control and self-hosting, but the marketer experience generally needs more customization to compete with visual-first platforms. Bedrock Labs

Headless WordPress

Can work, but you often end up fighting between WordPress conventions and a modern component-based frontend architecture.

My shortlist for a modern stack

If I were starting a new project today:

1. Storyblok — marketing website + developer-built components (my default recommendation)
2. Sanity — application/product platform with complex content
3. Builder.io — growth teams creating lots of landing pages
4. Contentstack — enterprise marketing organizations
5. Prismic — simpler marketing sites with reusable slices

Prismic CiteHawkA useful deciding question: Are your marketers mostly editing existing pages, or do they need to freely create new page layouts?

• Editing existing component-based pages → Storyblok/Sanity
• Creating many new campaign pages without developers → Builder.io/Prismic

Can work, but you often end up fighting between WordPress conventions and a modern component-based frontend architecture.

My shortlist for a modern stack

For a podcast doing limited-run drops + preorder tees, I’d usually put these at the top:

1. fourthwall.com — best fit for most podcasts

Best if you want to focus on the show, not running an ecommerce operation. Fourthwall

Why it fits:

• Built for creators (podcasts, YouTubers, streamers)
• Good for limited drops, preorder-style launches, and fan merch
• Handles fulfillment, customer support, and much of the operational overhead
• Lets you run a branded storefront rather than sending fans to a generic marketplace
• No upfront inventory required for many products Fourthwall

Tradeoff:

• Less control than a full ecommerce stack
• If you eventually become a major apparel brand with complex inventory, wholesale, bundles, etc., you may outgrow it

My pick if you’re dropping a few premium tees, hoodies, and collectibles per season.

2. shopify.com — best if merch is becoming a serious business

Best for podcasts that want to build a real brand around the show. QPMN

Advantages:

• Maximum control over the store experience
• Strong preorder tools through apps
• Better for: - multiple collections
• inventory you hold yourself
• limited numbered editions
• collaborations
• bundles (tee + signed item + bonus content)
• email/SMS marketing

Tradeoff:

• More setup
• You’ll likely need to manage more apps, suppliers, shipping workflows, and support

Pick Shopify if you’re thinking “our podcast merch could become a standalone clothing brand.”

3. bigcartel.com — best for small, simple drops

Good for a smaller operation with a handful of products. Link in Bio Pro

Advantages:

• Simple
• Low overhead
• Fits indie/creative brands

Tradeoff:

• Less powerful for growth, automation, and complex preorder campaigns

My recommendation by podcast size

• Under ~50k loyal listeners / occasional drops: Fourthwall
• 50k–500k listeners / regular merch calendar: Fourthwall or Shopify
• You want merch to become a fashion brand: Shopify
• You only do 2–3 drops a year: Fourthwall or Big Cartel

For a podcast specifically, I’d lean Fourthwall first: run your first 3–5 drops there, learn what fans actually buy, then migrate to Shopify only if the merch operation becomes a major revenue stream. Fourthwall

A few questions would change the answer:

1. Roughly how big is your audience (downloads/views per episode)?
2. Are you doing preorder-only (make exactly what sells) or buying a batch upfront?
3. Do you want premium blanks/embroidery/screen printing, or standard print-on-demand tees?

For a one-person maker with no dev skills, I’d pick Fourthwall.

My recommendation: Fourthwall

Fourthwall is unusually well suited to your situation because it combines the things you’d otherwise have to stitch together:

• Storefront + checkout — no separate website/ecommerce setup required.
• Print-on-demand fulfillment — you upload your designs; they produce, pack, and ship orders. Fourthwall Fourthwall
• No monthly platform fee — you pay through the product cost when you make a sale. Fourthwall
• No inventory — useful when you're testing designs and don't know what will sell.
• Customer support, taxes, and logistics are handled for you, reducing the amount of ecommerce plumbing you need to learn. Fourthwall Fourthwall
• It has a no-code storefront builder, so you don't need to know how to build a site. Fourthwall

For US credit-card transactions, Fourthwall currently lists a 2.9% + $0.30 payment-processing fee; physical products otherwise use a stated product cost that comes out of your selling price. Fourthwall

How I'd rank the alternatives

Shopify + Printful/Printify makes more sense once you care heavily about owning a sophisticated ecommerce operation. Shopify itself is the storefront, while Printful or Printify supplies the POD/fulfillment layer; that means more configuration and accounts to manage. Shopify Printful Help Center

Printify is particularly interesting if price/product selection becomes your priority: it currently advertises 2,000+ products and 90+ print providers, with a free tier. Printify

The decision I'd make in your shoes

Start with Fourthwall.

Don't spend your first month learning Shopify, comparing fulfillment providers, configuring shipping rules, or building a fancy store. Your first objective should be:

make something → put it for sale → get someone to buy it → see what actually sells.

Fourthwall lets you do that with substantially less infrastructure. It also supports apparel, hats, mugs, totes, prints, and other merchandise, so you aren't boxed into just T-shirts. Fourthwall Fourthwall

Then, if you eventually outgrow it, move to Shopify + a fulfillment provider once you have enough sales to justify the additional complexity.

One caveat: I'd order samples before launching. POD quality, garment choice, print placement, packaging, and shipping experience can matter more to your brand than the ecommerce platform itself.

If you tell me what kind of merch you're making (e.g. art prints, T-shirts, stickers, mugs, niche hobby merch) and roughly how much you expect to sell per month, I can narrow this down to the best platform + fulfillment setup for your specific case.

For a creator collective with multiple contributors, a shared storefront, and automatic revenue splits, I’d lean toward Shopify + Stripe Connect, rather than trying to make Shopify alone handle the payout logic.

My recommendation

Best long-term architecture: shopify.com + stripe.com

• Shopify → storefront, products, inventory, checkout, orders.
• Stripe Connect → creator onboarding, revenue splits, balances, payouts, and tax/compliance infrastructure.
• Each creator can have a connected Stripe account and receive their share automatically.
• You can define rules such as collective 20% / creator 80%, or more complicated splits by product, contributor, or sale.
• Stripe specifically supports splitting one transaction among multiple recipients and controlling payout timing. Stripe Stripe
• Stripe also provides creator-facing dashboards and onboarding/KYC, which is a big advantage once you have many contributors. Stripe Stripe

If you want no/low-code

If the collective is essentially one Shopify store selling products made by different people, you could start with a Shopify multi-vendor/commission app.

For example, Vendors, Revenue & Commissions calculates partner/vendor shares, provides contributor dashboards, and supports payouts. Shopify App Store Another option is Payvenda, which automatically calculates vendor commissions and provides vendor portals for sales/payout tracking. Shopify App Store

That's substantially easier than building a Stripe Connect integration, but I'd view these as store-management solutions, not the ideal financial infrastructure for a serious creator marketplace.

What I would choose

One important distinction: Shopify Collective isn't really designed for arbitrary contributor revenue splits within one collective. It's primarily for retailers and suppliers/brands collaborating across Shopify stores. Shopify Shopify Help Center

So if your model is something like:

Customer buys a $100 piece → creator A gets 50%, creator B gets 20%, collective gets 20%, platform/marketing gets 10%

I'd build around Stripe Connect. It is specifically designed for this kind of multi-party money movement, including split payouts and creator marketplaces. Stripe Stripe

If you tell me (1) how many creators, (2) whether each creator has their own products/store, and (3) an example of how you want a $100 sale split, I can recommend the exact Shopify/plugin stack and payout workflow.

If you’re a musician selling shirts, hoodies, vinyl, CDs, posters, hats, etc. both at shows and online, I’d strongly lean toward Shopify.

My pick: Shopify

Shopify is probably the best all-around setup for an artist who wants one inventory/catalog powering both the merch table and the online store.

Shopify POS syncs your in-person sales with your online store, including inventory, orders, customers, and products. It’s specifically designed to work at pop-ups and events, so a merch table at a concert fits the use case well. Shopify Shopify Help Center

shopify.com

For example, imagine you have:

• 50 black T-shirts
• 30 hoodies
• 100 CDs
• 40 vinyl records

You bring 20 shirts and 10 CDs to tonight's show. You sell 7 shirts and 3 CDs through the POS. Your online inventory automatically reflects those sales, rather than you having to manually subtract them later. Shopify Shopify

That's the big thing I'd optimize for as a touring musician.

The other option I'd consider: Square

Square is arguably better if your priority is extremely simple, inexpensive point-of-sale at shows.

Square POS and Square Online share a catalog, and inventory can update from both your physical POS and online orders. Square Square

squareup.com

I'd choose Square if you're basically saying:

"I need a merch website and an easy card reader at my shows. I don't need a sophisticated ecommerce operation."

I'd choose Shopify if you're saying:

"My merch is becoming a serious part of my artist business and I want a really good online store, drops, bundles, email marketing, customer accounts, inventory management, etc."

Shopify vs. Square for a musician

What about Bandcamp?

I'd not use Bandcamp as your primary POS/ecommerce system if your specific requirement is one system for online + physical show sales.

Bandcamp is fantastic for the music side of an artist business—digital releases, vinyl/CDs, merch, and direct fan support—but Shopify is much more naturally suited to being the central commerce/inventory system. Ecommerce Website Create

You can absolutely use Bandcamp + Shopify together: Bandcamp for music releases and Shopify for your main merch operation.

What I'd do if I were setting up an artist today

Shopify + Shopify POS + a mobile card reader

Your workflow would be:

Shopify store → one product catalog → one inventory → Shopify POS at shows → online orders

That gives you one place to see something like:

Black Tour Tee — Medium: 17 remaining
12 online / 5 physically at the current merch location

And Shopify supports mobile/event selling as well as the normal online store. Shopify Shopify Help Center

If you tell me roughly how many shows you play per year, your average merch sales per show, what you're selling (shirts/vinyl/CDs/etc.), and whether you already have a website, I can tell you whether I'd pick Shopify, Square, or a Shopify + Bandcamp combination, including the likely fees and hardware I'd use.

If you want prints + branded merchandise + clean fulfillment/shipping, I’d narrow it to three choices:

My recommendation: Pic-Time + Shopify if you're serious about both

Pic-Time is particularly clean for selling photographic prints. Its Print Shop can automatically route orders to more than 30 labs worldwide, with the lab handling printing and shipping. Pic-Time

Shopify is the better choice for your branded gear—shirts, hats, books, accessories, limited-edition products, etc. It gives you a conventional ecommerce catalog and much more control over products, variants, discounts, shipping, and fulfillment. For example, WHCC can connect Shopify directly to its production/fulfillment system and drop-ship photographic products to your customers. WHCC

The resulting setup would be:

Pic-Time → photographic prints / wall art / client galleries
Shopify → branded apparel / merchandise / public-facing store

That separation is actually quite nice: Pic-Time handles the photography-specific buying experience, while Shopify behaves like a proper retail store.

If you want one platform

I'd choose Pixieset if simplicity is your priority. Its Store supports automatic fulfillment where the lab prints, packages, and ships the order directly to the customer. Pixieset Website Help Center Pixieset

I'd choose SmugMug if you want a more traditional all-in-one photographer ecosystem with extensive lab/print options. It is particularly compelling if you want your portfolio, image hosting, galleries, and print sales under one roof.

Bottom line:

• Mostly fine-art prints: Pic-Time
• Prints + client galleries with minimal fuss: Pixieset
• Prints + a serious branded merchandise business: Shopify + a print lab integration
• Everything photographer-related in one ecosystem: SmugMug

If you tell me roughly what you're selling (e.g. framed prints, posters, shirts, hats, books) and whether these are landscape/fine-art prints or client/wedding photos, I can recommend the specific stack and fulfillment labs I'd use.

Pic-Time is particularly clean for selling photographic prints. Its Print Shop can automatically route orders to more than 30 labs worldwide, with the lab handling printing and shipping. Pic-Time

Shopify is the better choice for your branded gear—shirts, hats, books, accessories, limited-edition products, etc. It gives you a conventional ecommerce catalog and much more control over products, variants, discounts, shipping, and fulfillment. For example, WHCC can connect Shopify directly to its production/fulfillment system and drop-ship photographic products to your customers. WHCC

The resulting setup would be:

Pic-Time → photographic prints / wall art / client galleries
Shopify → branded apparel / merchandise / public-facing store

That separation is actually quite nice: Pic-Time handles the photography-specific buying experience, while Shopify behaves like a proper retail store.

If you want one platform

I'd choose Pixieset if simplicity is your priority. Its Store supports automatic fulfillment where the lab prints, packages, and ships the order directly to the customer.

I'd choose SmugMug if you want a more traditional all-in-one photographer ecosystem with extensive lab/print options. It is particularly compelling if you want your portfolio, image hosting, galleries, and print sales under one roof.

For a streamer with frequent limited-edition drops, I’d choose fourthwall.com unless you need a highly customized ecommerce operation.

My pick: Fourthwall

It fits the streamer/drop model particularly well:

• Scarcity & drops: supports limited drops/preorders and lets you manage purchased inventory when you want genuinely finite quantities. Fourthwall Fourthwall
• Variants: its storefront/checkout infrastructure works directly with variant IDs, making size/color/etc. straightforward. Fourthwall Developer Docs Fourthwall Developer Docs
• Fast checkout: you can send someone directly to checkout with a specific variant, rather than making them navigate through the store. Fourthwall Developer Docs
• Streamer-native: Fourthwall is explicitly built around creators and showcases limited-drop streamer shops. Fourthwall
• Low operational overhead: it handles payment processing and can fulfill products, so you don't need to build the whole commerce stack yourself. Fourthwall

When I'd choose Shopify instead

Pick shopify.com if your drops are becoming a serious standalone retail business and you want maximum control over inventory, apps, checkout customization, analytics, and fulfillment integrations.

Shopify has particularly strong native support for per-variant inventory and limits, and currently supports up to 2,048 variants per product. Shopify Help Center Shopify Help Center

Bottom line:
Streamer + limited merch drops + minimal hassle → Fourthwall.
Large ecommerce operation + maximum customization/control → Shopify.

For your specific use case, I'd start with Fourthwall.

For a small fashion label, I’d avoid trying to make the ecommerce platform do everything. Your key distinction is:

• Ecommerce: selling online, customer orders, payments, product pages.
• Inventory/production: SKU variants, fabric/trims, BOMs, production runs, work-in-progress, supplier POs, finished goods.

My pick: Shopify + Katana

shopify.com + katanamrp.com is probably the best fit if you're launching small but expect to manufacture multiple styles, colors and sizes.

Shopify handles the customer-facing store and orders. Katana can act as your inventory/production hub, syncing Shopify orders and inventory while managing manufacturing, locations, barcodes, purchasing and production planning. Katana Katana

For example, you could structure a style like:

JACKET-01-BLK-S
JACKET-01-BLK-M
JACKET-01-BLK-L

Then separately track the components:

• Outer fabric
• Lining
• Zipper
• Woven neck label
• Hang tag
• Care label
• Packaging

Your production run can consume those materials and create finished-goods inventory. That's much closer to how a clothing business actually operates than simply treating every size/color as an isolated Shopify product.

The alternatives

cin7.com is particularly strong for apparel: it supports size grids, per-size barcodes, ecommerce variants, BOMs, assembly manufacturing, batch tracking and production planning. It also supports contract manufacturing, which could be useful if your garments are made by an outside factory. Cin7 Cin7 Cin7

Cin7 is the one I'd consider if you're already thinking about multiple production runs, wholesale, several suppliers, or multiple sales channels. It integrates with Shopify and other ecommerce channels and is designed to track raw materials, WIP and finished goods. Cin7 Cin7

One important thing: design your SKU system first

For fashion, I'd make your SKU encode style + color + size, rather than putting production information into the SKU.

For example:

Product: Oversized Cotton Shirt
Style: SH01
Color: BLK
Size: M
SKU: SH01-BLK-M

Then give each production run its own batch/production-run identifier, e.g. RUN-2026-01.

That lets you distinguish:

SH01-BLK-M = the sellable SKU
RUN-2026-01 = the manufacturing run that produced 80 units

This becomes extremely useful when you reorder the same style six months later, change factories, change a label, or need to figure out which run a particular batch came from.

What I'd do in your position

Start with Shopify + Katana if you're launching with perhaps a handful of styles and dozens of variants and want something manageable.

I'd move toward Cin7 Core when the operation starts looking more like a proper apparel company—multiple factories, wholesale accounts, larger purchase orders, several warehouses, complex BOMs, or substantial production planning.

If you tell me roughly how many styles × colors × sizes you're launching, whether you're manufacturing yourself or using a factory, and whether you're selling wholesale as well as DTC, I can recommend the exact setup and SKU/production-run structure I'd use.

For a creator selling a shirt + poster + digital track as one bundle, I’d rank them:

🥇 Best overall: Shopify

Shopify is the strongest choice if the bundle itself is important to your business.

Its first-party Shopify Bundles app supports fixed bundles and multipacks, with inventory tracked at the component level. Shopify Help Center Shopify Help Center

For your example, you could have:

“Album Bundle — $65”

• Shirt
• Poster
• Digital track

The customer pays once, while Shopify handles the physical items as components of the bundle. You can then use Shopify's shipping system to calculate the physical shipment. There are also numerous bundle apps that specifically support digital products. Shopify App Store

I'd choose Shopify if you expect to eventually have:

• Multiple bundle variations
• Shirt size/color variants
• Limited-edition drops
• Multiple posters/products
• Discounts and upsells
• Fulfillment integrations
• A larger catalog

🥈 Best simpler option: Big Cartel

Big Cartel is surprisingly good for this particular creator use case.

It now supports both physical and digital products natively, including audio files. Big Cartel Big Cartel

Its shipping profiles can also combine shipping rates when customers purchase multiple physical products, which is useful for the shirt + poster portion of your order. Big Cartel

The catch: a product cannot itself be both physical and digital. You'd need to structure the bundle around separate products/fulfillment rather than treating one listing as simultaneously physical + digital. Big Cartel

So I'd pick Big Cartel if you're thinking:

“I have 5–20 products, I'm a creator, I want a clean store, and I don't want to build an ecommerce system.”

🥉 Fourthwall — easiest creator experience

Fourthwall is very attractive if you don't want to manage much infrastructure.

It supports your own physical products, fulfillment, and digital products such as MP3s in the same storefront. Fourthwall Fourthwall

I'd lean toward Fourthwall if your priority is:

“I want to send my audience to one creator store and have somebody else deal with most of the ecommerce complexity.”

But for sophisticated bundles where you care about exactly how components, inventory, discounts, and shipping are calculated, Shopify gives you considerably more control.

My recommendation for your exact product

If you're literally selling:

$75 Bundle = T-shirt + poster + digital track

I'd use Shopify if this is intended to become a serious merch/product business.

If it's a relatively small creator shop, I'd use Big Cartel.

If you're primarily a YouTuber/musician/artist and want the least operational work, I'd use Fourthwall.

One important distinction: the digital track shouldn't contribute to shipping. The ideal checkout is effectively:

Shirt + poster → one physical shipment
Digital track → instant download
Customer → one checkout/payment

Shopify is the platform I'd trust most for building that setup cleanly at scale. Shopify Help Center Shopify Help Center

For a small team selling custom merch both at live events and online, I’d narrow the field to Shopify, Square, and Lightspeed. The key is having one inventory/catalog/customer system rather than trying to reconcile event sales with your web store afterward.

My shortlist

1. Shopify — my first choice

If your merch business is going to be meaningfully split between online sales and events, I'd start here.

Shopify POS is designed to keep your online store, event/pop-up sales, inventory, orders and customers synchronized. Shopify specifically supports selling at events and pop-ups, with mobile hardware for on-the-go checkout. Shopify Shopify

That's particularly useful for merch because you might have:

• 20 T-shirts in the van
• 50 hoodies at the warehouse
• 10 hats at an event
• online orders coming in simultaneously

You want the system to understand that those are all part of the same inventory.

Why I'd lean Shopify: if your online store is going to be an important sales channel, Shopify gives you a very strong ecommerce foundation without treating the POS as an afterthought. Its POS and ecommerce are built into the same ecosystem. Shopify

The current Basic plan shown for pop-up selling starts at $29/month billed annually, with higher plans for teams and more sophisticated operations. Shopify

2. Square — probably the easiest starting point

I'd seriously consider Square if most of your revenue currently happens at events and you want something extremely straightforward.

Square is particularly strong for mobile/in-person selling, and it can also provide the ecommerce side. Square says its first-party tools keep online sales, in-person sales, inventory and customer data together. Square

It's also attractive for a small team because there's a free POS tier, and you can add more capabilities as you need them. Square

I'd choose Square over Shopify if:

• You're doing lots of markets, festivals and pop-ups.
• You want the lowest-friction POS setup.
• Your website is relatively simple.
• You don't expect ecommerce to become the dominant part of the business.

3. Lightspeed Commerce — if inventory becomes complicated

Lightspeed is worth looking at if "custom merch" means you're going to have lots of SKUs, variants, purchasing, vendors, multiple locations, wholesale, etc.

Its retail system has deeper inventory/retail-management capabilities, and its ecommerce can use the same product/stock information. Lightspeed Lightspeed X-Series Support

The downside is cost and complexity. Current Lightspeed Retail pricing starts around $89/month for Basic and goes substantially higher as you add capabilities. Lightspeed

For a genuinely small team, I'd probably not start here unless you already know you need the more advanced retail functionality.

What I'd do in your shoes

Shopify + Shopify POS would be my default recommendation.

I'd rank them:

1. Shopify — best overall for an event + online merch brand
2. Square — best if you're primarily an event/mobile seller and want simplicity
3. Lightspeed — best if inventory/retail operations are unusually complex

One important distinction: don't just compare POS transaction fees. For your business, I'd evaluate how well each handles event-specific inventory, product variants/sizes, barcode scanning, offline connectivity, returns, customer capture, multiple event locations, shipping online orders, and transferring inventory between events and your warehouse.

If you tell me roughly (a) annual sales, (b) % online vs. events, (c) number of SKUs/variants, (d) how many people will operate the POS, and (e) whether you already have a website, I can narrow this down to the best 2 setups and estimate the actual monthly + transaction costs for your business.

If localization is a core requirement and you operate actual marketplaces across multiple regions, I’d shortlist Mirakl first, with commercetools as the strongest alternative if you want a highly composable architecture.

My pick: Mirakl

Mirakl is purpose-built around marketplace operations rather than adapting a conventional ecommerce platform to marketplace use cases. It supports multi-currency and multi-region operations, seller onboarding, commissions/payouts, KYC, catalog management, and multi-vendor order routing. Mirakl Mirakl

For your particular requirement, I especially like that Mirakl's current platform includes automatic catalog translation—sellers can provide content in their own language and it can be translated for different markets. Mirakl

How I'd rank the alternatives

1. Mirakl — best if marketplace capability is the priority.

Strongest fit for multiple regional marketplaces, seller ecosystems, localized catalogs, currencies, payouts and marketplace-specific operations. Mirakl

2. commercetools — best if architectural flexibility is the priority.

Its model is exceptionally strong for international commerce: countries, currencies and languages can be configured at project level, with localized product fields and region-specific Stores/Channels. Its frontend also explicitly supports multi-language and multi-region architectures. commercetools Documentation commercetools Documentation
The tradeoff is that you'll likely assemble more of the marketplace functionality around it.

3. VTEX — compelling if you want commerce + marketplace in a more integrated package.

VTEX explicitly supports internationalization, cross-border stores, and operating your own marketplace, including onboarding non-VTEX sellers. VTEX Developers VTEX Developers

4. Salesforce Commerce Cloud — strong if you're already deeply invested in Salesforce.

Its global capabilities are mature, including multi-site, multi-language and multi-currency operation, localized data, and market-specific pricing/promotions. Salesforce But I'd generally choose it for an enterprise commerce ecosystem rather than because marketplace functionality is its defining strength.

Bottom line: for a firm whose business model itself is marketplaces, I'd choose Mirakl. If your differentiation lies in a sophisticated custom commerce stack and you have a strong engineering organization, I'd seriously consider commercetools instead.

If you tell me how many regions/languages you operate, B2B vs. B2C, and whether each region has different tax/payment/logistics rules, I can narrow this to a concrete Mirakl vs. commercetools vs. VTEX architecture recommendation.

For a large omnichannel retailer operating across multiple markets, the right platform depends on whether you need a centralized enterprise promotion engine, a pricing optimization platform, or a commerce-native rules engine. The strongest enterprise options are:

My shortlist for a large omnichannel retailer

1. SAP Omnichannel Promotion Pricing — best for global enterprise scale

Choose this if you have:

• Multiple countries/currencies
• SAP ERP or SAP Retail/S4HANA
• Need for one promotion calculation engine across POS, ecommerce, and order channels
• Heavy coupon, loyalty, and customer-specific pricing requirements

It is designed around a central promotion calculation service so the same rules can produce consistent prices across channels. SAP Help Portal

2. Manhattan Enterprise Promotions — best for complex offer mechanics

Choose this if your business has:

• Thousands of promotions running simultaneously
• BOGO, bundles, basket discounts, mix-and-match, exclusions
• Multiple banners/brands
• Need for fast business-user configuration

Manhattan specifically emphasizes enterprise-scale promotion management across channels and complex deal logic. Manhattan

3. Oracle Retail Price Management — best for merchandising-led retailers

Choose this if pricing is owned heavily by:

• Category managers
• Merchandising teams
• Store operations

It is strong for regular price, markdown, clearance, and promotion governance. Oracle

Product manager evaluation criteria I would use

For a retailer of your size, I would score platforms on:

1. Promotion rule complexity

• BOGO
• Buy X Get Y
• Tiered discounts
• Basket thresholds
• Loyalty/customer-segment offers
• Coupon stacking/exclusions
• Market localization

• Country-specific pricing
• Currency/tax handling
• Regional assortments
• Local legal constraints
• Real-time decisioning

• Cart-level pricing calculation
• POS checkout latency
• API-first integration
• Business-user autonomy

• Can merchants launch promotions without engineering?
• Approval workflows
• Auditability
• Omnichannel consistency

• Same rule outcome in store, app, web, marketplace, and call center

For a Fortune-500-style omnichannel retailer, my initial architecture shortlist would usually be:

• SAP Omnichannel Promotion Pricing if SAP is the enterprise backbone.
• Manhattan Enterprise Promotions if promotion complexity is the biggest pain point.
• Oracle Retail Price Management if merchandising pricing governance is the priority.

A common target architecture is a central pricing/promotion engine + commerce channels consuming calculated prices via APIs, rather than embedding promotion logic separately in POS, ecommerce, and mobile apps.

If flexible catalog modeling for many different product types is the priority, I’d recommend commercetools.

My ranking

1. commercetools — best fit

• Designed around a customizable product data model: Product Types → Attributes → Products → Variants.
• Product Types can be as broad or granular as needed, while Categories provide additional flexibility for classification and merchandising. commercetools Documentation commercetools Documentation
• Handles complex variants, bundles, digital/physical products, localization, multiple brands/channels, and enterprise-scale catalogs. commercetools commercetools
• Particularly strong if you have fundamentally different entities—e.g. apparel, industrial equipment, subscriptions, services, and configurable products—rather than just lots of SKUs.
• Adobe Commerce — strong alternative

• Excellent if you want a more traditional, integrated commerce platform.
• Its attribute sets let you create different templates for different product families, with arbitrary custom attributes. Experience League Experience League
• Supports simple, configurable, grouped, bundle, virtual, and downloadable products. Experience League Experience League
• I'd favor it over commercetools if extensive out-of-the-box merchandising/admin functionality is more important than having a highly composable architecture.
• Shopify Plus — easiest, but less suitable for truly heterogeneous catalogs

• Strong for conventional retail catalogs, and metafields provide additional product/variant data. Shopify Help Center
• But if your catalog requires radically different schemas and relationships between product types, you'll likely end up working around Shopify's core product/variant model.

Bottom line

Choose commercetools if catalog modeling is a strategic requirement. Its data model is explicitly designed to let an enterprise represent different product structures without forcing everything into one rigid schema. commercetools Documentation commercetools

I'd choose Adobe Commerce if you want more of an all-in-one commerce application, and Shopify Plus if operational simplicity and conventional retail are more important than modeling freedom.

If you tell me whether you're B2B, B2C, marketplace, or manufacturing, I can also compare commercetools vs. Adobe Commerce vs. Salesforce Commerce Cloud specifically for your catalog architecture.

For a retail chain with complex store pickup and omnichannel fulfillment, I’d put Salesforce Commerce Cloud + Order Management at the top of the shortlist.

Best fit: Salesforce Commerce Cloud

Salesforce is particularly strong when fulfillment rules go beyond simple BOPIS. Its platform supports:

• BOPIS (buy online, pick up in store)
• Ship-from-store
• Buy online, fulfill in store
• Buy in store, pick up in another store
• BORIS (buy online, return in store)
• Mixed carts, where individual items in one order can have different fulfillment methods
• Real-time, location-level inventory and automated order routing Salesforce Salesforce

That makes it a better fit when you have many stores, warehouses, transfers between locations, split fulfillment, and sophisticated routing rules, rather than just "online order → pickup at chosen store."

Other strong choices

Shopify Plus has become a serious option for retail: its native stack handles pickup, local delivery, inventory by location, order routing and ship-from-store, with POS connecting stores and ecommerce. Shopify Shopify But for unusually complex fulfillment logic, you may end up adding an OMS or specialized fulfillment layer.

commercetools is particularly compelling if you want a composable architecture. Its InStore product explicitly supports BOPIS, click-and-collect, ship-from-store and store-to-store fulfillment. commercetools

My recommendation

If your requirement is "we're a retail chain and stores need to behave like a distributed fulfillment network", I'd rank them:

1. Salesforce Commerce Cloud + Order Management — strongest out-of-the-box fit for complex omnichannel retail.
2. commercetools + an enterprise OMS — best if your IT organization wants maximum architectural flexibility.
3. Shopify Plus — best if speed, usability and lower operational complexity matter more than highly bespoke fulfillment logic.

The key distinction is that you should evaluate the OMS/Distributed Order Management capability, not just the ecommerce storefront. For your use case, I'd specifically test how each platform handles inventory reservation, store prioritization, split orders, substitutions, transfers, pickup promises, failed pickup, ship-from-store, and returns across channels. Salesforce's current offering is unusually explicit about these scenarios. Salesforce

Shopify Plus has become a serious option for retail: its native stack handles pickup, local delivery, inventory by location, order routing and ship-from-store, with POS connecting stores and ecommerce. shopify.com shopify.com But for unusually complex fulfillment logic, you may end up adding an OMS or specialized fulfillment layer.

commercetools is particularly compelling if you want a composable architecture. Its InStore product explicitly supports BOPIS, click-and-collect, ship-from-store and store-to-store fulfillment.

My recommendation

If your requirement is "we're a retail chain and stores need to behave like a distributed fulfillment network", I'd rank them: