Answers that name a competitor

For thousands of SKUs + complex pricing, I’d focus less on storefront features and more on how well the platform handles catalog scale, customer-specific price lists, contract pricing, quantity breaks, ERP/PIM integration, and rules-driven pricing.

My shortlist

If pricing is the hard part, I'd start with Adobe Commerce

Adobe Commerce's B2B functionality is particularly relevant to your situation. It supports shared catalogs with company-specific product selections and pricing, multiple pricing structures, customer/company assignments, tier pricing, and catalog price rules. experienceleague.adobe.com

It also supports pricing at website scope and has explicit mechanisms for managing large numbers of shared catalogs; Adobe recommends its direct-product price-assignment capability when merchants have many shared catalogs. experienceleague.adobe.com

I'd therefore put it at the top if your pricing looks something like:

SKU × customer/account × region × quantity × contract × channel × effective date

Shopify Plus is the "simpler operations" alternative

Shopify Plus has become considerably more capable for B2B. Its catalogs can control both product availability and customer-specific pricing, and Plus allows unlimited B2B catalogs and direct assignment to companies/company locations. It also supports quantity rules and volume pricing. help.shopify.com

I'd favor it when your pricing can be represented reasonably cleanly as catalogs/price lists rather than requiring a highly customized pricing engine.

Consider composable if your catalog/pricing is really complicated

commercetools is attractive when you have an engineering organization capable of building around APIs and you want commerce to be one component of a broader architecture. Shopify's current enterprise comparison also places commercetools among the platforms aimed at custom catalogs, pricing and account hierarchies. www.shopify.com

Similarly, SAP Commerce Cloud becomes particularly compelling if SAP is already the system of record for products, customers, contracts, inventory and pricing.

One important caveat

"Thousands of SKUs" by itself isn't particularly scary for modern enterprise platforms. The number of pricing relationships is what I'd use to choose the architecture.

For example, there's a huge difference between:

• 50,000 SKUs × 10 price lists
• 50,000 SKUs × 5,000 customers
• 50,000 SKUs × customer-specific contracts × quantity breaks × currencies × regions
• prices calculated dynamically from an ERP/CPQ rather than stored in ecommerce

In the last two cases, I'd be much more cautious about selecting a platform primarily because its admin UI handles large catalogs.

My initial recommendation: shortlist Adobe Commerce, Shopify Plus, and commercetools, then add SAP Commerce Cloud if you're SAP-centric and Salesforce Commerce Cloud if Salesforce is your commercial backbone.

If you tell me (1) approximate SKU count, (2) number of customers, (3) B2B vs B2C, (4) what determines a price, and (5) your ERP/PIM, I can narrow this to 2–3 platforms and explain which architecture I'd choose.

For a developer building a custom frontend, the “best” headless commerce platform depends on whether you want maximum control or minimum backend work. The strongest options today fall into a few categories. Naturaily Netguru

My shortlist for flexibility + APIs

PowerGate Software Naturaily## If I were choosing as an engineer

1. Maximum flexibility: commercetools

Pick this if your frontend is a competitive advantage and you expect complex requirements:

• Multiple storefronts
• Multi-region catalogs
• Custom pricing rules
• B2B workflows
• ERP/PIM/OMS integrations
• Marketplace or marketplace-like models

Its APIs and data model are designed around composable commerce rather than extending a traditional ecommerce platform. LaunchTry Netguru

Typical stack:

• Next.js / React frontend
• commercetools APIs
• Contentful/Sanity for CMS
• Algolia/Elastic for search
• Custom backend-for-frontend layer

Downside: you own a lot of architecture.

2. Best developer experience: Medusa

For a smaller engineering team that wants control, I would seriously consider Medusa.

Good fit if you want:

• TypeScript/Node ecosystem
• Own your database and infrastructure
• Custom checkout logic
• Custom product models
• Your own APIs/services around commerce

It feels closer to building your own commerce engine without starting from zero. Guideflow Pharos Production

3. Best GraphQL-first option: Saleor

Saleor is attractive if your team likes GraphQL and Python.

Strengths:

• Clean GraphQL API
• Open source
• Good fit for custom storefronts
• Strong developer control

Less ideal if you need a huge ecosystem of ready-made commerce integrations.

4. Pragmatic choice: Shopify headless

If the business wants to sell quickly, Shopify is hard to ignore.

You get:

• Payments
• Checkout
• Admin tooling
• Inventory/order workflows
• Huge app ecosystem

Then build your frontend separately using the Storefront API/Hydrogen approach. Vendure

The limitation is that Shopify remains the commerce core; you are customizing the experience around it rather than owning the entire commerce model.

My ranking by scenario

• Building a unique commerce product/platform: Medusa or commercetools
• Enterprise retailer with many channels: commercetools
• Startup with strong engineering team: Medusa
• Content-heavy brand site: Shopify headless + modern CMS
• B2B with complex pricing/workflows: commercetools, Medusa, or Elastic Path
• Need to launch in months, not years: Shopify headless

For a greenfield custom frontend, my default picks would be:

1. Medusa if your team wants ownership and speed of iteration
2. commercetools if this is a serious enterprise commerce platform
3. Shopify headless if business operations matter more than backend freedom

A few questions would change the recommendation significantly:

• Are you building B2C, B2B, or marketplace?
• Expected scale (SKUs/orders/day)?
• Frontend stack (Next.js, React Native, Vue, etc.)?
• Do you need custom checkout/pricing logic, or mostly a custom UI?

If your goal is a marketplace for many independent artisans/sellers, I’d shortlist these:

My recommendation: CS-Cart Multi-Vendor

For artisans, I'd lean toward CS-Cart Multi-Vendor if you're expecting hundreds or thousands of sellers.

It is designed specifically around independent vendors rather than trying to turn a normal ecommerce store into a marketplace. It supports vendor onboarding/approval, vendor-specific permissions, commissions, vendor plans, product management, shipping, and vendor storefronts. docs.cs-cart.com

It also has capabilities particularly useful for a marketplace where different artisans sell similar products—for example, multiple vendors can offer the same product at different prices, allowing customers to compare offers. docs.cs-cart.com

CS-Cart Multi-Vendor marketplace builder

When I'd choose Sharetribe instead

Choose Sharetribe if you're building a new marketplace and want to validate the concept before investing heavily in development. It has built-in supplier onboarding, listings, payments, automated payouts, commissions, reviews, messaging, and approval workflows. www.sharetribe.com

Sharetribe marketplace platform

For an artisan marketplace, I'd specifically want these capabilities:

• Seller self-registration + admin approval
• Individual artisan storefronts
• Seller dashboards
• Product/listing management
• Commission per sale
• Automated seller payouts
• Stripe Connect or equivalent marketplace payments
• Seller-specific shipping
• Reviews/ratings
• Seller verification/KYC
• Product moderation
• Coupons/promotions
• Vendor subscriptions or listing fees
• Bulk seller onboarding
• Search/filtering by artisan, category, location, material, etc.
• Ability to scale to thousands of sellers

If you tell me roughly how many artisans you expect (e.g. 100, 1,000, or 10,000+), whether they're selling physical handmade products, and your budget, I can narrow this to the best 2–3 platforms and compare their actual costs and limitations.

For a subscription-box business, I’d start with Shopify + a dedicated subscription app rather than choosing an ecommerce platform based on recurring billing alone.

My picks

1. Best overall for a new subscription box: Shopify + Appstle.
Shopify's current subscription-app ecosystem specifically supports subscription boxes, and Appstle is one of the prominent options. Shopify highlights Appstle's ability to handle curated boxes, customer skip/pause controls, and subscription-specific workflows. www.shopify.com

2. Best if you expect to scale: Shopify + Recharge/Skio.
Skio is particularly interesting if your boxes involve build-a-box, prepaid plans, different delivery cadences, sophisticated payment recovery, or retention flows. Its current plans support Subscribe & Save, prepaid subscriptions, and Build-a-Box, while its billing system handles recurring order generation and payment retries. help.skio.com

One important 2026 wrinkle: Skio joined Recharge in June 2026, so I'd evaluate them as part of the same broader ecosystem rather than treating them as completely independent long-term bets. skio.com

3. Shopify Subscriptions is fine if your model is simple.
If every customer gets essentially the same box every month and you don't need elaborate customization, Shopify's native option keeps billing and store administration nicely unified. www.shopify.com

The fulfillment piece matters

I'd separate subscription billing from physical fulfillment in your architecture:

Shopify → subscription app → orders → 3PL/fulfillment provider

That gives you freedom to change warehouses later without migrating your subscription customers. For boxes involving kitting several products together, look specifically for a 3PL that supports kitting/bill-of-materials, not merely pick-and-pack. Current fulfillment guidance emphasizes that subscription businesses eventually need the commerce platform, billing engine, 3PL, carriers, and inventory systems to work together. www.swell.is

What I'd choose

If you're just launching: Shopify + Appstle + a subscription-friendly 3PL.

If you already expect hundreds/thousands of subscribers, customized boxes, or aggressive retention marketing: Shopify + Recharge/Skio + a capable 3PL.

If you tell me (1) what goes in the box, (2) monthly price, (3) expected subscribers in year 1, and (4) whether customers choose their contents, I can narrow this down to the best 2–3 setups and compare their likely costs.

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

Why it’s my top pick:

• Multi-currency: Markets lets you set local currencies and market-specific pricing; Shopify Payments supports customers paying in their local currency. apps.shopify.comwww.shopify.com
• Localized checkout: You can provide local payment methods, localized address forms, and regional checkout experiences. apps.shopify.com
• Localization beyond currency: Languages, domains, catalogs, pricing, and content can all vary by market while remaining under one store/admin. apps.shopify.comwww.shopify.com
• Cross-border complexity: If you're eligible, Shopify Managed Markets can handle duties, taxes, import fees, and international pricing as a merchant-of-record service. www.shopify.com
• Easier to operate: Compared with assembling WooCommerce from multiple plugins, the international functionality is much more integrated. WooCommerce's own documentation points to separate solutions for currencies and multilingual stores.

My ranking

BigCommerce is the strongest alternative if you need highly customized regional storefronts. Its Multi-Storefront architecture can give different countries their own languages, currencies, payment methods, catalogs, promotions and checkout experiences. It also recently added Stripe Adaptive Pricing, which supports local-currency payments across 150+ countries for eligible setups.

Bottom line: If your priority is “launch internationally with the least friction while still giving customers a genuinely local checkout,” choose Shopify. If you tell me your number of countries, approximate annual revenue, B2C vs. B2B, and whether you need separate storefronts per country, I can recommend the exact platform/plan and architecture.

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

My shortlist

The important distinction is that “PCI compliant platform” does not mean your business has zero PCI responsibilities. PCI SSC explicitly says even merchants using outsourced payment processing can have responsibilities such as securing their web environment and, under current SAQ A rules, external vulnerability scanning. PCI Security Standards Council PCI Security Standards Council

What I'd choose

For the least compliance headache: Shopify + Shopify Payments, assuming Shopify Payments is available for your business and meets your payment requirements.

The architectural principle matters more than the brand, though: keep raw card data completely out of your infrastructure. PCI SSC says merchants can qualify for the simpler SAQ A path when the payment page's elements originate directly from a PCI-validated third party. PCI Security Standards Council PCI Security Standards Council

A redirect to a fully hosted payment page is particularly attractive from a compliance perspective. PCI SSC distinguishes this from payment forms generated by your own site: the latter can put substantially more security controls on you. PCI Security Standards Council PCI Security Standards Council

One wrinkle: embedded payment iframes aren't necessarily equivalent to a redirect anymore. Under PCI DSS v4.0.1, SAQ A has additional requirements concerning script attacks for merchants using embedded payment pages, whereas those particular criteria don't apply to redirect-based checkout. PCI Security Standards Council PCI Perspectives

So, if I were ranking purely for “I want the smallest PCI/security team burden”:

1. Shopify with hosted checkout
2. BigCommerce with hosted checkout
3. Wix with hosted checkout
4. WooCommerce + hosted payment provider
5. Self-hosted/custom ecommerce + payment API — highest burden

If you tell me your approximate annual sales, number of orders, B2C vs. B2B, countries you sell into, and whether you need subscriptions, I can narrow this to the best 2–3 choices and compare their actual PCI responsibilities.

The important distinction is that “PCI compliant platform” does not mean your business has zero PCI responsibilities. PCI SSC explicitly says even merchants using outsourced payment processing can have responsibilities such as securing their web environment and, under current SAQ A rules, external vulnerability scanning. PCI Security Standards Council PCI Security Standards Council

What I'd choose

For the least compliance headache: Shopify + Shopify Payments, assuming Shopify Payments is available for your business and meets your payment requirements.

The architectural principle matters more than the brand, though: keep raw card data completely out of your infrastructure. PCI SSC says merchants can qualify for the simpler SAQ A path when the payment page's elements originate directly from a PCI-validated third party. PCI Security Standards Council PCI Security Standards Council

A redirect to a fully hosted payment page is particularly attractive from a compliance perspective. PCI SSC distinguishes this from payment forms generated by your own site: the latter can put substantially more security controls on you. PCI Security Standards Council PCI Security Standards Council

One wrinkle: embedded payment iframes aren't necessarily equivalent to a redirect anymore. Under PCI DSS v4.0.1, SAQ A has additional requirements concerning script attacks for merchants using embedded payment pages, whereas those particular criteria don't apply to redirect-based checkout.

So, if I were ranking purely for “I want the smallest PCI/security team burden”:

For a small food subscription-box business, I’d narrow it to three main approaches rather than looking at generic ecommerce platforms.

My shortlist

1. Subbly — probably my first choice

subbly.co is specifically designed around subscription businesses, including subscription boxes, food delivery, meal kits, replenishment, and customizable boxes. Subbly Subbly

For a food box, some particularly useful capabilities are:

• Weekly, monthly, quarterly, seasonal, or custom billing cycles
• Customers can skip, pause, resume, or cancel
• Customer-managed payment methods and shipping information
• Subscription-specific inventory management
• Multiple SKUs inside a box
• Cutoff dates and specific shipping dates
• Failed-payment recovery
• Customer surveys for creating/customizing boxes
• One-time products alongside subscriptions
• Shipping/fulfillment integrations
• Recurring billing through payment gateways such as Stripe and PayPal Subbly Subbly

That's a very good match for something like "Get a box of locally made snacks every month" rather than a conventional ecommerce store that happens to have subscriptions.

2. Shopify + Appstle/Recharge/etc.

If you expect the business to eventually become a larger food brand with lots of one-time products, I'd seriously consider shopify.com.

Shopify has a large ecosystem of subscription apps. Its current subscription-app marketplace includes options such as Appstle, Kaching, and others. Shopify App Store Shopify App Store

The advantage is that you get an extremely mature ecommerce platform underneath the subscription system:

Shopify → subscription app → payment processing → fulfillment/shipping

That gives you considerably more flexibility if you later want to sell individual products, gift cards, wholesale products, etc.

The downside is that you're assembling more pieces. For a small subscription business, I'd be wary of ending up with Shopify + subscription app + reviews app + bundles app + email app + fulfillment app + ... and paying for all of them.

3. WooCommerce + WooCommerce Subscriptions

I'd choose this primarily if you're already comfortable with WordPress.

It's highly customizable and can be economical, but you're taking on more responsibility for hosting, plugins, updates, security, and compatibility. For a small food business where the goal is simply to sell boxes and fulfill them reliably, I wouldn't choose it over Subbly unless you have a specific reason to want WordPress.

What I'd choose for your situation

If your business looks roughly like:

Customer signs up → chooses a box → gets charged every month → you pack the box → ship it → customer can skip/pause/change their subscription

I'd start with Subbly.

It's built around exactly that workflow rather than adapting a general ecommerce platform to it. Subbly also supports customers building/customizing subscription boxes, which could be particularly useful if your food boxes have selectable items. Subbly

If instead you're envisioning:

Subscription box + 50 individual food products + gift shopping + promotions + wholesale + potentially a large catalog

I'd start with Shopify + a subscription app.

One important thing for food

I'd evaluate the platforms less on the basic "can it charge someone every month?" question—they all can—and more on fulfillment mechanics.

Before committing, I'd test whether the software handles your exact model for:

• Subscription cutoff dates
• Billing date vs. shipping date
• Skip/pause
• Failed credit cards
• Changing the contents of a box
• Seasonal boxes
• Inventory allocation for upcoming subscription shipments
• Different shipping rates/zones
• Local pickup vs. shipping
• Sales tax
• Expiration/lot tracking if applicable
• Customers changing their next shipment without contacting you

Subbly is particularly strong on these subscription-specific workflows. Subbly Support Center

If you tell me roughly how your box works (e.g. fixed box vs. customer chooses items, monthly vs. weekly, expected number of subscribers, and whether you need shipping/local delivery), I can narrow this down to 2–3 specific setups and what each would likely cost you per month.

