2026 Commerce Connect release notes

  • Updated

Follow this article to receive email notifications when new Commerce Connect packages are available for 2026. Product packages are found on the Optimizely NuGet server. 

You can find prior versions of release notes and user guides at the following locations:

June

EPiServer.Commerce 15.0.1

Bug fixes

  • COM-21667 – Fixed an issue where shipping method parameters with different names but the same value were incorrectly rejected as duplicates in the Commerce admin UI.
  • COM-21699 – Fixed a database migration failure that occurred when the database collation differed from the server collation.
  • COM-21743 – Fixed the Failed to process your payment checkout failure with 3D Secure (3DS) payments.
  • COM-21760 – Fixed a performance issue where Commerce UI module builds unnecessarily reprocessed unchanged .zip files in modules\_protected, increasing build times on sites with large module directories.

EPiServer.Tracking.Core 3.0.0

Enhancements

  • Released EPiServer.Tracking.Core 3.0.0, which adds support for .NET 10 and Optimizely CMS 13, enabling compatibility with Commerce 15.

EPiServer.Session 3.0.0

Enhancements

  • Released EPiServer.Session 3.0.0, which adds support for .NET 10 and Optimizely CMS 13, enabling compatibility with Commerce 15.

EPiServer.Personalization.Common 5.0.0

Enhancements

  • Released EPiServer.Personalization.Common 5.0.0, which adds support for .NET 10 and Optimizely CMS 13, enabling compatibility with Commerce 15.

May

Optimizely.Graph.Commerce 1.5.0

Enhancements

  • Updated the Optimizely.ContentGraph.Cms dependency to version 4.4.0 and resolved the related breaking changes. This keeps Optimizely.Graph.Commerce aligned with the latest Optimizely Graph CMS package, so Commerce Connect projects can adopt current Graph CMS features and fixes without dependency conflicts. See Optimizely Graph for Commerce Connect for setup details.

Bug fix

  • COM-21516 – Fixed the NullReferenceException that occurred in the Commerce Graph search provider when the Indexers section was omitted from SearchOptions in appSettings.json.

EPiServer.Commerce 14.45.2

Bug fixes

  • COM-21191 – Fixed the issue where saving a cart triggered three cache invalidation messages from DefaultOrderRepository, which could flood the Service Bus on high-traffic sites. The number of messages emitted per cart save is now reduced, easing pressure on the Service Bus while keeping cache consistency intact.
  • COM-21248 – Fixed the issue where the Commerce dashboard displayed incorrect logic and rendering errors when accessed. The dashboard now loads with the expected data and behavior.
  • COM-21269 – Fixed the incorrect discount calculation that occurred when stacking multiple percentage promotions on the same line item with ApplyPromotionUnitIndividually = true and PromotionExclusionLevel = ExclusionLevel.Unit. The internal ApplyDiscountIndividually method now uses Price instead of PlacedPrice, so combined promotions no longer reduce the line item to a 100% discount.

EPiServer.Commerce 14.45.3

Bug fixes

  • COM-21395 – Fixed the issue where clicking a catalog row on the catalog root page did not open the catalog item, and where the column-settings sidebar omitted the default columns.
  • COM-21423 – Fixed the MetaObjectValidationException ("Specified 'Created'/'Modified' field value was out of the range of valid values") that occurred when accessing /episerver/commerce on an empty Commerce project after upgrading CMS to 12.34.2 and Commerce to 14.45.1.

EPiServer.Commerce 14.45.4

Bug fixes

  • COM-21470 – Fixed the issue where a lower-priority promotion was incorrectly skipped on eligible line items when it shared an exclusion rule with a higher-priority promotion.
  • COM-21524 – Fixed the HTTP 400 You lack sufficient access rights to perform this operation error that occurred when saving the same variant price entry a second time in the Catalog UI. Successive edits to the same price entry now save without an access-rights error.
  • COM-21554 – Fixed the validation issue that prevented creating shipping method parameters with different names but the same value.
  • COM-21642 – Fixed the issue where the RemoveExpiredCarts scheduled job logged "No message" in its history when running under a UI culture without an available translation (for example, Vietnamese).

February

Optimizely.Graph.Commerce 1.4.0

Enhancements

EPiServer.Commerce 14.45.1

Bug fixes

  • COM-21140 – Updated the dependency to remove security vulnerabilities.
  • COM-21150 – Updated to skip setting the access rights in read-only mode.

EPiServer.ServiceAPI 7.3.2

Bug fixes

  • COM-21121 – Fixed an issue where LineItem custom properties were not saved.

January

Optimizely.Commerce.Opal.Tools 1.0.0

Enhancements

  • Added the ability to use Optimizely Opal tools for AI-powered campaign and promotion management. See Get started with Opal tools.
  • Released the Product Promotion agent in Optimizely Opal, which helps build and configure product promotions in Commerce Connect, seamlessly handling the assignment of products and variants and the application of specific promotion types. 

EPiServer.ServiceAPI 7.3.1

Bug fix

  • COM-20965 – Fixed an issue where the sort order of assets did not update after re-import through the Service API.