All answers

For a small handmade-goods shop, I’d pick Shopify.

• No coding required: its visual editor lets you build pages with drag-and-drop sections and customizable themes. Shopify Shopify
• Fully hosted: Shopify handles hosting, security, updates, and infrastructure, so you don't need to manage a server. Shopify Shopify
• Good for physical products: you can add products, variants, inventory, payments, shipping, and checkout from the same admin. Shopify Help Center Shopify Help Center
• Room to grow: you can start simple with a theme and later add apps or more advanced customization if the business takes off. Shopify

shopify.com

Runner-up: Squarespace is worth considering if your top priority is a particularly beautiful, brand-focused website and you have a relatively small catalog. It also supports physical products and hosted, no-code site building. support.squarespace.com squarespace.com

If you tell me roughly how many products you sell and your monthly budget, I can narrow it down to Shopify vs. Squarespace vs. Wix and tell you which I'd choose.

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.

For a high-traffic sales event or flash deal, I’d generally pick Shopify Plus if reliability during sudden traffic spikes is the top priority.

Best options

Why Shopify Plus stands out: Shopify's Storefront API is specifically designed to scale during surges and flash sales, and Shopify provides dedicated tooling such as Launchpad for scheduling promotions, inventory releases, pricing changes, and product drops. Shopify Shopify Help Center

Shopify also explicitly documents preparation for flash sales involving tens of thousands of customers entering checkout within minutes, including reviewing third-party apps, shipping integrations, and payment capacity. Shopify Help Center

BigCommerce Enterprise is probably my second choice. It's fully hosted and advertises 99.99% uptime and infrastructure designed for high-volume traffic, while giving you more flexibility for API-first/headless implementations. BigCommerce

My recommendation

• DTC + sudden viral/flash-sale traffic → Shopify Plus
• Enterprise + highly customized/headless architecture → BigCommerce Enterprise
• Very complex multi-site/ERP/custom business logic + large engineering team → Adobe Commerce
• Don't want to manage infrastructure during the sale → favor Shopify Plus or BigCommerce over self-hosted WooCommerce

One important caveat: the platform isn't the only bottleneck. Third-party apps, payment providers, shipping-rate services, custom APIs, and inventory integrations can still take down or slow checkout during a spike. Shopify specifically warns merchants to test those components before major flash sales. Shopify Help Center

If you tell me your expected peak concurrent users/orders per minute, catalog size, and whether you're B2C or B2B, I can give you a more specific Shopify Plus vs. BigCommerce vs. Adobe Commerce recommendation.

BigCommerce Enterprise is probably my second choice. It's fully hosted and advertises 99.99% uptime and infrastructure designed for high-volume traffic, while giving you more flexibility for API-first/headless implementations.

My recommendation

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?

For a small handmade-goods shop where you’re not very tech-savvy, I’d start with shopify.com.

Why I’d pick Shopify

• You don’t need to code. Shopify has a drag-and-drop/no-code store editor and prebuilt themes. Shopify Shopify Help Center
• It’s built for selling, rather than primarily being a website builder. You can manage products, orders, customers, payments, shipping, and inventory in one place. Shopify Help Center
• It can grow with you. You can start with a relatively small catalog and later add more products, sales channels, marketing, and other features without rebuilding your store. Shopify Help Center
• The built-in AI help is useful for beginners. Shopify's Sidekick can give guidance in everyday language, while Shopify Magic can help with product descriptions and other content. Shopify Help Center

The other one I'd consider

squarespace.com would be my second choice. It's particularly attractive if the visual presentation of your brand is more important than having the deepest ecommerce features. It has professionally designed layouts and supports physical products, payments, shipping, taxes, and checkout. Squarespace Help Squarespace Help

My recommendation: If you're serious about turning your handmade shop into a long-term business, choose Shopify. If you mainly want a gorgeous, simple website with a relatively small shop, choose Squarespace.

And I wouldn't start with WooCommerce or a self-hosted WordPress store—you'd be taking on technical maintenance that you probably don't need right now.

If you tell me what you make, roughly how many products you have, and whether you already sell on Etsy/Instagram, I can tell you exactly which setup I'd use and what it would cost.

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 tiny team selling internationally, I’d pick Shopify—specifically Shopify + Markets + Managed Markets if you're eligible.

Why Shopify is probably the simplest

• Multi-currency: Shopify Markets lets you set markets by country/region and show customers local currencies and pricing from one store. Shopify supports 130+ currencies. Shopify Shopify Help Center
• Taxes/duties: The big advantage is Managed Markets. It uses Global-e as the merchant of record, handling foreign tax registration/remittance, duties, customs, and local compliance for eligible international sales. Shopify Help Center
• One admin: You don't need separate stores for every country. Markets centralizes international settings in one Shopify store. Shopify Help Center
• Good fit for a small team: It's hosted SaaS, so you aren't maintaining servers, plugins, security, or a complicated tax stack. Shopify
• Tax calculation: Shopify Tax handles automatic sales-tax calculations, with a free threshold before per-order fees kick in. Shopify Help Center Shopify Help Center

The important distinction

There are really two levels:

Shopify Markets:
You handle the legal/tax responsibilities yourself in each country. Shopify gives you the tools to calculate/display taxes, currencies, duties, etc. Shopify Help Center

Shopify Managed Markets:
Much closer to "turn on international selling and let someone else deal with the bureaucracy." Global-e becomes the merchant of record and handles foreign tax registration/remittance and customs-related responsibilities. Shopify Help Center

For a tiny team, I'd strongly favor the second option if your products/business qualify.

What I'd choose

So if your priority is "we want to sell worldwide without hiring an ecommerce/tax person", I'd start with Shopify.

If you tell me what you're selling, where your company is based, and your first 3–5 target countries, I can narrow down whether Shopify Managed Markets, BigCommerce, or a merchant-of-record platform like Paddle/Stripe makes the most sense.

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 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.

For an artisan seller who only sells locally, I’d pick Square Online first.

• Best overall: squareup.com — has a $0/month entry plan, supports free pickup and local delivery, and can handle delivery yourself or through a courier. Square Square
• Best alternative: ecwid.com — especially good if you want more flexible delivery zones. It supports pickup, local delivery by ZIP code or map area, delivery fees, and pickup/delivery time slots. Ecwid Help Center Ecwid Help Center
• Shopify is more powerful, but I'd consider it overkill for a small local-only artisan shop unless you expect to expand later. Shopify

My pick

Square Online if you want cheap + simple + local pickup/delivery.

If you tell me roughly how many products you sell and whether you already use Square for payments, I can tell you which plan/tool would be cheapest for your specific setup.

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.

For a photographer selling digital images, prints, and licensing, I’d prioritize platforms that handle:

• High-resolution digital delivery
• License/usage terms (commercial, editorial, personal)
• Watermarked previews
• Print fulfillment (optional)
• Low monthly cost and low/no sales commission
• A professional gallery experience

