CaryvaneHelp
/
EN

Shopify backup

Shopify hosts a store and keeps its own platform running; it does not back up a merchant's data for the merchant, and says so. Products deleted, a bad bulk edit, an app that overwrites prices, a theme edit that breaks the storefront: none of it can be undone from Shopify's side. Caryvane backs up every Shopify store a customer runs — products, collections, customers, orders, content, navigation, themes, files and more — into the customer's own storage, keeping every version so the store can be seen as it stood on any date.

Shopify's own position

Shopify is responsible for the platform. The merchant is responsible for backing up their data. There is no store-level backup or restore on any Shopify plan, Plus included.

1. Create the app in Shopify (the merchant does this once per store) #

Since January 2026 a custom app is created in Shopify's Dev Dashboard, not in the store admin. The store owner needs ten minutes and the Shopify account that owns the store.

  1. Go to dev.shopify.com/dashboard and sign in with the account that owns the store. The store should appear under the organisation; if it does not, link it from the dashboard's Stores page.
  2. Create app → name it Caryvane Backup.
  3. Under Access scopes, tick the read scopes below. Add the write scopes too if you want restore from Caryvane: write_products, write_content, write_online_store_navigation, write_metaobjects, write_files, write_inventory so a restored product gets its stock back, and write_publications and write_translations (with read_publications and read_translations) so it goes back on its sales channels in its languages. Nothing else lets the app change the store.
  4. Release a version, then Install the app on the store from the dashboard.
  5. Open the app's Settings → Client credentials and copy the Client ID and Client secret. Send them to whoever manages Caryvane by a safe route (a password manager share, not email).

Scopes to tick: read_products, read_customers, read_orders, read_draft_orders, read_discounts, read_content, read_online_store_navigation, read_themes, read_files, read_metaobjects, read_metaobject_definitions, read_inventory, read_locations, read_shipping, read_markets, read_legal_policies. On Shopify Plus also read_gift_cards and read_companies.

Orders older than 60 days need one more step. With read_orders alone Shopify hands an app only the last 60 days of orders, and the scope that lifts that, read_all_orders, cannot be ticked: the scopes field refuses it. It is a protected scope you request from the app's settings in the Dev Dashboard (the access-request section; say the app backs up the store's own order history). Shopify approves it per app, usually within a few days; then release a new version and reinstall. Until it is approved the store card in Caryvane says Orders: last 60 days only, and Verify will show fewer orders than the store counts. Nothing already backed up is lost in the meantime.

Theme files are gated the same way. read_themes can be ticked, but Shopify still refuses an app the contents of theme files until it has approved theme access for that app, requested from the same place. Until then the run notes not available to this app — Themes and carries on with everything else; theme files join the backup from the first run after approval.

One app covers one store (or the stores of one Shopify Plus organisation). A merchant with three separate stores creates three apps.

1b. The one-click way: install the Caryvane Backup app #

