Introduction
In this article, you’ll learn how we handle OrderCentral updates, the difference between minor and major releases, and what you can expect as a customer.
How our release process works
We automatically update all OrderCentral orgs to ensure every customer runs on the same stable version. This allows us to provide optimal support and resolve issues quickly.
Patches (minor updates)
Minor updates, such as from version 3.0.11 to 3.0.12, are deployed automatically during the night. These updates include bug fixes and small technical improvements, but no new functionality.
Since these updates do not impact how the platform works, we don’t send a separate email notification for them.
Major releases (new versions)
Major releases, such as from version 2.0 to 3.0, introduce new features or significant changes. For these releases:
Customers receive an email in advance with an overview of all changes, including any required post-release actions.
All sandbox environments are updated one week later, allowing customers to test and verify that everything works as expected.
Production environments are updated one month later unless we receive feedback in the meantime that requires us to postpone the deployment (for example, in case of a detected issue).
Backwards compatibility
We ensure that every new version is fully backwards compatible. If something doesn’t work as expected after an update, resolving it becomes our top priority.