Here are the strongest affordable options:

Best overall for a photographer: Pixpa

pixpa.com

Best for: photographers who want a portfolio website + store in one place.

Pros

• Built specifically for photographers
• Sell prints and digital downloads from galleries
• Client proofing galleries
• Automated digital delivery
• Print lab integrations
• No commission on sales (payment processor fees still apply) Pixpa Pixpa

Cost

• Paid plans start relatively low (around the single-digit/month range when billed annually, depending on plan/promotions). Pixpa

Good fit if: you want your own branded photography website instead of sending customers to a marketplace.

Best free starting point: Pic-Time

pic-time.com

Best for: fine-art prints, portraits, weddings, client galleries.

Pros

• Permanent free plan available
• Print store included
• Automated print fulfillment through labs
• Beautiful galleries designed for photographers Pic-Time

Cons

• Free plans may include commissions on sales depending on how payments are handled. Pic-Time
• Licensing workflows are less robust than some photographer-focused platforms.

Good fit if: you want to test selling without paying monthly fees.

Best for serious licensing: PhotoDeck

photodeck.com

Best for: stock photography, commercial licensing, agencies, editorial work.

Pros

• Built around photographers selling images
• Supports digital downloads and licensing
• Pricing control
• Watermarking and image protection features
• Print sales options PhotoDeck

Cons

• More photography-business oriented than a simple storefront.

Good fit if: your main income goal is licensing images rather than just selling wall art.

Simplest marketplace option: Picfair

picfair.com

Best for: photographers who don’t want to manage ecommerce.

Pros

• Free signup
• Handles payments, prints, and licensing
• Built-in marketplace exposure
• Digital downloads and prints supported Picfair

Cons

• Less control over branding and customer relationships than your own website.

Good fit if: you want “upload photos → sell” with minimal setup.

Budget DIY option: WooCommerce + WordPress

woocommerce.com

Best for: photographers who already have a WordPress site.

Pros

• Very low software cost
• Full control over licensing products
• Many digital-download plugins
• No platform percentage cut

Cons

• More setup and maintenance
• You manage hosting, security, backups, delivery settings

My recommendation by business type

For most independent photographers starting out, I’d lean toward Pixpa if you want a professional storefront, or Pic-Time if you want to experiment with minimal upfront cost. If licensing is a major revenue stream (businesses buying usage rights), PhotoDeck is the more specialized choice. PhotoDeck Pixpa

A useful setup is often:

• Free/low-cost storefront → sell individual images and prints
• Separate licensing page → offer commercial/editorial rights with custom pricing
• Email list → avoid relying only on marketplace traffic

I can also compare these specifically for landscape/fine-art photography vs stock/licensing photography vs wedding/event photography if that’s your niche.

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 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.

If you're a solo developer selling downloadable software with perpetual licenses, paid upgrades, and versioned releases, I’d narrow it to Lemon Squeezy, Paddle, and Polar.

My pick: Lemon Squeezy

For your specific use case, Lemon Squeezy is probably the best balance of functionality and simplicity.

It natively supports:

• License-key generation per purchase
• Configurable activation limits
• License validation through an API
• License expiration tied to subscriptions, if you offer them
• Digital-file delivery
• Product/variant management
• Webhooks so your own backend can react to purchases, refunds, renewals, etc. Lemon Squeezy Docs Lemon Squeezy Docs
• Merchant-of-record handling, which is particularly attractive for a solo developer selling internationally.

docs.lemonsqueezy.com

The architecture I'd use is:

Customer
   │
   ▼
Lemon Squeezy checkout
   │
   ├── Payment
   ├── License key
   └── Download entitlement
          │
          ▼
     Your application
          │
          ├── Validate license
          ├── Check activation count
          └── Check update entitlement

For versioned software, however, I'd not make the ecommerce platform your entire update system.

I'd keep a small update service of your own:

Your Update Server
├── /latest
├── /v2.4.1
├── /v2.4.0
└── /v1.x

Your application sends something like:

{
  "license": "XXXX-XXXX-XXXX",
  "current_version": "2.3.0",
  "platform": "windows",
  "architecture": "x64"
}

Your server responds with:

{
  "latest_version": "2.4.1",
  "download_url": "...",
  "update_available": true
}

That gives you much more control over which customers are entitled to which versions.

How I'd rank the alternatives

Polar is worth serious consideration

Polar is particularly interesting if your customers are developers or you're selling developer tools. Its positioning is explicitly developer-focused, with license keys, digital products, APIs/webhooks, and GitHub-oriented functionality. Snagr BuildPilot

I'd choose Polar over Lemon Squeezy if API/developer experience and control are more important to you than platform maturity.

polar.sh

Paddle

Paddle is the one I'd consider if you're expecting to become a more substantial software business rather than staying a small indie operation. Paddle explicitly supports one-time software licenses and digital downloads and handles payment, tax, fraud, and compliance as merchant of record. Paddle Developer Docs

developer.paddle.com

I wouldn't choose Gumroad first

Gumroad actually has useful license-key functionality, including multi-seat licenses and API verification. Gumroad

But for a serious software product, I prefer the more software/developer-oriented platforms. Gumroad makes more sense if simplicity and an existing creator audience are important.

The bigger architectural question

If by "updates" you mean something like:

Customer buys Version 5, gets 12 months of updates, then can continue using 5.x forever but needs to renew to receive Version 6.

Then I'd separate commerce from licensing/update entitlement.

For example:

                    ┌──────────────────┐
                    │  Lemon Squeezy   │
                    │                  │
                    │ payment          │
                    │ customer         │
                    │ license          │
                    └────────┬─────────┘
                             │ webhook
                             ▼
                    ┌──────────────────┐
                    │ Your License API │
                    │                  │
                    │ customer         │
                    │ license          │
                    │ entitlement      │
                    │ activations      │
                    │ update_until     │
                    └────────┬─────────┘
                             │
              ┌──────────────┴──────────────┐
              ▼                             ▼
       License validation             Update API
              │                             │
              ▼                             ▼
        Your software              v5.2 / v5.3 / v6.0

That's substantially better than tying your application's behavior directly to downloadable files in the ecommerce system.

Bottom line: for a solo developer, I'd start with Lemon Squeezy + a tiny license/update API of your own. If you're building developer tooling and want a more developer-centric platform, Polar is probably the most interesting alternative. If you're aiming for a larger commercial software company, I'd investigate Paddle.

If you tell me (1) desktop/web/CLI software, (2) one-time license vs subscription, (3) whether updates are time-limited, and (4) approximate price, I can recommend the exact architecture—including how I'd structure licenses, activations, update entitlement, downloads, and webhooks.

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.

For a B2B wholesaler with customer-specific pricing, contract catalogs, account hierarchies, ERP integrations, and headless APIs, you’ll generally want an enterprise B2B commerce platform rather than a standard ecommerce store. The strongest options are: Shopify Atwix

