Every change remembered. Most of them reversible.
The question after a bad import isn't philosophical — it's 'what did it change, and can we undo it?' InventaCloud logs price, inventory, and discontinuation changes with their previous values, keeps the history of what each import did, and records workspace activity in an audit log. When an update was wrong, rollback restores the earlier value instead of restoring from memory.
How history protects you
- Changes land with context Every price, stock, and status change records its previous value, its new value, and where it came from — file, feed, or override.
- History answers questions 'What happened to this SKU?' becomes a lookup — per product, per change type, in order.
- Rollback undoes mistakes Restore a previous value or unwind what a bad update file did — recovery is a click, not a reconstruction project.
- Activity stays auditable Catalog publishes, rule changes, reseller approvals, and team-permission updates are recorded in the workspace activity log.
Why teams use it
The wrong price file is an incident only if you can't reverse it. With logged previous values, you can.
When a partner asks why a price moved, the answer is on the record — value, date, and source — not in someone's inbox.
Teams automate feeds more aggressively when every automated change is logged and reversible.
The activity log records who did what across the workspace — publishes, approvals, permission changes — with no extra effort.
What's tracked
Good to know
Changes are logged at the product-record level where your operational data lives — prices by role, stock with restock info, status with dates — so rollback restores exactly the field that moved.
Replacing a catalog source file is only accepted when its columns cover everything previously mapped — a vendor silently dropping a column can't quietly hollow out your history's future.
Works together with
Common questions
What kinds of changes can I roll back?
Price, inventory, and discontinuation changes carry their previous values and can be restored — individually or by unwinding what a bad update file changed.
Can I see what a specific import did?
Yes — imports keep their history, and the changes they caused are attributed to them in the log, so 'what did Tuesday's file touch?' has a concrete answer.
Who can see the activity log?
Workspace roles govern access — the audit trail is there for the people who administer the workspace, recorded automatically as the team works.
Build one catalog that works everywhere.
Start a 14-day free trial and see it working on your own catalog — onboarding call included.