Answers that name a competitor

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

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

shopify.com

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

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

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

My ranking

1. Shopify — best overall

• Fastest to launch and relatively easy for a small team to operate.
• Strong fit for a retailer because online and physical-store selling can be managed together through Shopify POS. Shopify Help Center Shopify Help Center
• You can start relatively simply and move up through plans as sales and operational complexity increase. Shopify Help Center
• Crucially, you aren't painting yourself into a corner: Shopify supports APIs, headless commerce, B2B and larger-scale setups later. Shopify
• BigCommerce — best if you expect complexity

• I'd consider it if you have a large/complicated catalog, multiple storefronts, B2B, or unusual pricing/inventory requirements.
• Its higher plans explicitly support multi-storefront and more sophisticated commerce operations. BigCommerce BigCommerce
• The tradeoff is that it's somewhat more platform than a small retailer needs initially.
• WooCommerce — best if you already live in WordPress

• Extremely flexible and open-source, with control over your code, data and hosting. WooCommerce WooCommerce
• It can scale substantially, but that flexibility generally means more technical responsibility—hosting, updates, plugins, security and performance.
• I wouldn't choose it specifically because you have limited dev resources unless WordPress expertise is already in-house.

What I'd do in your position

Start with Shopify, but architect the business—not the website—for scale.

That means:

• Shopify for the storefront, checkout, products and orders.
• Shopify POS if you want online/offline inventory and customer data connected.
• A good inventory/ERP system only when you actually need one, rather than building one yourself.
• Standard integrations for email/SMS, shipping, accounting and analytics.
• Keep your customer/product/order data clean and exportable.
• Avoid excessive custom code and obscure apps that become impossible to replace.
• Use Shopify's APIs when you eventually need custom functionality rather than rebuilding the entire commerce platform.

The key distinction is "scalable" vs. "customizable." WooCommerce can be more customizable, but for a resource-constrained retailer, Shopify's managed infrastructure can be considerably easier to scale operationally.

My rule of thumb: if you're going from one local store → meaningful online sales → multiple locations/channels, I'd pick Shopify. If you're already planning complex B2B pricing, multiple brands/stores, huge catalogs or unusual commerce logic, I'd investigate BigCommerce before committing.

If you tell me roughly annual revenue, number of SKUs, current POS (Square/Clover/etc.), and whether you have one or multiple physical locations, I can narrow this down to a specific stack and likely monthly cost.

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

My shortlist

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

What I'd pick for a startup

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

The particularly attractive combination is:

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

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

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

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

For an enterprise catalog with thousands of SKUs and complex pricing, I would avoid choosing based on “number of SKUs supported” alone. The harder problems are usually:

• Customer-specific price books and contract pricing
• Tiered/volume pricing
• Multiple catalogs by customer, region, channel, or business unit
• ERP/PIM synchronization
• Configurable products and variants
• Quote workflows and approval flows
• Fast search across a large product universe

Platforms that are often shortlisted for this type of environment include: Elastic Path Shopify

My shortlist by scenario

1. Industrial distributor / manufacturer

• Adobe Commerce
• SAP Commerce Cloud (if SAP is your ERP backbone)
• OroCommerce

2. Thousands of SKUs + customer-specific pricing + ERP-driven business

• SAP Commerce Cloud
• Adobe Commerce
• Elastic Path

3. B2B + direct-to-consumer on the same platform

• Shopify Plus
• BigCommerce Enterprise
• Adobe Commerce

4. You have a strong internal engineering team and want maximum flexibility

• commercetools
• Elastic Path

Questions I would use to narrow it down

1. How many price rules exist?

• 5–20 price lists is very different from 50,000 customer-specific contracts.
• Where is pricing mastered today?

• ERP (SAP, Oracle, Dynamics, NetSuite)?
• CRM?
• Ecommerce platform?
• Do customers see negotiated prices after login?

• If yes, account hierarchy and pricing engines become critical.
• How complex is your catalog?

