ChatGPT answers, unedited

Yes. For a mixed catalog of physical + digital products, I’d put WooCommerce at the top of the list, especially if you want a complete self-hosted store rather than a commerce backend you have to build around.

My shortlist

1. WooCommerce — my recommendation

WooCommerce handles physical, virtual, downloadable, and hybrid products natively. Importantly, a downloadable product doesn't have to be purely digital: you can have a physical item that also gives the customer a download, and WooCommerce can keep shipping calculations for that product. WooCommerce WooCommerce

It also has a particularly useful workflow for mixed orders: customers can receive access to their digital purchases before the physical portion of the order has shipped. WooCommerce

I'd choose it if you want:

• Physical products with inventory/shipping
• Digital downloads
• Products containing both physical and digital components
• Variations where some variants are physical and others digital
• Coupons, subscriptions, memberships, etc. through extensions
• A conventional admin interface rather than building your own
• A huge ecosystem of payment, shipping, tax and fulfillment integrations

The main downside is that you're also adopting WordPress, so a large store can require more care around plugins, performance and maintenance.

woocommerce.com

2. Medusa — if you're a developer

If by "single system" you mean one commerce backend feeding a custom website/app, I'd seriously consider Medusa.

It's TypeScript/Node.js, headless and modular, so it's considerably more natural for a custom storefront than WooCommerce. The tradeoff is that you're assembling more of the solution yourself; its ecosystem isn't remotely as broad as WooCommerce's. WPBundle OpenReplay Blog

I'd pick Medusa over WooCommerce if you already have a developer comfortable with TypeScript and want a custom React/Next.js storefront.

3. Saleor — for a sophisticated catalog

Saleor is worth considering if you're anticipating things like multiple warehouses, currencies, channels, complex catalog structures or B2B. It's GraphQL-first and designed around headless commerce. WPBundle OSSAlt

It's powerful, but probably overkill for a normal mixed physical/digital shop.

4. Sylius — if you're building a bespoke system

Sylius is excellent if you're a PHP/Symfony team and want the ecommerce engine to bend around your business rather than the other way around. It's explicitly an ecommerce framework, rather than an immediately turnkey store. GitHub

That's a strength for unusual requirements, but it means substantially more development work.

What I'd choose

If your priority is "one self-hosted system that I can actually run my business on": → WooCommerce.

If your priority is "one open-source commerce backend that my developers will build a custom storefront around": → Medusa.

If you're expecting enterprise-level catalog/channel/warehouse complexity: → Saleor.

For your particular requirement—selling physical and digital products together—WooCommerce has an unusually good fit because the physical/digital distinction is already built into its product and order model rather than requiring you to bolt on a digital-delivery system. WooCommerce

If you tell me roughly how many products you have, whether digital products are downloads/software/courses, and whether you need subscriptions, I can narrow this down to 1–2 systems and explain the architecture I'd use.

Yes. If you want one self-hosted, open-source catalog that can contain both physical and digital goods, I’d shortlist these:

🥇 My pick: Medusa

Medusa documentation

Medusa is particularly well suited to your situation because its current product model explicitly accommodates physical items, digital items, and products that don't require shipping or inventory. You can also classify products as physical/digital and configure shipping and inventory requirements independently. docs.medusajs.com

For digital products, Medusa has a documented approach for storing files and delivering download links after purchase, while physical products use its normal inventory, shipping, and fulfillment machinery. docs.medusajs.com

That means you can have a catalog like:

• T-shirt → inventory + shipping
• E-book → downloadable file, no shipping
• Software license → digital fulfillment
• Physical + digital bundle → custom fulfillment
• Print + downloadable PDF → both fulfillment paths

It also has sales channels, so the same catalog can potentially feed your web store, mobile app, B2B channel, etc. docs.medusajs.com

When I'd choose the others

Saleor is my second choice if you're building something larger or more enterprise-oriented. It has native recipes for digital products alongside its physical commerce functionality, plus strong multi-channel and multi-region capabilities. docs.saleor.io The downside is operational complexity: you're taking on a fairly sophisticated headless stack.

WooCommerce is the pragmatic choice if you want a complete store you can administer without building much yourself. Its enormous WordPress ecosystem makes unusual payment, download, subscription, shipping, and marketing requirements easier to solve with existing extensions. docs.medusajs.comdocs.medusajs.comdocs.saleor.iowww.wpbundle.com

Bagisto makes sense if you're already a Laravel/PHP shop; it has a conventional ecommerce architecture and built-in capabilities such as multi-currency and multi-locale support. ossalt.com

Bottom line

If your priority is "one clean system for physical + digital, self-hosted, open source, and customizable", I'd rank them:

1. Medusa → 2. Saleor → 3. WooCommerce → 4. Bagisto → 5. Sylius

I'd especially favor Medusa if you're comfortable with Node/TypeScript and want a modern headless architecture. Its documentation specifically treats physical and digital selling requirements as part of the same commerce model rather than forcing you to bolt a separate digital-store system onto the physical store. docs.medusajs.com

If you tell me your expected catalog size, whether you need subscriptions/licenses, and whether you want a traditional storefront or headless/Next.js, I can narrow this down to the best 1–2 options.

Yes. For a single self-hosted open-source store containing both physical and digital products, I’d shortlist these:

My pick: Medusa

Medusa is probably the best fit if you're deliberately looking for a modern, genuinely self-hosted commerce backend. Its product/catalog architecture can handle normal physical products, while its documentation has a specific digital-products implementation: digital products can be associated with the normal product model, stored through a file module, and fulfilled with download links after purchase. docs.medusajs.com

That makes a mixed order such as:

T-shirt + physical book + PDF ebook + downloadable software

a natural architecture rather than having to bolt an entirely separate digital storefront onto your physical store.

The catch is that digital delivery isn't as turnkey as WooCommerce. Medusa's docs describe implementing a Digital Product Module, file storage, and fulfillment logic, so expect some development work. docs.medusajs.com

If you want the least development: WooCommerce

I'd choose WooCommerce if your priority is "I want to run the store, not build the store." Its huge WordPress ecosystem makes physical + downloadable products straightforward, and you get a conventional admin/storefront rather than assembling a headless application. Its ecosystem is dramatically larger than Medusa's. www.wpbundle.com

The tradeoff is WordPress/plugin complexity and ongoing maintenance.

If you're building something substantial: Saleor

Saleor is compelling if you expect multiple channels, currencies, warehouses, sophisticated catalog rules, or a custom frontend. It's API-only/GraphQL and has native multichannel capabilities, with control over product, pricing, currency, and stock per channel. github.com

I'd rank it behind Medusa for your particular requirement because digital goods aren't its standout turnkey feature, whereas Medusa explicitly documents digital-product fulfillment.

Bottom line

• Want easiest: WooCommerce
• Want best modern open-source foundation for a mixed catalog: Medusa
• Want enterprise/headless/multichannel: Saleor
• Want Symfony/PHP and maximum customization: Sylius

One important distinction: if by "digital products" you mean ebooks/PDFs/software downloads, Medusa is a particularly good candidate. If you mean subscriptions, licenses, memberships, courses, or SaaS access, I'd evaluate the platforms differently because entitlement/subscription management becomes more important than simple file delivery.

Yes. If by mixed catalog you mean one storefront containing both shippable physical goods and downloadable/digital products, I’d shortlist these:

My pick: WooCommerce

WooCommerce is probably the least painful choice if you want one system rather than a commerce framework you have to assemble. Its mature extension ecosystem means physical fulfillment and downloadable products can coexist in the same catalog and checkout, while WordPress gives you a built-in CMS. Current comparisons continue to put WooCommerce well ahead of the other open-source options on ecosystem breadth. www.wpbundle.com

WooCommerce official site

If you're technical: Medusa

Medusa is more attractive if you're building a custom/headless storefront. Its Node/TypeScript architecture and modular design make custom product and fulfillment logic cleaner than WooCommerce, but you'll generally build more of the surrounding infrastructure yourself. www.wpbundle.com

Medusa official site

If the catalog is complex: Saleor

Saleor is particularly compelling for large catalogs, multiple warehouses/channels, multiple currencies, and API-first architectures. Its core is genuinely open source and self-hostable, but deployment and development are considerably more involved than WooCommerce. github.com

Saleor official site

Sylius

Sylius is excellent when you have developers and want the commerce system to conform to unusual business rules. It's a Symfony-based framework rather than the easiest turnkey merchant solution, so I'd choose it for customization, not simplicity. github.com

Sylius official site

Bottom line:

• Want to run the store yourself with minimal engineering: WooCommerce
• Want a modern custom/headless system: Medusa
• Large/complex catalog and multi-channel: Saleor
• Highly bespoke business logic: Sylius

If you tell me roughly how many physical products, how many digital products, and whether digital items are simple downloads vs. licenses/subscriptions, I can narrow this to one and explain exactly how I'd model the mixed catalog.

For a catalog that mixes physical goods + digital downloads, I’d shortlist these self-hosted open-source platforms:

www.wpbundle.com

My default recommendation: WooCommerce

If your goal is “one system that just handles products”, WooCommerce is usually the strongest choice:

• A product can be physical, virtual, downloadable, or a combination.
• Mature handling for:
  • inventory
  • shipping
  • taxes
  • coupons
  • customer accounts
  • subscriptions (with extensions)
  • digital delivery
• Huge ecosystem for payment gateways and fulfillment integrations. www.wpbundle.com

A typical mixed catalog works like:

• Physical product
  • SKU
  • stock quantity
  • weight/shipping class
  • fulfillment workflow

• Digital product
  • downloadable files
  • access limits
  • expiration rules
  • automatic delivery after payment

• Hybrid product
  • physical item shipped
  • bonus PDF/video/license delivered digitally

When I would choose Medusa instead

Pick Medusa if you are building a custom storefront and have developers comfortable with Node/TypeScript.

Good fit:

• custom React/Next.js storefront
• mobile apps
• unusual checkout logic
• marketplace-style workflows

Its modular architecture is attractive, but you’ll generally build more integrations compared with WooCommerce’s mature plugin ecosystem. www.wpbundle.com

When I would choose Saleor

Saleor makes sense if you expect:

• large catalogs
• multiple warehouses
• multiple sales channels
• international selling
• custom frontends

It is API-first and designed for headless commerce, but self-hosting is more involved than a traditional store platform. github.com

Platforms I’d avoid for your use case

I’d be cautious with older “all-in-one” carts unless you have a specific reason:

• OpenCart/PrestaShop-style systems can work, but digital-product workflows and modern extensibility may require more customization.
• Enterprise systems like Magento/Adobe Commerce can do it, but they are usually heavier than needed unless you have a large operation.

A practical stack choice

Solo founder / small team

WordPress + WooCommerce + a download-management extension + good backups

Developer-led business

Medusa + Next.js + object storage (for files)

Growing commerce operation

Saleor + custom storefront + managed infrastructure

If you tell me roughly:

1. number of products (10s, 100s, 10,000+),
2. whether digital items are files, memberships, courses, or licenses, and
3. whether you need subscriptions,

I can narrow this to one or two choices.

Yes. If mixed physical + digital products in one catalog is the core requirement, I’d shortlist these:

My recommendation: WooCommerce if you want one system and minimal engineering

WooCommerce is probably the most straightforward choice if you want physical and downloadable products living alongside each other, with a conventional admin interface.

Its big advantage is the ecosystem: products, inventory, shipping, taxes, payments, subscriptions, memberships, downloads, etc. can all be handled through the WordPress/WooCommerce ecosystem. Current comparisons still put its ecosystem far ahead of the newer headless platforms. www.wpbundle.com

If you want a modern, API-first architecture: Saleor

Saleor is the one I'd investigate most seriously if you're comfortable running Docker/PostgreSQL and building a custom storefront.

Saleor has a rich product model, multiple channels, inventory/warehouse capabilities, promotions, payments, translations, and an extensible GraphQL API. It's explicitly designed as an open-source, headless commerce engine. github.com

The catch is that digital fulfillment may require more integration/customization than WooCommerce. Saleor is excellent as the commerce core, but it's not as much of an out-of-the-box "upload file → customer gets download" solution.

Medusa: great if you're a TypeScript shop

Medusa is attractive if you'd rather build around Node.js/TypeScript. Its modular architecture makes custom fulfillment and product behavior relatively clean. born.mt

I'd choose it when your products/workflows are unusual enough that custom development is a feature, rather than when you simply want the easiest mixed physical/digital store.

The important distinction

If by "digital products" you mean things like:

• ebooks/PDFs
• software downloads
• music/video files
• license keys
• courses
• digital memberships

then I'd evaluate digital fulfillment specifically, rather than just asking whether a platform supports a "digital product" type.

For example, your ideal order could be:

Physical T-shirt + downloadable PDF + software license → one cart → one checkout → one order → physical item goes to shipping fulfillment while digital items are delivered immediately.

For that exact scenario, I'd start with WooCommerce. If you want a headless/custom application, I'd start with Saleor or Medusa instead.

If you tell me what kinds of physical and digital products you sell and roughly how many SKUs/orders you expect, I can narrow it down to 2–3 systems and compare digital delivery, inventory, variants, subscriptions, taxes, shipping, payment gateways, and self-hosting complexity.

Yes. If your catalog genuinely mixes physical goods + downloadable/digital products, I’d shortlist these:

My pick: Medusa

Medusa is particularly well suited if you want one catalog and checkout for both types.

Its current product model explicitly supports physical and digital selling requirements. Products can have shipping/inventory requirements independently configured, so a physical variant can require shipping while a digital one doesn't. docs.medusajs.com

The important caveat: digital fulfillment isn't as turnkey as physical fulfillment. Medusa's official digital-product implementation uses a custom Digital Product module, file storage, and fulfillment logic for download delivery. They provide a complete example, but you'll need to implement/adapt that portion rather than simply ticking "digital product" in the admin. docs.medusajs.com

Saleor is the strongest alternative

Saleor is worth choosing if you're building something more sophisticated. Its documentation has a dedicated Digital Products recipe and its modeling system is designed for things like mixed-model catalogs, multiple channels, custom product types, and complex commerce rules. docs.saleor.io

It's also genuinely self-hostable—the project provides Docker-based instructions for running the platform yourself. saleor.io

When I'd choose each

• Medusa → best overall if you're comfortable with development and want maximum flexibility.
• Saleor → best if you're building a serious headless/omnichannel operation with complex catalog rules.
• WooCommerce → best if you want the least development work and a conventional admin interface; its enormous WordPress plugin ecosystem is a major advantage.
• Bagisto → attractive if your stack is already Laravel/PHP.

For your specific requirement, I'd start with Medusa vs. Saleor. The deciding question is whether you want a developer-oriented commerce framework (Medusa) or a more opinionated, enterprise/headless commerce platform (Saleor).

If you tell me roughly how many physical products, how many digital products, and whether digital items are files, licenses, subscriptions, or courses, I can narrow this to one and explain the exact architecture I'd use.

For a single self-hosted open-source ecommerce system that handles both physical and digital products, I’d shortlist these:

My picks by scenario

1. You want one system and the least custom development
→ WooCommerce
A good choice if you already use WordPress or want a merchant-friendly admin. You can have:

• physical products with inventory/shipping
• downloadable files
• subscriptions/memberships
• mixed carts

2. You want a serious commerce engine that treats digital + physical equally
→ Spree Commerce
This is probably the strongest match for your wording. It supports combining digital and physical items in the same checkout, with separate fulfillment logic (shipping vs download/license delivery). spreecommerce.org

3. You are building a custom storefront/app
→ Medusa or Saleor
Better if you want:

• mobile apps
• custom customer experiences
• marketplace-style workflows
• API-first architecture

4. You want a more traditional “install it and run a store” platform
→ PrestaShop or similar mature PHP platforms. blog.openreplay.com

Features I would specifically verify before committing

For a mixed catalog, don’t just check “supports digital products.” Look for:

• ✅ one cart containing physical + digital items
• ✅ separate fulfillment paths
• ✅ automatic download delivery after payment
• ✅ inventory tracking only for physical SKUs
• ✅ tax handling differences between goods and downloads
• ✅ refunds that can partially affect digital vs physical items
• ✅ license keys or expiring downloads if you sell software/content
• ✅ bundles (e.g., “book + digital guide”)

If you expect hundreds/thousands of SKUs and want one long-term platform, I’d lean Spree Commerce. If you want to be selling quickly with minimal engineering, I’d lean WooCommerce. opensourceprojects.ccspreecommerce.org

Yes. If one catalog needs to contain both shippable physical goods and downloadable/licensed digital goods, I’d shortlist these:

My top pick: Spree Commerce

Spree Commerce is unusually well suited to your exact requirement. Its current platform explicitly supports physical products alongside digital downloads, license keys, and subscriptions, with a single catalog, checkout, and order history. It also supports separate fulfillment workflows for physical and digital items. spreecommerce.org

The open-source core is BSD-3-Clause licensed, self-hostable, and has a REST API plus TypeScript SDK. The project also provides an open-source Next.js storefront. github.com

So a customer could, for example, put:

• 1 physical T-shirt
• 1 downloadable PDF
• 1 software license
• 1 subscription

into one cart/order, while the physical item goes through shipping fulfillment and the digital items are delivered electronically.

When I'd choose the others

WooCommerce — best if you want a conventional store that a non-developer can administer. Its huge WordPress/plugin ecosystem makes almost anything possible, but you'll generally assemble the digital-product functionality through extensions rather than getting the same clean commerce-engine approach as Spree.

Saleor — I'd choose this for a larger, highly customized/headless operation. It's GraphQL-only, has a sophisticated catalog/order model, multi-channel support, multi-warehouse capabilities, and a strong API-first architecture. github.com The tradeoff is that you're taking on more engineering responsibility, particularly around digital fulfillment.

Medusa — attractive if your team is already comfortable with TypeScript/Node.js and you want to build your own commerce workflows. Its modular architecture is excellent for customization, but for your particular requirement I'd rank Spree ahead of it because mixed physical/digital commerce is explicitly a first-class Spree feature. born.mt

Bottom line: if your priority is “one open-source, self-hosted store where physical and digital products genuinely coexist as first-class products”, I'd start with Spree. If you tell me your approximate catalog size, whether you need subscriptions/licenses, and whether you want a ready-made storefront or headless, I can narrow it down to 2–3 options.

Yes. If one catalog needs to contain both shippable physical goods and non-shippable digital products, I’d shortlist these:

My pick: Medusa

Medusa is particularly well suited to your use case. Its current product model explicitly supports physical and digital items, including products that don't require shipping or inventory management. You can configure shipping and inventory requirements independently, so a physical T-shirt and a downloadable ebook can live in the same catalog and checkout. docs.medusajs.com

It's also MIT-licensed and self-hostable, with its commerce modules available as open source. docs.medusajs.comgithub.comsaleor.io

Why I'd choose it: if you're comfortable running a Node/TypeScript application and want a clean system that you can customize rather than a WordPress site with lots of plugins.

When I'd choose the others

• Saleor — probably the strongest alternative if you expect a sophisticated, headless setup with multiple channels, currencies, warehouses, or complex catalog rules. It's open source, self-hostable, and has a mature GraphQL API/admin stack. saleor.io
• WooCommerce — best if you want the least custom development and a huge plugin ecosystem. It handles downloadable products alongside physical products naturally. The tradeoff is a heavier WordPress/plugin architecture.
• Sylius — excellent if your team is already strong in PHP/Symfony and wants maximum control. It's MIT-licensed and designed as a customizable ecommerce framework rather than a turnkey shop. github.com

Bottom line:
Medusa for a modern custom store → Saleor for complex/enterprise headless commerce → WooCommerce for easiest operation and widest plugin ecosystem.

One important distinction: if by "digital products" you mean secure file delivery/downloads, license keys, subscriptions, or software activation, rather than simply products with no shipping, I'd compare the platforms specifically on those workflows before choosing.

Yes. If one catalog needs to contain both shippable physical goods and downloadable digital products, I’d shortlist these:

My pick: Shopware 6

Shopware is probably the closest match to your requirements. Its product system explicitly supports physical and digital products, and it can even represent physical and digital versions as variants of the same product. Digital files can be attached directly to products for customer delivery. docs.shopware.com

That makes a catalog such as:

• T-shirt — physical
• E-book — digital
• Photoshop template — digital
• Course — digital
• Book — physical and e-book variant
• Bundle — physical + digital components

much more natural than trying to bolt digital delivery onto a primarily physical-product system.

Shopware also has an open-source core and is designed for substantial customization/self-hosting. www.shopware.com

If you're developer-first: Saleor

Saleor is my second choice if you're comfortable building the storefront and integrations yourself. It's API-first/GraphQL, self-hostable, and has a rich catalog model, multi-channel support, inventory, orders, payments, etc. saleor.io

The catch is that digital fulfillment is more of an integration/building-block problem than Shopware's ready-made digital-product workflow. I'd choose Saleor when the store is part of a larger custom application rather than when you simply want to get a mixed catalog selling quickly.

If you want maximum ecosystem: WooCommerce

WooCommerce remains the pragmatic option. Physical products are its bread and butter, while downloadable products are well established through the WooCommerce ecosystem. The enormous plugin ecosystem is its biggest advantage, although it can also mean more maintenance and plugin dependency. www.wpbundle.com

Bottom line

For your exact requirement, I'd rank them:

1. Shopware 6 — best native mixed physical/digital catalog
2. WooCommerce — easiest and biggest ecosystem
3. Saleor — best modern/headless architecture
4. Medusa — excellent if your team is TypeScript/Node-oriented
5. Sylius — excellent if you need to customize the commerce domain heavily

If you tell me roughly how many SKUs you have, whether digital products are files vs licenses/courses, and whether you need subscriptions, I can narrow this to one or two systems.

Yes. For a single self-hosted catalog containing both physical and digital products, I’d shortlist these:

My pick: WooCommerce

If your priority is “I want this working without building a commerce platform myself,” I'd choose WooCommerce. Its mature ecosystem makes it particularly easy to have physical products with shipping/inventory alongside downloadable products, subscriptions, memberships, etc. It also gives you WordPress's CMS capabilities. www.wpbundle.com

The downside is that WooCommerce can become plugin-heavy, so I'd be selective about extensions.

Best modern alternative: Saleor

If you're comfortable with a more technical, headless architecture, Saleor is probably the strongest alternative. It's API-first, supports multiple channels, currencies, stock, and product data natively, and is explicitly designed to be self-hosted/open source. github.com

It's a particularly good choice if your catalog might eventually involve:

• physical + downloadable products
• multiple storefronts
• multiple warehouses
• multiple currencies/languages
• custom checkout/business logic
• mobile or other non-web sales channels

The tradeoff is significantly more engineering/DevOps than WooCommerce.

Medusa: excellent if you're building custom

Medusa is compelling if your team is TypeScript/Node-oriented. It's headless and modular, so you can build your own digital fulfillment/download logic alongside normal physical fulfillment. Current comparisons generally put it ahead for developer experience, while WooCommerce wins on ecosystem breadth. www.wpbundle.com

My ranking for your particular requirement:

1. WooCommerce — best if you want a complete store with minimal custom engineering
2. Saleor — best if you want a serious, headless platform that can handle complexity
3. Medusa — best if you're a TypeScript team building a bespoke storefront
4. Bagisto — good Laravel/PHP option
5. Sylius — excellent for developers wanting maximum customization

One important distinction: “supports digital products” isn't quite the same as “handles mixed fulfillment elegantly.” I'd specifically evaluate how each system handles an order containing, say, one physical item + one downloadable item—including payment, shipping calculation, inventory, fulfillment status, download authorization, refunds, and customer emails.

If you tell me your preferred tech stack (PHP/WordPress, Node/TypeScript, Python, etc.) and whether you need subscriptions/licenses/download protection, I can narrow this to 1–2 systems.

Yes. If you need one self-hosted open-source catalog containing both physical and digital products, I’d shortlist these:

My recommendation: Medusa

Medusa is particularly well suited to your requirement. Its current product model explicitly supports products that are physical, digital, or don't require shipping/inventory, and you can configure shipping and inventory requirements independently. docs.medusajs.com

For digital products, Medusa provides a fulfillment architecture specifically intended for delivering download links/files after purchase, while physical products can use normal shipping fulfillment. docs.medusajs.com

It's also MIT-licensed and open source, and is designed as a modular commerce backend rather than a monolithic storefront. docs.medusajs.comgithub.comgithub.combagisto.com

The resulting model can be something like:

• Physical T-shirt → inventory + shipping
• PDF ebook → no inventory + download fulfillment
• Video course → no shipping + digital fulfillment
• Physical + digital bundle → potentially both fulfillment paths
• Subscription/service → no physical fulfillment

That flexibility is the main reason I'd choose it over a conventional ecommerce package if you're building something that may evolve.

Bagisto is worth serious consideration

If you don't want to build as much yourself, I'd look closely at Bagisto. It has explicit downloadable products alongside its normal physical-product types, and downloadable products bypass shipping at checkout. docs.bagisto.com

Its headless APIs support simple, configurable, bundled, and downloadable products, including customer access to purchased downloads. github.com

It's Laravel/PHP-based and MIT-licensed, with a substantial extension ecosystem. bagisto.com

So I'd choose:

• Medusa → if you're comfortable with Node/TypeScript and want maximum flexibility.
• Bagisto → if you want more ecommerce functionality out of the box and like Laravel.
• WooCommerce → if you're already invested in WordPress and want the enormous plugin ecosystem.
• Saleor → if you're building a sophisticated, API-first operation with multiple channels, currencies, warehouses, etc. Saleor is exceptionally capable but has a steeper engineering footprint. saleor.io

For your specific “physical + digital in one catalog” requirement, I'd put Medusa and Bagisto at the top of the list. If you tell me your stack (PHP/Node/Python), approximate catalog size, and whether you need subscriptions, marketplaces, or multiple stores, I can narrow it to one.

Yes. If your key requirement is one catalog containing both shippable physical goods and downloadable digital products, I’d shortlist these:

1. Medusa — best fit for a mixed catalog

Medusa is probably my first choice. Its product model explicitly supports physical and digital items, including products that don't require shipping or inventory. Its fulfillment system can be customized for digital delivery while using normal fulfillment for physical orders. docs.medusajs.com

It is MIT-licensed, self-hostable, TypeScript/Node.js, and modular, so you can keep both product types in the same commerce backend. github.com

Medusa

Best if: you're comfortable with development and want a modern, API-first system that you can customize heavily.

2. WooCommerce — best if you want the easiest merchant experience

WooCommerce is worth considering if you don't need a headless architecture. WordPress/WooCommerce handles physical products and downloadable products in the same store, with a huge extension ecosystem.

The tradeoff is that you'll generally rely more on WordPress plugins for advanced functionality than you would with Medusa's commerce modules.

3. Saleor — best for sophisticated/headless stores

Saleor is another strong option. It's API-only, GraphQL-native, supports products, checkout, payments and shipping, and is designed for composable/headless deployments. It can be self-hosted from its open-source repositories. saleor.io

Saleor

The downside for your particular use case is that Medusa documents the physical/digital distinction explicitly, whereas with Saleor you're more likely to build/customize the digital-fulfillment workflow yourself.

My recommendation

I'd choose Medusa if you're building a new system today and want a genuinely unified catalog rather than bolting digital products onto a primarily physical-store platform. Its current documentation specifically addresses mixed physical/digital selling requirements, which is unusually relevant to your use case. docs.medusajs.com

If you tell me whether you need subscriptions, license keys, automatic file delivery, product bundles, inventory, multiple vendors, or a visual/no-code admin, I can narrow this to the best 1–2 choices.