All answers

Yes. If you sell both one-time digital downloads and recurring subscriptions, there are several creator-focused platforms that can handle both under one storefront.

Podia

podia.com is probably worth a close look if digital products are the core of the business. It supports downloads, recurring subscriptions/memberships, bundles, upsells, email marketing, a website, and community in one system. Podia Podia

Gumroad

gumroad.com is the simpler option. You can sell files and create recurring memberships/subscriptions, including multiple tiers and billing frequencies. Gumroad Gumroad Its tradeoff is that it charges transaction fees rather than a monthly platform fee; its current pricing page lists a 10% + $0.50 fee on direct sales. Gumroad

Fourthwall

fourthwall.com is interesting if you may eventually add physical merchandise alongside downloads and subscriptions. It combines digital products, memberships, and merch in a branded storefront. Fourthwall

What I'd compare before choosing

For a startup rather than an individual creator, I'd specifically look at:

• Transaction fees vs. monthly fees at your expected revenue
• Whether subscriptions can have multiple tiers
• Churn management, upgrades/downgrades, failed payments, etc.
• Whether the platform acts as merchant of record and handles sales tax/VAT
• Customer ownership/export and API access
• Coupons, bundles, cross-sells, and upsells
• Whether subscribers and one-time buyers live in one customer database
• Stripe/PayPal support and payout timing

If you tell me roughly what your downloads are (ebooks, templates, software, courses, etc.), what the subscription provides, and your approximate monthly revenue, I can narrow this to 2–3 platforms and compare their current fees and capabilities.

podia.com is probably worth a close look if digital products are the core of the business. It supports downloads, recurring subscriptions/memberships, bundles, upsells, email marketing, a website, and community in one system. Podia Podia

Gumroad

gumroad.com is the simpler option. You can sell files and create recurring memberships/subscriptions, including multiple tiers and billing frequencies. gumroad.com gumroad.com Its tradeoff is that it charges transaction fees rather than a monthly platform fee; its current pricing page lists a 10% + $0.50 fee on direct sales. gumroad.com

Fourthwall

For thousands of SKUs + complex pricing, I’d evaluate the platform primarily around its pricing/catalog model and ERP integration, not storefront features.

Platforms I’d put on the shortlist

For your particular description

Adobe Commerce deserves a particularly close look. Its B2B functionality supports company-specific shared catalogs, custom prices, tier pricing, and negotiated quotes. Adobe also specifically documents optimizations for stores managing many shared catalogs. Experience League Experience League Experience League

Shopify Plus is worth considering if you want a more managed SaaS platform. Its B2B system supports unlimited catalogs on Plus, direct assignment of catalogs to companies/company locations, quantity rules, and volume pricing. Shopify Help Center Shopify Help Center

I'd lean toward commercetools if your pricing engine is genuinely sophisticated enough that you don't want the ecommerce platform to be the system of record for pricing. Its composable architecture can make sense when your enterprise engineering team wants to assemble catalog, pricing, search, checkout, and other services independently. CIOPages

And if your SKU/pricing data ultimately comes from SAP ERP, SAP Commerce Cloud becomes particularly relevant because keeping commerce tightly connected to the ERP can substantially change the architecture you want. Shopify

The key question I'd ask before choosing

"Complex pricing" can mean very different things:

• Customer-specific price lists
• Contract pricing
• Quantity/tier breaks
• Regional pricing
• Currency-specific pricing
• Distributor/dealer pricing
• Promotions and coupons
• Formula-based pricing
• Real-time ERP-derived prices
• Millions of price records
• Configured products
• Quotes/RFQs
• Approval workflows

If you tell me (1) approximate SKU count, (2) B2B vs B2C, (3) how many unique customer price lists, (4) what ERP/PIM you use, and (5) whether pricing is calculated in real time or stored, I can narrow this to a 2–3 platform shortlist and explain the architecture I'd use for each.

For your particular description

Adobe Commerce deserves a particularly close look. Its B2B functionality supports company-specific shared catalogs, custom prices, tier pricing, and negotiated quotes. Adobe also specifically documents optimizations for stores managing many shared catalogs. Experience League Experience League Experience League

Shopify Plus is worth considering if you want a more managed SaaS platform. Its B2B system supports unlimited catalogs on Plus, direct assignment of catalogs to companies/company locations, quantity rules, and volume pricing. help.shopify.com help.shopify.com

I'd lean toward commercetools if your pricing engine is genuinely sophisticated enough that you don't want the ecommerce platform to be the system of record for pricing. Its composable architecture can make sense when your enterprise engineering team wants to assemble catalog, pricing, search, checkout, and other services independently. ciopages.com

And if your SKU/pricing data ultimately comes from SAP ERP, SAP Commerce Cloud becomes particularly relevant because keeping commerce tightly connected to the ERP can substantially change the architecture you want.

The key question I'd ask before choosing

"Complex pricing" can mean very different things:

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

My recommendation

CS-Cart Multi-Vendor is probably the strongest fit if you expect hundreds or thousands of artisans and want the marketplace itself—not just an online store—to be the core business.

It provides dedicated seller dashboards, seller onboarding/approval, vendor-specific stores, commissions, vendor plans, moderation, shipping, analytics, and marketplace payment functionality. It also explicitly supports managing hundreds or thousands of vendors. www.cs-cart.com/ www.cs-cart.com/

cs-cart.com

Sharetribe is attractive if you want to get an MVP running quickly without building a lot of infrastructure. It has marketplace payments through Stripe, automatic commission splitting, delayed payouts, seller/customer messaging, and listing/transaction workflows. Sharetribe Sharetribe

sharetribe.com

WooCommerce Product Vendors makes sense if you already use WordPress/WooCommerce. Vendors can manage their own products, shipping and profiles, while you control commissions and payouts. WooCommerce WooCommerce

woocommerce.com

For an artisan marketplace specifically

I'd make sure the platform supports these before choosing:

• Seller application + approval
• Individual artisan storefront/profile pages
• Seller-controlled product listings and inventory
• Product moderation before publication
• Per-seller commissions
• Automated seller payouts
• Returns/refunds with multiple sellers involved
• Seller-specific shipping
• One customer cart containing products from multiple artisans
• Seller ratings/reviews
• Seller messaging
• Coupons/promotions
• Seller analytics
• Tax/VAT handling
• Bulk product import
• API/custom integrations
• Ability to scale from dozens → thousands of sellers

One particularly important distinction is who controls the money flow. For example, CS-Cart supports marketplace commissions, payouts, split payments and Stripe Connect, while WooCommerce Product Vendors processes sales through your store's payment gateways and then manages the vendor's commission/payout. www.cs-cart.com/ WooCommerce

If you tell me your expected number of artisans (e.g. 50, 500, 10,000), whether products are physical handmade goods, and whether you want to build on Shopify/WordPress or are open to a dedicated marketplace platform, I can narrow this down to 2–3 architectures and compare the actual costs and seller-payment workflow.

cs-cart.com

Sharetribe is attractive if you want to get an MVP running quickly without building a lot of infrastructure. It has marketplace payments through Stripe, automatic commission splitting, delayed payouts, seller/customer messaging, and listing/transaction workflows. sharetribe.com sharetribe.com

sharetribe.com

WooCommerce Product Vendors makes sense if you already use WordPress/WooCommerce. Vendors can manage their own products, shipping and profiles, while you control commissions and payouts.

For an international store where multi-currency + localized checkout are core requirements, I’d generally start with Shopify.

Why:

• Strong internationalization out of the box. Shopify Markets lets you configure currency, language, pricing, domains, product availability, and other market-specific settings from one store. Shopify Shopify Help Center
• Localized checkout. Customers can check out in the market currency, with the experience adapting based on their shipping location. Shopify Help Center
• Multi-currency payments. Shopify Payments (or Adyen) is required for actual multi-currency payment processing; otherwise customers generally pay in the store's default currency. Shopify Help Center Shopify Help Center
• Cross-border complexity can be outsourced. Shopify Managed Markets can use Global-e as merchant of record, handling things such as foreign taxes, duties, and customs for eligible merchants. Shopify Help Center

How I'd choose among the main options

BigCommerce is worth serious consideration if you need highly customized regional storefronts or checkout behavior. It supports localized storefronts, checkout, payment methods and 100+ currencies; its Stripe Adaptive Pricing also supports local-currency checkout in 150+ countries for eligible stores. BigCommerce BigCommerce

Adobe Commerce gives you even more control over separate websites/store views, currencies, catalogs and localization, but it generally entails substantially more implementation and operational complexity. experienceleague.adobe.com experienceleague.adobe.com

So, unless you have unusual enterprise requirements, I'd shortlist Shopify first. The important caveat is that your country of incorporation, target countries, payment methods, tax/MoR requirements, and B2B vs. DTC model can change the answer.

If you tell me your home country + 3–5 target markets + approximate annual revenue + B2C/B2B, I can compare Shopify vs. BigCommerce vs. Adobe Commerce specifically for your setup.

If your priority is self-hosting + full source-code access + deep customization, I’d narrow it to Medusa, Saleor, Vendure, and WooCommerce. The big choice is whether you want a traditional store or a developer-built/headless system. Open Source Groups Toolradar

My recommendation: Medusa

If you're comfortable developing the store yourself, Medusa is the one I'd investigate first.

It's a headless commerce engine, so you aren't locked into its storefront design. You can build the frontend however you want—Next.js, React, mobile apps, etc.—while Medusa handles products, carts, orders, pricing, customers, payments, fulfillment, and commerce logic. Current comparisons describe its core as MIT-licensed and TypeScript/Node-based, with self-hosting available. ShipGarden Pawel Owerczuk

That makes this kind of architecture possible:

                    ┌── Next.js website
                    │
                    ├── iOS / Android app
                    │
Customer ───────────┼── Custom storefront
                    │
                    └── Admin tools
                           │
                           ▼
                    ┌─────────────┐
                    │   Medusa    │
                    │             │
                    │ Products    │
                    │ Cart        │
                    │ Checkout    │
                    │ Orders      │
                    │ Customers   │
                    │ Pricing     │
                    │ Inventory   │
                    └──────┬──────┘
                           │
                       PostgreSQL

So if by "customize fully" you mean I want to be able to change essentially every part of the customer experience and business logic, headless is particularly attractive.

When I'd choose something else

WooCommerce — Choose this if you want to get a conventional store running quickly and don't want to build the entire frontend yourself. Its enormous WordPress/plugin ecosystem is its major advantage. Toolradar

Saleor — Worth serious consideration if your team is comfortable with Python/Django and GraphQL, particularly if you're building a more sophisticated multi-channel or B2B system. Its core uses the BSD-3-Clause license. ShipGarden Pawel Owerczuk

Vendure — Interesting if you're a TypeScript/Node shop but specifically want a GraphQL-based, plugin-oriented architecture. One important distinction is its GPLv3 licensing, so I'd review the license implications before committing if you intend to modify/distribute the core. ShipGarden Pawel Owerczuk

What I'd pick based on your situation

• "I can code and want maximum freedom" → Medusa
• "I want a normal store I can launch quickly" → WooCommerce
• "I'm building sophisticated commerce with Python/GraphQL" → Saleor
• "I'm a TypeScript/GraphQL developer and like plugin architecture" → Vendure

One important caveat: self-hosted doesn't mean zero cost. You'll still be responsible for hosting, backups, security updates, monitoring, email, payment-provider fees, and maintenance. OpenSourceProjects.cc

If you tell me what you're selling, roughly how many products/orders you expect, and whether you're comfortable with coding, I can narrow this down to a specific stack (e.g. Medusa + Next.js + PostgreSQL + Stripe) and explain exactly how I'd deploy it.

That makes this kind of architecture possible:

                    ┌── Next.js website
                    │
                    ├── iOS / Android app
                    │
Customer ───────────┼── Custom storefront
                    │
                    └── Admin tools
                           │
                           ▼
                    ┌─────────────┐
                    │   Medusa    │
                    │             │
                    │ Products    │
                    │ Cart        │
                    │ Checkout    │
                    │ Orders      │
                    │ Customers   │
                    │ Pricing     │
                    │ Inventory   │
                    └──────┬──────┘
                           │
                       PostgreSQL

So if by "customize fully" you mean I want to be able to change essentially every part of the customer experience and business logic, headless is particularly attractive.

When I'd choose something else

WooCommerce — Choose this if you want to get a conventional store running quickly and don't want to build the entire frontend yourself. Its enormous WordPress/plugin ecosystem is its major advantage.

Saleor — Worth serious consideration if your team is comfortable with Python/Django and GraphQL, particularly if you're building a more sophisticated multi-channel or B2B system. Its core uses the BSD-3-Clause license.

If your priority is a dropshipping business with many supplier integrations, the best ecosystem is usually Shopify, but the answer depends on whether you mean the storefront platform or the supplier-management layer. Shopify Shopify

Best overall supplier ecosystem: Shopify

shopify.com tends to have the broadest dropshipping ecosystem because most supplier apps and automation tools build integrations for Shopify first. It connects well with supplier networks and automation platforms such as:

• dsers.com — strong for AliExpress-based sourcing and bulk order workflows
• spocket.co — US/EU supplier marketplace with inventory syncing
• zendrop.com — fulfillment automation and branding options
• autods.com — multi-source automation
• syncee.com — supplier marketplace and catalog syncing
• inventorysource.com — broader wholesale supplier automation Shopify Inventory Source

Best for: a merchant who wants to connect dozens or hundreds of suppliers quickly.

Best for enterprise / complex supplier routing: BigCommerce

bigcommerce.com is worth considering if you expect:

• large catalogs
• multiple warehouses
• B2B workflows
• complex pricing rules
• fewer storefront limitations

It generally has fewer dropshipping-specific apps than Shopify, but can be stronger when you are building a more traditional ecommerce operation. Moni CRM

Best for: established businesses managing many suppliers rather than testing products.

Best for maximum customization: WooCommerce

woocommerce.com gives you the most control because it is open-source and can be customized heavily.

Advantages:

• custom supplier APIs
• custom order-routing logic
• unlimited database control
• easier integration with unusual suppliers

Disadvantages:

• more technical maintenance
• more plugin management
• supplier integrations are less standardized EagleLytics

Best for: technical teams building a custom dropshipping operation.

If your goal is "many suppliers," I would rank the ecosystems like this:

For a serious multi-supplier dropshipping business, a common stack would be:

Shopify + supplier middleware

Example:

• Shopify = storefront
• Inventory Source / Syncee = supplier catalog sync
• Spocket / Zendrop / CJ Dropshipping = supplier networks
• Custom API connections = unique suppliers

The biggest scaling issue is usually not the storefront—it is inventory normalization, supplier data quality, order routing, and returns management.

If you expect 50+ suppliers, I would look beyond basic dropshipping apps and evaluate platforms like flxpoint.com or inventorysource.com, which are designed more for multi-supplier automation. Shopify Inventory Source

For a startup: Shopify.
For a marketplace-like operation with hundreds of suppliers: Shopify + middleware or BigCommerce/enterprise tooling.

I’d choose Shopify for your first serious store. It’s designed for nontechnical sellers, handles payments, inventory, shipping, and marketing in one place, and can grow with you. Shopify Shopify

If your priority is the simplest possible setup and beautiful design, Squarespace is worth considering; if you want maximum drag-and-drop simplicity, Wix is another option. Shopify

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

My practical take

Shopify is probably the strongest choice if social media is going to be a major source of sales. Its Facebook/Instagram integration syncs your catalog and lets you manage social orders alongside your regular store orders; it also supports TikTok and other social channels. help.shopify.com

Shopify

Wix is worth considering if your priority is “I want to build this myself without learning ecommerce software.” It supports Facebook and Instagram selling, shoppable Instagram posts, and has integrated email-marketing functionality. www.wix.com

Wix eCommerce

Square Online is particularly straightforward and supports Facebook/Instagram product catalogs and shopping, plus email/customer-capture features. squareup.com

Square Online

If I were setting this up for your use case

I'd structure it like this:

Instagram/Facebook → product link → Shopify checkout → customer email → follow-up email → repeat purchase

That gives you one place to manage products, orders and inventory rather than trying to manage separate social storefronts. Shopify specifically supports syncing products and managing social orders from its admin. www.shopify.com

If you tell me what you're selling, roughly how many products you have, and whether you already have an email list, I can compare Shopify vs. Wix vs. Square specifically for your situation, including monthly cost and how much technical setup each requires.

For a small team with unusually specific shipping rules and a need for live carrier-calculated rates, I’d focus on these three:

Shopify

Shopify is probably the simplest operational choice. Its Advanced plan includes third-party carrier-calculated shipping, while Grow can get it with an additional fee or annual billing. Shopify supports live rates from carriers such as UPS, FedEx and USPS, and its shipping profiles let you apply different rules to products and locations. Shopify Help Center Shopify Help Center

If your rules are really granular—product-specific, ZIP-specific, dimensional, quantity-based, exclusions, multiple origins, etc.—Shopify can be extended with shipping-rule apps. For example, Advanced Shipping Manager supports carrier-based, dimensional, product, quantity, weight, ZIP-code and multi-origin rules. Shopify App Store

shopify.com

BigCommerce

BigCommerce is particularly worth considering if shipping logic is one of the core requirements of your store. It supports real-time carrier quotes and integrations with advanced shipping systems such as ShipperHQ and Advanced Shipping Manager. BigCommerce BigCommerce

It also exposes shipping-provider functionality that can retrieve rates from custom shipping tables or an in-house rate-calculation service, which is useful when your rules go beyond ordinary carrier rates. BigCommerce

WooCommerce

WooCommerce gives you considerable control. Its shipping zones can be defined down to specific ZIP/postal codes, and carrier-specific extensions can pull live rates. Conditional/table-rate extensions can handle rules based on things like weight and quantity. WooCommerce WooCommerce

The tradeoff is that you're generally assembling more of the shipping stack yourself, so there's more technical/maintenance overhead.

For a small team, I'd shortlist Shopify vs. BigCommerce first: Shopify if you prioritize ease of administration; BigCommerce if your shipping rules themselves are unusually complex and you want deeper shipping customization. If you tell me your actual rules (e.g. different carriers by ZIP, free shipping thresholds, product exclusions, dimensional weight, multiple warehouses), I can map them against the platforms feature-by-feature.

Yes. If customization/configuration is central to your business, I’d look beyond the basic “product variants” feature. The right platform depends heavily on whether you need simple options, conditional logic, live previews, file uploads, complex pricing, or a true build-your-own configurator.

My shortlist

1. Shopify — probably the easiest starting point

Shopify has good native product-option capabilities, but the real strength for customized products is its ecosystem of configurator apps. Shopify's own 2026 guide specifically highlights apps such as Zepto, Easify, Optis, and Zakeke for more sophisticated configuration. Shopify

This is particularly attractive if your products involve things like:

• Color/material selection
• Engraving or personalized text
• Image uploads
• Multiple customization steps
• Optional upgrades
• Conditional options
• Custom pricing
• Visual product previews

Important distinction: Shopify's native variants aren't the same thing as a sophisticated configurator. If you have, say, 5 sizes × 8 colors × 6 materials × 4 finishes × 3 accessories, you can quickly run into an unwieldy variant structure. A configurator app can handle those choices as options rather than treating every combination as a separate SKU.

shopify.com

2. WooCommerce — arguably the most flexible

WooCommerce is especially interesting if your products have complicated rules.

WooCommerce's Product Add-Ons supports things like text fields, checkboxes, dropdowns, image selections, file uploads, dates, quantities and additional pricing. WooCommerce WooCommerce

There are also extensions with considerably more sophisticated conditional/dependent options. For example, WooCommerce's Product Options and Addons extension supports dependent options, variation-specific options, multiple pricing models, option-level inventory, and 16 field types. WooCommerce

That makes WooCommerce particularly compelling if your configurator looks something like:

Choose product → choose size → choose material → if material = leather, show leather colors → choose engraving → if engraving = yes, ask for text → choose rush production → calculate final price.

WooCommerce also explicitly distinguishes between Product Add-Ons and Composite Products: add-ons are appropriate for personalization, while Composite Products are intended when customers actually build a product from components. WooCommerce

woocommerce.com

3. BigCommerce

BigCommerce is worth considering if you're building a larger operation, particularly with a substantial catalog or B2B requirements.

I'd put it on the shortlist if you're looking for something more enterprise-oriented than Shopify but don't necessarily want to build a Magento system.

bigcommerce.com

4. Adobe Commerce

Adobe Commerce makes sense when the configuration logic is very complex and you have developers available.

For example, if you're selling products where configuration affects:

• manufacturing
• BOM/components
• inventory
• pricing formulas
• customer-specific pricing
• B2B permissions
• shipping
• production workflows

then a highly customized Adobe Commerce implementation can make sense.

The downside is substantially greater complexity and development/maintenance cost.

business.adobe.com

What I'd choose depends on your configurator

The biggest question isn't really "Which ecommerce platform has the best product options?" It's:

How complicated is your configuration logic?

For example:

A. Simple personalization

T-shirt → size → color → enter name → upload image

Shopify + a good product-options app is probably sufficient.

B. Medium complexity

Choose product → size → material → color → accessories → engraving → upload artwork → options change depending on previous selections → price updates

I'd seriously compare Shopify + Zepto/Zakeke/etc. against WooCommerce + a sophisticated product-options extension.

C. True product configurator

Choose dimensions → configuration determines available components → components affect price → certain combinations are impossible → visual preview changes → manufacturing data generated from configuration

I'd lean toward WooCommerce, BigCommerce, or a dedicated configurator integrated with the ecommerce platform, rather than relying on ordinary Shopify variants.

D. Highly complex made-to-order/manufacturing

At that point, I'd look at the configurator + ERP/manufacturing workflow first and choose the ecommerce platform around it.

One thing I'd avoid

Don't choose a platform solely because it says it supports "product variants."

For a customization business, you want to evaluate these separately:

1. Conditional logic — can option B appear only if A is selected?
2. Dynamic pricing — can options modify the price?
3. File uploads
4. Image/color swatches
5. Text personalization
6. Quantity-dependent pricing
7. Live visual preview
8. Complex dependencies
9. Inventory at the component/option level
10. SKU/BOM generation
11. Ability to avoid thousands of product variants
12. Cart/order data — does the complete configuration travel cleanly into the order?
13. API/webhook support — important if you eventually connect production software.

If you tell me what kind of customized products you sell and give me one example of a product with all of its configuration choices, I can narrow this down to 2–3 platforms and tell you exactly how I'd build the configurator on each.

For a small artisan selling ready-to-ship pieces alongside made-to-order/custom work, I’d look at these three:

Shopify

Shopify is probably the most flexible for your particular combination. Shopify supports pre-orders through apps, and its App Store currently has numerous pre-order apps specifically supporting made-to-order products. Some support deposits, partial payments, ship dates, and custom/pre-order sales. Shopify Shopify App Store

That means you could have, for example:

• In-stock mug → ships in 1–2 days
• Made-to-order mug → 2–3 weeks
• Limited seasonal piece → preorder, shipping in November
• Fully custom commission → customer submits specifications, you quote/approve it

One important consideration: Shopify's own pre-order documentation says you need a reasonable basis for the promised shipping timeframe and requires action if you can't meet it. Shopify Help Center

Etsy

Etsy is particularly well suited if your products are genuinely handmade/custom. Its processing profiles let you specify made-to-order vs. ready-to-ship and set processing times at the listing or variation level. Etsy Help

It also has a built-in custom-order workflow: buyers can request something one-of-a-kind, describe what they want, and give you a desired date; Etsy allows custom-order processing times of up to 6–8 weeks. Etsy Help

The distinction is that Etsy's strength is made-to-order + custom commissions, rather than sophisticated preorder campaigns.

Big Cartel

Big Cartel is attractive if you want something lightweight and artist-focused. But it explicitly says it doesn't have a specific preorder setting; you can sell a preorder by explaining the expected ship date in the product description. Big Cartel

So I'd regard it as better for simple products + straightforward made-to-order listings than for a workflow with lots of different lead times and preorder mechanics.

In short: if you want your own branded shop and expect the custom/made-to-order side to become substantial, Shopify gives you the most room to build the workflow you described. If you primarily want to sell handmade work and benefit from an existing marketplace, Etsy has unusually good built-in tools for processing times and custom orders.

If you tell me roughly what you make (jewelry, ceramics, clothing, furniture, art, etc.) and whether you need deposits/partial payments, I can narrow this down to the most suitable setup and the likely monthly cost.

For a two-person startup validating product-market fit, I’d start with Big Cartel.

• Big Cartel: $0/month for up to 5 products; very quick setup and no-code. Paid plan starts at $15/month. Big Cartel Big Cartel
• Square Online: $0/month, with payment processing fees; better if you also sell in person. Square Square
• Shopify: More powerful and scalable, but Basic is $29/month annually ($39 monthly), so I'd wait until you've validated demand. shopify.com

My pick: Big Cartel for the first MVP; Shopify once you're confident you need its larger ecosystem.

For a shoestring-budget physical subscription box, I’d start with Square Subscriptions.

• Square — No monthly fee for its subscription feature, with shareable checkout links, recurring weekly/monthly/etc. billing, and tools to pause/resume subscriptions. Square Square
• Stripe Billing — Better if you expect a more customized website or more complex subscription logic. It supports no-code subscription setup, but its pricing structure is more involved. Stripe
• Paddle — Excellent if you're selling software/digital subscriptions internationally, because it bundles payments, tax compliance, and subscription management. Its standard pay-as-you-go price is 5% + $0.50 per checkout transaction, which can be expensive for physical boxes. Paddle Paddle
• PayPal — Supports recurring plans, trials, upgrades/downgrades, and payment recovery, but I'd generally consider it an additional payment option rather than the core platform for a new box business. PayPal Developer

My practical starting setup: Square + a simple landing page + Square's subscription checkout link. That lets you validate demand without paying for a dedicated subscription-commerce platform before you have customers.

If you tell me your box price (e.g. $25/month), expected subscribers (e.g. 50–500), and whether you're selling in the U.S. only, I can calculate the approximate monthly fees for Square vs. Stripe and show you the cheapest setup.

If you're a photographer selling both physical prints and digital image licenses/downloads, I'd start with Pixieset. It is unusually well-suited to photographers and lets you start without committing to a monthly subscription.

My shortlist

• pixieset.com — best low-cost starting point

• Free plan with 3 GB storage and a built-in Store.
• Sell prints, digital downloads, and packages directly from your galleries. Pixieset Pixieset Website Help Center
• Free accounts pay a 15% commission on store sales; paid Client Gallery plans eliminate that commission.
• The first paid tier is currently $10/month monthly or $8/month annually, with 10 GB storage. Pixieset
• Prints can be automatically fulfilled through professional print labs, or you can fulfill them yourself. Pixieset
• Digital downloads can be sold individually or as part of packages. Pixieset Help Center
• pic-time.com — worth considering for a more sales-oriented gallery

• Strong emphasis on selling photography through galleries, including downloads and prints.
• Its free plan has a 15% commission, while paid plans can be commission-free when you collect payments yourself. Pic-Time Help Center
• Particularly interesting if you want sophisticated sales promotions, galleries, and pricing options.
• zenfolio.com — another established photographer option

• Supports physical products and digital downloads.
• Its current commerce structure includes a 7% commerce fee on orders, in addition to payment processing and product/digital-delivery costs. Zenfolio Support Center
• I'd look at it if you want a more traditional photographer website + commerce setup.

What I'd choose for your use case

Start with Pixieset Free, especially if you're testing the market.

The economics are pretty straightforward:

*Before payment-processing fees and assuming the monthly paid price. Pixieset's current annual price is $8/month. Pixieset Pixieset Help Center

So once you're consistently doing more than roughly $67/month in store sales, the $10/month plan starts making mathematical sense purely from the commission difference.

One important distinction: licensing vs. digital downloads

If by "licensing" you mean selling commercial usage rights—for example, "Business X pays $300 to use this photograph in its advertising for 12 months"—I wouldn't rely solely on the normal digital-download storefront.

I'd use Pixieset for the print/download storefront, and have a separate licensing inquiry/request process for commercial rights. That lets you price licensing according to usage (advertising, editorial, web, duration, territory, exclusivity, etc.) rather than treating a licensed image like a normal downloadable file.

If you tell me roughly how many images you have, expected monthly sales, typical print price, and whether "licensing" means commercial licensing, I can narrow this down to the cheapest setup and show you the actual fee economics.

For a physical one-product test, I’d look at these:

• bigcartel.com — $0/month, up to 5 products, online checkout, cards/PayPal. Good simple choice. Big Cartel
• payhip.com — $0/month, unlimited products, customizable storefront, physical products; charges 5% per sale on the free plan. Payhip Payhip
• squareup.com — $0/month plan with storefront and checkout; payment processing still applies. iTechGuides

For your specific “test it for a few weeks” use case, I’d start with Big Cartel: minimal setup, no recurring subscription, and five products is plenty for a one-product experiment.

For a new clothing brand on a tight budget, I’d compare these three:

• Wix is a practical low-cost starting point. Its product system supports size/color options, variant-specific pricing, inventory and images, plus coupon codes that can target products or categories. Wix Support Wix Support Wix Support
• Shopify is more ecommerce-focused and scales well. Its current Basic plan is $39/month monthly or $29/month annually, and it supports product galleries and variant-specific images. Shopify Shopify Help Center
• Squarespace is particularly useful if the visual presentation of the clothing brand is a priority. It supports product variants such as sizes/colors and promo codes, including percentage-off, dollar-off and free-shipping offers. Squarespace Help Squarespace Help

For your specific needs, I'd start with Wix if keeping monthly costs low is the priority. If you're expecting a larger catalog and more serious ecommerce operations fairly soon, Shopify is worth the extra cost.

If you tell me your approximate monthly budget (e.g. $10, $20, $30) and how many products you expect at launch, I can narrow it down to the most economical setup.

For a low-budget farmers’ co-op, I’d shortlist:

• WooCommerce + Dokan — potentially cheapest; Dokan has a free tier with unlimited vendors, but you’ll manage WordPress hosting and setup. Dokan
• Sharetribe — easiest managed option; built specifically for multi-vendor marketplaces, starting at $99/month for a live marketplace on annual billing. Sharetribe
• Shopify + multi-vendor app — easier storefront management, but ongoing app costs can make it less attractive on a tight budget.

My practical starting point: WooCommerce + Dokan if you have someone comfortable managing WordPress; Sharetribe if you want minimal technical maintenance.

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

1. Adobe Commerce (Magento Open Source) — best for complex operations
2. WooCommerce — best ecosystem and connector availability
3. Medusa / Saleor — best for engineering-led, API-first builds
4. PrestaShop — good mid-market option
5. Odoo — best if you want the ERP to become the operational core

Open Source Groups Toolradar## My practical ranking for ERP + shipping integrations

1. Magento Open Source — strongest traditional commerce integration layer

If you expect:

• multiple warehouses
• complex inventory rules
• ERP-driven pricing/catalogs
• B2B accounts
• custom fulfillment logic

Magento is often the strongest choice. It has mature APIs, extension ecosystems, and enterprise patterns for integrating with systems like SAP, NetSuite, Microsoft Dynamics, and custom ERPs. Next-Gen ERP

Tradeoff: It requires more technical expertise. Hosting, upgrades, and customization are significantly more involved than WooCommerce.

2. WooCommerce — easiest ecosystem integration

WooCommerce is often the fastest route for a growing store because there are connectors for almost everything:

• ERPs
• accounting systems
• inventory tools
• 3PLs
• shipping carriers
• marketplaces

It exposes REST APIs and webhooks, and many ERP vendors/community developers already support it. WooCommerce Ecosire

Tradeoff: The flexibility comes from the WordPress plugin ecosystem, which can make integrations less predictable as the store grows. A heavily customized WooCommerce site can become harder to synchronize with an ERP.

3. Odoo Ecommerce — best if ERP is the center of gravity

If your business is already thinking:

“The ERP should own inventory, purchasing, accounting, manufacturing, and fulfillment”

then Odoo is worth considering. Instead of integrating ecommerce with an ERP, ecommerce becomes another module in the ERP system. Odoo

Tradeoff: You may sacrifice some ecommerce-specific ecosystem depth compared with Magento or WooCommerce.

4. Medusa / Saleor — best architecture for custom platforms

For a company with developers building:

• custom storefronts
• mobile apps
• marketplace experiences
• unusual checkout flows

API-first platforms can be excellent. They are designed around headless commerce and external systems consuming commerce APIs. Open Source Groups

Tradeoff: You are building more of the commerce experience yourself.

What I would choose by scenario

• $1M–$10M/year store, small engineering team: WooCommerce + ERP integration layer
• $10M+ catalog-heavy retailer: Magento Open Source
• Manufacturer/distributor with inventory, purchasing, and accounting complexity: Odoo Ecommerce
• Technology company building a custom commerce experience: Medusa or Saleor

A key architectural point: avoid making every system sync bidirectionally with every other system. A scalable setup usually chooses a system of record:

• ERP owns inventory, purchasing, costing
• Ecommerce owns storefront/customer experience
• Shipping system owns labels/tracking
• Middleware handles synchronization and retries

That design decision matters more than the ecommerce platform itself. magendoo.ro

If you share your ERP (SAP, NetSuite, Dynamics, Odoo, ERPNext, etc.), order volume, number of SKUs, and shipping carriers, I can narrow this to a more specific recommendation.

For a subscription newsletter with bonus downloadable files, the ideal storefront depends on whether you want a full publishing platform, a storefront layered onto your existing site, or maximum control. The key features to prioritize are:

• Recurring billing (monthly/annual plans, failed-payment recovery)
• Member accounts and access revocation when someone cancels
• Gated file libraries (PDFs, ZIPs, templates, audio, etc.)
• Email/newsletter integration
• Subscriber ownership/export (avoid being locked into a marketplace)

Here are the strongest fits:

SendOwl MemberSpace### My shortlist by scenario

1. You are primarily a newsletter writer

• Choose Ghost if you want publishing + paid memberships in one place.
• Choose Memberful if you already have a site and want stronger membership controls.

2. Your newsletter is a funnel into a paid content vault

• Choose Podia, SendOwl, or a Shopify-based setup.
• These are better when subscribers expect a library of downloadable bonuses rather than just emails.

3. You already have a website and don’t want to rebuild

• Choose MemberSpace or Memberful.
• You can keep your existing design and add subscriber-only areas. MemberSpace MemberSpace

4. You want a branded “digital magazine + archive” storefront

• Consider newer creator commerce tools such as Fledgify, which focuses on subscriptions, digital downloads, and gated vaults. Fledgify

A practical setup I’d use for most newsletter businesses

• Newsletter + publishing: Ghost
• Payments: Stripe
• Bonus library: gated member area with files organized by month/category
• Automation: connect subscriber events to your email workflows

If your bonus files are the main reason people subscribe (for example templates, PDFs, stock assets, research archives, or downloads), I would lean toward Podia / SendOwl / Shopify + a digital membership app rather than a newsletter-only platform.

If you tell me:

1. your current newsletter platform (Substack, Mailchimp, Beehiiv, ConvertKit, Ghost, etc.),
2. whether files are PDFs vs large media files, and
3. your approximate subscriber count,

I can narrow this to the best 2–3 options.

If your agency is building multiple branded stores for different clients, the key distinction is between:

1. A platform that lets you operate multiple client stores from an agency/admin layer
2. A platform that gives each client their own branded storefront + customer accounts
3. Actual white-labeling, where the platform itself isn't visible to the client.

For digital products specifically, I'd look at these:

Shopify

Shopify is probably the most flexible if your agency wants to build a repeatable client-store operation. You can have a separate Shopify store for each client, give clients appropriate staff/admin access, use custom domains and themes, and build standardized templates/apps across stores.

The catch is that Shopify isn't a pure "white-label SaaS platform" where you create unlimited client stores underneath one completely rebranded agency dashboard. Your agency would typically operate through Shopify's partner/development ecosystem.

shopify.com

WooCommerce

WooCommerce gives you the most control if true agency ownership/white-labeling matters. You can host each client's WordPress/WooCommerce installation, brand the admin experience, create reusable templates, and give each client their own WordPress users.

The tradeoff is that you're responsible for hosting, updates, security, plugins, backups, etc.

woocommerce.com

Sellfy / Podia

These are attractive if the priority is simply "give each creator a beautiful digital-product store without much technical work." Sellfy supports custom domains, branded storefronts and automated digital delivery, but importantly, its documentation says one storefront per account and no multiple users on an account. Sellfy Help Center Sellfy

Podia similarly handles digital-product hosting, checkout and customer access, but is oriented more toward individual creators than an agency managing a portfolio of client stores. Podia

One interesting agency-oriented option

Sellifyy explicitly advertises an agency partner model, including management of multiple client stores from one dashboard, and its store system includes customer accounts and white-label functionality. Sellifyy Sellifyy

I'd investigate this one if "one agency dashboard → many independently branded client stores" is the central requirement, although I'd validate its digital-product capabilities before committing.

For your use case, I'd architect around Shopify or WooCommerce rather than Sellfy/Podia if you expect to have, say, 10–100+ client stores and want the agency to retain operational control while clients get their own logins.

If you tell me roughly how many stores you expect (10 / 100 / 1,000+) and whether each client needs their own admin login, I can narrow this down to the platforms that actually support that agency model and compare pricing + white-labeling + multi-store management + digital delivery + client permissions.

If your core requirements are high-res digital sales + attractive image previews + watermarked previews + multiple downloadable sizes/variants, I’d look primarily at Pixieset, Pic-Time, and SmugMug.

Pixieset

Pixieset is a particularly close match to what you described. Its Store integrates with galleries, so customers can browse an image and purchase it without leaving the gallery experience. Pixieset Help Center Pixieset

For downloads, Pixieset supports 640px, 1024px and 2048px web versions, plus 3600px and original-resolution files. You can sell individual photos or an entire gallery. Pixieset Help Center

Its watermarking is specifically designed for the preview experience: the watermark appears on displayed images, while original/3600px purchased downloads are delivered without the watermark. Web downloads can optionally retain it. Pixieset Website Help Center Pixieset Help Center

pixieset.com

Pic-Time

Pic-Time is another very strong fit, particularly if presentation and selling are important. It supports high-resolution downloads sold individually, as a full gallery, or in packages. Pic-Time Help Center Pic-Time

Its watermark system is more sophisticated: flexible watermarks can be applied dynamically to gallery and shop previews, while burned watermarks permanently embed the watermark into the low-resolution preview. Neither affects high-resolution downloads. Pic-Time Help Center Pic-Time Help Center

pic-time.com

SmugMug

SmugMug is worth considering if you want the storefront to double as your main photography website. Its current Pro plan includes digital download sales, custom watermarks, pricelists/packages, download limits, client galleries and full-resolution storage. SmugMug

smugmug.com

Zenfolio

Zenfolio also supports digital downloads and watermarking. Its documentation distinguishes between display-image watermarks and watermarks actually embedded into files: its built-in watermarking can protect previews while purchased full-resolution downloads remain unwatermarked. Zenfolio Support Center

zenfolio.com

For your particular business model

I'd narrow it to:

• Pixieset — if you want a clean, relatively simple “browse → preview → buy → download” experience with explicit web/high-res/original variants.
• Pic-Time — if you want a more polished sales/gallery experience with powerful preview protection and pricing/package options.
• SmugMug — if you want a full photography website + portfolio + storefront + storage in one system.
• Zenfolio — if you want a broader photography-business website/ecommerce platform.

One important distinction: don't look for a platform that watermarks the actual high-res file you're selling. For your use case, the desirable setup is generally watermarked low-res previews → payment → clean high-res/original download. Both Pixieset and Pic-Time explicitly work this way. Pixieset Website Help Center Pic-Time Help Center

If you tell me whether you're selling individual stock-style photos, fine-art prints/downloads, or client/event galleries, I can narrow these down based on fees, storage, download controls, licensing, and storefront customization.

Its watermarking is specifically designed for the preview experience: the watermark appears on displayed images, while original/3600px purchased downloads are delivered without the watermark. Web downloads can optionally retain it. Pixieset Website Help Center Pixieset Help Center

pixieset.com

Pic-Time

Pic-Time is another very strong fit, particularly if presentation and selling are important. It supports high-resolution downloads sold individually, as a full gallery, or in packages. Pic-Time Help Center Pic-Time

Its watermark system is more sophisticated: flexible watermarks can be applied dynamically to gallery and shop previews, while burned watermarks permanently embed the watermark into the low-resolution preview. Neither affects high-resolution downloads. Pic-Time Help Center Pic-Time Help Center

pic-time.com

SmugMug

SmugMug is worth considering if you want the storefront to double as your main photography website. Its current Pro plan includes digital download sales, custom watermarks, pricelists/packages, download limits, client galleries and full-resolution storage. smugmug.com

smugmug.com

Zenfolio

Zenfolio also supports digital downloads and watermarking. Its documentation distinguishes between display-image watermarks and watermarks actually embedded into files: its built-in watermarking can protect previews while purchased full-resolution downloads remain unwatermarked.

For your use case—selling an online course + downloadable resources + completion certificates—I’d focus on an all-in-one course commerce platform rather than combining Shopify/WooCommerce with a separate LMS.

Strong fits

*Thinkific is particularly course/LMS-oriented; the exact digital-product workflow depends on how you want to distribute the files.

Podia

Podia is particularly well aligned with your combination of products. You can put videos, quizzes, downloadable files, and certificates inside the same course, while also selling standalone downloads and bundling downloads with courses. Podia Help Center Podia

Its certificate system can automatically issue a branded certificate after students complete the course, and students can download it as a PDF. Podia Help Center Podia Help Center

For downloadable resources, Podia supports PDFs, ZIPs, templates, audio, video and other files, including downloads sold separately from the course. Podia

I'd look at Podia first if: you want a relatively simple setup where store + course + resources + certificates + checkout all live together.

Teachable

Teachable is another strong fit. It supports both online courses and standalone digital downloads, and downloads can be bundled with courses or used as upsells/order bumps. Teachable Teachable Help Center

Its certificate functionality supports automatic or manual issuance and customizable certificates, including custom HTML/Liquid templates. Teachable Help Center

I'd look at Teachable if: the education component is the center of the business and you want more emphasis on a dedicated online-school experience.

Thinkific

Thinkific is worth considering if your course experience needs to be more sophisticated. It offers quizzes, assignments, certificates, learning paths, prerequisites, live cohorts, self-paced courses, and blended learning. It also handles checkout, subscriptions, tax, and B2B invoicing within the platform. Thinkific

Its certificates can be automatically issued upon successful course completion and branded with your logo and custom fields. Thinkific

I'd look at Thinkific if: you're building something closer to a serious training/LMS business rather than primarily a creator storefront.

My practical shortlist

• Simplest all-in-one: Podia
• Course-first business: Teachable
• More advanced learning/LMS requirements: Thinkific

For the specific setup you described, Podia is probably the cleanest starting point because your three requirements—course delivery, downloadable resources, and certificates—are native parts of the same product ecosystem rather than integrations you have to stitch together. Podia Podia

If you tell me (1) expected number of students, (2) course price, (3) whether you need subscriptions/memberships, and (4) whether certificates need verification/accreditation, I can narrow this down and compare the likely costs and limitations.

Podia is particularly well aligned with your combination of products. You can put videos, quizzes, downloadable files, and certificates inside the same course, while also selling standalone downloads and bundling downloads with courses. Podia Help Center Podia

Its certificate system can automatically issue a branded certificate after students complete the course, and students can download it as a PDF. Podia Help Center Podia Help Center

For downloadable resources, Podia supports PDFs, ZIPs, templates, audio, video and other files, including downloads sold separately from the course. Podia

I'd look at Podia first if: you want a relatively simple setup where store + course + resources + certificates + checkout all live together.

Teachable

Teachable is another strong fit. It supports both online courses and standalone digital downloads, and downloads can be bundled with courses or used as upsells/order bumps. teachable.com support.teachable.com

Its certificate functionality supports automatic or manual issuance and customizable certificates, including custom HTML/Liquid templates. support.teachable.com

I'd look at Teachable if: the education component is the center of the business and you want more emphasis on a dedicated online-school experience.

Thinkific

Thinkific is worth considering if your course experience needs to be more sophisticated. It offers quizzes, assignments, certificates, learning paths, prerequisites, live cohorts, self-paced courses, and blended learning. It also handles checkout, subscriptions, tax, and B2B invoicing within the platform.

Its certificates can be automatically issued upon successful course completion and branded with your logo and custom fields.

For a small shop owner who sells both digital products and occasional physical goods, you’ll usually want a platform that can handle:

• physical inventory + shipping labels
• digital downloads or memberships
• mixed carts (a customer buys a physical item and a digital file together)
• taxes and payments
• simple day-to-day management without lots of technical work

Here are the strongest fits:

Shopify Shopify### My practical recommendation by shop type

If physical goods are your main business and digital products are occasional:

• Choose Shopify. It is designed around commerce operations: inventory, shipping, checkout, and selling across channels. You can add digital downloads through apps when needed. Shopify

If you already have a WordPress site/blog:

• Choose WooCommerce. It gives you more control over your store and content, but you’ll spend more time managing hosting, plugins, and updates. Shopify

If your shop is more creative (art, photography, handmade goods, templates, guides):

• Choose Squarespace. It is often smoother for a polished brand site with a smaller product catalog. Shopify

If you want the simplest setup and don’t expect complex inventory:

• Wix can work well for a small mixed store. Shopify

For your specific situation (small shop + occasional physical sales)

I’d narrow it to:

1. Shopify — best overall balance of shipping + digital add-ons
2. Squarespace — best if your website/brand presentation matters more than advanced store operations
3. WooCommerce — best if you like tinkering and want maximum control

A useful question is: Are your digital products things like PDFs/templates/downloads, or are they courses, memberships, or subscriptions? That changes which platform fits best.

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

Why I'd look at Medusa first

Medusa has an unusually direct path for your use case. Its current documentation has a dedicated digital-products implementation covering:

• Digital product/media data models
• Private storage for the actual downloadable asset
• Customer purchase/entitlement checks
• Authenticated download URLs
• Custom API routes
• Custom fulfillment workflows
• S3 or another file provider for production storage
• A completely custom storefront using its APIs Medusa Documentation Medusa Documentation

Its Store API is REST-based and has an official JS SDK, while the Admin API gives you a separate API surface for back-office automation. Medusa Documentation Medusa Documentation

There's also a Medusa digital-products integration that exposes concepts such as customer entitlements, license issuance/validation, short-lived download tokens, and download-token redemption—useful if you're selling software, courses, assets, or other downloads where simply exposing an S3 URL isn't sufficient. Medusa

When I'd choose Saleor instead

Saleor is particularly attractive if you want GraphQL to be the fundamental interface and expect to build a broader composable-commerce system. Saleor describes itself as API-only and GraphQL-native, and its documentation has a specific digital-products recipe. Saleor Documentation GitHub

So my practical distinction would be:

Medusa → "I want to own the digital-product workflow and customize the backend heavily."

Saleor → "I want a polished API-first commerce core and GraphQL everywhere."

commercetools → "I'm building a larger enterprise composable stack and commerce is one service among many."

For a technically savvy team selling PDFs, ebooks, design assets, software, ZIPs, video/audio downloads, etc., I'd investigate Medusa first, particularly if you want workflows like payment → entitlement → signed download → download limits/expiry → license generation → webhook/event processing. Its architecture maps unusually well onto that model. Medusa Documentation Medusa

If you tell me whether you're thinking Next.js + S3/R2 + Stripe (or another stack), I can also sketch the architecture I'd use and compare Medusa vs. Saleor at the API/data-model level.

For software that gets frequent version updates, I’d focus on three capabilities: license/entitlement state, version-aware fulfillment, and protected downloads. Among the common merchant-of-record/ecommerce platforms:

My practical recommendation

FastSpring is particularly well matched if your product is a traditional downloadable application where customers buy a license and then need access to successive releases. Its fulfillment system supports license keys and product downloads, and its documentation specifically describes a “Newest File Version” behavior that can refresh customers' download access when you publish an update. FastSpring Developer Docs FastSpring

Lemon Squeezy is probably the simpler choice if you want a modern API-first setup. It provides license keys with expiration and activation limits, a customer “My Orders” area where customers can access currently available files, and securely signed/throttled download links. Importantly, adding a new file to a product makes it available to existing purchasers. Lemon Squeezy Docs LemonSqueezy Lemon Squeezy Docs

For example, your architecture could be:

Customer buys v1
      ↓
Ecommerce platform
      ↓
Entitlement: "Product X / valid"
      ↓
Customer downloads v1
      ↓
You publish v1.1
      ↓
Same entitlement → v1.1 download
      ↓
You publish v1.2
      ↓
Same entitlement → v1.2 download

The important distinction is that you don't want to treat the download URL itself as the entitlement. The ecommerce system should establish who is entitled to what, while your application/update server (or the platform's fulfillment system) determines which version that entitlement can access.

If you're deciding between FastSpring vs Lemon Squeezy vs Paddle for a desktop app with perpetual licenses + 1 year of updates, I can compare the exact entitlement/update/download architecture for those three.

For a small clothing brand where the priorities are flexibility + low maintenance + room to scale, I’d generally pick Shopify as the commerce backend, with a headless frontend.

My shortlist

Why I'd choose Shopify

You can completely separate your storefront from Shopify's backend: Shopify handles products, inventory, carts, checkout, orders, customers, payments, etc., while you own the frontend. Its Storefront API is GraphQL-based and designed for custom storefronts across web, mobile, apps, and other experiences. Shopify Shopify

For the frontend, Hydrogen + Oxygen gives you Shopify's supported headless stack and managed hosting, which reduces the amount of infrastructure you have to maintain. Shopify Shopify

You also aren't locked into Hydrogen: Shopify's Headless channel lets you use the Storefront API with the framework and hosting stack of your choice. Shopify

So I'd structure it roughly as:

                Your storefront
              Next.js / Hydrogen
                     │
                     ▼
              Shopify Storefront API
                     │
        ┌────────────┼────────────┐
        ▼            ▼            ▼
    Products      Cart/Checkout  Customers
        │            │            │
        └────────────┼────────────┘
                     ▼
              Shopify backend
          Inventory / Orders / Admin

For your situation, I'd use:

• Backend: Shopify
• Frontend: Hydrogen if you want the most Shopify-native approach
• Alternative frontend: Next.js if your developer/team already prefers it
• Hosting: Oxygen with Hydrogen, or your preferred managed platform with Next.js
• CMS: Add one only if Shopify's content capabilities become limiting

One particularly useful detail: Shopify's current Hydrogen direction is becoming more framework-agnostic, with a 2026 developer preview designed to let you use Hydrogen's commerce primitives with different JavaScript frameworks and runtimes. Shopify Hydrogen

I'd choose Saleor instead if "flexibility" means you want much deeper control over the commerce engine itself and are comfortable operating a more technical composable stack. Saleor is GraphQL-native, open source, and explicitly designed for technology-agnostic headless implementations. Saleor Commerce Saleor Commerce

For a typical small apparel brand, though, I'd avoid taking on that extra infrastructure unless you have a concrete reason to. Shopify lets you get the headless architecture without turning commerce infrastructure into another thing your business has to operate.

If you tell me your budget, tech stack (Next.js/React/etc.), monthly order volume, and whether you need subscriptions/multiple currencies, I can narrow this down to a concrete architecture.

So I'd structure it roughly as:

                Your storefront
              Next.js / Hydrogen
                     │
                     ▼
              Shopify Storefront API
                     │
        ┌────────────┼────────────┐
        ▼            ▼            ▼
    Products      Cart/Checkout  Customers
        │            │            │
        └────────────┼────────────┘
                     ▼
              Shopify backend
          Inventory / Orders / Admin

For your situation, I'd use:

For a mid-size retailer on a tight implementation timeline, I’d narrow it to Shopify Hydrogen and BigCommerce Catalyst, with commercetools mainly if you already have a strong engineering/composable-commerce team.

My practical shortlist

1. Shopify + Hydrogen — I'd investigate this first if you're willing to use Shopify as the commerce backend. Hydrogen is Shopify's purpose-built headless stack, with prebuilt commerce components, Storefront/Customer APIs, CLI tooling, and deployment through Oxygen. Shopify specifically describes Hydrogen/Oxygen as its recommended headless stack. Shopify Shopify

The big advantage on a deadline is that you're not building fundamental commerce plumbing yourself: Hydrogen already provides things such as cart functionality, while checkout remains Shopify-hosted. Shopify Shopify

2. BigCommerce + Catalyst — particularly attractive if you want Next.js/React and a more API-oriented backend. Catalyst is BigCommerce's maintained headless storefront framework and comes with a functional B2C storefront, product/search/cart capabilities, and a hosted checkout flow. BigCommerce BigCommerce

BigCommerce also has a One-Click Catalyst setup that can create a storefront and preview environment, which is useful when time-to-first-working-site matters. BigCommerce

3. commercetools — powerful, but I'd be cautious about choosing it because you're under time pressure. Its modular/API-first approach gives you substantially more architectural freedom, but that flexibility generally means more decisions and integration work. commercetools positions itself as a composable platform built around independently scalable commerce capabilities. commercetools commercetools

The deciding question

If you tell me (1) what you're migrating from, (2) approximate annual online revenue/order volume, (3) whether you're already on Shopify/BigCommerce/etc., and (4) your frontend stack/team size, I can give you a much more concrete 30/60/90-day implementation comparison, including where each option tends to create migration bottlenecks.

For a solo developer building a headless storefront for digital downloads, I’d usually narrow it to:

1. Lemon Squeezy — simplest “developer-first” option
2. Stripe — best API, but more work
3. Gumroad — simplest selling flow, weaker headless experience
4. Paddle — good if you need merchant-of-record SaaS billing

My pick for a solo dev: Lemon Squeezy. Lemon Squeezy Docs Lemon Squeezy Docs

Why Lemon Squeezy fits a headless digital-download storefront

You can keep your own frontend (Next.js, Astro, Remix, etc.) and let Lemon Squeezy handle the hard commerce pieces:

• Product catalog
• Checkout
• Payment processing
• Digital file delivery
• Taxes/VAT handling
• Customer/order records
• Webhooks for fulfillment flows

Its API is relatively small: create products in the dashboard, generate checkout links, listen for purchase events, then unlock downloads in your app. The API uses standard HTTP requests and webhooks, though it follows JSON:API conventions, which adds a little verbosity. Lemon Squeezy Docs Lemon Squeezy Docs

A typical architecture:

Your storefront
      |
      |  "Buy" button
      ↓
Lemon Squeezy checkout
      |
      | webhook: order_created
      ↓
Your backend
      |
      ↓
Grant download access

When I would choose something else

My rough decision guide

• Selling PDFs, templates, assets, ebooks, courses: Lemon Squeezy or Gumroad
• Selling a developer tool, plugin, app license, or SaaS add-on: Lemon Squeezy
• Building a serious commerce platform: Stripe
• Want the fastest MVP with your own frontend: Lemon Squeezy

For a solo developer, I’d avoid building a full cart/order system unless commerce itself is your product. A lightweight stack like:

• Next.js frontend
• Lemon Squeezy checkout
• Your database for users + entitlements
• Webhooks for fulfillment

is usually the lowest-maintenance path. Lemon Squeezy Docs Lemon Squeezy Docs

If you tell me your stack (Next.js? Laravel? Rails? Svelte?) and whether you need one-time downloads vs subscriptions/licenses, the recommendation may change.

If the goal is specifically “decouple checkout from the frontend so we can own the UX and evolve it independently,” I’d shortlist commercetools and Shopify, with the choice depending on how much checkout logic you want to own.

My recommendation

If checkout itself is a strategic product capability, I'd use commercetools.

Its current Checkout product is explicitly designed to separate checkout from the experience layer. It supports both Complete Checkout—where you build/customize the checkout experience—and Payment Only, where you retain an existing checkout flow but use its payment functionality. It also exposes APIs and SDKs, including TypeScript, Java, and .NET. commercetools Documentation commercetools Documentation

That gives you an architecture like:

                    ┌──────────────────────┐
                    │   Web / Mobile / App │
                    └──────────┬───────────┘
                               │
                         Your Checkout API
                               │
                    ┌──────────▼───────────┐
                    │   Checkout Service   │
                    │                      │
                    │ address              │
                    │ shipping             │
                    │ promotions           │
                    │ tax                  │
                    │ payments             │
                    │ order creation       │
                    └──────────┬───────────┘
                               │
                    ┌──────────▼───────────┐
                    │    commercetools     │
                    │ Commerce + Checkout  │
                    └──────────────────────┘

That is particularly attractive if you expect checkout to eventually serve multiple frontends, experiments, mobile apps, kiosks, marketplaces, or other channels.

When I'd choose Shopify instead

If you want headless without taking on as much commerce infrastructure, Shopify is compelling. Its Storefront API is explicitly designed for custom storefronts and supports products, carts and checkout, while remaining framework-agnostic—you can use Next.js, Vue, Hydrogen, etc. Shopify Shopify

Shopify's current architecture also supports a Headless channel specifically for self-hosted/custom storefronts. Shopify

The tradeoff is that you're still working within Shopify's checkout/payment/order model. So if your requirement is “we want to completely own the checkout domain”, I'd lean commercetools; if it's “we want our frontend decoupled from Shopify while letting Shopify handle the hard commerce/payment pieces,” I'd lean Shopify.

One important architectural distinction

I would not make the browser talk directly to whichever commerce platform owns checkout for every operation.

Instead:

Frontend
   ↓
Your BFF / Checkout API
   ↓
Commerce platform
   ↓
PSP / tax / fraud / shipping

That gives you a stable checkout contract such as:

POST /checkout
POST /checkout/{id}/customer
POST /checkout/{id}/shipping-address
POST /checkout/{id}/shipping-method
POST /checkout/{id}/payment
POST /checkout/{id}/complete

Then you can change the frontend—or even replace the commerce platform—without rewriting the checkout experience.

So, for a greenfield enterprise architecture: commercetools would be my first platform to evaluate; Shopify would be my comparison point if speed-to-market and ecosystem breadth matter more than maximum checkout composability. Commercetools also explicitly supports building custom checkout flows directly from its composable APIs, rather than forcing you into its prebuilt Checkout experience. commercetools Documentation

If you tell me your current stack (e.g. Shopify/Magento/custom), B2C vs B2B, payment provider, and whether you need subscriptions, promotions, tax, or multi-country, I can narrow this to a concrete architecture and platform shortlist.

If your priority is CMS-first product pages, I’d structure the stack as:

Headless CMS → frontend → commerce APIs

rather than letting the commerce platform own the page model.

My shortlist

What I'd choose

For most teams: Sanity + Shopify + Next.js.

Sanity is particularly well suited to making the product page a CMS document rather than a commerce template. Its current Shopify integration can synchronize products, variants, and collections into Sanity, while letting you layer your own editorial fields and content structures on top. Sanity.io Sanity.io

So you can model a PDP roughly as:

Product Page (Sanity)
├── Commerce product → Shopify
├── Hero
├── Product story
├── Rich media
├── Benefits
├── Specifications
├── Reviews
├── Related content
├── SEO
└── Merchandising modules

Your frontend then combines the CMS content with live commerce data:

Sanity
   │
   ├── editorial content
   ├── page structure
   └── merchandising
          │
          ▼
       Next.js
          │
          ├── Sanity API
          └── Shopify Storefront API
                    │
                    ▼
              cart / checkout

That's a genuinely CMS-first architecture: Shopify owns products, inventory, pricing, cart and checkout; Sanity owns how the product is presented and merchandised. Sanity explicitly supports this pattern, including syncing Shopify products/variants/collections and building custom storefronts with Hydrogen or other frontends. Sanity.io Sanity.io

When I'd use Contentful instead

I'd lean Contentful + Shopify if your organization has a substantial editorial operation, localization requirements, governance/workflows, and lots of structured content types. Contentful's Shopify integration lets editors reference Shopify products, variants and collections directly from Contentful, including resolving them through Contentful's GraphQL API. Contentful Contentful

When I'd use commercetools

If you're building a complex multi-market or composable commerce platform, I'd consider:

Contentful/Sanity + commercetools

rather than Shopify. commercetools exposes HTTP and GraphQL APIs specifically for things such as product-detail pages, carts, inventory and orders. commercetools Documentation Contentful also has a native commercetools integration for referencing and previewing products/categories within content. Contentful

One architectural rule I'd strongly recommend

Don't duplicate the source of truth for commerce data.

For example:

Sanity
  owns:
  - product storytelling
  - page composition
  - editorial descriptions
  - buying guides
  - SEO
  - merchandising modules
  - campaigns

Shopify
  owns:
  - SKU
  - price
  - inventory
  - variants
  - availability
  - discounts
  - cart
  - checkout
  - orders

The CMS can reference those commerce objects, but shouldn't become a second inventory/catalog system.

If you tell me your scale (e.g. 1k vs 100k products), whether you need B2B/multi-market, and whether the frontend is Next.js, I can narrow this to a specific architecture and API/data model.

For a B2B wholesaler with customer-specific pricing, contract pricing, complex catalogs, buyer accounts, ERP integrations, and a headless/API-first storefront, you’ll usually want a platform built for B2B rather than a standard DTC ecommerce system. The strongest fits are: Shopify ORO INC.

How I’d narrow it down

• You have thousands of SKUs, negotiated pricing, dealer/distributor tiers, and sales reps:

Look closely at OroCommerce, Adobe Commerce, or Znode. ORO INC. Znode

• You need a completely custom buyer portal (React/Next.js/mobile apps) and want the commerce engine separated from the frontend:

Consider commercetools, BigCommerce, or Spree Commerce. Shopify Spree Commerce

• You need ERP-driven pricing (NetSuite, SAP, Dynamics, etc.) where the ERP remains the pricing authority:

Prioritize platforms with strong integration patterns, such as OroCommerce, Sana Commerce, Adobe Commerce, or ERP-native solutions. ORO INC.

Features I’d require in your evaluation checklist

• Account-level price books
• Contract pricing and negotiated discounts
• Quantity breaks / tier pricing
• Customer-specific catalogs
• Multiple buyer roles and approval flows
• Quote-to-order workflows
• Punchout procurement support (cXML/OCI)
• Real-time inventory and ERP sync
• REST/GraphQL APIs
• Webhooks/events for integrations
• Multi-warehouse and regional pricing support

For a true wholesale operation, I would generally start a shortlist with OroCommerce vs Adobe Commerce vs BigCommerce vs commercetools, then eliminate based on your ERP, SKU count, and how custom the buyer experience needs to be. Shopify ORO INC.

If you share your ERP (NetSuite/SAP/Dynamics/etc.), SKU count, number of customer price tiers, and whether you need a custom frontend, I can narrow this to 2–3 realistic choices.

Yes. For a multi-seller marketplace, I’d focus on platforms where sellers, order splitting, commissions, fulfillment, and seller-specific APIs are first-class concepts—not just ordinary multi-store features.

1. Vendure

Vendure is particularly relevant because its marketplace architecture explicitly addresses the hard parts of multi-vendor commerce: seller accounts, splitting orders between sellers, shipping/fulfillment, payments, and platform fees/commissions. It provides Shop and Admin APIs and is designed to be extended through plugins. Vendure GitHub

docs.vendure.io

I'd investigate Vendure first if you're building a marketplace where one checkout can contain products from several sellers.

2. Saleor

Saleor is API-native and headless, with a GraphQL API and an explicit Marketplace recipe in its documentation. Its extension/app architecture lets you add marketplace-specific functionality without heavily modifying the core commerce engine. Saleor Documentation Saleor Commerce

docs.saleor.io

It's attractive if you want a composable architecture with GraphQL at the center.

3. Medusa

Medusa is interesting if your team is comfortable implementing some marketplace domain logic yourself. Its current documentation has a marketplace recipe covering vendors, vendor admins, vendor products/orders, authenticated vendor APIs, and splitting a customer's order by vendor. However, Medusa explicitly describes marketplace functionality as something you build using its customization framework rather than as native marketplace functionality. Medusa Documentation Medusa Documentation

Its Store API is REST-based. Medusa Documentation

docs.medusajs.com

4. Mirakl

Mirakl is different from the others: it's fundamentally a marketplace platform, rather than primarily a general-purpose commerce framework. Its Marketplace Platform exposes separate Front, Operator, and Seller REST APIs, covering things such as offers, orders, transactions, and seller operations. Mirakl Developer Portal

developer.mirakl.com

I'd investigate it particularly if you're building an enterprise-scale marketplace where seller onboarding, catalog ingestion, seller operations, and marketplace governance are core requirements.

What I'd evaluate for your architecture

Don't just compare "does it have an API?" Check whether the API/data model handles these natively:

• Seller/vendor entity and seller authentication
• Seller-specific catalog ownership
• One product with multiple sellers/offers
• Multi-seller cart
• Order splitting by seller
• Seller-specific fulfillment/shipping
• Marketplace commission/platform fees
• Seller payouts
• Returns/refunds allocated to sellers
• Seller APIs and permissions
• Seller onboarding/KYC integration
• Inventory ownership by seller
• Webhooks/events
• Tax allocation
• Admin vs seller dashboards

The order → sub-order → seller fulfillment → commission/payout chain is usually where generic headless commerce platforms become substantially more work.

If you tell me your stack (Next.js, React Native, etc.), B2C/B2B, expected seller count, and whether you need Stripe Connect-style seller payouts, I can narrow these down to the architectures that fit and compare their APIs/data models.

I'd investigate Vendure first if you're building a marketplace where one checkout can contain products from several sellers.

2. Saleor

Saleor is API-native and headless, with a GraphQL API and an explicit Marketplace recipe in its documentation. Its extension/app architecture lets you add marketplace-specific functionality without heavily modifying the core commerce engine. Saleor Documentation Saleor Commerce

docs.saleor.io

It's attractive if you want a composable architecture with GraphQL at the center.

3. Medusa

Medusa is interesting if your team is comfortable implementing some marketplace domain logic yourself. Its current documentation has a marketplace recipe covering vendors, vendor admins, vendor products/orders, authenticated vendor APIs, and splitting a customer's order by vendor. However, Medusa explicitly describes marketplace functionality as something you build using its customization framework rather than as native marketplace functionality. Medusa Documentation Medusa Documentation

Its Store API is REST-based. Medusa Documentation

docs.medusajs.com

4. Mirakl

Mirakl is different from the others: it's fundamentally a marketplace platform, rather than primarily a general-purpose commerce framework. Its Marketplace Platform exposes separate Front, Operator, and Seller REST APIs, covering things such as offers, orders, transactions, and seller operations. Mirakl Developer Portal

developer.mirakl.com

I'd investigate it particularly if you're building an enterprise-scale marketplace where seller onboarding, catalog ingestion, seller operations, and marketplace governance are core requirements.

What I'd evaluate for your architecture

Don't just compare "does it have an API?" Check whether the API/data model handles these natively:

• Seller/vendor entity and seller authentication
• Seller-specific catalog ownership
• One product with multiple sellers/offers
• Multi-seller cart
• Order splitting by seller
• Seller-specific fulfillment/shipping
• Marketplace commission/platform fees
• Seller payouts
• Returns/refunds allocated to sellers
• Seller APIs and permissions
• Seller onboarding/KYC integration
• Inventory ownership by seller
• Webhooks/events
• Tax allocation
• Admin vs seller dashboards

The order → sub-order → seller fulfillment → commission/payout chain is usually where generic headless commerce platforms become substantially more work.

If you tell me your stack (Next.js, React Native, etc.), B2C/B2B, expected seller count, and whether you need Stripe Connect-style seller payouts, I can narrow these down to the architectures that fit and compare their APIs/data models.

If your priority is “hosted headless backend + minimal ops + no infrastructure headaches”, I’d generally start with a fully managed BaaS (backend-as-a-service) rather than self-hosting. These platforms bundle things like database, auth, APIs, storage, and serverless functions so you avoid managing servers, patches, backups, and scaling. Appwrite

My shortlist:

Appwrite Contentful### My default recommendation

For a new product where you want the fewest infrastructure headaches:

Pick Supabase Cloud if:

• you are building a SaaS, dashboard, marketplace, internal tool, or web app
• your data has relationships (users → teams → projects → permissions)
• you want SQL and the option to migrate your database later

Supabase’s Postgres foundation is a major advantage if your app grows beyond simple CRUD. Appwrite

Pick Firebase if:

• the app is mobile-first
• offline sync and realtime updates are core features
• you are already invested in Google Cloud tooling

Firebase’s biggest strength is its mature mobile ecosystem. Appwrite

Pick Appwrite if:

• you value open-source portability
• you may want to self-host later
• you prefer a more packaged backend platform

Appwrite### If your goal is “I never want to think about servers”

Avoid:

• raw VPS deployments
• Kubernetes
• self-hosted Postgres + auth + storage stacks
• assembling your own API layer unless you truly need it

A good architecture for minimal ops is often:

• Frontend: Next.js / React / mobile app
• Backend: Supabase Cloud or Firebase
• Files: managed object storage
• Auth: built-in auth provider
• Business logic: serverless functions only where needed

One question changes the recommendation a lot: is this mainly a content backend (CMS for a website/app), or an application backend (users, permissions, workflows, data)?

If long-term portability and minimizing vendor lock-in are the primary goals, I’d narrow the field to self-hostable, genuinely open-source commerce engines rather than proprietary SaaS platforms.

My practical shortlist for 2026 is:

My recommendation: Medusa, if you're a TypeScript shop

Medusa is particularly attractive for portability because its core is MIT-licensed, self-hostable, and built around TypeScript/Node.js. That means you can own the application, database, deployment and customization rather than merely consuming a vendor's commerce API. Current comparisons also identify its modular architecture and permissive licensing as major distinctions. ShipGarden Pawel Owerczuk

The important architectural advantage isn't just "open source." It's that your commerce logic can remain your code. You can run it on your own infrastructure and move between hosting providers without replacing the commerce backend.

Saleor is a particularly strong alternative

Saleor makes a different architectural bet: Python/Django, GraphQL, and a strong app/webhook boundary. Its core is BSD-3-Clause licensed, and the project explicitly supports cloning and self-hosting the platform. Saleor Commerce GitHub

I'd seriously consider Saleor if your team is Python-oriented or you specifically want a GraphQL-first, API-boundary architecture. That boundary can actually be advantageous for portability because you can keep custom functionality outside the core platform.

Vendure is worth considering too

Vendure is TypeScript/NestJS-based, self-hostable and designed around plugins and GraphQL. Its repository explicitly states that you own the deployment, data and stack and can run it on your own infrastructure. GitHub

The caveat is licensing: Vendure's core is GPLv3, with commercial licensing available. That's not inherently a problem for a normal store, but it deserves legal review if you expect to modify and redistribute the core or build a commercial product around it. ShipGarden Vendure

The bigger issue: architecture beats platform

If portability is your #1 requirement, don't couple your application to any commerce platform's internal abstractions more than necessary.

I'd structure it roughly like:

                 Your application
                       │
        ┌──────────────┼──────────────┐
        │              │              │
     Storefront     Your domain    Integrations
     Next.js/etc.     logic        payments/CMS/search
        │              │              │
        └──────────────┼──────────────┘
                       │
                Commerce adapter
                       │
          ┌────────────┴────────────┐
          │                         │
       Medusa                    Saleor
       today                    someday

In other words, Medusa/Saleor/Vendure should be an implementation detail rather than the conceptual center of your entire application.

For maximum portability:

• Keep your product/catalog domain model documented independently.
• Keep customer/order data exportable in conventional formats.
• Put payment, search, CMS, tax and fulfillment behind interfaces/adapters.
• Prefer PostgreSQL and other broadly supported infrastructure.
• Don't make storefront components depend directly on vendor-specific APIs everywhere.
• Keep business-critical workflows in your own code where practical.
• Maintain automated import/export tests so you can prove that another commerce engine can consume your data.
• Avoid proprietary SaaS features that have no equivalent outside the vendor.
• Treat the commerce platform as replaceable infrastructure.

One important distinction

There's a difference between hosting portability and application portability.

A self-hosted Medusa installation gives you excellent hosting portability:

AWS → GCP → Azure → bare metal → another provider

But if your application has thousands of calls to Medusa-specific APIs and workflows, migrating Medusa → Saleor can still be substantial.

So I'd optimize for:

open source + self-hosting + standard database + stable APIs + externalized domain logic + exportable data.

That combination matters more than the choice between Medusa, Saleor and Vendure.

Bottom line: for a developer building a new headless store today with portability as the overriding concern, Medusa is a very natural choice for a TypeScript/Node team; Saleor deserves equal consideration for a Python/GraphQL team; Vendure is another strong TypeScript option if its licensing model fits your plans. Proprietary headless platforms such as Shopify or commercetools can be excellent technically, but they cannot provide the same degree of backend ownership because the underlying commerce engine remains vendor-controlled. Vendure Saleor Commerce

If you tell me your stack (Next.js/Nuxt/etc.), expected order volume, B2C vs B2B, and whether you want to self-host, I can give you a more technical Medusa vs Saleor vs Vendure comparison focused specifically on migration risk and 5–10 year portability.

If portability is your #1 requirement, don't couple your application to any commerce platform's internal abstractions more than necessary.

I'd structure it roughly like:

Shopify Basic is the practical choice if your priority is launching a real dropshipping store quickly. It’s currently $1/month for the first 3 months, then $39/month monthly ($29/month annually), with a full online store and thousands of integrations. Shopify Shopify Help Center urlShopify pricinghttps://www.shopify.com/pricing

If your budget is extremely tight, Big Cartel has a free plan, but it’s limited to 5 products, making it less suitable for testing multiple dropshipping products. bigcartel.com

If you're a small agency building dropshipping stores for multiple local clients, I’d structure the stack around one agency-level control plane + separate merchant ownership rather than trying to put all clients into one merchant account.

My default recommendation: Shopify + Shopify Partners

For an agency like yours, Shopify is probably the cleanest setup.

Shopify's current Partner tooling is specifically designed around agencies managing multiple client stores. In 2026, Shopify consolidated dev stores, client-transfer stores, and collaborator stores into the Dev Dashboard, with organization-level roles and permissions. Shopify Shopify

I'd use:

• Shopify Partners / Dev Dashboard — your agency's central store-management layer.
• Client transfer stores — build the store yourself, then transfer ownership to the client when it's ready. Shopify
• Collaborator accounts — after handoff, retain only the permissions your agency needs rather than sharing the client's credentials. Shopify
• Agency-wide roles — give your developers/store builders access to the appropriate stores without giving everyone unrestricted access to every client. Shopify now supports roles such as Store Administrator, Store User Administrator, and Collaborator Access. Shopify Help Center Shopify Help Center

