Selecting an entire catalog when you meant one collection is the single easiest mistake to make in any bulk editor, because the two controls sit next to each other and the confirmation looks the same either way.
First ten minutes
- Stop any scheduled job that is still queued, before it processes more variants.
- Do not run a second bulk edit to fix the first. Two wrong edits are harder to unpick than one.
- Find your source of truth for the original prices: a snapshot, a CSV export, or an untouched staging catalog.
- Only then decide the fix.
If you have no snapshot
Shopify does not keep price history you can restore from. Your remaining options are a CSV export taken before the edit, your own supplier or cost sheet, or reconstructing from past orders — which only covers variants that actually sold.
Reconstructing without a snapshot
- Export the current catalog to CSV first, so you have a record of the damaged state before you change it again.
- Past orders give you real prices, but only for variants that sold. Expect gaps.
- Compare-at prices are usually the worst hit, because fewer merchants track them and they are rarely in old orders.
- Fix in batches and check a sample after each batch rather than trusting one large write.
Scoping so it cannot happen again
- Prefer collection or tag targeting over whole-catalog selection, even when the collection is most of the catalog.
- Read the variant count before confirming. "Entire store — 185 variants" and "Fall — 39 variants" are the same click away from each other.
- Preview the resulting price for every variant in scope before anything is written.
- Snapshot first, always, and keep the file where you can find it under pressure.
SaleGuard shows the variant count as you narrow the scope, previews every resulting price before it writes, and snapshots the originals into a CSV you keep — so a mis-scoped edit is one rollback rather than a reconstruction project.