Entity versions and publishing

Current version: 9.2

Sitecore XC supports versioning of Commerce items, so that you can track changes to content through each version of the entity. With the entity versioning feature, you can make offline edits to Commerce items, and only publish them to your storefront site when you are satisfied with the changes. You also have a history of all the changes made to the Commerce item, so you can see which entity version a particular change was made in.

Similar to Sitecore content items, you cannot change a Commerce entity if it has been published. If you want to change any of the information associated with the Commerce entity, you create a new version of the entity and make your changes there. When you finished making changes, you can then add it to the publishing workflow.

The Details page of a Commerce item that has versioning enabled contains an Entity Versions section that displays all of the existing versions for the Commerce item. The value of the Published field shows which versions have been published to the Storefront, and which versions have not.


You must be assigned to the Merchandiser role to access this functionality.

Entity Versions section

Adding entities to the publishing workflow

When you have finished making changes to a new entity version, you can place the entity in a publishing workflow.

The default publishing workflow has the following states:

Publishing workflow

When you place an entity version in a publishing workflow, it is automatically placed in a Draft state. After you submit it for approval, it is placed in the Awaiting Approval state, where the changes can be accepted or rejected. When the entity version is approved, the updated Commerce entity is published to the Content Delivery server.

You can modify the default publishing workflow definition or create your own custom workflows using the Workflow plugin.

Do you have some feedback for us?

If you have suggestions for improving this article,