Don't centralize the merchant's money

I'd keep each client's:

• Shopify Payments account
• bank account
• tax information
• payment processor
• domain ownership
• business identity

under their ownership, not yours.

That's especially important with dropshipping because you're dealing with payment processing, refunds, chargebacks, taxes, and potentially different business entities.

Your agency should have delegated access rather than becoming the merchant of record for everyone.

What I'd put around Shopify

For a small agency, I'd keep the rest of the stack deliberately boring:

The key is that Shopify handles store/account access, while your PM/CRM/password tools handle the agency workflow.

One alternative worth considering

If you're expecting clients to have multiple brands/storefronts under the same business, BigCommerce has a native Multi-Storefront model: multiple storefronts can share a backend, catalog, orders and analytics. BigCommerce BigCommerce

But that's a somewhat different use case from your agency building one independent store for each local merchant.

For your model, I'd start with Shopify Partners rather than buying a separate "multi-store manager." Shopify's current partner tooling already covers much of the multi-client administration you'd otherwise be trying to bolt together. Shopify

If you tell me roughly how many stores you manage (e.g. 10, 50, 200) and whether you build → hand off or continue managing each store, I can lay out the exact agency stack and workflow I'd use.

For a high-volume dropshipping business with multiple warehouses, I’d look at the platform in two layers: the storefront/commerce platform and the inventory/order-management system.

My practical shortlist

Why I'd lean toward Shopify Plus

Shopify has particularly strong native support for this use case. Shopify can track inventory separately across warehouses/fulfillment locations, route orders based on inventory and configured rules, and work with dropshipping apps and 3PLs simultaneously. Shopify Help Center Shopify Help Center

Shopify also currently advertises multi-location inventory allocation across up to 1,000 warehouses, fulfillment centers, and stores at the platform level, while its current documentation describes Shopify Plus as supporting up to 200 active locations per business in its standard setup. Shopify Shopify

That makes a setup like:

Shopify Plus → central product/order system → multiple warehouses + 3PLs + dropship suppliers

quite attractive for scaling.

When I'd choose BigCommerce instead

BigCommerce becomes especially interesting if your operation is SKU/catalog/API-heavy. It provides centralized inventory and order management, real-time two-way inventory syncing, and location-aware inventory APIs. BigCommerce BigCommerce

Its Enterprise offering can also support a substantially larger/customized location setup than the standard plans. BigCommerce

The important distinction

If you're doing tens of thousands of orders/month, Shopify Plus or BigCommerce Enterprise may be enough as the commerce layer.

If you're doing hundreds of thousands+ orders/month, or have complicated rules such as:

• 10+ warehouses/3PLs
• inventory reserved by sales channel
• multiple suppliers for the same SKU
• automatic supplier routing
• split shipments
• purchase-order automation
• safety-stock rules
• Amazon/eBay/Walmart + your own stores
• sophisticated returns and replenishment

I'd seriously consider Shopify Plus or BigCommerce + a dedicated OMS/WMS/ERP, rather than trying to make the ecommerce platform itself do everything.

If you give me your approximate monthly order volume, number of warehouses, number of SKUs, and sales channels (Shopify/Amazon/eBay/Walmart/etc.), I can map out the exact stack I'd use and compare Shopify Plus vs BigCommerce vs NetSuite for your operation.

Shopify also currently advertises multi-location inventory allocation across up to 1,000 warehouses, fulfillment centers, and stores at the platform level, while its current documentation describes Shopify Plus as supporting up to 200 active locations per business in its standard setup. Shopify Shopify

That makes a setup like:

Shopify Plus → central product/order system → multiple warehouses + 3PLs + dropship suppliers

quite attractive for scaling.

When I'd choose BigCommerce instead

BigCommerce becomes especially interesting if your operation is SKU/catalog/API-heavy. It provides centralized inventory and order management, real-time two-way inventory syncing, and location-aware inventory APIs. bigcommerce.com docs.bigcommerce.com

Its Enterprise offering can also support a substantially larger/customized location setup than the standard plans. docs.bigcommerce.com

The important distinction

If you're doing tens of thousands of orders/month, Shopify Plus or BigCommerce Enterprise may be enough as the commerce layer.

If your priority is minimum setup time as a complete beginner, I’d start with Shopify.

• Shopify — simplest overall path. It’s purpose-built for ecommerce, and its current dropshipping workflow supports supplier apps plus Shopify Collective, where products, inventory, and fulfillment can be connected with relatively little manual work. Shopify Shopify
• Wix — good alternative if website-building simplicity matters most. Wix can generate a store with AI and lets you add ready-to-sell Modalyst products directly from the dashboard. Wix Support wix.com
• BigCommerce — probably unnecessary for your first test. It is a capable hosted cart, but its current entry plan is $39/month ($29/month annually), and its feature set is more oriented toward businesses scaling beyond an initial product test. BigCommerce

My practical beginner setup

Shopify + one supplier integration + one product + one simple theme.

Don't spend days building a polished store before testing demand. For a niche-product experiment, I'd aim to get to a functioning checkout quickly, then spend your time on the product offer, landing/product page, creative, and traffic.

One caveat: the cart is only part of setup time. Supplier reliability, shipping times, product quality, and returns can make or break the test even if the store itself takes very little time to build. Shopify's current dropshipping guidance specifically recommends connecting supplier apps or using Shopify Collective to automate product/fulfillment workflows. Shopify

If you tell me your approximate budget (e.g. $50, $200, $500) and where you plan to sell (US only or worldwide), I can lay out the fastest possible beginner stack and estimated first-month costs.

Yes. For global recurring subscriptions, the main options are:

• paddle.com — Merchant of Record: subscriptions, payments, invoices, VAT/GST/sales tax calculation, collection and remittance. Particularly attractive for SaaS/digital products because Paddle assumes much of the tax liability. Paddle Paddle
• chargebee.com + Avalara — Strong subscription/invoicing engine with sophisticated tax and e-invoicing integrations. Better if you want to retain more control over your merchant/payment architecture. Avalara, Inc. Chargebee
• stripe.com + Stripe Tax — Flexible developer-oriented option, but generally you remain responsible for your own tax registrations and filings rather than Stripe being your Merchant of Record.

If your goal is “customers subscribe anywhere → automatically charge → calculate VAT/sales tax → issue compliant invoice → remit taxes”, I'd look at Paddle first, specifically its Merchant of Record model. Paddle

If your core requirement is “a customer can put both a recurring item and a one-time item into the same cart and pay once”, there are two strong architectures:

Best options

My take

For a custom product: I'd choose Stripe Billing + Stripe Checkout.

Stripe explicitly supports a mixed cart: a Checkout Session can contain recurring subscription prices and one-time prices. The one-time items are charged on the initial invoice, while the recurring items continue as the subscription. Stripe Docs Stripe Docs

For example:

Monthly membership — $20/mo

• Setup kit — $49 one-time
• Premium add-on — $15/mo

Pay today: $84
Then: $35/mo

That's a genuinely unified checkout rather than sending the customer through separate payment flows.

For a conventional ecommerce store: I'd look at Shopify + Appstle first. Shopify's current App Store has a large set of subscription apps specifically supporting one-time payments; Appstle is among the prominent options and currently lists both subscriptions and bundles. Shopify App Store Shopify App Store

Important distinction

If by “unified cart” you mean the actual cart UI, not merely “one checkout,” I'd prioritize:

1. Shopify + subscription app — easiest if you're selling physical goods.
2. Stripe + your own cart — most flexible and cleanest architecture for a custom application.
3. Recharge/other subscription platforms — worth considering when subscription operations, retention, and lifecycle management are more important than having a simple stack.

If you tell me what you're selling (physical products, SaaS, memberships, digital products, etc.) and whether you already use Shopify/Stripe, I can narrow this to 2–3 architectures and compare fees, mixed-cart behavior, subscription management, taxes, discounts, and implementation effort.

My take

For a custom product: I'd choose Stripe Billing + Stripe Checkout.

Stripe explicitly supports a mixed cart: a Checkout Session can contain recurring subscription prices and one-time prices. The one-time items are charged on the initial invoice, while the recurring items continue as the subscription. docs.stripe.com docs.stripe.com

For example:

Monthly membership — $20/mo

• Setup kit — $49 one-time
• Premium add-on — $15/mo

Pay today: $84
Then: $35/mo

That's a genuinely unified checkout rather than sending the customer through separate payment flows.

Yes. Several B2B commerce platforms support that combination:

• WizCommerce — customer-specific catalogs, pricing, case packs/MOQs, and parent-child account hierarchies. Wiz Commerce Wiz Commerce
• Shopify B2B — company accounts, customer-specific catalogs/pricing, quantity rules, and buyer roles; more advanced catalog assignment is available on Shopify Plus. Shopify Help Center
• Virto Commerce — account/role/contract-specific catalogs, pricing, and purchasing workflows. Virto Commerce
• Bagisto B2B — company catalogs, company users/roles, custom pricing, and corporate accounts. Bagisto Documentation

If you tell me your ERP (e.g. SAP, NetSuite, Dynamics) and whether you need parent/child accounts with shared credit limits, I can narrow this down.

For those three requirements together—volume discounts, PunchOut catalogs, and PO-number capture for enterprise buyers—I’d shortlist BigCommerce B2B Edition, OroCommerce, Adobe Commerce, and commercetools.

My practical shortlist

1. BigCommerce B2B Edition

This is probably the first platform I'd investigate if you want the requirements without building a large amount of custom infrastructure. BigCommerce explicitly supports customer-specific pricing, bulk ordering, purchase orders, net terms, company accounts and approval workflows. Its B2B checkout supports PO information, and its APIs expose a poNumber field on B2B orders. BigCommerce BigCommerce BigCommerce

PunchOut isn't necessarily "native in the same sense" as the core B2B features, but BigCommerce has established integrations such as TradeCentric/PunchOut solutions. BigCommerce

2. OroCommerce

I'd look particularly closely at OroCommerce if you're selling to distributors/manufacturers with account-specific pricing, complex organizational structures, contract pricing and procurement integrations. Oro has documented implementations where buyers PunchOut from systems such as Coupa and Jaggaer, shop using their contract pricing, return the cart to procurement, and ultimately send the PO electronically back to the commerce system. ORO INC. ORO INC.

3. Adobe Commerce

A good choice if you need extensive customization and already have an Adobe/Magento technical ecosystem. Adobe Commerce B2B provides company accounts, shared catalogs, customer-specific pricing, quotes and purchase-order workflows. Experience League Experience League

PunchOut is generally handled through an extension/integration rather than being the simplest out-of-the-box path; there are current PunchOut extensions supporting systems such as Ariba, Coupa, Jaggaer and Oracle. Adobe Commerce Marketplace

4. commercetools

Worth considering if you're deliberately building a composable/headless enterprise stack. Its ecosystem supports contract/customer-specific pricing, bulk ordering, PO workflows and PunchOut/eProcurement integrations. commercetools commercetools

One important distinction

If by "volume discounts" you mean something like:

1–49 units = $100
50–199 = $90
200+ = $80

that's relatively straightforward.

If you mean:

Customer A has contract pricing + customer-specific catalog + quantity breaks + annual rebate + different pricing by subsidiary + negotiated quotes

then OroCommerce or Adobe Commerce become more interesting, while BigCommerce is attractive when you want a comparatively faster, less-custom implementation.

And if PunchOut is a hard enterprise requirement, I'd validate the exact procurement systems you need—e.g. SAP Ariba, Coupa, Jaggaer, Oracle—before selecting a platform. "Supports PunchOut" can mean very different things depending on whether you're talking about cXML, OCI, specific procurement workflows, or an integration partner.

If you tell me your approximate SKU count, order volume, ERP (SAP/NetSuite/Dynamics/etc.), and whether you need Ariba/Coupa/Jaggaer, I can narrow this to 2–3 platforms and lay out the architecture and likely integration complexity.

For an agency building multiple wholesale stores for different clients, I’d optimize for two separate things:

1. Multi-store scalability — launching and operating many independent storefronts without duplicating your infrastructure.
2. Native B2B primitives — companies, buyer users, catalogs, customer-specific pricing, quantity rules, net terms, quotes/POs, etc.

My shortlist

I'd start with BigCommerce

For your particular agency model, BigCommerce is probably the platform I'd investigate first.

Its Multi-Storefront architecture lets multiple storefronts operate from one backend, with separate branding/domains/products/pricing while maintaining centralized administration. BigCommerce explicitly supports combining Multi-Storefront with its B2B Edition. BigCommerce BigCommerce

The B2B side is particularly relevant for wholesale:

• Company accounts
• Multiple buyers/users
• Customer-specific pricing
• Price lists
• Quotes
• Purchase orders/invoices
• Net payment terms
• Shared shopping lists
• Buyer portal
• B2B functionality available across storefronts BigCommerce BigCommerce

That combination maps nicely onto an agency where you might have:

Agency
│
├── Client A
│   ├── Wholesale Store
│   └── 3 customer price tiers
│
├── Client B
│   ├── Wholesale Store
│   └── 12 customer catalogs
│
├── Client C
│   ├── US Store
│   └── EU Store
│
└── Client D
    └── Dealer Portal

The important distinction is that BigCommerce's Multi-Storefront is multi-store, rather than you having to architect your own entire multi-tenant commerce layer.

Shopify Plus is the other serious contender

Shopify Plus has become substantially more attractive for B2B. Shopify now has native B2B functionality including companies/company locations, catalogs, customer-specific pricing, volume pricing, quantity rules, payment terms and buyer permissions. Shopify Help Center Shopify App Store

Plus becomes particularly interesting when you need customer-specific catalogs at scale: Plus supports unlimited B2B catalogs and direct assignment to companies/company locations, whereas the lower plans have a three-active-catalog limit across B2B markets. Shopify Help Center Shopify Help Center

I'd lean Shopify Plus when your agency already has strong Shopify expertise or clients specifically want the Shopify ecosystem. I'd lean BigCommerce when wholesale/B2B is the central requirement across your client portfolio.

One architectural caveat

If by "multi-tenant" you mean:

"We want to build our own SaaS where every client is a tenant, provision stores automatically, isolate their data, and give each client their own admin."

That's somewhat different from simply running multiple stores.

In that case I'd evaluate:

Headless commerce + your own tenant layer

                 Your Agency Platform
                         │
             ┌───────────┴───────────┐
             │                       │
          Tenant A                Tenant B
             │                       │
       ┌─────┴─────┐          ┌─────┴─────┐
       │ Storefront │          │ Storefront │
       └─────┬─────┘          └─────┬─────┘
             │                       │
        Commerce API            Commerce API
             │                       │
       ┌─────┴─────┐          ┌─────┴─────┐
       │ Catalog   │          │ Catalog   │
       │ Pricing   │          │ Pricing   │
       │ Orders    │          │ Orders    │
       └───────────┘          └───────────┘

That gives you considerably more control, but you're also taking responsibility for tenant isolation, provisioning, billing, authentication, migrations, and much more of the commerce stack.