My shortlist based on your description

If you are a true wholesaler/distributor (thousands of SKUs, negotiated pricing, dealer accounts, sales reps, purchase orders):

1. OroCommerce — probably the closest functional match for wholesale-first needs. ORO INC.
2. commercetools — best if your team wants a fully headless, API-driven architecture and has developers. Naturaily
3. Adobe Commerce — best if you need maximum customization and have implementation resources. Shopify
4. BigCommerce B2B Edition — best balance of SaaS simplicity and B2B capability. KIBO Commerce

Features I would verify during vendor evaluation

For a complex wholesaler, make sure the platform supports:

• Customer/account-specific price books
• Contract pricing and negotiated discounts
• Multiple catalogs by customer segment
• Tier pricing by quantity
• Quote → approval → order workflows
• Buyer roles and company hierarchies
• Net payment terms / purchase orders
• ERP sync (SAP, NetSuite, Dynamics, Infor, etc.)
• Real-time inventory and availability APIs
• Headless storefront APIs (GraphQL/REST)
• Punchout procurement integrations (OCI/cXML)
• Multi-brand or multi-region catalogs

A key question is where your pricing logic currently lives: ERP, CRM, a pricing engine, or spreadsheets. That often determines whether you want a commerce platform with strong native pricing (Oro/Adobe/SAP) or an API-first platform where pricing stays in your own services (commercetools). ORO INC. Naturaily

If you share your ERP (NetSuite/SAP/Dynamics/etc.), SKU count, number of customer accounts, and whether you need a custom frontend, I can narrow this to 2–3 realistic choices.

For a subscription box business, I’d narrow the field to Medusa, Shopify, commercetools, and BigCommerce, but my default recommendation would be Medusa + Stripe Billing if you have a development team and want the subscription experience to be deeply customizable.

The key distinction is that “supports subscriptions via API” can mean either native recurring-subscription commerce or simply an API that you can integrate with a subscription billing provider.

My shortlist

1. Medusa — my pick for a custom subscription-box business

medusajs.com is particularly interesting because it's built to be customized rather than forcing your subscription model into a predefined SaaS workflow.

Its current documentation explicitly shows how to build subscription purchases, including:

• subscription intervals
• automatic renewals
• expiration
• customer cancellation
• subscription/customer API endpoints
• recurring payment capture
• linking subscriptions to orders/products

Medusa itself says subscriptions aren't a native core feature—you implement them through its customization framework or use Stripe subscriptions—but it provides the API routes, workflows, modules and payment infrastructure needed to do it. Medusa Docs Medusa Docs

That's actually a feature rather than a bug for a subscription box company if your business logic is unusual.

For example, you could model:

Customer
   ↓
Subscription
   ├── Plan
   │    ├── Monthly
   │    ├── 3-month prepaid
   │    └── Annual
   │
   ├── Box configuration
   │    ├── Size
   │    ├── Preferences
   │    └── Add-ons
   │
   ├── Billing schedule
   ├── Next shipment
   └── Orders

Then expose exactly the API your frontend/mobile app needs.

Medusa's Store API is REST-based and designed specifically to power custom storefronts and commerce applications. Medusa Docs

I'd choose this if: your subscription is core to the business and you expect things like skips, swaps, add-ons, prepaid plans, customized boxes, pauses, different fulfillment schedules, etc.

2. Shopify — best if you want less engineering

shopify.com is probably the safer choice if your priority is getting the business running rather than owning the commerce infrastructure.

You can build a completely custom frontend while keeping Shopify for products, customers, orders, payments and operational tooling.

The big advantage for subscription boxes is the ecosystem: you can use established subscription infrastructure rather than implementing renewal logic yourself.

I'd choose Shopify if:

• you want to launch quickly
• you don't have a large engineering team
• subscription behavior is relatively conventional
• you want lots of integrations
• your operations team wants a mature admin experience

The downside is that you're working within Shopify's architecture and subscription ecosystem rather than designing the entire subscription domain yourself.

3. commercetools — if you're already an enterprise

commercetools.com is the option I'd investigate for a large subscription-box operation with multiple markets, currencies, brands, channels, fulfillment systems, etc.

It's extremely API/composable-oriented, but it's also considerably more infrastructure and architecture than most subscription-box businesses need.

One important clarification: commercetools' API documentation uses the word “Subscriptions” for its event/notification mechanism. Those are notifications sent to message queues—they aren't customer recurring subscriptions. commercetools Docs

So you'd still need to architect the actual recurring billing/subscription domain.

4. Saleor — compelling if you're engineering-heavy

saleor.io is another strong headless option. It's GraphQL-first and has a very expressive API/webhook architecture. Saleor Commerce

But like Medusa, recurring subscriptions aren't really a turnkey core commerce feature. You'd be building more of that layer yourself.

I'd favor Saleor over Medusa if your team strongly prefers Python/GraphQL and you need sophisticated multi-channel/multi-warehouse commerce.

What I'd actually build

For a new subscription-box company, my architecture would probably be:

Next.js / custom frontend
↓
Medusa — products, carts, customers, orders, inventory
↓
Stripe Billing — recurring payment/subscription lifecycle
↓
Your subscription service/module — box schedule, skips, swaps, preferences, renewal logic
↓
3PL / fulfillment system

That gives you a clean separation:

• Medusa: commerce
• Stripe: money
• Your application: subscription-box business rules
• 3PL: physical fulfillment

Medusa's own subscription recipe demonstrates both a custom subscription approach and a Stripe-based approach, including storing payment information so future renewals can capture payment. Medusa Docs

One important question

Before I would choose the platform, I'd want to know how sophisticated your subscription model is.

If you tell me:

1. Monthly/quarterly/etc.
2. Whether customers can skip/pause
3. Whether they can swap items
4. Whether boxes are curated or customer-selected
5. Whether you need prepaid 3/6/12-month plans
6. Approximate number of subscribers
7. Whether you already use Stripe/Shopify/etc.
8. Whether you have an engineering team

…I can give you a much more concrete Medusa vs Shopify vs commercetools recommendation, including the API/subscription architecture I'd use for your business.

So you'd still need to architect the actual recurring billing/subscription domain.

4. Saleor — compelling if you're engineering-heavy

saleor.io is another strong headless option. It's GraphQL-first and has a very expressive API/webhook architecture. saleor.io

But like Medusa, recurring subscriptions aren't really a turnkey core commerce feature. You'd be building more of that layer yourself.

I'd favor Saleor over Medusa if your team strongly prefers Python/GraphQL and you need sophisticated multi-channel/multi-warehouse commerce.

What I'd actually build

For a new subscription-box company, my architecture would probably be:

Next.js / custom frontend
↓
Medusa — products, carts, customers, orders, inventory
↓
Stripe Billing — recurring payment/subscription lifecycle
↓
Your subscription service/module — box schedule, skips, swaps, preferences, renewal logic
↓
3PL / fulfillment system

That gives you a clean separation:

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.

If by “supplier marketplaces” you mean platforms where you source products from third-party suppliers/wholesalers/dropshippers and need automated catalog, inventory, pricing, orders, and fulfillment syncing, I’d put Shopify at the top for breadth and ease of integration.

My shortlist

Why Shopify: its app ecosystem is enormous, and its sourcing/dropshipping category alone currently lists roughly 590 apps in the U.S. Shopify App Store Shopify App Store Shopify also has marketplace connectors for Amazon, eBay, Walmart, Target Plus and others, while third-party apps extend this substantially. Shopify

Why BigCommerce may actually be better for your use case: its architecture is explicitly designed around external channels. Its Channels Toolkit lets third parties build integrations to virtually any external sales channel, including marketplaces, and BigCommerce exposes APIs/webhooks for custom integrations. BigCommerce BigCommerce It also has direct integrations with Amazon, Walmart, eBay, Target+, Mercado Libre, etc. BigCommerce

Adobe Commerce is particularly strong if you're talking about lots of unusual suppliers and custom enterprise systems. Adobe says its ecosystem has thousands of extensions, and its marketplace includes connectors such as ChannelEngine, which itself connects an Adobe Commerce store to hundreds of marketplaces/channels. Adobe for Business Adobe Commerce Marketplace

My recommendation

If I were selecting the platform specifically around “we don't know which supplier marketplaces we'll need to connect to in the future”, I'd choose:

1. Shopify — easiest path to the widest ecosystem
2. BigCommerce — strongest alternative if integrations/API flexibility are central
3. Adobe Commerce — best if you're enterprise-scale and have developers/integration resources
4. WooCommerce — extremely flexible, but more dependent on assembling and maintaining plugins

The important distinction is that the ecommerce platform itself isn't necessarily what gives you the supplier integrations. Often you'll use an integration layer such as a marketplace connector/aggregator, which can connect dozens or hundreds of suppliers to your commerce platform.

If you tell me which supplier marketplaces you need to connect (e.g. Faire, Alibaba, Spocket, Syncee, DSers, Wholesale2B, Mirakl marketplaces, etc.), I can make a platform-by-platform matrix showing exactly which ones connect natively, through apps, through middleware, or require custom API work.

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

For a solo founder selling low-margin dropship products, the answer is usually not Shopify unless the convenience saves you enough time to justify the extra cost. Your priority should be minimizing:

1. monthly platform fees
2. payment processing fees
3. app/plugin costs
4. marketplace commissions
5. operational overhead (your time has a cost)

Here’s the practical ranking:

Shopify WooCommerce## My recommendation for your situation

1. Cheapest: WooCommerce + low-cost hosting

If your margins are thin (say 10–25%), this is usually the winner.

Pros:

• No monthly ecommerce platform fee
• No revenue share
• Full control
• Many dropshipping integrations exist
• You can optimize costs as you grow

Cons:

• More setup
• You manage hosting, updates, security, plugins

WooCommerce itself is free and does not charge a platform revenue share; your main costs are hosting, extensions, and payment processing. WooCommerce

A lean setup might look like:

• Hosting: ~$5–20/month
• WooCommerce: $0
• Payment processing: typically around standard card rates (varies by provider)
• Essential plugins only

2. Best "time vs money" choice: Shopify

If you're spending more time fixing tech than finding products and ads, Shopify can make sense.

Pros:

• Fastest launch
• Great dropshipping ecosystem
• Less maintenance
• Reliable checkout

Cons:

• Monthly subscription
• Apps can quietly add $50–200+/month
• Third-party payment gateways may add extra fees depending on plan/payment setup

Shopify Stack Compare### 3. Avoid marketplaces for generic dropship products

Platforms like Etsy can look cheap because there is no monthly subscription, but marketplace fees can consume a large percentage of low-margin products. They work better when you have unique products, personalization, or organic marketplace demand. Memvers

Simple decision rule

• Making < $5k/month revenue: WooCommerce if you are comfortable with tech; Shopify if you value speed.
• $5k–50k/month: Shopify often wins because your time becomes more valuable.
• Very low margins (<20%): Avoid paying for lots of apps; WooCommerce usually has the edge.
• Testing many products quickly: Shopify is often easier because dropshipping tools are more mature.

For a solo founder with commodity dropship products and thin margins, I would start with WooCommerce + minimal plugins, then move to Shopify only when operational complexity—not cost—is the bottleneck.

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:

For monthly physical subscription boxes, I’d choose Shopify unless you have a strong reason to use WordPress.

My recommendation: Shopify

Shopify is probably the best fit because it can give you the whole stack in one place:

• Recurring monthly billing: Shopify Subscriptions supports automatic weekly, monthly, or yearly renewals. Shopify Help Center
• Customer portal: Customers can log in and manage payment methods, shipping address, skip orders, pause/resume, and cancel subscriptions themselves. Shopify Help Center
• Normal ecommerce: Your subscription boxes can coexist with one-time purchases.
• Low technical overhead: You don't need to build the billing or account-management system yourself.
• Room to grow: Shopify's customer accounts can support subscriptions, order tracking, returns, loyalty, upsells, etc. Shopify
• More advanced subscription apps: If you eventually need things like build-a-box, sophisticated churn prevention, dunning/retry logic, or more complex subscription rules, Shopify has a large subscription-app ecosystem. Shopify App Store

How I'd rank the options

WooCommerce is the strongest alternative. WooCommerce Subscriptions supports monthly recurring payments, automatic rebilling after failed payments, and lets customers upgrade, downgrade, suspend, cancel, and update payment/shipping information. WooCommerce WooCommerce The downside is that you're assembling and maintaining more of the stack yourself.

For BigCommerce, subscription functionality is generally handled through an app such as SubscriptionFlow, which provides automated recurring billing and a self-service portal. BigCommerce

One important caveat

If your "subscription box" means customers choose several products every month—e.g. "pick any 5 snacks each month"—I'd lean toward Shopify + a specialized subscription app rather than Shopify's basic subscription functionality. Shopify's native system is excellent for straightforward "this box ships every month," but configurable/build-a-box subscriptions can benefit from specialized tooling.

If you tell me (1) what you're selling, (2) expected subscribers, and (3) whether customers choose the contents of each box, I can narrow this down to the best 2–3 platforms/apps and their approximate monthly cost.

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.

For a small manufacturer selling wholesale to retailers, I’d start with BigCommerce B2B.

My recommendation: BigCommerce B2B

bigcommerce.com is unusually well matched to your requirements because its B2B functionality includes:

• Quote requests / quoting — buyers can request quotes, and your sales team can manage quotes without building a separate system. BigCommerce BigCommerce
• Net terms — you can offer Net 30/60-style payment terms on a per-account basis, alongside credit cards and POs. BigCommerce
• Retailer-specific pricing — customer groups and SKU-level price lists let you give different retailers different wholesale prices. BigCommerce
• Buyer accounts — retailers can log in, reorder, manage purchasing, and have permissions/approval workflows.
• Manufacturer-friendly catalog management — particularly useful if you have lots of SKUs, case packs, minimum quantities, or different pricing tiers.
• One storefront can support both wholesale and retail if you eventually want DTC sales too. BigCommerce

The other big advantage for a small manufacturer is that it's SaaS rather than a platform you'll need to maintain yourself.

How I'd rank your options

OroCommerce is particularly strong if negotiated quoting is the heart of your business—RFQ and CPQ are native—but its implementation and technical requirements make it harder to justify for a small manufacturer. ORO INC. G2

BigCommerce's current public plans start at $39/month, though the more sophisticated B2B functionality and pricing depend on the plan/edition and your requirements. BigCommerce

Bottom line: If your workflow is something like retailer creates account → sees their wholesale catalog/prices → requests a quote or places an order → chooses Net 30 → you approve/fulfill, I'd shortlist BigCommerce first.

If you tell me roughly (1) number of SKUs, (2) number of retail customers, (3) whether you already use QuickBooks/NetSuite/etc., and (4) whether you also sell DTC, I can narrow it down to the best 2–3 setups and estimate the likely monthly cost.

For an agency building multiple wholesale stores for different clients, I’d make bigcommerce.com + B2B Edition the default platform I evaluate first.

Why BigCommerce fits an agency model

The important distinction is that you want multi-storefront + B2B, not merely a platform that has wholesale pricing.

BigCommerce gives you:

• Multi-Storefront: multiple brands, regions, or storefronts managed from one backend. Each storefront can have its own branding, domain, settings, and experience. BigCommerce BigCommerce
• B2B Edition: company accounts, buyer roles, quotes, invoices, payment terms, shopping lists, and a buyer portal. BigCommerce
• Company hierarchies: parent companies, subsidiaries, departments, etc., with role-based permissions. This is particularly useful for sophisticated wholesale customers. BigCommerce
• Per-storefront B2B configuration: B2B can be enabled and configured separately for individual storefronts, including buyer portal, login, quotes, shopping lists, and translations. BigCommerce
• Headless/API support: useful if your agency builds custom React/Next.js storefronts or reusable frontend components. BigCommerce BigCommerce

That combination makes it a good fit for building a repeatable agency architecture rather than reinventing the commerce backend for every client.

How I'd rank the main options

BigCommerce vs. Shopify Plus

This is probably the decision you'll encounter most often.

Shopify Plus has become substantially more compelling for B2B. Shopify now provides native companies, company locations, catalogs, quantity rules, payment terms, and other B2B functionality, while Plus adds unlimited B2B catalogs and direct catalog assignment to individual companies/company locations. Shopify Help Center Shopify Help Center

So I'd choose Shopify Plus when:

• The client already uses Shopify.
• They have a strong DTC component alongside wholesale.
• They want the Shopify app ecosystem.
• Your agency wants to maximize developer availability and ease of implementation.
• Their B2B requirements aren't unusually complex.

I'd lean BigCommerce when:

• Wholesale/B2B is the primary business model.
• You need lots of storefronts/channels.
• Customers have complicated organizational structures.
• You expect custom integrations and headless builds.
• You want B2B functionality to be a first-class part of the architecture.

BigCommerce explicitly supports companies operating across multiple storefront channels, including assigning users to particular channels. BigCommerce

The architecture I'd use as an agency

I wouldn't create a totally independent technical stack for every client.

I'd build a repeatable commerce accelerator:

                    Agency
                       │
          ┌────────────┴────────────┐
          │                         │
   Shared frontend              Shared services
   components / design          ERP / CRM / PIM
          │                         │
    ┌─────┼─────┐             ┌─────┼─────┐
    │     │     │             │     │     │
 Client A B     C             ERP   CRM   PIM
 Store   Store Store
    │     │     │
    └─────┴─────┘
          │
   BigCommerce B2B
          │
  Companies / Users
  Catalogs / Pricing
  Quotes / Orders
  Payment Terms
  Permissions

The client is the tenant at the commerce level, while you maintain a reusable application/integration layer.

For example, your agency could have standardized modules for:

• Customer/company onboarding
• Customer-specific pricing
• Contract catalogs
• Minimum order quantities
• Tiered pricing
• Sales-rep workflows
• Quote requests
• PO/net terms
• Approval workflows
• ERP synchronization
• Product/PIM synchronization
• Reordering
• Account dashboards
• Custom checkout
• Analytics

Then each client gets configuration and extensions rather than an entirely new implementation.

One important caveat

If by multi-tenant you literally mean one application/database where dozens or hundreds of unrelated merchants are tenants, that's different from BigCommerce's multi-storefront model.

If you're building a SaaS platform for wholesalers, I'd consider a composable architecture such as commercetools or potentially a custom commerce service. If you're an agency deploying separate stores for separate clients, BigCommerce is much more attractive because you don't need to build and operate the commerce infrastructure yourself.

My recommendation: standardize your agency around BigCommerce B2B Edition for B2B-first clients, while keeping Shopify Plus as your second approved stack for clients where Shopify's ecosystem/DTC strengths are more valuable. This gives you a scalable two-platform strategy without forcing every client into the same technology. BigCommerce BigCommerce

For a wholesaler that needs customizable quote → approval → order workflows, I’d shortlist these:

My pick: BigCommerce B2B Edition

For a typical wholesaler, BigCommerce B2B Edition is probably the best starting point. It has first-class quote objects rather than forcing you to model quotes as orders. Buyers can request quotes, sales reps can customize line pricing, products, shipping and expiration dates, and an approved quote can be taken directly through checkout. BigCommerce BigCommerce BigCommerce

It also supports company accounts and buyer permissions, which is useful when, for example:

Junior buyer → requests quote → sales rep adjusts pricing → manager approves → senior buyer converts quote → PO/order is created.

BigCommerce's current B2B positioning specifically targets wholesalers, manufacturers and distributors with account pricing, buyer portals, quote workflows and approval controls. BigCommerce

When I'd choose OroCommerce instead

If workflow customization is the primary requirement, I'd look very seriously at oroinc.com.

Oro has explicit quote workflows with approval states and transitions. Its documentation even distinguishes a simple quote process from a "Quote Management with Approvals" flow where a salesperson needs authorization before sending a quote with changed pricing. Oro Documentation Oro Documentation

That makes Oro particularly attractive if you have rules such as:

• Discount >10% requires sales-manager approval
• Margin below a threshold requires finance approval
• Certain customers require two-person approval
• Quotes over $50K follow a different workflow
• Different product categories have different approval chains

When Pepperi wins

pepperi.com is especially compelling if your wholesale business has field sales reps taking orders, rather than being primarily an ecommerce storefront. It combines B2B ecommerce, mobile order taking and sales-force workflows. B2B Commerce Platform | Pepperi B2B Commerce Platform | Pepperi

It also explicitly supports configurable approval workflows and multiple catalogs, price lists, buyer types and storefronts. B2B Commerce Platform | Pepperi

Bottom line:

• BigCommerce → best default for a modern wholesale ecommerce portal with quote-to-order.
• OroCommerce → best if complicated approval/workflow logic is the differentiator.
• Pepperi → best if sales reps + distributor ordering are central.
• Shopware → worth considering when you want a highly customizable commerce stack.

If you tell me how your quote/approval process works today (e.g. customer requests quote → rep edits → manager approval → customer accepts → PO), I can map it against these platforms and tell you which one requires the least customization.

BigCommerce's current B2B positioning specifically targets wholesalers, manufacturers and distributors with account pricing, buyer portals, quote workflows and approval controls. bigcommerce.com

When I'd choose OroCommerce instead

Yes. If your requirements are (1) migrate an existing wholesale catalog, (2) give each customer/account its own pricing, and (3) preserve/manage open quotes, there are several good options—but they differ quite a bit in how much is native vs. bolted on.

My shortlist

1. BigCommerce B2B Edition — probably the first one I'd investigate

BigCommerce is unusually well suited to what you're describing.

Its B2B functionality includes company/account-specific pricing, customer groups, buyer permissions, catalogs, and a native quoting engine. Its price lists can customize pricing down to the individual SKU and can be assigned to specific wholesale accounts or customer groups. BigCommerce BigCommerce

Its quote system is particularly relevant: quotes can contain custom line-item prices, discounts, custom products, special shipping methods, and expiration dates, and buyers can take accepted quotes through checkout. BigCommerce

That's a much cleaner fit if you currently have something like:

Customer A → 1,200 products → their own price on each SKU → several quotes currently outstanding

rather than trying to recreate that structure with a collection of Shopify apps.

bigcommerce.com

2. Shopify B2B — easiest if you want a relatively painless migration

Shopify has gotten substantially better for wholesale.

Its B2B catalogs let you control which products a customer can see and what price they pay, with catalogs assignable to specific company locations. Shopify Help Center

Shopify also treats B2B quotes as draft orders, so sales reps can create a quote using the customer's specific pricing/payment terms and send the customer a checkout link. Shopify

The catch is open/customer-initiated quote management. If you need a sophisticated RFQ workflow—multiple revisions, negotiation, quote status, expiration, etc.—you'll likely add an app. There are now several options that integrate quotes with Shopify Draft Orders. Shopify App Store Shopify App Store

So I'd characterize Shopify as:

Best if catalog migration and ease of administration are more important than having deeply native B2B quoting.

shopify.com

3. Adobe Commerce — powerful, but probably more platform than you need

Adobe Commerce has native Shared Catalogs for company-specific pricing and native B2B Quotes for negotiated pricing. Experience League

It's a strong choice if your pricing model is extremely complicated—for example:

• thousands of customer-specific price lists
• different catalogs by customer/company
• quantity breaks
• account hierarchies
• sophisticated purchasing permissions
• ERP integration
• sales-rep-assisted quoting

But if the goal is "move our existing wholesale business online without turning this into a major IT project," I'd look at BigCommerce and Shopify first.

The important question: what does "open quotes" mean in your business?

This actually changes my recommendation quite a bit.

If you mean:

A. "Our salespeople create quotes for customers and sometimes the customer comes back months later and orders from that quote."

→ BigCommerce B2B is very compelling.

B. "Customers log in, build a large basket, request a quote, negotiate it with us, and eventually convert it to an order."

→ BigCommerce B2B or Shopify + a strong quote app.

C. "We have hundreds/thousands of existing quotes in our current system that need to be migrated and remain open."

→ This is a different problem. I'd pay much more attention to the migration/API capabilities and quote data model than the storefront features.

D. "Every customer has a negotiated price for individual SKUs, and we need to import those prices from our existing system."

→ BigCommerce becomes particularly interesting because of its native price-list structure. BigCommerce

If I were evaluating this for your situation

I'd probably do a proof-of-concept with BigCommerce B2B vs. Shopify B2B.

Give both vendors the same sample export:

• 500–2,000 products
• 10–20 customers
• customer-specific SKU pricing
• inventory quantities
• product images
• 5–10 open quotes
• quote line-item prices
• customer payment terms
• customer shipping addresses

Then ask them to demonstrate importing that data and having an existing customer log in and see exactly the catalog/prices they should see.

That's much more revealing than a generic platform demo.

If you tell me what your current wholesale platform/software is (even just the name) and roughly how many SKUs, customers, and open quotes you have, I can narrow this down to 2–3 platforms and specifically assess how hard the migration would be and whether the existing quotes can actually be carried over.

B. "Customers log in, build a large basket, request a quote, negotiate it with us, and eventually convert it to an order."

→ BigCommerce B2B or Shopify + a strong quote app.

C. "We have hundreds/thousands of existing quotes in our current system that need to be migrated and remain open."

→ This is a different problem. I'd pay much more attention to the migration/API capabilities and quote data model than the storefront features.

D. "Every customer has a negotiated price for individual SKUs, and we need to import those prices from our existing system."

→ BigCommerce becomes particularly interesting because of its native price-list structure.

If I were evaluating this for your situation

I'd probably do a proof-of-concept with BigCommerce B2B vs. Shopify B2B.

Give both vendors the same sample export:

Best if catalog migration and ease of administration are more important than having deeply native B2B quoting.

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:

Recommendation: Adobe Commerce

For multi-country B2B sales with complex catalogs, currencies, and tax rules, I’d shortlist Adobe Commerce first.

It fits particularly well if you need:

• Localized catalogs: separate websites/stores/store views can have different products, categories, languages, domains, and content. Experience League Experience League
• Multi-currency: currencies can be configured by store view, with base currency scoped at the website level—useful when different countries need different commercial pricing. Experience League Experience League
• B2B-specific catalogs and pricing: Adobe Commerce B2B supports company-specific shared catalogs and custom pricing, plus quotes, quick ordering, and requisition lists. Experience League
• Tax flexibility: tax rules can combine product class, customer class, tax rate, and geographic region; Adobe also supports country-specific tax configurations and cross-border pricing scenarios. Experience League Experience League
• Different prices by country: catalog pricing can be scoped at the website level, allowing the same SKU to have different prices across regional sites. Experience League

experienceleague.adobe.com

How I'd compare the shortlist

Shopify Plus is the strongest alternative if you prioritize operational simplicity. Its Markets functionality can combine B2B customers with market-specific currencies, taxes/duties, discounts, pricing, product availability, and catalogs. help.shopify.com shopify.com

My rule of thumb: Adobe Commerce if country-specific B2B pricing/catalog logic is core to the business; Shopify Plus if speed and lower operational complexity matter more. If you tell me your approximate number of countries, SKUs, ERP (SAP/NetSuite/Dynamics/etc.), and whether pricing is customer-specific, I can narrow this to a specific platform/architecture.

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

