Answers that do not mention BigCommerce

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 a small handmade-goods shop with no coding experience, I’d look first at Shopify or Wix.

• Shopify — best if selling is the main focus. It’s fully hosted, has no-code themes and drag-and-drop editing, and handles products, checkout, payments, and orders in one place. Shopify Shopify
• Wix — good if you want more freedom over the visual design. Its AI and drag-and-drop tools are designed for people without coding skills, and hosting is included. wix.com wix.com
• Squarespace — worth considering if your handmade products are very design/brand-driven. It supports physical products, gift cards, and other commerce features directly in the platform. Squarespace Help

My practical recommendation: start with Shopify if you expect the shop itself to become an important sales channel; choose Wix if creating a beautiful, flexible brand website is equally important.

shopify.com · wix.com · squarespace.com

For a brick-and-mortar + online business, the right choice depends heavily on whether you need simple POS/e-commerce synchronization or a dedicated inventory hub.

The main options

• Shopify — Best fit if your online store is already on Shopify and you want the simplest setup. Shopify POS synchronizes inventory across physical locations, the online store, and other active sales channels in real time. Shopify Shopify Help Center
• Lightspeed — Worth considering if you're primarily a retail operation with multiple stores and need stronger retail/POS inventory capabilities. It tracks stock across stores, online, social and marketplaces. Lightspeed
• Cin7 — Better suited when inventory itself is the central problem: multiple sales channels, warehouses, marketplaces, wholesale, 3PLs, purchasing, etc. Cin7 says it supports 700+ integrations and real-time synchronization across POS, Shopify, Amazon, WooCommerce and other channels. Cin7 Cin7

How I'd narrow it down

The key question is what you're selling through. If you tell me your online platform (Shopify/WooCommerce/etc.), POS, number of stores, approximate SKU count, and marketplaces (Amazon/eBay/Walmart/etc.), I can compare the 2–3 systems that actually fit your setup, including likely cost and where the inventory sync can break down.

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 two-person boutique on a tight budget, I’d narrow it to Square Online vs. Big Cartel.

• Square Online — best if minimizing monthly cost is the priority. Square’s Free plan has $0/month subscription cost; you pay payment-processing fees when you make a sale. It also includes a website builder, shipping/local delivery/pickup, and syncing with Square POS. Square Square
• Big Cartel — best if you have a relatively small catalog and want a simple boutique storefront. Its Platinum plan is $15/month and supports up to 50 products, inventory tracking, discounts, online/in-person selling, and custom domains. Big Cartel Big Cartel
• Shopify — best if you expect to grow substantially, but it's harder to justify on a very tight budget: Basic is $39/month month-to-month or $29/month annually, before payment-processing costs. Shopify
• Ecwid — worth considering if you already have a website. It can embed a store into an existing site, but its paid plans are now considerably more expensive than Big Cartel; Venture is $35/month and Business is $65/month when billed monthly. Ecwid Help Center Ecwid | E-Commerce Shopping Cart

What I'd choose

If you're starting from scratch and every $10 matters, I'd start with Square Online Free. You can put the money toward inventory, photography, packaging, and marketing rather than a monthly platform fee.

If your boutique has fewer than ~50 products and you care more about having a polished, boutique-oriented storefront than keeping the subscription at $0, Big Cartel at $15/month is compelling.

If you tell me roughly how many products you carry, whether you already use Square for in-store checkout, and your monthly online sales target, I can compare the actual monthly + transaction costs for your situation.

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

The practical choice

• Square — best fit if you primarily sell at craft fairs, markets, pop-ups, or a small physical shop, and want the simplest setup. Square combines POS, inventory, payments, and an online store, and its Free plan has no monthly subscription fee; you pay processing fees when you sell. Square Square
• Shopify — better fit if your online store is going to be the center of the business, with markets/pop-ups as an additional sales channel. Shopify's Basic plan is currently $39/month when billed monthly, and its POS integrates with the online store and inventory. Shopify
• Wix — worth considering if the website/design/branding matters more than having a particularly strong retail POS. Its POS capabilities are more limited than Square's/Shopify's for a maker doing lots of in-person selling. wix.com Wix Help Center

For a typical maker

If you're making things like candles, pottery, jewelry, art, woodworking, baked goods, crafts, etc., I'd start with Square if your sales mix looks something like:

craft fairs + Instagram/Facebook + occasional local pickup + a simple online shop

You can start without a monthly software fee, use a phone with Tap to Pay or a $59 Square Reader, and keep your in-person and online inventory together. Square Square

I'd lean toward Shopify instead if your goal is:

primarily online sales + social media/ads + shipping orders + growing into a substantial ecommerce operation.

One particularly important distinction: Square is POS-first with an online store attached; Shopify is ecommerce-first with POS attached.

If you tell me what you make, roughly how much you expect to sell per month, and whether most sales will be online or at markets, I can lay out the actual monthly costs for Square vs. Shopify for your situation.

For a photographer selling both high-resolution digital files and physical prints, I’d narrow it to Pic-Time and Pixieset. Both are purpose-built for photographers rather than generic ecommerce platforms.

My take

Pic-Time would be my first platform to investigate if your business is heavily focused on selling prints. It specifically supports high-resolution downloads, custom-resolution products, digital/print packages, and a broad network of print labs. Pic-Time Help Center Pic-Time Help Center Pic-Time Help Center

Pixieset is an extremely strong alternative, particularly if you want a simpler ecosystem around client galleries. Its Store can automatically deliver your digital files at the resolution you specify while sending print orders to a professional lab for printing and shipping. Pixieset Website Help Center Pixieset Website Help Center

One important point for high-resolution files: neither platform is just selling a generic "download link." You can configure what resolution the customer receives, while retaining your full-resolution originals for print fulfillment. Pixieset, for example, sends the full-resolution uploaded image to the lab for automatic print orders. Pixieset Website Help Center Pixieset Website Help Center

If you tell me what you shoot (landscape, fine art, weddings, portraits, etc.) and roughly what you charge for a digital file/print, I can compare Pic-Time vs Pixieset specifically for your business model, including fees, storage, lab quality, and profit margins.

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.

For a small bakery with only a handful of products, I’d keep it very simple and avoid paying for a full e-commerce platform.

My shortlist

• squareup.com — probably the best fit

• $0/month on the Free plan; you pay payment-processing fees when customers order.
• Built specifically for food businesses, with pickup, curbside pickup, local delivery, ordering windows, and item availability. Square Square
• You can have a standalone ordering page, so you don't even need to build a separate website.
• Particularly good if you also take payments in person with Square.
• clover.com — good if you already use Clover

• Clover says its online ordering has no subscription or setup fee, although normal online card-processing fees apply. Clover Clover
• Orders can flow directly into your Clover system.
• I wouldn't buy Clover hardware just to get an inexpensive ordering page, though.
• pos.toasttab.com — better for a larger food operation

• Offers commission-free ordering and strong POS/menu integration. Toast Support Center Toast POS
• But for a bakery selling only a few items, Toast can be more infrastructure than you need.

What I'd do in your situation

Start with Square Free. You could have something like:

[Your Bakery Name]
Fresh bread • Cookies • Cakes

🥐 Croissants — $4
🍪 Cookie Box — $18
🎂 8" Cake — $35

Choose pickup date/time → Pay → Done

You can put the Square ordering-page link in your Instagram/Facebook bio, Google Business Profile, and on a QR code at the bakery. Square specifically supports an "Order Online" layout intended for prepared food and local pickup/delivery. Square

If you tell me roughly how many orders you expect per week and whether customers will pick up, get delivery, or both, I can compare the actual costs of Square vs. a couple of alternatives for your bakery.

Yes. If your goal is digital downloads + printable art with essentially $0 upfront cost, there are a few good options.

My first two to look at

• payhip.com — probably the most straightforward fit. Its Free Forever plan is $0/month, has unlimited products and unlimited revenue, and charges 5% per sale, plus Stripe/PayPal processing. It also automatically delivers digital files and can handle physical products. Payhip Payhip
• ko-fi.com — also $0/month, with 5% on shop sales plus payment processing. You can sell both digital files and physical prints, and there are no listing fees. Ko-fi Ko-fi Help

For printable wall art, planners, templates, coloring pages, PDFs, SVGs, etc., I'd lean toward Payhip because its free plan is explicitly designed around digital products and gives you unlimited products without a monthly subscription. Payhip Payhip

One important distinction: these platforms give you the store, but they don't manufacture physical prints. If by "prints" you mean customer orders a physical art print and someone else prints/ships it, you'd want to pair the store with a print-on-demand service. That lets you avoid inventory and shipping overhead.

If you tell me what you're planning to sell (e.g. wall art, digital planners, Canva templates, photography, AI art, invitations), I can map out a $0-upfront setup including the store, payment processing, print-on-demand option, and how much you'd actually keep from a $10/$20/$30 sale.

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 a small boutique with seasonal inventory and only occasional selling, I’d focus on low/no monthly cost when you’re not selling, simple inventory management, and an easy storefront.

My shortlist

Big Cartel is particularly well matched to your situation. Its free Gold plan supports up to 5 product listings, online selling, variants such as sizes/colors, and payments; its Platinum plan is $15/month if you need more products. Big Cartel Big Cartel

Square Online is arguably the better choice if your seasonal boutique also does craft fairs, pop-ups, markets, or a physical shop. Square's Free plan has no monthly subscription, while online card payments on the U.S. Free plan are currently 3.3% + 30¢. Square Square

Shopify is more powerful, but I'd generally avoid paying for it year-round if you're only opening the store for occasional seasonal drops. Its current Basic plan is $39/month when billed monthly ($29/month annually). Shopify

What I'd choose

• 5 or fewer products at a time: Big Cartel Gold
• More than 5 products + occasional seasonal sales: Big Cartel Platinum
• You sell both online and at physical events: Square Online
• You expect the boutique to become a regular business: Shopify

For your particular description, Big Cartel is probably the simplest low-cost starting point, especially if each season consists of a small curated collection rather than hundreds of SKUs. Its pricing also avoids paying a substantial monthly subscription during quiet periods. Big Cartel Big Cartel

If you tell me roughly how many products/SKUs you have per season and whether you sell at in-person markets, I can narrow it down between Big Cartel and Square and estimate your actual annual cost.

For a tiny prospect-facing demo store with $0 spend, I’d look at these:

• Square Online — probably the simplest if you want a hosted storefront immediately. Its free plan includes a website/store, catalog, checkout, and a free Square subdomain; you only incur payment fees if you actually process a sale. Square Square
• WooCommerce — best if your agency wants to demonstrate a more customizable, WordPress-based store. WooCommerce itself is free/open source, though normal hosted WordPress requires hosting. WooCommerce WooCommerce
• Big Cartel — worth considering for an extremely small catalog; current free offerings are aimed at only a handful of products. Aventine Post

For an agency demo specifically, I'd use Square Online if the goal is “here's a working store you can click through” with essentially no infrastructure to maintain. If the goal is “show prospects what our agency can build/customize,” I'd use WooCommerce because you have much more control over the storefront and code. Square WooCommerce

One caveat: “free” usually means $0/month, not literally zero possible costs—custom domains, payment processing, premium extensions, etc. can still cost money. WooCommerce

If you tell me whether you want (a) a polished demo URL in 10 minutes, (b) something your agency can heavily customize, or (c) a disposable sandbox that can be cloned for every prospect, I can narrow it down to the best setup.

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

For an international store with many countries, currencies, tax regimes, localized pricing, warehouses, and payment rules, I’d shortlist Saleor, Adobe Commerce (Magento Open Source), and Medusa rather than a simpler WordPress-based stack.

How I’d compare them

Adobe Commerce/Magento has particularly mature tax-rule machinery: tax rules can combine product class, customer class, tax rate and geographic region, and it supports international tax configuration and VAT-related functionality. Experience League Experience League

Saleor is compelling if you're building a custom/headless storefront. Its architecture is designed around multi-channel commerce, and it is frequently used for multi-currency and multi-region catalogs. Macrostack Macrostack

Medusa has explicit multi-region support: regions can have their own currency, tax configuration, payment providers, fulfillment providers and pricing, while its translation functionality handles localized product content. Medusa Docs Medusa Docs

My practical recommendation

If by "lots of tax and currency rules" you mean things like:

• EU VAT + OSS/IOSS
• US state/local sales tax
• GST/VAT in multiple countries
• tax-inclusive vs. tax-exclusive pricing
• different prices by market rather than simple FX conversion
• tax exemptions and B2B VAT IDs
• different payment methods per country
• multiple warehouses and fulfillment regions
• localized catalogs and languages
• country-specific checkout rules

I'd investigate Adobe Commerce first and Saleor second.

The important distinction is that tax complexity isn't just a feature checkbox. For serious international commerce, you'll probably want a dedicated tax engine/service (such as Avalara, Vertex, TaxJar, etc.) rather than trying to encode every jurisdiction's tax law directly into the ecommerce application.

If your team is primarily TypeScript/Node, Medusa becomes particularly interesting: its official multi-region model already covers currency, tax, pricing, payment and fulfillment configuration. Medusa Docs

If you tell me roughly how many countries you sell into, B2C vs B2B, number of currencies, and whether you need multiple warehouses/legal entities, I can narrow this to a concrete architecture and platform choice.

For a solo founder with limited dev skills, I’d narrow it to Saleor, Medusa, and WooCommerce—but they suit very different levels of technical involvement.

My take

If “modern admin + easy theming” are your two priorities, I’d look at Saleor first.

Saleor has a polished admin with catalog, orders, promotions, channels, etc., and its dashboard is explicitly designed to be extensible. Its current open-source stack also includes a Next.js/React/Tailwind storefront, which makes visual customization relatively approachable if you're comfortable making frontend changes. Saleor Commerce Saleor Commerce GitHub

The catch: Saleor is headless. You're not installing a theme and tweaking it like Shopify/WooCommerce. You're customizing a React storefront. That's substantially more technical for a non-developer. GitHub

Medusa is similar in this respect. It's TypeScript/Node-based and gives you a modern commerce backend plus considerable storefront freedom, but you're still building/customizing the frontend rather than simply selecting a theme. GitHub ShipGarden

WooCommerce is the one I'd consider if your actual priority is “I want to run the business myself without needing a developer.” Its WordPress foundation gives you an enormous ecosystem of themes and plugins, and you can get much further through configuration than with a headless platform. The tradeoff is that the admin/frontend architecture isn't as cleanly modern as Saleor/Medusa.

Vendure is worth knowing about, especially because its newer admin is React-based and its storefront stack uses Next.js, React, TypeScript, Tailwind and shadcn/Radix. Vendure Vendure But I'd put it lower on the list for a low-code solo founder because it's fundamentally a developer-oriented framework.

The important distinction

If by “easy theming” you mean:

“I want to pick a theme, change colors/fonts/layout, add products, and mostly stay out of code.”

→ WooCommerce is probably the better fit.

If you mean:

“I want a genuinely modern admin and want complete control over the storefront, and I'm willing to use AI/Cursor or occasionally hire a developer.”

→ Saleor is particularly interesting.

If you tell me what you're selling (physical/digital/subscriptions), roughly how many products, and whether you want to use AI coding tools, I can narrow this down to 1–2 platforms and explain what your actual setup would look like.

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 one-person creative business selling ebooks and printable art, I’d start with a tool that is:

• easy to launch without coding
• handles automatic file delivery
• doesn’t take a big cut of small sales
• lets you build a brand (not just a checkout page)

My top picks:

My recommendation for your situation

Start with Payhip. It’s probably the closest match for a solo creator selling:

• ebooks (PDF/ePub)
• printable wall art
• planners, templates, worksheets
• bundles and collections

You can launch cheaply, then upgrade only when sales justify it. Fourthwall

A simple setup could be:

1. Payhip → your storefront + digital delivery
2. Email newsletter (so customers belong to you, not just a marketplace)
3. Pinterest/Instagram/TikTok → traffic sources for printable art
4. Optional: add Etsy later if you want marketplace discovery

I’d choose Gumroad instead if your priority is “I want something live tonight with almost no setup.” UxerWave

I’d avoid starting with a full Shopify store unless you expect to add physical products, because the extra complexity and monthly cost usually aren’t needed for a small digital-only catalog. LaunchAdvisor

If you tell me roughly how many products you have (1–5 vs 50+) and your average price ($3 printable vs $30 ebook bundle), I can help pick the lowest-fee setup.

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.