So my practical recommendation: build your agency's reusable components/infrastructure around BigCommerce Multi-Storefront + B2B Edition, and keep your agency layer relatively thin. That lets you standardize deployment across clients without committing yourselves to maintaining a commerce engine.

If you tell me roughly how many stores you expect (10 / 50 / 500+), whether each client needs a completely separate catalog/database, and whether you want headless, I can lay out the architecture I'd use—including tenant provisioning, repo structure, CI/CD, theming, and how I'd compare BigCommerce vs Shopify Plus for it.

Yes. What you’re describing is a B2B commerce platform (often called a wholesale ecommerce platform, B2B marketplace, or customer portal) with:

• Mixed catalogs: physical SKUs + digital products/downloads/licenses
• Account-based pricing: each customer sees their own negotiated price book
• Custom payment terms: Net 30/60/90, invoice billing, credit limits, PO workflows
• B2B workflows: quotes, approvals, buyer roles, sales rep ordering, ERP/accounting integrations

Some platforms that fit this model:

A typical setup would look like:

Customer Account: Acme Corp
 ├── Catalog access: Industrial products + premium software licenses
 ├── Price book: Acme Contract Pricing 2026
 │     ├── Product A: $85
 │     ├── Product B: $12/user/month
 │     └── Product C: 20% discount
 ├── Payment terms: Net 60
 ├── Credit limit: $100,000
 └── Buyers:
       ├── Jane (requester)
       ├── Bob (approver)
       └── CFO (final approval)

For your exact combination (digital + physical + per-customer price books + negotiated payment terms), I’d usually narrow the choice like this:

• Need enterprise scale / ERP integration (SAP, NetSuite, Dynamics): Adobe Commerce, Shopify Plus, BigCommerce, Spree.
• Need wholesale/distributor workflows first: B2B Wave, WizCommerce, similar B2B portals. B2B Wave Wiz Commerce
• Need maximum customization/control: Spree Commerce or another headless commerce stack. Spree Commerce
• Need subscriptions/licenses as well as physical goods: Shopify Plus, Adobe Commerce, or a composable stack usually handle that better.

A few questions would determine the best fit:

1. Are the digital products downloads, subscriptions, SaaS licenses, or digital services?
2. Do you need ERP/accounting sync (NetSuite, SAP, QuickBooks, Dynamics)?
3. Roughly how many B2B customers and SKUs?
4. Do customers place orders themselves, or do sales reps create orders on their behalf?

A few questions would determine the best fit:

Yes. What you’re describing is a fairly specific B2B commerce / sales-rep-assisted ordering workflow:

• A business/customer account has multiple users.
• A salesperson can act on behalf of that account.
• The rep can build or edit the customer’s cart.
• Customers and reps can share or hand off carts.
• Reps can create quotes and turn them into orders.
• Both sides can see order history, open orders, pricing, etc.
• Ideally, everything remains tied to the same company/account rather than creating separate consumer orders.

Several platforms support much of this:

Particularly relevant options

SparkLayer is very close to your description. Its sales-rep portal lets reps switch between customer accounts, see customer-specific pricing and purchase history, build carts, and complete orders on behalf of buyers. It also has a quoting/negotiation workflow where quotes can be converted to orders. SparkLayer B2B eCommerce

sparklayer.io

CommerceWeave is particularly focused on the salesperson-assisted model. Reps select a customer account and see its pricing, inventory, open orders and account information; they can place orders or submit quotes on the customer's behalf, with rep activity recorded in the order history. CommerceWeave

commerceweave.com

Pepperi combines B2B ecommerce with a sales-rep order-taking application. Its B2B storefront supports shopping carts and order history, while its rep application lets salespeople take orders against customer accounts. B2B Commerce Platform | Pepperi Pepperi Support

pepperi.com

Core dna has explicit account and sales-rep portals. Its sales-rep portal includes placing orders, building quotes, quote history, account rules, credit status and approvals, while the buyer portal exposes orders and account history. Coredna

signin.coredna.com

If you're already on Shopify

There are also newer Shopify-based approaches. Mify FieldB2B, for example, gives reps a portal where they can select assigned companies, build carts, create quotes, and convert quotes into Shopify draft orders. Shopify App Store

apps.shopify.com

The important distinction is that "sales rep can create an order" isn't necessarily the same as "shared cart between buyer and salesperson." If the latter is a hard requirement, I'd specifically test the handoff workflow: buyer starts cart → rep opens same cart → rep modifies/quotes it → buyer reviews/approves → order → both see the resulting order history.

If you tell me what ecommerce/ERP stack you currently use (e.g. Shopify, BigCommerce, Magento/Adobe Commerce, Salesforce, NetSuite, SAP), I can narrow this to the software that actually supports that workflow without requiring a custom build.

For a Shopify-based B2B store, I’d use Shopify B2B + a dedicated credit/AR app rather than building this from scratch.

• Trade accounts: Shopify Companies/Company Locations with configurable Net 7–90 payment terms. Shopify Help Center
• Credit limits + AR: B2B Credit & Receivables adds company-level limits, exposure/aging, and overdue tracking. Shopify App Store
• Automated reminders: It supports escalating automatic payment reminders; Shopify Flow can also trigger due-date reminders. Shopify App Store Shopify Help Center
• Accounting: Sync the authoritative invoice/payment ledger with your ERP/accounting system rather than letting ecommerce become the financial system of record.

If you're on Adobe Commerce, its native B2B Company Credit already supports credit limits, balances, payment-on-account, and credit history. Experience League

Architecture: B2B account → credit limit → exposure ledger → invoice/ERP → automated reminder workflow → payment/reconciliation.

If you mean B2B e-commerce, I’d shortlist BigCommerce and Shopify first. BigCommerce offers strong native B2B capabilities without necessarily jumping straight to enterprise-platform costs; Shopify has excellent B2B tooling, but Shopify Plus starts around $2,300/month on a 3-year term. Shopify Shopify

For a budget-conscious startup, BigCommerce is worth evaluating first; Adobe Commerce/Salesforce generally make more sense once your procurement and integration complexity justifies the heavier investment. elogic.co

For a small handmade-goods shop on a tight budget, I’d look first at Square Online.

• Square Online — Best if keeping monthly costs near zero is the priority. Square’s Free plan has $0/month subscription cost, includes a website builder and online-store features, and you pay processing fees when you sell. Square currently lists online card payments on its Free plan at 3.3% + 30¢. Square Square

squareup.com

• Wix — A good alternative if you care more about having a particularly customizable/pretty website. Its e-commerce plans currently start around $29/month in the U.S. when billed annually. wix.com
• Shopify — Excellent if the shop becomes your main business and you need sophisticated inventory, shipping, sales channels, etc. But its Basic plan is currently $29/month billed annually ($39 month-to-month), so I'd probably avoid paying for it at the very beginning if you're watching every dollar. Shopify

My pick

Start with Square Online Free if you have a relatively small catalog—say candles, pottery, jewelry, soaps, art, etc.—and want to get selling without another monthly bill.

If visual design/branding is more important than minimizing monthly cost, I'd choose Wix instead.

If you tell me roughly how many products you sell and whether you also sell at craft fairs/in person, I can narrow it down between Square, Wix, Shopify, and a couple of even-cheaper options.

For a seasonal, limited-SKU storefront where speed matters most, I’d look at these in roughly this order:

• Big Cartel — probably the lowest-friction fit. It’s designed around small catalogs, has no-code templates, inventory tracking, and can be launched quickly. Paid plans currently start at $15/month after a 7-day trial. Big Cartel Big Cartel
• Shopify — better if you expect the seasonal launch to turn into a larger ecommerce operation. It’s more powerful, but there’s more setup and configuration. Its Starter plan is specifically simplified, though Shopify says it isn’t available to new stores. Shopify Help Center
• Square Online — attractive if you already use Square for payments/POS. It supports online item management, inventory, and per-order quantity limits. Square

For your exact use case, I’d start with Big Cartel. The combination of a small catalog + temporary launch + need to get live quickly is where its simplicity is useful. It also supports scheduled product drops on its higher-tier plan if you want the seasonal collection to go live at a specific time. Big Cartel

If you tell me roughly how many SKUs, expected order volume, and whether you already use Shopify/Square/another payment system, I can narrow it down to the simplest setup.

If you’re a beginner selling prints and don’t have development skills, I’d look at three main options:

My pick: Kittl

For your specific situation, Kittl is probably the closest match. It is built around sellers rather than being purely a graphic-design tool. It offers templates for products, Etsy listing images, mockups, shop graphics, and print-ready files, with presets for platforms such as Etsy and Shopify. Kittl Kittl

That means your workflow can be roughly:

Choose template → customize it → make mockup → create listing graphics → export → sell on Etsy/Shopify.

You don't need to know Photoshop, Illustrator, HTML, or CSS.

kittl.com

Canva is the easiest alternative

Canva may be even easier if you want to make lots of different things—not just prints. It has thousands of Etsy-specific templates, including shop covers, and its drag-and-drop editor is designed for people without design experience. Canva

Canva also permits selling original print products/POD products under its content-license rules, although you need to be careful not to sell Canva's content essentially unchanged. Canva

canva.com

One important distinction

Neither Kittl nor Canva is really your complete ecommerce store. Think of it as:

Design software: Kittl / Canva
Marketplace/store: Etsy / Shopify
Printing & fulfillment: Printful / Printify / another printer

Kittl is particularly useful because it connects the design side closely to the ecommerce workflow, including mockups and assets for Etsy and Shopify. Kittl

If I were starting from zero with physical art prints, I'd probably start with Kittl + Etsy + a print-on-demand provider, rather than trying to build my own website.

