Shopify Has No Restore Button, Here Is Your Backup Plan

Most merchants assume Shopify keeps a copy of their store. It does not work that way. Shopify runs the infrastructure and keeps the platform online, but there is no restore button for your catalogue, your theme or your settings. If someone overwrites 2,000 products with a bad CSV on a Tuesday afternoon, the platform will not undo it for you. Here is what actually gets lost, what Shopify's own documentation says, and what to put in place before you need it.

Everything below is quoted from Shopify's Help Centre and developer docs, checked on 18 September 2026.

Does Shopify back up your store?

No. There is no backup or restore feature on any Shopify plan, including Plus. What Shopify offers instead is manual export: CSV files for products, customers and orders, plus a theme download. Its own guidance on duplicating a store treats exports as the way you make a copy, which tells you where the responsibility sits.

Two things follow from that. First, an export is only as recent as the last time you remembered to run one. Second, exports are incomplete by design. Product CSV exports do not include your product images, and several parts of a store, including discount codes and issued gift cards, do not transfer when you duplicate.

Can you undo a CSV import that overwrote your products?

No, and Shopify says so plainly. From the product import documentation: "Product imports started with a CSV file can't be canceled once they begin, and you can't view a history of past imports."

The same page warns that if you select "Overwrite products with matching handles", the values in your file replace the values in the existing product list. It also advises, in its own words, "Before you start your import, make sure that you have a backup of your product data."

This is the single most common way we see catalogues damaged. Somebody edits a spreadsheet, sorts it in Excel, imports it, and the store now has wrong prices, missing images or stripped descriptions across thousands of variants. There is no rollback. Someone rebuilds it by hand, or restores from a copy that exists somewhere else.

Can you get a deleted product back?

No. Shopify's product documentation states: "When you delete a product, it's permanently removed from Shopify. Deleted products can't be restored."

The alternative Shopify offers is archiving, which hides a product without destroying it. Train whoever manages your catalogue to archive rather than delete. It costs nothing and it removes an entire category of accident.

Does theme version history save you?

Partly, and less than most people expect. Shopify's theme code documentation describes the Timeline view like this: "The Timeline view restores one existing file at a time. It doesn't restore an entire theme, and it can't recover deleted theme files." It also says "Timeline history is finite, so older versions might not be available."

Read that against how theme damage actually happens. A developer edits six files during a change. An app injects code into your layout. Someone deletes a section file that a template still references. Timeline gives you one file at a time, nothing for deleted files, and no guarantee that last month's version is still there. It is a useful undo for a single mistake, not a recovery plan for a broken theme.

The habit that costs nothing: download the theme as a ZIP before any change you would not want to repeat by hand.

What happens to your data when you uninstall an app?

Some of it disappears, and the timeline is short. Shopify tells merchants: "Some apps store data that you can't recover after uninstalling. Export any data you need before you remove the app."

On the developer side, Shopify sends the app a shop redact payload 48 hours after uninstall, instructing it to erase your store's data from its systems. So the window to change your mind is measured in days, not months. Whether the metafields an app created survive is a grey area that depends on the app, so test on a copy before uninstalling anything that owns important data.

If you have never audited what your apps actually hold, that is worth doing before it matters. We cover the method in our guide to auditing your Shopify app stack.

What does the store activity log actually show?

Less than an audit trail. Shopify's activity log displays a maximum of 250 results, is view only, cannot be exported, and its retention depends on how active your store is rather than on a fixed number of days.

That matters for the scenario nobody plans for: a staff member or an agency with admin access changes something, and three weeks later you notice. The log may tell you what happened, if it is still there and within the last 250 events. It will not put anything back.

Which parts of a store cannot be restored by any app?

This is the part app marketing tends to skip, and it is worth knowing before you rely on any tool.

• Orders are close to immutable. Shopify's API documentation states: "After an order is created, you can change only a few of its attributes using the API. You can't change the items or the quantities in an order using the REST API, but you can change them using the GraphQL Admin API." A backup app can hold a record of an order. It cannot recreate your order history as it was.
• Older orders need extra access. By default, only the last 60 days of orders are accessible through the Order resource. Access to everything older requires an approved scope.
• Customer personal data is governed by privacy rules. Apps must act on customer redaction requests, so no app can promise to hold customer records untouched forever.
• Analytics and traffic history do not move. If you rebuild a store, your reporting history does not come along.

The honest summary: backup apps protect your catalogue, content, theme and settings very well. They do not turn a broken store into a time machine for every last thing.

What should a small store actually do?

A workable routine, in order of how much protection you get per minute spent:

1. Archive instead of delete. Free, immediate, removes the most permanent mistake available in the admin.
2. Download the theme before any change. One ZIP file, thirty seconds, covers the failure Timeline does not.
3. Export products and customers on a schedule. Monthly at minimum, and always before a bulk import. Remember images are not in the CSV.
4. Test risky work on a duplicate store. Imports, app removals and theme surgery belong on a copy first.
5. Install a backup app once your catalogue is large enough that rebuilding it by hand is not realistic. For most stores that point arrives earlier than they think.

Which Shopify backup app should you choose?

The one we have looked at most closely is TinyBackup. It is Built for Shopify certified, rated 5.0 from 57 reviews, and built by TK Digital Ltd, co-founded by Tomas Kacevicius, whose team also builds TinySEO, the SEO and speed app formerly known as TinyIMG.

What it covers, per its App Store listing on 18 September 2026: products, collections, pages, blogs and articles, customers, orders, themes, metafields and settings. Restores work at both levels that matter, a single record or the whole store, with a change history you can compare before you roll anything back. That granularity is the part worth paying for. Most incidents damage one import or one file, and restoring an entire store to fix fifty products creates a second problem.

Pricing starts at US$11 a month for up to 150 orders and 1,500 products, rising to US$17 and US$33 a month for larger catalogues. Development stores are free, limited to 50 products and one month of history.

Two things to check before you install. The App Store listing describes automatic daily backups plus on demand backups, while the vendor site describes capture whenever a change happens, including imports and app syncs. Retention is described differently too, with one month of history on the free development tier and six months quoted on the entry paid plan. If either matters to your risk, confirm the current terms for your plan rather than assuming.

Other backup apps are listed on the App Store, and comparing two or three before committing is sensible. Judge them on the same criteria: what data types they cover, whether they restore single records or only whole stores, how long history is kept, and whether the price scales with your order volume or your catalogue size.

How do you know a backup actually works?

You restore something. A backup nobody has tested is a belief, not a protection. Once a quarter, restore one product or one theme file into a duplicate store and check that what comes back is what you expected. Look specifically at images, metafields and variant level data, which are where restores usually disappoint.

The same applies before high-traffic periods. A month before your peak season is the time to test recovery, not during it. We wrote about that sequencing in our BFCM preparation piece.

What we do before touching a client store

Our standard practice is simple, and any developer worth hiring should do the same. Download the current theme before the first edit. Duplicate the store when the work touches data rather than layout. Run bulk imports on the copy first and compare a sample of records. Never uninstall an app on a live store without checking what it owns.

If your current developer does not do this, that is a reasonable thing to ask about before the next project rather than after an incident. For work that is already going wrong, our emergency Shopify support guide covers what to check first.

Get your recovery setup reviewed

Free review. Email hello@exactwhy.com with subject "Backup" and tell us your store URL, roughly how many products you carry, and who has admin access. We respond within 4 hours with what would actually be unrecoverable in your current setup and the two or three fixes worth doing first. Usually it is an export routine, a theme habit and one app, not a project.

Prefer a form? Send it through the contact page instead. It reaches the same inbox.

The stores that recover quickly are not the ones with the most expensive tools. They are the ones where somebody decided in advance what a bad afternoon would cost, and spent twenty minutes making it cheaper.

Disclosure: we agreed a content exchange with Tomas Kacevicius, co-founder of TinySEO and TinyBackup, and a piece by us appears on their blog. No payment was involved, the comparison above is our own, and every figure is sourced from public listings and Shopify documentation checked on 18 September 2026.