All answers

For a small handmade goods shop with no coding skills, I’d usually narrow it down to these hosted options:

My quick recommendation:

• Just starting and testing demand: Etsy
• Want your own branded storefront: Shopify
• Selling a small collection of premium handmade items: Squarespace
• Want to design everything yourself visually: Wix
• Have 5–50 products and want simplicity: Big Cartel

For most handmade shops planning to build a recognizable brand, I’d start with Shopify and connect it to social channels or marketplaces later. It avoids needing to rebuild your store if your product line grows. Shopify

If you tell me:

1. roughly how many products you sell,
2. whether you already sell on Etsy/social media, and
3. your monthly budget,

I can narrow it to one best fit.

For high-traffic sales events and flash deals, the main options I’d compare are Shopify Plus, BigCommerce, and Adobe Commerce. The key distinction is how much infrastructure management you want to own.

What stands out

• Shopify Plus is particularly purpose-built for flash-sale scenarios. Shopify provides automated event scheduling, bot protection, and infrastructure designed to handle large surges in buyer traffic. Shopify Shopify
• BigCommerce runs on Google Cloud and says its infrastructure provides automatic scaling, load balancing, and traffic management. It also has native flash-sale and promotion capabilities. BigCommerce BigCommerce
• Adobe Commerce Cloud offers more infrastructure control. Its scaled architecture can independently scale web and service tiers, while autoscaling can add web nodes or increase node capacity. Experience League Experience League

If your priority is simply "don't let the flash sale take the store down," I'd focus first on Shopify Plus and BigCommerce. If you have a complex enterprise architecture and need extensive customization/control, Adobe Commerce Cloud is worth evaluating.

One important caveat: the platform isn't the whole bottleneck. Shopify specifically recommends load/volume testing third-party apps and payment providers before a major flash sale, since those dependencies can become the failure point even when the core platform scales. help.shopify.com

If you tell me your expected peak concurrent users/orders per minute and whether you're B2C, B2B, or marketplace, I can compare the three specifically for your traffic profile.

For an agency building and operating multiple client stores, I’d narrow the field to Shopify Plus vs. BigCommerce Multi-Storefront. The key distinction is whether your “multi-store” requirement means many independent client businesses or many storefronts belonging to one merchant.

My take

If you're an agency building stores for lots of unrelated clients: Shopify is probably the better operational fit.

Shopify's Partner infrastructure is explicitly designed around agencies: you can create dev stores and client-transfer stores, build them under your Partner organization, collaborate with clients, and transfer ownership when the project goes live. Shopify Help Center Shopify Help Center

For larger clients using Shopify Plus, organizations give you centralized user management, billing, store administration, and expansion-store functionality. Shopify Help Center Shopify Help Center

The important caveat: Shopify Plus expansion stores aren't a true shared-database multisite system. Each store has its own products, inventory, settings, etc.; synchronization generally requires apps or an ERP. Shopify Help Center

Where BigCommerce gets interesting

If your agency's model is more like:

"We have one client/company with 10 brands, regions, or storefronts, and we want to operate all of them from one backend."

then BigCommerce Multi-Storefront deserves serious consideration.

It lets you manage multiple storefronts from one control panel, with different domains, branding, catalogs, pricing, currencies, and customer experiences. Products can be made available on selected storefronts, while analytics and management remain centralized. BigCommerce BigCommerce

That's a materially different architecture from having 10 completely independent Shopify stores.

The decision I'd use

• Agency → many unrelated clients → Shopify
• One client → many brands/regions/storefronts → BigCommerce Multi-Storefront
• High-end Shopify clients needing international/B2B/brand expansion → Shopify Plus
• Clients needing centralized catalog + multiple distinct storefronts → BigCommerce MSF
• Agency wants maximum ecosystem, talent pool, apps, and client familiarity → Shopify

One other consideration: Shopify Plus currently includes the main store plus 9 expansion stores in the base monthly platform fee, with additional-store pricing beyond that; separate brands can require separate Plus contracts. Shopify

If you tell me roughly how many stores you expect to manage (10 / 50 / 500+) and whether each client needs their own Shopify/BigCommerce account, I can map out the actual agency operating model—store creation, staging, permissions, billing, client handoff, reusable themes, app management, and centralized reporting.

For larger clients using Shopify Plus, organizations give you centralized user management, billing, store administration, and expansion-store functionality. Shopify Help Center Shopify Help Center

The important caveat: Shopify Plus expansion stores aren't a true shared-database multisite system. Each store has its own products, inventory, settings, etc.; synchronization generally requires apps or an ERP. Shopify Help Center

Where BigCommerce gets interesting

If your agency's model is more like:

"We have one client/company with 10 brands, regions, or storefronts, and we want to operate all of them from one backend."

then BigCommerce Multi-Storefront deserves serious consideration.

It lets you manage multiple storefronts from one control panel, with different domains, branding, catalogs, pricing, currencies, and customer experiences. Products can be made available on selected storefronts, while analytics and management remain centralized.

That's a materially different architecture from having 10 completely independent Shopify stores.

The decision I'd use

If your priority is a large, diverse supplier ecosystem with many integrations, I’d put Shopify at the top of the shortlist.

Why Shopify fits a multi-supplier dropshipping business

• Very large app/integration ecosystem. Shopify has a dedicated dropshipping marketplace with integrations for AliExpress/Alibaba, CJdropshipping, Syncee, Printful, Printify, EPROLO, US/EU suppliers, and others. Shopify Help Center Shopify App Store
• Multiple sourcing models. You aren't locked into one supplier network—you can combine marketplace suppliers, private suppliers, regional suppliers, POD suppliers, and sourcing agents.
• Strong supplier-to-store automation. Inventory, pricing, product information, orders, fulfillment and tracking can be synchronized through supplier apps.
• Shopify Collective is particularly interesting if you want to build a network of established brands/suppliers rather than relying primarily on AliExpress-style sourcing. Shopify describes Collective as providing real-time product, pricing and inventory syncing between retailers and suppliers. Shopify Help Center
• The Shopify App Store currently has a substantial collection of dropshipping integrations, including DSers, CJdropshipping, Printful, Printify, Shopify Collective and others. Shopify App Store

How I'd compare the major platforms

BigCommerce deserves serious consideration if you're building something more technically sophisticated. Its marketplace has hundreds of pre-built integrations across fulfillment, sales channels, accounting, marketing, payments, etc., and its API/webhook architecture is designed for custom integrations. BigCommerce BigCommerce

WooCommerce is particularly flexible if you want to control the supplier architecture. Its official dropshipping extension, for example, supports assigning products to specific suppliers, importing inventory by supplier, supplier-specific fulfillment and tracking. WooCommerce

The important distinction

If by "supplier ecosystem" you mean:

"I want to connect 50–500 different suppliers, each with their own inventory feeds/API/order process, and have them all operate through one store."

Then I would look beyond the storefront platform itself. Shopify + a supplier integration/OMS layer may be a better architecture than trying to make Shopify directly manage hundreds of individual supplier connections.

For example:

Customer → Shopify → Order routing layer → Supplier A/B/C/D → Tracking → Shopify → Customer

That becomes especially important if you intend to onboard suppliers yourself, rather than simply installing existing dropshipping apps.

If you're actually considering building a dropshipping marketplace/platform where hundreds of suppliers can connect their own catalogs, rather than merely running a store with many suppliers, that's a different question—and I'd compare Shopify, BigCommerce, Medusa, Saleor, Mirakl, and a custom architecture very differently.

For a neighbourhood gift shop, I’d look for software that lets you keep a simple spreadsheet of SKU, product name, description, price, stock, category, and image URL and upload it without a lot of technical cleanup. These are the strongest options:

For your specific use case, I’d usually narrow it to:

Easiest day-to-day: Shopify

• You can build a spreadsheet, save as CSV, and import products in bulk. Shopify Help Center
• Good for gift shops with lots of one-off items, seasonal collections, and simple variants.
• Less time spent maintaining the website.

Most spreadsheet-friendly/flexible: WooCommerce

• The importer includes column mapping, so it can adapt better if your supplier spreadsheets have unusual columns. WooCommerce
• If you later need custom fields (gift occasions, materials, makers, etc.), WooCommerce has more room to customize. A paid extension can expand CSV handling for larger or more complex catalogs. WooCommerce

A few questions would change the recommendation:

1. Do you already use a checkout system (Square, Clover, Lightspeed, etc.)?
2. Roughly how many products do you carry (100, 1,000, 10,000+)?
3. Do you need the spreadsheet to update stock levels automatically, or just add new products?

For a small artisan selling both ready-made goods and custom items, these are strong fits:

• shopify.com — Best all-around/easiest setup. Use pre-order and made-to-order apps to show production windows, collect deposits, and manage custom items. Shopify supports pre-orders through apps with payment options such as full, partial, or later payment depending on setup. Shopify Help Center Shopify Help Center
• woocommerce.com — Best if you want more control. With WooCommerce Pre-Orders you can set availability dates, charge upfront or on release, and manage handmade or limited-run products. WooCommerce WooCommerce Add a lead-time plugin for “ships in 3–5 weeks” style messaging. Barn2 Plugins
• etsy.com — Good for artisan discovery, but custom lead-time workflows are less flexible than running your own store.

For your use case, I’d lean:

1. Shopify if you want simple operations and growth.
2. WooCommerce if your custom orders need detailed options, forms, or unusual workflows.
3. Etsy + Shopify/WooCommerce if you want marketplace traffic plus a dedicated shop.

Look for features like:

• per-product production times (“made in 2–4 weeks”)
• deposits or partial payments
• custom fields/options
• order notes and customer approvals
• preorder status emails
• ability to mix in-stock and made-to-order items

For a handmade business, avoid platforms that only handle “out of stock preorders” but cannot communicate custom production timelines.

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

• Square Online — best if you want a simple store that can grow: Its Free plan has $0/month in subscription costs and lets you build an online store and take payments; you pay processing fees when you make a sale. Square Square
• Big Cartel — especially good if you only have a tiny catalog: Its free Gold plan supports up to 5 products, online selling, cards/PayPal, and basic storefront features. Big Cartel
• Etsy — useful if you want access to an existing marketplace: It's not free per sale: Etsy currently charges $0.20 per listing plus a 6.5% transaction fee, along with payment-processing and potentially other fees. Etsy Help

What I'd do in your situation

Start with Square Online if you have more than ~5 products or expect your catalog to grow. You can launch without paying a monthly subscription, then worry about a custom domain and paid features after you're actually making sales.

Choose Big Cartel instead if you're starting with just a handful of handmade products and want a storefront geared toward artists/makers.

squareup.com
bigcartel.com

If you tell me roughly how many products you'll sell and whether you also sell in person at markets/craft fairs, I can narrow it down to the cheapest setup for you.

Yes. If the client literally has $0 budget for hosting, you have several workable options.

Best options

• squareup.com — Probably the easiest choice for a normal physical-product store. The Free plan is $0/month, includes hosted ecommerce, SSL, checkout, inventory, and a Square-hosted URL. You pay payment-processing fees when something sells. Square Square
• bigcartel.com — Genuinely free for a tiny catalog: up to 5 products, with a hosted storefront and no monthly fee. Good for artists, merch, or a very small product line. Big Cartel Big Cartel
• ecwid.com — Useful if you're already building a static site and want to embed ecommerce into it. Its free offering is more limited, so I'd check the current product/payment limits before committing.
• pages.github.com + a payment provider — If you're comfortable coding, you can host the storefront itself for free on static hosting and use something like Stripe Checkout/payment links. This gives you much more design control, but you'll have to build more of the ecommerce functionality yourself.

What I'd do as a freelancer

If this is a real client store with products, cart, checkout, orders, etc., I'd lean toward Square Online Free. You can build the client a legitimate hosted store without asking them to pay for hosting, and the platform handles the infrastructure. Square explicitly says its free plan includes hosting and SSL. Square

The catch is that "free hosting" doesn't mean "free ecommerce." Payment processing still costs money when the client makes sales, and custom domains generally require a paid plan. Square

If you tell me what you're building it with (plain HTML/JS, React/Next.js, WordPress, etc.) and roughly how many products, I can suggest a completely $0/month architecture that you can hand off to the client.

For a solo indie maker with zero dev experience, I’d narrow it to these:

• squareup.com — easiest all-around free starting point. $0/month, no coding required, hosted store, payments, shipping/pickup, inventory, and SEO tools. The free plan charges a transaction fee when you sell. Square Square
• bigcartel.com — great for a tiny indie catalog. Its Gold plan is genuinely $0 with no credit card required, and supports 5 products, variants, payments, tax tools, and a simple template. Big Cartel says you can launch in about 30 minutes. Big Cartel
• ecwid.com — good if you want a more traditional website. It emphasizes zero technical experience, drag-and-drop editing, templates, and a free company.site domain. Ecwid | E-Commerce Shopping Cart Ecwid | E-Commerce Shopping Cart
• shopify.com — consider later rather than starting here. It's very beginner-friendly and built to scale, but its lowest-cost options aren't as attractive if your priority is $0 upfront. Shopify

My practical pick

Start with Square Online if you're selling physical products. You can get a store live without touching code or paying a monthly subscription, then upgrade only when you actually need more customization. Square

If you're selling 5 or fewer products and want the absolute simplest indie-maker setup, I'd look at Big Cartel first. Big Cartel

If you tell me what you're selling (physical, digital, or both) and roughly how many products, I can narrow it down to one and give you a 30-minute setup plan.

For a tiny prospect-facing demo storefront with $0/month spend, I’d look at these:

• squareup.com — probably the simplest. Square has a $0/month Free plan with a hosted storefront, product catalog, checkout, shipping/pickup options, and hosting. You only incur payment-processing fees if you actually take payments. Square Square
• WooCommerce — free/open-source software, but you need WordPress hosting, so it isn't truly $0 unless you already have hosting.
• Ecwid — useful if you want to embed a small store into an existing agency/demo site; its free tier can be suitable for very small catalogs, though feature limits matter.
• Shopify — polished for demos, but generally better suited to a trial/prototype than a permanently free storefront.

For an agency demo, Square is particularly convenient: create 5–10 fictional products, brand the site for the prospect, and hand them a public storefront URL. You can leave checkout/payment processing unused, so the demo itself doesn't cost anything. Square

If you tell me whether you want (a) a public URL, (b) a fake checkout that never charges, or (c) a fully editable demo you can clone for each prospect, I can narrow it down to the most practical option.

For a photographer selling prints + digital downloads + licensing, I’d look first at Pixieset and Pic-Time. Both are built specifically around photography rather than being generic ecommerce platforms.

My shortlist

🥇 Pixieset — probably the easiest starting point

pixieset.com

Pixieset's free plan is genuinely usable: 3 GB storage, unlimited galleries, an integrated storefront, online payments and automatic print fulfillment. The tradeoff is a 15% commission on store sales. The Basic plan is currently $8/month when billed annually and removes the commission. Pixieset Pixieset

