Most people assume that because Shopify is a big, reliable platform, their store is automatically backed up somewhere safe. It’s a fair assumption — Shopify is big and reliable. But the backup you’re probably picturing, the one where you ring support and say “can you put it back to how it was on Tuesday,” doesn’t exist. Here’s how it actually works, and what we’d suggest you do about it. No alarm bells.

What does Shopify actually back up?

Shopify backs up its platform — not your individual store. The servers, the infrastructure, the software that keeps hundreds of thousands of stores running. If one of their data centres had a serious problem, those backups are what bring everyone back online. That part is genuinely well looked after, and it’s one of the reasons Shopify is a sound platform to build on.

This is usually called the shared responsibility model, which is a tidy way of saying: Shopify looks after the platform, and you look after what’s inside your account. Shopify handles uptime, security and disaster recovery for the system as a whole. You’re responsible for your own products, pages, theme tweaks, customer records and app settings — the things that make your store yours.

The reason Shopify can’t simply restore your store is partly technical. Their platform backup holds the data of every merchant at once, and it isn’t built so someone can reach in, find your store on a particular date and lift it back out without touching anyone else’s. So while the backup exists, it was never designed to undo a change you made.

How do stores actually lose data?

Rarely the dramatic way. The hacker-and-server-meltdown version is far less common than the everyday causes — which is exactly why those catch people out:

• Someone with admin access deletes a product, collection or page by accident, and doesn’t notice for a fortnight.
• A third-party app makes a bulk change you didn’t expect — overwriting pricing, stripping metafields, or reorganising collections during a sync.
• A CSV import goes in with an error and quietly overwrites hundreds of correct records with wrong ones.

In more than ten years on the platform we’ve seen versions of all of these. The common thread is that none of them feels like a “disaster” at the time — they’re small, ordinary actions, and that’s precisely the kind of thing Shopify’s platform backup was never meant to reverse.

Can’t I just export a CSV?

You can, and it’s better than nothing. Shopify lets you export products, customers and orders to CSV files from the admin, and you can download a copy of your theme too. For a small store on a tight budget, doing this regularly is a reasonable starting point.

The catch is that it’s piecemeal. A CSV export captures the data Shopify chooses to put in it — and that’s not everything. Product images, theme customisations, app configurations and the relationships between bits of data don’t all come along for the ride. So when you actually need to rebuild, you find you’ve got a spreadsheet of product titles but not a store. It’s a backup of some of your store, dressed up as a backup of all of it. It’s also manual, which means it relies on someone remembering every week — and that’s the part that quietly falls over.

Which backup tools would we point you to?

For most stores doing real volume, a proper account-level backup app is the sensible answer. Two we rate:

Rewind is the closest thing to the backup people think they already have. It takes automatic daily backups of your store data and lets you restore specific items — a single deleted product, or a wider rollback — without rebuilding from scratch. If you want “put it back to how it was on Tuesday” to be a real option, this is how you get it.

Matrixify comes at it from a different angle. It’s built for bulk import and export, handling large datasets across products, collections, customers, orders, pages, blogs, metafields and more. You can schedule exports to run automatically — including straight to your own FTP/SFTP server — so it doubles as a scheduled backup as well as a data-management tool. For larger or more complex stores, it earns its place.

Neither is the “right” answer for everyone. Rewind leans towards effortless restore; Matrixify towards control and scale. Plenty of merchants we work with use one or the other depending on how their store is set up and how often things change.

One thing to know: even a backup app doesn’t cover everything

It’s worth being clear-eyed here, because “we’ve got Rewind” can give a false sense that everything is covered. It isn’t quite. Rewind backs up the main store data — products, product images, customers, collections, blogs, pages and themes — and that’s the bulk of what most stores worry about.

The one we’d flag to clients is inventory. Stock quantities aren’t backed up (Shopify’s API doesn’t allow it), along with a few related product fields like weight and cost per item. So after restoring a product, you’d want to check stock levels and re-enter them where needed. Draft orders aren’t covered either.

A second group of things are backed up but can’t be restored at the click of a button — menu navigation, orders, shipping zones, locations, store policies and Shopify Translate & Adapt product translations among them. Rewind saves this data and will work with you to recreate it, but it’s a supported job rather than a one-click rollback. Metafields and metaobjects are covered too, on the right plan, with a few restore limitations around things like Companies and Files.

None of this is a reason to skip a backup — a backup that covers most of your store is vastly better than none. It’s just worth knowing where the edges are, so inventory in particular gets a manual check after any restore rather than being assumed safe.

So what would we suggest?

If you take one thing from this: don’t assume the backup exists. Most stores we look at don’t have a real one in place, and the owners are usually surprised to hear it.

A workable approach for most businesses looks like this — automated daily backups through an app, a copy of your data held somewhere outside Shopify, and a quick check that you could actually restore from it (a backup you’ve never tested isn’t really a backup). It’s not a big project. It’s an afternoon of setup you’ll be very glad of the one time you need it.