All answers

If you’re launching a subscription box service, I’d shortlist these:

My pick: Shopify + a subscription app

If you're starting from scratch, Shopify is probably the best foundation. Its native subscription system supports weekly/monthly/yearly auto-billing, skips, pauses, cancellations, discounts, and customer self-service. Shopify Help Center Shopify

More importantly for a box business, Shopify handles subscription orders through its normal fulfillment workflow, including scheduled/prepaid fulfillments and splitting fulfillment by location or shipping profile. Shopify Help Center

shopify.com

When I'd choose Recharge

If you expect subscriptions to become the core of the business rather than just an add-on, I'd look closely at Recharge. It has a much deeper subscription ecosystem and integrations with tools such as Klaviyo, Gorgias, and Tapcart. Shopify

It's particularly attractive if you need things like:

• sophisticated subscription management
• better retention/dunning workflows
• multiple fulfillment/3PL integrations
• a large catalog of subscription products
• more advanced subscription analytics

One important distinction

For a subscription box, I'd separate the problem into two systems:

Billing/subscription engine → Shopify Subscriptions, Recharge, Appstle, etc.
Physical fulfillment → Shopify's fulfillment system + your warehouse/3PL.

That gives you flexibility to change fulfillment providers later without rebuilding your subscription business.

If I were launching today: I'd start with Shopify + Appstle if keeping costs low is important, or Shopify + Recharge if you're funded and expect substantial subscription volume. Shopify's own 2026 comparison also lists Appstle and Recharge among its leading recurring-payment options. Shopify

If you tell me roughly how many boxes/month you expect (e.g. 100, 1,000, 10,000) and whether customers choose the contents or receive a curated box, I can recommend the best setup and estimate the monthly software/transaction costs.

I recommend Shopify with Shopify Markets for most international stores. It offers the best balance of multi-currency, localized checkout, speed to launch, and operational simplicity. Shopify Markets supports local currencies, market-specific pricing, translated storefronts, regional domains, and localized checkout options. Shopify Shopify Help Center

Choose based on complexity:

• Best overall: Shopify Markets — ideal for DTC brands expanding into multiple countries with similar catalogs. Shopify
• Best for enterprise with highly different regional stores: BigCommerce Multi-Storefront — better when each country needs different catalogs, pricing rules, content, or checkout experiences. BigCommerce BigCommerce
• Best for very large/global operations: consider a composable stack (headless frontend + commerce platform + payment/tax providers) if regions operate almost independently.

My default decision rule:

• 1–10 countries, mostly the same products → Shopify Markets
• 10+ countries with major regional differences → BigCommerce Multi-Storefront or enterprise commerce
• Complex B2B + B2C + ERP requirements → evaluate enterprise platforms

For most growing international retailers, Shopify Markets is the lowest-risk choice. Shopify

If you’re an agency building and managing many separate client stores, I’d narrow it to Shopify Plus vs. BigCommerce vs. Adobe Commerce. The best choice depends heavily on whether you want one client = one independent store or many storefronts inside one commerce instance.

My recommendation: Shopify Plus

For an agency workflow, Shopify Plus is probably the best overall choice.

Shopify Plus has organization-level management for multiple stores, including centralized users, billing, security, and store administration. Plus also supports expansion stores, which is particularly relevant when you're operating multiple client/brand storefronts. Shopify Help Center Shopify Help Center

help.shopify.com

The important distinction, though, is:

Shopify Plus is excellent for managing multiple stores. It isn't really a "multi-client agency control panel."

So if your workflow is:

Client A → Store A
Client B → Store B
Client C → Store C
...with different ownership, billing, staff, apps, domains, and permissions

I'd generally keep each client as a separate Shopify store and build an agency operating layer around Shopify rather than trying to make all clients one giant multi-store installation.

How I'd rank them

BigCommerce deserves serious consideration

BigCommerce has an unusually strong multi-storefront model. Its dashboard lets you create and manage multiple storefronts, assign products to different storefronts, manage customers/orders, and maintain different themes, pricing, currencies, domains, etc. BigCommerce

Its current plans explicitly include Multi-Storefront, with additional storefront pricing depending on the plan. BigCommerce

bigcommerce.com

So if your agency is building something like:

One client company → 5 brands/regions/storefronts

I'd actually lean BigCommerce in some cases.

Adobe Commerce is the power-user option

Adobe Commerce is extremely capable here. A single Commerce installation can have multiple websites, stores, and store views, with different domains, catalogs, pricing, currencies, customer data, etc. Experience League Experience League

But there's a catch for an agency: it's considerably more infrastructure and engineering-heavy. Adobe itself notes that increasing the number of websites/stores increases catalog/indexing/configuration complexity and can affect performance. Experience League

So I'd choose it when the client needs that complexity—not simply because you're an agency.

The architecture I'd use for an agency

If you're building dozens or hundreds of client stores, I'd structure the business roughly like this:

Agency platform

→ Client/tenant management
→ Staff + permissions
→ Billing
→ Store provisioning
→ Templates/themes
→ App/integration configuration
→ Deployment/versioning
→ Analytics/reporting
→ Client handoff/offboarding

Commerce platform

→ Client Store A
→ Client Store B
→ Client Store C
→ Client Store D
→ etc.

That separation is important.

You don't really want your agency's internal "multi-store management" system to become entangled with the commerce platform's concept of a store.

If I were starting an agency today

I'd probably choose:

Shopify Plus → if your priority is fast builds, standardized client delivery, reliability, ecosystem, and low operational burden.

BigCommerce → if your priority is multi-storefront architecture, B2B, multiple catalogs/pricing structures, and more control over the commerce layer.

Adobe Commerce → if you're targeting large enterprise clients with highly customized commerce requirements.

If you tell me roughly how many stores you expect to manage (10 / 50 / 500+), whether each client needs a totally separate Shopify/BigCommerce account, and whether you're building a standardized "store factory" with reusable themes/apps, I can recommend the architecture I'd use—including provisioning, Git/deployment, permissions, billing, and client handoff.

Shopify offers the strongest overall supplier ecosystem for a dropshipping business with many supplier integrations. vender.com.br AFCommerce

Ranking for supplier ecosystem:

1. Shopify — Best overall

• Largest app ecosystem for supplier connections and automation. eSellSphere
• Strong integrations with DSers (AliExpress), Spocket (US/EU suppliers), CJdropshipping, Zendrop, print-on-demand suppliers, and private-label providers. Shopify
• Best if you expect to test many suppliers, automate fulfillment, and scale quickly.
• WooCommerce — Best for customization

• More control over supplier workflows and data.
• Good for businesses with developers who need custom APIs, ERP connections, or complex catalogs.
• More maintenance compared with Shopify. Parse
• BigCommerce — Best for larger operations

• Strong native ecommerce features and good multi-channel scaling.
• Usually better once you have volume and want fewer third-party apps. Ecommerce Website Create

For a multi-supplier dropshipping operation, I would typically choose:

• Shopify + supplier apps/APIs → fastest ecosystem growth.
• Shopify + custom middleware (e.g., ERP/order router) → if you have dozens or hundreds of suppliers.
• WooCommerce → if supplier integrations are highly custom and you have technical resources.

The key distinction: the ecommerce platform is only the storefront; your real supplier ecosystem comes from integration layers (APIs, apps, inventory sync, order routing, and fulfillment automation). dropshippingbook.com

For a tight monthly budget, I’d focus on minimizing recurring costs and avoiding a big app/plugin stack. The right choice depends on whether you value simplicity or control.

My shortlist for a constrained budget:

1. WooCommerce + inexpensive managed WordPress hosting

• Best if you already have WordPress skills or someone technical.
• You avoid a platform subscription, but you take on hosting, updates, security, and plugin management. WooCommerce
• Good for: 10–1,000 products, content-heavy sites, businesses that want flexibility.
• Shopify Basic (or equivalent entry plan)

• Best if you need to launch quickly and don’t want to maintain infrastructure.
• The tradeoff is ongoing subscription cost plus possible app costs as you grow. Shopify
• Good for: founders who want to spend time selling rather than maintaining a site.
• Ecwid

• Worth considering if you have a simple catalog and an existing website.
• Can be cheaper than running a full standalone ecommerce stack. Shopify

For a lean “core features only” setup, I’d aim for:

• Hosted platform: Shopify/Ecwid → fewer technical costs
• Self-hosted: WooCommerce → lower software cost, more maintenance
• Avoid initially: paid themes, marketing automation suites, review apps, upsell apps, and complex inventory tools unless they directly increase sales

A few details would change the recommendation:

• Monthly software budget (e.g., under $20, $50, $100)?
• Number of products/SKUs?
• Physical products, digital products, subscriptions, or services?
• Do you already have a website (WordPress, Wix, etc.)?

For a solo entrepreneur selling custom T-shirts, I’d lean toward Shopify + a print-on-demand provider such as Printful if your goal is to avoid server administration while still building a real branded store.

Why this setup fits

• No server management: Shopify includes managed hosting, unlimited bandwidth, SSL, checkout, and the core ecommerce infrastructure. Shopify
• Print-on-demand: Printful can print, package, and ship orders automatically, so you don't need to hold T-shirt inventory or run fulfillment yourself. Printful Shopify
• Automation: A customer orders on Shopify → the order is sent to Printful → Printful fulfills and ships it. Printful Help Center
• Brand control: You get your own storefront, domain, product pages, and customer experience rather than relying entirely on a marketplace.
• Solo-friendly pricing: Shopify's current Basic plan is listed at $29/month when paid annually ($39 month-to-month), aimed specifically at solo entrepreneurs. Shopify

The main alternatives

Printful itself offers Quick Stores if you want an even simpler starting point, while also integrating with Shopify, Etsy, and other ecommerce platforms. Printful Help Center

What I'd do in your position

Start with Shopify + Printful. You pay for Shopify's managed infrastructure and let Printful handle production/fulfillment. That leaves your time for the things a solo business actually needs: designs, marketing, customer acquisition, and brand building.

One caveat: Shopify doesn't bring customers to you automatically. If you have zero audience and want to test whether your designs sell before paying for a standalone store, Etsy can be a useful alternative because it has an existing marketplace audience. Printful

If you tell me your monthly budget (e.g. $20, $50, $100) and whether you plan to print yourself or use print-on-demand, I can narrow it down to the most economical setup.

For a tiny team selling internationally, I’d look first at Shopify, particularly if minimizing tax/currency administration is more important than having the absolute lowest platform cost.

How the main options compare

Shopify Markets lets you configure currencies, regional pricing, languages/domains, and tax/duty presentation from one admin. Shopify Help Center Shopify Help Center

The particularly relevant feature for a tiny team is Shopify Managed Markets: where available, Global-e acts as the merchant of record and handles foreign tax registrations, remittance, duties and import taxes. Shopify currently lists a 3.5% Managed Markets transaction fee on Basic/Grow/Advanced, plus a 1.5% FX fee, on top of payment-processing fees. Shopify Help Center

That distinction matters: Shopify Markets alone does not make your tax obligations disappear—you remain the merchant of record and responsible for registrations/compliance. Shopify Help Center

Wix is also quite approachable: its multi-currency feature supports actual checkout in local currencies, and automated international tax calculation is available through Avalara. Wix Help Center wix.com

My practical shortlist for a tiny team:

• Shopify + Managed Markets → if you want to outsource as much international tax/duty complexity as possible.
• Shopify Markets without Managed Markets → if you're comfortable handling your own registrations/compliance and want lower additional fees.
• Wix → worth considering if site-building simplicity is your priority and your international footprint is relatively straightforward.
• WooCommerce → I'd choose it primarily when you already have strong WordPress expertise or need its flexibility, rather than for simplicity. WooCommerce

One important caveat: “taxes” isn't just calculating the right checkout rate. Whether you actually need to register, collect, and remit VAT/GST/sales tax depends on where your business and customers are, what you're selling, and local thresholds/rules.

If you tell me where your company is based, what you're selling (physical/digital), and your first 3–5 target countries, I can narrow this down to the simplest setup and flag where you'd likely need tax registrations.

That distinction matters: Shopify Markets alone does not make your tax obligations disappear—you remain the merchant of record and responsible for registrations/compliance.

For a small maker business—handmade goods, art, candles, jewelry, crafts, etc.—I’d narrow it to Square vs. Shopify.

My pick: Square

If your priority is simple POS + a straightforward online store without spending much, I’d start with Square.

• Square Free is $0/month and includes POS, inventory, sales reporting, customer management, and an online store that syncs with your in-person sales. Square Square
• It’s particularly good if you sell at markets, craft fairs, pop-ups, and occasional in-person events.
• Hardware is inexpensive: Square's contactless/chip reader is currently $59, while a Terminal is $299. Square
• You can start with essentially no monthly software commitment and upgrade later if you need advanced inventory, loyalty, staff management, etc. Square

When I'd choose Shopify instead

Pick Shopify if you expect the online store to become the center of the business.

Shopify has a stronger ecommerce ecosystem, more sophisticated online-store customization, marketing integrations, and room to grow. Its POS also keeps online and in-person inventory/orders connected. Shopify

The tradeoff is cost: Shopify Basic is currently $39/month month-to-month ($29/month when billed annually), before optional POS Pro, while Square can start at $0/month. Shopify Shopify

Quick decision

If I were starting a small maker business today, I'd start with Square. You can get the physical POS and online shop working together without committing to a substantial monthly subscription. If the online side takes off, moving to a more ecommerce-heavy setup becomes worth considering.

If you tell me what you make, roughly how many products you have, whether you sell mostly at markets or online, and your expected monthly sales, I can tell you which one I'd pick for your situation and estimate the actual monthly/payment-processing cost.

For a small artisan business selling ready-to-ship products alongside made-to-order/custom pieces, I’d lean toward Shopify.

Best fit: Shopify

Shopify is particularly strong when you need more than a simple storefront:

• Regular products: sell normally with inventory tracking.
• Pre-orders: Shopify supports pre-orders, including full, partial, or no payment upfront depending on your setup. Shopify Shopify Help Center
• Made-to-order: there are numerous Shopify apps specifically supporting made-to-order pre-orders. Shopify App Store
• Deposits: apps such as Downpay can handle deposits/partial payments for custom and pre-order sales. Shopify App Store
• Custom lead times: you can communicate different production/shipping windows per product or variant, with apps available when you need more sophisticated workflows.
• Room to grow: if you eventually have dozens of custom orders, multiple product options, or more complicated fulfillment, Shopify is less likely to become a constraint.

shopify.com

A simpler option: Big Cartel

Big Cartel is appealing if your catalog is small and you want something very straightforward. However, it doesn't have a dedicated pre-order setting; Big Cartel suggests putting the pre-order information and expected ship date in the product description and processing the order normally. Big Cartel

So I'd rank them:

My recommendation: If "made-to-order" is a core part of your business rather than an occasional exception, choose Shopify. If you mainly want a beautiful, simple shop with a handful of products and can communicate lead times manually, Big Cartel may be enough.

If you tell me what you make (e.g. ceramics, jewelry, furniture, clothing) and roughly how many orders you expect per month, I can narrow this down to 2–3 platforms and explain the exact workflow I'd use for custom orders.

Yes. For a brick-and-mortar studio selling scheduled classes + physical merchandise, I’d shortlist these:

Best fits

1. Wix — probably the simplest all-in-one choice

• Wix Bookings handles classes, workshops, private sessions, schedules, payments, memberships/packages, and client reminders. Wix Support wix.com
• Wix Stores handles merch, inventory, shipping, variants, and checkout. You can put both services and products in the same cart. Wix Support Wix Support
• This is particularly attractive if you want one website, one customer database, and one checkout experience.
• Squarespace + Acuity — best if the website/brand experience matters most

• Squarespace Commerce supports physical products, while Acuity Scheduling handles scheduled classes and appointments. Squarespace Help Squarespace
• Acuity supports classes, packages, subscriptions, gift cards, payments, reminders, and attendance-oriented scheduling. Squarespace Acuity Scheduling Help Center
• Squarespace also specifically supports selling classes/workshops with limited spots through its store. Squarespace Help
• I'd choose this if you want a polished, design-forward studio website.

My recommendation

Start with Wix if your priority is operational simplicity:
Class → book/pay → customer gets reminders → merch → same site/cart → inventory/order management.

Choose Squarespace + Acuity if your studio is highly brand-driven and you care more about having a beautiful, premium-looking site.

One important distinction: if by "classes" you mean fixed-time group classes with limited capacity (e.g. pottery Tuesday at 6 PM, 12 seats), I'd favor Wix Bookings or Acuity rather than treating classes merely as ecommerce products. Both are designed for actual scheduling. Wix Support Squarespace

If you tell me what kind of studio you run (fitness, art, dance, photography, ceramics, music, etc.) and roughly how many classes/customers you have per week, I can narrow it down to the best 2–3 options and compare monthly cost, booking fees, POS/in-person sales, memberships, and merch inventory.

For a small handmade-goods shop on a tight budget, I’d start with squareup.com.

• $0/month on the Free plan.
• You get a hosted storefront, checkout, shipping/local delivery, and inventory tools. Square Square
• You pay processing fees when you actually sell—currently 2.9% + $0.30 for the applicable online/API rate, with Square's fee structure varying by payment method. Square
• It's particularly attractive if you also sell at craft fairs or markets, because Square can connect online and in-person sales.

Another great option: Big Cartel

If you have only a tiny product catalog and want something aimed specifically at artists/makers, bigcartel.com is worth considering. Its free Gold plan supports up to 5 products, with no monthly subscription. Big Cartel Big Cartel

What I'd choose

My recommendation: Start with Square Online Free, get 5–20 products photographed and listed, and avoid paying for a custom domain or premium design until you're actually making consistent sales. You can upgrade later without rebuilding your whole business. Square

If you tell me roughly how many products you plan to sell and whether you'll also sell at local craft fairs, I can tell you which of Square, Big Cartel, Etsy, or Shopify is likely to cost you the least.

For a two-person startup validating product-market fit, I’d optimize for speed and low commitment, not maximum features.

My pick: Shopify

Shopify is probably the best default for you.

• Minimal setup: hosted store, checkout, payments, inventory, shipping, analytics, and templates are all in one place.
• Cheap to test: Shopify currently offers 3 days free, then 3 months for $1/month; the Basic plan is $29/month when billed annually. Shopify Shopify
• You won't have to migrate later: if the experiment works, Shopify can grow with you instead of becoming throwaway infrastructure.
• Good for a tiny team: Basic gives you a full online store and unlimited products without needing developers. Shopify Help Center

shopify.com

But there are two cheaper options

Square's free tier can give you a hosted storefront without a monthly subscription, although payment processing still applies. Big Cartel's free tier is limited to five products. iTechGuides Shopify

What I'd do in your shoes

Start with Shopify Basic and spend almost nothing on customization.

Use:

• A free theme
• Shopify Payments
• Your own domain
• 1–5 products
• No paid apps initially
• Shopify's built-in analytics
• Simple product photography
• One clear landing/product page

The goal isn't to build a beautiful ecommerce operation. It's to answer "Will strangers give us money for this?"

Once you're getting meaningful sales, then worry about subscriptions, sophisticated email automation, CRO, custom design, etc.

One caveat: if you're literally testing with a handful of products and expect fewer than ~5–10 orders/month, I'd seriously consider Square Online's free tier first. The $29/month Shopify subscription is worthwhile mainly because it gives you a much better long-term foundation.

If you tell me what you're selling (physical vs. digital), roughly how many SKUs, expected monthly sales, and whether you already have a website/domain, I can narrow this down to the cheapest sensible setup for your specific PMF test.

For an agency demo store (not a real merchant launch), I’d prioritize fast setup, shareable URL, realistic catalog/admin experience, and no credit card. Good options:

My picks by use case:

• Fastest prospect demo: Wix
• Most realistic ecommerce agency demo: Spree sandbox
• Showing Shopify/BigCommerce-style SaaS commerce: BigCommerce trial
• Permanent free URL you can keep showing prospects: a free hosted store builder like Freewebstore (with the tradeoffs of free plans) Freewebstore

For an agency, I’d probably create:

• 10–20 fake products
• branded homepage
• collection pages
• product detail page
• cart/checkout flow (even if checkout is disabled)
• a “behind the scenes” admin screenshot/video

If the goal is to impress B2B ecommerce prospects, I’d lean toward Spree; if the goal is a pretty portfolio demo link, I’d lean Wix. Spree Commerce wix.com

For a farmers’ co-op, I’d focus on software that supports multiple independent vendors, shared checkout, vendor commissions/payouts, product inventory, and pickup/delivery, without requiring a big custom build.

Shortlist

Sharetribe is probably the easiest place to start. It is purpose-built for marketplaces, doesn't require coding, supports product marketplaces and online payments, and its current live plans start at $99/month when billed annually. Sharetribe Sharetribe

sharetribe.com

WooCommerce is worth considering if someone in your co-op is comfortable administering WordPress. WooCommerce itself doesn't provide multi-vendor functionality—you add a marketplace plugin—but this approach can give you considerably more control over product variations, local pickup, subscriptions, farmers' boxes, and other agricultural-specific workflows. Dokan

CS-Cart Multi-Vendor is the more full-featured option. Its current cloud Basic plan is $95/month and supports up to 50 vendors; the platform specifically includes vendor commissions and marketplace-oriented payment flows. Its annual on-premise Standard plan is $725/year. www.cs-cart.com/ CS-Cart Documentation

What I'd prioritize for your co-op

Rather than paying for a conventional e-commerce store, I'd make sure the platform can handle this workflow:

Customer orders from 5 farms → one checkout → each farmer sees only their items → co-op takes its agreed commission → farmer gets their share → everything is consolidated for one pickup/delivery.

That last part is particularly important. A platform can technically be a "multi-vendor marketplace" while still being awkward for a farmers' market-style weekly ordering + centralized pickup model.

If you tell me roughly how many vendors you have, how many customers/orders you expect per week, whether customers pick up at one location or get delivery, and your monthly software budget, I can narrow this to 2–3 concrete setups and estimate the total monthly cost.

If your priority is “I want to take a client’s weird business requirement and implement it without fighting the platform,” I’d pick medusajs.com.

My ranking for a freelance developer

1. Medusa — my default recommendation

Medusa is particularly well suited to the kind of work you're describing. Its architecture explicitly separates API routes → workflows → modules → database, and custom modules can contain their own data models and business logic. Medusa Docs Medusa Docs

The important bit for a freelancer is that you aren't forced to build every integration as an external service. You can put things like:

• ERP synchronization
• custom pricing
• unusual fulfillment logic
• marketplace functionality
• custom payment providers
• customer-specific business rules
• scheduled jobs and event handlers

inside the Medusa application itself. Its workflows can orchestrate multiple systems, while modules provide the integration boundary. Medusa Docs

It also has a particularly nice reuse story: package a client's reusable functionality as a plugin containing modules, workflows, API routes, etc., then install that plugin into another client's Medusa project. Medusa Docs

For someone doing repeated client projects, that's a big advantage.

docs.medusajs.com

2. Vendure — arguably the closest competitor

If you're a TypeScript developer, I'd seriously evaluate vendure.io alongside Medusa.

Vendure's model is very plugin-centric: plugins can add entities, business logic, GraphQL API extensions, permissions, and Admin UI functionality. Vendure Vendure Vendure

That makes it excellent for a freelancer building repeatable vertical solutions.

I'd lean Vendure over Medusa if you particularly like GraphQL and want a more opinionated plugin architecture. I'd lean Medusa if you want maximum freedom and a more modular “commerce framework” feel.

3. Sylius — excellent if you're a PHP developer

sylius.com is extremely extensible because it's fundamentally a Symfony-based framework rather than a traditional monolithic store builder. Its plugin architecture is designed specifically for extending functionality without modifying core code. Sylius Academy

If you're already strong in Symfony/PHP, I wouldn't dismiss it just because Medusa is trendy. For deeply customized B2B/enterprise projects, Sylius can be an excellent choice.

4. Saleor — great API, slightly different philosophy

saleor.io is attractive if you want GraphQL everywhere and prefer integrations to live primarily as apps/extensions. Its documentation has dedicated concepts for apps, dashboard extensions, custom modeling, payments, channels, etc. Saleor Documentation

I'd choose it when a client's requirements are particularly multi-channel / international / B2B rather than simply “we need lots of custom code.”

5. WooCommerce — easiest to sell, not necessarily easiest to architect

woocommerce.com remains compelling because its ecosystem is enormous. Its extension model gives you PHP hooks, REST APIs, webhooks, Store API extensions, payment APIs, shipping APIs, etc. The WooCommerce Developer Blog The WooCommerce Developer Blog

But there's a catch: you're extending WordPress + WooCommerce, so sufficiently unusual requirements can turn into wrestling with WordPress conventions, plugin interactions, update compatibility, and legacy APIs. WooCommerce itself warns that relying on internal APIs can cause extensions to break during updates. The WooCommerce Developer Blog

So I wouldn't choose WooCommerce purely because “it's easy to extend.”

What I'd use in your position

I'd standardize around:

Medusa + PostgreSQL + TypeScript + Next.js

and build your own reusable layer of:

/client-project
  /src
    /modules
      erp/
      custom-pricing/
      shipping/
      loyalty/
    /workflows
    /api
    /subscribers
  /plugins
    your-reusable-integrations

That gives you a useful flywheel: client #1 pays you to build an integration → you package the generalized version → client #2 becomes substantially faster.

Medusa's current architecture is explicitly designed around this sort of customization and reuse. Medusa Docs Medusa Docs

Bottom line: If you're primarily a JS/TS freelancer doing bespoke integrations, I'd start with Medusa, with Vendure as the alternative I'd benchmark before committing. If you're PHP/Symfony-native, choose Sylius instead.

If multi-vendor marketplace functionality + total control of your data and infrastructure are the two hard requirements, I’d shortlist Bagisto, Mercur, and Vendure rather than a hosted marketplace platform.

My practical shortlist

1. Bagisto — strongest if you want marketplace features out of the box

Bagisto is particularly interesting because its official repository explicitly includes a Multi Vendor Marketplace capability: vendor dashboards, seller management, commissions, product approval, order handling, etc. It also has multi-tenant capabilities. The core project is MIT licensed. GitHub GitHub

That makes it attractive if your goal is:

• Multiple independent sellers
• Vendor dashboards
• Vendor catalogs
• Commissions
• Product approval
• Marketplace order management
• PHP/Laravel expertise
• Maximum control over your database and hosting

Tradeoff: its Laravel architecture may be less attractive if your engineering organization is primarily TypeScript/Node.js.

2. Mercur — particularly compelling for a modern marketplace

Mercur is purpose-built around the marketplace problem rather than simply being an ecommerce platform that you extend. It provides marketplace-specific primitives such as vendors, commissions, payouts, multi-vendor catalogs, an admin panel, vendor panel, and storefronts, while using Medusa underneath. GitHub GitHub

Its architecture is also explicitly designed for self-hosting: Node.js + PostgreSQL + Redis, with deployment options including containers/Kubernetes and even air-gapped environments. GitHub

For a company saying "we want Amazon/AliExpress-style marketplace functionality, but we want to own the infrastructure and data," I'd investigate Mercur first.

One important consideration is that Mercur also has an Enterprise layer, so you should carefully distinguish which functionality you need from the fully open-source core versus licensed additions. GitHub

3. Vendure — excellent if your marketplace is highly customized

Vendure is a TypeScript/NestJS/GraphQL platform with a plugin architecture and is explicitly positioned for B2B, multi-vendor marketplaces, and custom commerce models. GitHub GitHub

I'd lean toward Vendure when your marketplace has unusual business rules—for example:

• Complex vendor-specific pricing
• Multiple sales channels
• Sophisticated catalog relationships
• Custom fulfillment
• B2B + B2C
• Complex permissions
• Significant custom development

Its plugin-first architecture lets you extend the system without maintaining a heavily modified fork. GitHub

What about Medusa itself?

Medusa is a very good commerce foundation, but I'd distinguish Medusa from Mercur for this particular requirement.

Medusa's core is MIT-licensed and can be used to build marketplaces, but historically marketplace functionality was not native; the project itself described marketplace functionality as something that needed to be extended. GitHub GitHub

Mercur essentially addresses that gap by putting a dedicated marketplace layer on top of Medusa. GitHub

What I'd choose

For your stated requirements, I'd evaluate them in this order:

Mercur → Bagisto → Vendure

But the deciding factor is your technology stack:

• Laravel/PHP team: Bagisto
• Node/TypeScript team + modern marketplace: Mercur
• Node/TypeScript team + very complex/custom enterprise commerce: Vendure
• You want to assemble your own commerce architecture: Medusa

And by "total data ownership," I'd specifically verify that the deployment you choose lets you own/control the PostgreSQL database, object storage, search indexes, logs, backups, payment-related data, and analytics data. "Open source" by itself doesn't guarantee that every associated SaaS service is self-hostable.

If you tell me your stack (PHP vs Node), expected number of vendors, B2B/B2C, and whether you need vendor payouts/commissions, I can narrow this to the most appropriate architecture and compare the actual marketplace features and licensing in detail. GitHub GitHub GitHub

What I'd choose

For your stated requirements, I'd evaluate them in this order:

If your priorities are full data ownership + a manageable migration, I’d put PrestaShop at the top of the list.

My shortlist

Why I'd choose PrestaShop: its migration tooling is unusually practical. It supports importing categories, products, variants, customers, addresses, brands, suppliers, etc. through CSV, with field mapping, and PrestaShop explicitly documents migrations from platforms including Shopify, WooCommerce, BigCommerce, OpenCart and Adobe Commerce. PrestaShop Help Center PrestaShop Help PrestaShop

It also means your store/database can live on infrastructure you control rather than being tied to a hosted SaaS provider. PrestaShop specifically describes this as giving merchants control over their customer and product data. PrestaShop

The important caveat

Don't choose based only on "can I export my products?" A migration usually has to account for:

• Products, variants, categories and images
• Customers and addresses
• Historical orders
• Discounts/coupons
• Reviews
• SEO URLs and redirects
• Taxes and shipping rules
• Payment integrations
• Custom fields/metafields from your current platform

PrestaShop's own migration guidance recommends migrating in roughly that order and emphasizes validating the imported record counts against the old store. PrestaShop Help Center

Medusa is attractive if by "full control" you mean I want to own the entire commerce architecture and build a custom frontend. Its current migration tooling can import products, variants, prices, images, inventory and categories, but it's a considerably more developer-oriented migration than moving into a traditional ecommerce platform. Medusa Docs Medusa

So my rule of thumb is:

• Want the least painful escape from SaaS → PrestaShop
• Already comfortable with WordPress → WooCommerce
• Want a custom/headless architecture → Medusa
• Huge catalog, B2B, complex pricing/multiple stores → Magento Open Source

If you tell me what hosted platform you're migrating from (Shopify, BigCommerce, Wix, Squarespace, etc.), approximate product/order count, and whether you need subscriptions or B2B, I can narrow this to the best 1–2 choices and outline the actual migration path.

For a low-traffic boutique store run by a non-technical owner, I’d generally choose WooCommerce—provided you use managed WordPress/WooCommerce hosting rather than maintaining the server yourself.

How I’d compare the main options

Why WooCommerce: the day-to-day interface is familiar to WordPress users, installation is handled through the WordPress admin, and there is a large ecosystem of themes and extensions. WooCommerce WooCommerce

The important caveat is that self-hosted doesn't mean maintenance-free. WooCommerce requires keeping WordPress, PHP, WooCommerce, themes, and plugins current, and WooCommerce specifically recommends current supported PHP/MySQL versions. WooCommerce WooCommerce

OpenCart is a reasonable second choice. Its admin interface is specifically designed around store management, and its current upgrade tool can download and install updates from the admin panel. However, its own documentation recommends backups, staging, and checking extension compatibility before upgrades—tasks that are less appealing for a non-technical owner. OpenCart Documentation OpenCart Documentation

PrestaShop is powerful, but I'd be less inclined to use it for this particular scenario. Its current requirements and upgrade process involve more server/configuration considerations, and PrestaShop 9 recommends PHP 8.4 and substantial server memory. PrestaShop Help Center PrestaShop

My practical setup

For this particular store, I'd use:

WooCommerce + managed WordPress hosting + automatic backups + a hosted payment gateway + as few plugins as possible.

That combination is considerably easier for an owner to operate than handing them a bare VPS and saying "here's your self-hosted ecommerce system."

If by self-hosted you mean "I want to own/control the software and host it myself, but I don't want to become the sysadmin," I can also compare WooCommerce vs OpenCart vs PrestaShop vs Saleor specifically on setup time, updates, backups, security, and ongoing owner workload.

For a SaaS company that wants a small self-hosted store primarily for selling software licenses, I’d look first at WooCommerce, especially if you want the store to coexist with an existing SaaS billing system rather than become your billing system.

My shortlist

Why I'd lean WooCommerce

WooCommerce has unusually mature support for the exact combination you're describing:

• Recurring billing: WooCommerce Subscriptions supports weekly/monthly/annual billing, trials, upgrades/downgrades, cancellations, failed-payment handling, and 25+ payment gateways. WooCommerce
• Software licensing: extensions such as Kestrel's API Manager can issue license/API keys, control activations, and validate licenses from your SaaS. WooCommerce WooCommerce
• Subscription ↔ license lifecycle: Kestrel explicitly documents integration between its API Manager and WooCommerce Subscriptions. A subscription cancellation/expiration can deactivate the associated API keys, while plan changes can move the API access to the new subscription. WooCommerce
• Your SaaS can remain the source of truth: I'd structure it so WooCommerce handles commerce/order/payment orchestration, while your existing SaaS billing/account system remains authoritative for the actual customer account and application entitlement.

That last point is important. If you already have something like Stripe Billing, Chargebee, Recurly, Paddle, or an internal billing service, I wouldn't automatically move billing into the ecommerce platform just because you're adding a store.

A sensible architecture

For a SaaS selling, say, $99/year licenses and a few add-ons, I'd consider:

                 ┌─────────────────┐
                 │   Your SaaS     │
                 │                 │
                 │ Account/Entitle │
                 │ License service │
                 └────────┬────────┘
                          │ API/Webhooks
                          │
             ┌────────────▼────────────┐
             │       WooCommerce       │
             │                         │
             │ Store / Cart / Checkout │
             │ Orders                  │
             │ Subscriptions           │
             │ License provisioning    │
             └────────────┬────────────┘
                          │
                    Payment gateway
                          │
                    ┌─────▼─────┐
                    │  Stripe   │
                    └───────────┘

Or, if your existing billing system is already mature:

Customer
   │
   ▼
WooCommerce ────► Existing billing system
   │                       │
   │                       ▼
   └──────────────► SaaS entitlement/license service

The second model is attractive because you avoid having two competing subscription databases.

What about Medusa?

Medusa is interesting if your engineering team wants a modern, API-first/headless architecture. But there's a significant distinction: Medusa doesn't provide subscriptions natively. Its documentation describes subscriptions as something you implement/customize, using Stripe as an example. Medusa Docs

So I'd choose Medusa if you say:

"We're developers, we want the ecommerce engine as an API, and we're happy to build the subscription/license integration ourselves."

I wouldn't choose it merely because it's technically cleaner if the store is going to be small.

What about Saleor?

Saleor is similarly attractive for an API-first SaaS architecture, but you're taking on more of the integration yourself. For a small license store, that can be unnecessary engineering overhead.

My practical recommendation

If your requirements are approximately:

• self-hosted
• small catalog
• SaaS/software licenses
• one-time purchases and recurring licenses
• Stripe or another mainstream payment provider
• license activation/deactivation
• customer portal
• minimal custom ecommerce development

I'd start with WooCommerce + WooCommerce Subscriptions + a licensing/API extension.

The particularly interesting option is Kestrel API Manager, because its documentation explicitly covers SaaS licensing and its integration with WooCommerce Subscriptions. WooCommerce WooCommerce

woocommerce.com
woocommerce.com

If you tell me what billing system your SaaS already uses (Stripe Billing, Chargebee, Paddle, Recurly, etc.) and whether the licenses are perpetual or recurring, I can narrow this down to a concrete architecture and 2–3 options.

What about Medusa?

Medusa is interesting if your engineering team wants a modern, API-first/headless architecture. But there's a significant distinction: Medusa doesn't provide subscriptions natively. Its documentation describes subscriptions as something you implement/customize, using Stripe as an example.

So I'd choose Medusa if you say:

"We're developers, we want the ecommerce engine as an API, and we're happy to build the subscription/license integration ourselves."

I wouldn't choose it merely because it's technically cleaner if the store is going to be small.

What about Saleor?

Saleor is similarly attractive for an API-first SaaS architecture, but you're taking on more of the integration yourself. For a small license store, that can be unnecessary engineering overhead.

My practical recommendation

If your requirements are approximately:

If ERP + shipping integrations are the main requirement, I’d shortlist Shopware, Medusa, and Sylius rather than choosing purely on storefront features.

My practical comparison

Shopware

Shopware is particularly compelling if you want lots of existing connectors rather than building everything yourself.

Its API-first architecture supports ERP, PIM, CRM and other systems, and Shopware says its ecosystem has hundreds of extensions/connectors, including ERP and shipping integrations. Shopware Shopware

Its current integration ecosystem specifically lists things such as ShipStation for shipping and Xentral for ERP, while its marketplace also has an Odoo connector. Shopware Shopware Store

I'd lean Shopware if: you're a growing retailer and want integration flexibility without turning the ecommerce platform itself into a major software-development project.

Medusa

Medusa is arguably the most attractive if your developers will own the integrations.

Medusa treats external systems as modules and explicitly supports custom ERP integrations. Its documentation includes an ERP integration recipe and an Odoo integration, while its fulfillment modules include ShipStation. Medusa Docs Medusa Docs

That architecture is useful when, for example, you need:

ERP → inventory/pricing → ecommerce → order → shipping provider → tracking → ERP

and the standard workflow doesn't quite match your business. Medusa is designed to let you insert custom flows and logic into those processes. Medusa Docs Medusa Docs

I'd lean Medusa if: you have a competent TypeScript/Node team and expect significant custom integration work.

Sylius

Sylius is another strong option, particularly for a company with PHP/Symfony expertise. It's API-oriented and deliberately designed as a framework for highly customized commerce rather than simply a ready-made shop. GitHub

Its marketplace currently has a dedicated integrations category with dozens of integration plugins for ERPs, CRMs and external services. Sylius Addons Marketplace

I'd lean Sylius if: you're building something unusually customized and already have a strong Symfony/PHP engineering team.

The key distinction

I'd frame the decision this way:

• Want the largest ready-made integration ecosystem: Shopware
• Want maximum API/customization flexibility with modern TypeScript: Medusa
• Want a highly programmable commerce framework with Symfony/PHP: Sylius
• Want WordPress + ecommerce: WooCommerce

For a growing store, rather than an engineering-heavy custom commerce project, Shopware is probably the first platform I'd investigate. If you tell me which ERP (e.g. SAP, NetSuite, Odoo, Dynamics, Acumatica) and which shipping providers (e.g. ShipStation, Shippo, EasyPost, UPS/FedEx APIs) you're using, I can compare the actual integration paths and likely custom-development burden for each.

Shopware

Shopware is particularly compelling if you want lots of existing connectors rather than building everything yourself.

Its API-first architecture supports ERP, PIM, CRM and other systems, and Shopware says its ecosystem has hundreds of extensions/connectors, including ERP and shipping integrations. Shopware Shopware

Its current integration ecosystem specifically lists things such as ShipStation for shipping and Xentral for ERP, while its marketplace also has an Odoo connector. Shopware Shopware Store

I'd lean Shopware if: you're a growing retailer and want integration flexibility without turning the ecommerce platform itself into a major software-development project.

Medusa

Medusa is arguably the most attractive if your developers will own the integrations.

Medusa treats external systems as modules and explicitly supports custom ERP integrations. Its documentation includes an ERP integration recipe and an Odoo integration, while its fulfillment modules include ShipStation. Medusa Docs Medusa Docs

That architecture is useful when, for example, you need:

ERP → inventory/pricing → ecommerce → order → shipping provider → tracking → ERP

and the standard workflow doesn't quite match your business. Medusa is designed to let you insert custom flows and logic into those processes. Medusa Docs Medusa Docs

I'd lean Medusa if: you have a competent TypeScript/Node team and expect significant custom integration work.

Sylius

Sylius is another strong option, particularly for a company with PHP/Symfony expertise. It's API-oriented and deliberately designed as a framework for highly customized commerce rather than simply a ready-made shop. github.com

Its marketplace currently has a dedicated integrations category with dozens of integration plugins for ERPs, CRMs and external services.

I'd lean Sylius if: you're building something unusually customized and already have a strong Symfony/PHP engineering team.

The key distinction

I'd frame the decision this way:

For your setup, I’d pick payhip.com.

Why it fits a one-person creative business:

• $0/month to start, with a 5% transaction fee on the free plan. You get unlimited products and all features. Payhip Payhip
• It’s designed for ebooks, PDFs, printables, art, and other digital downloads, with multiple-file uploads and automatic delivery after purchase. Payhip Help Center Payhip Help Center
• It can handle EU VAT, which is particularly useful if you're selling to European customers. Payhip
• You can create a simple branded storefront without building a full ecommerce website.
• As you grow, the paid plans reduce the platform fee to 2% ($29/month) or 0% ($99/month). Payhip

What I'd choose

Gumroad is still very easy, and it handles worldwide tax obligations as a merchant of record, but its current direct-sale fee is 10% + $0.50, substantially more than Payhip's free plan. Gumroad Gumroad

My recommendation: start on Payhip Free, put your ebooks and printable bundles there, and drive traffic from Pinterest/Instagram/TikTok/email. You can upgrade only once your sales volume makes the 2% plan worthwhile.

If you tell me roughly how much you expect to sell per month (e.g. $300, $1,000, $3,000), I can calculate which storefront gives you the lowest total fees.

If you’re an agency managing multiple client stores, I’d separate the requirements into two things:

1. Each client gets their own storefront + account/admin
2. Your agency can centrally provision/manage those stores without exposing the underlying platform

Best fits

The big issue with Sellfy, for example, is that it explicitly allows only one storefront per account and doesn't currently support multiple users on an account. Sellfy Help Center

Podia is much better for the actual digital-product experience: it supports custom domains, branded storefronts, customer accounts, digital downloads, courses, memberships, etc. Podia But I wouldn't choose it as the underlying multi-client agency platform if you're trying to operate dozens/hundreds of independent stores.

What I'd choose for your agency

Shopify is probably the strongest default.

You can create a separate Shopify store for each client, give the client appropriate staff access, keep your agency as the development/management partner, and completely brand the storefront around the client's business. Shopify also has a mature partner ecosystem for agencies and supports multi-store/expansion-store setups. Axis Web Art BIZSPICE - Shopify Studio for US Brands

The architecture I'd use is roughly:

YOUR AGENCY
│
├── Client A
│   └── Shopify Store A
│       ├── client admin account
│       ├── custom domain
│       ├── client's branding
│       └── digital products
│
├── Client B
│   └── Shopify Store B
│       ├── client admin account
│       ├── custom domain
│       ├── client's branding
│       └── digital products
│
└── Client C
    └── Shopify Store C
        ├── client admin account
        ├── custom domain
        ├── client's branding
        └── digital products

That gives you true separation between clients, while your agency retains operational control.

But there's an important distinction

If by "white-label" you mean:

Our agency has one SaaS platform, we create stores inside it, clients log into their own branded dashboard, and they never know Shopify/another underlying platform exists.

Then Shopify isn't quite the same thing. You're really looking for a multi-tenant/agency SaaS commerce platform or potentially a custom layer on top of Shopify/WooCommerce.

If that's what you're building, I can compare the best 5 platforms specifically for an agency wanting to provision 50–1,000+ digital-product stores, including client login, sub-accounts, custom domains, white-label admin, Stripe Connect, fees, APIs, and automation.

If your core need is selling high-res photo downloads while showing protected previews, the main photography-focused storefronts worth comparing are Pixieset, Pic-Time, and ShootProof.

Pixieset

pixieset.com is probably the cleanest match if you want a straightforward "browse → preview → buy → automatically download" experience.

Its watermark system applies watermarks to displayed images, while your original remains unwatermarked. You can also configure web-size downloads to retain the watermark. Importantly, high-resolution/original downloads are delivered without the watermark, so buyers get the actual file they purchased. Pixieset Website Help Center Pixieset Website Help Center

For variants, you can create digital-download products with different resolutions—for example, a web-resolution product versus a high-resolution product—and sell either individual images or an entire collection. Pixieset Website Help Center

Pic-Time

pic-time.com is particularly interesting if you're selling fine-art/stock-like photography rather than just delivering client galleries.

It supports watermarked gallery and shop previews, including flexible or permanently burned-in low-resolution watermarks. High-resolution downloads aren't watermarked. Pic-Time Help Center Pic-Time Help Center

It also supports high-res download products priced per image, by volume, or as tiered packages, which is useful if you want things like "1 image / 5 images / entire set" offerings. Pic-Time Help Center

ShootProof

shootproof.com also checks the major boxes. Its current watermarking supports text/image watermarks with control over position, size and opacity, plus an optional AI-protection mode. Purchased digital downloads are delivered without the watermark. ShootProof Support

What I'd look at for your particular business

If you're selling individual high-resolution photographs as a product, rather than primarily delivering wedding/portrait galleries to clients, I'd pay particular attention to:

1. Pic-Time — strong fit if you want sophisticated storefront merchandising and packages.
2. Pixieset — strong fit if you want the simplest polished storefront and gallery combination.
3. ShootProof — worth considering if its broader client-management workflow fits your business.

One important distinction: watermarks generally belong on the preview, not the purchased high-res file. All three platforms support that basic model, which is what you'd want for selling downloadable originals. Pixieset Website Help Center Pic-Time Help Center ShootProof Support