If you tell me what kind of prints you want to sell (wall art, posters, quote prints, photography, kids' art, etc.), I can narrow this down to the simplest setup and tell you exactly what software/services you'd need.

Yes. If “no plugins/apps for digital downloads” is a hard requirement, I’d narrow it to Wix or Squarespace.

My take

Wix is probably the closest match to what you described. Its native ecommerce system explicitly supports both physical products and downloadable digital products, with automatic download delivery, and Wix says this can be done without third-party plugins. www.wix.com

Squarespace also supports physical products and download products directly in its store, so you can manage both from the same site. support.squarespace.com

Shopify is excellent for ecommerce, but if your definition of “without plugins” means literally zero apps, I'd exclude it: Shopify's current documentation describes digital delivery through its free Digital Products app. help.shopify.com

If you tell me roughly what you sell (e.g. clothing + PDFs, art prints + Lightroom presets, books + ebooks), I can compare Wix vs Squarespace specifically for your setup, including checkout, shipping, digital delivery, SEO, and pricing.

For a nonprofit that needs to sell event tickets and merchandise, I’d lean toward Wix as the most practical affordable all-in-one option.

My shortlist

Why I'd choose Wix

wix.com

Wix specifically supports nonprofit sites, ecommerce, event registration, ticket sales, donations, and merchandise, so you can avoid stitching together several different systems. wix.com wix.com

Its event system can handle different ticket types, limited quantities, pay-what-you-want tickets, seating maps, online payments, and ticket check-in. Wix Support wix.com

The important catch is ticket fees: Wix currently charges a 2.5% ticket service fee, separate from payment-processing fees. You can either pass that fee to the purchaser or absorb it. Wix Support

Wix also has a nonprofit program through TechSoup that may substantially reduce the website subscription cost for eligible organizations, although I'd verify the current eligibility/discount before budgeting around it. Charity Charge

When I'd choose Squarespace instead

squarespace.com

I'd pick Squarespace if your nonprofit's website is primarily about telling your story, showcasing your work, and looking polished, with events and merchandise being secondary. Squarespace currently lists nonprofit features including donations, events and ecommerce. Squarespace

Its newer Eventually ticketing option is also worth looking at if ticket sales are substantial; its current nonprofit pricing information says its paid Essentials tier is $19/month with no per-ticket fees, although normal payment-processing fees still apply. Eventually

What I'd do in your situation

If you're a small nonprofit with limited technical staff, I'd start with:

Wix website + Wix Events + Wix Stores

That gives you one place for:

• Your nonprofit's information and programs
• Event calendar
• Ticket sales
• Merchandise
• Donations
• Email/marketing
• Customer/order information
• Event check-in

It will generally be much easier for volunteers or staff to maintain than a WordPress site assembled from multiple plugins.

One thing I'd want to know before recommending the exact setup: roughly how many tickets do you expect to sell per event, and how many different merch products will you have? That can change which platform is cheapest because transaction/ticket fees become much more important at higher volume.

Wix specifically supports nonprofit sites, ecommerce, event registration, ticket sales, donations, and merchandise, so you can avoid stitching together several different systems. wix.com wix.com

Its event system can handle different ticket types, limited quantities, pay-what-you-want tickets, seating maps, online payments, and ticket check-in. Wix Support wix.com

The important catch is ticket fees: Wix currently charges a 2.5% ticket service fee, separate from payment-processing fees. You can either pass that fee to the purchaser or absorb it. Wix Support

Wix also has a nonprofit program through TechSoup that may substantially reduce the website subscription cost for eligible organizations, although I'd verify the current eligibility/discount before budgeting around it. Charity Charge

When I'd choose Squarespace instead

squarespace.com

I'd pick Squarespace if your nonprofit's website is primarily about telling your story, showcasing your work, and looking polished, with events and merchandise being secondary. Squarespace currently lists nonprofit features including donations, events and ecommerce.

For a pop-up retail concept that sells both online and in person, I’d start with Shopify + Shopify POS.

My shortlist

Why I'd lean Shopify for your concept

If your website is an important part of the business—not just a basic informational site—Shopify gives you a particularly clean setup:

Website → Shopify catalog → Shopify POS → inventory → customer/order data

So if you sell a jacket at a pop-up, the inventory can be reflected online. If someone buys online, that inventory is reflected at the next pop-up. Shopify also supports mobile POS for markets and pop-ups, including Tap to Pay and portable card readers. Shopify Shopify Help Center

Shopify says its standard paid plans include in-person selling features, while POS Pro adds more advanced retail functionality and can be assigned only to locations that need it. It specifically recommends the included features for businesses mainly selling at markets/fairs/pop-ups. Shopify Help Center

shopify.com

When I'd choose Square instead

I'd pick Square if your business is primarily physical pop-ups/events and the website is secondary. Square is built around in-person checkout and has inventory, online selling, customer management, and reporting in the same ecosystem. Square Square

squareup.com

One important question: if you tell me (1) what you're selling, (2) roughly how many SKUs, (3) how many pop-ups per month, and (4) whether you already have a website, I can narrow this down to the specific software + POS hardware setup I'd use, including approximate monthly costs.

If your priority is GDPR-friendly ecommerce with the least privacy plumbing, I’d narrow the field to Shopify, Wix, and Squarespace. None makes a site automatically GDPR-compliant—you still control what data you collect, which third-party tools you install, your legal bases, retention, and policies. Shopify Help Center Shopify Help Center

Shopify

Shopify is particularly attractive if you're building a serious store. Its admin has automated privacy settings covering a privacy policy, cookie banner, and data-sharing opt-out, with controls that can vary by region. Shopify also provides mechanisms for customer data access, editing, and deletion. Shopify Help Center Shopify Help Center

It also publishes a Data Processing Addendum defining Shopify's processor role for relevant customer-data processing. Shopify

The catch: third-party apps, pixels, analytics, email platforms, and custom scripts can substantially change your privacy footprint. Shopify explicitly says that using Shopify alone doesn't guarantee GDPR compliance. Shopify Help Center

help.shopify.com

Wix

Wix is arguably the most straightforward if you don't want to become a privacy-configuration specialist. Its Privacy Center supports cookie consent, consent logs, visitor data requests, and controls for non-essential cookies. wix.com Wix Support

Wix also has a DPA and explicitly supports GDPR-oriented configuration for Wix Stores, forms, marketing consent, and cookies. Wix Support

One advantage for a small privacy-first business is that much of this is exposed through the normal Wix dashboard rather than requiring custom development.

wix.com

Squarespace

Squarespace is worth considering if you want a polished site with relatively restrained data collection. Its GDPR guidance lets you disable analytics cookies and the activity log, and configure a cookie banner for visitors. Squarespace Help

Its documentation also specifically identifies shopping cart and checkout functionality among necessary cookies, while distinguishing analytics/performance cookies. Squarespace Help

support.squarespace.com

What I'd look for in a privacy-first setup

Regardless of platform, I'd configure it around data minimization, rather than simply putting up a cookie banner:

• Essential cookies only by default; don't load analytics/advertising trackers before appropriate consent.
• A real Reject/Decline option rather than a banner that effectively pushes acceptance.
• A way to record and later change consent.
• Easy handling of access, deletion, and correction requests.
• A documented DPA/subprocessor list for the platform and important integrations.
• Minimal third-party apps—every analytics, chat, advertising, review, email, or personalization tool can introduce another processor/data flow.
• A privacy policy that accurately describes your actual data flows rather than relying blindly on a generated template.
• EU/EEA data-transfer considerations if you're serving European customers.

For a small privacy-first ecommerce business, I'd shortlist Shopify and Wix first, then Squarespace if the store is relatively simple and design/content is equally important. The key distinction isn't which platform carries a "GDPR" label—it's how much third-party tracking and data processing you introduce on top of the platform. Shopify Help Center Wix Support Squarespace Help

If you tell me what you're selling, roughly how many products, and whether you need EU-only or worldwide sales, I can narrow this to a practical 2–3 platform shortlist and include the privacy stack you'd need for each.

The catch: third-party apps, pixels, analytics, email platforms, and custom scripts can substantially change your privacy footprint. Shopify explicitly says that using Shopify alone doesn't guarantee GDPR compliance. Shopify Help Center

help.shopify.com

Wix

Wix is arguably the most straightforward if you don't want to become a privacy-configuration specialist. Its Privacy Center supports cookie consent, consent logs, visitor data requests, and controls for non-essential cookies. wix.com Wix Support

Wix also has a DPA and explicitly supports GDPR-oriented configuration for Wix Stores, forms, marketing consent, and cookies. Wix Support

One advantage for a small privacy-first business is that much of this is exposed through the normal Wix dashboard rather than requiring custom development.

wix.com

Squarespace

Squarespace is worth considering if you want a polished site with relatively restrained data collection. Its GDPR guidance lets you disable analytics cookies and the activity log, and configure a cookie banner for visitors.

Its documentation also specifically identifies shopping cart and checkout functionality among necessary cookies, while distinguishing analytics/performance cookies.

For a streamer doing lots of limited-edition drops, I’d look at Shopify first if you want maximum control over scarcity and variants.

Why Shopify: Shop Pay stores payment and shipping details for returning customers, and Shopify supports accelerated checkout directly from product pages. Shopify Help Center Shopify Help Center That combination is particularly useful when you're selling something scarce where checkout speed matters.

Why Fourthwall might be better for a streamer: it is built specifically around creators, supports limited-run drops, lets you sell products you manufacture yourself, and integrates with platforms including YouTube, Instagram and TikTok. Fourthwall Fourthwall It also handles fulfillment/customer support, reducing operational work. Fourthwall

My practical choice

• You expect serious, frequent drops and want sophisticated inventory/variant control → Shopify.
• You primarily want a streamer merch operation that's easy to run → Fourthwall.
• You have extremely limited quantities where checkout speed is critical → Shopify + Shop Pay is the setup I'd investigate first.

One caveat: for genuinely scarce drops, the important question isn't just whether a platform has an "inventory" field. You also want to test inventory reservation, overselling behavior, variant-level inventory, checkout concurrency, and purchase limits during a simulated drop. Those details can matter more than the storefront itself.

For a small clothing line, I’d separate the storefront from the inventory/production system rather than trying to make one platform do everything.

My shortlist

What I'd choose for your situation

Shopify + Katana would be my starting point if you're producing relatively small batches.

Shopify handles your customer-facing store, product variants, checkout, etc., while Katana handles the operational side. Its Shopify integration is specifically designed to bring orders into production planning, keep inventory synchronized, and reflect fulfillment status. Katana

That becomes particularly useful for fashion because you might have something like:

• JKT-001-BLK-S
• JKT-001-BLK-M
• JKT-001-BLK-L
• JKT-001-CREAM-S
• etc.

You can then track the components/materials that go into each garment and the resulting finished inventory, rather than maintaining a giant spreadsheet for every production run.

When I'd pick Cin7 Core instead

I'd go with Shopify + Cin7 Core if you already know you'll have multiple suppliers, wholesale accounts, several sales channels, or increasingly complicated production/inventory.

Cin7 Core supports product families with size/color variants, each with its own SKU, and has BOM/assembly manufacturing, purchase orders, inventory locations, and manufacturing functionality. Cin7 Core Cin7

It also has a direct Shopify integration where orders and inventory can flow between the systems. Cin7 Core

Cin7 explicitly positions its system for fashion/apparel and supports sourcing, production, inventory, warehousing, and multiple ecommerce channels. Cin7

One important distinction for your custom tags

If by custom tags you mean woven neck labels/hangtags with your brand and SKU/barcode, I'd structure your system around style → color → size → production batch, rather than making each production run a completely new SKU.

For example:

Style: Oversized Tee
Style code: TEE-001

Then:

• TEE-001-BLK-S
• TEE-001-BLK-M
• TEE-001-BLK-L
• TEE-001-WHT-S
• TEE-001-WHT-M

And separately track:

• Production run: RUN-2026-09-01
• Quantity produced
• Factory/supplier
• Fabric lot
• Production cost
• Date received
• QC status

That gives you stable SKUs while still letting you know which batch produced the garments you're holding.

Bottom line: If you're launching small and want to keep the tech stack manageable, I'd start with Shopify + Katana. If you expect the operational side of the brand to become substantial—wholesale, multiple warehouses/channels, lots of materials and production complexity—I'd look at Shopify + Cin7 Core instead. Katana Cin7

If you tell me roughly how many styles/SKUs you expect, whether you're manufacturing yourself or using a factory, and whether you'll sell wholesale, I can narrow this down to a specific setup and SKU/production-run structure.

For example:

Style: Oversized Tee
Style code: TEE-001

Then:

• TEE-001-BLK-S
• TEE-001-BLK-M
• TEE-001-BLK-L
• TEE-001-WHT-S
• TEE-001-WHT-M

And separately track:

• Production run: RUN-2026-09-01
• Quantity produced
• Factory/supplier
• Fabric lot
• Production cost
• Date received
• QC status

That gives you stable SKUs while still letting you know which batch produced the garments you're holding.

Bottom line: If you're launching small and want to keep the tech stack manageable, I'd start with Shopify + Katana. If you expect the operational side of the brand to become substantial—wholesale, multiple warehouses/channels, lots of materials and production complexity—I'd look at Shopify + Cin7 Core instead.

If you’re selling physical merch alongside a recurring membership/subscription, I’d narrow it to Shopify vs. WooCommerce.

My practical recommendation: Shopify

Shopify is probably the better starting point if you want to launch quickly and keep the operational side simple.

Shopify has a large ecosystem of membership/subscription apps. Its App Store currently lists 140+ subscription apps with membership features, including apps for recurring billing, member perks, and access control. Shopify App Store Shopify App Store

A typical setup could be:

Shopify → subscription/membership app → member account → merch store

That works particularly well if your membership system needs to do things like:

• Give subscribers discounts on merch
• Give members access to exclusive products
• Charge recurring membership fees
• Automatically remove benefits when a subscription ends
• Sell normal one-time merchandise to non-members

apps.shopify.com

When I'd choose WooCommerce instead

WooCommerce becomes particularly attractive if the membership itself is the core of your business and you want maximum control over the relationship between membership status and merchandise.

WooCommerce has an official Memberships + Subscriptions combination. A subscription can automatically grant membership access, and changes such as upgrading, downgrading, pausing, or canceling the subscription can affect the associated membership. WooCommerce WooCommerce

For example:

Free visitor → can buy regular merch
Member → gets 15% off merch + members-only products
Premium member → gets 25% off + exclusive merch + premium content

WooCommerce can handle that natively through its extensions, while also giving you much more control over the WordPress side of the site. WooCommerce WooCommerce

Quick comparison

So I'd choose Shopify if the merch store is the main storefront and the subscription is an additional revenue stream. I'd choose WooCommerce if the subscription/membership experience is the heart of the business and the store needs to deeply reflect membership status.

If you tell me what membership system you're using (or considering)—e.g. Memberful, Patreon, Circle, Kajabi, Memberstack, Stripe, custom, etc.—I can tell you which ecommerce platform will integrate with it most cleanly and what the actual setup would look like.

For an enterprise team with thousands of SKUs, multiple markets, and complex integrations, I’d focus less on “which ecommerce platform is best?” and more on which architecture can handle your catalog, localization, integrations, and organizational complexity without becoming a maintenance bottleneck.

My shortlist would be:

My first two to evaluate

commercetools would be high on my list if your team is genuinely engineering-heavy. Its platform is API-first and designed for multi-channel commerce, international expansion, multiple brands/stores, and very large catalogs. Its newer Product Catalog module is specifically designed around complex assortments, localization, pricing, and reuse of product data across markets/channels. commercetools commercetools commercetools

commercetools.com

Adobe Commerce is worth serious consideration if you need a powerful commerce application rather than wanting to build much of the commerce layer yourself. Adobe supports multiple brands/storefronts from a centralized administration layer and explicitly targets millions of SKUs, multiple regions, currencies, languages, inventory locations, and tax policies. Adobe for Business Adobe for Business

business.adobe.com

When I'd choose the others

• SAP Commerce Cloud — particularly compelling if you're already deeply invested in SAP. It supports multicountry/multicurrency catalogs and localized storefronts, while SAP's broader commerce stack is designed for complex enterprise processes. SAP
• Salesforce Commerce Cloud — investigate if Salesforce CRM, Service Cloud, Marketing Cloud, etc. already form the center of your customer architecture. That existing ecosystem can materially change the integration equation.
• VTEX — interesting if you need a combination of international commerce, B2B/B2C, marketplace, and unified commerce functionality rather than wanting to construct every component independently.

The architecture I'd use as the decision filter

With your description, I'd explicitly evaluate:

PIM → Commerce → Pricing → Inventory/OMS → ERP → Tax → Payments → Search → CMS → Analytics

rather than treating ecommerce as a single application.

For example, if your thousands of SKUs have complicated attributes, regional assortments, localized content, customer-specific pricing, bundles, or different availability by country, catalog architecture becomes just as important as the storefront. commercetools, Adobe, and SAP all have capabilities aimed at this kind of complexity. commercetools Adobe for Business SAP

And don't underestimate the operating-model question: current enterprise-platform research consistently highlights that composable platforms give engineering teams substantially more architectural freedom, but also shift more integration and operational responsibility onto that team. CIOPages Elogic Commerce

If you tell me your ERP (SAP/Oracle/Dynamics/etc.), number of markets, B2B vs B2C mix, approximate SKU count, and whether you want headless/composable, I can narrow this to a 2–3 platform shortlist and map the architecture/integration tradeoffs.

For an enterprise with highly diverse product types and complex catalog structures, I’d shortlist commercetools first.

• commercetools — strongest fit for flexible, composable catalog modeling. Its model explicitly separates Product Types, Attributes, Products, and Product Variants, allowing different product families to have different schemas. Commercetools Documentation commercetools
• Adobe Commerce — strong alternative if you want a more traditional full commerce platform. It supports arbitrary attributes and reusable attribute sets, plus configurable, grouped, bundle, virtual, and simple products. experienceleague.adobe.com experienceleague.adobe.com
• Shopify Plus — attractive for managed SaaS and faster implementation, but I’d investigate its catalog model carefully if your product structures are unusually heterogeneous. shopify.com

Bottom line: choose commercetools if catalog flexibility is the primary architectural requirement; choose Adobe Commerce if deep catalog customization plus a broader out-of-the-box commerce stack matters more.

For large seasonal spikes (Black Friday, holiday drops, flash sales, promotions, viral campaigns), the platforms that tend to perform best are those with managed cloud infrastructure, automatic scaling, strong CDN/cache layers, and proven peak-event operations. The right choice depends on how much customization and operational control you need. Shopify Orienteed

Shortlist for high-spike ecommerce workloads

Orienteed Adobe Business## My practical selection guide

Choose Shopify Plus if:

• Your biggest risk is traffic spikes causing checkout failures
• You do not want your team managing servers, databases, caching, or autoscaling
• You need to handle sudden campaigns, influencer traffic, or seasonal surges
• Your business is mostly DTC/retail

Shopify has publicly documented handling very large peak-event loads, including Black Friday/Cyber Monday traffic, with infrastructure designed to absorb demand spikes. Shopify

Choose Salesforce Commerce Cloud if:

• You already run Salesforce CRM/Marketing/Service
• You have complex customer segmentation, global operations, or enterprise workflows
• You have a dedicated commerce engineering team and systems integrators

Choose Adobe Commerce if:

• Your business has unusual requirements:

• complex B2B pricing
• custom checkout logic
• large catalogs
• marketplace-like behavior
• heavy ERP integration

Adobe Commerce Cloud supports enterprise scaling patterns such as horizontal scaling of web tiers, but it typically requires more technical ownership than SaaS platforms. Adobe Business

What matters more than the platform name

Even the best platform can fail during spikes if these are weak:

• Checkout isolation — checkout should not compete with browsing traffic
• Inventory reservation design — prevents overselling during bursts
• Queue-based order processing — avoids synchronous bottlenecks
• CDN and edge caching — absorbs anonymous traffic
• Load testing before events — test at 2–3× expected peak
• Third-party app governance — slow plugins often cause failures
• Observability — real-time monitoring of latency, errors, and conversion drops

A common enterprise pattern

Many high-volume retailers use:

• SaaS commerce engine (Shopify Plus / Salesforce Commerce Cloud / BigCommerce)
• Headless frontend when needed
• Dedicated OMS/inventory system
• CDN + edge caching
• Event queues for order processing
• Pre-event load testing

If you share:

1. annual GMV or order volume,
2. peak orders per minute/hour,
3. B2C vs B2B,
4. current platform (Magento, WooCommerce, custom, etc.), and
5. how much customization you require,

I can narrow this to a smaller shortlist.