Key Insights in 60 Seconds
Skim the highlights, then jump to the part of your store you are worried about.
What You'll Learn
The Quick Verdict
Key takeaway
A bulk edit takes out the wrong three hundred products. An agency overwrites a template. A product you know you had is simply not there. Find your own case in column one — everything after this table is the evidence underneath it.
Do you need a backup app, by store profile
| Your situation | Pick | Why |
|---|---|---|
| One person, a handful of catalogue edits a month | No app yet — run the CSV routine | Shopify's own instruction for backing a store up is the export you can run today, and nobody else is changing the catalogue behind you |
| Staff, a contractor or an agency with catalogue or theme access | Buy the app — both start at $19 a month for a live store, up to 300 orders | More hands means more bulk edits, and Shopify documents product and customer profile deletion as permanent — and the only thing that reverses it is a copy made before |
| Apps write to your products, inventory or orders on their own | Buy the app, then restore one thing as a test | The restore list is shorter than the backup list, and it is a different document from the one the listing shows you |
| What you would hate to lose is settings — shipping, policies, markets | Write it down yourself — and date it | Rewind's own help page says it can only back up what Shopify's API lets it see, and that Shopify holds Settings back |
| Something is already gone | Nothing here brings it back — start the copy that protects the next one | Shopify documents product and customer deletion as final, and no page we read describes a support-side recovery window |
What Shopify Actually Keeps for You
Key takeaway
The platform is not indifferent to your data — it just draws the line in a different place than merchants expect. There are real mechanisms here, and each of them brings something back. What none of them does is return your store to how it looked on Tuesday.
Most of the confusion on this topic comes from that one word. When you cross-check anything on this page, read the page titled Backups and duplication as an instruction to you rather than a description of what the platform does on your behalf.
What the platform brings back, and where each mechanism stops
| Mechanism | What it brings back | Where it stops |
|---|---|---|
| CSV export from your admin | Whatever you exported, on the day you exported it | Only runs when you run it — nothing is scheduled for you |
| Timeline in the theme code editor | One existing theme code file, at a time | Not a whole theme, not a deleted file, and the history is finite |
| Undo and redo in the theme editor | Customizations you have not saved yet | Ends at Save — after that Shopify says you can no longer undo or redo |
| Archiving a product instead of deleting it | The product, in full, whenever you want it back | A decision you have to take before the mistake, not after |
| Duplicating a theme before you edit it | The theme as it stood, if you made the copy | Copies occupy your plan's theme slots, and deleting one is permanent |
Read on Shopify's Help Center pages for backups and duplication, editing theme code, the theme editor, products and duplicating themes, August 13, 2026.
What Shopify means when it says "backup"
Key takeaway
The clearest statement of the platform's position sits on the page merchants rarely open, because its title is about duplicating a store rather than protecting one. It describes backing up as something you do, with files you generate, stored wherever you keep files.
You can export CSV files from your Shopify admin to back up your store information. You can combine these CSV files with other data, such as a copy of your theme, to create a backup or duplicate of your store. Backing up your store can protect your data and let you create test environments or duplicate stores for new ventures.
Read that as the whole architecture of this topic in four sentences. The copy is yours to make, and its contents are whatever you thought to export. Everything else on this page — the app market, the manual routine, the arguments about cost — exists because that sentence leaves a gap somebody has to fill.
Can you undo a theme code change?
Key takeaway
Partly, and the boundaries matter more than the feature. The code editor keeps a Timeline of changes to your theme files, which is genuinely useful when one edit broke one template. It is not, and does not claim to be, a way back to yesterday's theme.
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. Timeline history is finite, so older versions might not be available.
Three further limits sit alongside it, and each catches somebody out. Restoring a file replaces the whole file contents, including changes you might want to keep — Shopify's own advice is to copy the current contents somewhere safe before you restore. Asset files such as images, CSS, JavaScript and fonts in the assets folder have no Timeline history at all. And a theme file you delete cannot be recovered.
What the visual theme editor remembers
Key takeaway
The theme editor — the one where you drag sections around rather than write Liquid — has undo and redo buttons, and they cover exactly one thing: the work of the current session. Shopify's wording is that you can use them to undo or redo unsaved customizations, and that after you save your changes, you can no longer redo or undo.
This is the sharpest divide in the whole section, and it is easy to miss because both things are called the theme editor. Code files keep a per-file history after saving; visual customizations do not keep anything. If your merchandising sits in section settings rather than in code, the only version of it that survives a bad afternoon is a theme you duplicated first.
Archive instead of delete: the one built-in safety net
There is one place where Shopify offers a reversible alternative rather than a warning, and it is worth building a habit around. When a product is out of stock, seasonal, or simply not wanted on the storefront, archiving removes it from view without removing it from the store. The catch is that it is a decision taken before the mistake, by someone who is not in a hurry — which is the opposite of how bulk deletions usually happen.
What Deletion Ends for Good
Key takeaway
The reason this topic reaches merchants as a panic rather than a plan is that the first lesson usually arrives as an incident. One is worth reading in the merchant's own words: in January 2025 a store owner posted that they had deleted all 3,000 of their products by mistake, holding nothing but an activity log listing the product IDs. The reply in that thread, from a Shopify Partner rather than Shopify staff, was that there is no built-in feature to recover deleted products directly.
Treat that as a community account rather than an official statement — but the documentation, read on its own, points the same way for all three record types below.
Can you recover a deleted product?
Key takeaway
No, and Shopify says so without hedging. The same paragraph that closes the door also names the alternative, which is why the archive habit above is worth more than any recovery procedure.
When you delete a product, it's permanently removed from Shopify. Deleted products can't be restored. If you run out of stock or no longer want to display a product for any reason, but you don't want to permanently delete the product from your store, then you can archive the product instead.
Deleting a customer profile, and the cases Shopify blocks
Key takeaway
Customer records follow the same rule with one useful difference. Shopify states plainly that deleting a customer profile can't be undone, and it also publishes a list of cases where the deletion is refused outright rather than quietly allowed — among them a profile with a redaction pending because of a GDPR erasure request, a scheduled gift card recipient, a customer who has had a subscription, and one attached to an order.
That refusal list is a safety net you did not know you had, and it is worth reading before you run a bulk cleanup of customers, because it explains why some rows disappear and others do not.
One distinction inside the same page is regularly collapsed, usually by people trying to comply with a privacy request. Erasing personal data is not the same as deleting a customer profile. When personal data is erased, Shopify redacts information such as the customer's name and address, while the profile and the order history remain in your admin.
Deleted orders: what the documentation does and doesn't say
Key takeaway
Orders are the most protected of the three, in the sense that Shopify makes them hard to delete in the first place: only certain order types can be deleted at all, and only once they have been archived or cancelled. What the documentation says about the deletion itself is narrower than merchants assume — deleted orders are removed from your Shopify admin and are no longer tracked in reports.
Note what that sentence does not claim. Across the three order-management pages we read — canceling orders, order status and managing orders, all read on August 13, 2026 — no page states that a deleted order can be restored, and none states that it cannot. The closest official wording is the removal sentence above, and it is silent on recovery.
In practice the safer habit is the one Shopify's own flow pushes you towards: cancel rather than delete, because a cancelled order is still a record of what happened. If refunds and cancellations are a routine part of your week, our guide to returns and cancellations covers where each of those actions leaves the order.
Is there a grace period where Shopify support can restore it?
We looked specifically for one and did not find it. Searching the product, customer and order deletion pages along with the backups and duplication overview, on August 13, 2026, for a grace period, a recovery window or a support-side restore, none of those pages describes a period in which Shopify support can bring back a deleted product, customer or order. That is the state of the documentation we read, not a promise about what support will say — asking costs nothing, and planning as though the answer is no costs nothing either.
Is Duplicating Your Store a Backup?
Key takeaway
Duplicating is the move merchants reach for when they want a safety copy, and it is a genuinely useful operation — for staging, for a test environment, for launching a second venture from a known-good starting point. As a backup it has a specific shape of hole in it, and Shopify publishes the shape.
The six considerations Shopify lists before you transfer store information
| What does not carry over | What Shopify's page says | What it costs you in practice |
|---|---|---|
| Orders | Orders can't be imported into a store through the Shopify admin; third-party apps or the API can, and that route is not supported by Shopify | Your trading history, and every report built on it, stays behind |
| Discount codes | Discount codes can't be transferred | Live campaigns and influencer codes have to be rebuilt by hand |
| Issued gift cards | Issued gift cards can't be transferred; gift card products move through the product CSV | Balances your customers are holding — a liability, not a setting |
| Visitor traffic data you already have | You can't import your visitor traffic data because you're now tracking a new .myshopify.com domain | Your historical baseline stays on the original store |
| Saved custom reports | Your saved custom reports can't be transferred | Report definitions get rebuilt from memory, usually badly |
| Traffic tracking going forward | Visitor traffic data can't be transferred | Analytics on the copy starts at zero, whatever the original recorded |
Shopify Help Center, backups and duplication, read August 13, 2026. The middle column paraphrases or quotes the page's own six bullet points; the right column is our reading of what each one costs a working store. Two of the six bullets concern visitor traffic; we keep them as the page lists them.
What a duplicate leaves behind
Key takeaway
The first row is the one that decides the question. Shopify's wording is that "Orders can't be imported into a store through the Shopify admin, but they can be imported using third-party apps from the Shopify App Store, or through the Shopify API. This is not supported by Shopify." A copy of your store that cannot hold your orders is a copy of the shop fittings, not of the trading.
The gift card row carries a cost that is easy to underestimate, because the balances customers hold are money you owe rather than data you keep. Issued cards do not transfer, while gift card products move across through the product CSV like any other product — our guide to gift cards as a liability explains why that distinction shows up in your accounts as well as in your admin.
None of this makes duplication a bad tool. It makes it a tool for a different job: running a second storefront, or testing a rebuild before it goes live. If that is closer to what you are actually trying to do, our guide to running multiple Shopify stores is the one to read instead.
Your paid theme stays with the store you bought it for
One line on the same page catches out anyone planning to keep a duplicate as a standby: when you buy a theme from the Shopify Theme Store, that theme is licensed only to the store that you originally bought it for. A duplicate store running your paid theme is not a licensed copy of it.
What a Backup App Actually Covers
Key takeaway
Shopify's own page ends the section on backups by pointing outward: "If you want to create a backup of your store's information, then you can use an app from the Shopify App Store." That is a fair description of where the market sits — and the question worth asking is not which app is best, but what the copying stops and the manual work starts.
What the two listings say they back up, and what they cost
Key takeaway
Two listings are enough to see the shape of the market. Both price by monthly order volume rather than by catalogue size, which means your bill is set by how busy the store is, not by how much there is to protect. Entry pricing on both apps is $19 a month for a live store with up to 300 orders a month, as listed on the Rewind and BackupMaster listings on August 13, 2026.
Rewind Backups and BackupMaster Backups, side by side
| What we compared | Rewind Backups | BackupMaster Backups |
|---|---|---|
| What the listing says it backs up | Products, themes, collections, customer data and more | Products, collections, themes, files, metafields, metaobjects, customers, orders, blogs, pages, inventories, translations and more |
| Entry tier | Backup + Restore, $19/month | Essentials, $19/month |
| Order ceiling on that tier | Up to 300 orders a month | Up to 300 orders a month |
| Next tiers | Protection Suite, $99/month up to 600 orders | $39/month up to 600 orders, $79/month up to 1500 |
| Annual price | — | $205.20 / $421.20 / $853.20 a year |
| Free trial | 7 days | 7 days |
| Backup history on the entry tier | 365 days | 365 days |
Observed on the App Store listings for BackupMaster Backups and Rewind Backups, August 13, 2026, with the free-trial and backup-history rows read on August 14, 2026. Listings change; confirm both before you buy. A dash means the figure is not among what we recorded from that listing on that date — read it as our record, never as a statement that the vendor does not offer it. Neither vendor's own higher-volume pricing page was checked, so nothing here describes a store above the top tier shown.
The blind spot Rewind documents
Key takeaway
Every one of these apps reaches your store the same way a developer's script would: through Shopify's API, with the permissions Shopify grants. That single fact is what sets the outer edge of what Rewind says it can promise, and its help page explains that limit more candidly than you might expect.
In most cases it comes down to lack of permissions. Items we can't backup are items we can't see. Shopify decides what kinds of items we can "see" or access using API like products or themes, but restricts access to other things like Settings because of the sensitive information contained within. Sensitive information like credit card numbers, your passwords, staff permissions and other information like that.
Two boundaries belong with that quote. It is one vendor writing about its own product, on a help page we read on August 14, 2026. And while the mechanism it describes — API permissions — applies to any app working the same way, we are not claiming every competitor has an identical list of gaps. What it does establish is where to look: the app's own documentation, not its listing.
The same page names the categories Rewind says it cannot yet back up or restore, and the list is longer than most merchants would guess — among them store settings, product inventory, customer accounts and files from the Files manager.
Backed up is not the same as restorable
Key takeaway
This is the distinction that decides whether an app earns its fee, and it is almost never on a listing page. Being copied and being recoverable at the press of a button are two separate conditions, and the same vendor publishes a list of records that meet the first but not the second:
- Customer saved searches
- Gift card products
- Locations
- Menu navigation
- Orders
- Product translations in Shopify Translate & Adapt
- Shipping zones
- Store policies
For those, Rewind's documented answer is that it holds the data and will work with you to recreate it by hand, on request. That is a real service, and it is also manual work done with the vendor rather than a restore. So the practical instruction is: read the restore matrix of whichever app you are considering, not its backup list — and if the class of data you most fear losing appears only on the second list, price the app accordingly.
When Does a Backup App Pay for Itself?
Key takeaway
Start with the only figure anybody can quote honestly, which is the price. A store running 250 orders a month sits in the lowest tier of both apps at $19 a month, which is $228 over a year paid monthly, at the tier that covers up to 300 orders a month. BackupMaster publishes an annual price for the same tier of $205.20, ten percent below twelve monthly payments. That annual figure is BackupMaster's own: the prices we recorded from Rewind's listing are monthly, so treat the ten percent as one vendor's discount rather than a market rate.
The other half of that sum is the part we are not going to invent. The odds that your store loses data this year, and the price of an hour spent rebuilding it, are not numbers we can put a source against. So price it against something you can count: the hours your last near miss cost you, and what rebuilding the catalogue from memory would take.
If you are the only person who touches the catalogue, your products change a few times a month, and you genuinely run the export routine below, a subscription is buying reassurance rather than protection. The honest recommendation in that case is to keep the money and make the routine real — including the part everybody skips, which is restoring something once to prove the files work.
The signal that flips the answer is not how often you edit. It is how many hands and how much software can change your store without asking you: staff and contractors with catalogue access, an agency in the theme, and apps with permission to write to products, inventory or orders. Each one adds a way for the store to change while you are not looking, and each is worth reviewing at the same time — our guide to store access and permissions covers who can delete what, and how to narrow it.
Which Protection Does Your Store Actually Need?
Key takeaway
The verdict table sorts merchants by who they are. This sorts by what would actually be lost — two readers with identical stores need opposite things depending on whether their configuration or their catalogue is the irreplaceable part.
The Minimum Discipline If You Don't Buy an App
Key takeaway
This is the routine the platform's own documentation describes, assembled into an order you can work through. Steps one to three apply to every store. Step four is the one that matters most if settings are what you would miss — and Rewind's own help page puts Store Settings outside what its backups reach. Step six is done once, and it is the step that decides whether the other five were worth doing.
Step two is where this page stops and another begins. Duplicating a theme before you edit it protects the file; keeping code changes reviewable over months is a wider discipline — version control, a change log, a rule that one change means one backup — and our section on keeping a store auditable is where that belongs. What matters here is narrower: make the copy, and get it out of the admin, because copies inside your admin compete for the theme slots your plan allows and stores on Basic, Grow and Advanced can add up to 20 themes, and Shopify Plus up to 100. When you hit the limit, something has to go — and deleting a theme is a permanent action, though you can download your theme before deleting it.
The Free Backup Routine
Six steps, assembled from Shopify's own documentation. Steps one to three apply to every store; step four covers what Rewind's help page says its backups cannot see; step six is what turns a pile of files into a backup.
Shopify's own instruction for backing a store up is to export CSV files from your admin and combine them with a copy of your theme.
Before you tick this off
- Exported the CSV files your store data lives in
- Saved them outside the admin, with the date in the filename
- Put the next run in the calendar, not in a good intention
A duplicate lives in your admin and occupies one of your plan's theme slots; a downloaded copy lives with you and occupies none.
Before you tick this off
- Duplicated the live theme before touching code or settings
- Downloaded the duplicate to storage you control
- Named it after the change you were about to make
Theme copies sit inside your plan's limit, and deleting a theme is permanent — download it before you delete it.
Before you tick this off
- Counted the themes in your admin against your plan's limit
- Downloaded anything you were about to delete
- Kept the copy of the last version you know was good
Shipping zones, policies, navigation, markets and notification settings are configured by hand, and Rewind's help page splits them two ways: Store Settings among the items it cannot back up at all, and shipping zones, store policies and menu navigation among the items it backs up but restores only by hand.
Before you tick this off
- Recorded shipping zones and rates
- Recorded policies, navigation and notification settings
- Dated the document and set its next review
Shopify offers archiving as the alternative to permanently deleting a product, and an order can only be deleted once it has been archived or cancelled.
Before you tick this off
- Switched the habit from Delete to Archive on products
- Agreed that nobody deletes an order to fix a mistake
- Checked who on your team can delete at all
A copy you have never restored is an assumption; restoring one product or one theme file turns it into a backup you can rely on.
Before you tick this off
- Restored one item from your own copy, end to end
- Timed how long it took
- Wrote down what the restore did not bring back
The Bottom Line
Key takeaway
The uncomfortable part of this topic is not the price of an app. It is that the platform documents deletion as final in three places, offers one reversible alternative, and leaves the copy to you — and most stores discover that arrangement at the worst possible moment. Knowing it in advance turns a panic into a decision that costs either an afternoon of your time or, for a live store, $19 a month at the entry tier of either app, up to 300 orders monthly, as listed on August 13, 2026.
Frequently Asked Questions
Front-end developer specializing in Shopify since 2017. Experienced in building custom Liquid themes, optimizing storefront performance, and integrating third-party apps. Writes in-depth, data-driven e-commerce guides based on hands-on experience with real merchant stores.
This article was written entirely by AI under human editorial direction. The editor sets the topic and structure, runs multi-stage validation on facts, links, and interactive elements, and verifies the output is useful from a business perspective. All claims are checked against official Shopify sources. Details may change — always confirm critical data at shopify.com.
Editorial PolicyWhat to Read Next
Who Gets Into Your Shopify Admin, and With What Access
Staff seat or collaborator account, what each permission category controls, what to give an assistant, bookkeeper or agency, and what to revoke when they go.
Read articleShopify Store Code Audit: Before You Fix or Rebuild
Inherited a messy Shopify store? Audit the theme code, ghost code, ScriptTags and access yourself — then decide fix vs rebuild, and what an audit costs.
Read articleShopify Agentic Commerce: Costs & When You Need a Dev
AI agents can now buy from your Shopify store. What agentic commerce costs today, what's automatic, and when you actually need a developer.
Read article