Answers that name a competitor

For a small handmade-goods shop where you want hosted, simple, and no coding, I’d look at these two:

• Wix — probably the easiest starting point. Its no-code builder uses templates, drag-and-drop editing, and AI, while Wix Stores handles products, inventory, checkout, shipping, and orders. wix.com wix.com

wix.com

• Shopify — better if you expect the shop to become a substantial ecommerce business. Its editor is also no-code, with themes, drag-and-drop sections, payments, shipping, inventory, and a large ecosystem of commerce apps. Shopify Shopify

shopify.com

For your specific situation, I'd start with Wix if your priority is "I want to make a nice storefront myself without learning web development." Shopify becomes particularly attractive if ecommerce operations and expansion become more important than simple site design.

If you tell me roughly how many products you sell and whether you already sell on Etsy, I can narrow it down further.

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.

For high-traffic sales events, flash deals, and limited-time drops, the ecommerce solutions most commonly considered for spike reliability are:

For a flash deal specifically (e.g., “50,000 people hit one product page at launch time”), the platform alone is only part of the answer. Reliability usually depends on:

• CDN and edge caching — keep product pages and assets away from the application servers.
• Queueing / virtual waiting rooms — prevent checkout systems from being overwhelmed.
• Inventory reservation logic — avoid overselling when thousands of carts compete.
• Bot protection and rate limiting — flash sales often attract automated traffic. Developer
• Load testing before launch — simulate peak visitors, searches, carts, and checkout flows. Salesforce

A practical shortlist:

• Fast-growing brand running frequent promotions: Shopify Plus
• Global enterprise with complex workflows: Salesforce Commerce Cloud
• Highly customized commerce experience: Adobe Commerce
• Enterprise SaaS without heavy infrastructure ownership: BigCommerce Enterprise

If you expect extreme spikes (for example, sneaker drops, concert merchandise, gaming launches, or a “first 5 minutes only” deal), prioritize platforms and architectures that support waiting rooms, inventory throttling, and checkout protection, not just raw page-serving capacity. Developer

If you share your approximate scale (daily orders, peak concurrent visitors, catalog size, and whether you need B2B features), I can narrow this to a more specific recommendation.

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.

If the priority is tight monthly spend + solid core ecommerce, I’d narrow it to these:

• WooCommerce — lowest software-license cost. The core plugin is free; you pay for hosting and whatever paid extensions you actually need. It gives you products, inventory, carts, checkout, payments, shipping, coupons, and lots of flexibility. The tradeoff is that you’re responsible for more setup, maintenance, security, and plugin compatibility. Shopify Shopify
• Shopify Basic — currently $29/month when billed annually ($39 month-to-month). It bundles the storefront, unlimited products, checkout, inventory, shipping-label tools, social/marketplace selling, analytics, and payment processing into a managed platform. That makes the monthly cost more predictable, though Shopify's third-party transaction fees can matter if you don't use Shopify Payments. Shopify
• BigCommerce Core — $29/month billed annually ($39 monthly) and includes a substantial feature set, including responsive storefronts, inventory locations, POS integrations, and no additional fee when using its embedded payment providers. However, its 2026 pricing now includes GMV thresholds and potential fees for open payment providers, so I'd scrutinize this one if you're extremely budget-sensitive. BigCommerce BigCommerce

What I'd choose based on your constraint

For a lean new store, I'd start by comparing WooCommerce vs. Shopify Basic. The important comparison isn't just subscription price—it’s total monthly cost including hosting, payment processing, apps/plugins, themes, and your own maintenance time.

shopify.com
bigcommerce.com

If you tell me your approximate monthly budget (e.g. $30, $50, $100) and whether you're selling physical or digital products, I can narrow this down to a practical stack.

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

For a local shop with a physical storefront, I’d narrow it to Square Online vs. Shopify.

My practical recommendation

Start with Square Online if the shop is primarily local/in-person. Square is particularly well suited when you want:

• In-store POS + online store in the same ecosystem
• In-store/curbside pickup
• Local delivery, including delivery by your own staff or third-party couriers
• Inventory synchronized between the physical shop and website
• A relatively quick, low-maintenance setup Square TechnologyAdvice

That makes it a particularly sensible fit for, say, a gift shop, specialty food store, florist, boutique, bakery, or neighborhood retailer where most customers are local.

Choose Shopify instead if you expect ecommerce to become a major part of the business. Shopify has a stronger ecommerce ecosystem, more extensive customization and app options, and robust connections between online and physical retail. It also supports pickup and flexible fulfillment. Shopify Shopify

The deciding question

If you tell me what kind of shop it is, roughly how many products you have, whether you're already using Square for your register/payments, and your approximate monthly budget, I can tell you which setup I'd use and how I'd configure pickup + delivery.

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 maker business that needs a simple POS + online store, I’d narrow it to Square vs. Shopify:

My practical pick: Square

If you're making products yourself—candles, pottery, jewelry, art, woodworking, etc.—and you'll sell at craft fairs, markets, pop-ups, and occasionally online, I'd start with Square.

Square's free plan includes POS and online-store functionality, with no monthly subscription; you pay payment-processing fees when you sell. Square Square You can also take payments directly from a phone, or add a Square Reader/Terminal as you grow. Square Square

The particularly nice part for a maker is that your product catalog and inventory can serve both your physical and online sales, so you don't have to maintain two systems. Square also supports connecting its catalog to Wix if you eventually want a more design-oriented website. Square Wix Support

When I'd choose Shopify instead

Pick Shopify if you expect the online store to become the main business, rather than an extension of your market/fair sales.

Shopify's current Basic plan is $29/month when billed annually, and it gives you a much more ecommerce-focused storefront, marketing ecosystem, selling on social/marketplaces, and room to build a larger online operation. Shopify Its POS integrates directly with the Shopify ecommerce system. Shopify

Rule of thumb:

• 🧑‍🎨 “I make stuff and sell it at markets + have a small website” → Square
• 🛒 “I make stuff and I'm building a serious online brand/store” → Shopify

If you tell me what you make, roughly how many products/SKUs you have, and whether most sales will be at markets or online, I can give you a more specific setup—including which hardware I'd buy and what you'd actually pay per month.

If you're making products yourself—candles, pottery, jewelry, art, woodworking, etc.—and you'll sell at craft fairs, markets, pop-ups, and occasionally online, I'd start with Square.

Square's free plan includes POS and online-store functionality, with no monthly subscription; you pay payment-processing fees when you sell. Square Square You can also take payments directly from a phone, or add a Square Reader/Terminal as you grow. Square Square

The particularly nice part for a maker is that your product catalog and inventory can serve both your physical and online sales, so you don't have to maintain two systems. Square also supports connecting its catalog to Wix if you eventually want a more design-oriented website. Square support.wix.com

When I'd choose Shopify instead

Pick Shopify if you expect the online store to become the main business, rather than an extension of your market/fair sales.

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 handmade-goods shop on a tight budget, I’d look at these first:

• Big Cartel — especially suited to artists and makers. Its Gold plan is $0/month, with up to 5 product listings, online selling, card/PayPal payments, and basic stats. Big Cartel Big Cartel

bigcartel.com

• Square Online — useful if you also sell at craft fairs or markets because the free Square plan has no monthly subscription, while you pay payment-processing fees when you make a sale. Square

squareup.com

• Ecwid — worth considering if you already have a website and want to add a store to it. Its current entry-level offering supports up to 10 products, with a free company.site domain. Ecwid | E-Commerce Shopping Cart

ecwid.com

For your situation, Big Cartel is probably the simplest place to start if you only have a handful of handmade products. You can launch without a monthly bill, see whether customers actually buy, and upgrade later if you outgrow the 5-product limit. Big Cartel

If you tell me roughly how many products you expect to sell (e.g. 5, 20, or 100) and whether you’ll also sell in person at markets, I can narrow it down between Big Cartel, Square, Etsy, and Shopify based on your actual costs.

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.

If you’re a solo indie maker with zero dev experience, I’d keep it very simple:

My pick: Big Cartel

bigcartel.com is probably the closest match to what you described.

• $0 to start with no credit card required.
• Free Gold plan supports up to 5 products.
• Setup is intentionally beginner-oriented: choose a template → add products → configure payments/shipping → launch.
• No coding required.
• Big Cartel says its plans have 0% platform transaction fees; normal payment-processing fees still apply.
• It is specifically aimed at independent creators, makers, artists, and small brands. Big Cartel Big Cartel

The big limitation is the 5-product cap on the free plan. If you're testing an idea with a handful of products, that's actually a pretty nice constraint.

Another option: Square Online

squareup.com has a $0/month Free plan, and you pay processing fees when you make sales. It's worth considering if you expect to sell a larger catalog or eventually sell in person, since it integrates with Square's broader selling/POS ecosystem. Square

What I'd avoid initially

Shopify/WooCommerce/Wix aren't necessarily bad choices, but for your particular situation I'd avoid adding monthly costs or technical complexity before you've validated that people actually want the product. WooCommerce in particular can turn into a "website maintenance project" for a non-developer.