For a shop selling high-res digital assets, I’d narrow it to Payhip, Sellfy, or Shopify + a dedicated download app. The key is not just file size—it’s bandwidth pricing, because a 2 GB asset sold 500 times means ~1 TB of downloads.

Payhip explicitly says it has unlimited storage and bandwidth, with a 5 GB per-file limit. Its free tier is $0/month with a 5% transaction fee, making it unusually attractive if you're starting out. Payhip Payhip

Sellfy also provides unlimited bandwidth, and its current documentation allows files up to 10 GB on Starter and up to 20 GB on higher plans. Its annual Starter pricing is currently $348/year (~$29/month). Sellfy Help Center Sellfy Help Center

Shopify's own Digital Downloads app supports files up to 5 GB with no bandwidth limit. If you need bigger files, the Fileflare Shopify app advertises unlimited bandwidth and no file-size limit, with storage-based plans starting at $19/month for 50 GB. Shopify Help Center Shopify App Store

What I'd choose

If you're primarily selling PSDs, AI/PSD templates, fonts, brushes, textures, mockups, SVGs, etc.: → Payhip.

It's hard to beat $0/month + unlimited bandwidth/storage while you're validating the shop. The 5 GB individual-file ceiling is the main limitation. Payhip

If your typical product is 5–20 GB: → Sellfy is more straightforward than building a Shopify stack. Sellfy Help Center

If you're building a serious branded ecommerce business: → Shopify + Fileflare is worth considering. You get Shopify's broader ecommerce infrastructure while outsourcing the heavy digital-file delivery to a specialized app. Shopify App Store Shopify App Store

One important distinction: storage isn't usually the expensive part—bandwidth is. If you tell me roughly (1) average file size, (2) number of products, and (3) expected monthly sales/downloads, I can calculate the approximate monthly cost for Payhip vs Sellfy vs Shopify and tell you where the break-even points are.

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.

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

My practical recommendation

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

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

For example, your architecture could be:

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

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

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

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 freelancer building a dropshipping MVP, I’d usually pick Shopify unless the client has a strong reason not to. It gets you from idea → working store → feedback loop fastest. Shopify is built as a hosted commerce platform, so you avoid spending MVP time on hosting, security, checkout plumbing, and plugin conflicts. Shopify Shopify

My shortlist:

Shopify Ecommerce-Platforms.com## My recommended freelancer MVP stack

Fastest path:

• Shopify storefront
• Premium/free theme (or lightweight custom theme)
• Product import app (depending on supplier)
• Shopify Payments + Stripe where appropriate
• Klaviyo/Mailchimp later
• Analytics + session recording from day one

Build only:

1. Landing/product pages
2. Product catalog
3. Checkout flow
4. Supplier/order workflow
5. Basic analytics
6. Customer feedback loop

Avoid building:

• Custom admin dashboards
• Custom inventory systems
• Custom checkout
• Complex user accounts
• Automated fulfillment logic before there are orders

When I’d choose something else

Choose WooCommerce if:

• The client already owns a WordPress ecosystem
• They need unusual product logic
• They have someone technical maintaining it

Choose headless/custom if:

• The “dropshipping store” is actually a marketplace, recommendation engine, subscription product, or has unusual UX requirements.

For a client paying a freelancer for an MVP, the key metric is usually how many experiments you can ship per week, not how much infrastructure you own.

A practical proposal would be: “Launch Shopify MVP in 2–4 weeks, validate demand, then rebuild/customize only the parts that prove valuable.”

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.

If your goal is a dropshipping store where you own the code and can build arbitrary supplier, fulfillment, payment, pricing, ERP, and automation integrations, I’d focus on headless open-source commerce engines, rather than traditional WordPress-style stores.

My shortlist

1. Medusa — probably the one I'd investigate first

Medusa is particularly interesting for your use case because it's essentially a commerce engine/framework rather than a rigid storefront. Its open-source modules cover things like products, carts, orders, customers, payments and fulfillment, while its architecture is explicitly designed for customization. GitHub

Its integration model is also useful for dropshipping: Medusa documents using integrations as a middleware layer between your commerce system and external services, including custom ERP integrations. Medusa Documentation

A dropshipping architecture could look like:

                 ┌── Supplier API #1
                 ├── Supplier API #2
Next.js Store ── Medusa ── Supplier Router
                 │             ├── Inventory sync
                 │             ├── Price sync
                 │             ├── Order submission
                 │             └── Tracking
                 │
                 ├── Stripe
                 ├── Tax service
                 ├── Email/SMS
                 └── Your analytics/ERP

That gives you considerably more control than trying to bend a SaaS platform's apps into doing something it wasn't designed for.

2. Saleor — excellent if you want maximum API composability

Saleor is GraphQL-native, API-only and headless, with an app architecture specifically intended for extending the platform without modifying its core. GitHub GitHub

It currently advertises 160+ webhooks, dashboard extensions and independently deployed apps, which is particularly attractive if you're building a system where orders need to trigger external fulfillment workflows. Saleor Commerce

For example:

Saleor
  │
  ├── order.created
  │       ↓
  │   Your fulfillment service
  │       ↓
  │   Select supplier
  │       ↓
  │   Submit supplier order
  │       ↓
  │   Receive tracking
  │       ↓
  └── Update Saleor order

I'd lean toward Saleor if GraphQL + Python is a good fit for your team.

3. Vendure

Vendure is another strong option if you're a TypeScript shop. Its core is built with TypeScript, NestJS, GraphQL and React, and its architecture is explicitly plugin-first. GitHub

That makes something like a custom SupplierPlugin or FulfillmentPlugin a natural architectural fit.

4. WooCommerce

WooCommerce is still worth considering if your priority is getting a store operational quickly rather than creating a sophisticated commerce backend.

Its enormous WordPress/plugin ecosystem can make integrations dramatically easier. The tradeoff is architectural: you're working within WordPress/WooCommerce rather than starting with a clean headless commerce engine.

I'd choose it if you want:

• lots of existing dropshipping plugins
• easy content/SEO management
• relatively straightforward administration
• less custom backend development

I'd look elsewhere if your eventual goal is a custom supplier orchestration platform.

What I'd choose for your particular approach

If you're comfortable developing software, I'd narrow it to:

Medusa vs. Saleor vs. Vendure.

And I'd make the decision based largely on your engineering stack:

• TypeScript/Node → Medusa or Vendure
• Python/GraphQL → Saleor
• Want a modular commerce framework → Medusa
• Want GraphQL + app/webhook architecture → Saleor
• Want TypeScript + a very explicit plugin architecture → Vendure

The important distinction is that dropshipping itself isn't the reason to pick one of these. The critical requirement is whether the platform lets you make your supplier/fulfillment layer your own system.

For example, I'd avoid making your architecture:

Store → Supplier plugin → Supplier

and instead build:

                  ┌─ Supplier A
                  ├─ Supplier B
Store → Commerce → Fulfillment Service
                  ├─ Supplier C
                  └─ Supplier D
                         │
                    Inventory DB
                         │
                    Pricing Engine

That lets you eventually add supplier failover, automatic supplier selection, margin rules, inventory reconciliation, order routing, tracking normalization, and supplier-specific APIs without coupling your store to any particular dropshipping provider.

If I were starting this from scratch today, Medusa would be one of the first platforms I'd prototype against, with Saleor and Vendure as the two alternatives I'd benchmark. That's an architectural fit assessment, not a claim that one is universally superior. Medusa Documentation GitHub Saleor Commerce

If you tell me your preferred stack (Node/TypeScript, Python, PHP, etc.) and roughly how you want to source products (AliExpress/Alibaba, private suppliers, Printful-style suppliers, wholesale distributors, etc.), I can lay out a full open-source dropshipping architecture including the store, supplier APIs, database, queues, inventory sync, order routing, payments, and hosting.

Saleor
  │
  ├── order.created
  │       ↓
  │   Your fulfillment service
  │       ↓
  │   Select supplier
  │       ↓
  │   Submit supplier order
  │       ↓
  │   Receive tracking
  │       ↓
  └── Update Saleor order

I'd lean toward Saleor if GraphQL + Python is a good fit for your team.

3. Vendure

Vendure is another strong option if you're a TypeScript shop. Its core is built with TypeScript, NestJS, GraphQL and React, and its architecture is explicitly plugin-first. GitHub

That makes something like a custom SupplierPlugin or FulfillmentPlugin a natural architectural fit.

4. WooCommerce

WooCommerce is still worth considering if your priority is getting a store operational quickly rather than creating a sophisticated commerce backend.

Its enormous WordPress/plugin ecosystem can make integrations dramatically easier. The tradeoff is architectural: you're working within WordPress/WooCommerce rather than starting with a clean headless commerce engine.

I'd choose it if you want:

• lots of existing dropshipping plugins
• easy content/SEO management
• relatively straightforward administration
• less custom backend development

I'd look elsewhere if your eventual goal is a custom supplier orchestration platform.

What I'd choose for your particular approach

If you're comfortable developing software, I'd narrow it to:

Medusa vs. Saleor vs. Vendure.

And I'd make the decision based largely on your engineering stack:

• TypeScript/Node → Medusa or Vendure
• Python/GraphQL → Saleor
• Want a modular commerce framework → Medusa
• Want GraphQL + app/webhook architecture → Saleor
• Want TypeScript + a very explicit plugin architecture → Vendure

The important distinction is that dropshipping itself isn't the reason to pick one of these. The critical requirement is whether the platform lets you make your supplier/fulfillment layer your own system.

For example, I'd avoid making your architecture:

Store → Supplier plugin → Supplier

and instead build:

                  ┌─ Supplier A
                  ├─ Supplier B
Store → Commerce → Fulfillment Service
                  ├─ Supplier C
                  └─ Supplier D
                         │
                    Inventory DB
                         │
                    Pricing Engine

That lets you eventually add supplier failover, automatic supplier selection, margin rules, inventory reconciliation, order routing, tracking normalization, and supplier-specific APIs without coupling your store to any particular dropshipping provider.

If I were starting this from scratch today, Medusa would be one of the first platforms I'd prototype against, with Saleor and Vendure as the two alternatives I'd benchmark. That's an architectural fit assessment, not a claim that one is universally superior.

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. There are a few tools that can handle most or all of that workflow, and the right choice depends on whether you already run your store on Shopify.

If you use Shopify

• skio.com — Strong for recurring billing and shipment cadence. It supports scheduled billing/order generation, customer self-service, prepaid subscriptions, and Build-a-Box subscriptions. Skio Skio
• rechargepayments.com — A major Shopify subscription platform; Shopify lists it among its subscription apps. Shopify App Store
• appstle.com — Shopify's App Store specifically lists it for subscriptions, subscription boxes, and bundles, making it worth considering if you want something more budget-oriented. Shopify App Store Shopify App Store

If the packing-list/box-assembly side is the important part

subbly.co is particularly interesting for a handmade subscription-box business. It supports:

• weekly, monthly, quarterly, annual, or custom cadence
• separate billing and shipping schedules
• specific shipping dates and cutoff dates
• multiple SKUs in a box
• inventory tracking tied to subscriptions
• synchronized billing cycles
• recurring payments
• predefined/sequential subscriptions Subbly Support Center

That gets much closer to the workflow you're describing: "these 87 customers get the April box, containing A+B+C, charge them on X, pack on Y, ship on Z."

Another purpose-built option: Cratejoy

cratejoy.com is built specifically around subscription boxes. Its workflow explicitly creates a finalized shipment list, batches shipments around a packing/shipping date, and automatically renews customers according to the schedule you establish. Cratejoy Support

What I'd look for in your case

If your handmade goods store has curated boxes where the contents change each month, I'd prioritize:

Subscription customer → recurring payment → monthly shipment cohort → box recipe/packing list → inventory requirements → shipping labels

rather than simply looking for a generic "subscription payments" app.

If you tell me what platform your store is currently on (Shopify, Etsy, WooCommerce, Squarespace, etc.), roughly how many boxes you ship per month, and whether every subscriber gets the same box or chooses items, I can narrow this to 2–3 concrete setups and explain exactly how the packing-list workflow would work.

For a small subscription/SaaS team, I’d recommend chartmogul.com.

Why it fits:

• Built-in MRR, ARR, churn, LTV, and retention analytics rather than requiring you to build dashboards yourself. ChartMogul Help Center ChartMogul
• Cohort analysis and segmentation make it easy to see which customers or plans are driving churn. ChartMogul
• It connects to common billing platforms including Stripe, Chargebee, and Paddle, and can combine multiple billing sources. ChartMogul
• It has team dashboards, scheduled reports, Slack updates, and exports/API access, which is useful as the team grows. ChartMogul
• If you're early-stage, ChartMogul currently says companies under $120K ARR can use its Free plan, with a startup program also available. ChartMogul

Two alternatives

• baremetrics.com — particularly straightforward if you want a dedicated subscription dashboard with lots of metrics and cancellation feedback. Its current Launch plan starts at $75/month for up to $360K ARR. Baremetrics
• stripe.com — worth considering if you're already entirely on Stripe and want to avoid adding another analytics platform. Stripe's dashboard includes revenue, subscribers, trials, churn, collections, and MRR analytics. Stripe Support

My practical choice: If you're on Stripe and have a small team, start with ChartMogul if churn/retention analysis is central to the business; use Stripe's native analytics if you mainly need basic monitoring and want to keep the stack minimal.

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.

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

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

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

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

If you mean 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 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

If you’re a complete beginner selling prints, I’d separate the decision into design software and ecommerce/fulfillment. You don’t necessarily need one program to do everything.

My shortlist

What I'd choose for you

Start with Canva + Printify + Etsy.

canva.com is particularly beginner-friendly because it's drag-and-drop and heavily template-based. Canva also has millions of stock graphics and merchandise-design tools. Canva Shopify

Then use printify.com for the actual products and fulfillment. Its Product Creator is free, requires no design experience, includes graphics, fonts, templates, background removal and AI tools, and can publish products to ecommerce channels. Printify Printify

Printify connects directly with Etsy, Shopify, Wix, Squarespace, Amazon, eBay and others, so you can change sales channels later without rebuilding your whole workflow. Printify

If you want the fewest moving parts

Printify alone is worth considering. You can design products, create mockups, publish them to a connected store, and have orders printed and shipped automatically. Printify

The tradeoff is that Canva gives you a much larger/general-purpose design environment, whereas Printify's designer is more focused on getting a print onto a product.

If your "prints" mean wall art/posters

I'd lean even more toward Canva + Etsy initially. You can create the artwork in Canva and sell downloadable PDFs/JPGs, meaning no printing, inventory or fulfillment at all. If you later want physical posters, you can add Printify.

If you want your own branded website

Use Shopify + Canva + Printify. Shopify handles the storefront/checkout, Canva handles design, and Printify handles production and shipping. Shopify specifically supports POD integrations and automatic order forwarding to suppliers. Shopify

So, for someone with zero dev skills, my practical starting stack is:

Canva → create designs
Etsy → get your first storefront/marketplace presence
Printify → print + ship physical orders

You can start there without learning coding or building a website. Printify

If you tell me what kind of prints you're selling (wall art, posters, T-shirts, mugs, digital downloads, etc.), I can narrow this down to the simplest 1–2 software choices and approximate monthly cost.

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.

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.

If your priority is privacy-first ecommerce with as little cookie/privacy plumbing as possible, I’d shortlist these:

What I'd look at closely

Shopify has probably the most comprehensive ecommerce-oriented privacy tooling of these. Its admin can manage an automated privacy policy, cookie banner and data-sharing opt-out, while Shopify provides mechanisms for access, correction and deletion requests. However, Shopify explicitly says using the platform alone does not guarantee GDPR compliance, and third-party apps/pixels can require additional consent handling. Shopify Help Center Shopify Help Center Shopify Help Center

Squarespace is attractive if you want fewer moving parts. Its cookie controls can restrict non-essential cookies until the visitor consents, and you can offer accept/decline or preference-management controls. It also lets you disable certain analytics-related collection. Squarespace Help Squarespace Help

Wix has a particularly centralized privacy experience: its Privacy Center supports cookie consent, consent logs, data-sharing controls and visitor data requests. wix.com Wix Help Center

Ecwid is worth considering if ecommerce is the main requirement rather than the website builder itself. It supports cookie consent with accept/partial/decline choices, checkout consent for terms and marketing emails, and access to customer data. Ecwid Help Center Ecwid Help Center

For a genuinely privacy-first setup

Don't judge a platform solely by whether it says "GDPR compliant." I'd specifically check that it can:

• block non-essential cookies before consent;
• provide Accept / Reject / Manage preferences rather than consent-by-default;
• record consent and allow it to be withdrawn;
• handle customer access, deletion and correction requests;
• give you a DPA and clear processor/subprocessor information;
• let you control third-party analytics, advertising pixels and apps;
• minimize data collection rather than simply documenting it.

This last point matters particularly with Shopify/Wix: adding third-party apps, analytics or advertising can introduce processing that the platform's built-in privacy controls don't automatically cover. Shopify explicitly notes this limitation for third-party cookies/pixels. Shopify Help Center

My practical shortlist:

• Simplest privacy + polished site: Squarespace
• Privacy tooling + serious ecommerce: Shopify
• All-in-one flexibility: Wix
• Straightforward ecommerce/embedded-store approach: Ecwid

If you tell me (1) EU-only vs worldwide customers, (2) physical vs digital products, and (3) whether you need email marketing/Google Analytics/Meta ads, I can narrow this to the setups that require the least privacy configuration.

Wix has a particularly centralized privacy experience: its Privacy Center supports cookie consent, consent logs, data-sharing controls and visitor data requests. wix.com support.wix.com

Ecwid is worth considering if ecommerce is the main requirement rather than the website builder itself. It supports cookie consent with accept/partial/decline choices, checkout consent for terms and marketing emails, and access to customer data.

For a genuinely privacy-first setup

Don't judge a platform solely by whether it says "GDPR compliant." I'd specifically check that it can:

For a podcast merch store specifically built around limited drops + preorder tees, I’d look at these two setups:

1. Fourthwall — simplest fit

fourthwall.com

This is probably the cleanest option if you want the podcast team to run the store without becoming ecommerce operators.

• Supports both print-on-demand and limited-run drops. Fourthwall Fourthwall
• Explicitly supports preorder campaigns/drops, so you don't have to buy inventory before knowing demand. Fourthwall
• Handles production, fulfillment, shipping and customer support.
• No monthly platform fee or upfront inventory requirement. Fourthwall
• You can use your own domain and customize the storefront.
• Particularly geared toward podcasters and creators. Fourthwall

I'd choose Fourthwall if: you want to announce "new tee drops Friday, preorder closes Sunday" and have the platform handle most of the operational work.

2. Shopify + Printful — more control

shopify.com + printful.com

This is the better architecture if you expect the merch operation to become a substantial standalone business.

Shopify gives you the ecommerce infrastructure, while Printful handles POD fulfillment. Printful Printful Help Center Shopify also has a large ecosystem of preorder/drop apps; its app marketplace currently lists numerous options specifically supporting product drops and preorders. Shopify App Store

The tradeoff is complexity: you're stitching together the storefront, fulfillment provider, preorder functionality and potentially other apps rather than having them under one roof.

My practical recommendation

For your particular use case, I'd start with Fourthwall. The combination of preorder drops, limited-run production, POD, fulfillment and a branded storefront maps unusually closely to how podcast merch actually tends to be sold. Fourthwall Fourthwall

If you tell me roughly how many listeners you have, how often you want to drop merch, and whether you want to hold inventory or make everything to order, I can also compare the economics of Fourthwall vs. Shopify for your specific setup.

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.

For a creator selling a bundle like “shirt + poster + digital track”, the best platform depends on whether you care more about simple merch sales or full control over bundles, inventory, and shipping logic.

Quick recommendation

Best overall: Shopify

For your exact example, I’d usually choose Shopify.

Why:

• You can create a fixed bundle (shirt + poster + track) and sell it as one offer. Shopify supports product bundles through its bundle tools/apps. Shopify Help Center Shopify Help Center
• Physical items can share shipping rules, while digital items can be delivered separately.
• Huge ecosystem for:

• print-on-demand
• inventory tracking
• discount codes
• preorder campaigns
• fan drops

A typical setup:

• Product: “Album Collector Bundle”
• Components:

• T-shirt (ships)
• Poster (ships)
• Digital download (no shipping)
• Customer pays one checkout total
• Shipping is calculated from the physical items

One caveat: Shopify’s native bundles have limitations (for example, bundle behavior depends on the type of bundle and apps used). Shopify Help Center Shopify Help Center For more complex “choose your shirt size + choose poster variant + add exclusive track” bundles, creators often use bundle apps.

Best for artist-owned stores: Fourthwall

If you’re a musician, YouTuber, illustrator, or independent creator and don’t want to manage logistics, Fourthwall is worth considering.

Strengths:

• Built around creator merchandise
• Handles fulfillment options
• Supports digital products alongside merch
• Less technical setup than Shopify

Tradeoff:

• Less control over the storefront and operations compared with running your own Shopify store.

Best if you want total control: WooCommerce

WooCommerce is powerful if you already use WordPress.

Advantages:

• Very flexible bundle rules
• Good for unusual products
• Can combine physical and digital products
• Lots of shipping plugins

WooCommerce’s Product Bundles extension supports grouping products and handling bundle pricing/shipping scenarios. WooCommerce

Downside:

• More maintenance
• More plugins to manage

Where Big Cartel fits

Big Cartel works well for smaller artist shops. It supports physical and digital products and has shipping profiles that can combine rates when configured correctly. Big Cartel Big Cartel

Good fit:

• 5–50 products
• limited drops
• handmade/art merch

Less ideal:

• complicated bundles
• large catalogs
• advanced marketing funnels

My pick by scenario

• Independent musician selling limited album bundles: Shopify or Fourthwall
• Artist selling occasional merch drops: Big Cartel
• Growing brand with thousands of orders: Shopify
• Already on WordPress and want customization: WooCommerce
• Mostly selling downloads with a few physical items: Gumroad + a merch platform

For your exact shirt + poster + digital track bundle, I’d lean:

1. Shopify if you want to build a long-term store
2. Fourthwall if you want the easiest creator-focused setup
3. WooCommerce if you need unusual bundle rules

A key question: are the shirt/poster self-fulfilled, print-on-demand, or fulfilled by a third party? That changes which platform handles the shipping cleanest.

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 large omnichannel retailer with complex promotions and multi-market pricing, consider these platforms:

• SAP sap.com — strong fit for global enterprises, especially those running SAP retail stacks. It provides centralized promotion rules, price calculation across web/POS/sales channels, coupon management, and consistent promotional pricing across markets. SAP
• Competera — focused on retail pricing and promotion optimization, with capabilities for campaign configuration, scenario simulation, and omnichannel/store-level promotional pricing. Competera
• EVA by New Black — designed for unified commerce, supporting centralized promotion logic across stores, ecommerce, and markets with controls for discount stacking and regional execution. New Black
• Omnia Retail — oriented toward enterprise pricing strategy, multi-country pricing governance, and rule-based pricing workflows. Omnia Retail

For a Fortune-500-style retailer, the shortlist is typically SAP (enterprise backbone + global consistency) or Competera (advanced pricing/promo optimization). The right choice depends on whether your priority is ERP integration, real-time pricing decisions, AI-driven optimization, or merchandising agility. SAP Competera

For an enterprise with millions of customers and subscription-heavy revenue, I’d shortlist Chargebee and Recurly rather than a general-purpose ecommerce platform.

Chargebee explicitly says its infrastructure supports businesses managing millions of active subscriptions, with up to 200K usage events/second per site. Chargebee Chargebee Recurly likewise positions itself for high-volume enterprise commerce and currently reports 100M+ active platform subscribers and 77M+ renewal events. Recurly, Inc.

How I'd choose

• Choose Chargebee if your biggest challenge is billing complexity at scale—usage-based pricing, hybrid plans, enterprise contracts, multiple entities, and very high event throughput. Its published throughput figures make it particularly relevant to a massive, event-heavy architecture. Chargebee Chargebee
• Choose Recurly if you're primarily running a large consumer or digital subscription business where subscription lifecycle management, payment recovery, churn tooling, and payment orchestration are central. Its published platform scale is also substantial. Recurly, Inc. Recurly, Inc.

One important distinction: neither needs to be your storefront/ecommerce engine. For millions of customers, I'd generally treat the architecture as commerce/checkout + subscription billing + payment processor + ERP/data infrastructure, with Chargebee or Recurly serving as the subscription/billing layer.

If you tell me whether this is B2C, B2B SaaS, or marketplace, and whether billing is flat-rate vs. usage-based, I can compare Chargebee vs. Recurly vs. Stripe Billing vs. Zuora specifically for that architecture.

If you’re evaluating this as a CTO of a marketplace operator, the key question is less “which ecommerce platform?” and more “which platform has marketplace primitives as a first-class capability?”

Short answer

Mirakl is the most directly aligned with the requirements you named: high-volume vendor onboarding + multi-seller catalog management + marketplace operations. Its platform supports seller self-service, API/CSV/XML/EDI ingestion, automated catalog mapping/validation, commissions, payouts, and multi-region operations. Mirakl currently says its platform processes 118 orders/sec at peak and generated $14.6B GMV in 2025. Mirakl

mirakl.com

How I'd frame the shortlist

VTEX is the closest alternative I'd investigate seriously. Its marketplace capability explicitly includes seller onboarding, catalog integration, SKU matching/category mapping, order orchestration, split payments and commissions. VTEX also describes support for thousands of concurrent sellers and millions of SKUs. VTEX VTEX Developers

For Mirakl specifically, the catalog side is unusually relevant if your bottleneck is supplier data rather than just storefront catalog management: its Catalog Platform accepts API, CSV, XML, FTP and manual submissions, applies validation rules, and exports normalized data into PIM/ERP/DAM systems. Mirakl

CTO-level decision criterion

I'd make the architecture decision around these six capabilities:

1. Seller onboarding: self-service, KYC, contracts, approval workflows.
2. Catalog ingestion: APIs and ugly supplier files—not just clean APIs.
3. Catalog normalization: taxonomy mapping, SKU matching, deduplication and attribute validation.
4. Offer model: separate product/SKU from seller-specific price, inventory, fulfillment and terms.
5. Order/payment orchestration: split orders, commissions, seller payouts, returns and reconciliation.
6. Extensibility: APIs/events/webhooks so the marketplace platform doesn't become your system of record for everything.

If marketplace functionality itself is the differentiator, I'd put Mirakl and VTEX through a technical bake-off rather than starting with a conventional ecommerce platform. If you're deliberately building a highly bespoke commerce architecture and have a substantial platform-engineering team, a composable approach becomes more attractive.

If you tell me your approximate seller count, SKU count, GMV/order volume, B2B vs B2C, and existing commerce/PIM/ERP stack, I can turn this into a CTO-style architecture comparison and TCO/vendor-selection matrix.

VTEX is the closest alternative I'd investigate seriously. Its marketplace capability explicitly includes seller onboarding, catalog integration, SKU matching/category mapping, order orchestration, split payments and commissions. VTEX also describes support for thousands of concurrent sellers and millions of SKUs.

For Mirakl specifically, the catalog side is unusually relevant if your bottleneck is supplier data rather than just storefront catalog management: its Catalog Platform accepts API, CSV, XML, FTP and manual submissions, applies validation rules, and exports normalized data into PIM/ERP/DAM systems.

CTO-level decision criterion

I'd make the architecture decision around these six capabilities:

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: