Commerce 13 is ready to go
The day has finally come, and we got the approval from our QA team for Commerce 13. It will be released to public earlier next week.
If you plan to upgrade to Commerce 13 (which you should ;) ), these are a few things to keep in mind
- Commerce 13 is a breaking change release, which means you will most likely have to update your code for it to get it compiled. If you are using a more recent version of Commerce and if you are using the up-to-date features, you will have less things to worry about, and vice versa, so that's important to plan ahead.
- The most signficant breaking changes in Commerce 13 are the removal of old promotion system, and old APIs like Entry, Node, and CartHelper, which we talked in details here https://world.episerver.com/blogs/Quan-Mai/Dates/2018/12/planned-breaking-changes-for-commerce-in-2019/. We urge you to switch to newer system/APIs because they are not only the way forward, they are also better in many aspects (if not "any aspects")
- We also take this change to introduce new features that would require breaking changes: new extendable OrderStatus and OrderShipmentStatus , a new API to get the parent order group from its component (orderforms, shipments or lineitems), or a new APIs to calculate taxes in batch of line items instead of one by one.
- Commerce 13 also contains some non breaking changes new feature, including per-promotion catalog item exclusion and managing shipping addresses in CSR UI.
A full list of changes in Commerce 13 can be seen here https://world.episerver.com/documentation/upgrading/episerver-commerce/commerce-13/breaking-changes-commerce-13/ .
Commerce 13 contains a small migration step, which should complete within seconds, so data migration should not be of your concern. You are welcome to test it when it's released and get back to us if you need further assistance.
A new version of ServiceAPI, FindCommerce and Avatax which support Commerce 13 will be quick to follow.