• 50,000 simple SKUs is often easier than 5,000 configurable products with dependencies.
• Do you need marketplace, punchout procurement, EDI, or CPQ integration?

If you share:

• approximate SKU count (5k / 50k / 500k+)
• B2B only vs B2B+B2C
• ERP (SAP, NetSuite, Dynamics, Oracle, other)
• pricing model (customer contracts, tiers, quotes, regional pricing)

…I can narrow this to a 2–3 platform recommendation.

For a developer building a custom frontend, the “best” headless commerce platform depends mostly on how much of the commerce engine you want to own. The strongest options today fall into a few categories. vendure.ionaturaily.com

ribbsaetersystems.com

My shortlist for a developer-first custom frontend

1. Medusa — probably the best balance of freedom + developer experience

Choose Medusa if you want:

• A Next.js/React frontend
• Full control over checkout, pricing, promotions, fulfillment
• A Node/TypeScript stack end-to-end
• The ability to modify the backend instead of fighting platform constraints

Architecture is closer to “commerce primitives you assemble” than a traditional SaaS store. It’s a strong choice when your product is not a standard Shopify-style catalog. hunchbite.comossalt.com

Typical stack:

Next.js frontend
        |
        |
Medusa API
        |
Postgres + payment/shipping integrations

2. Saleor — best if you love GraphQL

Choose Saleor if:

• Your frontend team prefers GraphQL
• You have complex product models
• You need multi-region, multi-channel, B2B capabilities
• You’re comfortable with Python/Django

Its API model is very clean for frontend developers because the storefront consumes a strongly structured GraphQL API. hunchbite.comossalt.com

3. commercetools — best for enterprise-scale composable commerce

Choose this when:

• You have many systems (ERP, PIM, CMS, loyalty, pricing engines)
• Commerce is one service in a larger architecture
• You have enterprise engineering resources

It gives enormous flexibility but usually requires more architecture work. vendure.ionaturaily.com

4. Shopify headless — best when you want to ship, not build commerce infrastructure

A custom frontend on Shopify gives you:

• Excellent checkout reliability
• Payments, tax, fraud, inventory, admin tooling
• Huge ecosystem

The tradeoff is that your backend customization is constrained by Shopify’s model. vendure.ionaturaily.comwww.askantech.com

If I were choosing for a new custom frontend project:

• Solo developer / small engineering team: Medusa
• GraphQL-first team: Saleor
• Enterprise architecture: commercetools
• Brand wants custom UX but doesn’t want commerce ops headaches: Shopify headless
• Marketplace or unusual checkout flows: Medusa or Saleor

For a modern stack like Next.js + React + TypeScript, I’d start by evaluating Medusa vs Saleor vs Shopify Storefront API. The deciding question is:

“Do I want to customize the commerce engine itself, or only customize the customer experience?”

If you need to rewrite commerce behavior → Medusa/Saleor.
If you mainly need a custom storefront → Shopify headless is often enough. ribbsaetersystems.com

I can also give you a developer-focused comparison of APIs, auth models, webhooks, checkout flows, and Next.js integration patterns if that’s the direction you’re building.

If you’re a developer building a custom frontend and your priorities are maximum flexibility + strong APIs, I’d generally rank the options differently than a business buyer would. The “best” choice depends on whether you want to own the commerce backend or just consume a powerful managed API. Guideflow Vendure

My shortlist for developer-first headless commerce

Naturaily Vendure## My recommendations by scenario

1. You want maximum control → Medusa

I’d look at Medusa first for a developer-built product.

Good if you want:

• Next.js / React storefront
• custom checkout logic
• unusual product models
• marketplace behavior
• your own infrastructure
• full control over backend code

It feels closer to a commerce framework than a traditional ecommerce platform. CozyCommerce

Stack example:

Next.js frontend
        |
        |
Medusa API
        |
Postgres + custom services

2. You love GraphQL → Saleor

Saleor is attractive if your frontend team wants a strongly typed API and excellent data querying.

Strengths:

• GraphQL-native
• clean developer experience
• great fit for React/Next.js
• good for custom storefronts

Tradeoff:

• you’ll likely spend more time adapting the platform to unusual business rules. Guideflow

3. You’re building enterprise-scale → commercetools

commercetools is one of the strongest API-first commerce platforms.

Choose it if you need:

• multiple regions
• complex pricing
• B2B workflows
• multiple storefronts
• composable architecture

Tradeoff:

• expensive
• requires experienced engineering teams
• you assemble more pieces yourself Guideflow

4. You want commerce solved, not built → Shopify headless

Shopify with a custom frontend is a pragmatic choice.

Great for:

• DTC brands
• subscriptions
• payments
• inventory
• apps/integrations
• launching quickly

The downside:

• you don’t own the backend model
• some deeply custom flows become workarounds Shopify

My ranking for a developer building a custom frontend

If I were choosing purely as an engineer:

1. Medusa — best balance of flexibility + developer experience
2. Vendure — excellent if you’re a TypeScript/NestJS shop
3. Saleor — best GraphQL-first option
4. commercetools — best enterprise API architecture
5. Shopify headless — best operational simplicity
6. BigCommerce headless — good middle ground

Naturaily VendureA few questions would change the recommendation:

• Are you building B2C, B2B, marketplace, subscriptions, or something custom?
• Are you using Next.js/React, Vue/Nuxt, mobile apps, or something else?
• Do you want to self-host, or is SaaS acceptable?

For a brick-and-mortar + ecommerce business, the “best” omnichannel inventory platform depends mainly on your complexity (number of stores, SKUs, warehouses, marketplaces, wholesale, manufacturing). There isn’t one universal winner, but these are the strongest fits:

My usual recommendations by scenario

• You have 1–3 stores + Shopify website:

→ Start with Shopify POS unless your inventory is unusually complex. Salesforce

• You have stores + Shopify + Amazon/eBay/wholesale + lots of SKUs:

→ Look seriously at Cin7. It is designed around keeping multiple sales channels and inventory locations synchronized. Cin7

• You are retail-first (fashion, gifts, specialty retail, many variants):

→ Lightspeed Retail is often a better operational fit than an ecommerce-first system. Fit Small Business

• You manufacture, kit products, or manage complex purchasing:

→ Consider Cin7, Katana, or an ERP approach. Cin7

Features I’d insist on before choosing

Make sure the platform supports:

• Real-time stock sync between store, website, and marketplaces
• Multi-location inventory (store, warehouse, back stock)
• Purchase orders and supplier management
• Barcode scanning and stock counts
• Returns/exchanges across channels
• “Available to promise” inventory (so you don’t oversell)
• Accounting integration (e.g., Xero/QuickBooks)
• Order routing (ship-from-store, pickup, warehouse fulfillment)

A few details would let me narrow this down:

1. What ecommerce platform are you using now (Shopify, WooCommerce, Magento, etc.)?
2. What POS runs your physical stores?
3. Roughly how many SKUs and locations?
4. Do you sell on marketplaces like Amazon/eBay or wholesale?

If your goal is an artisan marketplace with many independent sellers, I’d shortlist these three:

🥇 My recommendation: CS-Cart Multi-Vendor

For an artisan marketplace, CS-Cart Multi-Vendor is particularly strong because it is designed around the idea that many independent sellers operate inside one storefront. It supports separate vendor dashboards, vendor storefronts, product moderation, vendor commissions, vendor plans, vendor ratings, analytics, and seller-specific promotions. www.cs-cart.com/ www.cs-cart.com/

The payment architecture is also important: it supports marketplace payment flows, including Stripe Connect and PayPal, with automatic splitting of payments between the marketplace and vendors. www.cs-cart.com/ CS-Cart Documentation

It also advertises no vendor/product limits, an open API, self-hosting, and extensive customization, which is attractive if you expect hundreds or thousands of artisans rather than just a handful. www.cs-cart.com/

I'd choose it if your model is something like:

• 100–10,000+ artisans
• Each artisan has their own shop/profile
• Artisans upload/manage their own products
• You take a commission on each sale
• Customers can purchase from multiple artisans
• Each artisan receives their share automatically
• You control seller approval and product quality
• You may eventually add subscriptions, featured listings, advertising, etc.

🥈 Sharetribe

sharetribe.com is excellent if your priority is getting an MVP running quickly without building a marketplace platform from scratch.

It has built-in seller onboarding/KYC, Stripe payments, automatic payouts, commissions, delayed payouts, messaging, and marketplace management. Sharetribe Sharetribe

I'd pick Sharetribe if you're testing the concept and don't yet know whether you'll have 50 artisans or 5,000.

🏢 Mirakl

mirakl.com is the enterprise option. It is built for large-scale seller onboarding, catalog management, automated order routing, commissions, payouts, KYC, multi-country operations, and very large transaction volumes. Mirakl says its platform is used by 450+ enterprises. Mirakl

For a new artisan marketplace, though, I'd generally consider it too heavy and expensive unless you're already operating at enterprise scale.

What I'd choose

If you're building a real artisan marketplace rather than just an MVP:

CS-Cart Multi-Vendor + Stripe Connect

That gives you a much more traditional Etsy-style architecture: one marketplace → many artisan shops → one customer checkout → orders split by seller → commissions → seller payouts.

The most important thing isn't just "multi-vendor." I'd specifically evaluate the platform against seller onboarding, split payments, commissions, seller dashboards, shipping by vendor, returns/refunds, product approval, tax handling, and scalability.

If you tell me roughly how many artisans you expect (e.g. 100, 1,000, 10,000+) and whether you're building something like Etsy, I can recommend the best architecture and compare CS-Cart vs Sharetribe vs Shopify + marketplace app vs WooCommerce for your exact use case.

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

My ranking for a solo beginner:

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

Stage 1: Start with Etsy + a POD supplier

Use:

• Etsy storefront
• Printify or Printful for fulfillment

Why:

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

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

A realistic lean setup:

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

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

Stage 2: Move winners to Shopify

Once you have:

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

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

When WooCommerce makes sense

Choose WooCommerce if:

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

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

What I would avoid at the beginning

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

Simple beginner stack I’d choose

First 90 days:

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

After traction:

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

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

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

If you need B2B workflows out of the box—especially custom catalogs, customer-specific pricing, and net payment terms—you should focus on platforms with native B2B commerce modules rather than adding wholesale apps.

Here are the strongest options:

Experience League Shopify## My shortlist by scenario

1. You need serious B2B complexity (distributors, manufacturers)

Choose Adobe Commerce.

It is one of the deepest out-of-the-box B2B platforms:

• Customer/company accounts
• Shared catalogs
• Account hierarchies
• Custom pricing
• Quote workflows
• Requisition lists
• Buyer permissions

Experience League### 2. You want B2B + D2C on one platform

Choose Shopify Plus.

Shopify B2B includes:

• Company accounts and locations
• Custom catalogs
• Customer-specific pricing
• Net payment terms
• PO numbers
• Self-service reordering

Shopify Help Center Shopify Help CenterThe main caveat: if you need complex RFQs, multi-step approvals, or highly customized procurement flows, you may outgrow Shopify's native B2B features faster than Adobe/SAP-style platforms. Elogic Commerce

3. You want SaaS but more B2B-oriented than Shopify

Choose BigCommerce B2B Edition.

Good for:

• Wholesale catalogs
• Bulk ordering
• Customer groups
• Multi-store setups
• ERP integrations

Shopify## A practical recommendation

For most B2B companies today:

• $1M–$50M revenue, moderate complexity: Shopify Plus or BigCommerce
• $50M+ revenue, distributor/manufacturer workflows: Adobe Commerce or SAP Commerce
• Sales-driven enterprise with Salesforce CRM: Salesforce Commerce Cloud

Before selecting, I would verify these specific workflows:

1. Can each customer see a different catalog?
2. Can pricing vary by customer/account/contract?
3. Can buyers have roles (buyer vs approver vs admin)?
4. Can orders use Net 30/60/90 terms?
5. Can POs, quotes, and approvals happen without sales rep intervention?
6. Does it integrate cleanly with your ERP (NetSuite, SAP, Dynamics, etc.)?

If you share your industry (manufacturing, wholesale, distribution, SaaS, etc.), order volume, ERP, and whether you need B2B-only or B2B+D2C, I can narrow this to 2–3 best-fit platforms.

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

My pick: Shopify + a subscription app

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

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

shopify.com

When I'd choose Recharge

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

It's particularly attractive if you need things like:

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

One important distinction

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

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

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

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

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

For a subscription box business, I’d shortlist these:

• skio.com — best overall for a serious subscription-box operation. Skio handles recurring billing, payment retries, customer self-service, and—particularly useful for boxes—order days/cutoffs and batch fulfillment, so you can align all subscribers to a warehouse/shipping schedule. It also supports prepaid subscriptions and Build-a-Box models. Skio Skio Skio
• shopify.com — best if you're starting lean. It's native to Shopify, supports weekly/monthly/yearly recurring billing, skips/pauses/cancellations, and Shopify handles the resulting subscription orders through its normal fulfillment system. Shopify Help Center Shopify Help Center
• rechargepayments.com — strong mature alternative. It's worth considering if you expect a larger subscription program and need a broader subscription ecosystem/integrations; industry comparisons continue to put it among the leading Shopify subscription platforms. ChurnTools
• Appstle — worth evaluating if keeping costs down is important. Shopify's current app directory specifically lists it for subscriptions, subscription boxes, and bundles, with a free plan available. Shopify App Store

My pick

If your box is something like “customers receive a curated box on the 15th of every month”, I'd lean Shopify + Skio. Skio's order-day functionality is unusually well suited to this model: you can establish a cutoff, batch orders on a specific day, and coordinate fulfillment rather than having orders trickle into your warehouse every day. Skio

If you're validating the idea and expect only a few hundred subscribers initially, start with Shopify Subscriptions and avoid paying for more subscription infrastructure than you need.

If you tell me your expected subscriber count, box price, whether customers choose the contents, and whether you're self-fulfilling or using a 3PL, I can narrow this down to the best 1–2 options and compare their likely costs.

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

Choose based on complexity:

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

My default decision rule:

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

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

My recommendation: Shopify

For most international stores, I’d recommend Shopify, specifically Shopify Markets + Shopify Payments.

It’s the strongest combination of multi-currency, localized storefronts, and localized checkout without a lot of custom development. Shopify Markets lets you configure markets by country/region, including local currency, language, pricing, product availability, domains, and taxes. Shopify Help Center Shopify Help Center

Why Shopify fits your requirements

• Multi-currency: Customers can browse, checkout, and receive refunds in their local currency. Shopify Payments is required for multi-currency checkout in the standard setup. Shopify Help Center Shopify Help Center
• Localized checkout: The customer's shipping address can determine the appropriate market and therefore the checkout currency and other market-specific settings. Shopify Help Center
• Languages & domains: You can create localized experiences with different languages and country-specific domains/subfolders. Shopify
• Market-specific pricing: You can use automatic conversion or manually control exchange rates/pricing and rounding. Shopify Help Center
• International taxes/duties: If you're US-, UK-, or Canada-based and eligible, Shopify Managed Markets can additionally act as merchant of record and handle foreign taxes, duties, and import fees. Shopify Help Center Shopify

When I would choose something else

BigCommerce is particularly worth considering if you need highly customized regional storefronts and checkout/payment experiences; its international offering supports localized storefronts, currencies, payment methods, shipping, and tax. BigCommerce

Adobe Commerce is the better fit when you have a substantial technical team and need deep control over multiple websites/stores, currencies, languages, and regional configurations. Experience League Experience League

Bottom line: If you're building a new international store and don't have an unusual enterprise requirement, I'd start with Shopify Markets + Shopify Payments. It gives you the best balance of localization capability, checkout quality, and operational simplicity.

If you tell me where your business is based, the countries you want to sell into, and whether it's B2C or B2B, I can narrow this down to the best platform and plan for your specific setup.

If your priority is minimizing PCI DSS compliance work, I’d favor a fully hosted SaaS ecommerce platform with hosted checkout/payment fields rather than WooCommerce or a self-managed platform.

My shortlist

1. BigCommerce — probably my first choice for minimizing PCI burden.

BigCommerce maintains PCI DSS compliance for its platform, and its hosted checkout can keep card data away from your storefront. Its documentation explicitly describes a hosted checkout designed to simplify PCI compliance. BigCommerce BigCommerce

2. Shopify — excellent if you want the simplest overall operational model.

Shopify's fully hosted architecture means you aren't responsible for operating the ecommerce servers, applying OS patches, securing a WordPress installation, etc. For a standard Shopify checkout using Shopify Payments or another appropriately integrated provider, your PCI scope is substantially smaller than with a self-hosted store.

3. Adobe Commerce as a Cloud Service — strong security, but I'd choose it for enterprise requirements rather than minimum compliance effort.

Adobe says its cloud service is PCI DSS compliant and removes manual infrastructure patching/maintenance, but customers remain responsible for custom code and extensions.

What I'd avoid if PCI simplicity is the goal

WooCommerce

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

Best options

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

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

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

My recommendation

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

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

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

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

My recommendation

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

My recommendation: Shopify Plus

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

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

help.shopify.com

The important distinction, though, is:

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

So if your workflow is:

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

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

How I'd rank them

BigCommerce deserves serious consideration

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

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

bigcommerce.com

So if your agency is building something like:

One client company → 5 brands/regions/storefronts

I'd actually lean BigCommerce in some cases.

Adobe Commerce is the power-user option

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

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

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

The architecture I'd use for an agency

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

Agency platform

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

Commerce platform

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

That separation is important.

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

If I were starting an agency today

I'd probably choose:

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

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

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

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

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

My recommendation: Medusa

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

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

You can build something like:

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

and customize essentially every layer:

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

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

medusajs.com · github.com

When I'd choose something else

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

saleor.io · github.com

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

bagisto.com · github.com

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

sylius.com · github.com

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

What I'd pick

If I were starting a new project today:

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

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

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

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

bagisto.com · github.com

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

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

My shortlist by app type

1. Consumer shopping app (Amazon-style storefront)

Pick Shopify.

Why:

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

Typical stack:

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

2. Marketplace app (many sellers)

Consider Stripe Connect + a commerce backend.

Why:

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

3. Retail app tied to physical stores

Pick Square.

Why:

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

4. You want maximum control

Pick Medusa (or another headless commerce backend).

Why:

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

If I were choosing for a new mobile storefront

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

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

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

Ranking for supplier ecosystem:

1. Shopify — Best overall

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

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

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

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

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

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

If your priority is a large dropshipping business with many different supplier integrations, I’d choose Shopify.

The key distinction is that you’re not just looking for a good storefront—you want the largest and most mature supplier/integration ecosystem.

My ranking

1. Shopify — best overall

Shopify currently has hundreds of dropshipping/sourcing apps. Its App Store lists roughly 589 dropshipping apps and more than 480 sourcing-option apps, covering AliExpress, Alibaba, US/EU suppliers, private suppliers, print-on-demand, wholesale, fulfillment, and sourcing agents. Shopify App Store Shopify App Store

That gives you access to integrations such as:

• DSers / AliExpress
• CJdropshipping
• Spocket
• Syncee
• Zendrop
• Printful
• Printify
• Faire
• Supplier-specific/private apps
• Custom API integrations

For example, the current Shopify App Store shows DSers, Syncee, Spocket, Zendrop, CJdropshipping, Printful, Faire and others as active sourcing/dropshipping integrations. Shopify App Store Shopify App Store

The biggest advantage: if you add a new supplier six months from now, there's a good chance they already have a Shopify integration—or a developer can build one against Shopify's APIs.