If you tell me (a) whether you sell individual images or collections, (b) whether you need RAW/TIFF or just JPEG, and (c) your approximate monthly sales volume, I can narrow this down further and compare pricing, transaction fees, storage, custom-domain support, and download-size controls.

For variants, you can create digital-download products with different resolutions—for example, a web-resolution product versus a high-resolution product—and sell either individual images or an entire collection. Pixieset Website Help Center

Pic-Time

pic-time.com is particularly interesting if you're selling fine-art/stock-like photography rather than just delivering client galleries.

It supports watermarked gallery and shop previews, including flexible or permanently burned-in low-resolution watermarks. High-resolution downloads aren't watermarked. help.pic-time.com help.pic-time.com

It also supports high-res download products priced per image, by volume, or as tiered packages, which is useful if you want things like "1 image / 5 images / entire set" offerings. help.pic-time.com

ShootProof

shootproof.com also checks the major boxes. Its current watermarking supports text/image watermarks with control over position, size and opacity, plus an optional AI-protection mode. Purchased digital downloads are delivered without the watermark.

What I'd look at for your particular business

For your setup—paid online courses + downloadable resources + completion certificates—I’d look first at a course-first platform with built-in ecommerce, rather than Shopify/WooCommerce with a separate LMS.

Strong options

Thinkific is particularly well aligned with your requirements. It supports courses, paid digital downloads, and automatically issued completion certificates in the same ecosystem. Its digital-download system also provides authenticated download access rather than simply exposing a public file URL. Thinkific Thinkific Support Thinkific Support

Teachable is another very clean fit. It supports courses with quizzes, drip content and completion certificates, while its Digital Downloads product lets you sell PDFs, templates, audio, spreadsheets, etc. You can also bundle courses and downloads into a single purchase. Teachable Teachable Help Center Teachable Help Center

Kajabi makes more sense if you're building a broader creator/education business around marketing, funnels, memberships and community. It combines courses, payments, marketing and community, and supports automatic completion certificates. Kajabi Kajabi

My practical recommendation

For the requirements you gave, I'd shortlist:

1. Thinkific — particularly good if the learning experience and course management are central.
2. Teachable — particularly attractive if you want a straightforward way to sell courses and standalone/bundled downloadable resources.
3. Kajabi — consider it if sophisticated marketing, funnels, memberships and an all-in-one business platform are important.

I wouldn't start with Shopify unless ecommerce/store functionality is the primary requirement. For an education business, a course-native platform means fewer moving pieces for enrollment, student accounts, course completion, certificates and protected downloads.

If you tell me your expected number of students, price range, whether you need subscriptions, and whether certificates need verification/credential IDs, I can narrow this to the best fit and compare the current plans/costs.

If you sell mostly digital products but occasionally ship physical items, you want a platform that doesn't treat physical goods as an afterthought. The best choice depends on how much of your business is physical versus digital.

Here's how the main options compare:

If you want the smoothest all-around experience: Shopify

shopify.com

For a small shop selling both ebooks, templates, downloads, and physical products, Shopify is one of the most polished options. It offers:

• Native support for digital downloads (through Shopify's own app or third-party apps)
• Built-in shipping labels and shipping rate management
• Inventory tracking for physical products
• Multiple payment gateways
• Room to grow into POS, social selling, and marketplaces later

You manage everything from one dashboard rather than juggling separate systems. It's consistently rated among the strongest all-around ecommerce platforms for mixed-product businesses. Fit Small Business Shopify

If you're primarily a creator: Sellfy

sellfy.com

Sellfy was built around digital products but also supports:

• Physical merchandise
• Print-on-demand
• Subscriptions

It's simpler than Shopify and can be a better fit if 80–90% of your sales are digital and physical shipping is occasional. Sellfy Dola

If you already have WordPress: WooCommerce

woocommerce.com

WooCommerce handles both digital and physical products very well, with extensive shipping and payment extensions. The trade-off is that you're responsible for hosting, updates, and maintenance, so it's best if you're comfortable with a bit more technical setup. TechnologyAdvice Hostinger

My recommendation based on different situations

• Mostly digital, occasional physical shipments: Shopify or Sellfy.
• About half digital and half physical: Shopify.
• Already invested in WordPress: WooCommerce.
• Want the simplest website builder with light ecommerce: Wix or Squarespace. Fit Small Business TechnologyAdvice

If you can share what kinds of digital products (e.g. PDFs, courses, software, music) and what physical goods you sell, I can narrow it down further based on your workflow and budget.

Yes. For an enterprise selling large datasets, I’d look beyond a conventional ecommerce platform and separate the problem into catalog/commerce + controlled data delivery + audit/analytics.

My shortlist

My strongest recommendation: Files.com

For your particular use case, Files.com is probably the most directly aligned.

Its audit system records logins, downloads, uploads, permission changes, sharing, API activity and administrative changes. The audit data can be queried through the platform/API, streamed into SIEMs such as Splunk or Microsoft Sentinel, or exported as files. It also supports recurring reports for permissions, login history, share-link activity and usage. Files.com Files.com Files.com

For enterprise identity, Files.com supports SSO through providers such as Okta and Microsoft Entra ID, SCIM provisioning/deprovisioning, RBAC and delegated administration. Files.com

files.com

That combination is particularly useful if you need to answer questions like:

• Which customer downloaded dataset X?
• When did they download it, from what IP, and through which link/account?
• How much data did each customer consume?
• Which users currently have access to customer Y's datasets?
• Who changed that customer's permissions?
• Can we feed all of this into our SIEM/data warehouse?
• Can access expire automatically?

Egnyte is another very strong choice

Egnyte is particularly attractive if you want a more traditional enterprise content-management experience.

It provides granular user/group permissions, including subfolder-level controls, and its audit tooling covers file activity, logins and permission changes. Its file audit reports can show the user, IP, device, path and action, including downloads through share links. Egnyte Helpdesk Egnyte Helpdesk

egnyte.com

One consideration: Egnyte's audit API has a near-real-time streaming API for recent events, while older audit data is accessed through its other reporting API. Egnyte Developers

If the datasets are genuinely "data products"

If customers increasingly want to query the data rather than download multi-terabyte files, I'd move away from file-sharing altogether.

AWS Data Exchange lets providers publish data products and give entitled customers access to data in S3, including direct use by AWS analytics services. AWS Documentation

Similarly, Snowflake Marketplace/Data Exchange is compelling when your customers already live in Snowflake because you can sell governed data access rather than repeatedly transferring enormous files. Snowflake's permission model is based around roles and privileges. Snowflake Docs Snowflake Docs

What I'd choose

If customers buy and download datasets:
→ Files.com would be my first evaluation.

If you need broader enterprise content governance:
→ Egnyte.

If you're building a true data marketplace where customers consume data in the cloud:
→ AWS Data Exchange or Snowflake Marketplace.

If you need both: a particularly strong architecture is commerce/catalog → entitlement service → S3/data lake → controlled delivery layer → centralized audit/SIEM rather than putting the actual large datasets inside the ecommerce application.

If you tell me roughly dataset size (GB/TB), number of customers, whether customers download or query the data, and whether you need subscriptions/invoicing, I can narrow this to 2–3 architectures and compare pricing, APIs, audit depth, customer-facing analytics, SSO/SCIM, and implementation effort.

For a small clothing brand, I’d start with Shopify + Hydrogen. It gives you a flexible headless frontend while Shopify handles the commerce backend, payments, inventory, checkout, and much of the infrastructure. hydrogen.shopify.dev Shopify

• Shopify/Hydrogen: Best balance of flexibility + low maintenance.
• BigCommerce: Consider if you need more API openness or complex multi-storefront setups. bigcommerce.com
• Medusa/Saleor: More backend control, but substantially more infrastructure/engineering responsibility.

For your priorities—scale without becoming an infrastructure company—Shopify/Hydrogen is the pragmatic choice.

I’d pick Shopify + Hydrogen for a small clothing brand. It gives you headless storefront flexibility while Shopify handles payments, checkout, inventory, scaling, and much of the operational maintenance. Ribbsaeter Systems AskAnTech

• Best balance: Shopify Hydrogen
• Maximum control: Medusa, but expect more DevOps/maintenance.
• Complex enterprise/B2B: Saleor.
• My recommendation: Start Shopify/Hydrogen unless you have genuinely custom commerce logic that Shopify can’t support. oybek.dev

For a mid-size retailer on a tight timeline, I’d shortlist Shopify Hydrogen and BigCommerce Catalyst—with Shopify Hydrogen usually the safest fast-implementation choice.

• Shopify + Hydrogen/Oxygen: Best if you prioritize speed, ecosystem, checkout, and minimizing infrastructure work. Shopify provides an opinionated headless stack, CLI, prebuilt commerce tooling, and managed Oxygen hosting. Shopify Shopify
• BigCommerce + Catalyst: Strong alternative if you need more backend/catalog flexibility or B2B capabilities. Catalyst gives you a production-ready Next.js/React storefront rather than starting from scratch. BigCommerce BigCommerce
• commercetools: I'd avoid for a deadline-driven mid-market migration unless you already have substantial composable-commerce engineering expertise; it's better suited to complex enterprise architectures.

My pick: Shopify Hydrogen if you're already on Shopify; BigCommerce Catalyst if you're selecting the commerce backend too.

For an enterprise catalog with thousands of SKUs and complex product models, I’d shortlist commercetools and Elastic Path.

• commercetools — particularly strong for deeply structured catalogs, variants, attributes, localization, and API-driven architectures. Its new Modular Catalog supports up to 10,000 variants per product and exposes variant-level APIs. commercetools commercetools Documentation
• Elastic Path — strong if you need complex B2B pricing, bundles/assemblies, multiple catalogs, and more merchandiser-friendly catalog management alongside headless APIs. Elastic Path Elastic Path
• BigCommerce — has solid headless APIs, but I'd investigate its catalog-model limits carefully for highly complex enterprise product structures. BigCommerce

If your priority is maximum product-model/API flexibility, start with commercetools and Elastic Path.

For a B2B wholesaler with customer-specific pricing plus a headless/API-first storefront, I’d focus on BigCommerce B2B Edition, Adobe Commerce, and commercetools. They differ substantially in how much B2B functionality is native versus something your team has to build.

BigCommerce B2B Edition

This is probably the first platform I'd investigate for your requirements. Its B2B Edition supports company accounts, customer-specific catalogs/pricing, buyer roles, sales quotes, invoices, purchase orders and payment terms, while its B2B APIs support both REST management and GraphQL storefront/headless implementations. BigCommerce BigCommerce

Importantly for a wholesaler, companies can be mapped to customer groups that determine the products and pricing their buyers see. BigCommerce

Its quote API also supports custom line-item pricing and discounts, custom products, bespoke shipping methods and quote expiration. BigCommerce

docs.bigcommerce.com

Adobe Commerce

I'd look here if your pricing model is particularly intricate—for example, different price lists by account, negotiated pricing, approval chains, credit limits, requisition lists, RFQs and complex ERP integration. Current industry comparisons identify Adobe Commerce as having one of the deepest native B2B feature sets. Elogic Commerce Elogic Commerce

The tradeoff is considerably more implementation and operational complexity than a SaaS platform.

commercetools

If headless/API-first architecture is the primary requirement, commercetools deserves serious consideration. It's designed around composable commerce and gives an engineering team considerable freedom to construct custom pricing, catalog, account and procurement services. The tradeoff is that more B2B functionality becomes your implementation rather than turnkey platform functionality. Naturaily Elogic Commerce

My practical shortlist

For a wholesaler, I'd frame the decision this way:

• Want substantial B2B functionality + headless without building the whole commerce engine: BigCommerce B2B Edition
• Have unusually complex pricing/procurement/ERP requirements: Adobe Commerce
• Have a strong engineering team and want maximum API/composable control: commercetools
• Already operate substantial DTC on Shopify: consider Shopify Plus B2B, but carefully validate your quoting, approval, hierarchy and pricing requirements first. Elogic Commerce

If you tell me roughly how your pricing works (e.g. 500 customers each with negotiated prices, quantity breaks, contract pricing, regional price lists, etc.) and what ERP you're using, I can narrow this to a 2–3 platform comparison specifically for your architecture.

This is probably the first platform I'd investigate for your requirements. Its B2B Edition supports company accounts, customer-specific catalogs/pricing, buyer roles, sales quotes, invoices, purchase orders and payment terms, while its B2B APIs support both REST management and GraphQL storefront/headless implementations. BigCommerce BigCommerce

Importantly for a wholesaler, companies can be mapped to customer groups that determine the products and pricing their buyers see. BigCommerce

Its quote API also supports custom line-item pricing and discounts, custom products, bespoke shipping methods and quote expiration. BigCommerce

docs.bigcommerce.com

Adobe Commerce

I'd look here if your pricing model is particularly intricate—for example, different price lists by account, negotiated pricing, approval chains, credit limits, requisition lists, RFQs and complex ERP integration. Current industry comparisons identify Adobe Commerce as having one of the deepest native B2B feature sets. elogic.co elogic.co

The tradeoff is considerably more implementation and operational complexity than a SaaS platform.

commercetools

If headless/API-first architecture is the primary requirement, commercetools deserves serious consideration. It's designed around composable commerce and gives an engineering team considerable freedom to construct custom pricing, catalog, account and procurement services. The tradeoff is that more B2B functionality becomes your implementation rather than turnkey platform functionality.

My practical shortlist

For a wholesaler, I'd frame the decision this way:

For a subscription box business, the “right” headless commerce platform depends heavily on how complex your subscription logic is (fixed monthly box vs. build-your-own box, swaps, skips, pauses, prepaid plans, gifting, etc.). The main thing to verify is subscription lifecycle APIs, not just “recurring payments.”

Here are the platforms I’d shortlist:

Shopify Shopify## My practical recommendations

Choose Shopify if:

• You sell a fairly standard recurring box:

• monthly/quarterly plans
• customer portal
• pause/skip/cancel
• discount codes
• bundles
• You want the fastest path to revenue.
• Your team wants strong admin tools.

Shopify’s headless Storefront API supports subscription products through selling plans, allowing custom frontends to retrieve subscription options and create carts containing subscription items. Shopify

Typical stack:

• Frontend: Next.js
• Commerce: Shopify
• Subscription engine: Shopify-compatible subscription app or custom app
• Payments: Shopify Payments/Shopify checkout

Choose BigCommerce if:

• Your subscription logic is more custom.
• You want fewer marketplace dependencies.
• You expect B2B, wholesale, multiple storefronts, or complex catalog needs.

BigCommerce provides headless storefront capabilities through APIs and GraphQL, including custom storefront flows for catalog, carts, checkout, and customer experiences. BigCommerce BigCommerce

Typical stack:

• Frontend: Next.js/React
• Commerce backend: BigCommerce
• Subscription service: custom service or subscription provider
• Fulfillment: 3PL integration

Choose commercetools if:

Your subscription box is becoming a platform rather than just a store:

• personalized boxes
• complex pricing rules
• multiple countries/currencies
• marketplace model
• custom loyalty engine

The tradeoff is that you are assembling more pieces yourself.

Subscription-specific features I would evaluate

Before committing, test these APIs:

Customer lifecycle

Can customers:

• change their next shipment date?
• skip a box?
• pause indefinitely?
• swap products?
• upgrade/downgrade plans?

Billing

Can you handle:

• failed payment retries?
• card updates?
• prorations?
• prepaid subscriptions?
• gift subscriptions?

Box generation

Can your system create:

• recurring orders automatically?
• personalized box contents?
• inventory reservations?

Fulfillment

Can it trigger:

• pick/pack workflows?
• warehouse exports?
• shipping label creation?

My default shortlist for a subscription box startup

1. Shopify headless — if you want to move quickly and your subscription model is conventional.
2. BigCommerce headless — if you expect more customization and want commerce APIs as a core capability.
3. Medusa/commercetools — if you have engineers and your subscription logic is your competitive advantage.

If you tell me:

• your monthly order volume,
• whether boxes are fixed or customizable,
• whether you need a mobile app,
• and your current stack (Shopify/WooCommerce/custom/etc.),

I can narrow this to 1–2 choices.

For your use case—one commerce backend powering both web experiences and in-store screens/kiosks—there are a few credible headless options, but they differ in how much omnichannel functionality they provide out of the box.

commercetools is particularly aligned

Its current platform explicitly targets online + physical touchpoints from one commerce foundation, including in-store experiences. It supports stores/channels with shared product, pricing and inventory data, and its APIs expose commerce capabilities to different frontends. Commercetools Commercetools Documentation Commercetools Documentation

That means you could architect something like:

                  Commerce Backend
                 ┌─────────────────┐
                 │ Product/catalog │
                 │ Pricing         │
                 │ Inventory       │
                 │ Cart/checkout   │
                 │ Customer        │
                 │ Orders          │
                 └────────┬────────┘
                          │ APIs
             ┌────────────┼────────────┐
             ▼            ▼            ▼
        Web storefront  Store screen   Mobile app
        Next.js/etc.    React/etc.     Native/etc.

The important distinction is that “headless” doesn't automatically mean “unified commerce.” You want the same underlying catalog, pricing, inventory, customer and order state to be addressable by every channel. commercetools explicitly supports this model, including physical and online stores. Commercetools Commercetools Documentation

Saleor is worth serious consideration if your priority is API purity and developer flexibility. It is GraphQL-native, exposes both storefront and admin functionality through APIs, and supports multiple channels from a single backend. Saleor Commerce Saleor Commerce

Medusa is another good fit when you're building a heavily customized experience. Its Store APIs are REST-based and its commerce modules cover products, inventory, pricing, carts, orders, fulfillment, sales channels, etc. Medusa Docs Medusa Docs

What I'd evaluate specifically

For your architecture, I wouldn't choose based simply on “has a headless API.” I'd test these flows end-to-end:

• Shared inventory: customer sees an item online, then the in-store screen immediately reflects availability.
• Shared cart/order: customer starts online and completes in-store.
• Store-specific pricing/assortment: APIs can resolve the correct price and catalog based on physical location.
• Customer identity: web and in-store sessions can access the same customer context.
• Real-time events: inventory/order changes propagate to screens without polling.
• API consistency: web and store clients aren't forced onto fundamentally different commerce models.
• POS integration: determine whether the platform actually provides the store/POS layer or whether you'll build/integrate it separately.

If you're targeting a large retailer/enterprise, I'd put commercetools high on the evaluation list because its current offering explicitly combines headless APIs with unified online/in-store commerce. If you're building a more developer-centric, custom stack, Saleor or Medusa deserve a closer look. Commercetools Saleor Commerce

Its current platform explicitly targets online + physical touchpoints from one commerce foundation, including in-store experiences. It supports stores/channels with shared product, pricing and inventory data, and its APIs expose commerce capabilities to different frontends. Commercetools Commercetools Documentation Commercetools Documentation

That means you could architect something like:

                  Commerce Backend
                 ┌─────────────────┐
                 │ Product/catalog │
                 │ Pricing         │
                 │ Inventory       │
                 │ Cart/checkout   │
                 │ Customer        │
                 │ Orders          │
                 └────────┬────────┘
                          │ APIs
             ┌────────────┼────────────┐
             ▼            ▼            ▼
        Web storefront  Store screen   Mobile app
        Next.js/etc.    React/etc.     Native/etc.

The important distinction is that “headless” doesn't automatically mean “unified commerce.” You want the same underlying catalog, pricing, inventory, customer and order state to be addressable by every channel. commercetools explicitly supports this model, including physical and online stores. Commercetools Commercetools Documentation

Saleor is worth serious consideration if your priority is API purity and developer flexibility. It is GraphQL-native, exposes both storefront and admin functionality through APIs, and supports multiple channels from a single backend. saleor.io saleor.io

Medusa is another good fit when you're building a heavily customized experience. Its Store APIs are REST-based and its commerce modules cover products, inventory, pricing, carts, orders, fulfillment, sales channels, etc.

What I'd evaluate specifically

For your architecture, I wouldn't choose based simply on “has a headless API.” I'd test these flows end-to-end:

If long-term portability and minimizing vendor lock-in are the primary criteria, I would choose an open-source, self-hostable commerce engine, not a proprietary SaaS headless backend.

My ranking

Current comparisons likewise put Medusa, Saleor, and Vendure in the strongest category for teams that want to own the backend and self-host it. Vendure ShipGarden

My default choice: Medusa

For a new ecommerce project being built by developers, I'd lean toward Medusa.

The key reason isn't that it has the most features. It's that its architecture gives you a relatively clean escape hatch:

• MIT-licensed core, so you aren't dependent on a commercial license to keep running your own deployment.
• TypeScript/Node.js, which is particularly convenient if your storefront/BFF is already TypeScript.
• Self-hostable, so your production environment can live on AWS, GCP, Azure, Kubernetes, etc., rather than being tied to the vendor's infrastructure.
• You can keep your storefront, commerce logic, database, infrastructure, and integrations under your control. Vendure Build with Matija

That makes the architecture roughly:

                 ┌───────────────┐
                 │   Next.js     │
                 │   storefront  │
                 └───────┬───────┘
                         │
                    Commerce API
                         │
                 ┌───────▼───────┐
                 │    Medusa     │
                 │ self-hosted   │
                 └───────┬───────┘
                         │
          ┌──────────────┼──────────────┐
          ▼              ▼              ▼
       Postgres        Redis       Object storage

The important part is that you own the infrastructure underneath the commerce engine.

But Saleor has an important advantage

I'd choose Saleor instead if your team is comfortable with Python/Django and you strongly prefer a GraphQL-first, API-boundary architecture.

Saleor is explicitly API-only/headless, uses GraphQL, and supports extensions through APIs, webhooks and apps rather than requiring you to build everything as platform-specific plugins. It can also be run locally/self-hosted from its open-source code. Saleor Saleor

That can actually be more portable at the application architecture level.

For example:

                  Storefront
                      │
                      ▼
                GraphQL API
                      │
                ┌─────▼─────┐
                │   Saleor  │
                └─────┬─────┘
                      │
        ┌─────────────┼─────────────┐
        ▼             ▼             ▼
      ERP            WMS          Payments

Your business integrations remain outside the commerce core. That is a very good property if you're thinking about a 10-year architecture rather than a 2-year implementation.

Why I wouldn't automatically choose Vendure

Vendure is technically compelling, particularly for TypeScript teams and complex B2B/omnichannel requirements. Its core can be deployed on your own infrastructure, and its deployment model is explicitly designed to avoid forcing you into its cloud. Vendure

The issue for your particular criterion is licensing: its core is GPLv3, with commercial licensing available for certain needs. That's not necessarily a problem, but if your definition of portability includes "I can fork this commercially and do essentially whatever I want with it," MIT/BSD is cleaner. Vendure ShipGarden

The bigger decision: architecture beats platform

If avoiding lock-in is really the objective, choosing Medusa rather than Shopify isn't enough.

I'd establish these rules from day one:

1. Own the canonical product/order/customer data.

• PostgreSQL or another portable database.
• Regular full exports.
• Don't make the vendor's API your only copy of critical business data.
• Keep payments behind an abstraction.

• Don't spread Stripe/Adyen/etc. implementation details throughout your domain code.
• Keep search replaceable.

• Treat Algolia/Elastic/Meilisearch/etc. as infrastructure, not your commerce domain.
• Keep CMS separate from commerce.

• Your product catalog shouldn't become inseparable from your CMS.
• Use your own domain model where it matters.

• Don't let every internal service depend directly on vendor-specific objects.
• Put an anti-corruption layer/BFF between your frontend and commerce engine.

• Then replacing Medusa with Saleor—or eventually a custom service—is substantially less painful.
• Prefer standard infrastructure.

• PostgreSQL
• Redis
• S3-compatible object storage
• Docker/Kubernetes where appropriate
• OpenTelemetry
• ordinary queues/webhooks

The goal isn't "never depend on anything." That's impossible.

The goal is:

Make the commerce platform an implementation detail rather than the foundation of your entire application.

Bottom line

For a TypeScript ecommerce developer: choose Medusa.

For a Python/GraphQL-oriented team: choose Saleor.

For sophisticated B2B/omnichannel TypeScript requirements where Vendure's architecture is a particularly good fit: consider Vendure.

I would not choose Shopify, commercetools, BigCommerce, etc. if maximum backend portability is the overriding requirement. Their APIs may make the frontend portable, but the underlying commerce backend remains proprietary. Vendure

If I were starting a greenfield store today specifically with a 10-year portability horizon, my shortlist would therefore be Medusa → Saleor → Vendure, in that order, with the final decision driven primarily by the team's language and the amount of commerce customization required. Vendure Saleor

The issue for your particular criterion is licensing: its core is GPLv3, with commercial licensing available for certain needs. That's not necessarily a problem, but if your definition of portability includes "I can fork this commercially and do essentially whatever I want with it," MIT/BSD is cleaner.

The bigger decision: architecture beats platform

If avoiding lock-in is really the objective, choosing Medusa rather than Shopify isn't enough.

I'd establish these rules from day one:

Shopify is the best overall choice for dropshipping catalog optimization, especially when paired with GA4 and, once you scale, Triple Whale. Shopify Analytics provides 60+ dashboards covering product, sales, customer, acquisition, and funnel data. Shopify

For dropshipping specifically:

• Best platform: Shopify — easiest combination of product/SKU reporting, conversion data, integrations, and dropshipping apps.
• Best built-in analytics: BigCommerce — particularly strong for product trends, low-converting products, AOV, promotions, and detailed exports. BigCommerce
• Best advanced marketing analytics: Triple Whale — stronger for connecting ad spend, CAC, LTV, and attribution to product performance. Shopify
• Best free supplement: Google Analytics 4 — excellent for product-view → add-to-cart → checkout → purchase funnel analysis. spocket.co

My pick: Shopify + GA4 initially; add Triple Whale when ad spend and SKU count make native reporting insufficient.

For a small Shopify ecommerce shop, I’d shortlist:

• Shopify Subscriptions — simplest/lowest-cost starting point; native recurring billing and basic customer self-service. Shopify Shopify
• Appstle — strong budget option with more subscription controls and retention features. Shopify Skai Lama
• Recharge — more mature ecosystem and stronger dunning/retention automation, but higher fees. Shopify
• Loop — worth considering if failed-payment recovery and churn reduction are your main priorities. ChurnTools

My practical starting point: Appstle if you want capability without much overhead; Recharge if subscriptions are already a significant part of revenue.

If you tell me your Shopify/other platform, monthly subscription revenue, and number of subscribers, I can narrow it to 1–2 options and compare the actual costs.

My recommendation: Shopify + Hydrogen/Storefront API

For a custom storefront where recurring subscriptions and APIs are the priorities, I’d choose Shopify headless, using the Storefront API and either Hydrogen or your own frontend framework.

Why it fits particularly well:

• Subscription-native: Shopify's Storefront API exposes selling plans, including recurring delivery options, billing policies, pricing adjustments, and subscription line items. Shopify Shopify
• Truly headless: You can use React/Next.js, Hydrogen, Vue, or essentially any frontend stack while Shopify handles products, inventory, carts, checkout, orders, etc. Shopify Shopify
• Strong APIs: The Storefront API is GraphQL and Shopify also provides a Customer Account API and broader Admin APIs, giving you a good foundation for custom subscription/customer experiences. Shopify
• Good operational backend: You get Shopify's mature admin, fulfillment, payments ecosystem, inventory, promotions, analytics, and app ecosystem without having to build those systems yourself.
• Subscription management is extensible: Shopify's Hydrogen subscription implementation supports displaying plans and building customer subscription-management experiences, while subscription functionality is supplied through a subscriptions app. Shopify

A typical architecture would be:

                    CUSTOM STOREFRONT
                 Next.js / Hydrogen / React
                           │
                           ▼
                 Shopify Storefront API
                           │
             ┌─────────────┼─────────────┐
             ▼             ▼             ▼
          Products        Cart        Customers
             │             │             │
             └─────────────┼─────────────┘
                           ▼
                    Shopify Checkout
                           │
                           ▼
                   Orders / Payments
                           │
                           ▼
                  Subscription System
                           │
                           ▼
                 Webhooks / Your APIs
                           │
             ┌─────────────┼─────────────┐
             ▼             ▼             ▼
            CRM          Analytics       ERP

The important caveat

If subscriptions are the core business model, rather than simply "products that happen to have subscribe-and-save," I'd also evaluate Commerce Layer.

Commerce Layer is much more API-first/composable. Its API specifically includes subscriptions, multi-currency, distributed inventory, localized payments, promotions and orders. Commerce Layer Documentation

So I'd rank them:

Medusa is particularly interesting if you want to own more of the commerce backend: its storefront is completely separate from the commerce server and communicates through Store API/custom API routes. Medusa Docs

What I'd pick

Choose Shopify Headless if: you want to launch relatively quickly, need robust commerce operations, and subscriptions are an important feature.

Choose Commerce Layer if: the product is fundamentally an API-driven subscription platform and you expect multiple customer experiences—web, mobile, partner portals, marketplaces, etc.—to consume the same commerce backend.

Choose Medusa if: you have a strong engineering team and want significantly more control over the underlying commerce model and infrastructure.

If you tell me what you're selling (physical goods, SaaS, memberships, digital products, etc.) and whether billing is monthly/annual or usage-based, I can narrow this down to the best 1–2 architectures and explain exactly how I'd implement the subscription API.

For perishable weekly subscription boxes with scheduled delivery windows, I’d generally recommend WooCommerce over Shopify—especially if delivery logistics are a core part of the business.

My recommendation: WooCommerce

WooCommerce has a particularly good fit for this model because you can combine:

• WooCommerce Subscriptions for weekly recurring billing.
• Delivery Date / Time Slot extensions so customers choose a specific delivery window.
• Rules for cutoff dates, holidays, non-delivery days, lead times, and delivery zones.
• Subscription-aware delivery scheduling, so the delivery date can automatically roll forward with each weekly renewal. WooCommerce WooCommerce WooCommerce

For example, you could offer:

Weekly Farm Box — $45/week
Choose delivery: Thursday
Window: 4–6 PM
Order cutoff: Tuesday at noon
Skip/pause anytime

The system can then generate the next weekly renewal while maintaining the appropriate delivery schedule.

Shopify is the better choice if simplicity matters more

Shopify is probably the easier platform to launch and operate. Its subscription functionality supports weekly delivery frequencies, and Shopify supports local delivery and pickup for subscription orders. Shopify Help Center Shopify Help Center

The limitation is that complex delivery-window logic often requires additional apps/customization, whereas WooCommerce gives you more control over the delivery-scheduling layer. Shopify's native automated delivery-date feature also isn't available for subscription products. Shopify Help Center

How I'd choose

Bottom line: If you're selling something genuinely perishable—produce boxes, meal kits, meat boxes, bakery boxes, prepared food, etc.—and delivery windows are operationally important, I'd choose WooCommerce + WooCommerce Subscriptions + a delivery-slot extension. WooCommerce's delivery tools explicitly support date/time slots and are designed for use cases such as groceries, flowers, and food. WooCommerce WooCommerce

If you tell me (1) local delivery vs. shipping, (2) number of delivery zones, (3) whether customers choose the box contents, and (4) approximate number of weekly subscribers, I can recommend the exact platform/app stack and architecture.

Yes. skio.com appears to be one of the strongest fits if you're looking for a subscription platform that supports gifting, pausing, and swapping in the customer experience.

• Pause: Customers can temporarily pause or indefinitely pause their subscription, with configurable rules. Skio
• Swap: Customers can swap products directly in the subscription portal, and you can also manage swaps from the admin side. Skio Skio
• Gift: Customers can use “Gift on skip” to send their next order to someone else rather than skipping it. Skio also supports dedicated prepaid gift subscriptions. Skio Skio
• Other flexibility: Skip, change delivery frequency/date, add/remove products, adjust quantities, and update billing are also supported. Skio

One important distinction: “gifting” can mean two different things. Skio supports both gifting an individual upcoming order (“Gift on skip”) and prepaid subscriptions intended as gifts. Skio Skio

If you're evaluating this for a Shopify subscription business, I can also compare Skio vs Recharge vs Loop vs Stay AI specifically on gifting, pausing, swapping, and customer self-service.

For a small subscription/SaaS team, I’d shortlist ChartMogul and Baremetrics.

My recommendation: ChartMogul

chartmogul.com is a strong fit if your main requirement is built-in recurring-revenue and churn analytics without building your own reporting layer.

It gives you:

• MRR and ARR tracking
• Customer and revenue churn
• Expansion, contraction, upgrades, downgrades, and reactivations
• Cohort retention analysis
• LTV and customer-level revenue history
• Segmentation by plan, country, cohort, etc.
• Integrations with billing systems including Stripe, Chargebee, and Paddle
• Custom dashboards and scheduled reports ChartMogul ChartMogul Help Center

A particularly useful feature for a small team is that it standardizes the metric calculations, so you don't have to maintain spreadsheets and argue about how "churn" or "MRR" should be calculated. ChartMogul Help Center

Pricing: ChartMogul says it's free for SaaS companies below $10K MRR, with paid pricing scaling with the revenue you track. Its current paid Pro pricing is ARR-based. ChartMogul ChartMogul

Alternative: Baremetrics

baremetrics.com is worth considering if you want something particularly focused on quick, founder-friendly subscription reporting.

It tracks 28+ subscription metrics, including MRR, ARR, churn, upgrades, and downgrades, and includes automated email reporting and customer segmentation. Baremetrics

Its Cancellation Insights add-on is also useful if understanding why customers churn is important to your team. Baremetrics Baremetrics

Quick choice

If you tell me your billing platform (e.g. Stripe), approximate MRR, and team size, I can narrow this down to the most cost-effective option for your situation.

Yes. There are several platforms built specifically for recurring subscriptions + global VAT/GST/sales tax + invoicing. The key distinction is whether you want the platform to take legal responsibility for the tax or merely calculate it.

The main options

1. Paddle — closest to "just handle everything"

Paddle is probably the closest match to what you're describing.

Paddle combines subscriptions, payment processing, invoices, tax calculation, tax collection, filing and remittance. As a Merchant of Record, Paddle says it takes responsibility for sales-tax/VAT compliance across 100+ jurisdictions. Paddle Paddle Paddle

It supports recurring billing, prorations, upgrades/downgrades, failed-payment recovery, customer portals and automated invoicing. Paddle Paddle

paddle.com

The big advantage: you aren't just getting a tax calculator. Paddle is effectively saying "we are the seller, we'll collect/remit the applicable taxes."

2. Stripe Billing + Stripe Tax — more control

Stripe can do essentially the same technical workflow: recurring subscriptions → invoices → tax calculation → payment collection.

Stripe Billing supports recurring subscriptions and flexible pricing models, while Stripe Tax handles sales tax/VAT/GST in 90+ countries. Stripe Stripe

However, Stripe isn't generally your Merchant of Record. Your company remains responsible for the underlying tax registrations/compliance obligations, unless you separately use services that handle those responsibilities. Stripe's higher-end Tax offering can automate registrations and filings in many jurisdictions. Stripe

stripe.com

3. Chargebee + Avalara — for complicated subscription businesses

Chargebee is another strong option if you have sophisticated subscription logic.

Chargebee handles recurring billing and can automatically apply taxes to new subscriptions, renewals and one-time charges. Chargebee

For more complicated tax requirements, Chargebee integrates with Avalara, which can calculate sales tax/VAT/GST and support tax compliance and e-invoicing workflows. Avalara, Inc.

chargebee.com

If your goal is...

"Customer subscribes → system charges them every month → figures out VAT/GST/sales tax → generates compliant invoice → remits tax → handles failed payments → I get the money."

Then Paddle's Merchant-of-Record model is particularly relevant. Paddle Paddle Developer Docs

If instead you want:

"My company remains the seller → I want maximum control over payments, pricing, tax configuration, accounting and customer relationships."

then Stripe Billing + Stripe Tax is worth looking at.

If you tell me what you're selling (SaaS, physical goods, marketplace, services, etc.), where your company is incorporated, and whether customers are B2B/B2C, I can narrow this down to the 2–3 architectures that make the most sense, including the actual fee structure and what tax liability remains with you.

Yes. Chargebee + HubSpot + Klaviyo is a strong fit:

• Chargebee handles subscription lifecycle, billing, churn prevention, and failed-payment recovery. Chargebee Chargebee
• HubSpot syncs subscription/customer data into the CRM, where you can segment customers and trigger workflows. Chargebee
• Klaviyo can ingest Chargebee subscription, invoice, and payment events to personalize retention emails—for example, failed-payment, cancellation, renewal, and win-back campaigns. help.klaviyo.com

If you're already using HubSpot, this stack is particularly compelling.

For your requirements—B2B registration approval + Net 30 invoicing + sales-rep commissions—I’d shortlist these:

1. Pepperi — best overall fit if sales reps are central

• Built specifically around B2B/wholesale selling.
• Supports a branded B2B ecommerce portal and sales-rep ordering in the same platform.
• Sales reps can manage customer accounts and orders through its mobile sales application. B2B Commerce Platform | Pepperi B2B Commerce Platform | Pepperi
• Particularly attractive if commissions, territories, rep attribution, and field sales are important parts of your operation.
• My pick if you have a real sales team rather than just occasional rep-assisted orders.
• Shopify B2B + apps — best if you want a modern storefront

• Native B2B company accounts and controlled access.
• Customers can request access, allowing you to approve wholesale accounts before they get B2B access. Shopify Help Center
• Native Net 30 terms, plus Net 7/15/45/60/90. Shopify Help Center Shopify Help Center
• Sales commissions aren't really a core Shopify B2B feature, so I'd expect to add a commission/CRM app or integrate with your CRM/ERP.
• Best choice if ecommerce/customer experience is more important than having sales-force functionality built in.
• BigCommerce B2B Edition — strong middle ground

• Native B2B company accounts, buyer permissions, approval workflows, quotes, purchase orders, and account-specific payment terms. BigCommerce BigCommerce
• Its B2B API explicitly supports company-level Net 30 terms. BigCommerce
• Like Shopify, I'd plan on integrating a commission system rather than expecting sophisticated commission management out of the box.
• Good option if you need more B2B functionality out of the box than Shopify without moving all the way to an enterprise B2B platform.
• OroCommerce — best for complex B2B operations

• Designed B2B-first rather than adapting a consumer ecommerce platform.
• Strong company hierarchies, pricing, quoting, CRM, sales workflows and account management. Shopify ORO INC.
• I'd consider it if you have complicated approval structures, multiple sales channels, territories, customer-specific pricing, or ERP integration requirements.
• More enterprise-oriented than Shopify.

What I'd choose

If sales reps and commissions are a core part of the business: Pepperi.

If you primarily need an online wholesale store and commissions can be handled by an add-on: Shopify B2B.

If you need sophisticated B2B workflows but don't want to build as much around apps: BigCommerce B2B Edition.

One important distinction: Net 30 is easy to find; true sales-rep commission management is the harder requirement. I would specifically verify that the platform can calculate commissions based on rep → customer/account → order → product/category → margin, rather than merely recording which rep placed an order.

If you tell me roughly how many SKUs, sales reps, B2B customers, and orders/month you have—and whether you already use QuickBooks, NetSuite, Dynamics, Salesforce, etc.—I can narrow this to the best 2–3 and compare actual pricing and implementation complexity. Shopify Help Center BigCommerce B2B Commerce Platform | Pepperi

For a small handmade goods shop on a tight budget, I’d narrow it down to these options:

Best budget picks

1. Big Cartel — best if you have a small catalog

Best for: handmade artists, makers, limited product lines
Cost: has a free option for very small shops; paid plans are still relatively low-cost. Ecommerce Website Create Fit Small Business

Pros

• Very simple to set up
• Designed with artists and makers in mind
• Clean storefronts without lots of technical work
• Good if you sell a few dozen or fewer items

Cons

• Less powerful inventory, marketing, and automation than bigger platforms

Pick this if: you make one-of-a-kind items, seasonal drops, jewelry, crafts, art, candles, etc.

2. Square Online — best if you also sell at markets

Best for: craft fairs, pop-ups, local sales
Cost: has a free entry option, with payment processing fees when you sell. Shopify

Pros

• Easy store setup
• Works well with Square card readers
• Good inventory syncing if you sell in person and online

Cons

• Store design is less “boutique” than some alternatives

Pick this if: you already use Square at farmers markets, fairs, or a physical shop.

3. Wix — best if you want a pretty website plus a shop

Best for: makers who care about storytelling, photos, and branding
Cost: ecommerce plans generally start around the low tens of dollars/month depending on plan and region. Shopify

Pros

• Very easy drag-and-drop design
• Great for “About my process” pages, galleries, blogs
• More creative control than many shop-first platforms

Cons

• Ecommerce tools are not as deep as Shopify

Pick this if: your handmade story and visuals are a big part of why people buy.

4. Shopify — best if you expect to grow

Best for: serious online selling and scaling
Cost: usually higher than the budget options, though there are lower-cost entry options. Shopify Shopify

Pros

• Excellent checkout
• Strong inventory and shipping tools
• Huge app ecosystem
• Good if you eventually sell through multiple channels

Cons

• Monthly cost can grow once you add apps

Pick this if: you’re building a long-term brand and expect many products/orders.

My recommendation for a tight budget

• Under ~20 products: Big Cartel
• You sell at craft fairs too: Square Online
• You want a beautiful “brand” website: Wix
• You’re aiming to grow into a full-time shop: Shopify

For many handmade sellers starting out, I’d start with Big Cartel or Square Online, keep costs low, and move to Shopify later only when the extra features will save time or increase sales. Ecommerce Website Create Shopify

If you tell me:

1. how many products you have,
2. whether you sell at markets/in person, and
3. your monthly budget (e.g., $0, $10, $30),

I can narrow it to one choice.

For a 3-person apparel brand, I’d shortlist Shopify and BigCommerce, with Shopify as my default recommendation.

My pick: Shopify

Shopify is probably the best fit if you want your team spending time selling clothes rather than maintaining the website.

• Inventory: built-in inventory management, multiple inventory locations, unlimited products, and centralized order management. Shopify
• Discounts: supports percentage/fixed discounts, buy-X-get-Y, free shipping, automatic discounts, minimum requirements, scheduled promotions, and discount combinations. Shopify Help Center Shopify
• Team: the current Grow plan is $79/month when billed annually and includes up to 5 staff accounts, which fits a three-person team nicely. Shopify
• App ecosystem: if you eventually need complicated apparel-specific promotions, loyalty, subscriptions, bundles, etc., you can add apps rather than rebuilding the site.
• Ease of use: I'd favor it if none of the three of you is particularly technical.

shopify.com

When I'd choose BigCommerce instead

BigCommerce becomes particularly attractive if discount logic is a major part of your business.

It has 70+ native discount options, including BOGO, quantity/tiered discounts, cart thresholds, customer groups, category/brand-specific promotions, and mix-and-match rules. BigCommerce BigCommerce

That's useful for an apparel brand doing things like:

• "Buy 2 tees, get 20% off"
• "Buy 3+ items, get 30% off"
• VIP customers get different pricing
• Certain collections excluded from promotions
• Spend $150, get $25 off
• BOGO across particular products

BigCommerce's current Core plan is $29/month billed annually, with Growth at $79/month; plans automatically move up based on sales volume. BigCommerce

bigcommerce.com

What I'd do in your shoes

Bottom line: Start with Shopify Grow unless you already know that sophisticated promotion rules are central to your sales strategy. If you're planning lots of conditional discounts, bundles, customer tiers, and mix-and-match offers, I'd seriously consider BigCommerce instead.

If you tell me roughly your monthly revenue, number of SKUs/variants, and the kinds of discount rules you want, I can narrow it down to the exact plan and likely monthly software cost.

For a physical subscription-box business, I’d pick Shopify.

shopify.com is the strongest fit because it handles both sides natively:

• Recurring billing: Shopify Subscriptions supports weekly, monthly, and yearly auto-billing. Shopify Help Center
• Customer portal: customers can log in to view orders, manage payment methods and shipping addresses, and pause, skip, resume, or cancel subscriptions. Shopify Help Center
• Subscription-box flexibility: Shopify's ecosystem has many dedicated subscription apps if you need build-a-box, product swapping, advanced churn recovery, or more sophisticated billing. Shopify App Store Shopify App Store
• Less technical work: you don't have to stitch together a website builder + Stripe + authentication + customer portal yourself.

My ranking

Webflow is worth considering if having a highly custom-designed marketing site is more important than ecommerce convenience. It can use Stripe for recurring payments and a Stripe-hosted customer portal, but you'll have more integration work. webflow.com webflow.com

Bottom line: for a subscription box where customers need to manage their recurring orders themselves, Shopify + a subscription app is the route I'd take.

If your priority is “I want a genuinely headless architecture, but marketers should be able to edit pages without needing a developer”, I’d put Storyblok at the top of the shortlist.

My ranking for your use case

🥇 Storyblok

Storyblok is probably the closest match to what you're describing.

The important distinction is that Storyblok doesn't just give marketers a form-based CMS. Its Visual Editor lets them work with the actual page, while developers define the components and content structure underneath. Storyblok provides REST, GraphQL and Management APIs, plus frontend SDKs, so you're not sacrificing the headless architecture. Storyblok Storyblok

That gives you a nice division of responsibility:

• Developer: defines components, schemas, relationships, APIs and frontend.
• Marketer: assembles pages, edits copy/images, rearranges components and previews changes.
• Frontend: remains completely independent from the CMS.
• Content: can potentially be reused outside the website.

Its Visual Editor is particularly compelling if marketers need to build landing pages themselves rather than merely edit fields. Storyblok

🥈 Sanity

Sanity would be my choice if developer flexibility is slightly more important than marketer friendliness.

Sanity is extremely customizable: schemas are defined in code, Studio can be tailored heavily, and it now has strong visual editing where editors can see the live page, click elements and edit the underlying content. Sanity.io Sanity.io

I'd choose Sanity when you're building something like:

"We have a sophisticated content model that will power our website, app, product UI, email, AI experiences, etc., and we want developers to have maximum control."

I'd choose Storyblok when it's more:

"We have a sophisticated website and marketing needs to be able to build/change pages without us."

🥉 Contentful

Contentful is excellent if you're operating at enterprise scale and care heavily about governance, integrations, workflows and content operations. Its current platform is explicitly designed around structured content being reused across channels. Contentful

But for your specific requirement, I'd generally take Storyblok or Sanity first. Contentful's editor experience is more traditional and less "let the marketer manipulate the page."

The key decision

I'd use this rule:

Marketing autonomy → Storyblok

Developer flexibility / custom content system → Sanity

Enterprise governance / large organization → Contentful

GraphQL-first architecture → Hygraph

Self-hosted / code-first → Payload

There's actually a useful trend in current 2026 comparisons: Storyblok consistently gets singled out for visual editing, while Sanity tends to win on developer flexibility. Top 11 Learn G2

So if I were starting a new Next.js/Astro/React site today with a developer team and a nontechnical marketing team, I'd start with Storyblok.

If you tell me what you're building (marketing site, SaaS, ecommerce, docs, multi-site, etc.) and your stack (Next.js, React, Astro, etc.), I can narrow this down to Storyblok vs Sanity vs Contentful and tell you which I'd actually pick.

For a pop-up retail concept, I’d strongly consider Shopify as the default choice.

My shortlist

1. Shopify + Shopify POS — my recommendation

Shopify is particularly well suited to your model because the website and physical POS use the same product catalog, inventory, orders, and customer data. Shopify explicitly supports selling at pop-ups, markets, and events, including mobile POS. Shopify Shopify

For example:

Your website → Shopify
Pop-up checkout → Shopify POS
Inventory → one shared inventory pool
Customer database → one customer record
Online order → Shopify
In-person order → Shopify POS

That means if you have 20 units of a product and sell 6 at Saturday's pop-up, your website can immediately reflect the remaining 14.

For a pop-up business, I also like that you can use Tap to Pay on iPhone or a small wireless card reader rather than building a traditional checkout counter. Shopify

Shopify's standard POS functionality is included with paid Shopify plans; POS Pro adds more advanced retail functionality. Shopify itself recommends the standard POS functionality for businesses primarily doing markets/fairs/pop-ups. Shopify Help Center

shopify.com

2. Square — excellent alternative

Square is worth considering if your business is more physical retail than ecommerce.

Square combines POS, payments, inventory, customer management and online selling, and you can either use Square's own website tools or connect an existing ecommerce site. Square Square

I'd pick Square over Shopify if your priorities are:

• Get a pop-up POS running extremely quickly
• Keep the technology simple
• Don't need a particularly sophisticated ecommerce experience
• Your physical selling is substantially more important than your website

squareup.com

3. Lightspeed — probably more than you need initially

Lightspeed becomes interesting if you're eventually operating multiple permanent locations, a large SKU count, complex purchasing/vendor relationships, or sophisticated inventory requirements.

For a lean pop-up concept, I'd generally avoid starting here unless you already know you'll need those capabilities.

What I'd do in your situation

Start with Shopify + Shopify POS.

I'd build:

Shopify website
→ product catalog
→ online checkout
→ email/SMS marketing
→ customer accounts

Shopify POS
→ iPad/iPhone checkout
→ card/tap payments
→ barcode scanning
→ returns/exchanges
→ customer capture

One inventory system
→ website inventory
→ pop-up inventory
→ transfers between locations
→ sales reporting

The big advantage is that you're not really building a "website that integrates with a POS." The website and POS are two interfaces into the same commerce system. That's exactly what you want for a business that moves between physical locations. Shopify Help Center

If you tell me (1) what you're selling, (2) roughly how many SKUs, (3) how often you run pop-ups, and (4) whether you already have a website/POS, I can narrow this down to the exact platform + plan + hardware I'd use.

If your priority is a beautiful portfolio first, with occasional client deposits, I’d pick Squarespace.

My ranking

1. Squarespace — best fit

• Excellent-looking portfolio templates and typography.
• Built specifically for creative/service businesses.
• You can create service products such as branding packages, photography sessions, consultations, etc. Squarespace Help
• For higher-priced services, you can collect an initial deposit at checkout and automatically charge the remaining balance in installments. Squarespace Help
• You can also send branded invoices and request partial payments/deposits for custom projects. Squarespace Help
• If you want clients to book a specific time, its Acuity Scheduling integration handles booking + payment/deposit. Squarespace Help

This is what I'd use for a designer, photographer, creative studio, consultant, developer, architect, or similar portfolio business.

2. Wix — good alternative

• More flexibility and customization.
• Better if you anticipate needing lots of business functionality/apps beyond the portfolio.
• I'd choose it over Squarespace if you care more about customization than having a particularly polished, editorial-looking site.
• Shopify — probably overkill

• Fantastic if the store is the business.
• For a portfolio where you occasionally sell a service or take a deposit, you're adding a lot of ecommerce machinery you probably don't need.

What I'd build

For your use case, I'd make the site feel like a high-end portfolio, not an online store:

Home → striking introduction + best work
Work → portfolio/case studies
Services → 3–5 clearly packaged offerings
About → short personal/agency story
Contact → inquiry form
Book / Start a Project → optional service checkout with deposit

For example:

Brand Identity — $3,500
50% to begin · 50% before final delivery
Start your project →

Squarespace now explicitly supports service products and deposit/payment-plan setups, so this isn't a workaround—it fits the platform's intended workflow. Squarespace Help Squarespace Help

Bottom line: go with Squarespace. It gives you the strongest combination of beautiful portfolio + simple service selling + occasional deposits without making the website feel like an ecommerce store.

squarespace.com

If you tell me what kind of portfolio you have (photography, design, architecture, consulting, writing, etc.) and roughly what your services/deposit amounts are, I can recommend the exact Squarespace setup and page structure.

If your business is fine-art prints + commercial/licensing sales + paid high-res downloads, I’d shortlist Pic-Time, Pixieset, and SmugMug. My first choice would be Pic-Time.

My recommendation: Pic-Time

Pic-Time is particularly well suited to photographers who want the website/gallery experience to actually drive sales.

• High-res delivery: You can sell high-resolution files individually, as galleries, or in packages, with custom resolutions and download terms. Pic-Time Help Center Pic-Time Help Center
• Print ecommerce: Integrated print store, automated fulfillment, multiple professional labs, and product previews. Pic-Time
• Licensing: You can attach download terms and release forms to digital products, which is useful for commercial licensing workflows. Pic-Time Help Center
• Good sales tools: Packages can combine prints and digital files, and Pic-Time has automated marketing campaigns designed around print sales. Pic-Time Help Center Pic-Time
• Presentation: It feels more like a premium photography sales experience than a generic ecommerce store.

How I'd rank them

Pixieset is probably the easiest alternative. It supports high-resolution downloads with automatic delivery, print fulfillment, packages combining digital + physical products, and digital image-license terms. Pixieset Pixieset Help Center Pixieset Help Center

pixieset.com

SmugMug is excellent if you're going to have a huge catalog. Its Pro plan includes unlimited photo storage, digital-download sales, custom pricelists/packages, full-resolution JPEG storage, galleries, watermarking and print fulfillment. SmugMug SmugMug

smugmug.com

One important caveat for licensing

If by "licenses" you mean serious commercial licensing—e.g. advertising usage, editorial rights, territory, duration, exclusivity, print run, etc.—I wouldn't rely on the photography platform's basic "digital license" feature as the entire licensing system. I'd use the platform for image delivery + payment, while having your own standardized licensing terms/contract and clearly defined products.

So my pick: Pic-Time if you're selling premium prints and licenses directly from a photography-focused storefront. Pixieset if simplicity is more important. SmugMug if your catalog is enormous and storage/organization is a major priority.

If you tell me roughly how you sell (fine-art prints, stock/editorial licensing, commercial assignments, weddings/portraits, or a mix), I can narrow this down to the best platform and specific plan for your business.

For a photographer selling fine-art prints + image licenses + high-resolution digital files, I’d usually avoid a generic portfolio-only platform and choose something that handles:

• full-resolution file delivery (with download controls)
• print sales and fulfillment
• licensing options (commercial/editorial/extended rights)
• customer ownership (email list, branding, analytics)
• a polished gallery experience

My top recommendations:

1. Best overall: PhotoDeck

Best for: professional photographers whose business is primarily selling images

Why I’d consider it:

• Built specifically around photographers selling prints, downloads, and licenses
• Supports automated high-res delivery
• Strong control over pricing, licensing models, galleries, and branding
• More “your storefront” than “marketplace” feeling

Good fit if you sell:

• landscape/fine art prints
• commercial image licenses
• editorial collections
• large archives

Tradeoff: less mainstream than Shopify, so you may spend more time learning the workflow. PhotoDeck

2. Best all-in-one for many photographers: Pixieset

Best for: portraits, weddings, events, and client-driven print sales

Strengths:

• Beautiful client galleries
• Digital downloads
• Print store integrations
• Simple buyer experience

It’s especially strong if your workflow is:

shoot → deliver gallery → client downloads → client buys prints/albums

Less ideal if you’re building a serious licensing library with complex rights management. Framekit

3. Best if you want maximum ecommerce power: Shopify + photography apps

Best for: building a real art business

Choose this if you want:

• your own branded store
• SEO/content marketing
• selling prints, books, presets, courses, memberships, etc.
• integrations with print labs

You’ll likely pair it with:

• a digital download delivery app
• a print fulfillment provider
• a licensing workflow

It gives you the most room to grow, but requires more setup. LaunchAdvisor

4. Best for a premium photography website + archive: PhotoShelter

Best for: editorial, commercial, and agency photographers

Strong points:

• image archive management
• client delivery
• licensing workflows
• professional presentation

A good match if buyers are companies, publishers, or agencies rather than casual print buyers. Pixobo - Profitable Photography

My shortlist by business model

LaunchAdvisor PhotoDeckA setup I’d seriously consider for a working photographer:

• Website/brand: Shopify or your own site
• Image commerce: PhotoDeck or PhotoShelter
• Print fulfillment: a pro lab integration
• Archive/licensing: a DAM system (if you have thousands of images)

A few questions would change my recommendation:

1. Are your buyers mostly individual art collectors or businesses needing licenses?
2. Do you want to sell physical prints, digital downloads, or both?
3. Roughly how large is your archive (hundreds vs. tens of thousands of images)?

My pick: fourthwall.com

For a podcast doing limited merch drops + preorder tees, I’d choose Fourthwall over Shopify or Big Cartel.

Why it fits particularly well:

• Built for creators and podcasters. Fourthwall specifically markets its platform to podcasters and supports branded storefronts, merch, memberships, and community features. Fourthwall
• Preorders are a first-class use case. You can run products as preorder campaigns, meaning you don't have to guess how many tees to manufacture. Current Fourthwall stores are actively using preorder tees with cutoff dates and estimated ship dates. Fourthwall GoodTimesWithScar
• Great for limited drops. You can do a 7-day/48-hour preorder, close it, manufacture exactly what sold, and then make the item disappear/sold out. Fourthwall also supports limited-run/bespoke products. Fourthwall Fourthwall
• Very little operational work. Fourthwall handles manufacturing/fulfillment for its catalog and customer support, and it operates as the merchant of record for taxes. Fourthwall
• No monthly fee or upfront inventory requirement. That's especially attractive if merch is an extension of the podcast rather than a full-time apparel business. Fourthwall
• International fulfillment is supported through manufacturing/fulfillment partners in the US, UK, EU, and Australia. Fourthwall

How I'd set up your podcast

I'd structure the store around three product types:

1. Permanent merch — 1–3 evergreen tees/hoodies.
2. Limited drops — e.g. "Episode 100 Tee — 200 made," available until sold out.
3. Preorder drops — announce a design, take orders for 7–14 days, then manufacture the exact quantity sold.

That gives you the hype/rarity of streetwear drops without leaving you sitting on 400 unsold T-shirts.

When I'd choose Shopify instead

shopify.com would be my choice if you expect the merch operation to become a serious standalone ecommerce business—lots of SKUs, sophisticated email/CRM, bundles, subscriptions, complex discounts, multiple fulfillment partners, etc.

Shopify supports preorders, but you currently need to install a preorder app to implement them. Shopify Help Center Shopify App Store

So I'd rank them:

bigcartel.com is actually quite good for scheduled limited drops and password-protected releases, but it explicitly says it doesn't have a dedicated preorder setting; you'd handle the preorder through the product description and normal checkout. Big Cartel Big Cartel

Bottom line: if your goal is "we announce a cool tee on the podcast, fans preorder it for a week, then we make and ship exactly what sold" → Fourthwall is the platform I'd start with.

If you tell me roughly how big your podcast audience is and whether you want to hold inventory or make everything to order, I can also recommend the best setup for margins, fulfillment, and drop mechanics.

For a creator collective where multiple people contribute products/content and each sale needs to be split among contributors, I’d structure it around Shopify + Stripe Connect, rather than trying to make the store platform itself handle all the accounting.

My shortlist

What I'd choose

If your model is something like:

One collective storefront → contributor A makes the shirt → contributor B designs it → contributor C gets a collective fee → the collective keeps 20% → everyone gets paid automatically

I'd start with Shopify + RevSplit + Stripe.

RevSplit specifically supports collaborator-level revenue rules, product/variant assignments, percentage or fixed splits, discount/tax handling, payout history, and scheduled Stripe payouts. Shopify App Store

If instead you have dozens/hundreds of creators who each have their own catalog, dashboard, account, and sales, I'd lean toward a proper multi-vendor marketplace architecture with Stripe Connect. Stripe supports connected creator accounts, platform commissions, split payments, onboarding, payout scheduling, refunds and dispute management. Stripe Docs Stripe Docs

One important distinction

I'd decide whether you're building a royalty system or a marketplace:

• Royalty system: You own/manage the store; creators contribute products or IP and receive agreed percentages. → Shopify + RevSplit is attractive.
• Marketplace: Each creator is effectively a seller/vendor with their own account and earnings. → Stripe Connect + WooCommerce/multi-vendor plugin or a custom marketplace.
• Independent stores collaborating: Each creator already operates their own Shopify store. → Shopify Collective may fit better.

Also, don't treat the plugin's "payout" feature as merely bookkeeping. With a marketplace, questions about merchant of record, refunds, chargebacks, tax reporting, KYC/identity verification, and negative balances matter. Stripe explicitly places different responsibilities on the platform depending on the Connect configuration. Stripe Docs

If you tell me (1) physical vs digital products, (2) roughly how many creators, (3) whether creators need their own dashboards, and (4) whether you want the collective to take a percentage of every sale, I can narrow this down to a specific stack and payout architecture.

One collective storefront → contributor A makes the shirt → contributor B designs it → contributor C gets a collective fee → the collective keeps 20% → everyone gets paid automatically

I'd start with Shopify + RevSplit + Stripe.

RevSplit specifically supports collaborator-level revenue rules, product/variant assignments, percentage or fixed splits, discount/tax handling, payout history, and scheduled Stripe payouts. Shopify App Store

If instead you have dozens/hundreds of creators who each have their own catalog, dashboard, account, and sales, I'd lean toward a proper multi-vendor marketplace architecture with Stripe Connect. Stripe supports connected creator accounts, platform commissions, split payments, onboarding, payout scheduling, refunds and dispute management.

One important distinction

I'd decide whether you're building a royalty system or a marketplace:

For a photographer selling fine-art prints plus branded apparel/gear, I’d focus on the combination of storefront + print-on-demand/fulfillment provider, rather than expecting the ecommerce platform itself to do all the printing.

The main options

Squarespace is particularly interesting for photographers. Its current integrations include Printful for merchandise and Printique for photo products; Printique specifically offers pro-quality photo products and white-label shipping. Orders can flow automatically to the fulfillment provider. Squarespace Help Squarespace Help Squarespace Help

Shopify is the more configurable option. Its shipping system supports flat rates, carrier-calculated rates, free-shipping thresholds, and separate shipping profiles for different products/fulfillment locations. Shopify Help Center That's useful if, for example, your framed prints ship differently from T-shirts.

Big Cartel is appealing if you want something lightweight. It integrates with Printful, Printify, and theprintspace, including gallery-grade art prints. One caveat: Big Cartel says Printful shipping rates don't automatically sync, so you'll need to configure those rates yourself. Big Cartel Big Cartel

What I'd build for a photographer

A particularly clean setup would be:

Portfolio site → ecommerce checkout →

• Fine-art prints: a photography-focused provider such as Printique/theprintspace
• T-shirts, hoodies, totes, etc.: Printful
• Storefront: Squarespace or Shopify

Printful handles production, packing and shipping after an order, with no inventory for you to hold. It also supports international fulfillment. Printful

If having the photography portfolio and store feel like one beautiful website is the priority, I'd look closely at Squarespace + Printful/Printique.

If shipping rules, multiple fulfillment providers, international selling, and eventually adding your own inventory are more important, I'd look at Shopify.

If you tell me roughly (1) where most of your customers are, (2) whether you need framed prints, and (3) whether you want to hold any inventory yourself, I can narrow this to a practical setup and compare the likely fees/margins.

A particularly clean setup would be:

Portfolio site → ecommerce checkout →

For a creator selling a shirt + poster + digital track as one bundle, I’d look primarily at Shopify vs. Big Cartel.

Quick comparison

Shopify has a first-party free Bundles app that supports fixed bundles and multipacks, with inventory/order components handled individually. Shopify Help Center

Big Cartel is particularly interesting for your exact setup. It now supports physical and digital products natively, including MP3s, and digital files can be delivered automatically after purchase. Big Cartel Big Cartel More importantly, its shipping profiles can combine shipping charges across different products when the shipping rules match. Big Cartel

So, for example, you could have:

“Album Bundle — $55”
👕 Shirt
🖼️ Poster
🎵 Digital track
One physical shipment + instant digital delivery

My practical take

If you're a solo musician/artist and want the least complicated setup, I'd lean Big Cartel. It has unusually good alignment with the "physical merch + digital music" model, and its current shipping system explicitly supports combining rates across products. Big Cartel Big Cartel

If you expect to build a larger ecommerce operation—lots of SKUs, multiple bundle configurations, sophisticated inventory, discounts, subscriptions, fulfillment integrations, etc.—Shopify gives you substantially more room to grow.

One important distinction: “bundle product” and “combined shipping” are separate problems. A platform can make a bundle listing beautifully but still calculate shipping awkwardly. For your case, I'd prioritize the platform's ability to treat the shirt/poster as one physical shipment while the track is delivered digitally, rather than just looking for a "bundles" feature.

If you tell me whether you're shipping the shirts/posters yourself or using Printful/Printify, I can narrow this down considerably—the answer changes depending on fulfillment.

If your priority is selling directly from social posts and livestreams, I’d make Shopify the core commerce platform.

My recommendation: Shopify + native social channels

shopify.com is probably the easiest all-around setup because it can act as your central product/catalog/order system while connecting to multiple social platforms. Shopify currently supports direct social selling across TikTok, Instagram/Facebook, and YouTube. Shopify Shopify Help Center

Why I’d choose Shopify

The big advantage is that you don't have to choose one social network.

For example:

Shopify catalog → TikTok Shop → shoppable TikToks + LIVE

Shopify catalog → Instagram → tagged posts/Reels/Stories

Shopify catalog → YouTube → shoppable videos + livestreams

Inventory and orders can be managed centrally rather than maintaining separate product catalogs. Shopify Help Center Shopify

TikTok is particularly compelling if livestream selling is central to your strategy: TikTok Shop supports shoppable videos, LIVE shopping, a Shop tab, and product-linked advertising. TikTok For Business

For Instagram, Shopify can sync your catalog so products can be tagged in posts and Stories; current Instagram Shopping flows send customers to your Shopify checkout. Shopify Help Center

If livestreaming is your main business model

I'd consider adding a dedicated live-shopping tool on top of Shopify rather than replacing Shopify. Shopify's app ecosystem includes tools for shoppable Reels, UGC, and live selling, including apps that support Facebook, Instagram, and TikTok livestreams. Shopify App Store Shopify App Store

So my preferred architecture would be:

Shopify → social integrations → TikTok/Instagram/YouTube → posts + livestreams → checkout → Shopify

That gives you the widest social-platform coverage without locking your entire business into TikTok or Instagram.

If you tell me what you're selling, your approximate monthly sales, and whether TikTok/Instagram/YouTube is your biggest audience, I can narrow this down to the best 2–3 platforms and the exact setup I'd use, including fees and livestream capabilities.

Pick based on your store platform:

• Shopify: Shopify + Shopify Collabs is the simplest fit for influencer codes, affiliate links, creator discovery, and payouts inside Shopify. Shopify Add a dedicated affiliate tool like Refersion or UpPromote if you need deeper affiliate management. Shopify
• WooCommerce: WooCommerce + Affiliate for WooCommerce is strong if you want affiliate links, influencer coupon codes, commissions, and payouts managed in WordPress. WooCommerce
• Growing DTC brand with many creators: consider Upfluence or Triple Whale for influencer campaign tracking and attribution across codes + links. Upfluence Triple Whale Help Center

My default recommendation:

• Starting out: Shopify + Shopify Collabs.
• Serious affiliate program: Shopify + Refersion/UpPromote, or WooCommerce + Affiliate for WooCommerce.
• Heavy influencer marketing: add Upfluence/Triple Whale.

Key features to require: unique discount codes per creator, link tracking, commission rules, fraud/refund handling, and payout automation. WooCommerce Shopify

If I were the lead developer at a large retailer building a headless architecture for many storefronts, my default choice would be commercetools—unless your organization is already deeply invested in Salesforce or Shopify.

My ranking

Why I'd pick commercetools

For a large retailer, I'd optimize for independent storefront evolution, rather than simply asking which platform has the nicest headless APIs.

commercetools is particularly strong because it is API-first and modular: the commerce backend is deliberately separated from the experience layer, allowing multiple storefronts and channels to consume the same underlying commerce capabilities. commercetools commercetools

I'd structure it roughly like:

                    ┌── Brand A Web
                    ├── Brand B Web
                    ├── Brand C Web
                    ├── Mobile App
                    ├── Marketplace
                    └── In-store / Kiosk
                           │
                     Experience Layer
                           │
                 ┌─────────┴─────────┐
                 │ Commerce APIs     │
                 │ commercetools     │
                 └─────────┬─────────┘
                           │
        ┌──────────┬───────┼────────┬─────────┐
        │          │       │        │         │
     Catalog    Pricing  Cart     Orders    Inventory
        │          │       │        │         │
        └──────────┴───────┴────────┴─────────┘
                           │
             ERP / PIM / OMS / CRM / Search

The important architectural property is that Brand A doesn't become a special case in the commerce backend. You can establish shared capabilities and let each storefront own its presentation, content, merchandising experience, and release cadence.

That becomes especially valuable if you have:

• Multiple brands
• Different countries/regions
• Different catalogs or assortments
• B2C + B2B
• Multiple currencies/tax regimes
• Different frontend teams
• Web + mobile + other channels
• A PIM/ERP/OMS that you don't want the commerce platform to own
• A long-term goal of replacing individual components independently

Salesforce is the strongest alternative

If you're already a major Salesforce customer, I'd seriously consider Salesforce Commerce Cloud + Composable Storefront.

Salesforce's current architecture provides Commerce APIs, React-based PWA Kit, and Managed Runtime, and explicitly supports multiple sites/storefronts from a common codebase. Developer Developer

It also has a particularly mature model for organizations with multiple sites and storefronts; Salesforce documents configurations ranging from one site/multiple storefronts through multiple sites/multiple storefronts. Salesforce

So my decision rule would be:

Already Salesforce-heavy → Salesforce Commerce Cloud.

Starting relatively fresh and want maximum composability → commercetools.

Where Shopify Plus fits

Shopify Shopify Plus would be my choice if the priority is getting many storefronts operational quickly with a relatively small engineering/operations burden.

It now supports headless storefronts using Hydrogen and Oxygen, and Plus provides expansion stores and centralized organization management. Shopify Help Center Shopify Help Center

But I'd be more cautious if your requirement is genuinely "large retailer + many independently evolving storefronts + deep customization." Shopify's expansion stores are operationally separate stores even though they can be centrally managed, and Plus has constraints around how brands/stores are organized. Shopify Help Center Shopify

In other words:

Shopify Plus optimizes for operational simplicity. commercetools optimizes for architectural freedom.

What I'd actually standardize

Regardless of platform, I wouldn't make the commerce platform the center of the entire architecture.

I'd establish:

• Commerce: commercetools
• Frontend: Next.js/React or equivalent
• CMS: composable CMS
• Search: dedicated search engine
• PIM: authoritative product source
• OMS: authoritative order/fulfillment source
• CDP/CRM: customer identity and behavioral data
• API gateway/BFF: storefront-specific aggregation
• Event backbone: Kafka/Pub/Sub/etc.
• Observability: centralized tracing, metrics and logs
• Design system: shared components with brand-level theming

The key is to make storefronts disposable. If Brand C wants a radically different frontend six months from now, you should be able to replace its frontend without re-platforming commerce.

My recommendation

For your stated scenario, I'd shortlist commercetools and Salesforce Commerce Cloud, with Shopify Plus as the pragmatic alternative.

If you tell me roughly how many storefronts, brands, countries, SKUs, annual orders, and whether you already use Salesforce/Adobe/Shopify, I can give you a much more concrete architecture decision—including commercetools vs Salesforce vs Shopify, estimated engineering complexity, and the organizational/team implications.

Shopify Shopify Plus would be my choice if the priority is getting many storefronts operational quickly with a relatively small engineering/operations burden.

It now supports headless storefronts using Hydrogen and Oxygen, and Plus provides expansion stores and centralized organization management. help.shopify.com help.shopify.com

But I'd be more cautious if your requirement is genuinely "large retailer + many independently evolving storefronts + deep customization." Shopify's expansion stores are operationally separate stores even though they can be centrally managed, and Plus has constraints around how brands/stores are organized.

In other words:

Shopify Plus optimizes for operational simplicity. commercetools optimizes for architectural freedom.

What I'd actually standardize

Regardless of platform, I wouldn't make the commerce platform the center of the entire architecture.

I'd establish:

For a B2B division with custom/customer-specific pricing, POS, and large order volumes, I’d shortlist Adobe Commerce, Shopify Plus, and BigCommerce Enterprise—but I’d put Adobe Commerce first if the B2B side is genuinely complex.

My shortlist

1. Adobe Commerce — my choice for complex B2B

Adobe Commerce is particularly strong when pricing and ordering rules get complicated.

It natively supports:

• Company-specific catalogs and pricing
• Multiple buyer accounts and organizational hierarchies
• Negotiated quotes
• Purchase-order workflows and approvals
• Quick ordering by SKU
• Requisition lists/reordering
• Different payment and shipping rules by company
• B2B and B2C on the same commerce platform

Adobe's current documentation specifically supports shared catalogs with custom pricing per company, negotiated quotes, purchase orders, and quick ordering. Experience League Experience League Experience League

That's a very good match if your sales reps might say:

"Customer A gets 17% off, Customer B gets a contracted price, Customer C has a different price at 500+ units, and this customer needs a PO approval."

Adobe can model that kind of complexity much more naturally than a primarily DTC-oriented platform.

2. Shopify Plus — strongest if POS is strategically important

Shopify Plus becomes very compelling if the same business needs excellent physical-store POS + ecommerce + B2B.

I'd favor Shopify Plus if your model looks like:

Retail stores / showrooms + ecommerce + B2B portal

rather than:

Highly complex B2B sales organization + ERP-driven pricing + negotiated contracts.

Shopify's B2B offering includes company-specific catalogs, pricing, payment terms, purchasing permissions and bulk ordering. Shopify

The big advantage is the unified Shopify ecosystem and POS. If your B2B customers also interact with physical locations, that can substantially simplify the architecture.

3. BigCommerce Enterprise — very worth evaluating

BigCommerce is probably the one I'd put into the RFP alongside Adobe and Shopify.

It's particularly interesting when you want sophisticated B2B functionality but don't want the degree of platform customization/complexity that Adobe can bring.

BigCommerce is strong for:

• Customer-specific pricing
• Large catalogs
• Bulk ordering
• Multiple storefronts
• ERP/PIM integrations
• Headless commerce
• Enterprise-scale order volumes

Its POS story isn't as inherently central as Shopify's, though, so I'd scrutinize the exact POS architecture rather than treating "POS integration" as a checkbox.

The bigger question: where does pricing live?

For your situation, this is probably more important than the ecommerce platform itself.

If you have thousands of B2B customers with negotiated pricing, I'd want to know whether pricing is mastered in:

ERP → Commerce

or

Commerce → ERP

or some hybrid model.

For example:

Customer → Contract → Price List → Volume Breaks → Product/SKU → Region → Sales Rep → Payment Terms

If that's your reality, I'd lean Adobe Commerce or BigCommerce, with the commerce platform tightly integrated to the ERP.

If pricing is relatively straightforward and POS is a major part of the business, I'd lean Shopify Plus.

My recommendation

I'd rank them like this based on what you've described:

1. Adobe Commerce — best overall for sophisticated B2B requirements
2. Shopify Plus — best if POS/unified retail experience is a major priority
3. BigCommerce Enterprise — excellent middle ground
4. OroCommerce — worth considering if you're overwhelmingly B2B and need a B2B-first platform

One important caveat: POS could change my #1 recommendation. If you tell me what POS you use today, what ERP you use (SAP, NetSuite, Dynamics, etc.), approximate annual B2B revenue/order volume, number of SKUs, and whether B2B customers have negotiated prices or formal contracts, I can give you a much more definitive Adobe vs Shopify Plus vs BigCommerce architecture recommendation.

For a fast-fashion enterprise running many campaign microsites with frequent launches, I’d shortlist:

• Shopify Plus — strongest fit if speed, marketer autonomy, and rapid campaign launches matter most. Plus supports expansion stores and up to 25 custom headless storefronts. Shopify Help Center Shopify Help Center
• BigCommerce Enterprise — particularly compelling if you need many distinct storefronts/brands managed from one backend, with differentiated catalogs, pricing, domains, and experiences. BigCommerce BigCommerce
• Salesforce Commerce Cloud — consider if you need a highly customized, composable architecture integrated deeply with a broader enterprise Salesforce stack. Salesforce Developer

My architectural preference: Shopify Plus + a reusable headless/CMS campaign layer, rather than creating independent ecommerce stacks for every microsite. This gives marketing teams speed while keeping catalog, checkout, inventory, and operations centralized.

If you tell me your approximate GMV, number of microsites, countries, and whether each campaign needs a separate catalog/checkout, I can narrow this to an architecture.