Drupal Commerce Modules for Ecommerce: Essential Modules by Job, Version Compatibility and How to Vet Them

The core of a Drupal ecommerce site is Drupal Commerce, which provides products, carts, checkout, orders, promotions, payments and taxes. Add contributed modules for stock management, shipping, extra payment gateways and cart improvements. As of October 2026, Commerce 3.x supports Drupal 10.3 and 11, while the older 2.x line targets Drupal 9.3 and 10, so check compatibility before you choose any module.

Key Takeaways

• Drupal.org lists Commerce 3.3.12 (released October 16, 2026) as the latest stable release, compatible with Drupal ^10.3 and ^11, maintained by Centarro and covered by the Drupal security advisory policy. About 41,680 sites report using it.
• The Commerce 2.x line (8.x-2.40, August 2024) targets Drupal ^9.3 and ^10. Drupal 9 reached end of life in November 2023, so new projects should not start there.
• Commerce Stock's 3.x branch adds support for Commerce 3.0 and Drupal 11 but was described as beta, so check its current status for production use.
• Before you add a module, check its Drupal core compatibility, last release, security advisory coverage and open issues.
• For card payments, use hosted fields or redirect flows from your gateway so you do not handle raw card data.

Why choose Drupal for ecommerce?

Drupal suits stores that need custom content models, complex workflows, multilingual sites, strong access control or deep integrations. You build the site from Commerce and contributed modules instead of a fixed platform. The trade-offs are more development and maintenance effort than a hosted platform such as Shopify. For other choices, see no-code ecommerce app builders and our Drupal ecommerce development services.

Which Drupal versions and Commerce releases should you use?

Source: drupal.org/project/commerce, read in October 2026. The earlier version of this post covered Drupal 9 and Commerce 2.x with Drupal 8.5 as the baseline, which is out of date. Drupal 10's own support end date was not confirmed in our research, so check Drupal.org's release cycle page when you plan your upgrade path. See our Drupal migration and upgrade service.

Which modules do you need, by job?

Modules from the earlier version, such as Basic Cart, Commerce Cart Estimate, Commerce Exchanger and Commerce Shipping Weight Tariff, may be niche or unmaintained for current versions. We did not verify them, so check each one's compatibility tab before use. The earlier version also described the Stripe module as supporting Bitcoin payments, which we could not confirm, so check your gateway's supported methods.

Inventory: Commerce Stock

Drupal.org says Commerce Stock's 3.x branch added support for Commerce 3.0 and Drupal 11, and its release notes call it a beta for a while. The older 8.x-1.x branch covered Drupal 9.2 and 10 and one issue says it was made incompatible, so confirm which branch you can use (Commerce Stock).

Payments

Prefer gateways that provide hosted fields, redirects or tokenization, so card data does not touch your server. Check the gateway's module status, supported payment methods in your country and PCI DSS responsibilities. Gateways named in the earlier version included Authorize.net, Stripe, PayPal, Square, Braintree and Razorpay.

Shipping and fulfillment

Use Commerce Shipping with flat-rate rules or live carrier rates, depending on your products. Carrier modules need an account with the carrier and testing for each service level.

Planning a Drupal store? Tell us your catalog, payments and integrations, and we will help you scope it. Get your project scoped

How do you vet a Drupal module?

1. Check core compatibility on the module page for Drupal 10.3 or 11.
2. Check the last release date and whether the maintainers respond to issues.
3. Look for security advisory coverage (the shield icon on stable releases).
4. Review the usage count and open issues for blocking bugs.
5. Test on a staging site with real products and a full checkout.
6. Plan updates. Use Composer, apply security updates promptly and test after each update.

What else matters for a Drupal store?

• Performance. Caching, image handling and database tuning for catalog pages.
• Security and PCI. Hosted payment fields, HTTPS, access control and regular updates.
• Hosting. A host that supports Drupal and your traffic.
• Headless options. You can keep Commerce on the back end and build the storefront in a JavaScript framework. See headless Drupal.
• Cost. We found no reliable cost data for Drupal Commerce builds. Ask for a written estimate against a clear feature list.

How Appic builds Drupal ecommerce sites

Appic Softwares has built custom software since 2018, with offices in Jaipur (India), Frisco, Texas (USA) and Munich (Germany), and a 5.0 Clutch rating from 24 verified reviews. We offer Drupal development, Drupal ecommerce development and dedicated Drupal developers. Our average rate is about $35 per hour, and projects typically start around $10,000 for a focused scope. Appic is a publisher with a commercial interest, so compare quotes.

What changed from the earlier version of this post?

The September 2023 version was built on Drupal 9 and Commerce 2.x, covered "4 must-have modules" while listing about a dozen, repeated a sentence, left several modules unlinked, made unverified claims such as Bitcoin support for Stripe, gave vague payment-method guidance without PCI notes and had no FAQ. This update adds current Commerce and Drupal compatibility, a job-based module table, a vetting checklist and performance, security and hosting notes.

Ready to build a Drupal ecommerce site? Share your catalog, payments and integrations. We will reply with a plan and a cost range. Talk to our team