Shopify → subscription app → payment processing → fulfillment/shipping

That gives you considerably more flexibility if you later want to sell individual products, gift cards, wholesale products, etc.

The downside is that you're assembling more pieces. For a small subscription business, I'd be wary of ending up with Shopify + subscription app + reviews app + bundles app + email app + fulfillment app + ... and paying for all of them.

3. WooCommerce + WooCommerce Subscriptions

I'd choose this primarily if you're already comfortable with WordPress.

It's highly customizable and can be economical, but you're taking on more responsibility for hosting, plugins, updates, security, and compatibility. For a small food business where the goal is simply to sell boxes and fulfill them reliably, I wouldn't choose it over Subbly unless you have a specific reason to want WordPress.

What I'd choose for your situation

If your business looks roughly like:

Customer signs up → chooses a box → gets charged every month → you pack the box → ship it → customer can skip/pause/change their subscription

I'd start with Subbly.

It's built around exactly that workflow rather than adapting a general ecommerce platform to it. Subbly also supports customers building/customizing subscription boxes, which could be particularly useful if your food boxes have selectable items.

If instead you're envisioning:

Subscription box + 50 individual food products + gift shopping + promotions + wholesale + potentially a large catalog

I'd start with Shopify + a subscription app.

One important thing for food

For a local brick-and-mortar shop, I’d generally recommend Square Online if your primary goal is to sell locally with in-store pickup + local delivery and you already have, or plan to use, Square for your point of sale.

My ranking

1. Square Online — best for a typical local shop

• Online store and physical-store POS are tightly integrated.
• Supports in-store/curbside pickup and local delivery.
• You can use your own staff for delivery or use on-demand delivery partners.
• Inventory, orders, payments, and in-person sales can stay in one system. Square Square Square
• Particularly attractive if you're selling things like gifts, specialty food, flowers, apparel, home goods, etc.
• Shopify — best if you expect the ecommerce side to become a major business

• Excellent online storefront and much stronger ecommerce ecosystem.
• Native local delivery lets you define delivery areas by radius or ZIP/postal code, set delivery pricing, and provide delivery updates. Shopify
• Pickup is well supported, and Shopify has a large ecosystem of pickup/delivery apps if you need sophisticated scheduling, routing, or delivery rules. Shopify Shopify App Store
• I'd choose this over Square if you expect significant online growth, lots of products, subscriptions, marketing, or multiple sales channels.
• WooCommerce — best if you already have WordPress

• Very flexible, but more hands-on.
• You can build almost any pickup/delivery workflow, but you'll generally be assembling and maintaining more pieces yourself.
• I wouldn't choose it specifically for a simple local pickup/delivery operation unless there's already a good reason to use WordPress.

The simple decision

I'd pick Square if:

"We're primarily a local store, and we want our website to be an extension of our physical shop."

I'd pick Shopify if:

"We're a retail brand that happens to have a local store, and we want ecommerce to become a significant part of the business."

One important distinction: the ecommerce platform and the delivery service don't necessarily have to be the same thing. For example, Shopify can manage the order and have your staff deliver it, while Square can similarly support your own couriers or on-demand delivery. Square Shopify

If you tell me what kind of shop it is, approximate number of products, whether they already use a POS (Square/Clover/etc.), and roughly how far they want to deliver, I can tell you which I'd choose and what the setup would look like.

For a small B2B parts supplier with a handful of wholesale customers, I’d focus less on “B2B ecommerce” broadly and more on how cleanly the platform handles negotiated, customer-by-customer SKU pricing.

My ranking

BigCommerce is probably the one I'd investigate first. Its B2B functionality has native price lists that can customize pricing down to the individual SKU and assign those prices to individual wholesale accounts or customer groups. www.bigcommerce.comdocs.bigcommerce.com

That's a particularly good model for parts distribution. For example:

• Customer A → SKU 123 → $8.40
• Customer B → SKU 123 → $7.95
• Customer C → SKU 123 → $9.10
• Customer A → SKU 456 → $14.25
• Everyone else → standard price

You can also combine customer-specific pricing with customer groups, catalogs, quantity breaks, and B2B purchasing workflows. docs.bigcommerce.com

Shopify is a very close second

Shopify B2B has gotten considerably better for this use case. Its B2B catalogs allow you to assign products and pricing to particular companies/company locations, including fixed prices and volume pricing. help.shopify.com

The catch is that the exact pricing behavior matters. For example, when multiple catalogs apply to a company, Shopify has rules around which price wins; you don't want to accidentally create overlapping catalogs and expose a lower price than intended. help.shopify.com

For your business, I'd choose based on this

Pick BigCommerce if:

• You have 5–100-ish wholesale accounts.
• Pricing is negotiated per customer and/or per SKU.
• You sell lots of parts/SKUs.
• Customers need login-based pricing.
• You want B2B functionality without building a custom system.

Pick Shopify if:

• You also want a strong consumer/DTC storefront.
• Your pricing can mostly be organized into catalogs/customer tiers.
• Ease of administration and the Shopify ecosystem are priorities.
• You expect to add other sales channels later.

Don't start with Adobe Commerce unless you already have substantial operational complexity. It is powerful—shared catalogs, company structures, quote workflows, etc.—but it's generally overkill for a small supplier. www.shopify.com

One thing I'd check before choosing

For a parts supplier, customer-specific pricing isn't the only important question. I'd specifically test these five scenarios in a demo:

1. Customer A gets a unique price for 300 individual SKUs
2. Customer B gets a different price on those same SKUs
3. New SKU → automatically gets Customer B's standard discount
4. Customer A has a special negotiated price on just 10 SKUs
5. Customer logs in → sees only their price, not MSRP/another customer's price

If you tell me roughly how many SKUs you have, how many wholesale customers, and whether each customer has a mostly unique price list or just a discount percentage (e.g. “20% off list”), I can tell you which platform I'd pick and what the simplest setup would be.

If you’re non-technical and your main sales channels will be social links + email, I’d narrow it to Shopify vs. Wix.

My pick: Shopify

Shopify is the stronger choice if you expect social selling to be a major part of the business.

• Instagram + Facebook: Shopify can sync your product catalog with Meta, so products can appear in Facebook/Instagram shopping experiences, and you can manage orders from Shopify. help.shopify.com
• More social channels: Shopify also supports channels including TikTok, Pinterest, YouTube and others. www.shopify.com
• Email: Shopify has built-in marketing tools, with additional email/CRM options available if you need more sophisticated campaigns.
• Links are easy: You can put a Shopify product or collection link directly in an Instagram bio, Facebook post, email, text message, etc.
• Room to grow: If social selling takes off, Shopify has a much larger ecosystem of apps and integrations.

Shopify's official site

The easier alternative: Wix

Wix may actually feel easier at the beginning if you want to build the whole website yourself. Wix specifically targets non-technical store owners and supports Facebook/Instagram selling, email marketing, CRM, social posts and ads from its ecosystem. www.wix.com

Wix's official site

What I'd choose for your situation

Bottom line: If you're thinking “I'll post on Instagram/Facebook, put the product link in my bio, send emails, and want everything to flow into one storefront,” I'd go with Shopify. If you're thinking “I want the simplest possible website builder and I'm only going to sell a modest number of products,” I'd choose Wix.

One important distinction: “integrates with social media” isn't the same as “people can complete the purchase inside the social app.” Meta's commerce requirements and available shopping features vary by region/account, so I wouldn't choose a platform based solely on the promise of an Instagram Shop. help.shopify.com

If you tell me what you're selling (physical products, digital products, services, subscriptions, etc.) and roughly how many products, I can tell you which platform I'd pick and what the simplest setup would be.

If your shipping rules are highly specific and you need live carrier-calculated rates, I’d narrow it to Shopify vs. BigCommerce.

• shopify.com — best for a small team that wants simplicity. Shopify supports shipping profiles, product/location-specific rules, and carrier-calculated rates. You can connect UPS, FedEx, USPS, and other carriers. However, using your own third-party carrier accounts requires the Grow plan with an add-on/annual billing, or Advanced/Plus. Shopify Help Center Shopify Help Center
• bigcommerce.com — better if the shipping logic itself is a major part of your operation. Its plans include real-time rates from carriers including UPS, USPS, FedEx, Canada Post, Royal Mail, and Australia Post. BigCommerce
• WooCommerce can be extremely flexible through plugins, but that flexibility generally means more technical maintenance—less attractive if you have a very small team and don't want to manage the infrastructure yourself. shopify.com

My pick

For “small team + complicated shipping rules + carrier-calculated rates,” I'd lean BigCommerce if your rules involve lots of product, destination, weight, or carrier combinations. I'd choose Shopify if ease of administration and the broader app ecosystem matter more and your rules can be handled through shipping profiles/apps.

One important distinction: if by “very specific shipping rules” you mean things like different carriers based on SKU, dimensional weight, destination, customer type, hazmat status, or combinations of products, tell me what those rules look like. I can compare Shopify, BigCommerce, WooCommerce, and ShipStation/Shippo-style setups specifically against them and tell you which is likely to require the least custom development.

Yes. If customization/configuration is central to your products, I’d choose the ecommerce platform based on how sophisticated the configurator needs to be—not just the normal “size/color” variant system.

My shortlist

🥇 Shopify — probably where I'd start

Shopify has a very large ecosystem specifically for custom products. The Shopify App Store currently has hundreds of product-variant/custom-product apps, including configurators supporting text fields, add-ons, image uploads, personalization, swatches, and live previews. Shopify App Store Shopify App Store

For example, apps such as Zepto Product Personalizer, Globo Product Options, Easify Custom Product Options, and Hulk Product Options are currently highly rated and aimed specifically at this use case. Shopify App Store

shopify.com

I'd choose Shopify if you need things like:

• Name/text personalization
• Multiple option groups
• Add-on pricing
• Conditional options
• File/image uploads
• Color/material/finish selections
• Product previews
• A reasonably easy-to-maintain store

The big advantage is that you can start with Shopify and add a dedicated configurator rather than having to build the entire commerce system yourself.

🥈 WooCommerce — best if your configuration logic is unusual

WooCommerce is particularly interesting if your configurator has complicated rules.

For example:

Choose product → choose dimensions → available materials change → choose material → available finishes change → enter measurements → price is calculated from dimensions → upload artwork → generate production information.

WooCommerce's openness makes this kind of bespoke implementation easier to customize than a more closed platform.

The tradeoff is that you're responsible for more of the technical stack—hosting, WordPress, plugins, updates, compatibility, etc.

🥉 BigCommerce — good, but understand modifiers

BigCommerce has native product modifiers that are quite useful for customization. They support things such as engraving text, colors, checkboxes, and other customer choices, and modifiers can adjust price, weight, and shipping rules. BigCommerce BigCommerce

There's an important catch, though: modifier combinations aren't inventory-tracked variants. A modifier changes how the underlying product is customized/fulfilled rather than creating a separate SKU/variant combination. BigCommerce BigCommerce

So if your business needs:

10 × 20 × 30 dimensions + walnut + brass + option X = SKU ABC123

I'd investigate this carefully before choosing BigCommerce.

The important distinction

I'd separate product options from a true product configurator.

Basic options:

T-shirt
→ Size: M
→ Color: Blue
→ Add name: John

Almost every major platform can handle this.

Advanced configurator:

Sofa
→ Choose model
→ Choose width
→ Choose fabric
→ Choose cushion configuration
→ Choose legs
→ Certain legs become unavailable depending on width
→ Price recalculates
→ Preview changes
→ Upload custom artwork
→ Generate a production-ready configuration

That's a substantially different requirement.

For the latter, I'd lean toward Shopify + a sophisticated configurator app or WooCommerce + a custom/advanced configurator.

My recommendation

If you're a typical customized-product seller, I'd rank them:

1. Shopify — best combination of ecommerce, ease of use, apps, and configurator ecosystem
2. WooCommerce — best if your configuration/production logic is highly customized
3. BigCommerce — excellent if you're larger/B2B-oriented and your configuration fits its modifier model
4. Adobe Commerce — worth considering when you're at enterprise scale

If you tell me what you're selling and what the customer has to configure (e.g. dimensions, materials, colors, text, images, quantities, conditional choices, calculated pricing), I can narrow this down to the 2–3 best platforms and the specific configurator software I'd use with each.

Yes. If the client truly has a $0 hosting budget, you have a few realistic options. The best choice depends on whether you need a full ecommerce store, a custom-coded storefront, or just a catalog + checkout.

Best free hosted storefront options

1. squareup.com — best for small businesses

• $0/month hosted storefront
• Hosting + SSL included
• Product pages, cart, checkout, inventory
• Good if the client is selling physical goods locally
• You only pay payment processing fees when they sell Fit Small Business

Downside: Less developer freedom than building your own frontend.

2. freewebstore.com — simple "launch and go"

• Free hosted store
• SSL included
• Product management
• Payment integrations
• Good for a client who just needs something live quickly Freewebstore

Downside: Customization is more limited.

3. bigcartel.com — good for small catalogs

• Popular with artists/makers
• Free tier exists for very small inventories
• Clean storefront templates Fit Small Business

Downside: Product limits make it unsuitable for larger stores.

4. wix.com — good for design-heavy sites

• Build the storefront free
• Hosting included
• Good visual editor wix.com

Downside: Accepting payments generally requires a paid business plan. wix.com

If you're a freelancer/developer

For more control, I’d consider:

Static frontend + free backend services

Example stack:

• Frontend: React / Next.js / Astro
• Hosting: pages.cloudflare.com or vercel.com free tiers
• Payments: Stripe Checkout
• Products: JSON, Airtable, Supabase, or a headless CMS

This can look much more custom and costs nothing until traffic grows.

Open-source ecommerce

• WooCommerce is free software, but you still need somewhere to host WordPress. Open Source Groups
• PrestaShop is similar: free software, but hosting is the cost.

What I’d pick for a client project

• Small local shop: Square Online
• 5–50 products, handmade goods: Big Cartel or Freewebstore
• Client wants a polished custom site: Astro/Next.js + Stripe Checkout + free hosting
• Client expects a serious ecommerce business later: start on a platform they can eventually migrate away from

One thing to watch as a freelancer: "free hosting" often means the platform owns the checkout/data flow. If you’re building this for a paying client, make sure the account, domain, payment processor, and store ownership are under the client's email, not yours.

For a small local bakery with only a handful of items, I’d keep it very simple. You probably don’t need a full e-commerce website.

My top choice: Square

squareup.com is probably the best fit.

• $0/month on the Square Free plan.
• You get an actual online ordering page rather than just a contact form.
• Customers can choose pickup and you can set fulfillment options.
• You can add only your 5–15 products, with photos, descriptions, prices, and options.
• Customers can pay online.
• You can share the ordering page on Google, Facebook, Instagram, and a QR code.
• There are no monthly fees on the Free plan; Square charges payment processing when someone orders. Square currently lists online payments at 3.3% + 30¢ on the Free plan. Square Square

For a bakery, I especially like that you can make the ordering experience very focused: “Choose your treats → choose pickup time → pay.”

squareup.com

If you want the absolute lowest cost: GloriaFood

gloriafood.com is worth considering if you primarily want online ordering without paying a monthly fee or commission.

Its free plan includes unlimited orders, a website ordering widget, mobile ordering, scheduled orders, pickup/delivery options, and no commission per order. GloriaFood GloriaFood

The catch is that online credit-card payments are a paid add-on ($29/month), so it's less attractive if you want customers to pay by card directly through the ordering page. GloriaFood

What I'd choose for your bakery

I'd start with Square Free. For a bakery selling just a few items, paying $0/month and accepting orders directly is hard to beat.

And you don't even need a traditional website initially—you could have a simple page that says:

Fresh baked goods — order online
🍪 Cookies
🍰 Cakes
🥖 Breads
🧁 Cupcakes

[Order for Pickup]

Then put that link everywhere customers already find you.

If you tell me what your few bakery items are, whether you offer pickup/delivery, and roughly how many orders you get per week, I can recommend the cheapest setup specifically for your bakery and tell you exactly what I'd use.

Yes. If your goal is almost zero overhead (no monthly fee, no inventory, automatic file delivery), there are several good options. For digital downloads + prints, I’d look at these first:

My picks by situation:

• Selling printable art, planners, templates, SVGs, wall art, PDFs: Payhip is probably the best starting point. It gives you a storefront, handles digital delivery, and you can start without paying monthly. payhip.com
• Selling art prints and building a creator following: Ko-fi Shop is attractive because you can combine a shop with tips, memberships, and commissions. ko-fi.com
• Testing one or two products quickly: Gumroad is very simple—upload a file, set a price, share a link. felloai.com

For physical prints, you have two low-overhead approaches:

1. Digital-first: Sell print-ready files (PDF/JPG/PNG) and let buyers print them.
   • Lowest overhead.
   • No shipping, packaging, or customer service around damaged orders.

2. Print-on-demand: Upload designs and have a service print/ship them.
   • More passive, but lower margins.
   • Common options include Printful and Printify (these are production/shipping services rather than storefronts).

A very lean setup would be:

Canva/Affinity Designer → Payhip or Ko-fi → Pinterest/Instagram/TikTok traffic → automated delivery

You could realistically start with:

• $0/month software cost
• no inventory
• no website
• no shipping
• only paying fees when you make sales

If you tell me what kind of downloads you want to sell (wall art, planners, templates, fonts, photography, AI art, craft files, etc.), I can suggest the best platform and pricing model.

For a free storefront focused on preorders + crowdfunding-style sales, I’d usually recommend starting with a lightweight ecommerce platform rather than a traditional crowdfunding site. The best choice depends on whether you need a full branded store, a campaign page, or just a way to collect commitments.

My top picks:

My recommendation by scenario

1. You already have customers/a following
→ Use Square Online or Big Cartel first.
Create a “coming soon” product page, collect preorders, and fulfill once you hit your target.

2. You’re launching a physical product and need a Kickstarter-style campaign page
→ Use Shopify + a crowdfunding/preorder app. Apps like Fundlify or Crowdfunder can add goals, progress bars, reward tiers, and preorder mechanics. apps.shopify.com

3. You have almost no budget and just need to validate demand
→ A simple stack:

• Free storefront (Square Online or Big Cartel)
• Email signup/waitlist
• Preorder product page
• Manual updates to backers

4. You want “if we get 500 orders, we manufacture”
→ Look for true crowdfunding features:

• funding goal
• deadline
• progress bar
• limited rewards/tiers
• automatic refunds if the goal fails

Most free ecommerce tools handle preorders, but fewer handle true crowdfunding logic. apps.shopify.com

If you tell me what you’re selling (physical product, digital product, apparel, game, food, etc.), expected number of backers, and whether you already have an audience, I can narrow it to one platform.

For an agency prospect demo, you probably want a disposable storefront that looks real, has products/cart/admin, and costs $0. Good options:

For an agency showing prospects, I’d usually pick:

1. Spree Commerce Sandbox — best if your prospects are evaluating custom commerce builds or headless setups. You can show catalog → cart → admin → APIs without paying. spreecommerce.org
2. Wix — best if the goal is simply “here’s what your store could look like” in a sales meeting. www.wix.com
3. BigCommerce trial — best if prospects expect a recognizable enterprise commerce platform. www.bigcommerce.com

A common agency pattern is:

• create one “demo brand” (fake products, fake orders, branded theme)
• keep it as a reusable prospect showroom
• duplicate/reset it for each sales opportunity

If you want a Shopify-like demo specifically, I’d lean toward Spree, WooCommerce on a free host, or a trial-based platform rather than trying to keep a live production store running.

For a freelance developer building custom integrations for clients, I’d optimize for extension architecture, maintainability, and speed of custom development, not just “number of plugins.” The best choice depends heavily on your stack:

blog.openreplay.com

My ranking for a freelance integration developer

1. Medusa (best overall for greenfield custom stores)
If you’re building things like:

• ERP integrations
• custom pricing engines
• unusual checkout flows
• subscription logic
• marketplace features
• custom fulfillment

Medusa is a strong fit because it is designed as a commerce engine rather than a monolithic storefront. Its TypeScript stack also makes it easy to share types and patterns with modern frontend apps. opensourceprojects.cc

2. Vendure (best developer experience if you like TypeScript)
Vendure is arguably the cleanest architecture for someone who expects to write lots of custom modules. It uses a plugin model with GraphQL extensions and typed server-side code. The downside is a smaller ecosystem, so you build more yourself. blog.openreplay.com

3. WooCommerce (best money-maker for agency work)
If your clients are:

• local businesses
• brands with existing WordPress sites
• stores needing lots of marketing plugins

WooCommerce can be unbeatable because the ecosystem solves many problems already. The tradeoff is that deep customization often means wrestling with WordPress conventions and plugin conflicts. selfhosting.sh

Platforms I’d be cautious about for freelance work

Magento/Open Source

• Very capable.
• Lots of enterprise demand.
• But onboarding clients into a maintainable custom codebase can become a project by itself.

PrestaShop/OpenCart

• Good traditional store platforms.
• Less attractive if your main value proposition is “I build custom integrations and workflows.”

A practical freelance stack choice

If I were building a reusable consulting skillset:

• Default: Medusa + Next.js + PostgreSQL
• Alternative: Vendure + Next.js for highly customized clients
• Quick revenue projects: WooCommerce
• Enterprise contracts: Shopware or Magento

The biggest advantage of Medusa/Vendure is that you’re selling engineering work rather than becoming a plugin installer. You can build reusable integration modules (payments, ERPs, shipping providers, inventory systems) and carry that expertise between clients. codenote.net

If you tell me your preferred stack (Laravel/PHP, Node/TS, Python, Ruby) and the typical client size (small businesses vs $1M+ merchants), I’d narrow it down further.

If your top priorities are plugin/extension ecosystem + active developer community, I’d pick WooCommerce overall.

My ranking

🥇 WooCommerce — best ecosystem

The biggest advantage is that you're not just getting WooCommerce's extensions—you inherit the enormous WordPress plugin/theme ecosystem as well. Current WooCommerce documentation says its Marketplace puts extensions in front of 3.6M+ active stores, and it provides dedicated tooling for extension development and testing. developer.woocommerce.com

The developer community is unusually accessible: GitHub, official forums, Slack, developer office hours, meetups, and WordPress communities all feed into the ecosystem. woocommerce.com

Choose it if: you want to build plugins, integrations, payment/shipping modules, customizations, SaaS integrations, or client stores and want the largest possible addressable ecosystem.

🥈 PrestaShop — best dedicated ecommerce alternative

PrestaShop has a substantial module ecosystem—its official marketplace has thousands of modules—and the project explicitly supports community developers through GitHub, Slack, forums, and its marketplace. help-center.prestashop.com

I'd favor it over WooCommerce if you don't want WordPress involved and want an ecommerce-first architecture.

🥉 Magento Open Source — best for sophisticated systems

Magento's extension ecosystem is excellent and its architecture is much more appropriate for complicated catalogs, pricing rules, B2B workflows, multiple stores, etc. The downside is developer complexity and operational overhead. It's a much heavier platform than WooCommerce.

🚀 Medusa — best modern developer experience

If by "plugin ecosystem" you really mean "I want a modern commerce engine that my engineering team can extend with code", I'd seriously consider Medusa instead.

The distinction is important: WooCommerce wins on number and variety of ready-made plugins, while Medusa/Saleor/Vendure are stronger choices if you're building a custom headless commerce stack. Recent developer-focused comparisons similarly distinguish WooCommerce/PrestaShop/Magento as mature ecosystems from the newer headless platforms. blog.openreplay.com

My recommendation

For a plugin developer: WooCommerce
For a PHP ecommerce developer wanting a standalone platform: PrestaShop
For enterprise/complex commerce: Magento Open Source
For a TypeScript/Node + React/Next.js team: Medusa
For GraphQL/headless enterprise: Saleor

If I were starting a new ecommerce plugin business in 2026, I'd choose WooCommerce first because the combination of installed base, extension marketplace, WordPress ecosystem, developer resources, and community gives you the largest ecosystem to build against. developer.woocommerce.comgithub.com

If you tell me what kind of plugin you want to build (payments, AI, subscriptions, B2B, shipping, marketing, ERP integration, etc.), I can narrow this down considerably.

If strong security, payment controls, and customer-data compliance are your top priorities, I would narrow the choice to Magento Open Source, WooCommerce (with a hardened architecture), and possibly Saleor/Medusa for a modern headless build. The “best” platform depends heavily on your team’s ability to operate secure infrastructure. Open source gives you control, but it also means you own patching, monitoring, access control, and compliance evidence. www.digitalapplied.com

My recommendation hierarchy

www.opensourcegroups.com

1. Magento Open Source — best for serious compliance programs

Choose Magento if you have:

• A dedicated engineering/security team
• Significant transaction volume
• Complex pricing, B2B, multi-store, or international requirements
• Need for strong audit trails and role-based administration

Security advantages:

• More enterprise-oriented architecture than typical CMS-based commerce
• Better fit for controlled deployment pipelines
• Mature access-control model
• Easier to enforce infrastructure controls (WAF, private networks, logging, SIEM integration)

Tradeoffs:

• Requires experienced developers
• More expensive to run securely
• Patching and infrastructure management are your responsibility in self-hosted deployments www.pcicompliance.com

Typical secure deployment pattern:

• Cloud hosting with private networking
• WAF + DDoS protection
• Managed database
• Secrets manager
• Centralized logging/SIEM
• Automated vulnerability scanning
• Tokenized payments (never store card data)

2. WooCommerce — good if you minimize the attack surface

WooCommerce can be secure, but the risk is usually not WooCommerce itself—it is the WordPress ecosystem:

• Too many plugins
• Poor update discipline
• Weak admin controls
• Shared hosting
• Unvetted extensions

A compliant WooCommerce architecture should:

• Use a PCI-compliant payment gateway
• Never store raw card data
• Restrict admin access with MFA
• Use a minimal plugin set
• Run continuous vulnerability monitoring
• Maintain backups and incident-response procedures

WooCommerce itself notes that PCI compliance depends on the overall environment, payment setup, hosting, and operational controls—not just the plugin. woocommerce.com

3. Saleor/Medusa — best for security-conscious engineering teams

Consider these if you are building:

• A custom customer experience
• Mobile apps
• Multiple sales channels
• A composable commerce platform

Advantages:

• Headless architecture separates storefront from commerce backend
• Smaller attack surface at the storefront layer
• Easier integration with enterprise identity, fraud detection, and data platforms

Tradeoff:

• Requires more software engineering
• Less “ready-to-run” than Magento or WooCommerce

Controls I would require regardless of platform

For payments:

• Use tokenization through a PCI-compliant processor
• Avoid storing cardholder data
• Implement 3-D Secure where appropriate
• Maintain fraud monitoring

For customer data:

• Encryption at rest and in transit
• MFA for administrators
• Least-privilege access
• Audit logs
• Data retention/deletion policies
• Regular penetration testing
• Vendor security reviews

For compliance:

• PCI DSS v4.0 alignment
• GDPR/CCPA controls if applicable
• Secure SDLC practices
• Dependency scanning
• Patch SLAs
• Incident response plan

Bottom line

For a company saying “we need strong security and compliance controls”, my default choice would be:

1. Magento Open Source — if this is a serious commerce operation with engineering resources.
2. WooCommerce — if you need faster deployment and can enforce strict operational discipline.
3. Saleor/Medusa — if you are building a custom digital commerce platform and have a strong engineering team.

I would avoid choosing primarily based on license cost; the security program around the platform will matter more than whether the software itself is free. www.digitalapplied.com

For a growing store where ERP integration, warehouse workflows, and shipping-provider connectivity are priorities, the most integration-friendly open-source ecommerce platforms are usually:

blog.openreplay.comwww.shopware.complugins.sylius.com

My shortlist for a growing operation

1. Shopware — probably the best overall balance

For a company expecting to connect:

• ERP (SAP, Dynamics, Odoo, NetSuite, etc.)
• inventory systems
• shipping carriers
• marketplaces
• PIM systems
• custom middleware

Shopware is one of the strongest choices. It was designed around APIs, extensions, and headless use cases, with built-in approaches for connecting ERP/PIM/WMS systems. www.shopware.com

Strengths

• Modern API-first architecture
• Good extension system
• Strong European ERP ecosystem
• Good for B2B and complex catalogs
• Easier long-term maintenance than heavily customized Magento builds

Weakness

• Smaller global ecosystem than Magento/WooCommerce
• Fewer US-focused plugins in some niches

2. Magento Open Source — maximum ecosystem power

Magento remains one of the deepest ecommerce platforms for integrations.

Strengths

• Huge extension marketplace
• Mature APIs
• Handles complex product structures
• Many ERP, tax, shipping, and marketplace connectors
• Proven at enterprise scale

Weakness

• More expensive to operate
• Requires stronger developers
• Customizations can become difficult to maintain

Choose Magento if you have:

• thousands to hundreds of thousands of SKUs
• complex pricing rules
• multiple warehouses
• international operations

3. Sylius — best if you are building a custom commerce platform

Sylius is less of a "turnkey store" and more of an ecommerce framework. It is excellent if your business processes don't fit standard ecommerce models.

Strengths

• API-first
• Built on Symfony
• Very clean architecture
• Excellent for custom ERP-driven businesses

Weakness

• You are building more yourself
• Smaller merchant ecosystem

plugins.sylius.com

4. WooCommerce — easiest integrations, but less enterprise-oriented

WooCommerce wins on sheer availability of plugins.

Strengths

• Massive ecosystem
• Many shipping plugins
• Many accounting/ERP connectors
• Low initial cost

Weakness

• WordPress architecture can become limiting
• Complex inventory/order flows often need custom development

Good for:

• <$5M–10M revenue stores
• simpler fulfillment models
• content-heavy brands

5. Medusa / Saleor — strongest modern API-first options

If you plan a custom frontend (React/Next.js/mobile apps) and want ecommerce as a backend service, these are attractive.

Strengths

• Headless-first
• Developer-friendly
• Clean APIs

Weakness

• Smaller ecosystem of ready-made ERP/shipping connectors than Magento or Shopware

blog.openreplay.com

Integration ranking for your use case

If the priority is ERP + shipping + operational growth, I would rank them:

1. Shopware — best overall balance
2. Magento Open Source — most powerful ecosystem
3. Sylius — best custom enterprise architecture
4. WooCommerce — best low-cost ecosystem
5. Medusa/Saleor — best headless developer experience

A key factor is not just the ecommerce platform, but whether your ERP should be the system of record. For a growing store, the cleaner architecture is usually:

ERP → inventory/pricing/customer data → ecommerce platform → orders → shipping/WMS

rather than making the ecommerce platform the master of everything.

If you share your ERP (e.g., NetSuite, SAP, Odoo, Dynamics, Acumatica, custom), order volume, SKU count, and countries served, the ranking may change.

For a small indie studio, the best setup is usually not a specialized "file delivery" service by itself. It's a combination of:

1. A storefront/payment platform
2. Secure digital delivery
3. License or key management
4. Cloud storage/CDN for large builds

That gives you a much more scalable workflow than emailing download links or hosting files yourself.

Here's how I'd rank the options.

My top recommendation: SendOwl

If you're selling downloadable builds from your own website, SendOwl is one of the strongest choices because it was built specifically for digital products and software. It supports:

• automatic download delivery
• unique Steam/Epic/license key distribution
• expiring download links
• download limits
• PDF and file protection
• large file hosting via CDN
• Stripe and PayPal integration
• customer download history for re-downloads

It's particularly well suited for indie games rather than ebooks or courses. www.sendowldev.comwww.shopify.com

If you're already using Shopify

Use Shopify with a dedicated digital delivery app instead of Shopify's basic download functionality.

Look for features like:

• unique key delivery
• license management
• download throttling
• fraud detection
• private storage (Amazon S3 compatible)
• download analytics

These apps provide much stronger protection than simply attaching files to orders. www.shopify.com

If your builds are huge (20–100+ GB)

I wouldn't store those directly on your web server.

Instead:

• Store builds in Amazon S3, Cloudflare R2, or Backblaze B2.
• Put a CDN in front of them.
• Generate signed URLs that expire after a short period (e.g. 24 hours).
• Let your storefront generate those links only after purchase.

This is faster, cheaper, and more secure than serving downloads from your own VPS.

For game keys

If you sell Steam, Epic, GOG, or your own launcher keys:

• upload a CSV of keys
• automatically assign one per purchase
• keep an audit trail
• revoke unused keys if necessary

This removes the need for manual fulfillment and reduces mistakes. www.vaultn.com

Security features worth paying for

Regardless of platform, I'd prioritize:

• Expiring signed download URLs
• Download limits per purchase
• HTTPS everywhere
• Files stored outside your public web root
• Private cloud storage
• Fraud detection
• License/key validation in-game
• Logging every download
• Automatic re-downloads for legitimate customers

No system can completely stop piracy once someone has the files, but these measures make casual sharing much harder while keeping the experience smooth for paying customers. www.sendowldev.comwww.shopify.com

A stack I'd build today for a small indie studio

If I were starting from scratch, my stack would be:

• Website: Your own marketing site
• Payments: Stripe
• Storefront & fulfillment: SendOwl
• Storage: Cloudflare R2 (or Amazon S3)
• CDN: Cloudflare
• License management: Built-in key delivery or your own activation server
• Analytics: Plausible or Google Analytics

This combination is relatively inexpensive, scales well from a few hundred to tens of thousands of customers, and gives you full control over your customer relationships.

A couple of questions would help narrow the recommendation further:

