Undo a bulk edit on Shopify

Shopify’s CSV route has no undo. Once the import is processed, the previous values exist only in the file you exported beforehand — assuming you exported one, and assuming you can work out which rows changed.

Every task in Bulk Product Edit by MITS records the previous value of every field it writes, which turns “undo” into a button rather than a restore project.

Three ways back

• Manual revert — open the finished task and revert it; the stored previous values are written back.
• Scheduled revert — set a revert time when you create the task, and it rolls back on its own.
• Selective correction — build a new task with a narrower filter to fix only the part that was wrong.
• Reverting is itself tracked, so the history shows both the change and the rollback.

What the log tells you

• Product and variant — exactly which items were touched.
• Property — which field changed.
• Old data and new data — the values before and after.
• Status — done, failed, skipped, reverted, revert failed.
• Service message — why an item was skipped, when it was.
• History is kept for 30 days on Basic, 45 on Standard and 90 on Plus; the Free plan keeps none.

A worked example: a discount that hit the wrong collection

1. Open the task in the task list and read the log — the product column shows what was actually matched.
2. Revert the task. Prices return to the values stored when it ran.
3. Fix the filter, preview the selection, and confirm the count matches your expectation this time.
4. Run the corrected task.

Why some items are skipped

If a product changed after the task ran — by another app, another task, or someone editing it by hand — a revert would overwrite the newer value. The app skips those items and lists them, rather than assuming its own snapshot is still authoritative.

That is a deliberate trade: a revert that is safe and reports what it did not touch is more useful than one that silently wins.

Related guides