The open-source ecommerce framework for Drupal, maintained by Centarro. When it's the right engine for your store, and when WooCommerce or Shopify is the smarter pick.
Drupal Commerce is the ecommerce framework that turns a Drupal site into a store. It is free, open source under the GPL, maintained mainly by Centarro, and it runs everything from small catalogs to stores processing billions in annual sales. The question worth answering isn’t “what is it,” which the official docs cover well. It’s whether you should build your store on it. We build both Drupal Commerce and WooCommerce stores, so here is the honest version.
It is not a bolt-on shopping cart. Commerce is a set of Drupal modules that model products, orders, payments, taxes, and promotions as native Drupal entities. That matters because everything else in Drupal, content, users, permissions, multilingual, views, treats your store data as first-class. You are not gluing a store onto a CMS. The store is part of the CMS.
The current line is Commerce 2.x and 3.x running on Drupal 10 and 11. Payments go through gateway modules for Stripe, PayPal, Braintree and others. Tax is handled by Commerce Tax with optional TaxJar or Avalara integration for US sales-tax automation. None of that costs a license fee.
We recommend it in a few specific situations, not as a default:
That last point is the real commercial case. For a large, complex store, the practical alternatives to Drupal Commerce are Adobe Commerce and a custom build, and both cost far more to license or maintain. Drupal Commerce gives you enterprise-grade flexibility with no software fee, which is why the deals in this niche are valuable even though the search volume is modest.
Most small stores should not use Drupal Commerce, and we will tell you so. If you have a simple catalog, want to launch in a few weeks, and don’t already run on Drupal, WooCommerce or Shopify will get you there faster and cheaper. The Drupal developer pool is smaller and more expensive than the WordPress one, so ongoing maintenance costs more. You are paying for power you may not need.
A rough rule we use: if your store is the whole business and it’s straightforward, go WooCommerce or Shopify. If your store is one part of a larger content operation, or the commerce logic is genuinely complex, Drupal Commerce starts to earn its cost.
People ask this constantly. WooCommerce wins on speed to launch, plugin selection, hosting options, and cheaper developers. Drupal Commerce wins on data modeling, complex catalogs, B2B rules, and keeping a large editorial site and its store in one coherent system. We have migrated stores in both directions, and the move is almost always driven by fit rather than by one platform being “better.” A store that outgrew WooCommerce’s content side moves to Drupal. A store that never needed Drupal’s depth moves the other way to cut cost.
The software is free. The build is not. A real Drupal Commerce store is a development project, payment setup, tax configuration, catalog modeling, theme, and testing, so budget for developer time, not a license. That is the same trap people hit with Magento Open Source: “free” describes the download, not the store. If a fixed monthly subscription and zero developer involvement is what you want, that is an argument for Shopify, not against Drupal Commerce.
If you want a straight answer about whether Drupal Commerce fits your store, we give one before any contract. See our Drupal development services, browse the full Drupal modules we work with, or read how we handled a store migration in our WooCommerce case study.
Products, orders, payments, and taxes are Drupal entities, so content, users, permissions, and multilingual all apply to your store data directly.
Stripe, PayPal, Braintree and other gateway modules, with support for off-site and on-site (PCI-friendly) flows.
Commerce Tax handles rates and rules, with optional TaxJar or Avalara integration for automated US sales tax.
Run several stores, currencies, and languages from one install, which is where it pulls ahead of simpler carts.
We use this in real client projects — here's what we've learned.
Right engine for the right store. Drupal Commerce is excellent when commerce is part of a larger content operation, or when catalog and pricing logic is genuinely complex and you’d otherwise be looking at Adobe Commerce. For a simple store that needs to launch fast, it’s the wrong tool, and we’d point you to WooCommerce or Shopify instead.
Yes. The software is open source under the GPL with no license fee. You pay for hosting and for the development work to build and maintain the store, which is the real cost of any serious ecommerce site.
For the right store, yes. It’s strong when commerce sits inside a larger content site or when catalog and pricing logic is complex. For a small, simple shop, WooCommerce or Shopify is usually a better fit.
WooCommerce for fast launch, simple catalogs, cheaper developers, and a bigger plugin ecosystem. Drupal Commerce for complex catalogs, B2B pricing, multi-store setups, and editorial sites where content and commerce belong together.
The software is free, so the cost is development: payment setup, tax configuration, catalog modeling, theme, and testing. It’s a project budget, not a subscription. We scope it per store and tell you up front if a cheaper platform would serve you better.
It’s maintained primarily by Centarro, the company founded by the project’s original creators, with contributions from the wider Drupal community. It’s an actively developed project, currently on Commerce 2.x and 3.x for Drupal 10 and 11.
Yes. We map products, customers, orders, and URLs so you keep your search rankings. The move makes sense when a store has outgrown WooCommerce’s content side, not as a default upgrade.
We can install, configure, or customize it for you.