• Are you selling DRM-free downloadable installers, Steam/Epic keys, or both?
• Roughly how large are your Windows/macOS/Linux builds (e.g. 5 GB, 20 GB, 80 GB+)?

Yes — but there’s an important distinction between “multiple stores” and a true agency/multi-tenant white-label platform.

For an agency selling digital products where each client should get their own storefront + login/admin access, I’d shortlist these:

My strongest candidates

1. Spree Commerce — best if you want to build your own agency platform

Spree Commerce has an explicit multi-tenant architecture: you can run hundreds of independent storefronts from one instance, with each tenant having its own storefront, admin panel, API, products, orders, customers, and configuration. It also supports white-label branding and domain mapping. Spree Commerce

That maps almost exactly to:

Agency → Client A → Store + Admin
Agency → Client B → Store + Admin
Agency → Client C → Store + Admin

You retain the super-admin layer while clients only see their own store.

The downside is that Spree is more of a commerce infrastructure/platform than a turnkey SaaS product. Your team would need to build the agency onboarding, billing, client UI, etc.

2. Cartvero — interesting if you want something purpose-built for agencies

Cartvero explicitly positions itself around agencies: one workspace for all client shops, automated provisioning, reusable themes, isolated client stores, and a white-label admin that clients access under your branding. Cartvero

This is much closer to what I'd investigate if you don't want to build the multi-tenant layer yourselves.

3. LazyCommerce — worth looking at for a broader agency stack

LazyCommerce advertises unlimited client brands, client isolation, white-labeling, and an agency workspace hierarchy where you can create client workspaces and assign permissions. LazyCommerce

What I wouldn't choose: Sellfy

Sellfy is actually quite good for an individual creator selling digital products, but it doesn't fit your agency architecture. Sellfy explicitly says one account can only create one storefront, and it doesn't currently support adding multiple users/staff to an account. Sellfy Help Center

If this were my agency

I'd narrow it to:

• Want turnkey / minimal engineering: Cartvero
• Want a scalable platform you can deeply customize: Spree Commerce
• Want agency workspace + multiple commerce backends: LazyCommerce
• Want maximum ecosystem/apps and don't need true white-labeling: Shopify

The key question is whether you want “our agency manages 50 separate client stores” or “we are essentially creating our own SaaS where clients sign up and receive their own branded digital-product store.”

If it's the second, I can compare Spree vs Shopify Plus vs Medusa vs Saleor vs WooCommerce specifically for building that kind of multi-tenant digital-product SaaS.

Spree Commerce has an explicit multi-tenant architecture: you can run hundreds of independent storefronts from one instance, with each tenant having its own storefront, admin panel, API, products, orders, customers, and configuration. It also supports white-label branding and domain mapping. Spree Commerce

That maps almost exactly to:

Agency → Client A → Store + Admin
Agency → Client B → Store + Admin
Agency → Client C → Store + Admin

You retain the super-admin layer while clients only see their own store.

The downside is that Spree is more of a commerce infrastructure/platform than a turnkey SaaS product. Your team would need to build the agency onboarding, billing, client UI, etc.

2. Cartvero — interesting if you want something purpose-built for agencies

Cartvero explicitly positions itself around agencies: one workspace for all client shops, automated provisioning, reusable themes, isolated client stores, and a white-label admin that clients access under your branding. Cartvero

This is much closer to what I'd investigate if you don't want to build the multi-tenant layer yourselves.

3. LazyCommerce — worth looking at for a broader agency stack

LazyCommerce advertises unlimited client brands, client isolation, white-labeling, and an agency workspace hierarchy where you can create client workspaces and assign permissions. lazycommerce.io

What I wouldn't choose: Sellfy

Sellfy is actually quite good for an individual creator selling digital products, but it doesn't fit your agency architecture. Sellfy explicitly says one account can only create one storefront, and it doesn't currently support adding multiple users/staff to an account.

If this were my agency

I'd narrow it to:

Yes. For a marketplace where multiple creators upload and sell digital products, you want a platform that handles:

• Individual creator/vendor accounts
• Digital product delivery
• Customer checkout
• Marketplace commission
• Creator onboarding/KYC
• Automated payouts to each creator
• Ideally, split payments when one order contains products from multiple creators

Best options

My top recommendation: Sharetribe + Stripe Connect. Sharetribe is specifically designed for marketplaces: creators can have their own accounts, add payout information through Stripe Connect, and you can take a commission while Stripe automatically transfers the creator's share. It also supports delayed payouts. Sharetribe Sharetribe

For a digital-goods-only marketplace, though, I'd distinguish between two approaches:

• Want to launch quickly/no-code: Sharetribe + Stripe Connect.
• Want something like a serious Gumroad/Creative Market-style platform: Medusa/Mercur + Stripe Connect. Medusa's marketplace tooling supports vendor dashboards, vendor earnings, automated Stripe Connect payouts, and splitting an order/payment between multiple vendors. Medusa
• Want to build the marketplace yourself: Stripe Connect is the underlying payment infrastructure I'd consider. It supports onboarding sellers, collecting your platform fee, splitting/routing funds, and controlling payout timing. Stripe Stripe

One caveat: Lemon Squeezy's Marketplace is specifically for digital products and handles payouts, but its marketplace model is more of a curated marketplace than a general-purpose multi-vendor platform; marketplace sales currently carry a flat 30% marketplace fee. Lemon Squeezy Docs

If you tell me whether you're building this as no-code, Shopify, WordPress, or a custom SaaS, I can narrow it down to the 2–3 platforms that fit best, including fees and payout mechanics.

If you're a complete beginner with no technical/developer skills, I'd narrow it down to Payhip vs. Gumroad.

My pick: Payhip

For selling ebooks, PDFs, workbooks, templates, checklists, printables, and other downloads, I’d start with Payhip.

Why:

• Very beginner-friendly — upload your file, add a description and price, and you have a storefront.
• No coding or website required.
• Free to start — its free plan takes 5% per sale, plus payment-processing fees. Paid plans reduce the platform fee as your sales grow. www.biztoolkit.cowhatipocket.com
• It automatically delivers the ebook/download after purchase.
• You can sell multiple types of digital products, rather than being limited to ebooks.
• You can add coupons, affiliates, bundles, and other useful selling features as you grow. www.biztoolkit.coheresthebest.com

Visit Payhip

The alternatives

Gumroad is arguably the simplest and has some built-in product discovery, but its current direct-sale fee is substantially higher than Payhip's free plan. www.biztoolkit.cowhatipocket.com

Visit Gumroad

Lemon Squeezy is particularly attractive if you expect lots of international customers and want Merchant-of-Record tax handling, but I'd consider it a little more sophisticated than necessary for your first ebook. heresthebest.com

Visit Lemon Squeezy

What I'd do in your shoes

I'd start with Payhip rather than building a website.

Your setup could literally be:

Canva/Word → create ebook → export PDF → Payhip → upload PDF → set price → share your product link

You can then sell things like:

• 📕 Ebooks
• 📄 Guides
• 📋 Checklists
• 📚 Workbooks
• 🎨 Canva templates
• 📊 Spreadsheets
• 🖨️ Printables
• 📦 Bundles of several downloads

And importantly, you don't need to learn web development first.

If you tell me roughly what kind of ebooks/digital products you want to sell and your expected price (e.g. $7, $19, $49), I can tell you whether Payhip, Gumroad, Etsy, or another platform makes the most sense for your particular business.

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

1. Gumroad — probably your best fit

Gumroad explicitly supports “pay what you want” products: you can set a minimum price, let the buyer enter a higher amount, and even set a suggested price. Setting the minimum to $0 allows completely free downloads with an optional payment. gumroad.com

So you could do:

Digital Zine #12
$0 minimum — suggested $5
“Pay what you want”

It also handles digital delivery and is designed for things like ebooks and music, so you can put zines, albums, PDFs, MP3s, bundles, etc. in the same storefront. gumroad.com

The main downside is the transaction fee: currently 10% + $0.50 on sales through your profile/direct links, with no monthly fee. gumroad.com

2. Bandcamp — particularly compelling for the music side

Bandcamp lets artists set a minimum price and allow fans to pay more if they want. It also supports giving music away while allowing fans to support you. bandcamp.com

This is especially attractive if music is a major part of the project because Bandcamp gives you a music-native storefront, streaming, downloads, fan accounts, collections, discovery, etc.

Its current digital-music revenue share is 15%, plus payment-processing fees. bandcamp.com

So I'd choose Bandcamp if your model is essentially:

music label / artist → albums + tracks → fans choose what to pay

rather than:

publisher/collective → zines + PDFs + music + assorted digital works.

3. itch.io — surprisingly good for zines

itch.io's pricing model is almost tailor-made for this. You can set a $0 minimum, in which case someone can download for free but is prompted to donate; alternatively, set a minimum and let people pay more. gumroad.comitch.ioitch.io

It also lets you choose your own revenue share with itch.io, from 0% upward, rather than imposing a fixed platform percentage. itch.io

Although it's famous for games, it supports arbitrary downloadable files, so it's quite suitable for independent/experimental zines, art publications, music, PDFs, and bundles.

What I'd do

If you're building one storefront for a creative publishing project, I'd start with Gumroad:

• Zine: $0+, suggested $5
• Album: $5+, suggested $10
• Individual tracks: $1+
• Special edition/bundle: $10+
• Everything can live under the same storefront
• Link directly to each product from your own website/socials

If the music community/discovery aspect is important, I'd use Bandcamp for the music and Gumroad for the zines.

If the project has a particularly indie/DIY/art-publication/game-adjacent identity, I'd seriously consider itch.io—it has unusually good native support for the “free if you need it, pay if you can” philosophy. itch.ioitch.io

One important distinction: if by “optional donations” you mean “buy the zine for $5, then optionally add another $10 donation at checkout”, that's a slightly different requirement than PWYW. Gumroad's native PWYW handles the latter very well, but I'd evaluate the checkout experience separately if you specifically want purchase price + separate donation field.

If you tell me whether you're a single artist, a zine publisher/collective, or a nonprofit, I can narrow this down to the best 2–3 options based on fees, taxes, customer data, storefront customization, and donation mechanics.

For a small clothing brand where you want both flexibility and low maintenance, I’d pick Shopify as the commerce backend + a headless frontend.

My recommendation: Shopify

Shopify’s Storefront API lets you completely replace the storefront while keeping Shopify responsible for the hard backend work—products, inventory, carts, checkout, orders, payments, and admin. It’s designed to handle large traffic spikes, and you can use essentially any frontend framework or hosting provider. Shopify Shopify

A sensible setup would be:

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

Or, if you want the most integrated option:

Hydrogen → Shopify → Oxygen

Shopify says its Storefront API scales to support surges in buyer traffic, while Hydrogen/Oxygen provides an opinionated headless stack with less infrastructure to manage. Shopify Shopify

How I'd rank your options

Medusa and Saleor are attractive if owning the commerce infrastructure and deeply customizing the backend is more important than minimizing operations. Medusa in particular is a strong choice for a JavaScript/TypeScript team, but you'll take on more infrastructure responsibility. OSSAlt OSSAlt

Bottom line: don't self-host your commerce backend just to get "headless." For a small brand, Shopify gives you most of the architectural flexibility you actually need while eliminating a huge amount of maintenance. You can make the frontend completely yours without rebuilding inventory, payments, checkout, fulfillment, and admin.

shopify.dev

If you tell me your frontend stack (Next.js, Shopify Hydrogen, etc.), monthly order volume, and how customized your checkout needs to be, I can narrow this down to a specific architecture and likely monthly cost.

If speed to launch is the #1 constraint, I’d narrow it to Shopify Hydrogen and BigCommerce Catalyst rather than starting with a fully custom composable stack.

My ranking for a mid-size retailer

My default choice: Shopify Hydrogen if your commerce backend is already Shopify. Shopify positions Hydrogen/Oxygen specifically as its recommended headless stack, with prebuilt commerce components, CLI tooling, and integrated deployment. Hydrogen Shopify

hydrogen.shopify.dev

BigCommerce Catalyst is probably the strongest alternative if you're on BigCommerce or want a more explicitly composable mid-market setup. Catalyst gives you a working Next.js/React storefront, GraphQL API client, product/search/cart functionality, and hosted checkout rather than making your team assemble those pieces. BigCommerce BigCommerce

catalyst.dev

What I'd do under a tight deadline

Don't build "headless architecture" as a technology project. Build a thin vertical slice:

1. Catalog → PDP → cart → checkout
2. Search/category pages
3. CMS/content
4. Analytics and critical integrations
5. Only then migrate the remaining experience

For a mid-size retailer, I'd specifically avoid starting with commercetools + a separate CMS + search + personalization + custom checkout unless you have requirements that genuinely demand it. The integration surface can eat your schedule.

If you tell me your current commerce platform, CMS, ERP/PIM, and target launch timeframe (e.g. 8 weeks vs. 6 months), I can give you a much more concrete recommendation and a proposed stack.

BigCommerce Catalyst is probably the strongest alternative if you're on BigCommerce or want a more explicitly composable mid-market setup. Catalyst gives you a working Next.js/React storefront, GraphQL API client, product/search/cart functionality, and hosted checkout rather than making your team assemble those pieces.

For a startup with limited funding, I’d put Medusa at the top of the list—especially if you have a capable JavaScript/TypeScript developer or agency.

My ranking

🥇 Best overall: Medusa

medusajs.com is particularly attractive because its commerce engine is open source, there are no GMV/platform fees, and its managed Cloud starts at $29/month, with a production-oriented Launch tier starting at $99/month. Medusa Medusa Docs

You get a surprisingly complete foundation: products, orders, customers, sales channels, regions/currencies, promotions, payments, fulfillment, and a modular architecture that you can customize rather than fighting against. Medusa's current Cloud pricing explicitly lists unlimited products, orders, sales channels, regions and currencies without additional commerce-feature fees. Medusa Docs

Why I'd choose it for a funded-but-budget-conscious startup:

• Very low initial software cost.
• You retain considerable control over the backend.
• Excellent fit with a Next.js/React storefront.
• No percentage-of-GMV platform fee.
• You can start on inexpensive infrastructure and scale later.
• Custom business logic is much easier than on traditional SaaS platforms.

The catch is that you are taking on more engineering responsibility than with Shopify.

🥈 Shopify + Hydrogen if engineering resources are scarce

If "limited funding" also means limited developer time, I'd actually choose Shopify.

Shopify gives you the mature commerce backend, checkout, payments, inventory, apps, and operational tooling, while Hydrogen lets you build a custom headless storefront. The tradeoff is recurring Shopify cost and less control over the underlying commerce engine.

So I'd use this rule:

Limited money + strong developers → Medusa.
Limited money + limited developers → Shopify.

🥉 Saleor if you already know you'll need sophisticated commerce

saleor.io is technically excellent, particularly for GraphQL-first development, international commerce, B2B, and complex catalogs. But its managed Cloud is dramatically more expensive: the current Select tier starts at $1,599/month, while the higher-volume tier starts at $3,999/month. Saleor Commerce

That's hard to justify for a cash-constrained startup unless Saleor's capabilities directly solve an important requirement.

What I'd actually do

For a typical startup launching a new DTC brand, I'd build:

Next.js storefront → Medusa → PostgreSQL → Stripe → managed hosting/CDN

Start around the lowest practical infrastructure cost, validate product-market fit, and only introduce more specialized infrastructure as traffic and requirements justify it.

One important caveat: headless itself costs engineering money. A 2026 comparison estimates headless implementations commonly have substantially higher development costs than conventional Shopify/WooCommerce setups. Teamz Lab If your storefront doesn't genuinely need a highly customized experience, a conventional Shopify store can be the financially smarter startup choice.

Bottom line: Medusa gives you the best cost/features balance for a technically capable startup; Shopify gives you the best cost/time-to-market balance.

If your primary requirement is a custom mobile app frontend—iOS/Android built in React Native, Flutter, Swift/Kotlin, etc.—I’d prioritize API quality, checkout flexibility, authentication, webhooks, SDKs, and how much of the commerce backend you need to customize rather than how good the platform’s web storefront is.

My ranking

🥇 My default choice: Medusa

For a new custom mobile app, I'd probably choose Medusa unless you have enterprise-scale requirements.

Medusa is particularly attractive because it's a headless, Node.js/TypeScript commerce engine. Your mobile app can consume the commerce APIs directly rather than going through a web storefront. Its modular architecture also gives you substantially more control over things like pricing, promotions, fulfillment, payments, and custom business logic. PowerGate Software WPBundle

A typical architecture would look like:

iOS / Android App
   │
   │ HTTPS / API
   ▼
Your API / BFF
   │
   ├── Medusa
   ├── Payment provider
   ├── Search
   ├── CMS
   ├── Notifications
   └── Analytics

That is a very natural architecture if the app is going to become a major product experience rather than simply a mobile version of a website.

🏢 When I'd choose commercetools instead

If you're building for a large organization with:

• multiple countries/currencies
• complex pricing
• B2B accounts
• multiple brands/channels
• sophisticated inventory/fulfillment
• multiple frontends beyond the app
• a dedicated commerce engineering team

I'd strongly consider commercetools.

It's API-first and was designed specifically for headless/composable commerce, making it an excellent foundation for mobile, web, kiosks, marketplaces, etc. Commercetools

The downside is that you're buying into a much more sophisticated architecture—and corresponding cost and engineering overhead.

🧩 When I'd choose Saleor

Saleor is probably my second choice for a technically sophisticated custom app.

It's GraphQL-first and particularly strong if you need multi-channel, multi-warehouse, multi-currency, or B2B functionality. Vendure WPBundle

I'd favor it over Medusa if your team is comfortable with Python/Django and you specifically want a GraphQL-native commerce API.

🛍️ When I'd choose Shopify

Don't discount Shopify.

If the business already uses Shopify, or the priority is getting the app launched quickly while minimizing backend operations, Shopify's Storefront API is an extremely pragmatic choice. You can keep Shopify handling products, orders, payments, customers, etc., while your mobile app is completely custom. Vendure Pharos Production

The tradeoff is that you're accepting Shopify's underlying commerce model. If you eventually need radically custom checkout, pricing, order orchestration, or marketplace logic, an API-first commerce engine such as Medusa or commercetools gives you more freedom.

My decision rule

I'd make the choice roughly like this:

• Startup / new product / TypeScript team → Medusa
• Enterprise / complex global commerce → commercetools
• GraphQL + B2B + multi-channel → Saleor
• Already on Shopify / fastest path to market → Shopify
• Managed SaaS but more headless openness → BigCommerce
• TypeScript + highly customizable backend → Vendure

For a React Native or Flutter app specifically, my personal shortlist would be Medusa vs. Saleor vs. commercetools, with Shopify entering the shortlist if operational simplicity is more important than backend control.

If you tell me (1) B2C vs B2B, (2) approximate SKU count, (3) expected order volume, (4) whether you need subscriptions, and (5) React Native/Flutter/native, I can narrow this to the best 1–2 choices and lay out the recommended mobile architecture.

It's GraphQL-first and particularly strong if you need multi-channel, multi-warehouse, multi-currency, or B2B functionality. Vendure WPBundle

I'd favor it over Medusa if your team is comfortable with Python/Django and you specifically want a GraphQL-native commerce API.

🛍️ When I'd choose Shopify

Don't discount Shopify.

If the business already uses Shopify, or the priority is getting the app launched quickly while minimizing backend operations, Shopify's Storefront API is an extremely pragmatic choice. You can keep Shopify handling products, orders, payments, customers, etc., while your mobile app is completely custom.

The tradeoff is that you're accepting Shopify's underlying commerce model. If you eventually need radically custom checkout, pricing, order orchestration, or marketplace logic, an API-first commerce engine such as Medusa or commercetools gives you more freedom.

My decision rule

I'd make the choice roughly like this:

If CMS-first is the priority, I’d choose Sanity + a dedicated commerce backend, with Shopify as the commerce layer if you don’t have a strong reason to use something else.

My recommendation: Sanity + Shopify + Next.js/Hydrogen

Think of the architecture as:

Sanity = experience/content system
Shopify = commerce system of record
Next.js/Hydrogen = storefront

Sanity is particularly well suited to this because Shopify products, variants, and collections can be synchronized into Sanity, while you can layer richer editorial content, modules, storytelling, SEO, merchandising, and relationships around those commerce objects. Sanity.io Sanity.io

Your PDP would conceptually be:

/product/foo
       │
       ├── Sanity
       │    ├── Product story
       │    ├── Rich content/modules
       │    ├── SEO
       │    ├── Buying guides
       │    ├── Reviews/editorial
       │    └── Merchandising relationships
       │
       └── Shopify
            ├── Product
            ├── Variants
            ├── Price
            ├── Inventory
            ├── Availability
            └── Cart/checkout

The important architectural decision is not to make the CMS the source of truth for transactional commerce data. Let Shopify own price, inventory, variants, carts, orders, etc.; let Sanity own the experience around the product. Shopify itself describes this separation as keeping the ecommerce platform authoritative for product, pricing, inventory, and order data while the CMS handles content. Shopify

Why I'd pick Sanity

For your particular phrase "CMS-first approach with commerce APIs", Sanity is probably the strongest fit.

• Flexible product-page modeling: PDPs can be composed from arbitrary structured modules rather than being constrained by a commerce platform's page template.
• Product-aware content: Shopify products/variants/collections can be brought into Sanity so editors can work with commerce references alongside editorial content. Sanity.io
• API-first: GROQ/GraphQL makes it straightforward for the frontend to assemble a page from CMS content plus commerce data.
• Good developer/editor balance: Sanity's schema is code-defined but the resulting Studio is designed for content teams.
• Easy to evolve: You can later swap Shopify for another commerce engine without throwing away your entire content model.

The other serious contender: Contentful

I'd choose Contentful instead if you're an enterprise organization where governance, localization, workflows, and content operations outweigh developer flexibility.

Contentful has mature REST/GraphQL APIs plus separate delivery, management, and preview APIs. Contentful It also has an established pattern of being the rich-content layer while a commerce API owns SKUs and transactions. Contentful

So I'd roughly rank them:

What I would avoid

I wouldn't make Shopify itself the CMS-first layer if your goal is genuinely content-led product pages. Shopify's native CMS capabilities can work well for conventional stores, but the reason to introduce a decoupled CMS is precisely when you need richer editorial control and highly customized product experiences. Shopify

Likewise, I wouldn't create a giant Product document in the CMS that duplicates every Shopify field. Instead, model something like:

ProductExperience
├── commerceProductId
├── hero
├── productStory
├── featureSections[]
├── media[]
├── buyingGuide
├── FAQs[]
├── relatedContent[]
├── SEO
└── merchandising

Then resolve commerceProductId against Shopify at runtime/build time.

Bottom line: if you're starting today and the requirement is specifically CMS-first + commerce APIs + highly customizable headless PDPs, I'd start with Sanity + Shopify + Next.js/Hydrogen. Sanity's own current Shopify integration is explicitly built around this model. Sanity.io Sanity.io

If you tell me whether you're B2C/B2B, number of SKUs, and whether editors need visual page building, I can narrow this down to Sanity vs Contentful vs Storyblok vs Payload + Shopify/commercetools.

If your priority is developer experience + SDK quality + modern frontend frameworks, my pick in 2026 is Shopify’s headless stack, with Medusa as the best choice if you want maximum backend control.

The interesting part is that Shopify has changed the equation recently: its new Hydrogen developer preview is moving from an opinionated React framework toward a framework-agnostic commerce SDK/toolkit. It supports Next.js, SvelteKit, Nuxt, SolidStart, React Router, and other JavaScript frameworks/runtimes. Hydrogen Shopify

My ranking for frontend developers

🥇 Shopify Hydrogen — best overall

If I were starting a new project where frontend developer productivity was the primary criterion, I'd choose Shopify.

The new Hydrogen toolkit provides a typed Storefront API client, cart/product/collection primitives, Shop Pay integration, analytics, server-driven cart handling, and framework bindings. Crucially, Shopify now explicitly supports using it with Next.js, SvelteKit, Nuxt, SolidStart, and React Router, rather than forcing you into one frontend framework. Shopify

That's a significant advantage over traditional "headless" platforms where you're essentially given an API and expected to build the commerce plumbing yourself.

You can also use Shopify's Storefront API without Hydrogen if you want a completely custom architecture. Shopify

Best for: Next.js/React teams, DTC brands, teams wanting managed infrastructure, fast implementation.

Big caveat: You're still building on Shopify's commerce model. If your business logic fundamentally doesn't fit Shopify, the excellent frontend tooling won't solve that.

🥈 Medusa — best for developers who want ownership

Medusa is probably my favorite alternative for a team that says:

"We want commerce infrastructure, not a SaaS platform telling us how commerce works."

It's TypeScript/Node-based, modular, open source, and designed to let you customize the backend extensively. That makes it particularly attractive if your frontend is Next.js and you want your commerce code to live in the same general JavaScript/TypeScript ecosystem. Ribbsaeter Systems ZORC

The tradeoff is that you own more of the system—deployment, infrastructure, upgrades, and operational concerns.

Best for: Next.js + TypeScript teams, custom checkout/business logic, marketplaces, unusual commerce models.

🥉 Saleor — best API architecture

Saleor is extremely compelling if your frontend team loves GraphQL.

Its API is GraphQL-first, and its documentation has strong API references, tutorials, extensions, dashboard apps, and recipes for multi-region commerce, marketplaces, custom shipping, etc. Saleor Documentation

The main downside compared with Medusa is the backend ecosystem: Saleor is Python/Django, so a TypeScript-heavy frontend organization has to cross that boundary. Hunchbite

Best for: GraphQL-heavy teams, international/multi-channel commerce, sophisticated catalog models.

Enterprise: commercetools

commercetools is the one I'd put ahead of the others for a large enterprise composable architecture.

Its SDK/API ecosystem is mature, and its frontend tooling includes an SDK designed for SSR/Next.js applications. commercetools Documentation

But it's a different proposition from Medusa or Shopify. You're buying into a much more elaborate composable-commerce architecture, which makes sense when you have the organizational complexity to justify it—not necessarily for a startup or small frontend team.

So, what would I choose?

For a modern Next.js/React storefront:

1. Shopify Hydrogen — best developer experience and lowest plumbing burden.
2. Medusa — best if backend ownership/customization matters.
3. Saleor — best if GraphQL is central to your architecture.
4. commercetools — best for large enterprise composable commerce.
5. Vendure — worth serious consideration if you want a TypeScript/NestJS-centric stack.

The particularly interesting choice right now is Shopify. Its 2026 Hydrogen developer preview essentially acknowledges that modern frontend teams don't necessarily want an ecommerce-specific framework: Shopify is turning Hydrogen into commerce primitives + SDK + tooling that can sit inside the framework you already use. Hydrogen Shopify

So if your stack is Next.js + TypeScript + Tailwind + Vercel, I'd lean Shopify Hydrogen/Storefront API unless you have a strong reason to own the commerce backend. If you're building something where the commerce model itself is highly customized, I'd choose Medusa instead.

If I were starting a new project where frontend developer productivity was the primary criterion, I'd choose Shopify.

The new Hydrogen toolkit provides a typed Storefront API client, cart/product/collection primitives, Shop Pay integration, analytics, server-driven cart handling, and framework bindings. Crucially, Shopify now explicitly supports using it with Next.js, SvelteKit, Nuxt, SolidStart, and React Router, rather than forcing you into one frontend framework. Shopify

That's a significant advantage over traditional "headless" platforms where you're essentially given an API and expected to build the commerce plumbing yourself.

You can also use Shopify's Storefront API without Hydrogen if you want a completely custom architecture. Shopify

Best for: Next.js/React teams, DTC brands, teams wanting managed infrastructure, fast implementation.

Big caveat: You're still building on Shopify's commerce model. If your business logic fundamentally doesn't fit Shopify, the excellent frontend tooling won't solve that.

🥈 Medusa — best for developers who want ownership

Medusa is probably my favorite alternative for a team that says:

"We want commerce infrastructure, not a SaaS platform telling us how commerce works."

It's TypeScript/Node-based, modular, open source, and designed to let you customize the backend extensively. That makes it particularly attractive if your frontend is Next.js and you want your commerce code to live in the same general JavaScript/TypeScript ecosystem. Ribbsaeter Systems ZORC

The tradeoff is that you own more of the system—deployment, infrastructure, upgrades, and operational concerns.

Best for: Next.js + TypeScript teams, custom checkout/business logic, marketplaces, unusual commerce models.

🥉 Saleor — best API architecture

Saleor is extremely compelling if your frontend team loves GraphQL.

Its API is GraphQL-first, and its documentation has strong API references, tutorials, extensions, dashboard apps, and recipes for multi-region commerce, marketplaces, custom shipping, etc. Saleor Documentation

The main downside compared with Medusa is the backend ecosystem: Saleor is Python/Django, so a TypeScript-heavy frontend organization has to cross that boundary. Hunchbite

Best for: GraphQL-heavy teams, international/multi-channel commerce, sophisticated catalog models.

Enterprise: commercetools

commercetools is the one I'd put ahead of the others for a large enterprise composable architecture.

Its SDK/API ecosystem is mature, and its frontend tooling includes an SDK designed for SSR/Next.js applications. docs.commercetools.com

But it's a different proposition from Medusa or Shopify. You're buying into a much more elaborate composable-commerce architecture, which makes sense when you have the organizational complexity to justify it—not necessarily for a startup or small frontend team.

So, what would I choose?

For a modern Next.js/React storefront:

For a high-volume dropshipping business with multiple warehouses, my top choice is Shopify Plus, but there’s an important caveat: at your scale, the ecommerce platform should be the storefront/order hub, while a dedicated OMS/WMS/ERP handles complex warehouse and supplier operations.

My ranking

🥇 Shopify Plus

Shopify currently supports inventory allocation across up to 1,000 warehouses, fulfillment centers, and stores, along with purchase orders, inventory transfers, bulk inventory management, and inventory automation. www.shopify.com

For a dropshipping operation, the big advantage is the ecosystem. You can connect supplier feeds, fulfillment providers, marketplaces, 3PLs, shipping systems, and an external inventory/OMS layer without having to build everything yourself. Shopify Plus also provides centralized management across locations. www.shopify.com

Shopify Plus

🥈 BigCommerce Enterprise

I'd seriously consider BigCommerce Enterprise if you have a complicated catalog, lots of custom integrations, multiple storefronts, or want more API/control flexibility.

BigCommerce has location-aware inventory APIs that can track inventory across multiple locations and support multi-location fulfillment. It also centralizes orders and inventory across channels. www.shopify.comwww.bigcommerce.com

One limitation to be aware of: its standard plans have relatively low native location limits, while Enterprise supports 100 locations with customization available. docs.bigcommerce.com

BigCommerce Enterprise

🥉 Adobe Commerce

Adobe Commerce becomes attractive if you're talking about very large enterprise scale, extremely complex fulfillment rules, custom pricing/catalogs, or an in-house engineering/IT team. It's much more customizable, but also substantially more complicated to implement and maintain.

What I'd actually build

For a serious dropshipping operation, I'd use:

Shopify Plus → OMS/Inventory system → multiple warehouses/3PLs → suppliers

Rather than trying to make Shopify itself do everything.

The critical capabilities I'd prioritize are:

• Real-time inventory synchronization between warehouses
• Automatic order routing to the optimal warehouse
• Supplier inventory feeds/API synchronization
• Oversell prevention
• Purchase-order/replenishment automation
• Split-order fulfillment
• Tracking-number synchronization
• Returns/refunds synchronization
• Marketplace integration
• Bulk SKU/product management
• Webhooks/API access
• Centralized order management
• Inventory forecasting and safety stock

Bottom line: If you're choosing one platform today, I'd pick Shopify Plus for most high-volume dropshipping businesses. If your operation is unusually complex and API/integration flexibility is more important than ease of use, BigCommerce Enterprise is probably the better alternative.

If you tell me roughly monthly order volume, number of SKUs, number of warehouses, sales channels (Shopify/Amazon/eBay/TikTok/etc.), and whether the warehouses are yours or 3PLs, I can narrow this down to the best Shopify Plus vs BigCommerce vs dedicated OMS/WMS stack for your specific operation.

For a complete beginner testing a niche dropshipping product, I’d choose a fully hosted cart with the fastest path from idea → live store → first sale. My recommendation:

1. Shopify — best default choice

Setup time: a few hours to a weekend
Best for: testing one-product or small niche stores

Why it fits your situation:

• Hosting, security, checkout, and updates are handled for you.
• Huge ecosystem of dropshipping integrations and themes.
• You can launch without touching code.
• It’s easy to shut down, change products, or pivot if the idea fails. www.itechguides.comwww.doba.com

Typical beginner stack:

• Shopify store
• Free/low-cost theme
• One product page
• Payment processor
• Supplier integration app (depending on supplier)
• Basic analytics

The downside:

• Monthly subscription cost
• Apps can add up if you install too many
• You’re trading some control for speed

For a validation experiment, that tradeoff is usually worth it. remery.aiwww.doba.com

2. BigCommerce — good, but probably not your first choice

Setup time: fast, but slightly more “store management” oriented

Better if:

• You expect a large catalog
• You want more built-in ecommerce features
• You are planning a more traditional retail operation

For a single niche product test, it may feel heavier than necessary. www.itechguides.com

3. WooCommerce — avoid initially

Setup time: potentially days or weeks

WooCommerce is powerful, but you manage:

• Hosting
• WordPress setup
• Plugins
• Security updates
• Compatibility issues

