All Collections
X-Cart Updates
Update Waves and Update Availability
Update Waves and Update Availability

Learn what are the update waves and how to use them for best.

Olga Tereshina avatar
Written by Olga Tereshina
Updated over a week ago

X-Cart releases software updates in several waves to ensure continuous secure, and seamless online store functioning. A store admin can select when to apply updates and whether to stay within the current software branch or move forward with the latest one.

Update Waves

Once a new X-Cart software version is released, updates become available to existing X-Cart users in two waves. Such a split ensures more thorough testing of the process.

The first wave is called the Developer wave. It opens at the time of the official X-Cart release announcement and targets X-Cart developers and early adopters. It allows 3rd party developers to adapt their add-ons to a new X-Cart core. It also lets the tech-savvy X-Cart users try the update and ensure it does not cause issues in their specific store environment.

The second wave is the Merchant wave. This wave usually becomes available in 2-7 days following the official release announcement and targets all X-Cart users.

The Developer wave provides access to the new X-Cart features earlier. However, updating in the Developer wave may be recommended only for users prepared to deal with issues, should they arise.

By default, all new X-Cart stores are configured to get updates in the Merchant wave. If you need access to new X-Cart releases in the Developer wave, switch the "Upgrade access level" setting to Developer in the Upgrade Options section of the Environment page in your store’s Admin area (System tools > Environment).

Availability of Updates for Different Versions

A major update involving a change of the second sequence in the version number can apply only to the latest version of a branch. In other words, if the 5.0.x branch consists of the versions 5.0.10, 5.0.11, 5.0.12, 5.0.13, 5.0.14, then 5.0.14 is the only version number you can update to the next 5.1.x branch.

The updates involving the change of the third sequence in a version number are not that rigid, which means you can update a 5.0.10 store to 5.0.14 in one run.

A store update from 5.0.10 to 5.1.0 implies a two-step procedure: first, an update from 5.0.10 to 5.0.14, and then - from 5.0.14 to 5.1.0.

Related pages:

Did this answer your question?