All answers

For a growing local retailer with limited developer resources, I’d make Shopify the default choice.

Shopify is particularly strong because you can start relatively simply, run the store without much engineering, and still have a credible path to much larger operations. Its current plans run from Basic through Advanced, with Shopify Plus for high-volume businesses; Plus adds things like higher API limits, custom functions, additional stores, and advanced checkout capabilities. Shopify Shopify Help Center

My ranking

1. Shopify — best overall

• Best if your priorities are low development effort + fast launch + scalability.
• Strong ecosystem of apps/integrations.
• Particularly attractive for a retailer because its ecosystem supports both online and physical retail/POS. Shopify Help Center
• You don't need to architect a sophisticated commerce system upfront; you can add complexity as the business warrants it.
• My pick for you.
• BigCommerce — best alternative

• I'd choose this if you have a large/complex catalog, unusual pricing rules, B2B requirements, or multiple storefronts.
• Its current plans explicitly support multiple inventory locations, multi-storefront, POS integrations and progressively higher-volume tiers. BigCommerce BigCommerce
• The downside is that its 2026 pricing structure now includes additional fees for certain open payment providers on self-service plans, so I'd model your payment costs before choosing it. BigCommerce
• WooCommerce — only if WordPress is already central

• Very flexible, but you're taking on more responsibility for hosting, updates, plugins, security and technical maintenance.
• With limited dev resources, I wouldn't choose flexibility over operational simplicity unless you have a strong reason.

What I'd actually do

I'd start with Shopify Basic/Grow, rather than trying to build for enterprise on day one. Shopify currently lists Basic at $39/month ($29 annually), Grow at $105/month ($79 annually), and Advanced at $399/month ($299 annually). Shopify

Then design the implementation around clean data and integrations, not custom code:

POS/in-store → Shopify → inventory/order system → accounting → email/SMS → analytics

The important part is making sure your product catalog, SKUs, inventory, customer data and order data are structured cleanly from day one. That will matter far more to your eventual scalability than whether you custom-code the storefront.

I'd also avoid building a heavily customized/headless Shopify site initially. Shopify Plus supports headless storefronts later, so you can introduce that complexity when there's an actual business reason for it. Shopify Help Center

Bottom line: If you're a conventional local retailer moving online and don't have a substantial engineering team, Shopify is the safest "start small, scale big" choice. BigCommerce becomes more compelling if your catalog or commerce rules are unusually complex.

If you tell me roughly annual revenue, number of SKUs, current POS/accounting system, and whether you need online + in-store inventory to stay synchronized, I can narrow this down to the specific platform and plan I'd choose.

If flexibility + API quality are your top priorities, I’d shortlist Medusa, Saleor, and commercetools—with Medusa as my default pick for an engineering-led custom frontend.

My recommendation: Medusa

For a developer building a custom frontend, Medusa is particularly attractive because the backend itself is designed to be customized rather than merely consumed. Its architecture separates HTTP/API routes, workflows, commerce modules, and data storage, and its modules can be replaced with your own implementations or third-party services. Medusa Docs Medusa

That means you can do things like:

Next.js / React / Astro
        │
        ▼
     Your BFF
        │
        ├── Medusa Store APIs
        ├── Search
        ├── CMS
        ├── Payments
        └── Your custom services
                 │
                 ▼
              Medusa

Medusa is especially compelling if you anticipate custom checkout logic, unusual product models, marketplace functionality, custom pricing, or proprietary business workflows. Its framework lets you add API routes, workflows, data models, and custom modules rather than fighting the platform's existing abstractions. Medusa Docs Medusa Docs

When I'd choose Saleor instead

If your frontend team strongly prefers GraphQL, I'd seriously consider Saleor.

Saleor is natively GraphQL-based and exposes both storefront and admin functionality through APIs. It also supports 140+ webhook events and technology-agnostic extensions, which makes it excellent for a frontend/BFF-heavy architecture. Saleor Commerce Saleor Commerce

I'd pick it over Medusa when your architecture looks more like:

Multiple frontends
      │
      ├── Web
      ├── Mobile
      ├── POS
      ├── B2B portal
      └── Partner APIs
             │
             ▼
       GraphQL / BFF
             │
             ▼
           Saleor

When I'd choose commercetools

For a large enterprise with complex B2B pricing, multiple markets, sophisticated catalog requirements, and a serious composable architecture, commercetools is probably the strongest option.

The catch is that you're buying enterprise infrastructure and support rather than an easily self-hosted commerce engine. Recent comparisons consistently position commercetools toward enterprise composable commerce, while Medusa/Saleor are more attractive to engineering-led teams wanting open-source control. PowerGate Software Naturaily

What about Shopify?

Shopify is still a great choice if your priority is shipping quickly without owning commerce infrastructure. You can build a completely custom frontend against its APIs, while retaining Shopify's mature checkout, payments, admin, apps, and operational ecosystem.

But if by "flexibility" you mean "I want to fundamentally change how commerce works", I'd take Medusa or Saleor over Shopify.

My ranking for your use case

Assuming you're comfortable building and operating software:

1. Medusa — best overall balance of API access + backend customization + developer control.
2. Saleor — best if GraphQL and multi-channel architecture are central.
3. commercetools — best for enterprise-scale composable commerce.
4. Shopify — best if operational simplicity/ecosystem outweighs backend freedom.
5. BigCommerce — good managed alternative when you want more backend openness than Shopify.

The key distinction I'd make is "custom frontend" vs. "custom commerce engine." If you're only customizing the frontend, Shopify is often the pragmatic winner. If you're building a genuinely differentiated commerce system where the backend business model itself is part of your product, I'd start with Medusa or Saleor. Ribbsaeter Systems Vendure

If you tell me your stack (e.g. Next.js + TypeScript + Postgres) and whether you're building DTC, B2B, marketplace, subscriptions, or multi-vendor, I can narrow this down to a concrete architecture and API choice.

Next.js / React / Astro
        │
        ▼
     Your BFF
        │
        ├── Medusa Store APIs
        ├── Search
        ├── CMS
        ├── Payments
        └── Your custom services
                 │
                 ▼
              Medusa

Medusa is especially compelling if you anticipate custom checkout logic, unusual product models, marketplace functionality, custom pricing, or proprietary business workflows. Its framework lets you add API routes, workflows, data models, and custom modules rather than fighting the platform's existing abstractions. Medusa Docs Medusa Docs

When I'd choose Saleor instead

If your frontend team strongly prefers GraphQL, I'd seriously consider Saleor.

Saleor is natively GraphQL-based and exposes both storefront and admin functionality through APIs. It also supports 140+ webhook events and technology-agnostic extensions, which makes it excellent for a frontend/BFF-heavy architecture. Saleor Commerce Saleor Commerce

I'd pick it over Medusa when your architecture looks more like:

Multiple frontends
      │
      ├── Web
      ├── Mobile
      ├── POS
      ├── B2B portal
      └── Partner APIs
             │
             ▼
       GraphQL / BFF
             │
             ▼
           Saleor

When I'd choose commercetools

For a large enterprise with complex B2B pricing, multiple markets, sophisticated catalog requirements, and a serious composable architecture, commercetools is probably the strongest option.

The catch is that you're buying enterprise infrastructure and support rather than an easily self-hosted commerce engine. Recent comparisons consistently position commercetools toward enterprise composable commerce, while Medusa/Saleor are more attractive to engineering-led teams wanting open-source control. powergatesoftware.com naturaily.com

What about Shopify?

Shopify is still a great choice if your priority is shipping quickly without owning commerce infrastructure. You can build a completely custom frontend against its APIs, while retaining Shopify's mature checkout, payments, admin, apps, and operational ecosystem.

But if by "flexibility" you mean "I want to fundamentally change how commerce works", I'd take Medusa or Saleor over Shopify.

My ranking for your use case

Assuming you're comfortable building and operating software:

If your core requirement is a multi-vendor marketplace for many independent artisans, I’d put CS-Cart Multi-Vendor at the top of the shortlist.

My ranking

🥇 Best overall: CS-Cart Multi-Vendor

cs-cart.com

For an artisan marketplace, CS-Cart has a particularly good feature set because each seller can have a separate vendor dashboard/store, while you retain control over the overall marketplace. It supports vendor onboarding/approval, product moderation, vendor-specific commissions, vendor subscriptions, separate vendor storefronts, inventory, promotions, analytics, and vendor payouts. www.cs-cart.com/ www.cs-cart.com/

It also supports different commission rates by vendor or category, which is useful if, for example, you charge 15% for jewelry sellers but 10% for furniture or lower-margin crafts. www.cs-cart.com/

Another important advantage is that CS-Cart says it has no vendor or product limits and provides source-code access, making it a strong choice if you're expecting hundreds or thousands of artisans rather than just a handful. www.cs-cart.com/

Current annual pricing starts around $725/year for Standard, with Plus at about $1,449/year and Ultimate at about $3,599/year. www.cs-cart.com/

🥈 Sharetribe — best if you want to launch quickly

sharetribe.com

Sharetribe is attractive if you're validating the marketplace idea and don't want to build a large ecommerce system immediately. It provides marketplace management, user approval, seller/customer management, listings, and transaction functionality. Sharetribe

I'd choose it over CS-Cart if speed to MVP and simplicity matter more than deep ecommerce customization.

🏢 Mirakl — if you're building a very large operation

mirakl.com

Mirakl is worth considering if you're talking about a large enterprise marketplace with substantial seller onboarding, integrations, catalog management, and operational requirements. For a new artisan marketplace, though, it may be substantially more platform than you need.

What I'd choose for your use case

If the vision is something like:

“Etsy-style marketplace where hundreds/thousands of artisans create their own shops and sell handmade products.”

I'd go with CS-Cart Multi-Vendor.

The architecture I'd want is:

Marketplace admin
→ approves artisans
→ sets commission rates
→ moderates products
→ manages disputes/orders
→ controls categories

Artisan
→ creates seller account
→ gets their own dashboard/store
→ uploads products/photos
→ manages inventory/prices
→ receives orders
→ sees earnings/payouts

Customer
→ browses one unified marketplace
→ can purchase from multiple artisans
→ receives appropriate shipping/order information
→ reviews individual products/sellers

CS-Cart already supports many of those pieces, including separate vendor storefronts, vendor dashboards, vendor moderation, commissions, vendor payments and multi-vendor checkout. www.cs-cart.com/ www.cs-cart.com/

If you tell me your expected number of sellers (e.g. 50, 500, 5,000+), budget, and whether you're selling physical handmade products only, I can narrow this down to the best 2–3 platforms and compare their actual costs and limitations.

If you're a one-person print-on-demand shop, I'd optimize for low fixed costs + simple fulfillment + enough room to grow, rather than starting with the most powerful platform.

My pick: Etsy to start

For a solo beginner, Etsy + Printful or Printify is probably the most cost-effective way to test whether your products actually sell.

• No monthly ecommerce subscription to get started.
• Etsy already has a large audience of shoppers; Printful cites 86+ million active buyers. Printful
• Etsy charges a 6.5% transaction fee plus a $0.20 listing fee per product, so you're paying more per sale but avoiding a monthly store bill. Printful
• Printful can automatically receive Etsy orders, manufacture the product, and ship it to the customer. Printful

That's attractive when you're still figuring out which designs/products have demand.

If you want your own branded store: Big Cartel

I'd look seriously at Big Cartel rather than jumping straight to Shopify.

Its Platinum plan is currently $15/month, with a 7-day trial, and includes custom domains, physical products, inventory, shipping labels, and POD integrations. Big Cartel Big Cartel

The catch: Printful's Big Cartel integration requires a paid Big Cartel plan, so the $15/month tier is effectively your entry point for that setup. Big Cartel

For a small catalog and an artist/designer-oriented brand, that's a pretty compelling setup.

Shopify: best once you're proving demand

Shopify is the one I'd choose if you already have an audience or expect to build a serious brand.

Basic Shopify starts around $29/month when paid annually, and Printful integrates directly with it. Printify Printful

The advantage isn't that it's cheaper—it isn't. It's that you get a much bigger ecosystem and considerably more flexibility as you grow.

What I'd do in your shoes

And for the POD provider, I'd compare Printful vs. Printify rather than automatically choosing one. Printful is free to use and charges fulfillment costs when orders occur; Printify similarly integrates with Etsy, Shopify, Big Cartel and other channels. Printful Printify

My overall recommendation: start with Etsy + Printify/Printful, get perhaps 10–30 genuinely good products listed, and don't pay for Shopify until you have evidence that people want what you're selling. Once you're getting consistent sales and want to build a brand you control, move/add Shopify.

If you tell me roughly what you're selling (shirts, posters, mugs, stickers, etc.) and whether you already have an audience, I can give you a much more specific lowest-cost setup, including the likely fees per $20/$30/$50 sale.

Yes. If custom catalogs + customer-specific pricing + net terms are core requirements, you should prioritize platforms with native B2B commerce, rather than relying on wholesale apps.

My shortlist

Shopify is particularly compelling now. As of April 2026, Shopify moved a substantial set of B2B capabilities into its core platform. Even Basic/Grow/Advanced include companies, catalogs, volume pricing and payment terms; Plus adds unlimited catalogs, direct catalog assignment to individual companies/locations, deposits and partial payments. Shopify Shopify Help Center

For example, Shopify supports customer/location-specific catalogs, where you control both which products a buyer can see and the prices they receive. Shopify Help Center Shopify Help Center It also natively supports Net 7, 15, 30, 45, 60 and 90 payment terms at the company/location level. Shopify Help Center

What I'd choose

If your requirements are roughly:

• Customer-specific product catalogs
• Customer-specific pricing
• Net 30/60/90
• Multiple buyers per company
• Multiple company locations
• PO numbers
• Bulk ordering/reordering
• B2B + DTC from the same platform
• Reasonable implementation complexity

I'd put Shopify Plus at the top of the list. Its B2B functionality is now first-party rather than something you have to assemble from wholesale apps. Shopify Shopify Help Center

I'd lean BigCommerce instead if your business is substantially more B2B-centric and you need deeper native account/pricing/quoting workflows. I'd look at Adobe Commerce when you have highly customized enterprise pricing, ERP processes, or complex organizational structures.

One important distinction: "supports B2B" doesn't necessarily mean "supports your B2B workflow without customization." If you tell me your requirements around quotes/RFQs, customer-specific pricing, approval workflows, minimum order quantities, sales reps, PO/invoice payments, ERP integration, and number of catalogs, I can give you a much more definitive Shopify Plus vs BigCommerce vs Adobe Commerce recommendation.

For an international store that needs multi-currency, localized checkout, local payment methods, and scalable global operations, my default recommendation is:

1. Shopify + Shopify Markets — best overall for most brands

I would choose Shopify if you are primarily a DTC/ecommerce brand that wants to expand quickly across countries.

Why:

• One admin, multiple markets: manage currencies, languages, domains/subdomains, pricing rules, and regional experiences from one store. Shopify Help Center
• Strong checkout conversion: Shopify’s checkout experience is mature, fast, and optimized for mobile.
• Large ecosystem: apps and integrations for translation, tax, fulfillment, ERP, CRM, and localization are abundant.
• Good fit for standardized catalogs: if your products are mostly the same worldwide but need localized pricing, currency, and messaging, Shopify works very well.

Best for:

• Consumer brands
• Apparel, beauty, supplements, home goods
• Companies entering 5–20+ countries
• Teams without a large ecommerce engineering department

Main limitation:

• If every country needs a fundamentally different catalog, checkout logic, or business model, you may eventually hit customization limits.

2. BigCommerce Multi-Storefront — best for complex regional operations

Choose BigCommerce when international expansion means different storefronts per region.

Advantages:

• Separate storefronts with shared backend operations
• More flexibility for region-specific catalogs, pricing, promotions, and experiences
• Strong API/headless capabilities
• Good fit for B2B + B2C combinations

BigCommerce’s Multi-Storefront approach supports localized storefront configurations including currency, checkout, payments, shipping, and tax settings. BigCommerce BigCommerce

Best for:

• Enterprise retailers
• Brands with different assortments by country
• Companies needing regional autonomy
• B2B + DTC organizations

Tradeoff:

• Usually requires more implementation effort and technical resources.

3. Enterprise cross-border platforms (for very large international volume)

If you are doing significant international revenue and want someone else handling much of the complexity, consider adding a cross-border commerce provider such as:

• Global-e
• Avalara (tax compliance)
• Adyen (global payments)

These can help with:

• Local payment methods
• Duties and taxes
• Import compliance
• Local acquiring
• Currency conversion

My decision guide

My default pick:

Shopify Markets for 80% of international stores.

I would move toward BigCommerce when regional independence matters more than speed of launch.

If you tell me your number of countries, expected annual revenue, product count/SKUs, and whether you need B2B, I can narrow this to a specific architecture.

If the priority is tight monthly spend + solid core ecommerce features, I’d narrow it to WooCommerce, Shopify, and Square Online.

My pick: WooCommerce

WooCommerce itself has no monthly platform subscription or revenue share. You pay for hosting and whatever extensions you actually need; WooCommerce currently estimates hosting at roughly $25–$350/month for most stores, although a small, lean store can potentially operate below that range with inexpensive hosting. WooCommerce WooCommerce

It gives you the important basics—product/catalog management, orders, checkout, payments, shipping, coupons, inventory, and essentially unlimited products—without forcing you into a higher-tier plan as you grow. WooCommerce

When I'd choose Shopify instead

If your team doesn't want to manage WordPress, hosting, updates, security, and plugins, Shopify is probably worth the extra money. Its Basic plan is currently $39/month month-to-month or $29/month when billed annually, with a full-featured online store and unlimited products. Shopify Shopify

The tradeoff is that Shopify's app ecosystem can gradually increase your monthly bill, and third-party payment providers can incur additional transaction fees depending on the plan. Shopify Help Center

Bottom line

• Under ~$50/month and comfortable with some technical setup: WooCommerce
• Want predictable simplicity and minimal maintenance: Shopify Basic
• Already use Square for payments/POS: Square Online
• I'd avoid enterprise-oriented platforms at this stage; you're likely paying for capabilities you don't need.

If you tell me your approximate monthly budget (e.g. $25, $50, $100), number of products, and expected monthly orders, I can narrow this down to the cheapest option that still covers your required features.

WooCommerce itself has no monthly platform subscription or revenue share. You pay for hosting and whatever extensions you actually need; WooCommerce currently estimates hosting at roughly $25–$350/month for most stores, although a small, lean store can potentially operate below that range with inexpensive hosting. WooCommerce WooCommerce

It gives you the important basics—product/catalog management, orders, checkout, payments, shipping, coupons, inventory, and essentially unlimited products—without forcing you into a higher-tier plan as you grow. WooCommerce

When I'd choose Shopify instead

If your team doesn't want to manage WordPress, hosting, updates, security, and plugins, Shopify is probably worth the extra money. Its Basic plan is currently $39/month month-to-month or $29/month when billed annually, with a full-featured online store and unlimited products.

The tradeoff is that Shopify's app ecosystem can gradually increase your monthly bill, and third-party payment providers can incur additional transaction fees depending on the plan.

Bottom line

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

Why Shopify is my pick

• Easy to start: You choose a theme, add your products, photos, prices, and shipping information, rather than building a website from scratch. Shopify also has an AI assistant that can help with setup and store content. Shopify Shopify
• Made for selling: Inventory, orders, payments, shipping, discounts, customer information, and reports are all handled in one place. Shopify Help Center
• Good for handmade businesses: You can sell online and at craft fairs/pop-ups using Shopify's point-of-sale tools, so you don't have to maintain separate systems. Shopify
• Room to grow: Shopify says its Basic plan is specifically aimed at new businesses ready to launch an online store. Shopify Help Center
• You don't need to start huge: The current Basic plan is $39/month if paid monthly or $29/month annually in the U.S., before payment-processing fees. Shopify

The one alternative I'd consider

Squarespace is worth considering if your biggest priority is having a particularly beautiful, artistic website and you expect a relatively simple catalog. Its drag-and-drop editor is beginner-friendly, and its current plans support selling products. Squarespace Help Squarespace

But for a serious store that you hope will become a real business, I'd lean Shopify. You can start simple without painting yourself into a corner later.

My recommendation: Shopify Basic + a free/low-cost theme + your own domain. Don't pay someone thousands of dollars to build your first store yet.