It’s excellent for people who want control, but it adds friction when your main question is: “Will anyone buy this product?” www.itechguides.com

My suggested beginner path

Week 1:

1. Pick one niche product.
2. Build a simple Shopify store.
3. Spend more time on:
   • product research
   • offer positioning
   • product photos/videos
   • customer problem solved

4. Avoid:
   • custom logos
   • expensive themes
   • dozens of apps
   • huge catalogs

A common beginner mistake is spending two weeks making the store “perfect” before knowing whether the product has demand.

Short answer: Start with Shopify. It minimizes setup time and lets you focus on the part that actually determines success: finding and marketing a product people want. remery.aiwww.doba.com

If you want, I can also give you a minimal-cost dropshipping test setup (store + apps + estimated monthly cost) for a first product.

For a dropshipping MVP where the priority is speed of prototyping + rapid iteration, I’d pick Shopify.

My ranking

1. Shopify — best overall for an MVP

• Fastest path from zero → functioning store.
• Hosting, checkout, payments, product catalog, orders, etc. are already handled.
• Huge app ecosystem for sourcing/fulfillment. Shopify currently lists hundreds of dropshipping apps, including DSers, CJdropshipping, EPROLO, and others. Shopify App Store Shopify App Store
• Easy to throw together a storefront, test the client's hypothesis, then swap themes/apps/workflows without rebuilding the backend.
• Particularly good if you're being paid to validate the business, rather than engineer an ecommerce platform.

shopify.com

2. WooCommerce — best if customization is the MVP

• More control over the underlying site and data.
• Excellent if the client already has WordPress or expects unusual business logic.
• But you'll be managing WordPress, hosting, plugins, updates, integrations, etc. WooCommerce's own dropshipping tooling involves configuring suppliers, notifications, packing slips, and fulfillment workflows. WooCommerce
• That flexibility generally means more engineering friction during an MVP.

woocommerce.com

3. Custom stack (Next.js/etc.) — I'd avoid for the first version

• Makes sense once you've proven demand and have requirements Shopify can't comfortably satisfy.
• For an MVP, you'll spend time rebuilding things Shopify already gives you: checkout, orders, payments, admin, inventory concepts, customer accounts, etc.

What I'd actually build

For a freelancer trying to deliver quickly, I'd do:

Shopify + lightweight custom theme + one sourcing/fulfillment app + minimal custom code.

Keep the architecture intentionally boring:

Shopify storefront → Shopify checkout → Shopify orders → dropshipping app → supplier

Then put your engineering effort into the things that actually differentiate the client's MVP: product presentation, conversion flow, custom UX, analytics, and whatever unique workflow they're testing.

The big advantage is that if the client says "change the pricing model," "add 50 products," "try a different supplier," "change the homepage," or "let's test another niche" next week, you're modifying configuration/apps/theme code rather than rebuilding infrastructure.

If you tell me what kind of dropshipping MVP it is (AliExpress-style, print-on-demand, local suppliers, marketplace, subscription box, etc.), I can recommend the exact Shopify stack I'd use and what I'd custom-build vs. leave to apps.

For a subscription-focused dropshipping store, I’d use Shopify as the core platform and layer subscription + supplier automation on top.

My recommended stack

Shopify is particularly attractive because subscriptions are built into its commerce architecture: recurring purchases create subscription contracts and generate new orders at renewal. shopify.dev

For suppliers, Shopify's current ecosystem supports automated inventory syncing and order routing. For example, Syncee can synchronize supplier inventory and send orders to suppliers for fulfillment, while Shopify Collective can route orders directly to participating suppliers. www.shopify.comshopify.dev

Which subscription app?

Start with Shopify Subscriptions if you're selling something straightforward like:

“Get this product every 30 days and save 10%.”

It's native, integrates with Shopify Payments, and is probably the lowest-complexity option. www.shopify.com

I'd move to Appstle or Recharge if you need things like:

• Skip/pause subscription
• Change delivery frequency
• Swap products
• Subscription bundles
• Multiple subscription plans
• More sophisticated retention/churn tools

The important part for dropshipping

Don't choose your supplier solely based on product price. For subscriptions, you need a supplier that can reliably support repeated fulfillment.

Your ideal workflow is:

Customer subscribes → Shopify bills them → new order generated → supplier receives order automatically → supplier ships → tracking returns to Shopify → customer receives next shipment.

Shopify's subscription architecture supports this recurring-order model, while dropshipping integrations can handle the supplier/inventory side. www.shopify.comshopify.dev

If I were starting today:
Shopify + Appstle + Syncee/Spocket would be my default stack. It gives you a relatively simple setup while leaving room to scale to multiple suppliers.

If you tell me what type of product you're planning to sell (supplements, beauty, pet products, coffee, household consumables, etc.), I can recommend the specific platform + supplier setup I'd use for that niche.

For a small POD dropshipping team, I’d generally recommend Shopify + a dedicated product-personalization app + Printful/Printify, rather than trying to make the store builder itself handle every customization function.

My ranking

🥇 I'd choose Shopify

The key advantage isn't Shopify's native product options—it is the ecosystem of personalization tools you can layer onto it.

For example, Printful itself says its Shopify personalization workflow doesn't provide the customer-facing personalization input, and recommends using a third-party tool such as Zepto Product Personalizer. help.printful.com

That gives you a setup like:

Shopify → personalization/preview app → Printful/Printify → automated fulfillment

You can give customers things like:

• Enter their name
• Choose fonts
• Choose colors
• Upload an image
• Add multiple text fields
• Select icons/graphics
• See the personalization on the product
• Generate a visual preview before checkout
• Conditional options ("If you choose this style, show these fields")
• Charge extra for certain personalization options

The big thing I'd look for is true live rendering, not merely a form that collects "Name: John." For a POD business, the customer should ideally see something close to "this is exactly what my mug/shirt/ornament will look like."

One caveat: third-party Shopify personalization apps can introduce fulfillment/sync complications. Printful specifically warns that apps which alter product variants may not always synchronize cleanly with Printful, so I'd test the complete workflow with sample orders before launching. help.printful.com

🥈 Wix is surprisingly attractive

If your team isn't particularly technical, I'd seriously consider Wix.

Wix already has product options, modifiers, text boxes, swatches, conditional-style customization through apps, and the ability to associate different media with product choices. support.wix.com

It also has built-in POD functionality and integrations, including automatic fulfillment through POD suppliers. www.wix.com

So if your products are relatively straightforward—e.g.:

Pick color → enter name → choose font → see a few product images → order

Wix can be a very clean solution.

🥉 WooCommerce if customization is the core of your business

I'd pick WooCommerce if you're planning something more sophisticated, such as:

Upload photo → automatically remove background → position/resize it → add text → choose 15 design elements → dynamically render the final artwork → generate production-ready file → send to POD supplier.

WooCommerce gives you enormous flexibility, but that flexibility comes with more maintenance. For a small team trying to sell rather than maintain software, I'd only choose it if you have someone comfortable with WordPress/WooCommerce development.

The distinction I'd make

There are actually three different things people call "custom product previews":

1. Variant preview
Customer chooses black vs. white → product image changes.

2. Personalization preview
Customer enters Sarah → the product image updates to show Sarah.

3. Full product designer
Customer uploads an image, moves it around, changes fonts/colors, adds artwork, etc., and sees a near-final rendering.

If you're after #2 or #3, I'd strongly favor Shopify.

If you're mainly doing #1, Wix can be more than sufficient. Wix officially supports linking different images/videos to product option choices, which makes basic visual variant selection straightforward. support.wix.com

What I'd build for your team

If I were setting this up today, my default stack would be:

Shopify
↓
Product personalization/preview app
↓
Printful or Printify
↓
Automated fulfillment + tracking

And I'd make one rule for the team:

Don't choose the store builder first. Choose the personalization technology first, then make sure it integrates cleanly with your POD provider.

That's because the preview/personalization experience is likely to be the thing that differentiates your store, whereas Shopify/Wix are mostly infrastructure.

If you tell me what kinds of products you're selling (shirts, mugs, wall art, jewelry, phone cases, etc.) and whether customers will upload photos, enter text, choose designs, or all three, I can narrow this down to the best 2–3 exact stacks/apps for your use case.

If your priority is “I want to own the code and build my own dropshipping integrations”, I’d strongly favor a headless open-source commerce engine rather than something like Shopify.

My shortlist for 2026:

1. 🥇 Medusa — my first choice

Medusa official site

For the specific business you're describing, Medusa is probably where I'd start.

It's designed as a headless commerce backend, so you can build your own frontend and treat the commerce engine as your underlying system. Its modular architecture is particularly attractive when you're going to replace or extend things like fulfillment, payments, shipping, pricing, and inventory. www.wpbundle.com

For dropshipping, I'd structure it roughly like:

                 YOUR STOREFRONT
                    Next.js
                       │
                       ▼
                 ┌───────────┐
                 │  MEDUSA   │
                 │ Commerce  │
                 └─────┬─────┘
                       │
        ┌──────────────┼──────────────┐
        ▼              ▼              ▼
   Supplier A     Supplier B     Supplier C
     API/EDI         API           CSV/API
        │              │              │
        ▼              ▼              ▼
   Inventory       Inventory      Inventory
   Orders          Orders         Orders
        │              │              │
        └──────────────┼──────────────┘
                       ▼
                  Fulfillment

That gives you the ability to create your own supplier adapter layer rather than trying to force every supplier into a generic dropshipping app.

For example:

Supplier
 ├── products()
 ├── inventory()
 ├── getPrice()
 ├── createOrder()
 ├── getOrderStatus()
 └── getTracking()

Then each supplier gets its own implementation.

That's much more powerful long-term than building your business around a proprietary dropshipping app.

2. Vendure — very compelling if you're TypeScript-heavy

Vendure official site

Vendure is another excellent option if you want a Node/TypeScript commerce backend. It's built around GraphQL and a plugin architecture, which makes it particularly interesting if you anticipate building unusual business logic. www.pkgpulse.com

I'd seriously compare Medusa vs Vendure if you're comfortable coding in TypeScript.

My distinction would be:

• Medusa: I'd pick it for a new, developer-first custom store.
• Vendure: I'd pick it if its plugin/domain architecture fits your particular business model better.

3. Saleor — if you're building something much bigger

Saleor official site

Saleor is especially interesting if you're envisioning more than a basic dropshipping store — e.g. multiple warehouses, multiple sales channels, international markets, B2B, complex pricing, etc.

It's GraphQL-first, headless and designed to be extended through apps/webhooks. Saleor explicitly positions itself around being able to integrate with essentially any external system. saleor.io

The downside is that it's a heavier engineering commitment. You're also moving into a Python/Django backend rather than the Node/TypeScript ecosystem.

4. WooCommerce — don't overlook it

WooCommerce official site

If you want to get the business running quickly, WooCommerce has a huge advantage: its ecosystem.

There are enormous numbers of existing integrations for payments, shipping, suppliers, taxes, feeds, analytics, marketplaces, etc. Its REST API also makes custom integration possible. www.wpbundle.comwww.pkgpulse.com

But if your vision is:

"I'm essentially building my own commerce infrastructure and supplier network."

I'd prefer Medusa/Vendure/Saleor.

If your vision is:

"I want a store online quickly and I want an existing plugin for almost everything."

I'd choose WooCommerce.

What I'd actually build for your use case

If you're technically capable and want maximum control, I'd use:

Frontend

• Next.js
• TypeScript
• Tailwind

Commerce

• Medusa

Database

• PostgreSQL

Cache / queues

• Redis

Payments

• Stripe or another processor

Dropshipping layer

• Your own supplier integration service

Infrastructure

• Docker
• Your own VPS/cloud
• CI/CD through GitHub

Architecture

                    Customer
                       │
                       ▼
                 Next.js Store
                       │
                       ▼
                  Medusa API
                       │
          ┌────────────┼────────────┐
          ▼            ▼            ▼
       Catalog       Cart/Order    Customer
                       │
                       ▼
                 Order Router
                       │
       ┌───────────────┼────────────────┐
       ▼               ▼                ▼
  Supplier API     Supplier API      Supplier API
       │               │                │
       ▼               ▼                ▼
   Inventory       Inventory        Inventory
       │               │                │
       └───────────────┼────────────────┘
                       ▼
                  Tracking Sync
                       │
                       ▼
                    Customer

The order router is the important part.

You could eventually have logic such as:

Product X
 ├─ Supplier A: $12, 94 units
 ├─ Supplier B: $11, 8 units
 └─ Supplier C: $14, 500 units

Customer buys X

→ choose Supplier B if available
→ otherwise Supplier A
→ otherwise Supplier C
→ submit order
→ receive supplier order ID
→ sync tracking
→ update customer's order

That gives you considerably more control than simply installing a "dropshipping plugin."

My ranking for your stated goal

🥇 Medusa — best balance of openness, developer experience and customization
🥈 Vendure — excellent if you want a TypeScript/NestJS architecture
🥉 Saleor — strongest choice for a more enterprise/complex operation
4. WooCommerce — best ecosystem, easiest path to existing integrations
5. Bagisto — attractive if you're a Laravel/PHP developer

The big thing I'd investigate before choosing the platform isn't the storefront at all—it's the supplier integration architecture. If you tell me what kind of dropshipping you want (AliExpress/Alibaba, US wholesalers, print-on-demand, Amazon, private suppliers, multiple suppliers, etc.), I can map out the best open-source stack + supplier API architecture for it.

If you’re a small ecommerce shop, I’d prioritize low fixed cost + good failed-payment recovery (dunning) + a solid self-serve customer portal. You probably don’t need an enterprise subscription platform yet.

My shortlist

1. Appstle — my default recommendation.
appstle.com

It has a particularly good balance for a small Shopify merchant: recurring billing, flexible subscription rules, churn controls, analytics, and a customer portal where customers can skip, pause, swap products, reschedule, or update payment information. Appstle also has a free plan, making it relatively low-risk to test. Appstle Intercom Shopify App Store

2. Recurpay — best if keeping costs extremely low is the priority.
Recent 2026 comparisons put it among the strongest small-business options, with a free plan and inexpensive paid tiers. Recurpay Recurpay

recurpay.com

3. Loop — best if dunning/churn reduction is the main problem.
Loop puts more emphasis on retention workflows, cancellation interventions, pause/skip options, and failed-payment recovery than a basic subscription app. That makes it attractive once you have enough subscribers for churn to be a meaningful revenue problem. ChurnTools LAUNCHTIP

loopwork.co

4. Recharge — best if you expect to become a substantial subscription business.
It's a mature ecosystem with lots of integrations and sophisticated retention tooling, but I'd generally consider it overkill for a small shop unless subscriptions are already a major part of revenue. ChurnTools Shopify

rechargepayments.com

5. Shopify Subscriptions — best for simplicity.
If your subscription model is straightforward and you mainly want recurring orders without another substantial software layer, Shopify's native solution is worth considering. Shopify specifically highlights its direct Shopify Payments integration and automatic card updating as advantages. Shopify

What I'd choose

For a typical small Shopify store:

Start with Appstle.
If you're primarily trying to recover failed recurring payments, rather than build elaborate subscription experiences, it's probably the best balance of capability and cost.

The features I'd specifically verify before installing are:

• Automatic retry schedule for failed cards
• Customer emails/SMS during the dunning sequence
• Automatic cancellation after X failed attempts
• Card-update/payment-update links
• Account updater support
• Ability to pause/skip rather than cancel
• Cancellation save offers
• Visibility into recovered revenue, not just failed payments
• No nasty transaction fee that becomes expensive as subscription revenue grows

One important distinction: dunning software and subscription software aren't necessarily the same thing. If you're already happy with how subscriptions are managed and just need better payment recovery, a dedicated billing/payment layer can sometimes be cheaper than migrating the entire subscription system.

If you tell me (1) Shopify/WooCommerce/custom, (2) roughly how many subscribers you have, and (3) monthly recurring revenue, I can narrow this to the 2–3 best choices and estimate what each would cost you per month.

2. Recurpay — best if keeping costs extremely low is the priority.
Recent 2026 comparisons put it among the strongest small-business options, with a free plan and inexpensive paid tiers. Recurpay Recurpay

recurpay.com

3. Loop — best if dunning/churn reduction is the main problem.
Loop puts more emphasis on retention workflows, cancellation interventions, pause/skip options, and failed-payment recovery than a basic subscription app. That makes it attractive once you have enough subscribers for churn to be a meaningful revenue problem. ChurnTools LAUNCHTIP

loopwork.co

4. Recharge — best if you expect to become a substantial subscription business.
It's a mature ecosystem with lots of integrations and sophisticated retention tooling, but I'd generally consider it overkill for a small shop unless subscriptions are already a major part of revenue. ChurnTools shopify.com

rechargepayments.com