It supports print products, digital downloads and packages, so you could structure a gallery like:

• Digital download — web resolution
• Digital download — full resolution
• Fine-art print — various sizes
• Print + digital bundle
• Commercial image license — custom/negotiated

Pixieset Help CenterWhy I'd consider it: very little technical setup. You can have a polished photography storefront without building Shopify/WordPress yourself.

🥈 Pic-Time — particularly interesting for selling prints

pic-time.com

Pic-Time has a permanent free plan, and its Print Shop is included without a monthly fee. It can automatically fulfill prints through 30+ labs worldwide. The free plan has a 15% commission, while the Beginner plan is $7/month annually. Pic-Time Pic-Time Onboarding

It also has unusually good controls for digital-download packages, volume pricing, full-gallery pricing, and custom products. Pic-Time Help Center Pic-Time Help Center

That makes it attractive if you're selling photography more like art/stock/licensed imagery rather than simply delivering client galleries.

What about licensing?

This is the one area where I'd distinguish "selling digital files" from "selling licenses."

If by licensing you mean something like:

"Commercial use of this photograph for one print campaign, one year, North America, $500"

I'd want a platform where you can create a custom digital product/payment + license terms, rather than treating it as an ordinary photo download.

For a small photography business, you can keep the storefront on Pixieset/Pic-Time and handle unusual commercial licenses through a custom product/invoice and a separate license agreement. That avoids paying for a much more complicated stock-photo platform before you actually need one.

What I'd choose

Starting out / keeping costs near zero: Pixieset Free.

Print-heavy fine-art photography: Pic-Time Free, especially if automated lab fulfillment matters.

Regular commercial licensing: I'd use Pixieset or Pic-Time for the storefront and galleries, but build a more explicit licensing workflow around them rather than relying on a generic "download" product.

If you tell me roughly how many images you have, whether you're selling fine-art prints vs. client prints, and what kind of licensing (editorial/commercial/stock), I can narrow this down to the most economical setup and show you exactly how I'd structure the store.

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

• Medusa — particularly compelling if your team is comfortable with TypeScript/Node. Its managed Cloud starts at $29/month, has 0% GMV fees, and includes backend + storefront hosting. You can also self-host, so you retain an escape hatch if infrastructure costs become important. docs.medusajs.com
• Saleor — very capable GraphQL/headless option, with an open-source version you can self-host. However, its managed Cloud pricing is currently much higher, starting at $1,599/month, so it makes more sense if you specifically value its architecture/features or have the engineering resources to self-host. saleor.io
• Shopify + Hydrogen — worth evaluating if minimizing engineering/operations work matters more than minimizing platform cost. It's generally a different tradeoff: managed commerce infrastructure and ecosystem versus greater platform dependence.

My evaluation shortlist

For a small team, I'd prototype the same simple store in Medusa and Shopify/Hydrogen, then compare the actual monthly cost and developer effort. Medusa's $29 Cloud entry point makes that experiment relatively inexpensive. docs.medusajs.com

If you tell me your expected monthly orders, SKU count, and frontend stack (e.g. Next.js), I can narrow this to a concrete low-cost architecture and estimated monthly bill.

For complex international tax, currency, language, and regional rules, I’d shortlist Saleor and Medusa. Saleor is particularly designed around multi-channel, multi-currency, tax, warehouse, and permission complexity. Macrostack eryxinnovationslab.com

• Saleor — strongest fit for highly complex localization; Python/GraphQL, channel-based regionalization.
• Medusa — excellent if your team is TypeScript/Node; its Region module supports localized currencies, taxes, shipping, and payments. Medusa
• Shopware — worth considering if you want a more turnkey, traditional ecommerce platform rather than a headless commerce backend. EU Vetted

For your specific description, I’d investigate Saleor first, especially if tax jurisdiction logic and many distinct markets are central requirements.

For a static/headless storefront, I’d shortlist these:

• Medusa — my default for a TypeScript/JavaScript stack. REST API + JS SDK, modular architecture, and MIT-licensed core. Vendure Pawel Owerczuk
• Saleor — excellent if you prefer GraphQL and have Python/Django expertise; particularly strong for multi-channel commerce. Vendure
• Vendure — TypeScript + NestJS + GraphQL, with a structured plugin system; worth considering for complex B2B/multi-channel setups. Vendure Eryx Innovations Lab

For a static site specifically, I’d start with Medusa unless GraphQL is a firm requirement. Your architecture can be:

Static site → Medusa API → PostgreSQL

If you tell me your frontend stack (Astro, Next.js, plain HTML, etc.) and whether you need subscriptions/B2B/multiple stores, I can narrow it down.

For a one-person creative business selling ebooks and printable art, I’d look at these three:

• payhip.com — probably the simplest fit. Its free plan is $0/month + 5% per sale, with unlimited products and revenue, and it specifically supports ebooks, PDFs, digital downloads, coupons, affiliates, and embedded checkout. You still pay Stripe/PayPal processing fees. Payhip Payhip Payhip
• lemonsqueezy.com — good if you want taxes handled for you. There's no monthly ecommerce fee; the standard fee is 5% + $0.50 per transaction, with Lemon Squeezy acting as merchant of record and handling sales-tax/VAT collection and remittance. LemonSqueezy Lemon Squeezy Docs
• gumroad.com — very easy to launch, but pricier. There’s no monthly fee, but direct sales cost 10% + $0.50, and sales through its Discover marketplace cost 30%. Gumroad also handles worldwide sales-tax obligations as merchant of record. Gumroad

My practical pick

Start with Payhip if your priority is simple storefront + low ongoing cost. You can put your ebooks and printable bundles in one storefront without paying a monthly subscription, then move to its $29/month plan if your sales volume eventually makes the lower 2% transaction fee worthwhile. Payhip

If tax/VAT administration is something you particularly don't want to deal with, I'd instead consider Lemon Squeezy.

If you tell me roughly how much you expect to charge per product (e.g. $5, $15, $30) and how many sales/month you expect, I can calculate the approximate fees for each and show you the break-even point.

For a multi-vendor marketplace where many creators sell digital goods and receive payouts, you’ll want a platform that supports:

• Creator/vendor accounts
• Digital file delivery (downloads, licenses, courses, assets, etc.)
• Commission splits
• Automated seller payouts
• Vendor dashboards
• Tax/payment compliance support

Here are some options depending on whether you want a hosted marketplace or to build your own marketplace:

Some marketplace-focused digital solutions include Shopify-based multi-vendor setups where creators upload products, commissions are calculated, and payouts are handled through payment integrations. Garnet Marketplace PuppetVendors

If you are building a marketplace like "Etsy for digital products"

A common architecture is:

Frontend

• Shopify, Webflow, Bubble, Next.js, or custom React app

Marketplace engine

• Sharetribe
• Arcadier
• Custom backend

Payments

• Stripe Connect — commonly used for marketplace payouts, because it can route payments and split funds between the marketplace and sellers

Digital delivery

• Amazon S3 + signed URLs
• Digital downloads plugin
• Built-in asset delivery system

My shortlist by use case

Fastest launch (no/low code):

• Shopify + multi-vendor marketplace app Garnet Marketplace PuppetVendors
• Arcadier

Most customizable marketplace:

• Sharetribe + Stripe Connect

WordPress-based:

• WooCommerce + Dokan/WCFM-style vendor marketplace plugins

Creator-first SaaS marketplace:

• Consider newer digital creator marketplaces such as Knotwell, which focuses on digital assets and creator revenue sharing. Knotwell

If you’re aiming for something like Gumroad + Etsy combined (thousands of creators, automatic payouts, subscriptions, licensing, affiliate commissions), I’d lean toward Sharetribe/Stripe Connect or a custom stack rather than a normal ecommerce platform.

Lemon Squeezy fits this use case particularly well. It provides license keys/entitlements, subscription-linked access, customer downloads, and securely signed/throttled download links. You can replace uploaded files with each release so existing customers receive the latest version. LemonSqueezy Lemon Squeezy Docs

Gumroad also supports license verification, but more of the entitlement enforcement is left to your application. gumroad.com

If you're a complete beginner with no development skills, I’d narrow it down to Payhip, Gumroad, and Podia. You don't need to build or host a website yourself with any of them.

My practical shortlist

Payhip would be my starting point for your situation. Its free plan gives you unlimited products and revenue, with a 5% transaction fee. It specifically supports ebooks, PDFs and other digital products, and includes things like coupons, affiliates and pay-what-you-want pricing. Payhip Payhip

payhip.com

Gumroad is arguably even simpler. There's no monthly subscription, and it handles sales-tax obligations as merchant of record. The tradeoff is a substantially higher transaction fee: 10% + $0.50 on sales through your profile/direct links, or 30% when a customer comes through its Discover marketplace. Gumroad

gumroad.com

Podia makes more sense if you eventually want to sell ebooks alongside courses, memberships, coaching, email marketing, and a more complete website. It supports PDFs, ebooks, audio, video, ZIP files and other downloads, with built-in sales pages and delivery. Podia Podia Help Center

podia.com

What I'd do if I were starting from zero

I'd start with Payhip, rather than Shopify or WordPress.

Your basic workflow can be:

1. Create your ebook/PDF.
2. Create a free Payhip account.
3. Upload the file.
4. Add a cover image, description and price.
5. Connect Stripe or PayPal.
6. Publish the product.
7. Share the product page wherever you find customers.

You can start without paying a monthly subscription, which is particularly useful while you're testing whether people actually want your products. Payhip

If you tell me what kinds of digital products you want to sell (e.g. ebooks, planners, Canva templates, printables, AI prompts, courses, spreadsheets), I can also compare Payhip vs Gumroad vs Etsy vs Shopify specifically for your business model and show you what I'd choose.

Gumroad is arguably even simpler. There's no monthly subscription, and it handles sales-tax obligations as merchant of record. The tradeoff is a substantially higher transaction fee: 10% + $0.50 on sales through your profile/direct links, or 30% when a customer comes through its Discover marketplace. gumroad.com

gumroad.com

Podia makes more sense if you eventually want to sell ebooks alongside courses, memberships, coaching, email marketing, and a more complete website. It supports PDFs, ebooks, audio, video, ZIP files and other downloads, with built-in sales pages and delivery.

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

1. Payhip — probably the simplest fit

payhip.com supports PWYW directly: you can set a product to 0+ for completely optional payment, or 5+ for a $5 minimum with customers free to pay more. It supports digital products and automatically delivers downloads. Payhip Help Center Payhip Help Center Payhip

For example, a zine could be:

Digital Zine — $5 or more
Pay what you can. If you'd like to support the project, you can choose a higher amount.

Payhip's current pricing starts at $0/month + 5% transaction fee, with paid plans reducing or eliminating the platform transaction fee. Payhip

2. Gumroad — particularly good for creator/music sales

gumroad.com also has native PWYW. You can set a minimum amount and a suggested amount, and customers can enter whatever they'd like to pay above the minimum. It also supports a $0 minimum, allowing genuinely free downloads with optional payment. Gumroad

Its current direct-sale fee is 10% + $0.50 per transaction, with a higher fee for sales through its Discover marketplace. Gumroad

3. WooCommerce — best if you want your own storefront

If you already have WordPress, WooCommerce + Name Your Price gives you substantially more control. The official extension supports customer-entered prices, suggested prices, minimums, and donations, and it works with both simple and variable products. WooCommerce WooCommerce

That's attractive if you eventually want something like:

• Zine: $3 minimum / $7 suggested / unlimited maximum
• Album: $5 minimum / $10 suggested
• Free sampler: $0+
• Separate "Support the artist" contribution
• Your own domain and storefront
• More control over branding and checkout

The tradeoff is that you're managing WordPress/WooCommerce and paying for extensions rather than getting the whole system in one hosted package.

My practical take

For a small independent publishing/music project, I'd start with Payhip if the priority is "get this working with minimal technical overhead." Its 0+ / 5+ pricing model maps almost exactly to what you're describing.

I'd choose Gumroad if you particularly value the creator-oriented marketplace/discovery ecosystem.

I'd choose WooCommerce if you want the store to become a substantial part of your own website and want maximum control over the pricing and donation experience.

One important distinction: if by "optional donations" you mean someone can buy a $5 zine and then add an entirely separate $10 donation at checkout, rather than simply letting them pay $15 for the zine, I'd verify that specific checkout flow before choosing. PWYW handles the latter very well; a separate donation field is a slightly different requirement.

Its current direct-sale fee is 10% + $0.50 per transaction, with a higher fee for sales through its Discover marketplace. gumroad.com

3. WooCommerce — best if you want your own storefront

If you already have WordPress, WooCommerce + Name Your Price gives you substantially more control. The official extension supports customer-entered prices, suggested prices, minimums, and donations, and it works with both simple and variable products.

That's attractive if you eventually want something like:

For a startup with limited funding, I’d focus on total cost of ownership rather than raw feature count. Based on current 2026 pricing and capabilities, Medusa is a particularly cost-efficient option if you have some engineering capability. Medusa Docs Medusa

Why I'd look at Medusa first

medusajs.com is open source and can be self-hosted, so the software itself doesn't require a large platform subscription. Its managed Cloud currently starts at $29/month, with Launch at $99/month and Scale at $299/month, and Medusa states that its Cloud plans have 0% GMV platform fees. Medusa Docs Medusa

That gives you a useful progression:

• Very early MVP: self-host Medusa → minimize software costs.
• Launching: Medusa Cloud Develop → $29/month starting point.
• Growing traffic: Launch → $99/month, adding things such as autoscaling, backups, custom domains and Redis-backed KV.
• More complex operation: Scale → $299/month, adding background workers and additional infrastructure. Medusa Docs

The main tradeoff is engineering effort. Headless commerce isn't inherently cheap just because the commerce engine is open source—you still need developers to build the storefront, integrations, deployment, monitoring, etc.

When I'd choose something else

Shopify + Hydrogen makes sense if your startup has limited engineering resources, rather than merely limited cash. You're paying more for a managed commerce backend, but you get Shopify's established commerce infrastructure and ecosystem. Current comparisons describe Hydrogen as the lower-operational-burden route, while Medusa gives you substantially more ownership and customization. Ribbsaeter Systems Ask An Tech

Saleor is worth considering if you specifically need its GraphQL-first architecture, sophisticated multi-channel/international capabilities, or have a Python team. Its managed offering is much more expensive than Medusa's at the current published pricing, so it is harder to justify for a cash-constrained startup unless you need those capabilities. Saleor Eryx Innovations Lab

My practical decision rule

• You have 1–3 capable developers: Medusa
• You have little/no engineering capacity: Shopify + Hydrogen
• You need complex B2B/multi-market capabilities from the outset: investigate Saleor
• You're already operating at enterprise scale: look at commercetools/other enterprise composable platforms

So, for the specific constraint "startup + limited funding + wants headless", I'd put Medusa at the top of the shortlist, provided you have enough engineering capability to own a headless stack. ShipGarden Medusa Docs

If you tell me your monthly budget, expected orders/month, tech stack (Next.js/React/etc.), and whether you need B2B, I can narrow this down to a concrete architecture and estimated monthly cost.

I’d shortlist commercetools, Saleor, and Medusa—with commercetools the strongest fit for an enterprise-grade, highly decoupled checkout.

• commercetools — API-first/composable, with a dedicated Checkout API supporting both fully custom checkout and payment-only flows. Strong choice if checkout needs to evolve independently of the frontend and integrate multiple channels. commercetools Documentation commercetools Documentation
• Saleor — GraphQL-native and fully headless, with checkout, payments, shipping, and extensibility exposed through APIs. Particularly attractive if you want maximum frontend/BFF control and open-source flexibility. Saleor Documentation Saleor Commerce
• Medusa — Very developer/customization-oriented; storefronts are separate applications and commerce operations are exposed through APIs. Good if you want to own more of the checkout implementation. Medusa Docs Medusa Docs

Architecture-wise: I’d put a Checkout BFF/service between your frontend(s) and commerce platform, rather than letting the frontend directly orchestrate carts, payments, shipping, promotions, and order creation. That gives you freedom to swap frontend frameworks/channels—and potentially commerce components—without rewriting checkout.

If you tell me your scale, B2C/B2B, payment provider(s), and whether you want SaaS vs self-hosted, I can narrow this to an architecture recommendation.

If your primary requirement is a custom iOS/Android app frontend, I’d narrow the field to Shopify, Medusa, and Saleor. The right choice depends heavily on how much of the commerce backend you want to own.

My recommendation

For most teams building a custom mobile app, I'd start with Shopify.

Shopify's Storefront API is explicitly designed for custom experiences including native iOS, Android, and React Native apps. Its mobile architecture provides product/catalog/cart functionality through the Storefront API, while Checkout Kit can present Shopify's checkout inside the app. Shopify Shopify Shopify

That gives you an architecture roughly like:

┌───────────────────────────────┐
│       iOS / Android App       │
│                               │
│  React Native / Swift / Kotlin│
└───────────────┬───────────────┘
                │
                │ Storefront API
                ▼
┌───────────────────────────────┐
│           Shopify             │
│                               │
│ Products • Customers • Cart   │
│ Inventory • Orders • Checkout │
└───────────────────────────────┘

The major advantage is that you don't have to build and maintain things like inventory, order management, payments, admin tooling, and much of the commerce infrastructure yourself.

When I'd choose Medusa instead

I'd seriously consider Medusa if your mobile app is not merely a custom presentation layer but the product itself has unusual commerce behavior.

Medusa's Store API is explicitly intended for storefronts including commerce mobile apps, and its authentication supports JWTs specifically suited to mobile/client applications. Medusa Docs

It also lets you create custom API routes, workflows, and integrations, giving you substantially more control over the backend. Medusa Docs Medusa Docs

For example, if you're building:

• A marketplace
• Complex subscription/entitlement logic
• Highly customized checkout
• Unusual fulfillment rules
• Multiple external systems
• A commerce app with significant proprietary business logic

I'd lean toward Medusa.

The tradeoff is that you're taking on more engineering and infrastructure responsibility than with Shopify.

Where Saleor fits

Saleor is particularly interesting if your team likes GraphQL and wants an API-first, open-source commerce backend. Current comparisons characterize its architecture as Python/Django with GraphQL, versus Medusa's TypeScript/Node/REST approach. Eryx Innovations Lab OSSAlt

I'd put it on the shortlist if your backend team is already comfortable with Python/GraphQL or you have sophisticated multi-channel/B2B requirements.

A practical decision rule

I'd use this:

Choose Shopify if:

• You want to launch quickly.
• Your mobile app is primarily a custom shopping experience.
• You don't want to operate the commerce backend.
• You need mature payments, checkout, inventory, orders, and merchant tooling.
• Your business logic mostly fits standard ecommerce concepts.

Choose Medusa if:

• Your engineering team wants control of the backend.
• You expect substantial custom commerce logic.
• You want an open-source foundation.
• Your team is strong in TypeScript/Node.
• Your mobile app is going to have behavior that doesn't fit neatly into Shopify.

Choose Saleor if:

• GraphQL is a major architectural preference.
• Your team is comfortable with Python.
• You need sophisticated multi-channel/B2B capabilities.
• You want open-source and API-first architecture.

Choose commercetools if:

• This is a large enterprise project.
• You're building a genuinely composable commerce architecture.
• You have the engineering budget to support considerable complexity.

One important architectural point

For a serious mobile app, I wouldn't have the app directly call every third-party service.

I'd generally structure it as:

              iOS / Android
                    │
                    ▼
          ┌──────────────────┐
          │  Your API/BFF    │
          └────────┬─────────┘
                   │
       ┌───────────┼────────────┐
       ▼           ▼            ▼
    Commerce      CMS       Analytics
    Platform
       │
       ▼
   Payments

A BFF (backend-for-frontend) can give you a stable API specifically for your app, hide internal implementation details, combine multiple API calls, enforce authorization, and prevent your mobile client from becoming tightly coupled to the commerce platform.

If you're building a React Native app, Shopify becomes especially attractive because Shopify explicitly supports React Native mobile storefronts, while Medusa provides a JavaScript SDK plus direct REST APIs that can also fit naturally into that stack. Medusa Docs Shopify

Bottom line: for a conventional ecommerce mobile app, I'd start with Shopify; for a highly differentiated/custom commerce application, I'd start with Medusa. The distinction is less about whether either can power a mobile app—they both can—and more about how much of the commerce engine you want to control yourself. Medusa Docs Shopify

If by “best developer tools and SDKs” you mean TypeScript quality, modern React/Next.js integration, composability, CLI/tooling, API ergonomics, and freedom to choose the frontend framework, the landscape in 2026 looks roughly like this:

Shopify

Shopify currently has arguably the most mature overall frontend developer experience.

Its Storefront API is GraphQL, and Shopify provides an official Storefront API client, Node.js libraries, Hydrogen, Hydrogen React, TypeScript tooling, and React Router tooling. Shopify

The particularly interesting development in 2026 is Shopify's new Hydrogen developer preview: Shopify is moving Hydrogen from an opinionated React/React Router framework toward a framework-agnostic SDK/toolkit that can work with different JavaScript frameworks and runtimes. Shopify Hydrogen

That makes Shopify considerably more interesting if your team doesn't want to commit to Hydrogen.

shopify.dev

Medusa

Medusa is particularly compelling if you're a developer-first team.

Its JS SDK is designed specifically for custom storefronts and can be used with Next.js, React, Vue, Angular, or essentially any JavaScript frontend. It also provides TypeScript types and explicit integration guidance for things such as Next.js caching. Medusa Docs Medusa Docs

The big difference from Shopify is architectural: Medusa gives you considerably more control over the commerce backend and business logic. That's attractive when your storefront isn't just a customized version of conventional ecommerce.

docs.medusajs.com

commercetools

commercetools has extremely strong API/SDK infrastructure, particularly for enterprise teams.

Its SDKs include an official TypeScript SDK, and they're generated from the API specifications, giving you typed representations of resources, fields, endpoints, and request builders. commercetools Documentation

The frontend SDK is also designed around editable source code rather than locking you into a proprietary frontend framework. commercetools Documentation

The tradeoff is that its developer experience is more enterprise/composable than “spin up a storefront in an afternoon.”

docs.commercetools.com

Saleor

Saleor is worth serious consideration if your developers strongly prefer GraphQL + TypeScript.

It fits naturally with modern React/Next.js architectures because the frontend can treat the commerce backend as a strongly typed GraphQL service rather than adopting a large proprietary frontend framework.

My practical takeaway

If I were evaluating purely on frontend developer experience, rather than commerce functionality or price:

• Shopify — strongest all-around ecosystem and tooling; especially compelling now that Shopify is pushing toward framework-agnostic Hydrogen.
• Medusa — strongest choice if developer control and customization matter most.
• Saleor — particularly attractive for GraphQL/TypeScript-heavy teams.
• commercetools — strongest fit for large composable/enterprise architectures.
• BigCommerce — good middle ground if you want a managed commerce platform while keeping a modern custom frontend.

One important distinction: “best SDK” and “best headless commerce platform” aren't necessarily the same thing. For example, a Next.js team may prefer Medusa's developer ergonomics while an enterprise team may prefer commercetools because of its broader composable architecture.

If your stack is specifically Next.js + TypeScript + Tailwind, I can also give you a developer-focused comparison of Shopify vs Medusa vs Saleor vs commercetools, including SDK quality, type safety, local development, webhooks, checkout customization, caching, preview environments, and deployment.

That makes Shopify considerably more interesting if your team doesn't want to commit to Hydrogen.

shopify.dev

Medusa

Medusa is particularly compelling if you're a developer-first team.

Its JS SDK is designed specifically for custom storefronts and can be used with Next.js, React, Vue, Angular, or essentially any JavaScript frontend. It also provides TypeScript types and explicit integration guidance for things such as Next.js caching. Medusa Docs Medusa Docs

The big difference from Shopify is architectural: Medusa gives you considerably more control over the commerce backend and business logic. That's attractive when your storefront isn't just a customized version of conventional ecommerce.

docs.medusajs.com

commercetools

commercetools has extremely strong API/SDK infrastructure, particularly for enterprise teams.

Its SDKs include an official TypeScript SDK, and they're generated from the API specifications, giving you typed representations of resources, fields, endpoints, and request builders. docs.commercetools.com

The frontend SDK is also designed around editable source code rather than locking you into a proprietary frontend framework. docs.commercetools.com

The tradeoff is that its developer experience is more enterprise/composable than “spin up a storefront in an afternoon.”

For a subscription box business, I’d evaluate platforms based less on “headless” capability alone and more on subscription lifecycle APIs:

• create subscription
• pause/skip/resume
• swap products
• change billing dates
• manage payment methods
• handle failed payments/dunning
• generate recurring orders
• expose customer self-service controls

The shortlist I’d consider:

Shopify BigCommerce## My usual recommendation by stage

1. Growing subscription box brand: Shopify headless

For most subscription boxes, I would start here.

Why:

• Mature checkout and payments ecosystem
• Strong customer account model
• Subscription concepts are first-class through selling plans and subscription APIs
• Huge ecosystem for fulfillment, CRM, email, analytics, and subscription tooling

Shopify’s Storefront API supports retrieving subscription products through selling plans and creating carts with subscription line items. Shopify Shopify also provides subscription APIs for selling plans, subscription contracts, and payment methods. Shopify

Typical stack:

• Frontend: Next.js / Remix
• Commerce: Shopify
• Subscription engine: Shopify Subscriptions or a specialized app
• Fulfillment: 3PL integration
• CRM: Klaviyo/Customer.io/etc.

This is usually the lowest operational risk.

2. More API control: BigCommerce headless

Consider BigCommerce if you want a more open backend while still avoiding building everything yourself.

Strengths:

• Strong headless APIs
• Good catalog/order/customer foundations
• Checkout APIs designed for custom storefronts

BigCommerce documents headless storefront architectures using APIs and supports custom storefront implementations. BigCommerce Its APIs can also support subscription-related experiences, including recurring orders through custom implementations. BigCommerce

Potential downside:

• Subscription workflows may require more assembly depending on your exact model.

3. Enterprise composable: commercetools

Choose this if your subscription business is becoming a complex commerce platform.

Good when you need:

• multiple brands
• multiple countries/currencies
• unusual subscription rules
• custom pricing engines
• complex integrations

The tradeoff is that you will own more of the subscription domain logic. commercetools provides APIs, extensions, and event subscriptions for building custom commerce workflows. commercetools Documentation commercetools Documentation

4. Maximum control: Medusa or custom stack

Good if your team wants to own the entire system.

You may build:

• subscription contracts
• billing scheduler
• retry logic
• customer portal
• fulfillment rules

This can be powerful but becomes a software product you maintain.

What I would choose for a subscription box specifically

A rough decision tree:

• <$5M/year revenue or small engineering team → Shopify headless
• $5M–$50M/year and need more backend flexibility → Shopify Plus or BigCommerce
• Large enterprise, many markets, unusual subscription rules → commercetools
• Engineering-first company that wants total control → Medusa/custom

A key question: what kind of subscription box are you running?

The best choice changes a lot depending on whether you need:

1. fixed monthly boxes (“send the same box every month”),
2. build-your-own box subscriptions,
3. skip/swap/add-on flows,
4. prepaid annual subscriptions,
5. marketplace-style subscriptions with many vendors.

For a freelancer building a dropshipping MVP where the priority is speed of prototyping + easy iteration, I’d generally start with Shopify.

My practical ranking by use case

Why Shopify is attractive for your situation

1. You can get a functioning store very quickly.
You don't need to build product/catalog management, checkout, orders, customer accounts, payments, etc. from scratch.

2. Shopify has a particularly nice development workflow. Its CLI supports rapid local development, and Shopify provides dev stores specifically for building/testing. For a client project, Shopify also has client transfer stores, which are designed for freelancers/agencies to build a store and hand it over to the merchant. Shopify Shopify

3. You can keep the MVP mostly native.
I'd avoid building a custom frontend initially. Start with a Shopify theme + a small custom app/backend only where the client's workflow actually requires it. Shopify supports app extensions for integrating functionality into the online store. Shopify

4. There's a big existing dropshipping/app ecosystem.
That matters enormously for an MVP: supplier integration, product importing, fulfillment, inventory syncing, email, analytics, etc. can often be plugged in rather than developed.

When I'd choose WooCommerce instead

I'd lean toward WooCommerce if the client specifically wants maximum control and custom backend behavior, or already has a WordPress site.

WooCommerce exposes APIs for products, orders, customers, shipping zones, etc., and its Store API covers customer-facing product/cart/checkout functionality. The WooCommerce Developer Blog The WooCommerce Developer Blog

It's also quite hackable because you effectively own the WordPress/PHP stack. But that flexibility comes with more infrastructure/plugin/theme maintenance, which can slow down an MVP.

WooCommerce even has an official dropshipping extension that can group orders by supplier and automatically notify suppliers. WooCommerce

What I'd actually build

For a freelancer MVP, I'd probably do:

Shopify → native theme → dropshipping app/supplier → tiny custom app only where necessary

Rather than:

React/Next.js → custom backend → database → Stripe → custom checkout → supplier APIs → admin dashboard

The latter can be technically fun, but you're taking on a huge amount of functionality that Shopify already solves.