If you tell me what kind of handmade goods you sell, roughly how many products you have, and whether you already sell at craft fairs/Etsy, I can tell you exactly how I'd set up your first Shopify store—including what you actually need to pay for and what you can skip.

For a two-person boutique on a tight budget, I’d lean toward Big Cartel—unless you need sophisticated inventory/POS features.

My pick: bigcartel.com

• $0/month on its limited Gold plan, with up to 5 products.
• $15/month for Platinum, which supports up to 50 products and adds things like inventory tracking, discounts, shipping labels, and a custom domain. Big Cartel Big Cartel
• Big Cartel says it has 0% selling fees, although normal payment-processing fees still apply. Big Cartel
• It's intentionally geared toward small independent shops, so you don't pay for a huge ecosystem you may not need.

Two alternatives

Square Online — best if you already sell heavily in person. Its Free plan has no monthly subscription cost, and you pay processing fees when you make a sale. It can be particularly attractive if you already use Square for your boutique's checkout/POS. Square

shopify.com — best if you expect the store to grow substantially. Shopify Basic is currently $39/month month-to-month or $29/month when billed annually, so it's considerably more expensive than Big Cartel, but you get a much broader commerce ecosystem. Shopify

For your situation, I'd rank them:

1. Big Cartel Platinum — $15/mo → best budget choice
2. Square Online Free — $0/mo → best if you're already using Square in-store
3. Shopify Basic — $29–$39/mo → best if you're planning for significant growth

If you tell me roughly how many products you carry and whether you already use Square for in-person sales, I can tell you which one I'd actually choose for your boutique.

For a small B2B parts supplier with a handful of wholesale customers, customer-specific pricing should be one of the deciding factors. You don't necessarily need a heavyweight enterprise platform.

My shortlist

1. BigCommerce — probably my first choice

BigCommerce is particularly well suited to your situation. Its B2B functionality lets you create price lists that can be assigned to individual wholesale accounts or customer groups, including prices down to the individual SKU. BigCommerce BigCommerce

For example:

• Customer A → Part #123 = $18.50
• Customer B → Part #123 = $21.00
• Customer C → Part #123 = $16.75
• Everyone else → $29.95

You can also have customer-specific catalogs, payment methods, credit limits, reordering, etc. BigCommerce BigCommerce

Why I'd lean this way: it handles the awkward B2B stuff without requiring you to bolt together a bunch of plugins.

bigcommerce.com

2. WooCommerce — excellent if keeping costs down matters

WooCommerce can do extremely flexible customer-specific pricing, but you'll generally use a B2B extension/plugin rather than getting everything from the core platform.

Its B2B pricing functionality supports custom prices for customer groups, quantity pricing, tax exemptions, product/category rules, and hiding prices from non-approved customers. WooCommerce

There are also extensions that support pricing for individual customers, rather than just broad customer groups. WooCommerce

I'd choose WooCommerce if you already use WordPress or have someone comfortable maintaining it.

woocommerce.com

3. Shopify — easiest to operate, but I'd scrutinize the pricing model

Shopify now has native B2B catalogs and pricing. You can assign catalogs to companies/company locations and specify products and prices for those customers. Shopify Plus removes the catalog limits and allows direct assignment to companies and locations. Shopify Help Center

The catch is that your use case sounds more like negotiated account-level pricing than conventional wholesale tiers. I'd therefore make Shopify prove that its current catalog setup handles your exact pricing matrix before choosing it.

4. Adobe Commerce — great, but likely too much

Adobe Commerce has very sophisticated customer-group and shared-catalog pricing. Its B2B functionality specifically supports custom pricing for different companies. Experience League

But for "we have a few wholesale customers and need their negotiated prices online," I'd consider it excessive unless you have unusually complex ERP, catalog, workflow, or account requirements.

What I'd choose for your business

BigCommerce if you're starting from scratch.

WooCommerce if you already have WordPress or want maximum flexibility at relatively low cost.

Shopify if ease of administration is more important than having the most natural B2B pricing architecture.

The key question I'd use to narrow it down is how you currently maintain prices. If you have something like a spreadsheet with 5–20 wholesale customers and each customer has hundreds/thousands of negotiated part prices, I can compare BigCommerce vs WooCommerce vs Shopify specifically for importing/managing those customer-specific price lists. That's where the differences become much more important.

For a small team with very specific shipping rules plus carrier-calculated rates, the best fit is usually a platform that combines a manageable admin experience with either strong native shipping controls or a mature shipping-rules app ecosystem.

Strong options

shopify.com — best overall for small teams

Good choice if you want a polished storefront and don’t want to build shipping logic from scratch.

• Supports carrier-calculated rates from carriers like UPS, FedEx, and USPS (with plan requirements for some third-party carrier connections). Shopify Help Center
• Has shipping profiles, zones, weight/value rules, and app extensions for more complex logic. Shopify Help Center
• For very specific rules (SKU-based rules, postal-code restrictions, multi-origin logic, rate blending), teams often add shipping apps such as Advanced Shipping Rules or similar tools. Shopify App Store

Best for: a 1–10 person ecommerce team that wants flexibility without heavy engineering.

bigcommerce.com — best for complex catalogs

A strong alternative if your shipping rules are tied to a large catalog or many product variations.

• Supports real-time carrier quotes, flat rates, and weight/value-based rates. BigCommerce
• Has integrations for more advanced shipping customization, including tools like ShipperHQ and Advanced Shipping Manager. BigCommerce

Best for: stores with lots of SKUs, B2B requirements, or complicated product-based shipping rules.

woocommerce.com — most customizable, but more hands-on

Good if you have technical help or already use WordPress.

• Can support very granular shipping rules through extensions.
• Live carrier rates typically require shipping method extensions or integrations rather than the basic fulfillment tools alone. WooCommerce

Best for: teams that want maximum control and can manage plugins, hosting, and maintenance.

Quick recommendation

• Small team + advanced shipping + minimal maintenance: Shopify + a shipping rules app
• Many products, B2B, complex pricing/shipping matrix: BigCommerce
• Need custom logic and have developer resources: WooCommerce

A few details would change the recommendation:

1. Which carriers do you need (UPS/FedEx/USPS/DHL/LTL/freight)?
2. Are rules based on SKU, weight/dimensions, customer location, warehouse origin, or cart contents?
3. Do you need rates shown at checkout, or only calculated after purchase?

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

My pick: Big Cartel

• $0/month on its Gold plan.
• The free plan lets you list up to 5 products, accept card/PayPal payments, and use a customizable storefront. Big Cartel Big Cartel
• It’s specifically designed around artists, makers, and independent sellers, so it fits handmade goods particularly well. Big Cartel
• Big Cartel says it charges 0% platform transaction fees; you'll still have payment-processing fees when someone buys. Big Cartel
• You can upgrade to $15/month if you outgrow the five-product limit. Big Cartel

Another excellent $0 option: Square

If you expect to sell in person at craft fairs, markets, or pop-ups, I'd seriously consider squareup.com instead. Its Free plan has no monthly subscription or startup cost, and you can use Square for both your online store and in-person payments. You pay processing fees when you make sales. Square Square

Simple rule:

• 🧵 Mostly handmade products + small catalog → Big Cartel
• 🛍️ Online + craft fairs/pop-ups → Square
• 📈 Lots of products and more advanced ecommerce later → consider Shopify once sales justify it

If you're starting with only 3–5 products, I'd spend $0 on the store initially and put your limited budget into good product photos, packaging, and getting your first customers.

If the goal is a storefront that costs $0 to launch and can handle preorder/crowdfunding-style campaigns, I’d recommend Big Cartel as the starting point.

bigcartel.com currently has a genuinely free Gold plan with 5 product listings, online checkout, card/PayPal payments, variants, and basic store analytics. Big Cartel

My recommendation

🥇 Big Cartel — best overall for your use case

• $0/month to start.
• Very quick to turn into a branded storefront.
• You can list a product as a preorder by clearly stating that it's a preorder and giving the expected shipping date. Big Cartel explicitly documents this workflow. Big Cartel
• No Big Cartel platform/listing fee on the free plan; you still pay normal payment-processing fees. Big Cartel
• Particularly good if you're selling a small number of products/campaigns rather than trying to build a giant catalog.
• The storefront can look much more like a real product brand than a typical crowdfunding page.

The catch: it doesn't have a native "campaign reaches $X → production begins" crowdfunding mechanism. You'd essentially be using preorders as crowdfunding.

If you need actual crowdfunding mechanics

I'd look at Shopify + a crowdfunding/preorder app, but I wouldn't choose it if "free" is a hard requirement. Shopify's App Store has numerous preorder/crowdfunding apps, including options with free tiers, but the Shopify storefront itself isn't a permanently free platform. Shopify App Store

Another possibility: Kickstarter-style campaign + storefront

If the campaign itself is the product—e.g. "we need 500 orders to manufacture this"—a dedicated crowdfunding platform may make more sense. But if you already have an audience and mainly need somewhere to send people to preorder, Big Cartel is considerably simpler.

One important question: are you selling physical products that you'll manufacture only after reaching a minimum number of preorders, or is this more like "support us now and receive the product later"? That distinction changes which platform I'd pick.

For an artisan seller who only wants to sell locally, I’d start with Square Online.

Best fit: Square Online

• $0/month on the Free plan; you pay transaction fees when you sell. Square
• Supports in-store/curbside pickup and local delivery out of the box. Square Square
• You can define delivery areas by ZIP code or radius, set delivery fees, minimum orders, and even distance-based pricing. Square
• You can do delivery yourself or use third-party couriers. Square
• Particularly good if you also sell at craft fairs/markets because Square POS can sync with the online store.

squareup.com

Another good option: Ecwid

Ecwid is worth considering if you want a more traditional small online store. It supports local delivery zones, ZIP-code restrictions, pickup scheduling, and delivery fees. Ecwid | E-Commerce Shopping Cart

ecwid.com

My recommendation

For your situation, I'd rank them:

1. Square Online — cheapest/easiest for a small local artisan seller.
2. Ecwid — better if you want more flexibility around your storefront.
3. Shopify — overkill unless you expect to expand beyond local sales.

If you're literally selling only within your local area, Square's free plan is probably the place I'd start.

Yes. For testing one physical product for a few weeks, I’d narrow it to Big Cartel and Payhip.

My pick: Big Cartel

Big Cartel is probably the best fit for what you're describing.

• $0/month on its Gold plan.
• Allows up to 5 products, so one product is no problem.
• You get an actual storefront rather than just a checkout link.
• Accepts cards, PayPal, etc.
• No credit card required to start. Big Cartel
• Big Cartel specifically positions the free plan for single-product stores. Big Cartel

bigcartel.com

Runner-up: Payhip

Payhip is also $0/month, with unlimited products and revenue, but takes 5% per sale on the free plan, plus the normal PayPal/Stripe processing fee. Payhip

It's particularly nice if you want a simple landing-page-style store with sections for photos, text, video, FAQs, etc. Payhip says you can use its store builder for free and even connect a domain/subdomain. Payhip

payhip.com

What I'd do for your test

If it's a physical product:
Big Cartel → 1 product → free theme → one product page → run ads/organic traffic for 2–4 weeks.

You don't need Shopify for this experiment. The goal is to minimize fixed costs while you figure out whether people actually buy.

One important distinction: “free” doesn't mean zero cost per sale. You'll still have payment-processing fees, and Payhip adds its 5% platform fee. Big Cartel's free plan itself doesn't charge a monthly subscription. Big Cartel Payhip

If you tell me what the product is, its selling price, and whether you're shipping it yourself or using a supplier, I can tell you which setup I'd use and what the cheapest stack would be for the 2–4 week test.

For a 10-person startup building a high-traffic headless storefront, I would narrow the field pretty aggressively. You probably do not want a traditional monolith like Magento/WooCommerce unless you have a very specific reason. For a greenfield headless build, the strongest open-source candidates today are Medusa, Saleor, and Vendure. Vendure

My default recommendation for your team:

1. Pick Medusa if you are a TypeScript/React shop

Best fit: 10–30 person product teams building a custom DTC/B2B storefront that need speed and flexibility.

Why I’d lean here:

• TypeScript/Node stack pairs naturally with a Next.js storefront.
• Modular architecture: you can replace pieces rather than fork the whole platform.
• Good developer experience for a small team.
• MIT license is startup-friendly.
• Easier hiring: many frontend/full-stack engineers can contribute. Vendure Build With Matija

Tradeoffs:

• You are still building a lot: merchandising UX, CMS workflows, search, analytics, personalization, etc.
• Some enterprise commerce features may require custom modules.

A common architecture would be:

Next.js storefront
        |
        v
Medusa API
        |
  ----------------
  |      |       |
Postgres Redis  Workers
        |
Stripe / Adyen / Tax / Shipping APIs

For a startup, I like this because your team owns the customer experience instead of fighting a legacy admin system.

2. Pick Saleor if you have complex commerce requirements

Best fit: marketplaces, international commerce, B2B, multi-channel.

Strengths:

• GraphQL-first API.
• Strong catalog/channel concepts.
• Mature handling of things like warehouses, pricing, and complex commerce models. Designodin

Tradeoffs:

• Python/Django backend means less overlap if your team is all TypeScript.
• More opinionated architecture.
• Operationally heavier for a small team.

I would choose Saleor over Medusa if your roadmap includes things like:

• multiple regions/currencies from day one
• complicated pricing rules
• wholesale accounts
• multiple inventory locations
• marketplace-style workflows

3. Pick Vendure if your team loves NestJS

Best fit: TypeScript teams wanting a strongly structured backend.

Strengths:

• TypeScript end-to-end.
• NestJS architecture feels familiar to backend engineers.
• Good plugin model.
• Strong fit for custom commerce applications. OpenReplay Blog

Tradeoffs:

• Smaller ecosystem/community than Medusa.
• You may build more integrations yourself.

What I would avoid for your situation

Magento / Adobe Commerce

Powerful, but a 10-person startup usually spends too much time operating and customizing it.

WooCommerce headless

Great ecosystem, but the underlying model is still WordPress-centric. It is usually not what I would start with for a high-traffic, API-first storefront.

Building from scratch

Tempting, but commerce has thousands of edge cases:

• tax
• refunds
• inventory race conditions
• promotions
• carts
• payment retries
• fulfillment states

You want to own your differentiation, not reinvent checkout state machines.

My shortlist for your startup

For a typical 10-person startup targeting high traffic, I would start with Medusa + Next.js + PostgreSQL + Redis + a managed search layer (Algolia/OpenSearch/Elastic) and keep the commerce core replaceable.

The bigger scaling risks usually won't be the commerce engine itself; they will be:

• product search
• inventory consistency
• checkout/payment reliability
• caching strategy
• content delivery
• observability

Those deserve architectural attention early. OSSAlt

A few details would change my recommendation:

1. Is this DTC, B2B, or a marketplace?
2. What stack is your team strongest in (TypeScript, Python, PHP)?
3. Expected scale: 10k, 100k, or millions of SKUs/orders?

• tax
• refunds
• inventory race conditions
• promotions
• carts
• payment retries
• fulfillment states

You want to own your differentiation, not reinvent checkout state machines.

My shortlist for your startup

For a typical 10-person startup targeting high traffic, I would start with Medusa + Next.js + PostgreSQL + Redis + a managed search layer (Algolia/OpenSearch/Elastic) and keep the commerce core replaceable.

The bigger scaling risks usually won't be the commerce engine itself; they will be:

• product search
• inventory consistency
• checkout/payment reliability
• caching strategy
• content delivery
• observability

Those deserve architectural attention early.

A few details would change my recommendation:

If your main criterion is “I want to build custom integrations for lots of different clients without fighting the platform,” I’d pick Medusa.

My ranking for a freelance developer

1. Medusa — best overall for custom integrations
2. Vendure — arguably the nicest alternative if you want a very structured TypeScript plugin architecture
3. Sylius — excellent if you’re comfortable with Symfony/PHP
4. Saleor — powerful, especially for B2B, but more infrastructure/architecture than you usually need
5. WooCommerce — easiest to find an existing integration for, but less pleasant when you need deep custom business logic

Why Medusa is my default

Medusa is TypeScript/Node-based and was designed around modular commerce rather than being a monolithic CMS with ecommerce bolted on. Its modules cover things like products, carts, orders, pricing and fulfillment, and you can replace or extend pieces with your own code. OSSAlt OSSAlt

For freelance work, that's particularly attractive because your typical project becomes:

Next.js storefront → Medusa → custom modules/integrations → client's ERP/CRM/WMS/payment/shipping system

You can keep the whole custom stack in JavaScript/TypeScript, which reduces context switching and makes it easier to reuse patterns between clients. OpenReplay Blog Designodin

The downside is important: Medusa's extension ecosystem is much smaller than WooCommerce's. If a client wants some obscure accounting/shipping/marketing integration, you're more likely to build it yourself. WPBundle

When I'd choose something else

Choose Vendure if you want Node/TypeScript but put a premium on a formal plugin architecture and type-safe extension points. It's a particularly compelling choice for a developer building a reusable integration layer across many projects. OpenReplay Blog

Choose Sylius if you're already strong in Symfony. It's less “plug-and-play ecommerce” and more like an ecommerce framework you can shape around the client's business. That's fantastic for highly bespoke projects, but the Symfony learning curve makes it a worse universal recommendation for a JS-focused freelancer. OpenReplay Blog Edana

Choose Saleor when the clients tend toward sophisticated B2B/multichannel requirements. Its GraphQL-first architecture and built-in multi-channel, multi-warehouse capabilities are excellent, but you're taking on Python/Django plus Redis/Celery infrastructure rather than a relatively straightforward Node stack. OpenReplay Blog Ribbsaeter Systems

Choose WooCommerce when “does an integration/plugin already exist?” matters more than architectural elegance. Its enormous plugin ecosystem is a huge advantage, particularly for conventional SMB stores. But deeply customized workflows can eventually turn into a pile of WordPress hooks, plugins, and compatibility issues. OSSAlt ossium

For your specific business model

I'd actually standardize your freelance offering around Medusa + Next.js + PostgreSQL, and build your own small library of reusable integration modules:

• ERP sync
• CRM/customer sync
• payment providers
• shipping/fulfillment
• tax
• inventory
• webhooks/event processing
• product/catalog imports
• custom checkout logic

Then each new client mostly becomes configuration + a handful of client-specific adapters, rather than starting from scratch.

If you tell me what kinds of clients/integrations you typically build (Shopify migrations, ERP integration, subscriptions, marketplaces, B2B, custom checkout, etc.), I can narrow this down to Medusa vs Vendure vs Sylius and tell you which I'd standardize on.

When I'd choose something else

Choose Vendure if you want Node/TypeScript but put a premium on a formal plugin architecture and type-safe extension points. It's a particularly compelling choice for a developer building a reusable integration layer across many projects. OpenReplay Blog

Choose Sylius if you're already strong in Symfony. It's less “plug-and-play ecommerce” and more like an ecommerce framework you can shape around the client's business. That's fantastic for highly bespoke projects, but the Symfony learning curve makes it a worse universal recommendation for a JS-focused freelancer. OpenReplay Blog edana.ch

Choose Saleor when the clients tend toward sophisticated B2B/multichannel requirements. Its GraphQL-first architecture and built-in multi-channel, multi-warehouse capabilities are excellent, but you're taking on Python/Django plus Redis/Celery infrastructure rather than a relatively straightforward Node stack. OpenReplay Blog ribbsaetersystems.com

Choose WooCommerce when “does an integration/plugin already exist?” matters more than architectural elegance. Its enormous plugin ecosystem is a huge advantage, particularly for conventional SMB stores. But deeply customized workflows can eventually turn into a pile of WordPress hooks, plugins, and compatibility issues.

For your specific business model

If multi-vendor marketplace capability + total data ownership are your top requirements, I would prioritize self-hosted open-source platforms over SaaS marketplaces. The best fit depends on your business model, engineering capacity, and scale. Mercur Twosided

Shortlist

My recommendation by scenario

1. You want maximum control and long-term ownership

Choose Spree Commerce or Bagisto.

• Your database stays on your infrastructure.
• You control customer, vendor, order, and transaction data.
• You avoid marketplace SaaS lock-in.
• You can modify the code and workflows.

Spree specifically positions its marketplace capabilities around vendor dashboards, multi-vendor checkout, commissions, APIs, and self-hosted ownership. Spree Commerce

2. You need to launch quickly but still own the platform

Choose CS-Cart Multi-Vendor.

Good if you need:

• vendor registration
• seller dashboards
• commissions
• product approvals
• shipping workflows
• marketplace operations without building everything

The tradeoff is that it is less developer-centric than a pure open-source framework. Twosided Jujubesy

3. You are building a unique marketplace business model

Choose a composable/headless approach:

• Backend: Spree, Medusa, Bagisto, or Magento
• Frontend: React/Next.js/Vue
• Payments: your own processor integrations
• Infrastructure: your cloud account
• Data warehouse: your own stack

This gives you the strongest ownership and flexibility.

Platforms I would be cautious about for “total data ownership”

• Shopify marketplace apps — convenient, but you remain dependent on Shopify’s ecosystem.
• Sharetribe — excellent for validation and service marketplaces, but hosted SaaS means less infrastructure ownership.
• Mirakl-type enterprise marketplace layers — powerful, but usually introduce vendor dependency and licensing costs. Mercur

My default recommendation

For a company serious about owning its marketplace:

Tier 1 choice: Spree Commerce
Tier 2 choice: Bagisto
Fastest operational launch: CS-Cart

A few questions would change the recommendation:

1. Are you building a B2C marketplace (Amazon-style), B2B marketplace, or services marketplace?
2. How many vendors do you expect (100, 10,000, 100,000+)?
3. Do you have an internal engineering team (PHP/Laravel, Node.js, Java, etc.)?
4. Do you need built-in vendor payouts/split payments?

Yes. For a single self-hosted open-source store handling both physical and digital products, my first choice would be Saleor.

Best options

Why Saleor stands out: its documentation explicitly has a digital-products recipe covering licenses, services, and other non-physical goods, while its core catalog handles ordinary products and variants. It also supports shipping configuration separately, which makes a catalog containing downloadable goods alongside shippable products a natural fit. Saleor Documentation

Saleor is also genuinely self-hostable: its current open-source stack can be cloned and run with Docker, with the Dashboard and commerce API included. Saleor Commerce

When I'd pick something else

• Choose WooCommerce if you want the least development work, WordPress built in, and access to an enormous plugin ecosystem. It's particularly attractive if your digital products are conventional downloads and your physical products don't require unusual fulfillment logic. WPBundle
• Choose Medusa if you're building a custom storefront with Next.js/TypeScript and want the commerce backend to be extremely programmable. Its modular Node.js architecture is particularly appealing to developers, though you'll generally build more integrations yourself. WPBundle OpenReplay Blog
• Choose Sylius if you have PHP/Symfony expertise and expect substantial custom business rules. It's more of an ecommerce framework than an out-of-the-box merchant platform. github.com

My recommendation

If your catalog looks something like:

T-shirts + books + downloadable PDFs + software/licenses + online services

I'd shortlist Saleor and WooCommerce first.

If you're a developer building a custom modern storefront, I'd go Saleor. If you want something you can install, configure, and operate without building much commerce infrastructure, I'd go WooCommerce.

If you tell me roughly how many physical products vs. digital products you have, whether digital items need license keys/download limits, and whether you want a built-in storefront or headless, I can narrow this to one platform and explain the architecture I'd use.

If your top priorities are plugin/extension ecosystem + active developer community, my pick is WooCommerce.

My ranking

🥇 WooCommerce — best overall ecosystem

WooCommerce is hard to beat if ecosystem size is the primary criterion. It sits on top of WordPress, so you get the enormous WordPress plugin/theme/developer ecosystem in addition to WooCommerce-specific extensions. Current comparisons consistently identify it as having the broadest open-source ecommerce extension ecosystem. Toolradar OSSAlt

The developer infrastructure is also mature: WooCommerce maintains extensive developer documentation, a public GitHub monorepo, extension-development tooling, a community Slack, forums, and an official marketplace. Its GitHub repository currently shows thousands of contributors/forks and ongoing releases. GitHub WooCommerce The WooCommerce Developer Blog

Choose it if: you want to be able to say, "There's probably already a plugin for this."

The main downside is architectural: WordPress + WooCommerce can become messy when you have lots of plugins, complex business logic, or highly customized infrastructure.

🥈 PrestaShop — best dedicated ecommerce alternative

PrestaShop is worth considering if you don't want the WordPress dependency. Its architecture is ecommerce-first, and it has a mature module/theme system. Developers can extend it through modules, themes, and overrides, with active GitHub discussions, Slack, and forums. GitHub

I'd choose PrestaShop over WooCommerce when the store itself is the application, rather than a content-heavy WordPress site that happens to sell things.

🥉 Magento Open Source — best for complex systems

Adobe's Magento Open Source remains attractive when you need sophisticated catalogs, pricing rules, multi-store setups, B2B functionality, and enterprise-grade customization.

But there's an important tradeoff: its ecosystem is strong, yet development is considerably more complex than WooCommerce. You're generally choosing depth over accessibility.

🚀 Medusa — best modern developer experience

If by "best for developers" you mean modern architecture rather than the biggest plugin marketplace, I'd seriously consider Medusa.

It's Node.js/TypeScript-oriented and designed around headless/composable commerce. Recent comparisons put Medusa among the strongest choices for teams building custom React/Next.js storefronts. OSSAlt OpenReplay Blog

The catch is that its ecosystem is much younger and smaller than WooCommerce's. You may end up building integrations that already exist as plugins in WooCommerce.

Bottom line

If I were choosing specifically for plugin ecosystem + community support:

1. WooCommerce — best overall, by a significant margin
2. PrestaShop — excellent dedicated ecommerce ecosystem
3. Magento Open Source — strongest for sophisticated/enterprise customization
4. Medusa — best modern developer-first/headless option
5. Saleor — excellent API/GraphQL architecture, smaller extension ecosystem

One useful distinction: "best ecosystem" and "best developer architecture" are no longer the same answer. WooCommerce wins the former; Medusa/Saleor are more compelling if you're building a modern headless application from scratch. opensourcegroups.com wpbundle.com

If you tell me your stack (PHP/Node/Python/etc.), expected catalog size, and whether you want traditional or headless, I can narrow this down to the best 2–3 options for your particular project.

The developer infrastructure is also mature: WooCommerce maintains extensive developer documentation, a public GitHub monorepo, extension-development tooling, a community Slack, forums, and an official marketplace. Its GitHub repository currently shows thousands of contributors/forks and ongoing releases. GitHub WooCommerce The WooCommerce Developer Blog

Choose it if: you want to be able to say, "There's probably already a plugin for this."

The main downside is architectural: WordPress + WooCommerce can become messy when you have lots of plugins, complex business logic, or highly customized infrastructure.

🥈 PrestaShop — best dedicated ecommerce alternative

PrestaShop is worth considering if you don't want the WordPress dependency. Its architecture is ecommerce-first, and it has a mature module/theme system. Developers can extend it through modules, themes, and overrides, with active GitHub discussions, Slack, and forums. GitHub

I'd choose PrestaShop over WooCommerce when the store itself is the application, rather than a content-heavy WordPress site that happens to sell things.

🥉 Magento Open Source — best for complex systems

Adobe's Magento Open Source remains attractive when you need sophisticated catalogs, pricing rules, multi-store setups, B2B functionality, and enterprise-grade customization.

But there's an important tradeoff: its ecosystem is strong, yet development is considerably more complex than WooCommerce. You're generally choosing depth over accessibility.

🚀 Medusa — best modern developer experience

If by "best for developers" you mean modern architecture rather than the biggest plugin marketplace, I'd seriously consider Medusa.

It's Node.js/TypeScript-oriented and designed around headless/composable commerce. Recent comparisons put Medusa among the strongest choices for teams building custom React/Next.js storefronts. OSSAlt blog.openreplay.com

The catch is that its ecosystem is much younger and smaller than WooCommerce's. You may end up building integrations that already exist as plugins in WooCommerce.

Bottom line

If I were choosing specifically for plugin ecosystem + community support:

For that profile, WooCommerce is probably the easiest self-hosted option to maintain.

My ranking

1. WooCommerce — easiest overall

• Familiar WordPress admin interface.
• Huge ecosystem, so finding themes, payment integrations, shipping tools, and people who can help is relatively easy.
• For a small, low-traffic catalog, it doesn't require much server horsepower; WooCommerce's own guidance gives a simple baseline of 1 vCPU and 2 GB RAM. The WooCommerce Developer Blog
• The downside is that you're maintaining WordPress + WooCommerce + themes + plugins + PHP, so updates and backups still matter. WooCommerce specifically recommends backups and staging before updates. WooCommerce WooCommerce
• PrestaShop — good dedicated-store alternative

• More purpose-built than WooCommerce.
• A reasonable choice if you don't want WordPress at all.
• I'd still put it behind WooCommerce for a non-technical owner because the WordPress/WooCommerce ecosystem tends to make finding help and extensions easier.
• OpenCart — lightweight, but less attractive today

• Relatively straightforward and lightweight.
• Smaller ecosystem and less mainstream than WooCommerce, which matters when the owner eventually needs someone to troubleshoot something.
• Shopware — avoid for this use case

• Powerful, but it's aimed at substantially more sophisticated deployments.
• Shopware itself says its self-hosted version is appropriate when you have an expert developer team; its cloud version is what it recommends when you want infrastructure and updates handled for you. Shopware
• Its current self-hosted requirements also involve things such as PHP 8.2–8.4, Node.js 20+, and MySQL/MariaDB configuration. Shopware Documentation

The important caveat

If by self-hosted you mean "I want the store software on my own VPS and the owner shouldn't need to understand Linux, databases, SSL, backups, etc.", then I'd actually choose:

WordPress + WooCommerce + a managed WordPress host, rather than installing WooCommerce manually on a VPS.

That's still self-hosted in the sense that you control the application/site and can migrate it, but the hosting company handles much of the unpleasant server maintenance. WooCommerce itself emphasizes that the host affects security, stability, and performance. WooCommerce

For a low-traffic boutique store with a non-technical owner, my sweet spot would therefore be:

WooCommerce + a reputable managed WordPress host + a small number of well-maintained plugins.

The last part is important: plugin sprawl is probably a bigger maintenance risk than WooCommerce itself. Keep the installation boring and conventional, and it can be quite easy to operate.

If strong security/compliance for payments and customer data is the priority, I’d choose Magento Open Source (Adobe Commerce’s open-source edition) over WooCommerce or PrestaShop—provided you have a capable engineering/security team.

My ranking

*These can be excellent security architectures, but they put substantially more responsibility on your engineering team.

Why I'd pick Magento

Magento has a relatively mature security model for a self-hosted open-source platform: 2FA, CAPTCHA/reCAPTCHA, security scanning, security advisories and a formal security-patch process are documented by Adobe. Experience League Experience League

It's also designed for more complex enterprise commerce requirements than WooCommerce. The important caveat is that Magento Open Source itself does not make you PCI compliant. Adobe explicitly notes that merchants remain responsible for their PCI obligations and the security of their implementation. Experience League

And you need to take patching seriously: Adobe has continued issuing security updates for Magento Open Source in 2026, including fixes for issues capable of arbitrary code execution and privilege escalation. Adobe Help Center

The architecture matters more than the platform

For a security-sensitive payment system, I would design it so that:

• The ecommerce application never stores raw card numbers.
• Payments go through a PCI-compliant processor using hosted fields/tokenization or an appropriately scoped hosted checkout.
• Customer PII is encrypted in transit and protected at rest.
• Admin access requires MFA, least privilege and preferably SSO.
• Production access is tightly restricted and audited.
• WAF + CDN + DDoS protection sit in front of the storefront.
• Dependencies, extensions and OS packages are continuously vulnerability-scanned.
• Security patches are tested and deployed rapidly.
• Centralized immutable logging/SIEM captures authentication, privilege changes, payment events and sensitive-data access.
• Backups are encrypted, isolated and regularly restore-tested.
• You maintain documented retention/deletion procedures for customer data.
• PCI DSS, GDPR/CCPA and your organization's security policies are treated as separate compliance requirements, not something the ecommerce platform magically provides.

One important alternative

If your organization doesn't specifically require self-hosted open source, I'd seriously consider Adobe Commerce Cloud rather than operating Magento Open Source yourself. Adobe currently documents SOC 2 Type II, ISO 27001 and PCI DSS coverage for its Commerce cloud infrastructure, while maintaining a shared-responsibility model for your application, code, extensions and data. Experience League Experience League

That can remove a substantial amount of infrastructure/security operational burden.

Bottom line: For a genuinely security- and compliance-sensitive organization that requires open source, I'd shortlist Magento Open Source first. If minimizing operational compliance burden matters more than having the platform itself be open source, Adobe Commerce Cloud deserves serious consideration. WooCommerce is perfectly capable of a secure deployment, but its security responsibility extends across WordPress, WooCommerce, themes, plugins and hosting, which creates a larger dependency surface; WooCommerce itself explicitly says the store owner remains responsible for PCI compliance. WooCommerce WooCommerce

If you tell me your company size, expected transaction volume, cloud (AWS/Azure/GCP), and compliance requirements (PCI DSS, SOC 2, HIPAA, GDPR, etc.), I can narrow this down to a specific architecture and platform choice.

The architecture matters more than the platform

For a small indie studio, I’d avoid building file delivery from scratch unless you need a custom storefront. The best choice depends on whether you want a store to handle purchases/keys or just secure file delivery.

My picks

🥇 For your situation: R2 + signed downloads

If you're selling directly through your own website, Cloudflare R2 is probably my recommendation.

R2 is S3-compatible object storage designed for serving large amounts of data, and importantly for games, it has no egress bandwidth fees. developers.cloudflare.com

The architecture I'd use is:

Customer purchases → your backend records entitlement → backend generates short-lived signed URL → customer downloads directly from R2

The customer never gets your storage credentials. R2's presigned URLs can be restricted to a particular object and expiration time, and Cloudflare explicitly recommends them for time-limited downloads. developers.cloudflare.com

I'd make the URL something like 1–6 hours, rather than a permanent download URL. You can also require the customer to authenticate before generating it.

R2 encrypts stored objects with AES-256 and uses TLS for data in transit. developers.cloudflare.com

What I'd build around it

For each purchase:

Order
 └── entitlement
      ├── product = Game X
      ├── version = 1.4.2
      ├── customer = ...
      └── download permission
              ↓
        Your download API
              ↓
      signed R2 URL
              ↓
       Game ZIP / installer

I'd keep the R2 bucket private. Don't put the game files in a publicly readable bucket.

Also give every release a checksum (e.g. SHA-256) so your launcher/customer support can verify that a downloaded build isn't corrupted.

If you don't want to build any of this

I'd seriously consider itch.io. It already provides hosted game downloads, sales, and download keys; its download keys are URLs granting access to a project's files. itch.io

That's particularly attractive if you're a tiny team and would rather spend engineering time on the game than on entitlement systems, payment handling, download infrastructure, refunds, and customer support.

S3 is the alternative

S3 is technically excellent. AWS supports presigned URLs specifically for granting customers temporary access without changing bucket policies or giving them AWS credentials. docs.aws.amazon.com

The main reason I'd choose R2 over S3 for an indie game store is the bandwidth economics: large game downloads can generate a lot of egress, and R2's lack of egress fees makes the cost model much more attractive. developers.cloudflare.com

Bottom line:

• Want zero/minimal engineering: itch.io.
• Own website + want a professional custom store: Cloudflare R2 + private bucket + short-lived presigned URLs.
• Need sophisticated cloud infrastructure / already live in AWS: S3 + presigned URLs.
• Selling through Steam: use Steam's distribution and Steam keys rather than delivering Steam builds yourself. Steam specifically supports keys for distribution through other stores. partner.steamgames.com

If you tell me roughly how large your builds are (e.g. 2 GB vs 50 GB), expected monthly downloads, and whether customers buy through your own website or a storefront, I can recommend a concrete stack and estimate the monthly cost.

Yes. For an agency model—multiple client-owned digital-product stores, separate client logins, and your agency operating everything behind the scenes—I’d narrow it to a few options.

Best fits

Lemon Squeezy is particularly interesting for your use case because one account can manage multiple independent stores, each with its own products, domains, customers, billing and payouts. It's also purpose-built for digital products and acts as the merchant of record, handling sales tax/VAT. Lemon Squeezy Docs Lemon Squeezy Lemon Squeezy Docs

However, if by white-label you mean:

"Our agency has one master dashboard → Client A sees only Client A's store → Client B sees only Client B's store → clients log into a branded portal → we control the infrastructure"

then Lemon Squeezy isn't quite a full agency/white-label SaaS platform. Its multi-store functionality is primarily an account/store management feature.

Shopify is the more flexible architecture

Shopify gives you much stronger client/staff permissions and an enormous app/API ecosystem. You can create one Shopify store per client and have your agency retain partner/admin access while giving clients restricted staff access.

There's also now an interesting third-party option, Plectix Multi-Store Hub, which specifically markets agency workspaces, isolated white-labeled client views, multi-store management, and a unified dashboard across Shopify stores. Shopify App Store Shopify App Store

apps.shopify.com

If you're building your own agency platform

I'd seriously consider this architecture:

Your Agency SaaS
→ Client A workspace
→ Client B workspace
→ Client C workspace
→ each connected to its own Lemon Squeezy or Shopify store
→ your agency owns/administers the infrastructure
→ client gets a restricted branded dashboard

That gives you much more control over client isolation, recurring agency fees, branding, domains, permissions, analytics and onboarding than trying to force a creator platform into an agency model.

One notable advantage of Lemon Squeezy is that you can have many stores under the same account, which maps nicely to the "one client = one store" model. Lemon Squeezy Docs

My ranking for your specific business:

1. Shopify + custom/agency management layer — best if you want maximum control and scalability.
2. Lemon Squeezy — best if the priority is digital products + simple deployment + merchant-of-record.
3. Whop/white-label infrastructure — worth investigating if you want the platform itself to be white-labeled.
4. Sellfy/Podia — great for individual creators, but I'd avoid them for a multi-client agency architecture. Sellfy, for example, explicitly says one storefront per account and doesn't support multiple users on an account. Sellfy Help Center

If you tell me (1) whether clients need their own login, (2) whether they need to see sales/orders/customers, and (3) whether your agency wants to own the Stripe/payment accounts, I can narrow this down to the 2–3 platforms that actually fit your SaaS/agency model.

Lemon Squeezy is particularly interesting for your use case because one account can manage multiple independent stores, each with its own products, domains, customers, billing and payouts. It's also purpose-built for digital products and acts as the merchant of record, handling sales tax/VAT. Lemon Squeezy Docs Lemon Squeezy Lemon Squeezy Docs

However, if by white-label you mean:

"Our agency has one master dashboard → Client A sees only Client A's store → Client B sees only Client B's store → clients log into a branded portal → we control the infrastructure"

then Lemon Squeezy isn't quite a full agency/white-label SaaS platform. Its multi-store functionality is primarily an account/store management feature.

Shopify is the more flexible architecture

Shopify gives you much stronger client/staff permissions and an enormous app/API ecosystem. You can create one Shopify store per client and have your agency retain partner/admin access while giving clients restricted staff access.

There's also now an interesting third-party option, Plectix Multi-Store Hub, which specifically markets agency workspaces, isolated white-labeled client views, multi-store management, and a unified dashboard across Shopify stores. Shopify App Store Shopify App Store

apps.shopify.com

If you're building your own agency platform

I'd seriously consider this architecture:

Your Agency SaaS
→ Client A workspace
→ Client B workspace
→ Client C workspace
→ each connected to its own Lemon Squeezy or Shopify store
→ your agency owns/administers the infrastructure
→ client gets a restricted branded dashboard

That gives you much more control over client isolation, recurring agency fees, branding, domains, permissions, analytics and onboarding than trying to force a creator platform into an agency model.

One notable advantage of Lemon Squeezy is that you can have many stores under the same account, which maps nicely to the "one client = one store" model.

My ranking for your specific business:

For a small shop owner who sells both digital products and occasional physical goods, the best fit is usually a platform that treats digital downloads as a normal product type while still handling inventory, shipping, taxes, and order management. Fit Small Business Hostinger

My shortlist:

1. shopify.com — Best overall for a mixed store

Best if: you want one system that can grow with you.

Why it works well:

• Sell physical items with inventory, variants, shipping rates, and fulfillment.
• Sell digital files (ebooks, templates, downloads, courses) using apps or integrations.
• Strong checkout, payment processing, marketing tools, and customer management.
• Good if you may eventually sell through social media, marketplaces, or in person. Fit Small Business

Downside: monthly cost plus possible app costs can add up, especially for advanced digital-product features.

My pick for: a handmade goods shop, creator brand, boutique, or small business that expects to grow.

2. squareup.com — Best if you also sell in person

Best if: you run a market stall, pop-up, retail counter, or physical shop.

Why it works well:

• Syncs online sales with Square’s point-of-sale ecosystem.
• Good inventory management for physical products.
• Simple setup for occasional online selling. Fit Small Business TechRadar

Downside: digital products are not its strongest area compared with Shopify or creator-focused platforms.

My pick for: a local shop that mostly sells physical goods but occasionally adds digital items.

3. woocommerce.com — Best if you already use WordPress

Best if: you want maximum control.

Why it works well:

• Handles both physical and downloadable products.
• Huge ecosystem of plugins for shipping, memberships, subscriptions, and digital delivery.
• You own the website rather than renting a hosted store. Hostinger

Downside: more setup and maintenance than Shopify.

My pick for: someone comfortable managing a website or already invested in WordPress.

4. wix.com — Best for a simple, attractive storefront

Best if: your store is small and brand/design-focused.

Why it works well:

• Easy drag-and-drop website building.
• Supports physical and digital products.
• Good for artists, makers, portfolios, and small catalogs. TechRadar

Downside: may feel limiting as your catalog and operations become more complex.

My recommendation by situation

• Mostly digital + some physical shipping: Shopify
• Mostly physical + occasional digital downloads: Square Online or Shopify
• Already have WordPress: WooCommerce
• Small creative brand with a beautiful website focus: Wix or Shopify

For a typical small shop owner who wants the least hassle, I’d start with Shopify because it handles the “mixed inventory” problem cleanly and gives you room to grow. Fit Small Business

If you tell me what your digital products are (downloads, courses, memberships, templates, etc.) and roughly how many physical items you sell, I can narrow it down further.

For digital downloads specifically, I’d put Medusa at the top of your shortlist.

My ranking

1. Medusa — best fit for your use case

• TypeScript/Node.js and very API-oriented.
• Its current docs have a dedicated digital-products implementation: digital-product modules, file storage, custom API routes, customer purchase history, and authenticated download URLs. Medusa Docs Medusa Docs
• Particularly attractive if you want to own the workflow rather than adapt a SaaS platform's notion of a "digital product."
• REST Store API plus a JS SDK make it straightforward to put a Next.js/custom frontend on top. Medusa Docs

Architecture I'd consider:
Next.js → Medusa API → Stripe → order/payment event → digital entitlement → S3/R2 → signed download URL

2. Vendure — excellent if you're strongly TypeScript/NestJS-oriented

• GraphQL-first Shop API with a very extensible plugin architecture. Vendure Vendure
• It actually has an official digital-products guide covering custom fields, fulfillment handlers, download links, and automatic fulfillment after payment. GitHub
• I'd choose it over Medusa if you particularly value GraphQL + strongly structured TypeScript/NestJS architecture.
• Saleor — best API sophistication, but potentially more platform than you need

• GraphQL-only/API-only architecture with webhooks, apps, metadata, and API extensions. Saleor Store GitHub
• Its app model is particularly good if you want the download/entitlement machinery to live in separate services. GitHub
• I'd favor it for multi-channel, international, complex commerce, rather than a relatively focused digital-download store.

The important distinction

For digital goods, I'd prioritize workflow extensibility over built-in "digital downloads" features.

You probably want the commerce platform to handle:

• products/variants
• pricing and discounts
• carts/checkout
• payment state
• orders
• customers
• webhooks/events

…and have your application own:

• entitlements
• download limits
• license keys
• versioning
• expiring URLs
• S3/R2 objects
• revocation
• customer download history
• post-purchase fulfillment

That makes Medusa particularly compelling because its current digital-product recipe explicitly follows this modular approach: file storage + digital-product module + fulfillment + custom Store/Admin APIs. Medusa Docs

If I were building this today as a technically sophisticated solo developer or small team, I'd pick Medusa + Next.js + Stripe + Cloudflare R2/S3. If GraphQL is a hard requirement, I'd pick Vendure or Saleor instead.

If you tell me roughly how many SKUs/downloads you expect and whether you need subscriptions, license keys, bundles, or customer-specific files, I can narrow this down further.

For an agency building custom frontends for multiple clients, I’d avoid choosing a platform purely on “headless support.” The important question is whether the commerce backend can become a repeatable foundation for many builds: multi-store, tenant isolation, API quality, merchant tooling, and maintainability.

My shortlist would be:

1. BigCommerce — best agency default for many clients

bigcommerce.com

Recommended for: SMB → mid-market brands that want a custom Next.js/React storefront without your agency owning the entire commerce stack.

Strengths:

• Strong headless APIs (catalog, cart, checkout, orders)
• Multi-storefront support
• Managed hosting/security/payment complexity
• Good balance between merchant usability and frontend freedom
• Easier client handoff than fully composable systems

Tradeoff:

• You work within BigCommerce’s commerce model rather than owning every domain object. BigCommerce

Agency fit: ⭐⭐⭐⭐⭐
This is probably the platform I’d standardize around if you want a repeatable delivery model.

2. commercetools — enterprise composable choice

commercetools.com

Recommended for: Large clients with complex requirements:

• Multiple brands
• Multiple regions
• B2B pricing
• Complex catalogs
• ERP/PIM/OMS integrations

Strengths:

• API-first from the ground up
• Very flexible domain modeling
• Designed for composable commerce and multi-channel architectures Vendure

Tradeoff:

• Your agency is taking on more architecture responsibility: - CMS
• search
• promotions
• checkout UX
• integrations
• operations

Agency fit: ⭐⭐⭐⭐
Great for high-value enterprise projects, less ideal as a default platform for every client.

3. Shopify Plus + Hydrogen — fastest path for DTC

shopify.com

Recommended for: Brands that mostly need:

• Beautiful custom storefronts
• Fast launches
• Strong merchant adoption

Strengths:

• Excellent ecosystem
• Great checkout
• Mature APIs
• Huge pool of Shopify-trained clients/developers

Tradeoff:

• Multi-tenant/multi-brand architecture is not its strongest area compared with true composable platforms. Netguru

Agency fit: ⭐⭐⭐⭐
Excellent if your clients are primarily DTC brands.

4. Saleor or Medusa — when you want your own platform layer

saleor.io
medusajs.com

Recommended for: An agency trying to build a reusable commerce platform/IP.

Strengths:

• More control
• Open source
• Can create your own multi-tenant SaaS layer
• Better if you want to own the architecture

Tradeoff:

• Your team owns: - hosting
• upgrades
• scaling
• security
• operational tooling

Agency fit: ⭐⭐⭐
Powerful, but you become a software company.

My recommendation for an agency model

I would create a tiered offering:

For your internal architecture, I’d standardize your frontend stack around:

• Next.js
• TypeScript
• Tailwind/design system
• API gateway/BFF layer
• CMS abstraction
• Analytics/personalization integrations

Then your agency sells the frontend experience layer while swapping commerce engines underneath.

If your goal is specifically “one platform where we can host hundreds of client stores as tenants”, I’d look harder at commercetools, Saleor, Vendure, or Medusa rather than Shopify/BigCommerce, because those are closer to building a commerce platform rather than just delivering stores. Vendure guideflow.com

Then your agency sells the frontend experience layer while swapping commerce engines underneath.

If your priority is CMS-first product pages, I’d pick Sanity + a commerce API, with Shopify as the commerce backend for most DTC brands.

The key architectural decision is: CMS owns the page experience; commerce owns the transactional truth.

My default stack

Sanity → Next.js → Shopify Storefront API

• Sanity: product-page content, storytelling, merchandising modules, SEO, landing pages, related content, buying guides, FAQs, etc.
• Shopify: products, variants, prices, inventory, discounts, carts, checkout, orders.
• Next.js: renders the product page and composes Sanity content with live commerce data.
• CDN/cache: cache the content-heavy portions aggressively, while keeping price/inventory/cart data appropriately fresh.

Sanity now has an official Shopify connector that can synchronize products, variants, and collections into Sanity, while allowing you to add richer structured content around those products. Sanity.io Sanity.io

That makes the authoring model something like:

Product
├── Commerce identity → Shopify product/variant
├── Editorial content → Sanity
├── Hero media → Sanity
├── Product story → Sanity
├── Benefits → Sanity
├── FAQs → Sanity
├── Buying guide → Sanity
├── Reviews → Reviews API
└── Price / inventory / availability → Shopify API

The important bit: don't duplicate commerce data into the CMS as your source of truth. Use the CMS to enrich/reference the product, while Shopify remains authoritative for transactional fields.

When I'd choose something else

Contentful + commercetools is particularly compelling if you're building a serious composable-commerce architecture. Contentful has an official commercetools integration where editors can browse/reference products and categories, and product data can be resolved through Contentful's GraphQL API. Contentful Contentful

Why I'd lean Sanity for your description

"CMS-first with commerce APIs" implies that the product page isn't merely a commerce template with some CMS fields bolted on. You probably want the CMS to define the experience and composition.

Sanity is unusually good at that because you can model a product page as structured, composable content rather than a fixed product template. Its Shopify integration is specifically designed around combining Shopify product data with richer Sanity content. Sanity.io Sanity.io

I'd therefore start with:

Sanity + Shopify + Next.js

and make the frontend's product-page query effectively:

Sanity:
  "What should this product page look like?"

+
Shopify:
  "What can the customer actually buy right now?"

=
Rendered PDP

If you're building a large catalog, multiple brands/markets, or B2B, I'd change the recommendation toward Sanity/Contentful + commercetools rather than Shopify. Commercetools is explicitly API-first and designed to let you keep the frontend and surrounding technology stack independent of the commerce backend. commercetools.com

If you tell me your commerce backend (Shopify, commercetools, BigCommerce, Medusa, custom, etc.) and whether marketers need visual page editing, I can narrow this down to a concrete architecture.

If your team is already committed to serverless frontends + JAMstack, I’d narrow the field to Shopify, Medusa, Saleor, and commercetools. Headless commerce is a natural fit because the storefront can be independently deployed as a static/SSR/edge app while commerce remains an API backend. Naturaily Ecosire

My ranking

1. Shopify — best if "serverless" means minimal operations

A typical architecture would be:

Next.js/Astro → Shopify Storefront API → Shopify checkout

Your frontend can be statically generated or rendered at the edge, while Shopify handles products, inventory, orders, payments, and the operational side of commerce. This is probably the best default choice for a small-to-mid-sized team that doesn't want to operate a commerce backend. Ribbsaeter Systems eSEOspace

The downside is that you're still fundamentally using Shopify's commerce model. If you need unusual pricing, checkout, fulfillment, or marketplace logic, you'll eventually run into its boundaries.

2. Medusa — my pick for a developer-centric JAMstack team

If your team is comfortable with TypeScript/Node.js, I'd seriously consider Medusa.

Next.js/Astro → Medusa API → PostgreSQL/services

Medusa is modular and API-driven, so the frontend doesn't need to know or care how the commerce backend is implemented. Its Node/TypeScript stack also makes it particularly attractive when your frontend and backend engineers already live in the JavaScript ecosystem. OSSAlt Born Digital

The catch: it's not as "serverless by default" as Shopify. You either operate the backend yourself or use its managed offering. So you get more architectural control in exchange for more operational responsibility.

3. Saleor — excellent if GraphQL is central to your stack

Saleor is particularly compelling if your frontend architecture is heavily GraphQL-oriented.

Next.js/Astro → GraphQL → Saleor

It has a GraphQL-first API and is particularly strong for multi-channel, international, and more sophisticated commerce requirements. OSSAlt Designodin

I'd choose it over Medusa if your organization already has Python/Django expertise or if GraphQL/schema-driven development is an important architectural requirement.

4. commercetools — best for enterprise composable commerce

If you're talking about a large organization with multiple brands, countries, channels, complex B2B pricing, etc., commercetools is probably the architectural heavyweight I'd evaluate first.

It's designed around composable/API-first commerce, so it works very well with independently deployed frontend applications. The downside is that you're buying an enterprise platform and taking on a substantially more involved implementation. Naturaily Madgeek

What I'd choose

For a team saying "we prefer serverless frontends and JAMstack", rather than simply "we need headless," my shortlist would be:

1. Shopify Storefront API — if minimizing backend operations is the priority.
2. Medusa — if engineering control and TypeScript are the priority.
3. Saleor — if GraphQL and sophisticated commerce are the priority.
4. commercetools — if you're enterprise-scale and genuinely need composable commerce.

My default recommendation: Shopify for operational simplicity; Medusa for architectural freedom.

One important distinction: JAMstack doesn't mean the commerce backend itself has to be serverless. Your product/category/content pages can be statically generated or edge-rendered, while carts, customer sessions, inventory, and checkout remain dynamic API interactions. That's generally the cleanest architecture for this model. Naturaily

If you tell me your frontend framework (Next.js, Astro, Gatsby, Nuxt, etc.), expected traffic/SKU count, B2B vs. DTC, and whether you want to self-host, I can narrow this to a specific architecture and platform.

Your frontend can be statically generated or rendered at the edge, while Shopify handles products, inventory, orders, payments, and the operational side of commerce. This is probably the best default choice for a small-to-mid-sized team that doesn't want to operate a commerce backend. Ribbsaeter Systems eSEOspace

The downside is that you're still fundamentally using Shopify's commerce model. If you need unusual pricing, checkout, fulfillment, or marketplace logic, you'll eventually run into its boundaries.

2. Medusa — my pick for a developer-centric JAMstack team

If your team is comfortable with TypeScript/Node.js, I'd seriously consider Medusa.

Next.js/Astro → Medusa API → PostgreSQL/services

Medusa is modular and API-driven, so the frontend doesn't need to know or care how the commerce backend is implemented. Its Node/TypeScript stack also makes it particularly attractive when your frontend and backend engineers already live in the JavaScript ecosystem. OSSAlt Born Digital

The catch: it's not as "serverless by default" as Shopify. You either operate the backend yourself or use its managed offering. So you get more architectural control in exchange for more operational responsibility.

3. Saleor — excellent if GraphQL is central to your stack

Saleor is particularly compelling if your frontend architecture is heavily GraphQL-oriented.

Next.js/Astro → GraphQL → Saleor

It has a GraphQL-first API and is particularly strong for multi-channel, international, and more sophisticated commerce requirements. OSSAlt Designodin

I'd choose it over Medusa if your organization already has Python/Django expertise or if GraphQL/schema-driven development is an important architectural requirement.

4. commercetools — best for enterprise composable commerce

If you're talking about a large organization with multiple brands, countries, channels, complex B2B pricing, etc., commercetools is probably the architectural heavyweight I'd evaluate first.

It's designed around composable/API-first commerce, so it works very well with independently deployed frontend applications. The downside is that you're buying an enterprise platform and taking on a substantially more involved implementation.

What I'd choose

For a team saying "we prefer serverless frontends and JAMstack", rather than simply "we need headless," my shortlist would be:

If developer experience, SDK quality, and modern frontend-framework support are your top criteria, my pick in 2026 is Shopify, specifically its evolving Hydrogen + Storefront API stack.

My ranking

🥇 Shopify Hydrogen — best overall

Shopify has probably the strongest combination of SDKs, documentation, tooling, APIs, examples, and frontend integration.

The current Hydrogen stack gives you:

• Typed Storefront API client
• React/React Router integration
• Commerce primitives for products, carts, collections, etc.
• Customer Account API integration
• CLI and local-development tooling
• TypeScript/IntelliSense support
• First-party analytics
• Shop Pay integration
• Oxygen deployment
• Extensive examples and starter templates Shopify Shopify Shopify App Store

The particularly interesting development is that Shopify is moving Hydrogen toward an SDK/toolkit rather than forcing you into one frontend framework. The current developer preview supports Next.js, SvelteKit, Nuxt, SolidStart, and React Router, with the core commerce logic implemented as framework-agnostic JavaScript. Shopify Hydrogen

That is a pretty compelling answer if your frontend team likes to experiment with modern frameworks.

shopify.dev

🥈 Medusa — best if you want control

Medusa is arguably the better developer-centric architecture if you don't want Shopify's commerce model.

Its JS SDK can be used from Next.js, React, Vue, Angular, or essentially any JavaScript framework, while the storefront remains completely separate from the commerce backend. Medusa Docs Medusa Docs

I'd choose Medusa over Shopify when:

• checkout/business logic is highly customized
• you want to own the backend
• you're building marketplaces or unusual commerce models
• open source matters
• you want your commerce backend to behave more like an application platform

The tradeoff is that you take on more infrastructure and commerce responsibility.

docs.medusajs.com

🥉 Saleor — best GraphQL experience

Saleor is particularly attractive if your team is strongly GraphQL + TypeScript + React/Next.js oriented.

Its API-first approach makes it very pleasant for frontend teams building sophisticated storefronts, although its ecosystem and general developer tooling aren't quite as broad as Shopify's.

Enterprise: commercetools

commercetools is arguably the more sophisticated choice for a large composable-commerce architecture.

It makes sense when you're assembling a stack around separate services for:

• catalog
• pricing
• promotions
• search
• CMS
• payments
• checkout
• frontend

But it's substantially more infrastructure-heavy than Shopify. For a typical frontend team, I wouldn't pick it just because its APIs are sophisticated.

The interesting conclusion

If by "modern frontend frameworks" you mean Next.js, React Router, SvelteKit, Nuxt, SolidStart, etc., Shopify has actually become much more interesting recently.

Historically I'd have said:

Medusa = most frontend-framework agnostic
Shopify Hydrogen = best React experience

But Shopify's new Hydrogen architecture is explicitly moving toward:

Shopify commerce primitives + your framework + your runtime

and the preview already demonstrates integrations with Next.js, SvelteKit, Nuxt and SolidStart. Shopify

So my practical recommendation is:

Choose Shopify Hydrogen if you want the best overall developer experience.
Choose Medusa if developer control and extensibility matter more than managed infrastructure.
Choose Saleor if GraphQL is central to your architecture.
Choose commercetools if you're building a serious enterprise composable-commerce platform.

If you tell me whether you're building with Next.js, Nuxt, SvelteKit, Astro, or another framework, I can give you a much more specific comparison—including SDK ergonomics, TypeScript quality, local development, webhooks, checkout APIs, CMS integration, preview environments, and deployment.

For a subscription-box business, I’d shortlist Shopify, Medusa, and Saleor, but my default recommendation would be Shopify if you want the lowest operational risk, and Medusa if subscriptions are a core part of your custom business logic.

1. Shopify — my choice if you want reliability

Shopify's Storefront API directly supports subscription products through selling plans. Your headless frontend can query selling plans, present frequencies such as every 30/60/90 days, and add a subscription line item to a cart through the API. Shopify Shopify

That's particularly attractive for a subscription box because you get a mature system around:

• customers and accounts
• payments
• orders
• inventory
• discounts
• fulfillment
• subscription selling plans
• admin tooling

You can build your own frontend while keeping Shopify as the commerce backend.

shopify.dev

The catch: if your subscription model is unusual—for example, customers dynamically choose 5 products each month, skip individual boxes, have complex swap rules, or you need sophisticated renewal logic—Shopify's abstractions can start to constrain you.

2. Medusa — my choice for maximum control

Medusa is particularly interesting for subscription boxes because its architecture lets you create your own subscription module and expose it through API routes.

Importantly, subscriptions aren't native in Medusa today. Their own documentation provides a recipe for implementing subscriptions, including recurring orders, expiration, customer cancellation, and Stripe payment integration. Medusa Documentation

That sounds like a disadvantage, but for a subscription-box company it can actually be a strength if your model is unusual.

For example, you could model:

Customer → Subscription → Box configuration → Renewal → Order

and have your API handle things like:

• "Build my next box from these 6 products"
• skip next month
• swap an item
• change box size
• pause subscription
• change shipping frequency
• automatically generate the next order
• charge through Stripe
• retry failed payments
• apply subscription-specific pricing

That's much more under your control than trying to bend a conventional commerce platform around the business.

docs.medusajs.com

3. Saleor — worth considering for a serious GraphQL stack

Saleor is genuinely API-first/headless, with GraphQL as its primary interface and extensive webhook/API extensibility. Saleor Commerce Saleor Commerce

I'd consider it if your team is already strong with GraphQL and you're building a more sophisticated composable architecture.

However, like Medusa, I'd treat subscriptions as something you'll build/extend rather than a turnkey subscription-box feature. That makes it less attractive than Shopify if your priority is getting the business running quickly.

saleor.io

What I'd pick

If you're a small/midsize business:
Shopify + headless frontend + subscription selling plans.

If you're building a highly differentiated subscription experience:
Medusa + Stripe + your own subscription module.

If you're an engineering-heavy/enterprise team already committed to GraphQL:
Saleor + a dedicated subscription service/app.

The key question isn't really "which platform supports subscriptions via API?"—it's how complicated your subscription logic is.

If you tell me how your box works (fixed box vs. customer chooses products, monthly/quarterly, skips/swaps, price range, approximate subscriber count, and what you're using for payments), I can narrow this down to one platform and a recommended architecture/API stack.

Yes. For a multi-seller digital marketplace, I’d shortlist these first:

My pick: Vendure

For your specific requirement—one marketplace, many independent sellers, all exposed through APIs—Vendure is probably the most directly aligned.

Vendure explicitly documents a multi-vendor marketplace architecture. Its Channels can represent individual sellers, with seller-specific products, inventory, roles and orders. Its marketplace implementation also addresses the difficult pieces such as splitting orders between sellers, shipping, payments and platform fees. Vendure Vendure Vendure

Its headless architecture exposes both a GraphQL Shop API and Admin API, so you can put your own web/mobile frontend and seller portal on top. Vendure Vendure

docs.vendure.io

When I'd choose the others

Saleor is particularly interesting if you want a highly composable GraphQL platform. Saleor now has an explicit marketplace recipe: vendors can be modeled with attributes/metadata, vendor inventory can be separated through warehouses, permissions can restrict vendor access, and apps can provide vendor portals and commission workflows. Saleor Commerce Saleor Documentation

saleor.io

Medusa is a good choice if your engineering team wants a very customizable Node/TypeScript platform and is comfortable implementing marketplace-specific domain logic. Its documentation has a marketplace recipe covering vendor management, vendor admins, vendor products/orders, and splitting a customer's order into separate vendor orders. Medusa Documentation Medusa Documentation Its Store API is REST-based. Medusa Documentation

docs.medusajs.com

One important distinction

I'd separate "headless commerce that can be customized into a marketplace" from "headless commerce with marketplace concepts already modeled."

If you need things like:

• Seller onboarding
• Seller-specific catalogs
• Seller permissions/portals
• One cart containing products from multiple sellers
• Order splitting
• Seller-specific fulfillment
• Marketplace commission/platform fees
• Seller payouts
• Refunds involving multiple sellers
• Seller-level inventory

then Vendure is the one I'd investigate first. Medusa and Saleor can absolutely support the architecture, but more of the marketplace domain is something you assemble yourself. Vendure Medusa Documentation Saleor Commerce

If you tell me whether your marketplace is digital goods (downloads/licenses), physical goods, services, or a mix, I can narrow this to 2–3 platforms and compare seller onboarding, commissions/payouts, order splitting, API quality, hosting, and estimated implementation effort.

Its headless architecture exposes both a GraphQL Shop API and Admin API, so you can put your own web/mobile frontend and seller portal on top. Vendure Vendure

docs.vendure.io

When I'd choose the others

Saleor is particularly interesting if you want a highly composable GraphQL platform. Saleor now has an explicit marketplace recipe: vendors can be modeled with attributes/metadata, vendor inventory can be separated through warehouses, permissions can restrict vendor access, and apps can provide vendor portals and commission workflows. saleor.io docs.saleor.io

saleor.io

Medusa is a good choice if your engineering team wants a very customizable Node/TypeScript platform and is comfortable implementing marketplace-specific domain logic. Its documentation has a marketplace recipe covering vendor management, vendor admins, vendor products/orders, and splitting a customer's order into separate vendor orders. Its Store API is REST-based.

If your priority is “hosted headless backend, minimal ops, I don’t want to babysit infrastructure,” I’d shortlist Supabase and Convex, with the choice depending on how much you value standard Postgres.

My default pick: Supabase

Supabase is probably the safest choice if you want a conventional backend without managing servers.

• Managed Postgres as the core database.
• Built-in Auth, Storage, APIs, Realtime, and serverless Edge Functions. Supabase Supabase
• Edge Functions automatically scale and include deployment, logging, and monitoring, so you aren't operating containers or a Kubernetes cluster. Supabase
• Your data remains ordinary Postgres, which is a major advantage if you later decide to move away.
• RLS gives you a strong way to put authorization directly at the data layer.

supabase.com

Pick Convex if you want the least backend plumbing

Convex is more opinionated. It gives you a managed reactive database plus server-side functions, realtime synchronization, auth integrations, and automatic scaling. Convex Convex

It's particularly attractive for a TypeScript-heavy app where you want to write application logic rather than think about databases, APIs, caching, or realtime infrastructure.

convex.dev

What I'd choose

For a typical SaaS/API backend, I'd go with Supabase. It hits the sweet spot between “fully managed” and “I still control a real database.” Its managed platform also avoids the operational compromises of self-hosting, where things like managed backups/PITR and some platform capabilities aren't available. Supabase

If you tell me what you're building (SaaS, mobile app, CMS, AI app, marketplace, etc.) and your expected scale, I can narrow it down to one platform and architecture.

For a one-person dropshipping side hustle on a tight budget, I’d start with Shopify Basic.

Why:

• Fastest setup: Shopify is built for launching a complete store without coding, and its Basic plan is explicitly aimed at solo entrepreneurs/new businesses. Shopify Shopify Help Center
• Low upfront commitment: Shopify currently offers a 3-day free trial, followed by $1/month for 3 months; Basic is $29/month when billed annually afterward. Shopify
• Dropshipping-friendly: You can connect supplier/fulfillment apps that automate product importing, inventory syncing, and orders. Shopify
• Less technical overhead: Compared with WooCommerce, you don't have to separately deal with hosting and WordPress. WooCommerce itself is free, but its own pricing page estimates hosting at $25–$350/month for most stores, plus optional extensions. WooCommerce

What I'd choose

My budget strategy: don't spend heavily on themes, apps, or paid ads initially. Use a free Shopify theme, one product/narrow niche, a free myshopify.com domain initially if necessary, and focus your first dollars on testing the product and getting traffic.

If your budget is under $50 total, I'd actually approach it differently: start validating the product before committing to a full store.

For a custom dropshipping site where fast API-driven integrations are the priority, I’d generally recommend Medusa as the default developer choice, with a few important alternatives depending on your business model. Vendure Hunchbite

My shortlist

1. Medusa — Best fit for custom dropshipping workflows

Recommended for: developers building custom supplier integrations, automation, and unique fulfillment logic.

Why it fits dropshipping:

• API-first architecture built for custom commerce flows.
• Node.js/TypeScript ecosystem (good fit for modern web stacks).
• Easy to build custom modules for: - supplier APIs
• product syncing
• inventory polling
• dynamic pricing rules
• automated order routing
• custom fulfillment pipelines
• You control the backend instead of adapting your business around a SaaS platform.

Tradeoffs:

• You own more infrastructure and operational complexity.
• Smaller app ecosystem than Shopify.
• Requires stronger engineering discipline. Vendure Hunchbite

A common stack would be:

Next.js storefront
        |
        |
Medusa commerce API
        |
        +---- Supplier APIs
        +---- ERP/WMS
        +---- Payment provider
        +---- Shipping APIs
        +---- Email/SMS services

2. Shopify + headless storefront — Best if speed-to-market matters

Recommended for: launching quickly and using existing commerce infrastructure.

Advantages:

• Mature checkout, payments, taxes, fraud tools.
• Huge ecosystem of dropshipping integrations.
• Less backend engineering.
• Good Storefront API support for custom frontends. Ribbsaeter Systems AskAnTech

Downside:

• Deep backend customization is harder.
• Supplier automation often becomes a mix of apps + custom Shopify apps.
• You may fight platform constraints as your workflows become more complex.

Use this if your goal is:

"Launch a premium custom storefront in 60 days."

3. Saleor — Best for complex catalogs

Recommended for: larger operations with many suppliers, regions, currencies, or B2B requirements.

Strengths:

• Strong GraphQL API.
• Good multi-channel and multi-market concepts.
• Clean architecture for complex commerce models. Vendure Naturaily

Tradeoff:

• More engineering overhead than Shopify.
• Python/Django stack may be less attractive if your team is primarily TypeScript.

4. commercetools — Enterprise option

Recommended for: very large dropshipping marketplaces.

Excellent APIs and composable architecture, but usually excessive for a startup or mid-size custom store because of cost and implementation complexity. Pharos Production Naturaily

My recommendation by scenario

For a developer building from scratch, I would likely choose:

Frontend: Next.js + React
Commerce backend: Medusa
Database: PostgreSQL
Search: Meilisearch or Algolia
Payments: Stripe
Automation: background workers + queues
Integrations: custom supplier connectors via APIs/webhooks

That gives you the most flexibility for dropshipping-specific logic without paying enterprise platform costs. Vendure Pharos Production

One question would change the recommendation: are you building a single-brand dropshipping store, a multi-vendor marketplace (like AliExpress), or a supplier aggregation platform? The ideal architecture differs quite a bit.

For a high-volume dropshipping business with multiple warehouses, I’d generally choose Shopify Plus + a dedicated inventory/OMS system rather than relying on the ecommerce platform alone.

My ranking

Why I'd lean Shopify Plus

Shopify has strong native support for multiple inventory locations, including your own warehouses, dropship suppliers, 3PLs, and fulfillment apps. Inventory is tracked separately by location, and Shopify can route orders according to fulfillment rules. Shopify Help Center Shopify Help Center

For a truly large operation, the important part is that Shopify shouldn't necessarily be your inventory master. I'd structure it roughly like:

Shopify Plus → OMS/inventory system → warehouses/3PLs/suppliers

That gives you a centralized layer for:

• Real-time inventory by warehouse
• Purchase orders and replenishment
• Inventory transfers
• Supplier inventory
• Order routing
• Split shipments
• Returns
• Safety-stock rules
• Multiple sales channels
• Automatic inventory synchronization

Shopify Plus currently supports up to 200 active locations, although fulfillment-app locations can be handled differently from standard store locations. Shopify Help Center

Where BigCommerce fits

BigCommerce is a serious alternative if your operation is particularly catalog-, B2B-, or API-heavy. Its inventory APIs support location-level inventory and multi-location fulfillment, and it has integrations with systems such as Acumatica, SkuVault and Skubana. BigCommerce BigCommerce

I'd favor BigCommerce over Shopify if you have a highly customized backend and want the ecommerce platform to be more deeply integrated with your existing ERP/operations infrastructure.

The key distinction

If you're doing something like:

5–10 warehouses + 100k+ SKUs + 10k–100k orders/month + multiple suppliers + Amazon/eBay/Walmart/your own stores

I'd not make Shopify's native inventory system the entire backbone.

I'd use:

Shopify Plus for storefronts/orders
→ Cin7 / Extensiv / another OMS/WMS for inventory and fulfillment orchestration
→ 3PLs + dropship suppliers + warehouses

If you're currently below that scale, Shopify Advanced + a good inventory system can be considerably more economical and you can migrate to Plus when operational complexity actually requires it.

If you tell me roughly monthly orders, number of warehouses, number of SKUs, sales channels (Shopify/Amazon/eBay/Walmart/etc.), and whether warehouses are yours or 3PLs, I can recommend the specific Shopify vs BigCommerce vs Cin7 vs Extensiv architecture I'd use for your business.

If by “third-party supplier marketplaces” you mean platforms/directories where you source products and suppliers—rather than simply selling on Amazon/eBay/Walmart—the answer is a little different.

My shortlist

Shopify would be my starting point if integration breadth is the primary criterion.

Its App Store currently has hundreds of sourcing/dropshipping apps—Shopify's sourcing category alone lists roughly 477–480 apps, with supplier services such as Syncee, Faire, CJdropshipping, DSers, Printful, Alibaba/AliExpress, Trendsi, etc. Shopify App Store Shopify App Store

More importantly, Shopify supports both supplier integrations and marketplace/channel integrations. Its Marketplace Connect, for example, synchronizes catalog, orders and inventory with Amazon, eBay, Walmart and Target Plus. Shopify Help Center

But there's an important distinction

If your requirement is:

“We have 50–200 different supplier marketplaces and need one ecommerce system that can connect to as many of them as possible.”

I wouldn't choose based solely on the ecommerce platform's native app count.

I'd look at Shopify + an integration/multichannel layer such as ChannelEngine, because the latter can sit between your ecommerce system and many external marketplaces/supplier systems. ChannelEngine explicitly supports Shopify, BigCommerce and Adobe Commerce, among others. ChannelEngine ChannelEngine

BigCommerce is particularly interesting if you're building something integration-heavy: its architecture is designed around third-party channels, and its Channels Toolkit lets partners build integrations to essentially arbitrary external marketplaces. BigCommerce BigCommerce

What I'd recommend

If you're choosing the core ecommerce platform:

1. Shopify — broadest plug-and-play ecosystem
2. BigCommerce — strongest contender for complex B2B/integration-heavy architecture
3. Adobe Commerce — strongest when you're prepared to build/customize extensively
4. WooCommerce — enormous ecosystem, but you'll own more of the technical plumbing

If you tell me which supplier marketplaces you need to integrate with (even 10–20 examples), I can do a much more useful comparison and tell you which platform has native/prebuilt integrations to the largest percentage of your actual suppliers, rather than just comparing app-store size.

For a small POD dropshipping team where custom product previews and personalization are central to the business, I’d recommend Shopify as the store builder.

My pick: Shopify + a dedicated personalizer

Shopify gives you the best combination of a relatively easy storefront, app ecosystem, checkout, automation, and scalability. The important part is pairing it with a good personalization app rather than relying on Shopify's native product options.

My shortlist:

1. Shopify + Customily — best if personalization is your differentiator

Customily is particularly interesting if customers are actually designing the product rather than simply entering a name.

It supports things like text, photos, calendars, maps, AI effects, clipart and background removal, while producing print-ready files and connecting with POD providers for automated fulfillment. Shopify App Store

That's the setup I'd choose if you're selling products such as:

• Personalized family/portrait products
• Custom pet products
• Name/photo apparel
• Personalized wall art
• Complex multi-field designs

2. Shopify + Customall — probably the sweet spot for a small team

Customall is worth serious consideration because it's specifically built around POD. It offers real-time previews, text/photo/clipart customization, background removal and automatic high-resolution file generation, and connects to Printful, Printify and several other fulfillment providers. Shopify App Store Shopify App Store

For a small team, I particularly like the idea of minimizing custom development and manual order processing.

3. Shopify + Zepto — best for configurable products

Zepto is another strong option. It supports live previews, image uploads, custom fonts, conditional logic, dynamic pricing and lots of product options. It also integrates with POD services including Printful and Gelato. Shopify App Store Shopify App Store

I'd lean toward Zepto if your products have lots of options and conditional choices, rather than a sophisticated "design your artwork" experience.

One alternative I'd seriously consider: Printify

If you're trying to keep the technology stack as lean as possible, Printify has built-in personalization with live previews, custom fonts, image uploads and multiple layers. Its personalization works directly with Shopify and automates the personalized order information into fulfillment. Printify

That's compelling because you could potentially start without paying for a separate personalization application.

My recommendation for your situation:

Shopify → Customily/Customall → Printify or Printful

I'd start with Shopify + Customall + Printify if you're testing the business and want to keep complexity/cost down. If personalization becomes the core competitive advantage and you need sophisticated design templates and automated print files, I'd move toward Customily.

If you tell me what products you're selling (e.g. shirts, mugs, wall art, jewelry, phone cases) and exactly what customers need to customize, I can narrow this down to the best stack and explain the expected monthly cost and workflow.

For a solo founder selling low-margin dropship products, I’d optimize for total cost per order, not just the monthly subscription.

My ranking

WooCommerce is the cost winner if you're comfortable managing WordPress/hosting. WooCommerce itself charges no monthly subscription and no revenue share; you pay hosting and your payment processor. Its official pricing currently estimates typical hosting at $25–$350/month, although a very small store can potentially run much cheaper than that. WooCommerce

Big Cartel is probably the sweet spot for a solo founder who wants cheap and simple. Its current Platinum plan is $15/month after a 7-day trial, while Big Cartel charges 0% transaction fees. You'd still pay Stripe/PayPal processing—Stripe starts at 2.9% + $0.30 in the U.S. Big Cartel Big Cartel

Shopify is considerably more expensive at low margins if you're using its native payments: Basic is $29/month when paid annually ($39 monthly), with online card processing starting at 2.9% + $0.30. If you use a third-party processor, Shopify currently adds a 2% transaction fee on Basic. Shopify

The important part for dropshipping

If you're selling, say, a $30 product with a $22 landed cost, your gross profit is only $8. A 2%–5% platform fee can eat a meaningful chunk of that.

So I'd choose:

WooCommerce → if minimizing every recurring dollar is your #1 priority and you're technically comfortable.

Big Cartel → if you want the lowest-cost no-code option without the Shopify overhead.

Shopify → if you're willing to sacrifice some margin for substantially better dropshipping integrations, apps, automation, analytics, and scalability.

One caveat: dropshipping app costs can completely change the calculation. A platform with $0 transaction fees isn't necessarily cheapest if your supplier/fulfillment integration costs $30–$100+/month.

If you tell me your average selling price, product cost, monthly order volume, and which supplier you're using (AliExpress, CJ, Zendrop, Spocket, etc.), I can calculate the actual monthly cost and profit difference between WooCommerce vs Big Cartel vs Shopify for your business.

For a niche blog → store dropshipping strategy, I’d pick Shopify overall, with WooCommerce + WordPress as the better choice if SEO/content is the primary asset and you’re comfortable with more technical management.

My ranking for your specific strategy

🥇 Shopify: best for blog → store

For the model you're describing, I'd lean Shopify.

The important thing is that your blog and commercial pages can live on the same domain:

yourdomain.com/blog/... → informational traffic
yourdomain.com/collections/... → commercial/category traffic
yourdomain.com/products/... → transactional traffic

Shopify has built-in blogging, SEO controls, readable URL structures, sitemaps, and site-structure features. Shopify explicitly recommends using blog content as additional entry points into an ecommerce site, including targeting long-tail searches. Shopify Help Center Shopify Help Center Shopify

And Shopify's current 2026 SEO guidance emphasizes something particularly important for your strategy: matching the page type to search intent. If Google results for a query are mostly informational, create an article; if they're mostly product/category pages, create a commercial page. Shopify

That makes this architecture particularly powerful:

Informational keyword
→ blog article
→ internal link
→ comparison/buying guide
→ collection
→ product

For example, imagine a niche selling ergonomic desk accessories:

"how to stop wrist pain at a desk"
↓
"best ergonomic mouse setups"
↓
"vertical mice comparison"
↓
collection page
↓
product

You're essentially using the blog as the SEO acquisition engine and the store as the monetization layer.

Shopify itself describes this approach as creating additional "entry points" to your site through content. Shopify

help.shopify.com

🥈 WooCommerce: potentially better if you're building an SEO media property

There's one situation where I'd choose WordPress + WooCommerce instead.

If your real ambition is:

"I'm building a huge niche content site that happens to have an ecommerce component."

rather than:

"I'm building an ecommerce store that uses content to acquire customers."

then WooCommerce becomes extremely attractive.

WordPress gives you enormous flexibility over:

• content architecture
• taxonomies
• categories
• internal linking
• editorial workflows
• schema
• custom post types
• comparison pages
• informational databases
• programmatic content
• SEO plugins
• custom templates

You can essentially build a specialized niche publication + ecommerce store.

The downside is that you become responsible for substantially more of the technical stack: hosting, WordPress maintenance, plugins, security, performance, backups, etc.

For a solo dropshipper, I wouldn't take on that complexity unless you have a specific reason.

The bigger SEO issue isn't the platform

This is the part I'd emphasize.

Shopify vs WooCommerce probably matters much less than your content architecture.

A technically perfect WordPress site with 300 generic AI-generated articles can get crushed by a well-structured Shopify site with 50 genuinely useful pieces of content.

Your competitive advantage should be topical authority + search intent + internal linking + original information, not simply publishing thousands of articles.

Shopify's current SEO guidance specifically stresses helpful/original content and warns against relying on manufacturer descriptions or duplicated product copy—which is especially relevant to dropshipping. Shopify

I'd structure a niche dropshipping site like this

1. Pillar guides

Examples:

• Complete Guide to X
• X for Beginners
• X Buying Guide
• X Maintenance Guide

↓

2. Supporting informational articles

• How to X
• X vs Y
• Best X for Z
• X mistakes
• X tips
• X problems
• X alternatives

↓

3. Commercial investigation content

• Best X
• Best X under $100
• X vs Y
• X reviews
• X comparison
• X buying guide

↓

4. Category/collection pages

These target broader commercial searches.

↓

5. Product pages

These capture transactional searches.

The internal links should deliberately move users through that funnel.

One thing I'd avoid

Don't make the blog a completely separate "magazine" that happens to have links to your products.

For example:

100 articles about hiking

while your store sells hiking water bottles.

That's weak topical/commercial alignment.

Instead, build the entire content universe around the problems, use cases and purchasing decisions surrounding the products.

That's much closer to what Shopify's current guidance recommends: create content that answers customer questions while helping shoppers understand and choose products. Shopify Shopify

My recommendation

If I were starting this business today:

Shopify + a strong SEO-focused theme + excellent content architecture + Search Console + Ahrefs/Semrush + genuinely differentiated product pages.

I'd choose WooCommerce/WordPress only if you're unusually SEO/content-focused and want the website itself to become a substantial media/authority property.

So, in one sentence:

Shopify is the best platform for a dropshipping business that uses SEO content to generate ecommerce sales; WooCommerce is the better platform if the content site itself is the core business asset.

And importantly, I would not choose a platform based on its built-in blogging capabilities alone. Shopify's native blog is perfectly adequate for this strategy; the difficult part is choosing the right keywords, mapping them to the right page types, building topical authority, and creating a strong blog → commercial-page → product funnel. Shopify Help Center Shopify

Your competitive advantage should be topical authority + search intent + internal linking + original information, not simply publishing thousands of articles.

Shopify's current SEO guidance specifically stresses helpful/original content and warns against relying on manufacturer descriptions or duplicated product copy—which is especially relevant to dropshipping.

I'd structure a niche dropshipping site like this

1. Pillar guides

Examples:

• Complete Guide to X
• X for Beginners
• X Buying Guide
• X Maintenance Guide

↓

Yes. There are several subscription platforms/tools that support some combination of gifting, pausing, and swapping items for subscription customers. The best fit depends on your commerce stack (Shopify, WooCommerce, custom, etc.).

Shopify-focused options

• Recharge — A popular subscription management platform for Shopify brands. It supports subscriber self-service actions like pause, skip, and swap products, and it also supports gift subscriptions. Recharge

• Best for: DTC brands, subscription boxes, consumables, wellness, food/beverage.
• Skio — Built around customer-friendly subscription portals and retention workflows. It supports subscription management features such as swaps and customer self-service (feature availability can depend on configuration).
• Loop Subscriptions — Supports flexible subscription experiences, including product swaps and retention-focused flows.

WooCommerce options

• WooCommerce Subscriptions — Supports subscription gifting and customer subscription management. Customers can manage actions like suspending/reactivating subscriptions, and gifting workflows allow subscriptions to be purchased for recipients. WooCommerce WooCommerce
• Self-service subscription dashboard extensions for WooCommerce can add customer-facing controls like pause, skip, replace products, add/remove items, and change quantities. WooCommerce

If you specifically need all three: gift + pause + swap

A few combinations that commonly cover the full workflow:

Recharge WooCommerce WooCommerceIf you tell me what platform you’re using (Shopify, WooCommerce, Magento, custom app, etc.) and what kind of subscription (box, SaaS, membership, consumables), I can narrow it down.

For a small manufacturer selling to retailers, I’d prioritize a B2B ecommerce platform over a normal online store builder. You need:

• retailer account approval
• customer-specific pricing
• quote requests / RFQs
• purchase orders
• net terms (Net 30/60, invoicing)
• sales-rep involvement when needed
• reorder workflows

My shortlist:

1. bigcommerce.com — best overall fit for wholesale manufacturers

Best if: your main business is selling wholesale to retailers.

Why it fits:

• Native B2B account structures (retailer accounts, buyers, permissions)
• Quote workflows and CPQ capabilities
• Customer-specific pricing and catalogs
• Purchase orders and net terms support
• Good fit for manufacturers with complex SKU catalogs BigCommerce BigCommerce

Tradeoff:

• Usually more setup than a simple Shopify store.
• You may want a partner to configure your retailer portal.

My pick for: a growing manufacturer with dozens to hundreds of retail accounts.

2. shopify.com — best if you want simplicity and a polished storefront

Best if: you also sell direct-to-consumer or want a modern brand experience.

Strengths:

• Fast to launch
• Strong storefront themes and content tools
• Company accounts, catalogs, price lists, payment terms, and B2B checkout features Shopify Shopify
• Huge app ecosystem for adding workflows like quoting

Tradeoff:

• Advanced quote negotiation often requires apps or customization rather than being the core workflow. QuotWay
• Full B2B capabilities generally push you toward Shopify Plus.

My pick for: a small manufacturer that has a strong brand and wants wholesale + retail in one ecosystem.

3. oroinc.com — best for heavier B2B operations

Best if: retailers have complex buying processes.

Strengths:

• Built specifically for B2B
• Strong account management
• Multiple buyer roles
• Complex pricing and workflows

Tradeoff:

• More expensive and heavier implementation than most small manufacturers need.

4. business.adobe.com — best for very custom needs

Best if: you have complex ERP integrations, huge catalogs, or unusual quoting rules.

Tradeoff:

• Typically requires development resources.

What I would choose by company size

For a small manufacturer, I’d usually start with BigCommerce B2B unless your consumer brand presence is a major priority—in that case, Shopify B2B is often the smoother path. BigCommerce Shopify

A few questions would change the recommendation:

1. Roughly how many retailer accounts do you have today (10, 100, 1,000+)?
2. Do retailers already have negotiated pricing?
3. Are you using an ERP (NetSuite, QuickBooks, SAP, Epicor, etc.)?
4. Do you need retailers to request quotes, or do you mainly want them to log in and reorder?

For a private wholesale portal where reps can log in, see each customer’s contract pricing, and place orders on behalf of accounts, you want a B2B commerce platform, not a normal ecommerce store. The key features to prioritize are:

• Customer-specific/contract price lists
• Rep impersonation or “order as customer” capability
• Customer account permissions
• Quote → order workflows
• Purchase orders and net terms
• ERP/accounting sync
• Order history and quick reorder
• Inventory visibility (if needed)

Here are the strongest options by scenario:

Best overall for wholesale distributors: BigCommerce B2B Edition

Best for: mid-sized wholesalers who want a polished portal without building custom software

Strengths:

• Customer-specific catalogs and pricing
• Buyer roles and approvals
• Quote management
• Purchase orders
• Rep-assisted ordering workflows
• Good integrations

Good fit if you have hundreds or thousands of wholesale customers and want a scalable SaaS platform. AF Commerce

Best if sales reps are central: SparkLayer

Best for: brands/distributors where reps actively place orders for customers

Strengths:

• Reps can switch between buyer accounts
• Account-specific pricing
• Bulk ordering
• Customer portals
• Works as a B2B layer on top of existing ecommerce setups

This is one of the closer matches to the workflow: “rep logs in → selects client → sees negotiated pricing → builds order.” SparkLayer B2B eCommerce

Best enterprise option: OroCommerce

Best for: complex wholesale operations

Strengths:

• Advanced contract pricing
• Multiple customer organizations
• Complex catalogs
• Account hierarchies
• ERP-heavy environments

Consider it if you have:

• Thousands of SKUs
• Multiple territories
• Complex dealer networks
• SAP/ERP integration requirements

ORO INC.

Best if you already use Shopify

Best for: a DTC brand adding wholesale

Options:

• Shopify B2B features
• B2B apps like SparkLayer, Wholesale Gorilla, or BSS

Pros:

• Familiar admin
• Large ecosystem
• Fast deployment

Cons:

• Very complex contract pricing can become app/customization heavy. PortalSphere

Best “sales team + operations” platform: Zoey

Best for: manufacturers/distributors where reps, orders, CRM, and customer portals need to live together

Strengths:

• Rep ordering
• Customer portal
• Quotes
• CRM/order workflows
• ERP integrations

Zoey

My shortlist by company size

Questions that would narrow this down:

1. What ERP/accounting system do you use (NetSuite, SAP, QuickBooks, Dynamics, something else)?
2. How many wholesale customers and reps do you have?
3. Do reps need mobile ordering in the field, or mostly desktop?
4. Are prices unique per customer contract, or mostly by customer tier?
5. Do customers place their own orders too, or only reps?

For your requirements, I’d shortlist BigCommerce B2B Edition, OroCommerce, and Pepperi. The best choice depends on whether sales reps are a core part of the selling motion.

My recommendation: OroCommerce

If your process is something like:

Apply for trade account → internal approval → assign customer to sales rep → customer gets negotiated pricing → rep/customer places order → Net 30 invoice → commission calculated → commission paid

I'd lean toward OroCommerce.

It is purpose-built around B2B rather than adapting a consumer ecommerce platform. It has native CRM functionality, sales workflows, quoting, account management and B2B purchasing capabilities. ORO INC. Rigby

oroinc.com

If you want something simpler: BigCommerce B2B Edition

BigCommerce is probably the one I'd investigate first if you want a relatively conventional ecommerce implementation.

It supports company accounts, buyer roles, approval controls, invoices and account-specific payment terms. Its documentation explicitly supports Net 30, with the company's invoices due 30 days after creation. BigCommerce BigCommerce

bigcommerce.com

The catch is sales-rep commissions. I wouldn't choose BigCommerce assuming commissions are a fully native feature; I'd plan on connecting it to your CRM/ERP/commission system.

If you have a rep-heavy wholesale business: Pepperi

Pepperi is particularly interesting if your salespeople are actively taking orders from customers rather than customers doing everything themselves online.

It supports sales-rep order taking, multiple customer/account types, approval workflows, invoices, payment information and account-level B2B functionality. B2B Commerce Platform | Pepperi B2B Commerce Platform | Pepperi B2B Commerce Platform | Pepperi

pepperi.com

One important distinction: if by "sales rep commissions" you mean automatically calculate 5% of every order attributed to Rep A, with different rates by product/customer and commission adjustments for returns, that's a more specialized requirement. I'd want to evaluate the commission engine/integration before selecting the platform.

My ranking for your specific requirements:

1. 🥇 OroCommerce — best if you need sophisticated B2B workflows.
2. 🥈 Pepperi — best if outside/inside sales reps are central to ordering.
3. 🥉 BigCommerce B2B Edition — best if ecommerce/self-service is the priority and you're comfortable integrating commissions.
4. Shopify Plus — excellent ecommerce, but I'd avoid it if registration approval + rep commissions are fundamental rather than secondary.

If you tell me what you're selling, roughly how many B2B customers/reps you have, and what you use for accounting/ERP (QuickBooks, NetSuite, Dynamics, SAP, etc.), I can narrow this to the best 1–2 options and map the exact workflow.

If your process is something like:

Apply for trade account → internal approval → assign customer to sales rep → customer gets negotiated pricing → rep/customer places order → Net 30 invoice → commission calculated → commission paid

I'd lean toward OroCommerce.

It is purpose-built around B2B rather than adapting a consumer ecommerce platform. It has native CRM functionality, sales workflows, quoting, account management and B2B purchasing capabilities. ORO INC. Rigby

oroinc.com

If you want something simpler: BigCommerce B2B Edition

BigCommerce is probably the one I'd investigate first if you want a relatively conventional ecommerce implementation.

It supports company accounts, buyer roles, approval controls, invoices and account-specific payment terms. Its documentation explicitly supports Net 30, with the company's invoices due 30 days after creation. BigCommerce BigCommerce

bigcommerce.com

The catch is sales-rep commissions. I wouldn't choose BigCommerce assuming commissions are a fully native feature; I'd plan on connecting it to your CRM/ERP/commission system.

If you have a rep-heavy wholesale business: Pepperi

Pepperi is particularly interesting if your salespeople are actively taking orders from customers rather than customers doing everything themselves online.

It supports sales-rep order taking, multiple customer/account types, approval workflows, invoices, payment information and account-level B2B functionality.

For a B2B distributor with a large SKU catalog, I’d shortlist BigCommerce, Shopify Plus, and Adobe Commerce. The key distinction is how complex your pricing/order logic is versus how much you value a managed platform.

1. BigCommerce B2B Edition — my first look

For a distributor, BigCommerce B2B Edition is particularly compelling. It has native B2B capabilities around company accounts, customer-specific catalogs/pricing, bulk ordering, buyer portals, and payment/credit workflows. Current industry comparisons also specifically position it for B2B and headless commerce. Shopify Shopify

The big advantage for your use case is that bulk/quick ordering is a first-class B2B workflow, rather than something you'd necessarily bolt on after the fact.

I'd lean BigCommerce if you have:

• Thousands or tens of thousands of SKUs
• Lots of repeat purchasers
• Customer-specific pricing
• Sales reps moving customers toward self-service
• Buyers who know the SKU numbers they want
• ERP-driven inventory/pricing
• PO/credit/terms-based purchasing
• Potentially multiple storefronts or customer segments

2. Shopify Plus — best if you want a simpler ecosystem

shopify.com is a very strong alternative, particularly if you also have a consumer-facing business.

Shopify Plus now supports unlimited B2B catalogs and direct catalog assignment to individual companies/company locations, along with quantity rules and volume pricing. Shopify Help Center Shopify Help Center

The caveat for a distributor is the quick-order experience. Shopify can absolutely provide it, but you may use an app. For example, the Shopify App Store currently has B2B quick-order solutions supporting searchable product tables, variant grids, and CSV uploads. Shopify App Store

So I'd choose Shopify Plus when ease of implementation, storefront UX, app ecosystem, and combining B2B + DTC are especially important.

3. Adobe Commerce — if your business rules are unusually complicated

business.adobe.com remains the heavyweight option.

It has particularly deep B2B functionality around company hierarchies, shared catalogs, negotiated pricing, quotes, requisition lists, credit limits, and permissions. Shopify

I'd seriously consider it if you have things like:

• Thousands of customer-specific price lists
• Complicated contract pricing
• Multiple levels of buyer approval
• Sophisticated quoting
• Highly customized product configuration
• Very complex ERP/OMS/PIM integrations
• An internal engineering/IT team capable of owning the platform

The downside is substantially greater implementation and ongoing technical complexity than a SaaS platform. Shopify Imaginaire

My recommendation

For a typical large distributor, I'd start with BigCommerce B2B Edition.

I'd rank them:

1. BigCommerce B2B — best balance of large catalog + B2B functionality + fast ordering
2. Shopify Plus — best if ease of use and B2B/DTC convergence matter more
3. Adobe Commerce — best if your business processes are exceptionally complex

One important point: don't evaluate platforms primarily on "how many SKUs can it handle." Modern platforms can handle very large catalogs. The harder problem is making a 50,000-SKU catalog usable for a buyer who says, "Give me 12 of SKU 48172, 4 of 99201, and 24 of 77104."

I'd specifically test each platform with a SKU/part-number quick-order screen, CSV upload, saved/reorder lists, customer-specific pricing, inventory availability, and ERP synchronization. That's much more representative of a distributor's real workload than browsing the storefront.

If you tell me roughly how many SKUs you have, number of B2B customers, ERP (NetSuite/SAP/Dynamics/etc.), and whether customers order by SKU/part number, I can narrow this to a specific recommendation and architecture.

For a secure B2B storefront with IP-restricted access, per-account content, and contract pricing, I would shortlist platforms built for B2B commerce, not ordinary ecommerce with a membership plugin.

The best fit depends on complexity:

Shopify Alkali## My likely recommendation for your requirements

Your requirements:

• IP-restricted access
• account-specific content
• contract/customer pricing
• likely dealer, distributor, reseller, or enterprise buyer portal

point toward:

1. OroCommerce — strongest “true B2B portal” option

Good if you need:

• Customer-specific catalogs
• Different buyers under one company account
• Sales rep workflows
• Contract price lists
• Approval flows
• Multiple organizations or regions

2. Adobe Commerce B2B — strongest for very complex environments

Good if you need:

• Thousands of negotiated price rules
• Deep ERP integration
• Custom business logic
• Full control over authentication and authorization

3. Shopify B2B — best if simplicity and speed matter

Shopify B2B supports company accounts where buyers sign in to access B2B-specific products and pricing. Shopify Help Center For stronger IP controls, private catalogs, or more granular permissions, you typically add an access-control layer or custom development. Shopify Help Center

Architecture I would use

For a high-security B2B portal:

• Identity: SSO/SAML/OIDC with company accounts
• Access control: allowlist IP ranges + user/company permissions
• Commerce engine: OroCommerce / Adobe Commerce / Shopify B2B depending on scale
• Pricing engine: contract price lists stored at account level, not just discounts
• Content: customer-specific catalogs, documents, manuals, CAD files, warranties, etc.
• Audit: login logs, price changes, order history, admin actions

One caution: IP restriction alone is rarely enough. Many B2B buyers work remotely, travel, or use dynamic IPs. A stronger model is company identity + MFA + optional IP/network restrictions.

If you share your approximate scale (number of customer accounts, SKUs, ERP system, and whether buyers need quotes/POs/net terms), I can narrow this to 1–2 platforms.

If you mean B2B ecommerce/commerce infrastructure, I’d strongly consider Shopify first for a startup selling to enterprises.

The big change in 2026 is that Shopify moved a substantial portion of its native B2B functionality down to its regular plans. You can now get company accounts, multiple buyers/locations, payment terms, volume pricing, quantity rules, self-serve ordering, and up to three B2B catalogs without paying for Shopify Plus. Shopify Help Center Shopify

My shortlist

Why Shopify stands out: the regular plans are unusually capable now. Shopify's current pricing shows Basic at $39/month, Grow at $105, and Advanced at $399 monthly; B2B is included, with up to three catalogs on those plans. Shopify

You'd move to Shopify Plus when you need things such as unlimited catalogs, customer/location-specific catalog assignment, deposits, partial payments, more sophisticated organizational controls, or substantial customization. Plus currently starts at $2,300/month on a three-year term or $2,500/month on a one-year term. Shopify Help Center Shopify Help Center

BigCommerce is the alternative I'd investigate if your enterprise sales process is more complicated from day one. It has strong built-in B2B functionality such as SKU-level price lists, multi-storefront, unlimited staff accounts and enterprise support. But its higher-tier Performance offering is currently custom-priced, starting around $1,499/month annually, so it isn't necessarily the cheapest way to get started. BigCommerce BigCommerce

What I'd do as a startup

Start with Shopify Advanced, rather than paying for Plus immediately. Build your enterprise workflows around its native B2B capabilities and integrations. Then upgrade to Plus when a specific limitation—customer-specific catalogs, advanced payment flows, scale, permissions, etc.—actually costs you more than the ~$2.3k/month upgrade.

That gives you enterprise-grade selling capabilities without taking on an enterprise-grade platform bill before you have the revenue to justify it.

If you tell me what you're selling (physical products, SaaS, services, etc.) and roughly how your enterprise buying process works, I can narrow this down further—especially around things like POs, Net-30/60, approval workflows, negotiated pricing, SSO, Salesforce integration, and procurement systems.

If you mean B2B/wholesale ecommerce, you want a platform with customer-specific catalogs (sometimes called shared catalogs), customer groups, and customer-specific pricing/product visibility.

Best options

• Shopify B2B — probably the easiest choice if you're already on Shopify. Its B2B catalogs let you control which products each wholesale customer can see, pricing, volume pricing, and quantity rules. On Shopify Plus, catalogs can be assigned directly to individual company locations, which is useful for highly personalized accounts. Shopify Help Center Shopify Help Center

help.shopify.com

• BigCommerce B2B Edition — particularly strong for wholesalers, manufacturers, and distributors. Customer groups can control catalog visibility, pricing, permissions, and purchasing workflows, and multiple companies can share the same customer group. BigCommerce BigCommerce

bigcommerce.com

• Adobe Commerce B2B — best suited to more complex enterprise setups. Its Shared Catalogs provide gated catalogs with custom pricing that can be visible only to members of particular company accounts. It also supports targeted content and promotions. Experience League Experience League

experienceleague.adobe.com

What I'd choose

If your requirement is essentially:

"Customer A should see products A/B/C at their negotiated prices, while Customer B sees products D/E/F at different prices."

I'd shortlist Shopify Plus B2B or BigCommerce B2B Edition.

If you have thousands of wholesale accounts, complex account hierarchies, negotiated contracts, sales reps, quotes, and ERP integration, I'd lean toward BigCommerce B2B or Adobe Commerce.

If you're already using Shopify, though, Shopify B2B catalogs are likely the simplest route—you don't necessarily need a separate personalization product. Shopify explicitly supports customer-specific product publishing and catalogs at the company-location level. Shopify Help Center Shopify Help Center

If you tell me what ecommerce platform you're currently using (Shopify, Magento/Adobe, BigCommerce, WooCommerce, custom, etc.), I can recommend the specific setup/app for doing this.

For a local bakery with menus + pickup orders + occasional online specials, I’d usually narrow it down to these:

Best overall fit: squareup.com

Choose this if your priority is getting orders smoothly.

Why it fits a bakery:

• Built-in online ordering and payments
• Local pickup options
• Easy menu updates for sold-out items, seasonal treats, and specials
• Works well if you already use Square at your register or markets
• Low upfront cost (there is a free tier) Baker Setup BakingSubs

Tradeoff: The website design is more functional than premium-looking.

Best if your bakery is brand/image focused: squarespace.com

Choose this if you sell things where photos and branding matter—custom cakes, wedding desserts, artisan breads, etc.

Why it fits:

• Beautiful templates for showcasing products
• Strong menu/gallery pages
• Good for telling your bakery story and highlighting specials
• Makes a small bakery feel more like a polished brand WebsiteBuilderReport.com

Tradeoff: Ordering features may require a higher plan or additional setup compared with Square.

Good middle ground: wix.com

Choose this if you want lots of control over the design.

Strengths:

• Drag-and-drop editing
• Flexible layouts
• Restaurant/menu and ordering features available wix.com

Tradeoff: More customization means more time spent managing the site.

I’d probably avoid for your situation:

• shopify.com — excellent if you ship products nationally, but often more than a local pickup bakery needs. Baker Setup
• A custom-built website — usually unnecessary unless you have very specific needs.

My recommendation:

• Small local bakery, weekly menu, pickup orders: Square Online
• Boutique bakery, custom cakes, lots of photography/social media: Squarespace
• You want to design everything yourself: Wix

A common setup that works well is: Squarespace for the beautiful front-end + a dedicated ordering system, or simply Square Online for everything if you want the least maintenance. BakingSubs WebsiteBuilderReport.com

If you tell me whether you already use Square for payments, whether you do custom cakes, and roughly how many orders you expect per week, I can narrow it to one choice.

For an agency that builds sites for clients and wants true white-labeling + ecommerce, my first choice would be Duda.

My recommendation: Duda

duda.co

It is unusually well suited to the agency model because it isn't just a website builder—it is designed around managing lots of client websites under your brand.

Why I'd pick Duda

The big differentiator is white-labeling at the platform level. You can brand the login, editor, dashboard, domain, emails, client portal, etc., so the client experience can be presented as your agency's own platform. Duda explicitly supports custom branding, client permissions, client dashboards and branded communications. Duda Duda Support

It also has native ecommerce, including payments, inventory, multilingual stores, APIs and client permissions. Duda

And for an agency, the operational stuff matters enormously: reusable sections/templates, centralized management of client sites, permissions, hosting/SSL, and automation/API capabilities are all built into the platform. Duda Duda

One important caveat: Duda's white-label functionality is on its White Label/Custom plans, with White Label plans currently starting at $149/month. Duda

When I'd choose Wix Studio instead

wix.com

I'd seriously consider Wix Studio if your agency prioritizes design freedom and ecommerce functionality over completely hiding the underlying platform.

Wix Studio has excellent agency workflows, multi-site management, collaboration, client handoff, and a much deeper native ecommerce/business feature set. Its ecommerce supports customizable checkout/pricing, inventory, 80+ payment providers, POS, APIs and even headless implementations. wix.com wix.com

So I'd frame it this way:

• You want to sell "our website platform" to clients → Duda
• You want to build beautiful, sophisticated ecommerce sites efficiently → Wix Studio
• You want maximum designer/developer control and don't care as much about white-labeling → Webflow
• You want an agency platform that can eventually become a recurring SaaS/revenue product → Duda

One thing I'd investigate before committing

If your business model is something like "$X/month and we provide your website + hosting + ecommerce + maintenance", Duda becomes particularly interesting. Its white-label capabilities and APIs are intended for exactly this kind of model, including embedding the platform into your own technology. Duda Duda

If you tell me roughly how many sites you manage (e.g. 20 vs. 500), the average client price, and whether clients need to edit their own sites, I can narrow this down to the best platform and plan for your agency.

The big differentiator is white-labeling at the platform level. You can brand the login, editor, dashboard, domain, emails, client portal, etc., so the client experience can be presented as your agency's own platform. Duda explicitly supports custom branding, client permissions, client dashboards and branded communications. Duda Duda Support

It also has native ecommerce, including payments, inventory, multilingual stores, APIs and client permissions. Duda

And for an agency, the operational stuff matters enormously: reusable sections/templates, centralized management of client sites, permissions, hosting/SSL, and automation/API capabilities are all built into the platform. Duda Duda

One important caveat: Duda's white-label functionality is on its White Label/Custom plans, with White Label plans currently starting at $149/month. Duda

When I'd choose Wix Studio instead

wix.com

I'd seriously consider Wix Studio if your agency prioritizes design freedom and ecommerce functionality over completely hiding the underlying platform.

Wix Studio has excellent agency workflows, multi-site management, collaboration, client handoff, and a much deeper native ecommerce/business feature set. Its ecommerce supports customizable checkout/pricing, inventory, 80+ payment providers, POS, APIs and even headless implementations.

So I'd frame it this way:

• You want to sell "our website platform" to clients → Duda
• You want to build beautiful, sophisticated ecommerce sites efficiently → Wix Studio
• You want maximum designer/developer control and don't care as much about white-labeling → Webflow
• You want an agency platform that can eventually become a recurring SaaS/revenue product → Duda

One thing I'd investigate before committing

For what you described, I’d pick Squarespace.

It hits a particularly nice sweet spot between beautiful portfolio design and simple service payments:

My ranking

1. Squarespace — best overall for you

• Excellent-looking portfolio templates and galleries.
• You can sell services as products, without turning the site into a big online store. Squarespace Help Squarespace Help
• You can take an up-front deposit and then scheduled installments for a service. Squarespace Help
• You can also send professional invoices/payment links for one-off client projects. Squarespace Squarespace Help
• Particularly good if clients usually contact you first, and only occasionally need to pay a deposit.
• Wix — best if you want more booking/business functionality

• Wix Bookings lets you set a specific deposit amount when someone books a service. Wix Support Wix Support
• You can accept online payments, invoices, packages, memberships, etc. wix.com wix.com
• More flexible than Squarespace for a business where booking/scheduling is central.
• I'd choose it over Squarespace if you're going to have lots of appointments rather than occasional project deposits.
• Shopify — probably overkill

• Fantastic if ecommerce is the main business.
• For a portfolio where you occasionally sell a $500–$5,000 service or collect a project deposit, I'd rather have the cleaner portfolio experience of Squarespace.

What I'd build

For a creative/service portfolio, I'd make the site something like:

Home → striking intro + best work
Work → portfolio/case studies
Services → 3–5 clearly defined offerings
About → short personal story
Contact → inquiry form
Book / Pay Deposit → simple service checkout

For example, your Services page could have:

Brand Identity — $2,500
Strategy, visual identity, logo system, and brand guidelines.
$750 deposit to begin

The client can then pay the deposit without you having to maintain a traditional ecommerce catalog. Squarespace specifically supports service products and payment plans like this. Squarespace Help Squarespace Help

So if your priority is “beautiful portfolio first, occasional client payments second,” I'd go Squarespace. If it's “service business with lots of appointments and deposits,” I'd go Wix.

squarespace.com
wix.com

If analytics + conversion optimization are core requirements, I’d pick Shopify for most businesses.

shopify.com

My ranking

1. Shopify — best overall

• Strong built-in ecommerce analytics: sales, sessions, conversion rate, AOV, products, customers, and marketing attribution. Shopify Help Center Shopify Help Center
• Real-time analytics and customizable reporting, with deeper data exploration and API access. Shopify
• Conversion is tightly integrated into the commerce platform: Shop Pay, checkout optimization, abandoned-cart recovery, marketing tools, etc. Shopify
• Huge app ecosystem if you eventually want A/B testing, heatmaps, personalization, advanced attribution, or customer-data tools.
• Best choice if you're primarily DTC/ecommerce and want marketing and conversion teams to move quickly.
• BigCommerce — best if you want more analytics/data flexibility out of the box

• Built-in reporting includes storefront conversion rates, AOV, cart abandonment, customer behavior, product performance and more. BigCommerce BigCommerce
• Particularly attractive for larger catalogs, B2B, or businesses that want a more open/flexible data architecture. BigCommerce
• Its one-page checkout and ecommerce functionality are strong. BigCommerce
• I'd choose this over Shopify if sophisticated catalog/B2B requirements outweigh checkout simplicity.
• Wix — good website builder, but not my first choice for your requirement

• It's excellent when the website itself is the priority.
• But for a business where analytics and conversion optimization are deeply intertwined with ecommerce, I'd rather start with a commerce-first platform. BigCommerce itself describes Wix as website-builder-first rather than ecommerce-first. BigCommerce

The important distinction

If by "solid analytics" you mean "I want to know what's happening and optimize revenue", Shopify is very good.

If you mean "I want Hotjar/GA-style behavioral analytics + funnels + session recordings + A/B testing + personalization all built directly into the builder", none of the mainstream builders completely nails all of that natively. You'd typically add specialized CRO/analytics tools on top. Shopify's own documentation explicitly positions its built-in analytics as the foundation that can be complemented by CRO tools. Shopify

So my default recommendation: Shopify. It's the best balance of storefront building, checkout conversion, ecommerce analytics, marketing, and extensibility.

If you tell me what you're selling, roughly how much traffic/orders you expect, and whether you're B2C or B2B, I can narrow it down to Shopify vs BigCommerce vs Wix vs WooCommerce for your specific situation.

For a musician selling merch at shows + directly through your website, I’d lean toward Shopify as the best all-around solution.

My ranking

🥇 Shopify — my pick

Shopify is particularly good for a musician because you can have one product catalog and one inventory count for everything.

For example, you have:

• 50 black T-shirts
• 25 vinyl records
• 100 posters

You take 8 shirts and 3 vinyl records to tonight's show. When you sell them through Shopify POS, the inventory is updated in the same Shopify backend that powers your website. Shopify specifically supports selling at pop-ups/events and syncing orders and inventory with the online store. Shopify Shopify Help Center

You can also use a phone/tablet-based POS at shows, with optional card readers and other hardware. Shopify

shopify.com

Why I'd choose it for an artist:

• Excellent merch/product management
• Excellent inventory tracking
• Professional-looking artist website
• POS works at gigs, festivals and pop-ups
• Online + physical sales are genuinely unified
• Easy to add email marketing, discounts, gift cards, shipping, etc.
• Scales well if your merch operation gets serious

The downside is that Shopify is more ecommerce platform than you probably need at first, and there are monthly costs plus payment-processing costs.

🥈 Square — best simple alternative

If you're thinking:

"I mostly need to sell merch at shows, but I also want a decent online store."

I'd seriously consider Square.

Square's POS and online store are built around the same catalog, and its system syncs in-person sales, online orders and inventory. Square Square

squareup.com

The big advantage is simplicity. Square is excellent for taking payments at a merch table. You can start with relatively minimal hardware and expand later.

I'd pick Square over Shopify if your business is primarily:

Band → shows → merch table → occasional online orders

I'd pick Shopify if it's:

Band → website → merch → shows → social media → growing online business

🥉 Big Cartel

Big Cartel is attractive because it was built with artists and small independent sellers in mind.

It's worth considering if you have a relatively small catalog and want a simple artist-branded store rather than building a full ecommerce operation.

The catch is that Shopify and Square have the stronger native POS/inventory ecosystems, which matters when you're standing behind a merch table trying to move 30 people through checkout after a show.

What I'd actually do as a musician

If I were setting this up for an independent artist today, I'd probably go:

Shopify + Shopify POS + a phone/iPad + card reader

Your workflow becomes:

Shopify admin
→ create "Black Tour Tee – Large"
→ inventory = 30

Online
→ fan buys one
→ inventory = 29

Show
→ you sell one through POS
→ inventory = 28

Next show
→ you bring 20
→ sell 7
→ Shopify knows you have 21 total remaining

That unified inventory is the important part. Shopify explicitly supports real-time inventory across online stores, POS and multiple locations. Shopify

One important question

If you tell me roughly how big your operation is (e.g. 1–2 shows/month and 5 merch SKUs vs. 100+ shows/year and 30 SKUs), I can tell you whether Shopify or Square makes more financial sense, including the POS hardware and monthly/payment fees.

If your priority is “I’m a photographer, I want to sell prints, and I don’t want fulfillment/shipping to become a second job,” I’d narrow it to Pixieset, SmugMug, and Shopify + a print-on-demand service.

My ranking

🥇 Pixieset — probably your best fit

For a working photographer, this is the cleanest option I'd investigate first.

Pixieset's Store is built around photography galleries, so customers can buy prints directly while viewing your images. Its automatic fulfillment sends orders to professional labs, which print, package and ship directly to the customer, with white-label packaging. Pixieset Website Help Center Pixieset

It also handles shipping particularly cleanly: with automatic fulfillment, you don't have to configure shipping yourself. The selected lab supplies the shipping methods and calculates the shipping cost based on the order and destination. Pixieset Website Help Center

You can use labs including WHCC, ProDPI, Miller's, Mpix, Loxley Colour and Atkins Pro, with international availability depending on the lab. Pixieset Website Help Center

The catch: branded merchandise is where Pixieset becomes less compelling. It's superb for photographic prints, wall art, albums, cards, etc., but if your vision includes a substantial line of T-shirts, hoodies, hats, mugs and other branded merchandise, Shopify + a POD provider gives you considerably more flexibility.

pixieset.com

🥈 SmugMug — excellent if prints are the business

SmugMug is similarly photographer-centric. It handles payments, orders, fulfillment and delivery, and lets you set your own pricing/margins. Its catalog includes photographic prints as well as things like mugs and magnets. SmugMug

I'd pick SmugMug over Pixieset if your business is primarily selling your photography as physical products, rather than building a broader lifestyle/merch brand.

smugmug.com

🥉 Shopify + Printful/Printify — best for building a brand

If by “branded gear” you mean something like:

Photography prints + T-shirts + hoodies + hats + tote bags + stickers + mugs + limited-edition drops

then I'd seriously consider Shopify.

You get a much more conventional ecommerce storefront and can connect print-on-demand fulfillment so that orders are produced and shipped without you stocking inventory. The tradeoff is that you're assembling the system yourself rather than getting the photographer-specific experience of Pixieset.

My rule of thumb:

• 80%+ fine-art/photo prints → Pixieset
• Mostly photography prints, some merchandise → SmugMug or Pixieset
• Photography is the brand, and merchandise is becoming a major product line → Shopify + POD
• You want maximum control over branding, products, bundles and customer experience → Shopify

One particularly attractive setup is actually Pixieset + Shopify: Pixieset for client galleries and photographer-oriented print sales, Shopify for your public-facing merch brand. That avoids forcing one platform to do two very different jobs.

If you tell me roughly what you want to sell (e.g. fine-art prints + 5–10 apparel designs) and whether you already have a website, I can compare the actual fulfillment/lab options, shipping, fees, and branding limitations of Pixieset vs. SmugMug vs. Shopify for your situation.

Pixieset's Store is built around photography galleries, so customers can buy prints directly while viewing your images. Its automatic fulfillment sends orders to professional labs, which print, package and ship directly to the customer, with white-label packaging. Pixieset Website Help Center Pixieset

It also handles shipping particularly cleanly: with automatic fulfillment, you don't have to configure shipping yourself. The selected lab supplies the shipping methods and calculates the shipping cost based on the order and destination. Pixieset Website Help Center

You can use labs including WHCC, ProDPI, Miller's, Mpix, Loxley Colour and Atkins Pro, with international availability depending on the lab. Pixieset Website Help Center

The catch: branded merchandise is where Pixieset becomes less compelling. It's superb for photographic prints, wall art, albums, cards, etc., but if your vision includes a substantial line of T-shirts, hoodies, hats, mugs and other branded merchandise, Shopify + a POD provider gives you considerably more flexibility.

pixieset.com

🥈 SmugMug — excellent if prints are the business

SmugMug is similarly photographer-centric. It handles payments, orders, fulfillment and delivery, and lets you set your own pricing/margins. Its catalog includes photographic prints as well as things like mugs and magnets. SmugMug

I'd pick SmugMug over Pixieset if your business is primarily selling your photography as physical products, rather than building a broader lifestyle/merch brand.

smugmug.com

🥉 Shopify + Printful/Printify — best for building a brand

If by “branded gear” you mean something like:

Photography prints + T-shirts + hoodies + hats + tote bags + stickers + mugs + limited-edition drops

then I'd seriously consider Shopify.

You get a much more conventional ecommerce storefront and can connect print-on-demand fulfillment so that orders are produced and shipped without you stocking inventory. The tradeoff is that you're assembling the system yourself rather than getting the photographer-specific experience of Pixieset.

My rule of thumb:

• 80%+ fine-art/photo prints → Pixieset
• Mostly photography prints, some merchandise → SmugMug or Pixieset
• Photography is the brand, and merchandise is becoming a major product line → Shopify + POD
• You want maximum control over branding, products, bundles and customer experience → Shopify

One particularly attractive setup is actually Pixieset + Shopify: Pixieset for client galleries and photographer-oriented print sales, Shopify for your public-facing merch brand. That avoids forcing one platform to do two very different jobs.

If you tell me roughly what you want to sell (e.g. fine-art prints + 5–10 apparel designs) and whether you already have a website, I can compare the actual fulfillment/lab options, shipping, fees, and branding limitations of Pixieset vs. SmugMug vs. Shopify for your situation.

For a streamer doing lots of limited-edition drops, I’d usually choose a platform based on how intense the drops are (hundreds of fans rushing at once vs. smaller VIP releases).

Best overall: Shopify + drop-focused apps

Best if scarcity is the core of your business.

Why:

• Strong inventory controls for limited quantities
• Handles variants well (sizes, colors, editions, bundles)
• Very fast checkout with Shop Pay, Apple Pay, Google Pay, etc.
• Huge ecosystem for: - waitlists
• countdowns
• password-protected drops
• early access for subscribers
• bots/fraud protection
• preorder workflows

A Shopify setup is usually the choice when you’re treating merch like a real streetwear-style drop operation. Shopify’s app ecosystem also includes tools specifically for limited editions and shared inventory pools across variants. Shopify App Store

Pick Shopify if:

• You sell thousands of units during launches
• You have many SKUs/variants
• You want maximum control over branding and customer data

Best creator-native option: Fourthwall

Best if you want “streamer merch store” simplicity.

Why:

• Built specifically for creators
• Supports limited-run drops and custom products
• Integrates with creator channels like Twitch, YouTube, TikTok, and streaming tools
• Handles payments and fulfillment options
• Easier to operate than a full ecommerce stack Fourthwall Fourthwall

Fourthwall supports checkout methods like cards, PayPal, Apple Pay, Google Pay, and Amazon Pay, which helps reduce checkout friction during drops. Fourthwall

Pick Fourthwall if:

• You want to launch fast
• You don’t want to manage apps, inventory systems, and fulfillment complexity
• Your audience already follows you from Twitch/YouTube

Other options worth considering

Gumroad

Good for:

• digital collectibles
• memberships
• simple creator products

Less ideal for:

• complex apparel variants
• high-volume physical drops

WooCommerce

Good for:

• maximum customization

Less ideal for:

• “drop day” reliability unless you have technical help

My recommendation by streamer size

• Small/medium streamer (10k–200k followers): Fourthwall
• Large streamer with hype drops: Shopify
• Merch brand ambitions (limited sneakers, numbered editions, collabs): Shopify + custom drop tooling
• Mostly digital goods: Gumroad or Shopify

For a streamer whose main feature is scarcity + variants + “everyone clicks buy at the same second”, I’d lean Shopify. For a streamer who wants a low-maintenance merch operation, I’d lean Fourthwall. Fourthwall Fourthwall

If international merch + localized pricing + duties handled cleanly are the priorities, I’d put these at the top of the shortlist:

1. Shopify + Managed Markets — probably your best fit

This is the one I'd evaluate first. Shopify Markets lets you create country/region-specific markets, currencies, price adjustments and fixed local prices. Shopify Help Center Shopify Help Center

The particularly relevant piece is Managed Markets: it acts as a merchant of record and handles international tax registration/remittance, duties/import taxes, local payment methods and regulatory complexity. Shopify App Store Shopify Help Center

In 2026, Shopify also added Adaptive Pricing, which can automatically adjust international prices to account for currency conversion, duties, taxes and Managed Markets fees—very close to the "show customers the right all-in price" experience you're describing. Shopify Changelog

The tradeoff is cost: Managed Markets has transaction/FX fees, so you'll want to model those against your international gross margin. Shopify currently lists a 3.5% Managed Markets fee for Basic/Grow/Advanced and 3.25% for Plus, in addition to applicable FX/payment costs. Shopify Help Center

I'd choose this if: you're primarily selling DTC merch and want your team spending time on products/marketing rather than international tax and customs administration.

2. Global-e — worth considering if international is a major business

Global-e is specifically built around cross-border commerce and is particularly interesting if you're expecting a substantial percentage of revenue from outside the US.

The big conceptual advantage is similar to Managed Markets: you can outsource much of the complexity around local currencies, pricing, taxes, duties, payment methods and cross-border compliance rather than assembling a stack yourself.

I'd put it ahead of Shopify if you're becoming a serious global brand with many markets, rather than simply wanting to make a US merch store available internationally.

3. BigCommerce — strong if you need more backend flexibility

BigCommerce is worth a serious look if you have a complicated catalog, multiple storefronts, B2B requirements, or an engineering team that wants more control.

Its weakness for your particular requirement is that the "international selling" experience isn't quite as neatly packaged as Shopify + Managed Markets. You may end up assembling additional tax, duties, payments and localization services.

What I'd actually do

For a typical merch business, I'd narrow it to:

Shopify + Managed Markets → Global-e → BigCommerce

And I'd make the decision based on who is responsible for the international transaction.

The key question isn't just "can the platform display € prices?" Almost all of these can. You want to know:

• Can we set different actual prices by country rather than simply FX-converting USD?
• Can the customer see duties/taxes before paying?
• Can we make the order DDP (duties paid) so there aren't surprise charges at delivery?
• Who is the merchant of record?
• Who handles VAT/GST registration and remittance?
• Can we guarantee the customer's price while protecting our margin from FX/duty changes?
• How much does each international order actually cost us after platform + payment + FX + duties + fulfillment fees?

For a merch-focused company, Shopify Managed Markets is the one I'd prototype first. It gets unusually close to "turn on a country and start selling there" rather than requiring you to build an international-commerce stack yourself. shopify.com Shopify App Store

If you tell me roughly annual GMV, where you're based, your top 5 target countries, and whether you're doing print-on-demand or holding inventory, I can narrow this down to the best 2–3 options and compare the economics.

In 2026, Shopify also added Adaptive Pricing, which can automatically adjust international prices to account for currency conversion, duties, taxes and Managed Markets fees—very close to the "show customers the right all-in price" experience you're describing. Shopify Changelog

The tradeoff is cost: Managed Markets has transaction/FX fees, so you'll want to model those against your international gross margin. Shopify currently lists a 3.5% Managed Markets fee for Basic/Grow/Advanced and 3.25% for Plus, in addition to applicable FX/payment costs. Shopify Help Center

I'd choose this if: you're primarily selling DTC merch and want your team spending time on products/marketing rather than international tax and customs administration.

2. Global-e — worth considering if international is a major business

Global-e is specifically built around cross-border commerce and is particularly interesting if you're expecting a substantial percentage of revenue from outside the US.

The big conceptual advantage is similar to Managed Markets: you can outsource much of the complexity around local currencies, pricing, taxes, duties, payment methods and cross-border compliance rather than assembling a stack yourself.

I'd put it ahead of Shopify if you're becoming a serious global brand with many markets, rather than simply wanting to make a US merch store available internationally.

3. BigCommerce — strong if you need more backend flexibility

BigCommerce is worth a serious look if you have a complicated catalog, multiple storefronts, B2B requirements, or an engineering team that wants more control.

Its weakness for your particular requirement is that the "international selling" experience isn't quite as neatly packaged as Shopify + Managed Markets. You may end up assembling additional tax, duties, payments and localization services.

What I'd actually do

If you’re describing a B2B division with customer-specific pricing, POS, and very large order volumes, I’d shortlist Shopify Plus, Adobe Commerce, and BigCommerce Enterprise—but I’d put Shopify Plus and Adobe Commerce at the top of the evaluation.

My initial ranking

1. Shopify Plus — probably my first choice

Shopify is particularly compelling if POS is an important part of the B2B operation.

Shopify's current B2B functionality supports company/location accounts, customer-specific catalogs, custom pricing, volume pricing, quantity rules, payment terms and self-service ordering. Plus also allows catalogs to be assigned directly to individual companies/company locations, which is important when pricing is negotiated customer-by-customer. Shopify Help Center Shopify Help Center

The bigger advantage in your case is the unified commerce model: Shopify positions B2B, DTC and POS as operating through the same commerce infrastructure. Shopify

I'd favor Shopify Plus if you want:

• B2B ecommerce + physical POS
• Customer-specific price lists
• Volume/tier pricing
• Multiple locations under a corporate account
• Net terms / invoicing
• Large order quantities
• A relatively fast implementation
• A modern API/integration layer for ERP, PIM, WMS, etc.
• The ability to eventually support both B2B and DTC without maintaining separate commerce platforms

Potential concern: if your pricing engine is extremely complicated—for example, thousands of contractual price rules involving customer × SKU × quantity × region × date × sales rep × rebate × freight—you'll want to prototype that logic carefully before committing. Shopify has APIs and extensibility, but you don't want to recreate an ERP pricing engine in Shopify.

2. Adobe Commerce — strongest if B2B complexity is the priority

Adobe Commerce is the one I'd investigate if the B2B side is much more complex than a typical wholesale business.

Adobe's B2B functionality includes company hierarchies, shared catalogs, negotiated quotes, purchase orders, approval rules, requisition lists, credit/account payment and customer-specific pricing. Adobe Developer Adobe Developer

That's a very good fit when you have things like:

Corporate account → subsidiaries → locations → buyers → approval limits → negotiated contracts → custom catalogs → complex pricing → PO → ERP

The downside is that you're taking on a considerably more substantial technology implementation. Adobe itself is much more of a build/customize enterprise commerce platform than a turnkey commerce operating system.

So I'd choose Adobe when business complexity outweighs implementation simplicity.

3. BigCommerce Enterprise — definitely worth putting in the RFP

BigCommerce is probably the third platform I'd put into the bake-off.

It's particularly interesting if you want strong native B2B capabilities while maintaining a more open/headless architecture. Current comparisons characterize its Enterprise offering as supporting large catalogs, high traffic, multi-store setups and advanced B2B functionality. Shopify

I'd put it ahead of Shopify if you have a strong reason to avoid Shopify's ecosystem or need a particular architecture/integration model.

The key question isn't really "which ecommerce platform?"

For your use case, I'd actually start with the pricing/order architecture.

I'd map these requirements before choosing:

1. How many B2B customers?
2. How many SKUs?
3. How many orders/month?
4. Largest order by line count and units?
5. Is pricing customer-specific, customer-group-specific, or contract-specific?
6. Can one customer have multiple price lists/catalogs?
7. Do customers have multiple locations and buyers?
8. Do buyers need POs, approval workflows and credit limits?
9. Do sales reps place orders on behalf of customers?
10. Does POS need to use the exact same customer pricing/inventory as ecommerce?
11. What ERP is behind the business—SAP, NetSuite, Dynamics, Oracle, custom, etc.?
12. Where is the source of truth for price, inventory and customer data?
13. Are orders mostly standard SKU orders, or do you have configured/custom products?
14. Do you need quotes/RFQs?
15. How much pricing logic currently lives inside your ERP?

One architecture I'd seriously consider

If POS is genuinely important, I'd lean toward:

Shopify Plus
→ B2B storefront + customer accounts + POS
→ ERP as financial/customer/inventory authority
→ PIM for product data if needed
→ WMS/3PL for fulfillment
→ middleware/API layer for synchronization

That gives you a relatively clean separation between commerce experience and enterprise back office.

If, however, the ERP currently owns an extremely sophisticated contractual pricing engine and your ecommerce platform needs to reproduce that pricing in real time, I'd investigate Adobe Commerce vs. Shopify Plus much more deeply before deciding.

Shopify itself now emphasizes ERP/API integrations and custom B2B solutions, so it doesn't necessarily require you to move the ERP pricing engine into Shopify. Shopify

My short answer:
Shopify Plus if you want the best combination of B2B + POS + scale + speed.
Adobe Commerce if complex B2B pricing/workflows are the dominant requirement.
BigCommerce Enterprise as the third platform I'd benchmark.

If you tell me your ERP, approximate annual B2B revenue, number of customers/SKUs, order volume, and what POS you currently use, I can narrow this down substantially and give you a Shopify Plus vs Adobe Commerce vs BigCommerce architecture recommendation.

I'd put it ahead of Shopify if you have a strong reason to avoid Shopify's ecosystem or need a particular architecture/integration model.

The key question isn't really "which ecommerce platform?"

For your use case, I'd actually start with the pricing/order architecture.

I'd map these requirements before choosing:

1. How many B2B customers?
2. How many SKUs?
3. How many orders/month?
4. Largest order by line count and units?
5. Is pricing customer-specific, customer-group-specific, or contract-specific?
6. Can one customer have multiple price lists/catalogs?
7. Do customers have multiple locations and buyers?
8. Do buyers need POs, approval workflows and credit limits?
9. Do sales reps place orders on behalf of customers?
10. Does POS need to use the exact same customer pricing/inventory as ecommerce?
11. What ERP is behind the business—SAP, NetSuite, Dynamics, Oracle, custom, etc.?
12. Where is the source of truth for price, inventory and customer data?
13. Are orders mostly standard SKU orders, or do you have configured/custom products?
14. Do you need quotes/RFQs?
15. How much pricing logic currently lives inside your ERP?

One architecture I'd seriously consider

If POS is genuinely important, I'd lean toward:

Shopify Plus
→ B2B storefront + customer accounts + POS
→ ERP as financial/customer/inventory authority
→ PIM for product data if needed
→ WMS/3PL for fulfillment
→ middleware/API layer for synchronization

That gives you a relatively clean separation between commerce experience and enterprise back office.

If, however, the ERP currently owns an extremely sophisticated contractual pricing engine and your ecommerce platform needs to reproduce that pricing in real time, I'd investigate Adobe Commerce vs. Shopify Plus much more deeply before deciding.

Shopify itself now emphasizes ERP/API integrations and custom B2B solutions, so it doesn't necessarily require you to move the ERP pricing engine into Shopify.

For a digital-first enterprise that explicitly wants to decouple frontend and backend, my default recommendation would be commercetools—with Shopify Plus as the stronger choice if you prioritize operational simplicity and speed over maximum architectural freedom.

My shortlist

Current enterprise comparisons similarly position commercetools around engineering-heavy composable deployments, Elastic Path around complex B2B/B2B2C, and Shopify Plus around faster, lower-operational-load deployments. Elastic Path CIOPages

Why I'd pick commercetools for your stated architecture

If your phrase "decouple frontend and backend" is the architectural priority—not just a desire for a custom React storefront—commercetools is particularly compelling.

You can treat commerce as a set of services/APIs and independently evolve:

• Web frontend
• Mobile apps
• In-store experiences
• CMS/content
• Search
• Personalization
• Checkout
• PIM
• ERP
• Customer data
• Market-specific experiences

That makes it a strong fit when you're building a composable commerce platform rather than simply putting a headless storefront on top of a conventional commerce platform.

The tradeoff is important: you're taking on considerably more integration and platform engineering responsibility. That's appropriate if you have a strong internal engineering/platform organization; it can become expensive if you don't.

When I'd choose Shopify Plus instead

I'd choose Shopify Plus if your real requirement is:

"We want our frontend completely independent, but we don't want to own the complexity of the commerce backend."

That's a materially different requirement.

Shopify now supports custom storefronts through its Storefront API, with Hydrogen/Oxygen as its native headless stack, while also allowing teams to use their own frontend framework and hosting. Shopify Shopify

It gives you a particularly attractive division of responsibility:

Your team owns
→ React/Next.js/Hydrogen UX
→ design system
→ frontend deployment
→ CMS/content experience
→ experimentation

Shopify owns
→ products
→ cart
→ checkout
→ orders
→ pricing
→ commerce infrastructure
→ platform reliability

Shopify explicitly supports both Hydrogen and bring-your-own frontend stacks, so you're not forced into Hydrogen to get the headless architecture. Shopify Shopify

For a large B2C/D2C organization, that's an extremely compelling tradeoff.

The key decision

I'd frame it this way:

Choose commercetools if:

• Commerce is becoming a core technology platform.
• You have substantial engineering/platform capabilities.
• Multiple brands, markets, channels, or business models need to share commerce capabilities.
• You expect to swap individual components over time.
• Avoiding vendor architectural constraints is strategically important.
• B2B/B2C/B2B2C complexity is significant.

Choose Shopify Plus if:

• You're primarily B2C/D2C.
• You want a genuinely decoupled frontend.
• You want enterprise-scale commerce without operating a large commerce platform team.
• Speed to market and reliability matter more than maximal composability.
• You want to keep the commerce backend relatively standardized while differentiating heavily on customer experience.

Shopify's current enterprise offering supports headless storefronts and says its Storefront API is capable of very high request volumes, while Shopify manages the underlying commerce infrastructure. Shopify Shopify

My recommendation

If I were designing the architecture from scratch for an enterprise with a strong digital engineering organization, I'd shortlist:

1. commercetools — best pure composable/headless choice
2. Shopify Plus — best headless + managed-platform choice
3. Elastic Path — worth serious consideration for complex B2B/B2B2C
4. SAP Commerce Cloud — primarily if SAP is already central to the enterprise
5. Adobe Commerce — primarily if Adobe/Magento is already strategic

The biggest mistake would be choosing based on "headless" marketing alone. The important question is how much of the commerce stack you actually want to own. Headless removes the frontend dependency; it doesn't magically remove backend complexity.

If you tell me your B2B vs B2C mix, annual GMV/order volume, number of countries/brands, ERP (SAP/Oracle/etc.), and whether you have a 20+ person engineering/platform team, I can narrow this to a concrete architecture and vendor recommendation.

For a large B2C/D2C organization, that's an extremely compelling tradeoff.

The key decision

I'd frame it this way:

Choose commercetools if:

For an enterprise commerce stack with complex ERP + PIM integrations, the “best” platform is usually determined less by storefront features and more by how well it handles master data ownership, catalog complexity, pricing rules, order orchestration, and integration architecture. CIOPages Elogic Commerce

The strongest candidates are typically:

My typical shortlist by ERP environment

If you run SAP ERP / S4HANA

1. SAP Commerce Cloud
2. Adobe Commerce
3. commercetools

SAP Commerce is usually the natural fit because the commerce layer sits close to SAP master data and business processes. Shopify

If you run Microsoft Dynamics 365

1. Adobe Commerce
2. commercetools
3. Salesforce Commerce Cloud

Adobe has a broad enterprise connector ecosystem and tends to be flexible for mixed ERP environments. Adobe for Business

If you have a “best-of-breed” stack

Example:

• ERP: SAP / Oracle / Infor / Dynamics
• PIM: Akeneo / Salsify / inRiver / Pimcore
• OMS: Manhattan / Fluent / IBM Sterling
• CMS: Contentful / Adobe Experience Manager

Then I would lean toward:

• commercetools (if you have strong engineering)
• Adobe Commerce (if you want more packaged commerce capabilities)
• SAP Commerce (if SAP dominates your landscape)

The architecture pattern that usually works best

For complex enterprises, avoid making the ecommerce platform the “system of record.” A common pattern is:

• ERP → inventory, cost, financials, fulfillment rules
• PIM → product content, attributes, digital assets
• Commerce platform → storefront, cart, promotions, customer experience
• OMS → order routing and fulfillment orchestration
• Middleware/iPaaS → synchronization and transformation

The key evaluation questions are:

1. Where does product truth live? ERP or PIM?
2. Who owns pricing? ERP, CPQ, commerce, or contract systems?
3. How many catalogs? One consumer catalog vs thousands of customer-specific catalogs?
4. Do you need B2B workflows? Quotes, approvals, buying groups, contract pricing, punchout?
5. How much customization can your team operate long term?

If you share:

• ERP (SAP, Oracle, Dynamics, Infor, NetSuite, custom)
• PIM (Akeneo, Salsify, inRiver, Pimcore, etc.)
• B2B vs B2C
• approximate SKU count and number of storefronts/regions

…I can narrow this to a 2–3 platform recommendation.

If global shopper latency and edge/CDN performance are the primary criteria, I’d put Shopify Plus at the top of the enterprise shortlist today.

My ranking for this specific requirement

Why Shopify stands out

Shopify's current enterprise architecture is unusually compelling if you don't want your team operating the CDN/edge layer themselves. Shopify says its infrastructure now spans 330+ points of presence across 125+ countries, with sub-50ms response times cited from Cloudflare. It also supports storefronts and checkout at the edge. Shopify Shopify

Its standard storefront infrastructure automatically includes a Cloudflare-powered CDN, image optimization, caching and related performance optimizations. Shopify Help Center

The important distinction is that you're not merely getting a CDN for images and JavaScript. Shopify is increasingly pushing commerce workloads themselves toward the edge, including storefront delivery and checkout. Shopify reports handling up to 40,000 checkout starts/minute and 99.9% uptime during major events. Shopify

For a global retailer, that's a big architectural advantage: your engineering team doesn't have to assemble something like:

commerce backend → origin → CDN → edge functions → cache invalidation → regional failover → checkout optimization

You get much of that as a managed platform.

Where I'd consider BigCommerce instead

bigcommerce.com is probably my second choice if architectural flexibility matters almost as much as raw latency.

BigCommerce is SaaS and manages hosting/performance for you, with a claimed 99.99% uptime and 100% uptime during Cyber Week since 2016. BigCommerce

The tradeoff is that Shopify currently has a more compelling story around globally distributed edge infrastructure as an integrated part of the commerce platform, rather than simply having good global hosting/CDN capabilities.

The important caveat: CDN ≠ low-latency commerce

For your use case, I'd evaluate vendors on four separate latency layers:

1. Static delivery — images, JS, CSS, fonts.
2. HTML/SSR delivery — TTFB for category/product pages.
3. Dynamic API calls — pricing, inventory, personalization, recommendations.
4. Checkout — cart, payment, tax, promotions and order creation.

A platform can have an outstanding CDN and still have poor checkout latency if dynamic requests have to travel halfway around the world to a centralized origin.

That's why I'd favor Shopify for a global consumer storefront: its current architecture explicitly positions storefront delivery and checkout at the edge, rather than just putting static assets behind a CDN. Shopify

Bottom line

If I were choosing purely for "fastest global shopping experience with the least infrastructure to operate": Shopify Plus.

If I wanted maximum control and had a strong platform engineering team: composable commerce + Cloudflare/Akamai/Fastly + strategically distributed application infrastructure.

If I needed openness/customization but still wanted managed SaaS: BigCommerce Enterprise.

For a serious enterprise evaluation, though, I wouldn't accept vendor-wide "X% faster" claims. I'd run the same RUM + synthetic test from 10–20 global markets, measuring p50/p75/p95 TTFB, LCP, INP, product-page API latency, cart latency, and checkout latency. That's where the real platform differences become apparent.

Where I'd consider BigCommerce instead

bigcommerce.com is probably my second choice if architectural flexibility matters almost as much as raw latency.

BigCommerce is SaaS and manages hosting/performance for you, with a claimed 99.99% uptime and 100% uptime during Cyber Week since 2016. bigcommerce.com

The tradeoff is that Shopify currently has a more compelling story around globally distributed edge infrastructure as an integrated part of the commerce platform, rather than simply having good global hosting/CDN capabilities.