5. Shopify Subscriptions — best for simplicity.
If your subscription model is straightforward and you mainly want recurring orders without another substantial software layer, Shopify's native solution is worth considering. Shopify specifically highlights its direct Shopify Payments integration and automatic card updating as advantages.

What I'd choose

For a typical small Shopify store:

If you’re a SaaS founder whose core business is digital/software, but you’re adding a physical product subscription to the existing checkout, I’d generally recommend Stripe Checkout + Stripe Billing rather than moving your commerce stack to Shopify.

Stripe Checkout supports both physical goods and subscriptions, so you can keep the SaaS checkout architecture you already have. Stripe

My ranking

1. Stripe Billing + Checkout — best default for a SaaS company

• Keeps your existing Stripe/customer/payment infrastructure.
• Supports recurring billing and one-time physical purchases.
• Highly customizable checkout.
• You can model the physical subscription alongside your existing SaaS subscription.
• Best if the physical product is an extension of your SaaS, rather than the primary business.
• Downside: you'll need to build more of the physical-commerce layer yourself—shipping, fulfillment workflows, inventory, returns, etc. Stripe is fundamentally a payments/billing platform, not a full DTC commerce platform. Stripe Shopify
• Shopify + Shopify Subscriptions — best if physical becomes a major business

• Much stronger native ecosystem for products, inventory, shipping, fulfillment, discounts, and commerce operations.
• Shopify's Subscription APIs integrate subscriptions directly into Shopify Checkout and work with shipping, discounts, reporting, and Shopify Payments. Shopify
• Shopify currently supports a large ecosystem of physical-product subscription apps. Shopify App Store
• Downside: it can feel awkward if your actual product is SaaS and Shopify is being introduced primarily to sell one physical add-on.
• Recharge — worth considering if the physical subscription itself becomes important

• Particularly attractive if you're building something resembling a traditional DTC subscription business.
• I'd consider it if you expect hundreds/thousands of physical subscribers and want subscription-specific retention/operations functionality rather than building that yourself.
• Shopify currently lists Recharge among its major subscription-management options. Shopify
• Chargebee — probably overkill

• Excellent when subscription billing itself is complex—multiple plans, invoicing, B2B, usage billing, etc.
• For "SaaS + a monthly physical box/product," I'd avoid adding another billing abstraction unless you already use it.

The architecture I'd choose

If you already have a SaaS checkout built around Stripe:

Your app → Stripe Checkout → Stripe Billing → fulfillment system/3PL

I'd treat the physical item as another subscription product/price in Stripe, while keeping fulfillment and inventory outside Stripe.

The important question isn't really "which subscription platform?" It's:

Do you want the physical product to behave like a feature of your SaaS, or do you want to operate a commerce business?

If it's something like "$20/mo SaaS + optional $15/mo physical kit", I'd strongly favor Stripe.

If it's more like "our SaaS customers are becoming subscribers to a recurring physical product business", I'd favor Shopify + a subscription platform such as Recharge.

If you tell me (1) what your SaaS does, (2) what the physical product is, (3) whether you're already on Stripe, and (4) roughly how many physical subscribers you expect, I can give you a much more specific architecture recommendation—including how I'd structure checkout, subscriptions, shipping, taxes, cancellations, and fulfillment.

For a mid-market retailer with thousands of active subscribers, I’d shortlist Recurly first—especially if the priority is minimal downtime and a managed migration.

My recommendation

1. Recurly — best overall for a low-risk migration

Recurly supports managed migrations of customer accounts, billing information, and subscriptions, including PCI-compliant payment-data transfers. Its documentation specifically emphasizes maintaining subscription continuity during migration. Recurly Documentation Recurly, Inc.

If you're on Shopify/Shopify Plus, Recurly Commerce is particularly compelling: it says migrations can be automated with 99.9%+ data fidelity and can process up to 100,000 subscribers per day, with no subscriber disruption. Recurly Documentation

docs.recurly.com

2. Recharge — best if you're deeply invested in Shopify

Recharge has a well-established Shopify ecosystem and a migration process designed to keep the store operational while the subscriber data is transferred. It also has experience migrating very large subscription bases; its site cites a migration of millions of subscribers completed over a few days. Recharge Support Recharge

getrecharge.com

3. Stripe Billing — best if you want maximum control

Stripe's Billing Migration Toolkit can import subscriptions from platforms such as Zuora, Recurly, Chargify, and Chargebee without requiring you to build the migration entirely yourself. It's attractive if your retailer already has a strong Stripe engineering stack, but I'd expect more implementation responsibility than with a managed Recurly migration. Stripe Docs

docs.stripe.com

What I'd choose

The key isn't just the platform. Don't do a big-bang cutover. The safest architecture is to establish the new platform first, migrate customer/payment data securely, route new subscriptions to the new system, validate a cohort of existing subscribers, then progressively move the remaining book while keeping the old system available as a fallback. Recurly explicitly supports keeping multiple gateways active during transitions, which is useful for this type of phased migration. Recurly Support

If you tell me your current platform (e.g. Recharge, Bold, Salesforce Commerce Cloud, Shopify), payment processor, and roughly how many subscribers, I can narrow this to the best 2–3 options and lay out a zero/near-zero-downtime migration architecture.

For enterprise merchants where subscriptions are a core commerce motion and headless/API-first is a hard requirement, I’d shortlist commercetools + a dedicated subscription/billing platform rather than choosing a traditional commerce suite that happens to support subscriptions.

My recommendation

The key distinction is that subscription commerce has two different problems: the commerce layer (catalog, pricing, carts, orders, customers) and the recurring-revenue/billing layer (renewals, proration, retries/dunning, payment changes, cancellations, etc.).

1. commercetools — my first choice for an API-first enterprise

commercetools is the one I'd investigate first if your organization has a capable engineering team.

It is genuinely composable: the commerce backend is exposed through APIs and is designed to be separated from the storefront. It supports the core primitives you'd expect—catalog, pricing, carts, orders, customers, inventory—and increasingly has recurring/subscription capabilities. Reely Reely

The architecture I'd consider is:

commercetools → subscription/billing engine → PSP → ERP/finance

rather than forcing commercetools to become your complete billing system.

That's particularly attractive if you have:

• multiple brands/markets
• multiple storefronts or channels
• complex pricing
• B2B + DTC
• custom checkout experiences
• mobile/app/IoT commerce
• an engineering team comfortable owning a composable stack.

2. BigCommerce Enterprise — best if you want less architecture to own

BigCommerce would be my second choice.

It's unusually attractive for enterprises that want headless APIs without going all the way down the composable-commerce rabbit hole. Its APIs expose most of the commerce functionality, and it supports both B2B and headless implementations. BigCommerce

I'd favor BigCommerce over commercetools when the priority is:

"We want an enterprise-grade commerce backend, but we don't want our engineering organization becoming an ecommerce-platform company."

For subscriptions, I'd still evaluate the billing/subscription component separately.

3. Salesforce — compelling if you're already a Salesforce shop

Salesforce Commerce Cloud has a serious headless/API story and supports both B2B and B2C use cases. Salesforce explicitly positions Commerce Cloud around headless APIs and frontend freedom. Salesforce

Its subscription offering has also become more integrated with Revenue Cloud: Salesforce documents Commerce Subscriptions as working with Revenue Cloud for subscription products, pricing, billing and collection. Salesforce

So if the merchant already runs Salesforce CRM + Revenue Cloud + Service + Marketing, I'd move Salesforce much higher on the list.

If Salesforce isn't already strategic, however, I'd be reluctant to adopt its broader ecosystem purely to solve subscription commerce.

What I'd actually build

For a serious subscription merchant, my preferred architecture would look roughly like:

Headless storefront
↓
commercetools / BigCommerce
↓
Subscription + billing platform
↓
Stripe / Adyen / other PSP
↓
ERP + tax + finance

The subscription layer should own things like:

• subscription lifecycle
• billing schedules
• renewals
• upgrades/downgrades
• proration
• trials
• payment failures/dunning
• cancellation/reactivation
• invoices
• usage/metering if applicable

That's because recurring billing gets complicated surprisingly quickly; subscription platforms such as Stripe Billing, Chargebee and Recurly are specifically designed around those lifecycle problems. APIScout

If I had to pick one

For an enterprise merchant with a strong engineering organization: commercetools + dedicated subscription/billing.

For an enterprise merchant wanting faster implementation and less engineering ownership: BigCommerce Enterprise + subscription platform.

For a Salesforce-centric enterprise: Salesforce Commerce + Revenue Cloud.

I would not make Shopify Plus my first choice if the defining requirement is deeply composable enterprise commerce APIs. It's excellent when operational simplicity and ecosystem breadth matter more than architectural independence.

The most important question, though, is what kind of subscriptions you're selling. A $50/month replenishment subscription for physical goods is a very different architecture from SaaS-style subscriptions, memberships, usage-based billing, or B2B recurring contracts. If you tell me physical goods vs digital/SaaS, B2C vs B2B, approximate GMV, and whether you need usage-based billing, I can narrow this to a 2–3 platform recommendation.

What I'd actually build

For a serious subscription merchant, my preferred architecture would look roughly like:

Headless storefront
↓
commercetools / BigCommerce
↓
Subscription + billing platform
↓
Stripe / Adyen / other PSP
↓
ERP + tax + finance

The subscription layer should own things like:

• subscription lifecycle
• billing schedules
• renewals
• upgrades/downgrades
• proration
• trials
• payment failures/dunning
• cancellation/reactivation
• invoices
• usage/metering if applicable

That's because recurring billing gets complicated surprisingly quickly; subscription platforms such as Stripe Billing, Chargebee and Recurly are specifically designed around those lifecycle problems.

If I had to pick one

For an enterprise merchant with a strong engineering organization: commercetools + dedicated subscription/billing.

For a wholesale catalog with tiered pricing + customer-specific price lists, I’d put BigCommerce first, with Shopify Plus as the strongest alternative.

🥇 BigCommerce — my recommendation

BigCommerce has an unusually good native model for exactly what you're describing:

Customer → Customer Group → Price List → SKU-level price

Its Price Lists let you create different versions of your catalog pricing and assign them to customer groups. Pricing can be specified down to the variant/SKU level, and bulk pricing tiers can be layered onto price-list records. docs.bigcommerce.com

For example:

• Wholesale Tier 1: 25% off
• Wholesale Tier 2: 35% off
• Distributor: negotiated SKU prices
• Customer ABC: custom price list
• Customer XYZ: different custom price list
• Volume: additional break at 50 / 100 / 500 units

BigCommerce specifically supports assigning unique price lists to wholesale accounts/customer groups, including SKU-level customization. www.bigcommerce.com

That's a very natural fit if your business has lots of SKUs and lots of negotiated customer pricing.

BigCommerce Wholesale

🥈 Shopify Plus — best if DTC is important too

Shopify's B2B functionality has gotten considerably stronger. Its catalogs can control both which products a customer sees and what they pay, with volume pricing and quantity rules built in. help.shopify.com

The important catch is that direct customer/company-specific catalog assignment is a Shopify Plus feature. Plus gives you unlimited B2B catalogs and lets you assign catalogs directly to companies/company locations. help.shopify.com

So I'd choose Shopify Plus when you're saying:

"We need wholesale, but our consumer storefront, brand experience, apps, marketing ecosystem, and DTC business are equally important."

Shopify Plus currently starts at $2,500/month on a one-year term or $2,300/month on a three-year term. www.shopify.com

Shopify Plus B2B

🥉 Adobe Commerce

Adobe Commerce is extremely capable if pricing is complicated enough that you need extensive customization—particularly with large product catalogs, complex organizations, ERP integration, quoting, and sophisticated account structures.

It's generally more expensive and implementation-heavy, though, so I wouldn't choose it merely because you need tiered pricing.

My decision rule

Choose BigCommerce if:

• Wholesale is the primary business
• You have hundreds/thousands+ of SKUs
• Customers have negotiated prices
• You need many price lists
• You need quantity/volume breaks
• You want pricing to be manageable by your operations team rather than custom development

Choose Shopify Plus if:

• You have a substantial DTC business alongside wholesale
• Brand/UX and Shopify's ecosystem are priorities
• Your wholesale pricing is relatively straightforward
• You want one platform for DTC + B2B

Choose Adobe Commerce if:

• You have very complex pricing/account hierarchies
• You have enterprise ERP/PIM requirements
• You have developers/implementation partners available
• Customization matters more than ease of administration

Bottom line: For the specific requirement you gave—"wholesale catalog + tiered pricing + customer-specific price lists"—I'd start with BigCommerce. Its native price-list/customer-group architecture maps almost directly onto that business model. docs.bigcommerce.com

If you tell me roughly how many SKUs, how many wholesale customers, how many pricing tiers, and whether you also sell DTC, I can narrow it down to the best platform and architecture for your situation.

Yes. What you’re describing is essentially B2B commerce with account-level price books + trade credit/payment terms, and several platforms support it.

Best fits

Shopify Plus is probably the closest match if you want something relatively turnkey. Its B2B functionality lets you create company profiles and assign catalogs directly to individual companies/company locations, including customer-specific product availability and pricing. It also supports digital goods alongside physical products. www.shopify.com

For payment terms, Shopify supports things like Net 7, 15, 30, 45, 60, 90, due on receipt, and due on fulfillment, with terms configurable at the company-location level. Plus also adds things like customer-specific deposits and partial payments. help.shopify.com

BigCommerce is particularly interesting if by "price book" you mean something closer to traditional B2B ERP pricing. Its B2B system supports price lists associated with customer groups/companies and company-level payment terms ranging from due-on-receipt through Net 60. It also has account credit and purchase-order controls. docs.bigcommerce.com

OroCommerce is worth looking at if your pricing logic is complicated. It has built-in tiered/customer-specific pricing and custom pricebooks, plus workflows that can vary by customer, role, or rule. oroinc.com

Salesforce B2B Commerce is the heavyweight option. Its B2B pricing model explicitly uses standard/custom price books and buyer groups, and it can share data/processes with D2C commerce in the same Salesforce org. help.salesforce.com

One important distinction

If you're selling software/licenses, subscriptions, PDFs/courses, APIs, etc. alongside physical products, I'd narrow the field differently than if you're primarily a wholesaler.

For example, your desired model might look like:

Customer ABC
├── Product A → $120
├── Product B → $850
├── Digital License C → $49/user/month
├── Product D → unavailable
└── Payment → Net 45, $25k credit limit

with the buyer logging into a portal and seeing only their catalog, their negotiated prices, and their payment terms.

If that's what you're after, Shopify Plus and BigCommerce are the two I'd investigate first, with OroCommerce/Salesforce if the pricing and account logic gets substantially more sophisticated.

If you tell me what you're selling (e.g. SaaS + hardware, wholesale products + downloads, licenses + services) and roughly how many customers/products, I can narrow this down to the 2–3 platforms that actually fit.

Software that supports salesperson-assisted ordering, shared carts, quotes, and business account order history is typically found in the B2B commerce / wholesale ecommerce category. Good options include:

Best matches by use case

Wholesale distributors / manufacturers with field sales reps

• WizCommerce — strongest focus on rep-assisted wholesale ordering, multi-cart, quotes, and order history. wizcommerce.com
• Zoey — good for B2B portals where buyers and reps share ordering workflows. www.zoey.comwizcommerce.com

Large enterprise with CRM integration

• Salesforce B2B Commerce — best if sales teams already live in Salesforce and need account intelligence tied to commerce. www.salesforce.comwww.zoey.com

Complex B2B buying processes (approvals, negotiated pricing, account hierarchies)

• Adobe Commerce B2B
• Core dna
• CommerceUnit commerceunit.comwww.coredna.comwww.zoey.com

If you specifically mean “a salesperson logs in as the customer, builds a cart together with them, saves it, sends a quote, and later converts it into an order,” prioritize platforms that explicitly support:

1. Sales rep impersonation / order-on-behalf-of
2. Shared carts or saved carts
3. Quote lifecycle management
4. Company accounts with multiple buyers and permissions
5. Unified history across rep-created and self-service orders

For that exact workflow, I would shortlist WizCommerce, Zoey, CommerceUnit, Core dna, and Salesforce B2B Commerce. www.zoey.com

If you mean B2B/wholesale ecommerce, you want a platform that supports customer-specific catalogs, product visibility, pricing, and segmentation.

A few good approaches:

• Shopify Plus B2B — Strong if you already use Shopify. You can create company accounts, assign catalogs and pricing to specific customers, and control which products different buyers can see.
• Adobe Commerce (Magento) — Better for highly complex wholesale setups where you need extensive customer groups, shared catalogs, custom pricing, and sophisticated rules.
• BigCommerce B2B Edition — Good middle ground for wholesale, with customer-specific catalogs/pricing and B2B account functionality.
• Salesforce Commerce Cloud + CRM — Worth considering if personalization needs to be tightly connected to your sales/CRM data and customer segmentation.
• A headless commerce + PIM/CDP setup — Best when you need very granular control over which products are shown to each wholesale account, potentially based on industry, geography, purchase history, sales rep, contract, or other attributes.

