Using MerchDash

Change history & rollback

Preview before you commit, and revert anything afterwards.

Every change MerchDash makes, from an automation run, a manual edit, or a bulk action, is recorded in Change history, grouped by the run that produced it. History spans all your enabled marketplaces, with a per-marketplace filter.

Preview before you commit

In the editor, Preview (dry-run) computes exactly which items a rule would change and why, without touching Amazon (see Preview & debug). Review-mode runs do the same: the changes wait in the queue for your approval.

Revert anything

Open any run to inspect each change, the item, the field, its before and after values, and the reason the rule attached with note(), then revert a single change or the whole run. Reverts are themselves logged as linked entries, so the trail is always complete; nothing is ever silently rewritten.

Change History grouped by run, each row showing the rule, time, trigger, status (Applied or Reverted), a change count, and Show details / Revert run actions. — Change history: every run, its status, and one-click revert.

Undoing a whole run works through it one change at a time, restoring each value on Amazon and confirming it before moving on, so a run with thousands of changes takes a while. Revert run counts up as it goes (Reverting 240/2,000…) and keeps running even if you close the tab, press it again later and it re-attaches to the revert already in progress instead of starting a second one.

How long it is kept. Run history follows your plan’s automation-history window, 14 days on Starter, 45 on Growth, 90 on Scale (see Plans & billing). A run stays fully inspectable and revertible for that whole window; after it ages out, the change itself remains in place on Amazon but can no longer be rolled back from here. Your metric archive is a separate, much longer window, 180 days to lifetime, and is unaffected.