The question that decides whether bulk editing is safe: what happens when the rule was wrong?
You will be redirected to the Shopify app store.
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.
Try a change on five products before trusting the catalog to it.
You will be redirected to the Shopify app store.
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.


| Field | How the revert works |
|---|---|
| Price, compare-at, cost | The old value is written back |
| Inventory quantity | The change is reversed by the same amount, keeping sales made in between |
| Tags | Limited: added tags are not removed — run a remove-tags task instead |
| Title, description, SEO, handle | The previous text is written back |
| Status, vendor, type, SKU, barcode, weight, tax | The previous value is written back |
For promotions, set the revert time when you create the task. The app restores the old values at that moment, which is how a weekend sale ends on Monday at 00:00 without anyone logging in.
Task history is kept for 30 days on Basic, 45 on Standard and 90 on Plus; the free plan has no task history. A task can be reverted while it is in history.
Give a price change a start time and a revert time so it ends by itself.
Read moreWhat Shopify’s built-in editor and CSV do, and the three jobs they cannot do.
Read moreThe seven recurring failures, and the thirty-second check that prevents each.
Read more