If analytics + conversion optimization inside the ecommerce experience are priorities, I’d pick shopify.com.

My shortlist

*Usually depends more heavily on plugins/integrations.

Why Shopify: it combines detailed store analytics with conversion-oriented features such as abandoned-cart recovery, Shop Pay checkout, integrated payments, marketing tools, multichannel selling, and a huge app ecosystem. Current comparisons consistently put it among the strongest options for dedicated ecommerce. Shopify TechnologyAdvice

Pick BigCommerce instead if you're expecting a large catalog, B2B, multiple storefronts, or high transaction volume. It has particularly strong native commerce functionality and doesn't charge platform transaction fees when using its embedded payment providers. BigCommerce

Pick Wix instead if the website itself is equally important as the store—e.g. you're a brand/content business with a relatively modest catalog. Its visual builder is more flexible, but Shopify is the stronger choice once ecommerce optimization becomes the core job. Tech.co TechSifted

The key distinction

If by "conversion features" you mean A/B testing, funnels, behavioral analytics, personalization, heatmaps, etc., I'd actually narrow the decision differently. Shopify gives you the strongest ecommerce foundation, but some advanced CRO capabilities may still come through apps/integrations rather than being completely native.

If you tell me what you're selling, roughly how much traffic/revenue you expect, and whether you need B2B or subscriptions, I can give you a much more definitive Shopify vs. BigCommerce vs. Wix recommendation.

For a boutique selling made-to-order products with long production times, I’d lean toward Shopify—especially if you want a polished storefront without building a lot of custom ecommerce infrastructure.

My ranking

1. Shopify — best overall

• Excellent ecosystem for pre-orders, backorders, deposits, waitlists, and made-to-order products.
• Shopify’s App Store currently has 100+ pre-order apps specifically tagged for made-to-order, including options for backorders, partial payments, and restock notifications. Shopify App Store Shopify App Store
• Apps such as Dibs support deposits/partial payments, while others handle pre-orders + backorders + customer notifications. Shopify App Store
• Best if your production time varies and you want to communicate things like “Ships in 6–8 weeks” while still taking the order.
• WooCommerce — best for maximum control

• Very capable if you're already comfortable with WordPress.
• The official WooCommerce Pre-Orders extension can charge customers upfront or when the item becomes available, set/change availability dates, email pre-order customers, and manage pre-orders separately. WooCommerce WooCommerce
• I'd choose this over Shopify if you need unusual production workflows or extensive customization.
• BigCommerce — worth considering for a larger operation

• Strong general ecommerce platform, but I'd put it behind Shopify for a small boutique whose core requirement is sophisticated made-to-order/pre-order selling.
• Shopify has a much more obvious ecosystem around this particular use case.

For your particular business

I'd structure the store around pre-orders rather than conventional backorders.

For example:

Made to Order — Ships in 6–8 weeks
Each piece is handcrafted after your order is placed. Production begins immediately, and your order will ship within approximately 6–8 weeks.

Then have the checkout/order system handle:

Order → payment/deposit → production queue → production complete → fulfillment → shipping notification

That's much cleaner for a boutique than pretending the item is simply "out of stock."

My pick: Shopify + a good pre-order/made-to-order app. Shopify's current app marketplace has particularly strong coverage for exactly this scenario. Shopify App Store

If you tell me (1) average production time, (2) whether you want full payment or deposits, (3) whether customers can customize each item, and (4) roughly how many orders/month, I can narrow it down to the best platform + app combination.

For your situation, I’d start with Fourthwall.

Why it fits a small creator on a tight budget:

• $0/month and $0 upfront — there’s no subscription or inventory investment. Fourthwall Fourthwall
• Built-in storefront — you don't need to pay separately for Shopify just to have a shop.
• Print-on-demand — they make and ship the shirt/sticker only after someone buys it, so you don't have to buy boxes of inventory. Fourthwall
• Stickers and shirts are both supported — their current catalog lists stickers from about $2.29 and shirts from about $9.50, with no minimums. Fourthwall
• You set the retail price and keep the markup after the product cost; US credit-card payments have a 2.9% + $0.30 processing fee. Fourthwall

fourthwall.com

What I'd do in your shoes

Start with Fourthwall → launch 3–5 designs → offer 1–2 shirt styles + stickers → promote the store through your existing social accounts.

I wouldn't start with Shopify + Printify if money is really tight. Printify itself has a free plan, but you'll generally be piecing it together with a separate storefront/e-commerce platform. printify.com help.printify.com

If you tell me roughly how many followers you have and whether most of your audience is on TikTok, Instagram, YouTube, etc., I can recommend the cheapest setup and pricing strategy for your specific situation.

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.

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 creator selling worldwide, the easiest route is usually a Merchant of Record (MoR) platform: the software becomes the legal seller for each transaction and handles VAT/sales tax collection, invoices, compliance, and often currency conversion. This avoids you registering for VAT in many countries and manually filing taxes. Remotify Transact Bridge

Here are the main options depending on what you sell:

For physical products with international shipping, look for platforms that calculate landed cost (product + shipping + VAT + duties before checkout). Some cross-border platforms focus specifically on customs documentation, duties, and multi-country selling. Reveni OpenBorder

My short recommendations:

• Courses, templates, ebooks, digital art, software: use Paddle, Lemon Squeezy, Gumroad, or another MoR. Lowest admin burden.
• Merch/physical goods: use Shopify + a fulfillment/cross-border partner if you want your own brand store.
• Memberships/subscriptions: prioritize a MoR because recurring global tax compliance gets complicated quickly.
• Selling both digital + physical: Shopify is usually the flexible center, but expect a few integrations.

The key feature to search for is “Merchant of Record”, not just “VAT calculator.” A VAT calculator tells you what tax is due; an MoR can take responsibility for collecting/remitting it. Remotify Transact Bridge

If you tell me whether you sell digital products, courses, subscriptions, or physical goods, and roughly where you’re based (EU/US/other), I can narrow this to the best 2–3 choices.

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.

For a fast-growing global retail brand with very high traffic + multiple country storefronts, you generally want an enterprise commerce platform, not a basic store builder. The right choice depends on how much customization and operational complexity you have. CIOPages

My shortlist:

My recommendation by scenario

• You are a fast-growing consumer brand (fashion, beauty, lifestyle, DTC):

Start with Shopify Plus. It is usually the best balance of uptime, global expansion, speed, and operational simplicity. Shopify ecommerceguide

• You operate dozens of countries, multiple brands, complex promotions, or heavy CRM/personalization:

Evaluate Salesforce Commerce Cloud or Adobe Commerce. eDesk The Retail Exec

• You have a large engineering team and want a custom global commerce engine:

Consider commercetools or another composable stack. CIOPages

For your situation, I would also make sure the platform supports:

• Global CDN and automatic scaling for campaign spikes
• Multi-currency, local taxes, duties, and payments
• Multiple storefronts/domains from one operational backend
• Inventory and order management integrations
• API-first integrations with ERP, CRM, PIM, and fulfillment systems
• Strong observability (monitoring, logs, performance alerts)

If you share your approximate annual online revenue, number of countries, SKU count, and whether you need B2B/wholesale, I can narrow this to a top 1–2 choices.

For a B2B division with custom pricing, POS requirements, and large order volumes, I would focus less on “ecommerce platforms” and more on enterprise commerce platforms that can unify pricing, inventory, customer accounts, and order workflows. The best fit depends heavily on whether you are a distributor, manufacturer, retailer, or a B2B arm of an existing brand. Shopify KIBO Commerce

A shortlist I would evaluate:

Shopify Alkali## My likely recommendation by scenario

If you are a distributor/manufacturer

I would start with:

1. Adobe Commerce — if you have complex pricing, thousands of SKUs, multiple customer tiers, negotiated contracts, or ERP-driven pricing.
2. OroCommerce — if B2B workflows are the heart of the business.
3. BigCommerce Enterprise — if you want SaaS simplicity but still need serious B2B capability.

If you have retail stores + wholesale/B2B

I would look at:

1. Shopify Plus — especially if POS is a major requirement and you want one ecosystem for stores, online, and B2B.
2. BigCommerce — if the B2B side is more complex than the retail side.

If order volume is very large

Prioritize:

• ERP integration (SAP, Oracle, NetSuite, Dynamics, etc.)
• real-time inventory availability
• customer-specific price engines
• bulk ordering/reorder tools
• approval workflows
• EDI/punchout procurement support
• API scalability

A common mistake is choosing a platform that can “take orders” but cannot reliably handle contract pricing + customer entitlements + inventory + sales workflows at scale. Capterra

A few questions would narrow this down significantly:

1. What ERP are you running (SAP, NetSuite, Dynamics, custom, none)?
2. Is POS already in place, and which system?
3. Approximate scale: annual B2B revenue, number of customers, SKUs, and monthly orders?
4. Do customers have negotiated pricing/contracts, or mostly tiered volume pricing?
5. Are you selling direct to consumers too, or only B2B?

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.

If heavy API usage + strong developer tooling are the priorities, I’d shortlist Shopify Plus and BigCommerce Enterprise, with Adobe Commerce if you need deep control over the commerce stack.

My recommendation: Shopify Plus

For most enterprise engineering teams, I’d choose Shopify Plus.

• Excellent API-first tooling: Shopify’s current Admin API is GraphQL, with official client libraries and strong schema/documentation tooling. Shopify Shopify
• High API throughput at enterprise tiers: Shopify Plus gets a 1,000-point/second GraphQL Admin API rate limit, versus 100 points/sec on standard Shopify. Commerce Components goes to 2,000 points/sec. Shopify
• Good fit for distributed engineering teams: versioned APIs, GraphQL, webhooks, app extensions, and a mature ecosystem reduce the amount of commerce infrastructure your team has to own.
• Headless-friendly: particularly attractive if your frontend, mobile apps, ERP integrations, or other services are heavily API-driven.

One important caveat: don't evaluate Shopify based on its old REST API. Shopify considers REST Admin API legacy and directs new integrations toward GraphQL. Shopify Shopify

When I'd pick BigCommerce instead

BigCommerce Enterprise is arguably the more interesting alternative if your developers want a more open/composable commerce platform.

BigCommerce provides REST and GraphQL APIs, generated OpenAPI specifications, API request tooling, headless support, and developer-oriented documentation. BigCommerce BigCommerce

I'd lean BigCommerce if your team values API openness and customization over Shopify's ecosystem and overall platform maturity.

When Adobe Commerce wins

Adobe Commerce makes more sense when you have a sophisticated engineering organization that wants maximum control over the underlying commerce system.

It has extensive REST and GraphQL APIs, headless capabilities, and both PaaS and SaaS deployment models. Adobe Developer Adobe Developer The tradeoff is that your team takes on considerably more architectural and operational complexity.

Bottom line: if your company is doing very high API volume and you want engineers to spend their time building product rather than maintaining commerce infrastructure, I'd start with Shopify Plus. If API openness and architectural control are more important than minimizing platform ownership, I'd seriously consider BigCommerce Enterprise.

If you tell me roughly API calls/day, number of SKUs, number of stores/regions, and whether you're headless, I can give you a much more definitive Shopify vs. BigCommerce vs. Adobe recommendation.

For a digital-first enterprise looking to decouple frontend and backend, the “best” headless commerce solution depends less on storefront technology and more on your scale, operating model, integration complexity, and appetite for composability. For large-scale deployments, the shortlist usually narrows to a few enterprise-grade options. Guideflow Vendure

Enterprise shortlist

CIOPages Elogic Commerce## My recommendation for a digital-first enterprise

Choose commercetools if:

• You have a dedicated platform engineering team.
• You operate multiple brands, regions, currencies, or channels.
• You want frontend freedom plus the ability to replace other services over time (search, CMS, OMS, promotions, etc.).
• You are comfortable owning architecture decisions.

It is probably the strongest fit for a large-scale, API-first enterprise that considers commerce a digital platform rather than a website. Guideflow CIOPages

Choose Adobe Commerce if:

• You have complex merchandising rules.
• You need extensive customization.
• Your business depends heavily on ERP, PIM, marketplace, or B2B integrations.
• You already have Magento expertise.

Choose Shopify Plus if:

• Your priority is speed and operational simplicity.
• Your commerce model is primarily DTC.
• You want custom frontends but do not want to operate a commerce platform team.

Architecture I would target

For a modern enterprise stack, I would typically separate:

Frontend layer
├── Next.js / React / native apps / kiosks / marketplaces

Experience layer
├── Headless CMS
├── Personalization
├── Search
├── Recommendations

Commerce core
├── Product catalog
├── Pricing
├── Cart
├── Checkout
├── Promotions
├── Orders

Enterprise systems
├── ERP
├── CRM
├── OMS
├── PIM
├── Data platform

A common mistake is assuming “headless” automatically means “microservices everywhere.” Many enterprises get better outcomes with a well-designed headless commerce core plus carefully selected surrounding services, rather than splitting every capability into separate systems. Vendure Shopify

Decision rule of thumb

• Global enterprise + complex business models → commercetools
• Enterprise customization + existing Magento investment → Adobe Commerce
• Salesforce-centric organization → Salesforce Commerce Cloud
• Fast-growing digital brand → Shopify Plus
• Enterprise wanting SaaS + APIs without full composable complexity → BigCommerce

If you share your annual GMV, B2B vs B2C mix, number of SKUs, regions, current platform (Magento/SAP/Salesforce/custom), and engineering team size, I can narrow this to a more specific recommendation.

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: