A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More

Quan Mai
Dec 19, 2018
  3503
(9 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
Scheduled job for deleting content types and all related content

In my previous blog post which was about getting an overview of your sites content https://world.optimizely.com/blogs/Per-Nergard/Dates/2026/1/sche...

Per Nergård (MVP) | Jan 30, 2026

Working With Applications in Optimizely CMS 13

💡 Note:  The following content has been written based on Optimizely CMS 13 Preview 2 and may not accurately reflect the final release version. As...

Mark Stott | Jan 30, 2026

Experimentation at Speed Using Optimizely Opal and Web Experimentation

If you are working in experimentation, you will know that speed matters. The quicker you can go from idea to implementation, the faster you can...

Minesh Shah (Netcel) | Jan 30, 2026

How to run Optimizely CMS on VS Code Dev Containers

VS Code Dev Containers is an extension that allows you to use a Docker container as a full-featured development environment. Instead of installing...

Daniel Halse | Jan 30, 2026

A day in the life of an Optimizely OMVP: Introducing Optimizely Graph Learning Centre Beta: Master GraphQL for Content Delivery

GraphQL is transforming how developers query and deliver content from Optimizely CMS. But let's be honest—there's a learning curve. Between...

Graham Carr | Jan 30, 2026

Optimizely Graph Best Practices - Security, Access Control and Performance Optimisation

Introduction Building on Part 1's content modeling and querying practices , this Part 2 focuses on the security and performance considerations...

Jon Williams | Jan 29, 2026