World is now on Opti ID! Learn more

Quan Mai
Dec 19, 2018
  66
(0 votes)

Planned breaking changes for Commerce in 2019

When we are closing on the end of 2018, it's probably the best time to talk about what future - namely 2019 - has for us. What I can share at the moment is we started working on a new major version of Commerce - most likely, Commerce 13. Since we moved to the weekly releases process, major releases have no long contained new major features, because thoses should have been released in some minor releases as soon as our QA give it a GO. Instead, major releases are now reserved for breaking changes, so you know what you should expect when you upgrade.

So far, these breaking changes have been planned:

  • There will be a small breaking change in behavior with promotion engine to make it works better with rounding.
  • There will be a small breaking change with tax calculation interface to allow tax calculation in batches.

Also, old APIs and features built on old APIs that were marked Obsolete for more than 12 months since release will be removed, most notably:

  • The old promotion system. (Yay!). We wholeheartly recommend the (new) promotion system because it is superior in every way.
  • WarehouseInventory and its related APIs (finally). We recommend to use IInventoryService instead.
  • APIs that use ApplicationId (which were obsoleted in Commerce 11). Just use the overload without ApplicationId.
  • CartHelper! We recommend to use the abstraction APIs (IOrderRepository and other interfaces)
  • Node/Entry. We recommend to use content API (IContentLoader/IContentRepository/EntryContentBase ...) instead.
  • Commerce Gadgets will be removed.

While we are working hard to make all these things happen, the list is not final, and might change during the development phase. We will keep you posted.

Dec 19, 2018

Comments

Please login to comment.
Latest blogs
Make Global Assets Site- and Language-Aware at Indexing Time

I had a support case the other day with a question around search on global assets on a multisite. This is the result of that investigation. This co...

dada | Jun 26, 2025

The remote server returned an error: (400) Bad Request – when configuring Azure Storage for an older Optimizely CMS site

How to fix a strange issue that occurred when I moved editor-uploaded files for some old Optimizely CMS 11 solutions to Azure Storage.

Tomas Hensrud Gulla | Jun 26, 2025 |

Enable Opal AI for your Optimizely products

Learn how to enable Opal AI, and meet your infinite workforce.

Tomas Hensrud Gulla | Jun 25, 2025 |

Deploying to Optimizely Frontend Hosting: A Practical Guide

Optimizely Frontend Hosting is a cloud-based solution for deploying headless frontend applications - currently supporting only Next.js projects. It...

Szymon Uryga | Jun 25, 2025

World on Opti ID

We're excited to announce that world.optimizely.com is now integrated with Opti ID! What does this mean for you? New Users:  You can now log in wit...

Patrick Lam | Jun 22, 2025

Avoid Scandinavian Letters in File Names in Optimizely CMS

Discover how Scandinavian letters in file names can break media in Optimizely CMS—and learn a simple code fix to automatically sanitize uploads for...

Henning Sjørbotten | Jun 19, 2025 |