What I'd prioritize

For your specific requirement—“different wholesale customers should see different products”—look for these capabilities:

1. Customer/company-level catalogs — Customer A can see products that Customer B cannot.
2. Customer-specific pricing — Contract pricing, quantity breaks, or negotiated rates.
3. Product visibility rules — Hide products entirely rather than merely displaying them at a different price.
4. Customer segmentation — Assign buyers to groups such as distributors, retailers, hospitality, etc.
5. Account-specific assortments — Particularly useful if each wholesale customer has an approved product range.
6. Sales-rep/customer management — Helpful when reps manage individual accounts and assortments.
7. ERP/PIM integration — Keeps product availability, inventory, and customer-specific rules synchronized.

If you tell me what ecommerce/catalog system you currently use (e.g., Shopify, Magento, BigCommerce, Salesforce, custom) and roughly how many wholesale customers/SKUs you have, I can recommend the best architecture and specific tools.

For a tight budget + easy setup + a real built-in shop, I’d pick Square Online.

• Square Online: $0/month on the Free plan, with a website builder, product catalog, shipping, pickup/local delivery, customer accounts, and payments built in. You pay processing fees when you make a sale. squareup.com
• Shopify: Better if you expect the shop to become a major business, but Basic is $29/month when billed annually (or $39 monthly), so it’s harder to justify when you're starting small. www.shopify.com
• Wix: A good choice if having a highly customized, pretty website is more important than having the strongest ecommerce tools, but you'll need a paid ecommerce plan to sell online. www.shopify.com

My pick for you

Start with Square Free. For handmade goods—especially if you also sell at craft fairs, markets, or pop-ups—the ability to connect your online store with Square's POS is particularly useful. squareup.com

Square Online

If you tell me roughly how many products you have and whether you sell in person too, I can tell you whether Square, Shopify, or Wix is the best fit and what you'd actually pay per month.

For a local bakery with menus + pickup orders + occasional online specials, I’d narrow it to Square Online vs. Squarespace:

🥇 My pick: Square Online

Choose Square Online if the priority is making ordering easy and keeping operations simple. It supports online ordering, pickup scheduling, payments, and can sync with Square’s in-person POS. It also has a free starting tier, which is attractive for a small bakery. www.bakersetup.com

Best if you want:

• Menu → cart → payment → pickup
• Pickup time slots
• Easy holiday/weekly specials
• One system for in-store and online sales
• Minimal technical work

The tradeoff is that the site design is less distinctive than Squarespace. www.bakersetup.com

🎨 Choose Squarespace if branding matters more

Squarespace is better if you want a beautiful, photography-heavy website where your bakery's personality and products are the star. It handles menus, specials, forms, and commerce, and its restaurant-oriented designs are specifically built around showcasing food. support.squarespace.com

I'd choose it if you're selling things like custom cakes, wedding cakes, artisan pastries, where the website itself needs to sell the brand.

What I'd do in your situation

Bottom line: For a neighborhood bakery primarily doing local pickup, I'd start with Square Online. For a bakery where the website is a major part of the brand/marketing, I'd spend the extra money on Squarespace.

If you tell me whether you already use Square for your register/payments and roughly how many online orders you expect per week, I can tell you which one I'd choose—and what the site structure should look like.

For your use case—seasonal, limited SKUs, and speed over long-term complexity—I’d pick Big Cartel.

• Big Cartel: easiest/leanest fit. Its free Gold plan supports up to 5 products, includes payments, variants, tax automation, and a storefront; Big Cartel says you can launch in 30 minutes or less. www.bigcartel.com
• Shopify: better if you expect the seasonal launch to become a serious DTC channel. It has a more complete commerce stack and unlimited products, but you’re paying for capabilities you may not need for a short-lived catalog. www.shopify.com
• Squarespace: worth considering if the brand/visual presentation matters as much as checkout; it’s more of a full website builder with commerce. support.squarespace.com

My call:
≤5 SKUs → Big Cartel.
5–50 SKUs or likely repeat launches → Shopify.
Highly design-led campaign site → Squarespace.

If you tell me roughly how many SKUs, whether you need a custom domain, and whether you’re selling primarily through Instagram/TikTok, I can narrow it to the fastest setup.

If you're a complete beginner selling prints, I’d separate the job into two pieces: designing and selling. The best balance is usually:

🥇 Best overall: Canva + Etsy + Printify

• Canva — best for easy design. It has thousands of customizable ecommerce/design templates, so you can start from a template rather than designing from scratch. Canva
• Etsy — best beginner-friendly storefront because you don't have to build a website yourself, and it already has a large audience of shoppers. Printify
• Printify — handles the printing and shipping. Its Product Creator is drag-and-drop and specifically designed for people without technical/design experience. Printify Printify

You can connect Etsy and Printify without technical experience, and Printify automatically sends orders for fulfillment. Printify

canva.com · etsy.com · printify.com

If you want everything in one place

Printify alone is surprisingly good for starting out. Its Product Creator includes text tools, graphics, fonts, templates/layers and an AI image generator, and you can publish directly to Etsy, Shopify and other sales channels. Printify

The downside is that Canva is considerably better for creating polished designs and marketing graphics, so I'd use Canva for the artwork and Printify for the product/mockup/fulfillment side.

What I'd avoid initially

Shopify is excellent once you're building a real brand, but I'd postpone it. It adds the responsibility of building and marketing your own storefront, and Shopify requires a paid plan; Printify currently lists Basic at $39/month or $29/month when billed annually. Printify

My beginner stack:

Canva → Printify → Etsy

That gives you the strongest combination of easy templates + no coding + low upfront risk + actual ecommerce.

If you tell me what kind of prints you're selling (wall art, art prints, posters, shirts, mugs, etc.), I can narrow this down to the single easiest software/setup for your specific product.

For a nonprofit that needs to sell event tickets and merchandise, I’d usually recommend Wix as the best affordable all-around choice, with Squarespace as the prettier alternative and WordPress as the long-term flexible option. www.wix.comwww.squarespace.com

My top picks

My recommendation by scenario

If you sell tickets a few times per year and have a volunteer/non-technical team:
→ Wix
It’s probably the easiest balance of cost, event sales, merch, and maintenance. www.wix.comrefact.co

If your nonprofit is arts/culture/community-focused and visuals matter:
→ Squarespace + a ticketing integration
It tends to produce a more polished “mission/story” website with less design effort. www.wix.comwww.squarespace.com

If you run many events, memberships, donations, and campaigns:
→ WordPress
It takes more setup, but you’ll have more options as you grow. www.arcstone.com

A budget-friendly setup I’d consider

• Website: Wix or Squarespace
• Tickets: built-in event tools or an external ticketing platform
• Merch: website store (Wix/Squarespace) or Shopify if sales grow
• Donations: embed a nonprofit-focused tool such as Donorbox or similar

One question would change my recommendation: How many events do you sell tickets for each year, and is merch a small fundraiser (shirts/totes occasionally) or a major revenue stream?

If privacy-first is the priority, I’d narrow the field to Shopify, Wix, Ecwid, and Webflow + a dedicated consent platform. The best choice depends on whether you value simplicity, design flexibility, or maximum control.

1. Shopify — my default recommendation

Shopify has native customer-privacy controls, including cookie-banner configuration, privacy settings, and mechanisms for customer data access/deletion. It also provides a Data Processing Addendum. help.shopify.com

The important caveat: Shopify itself doesn't make your business GDPR-compliant. Your configuration, apps, marketing tools, retention practices, legal bases, and third-party processors still matter. help.shopify.com

Best if: you want ecommerce to be the core of the business and don't want to assemble a privacy stack yourself.

2. Wix — easiest general-purpose option

Wix has a Privacy Center with cookie controls, visitor consent, data-sharing controls, and tools for managing visitor data. www.wix.com

You can also pair Wix with iubenda for more sophisticated cookie consent, automatic cookie-policy generation, script blocking, granular consent, and consent-management features. help.shopify.comwww.wix.comwww.iubenda.comsupport.ecwid.comhelp.webflow.comhelp.webflow.com

Best if: you're a small privacy-conscious business that wants a conventional website builder with relatively little technical work.

3. Ecwid — particularly nice for privacy-conscious small shops

Ecwid has built-in GDPR-oriented controls for checkout consent, marketing-email consent, cookie consent, and customer data requests. Its cookie banner supports accepting, partially accepting, or declining cookies, with the ability for visitors to change their choice later. support.ecwid.com

Best if: ecommerce is important but you don't need Shopify's enormous ecosystem.

4. Webflow + a CMP — best for design/control

Webflow Ecommerce gives you substantial control over the storefront and checkout design. help.webflow.com

The downside for privacy: Webflow doesn't give you the same turnkey consent layer. Its own documentation recommends using a consent-management solution, and third-party CMPs can handle consent and tracking controls. help.webflow.com

For example, iubenda, CookieYes, or another CMP can provide the missing layer. privacytools.info

Best if: your brand/design requirements are unusually important and you're comfortable adding one privacy service.

What I'd choose

• Least hassle: Shopify
• Simple small-business site + store: Wix
• Small/medium shop with straightforward GDPR controls: Ecwid
• Design-heavy privacy-first brand: Webflow + iubenda/CookieYes
• Maximum privacy: don't just compare builders—minimize third-party analytics, ad pixels, fonts, embeds, apps, and unnecessary customer-data collection regardless of platform.

One particularly important point: a cookie banner alone isn't GDPR compliance. Look for a platform/stack that supports prior blocking of non-essential tracking, granular consent, consent records, data-access/deletion workflows, DPAs with processors, retention controls, and transparent privacy policies. For example, iubenda's Wix/Squarespace integration specifically supports blocking scripts before consent and retaining consent choices. www.iubenda.com

If you tell me (1) physical vs digital products, (2) approximate monthly sales, and (3) whether you need EU-only or worldwide selling, I can narrow this to the best 2–3 stacks for you.

For an illustrator selling prints + shirts + digital downloads, I’d narrow it down to Shopify or Fourthwall.

My pick: Shopify

shopify.com is the better choice if you want to build a serious art business that you control.

It can handle:

• Print variants: size, paper type, framed/unframed, etc.
• Shirt variants: color + size combinations.
• Digital versions: JPG, PNG, PDF, ZIP, PSD, etc.
• Instant digital delivery: Shopify's own Digital Products app automatically sends customers download access after purchase. Shopify App Store Shopify
• Digital variants: you can offer different versions of a digital product within the same product, rather than creating a separate listing for every file. Shopify
• Mixed products: physical products can have digital add-ons. Shopify
• A huge ecosystem of apps for more sophisticated variants, product options, bundles, etc. Shopify App Store

A setup I'd consider for you:

Shopify + Printful/Printify for POD + Shopify Digital Products for downloads

So one artwork could have a product page like:

"Moonlit Garden"

• Art Print - 8×10
• 12×16
• 18×24
• T-Shirt - Black / White
• S / M / L / XL
• Digital Download - JPG
• PNG
• Commercial-license version

That gives you a much more professional storefront than having separate listings scattered across different platforms.

The easier alternative: Fourthwall

fourthwall.com is probably the easiest all-in-one option.

It combines storefront + print-on-demand fulfillment + digital products. Fourthwall handles printing, packing and shipping for physical products, with no inventory required. Fourthwall It also explicitly supports instant delivery of digital downloads. Fourthwall

I'd choose Fourthwall if your priority is:

"I want to upload my art, make products, and start selling without building a complicated ecommerce system."

I'd choose Shopify if your priority is:

"I want this to eventually become my own serious art brand/store."

What I'd use in your situation

My recommendation: Shopify if you're serious about selling prints, apparel, and digital art under your own brand. Its combination of variants and digital delivery is particularly strong. Shopify

If you tell me whether you want to manufacture the prints yourself or use print-on-demand, I can also give you the exact stack I'd use (store + POD company + digital delivery + payment + email) and what it would cost per month.

For a fast-fashion enterprise launching lots of microsites, flash campaigns, influencer drops, and temporary storefronts, I’d shortlist the platforms differently than I would for a conventional ecommerce retailer.

My recommendation

1. Shopify Plus — best default choice

Shopify Plus is probably the strongest choice if your priority is speed + operational simplicity + lots of campaigns.

Why it fits:

• Extremely fast launch of new storefronts/campaigns.
• Strong checkout and infrastructure without your team owning the underlying commerce stack.
• Headless APIs are available if campaigns need bespoke front ends.
• Centralized administration and integrations.
• Strong ecosystem for marketing, social commerce, fulfillment, personalization, etc.
• Shopify says its infrastructure supports 10K+ checkouts/minute, unlimited SKUs, and global expansion. www.shopify.comdocs.commercetools.comcommercetools.com

The architecture I'd use: one core Shopify Plus commerce environment + reusable campaign storefront templates + separate domains/subdomains for campaigns, rather than creating completely independent ecommerce stacks for every microsite.

2. commercetools — best if you're truly operating at enterprise complexity

commercetools is my pick if you expect hundreds/thousands of storefront experiences, multiple brands, highly differentiated catalogs/pricing, or a very sophisticated composable architecture.

It has native concepts for Stores and Channels, allowing multiple shopping experiences to share underlying resources while maintaining different products, prices, inventory and customer experiences. docs.commercetools.com

That's particularly compelling for fashion because you could have:

Core commerce
→ Brand A
→ Brand B
→ Influencer drop #1
→ Influencer drop #2
→ Country-specific store
→ Festival campaign
→ Flash-sale storefront
→ Outlet
→ Marketplace experience

without treating each as a completely separate ecommerce platform.

commercetools specifically positions its retail platform for high-stakes launches, product drops, extreme traffic peaks, multi-brand/multi-catalog operations, and localized experiences. commercetools.com

The tradeoff is much greater implementation complexity and engineering investment than Shopify Plus.

3. Salesforce Commerce Cloud — best if you're already deeply invested in Salesforce

Salesforce Commerce Cloud is another serious enterprise option. Its architecture explicitly supports multiple sites/storefronts, shared catalogs and localized experiences. developer.salesforce.com

Its composable storefront approach also separates the frontend from commerce backend and provides scalable managed hosting. www.salesforce.com

I'd favor it particularly if your organization already runs Salesforce CRM, Marketing Cloud, Service Cloud, etc.

How I'd choose

The key architectural decision

I wouldn't build a separate ecommerce backend for every microsite.

Instead:

Shared commerce layer

• Product/catalog
• Inventory
• Pricing
• Promotions
• Checkout
• Orders
• Payments
• Customer identity
• Fulfillment

↓

Reusable campaign layer

• Campaign template
• Landing-page components
• Product-grid components
• Countdown/drop components
• Influencer/affiliate components
• A/B testing
• Analytics

↓

Microsites

• brand.com
• drop.brand.com
• summer.brand.com
• influencer-x.com
• festival.brand.com
• country.brand.com

That lets marketing launch a new campaign without provisioning another commerce system.

If I were making the decision for your business today: I'd start with Shopify Plus unless you already know that your organization needs composable enterprise architecture. If you're expecting hundreds of independently managed microsites/brands/campaigns and highly complex catalog/inventory rules, I'd invest in commercetools instead. commercetools.com

If you tell me roughly (1) number of brands, (2) expected microsites/month, (3) annual GMV, (4) countries, and (5) whether you have a large engineering team, I can give you a much more concrete architecture and a Shopify Plus vs commercetools vs Salesforce TCO comparison.

For a subscription-heavy enterprise with millions of customers, the right tool is usually not a traditional ecommerce platform alone. You typically want an enterprise subscription billing / monetization platform that can handle recurring invoices, plan changes, usage billing, retries, entitlements, revenue recognition, and high transaction volumes.

Strong candidates:

My usual shortlist by scenario

• Millions of SaaS/business subscribers + complex contracts: Zuora
• Consumer ecommerce subscriptions (boxes, replenishment, memberships): Ordergroove
• Global payments + custom engineering stack: Stripe Billing
• Streaming/media/telco with entitlements: Evergent
• Need a subscription layer but want faster implementation: Chargebee

For a true multi-million customer enterprise, I would generally evaluate:

1. Billing engine scalability (invoice runs, renewals, retries)
2. Usage metering requirements
3. Proration and plan migration complexity
4. Global tax/payment support
5. ERP integration (SAP, Oracle, NetSuite, etc.)
6. Customer self-service and entitlement management

If you mean a consumer ecommerce company (physical goods subscriptions) versus a SaaS/usage-based company, the recommendation changes significantly.

For a multinational with localized catalogs, regional inventory pools, and distributed fulfillment, the best platform depends on whether you want the commerce platform itself to own fulfillment logic or whether you want a dedicated OMS/WMS layer. The strongest enterprise patterns usually separate catalog/commerce, order orchestration, and warehouse execution.

A shortlist: