The new release of Drupal Commerce resolves 39 issues, including administrative improvements and a new API for resolving currencies.

Replacing Inline Entity Form with a better order items widget

The new order items widget eliminates Commerce Core's final out-of-the-box usage of the Inline Entity Form module. Eventually, we want to eliminate this dependency, and for two reasons. First, our own widget provides a better user experience. The new widget offers a cleaner interface that displays SKUs in the order items table, making it easier for merchants to verify they're adding the correct products. The video below demonstrates the new widget.

Second, Inline Entity Form still doesn’t have a stable release, which can cause build and installation issues.

Looking ahead, this foundation sets us up for even more ambitious improvements to order management, including support for inline editing directly from the order page.

Status for Store entities

In a marketplace scenario, where there are multiple stores from multiple merchants, administrators need a way to disable and enable stores easily. Important for new store approval workflows or sunsetting a brand. We’ve now added a status field to the store entity, with the following implications:

• Products assigned only to disabled stores cannot be added to carts
• Existing carts tied to disabled stores become inaccessible for checkout
• The system prevents order creation for disabled stores entirely

There are still some improvements to make around this feature, but the field enables some core functionality that marketplace operators have been missing.

A new currency resolver API 

Previously, Commerce lacked a standardized way to determine the current currency programmatically. The new currency resolver API fills this gap. This API enables more sophisticated multi-currency experiences. The Commerce Currency Resolver module has already been updated to use this new approach, demonstrating how contrib modules can now provide currency switching based on user preferences, cookies, or geographic detection through a standardized interface.

Customer experience improvements

We've added the ability to set default payment methods, addressing a long-standing user experience gap where returning customers had to reselect their preferred payment option. The system now properly handles payment method defaults both in account management and during checkout.

We've also improved tax transparency by allowing merchants to display tax rates in adjustment labels, so customers see "VAT (20%)" instead of just "VAT" in order summaries.

Other notable additions, bug fixes, and stability improvements

• Fixed a security issue where unpublished product variations could be accessed by anonymous users despite being marked as unpublished.
• Improved order item type access controls to allow proper display in Views and administrative interfaces without requiring full administrative permissions.
• Resolved exceptions when payment methods were deleted during active checkout processes, preventing customers from being stuck in broken checkout flows.
• Improved order refresh logic to prevent calculation errors during cart updates.
• Added the ability to specify a custom email address when resending order receipts.
• Improved validation in the AddToCartForm to prevent non-purchasable items from being submitted.

What’s next?

Commerce Core 3.2.0 is available now through Composer for sites running Drupal 10.3+ or Drupal 11. We recommend thorough testing in development environments before updating production sites, particularly if you're using custom payment gateway implementations or complex promotion configurations.

We're grateful to all 73 contributors who made this release possible. The breadth of contribution demonstrates the strength of the Commerce community and helps ensure the platform continues to evolve based on real-world usage.

You can view the complete list of changes in the release notes.