Legacy Knowledge Base
Published Jul. 2, 2025

How to upgrade Commerce

Written By

Viktória Gyömbér

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • Is it possible to upgrade Commerce version, and if so, how would this be done?

Environment

  • Liferay DXP 7.1+
  • Liferay Commerce

Resolution:

Follow these points below for Commerce upgrade:

  1. Shut down Liferay.
  2. Delete the osgi/state folder in Liferay Home.
  3. Delete Liferay Commerce - API.lpkg and Liferay Commerce - Impl.lpkg from osgi/marketplace.
  4. Place the new .lpkg in the Deploy folder.
  5. Start Liferay. When prompted by the log, shut down and restart again.

Once you’ve completed these steps, it’s a best practice to initiate a full reindex by going to Control Panel → Configuration → Search and reindex all search indexes.

If you remove the Commerce package it won't remove the data from your database, therefore your state should be the same after deploying the new Commerce version.

Additional Information

The following article also helpful for this topic:
Commerce 2.0.0 Release Highlights

And also please check the Compatibility Matrix in order to know which Commerce version compatible with your current DXP version.

Did this article resolve your issue ?

Legacy Knowledge Base