2. WooCommerce — potentially better if you're technically sophisticated

WooCommerce is extremely flexible. You can assign products to different suppliers, import supplier inventory, automate supplier order notifications, and build/customize integrations yourself. WooCommerce WooCommerce

I'd seriously consider WooCommerce if your model is:

"We have 50–500 suppliers and want to control the integration layer ourselves."

You get more technical freedom than Shopify, but you also take on considerably more responsibility for hosting, plugins, maintenance, compatibility, security, and integration reliability.

3. BigCommerce — interesting for a sophisticated operation

BigCommerce has a strong API/app ecosystem and allows partners to build and distribute integrations through its App Marketplace. Its Channels Toolkit also lets developers build integrations for external sales channels. BigCommerce BigCommerce

I'd put it ahead of Shopify only if your business has unusually complex catalog, B2B, pricing, or operational requirements.

My recommendation for your specific use case

If you're building a multi-supplier dropshipping operation, I'd use:

Shopify + a supplier integration layer

rather than trying to make Shopify itself responsible for every supplier.

For example:

Suppliers → Integration/middleware → Shopify → Customer

The middleware can normalize:

• SKU/product IDs
• Inventory
• Supplier pricing
• Product variants
• Shipping methods
• Order routing
• Tracking numbers
• Returns
• Supplier-specific rules

That becomes particularly important once you have dozens or hundreds of suppliers.

One important caveat

If by "supplier ecosystem" you mean you want to build a platform where suppliers themselves connect to your marketplace, rather than simply finding suppliers to sell through your own store, the answer changes.

In that case I'd compare Shopify, WooCommerce, BigCommerce, Medusa, Saleor, and a custom headless architecture based on supplier APIs, multi-vendor functionality, webhooks, catalog synchronization, and order routing.

If that's what you're building, I can give you a technical architecture comparison for 10, 100, and 1,000+ suppliers—that's a substantially different decision.

BigCommerce has a strong API/app ecosystem and allows partners to build and distribute integrations through its App Marketplace. Its Channels Toolkit also lets developers build integrations for external sales channels.

I'd put it ahead of Shopify only if your business has unusually complex catalog, B2B, pricing, or operational requirements.

My recommendation for your specific use case

If you're building a multi-supplier dropshipping operation, I'd use:

Shopify + a supplier integration layer

rather than trying to make Shopify itself responsible for every supplier.

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

My shortlist for a constrained budget:

1. WooCommerce + inexpensive managed WordPress hosting

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

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

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

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

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

A few details would change the recommendation:

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

For a tight monthly budget, I’d focus on total cost of ownership, not just the advertised subscription price. The cheapest platform can become expensive if you need lots of paid plugins, developer help, or maintenance. Compare the Cloud WooCommerce

My shortlist:

My recommendation by scenario

• Under ~£30/month and you have some technical ability:

Choose WooCommerce. The core software is free, and you can start lean with inexpensive hosting and only add extensions when needed. WooCommerce

• Under ~£50/month and you want the least hassle:

Choose Shopify. It gives you hosting, checkout, product management, payments integrations, and a large ecosystem without needing to manage servers. Shopify

• You expect growth and want fewer add-ons later:

Consider BigCommerce. It includes more built-in commerce functionality, which can reduce app costs as you scale. Compare the Cloud BigCommerce

For a typical small ecommerce business needing the “core” stack:

• Product catalogue ✅
• Inventory ✅
• Payments ✅
• Shipping rules ✅
• Discounts/coupons ✅
• Customer accounts ✅
• Basic analytics ✅
• Email marketing integrations ✅

…I’d usually pick:

1. Shopify if your priority is speed and reliability.
2. WooCommerce if your priority is keeping monthly costs as low as possible.
3. BigCommerce if you already know you’ll need more advanced selling features.

If you tell me your monthly budget (e.g., £20, £50, £100), number of products, country, and whether you have a developer/WordPress experience, I can narrow it to one choice.