ZenotiHelp

Manage product change logs

ZTZenoti Docs Team Updated August 28, 2026 1 min readGuide

Access, filter, and interpret product change logs to understand what changed, when, and which source made the change.

Audience: Administrators who audit and investigate product data changes.

Before you begin

Permission: Edit (under Products) — Required to view change history.

Steps

Access product change history

  1. Open the product change history from the product row — select the history icon next to a product in the inventory stock list, or in any Reports > Inventory report that lists products.
  2. Use the search filters to select the product and date range you want to review.
  3. Click Search.
  4. Review the change log results.

Read the change log

Each change log entry shows:

  • Product — The product that was modified.
  • Change date — When the change occurred.
  • Source — Which system or process made the change (for example, admin interface, import, Shopify sync, bulk API).
  • Changes — What fields were modified and the old and new values.

Filter by date range

  1. On the Product History page, enter a Start date and End date.
  2. Click Search to narrow the results to the selected period.

Filter by product

  1. Enter the product name or product code in the search field.
  2. Click Search to show change history for only that product.

Identify the source of a change

The change log attributes each modification to its source. Use this to determine whether a change was made manually through the admin interface, via an automated process such as Shopify sync, or through a bulk import.

Tips

  • When investigating unexpected product data, start by filtering the change log to the period when the change might have occurred.
  • Changes from Shopify sync or bulk import operations are clearly labeled — use this attribution to understand whether a change was intentional.
  • Change logs are useful for compliance and auditing purposes, particularly when product pricing has changed unexpectedly.
Was this article helpful?
Your feedback helps us improve our documentation.