Who changed what, when

See every saved edit and every published change across products, variants, collections, and stores. Each entry records the author, source, time, and field-level before and after.

Try for freeSee how it works

Trusted by 50+ top merchants worldwide

Catalog context

Know how every value got here

History gives teams enough context to understand a catalog change before changing it again. It separates the work your team saved from the update customers could actually see.

The current value hides the story

A price, title, or metafield can look wrong without showing what it replaced, who changed it, or whether the new value ever reached a store.

Edited and published are different facts

Several draft edits can happen before one publish. Teams need to see both the work inside Peak PIM and the final delta that actually went live.

More people and stores create more questions

Shared catalog work becomes difficult to explain when agencies, regional teams, imports, scheduled operations, and AI assistants all make changes.

Learn more
Two lenses, one timeline

See the edit and the publish separately

Move from every draft decision to the exact store update it produced, then investigate a single item or the whole account from the same activity model.

Saved

Follow every edit before it goes live

See creations, updates, deletions, links, unlinks, and reverted values with their author, source, time, and exact field-level before and after.

Published

See what each store actually received

Review the final delta published to every store, including failed publishes and their errors. Multiple draft edits collapse into the one change that shipped.

Investigate

Find the full story from one timeline

Open an item's History tab or filter account-wide Activity by store, item type, and action to understand what happened while you were away.

Built for catalog teams

Accountability without guesswork

History turns team activity into shared context. Agencies can answer client questions, operators can understand bulk work, and AI-assisted catalog changes remain as auditable as human edits.

Learn more

Read the value before and after

Every entry identifies the changed field and preserves both values, so your team can understand the decision before making another edit.

Know who or what made the change

Activity is attributed to a teammate, Peak support, a background job, or an AI assistant. AI Assistant and MCP activity stay clearly labeled and fully auditable.

Keep bulk work readable

Bulk edits, supplier imports, Harmonize fixes, and Drop apply or revert events stay grouped as operations instead of flooding the timeline with disconnected rows.

Keep context after the item is gone

Deleted products and other catalog records retain a readable timeline by name. The activity record does not disappear with its subject.

Give every catalog change a clear story

Track the edit, the publish, the person or process behind it, and the exact values before and after across every store.

Try for freeBook a demo

10-day free trial. Free setup. No credit card.

Frequently asked questions

Everything you need to know about catalog change history and activity tracking in Peak PIM.

History records catalog creations, updates, deletions, links, unlinks, reverted values, and publishing outcomes. Each entry includes the time, actor, source, affected item and store, and field-level before and after values when applicable.

Saved changes show the edits made inside Peak PIM before they go live. Published changes show the final delta that actually reached each store. If a price is edited three times before publishing, Saved changes shows all three edits while Published changes shows the one before-and-after delta sent to the store.

Each product, variant, collection, and supported catalog item has its own History tab. The account-wide Activity page combines catalog events and can be filtered by store, item type, and action.

Yes. A product timeline includes changes to its variants so the complete product story remains visible in one place.

Yes. Changes made by the Peak PIM AI Assistant or through the AI Connector (MCP) are labeled as AI activity and include the same author, source, timestamp, and before-and-after context as other catalog changes.

High-volume operations are grouped under their source, such as Bulk edit, Supplier import, Harmonize, or Drop. A Drop records both the apply event and its automatic revert, while the group keeps hundreds of related changes readable.

Its timeline remains readable by item name. Deleting the catalog record does not erase the activity that explains what happened to it.

History does not offer one-click version restore today. It preserves the before value for every recorded field change, so your team always has the context needed to recover a value manually without guessing.

Yes. Published changes are recorded per store, and a failed publish remains visible with its error instead of appearing as though the new value reached the storefront.

Still have questions?

Reach out to our team and we’ll help you find the right setup.

Talk to us