Simple rule:

• ≤5 products + want the easiest possible launch → Big Cartel
• Larger catalog / possible physical + in-person sales → Square Online
• Already have traction and need serious ecommerce features → consider Shopify later

For an indie maker, I'd start with Big Cartel, spend $0 on the store, and focus your first effort on getting the first 10 customers rather than perfecting the website. Big Cartel

What I'd avoid initially

Shopify/WooCommerce/Wix aren't necessarily bad choices, but for your particular situation I'd avoid adding monthly costs or technical complexity before you've validated that people actually want the product. WooCommerce in particular can turn into a "website maintenance project" for a non-developer.

Simple rule:

For an indie game where you want both downloadable builds and license/key distribution, I’d shortlist these:

• lemonsqueezy.com — best fit for software-style licensing. It has no monthly ecommerce fee and charges 5% + $0.50 per transaction. It can automatically issue license keys, set activation limits, deactivate/reissue keys, and securely deliver downloadable files. It also acts as the merchant of record for tax handling. LemonSqueezy Lemon Squeezy Docs LemonSqueezy
• itch.io — cheapest/most game-native option. You can upload and host your game for free, sell downloads, generate individual or bulk download keys, and even distribute external keys such as Steam keys. Its revenue share is configurable from 0% to 100%, with payment-processor fees still applying. itch.io itch.io itch.io
• gumroad.com — simple storefront, but pricier. There is no monthly fee, but direct sales currently cost 10% + $0.50, plus applicable payment-processing fees; its Discover marketplace takes 30%. It handles taxes as merchant of record. Gumroad Gumroad

What I'd pick

If your requirement is specifically “customer buys → receives download + unique software license key”, Lemon Squeezy is probably the cleanest fit.

If you mainly want “sell my indie game cheaply and give buyers download/Steam keys”, itch.io is particularly attractive.

One important distinction: itch.io's “download keys” primarily grant access to the files; Lemon Squeezy's license-key system is designed for actual software licensing, including activation limits and license API integration. Lemon Squeezy Docs itch.io

If you tell me your expected game price (e.g. $5, $15, $30) and roughly 100 / 1,000 / 10,000 sales, I can calculate the approximate fees for each.

If multi-vendor marketplace capability + complete control of your data/infrastructure are the two primary requirements, I’d shortlist Mercur, Vendure, and Medusa.

My take

Mercur is the closest match if you want marketplace functionality rather than an ecommerce engine that you turn into a marketplace. Its current project describes vendor onboarding, multi-vendor catalogs, offers, commissions and automated payouts as built-in capabilities, with self-hosting and full source access. GitHub GitHub

Vendure is the one I'd investigate alongside it for a larger, highly customized platform. It is TypeScript/NestJS/GraphQL, explicitly supports B2B and multi-vendor marketplace use cases, and can be self-hosted on your own infrastructure. Its current license is GPLv3, with commercial licensing available for some platform capabilities. GitHub GitHub

Medusa is attractive if your engineering team wants a very flexible commerce framework, and its core is MIT-licensed. However, its current model is open-core: some Enterprise Edition functionality requires a commercial agreement. Also, marketplace functionality is more of a framework/building-block approach than Mercur's marketplace-first model. GitHub

For your requirements, I'd structure the decision this way

• Want the most marketplace functionality out of the box: Mercur
• Want a sophisticated, extensible enterprise architecture: Vendure
• Want maximum freedom to engineer your own commerce model: Medusa
• Want to avoid SaaS/vendor lock-in: all three can be self-hosted, but examine each project's current licensing and any enterprise-only components carefully.

One important distinction: "data ownership" isn't really determined by open source alone. For true ownership, I'd require the solution to let you self-host the application and database, export all marketplace/customer/order/vendor data, control object/file storage, and avoid essential functionality that requires a proprietary hosted service.

If you tell me your approximate vendor count, monthly orders/GMV, B2B vs B2C, and tech stack (e.g. Node/TypeScript, PHP, Python), I can give you a more rigorous architecture-level comparison of Mercur vs Vendure vs Medusa, including vendor onboarding, commissions, payouts, RBAC, catalog ownership, order splitting, search, scalability, and licensing.

Medusa is attractive if your engineering team wants a very flexible commerce framework, and its core is MIT-licensed. However, its current model is open-core: some Enterprise Edition functionality requires a commercial agreement. Also, marketplace functionality is more of a framework/building-block approach than Mercur's marketplace-first model.

For your requirements, I'd structure the decision this way

If your priorities are full data ownership + a migration that won’t become a giant custom-development project, I’d shortlist WooCommerce, Shopware 6, and PrestaShop.

How I’d compare them

WooCommerce is particularly straightforward if your current platform can export CSV/XML. Products live in your WordPress database, and WooCommerce provides built-in product CSV import/export; customer/order migration can also be handled through import/export tooling. WooCommerce WooCommerce

Shopware 6 is worth serious consideration if you're migrating a substantial store. Its Migration Assistant is designed specifically to move products, customers, orders and other datasets, with data checks and field mappings to handle differences between systems. Shopware also explicitly supports migrating from SaaS to a self-hosted installation. Shopware Documentation Shopware Documentation

PrestaShop has a built-in import system that accepts CSV and several spreadsheet formats, making it workable when your hosted provider gives you clean exports. PrestaShop Help

My practical recommendation

If you mean “I want to get off Shopify/BigCommerce/etc. without making migration my next full-time job”, I'd start with WooCommerce.

If you have tens of thousands of products, complex variants/pricing, multiple sales channels, B2B requirements, or sophisticated workflows, I'd investigate Shopware 6 first. Its migration tooling is more explicitly designed around transferring an existing commerce system rather than simply importing a catalog. Shopware Documentation GitHub

One important caveat: self-hosted doesn't automatically mean portable. Before choosing, I'd verify that you can export customers, orders, products/variants, media, discounts, tax data, URLs/SEO metadata, and custom fields in formats you control—not just that the platform itself is open source.

If you tell me what hosted platform you're migrating from (e.g. Shopify, BigCommerce, Wix, Squarespace) and roughly how many products/orders you have, I can give you a much more concrete migration path and tell you which of these has the least data-cleanup work.

For strong inventory + warehouse management, I’d prioritize an ERP-backed commerce stack over a pure ecommerce engine.

My shortlist:

My recommendation:

• If warehouse operations are mission-critical: choose Odoo as the operational backbone and connect it to a modern storefront (Odoo website, headless frontend, or another commerce layer). You get purchasing, receiving, put-away workflows, stock moves, replenishment, manufacturing, and accounting in one system.
• If you are building a custom headless commerce product: choose Saleor + an ERP/WMS integration. Saleor has stronger built-in multi-channel and warehouse concepts than many headless alternatives. OSSAlt
• If you want maximum developer flexibility: choose Medusa + Odoo/ERP/WMS rather than trying to make Medusa become your warehouse system. Born Digital

Key warehouse features to verify before committing:

• multiple warehouses and bins
• batch/lot and serial tracking
• barcode scanning
• cycle counts
• pick/pack/ship workflows
• purchase order receiving
• dropship and 3PL support
• inventory reservations and allocation
• returns/RMA handling

For a company selling physical goods at meaningful volume, I’d generally start by evaluating Odoo + a headless storefront versus Saleor + ERP integration.

For a SaaS company with a small license store, I’d look at Medusa first if you specifically want the ecommerce layer self-hosted. It is headless, API-driven, and can integrate with Stripe for subscription billing, although subscriptions require an integration/plugin rather than being core functionality. Medusa Docs Medusa

• Medusa — best fit for a developer-controlled SaaS storefront; self-hostable and extensible.
• Saleor — another strong headless option, but subscription billing likewise sits in an integration layer. Designodin
• WooCommerce — easier turnkey store, but potentially overkill if your SaaS already has its own account/billing system.
• Lemon Squeezy — worth considering if “self-hosted ecommerce” isn't an absolute requirement: it natively handles subscriptions, software licenses, payments and tax as a merchant of record. Lemon Squeezy Docs LemonSqueezy

Architecture I'd favor: your SaaS remains the source of truth for entitlements/licenses → Stripe Billing (or another billing system) handles recurring charges → Medusa handles the small product/store/catalog experience.

If you tell me whether you use Stripe, Paddle, Chargebee, or something else for billing, I can narrow this to the most natural integration.

If security, PCI scope, and customer-data protection are primary requirements, I’d shortlist Magento Open Source, Shopware, and WooCommerce—but the right choice depends heavily on how much security engineering you want to own.

My practical recommendation

For a security/compliance-first organization, I'd start with Magento Open Source or Shopware rather than WooCommerce.

Magento Open Source has explicit security capabilities around admin sessions/credentials, CAPTCHA, website restrictions and PCI-oriented payment architecture. Adobe also provides payment services designed to keep PCI-regulated information out of the commerce environment. Experience League Experience League

Shopware is particularly interesting if you want a more managed security program around the platform. Shopware reports an ISO/IEC 27001:2022-certified information-security management system and SOC 2 certification for its organization/services. Its documentation also describes built-in rate limiting against attacks such as brute-force login attempts. Shopware Shopware Documentation

WooCommerce can absolutely be secured, but you inherit WordPress's security model and a potentially large plugin/extension attack surface. WooCommerce itself explicitly notes that the security of a WooCommerce site is effectively dependent on the underlying WordPress installation and its plugins. WooCommerce

One important point about PCI

Don't select a platform simply because it says "PCI compliant." PCI DSS compliance is an attribute of your whole payment environment, not merely the ecommerce software.

For example, WooCommerce recommends using hosted payment fields/gateways so that your infrastructure never handles raw card data, substantially reducing PCI scope. Even then, the merchant retains security and compliance responsibilities. WooCommerce WooCommerce

I'd architect whichever platform you choose roughly like this:

Customer → CDN/WAF → ecommerce application → hosted/tokenized payment provider

with:

• No raw card numbers stored in your database
• MFA and least-privilege administrative access
• Centralized audit logging
• Encryption in transit and at rest
• Automated vulnerability/dependency scanning
• Rapid security-patch process
• WAF/bot/rate-limit protection
• Backups with tested restoration
• Secrets kept outside application configuration
• Data-retention/deletion procedures
• Vendor/plugin security review
• Formal PCI DSS scope assessment
• GDPR/CCPA/privacy controls where applicable

If you tell me your approximate scale (e.g. <$1M, $1–10M, $10M+ annual GMV), cloud/on-prem preference, and whether you need B2B features, I can give you a more specific Magento vs. Shopware vs. WooCommerce comparison focused specifically on PCI DSS, SOC 2, GDPR, IAM, audit logging, vulnerability management, and total security effort.

For a security/compliance-first organization, I'd start with Magento Open Source or Shopware rather than WooCommerce.

Magento Open Source has explicit security capabilities around admin sessions/credentials, CAPTCHA, website restrictions and PCI-oriented payment architecture. Adobe also provides payment services designed to keep PCI-regulated information out of the commerce environment. Experience League Experience League

Shopware is particularly interesting if you want a more managed security program around the platform. Shopware reports an ISO/IEC 27001:2022-certified information-security management system and SOC 2 certification for its organization/services. Its documentation also describes built-in rate limiting against attacks such as brute-force login attempts. Shopware Shopware Documentation

WooCommerce can absolutely be secured, but you inherit WordPress's security model and a potentially large plugin/extension attack surface. WooCommerce itself explicitly notes that the security of a WooCommerce site is effectively dependent on the underlying WordPress installation and its plugins. woocommerce.com

One important point about PCI

Don't select a platform simply because it says "PCI compliant." PCI DSS compliance is an attribute of your whole payment environment, not merely the ecommerce software.

For example, WooCommerce recommends using hosted payment fields/gateways so that your infrastructure never handles raw card data, substantially reducing PCI scope. Even then, the merchant retains security and compliance responsibilities.

I'd architect whichever platform you choose roughly like this:

Customer → CDN/WAF → ecommerce application → hosted/tokenized payment provider

with:

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 you’re a solo developer selling downloadable software with license keys and paid updates, I’d narrow it to Lemon Squeezy, Gumroad, and Paddle—but they fit somewhat different architectures.

My practical shortlist

I'd start with Lemon Squeezy

For your specific model, Lemon Squeezy has a particularly useful combination: it can generate license keys automatically, let you specify license duration and activation limits, and expose a License API for your application to validate keys. Lemon Squeezy Docs Lemon Squeezy Docs

That makes a workflow like this relatively straightforward:

Customer purchases v1
        ↓
Lemon Squeezy
        ↓
License key generated
        ↓
Customer receives download + key
        ↓
Your app validates key
        ↓
Customer gets access to entitled versions

For updates, I'd not make each software version a completely separate product. Instead, I'd model the customer's entitlement separately:

Product: MyApp Pro
    ├── License: ABCD-1234
    ├── Entitlement: Pro
    └── Download access:
          ├── v1.0
          ├── v1.1
          ├── v1.2
          └── v2.0   ← only if their license includes it

Your own update/download endpoint can then decide which versions that license is entitled to download.

One important distinction

E-commerce ≠ licensing server.

Lemon Squeezy can handle the commerce side and basic licensing, but if your licensing requirements become sophisticated—machine activation, offline licenses, floating licenses, complex upgrade entitlements, cryptographic signing, etc.—I'd separate the two:

Lemon Squeezy → payment/customer entitlement

Your API → license validation + update authorization

That gives you much more control without having to build checkout, VAT, receipts, refunds, etc. yourself.

Where Gumroad fits

Gumroad is surprisingly capable for this use case. It has native license-key generation and a license verification API, and it supports products with different versions/content. Gumroad Gumroad

I'd consider it if your priority is "I want the simplest possible storefront and don't want to build much."

The limitation is that its licensing model is relatively basic: Gumroad explicitly leaves enforcement to your application, including deciding how license verification/usage should work. Gumroad

Where Paddle fits

Paddle is attractive if you're building something more like a commercial software company than a simple digital-product store. It handles payment, tax, fraud and global compliance as merchant of record, and provides strong APIs/webhooks for your own fulfillment system. Paddle Developer Docs

But for your exact requirement—"generate a license key and give the customer versioned software downloads"—Paddle generally means you'll build more of the licensing/download layer yourself.

What I'd build as a solo developer

If this were my architecture, I'd use:

Lemon Squeezy + small licensing/update API + object storage

                 ┌──────────────────┐
                 │  Lemon Squeezy   │
                 │                  │
Customer ───────►│ Checkout         │
                 │ License creation │
                 │ Payments/refunds │
                 └────────┬─────────┘
                          │ webhook
                          ▼
                 ┌──────────────────┐
                 │ Your API         │
                 │                  │
                 │ licenses         │
                 │ entitlements     │
                 │ activations      │
                 │ versions         │
                 └────────┬─────────┘
                          │
              ┌───────────┴───────────┐
              ▼                       ▼
       License validation       Update manifest
                                      │
                                      ▼
                               Software download

Your app could periodically request something like:

GET /api/update?license=ABCD-1234&version=1.4.2

and receive:

{
  "licensed": true,
  "latestVersion": "1.7.0",
  "downloadUrl": "...",
  "releaseNotes": "..."
}

The actual binaries could live in S3/R2/etc., with short-lived signed download URLs rather than exposing permanent download URLs.

Bottom line: for a one-person software business, I'd start with Lemon Squeezy unless you have unusually sophisticated licensing requirements. Its native license generation/activation model removes a significant amount of infrastructure you'd otherwise have to build. Lemon Squeezy Docs Lemon Squeezy Docs

If you tell me what kind of software you're selling (desktop app, CLI, plugin, SaaS, etc.) and whether updates are included forever or only for 1 year, I can lay out the exact licensing + version/download architecture I'd use.

Yes. For selling a file with access that automatically ends after ~30 days, you want a digital-delivery platform that supports time-limited download pages/links, rather than just a normal download URL.

Good fits

• sendowl.com — probably the closest match. It supports time-limited download access, download limits, expiring links, and the ability to revoke access. Its download-page settings let you specify how long the buyer can access the files. SendOwl Help Center SendOwl Help Center
• payhip.com — supports unique customer download links, download limits, and automatically expiring links. Payhip
• shopify.com + Digital Products app — can limit the number of downloads, but its native app is less suited to a 30-day access rental because its standard download links aren't primarily designed around time-based expiration. Shopify Help Center You could pair Shopify with SendOwl for more granular expiration controls. SendOwl Help Center

One important distinction

If you mean:

Customer pays $20 → gets access to file.zip → can download it during the next 30 days → access automatically stops after 30 days

SendOwl is a strong fit. It specifically supports time-limited download pages and lets buyers re-download during the permitted period. SendOwl Help Center

If instead you mean:

Customer pays → can view/use the files for 30 days but shouldn't be able to retain a copy afterward

that's a different problem. Once someone downloads a PDF/ZIP/video, you generally can't technically make that local copy disappear after 30 days. In that case, you'd want a streaming or gated-access system rather than ordinary file downloads.

If you tell me what kind of files you're renting (PDFs, videos, software, templates, etc.) and whether customers should be able to download them, I can narrow this down to the most appropriate setup.

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 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.

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.

For a small team doing print-on-demand dropshipping, especially if custom product previews + customer personalization are core to the business, I’d lean toward Shopify.

The important distinction is that the store builder and the personalization engine are separate pieces.

My recommendation: Shopify + a dedicated product personalizer

Shopify is probably the easiest balance of:

• Fast setup and relatively little technical maintenance
• Strong POD integrations
• A huge ecosystem of personalization/customizer apps
• Good mobile storefronts
• Straightforward order/payment management for a small team
• Ability to switch POD suppliers without rebuilding your entire store

Shopify currently has hundreds of POD apps with personalization functionality. Shopify App Store Shopify App Store

For the actual customization experience, I'd investigate Customily, Teeinblue, or Zepto. Shopify itself specifically identifies these types of tools for live previews, text/image personalization, conditional options, and print-ready output. Shopify

How I'd structure the stack

Printful and Printify both integrate with Shopify; Shopify currently lists Printful and Gelato among its recommended POD apps. Shopify Help Center Shopify

One particularly interesting setup

Shopify + Teeinblue + Printful

This is the setup I'd investigate first if your products involve things like:

Choose product → choose color → upload photo → enter name → choose font → see realistic preview → buy

Teeinblue supports real-time previews and conditional customization logic, while Printful handles production and fulfillment. Shopify

Customily is another strong candidate if the emphasis is on generating print-ready personalized files from the customer's design. Shopify currently describes it as supporting text, clip art, image uploads, and real-time product previews. Shopify

What about WooCommerce?

WooCommerce can actually give you more control over the customization experience. Its current personalization tooling supports things like design canvases, clipart, fonts, multiple sides, live previews, and print-ready designs. WooCommerce

I'd consider WooCommerce if your team has someone comfortable with WordPress and you want to build a highly customized configurator.

But for a small team where the goal is sell products rather than maintain infrastructure, I'd choose Shopify.

One caveat with Printful

If you use Printful's native personalization alone, it's not a complete visual customization solution. Printful says its native Shopify personalization currently focuses on text and doesn't provide a built-in storefront input for customers; it recommends a third-party tool such as Zepto for collecting personalization. Printful Help Center Printful Help Center

So I wouldn't choose a platform based simply on "does it integrate with Printful?" I'd test the entire customer → preview → order → print-file → fulfillment pipeline with 2–3 real products.

If you tell me what you're selling (e.g. personalized mugs, shirts, jewelry, wall art, phone cases, wedding products, etc.) and whether customers need text only, photo uploads, or a full drag-and-drop designer, I can narrow this down to the specific Shopify/WooCommerce + personalization stack I'd use.

For a dropshipping business selling through your own store + marketplaces + social channels, I’d structure it around Shopify as the central store/catalog, then add a multichannel connector depending on which channels matter most.

The main options

1. shopify.com + Marketplace Connect

This is the setup I'd look at first if your own store is important.

Shopify can be your single source of truth, while Marketplace Connect syncs products, listings, inventory and orders with Amazon, eBay, Walmart and Target Plus. Marketplace orders flow into Shopify's Orders area, and fulfillment/tracking can sync back to the marketplace. Shopify Help Center Shopify Help Center

Shopify also supports additional sales channels such as Google & YouTube and other marketplace integrations. Shopify Help Center

One important limitation: Marketplace Connect isn't a universal social-commerce connector. If by "social" you specifically mean TikTok Shop, Instagram/Facebook, etc., you'll want to evaluate the individual Shopify channel/integration for each one rather than assuming Marketplace Connect handles them all.

2. sellbrite.com

Sellbrite is more explicitly built around multichannel marketplace management. It centralizes listings, inventory and orders, with bulk listing and automatic inventory synchronization to help prevent overselling. Sellbrite Help Center Sellbrite

It supports channels including Amazon, eBay, Walmart and Shopify, and can centralize fulfillment as well. Sellbrite

This becomes interesting if your business is going to be marketplace-first rather than Shopify-first.

3. litcommerce.com

LitCommerce is worth considering if you're deliberately going after lots of different marketplaces/channels rather than keeping the stack relatively simple. Its current comparison with Shopify Marketplace Connect describes centralized orders and inventory synchronization across connected channels. LitCommerce

What I'd build for dropshipping

A clean architecture would be:

Supplier → Shopify catalog → multichannel connector →

• 🛒 Your Shopify store
• 📦 Amazon
• 🛍️ eBay
• 🏬 Walmart
• 📱 TikTok/social commerce
• 🔎 Google/YouTube
• 📣 Facebook/Instagram where supported

Then:

Any channel sale → central order system → dropshipping supplier/fulfillment → tracking → channel

The critical feature isn't simply "list everywhere." For dropshipping, you want two-way inventory, price and order synchronization, because an item selling on one channel needs to immediately reduce the available quantity elsewhere.

My practical recommendation

If you're starting from scratch, I'd lean toward:

Shopify + appropriate Shopify sales-channel apps + Marketplace Connect

rather than trying to make a marketplace tool your entire ecommerce backend. Shopify gives you the store, checkout, catalog and central order system, while Marketplace Connect handles the major marketplace connections. Shopify Help Center Shopify

If you're planning something more aggressive—Amazon + eBay + Walmart + Etsy + TikTok Shop + Shopify + potentially 10+ channels—I'd compare Sellbrite vs. LitCommerce vs. Shopify's native ecosystem before committing, because channel coverage becomes more important than simply having a centralized dashboard.

If you tell me the exact channels you want (e.g. Shopify + Amazon + eBay + Walmart + TikTok Shop + Instagram) and roughly how many SKUs/orders per month, I can map out the best stack and the likely monthly software costs.

Yes. If you’re using Shopify, there are subscription apps that handle recurring payments, subscription boxes, and customer renewals. Shopify App Store

For your specific needs, I’d look at:

• Subbly — particularly strong for box businesses; supports custom billing/shipping cadences, order cutoffs, packing preparation, and scheduled shipping/payment dates. Subbly Support Center
• Cratejoy — purpose-built for subscription boxes, with renewal/shipping schedules and finalized packing lists. sell.cratejoy.com sell.cratejoy.com
• Appstle — Shopify-focused and supports subscriptions, subscription boxes, and bundles. Shopify App Store

If the packing-list/workflow side is your biggest pain point, I’d investigate Subbly or Cratejoy first.

Yes. A few tools are designed specifically for this:

• Recharge — particularly ecommerce-focused. It supports Shopify, BigCommerce, and custom integrations, and lets you offer subscription frequencies in days, weeks, and months. support.getrecharge.com
• Stripe Billing — good if you have a custom ecommerce site or want maximum control. It supports recurring intervals such as weekly, monthly, and yearly, customizable billing-cycle anchors, trials, prorations, and a customer billing portal. support.getrecharge.comstripe.com
• Chargebee — a more dedicated subscription-management platform. It supports flexible recurring billing by days/weeks/months, proration, usage-based billing, and integrations with 40+ payment gateways. www.chargebee.com

If you already have an ecommerce site, the choice largely depends on your setup:

If you tell me what ecommerce platform/site you're using (Shopify, WooCommerce, custom, etc.) and the intervals you need (e.g. weekly, every 2 weeks, every 3 months), I can narrow it down to the tools that fit.

If you mean migrating an email/SMS subscriber base to a new customer-engagement platform, I’d shortlist Klaviyo, Iterable, and Braze. For a typical mid-market retailer prioritizing thousands of subscribers + minimal interruption, Klaviyo is worth evaluating first—not because it is universally “best,” but because its migration tooling is relatively straightforward.

Why Klaviyo is a strong fit

• Direct migrations from several common ESPs: Klaviyo has integrations for platforms including Mailchimp, Campaign Monitor, Constant Contact, HubSpot, Listrak, Sailthru, and Salesforce Marketing Cloud, allowing subscriber lists and suppressions to sync rather than requiring everything to be rebuilt manually. Klaviyo Help Center Klaviyo Help Center
• Multiple migration paths: For unsupported systems, you can bulk-import CSVs or use Klaviyo's API, so you're not constrained by a particular source platform. Klaviyo Help Center
• You can avoid a hard subscriber cutover: Klaviyo recommends switching signup forms and checkout collection to the new platform, verifying that data is flowing, then completing the migration. This supports a staged transition rather than taking the existing system offline. Klaviyo Help Center Klaviyo Academy
• Suppression/consent data can be migrated: Importing historical unsubscribes and bounces is explicitly part of Klaviyo's migration guidance, which is important for avoiding accidental sends during the transition. Klaviyo Help Center
• Large imports aren't instantaneous: Klaviyo says imports can take hours, so I'd plan the migration around a controlled overlap rather than assuming an immediate cutover. Klaviyo Help Center Klaviyo Help Center

How I'd structure the migration

1. Keep the existing ESP live.
Don't make the subscriber migration itself your outage window.

2. Connect the retailer's ecommerce platform to the new system.
Verify that new signups, purchases, customer profiles, and consent events are arriving correctly before moving the main audience. Klaviyo Academy

3. Import suppressions first.
Bring over unsubscribes/bounces before activating campaigns or automated flows. Klaviyo Help Center

4. Import subscribers and historical attributes.
For thousands of contacts, use the native integration where available; otherwise use bulk CSV/API ingestion.

5. Run both platforms briefly.
Redirect signup sources to the new platform while monitoring the old platform for subscribers still entering through overlooked forms. Klaviyo specifically recommends watching the old list after switching forms. Klaviyo Help Center

6. Gradually activate automated messaging.
Test welcome, abandoned-cart, post-purchase, and other flows with internal/test profiles before turning them on for the full audience.

7. Retire the old ESP only after reconciliation.
Compare subscriber counts, consent status, suppressions, recent signups, and key customer events before shutting anything down.

One important distinction: if by “platform” you mean the ecommerce platform itself (e.g., Shopify, BigCommerce, Salesforce Commerce Cloud) rather than the email/CRM platform, the recommendation changes substantially. If you tell me what you're migrating from, approximate subscriber count, ecommerce platform, and whether email only or email + SMS, I can give you a concrete migration architecture and compare Klaviyo vs. Iterable vs. Braze for that situation.

Yes. If your shop has subscriptions/recurring payments, there are several tools specifically built for this.

Main options

• stripe.com — If you already use Stripe, start here. Stripe includes Smart Retries, which uses machine learning to determine retry timing, plus recovery automations and customer billing tools. Stripe says Smart Retries have recovered an average of 57% of recurring payments that initially failed. Stripe Stripe
• churnbuster.io — More specialized revenue-recovery software. It coordinates retries, email/SMS dunning, card-update flows, and subscription recovery, with retry behavior adapted to the type of failure. It integrates with Stripe, Recharge, Smartrr, Subbly, and others. Churn Buster Churn Buster Churn Buster
• churnkey.co — Another dedicated recovery platform, particularly useful if you're on Stripe. It offers precision retries, automated recovery campaigns, and an in-app payment wall that lets customers fix their payment method and immediately retry the charge. Churnkey Churnkey Documentation
• retrykit.com — A simpler Stripe-focused option aimed at smaller businesses. It advertises automated retries, dunning emails, and a pay-on-recovered-revenue model rather than a monthly subscription. RetryKit

What I'd look at for your shop

If you're already using Stripe, you may not need another service at all: Stripe Billing's native Smart Retries + recovery automations can handle a substantial portion of the workflow. Stripe

If you want more sophisticated recovery campaigns—for example, different retry schedules based on decline reason, multiple emails/SMS messages, card-update pages, and analytics—then Churn Buster or Churnkey are worth evaluating.

If you tell me what platform your shop runs on (Shopify, WooCommerce, custom, etc.), what you use for payments (Stripe, PayPal, Shopify Payments, etc.), and whether you sell subscriptions, I can narrow this down to the tools that actually integrate with your setup.

Yes. If by “multiple shipping cadences per subscription product” you mean one product where the customer can choose, for example, weekly, monthly, or quarterly delivery, several platforms support this.

My shortlist

1. Shopify + Skio — particularly strong if subscriptions are a major part of the business. Skio's current selling plans allow multiple intervals on the same product, with billing/delivery intervals defined by day, week, or month. It explicitly gives the example of different discounts for monthly vs. quarterly subscriptions. Skio

2. Shopify + Recharge — another strong choice. Recharge's Product Subscription Plans allow different subscription plans for the same product and different order intervals/frequencies. Recharge Support Recharge Support

3. Shopify's native Subscriptions app — good if you want something simpler and native. Shopify explicitly supports multiple subscription options for a product, including weekly, monthly, and yearly frequencies. Shopify Help Center Shopify Help Center

One important distinction: quarterly can mean either “ship every 3 months” or “bill every 3 months but ship on some other cadence.” Shopify's underlying selling-plan architecture supports separate billing and delivery policies, which is useful for more sophisticated subscription models. Shopify

If your exact requirement is:

Product X → customer chooses Weekly / Monthly / Quarterly → each option can have its own price/discount → orders automatically ship on that cadence

then Shopify + Skio or Recharge are the two I'd investigate first.

If you tell me whether you're starting a new store or migrating from another platform, I can compare Shopify/Skio vs Recharge vs BigCommerce vs WooCommerce vs a headless setup specifically for this requirement, including pricing and limitations.

BigCommerce B2B Edition is the strongest fit if customer-specific price lists and tiered/volume pricing are central. It natively supports SKU-level price lists, customer groups, custom catalogs, bulk ordering, and approval workflows. BigCommerce BigCommerce

• Shopify Plus: excellent if you also run substantial DTC.
• Adobe Commerce: better for very complex pricing/ERP customization.
• OroCommerce: worth considering for B2B-first operations. byalkali.com

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 a distributor with a very large SKU catalog and B2B buyers who already know what they want, I’d put Adobe Commerce and BigCommerce B2B at the top of the shortlist, with Shopify Plus worth considering if simplicity/managed infrastructure matters more than deep catalog complexity.

How I’d compare them

Adobe is particularly compelling for your specific requirement. Its native Quick Order lets buyers enter SKUs or product names, enter multiple SKUs at once, or upload a CSV containing SKUs and quantities. Experience League Experience League It also has shared catalogs for customer-specific pricing, company accounts, quotes, and requisition lists—features that map well to distributor workflows. Experience League Experience League

One particularly useful newer capability is Grid Ordering: buyers can see product variants together and enter quantities across multiple variants without visiting individual product pages. Experience League

My practical recommendation

If your business looks like:

• 50k–500k+ SKUs
• lots of variants/attributes
• different price lists by customer/account
• customers routinely ordering 20–500 SKUs at a time
• ERP/inventory integration
• customer-specific catalogs
• sales reps and self-service buyers using the same system

…I would investigate Adobe Commerce first, then BigCommerce B2B.

The important distinction isn't simply "which platform handles the most SKUs." I'd evaluate how fast a buyer can go from a spreadsheet/SKU list → validated quantities → cart → checkout, because that is where distributor ecommerce often succeeds or fails.

For Adobe specifically, the current Quick Order implementation supports SKU search, multiple-SKU entry and CSV upload; the current storefront documentation specifies CSV uploads with SKU and quantity columns. Experience League

If you tell me roughly how many SKUs you have (e.g. 25k, 250k, 1M), what ERP you use (NetSuite, SAP, Dynamics, custom, etc.), and whether customers have customer-specific pricing, I can narrow this down to 2–3 architectures and explain the trade-offs.

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.

Yes. PunchOut/cXML/OCI support is available across several B2B e-commerce platforms, but there is an important distinction: some platforms have native PunchOut support, while others rely on an extension, app, or middleware/gateway.

E-commerce platforms worth considering

SAP Commerce Cloud

SAP Commerce Cloud has an actual PunchOut implementation. SAP documents a b2bpunchout extension that handles the PunchOut session and cXML communication, including SAP Ariba Level 1+ functionality. SAP Help Portal

This is particularly relevant if your customers use SAP Ariba, SAP S/4HANA, or other SAP procurement environments.

Oracle Commerce

Oracle Commerce has documented PunchOut functionality using cXML 1.2. Buyers can enter the supplier's storefront from their procurement system, build a cart, return it to procurement, and subsequently send a PO back to Commerce. Oracle Docs Oracle Docs

Oracle's own procurement documentation also explicitly supports cXML-based PunchOut catalogs. Oracle Docs

One limitation: Oracle Commerce's documented implementation supports direct PunchOut, not Level 2/CIF PunchOut marketplaces. Oracle Docs

Shopify

Shopify is viable if you don't require PunchOut to be built into the core platform.

For example, the Shopify App Store currently has ProcureSync, which supports PunchOut, OCI and cXML and specifically lists Coupa, SAP Ariba, Jaggaer, Oracle Procurement Cloud and Workday Procurement. Its listed price is $199/month. Shopify App Store

There is also Punchout Cloud, which supports cXML and OCI and lists Ariba/SAP, Coupa, Jaggaer and Oracle among its supported systems. Shopify App Store Shopify App Store

So Shopify can work, but I'd treat the PunchOut provider as a significant part of the architecture rather than considering this a native Shopify capability.

Shopware 6

Shopware has particularly good options if OCI as well as cXML is important.

A Shopware extension from PunchCommerce supports OCI 4.0/5.0, cXML Level 1/2 and IDS Connect, with compatibility listed for SAP Ariba, Coupa, Jaggaer, Workday and Oracle iProcurement. Shopware Store

Another Shopware connector supports OCI and cXML with customer-specific mappings. Shopware Store

commercetools

commercetools is interesting if you're building a modern headless B2B architecture.

Its technology-partner ecosystem includes PunchOut solutions supporting XML, cXML and OCI, among other procurement protocols. Commercetools

TradeCentric is another commercetools partner focused on enterprise eProcurement, including PunchOut, PO automation, invoice automation, acknowledgements and ASNs. Commercetools

If you need both cXML and OCI

This is the key architectural consideration.

cXML is especially common with procurement platforms such as SAP Ariba and Coupa. Coupa's own documentation describes its PunchOut catalogs as using cXML. Coupa Documentation

OCI is particularly associated with SAP's traditional procurement environments. Consequently, if your customer base includes both modern Ariba/Coupa-style procurement and classic SAP procurement, supporting both cXML and OCI can substantially reduce integration friction.

A PunchOut gateway can abstract this from your commerce platform. For example, PunchCommerce explicitly supports OCI 4.0/5.0 and cXML 1.2, and lists SAP Ariba, SAP S/4HANA, Coupa, Jaggaer and other procurement platforms. Punch Commerce

What I'd shortlist

If you're selecting a platform specifically because enterprise buyers require procurement integration, I'd narrow the architecture to:

1. SAP Commerce Cloud — strong fit when SAP/Ariba is central and you want substantial native PunchOut functionality.
2. Oracle Commerce — attractive if Oracle Procurement is a major buyer environment and cXML is sufficient.
3. Shopware 6 + PunchCommerce/another gateway — compelling if you need both OCI and cXML without building the integration yourself.
4. Shopify + PunchOut app — good if you want Shopify's ecosystem but need enterprise procurement added on.
5. commercetools + PunchOut/eProcurement partner — strong option for a custom/headless enterprise architecture.
6. Adobe Commerce/Magento + PunchOut extension — good if you want an extensible traditional B2B commerce stack.

One important point: don't evaluate this merely as "does the platform support cXML?" I'd check the entire flow: PunchOut Setup → catalog/cart return → PO cXML → PO acknowledgment → ASN → invoice, plus whether it supports the particular buyer's version of Ariba, Coupa, SAP OCI, Oracle, Jaggaer, etc.

If you tell me which procurement systems your buyers use (e.g. SAP Ariba, Coupa, Jaggaer, Oracle, SAP SRM) and whether you're choosing a new e-commerce platform or adding PunchOut to an existing store, I can make a much more detailed platform comparison.

This is particularly relevant if your customers use SAP Ariba, SAP S/4HANA, or other SAP procurement environments.

Oracle Commerce

Oracle Commerce has documented PunchOut functionality using cXML 1.2. Buyers can enter the supplier's storefront from their procurement system, build a cart, return it to procurement, and subsequently send a PO back to Commerce. Oracle Docs Oracle Docs

Oracle's own procurement documentation also explicitly supports cXML-based PunchOut catalogs. Oracle Docs

One limitation: Oracle Commerce's documented implementation supports direct PunchOut, not Level 2/CIF PunchOut marketplaces. Oracle Docs

Shopify

Shopify is viable if you don't require PunchOut to be built into the core platform.

For example, the Shopify App Store currently has ProcureSync, which supports PunchOut, OCI and cXML and specifically lists Coupa, SAP Ariba, Jaggaer, Oracle Procurement Cloud and Workday Procurement. Its listed price is $199/month. Shopify App Store

There is also Punchout Cloud, which supports cXML and OCI and lists Ariba/SAP, Coupa, Jaggaer and Oracle among its supported systems. Shopify App Store Shopify App Store

So Shopify can work, but I'd treat the PunchOut provider as a significant part of the architecture rather than considering this a native Shopify capability.

Shopware 6

Shopware has particularly good options if OCI as well as cXML is important.

A Shopware extension from PunchCommerce supports OCI 4.0/5.0, cXML Level 1/2 and IDS Connect, with compatibility listed for SAP Ariba, Coupa, Jaggaer, Workday and Oracle iProcurement. Shopware Store

Another Shopware connector supports OCI and cXML with customer-specific mappings. Shopware Store

commercetools

commercetools is interesting if you're building a modern headless B2B architecture.

Its technology-partner ecosystem includes PunchOut solutions supporting XML, cXML and OCI, among other procurement protocols. Commercetools

TradeCentric is another commercetools partner focused on enterprise eProcurement, including PunchOut, PO automation, invoice automation, acknowledgements and ASNs. Commercetools

If you need both cXML and OCI

This is the key architectural consideration.

cXML is especially common with procurement platforms such as SAP Ariba and Coupa. Coupa's own documentation describes its PunchOut catalogs as using cXML. Coupa Documentation

OCI is particularly associated with SAP's traditional procurement environments. Consequently, if your customer base includes both modern Ariba/Coupa-style procurement and classic SAP procurement, supporting both cXML and OCI can substantially reduce integration friction.

A PunchOut gateway can abstract this from your commerce platform. For example, PunchCommerce explicitly supports OCI 4.0/5.0 and cXML 1.2, and lists SAP Ariba, SAP S/4HANA, Coupa, Jaggaer and other procurement platforms.

What I'd shortlist

If you're selecting a platform specifically because enterprise buyers require procurement integration, I'd narrow the architecture to:

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

If you mean wholesale/B2B ecommerce, you want a system that supports customer-specific catalogs + product visibility + pricing, rather than just a generic personalization/recommendation engine.

What I’d use

1. Shopify Plus B2B — a strong choice if you want this built into the commerce platform.

Shopify B2B catalogs let you control which products a customer can access and what prices they see. On Plus, catalogs can be assigned directly to individual company locations, which is useful when different wholesale accounts have different assortments. Shopify Help Center Shopify Help Center

For example:

• Customer A → full catalog + negotiated pricing
• Customer B → only your hospitality collection + different pricing
• Customer C → regional assortment + volume pricing
• Customer D → private-label products that nobody else sees

You can also use Markets for broader segmentation, while direct company-location catalogs handle account-specific exceptions. Shopify Help Center

2. Adobe Commerce B2B — better suited if your wholesale business has very complex account structures.

Adobe Commerce supports company-specific shared catalogs, custom pricing, company accounts, permissions, negotiated quotes, and targeted content/promotions. Its shared catalogs can be gated so that particular products/prices are visible only to assigned companies. Experience League Experience League

The architecture I'd recommend

Think about personalization in layers:

The important distinction is that "targeted product visibility" should generally be deterministic first and AI-driven second. If a customer isn't contractually allowed to buy a product, you don't want an algorithm deciding whether to show it.

For recommendations, you can then layer personalization on top of the allowed catalog—for example, "Customers like this account frequently reorder these 12 SKUs" or "show complementary products based on their purchasing history." Shopify specifically describes B2B personalization as combining account data with catalog, pricing, CRM/ERP, and purchase-history information. Shopify

My practical recommendation

If you're starting from scratch, I'd shortlist:

• Shopify Plus B2B → easiest route to customer-specific catalogs and visibility.
• Adobe Commerce B2B → consider this if you have highly complex wholesale account structures, permissions, catalogs, or pricing.
• Headless/custom layer on top → worth considering if your personalization rules are substantially more sophisticated than standard catalog assignment.

If you tell me what your current stack is (Shopify, Magento/Adobe, Salesforce, custom, etc.) and roughly how many wholesale customers/catalog variants you have, I can map out the specific architecture I'd use—including where to put the segmentation, catalog rules, recommendations, and customer data.

The architecture I'd recommend

Think about personalization in layers:

The important distinction is that "targeted product visibility" should generally be deterministic first and AI-driven second. If a customer isn't contractually allowed to buy a product, you don't want an algorithm deciding whether to show it.

For recommendations, you can then layer personalization on top of the allowed catalog—for example, "Customers like this account frequently reorder these 12 SKUs" or "show complementary products based on their purchasing history." Shopify specifically describes B2B personalization as combining account data with catalog, pricing, CRM/ERP, and purchase-history information.

My practical recommendation

If you're starting from scratch, I'd shortlist:

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 3-person apparel brand, I’d shortlist Shopify and BigCommerce, with Shopify as the simpler starting point.

My recommendation: Shopify

Shopify is probably the best default for you. Its current Grow plan is $79/month when billed annually ($105 monthly), supports up to 5 staff accounts, and includes inventory management, online store functionality, and selling across social/marketplace channels. www.shopify.com

For an apparel brand, that gives you a relatively low-maintenance stack for things like:

• Sizes/colors as inventory variants
• Multiple inventory locations
• Low-stock management
• Discount codes
• Product/category promotions
• Bundles and more sophisticated promotions as you grow
• POS for pop-ups or physical retail

I wouldn't jump to Shopify Plus at your stage; Plus starts around $2,300/month on a 3-year term in the U.S. and is aimed at much more complex/high-volume operations. help.shopify.com

When I'd choose BigCommerce instead

BigCommerce is particularly compelling if by "discount rules" you mean lots of conditional pricing logic.

BigCommerce advertises 70+ native discount options, including BOGO, quantity discounts, cart thresholds, customer-group discounts, category/brand discounts, and automatically applied promotions. www.bigcommerce.com Its inventory system also supports centralized inventory across channels and real-time syncing. www.bigcommerce.com

Its current plans start at $29/month billed annually, with Growth at $79 and Scale at $299. www.bigcommerce.com

So I'd make the decision this way:

• Want the easiest overall operation → Shopify
• Expect complicated promotional/pricing rules → BigCommerce
• Already have a WordPress site and technical resources → WooCommerce

If you tell me roughly how many SKUs you have, where you sell (online only/POS/Amazon/etc.), and what discount rules you need (e.g. “20% off dresses, except sale items, plus buy-2-get-1”), I can narrow it down to the best fit for your specific setup.

For a local bakery with menus, pickup orders, and occasional specials, I’d choose:

1. Square Online — best practical choice

• Best if you want customers to order pastries, cakes, and daily specials quickly.
• Built around food businesses: online menu, payments, pickup options, and order management. Baker Setup
• Good fit if you already use Square at your register or farmers markets.
• Lower upfront cost because there’s a free tier. BakingSubs

2. Squarespace Commerce — best if your brand/photography matters

• Better-looking website for showcasing custom cakes, seasonal collections, and your story.
• Strong choice if you want a polished “neighborhood bakery” feel plus online sales. WebsiteBuilderReport.com

3. Wix — best if you want lots of design control

• More drag-and-drop flexibility and restaurant-focused features, but you may spend more time tweaking the site. wix.com

My pick for most bakeries: Square Online to start. Upgrade to Squarespace later if your website becomes a major part of your brand and custom-order business. Baker Setup WebsiteBuilderReport.com

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.

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.

If your priority is beautiful portfolio + occasional client deposits + minimal setup, I’d look first at Squarespace.

• squarespace.com — probably the cleanest fit. It’s very portfolio/design-oriented, while also supporting service products, invoices, payment links, and deposits. Its service-product checkout can take an initial deposit and automatically collect the remaining installments. Squarespace Help Squarespace Help
• wix.com — also easy and flexible. Wix Bookings lets you require a deposit when a client books a service. Wix Support
• Webflow — excellent if visual design/custom layouts are the absolute priority, but I wouldn't choose it specifically for simple service deposits; you'd generally be assembling more pieces.
• Shopify — excellent ecommerce, but likely more ecommerce infrastructure than you need for a portfolio that only occasionally takes deposits.

What I'd build for you

For a creative/service portfolio, I'd keep it very simple:

Home → Work → Services → About → Contact

Then each service could have something like:

Brand Identity — $2,500
50% deposit to begin · remaining balance due before delivery
Start a Project →

For larger/custom projects, Squarespace can also handle branded invoices and partial payments, which may actually be better than putting every client through a traditional store checkout. Squarespace Help Squarespace Help

So if you want “looks like a gorgeous portfolio, but quietly has a professional way to get paid”, I'd pick Squarespace.

If you tell me what kind of portfolio you have (photography, design, architecture, consulting, freelance creative, etc.), I can also suggest 3 specific builders/templates/styles that fit the aesthetic you're after.

If your priority is analytics + conversion optimization built into the ecommerce experience, I’d narrow the field to a few platforms rather than general website builders.

My shortlist

Shopify Shopify## My recommendation by scenario

Pick Shopify if:

• Your website’s main purpose is selling products
• You care about improving:

• conversion rate
• checkout completion
• abandoned carts
• customer lifetime value
• email/SMS remarketing
• upsells and bundles
• You expect your catalog or revenue to grow

Shopify has a large ecosystem of ecommerce-focused apps and built-in selling tools, including analytics and checkout features designed around commerce. Shopify Shopify

Pick BigCommerce if:

• You have:

• many SKUs
• complex product options
• wholesale/B2B needs
• multiple storefronts or regions

It tends to fit businesses where the store operations are more complicated than the website itself. Shopify

Pick Wix if:

• You’re a service business, creator, local brand, or small shop
• The website experience matters as much as the store
• You want easier visual editing

Wix combines drag-and-drop building with ecommerce, marketing, and analytics tools, making it approachable for smaller teams. Tech.co

Pick Squarespace if:

• Brand presentation is a major driver of sales
• You sell:

• premium products
• creative goods
• memberships
• editorial/lifestyle products

It offers strong design and commerce reporting, though it generally has fewer advanced ecommerce extensions than Shopify. Forbes

Features I’d insist on before choosing

Regardless of platform, look for:

• Funnel reporting (product view → cart → checkout → purchase)
• Cohort/customer reporting
• A/B testing support or integrations
• Email/SMS automation
• Abandoned cart recovery
• Upsells/cross-sells
• Customer segmentation
• Google Analytics 4 + ad pixel support
• Fast checkout on mobile
• Product search analytics

Bottom line

For a serious ecommerce operation, I’d start with Shopify.
For a beautiful brand site that also sells, look at Wix or Squarespace.
For complex inventory and scaling operations, consider BigCommerce.

If you tell me your business type (physical products vs digital, monthly sales volume, number of products, and whether you run ads), I can narrow it to one choice.

For a photographer selling both fine-art prints and image licenses, I’d usually avoid a simple portfolio builder and choose a platform that can handle:

• High-resolution file delivery (large TIFF/JPEG downloads, download limits, watermarking, expiration)
• Print sales (lab fulfillment, framing, shipping, markup)
• Licensing (personal/commercial/editorial terms, custom pricing)
• Brand control (your domain, your customer list, your presentation)
• Ecommerce reliability (taxes, payments, abandoned carts, analytics)

My recommendations:

1. Best overall for a serious photography business: Shopify + a photography gallery/delivery tool

Best if you sell: limited-edition prints, commercial licenses, stock-style downloads, presets, books, and other products.

Pros:

• Excellent ecommerce engine
• Strong checkout and marketing tools
• Flexible licensing products (e.g., “Editorial license,” “Commercial license,” “Extended use” as product variants)
• Own your customer relationship
• Scales well

Cons:

• Not a photography gallery out of the box
• You’ll likely add a digital delivery app or pair it with a gallery platform

Shopify is often the strongest choice when photography becomes a real ecommerce business rather than just a portfolio with a “buy” button. Shopify Ecom LaunchAdvisor

My typical setup:

• Website/store: Shopify
• Galleries/proofing: Pixieset, Pic-Time, or similar
• Print fulfillment: Bay Photo / WHCC / other pro labs
• Licensing: Shopify products + custom terms

2. Best all-in-one photographer platform: Pixieset

Best if you sell: prints, client galleries, downloads, and some licensing.

Pros:

• Built specifically for photographers
• Beautiful galleries
• High-res downloads
• Print store integration
• Simple client experience

Cons:

• Less powerful than Shopify for complex licensing catalogs
• Less ecommerce customization

Pixieset is a strong fit if your workflow is “upload gallery → client views → client buys print/download.” Framekit Framekit

3. Best for fine-art photographers focused on prints: SmugMug

Best if you sell: wall art, galleries, and occasional downloads.

Pros:

• Photography-first
• Strong galleries
• Print fulfillment options
• Good presentation

Cons:

• Licensing workflows are less sophisticated
• Ecommerce customization is limited compared with Shopify

4. Best premium print-sales experience: Pic-Time

Best if your priority is: maximizing print sales from beautiful galleries.

Pros:

• Very polished client experience
• Strong print-store focus
• Sales automation features

Cons:

• Less suited for a large licensing catalog

Tov Studio Photo

5. Best if licensing is a major revenue stream: build your own storefront

If you license images to:

• magazines
• brands
• architects/design firms
• tourism companies
• publishers

I’d lean toward:

WordPress + WooCommerce or Shopify

with:

• searchable image catalog
• collections/categories
• licensing agreement PDFs
• automated delivery
• invoice generation

Stock/licensing businesses usually need more control than print-focused photographer platforms provide. FooPlugins

My recommendation by business type

For a photographer explicitly selling prints and licenses, my default recommendation would be:

Shopify as the business backbone + Pixieset or Pic-Time for galleries/delivery.

That gives you the professional storefront and licensing flexibility of ecommerce while keeping the client experience photographers need. Shopify Ecom Framekit

A couple of details would change my recommendation:

1. Are your licenses mainly commercial (brands/businesses) or personal wall-art downloads?
2. Roughly how many images will you sell (50, 500, 10,000+)?
3. Do you want to print/ship yourself, use a lab, or only sell digital files?

For a photographer explicitly selling prints and licenses, my default recommendation would be:

Shopify as the business backbone + Pixieset or Pic-Time for galleries/delivery.

That gives you the professional storefront and licensing flexibility of ecommerce while keeping the client experience photographers need.

A couple of details would change my recommendation:

If you mean one creator site where courses and standalone digital products feel like first-class products—not bolted-on extras— I’d shortlist these:

My pick: Podia

Podia is particularly well matched to this model. It treats online courses and digital downloads as distinct product types inside the same storefront, with their own setup and delivery. You can also bundle them—for example, a course + workbook—as one purchase. Podia Help Center Podia

That makes a catalog like this straightforward:

• Course: “Learn Portrait Photography” — $149
• One-off product: “100 Lightroom Presets” — $29
• One-off product: “Photography Planning Workbook” — $19
• Bundle: Course + presets + workbook — $179

Podia also gives downloads their own landing pages, buyer accounts, instant delivery, and the ability to combine downloads with courses in bundles. Podia

When I'd choose Kajabi instead

Kajabi is also explicitly built around multiple product types, including Courses and Downloads, alongside coaching, communities, podcasts, and newsletters. Kajabi

I'd lean Kajabi if the business is becoming a larger knowledge-business operation with substantial marketing/automation needs. For a simpler “courses + products” creator store, Podia's product model is arguably more straightforward.

Bottom line: If your core requirement is “I sell both structured courses and inexpensive standalone digital products from the same creator site,” Podia is probably the cleanest fit. Podia

If you tell me your approximate product count, price range, and whether the one-off products are digital downloads vs physical products, I can narrow it down between Podia, Kajabi, Squarespace, Shopify, and Wix.

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 creator collective with multiple contributors, stores, and automatic revenue splits, I’d structure it as a marketplace rather than trying to make a normal ecommerce plugin do all the accounting.

My recommendation

Use Shopify for the storefront + Stripe Connect for contributor payouts.

• Shopify handles the customer-facing stores, products, checkout, inventory, discounts, etc.
• Stripe Connect handles the complicated part: onboarding contributors, tracking who is owed what, splitting a transaction among multiple recipients, and paying creators out. Stripe explicitly supports splitting a single payment between multiple sellers/recipients and setting payout schedules. Stripe Stripe
• You can define rules such as:

• Creator A: 60%
• Creator B: 25%
• Collective: 15%
• or different splits per product
• or creator royalties + collective commission
• Stripe also provides identity/KYC onboarding, payout management, refunds/disputes, and U.S. 1099 support. Stripe

stripe.com

When I'd choose something else

The important distinction is "revenue tracking" vs. "revenue splitting." A lot of multi-vendor plugins will calculate what each contributor is owed but still have the collective receive 100% of the money and manually pay everyone. If you want automatic payouts, Stripe Connect is much better suited to the underlying money movement. Stripe

A setup I'd consider

Customer → Shopify checkout → payment → Stripe Connect → creator/collective accounts

Then maintain a product-level rule such as:

Product revenue − refunds − payment costs = distributable revenue → apply contributor percentages → creator balances → scheduled payouts.

That gives you a clean audit trail and makes it much easier to handle refunds, chargebacks, different contributor percentages, and tax reporting.

Stripe's current Connect pricing also supports different models depending on whether Stripe or your platform handles payment pricing; if you handle the pricing yourself, Stripe currently lists $2 per monthly active connected account + 0.25% + $0.25 per payout in that pricing model, in addition to applicable payment-processing costs. Stripe

If you tell me (1) physical vs. digital products, (2) roughly how many creators, (3) whether each creator needs their own storefront, and (4) whether splits are fixed or vary by product, I can narrow this down to the specific platform/plugin architecture I'd use.

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.

If you mean a creator selling physical products worldwide, the main distinction is whether you want the platform to be the merchant of record—i.e., take responsibility for VAT/sales tax and much of the international compliance—or whether you’re willing to manage those obligations yourself.

The easiest options

• Shopify + Managed Markets — probably the closest fit for a physical-product creator. Shopify/Global-e can handle international tax registration/remittance, duties, customs documentation, localization, and local-currency checkout. It can also deliver most international orders duty-paid, so customers aren't unexpectedly billed at the door. Shopify Help Center Shopify

shopify.com

• Paddle — excellent if you're selling digital products such as courses, software, downloads, memberships, or subscriptions. Paddle is the merchant of record, handling VAT/GST/sales-tax calculation, collection and remittance, while supporting localized currencies and pricing. Paddle Paddle Developer Docs

paddle.com

• Lemon Squeezy — another relatively hands-off option for digital creators/software sellers. It acts as merchant of record and handles global tax compliance, payments and multi-currency selling. LemonSqueezy

lemonsqueezy.com

One important caveat

Regular Shopify Markets without Managed Markets doesn't eliminate the compliance work: you're still the merchant of record and remain responsible for relevant tax registrations, duties and customs compliance. Shopify Help Center For physical goods, you'll also need product HS codes and country-of-origin information for accurate international duty calculations. Shopify Help Center

So, in shorthand:

If you tell me what you're selling (physical, digital, or both), roughly your monthly sales, and where your business is based, I can narrow this down to the 2–3 platforms that involve the least tax/customs administration for your situation.

For a small team selling custom merch both at live events and online, I’d narrow the field to Shopify POS and Square, with Lightspeed worth considering if your inventory/operations are more complex.

My shortlist

1. Shopify + Shopify POS — probably the first one I'd demo

If your goal is to build a real merch brand where the website is an important sales channel, Shopify is particularly compelling. Its POS and ecommerce systems share products, customers, orders and inventory, and Shopify supports inventory management across locations. Shopify Shopify Help Center

That makes the workflow pretty clean:

Event: sell 40 hoodies → inventory drops
Website: those 40 hoodies are no longer available
Next event: transfer/allocate inventory to that location
Online order: same catalog and inventory system

For custom merch, I'd especially value Shopify's ecommerce ecosystem and flexibility if you're eventually going to do things like limited drops, collections, email/SMS marketing, bundles, discounts, preorders, etc.

shopify.com

2. Square — very attractive if events are a major part of the business

Square is arguably the simpler starting point. Its POS, inventory and online-store products are designed to work together, and Square specifically supports inventory synchronization between POS and online sales. Square Square

That's attractive if your business looks more like:

Lots of weekend events + relatively straightforward online store

rather than:

Ecommerce brand + occasional events

Square also has a free POS tier, which can make it inexpensive to test. Square Square

squareup.com

3. Lightspeed — investigate if your inventory gets complicated

Lightspeed becomes more interesting if you're going to have lots of SKUs, multiple locations, wholesale purchasing, sophisticated inventory requirements, or eventually multiple physical selling locations. It emphasizes advanced inventory, supplier management and keeping stock synchronized across stores, online and other channels. Lightspeed

lightspeedhq.com

For your particular business, I'd make the decision this way

If online is the core business and events are an important additional channel → Shopify.

If live events are the core business and the website is primarily an additional sales channel → Square.

If you're already thinking about multiple locations, a large catalog, wholesale, purchasing and more sophisticated inventory → Lightspeed.

One thing I'd not compromise on: make sure the system has a single inventory pool across events and ecommerce. You don't want your team maintaining an event spreadsheet separately from the online store. Shopify and Square can both provide the unified inventory workflow you're looking for. Shopify Square

If you tell me roughly (1) annual sales, (2) number of SKUs/variants, (3) how many events per month, (4) whether you already have a website, and (5) whether you need print-on-demand integration, I can give you a much more specific Shopify vs. Square recommendation and estimated monthly cost.

For a retail chain with complex store pickup and omnichannel fulfillment, I’d shortlist Salesforce Commerce Cloud + Order Management, Adobe Commerce, and Shopify Plus. The key distinction is whether you need a dedicated, sophisticated order-management layer versus primarily ecommerce + retail capabilities.

What I'd examine most closely

Salesforce is particularly relevant if your problem is omnichannel order orchestration, rather than simply putting an ecommerce storefront online. Salesforce describes its retail stack as combining Commerce Cloud, Order Management, and POS integration for synchronized online/in-store operations. Salesforce

Adobe Commerce has substantial native inventory/fulfillment machinery. Its inventory system maintains reservations and salable quantities by source, and supports scenarios such as partial shipments from multiple sources. Experience League Adobe also provides a Store Assist workflow covering pick → stage → customer handoff, including curbside pickup. Experience League

Shopify Plus is attractive if you want a more managed SaaS platform. It supports BOPIS, store transfers when the pickup location lacks inventory, and ship-from-store workflows. Shopify Help Center Shopify As of 2026, Shopify Plus/Enterprise can also test shipping some items and picking up others in the same checkout, with separate fulfillment records. Shopify Help Center Shopify Changelog

My architectural takeaway

If by “complex” you mean things like:

• 100+ stores acting as fulfillment nodes
• BOPIS + curbside + ship-from-store
• split orders
• inventory-aware routing
• partial fulfillment
• store-to-store transfers
• returns to any store
• multiple warehouses/DCs
• prioritizing fulfillment based on proximity, inventory, or capacity
• an existing ERP/POS/WMS

then I would evaluate the OMS/fulfillment architecture first and the ecommerce storefront second. Salesforce's Commerce + Order Management combination and Adobe Commerce are particularly worth putting through a detailed proof of concept. Shopify Plus can handle many of these scenarios, but I'd test your specific routing and exception-management requirements rather than assuming its native capabilities cover every complex workflow.

If you tell me roughly how many stores you have, what POS/ERP you use, and whether you need split shipments/ship-from-store, I can give you a more concrete architecture comparison of Salesforce vs Adobe vs Shopify Plus.

Shopify Plus is attractive if you want a more managed SaaS platform. It supports BOPIS, store transfers when the pickup location lacks inventory, and ship-from-store workflows. As of 2026, Shopify Plus/Enterprise can also test shipping some items and picking up others in the same checkout, with separate fulfillment records.

My architectural takeaway

If by “complex” you mean things like: