How to back up a Shopify store before a bulk edit

The five minutes before, and why they are worth more than the hour after

You are about to change prices across a vendor, retag a season, run a CSV import from a supplier feed, or let an app rewrite inventory. The edit itself takes a minute. What decides how the day ends is whether the state before it exists anywhere with a timestamp on it.

Everything below is free and takes about five minutes. The paid part comes last, and it is the smallest part of the page.

1. Export exactly the selection you are about to touch

In Products, filter down to the rows the edit will hit, select them, and export the selection rather than the whole catalogue. A narrow file is the one you can actually read at 6pm, and re-importing it puts back only what you touched. Inventory has its own CSV export, and it is a separate file - the products export does not carry quantities.

Know what the file will not carry before you rely on it: collection membership is never in a products export, image files are referenced by URL rather than contained, and app-created metafields are not there. The itemised version of that list is on what a CSV export leaves out.

2. Write down the minute you start, in UTC

This is the cheapest line in this page and the one people skip. Any point-in-time restore, from any tool, needs the moment before the first write - not the date, the minute. A date with no time means the end of that day, which is after the mistake rather than before it, and the hours are read in UTC rather than in your own timezone.

If an app or a scheduled job is doing the writing, note when you started it and pause anything else that writes to the same records. Two writers make the timeline unreadable afterwards.

3. Duplicate the one thing you are experimenting on

For a single product, Duplicate costs one click and gives you the original untouched. For a theme, duplicate before editing and keep a downloaded .zip of whatever is currently live - theme backups are their own short page. This does not scale to a catalogue, which is the whole reason the first two steps exist.

What the admin will not give you afterwards

Unsaved bulk changes are discarded if you navigate away - that is the only undo in the room. Once saved, the admin has no button that puts the previous values back, no per-product history to open, and no record of what the values were. A CSV import behaves the same way: it matches rows by handle and overwrites what the file describes.

Shopify says as much itself. Its own guidance on backups is to export CSV files from the admin and keep them, which is a fair description of where the platform stops - see does Shopify back up your store for the full answer. Checked against Shopify's documentation on 23 August 2026.

What a versioned backup adds to those five minutes

It removes the remembering. The state before the edit is captured whether or not anyone thought to export, per record and dated, and the question afterwards becomes "what did this product look like at 14:05" rather than "did someone save a file".

In StoreVault a restore to a moment in time produces a plan first: it lists what would change, what already matches, and what is missing and would be recreated. Nothing is written until you apply it, and an applied restore can itself be undone, because the app keeps what it overwrote. The reasoning behind that shape is on why a restore needs a plan first, and an undo after.

The honest limits

Restores put back fields, not files: the image list is in the backup, the media is not re-attached. Orders and customers are archive and export rather than a rewrite. Data that lives inside another app belongs to that app. And a backup app only knows the store from the day it was installed - the complete boundary is on what backup apps can and cannot restore.

If the edit has already happened, this is the wrong page - go to undoing a bulk edit. If you are choosing a tool for this rather than fixing something today, the comparison with the best-known one is on the Rewind alternative page, and the same preparation applied to a bigger change is on backing up before a migration.

The five free minutes above work. They just depend on someone remembering them on the one afternoon nobody does. A backup app covers you from the day it is installed rather than the day you need it, which is why the day to install one is a quiet one.

StoreVault on the Shopify App Store - versioned backups of products, collections, content, inventory and themes, with a plan shown before any restore writes.