If the client's MVP is something more unusual—e.g. custom supplier matching, automated product sourcing, dynamic margins, AI product selection, multi-supplier fulfillment, or a bespoke merchant dashboard—then I'd reconsider and potentially use Shopify as the commerce engine while putting the custom logic in a separate app/backend.

If you tell me what the MVP actually needs to do (supplier, product import, checkout, fulfillment, custom features, expected traffic), I can sketch the fastest architecture and what I'd build vs. buy.

For a subscription-focused dropshipping store, I’d build around Shopify rather than trying to make the supplier platform itself handle subscriptions.

Recommended setup

Shopify + subscription app + dropshipping/fulfillment supplier

• Storefront & orders: Shopify
• Recurring billing: Appstle, Recharge, or another Shopify subscription app
• Supplier/fulfillment: Zendrop, DSers, AutoDS, Spocket, or a direct supplier
• Automation: Have each subscription renewal create a normal Shopify order that gets passed to your fulfillment system.

Shopify currently has a large ecosystem of subscription apps. For example, Appstle supports subscriptions, subscription boxes and bundles, while Recharge supports recurring purchases and automatic order creation. Shopify App Store Shopify App Store

For suppliers, Shopify's own 2026 supplier guide lists options including Shopify Collective, Syncee, DropCommerce, DSers, CJDropshipping, Zendrop, AutoDS and Spocket. Shopify

The key issue with dropshipping subscriptions

The subscription software isn't actually the hardest part. Supplier synchronization is.

Suppose you sell a $39/month skincare subscription:

1. Customer subscribes on Shopify.
2. Subscription app charges them every 30 days.
3. A new Shopify order is generated.
4. Your fulfillment app sends the order to the supplier.
5. Supplier ships it and returns tracking.
6. Customer's subscription continues until they pause/cancel.

You want the supplier system to handle inventory changes, order submission, tracking, SKU mapping, and ideally automatic fulfillment rather than manually recreating every renewal.

What I'd choose

BigCommerce can certainly handle recurring commerce, and its SubscriptionFlow integration can automatically turn paid subscription renewals into BigCommerce orders. BigCommerce BigCommerce But for a new subscription-focused dropshipping operation, Shopify's combination of storefront, subscription apps, and supplier integrations is generally the simpler architecture.

If you're starting from scratch, my default stack would be Shopify + Appstle + a supplier with reliable US fulfillment. The important part is choosing a supplier whose inventory and fulfillment API/integration works reliably with recurring orders—not merely one that supports ordinary dropshipping.

If you tell me what type of product you want to sell (supplements, skincare, pet products, coffee, household consumables, etc.) and your target monthly price, I can narrow this down to a specific platform + supplier + subscription stack.

If your priority is mobile performance + a low-friction checkout for a dropshipping store, I’d put Shopify first, particularly if you want to launch quickly and spend your time on products/marketing rather than infrastructure.

How I’d compare them

Shopify: Its checkout is responsive/mobile-first, and Shop Pay can save returning customers from re-entering shipping and payment information. Shopify reports up to a 50% checkout-conversion improvement versus guest checkout for Shop Pay. Shopify Shopify

Shopify also gives you real-user Core Web Vitals reporting, so you can monitor mobile performance after installing your theme/apps. Shopify Help Center Shopify Help Center

BigCommerce: A strong alternative if you want more built-in flexibility. Its default checkout is one-page and responsive, with support for wallets such as Apple Pay and PayPal. BigCommerce BigCommerce

WooCommerce: It has made substantial recent performance improvements—WooCommerce reports a 19% faster checkout from its 2026 cart/checkout work, and further performance improvements landed in WooCommerce 11.0. WooCommerce WooCommerce But your actual mobile speed depends much more heavily on your WordPress hosting, theme, plugins, caching, and payment setup.

My recommendation for your use case

Shopify + a lightweight theme + minimal apps + Shop Pay/Apple Pay/Google Pay is the combination I'd investigate first.

The important caveat is that platform choice isn't the whole performance equation. Shopify itself notes that apps, third-party scripts, analytics, theme code, and image/video sizes can materially affect storefront performance. Shopify Help Center

For a dropshipping storefront, I'd specifically optimize for:

• LCP ≤ 2.5s
• INP ≤ 200ms
• CLS ≤ 0.1
• Very lightweight product pages
• WebP/AVIF product imagery
• Minimal tracking/upsell apps
• Express checkout visible early
• Guest checkout
• Apple Pay / Google Pay / Shop Pay
• Address autocomplete
• No intrusive popups on the first mobile visit

Those are Google's "good" Core Web Vitals thresholds, and Shopify exposes them in its performance reporting. Shopify Help Center

If you're deciding between Shopify, WooCommerce, BigCommerce, and a headless/custom stack specifically for a high-converting mobile dropshipping store, I can also break down expected speed, checkout friction, costs, app ecosystem, and scalability side-by-side.

BigCommerce: A strong alternative if you want more built-in flexibility. Its default checkout is one-page and responsive, with support for wallets such as Apple Pay and PayPal. bigcommerce.com bigcommerce.com

WooCommerce: It has made substantial recent performance improvements—WooCommerce reports a 19% faster checkout from its 2026 cart/checkout work, and further performance improvements landed in WooCommerce 11.0. woocommerce.com woocommerce.com But your actual mobile speed depends much more heavily on your WordPress hosting, theme, plugins, caching, and payment setup.

My recommendation for your use case

Shopify + a lightweight theme + minimal apps + Shop Pay/Apple Pay/Google Pay is the combination I'd investigate first.

For monthly physical subscription boxes, I’d start with Shopify + Shopify Subscriptions.

Why Shopify fits your requirements

Shopify's first-party Subscriptions app supports automatic weekly, monthly, and yearly renewals. Customers can manage subscriptions, including pausing, resuming, skipping orders, canceling, updating payment methods, and changing shipping addresses, through their customer account. Shopify Help Center Shopify Help Center

help.shopify.com

The main alternative: WooCommerce

WooCommerce + WooCommerce Subscriptions is worth considering if you already use WordPress or want much more control over your store.

It supports recurring billing, multiple payment gateways, failed-payment rebilling, and a customer My Account → Subscriptions area where subscribers can manage their subscriptions. WooCommerce WooCommerce

The tradeoff is that WooCommerce generally requires more technical setup and ongoing maintenance. The Subscriptions extension itself is currently listed at $279/year, before considering hosting and other extensions. WooCommerce

My practical recommendation

• Starting from scratch: Shopify + Shopify Subscriptions
• Already on WordPress: WooCommerce + WooCommerce Subscriptions
• Want the simplest customer experience: Shopify
• Want maximum technical/customization control: WooCommerce

One important caveat: if your box needs complex subscription logic—for example, letting subscribers choose several products each month, build their own box, swap individual items, add one-time extras to the next shipment, or use sophisticated churn/retention flows—I would look beyond the basic Shopify Subscriptions app and evaluate a dedicated subscription platform/app.

If you tell me what kind of box you're selling, expected monthly subscribers, price per box, and whether customers choose/customize what's inside, I can narrow it down to the best 2–3 setups and compare their actual costs.

The main alternative: WooCommerce

WooCommerce + WooCommerce Subscriptions is worth considering if you already use WordPress or want much more control over your store.

It supports recurring billing, multiple payment gateways, failed-payment rebilling, and a customer My Account → Subscriptions area where subscribers can manage their subscriptions.

The tradeoff is that WooCommerce generally requires more technical setup and ongoing maintenance. The Subscriptions extension itself is currently listed at $279/year, before considering hosting and other extensions.

My practical recommendation

For a small ecommerce shop, the “best” subscription + dunning software usually depends on your platform (Shopify, WooCommerce, custom store), monthly subscription volume, and how much you need beyond charging cards. The biggest differentiator is often failed payment recovery (dunning) and subscriber self-service, not the recurring billing itself. ChurnTools

Here are the strongest options:

Shopify Shopify## My shortlist by shop size

If you have <500–1,000 subscribers

Start with:

• Appstle — likely the best balance of cost and capability for a small Shopify merchant. Shopify OneCart
• Shopify Subscriptions — if you only need basic “subscribe & save.” Shopify

If subscriptions are becoming a major revenue channel

Consider:

• Recharge — especially if you need many integrations (email, support, loyalty, analytics). Shopify
• Loop Subscriptions — if churn reduction and cancellation-save flows are a priority. ChurnTools

If you are not on Shopify

• Stripe Billing is often the cleanest foundation for a custom ecommerce stack. Shopify
• Chargebee is worth evaluating if you have multiple pricing models, plans, invoices, or B2B-style subscriptions. Shopify

Features I would prioritize for dunning

Make sure the tool supports:

• Automatic retry schedules after failed cards
• Email/SMS payment update reminders
• Customer self-service card updates
• Pause/skip options (to prevent cancellations)
• Cancellation surveys and save offers
• Subscription analytics (failed payment rate, churn, recovery rate)

A cheap subscription app that only retries payments may cost more in lost revenue than a slightly more expensive one with better recovery flows.

If you tell me:

1. your ecommerce platform (Shopify/WooCommerce/custom),
2. number of subscribers, and
3. whether you sell physical products, memberships, or digital goods,

I can narrow this to 2–3 choices.

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

My default recommendation:

1. If physical products are an add-on to your SaaS: use Stripe + a commerce layer

Best fit: SaaS app + hardware, kits, consumables, onboarding boxes, replenishment products.

Stack:

• stripe.com for SaaS subscriptions and payments
• shopify.com (or a headless commerce layer) for physical inventory, fulfillment, shipping, returns
• Connect the customer identity between the two

Why:

• Your SaaS billing logic stays clean (plans, seats, usage, upgrades).
• Physical products get proper ecommerce workflows: SKUs, inventory, shipping, taxes, fulfillment.
• You avoid forcing a DTC subscription platform to handle SaaS concepts. Stripe Billing is designed for flexible subscription models, while ecommerce subscription tools tend to focus on physical-product workflows. SimpleSubscription Shopify

Example:

Customer pays $99/mo SaaS plan → adds a $20/mo refill kit → SaaS stays in Stripe, product subscription runs through Shopify.

2. If the physical subscription is becoming a major revenue stream: use Shopify + Recharge (or similar)

Best fit: coffee, supplements, skincare, pet products, consumables, subscription boxes.

Stack:

• shopify.com
• rechargepayments.com or another Shopify subscription app

Advantages:

• Better customer self-service: skip, pause, swap, change address.
• Better fulfillment ecosystem.
• Less engineering work. Shopify Swell

The tradeoff: you now have two customer systems (SaaS account + commerce account) unless you build a sync layer.

3. If you need one unified checkout experience

Consider a headless commerce approach:

• Frontend: your SaaS app
• Billing: Stripe
• Commerce: Shopify APIs or another commerce backend

This gives you:

• One login
• One checkout flow
• SaaS + physical product bundles

But it requires engineering investment.

My decision rule

One thing I’d avoid: putting your entire SaaS business into Shopify just because you’re adding a physical subscription. Shopify is excellent for commerce, but SaaS billing models (usage, seats, metered pricing, entitlements) usually fit better in a billing-native system. SimpleSubscription ToolStackChoice

If you tell me:

1. your SaaS stack (Stripe? Paddle? Chargebee? custom?),
2. the physical product (hardware/refill/box/etc.), and
3. whether customers should manage everything from one account,

I can suggest a more specific architecture.

One thing I’d avoid: putting your entire SaaS business into Shopify just because you’re adding a physical subscription. Shopify is excellent for commerce, but SaaS billing models (usage, seats, metered pricing, entitlements) usually fit better in a billing-native system.

If you tell me:

For perishable weekly subscription boxes with scheduled delivery windows, I’d narrow the choice to Shopify vs. WooCommerce, with the right delivery/subscription layer added.

Practical comparison

Shopify supports subscription products and local delivery, including delivery by postal codes or geographic zones. Shopify's local-delivery tooling can also provide driver routing and delivery updates. Shopify Help Center Shopify

For your particular use case, though, WooCommerce has a particularly good fit if delivery scheduling is central to the business. WooCommerce Subscriptions supports weekly recurring shipments, while its delivery extensions can handle delivery dates, time slots, cutoffs, holidays, capacity, and subscription renewals. WooCommerce WooCommerce WooCommerce

What I'd build

If you're delivering, say, fresh produce, prepared meals, bakery boxes, flowers, etc., I'd structure it as:

WooCommerce + WooCommerce Subscriptions + Order Delivery

That gives you:

• Weekly recurring billing
• A customer's recurring delivery day
• 2–4 hour delivery windows
• Order cut-off times
• Maximum orders per delivery window
• Holidays/blackout dates
• Delivery zones
• Different schedules for different products
• Customers changing or skipping upcoming deliveries
• Delivery dates automatically carried forward on subscription renewals

WooCommerce's documentation specifically describes the subscription-renewal workflow for recurring products such as groceries and subscription boxes, including recalculating delivery dates around cutoffs, holidays, weekends and unavailable slots. WooCommerce

Shopify would be my other architecture to consider if you value simpler administration and faster launch over highly customized fulfillment logic. Shopify already supports subscriptions + local delivery, but sophisticated delivery-window/capacity behavior generally means adding an app; its App Store currently has numerous scheduling-focused delivery solutions. Shopify Help Center Shopify App Store

If you tell me (1) what you're selling, (2) your delivery radius, (3) how many boxes you expect per week, and (4) whether you use your own drivers or a courier, I can recommend an actual stack—including the subscription, delivery-window, routing, and payment components.

If you're delivering, say, fresh produce, prepared meals, bakery boxes, flowers, etc., I'd structure it as:

WooCommerce + WooCommerce Subscriptions + Order Delivery

Yes. If you're looking for a subscription-management platform that lets customers gift, pause, and swap items, Skio is a strong match.

• Pause: Customers can pause indefinitely or temporarily, with configurable pause options. Skio Skio
• Swap items: Customers can swap products/variants, adjust quantities, or add products through the customer portal. Skio
• Gift: Skio supports “gift on skip,” allowing a subscriber to gift an upcoming order rather than skip it. It also supports prepaid gift subscriptions where someone buys a subscription for another person. Skio Skio
• Self-service: These actions can be exposed directly to customers in the subscription portal, rather than requiring support intervention. Skio Skio
• Automations: Skio's Journeys can trigger product swaps, gifts, discounts, and other subscription changes based on customer behavior. Skio

skio.com

One important distinction: if by “gifting” you mean “I have an active subscription and want to send this month's item to someone else”, Skio's Gift on Skip feature is particularly relevant. If you mean “buy a 3/6/12-month subscription as a gift for another person”, its prepaid gift subscription feature covers that, although there are some restrictions on what the recipient can change. Skio

If you tell me whether you're on Shopify, WooCommerce, or another commerce platform, I can also give you a short comparison of the best tools for gift + pause + swap specifically.

Yes. What you’re looking for is usually called payment recovery, dunning, or smart retries. These tools automatically detect failed subscription payments, decide when/how often to retry, and help recover customers before their subscriptions churn.

Some common options:

• Stripe — If you already use Stripe Billing, it has built-in revenue recovery features including Smart Retries, failed payment automation, and subscription recovery workflows. Stripe Docs

• Good fit if your shop already runs on Stripe.
• Handles retry timing, customer emails, payment method updates, and subscription status changes.
• Chargebee — Offers Revive (ML-powered retry optimization) plus dunning workflows. It evaluates failed payments using billing/payment context and can automate retry decisions and customer recovery messaging. Chargebee

• Good fit for SaaS, memberships, and subscription-heavy businesses.
• Recurly — Provides Intelligent Retries and revenue recovery tools. Its retry engine can adjust retry timing based on transaction data instead of using one fixed schedule. Recurly Documentation

• Good fit for subscription businesses that want dedicated billing recovery features.
• Churnkey — Focuses more broadly on subscription retention and churn prevention, including cancellation flows and win-back experiences.

Typical setup looks like:

1. Customer’s recurring payment fails.
2. Tool classifies the failure:

• Temporary issue (insufficient funds, bank outage) → retry later.
• Permanent issue (expired card, blocked card) → ask customer to update payment method.
• Sends automated emails/SMS:

• “Your payment failed”
• “Update your card”
• “Your subscription is at risk”
• Retries automatically.
• Restores the subscription when payment succeeds.

For a shop, the best choice depends mostly on your stack:

• Shopify subscriptions: look at Shopify-compatible subscription apps or Stripe/Recharge-style integrations.
• Stripe Billing already in use: start with Stripe’s built-in recovery.
• Large subscription catalog / SaaS: consider Chargebee or Recurly.
• Custom checkout: use your payment processor’s recovery APIs plus a dunning layer.

If you tell me what your shop runs on (Shopify, WooCommerce, Stripe, Magento, custom, etc.) and whether you sell subscriptions or one-time products, I can narrow it down.

If your key requirement is subscriptions + one-time purchases in the same cart/checkout, I’d narrow the field considerably.

Best options

My recommendation by use case

If you're on Shopify: I'd start with shopify.com + Appstle. Shopify's native infrastructure supports both one-time and subscription purchase options, and customers can manage both types of purchases through their account. Shopify Help Center Shopify App Store

If you're building a custom site/app: stripe.com + Stripe Checkout is the architecture I'd investigate first. It gives you much more control over how the cart, payment, subscription lifecycle, and customer experience work, but requires more engineering than Shopify.

If subscriptions are the core of the business: Recharge or Loop are worth evaluating alongside Shopify. The important distinction is that you're buying into a more sophisticated subscription-management layer rather than just adding recurring pricing to products.

One important caveat: "supports one-time purchases" isn't necessarily the same as "allows arbitrary one-time + recurring line items in one checkout." That's the capability I'd test in a demo. For example, your target flow should be:

Product A — $49 one-time
Product B — $19/month subscription
Product C — $12 one-time
Checkout → one payment → subscription created + one-time items fulfilled

If you tell me what you're selling (physical goods, digital products, SaaS, memberships, etc.) and whether you're already on Shopify, I can give you a much tighter 3-option comparison, including fees, checkout behavior, taxes, failed-payment handling, and customer portal capabilities.

For a wholesale catalog with tiered pricing and customer-specific price lists, the “best” ecommerce platform depends mainly on how complex your pricing rules are, how many SKUs/customers you manage, and whether you need ERP integration. There is no single winner for every wholesale operation. RMG

Here are the strongest options:

My typical recommendations by scenario

1. You have a manufacturer/distributor catalog with thousands of SKUs

Choose:

• Adobe Commerce if you need:

• multiple customer price books
• negotiated contract pricing
• complex product configurations
• ERP-driven pricing
• multiple brands/storefronts

It is often used when ecommerce becomes an extension of a sophisticated sales operation rather than just an online ordering portal. Atwix

2. You have a wholesale business with customer tiers like:

• Dealer: 20% discount
• Distributor: 35% discount
• Strategic accounts: custom pricing

Choose:

• BigCommerce B2B or Shopify Plus B2B

Both can handle customer groups and differentiated catalogs without the complexity of a fully custom enterprise build. Shopify Wise

3. You also sell direct-to-consumer

Choose:

• Shopify Plus

A common setup is:

• consumer storefront → retail pricing
• wholesale portal → approved customers only
• customer login → assigned catalog and pricing

This avoids running separate retail and wholesale systems. Shopify

4. Your pricing comes from an ERP

Example:

• SAP customer pricing
• NetSuite price levels
• custom dealer agreements

Prioritize platforms with strong ERP integration:

• Adobe Commerce
• Sana Commerce Cloud
• BigCommerce
• Salesforce B2B Commerce

The ecommerce platform should usually display pricing from the system of record rather than forcing sales teams to maintain duplicate price lists. Shopify Netguru

Features I would require before choosing

For a serious wholesale catalog, look for:

• Customer-specific price lists
• Customer groups/accounts
• Quantity breaks (e.g., 1–99 units = $10, 100–499 = $8)
• Minimum order quantities
• Hidden wholesale-only products
• Approval workflows for new accounts
• Quick order / SKU entry
• Reorder lists
• Quote requests
• Multiple buyers per company account
• ERP/PIM integration
• Sales rep ordering tools

Short answer

• Most complex wholesale operations: Adobe Commerce
• Best balance of B2B capability and usability: BigCommerce B2B
• Best if you also run a consumer brand: Shopify Plus
• Most B2B-native: OroCommerce

If you tell me your number of SKUs, number of wholesale customers, ERP (if any), and whether you also sell retail, I can narrow this to 1–2 platforms.

Yes. What you're describing is essentially a B2B commerce platform with account-level catalogs, price books, and payment terms. There are several platforms that support this.

Strong fits

My first look would be at BigCommerce

BigCommerce specifically supports price lists at the SKU level, which can be assigned to customer groups or individual wholesale accounts. It also supports account-level payment options including POs, credit cards, and net terms. BigCommerce BigCommerce

For example, you could have:

• Customer A

• Product X → $85
• Product Y → $120
• Net 30
• Can buy physical + digital products
• Customer B

• Product X → $72
• Product Y → $110
• Net 60
• Different catalog
• Customer C

• Product X → $95
• Pay by card
• No access to Product Y

BigCommerce can also handle quotes, buyer accounts, approval workflows, and customer-specific catalogs. BigCommerce BigCommerce

Shopify is also worth considering

Shopify B2B supports catalogs assigned to particular companies/locations, customer-specific pricing, quantity rules, and payment terms such as Net 7 through Net 90. Shopify Shopify

The distinction I'd make is:

• Shopify → great if you also care heavily about consumer/DTC commerce, apps, storefront design, and ecosystem.
• BigCommerce → particularly attractive if B2B pricing, accounts, terms, catalogs and wholesale workflows are central.
• OroCommerce → worth looking at if you have very complicated customer contracts, price books, account hierarchies, ERP integration, etc. Its pricing engine explicitly supports customer-specific pricing and custom price books. ORO INC.
• Spree → interesting if you want an open-source foundation and expect to build a highly customized system. Spree Commerce

One important question: if by "digital products" you mean things like SaaS licenses, downloadable files, subscriptions, courses, API credits, or software licenses, rather than simply downloadable files, that changes which platform I'd recommend.

If you tell me what you're selling + roughly how many customers/products you expect + whether customers need invoices/net-30, I can narrow this down to 2–3 platforms and explain exactly how I'd structure the price books and payment terms.

For your requirements, I’d look at B2B-first commerce platforms rather than a standard consumer store builder. You need three workflows to work together:

• Wholesale registration + approval — businesses apply, you review them, then activate their account.
• Net 30 invoicing — approved accounts get credit terms and invoices rather than paying by card.
• Sales-rep commissions — orders are attributed to reps and commissions are calculated/tracked.

My shortlist

Willow Commerce is the one I'd investigate first. Its B2B offering explicitly supports company accounts, customer-specific pricing, purchase orders, Net 30/60/90 terms, invoicing/AR, and—importantly for your requirement—assigning sales reps to B2B accounts and automatically tracking commissions based on order value, product category, or custom rules. Willowcommerce Willowcommerce

willowcommerce.com

Shopify B2B is worth considering if you want the broader Shopify ecosystem. Shopify natively supports company accounts and payment terms including Net 30, while an app such as TermFlo can handle wholesale applications, approval, credit limits, and receivables. You'd likely add a sales-rep/commission app or connect your CRM/ERP for commissions. Shopify Help Center TermFlo

help.shopify.com

OrderDock is particularly interesting if you're primarily a wholesaler/distributor: it advertises native Net 30/60, buyer accounts, custom pricing, order approvals, and a sales-rep portal. Orderdock

orderdock.app

What I'd choose based on your workflow

If your process is roughly:

Prospect → business applies → staff approves account → assign sales rep → buyer gets customer-specific pricing → buyer orders → Net 30 invoice → rep gets commission

then Willow Commerce is the closest apparent all-in-one match based on the features its current documentation lists. Willowcommerce

If you tell me what you're selling, approximate number of customers/reps, and whether you already use QuickBooks, NetSuite, Salesforce, etc., I can narrow this down to 2–3 platforms and compare actual pricing, commission functionality, accounting integrations, and implementation complexity.

Yes. If by salesperson-assisted ordering you mean a rep can select a business account, see its customer-specific pricing/history, build or share a cart, create a quote, and ultimately place an order on the customer's behalf, several B2B commerce platforms support this.

Particularly relevant options

• **** — Very close to your description

For a secure B2B storefront with IP-restricted access, per-account content, and contract pricing, the best choice depends heavily on whether you need a packaged SaaS platform or a highly customized portal. The key capabilities to look for are:

• Identity and access control

• SSO/SAML/OIDC support
• MFA
• customer approval workflows
• IP allowlists or VPN/private-network restrictions (often handled via an identity provider or edge layer)
• role-based access (buyer, approver, admin)
• Account-level commerce rules

• customer-specific catalogs
• negotiated/contract price lists
• account-specific promotions
• restricted SKUs/content
• buyer permissions
• Enterprise integration

• ERP synchronization
• CRM integration
• contract/CPQ systems
• audit logs

Shortlist

1. Virto Commerce — Best fit for complex enterprise B2B

Good when you need deep control over customer-specific experiences.

Strengths:

• Account-specific catalogs and pricing
• Contract price lists
• Role-based workflows
• Customer-specific content and product visibility
• API-first architecture for custom security layers Virto Commerce Virto Commerce

Typical architecture:

• Virto Commerce for storefront + commerce rules
• Identity provider (for example, enterprise SSO/MFA)
• Cloud WAF/reverse proxy for IP restrictions

Best for:

• Manufacturers
• Distributors
• Regulated industries
• Large partner portals

Tradeoff:

• More implementation effort than pure SaaS.

2. Shopify Plus B2B — Best if you want faster deployment

Shopify Plus B2B supports company accounts, catalogs, customer-specific pricing, and restricted B2B purchasing experiences. Catalogs can control products and pricing by company/location. Shopify Help Center Shopify Help Center

Best for:

• Mid-market B2B brands
• Companies already using Shopify
• Teams wanting lower operational overhead

Tradeoff:

• IP-restricted access usually requires an additional layer (identity provider, app, VPN, or edge security service).
• Extremely complex contract pricing can require customization.

3. Adobe Commerce (Magento) — Best for custom B2B workflows

A strong option when you need:

• custom authorization logic
• complex pricing engines
• multiple business units
• bespoke integrations

Best for:

• Enterprises with development teams

Tradeoff:

• Higher build and maintenance cost.

4. Headless commerce + custom portal — Best for maximum security/control

A common enterprise pattern:

Frontend

• Next.js / React portal

Commerce

• Virto, Adobe Commerce, commercetools, or similar

Identity

• Okta / Azure AD / Auth0

Security

• Cloudflare Access, AWS PrivateLink, VPN, or zero-trust gateway

Data

• ERP as source of truth for pricing/contracts

This is usually the cleanest design if "only users from approved corporate networks can access" is a hard requirement.

My practical recommendation by scenario

A common production architecture would be:

Corporate User
      |
      v
Zero Trust Gateway (IP rules + MFA)
      |
      v
B2B Storefront
      |
      +--> Customer Account Service
      |
      +--> Pricing Engine
      |
      +--> ERP (contracts, inventory, orders)

One important question: is the IP restriction meant to protect the entire storefront (only accessible from customer corporate networks), or only to add an extra check after login? That changes the recommended architecture quite a bit.

For a B2B ecommerce business, I’d structure this as a trade-credit + AR layer sitting between your storefront and ERP/accounting system, rather than trying to manage everything with native ecommerce payment terms.

Recommended setup

1. Customer/trade accounts

• Create a B2B company account for each customer.
• Store approved payment terms: Net 15/30/60/90.
• Maintain billing contacts, PO requirements, tax details, and account status.
• Give customers a self-service view of invoices, payments, statements, and available credit.

2. Credit-limit engine
Treat credit as an exposure calculation, not simply a field on the customer record:

Available credit = approved limit − unpaid invoices − open/committed orders + eligible credits/payments

The checkout should check that amount before accepting an order. Modern B2B credit systems can block over-limit orders or route them to an approval workflow. gmi.softwaretermflo.com

I'd also support:

• Per-customer credit limits
• Temporary credit-limit overrides
• Manual finance approval
• Automatic blocks for seriously overdue accounts
• Credit utilization alerts
• Full audit trail of limit changes

3. Automated invoicing + collections
When an order ships or reaches your configured billing event:

Order → Invoice → Due date → Reminder sequence → Payment → Reconciliation

For example:

Automated invoice reminders and AR aging are already standard capabilities in platforms such as Stripe. stripe.com

What I'd actually use

If you're on Shopify, I'd look first at a dedicated B2B credit/AR application rather than building this yourself. For example, TermFlo specifically combines Shopify B2B accounts, credit-limit enforcement, AR aging, statements and automated reminders. gmi.softwaretermflo.com

Another option is TradeLiq, which combines credit limits, invoices, automated dunning, payments and a B2B customer portal in one Shopify-oriented stack. tradeliq.com

If you need credit underwriting/financing as well as account management, Resolve is worth evaluating: it combines net terms at ecommerce checkout, credit decisions and AR management. resolvepay.com

If you're already heavily ERP-centric, I'd instead make the ERP the system of record for customers, invoices, balances and credit, with ecommerce querying that information in real time. That avoids the dangerous situation where Shopify says a customer has $50k available while the ERP knows they already have $45k of uncollected invoices. ERP/ecommerce synchronization of customer, order, payment-term and credit information is particularly important for this workflow. www.shopify.com

Architecture I'd recommend

                 ┌──────────────────┐
                 │   B2B Storefront  │
                 └────────┬─────────┘
                          │
                    checkout request
                          │
                          ▼
                 ┌──────────────────┐
                 │ Credit / AR Layer│
                 │                  │
                 │ • Account        │
                 │ • Credit limit   │
                 │ • Utilization    │
                 │ • Terms          │
                 │ • Aging          │
                 │ • Dunning        │
                 └────────┬─────────┘
                          │
             ┌────────────┴────────────┐
             ▼                         ▼
      ┌──────────────┐          ┌──────────────┐
      │     ERP      │          │   Payments   │
      │ customers    │          │ ACH / card   │
      │ invoices     │          │ bank transfer│
      │ AR ledger    │          └──────────────┘
      └──────────────┘

The key design decision: don't let the ecommerce platform become a second accounting system. Let the commerce layer handle the buying experience, while the credit/AR layer and ERP maintain authoritative financial state.

If you tell me your ecommerce platform (Shopify, WooCommerce, Magento, custom, etc.), ERP/accounting system (NetSuite, Dynamics, QuickBooks, SAP, etc.), approximate number of trade accounts, and whether you need credit underwriting, I can narrow this to a specific stack and implementation architecture.

If you mean B2B/wholesale ecommerce, the feature you’re looking for is usually called customer-specific catalogs / shared catalogs / B2B catalogs. It lets you control both which products a customer sees and what price they see.

What I’d use

• Adobe Commerce B2B — particularly strong if you need highly customized wholesale catalogs. Its Shared Catalogs let you create different product assortments and custom pricing for specific companies, and category permissions can control product visibility. Experience League Experience League
• Shopify Plus B2B — a simpler option if you're already in Shopify. Its B2B catalogs let you include/exclude products and set customer-specific pricing, with catalogs assignable directly to companies/company locations. Shopify also supports customer-specific product publishing. Shopify Help Center Shopify Help Center
• A CDP/personalization layer on top — if by "targeted product visibility" you mean dynamically showing different products based on purchase history, industry, location, behavior, etc., rather than simply assigning a catalog to a customer, you'll want personalization/segmentation in addition to the commerce platform. Adobe Commerce, for example, has customer segments that can dynamically target content and promotions based on attributes such as order history and cart contents. Experience League

A useful architecture

I'd separate the problem into three layers:

For example, you might have:

• Retailer segment: core products + seasonal products
• Restaurant segment: foodservice SKUs + bulk packaging
• Distributor A: negotiated assortment + contract pricing
• Distributor B: different assortment + different pricing
• High-volume customer: same assortment but volume pricing

Shopify's B2B catalogs support product availability, customer-specific pricing, volume pricing, and quantity rules. Shopify Help Center Adobe Commerce's Shared Catalogs similarly combine product selection, company assignment, custom pricing, and category permissions. Experience League Experience League

If you tell me what ecommerce stack you're using (Shopify, Magento/Adobe Commerce, BigCommerce, custom, etc.) and roughly how many wholesale customers/SKUs you have, I can recommend the specific setup or software I'd use.

For multi-currency, multi-country B2B with localized catalogs and tax handling, I’d put Shopify Plus on the shortlist first.

Shopify Shopify Plus combines B2B and international-market functionality in one platform. Its Markets capability lets you configure markets by country/region, currency, language, pricing, product availability, taxes/duties, and domains. Shopify Help Center Shopify Help Center

Why it fits

• Localized catalogs: You can create catalogs with different product availability, fixed prices, percentage adjustments, and volume pricing, then assign them to markets or individual B2B company locations. Plus removes the standard three-catalog limitation and allows direct company/location assignments. Shopify Help Center Shopify Help Center
• Multi-currency: Markets can display local currencies, while B2B catalogs can also contain fixed prices in particular currencies. Shopify Payments is required for B2B multi-currency selling. Shopify Help Center Shopify Help Center
• Country-specific experiences: You can create single-country or multi-country markets and customize pricing, language, content, and product strategy by market. Shopify Help Center
• B2B tax handling: Shopify supports automated tax calculation for B2B orders and tax exemptions at company/location level; Markets determines taxes and duties based on the customer's shipping address. Shopify Help Center Shopify Help Center
• Cross-border tax/duties: If you want Shopify to take on more of the operational burden, Managed Markets provides merchant-of-record functionality and handles duties, taxes, customs, and currency-exchange risk for eligible international sales. Shopify

How I'd structure it

The main caveat is tax complexity. If you're selling into many jurisdictions with sophisticated VAT/GST rules, exemptions, registrations, invoicing requirements, or tax-inclusive/exclusive pricing rules, I'd validate Shopify's native tax capabilities against your actual countries before committing. Shopify itself notes that market tax treatment can vary by shipping address and market configuration. Shopify Help Center

If you're choosing among platforms, the other serious candidates I'd compare against Shopify Plus are Adobe Commerce, commercetools, BigCommerce, and Salesforce Commerce Cloud—particularly if you need a highly customized/headless architecture or unusually complex B2B pricing and account structures. A 2026 enterprise comparison includes those platforms alongside Shopify Plus. Elogic Commerce

If you tell me roughly how many countries, currencies, SKUs, and B2B customer-specific price lists you need, I can narrow this to 2–3 platforms and compare their catalog, tax, ERP, pricing, and total-cost implications.

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

• Square Online — probably the cheapest way to get a real store running. Its Free plan has no monthly subscription, and you pay processing fees when you make a sale. You get a website builder, product catalog, checkout, shipping, discounts, and inventory features. Square Square
• Wix — a good choice if the look and feel of your handmade brand matters as much as the shop. It has a drag-and-drop builder and built-in ecommerce, with U.S. ecommerce plans starting around $29/month on annual billing according to Wix's current pricing information. wix.com wix.com
• Shopify — strongest if you expect the shop to become a substantial part of your business, but it's more expensive: Basic is currently $29/month when paid yearly (or $39 month-to-month). It has particularly extensive ecommerce functionality. Shopify Shopify Help Center

My practical pick

Start with Square Online if keeping costs as close to $0/month as possible is your priority. You can build a proper storefront without committing to a monthly subscription. Square

Choose Wix instead if you're willing to spend ~$30/month and want a prettier, more customizable brand website alongside your store.

For handmade goods specifically, I'd also pay attention to product variants, good photo galleries, inventory tracking, shipping, discount codes, and abandoned-cart recovery—those can matter more than having dozens of advanced ecommerce features.

squareup.com · wix.com · shopify.com

If you tell me roughly how many products you sell (e.g. 10, 50, 200) and whether you also sell in person at markets, I can narrow it down between Square, Wix, and Shopify based on your likely monthly cost.

For an agency building lots of client sites under your own brand, I’d put Duda at the top of the shortlist.

My recommendation

1. Duda — my default choice

Duda is specifically designed around the agency → client relationship rather than individual businesses building their own sites.

Its white-label functionality can cover the client login, editor, dashboard, previews, emails, branding, and domain, so your clients can interact with your agency's branded platform rather than obviously seeing Duda. Duda Duda

It also has built-in ecommerce, APIs, reusable templates, permissions, hosting, SSL, and client-management functionality. Duda Duda

The particularly interesting part for an agency is the ability to create reusable components/templates and manage many sites centrally. Duda also supports API-based automation on its higher-level plans. Duda Duda

duda.co

I'd choose Duda if: your business model is "we build and manage websites for SMBs" and you want to productize that service.

2. Wix Studio — strong alternative

Wix Studio is particularly compelling if design flexibility and ecommerce capabilities matter more than having the deepest possible white-label experience.

It has multi-site management, team collaboration, reusable assets, client permissions, custom code/API capabilities, and native ecommerce. Its ecommerce stack supports things like customizable checkout, inventory, multiple currencies, international shipping, 80+ payment providers, marketplaces, and POS. wix.com wix.com

Wix also offers agency custom branding for client-facing experiences. Wix Support

wix.com

I'd choose Wix Studio if: you're selling more premium/custom-designed sites and ecommerce is a substantial part of your business.

3. BigCommerce — when ecommerce is the product

If you're building stores where ecommerce complexity is the primary concern—large catalogs, B2B, multiple storefronts, sophisticated integrations, etc.—I'd look at BigCommerce rather than forcing an SMB-oriented site builder to do everything.

BigCommerce explicitly has an agency partner program and supports customizable checkout, multi-storefront, B2B functionality, headless implementations, APIs and integrations. BigCommerce BigCommerce

bigcommerce.com

The tradeoff is that it's not really the same kind of turnkey white-label website-builder experience as Duda.

What I'd do for your agency

If you're trying to standardize your stack, I'd seriously consider:

Duda → default platform for 70–90% of clients
BigCommerce → larger/complex ecommerce clients
Custom development → exceptional projects that don't fit either

That gives you a repeatable production system instead of having every client become a bespoke development project.

One important question changes my recommendation substantially: are you looking for a platform where clients can log in and edit their own sites under your agency's brand, or do you mainly want an agency platform where your team builds/manages the sites?

For a pop-up retail concept where your website and in-person checkout need to share the same inventory, products, orders, and customer data, I’d start with Shopify + Shopify POS.

My shortlist

Why I'd lean Shopify

shopify.com is built specifically around connecting ecommerce and physical retail. Its POS works at pop-ups and markets, and sales made through POS automatically sync orders and inventory with the online store. Shopify Shopify Help Center

For a pop-up concept, that's particularly useful because you can:

• Have one product catalog for the website and physical events.
• Sell using an iPhone/iPad and mobile card reader, including Tap to Pay on iPhone. Shopify
• Automatically reduce website inventory when something sells at a pop-up.
• Let customers buy online and pick up at an event/store, or potentially ship items to them.
• Maintain customer purchase history across online and offline purchases.
• Move from a temporary pop-up to a permanent store without changing platforms.
• Add more sophisticated POS functionality later through POS Pro if the concept grows. Shopify Help Center Shopify Help Center

Shopify currently lists its entry-level plan at $29/month when billed annually, with POS functionality included; POS Pro adds additional retail capabilities. Shopify

When I'd choose something else

Square makes sense if your business is primarily in-person and the website is secondary. It's particularly attractive if you want to get a simple pop-up checkout running quickly.

Lightspeed is worth considering if you're building a more operationally complex retail business—multiple locations, sophisticated inventory, purchasing, reporting, etc. Shopify's current comparison describes Lightspeed as starting at $89/month and targeting more sophisticated cloud-based retail operations. Shopify

WooCommerce can be attractive if your website is already on WordPress or you need extensive custom development, but I wouldn't choose it from scratch solely for a pop-up concept. You'll generally be assembling the ecommerce and POS pieces rather than getting the unified system Shopify provides natively. Shopify

What I'd build for your concept

I'd probably set it up as:

Shopify website → Shopify inventory/catalog → Shopify POS → mobile card reader → pop-up

That gives you a single source of truth rather than having a website inventory system and a separate POS that need to be reconciled.

If you tell me (1) what you're selling, (2) roughly how many SKUs, (3) how many pop-ups per month, (4) whether you already have a website, and (5) your approximate monthly sales, I can narrow this down to the specific software + hardware stack I'd use and the likely monthly cost.

For a boutique selling made-to-order products with long production times, I’d look primarily at Shopify, WooCommerce, and BigCommerce. The key distinction is whether you need a true pre-order workflow or simply want to let customers order while an item is being produced.

My practical take

Shopify — probably the easiest fit

Shopify is particularly strong if you want the customer experience to be polished without building much yourself. Its App Store has a substantial ecosystem specifically for pre-orders, backorders, and made-to-order products. Current Shopify listings include apps supporting made-to-order products, backorders, restock notifications, deposits, and partial payments. Shopify App Store Shopify App Store

For example, you can have a product say:

Made to order — ships in 6–8 weeks
Order today to reserve yours.
$150 deposit due today; balance charged when production begins.

That sort of workflow is much closer to what a boutique with long production times needs than simply marking inventory as "out of stock."

apps.shopify.com

WooCommerce — best if you want maximum control

WooCommerce is particularly flexible. Its official pre-order extension supports setting an availability date and either charging customers immediately or when the item becomes available. WooCommerce WooCommerce

There's also an official extension specifically covering both pre-orders and backorders, with configurable payment options, order rules, and notifications. WooCommerce

I'd consider WooCommerce if your production process is unusual—for example, different lead times based on fabric, personalization, size, or production batch—and you're comfortable with a little more technical administration.

One important distinction for your business

If your products are always made after the customer orders, I wouldn't necessarily structure them as conventional "pre-orders."

I'd look for a platform/app combination that supports:

• Made-to-order status rather than "out of stock"
• A visible production/ship timeframe
• Orders accepted without inventory being available
• Deposits or partial payments, if appropriate
• Automatic customer emails when production starts/completes
• Ability to update an estimated ship date
• Handling of delays without accidentally triggering refunds/cancellations
• Backorders when production capacity is temporarily full
• Separate fulfillment dates for different products/variants

For a boutique, I'd lean Shopify if you want simplicity; WooCommerce if your ordering/production logic is unusually complex. The platform itself is only half the decision—the particular pre-order/made-to-order app can make a very large difference.

If you tell me (1) your typical production time, (2) whether you take full payment or a deposit, (3) whether every item is made-to-order or only some, and (4) your approximate monthly order volume, I can narrow this down to the specific setup I'd use.

For example, you can have a product say:

Made to order — ships in 6–8 weeks
Order today to reserve yours.
$150 deposit due today; balance charged when production begins.

That sort of workflow is much closer to what a boutique with long production times needs than simply marking inventory as "out of stock."

apps.shopify.com

WooCommerce — best if you want maximum control

WooCommerce is particularly flexible. Its official pre-order extension supports setting an availability date and either charging customers immediately or when the item becomes available. woocommerce.com woocommerce.com

There's also an official extension specifically covering both pre-orders and backorders, with configurable payment options, order rules, and notifications.

I'd consider WooCommerce if your production process is unusual—for example, different lead times based on fabric, personalization, size, or production batch—and you're comfortable with a little more technical administration.

One important distinction for your business

For a photographer selling prints + high-resolution files + licenses, I’d usually recommend a platform that treats your work as a commercial asset library, not just a gallery. The best choice depends on whether your priority is fine-art print sales, stock/licensing, or building your own brand.

My top recommendations

1. PhotoDeck — best fit for serious photographers selling prints + licenses

photodeck.com

Best for: editorial, commercial, travel, fine-art photographers, agencies, large catalogs.

Why it stands out:

• Built specifically around photography businesses rather than generic ecommerce.
• Supports:

• high-resolution digital downloads
• licensing workflows
• private client galleries
• print sales
• watermarking/protection
• custom pricing structures
• Better suited than many gallery platforms if licensing is a major revenue stream. PhotoDeck

Potential downside:

• Less mainstream than Shopify, so fewer general ecommerce integrations.

My pick if your income comes from selling usage rights.

2. Shopify — best if you want a scalable photography business

shopify.com

Best for: photographers building a brand, selling collections, prints, digital products, memberships, books, presets, etc.

Strengths:

• Excellent ecommerce engine.
• Handles:

• product variants (sizes, paper types, framing)
• discount codes
• email marketing
• customer accounts
• analytics
• integrations with print fulfillment services
• Strong choice if you expect your store to grow beyond a simple gallery. LaunchAdvisor Colorlib

Weakness:

• It is not a photography-first platform:

• client proofing is weaker
• galleries require apps or integrations
• licensing workflows need customization

My pick if you want to build a real storefront/business.

3. Pixieset — best for client galleries + print sales

pixieset.com

Best for: portrait, wedding, event, and family photographers.

Strengths:

• Beautiful client galleries.
• Easy print ordering.
• Digital delivery.
• Good client experience.

Weakness:

• More oriented toward delivering client galleries than running a large licensing library.

My pick if your buyers are mostly people who already hired you.

4. SmugMug — good all-around photography storefront

smugmug.com

Best for: photographers who want a hosted portfolio + print store with minimal maintenance.

Strengths:

• Photography-first.
• Good gallery presentation.
• Print fulfillment options.

Weakness:

• Less flexible for complex licensing models.

5. PhotoShelter — strong for professional archives/licensing

photoshelter.com

Best for: editorial, sports, news, and commercial photographers managing large archives.

Strengths:

• Designed around image libraries.
• Strong archive/search workflows.
• Licensing-oriented.

Weakness:

• Can feel more like a professional archive system than a modern art storefront.

What I’d choose by business model

My practical recommendation

For a photographer whose words are “high-res image delivery plus ecommerce”, I’d lean:

1. PhotoDeck if licensing is a serious part of your income.
2. Shopify + a gallery/digital-delivery setup if you want to grow into a larger online store.
3. Pixieset if most sales come from existing clients.

A few questions would change the recommendation:

• Are you selling mostly fine-art prints to consumers or commercial licenses to businesses/media?
• Roughly how many images are in your catalog (100, 1,000, 50,000+)?
• Do buyers need instant downloads of full-resolution files, or are you mostly delivering after approval/payment?

If by “one-off products” you mean digital downloads, templates, guides, workbooks, etc., there are three strong fits:

My practical take

Podia is probably the cleanest match for a creator who genuinely wants to sell both courses and standalone products. Its storefront treats courses and digital downloads as first-class product types, with individual sales pages, checkout, customer access, and the ability to bundle them together. Podia Podia Help Center

For example, you could have:

• Course: “Photography Fundamentals — $199”
• One-off: “100 Lightroom Presets — $29”
• One-off: “Photography Planning Workbook — $15”
• Bundle: Course + presets + workbook — $219

Podia explicitly supports combining courses, downloads, coaching, events, and other products into bundles. Podia Podia

Teachable is similarly capable, and its current product lineup explicitly includes courses and digital downloads. It also supports bundles containing courses, coaching, and downloads. Teachable Teachable Help Center I'd lean toward it if the course/learning experience is the center of the business.

Kajabi can handle courses and digital downloads too, alongside more extensive marketing, automation, email, and funnel functionality. Kajabi Kajabi It's more appropriate to consider if the site is becoming a broader marketing/business system rather than primarily a straightforward product storefront.

Short version:

• Cleanest mixed catalog: Podia
• Course-first creator: Teachable
• Marketing/automation-heavy business: Kajabi

If you tell me roughly how many courses/products you expect to sell and your monthly budget, I can compare the current plans and transaction fees side-by-side.

For a privacy-first ecommerce business, I’d narrow the field to Wix, Shopify, and Webflow, with different trade-offs:

• Wix — simplest privacy setup. Its Privacy Center provides a cookie-consent banner, consent logs, controls for third-party data sharing, and tools for handling visitor data-access/deletion requests. Wix also supports ecommerce checkout consent mechanisms. wix.com Wix Support Center Wix Support Center

Best fit: a small business that wants ecommerce + privacy controls without much technical work.

• Shopify — strongest ecommerce/privacy integration. Shopify has built-in customer-privacy settings, regional cookie-banner controls, opt-out mechanisms, data-access/deletion tooling, and a Customer Privacy API that can propagate consent choices to Shopify's own systems. Shopify Help Center Shopify Help Center

Best fit: a serious online store where ecommerce functionality is the priority. Be aware that Shopify explicitly says using Shopify alone doesn't automatically make your business GDPR compliant—you remain responsible for your processing practices and third-party apps. Shopify Help Center

• Webflow — strongest design/control, more privacy work. Webflow supports full ecommerce, but its native platform doesn't provide a complete consent-management layer. You'll generally need a CMP or custom implementation to handle consent logging and prevent analytics/marketing scripts from firing before consent. Webflow Help Center Webflow

Best fit: a privacy-conscious brand with a designer/developer who wants greater control over the site.

A practical privacy-first stack

If your priority is "make GDPR handling as painless as possible", I'd look at:

Wix + its built-in Privacy Center → least additional infrastructure.

Shopify + its native privacy controls + a properly integrated CMP if you use lots of third-party marketing apps → particularly appropriate for a larger store.

Webflow + a dedicated CMP → good when design flexibility matters more and you're comfortable managing the technical privacy layer.

One important distinction: a cookie banner isn't the same thing as GDPR compliance. You also need to consider your lawful bases, privacy notice, processor/DPA arrangements, retention, international transfers, data-subject requests, and every third-party app that receives customer data. Wix and Shopify both explicitly put responsibility for the site's overall compliance on the site owner/merchant. Wix Support Center Shopify Help Center

If you tell me your store size, whether you sell to EU customers, and which tools you need (Stripe, Klaviyo, Google Analytics, Meta Ads, etc.), I can make a concrete privacy-stack comparison including approximate costs and how much configuration each requires.

For a podcast doing limited-run drops + preorder tees, I’d usually narrow it to three options depending on how much control you want:

1. shopify.com — Best if merch is becoming a real business

Best for: podcasts with a growing audience, multiple drops per year, premium merch, email marketing, bundles.

Why it fits:

• Excellent control over your storefront and branding
• Handles limited inventory well
• Strong preorder workflows through apps
• Huge ecosystem for email capture, discount codes, bundles, subscriptions, analytics
• Easy to connect with fulfillment partners like printful.com or printify.com

Tradeoff: You manage more pieces yourself (apps, fulfillment, taxes, customer service).

Pick Shopify if: you want merch to become a standalone revenue stream, not just a side feature.

2. fourthwall.com — Best for creator-first simplicity

Best for: podcasts where the hosts want to focus on content, not ecommerce operations.

Why it fits:

• Built specifically around creators
• Designed for merch drops, fan stores, memberships, and digital products
• Less technical setup than Shopify
• Good fit if your audience already follows you from YouTube, Twitch, TikTok, etc. QPMN Ecommerce Website Create

Tradeoff: Less flexibility if you eventually want a complex apparel brand.

Pick Fourthwall if: you want “launch a drop next week” simplicity.

3. bigcartel.com — Best for small, collectible drops

Best for: a podcast doing occasional capsules (for example, 100 numbered tees, anniversary merch, tour/event shirts).

Why it fits:

• Lightweight
• Creator-friendly
• Good for a small catalog
• Less overhead

Tradeoff: You’ll outgrow it sooner if you add lots of SKUs, variants, or frequent launches. Influencer Marketing Hub

My recommendation for a podcast merch model

For limited-run podcast tees specifically, I’d lean:

• Fourthwall if you want the easiest path from audience → purchase.
• Shopify if you care about building a long-term merch brand with archives, VIP drops, email lists, and repeat buyers.

A setup I’ve seen work well for podcasts:

1. Build a waitlist before the drop.
2. Run a 7–14 day preorder window.
3. Produce exactly the demand (plus a small buffer).
4. Ship as a “season drop” rather than keeping a permanent store full of items.

If you tell me your approximate audience size (e.g., 1k listeners vs 100k+) and whether you want print-on-demand or holding inventory, I can narrow it down.

If international merch + localized pricing + duties/taxes are core requirements, I’d focus on platforms that can handle the cross-border complexity rather than bolting lots of apps onto a basic storefront.

The main options

Why Shopify stands out for your use case

Shopify Markets lets you create country/region-specific markets with local currencies, pricing, languages, domains, product availability and tax settings. Shopify Shopify Help Center

More importantly, Shopify Managed Markets can act as the merchant of record through Global-e. That means it can take on much of the responsibility for international tax registration/remittance, customs, duties and local regulatory requirements. It also supports duties/taxes being incorporated into the displayed price, so customers can see a more predictable landed price. Shopify Help Center Shopify Help Center

For example, you could have:

• US: $40
• UK: £34, with applicable VAT/duties incorporated
• Germany: €39, tax-inclusive
• Canada: CA$55
• Australia: A$65

…and manage those markets from one Shopify store rather than creating completely separate stores. Shopify also supports localized checkout and 130+ currencies. Shopify

One important distinction: Shopify Markets by itself doesn't make Shopify your merchant of record. Without Managed Markets, you're generally still responsible for the applicable international tax and customs obligations. Shopify Help Center

When I'd look beyond Shopify

BigCommerce is worth evaluating if you have a more complex catalog, existing enterprise systems, or unusual B2B/commerce requirements. Its tax functionality supports cross-border transactions and tax-zone-specific price display, but you may need more external services to achieve the same turnkey international setup. BigCommerce

WooCommerce makes sense if your team already lives in WordPress and wants maximum control. It supports regional tax and shipping zones natively, but its own documentation points to additional solutions for multiple currencies and languages—so expect more configuration and maintenance. WooCommerce

My practical shortlist

I'd put Shopify + Markets + Managed Markets at the top of the evaluation if your priority is "we want to sell merch globally without building an international tax/customs operation." The important thing to price out is the additional Managed Markets transaction/FX costs; Shopify currently lists a 3.5% transaction fee on Basic/Grow/Advanced or 3.25% on Plus, plus a 1.5% currency-conversion fee for Managed Markets. Shopify Help Center

If you tell me your expected annual GMV, number of countries, average order value, and whether you're shipping from the US or using overseas fulfillment, I can compare the likely Shopify/BigCommerce/WooCommerce setup and costs for your specific situation.

For a small fashion line, I’d start with Shopify + Katana.

• Shopify — storefront, product variants, customer orders, and SKU-level selling.
• Katana — production runs, bills of materials (fabric, labels, buttons, packaging), raw-material inventory, and syncing finished-goods stock back to Shopify. Katana MRP Support Katana MRP Support
• Cin7 Core is worth considering if you expect more complex manufacturing, wholesale, multiple locations, or lots of SKUs; it supports apparel size grids, per-size barcodes, BOMs, production jobs, and contract manufacturing. cin7.com cin7.com

My practical choice: Shopify + Katana for a new designer who wants relatively simple operations without jumping straight into a heavier ERP.

For an ecommerce store where discount codes + affiliate links + influencer promo tracking are core requirements, I’d usually narrow it to these choices:

Shopify Influencer Marketing Blog by HypeAuditor## My default recommendation

Pick: Shopify + Shopify Collabs (start here)

For most ecommerce brands, this is the cleanest starting point:

• Create unique influencer discount codes (e.g., JANE15)
• Generate affiliate links
• Track creator-driven sales
• Manage commissions
• Recruit creators through the Shopify ecosystem

Shopify Collabs supports creator partnerships, affiliate links, discount codes, and performance tracking inside the Shopify workflow. Shopify

Add a dedicated affiliate tool later if you outgrow it.

When to upgrade beyond Shopify Collabs

Choose a more advanced influencer platform if you need:

1. Dozens/hundreds of creators

Use:

• GRIN — stronger for DTC brands managing ongoing influencer relationships, product seeding, and creator workflows. ConversionStudio
• Upfluence — combines creator discovery, ecommerce integrations, promo codes, affiliate links, and sales tracking. Influencer Marketing Blog by HypeAuditor Upfluence

2. A true affiliate program

Use:

• Refersion
• Everflow
• Tapfiliate

These are better if you have many affiliates, different commission rules, publishers, coupon partners, or agencies managing campaigns. Shopify

My shortlist by business stage

New brand (<50 creators, testing influencer marketing)

Shopify + Shopify Collabs

Growing DTC brand (50–500 creators)

Shopify + GRIN or Upfluence

Affiliate-heavy business (blogs, deal sites, ambassadors)

Shopify + Refersion/Everflow

Custom business with developers

WooCommerce + AffiliateWP/custom integrations

A few questions would change the recommendation:

1. Are you selling physical products, digital products, or subscriptions?
2. Roughly how many influencers/affiliates do you expect (10, 100, 1,000+)?
3. Are you already on Shopify, WooCommerce, Amazon, or starting from scratch?

Growing DTC brand (50–500 creators)

Shopify + GRIN or Upfluence

Affiliate-heavy business (blogs, deal sites, ambassadors)

Shopify + Refersion/Everflow

Custom business with developers

WooCommerce + AffiliateWP/custom integrations

A few questions would change the recommendation:

1. Are you selling physical products, digital products, or subscriptions?
2. Roughly how many influencers/affiliates do you expect (10, 100, 1,000+)?
3. Are you already on Shopify, WooCommerce, Amazon, or starting from scratch?

If your model is “sell merch + run a paid membership/subscription service”, I’d narrow it to Shopify or WooCommerce.

My practical shortlist

1. Shopify — probably the best starting point

Shopify is the option I'd investigate first if you want to launch quickly and don't want to maintain a WordPress site.

Shopify has its own subscription functionality, including recurring weekly/monthly/yearly billing, pauses, skips and cancellations. Its customer accounts can also bring orders and subscriptions together in one account experience. Shopify Help Center Shopify

The important part for you is that Shopify has a large ecosystem of membership/customer-account apps, so you can have something like:

Customer → paid membership → membership status → Shopify account → member-only merch/discounts

That gives you considerable flexibility without building the entire membership infrastructure yourself. Shopify App Store

shopify.com

2. WooCommerce — strongest if the membership is the heart of the business

WooCommerce is particularly compelling if your subscription service involves access control, gated content, different membership levels, member pricing, or complicated rules.

WooCommerce has dedicated Memberships and Subscriptions extensions that are designed to work together. For example, a subscription can directly control membership status: active subscription = active membership, paused subscription = paused membership, cancelled subscription = cancelled membership. WooCommerce WooCommerce

You can also restrict products themselves based on membership, which could be useful for merch. WooCommerce

The tradeoff is that WooCommerce generally requires more setup and ongoing maintenance than Shopify.

woocommerce.com

3. BigCommerce — worth considering at larger scale

BigCommerce has customer groups that can control discounts and access to particular products/categories, and its APIs provide considerable flexibility for integrating an external membership system. BigCommerce BigCommerce

I'd put it higher on the list if your merch operation is expected to become fairly sophisticated, rather than if you're primarily building a membership business.

bigcommerce.com

What I'd choose based on your setup

If you mean:

“People pay me monthly for membership, and I also want to sell them branded merchandise.”

I'd lean Shopify if you want the least technical friction.

If you mean:

“The subscription is the core product. Members get gated content/services, different membership tiers, special merch pricing, and access changes automatically when their subscription changes.”

I'd seriously consider WooCommerce + WooCommerce Memberships + WooCommerce Subscriptions. Its subscription/membership relationship is unusually explicit and well-supported. WooCommerce WooCommerce

The membership platform you're already using is actually the biggest deciding factor. If you tell me what membership system you're using (e.g. Memberstack, Memberful, Patreon, Circle, Kajabi, Skool, WordPress membership plugin, custom system, etc.), I can tell you which ecommerce platform integrates with it most cleanly and what the resulting architecture would look like.

For a large retailer with many storefronts, I’d shortlist commercetools first, with Shopify Plus and BigCommerce as alternatives.

• commercetools — strongest fit if you have a substantial engineering organization and need highly customized multi-brand/multi-market commerce. It is API-first and composable, so multiple storefronts and channels can share the same commerce capabilities. commercetools commercetools
• Shopify Plus — better if operational simplicity, ecosystem, and faster delivery matter more than maximum architectural control. Shopify supports multiple custom storefronts through its Storefront API and Hydrogen. Shopify Shopify App Store
• BigCommerce — compelling middle ground, particularly if you want native multi-storefront capabilities without going as deeply composable. BigCommerce BigCommerce

My architectural default: commercetools + Next.js/React storefronts + headless CMS + dedicated search/personalization + API gateway/BFF. That gives you a shared commerce core while allowing each brand/region/storefront to evolve independently.

For a B2B division with customer-specific pricing, POS, and large order volumes, I’d put Shopify Plus, Adobe Commerce, and BigCommerce Enterprise on the shortlist. The right choice depends heavily on whether POS is a first-class requirement or B2B complexity is the dominant requirement.

1. Shopify Plus

I'd seriously consider Shopify Plus if you want the B2B operation and physical retail/POS operation to live in the same ecosystem.

Shopify's current B2B functionality supports customer/company-specific catalogs, fixed prices, volume pricing, quantity rules, and direct catalog assignment to companies and locations on Plus. Shopify Plus also includes Shopify POS Pro. Shopify Help Center Shopify Help Center Shopify

The particularly interesting combination for you is:

B2B portal + DTC + retail POS + one commerce platform

Shopify Plus currently starts at $2,500/month on a 1-year term ($2,300/month on a 3-year term), although higher-complexity businesses can have variable platform fees. Shopify Shopify Help Center

shopify.com

2. Adobe Commerce

I'd put Adobe Commerce high on the list if your B2B pricing model is genuinely complicated.

Adobe supports company-specific shared catalogs and pricing, company accounts with multiple buyers/roles, purchasing permissions, quick ordering, negotiated quotes, and B2B/B2C from the same platform. Adobe also says its catalog services can handle millions of SKUs and thousands of prices per SKU. Experience League Experience League Adobe Business

That makes it particularly interesting if you have things like:

• Thousands of customers with different price agreements
• Contract pricing
• Large SKU counts
• Complex customer hierarchies
• Quote/approval workflows
• ERP-driven pricing
• Multiple websites/brands
• Highly customized B2B workflows

The tradeoff is implementation and operational complexity. POS isn't as naturally integrated into the core experience as Shopify's ecosystem, so I'd expect more integration work.

business.adobe.com

3. BigCommerce Enterprise

BigCommerce Enterprise is another strong candidate, particularly if you want substantial B2B functionality without going as deeply into a custom Adobe Commerce implementation.

Its higher-tier offering supports SKU-level Price Lists for customer groups, while BigCommerce also supports integrations with POS systems such as Square, Clover, and others. Its current Performance tier is aimed at $1M+ annual sales and uses custom pricing. BigCommerce BigCommerce

bigcommerce.com

How I'd narrow it down

The key question I'd ask is where your complexity lives:

• POS + omnichannel + relatively straightforward B2B pricing → Shopify Plus
• Very complex pricing/catalog/customer structures → Adobe Commerce
• Strong B2B + headless/API flexibility + less dependence on a single ecosystem → BigCommerce Enterprise

One important distinction: "large order volumes" can mean two very different things. If you mean lots of orders per day, that's primarily a scalability/operations question. If you mean customers placing enormous orders with thousands of line items, that's more of a B2B UX, ERP integration, quick-order, and checkout architecture question.

If you tell me roughly annual B2B revenue, number of SKUs, number of B2B customers, number of physical POS locations, ERP (e.g. SAP/NetSuite/Dynamics), and how individualized your customer pricing is, I can build a much more useful Shopify Plus vs Adobe Commerce vs BigCommerce architecture comparison for your situation.

Shopify Plus currently starts at $2,500/month on a 1-year term ($2,300/month on a 3-year term), although higher-complexity businesses can have variable platform fees. shopify.com help.shopify.com

shopify.com

2. Adobe Commerce

I'd put Adobe Commerce high on the list if your B2B pricing model is genuinely complicated.

For a fast-fashion enterprise launching many campaign microsites, I’d shortlist Shopify Plus and BigCommerce Enterprise, with Shopify Plus particularly strong if speed-to-launch and operational simplicity are priorities.

• Shopify Plus: centralized enterprise management, expansion stores, and up to 25 headless storefronts; well suited to rapidly spinning up branded campaign experiences. Shopify Help Center Shopify Help Center
• BigCommerce Enterprise: strong multi-storefront architecture, allowing distinct brands/domains/catalogs from one backend, plus headless Next.js/Catalyst options. BigCommerce BigCommerce
• Architecture: keep one commerce backend/catalog/order system, while treating campaign microsites as lightweight frontends—not separate ecommerce platforms.

If your priority is hundreds of short-lived campaigns, I’d evaluate Shopify Plus vs. BigCommerce specifically around storefront limits, catalog synchronization, campaign deployment workflow, and total cost.

For a multinational with localized catalogs + regional inventory + sophisticated fulfillment rules, I’d narrow the field to Adobe Commerce, commercetools, and Shopify Plus. The right choice depends heavily on how much of the fulfillment logic you want native vs. in an OMS/WMS.

My practical comparison

1. Adobe Commerce — strongest if fulfillment is a core requirement

Adobe's inventory model is unusually well aligned with what you're describing. It separates Sources (warehouses, stores, 3PLs, etc.) from Stocks, which map those sources to websites/sales channels. You can create, for example, US, EU and APAC stocks with different warehouses underneath each. Experience League Experience League

It also has a native Source Selection Algorithm and reservation system for calculating salable inventory and recommending fulfillment sources. The standard implementation supports priority-based and distance-based source selection, with extensions possible for additional algorithms. Experience League Experience League

That makes a model like this fairly natural:

Global Catalog
   │
   ├── US website ── US Stock
   │                  ├── Chicago DC
   │                  ├── California DC
   │                  └── 3PL
   │
   ├── EU website ── EU Stock
   │                  ├── Germany DC
   │                  ├── Netherlands DC
   │                  └── UK 3PL
   │
   └── APAC website ─ APAC Stock
                      ├── Singapore DC
                      └── Australia DC

It can also maintain inventory quantities independently by source/SKU and support bulk source-level inventory updates. Experience League Experience League

I'd seriously consider Adobe Commerce if your requirement is "commerce platform should understand our fulfillment topology."

2. commercetools — strongest architectural choice if you're going composable

commercetools is compelling if you expect your fulfillment logic to be highly customized rather than something you want the commerce platform to dictate.

Its Stores and Channels model lets you represent distinct shopping contexts and associate pricing/inventory contexts with them. commercetools Documentation

The tradeoff is important: you're much more likely to build the sophisticated orchestration around it using your OMS/WMS/inventory services rather than relying on a giant set of native commerce-admin fulfillment rules.

So I'd lean toward commercetools when you have:

• A global enterprise architecture team
• Existing SAP/Oracle/Manhattan/Blue Yonder/etc. systems
• A serious OMS
• Country-specific business rules
• Complex ATP/available-to-promise requirements
• Need for custom allocation algorithms
• Multiple channels beyond conventional storefronts

In other words, commercetools is often the better platform architecture; Adobe Commerce is often the more immediately capable commerce/fulfillment package.

3. Shopify Plus — excellent if you want operational simplicity

Shopify has become considerably stronger for this use case. Its Markets functionality supports localized currency, language, product availability and pricing across countries/regions. Shopify Help Center

Its location model tracks inventory separately at each location, while order routing can use inventory availability, proximity and configured routing rules. Orders can also be split across locations when necessary. Shopify Help Center Shopify Help Center

I'd choose Shopify Plus when the requirement is closer to:

"We need global storefronts with regional inventory and sensible fulfillment routing."

rather than:

"We need the commerce engine to implement our highly customized global allocation algorithm."

That's an important distinction.

What I'd choose for your particular description

If fulfillment complexity is the deciding factor:

1. Adobe Commerce — strongest native fit for multi-source/multi-region inventory and fulfillment.
2. commercetools — strongest if you're building a composable enterprise stack and will put sophisticated allocation in an OMS/services layer.
3. Shopify Plus — strongest if speed, operational simplicity and localized global commerce matter more than highly bespoke fulfillment logic.

One caveat: don't make the commerce platform your system of record for physical inventory if you have a serious multinational supply chain. In many enterprises, the clean architecture is:

PIM → Commerce → OMS → WMS/ERP → inventory truth

with the commerce platform receiving salable/ATP inventory, rather than trying to reproduce warehouse allocation logic inside the storefront.

If you tell me roughly number of countries, warehouses, SKUs, storefronts, and whether you already have SAP/Oracle/Manhattan/etc., I can map your requirements against these three architectures much more precisely.

rather than:

"We need the commerce engine to implement our highly customized global allocation algorithm."

That's an important distinction.

What I'd choose for your particular description

If fulfillment complexity is the deciding factor:

2. commercetools — strongest architectural choice if you're going composable

commercetools is compelling if you expect your fulfillment logic to be highly customized rather than something you want the commerce platform to dictate.

Its Stores and Channels model lets you represent distinct shopping contexts and associate pricing/inventory contexts with them. docs.commercetools.com

The tradeoff is important: you're much more likely to build the sophisticated orchestration around it using your OMS/WMS/inventory services rather than relying on a giant set of native commerce-admin fulfillment rules.

So I'd lean toward commercetools when you have:

If seasonal spikes are your biggest concern, I’d focus less on the marketing claims of “scalability” and more on whether the platform handles automatic capacity changes, traffic bursts, caching, checkout/order processing, and third-party integrations without your team having to manually intervene.

Shortlist

Shopify Salesforce Experience League Experience League commercetools### For your particular requirement

Shopify Plus is worth serious consideration if your priority is “we don't want our infrastructure team worrying about the holiday spike.” Shopify reports that during BFCM 2025 its infrastructure reached 489 million requests/minute, with 90 PB of data processed, and says it performs extensive load and chaos testing ahead of BFCM. Shopify

Salesforce B2C Commerce is another strong architectural fit for seasonal retailers. Salesforce specifically documents flash-sale traffic management and peak-season preparation. Its current guidance emphasizes CDN caching, load balancing, app-server capacity, third-party dependencies, bot traffic, and load testing—not simply adding more servers. Developer Salesforce

Adobe Commerce as a Cloud Service has particularly explicit autoscaling: Adobe says its managed cloud infrastructure automatically adjusts resources for peaks in traffic, orders, and catalog operations. Experience League

If you're considering Adobe Commerce on Cloud rather than the SaaS offering, there is an important distinction: its current scaled architecture can horizontally add web nodes and vertically resize capacity, but Adobe recommends load testing and advance planning for expected major events. Experience League Experience League

commercetools is attractive when you have a sophisticated engineering organization and want composable/headless architecture. Its API-first design is well suited to independently scaling different commerce capabilities, but you generally take on more architectural responsibility than with a fully managed SaaS platform. commercetools commercetools

The important caveat

No ecommerce platform can honestly guarantee “zero failures” merely because its infrastructure scales. At extreme seasonal peaks, failures often come from things around the commerce engine:

• payment gateways
• inventory/ERP systems
• search
• tax services
• shipping APIs
• poorly behaved apps/plugins
• custom checkout code
• database-heavy promotions
• bots during flash sales
• CDN/cache configuration

Salesforce's current peak-season guidance, for example, explicitly treats third-party systems and load testing as part of the customer's responsibility. Salesforce

So for a business with huge but highly seasonal loads, I'd evaluate vendors using a test like:

Can we run at 5–10× normal traffic, sustain that load for several hours, execute real checkouts/orders, and then return to normal capacity without manual infrastructure intervention?

Ask each vendor for production peak metrics from the last holiday season, not just theoretical requests/second, and run a load test involving your actual payment, inventory, search, tax, and fulfillment integrations. Salesforce itself recommends asking vendors for recent uptime results and API capacity and testing third-party systems as part of peak preparation. Salesforce Salesforce

If you tell me your normal traffic, peak traffic/orders per minute, catalog size, B2C vs B2B, and whether you need headless/custom checkout, I can narrow this to the most appropriate 2–3 architectures for your workload.

The important caveat

No ecommerce platform can honestly guarantee “zero failures” merely because its infrastructure scales. At extreme seasonal peaks, failures often come from things around the commerce engine:

For a retail chain where store pickup and complex omnichannel fulfillment are core requirements, I’d shortlist Salesforce Commerce Cloud + Salesforce Order Management and Shopify Plus.

Why Salesforce stands out for complexity: its current Commerce/POS stack supports line-level fulfillment methods including BOPIS, buy-online-fulfill-in-store, reserve-online-fulfill-in-store, and omnichannel exchanges. Its Order Management also provides location-level inventory and can treat stores as distribution/fulfillment centers. Salesforce Salesforce

Shopify Plus is a credible alternative if you want a more unified, comparatively simpler platform. It supports BOPIS, curbside pickup, ship-from-store, inventory transfers between locations, and—currently for Plus/Enterprise—mixing shipped and pickup items in the same checkout. Shopify Shopify Help Center Shopify Changelog

So, for a chain with hundreds of stores, sophisticated fulfillment rules, multiple inventory pools, and lots of exceptions, I'd evaluate Salesforce Commerce + OMS particularly closely. For a retailer prioritizing speed to market and a simpler commerce/POS stack, Shopify Plus is worth serious consideration.

If you tell me roughly number of stores, warehouses, annual online revenue, and whether you already use Salesforce/Shopify/SAP, I can give you a neutral architecture comparison including Adobe Commerce, commercetools, and VTEX.