Nobody creates a custom app at all: install Caryvane Backup from the Shopify App Store (the console's Install from the Shopify App Store button opens the listing). Shopify asks the store owner to approve the app, then sends them to Caryvane to sign in and link the store to the right customer. Caryvane sends them on to Shopify's plan page and they come back; the store is then ready for a storage choice. Stores connected this way are billed by Shopify on the plan chosen, not on the Caryvane invoice, and back up while that plan is active. They need no paid Caryvane subscription and use no cloud credits. While the store is on a plan, including the plan's free trial on Shopify, the Caryvane account stays open without asking for card details, and once Shopify starts charging for the plan the account is active. Agents on the customer's own machines still need a Caryvane subscription. If the app is uninstalled from the store, backups stop and the copies already taken stay in the customer's storage.

Stores already connected with their own custom app keep working, on Caryvane's invoice.

2. Connect the store in Caryvane #

The destination must be object storage that encrypts at rest by default — Amazon S3, Wasabi, Backblaze B2, Azure Blob, DigitalOcean Spaces, Cloudflare R2, Linode or Vultr. A store's records include customer names, addresses and orders, and Shopify asks that they are held encrypted; those stores do it without being asked, an SFTP server, network share or local folder may not, so the console refuses them for Shopify. Other S3 storage (OVH, Scaleway, MinIO and so on) is accepted when its bucket has default encryption switched on: Caryvane asks the bucket when you save, and if it does not, the message says how to switch it on.

  1. Connectors → choose the customer → in the Shopify card, Connect a store.
  2. Enter the store's permanent address (something.myshopify.com, shown under Settings → Domains in the Shopify admin), the Client ID and the Client secret. Caryvane tests them against Shopify straight away and shows the store's name and plan.
  3. On the store's row, Choose storage: a cloud storage target of the customer's (S3, Wasabi, Azure and so on — not an SMB share or local folder, as the backup runs in the cloud), a folder, and how long to keep history (seven years by default). The first backup starts at once.

Each store gets its own folder, named after it, inside the folder you chose. Nothing is installed at the customer. The client secret is stored encrypted and never leaves Caryvane's server; the backup workers only ever receive a 24-hour access token.

The row shows any recommended scope the app was not given, so you know what is not being backed up. To add a scope later: tick it in the Dev Dashboard, release a new version, reinstall, then Reconnect in Caryvane with the same credentials.

3. What is captured #

The first backup captures everything through Shopify's bulk operations, which run on Shopify's side and do not count against the store's API limits; a large catalogue takes an hour or two. Afterwards each nightly run asks only for what changed. A record edited twice between runs keeps the later state; an unchanged record is never written again.

Every version of every record is kept as its own file for the retention period. A record deleted in Shopify is marked as gone, never removed: that is the point of the backup.

4. Browsing the store as at any date #

Connectors → Shopify → Browse opens the store's backup: record types down the side with counts, the records of the chosen type in the middle, the chosen record on the right with its history. As at in the header shows everything as it stood at the end of a chosen day — the end of last month, the end of last year, or any date — so "what did this product look like before the bulk edit" is a date and a click.

Every record opens as a readable layout built from Shopify's own data; Download JSON gives the raw record, and a theme file or image downloads as itself.

5. Getting data back #

What you needHow
A product, collection, page, blog post, menu, redirect, metaobject or file deleted or damagedOpen it in Browse as at a date before the problem and click Restore to Shopify. If the record still exists you choose: set it back to this version, or create a copy (a new record with a -restored handle, the live one untouched). A deleted record is re-created, a product with its variants, options, metafields, images and the stock it had then, at every location that is still active. A product set back in place keeps its current stock, because stock has moved with every sale since; tick Also restore stock levels when you want the old figures back, for example after a bad bulk edit. Cost, tariff code, country of origin and category always come back with the product. A re-created product also goes back on the sales channels it was on, into the manual collections that listed it (smart collections pick it up by their rules), with its translations and its fixed market prices on the price lists that still exist. A copy gets its prices but stays off channels and collections until you choose, so customers don't see it twice. Anything Shopify refuses on the way is listed in the restore's result; the product itself is never undone. The app on the store needs the matching write scope (write_products, write_content, write_online_store_navigation, write_metaobjects, write_files, plus write_inventory, write_publications and write_translations for stock, channels and languages); without it the restore is refused and says which scope to add. The assistant tool is restore_shopify_record.
Many products or customers at onceExport → Shopify import CSV (as at a date before the problem) gives products_export.csv and customers_export.csv in Shopify's own import formats. In the Shopify admin: Products → Import, Customers → Import.
A theme as it wasOpen the theme in Browse, as at the date; download the files you need (or the whole backup as JSON, which includes every theme file) and upload them in the theme code editor, or add the theme as a new unpublished theme and publish once checked.
DiscountsOpen the discount as at the date and recreate it from the readable view; Shopify's API does not take a discount back as it was.
Orders, customer history, gift card balances, payoutsCannot go back into Shopify by any means — an order cannot be re-created as a historical order. The backup keeps them as a complete, dated record for accounting, disputes and audits; export as JSON.
The whole store as at a dateExport → Everything as JSON: every record and every file, one ZIP, with a README.

Never say "restore your store". Shopify does not allow any application to turn a store back to last Tuesday; what every backup product sells is export-and-reimport for the things Shopify imports, and evidence for the rest.

6. Checking the backup is complete #

Browse → Verify (and the verify_shopify_backup assistant tool) compares the backup's counts of products, collections, customers and orders with the store's live counts. Fewer orders than Shopify counts almost always means the app does not yet have read_all_orders (see the app steps).

7. What it costs #

A store installed from the Shopify App Store is billed by Shopify, on the plan chosen in the Shopify admin. Manage plan in the Shopify card opens that page. Disconnecting a store in Caryvane stops its backups, but Shopify keeps charging until the app is uninstalled in Shopify.

A store connected with its own custom app is billed per month from the day its backup starts, while it stays connected, pro-rata by days; Shopify Plus stores at the Plus store rate. There is no charge for the amount of data. Disconnecting a store stops the fee; what was backed up stays browsable and exportable for its retention period. Ask us for the current rates.

Notes #