The History tab tracks every modification made across Akeneo PIM entities and records. Use it to audit changes, verify when updates occurred, and identify which user or automated process performed the update.

History tracking is available for:

• Catalog Data & Values: Product, Product Model, Assets, and Reference Entity records
• Catalog Structure & Configuration: Channels, Categories, Families, Attributes, Attribute Groups, Association Types, Groups, Job Profiles, Reference Entity structures, Roles, and Automation Rules

For example, if a Product description changes unexpectedly after an import, you can compare the previous and new values and identify the source of the update.

Access History tabs

1. Open the Product, Product Model, or configuration entity you want to review.
2. Open the History tab.
3. Select a version to expand its details.

Read a History entry

Versions are listed from newest to oldest. Each entry can include:

• Version: the sequence number of the recorded change.
• Author: the user or process that made the change.
• Date and time: when the change was recorded.
• Modified fields: the Product values or entity properties that changed.
• Old value and new value: the value before and after the change.

For localizable or channel-specific Product values, the entry identifies the relevant Locale and Channel so you can review the correct context.

Identify the change source

History records the origin of a change as its author. Depending on how the update was made, the author can be:

• a user who saved a change in the PIM interface;
• an import job;
• an API import endpoint;
• an AI configuration;
• Ziggy acting for the user who requested the AI action.

The Author entry can also include the source context, such as John Doe (ui). 

When an automation Rule makes the change, its execution type and label appear next to the author, helping you identify which rule produced the update. 

When Ziggy made the change, a sparkle icon appears next to the requesting user. Hover over the icon to confirm that Ziggy made the change.

Review versioned resources and retention

Investigate an unexpected Product change

Scenario: A Product description changed unexpectedly, and you need to identify the source of the update.

1. Open the Product.
2. Select the History tab.
3. Locate the relevant version by its date and modified fields.
4. Expand the version to compare the old and new values.
5. Review the Author entry to determine whether the change came from a user, import job, API endpoint, AI configuration, or Ziggy action.

Review configuration changes

Scenario: A Rule or Attribute configuration changed and affected how Product data behaves.

1. Open the relevant configuration entity, for example, Settings > Rules.
2. Select the History tab.
3. Expand a version to identify the modified fields.
4. Compare the old and new values to understand which conditions, actions, or parameters changed.

Restore a previous version

Scenario: Incorrect values were saved on a Product or Asset, and you need to recover an earlier state.

1. Open History and locate the version containing the correct values.
2. Review its changed fields, old values, new values, and context.
3. Click Restore when the action is available.

Restoring does not remove the audit trail or delete later versions. It creates a new version containing the values from the selected version.