What restores, and what doesn't

This page is read from the same field lists Aislekit Backup uses to restore your items and to check every restore afterwards, so it can't promise more than the app does. Each field listed under "restored and checked" is put back and then read back from Shopify, one by one, after every restore.

Products

Restored and checked field by field

Details	Title, Vendor, Product type, Status, Tags, Theme template, Category, Gift card, Gift card template, Sold only as a subscription, Combined listing role
Content	Description
Search engine listing	URL handle, SEO, SEO title, SEO description
Prices	Price, Compare-at price, Cost per item
Variants	Options and option values, Variants, Variant order, Variant options, SKU, Barcode, Charge tax, Show unit price, Unit price measurement, Sold only as part of a bundle
Inventory settings	Sell when out of stock, Inventory settings, Track quantity, Physical product (requires shipping), Weight, Country of origin, Province of origin, HS code, HS codes by country, Locations the variant is stocked at
Images	Images and media, Variant image
Metafields	Metafield, Variant metafield
Collections	Collections
Sales channels	Sales channels, Published date, Variant sales channels

Limits

A restore can't put these back exactly. Most are Shopify's own rules, and a few are choices made to protect you or your customers; each one says why. A receipt names each one it meets.

A variant's per-channel publish date shows when the variant was last created or published: Shopify stamps it and accepts no earlier date, so a variant the restore has to create again (the product deleted, or the variant removed since) shows the restore's date. This applies to every restore.
An HS code for a country that was added after the backup stays on the variant: Shopify has no way to remove one. The codes that were backed up are put back. This applies to every restore.
Stock at a location deleted since the backup can't come back there: the product comes back stocked at its other locations. Restore the location first (it comes back under a new id), then the product, and its stock goes to the location again. This applies to every restore.

Not backed up

Shopify-hosted videos and 3D models	Their details are kept but not their files (a video can be up to 1 GB). External videos (YouTube, Vimeo) restore exactly.
Selling plans (subscriptions) and market-specific prices	Not in version 1.
Bundle components and combined listing children	Not in version 1; the product's own fields are backed up.
Shipping profile assignment	Needs a shipping permission this app does not ask for.
Damaged, safety stock and quality control counts	Only the available and on hand counts are kept, and only the available count is restored.
Orders, reviews and other apps' records that point at a deleted product	A re-created product gets a new id, and records outside the store's own references cannot be re-linked.

Collections

Restored and checked field by field

Details	Title, URL handle, Theme template
Content	Description
Search engine listing	Search engine listing, Search engine title, Search engine description
Images	Collection image, Collection image file, Collection image file name, Collection image alt text, Collection image width, Collection image height
Metafields	Metafield
Position in collections	Sort order, Products and their order, Product at a position
Collection conditions	Where the products come from, Product source, Product source name, Product source description, Rules apply to products or to single variants, Rules shared with other collections, Products must match all conditions, or any, Conditions, Condition, Hand-picked products, Hand-picked product, Exclusions, Exclusions must match all conditions, or any, Exclusion condition, Product excluded by hand, Collections this collection takes its products from
Sales channels	Sales channels, Sales channel, Published on a sales channel, Publish date on a sales channel

Not backed up

Metafields another app keeps private	Shopify does not show them to this app, and no restore ever sends a partial list that could remove them
Which app created an automated collection's rules	a restore writes the rules back itself, so Shopify records this app as their creator; the rules and their products are the same

Pages

Restored and checked field by field

Details	Title, URL handle, Theme template
Content	Content
Search engine listing	SEO title, SEO description
Metafields	Metafield
Sales channels	Visibility, Publish date

Not backed up

Another app's private metafields on a page	Shopify does not show them to other apps

Blogs

Restored and checked field by field

Details	Title, URL handle, Comment settings, Theme template, FeedBurner feed
Search engine listing	SEO title, SEO description
Metafields	Metafield

Limits

A restore can't put these back exactly. Most are Shopify's own rules, and a few are choices made to protect you or your customers; each one says why. A receipt names each one it meets.

A blog's FeedBurner feed cannot be set through Shopify's API, so it is not put back. This applies to every restore.

Not backed up

Another app's private metafields on a blog	Shopify does not show them to other apps

Blog posts

Restored and checked field by field

Details	Title, URL handle, Author, Tags, Theme template, Blog
Content	Content, Excerpt
Search engine listing	SEO title, SEO description
Images	Image alt text, Image
Metafields	Metafield
Sales channels	Visibility, Publish date

Not backed up

Article comments	they are written by customers: this app never reads them, and Shopify has no way to create one
The staff account an author name was linked to	Shopify's API shows an article's author as a name only, so the name is what comes back
Another app's private metafields on an article	Shopify does not show them to other apps

Menus

Restored and checked field by field

Details	Menu title, Menu handle
Menu links	Menu item

Not backed up

The customer account pages a menu item points at	they are Shopify's own pages; the menu item is backed up, and the page it points at must still exist for the link to work

Metafield definitions

Restored and checked field by field

Details	Where it applies, Namespace, Key, Name, Description, Type, Capabilities, Pinned, Standard definition
Position in collections	Pinned position
Collection conditions	Validation rules, Category conditions
Sales channels	Access

Limits

A restore can't put these back exactly. Most are Shopify's own rules, and a few are choices made to protect you or your customers; each one says why. A receipt names each one it meets.

Shopify can pin a metafield definition only at the end of the pinned list, so its place among other pinned definitions may change. This applies to every restore.

Not backed up

Metafield definitions for customers, orders, companies, locations, markets and other owner types	version 1 backs up the catalogue and online store content, and their definitions
Metaobject definitions and metaobject entries	not in version 1
Another app's metafield definitions	they belong to that app, which manages them itself

Metaobject definitions

Restored and checked field by field

Details	Type, Name, Description, Field used as the entry's name, Translations, Field, Standard definition
Search engine listing	SEO fields, Field used as the SEO title, Field used as the SEO description
Position in collections	Field order
Collection conditions	Field validation rules
Sales channels	Storefront and customer account access, Active and draft status, Web pages, Web page address

Not backed up

Another app's metaobject definitions	they belong to that app, which manages them itself
A metaobject field's earlier type, once it has changed	Shopify can't change the type of a metaobject field, so a field whose type changed since the backup keeps its new type and its rules.

Metaobject entries

Restored and checked field by field

Details	Type, Handle, Online store template
Content	Field
Sales channels	Active or draft

Not backed up

Entries of another app's metaobject types	they belong to that app, which manages them itself

Translations

Restored and checked field by field

Details	What the translations belong to
Content	Translated field, Title, translated, Description, translated, Excerpt, translated, Handle, translated, SEO title, translated, SEO description, translated, Product type, translated, Policy text, translated, Option, option value or menu item, translated

Not backed up

Translations set for one market only	the app doesn't have access to your markets, so it backs up the translations all your markets share
Translations of metafields and of image alt text, and of theme, checkout, notification and filter content	Shopify keeps each of those as a separate item that this version doesn't back up
Translations of another app's metaobject entries	they belong to that app, which manages them itself

Themes

Restored and checked field by field

Details	Theme name, Theme Store link
Sales channels	Current theme or library

Limits

A restore can't put these back exactly. Most are Shopify's own rules, and a few are choices made to protect you or your customers; each one says why. A receipt names each one it meets.

A restore never publishes or unpublishes a theme, so the theme your store shows stays the one you chose. This applies to every restore.
Shopify's API cannot set which Theme Store theme a theme comes from, so a deleted theme put back can show another Theme Store link. This applies when a deleted item is re-created.

Not backed up

A theme Shopify is still installing	its files are read on the next pass, once Shopify has finished
Restores of themes and theme files, for now	Shopify must approve an app before it can change theme files; until it approves this one, themes are backed up and can be compared, and a restore says it is waiting and changes nothing

Theme files

Restored and checked field by field

Details	File name
Content	Code
Images	File

Not backed up

Restores of themes and theme files, for now	Shopify must approve an app before it can change theme files; until it approves this one, themes are backed up and can be compared, and a restore says it is waiting and changes nothing
A download of a theme or of its files	Shopify's App Store rules do not allow an app to offer one, so themes are never in an export
A binary theme file (an image or a font) over 25 MB	it is named on the item instead of stored

Files

Restored and checked field by field

Details	Kind of file, File name, Alt text, Upload date, Video link
Images	File contents, File size, File type, Image width, Image height

Limits

A restore can't put these back exactly. Most are Shopify's own rules, and a few are choices made to protect you or your customers; each one says why. A receipt names each one it meets.

A restored file shows the upload date Shopify gave it, not the original one: Shopify sets that date itself and doesn't let an app change it. This applies to every restore.

Not backed up

Images and videos attached to products	they are backed up and restored with their product
The files of 3D models, and videos linked from YouTube or Vimeo, on the Files page	their details are listed in your backup, but the app can't put them back yet
Files larger than 25 MB	they are listed with their details and marked as not backed up

URL redirects

Restored and checked field by field

Details	Redirect from, Redirect to

Discounts

Restored and checked field by field

Details	Discount type, Title, Start date, End date, Tags, Discount codes, Combinations, Eligibility, One use per customer, Limit on total uses, Discount value, Applies to, Purchase type, Customer buys, Customer buys from, Minimum purchase, Shipping countries, Maximum shipping rate, Subscription payments, Uses per order, App
Metafields	Metafield

Limits

A restore can't put these back exactly. Most are Shopify's own rules, and a few are choices made to protect you or your customers; each one says why. A receipt names each one it meets.

A discount that comes back after a delete counts its uses from zero, and a customer who used it can use it again: Shopify keeps those counts with the discount that was deleted. This applies when a deleted item is re-created.
A discount for specific customers is backed up without the customers, because the app does not read customer data. Restored in place it keeps the customers it has now; brought back after a delete it is switched off, so you can add the customers and switch it on. This applies to every restore.
A discount for specific markets is backed up without the markets, because the app does not ask for access to your markets. Restored in place it keeps the markets it has now; brought back after a delete it is switched off. This applies to every restore.
A free shipping discount can only name countries in your shipping zones, so a country no longer in one is left out. This applies to every restore.
A code that another discount uses now cannot come back, because a code belongs to one discount in a store. This applies when a deleted item is re-created.
A discount another app provides is backed up so you can see it, but only that app can restore it. This applies to every restore.

Not backed up

Which customers a discount is limited to	the app does not read customer data
Which markets a discount is limited to	the app does not ask for access to your markets
Codes past the first 10,000 of one discount	a discount can hold millions of codes; the backup keeps the first ones in code order and counts the rest
How many times each discount and code was used	Shopify counts uses itself and does not let anyone set them

Policies

Restored and checked field by field

Details	Policy
Content	Policy text

Limits

A restore can't put these back exactly. Most are Shopify's own rules, and a few are choices made to protect you or your customers; each one says why. A receipt names each one it meets.

Shopify refuses changes to a privacy policy it manages automatically. Turn automatic management off in Settings, Policies, then restore it. This applies to every restore.

Not backed up

Whether Shopify manages your privacy policy automatically	the Admin API does not show that setting

Shipping profiles

Restored and checked field by field

Details	Name, General profile, Shipping origins and zones, Ships from, Zone name, Countries and regions, Shipping rates, Products in this profile

Limits

A restore can't put these back exactly. Most are Shopify's own rules, and a few are choices made to protect you or your customers; each one says why. A receipt names each one it meets.

The general profile is backed up and compared, but the app does not restore it yet: Shopify refuses changes to rates set up with its newer shipping settings, which the general profile uses. The comparison shows each zone and rate as it was, to set again in Settings, Shipping and delivery. This applies to every restore.
A zone with rates calculated by a carrier is backed up but not rewritten by a restore, so that zone stays as it is. This applies to every restore.
A zone the restore rewrites is made again, so Shopify gives it and its rates new ids; what they hold is what the backup held. This applies to every restore.

Not backed up

Which products the general profile holds	it holds every product no other profile holds, so the other profiles' lists say it
Local delivery and local pickup settings	they belong to each location, not to a shipping profile
Subscription plan groups linked to a profile	not in this version

Locations

Restored and checked field by field

Details	Location name, Active, Address, Apartment, suite, etc., City, State or province, Country, Postal code, Phone
Metafields	Metafield
Sales channels	Fulfils online orders, Local pickup, Pickup time, Pickup instructions

Limits

A restore can't put these back exactly. Most are Shopify's own rules, and a few are choices made to protect you or your customers; each one says why. A receipt names each one it meets.

A re-created location starts with no stock: stock counts belong to each product's backup, not to the location. This applies when a deleted item is re-created.
A location that holds stock, or the last active one that fulfils online orders, is left active: Shopify deactivates a location that holds stock only by moving the stock somewhere else, and a restore never moves stock or stops online orders. The receipt says which. This applies when an item is restored in place.
The last active location that fulfils online orders keeps fulfilling them, because switching it off would stop the store taking online orders. This applies when an item is restored in place.
A location that a fulfilment service app manages is backed up, but only that app can change it, so it is not restored. This applies to every restore.

Not backed up

Stock counts at a location	Each product's backup holds its stock per location
A location's order, transfer and stock adjustment history	Those are Shopify's records of what happened there, not settings of the location

Markets

Restored and checked field by field

Details	Market name, Handle, Status, Market type
Prices	Currency, Exchange rate, Local currencies, Price rounding, Taxes and duties in prices, Adaptive pricing, Catalogs, Catalog, Catalog status, Price list, Price adjustment, Compare-at prices, Fixed prices
Metafields	Metafield
Collection conditions	Who the market applies to, Countries and regions, Retail locations, Sales channels, B2B company locations
Sales channels	Domains and subfolders, Default language, Other languages

Limits

A restore can't put these back exactly. Most are Shopify's own rules, and a few are choices made to protect you or your customers; each one says why. A receipt names each one it meets.

Shopify sets a market's own currency, or a price list in another currency, only when the store's payment provider takes more than one currency (Shopify Payments does). Without one, the market keeps the store's currency. This applies to every restore.
Which B2B company locations a market applies to is customer data Shopify protects, so it is not in the backup: a B2B market is restored in place without touching them, and a deleted one is not re-created. This applies to every restore.
A subfolder (like /en-nz) comes back with its market. A web presence on a domain of its own comes back only while that domain is still connected to the store and still has its web presence. This applies when a deleted item is re-created.
Shopify keeps at least one market for countries and regions active, so a restore never switches off the store's last active one: it stays active, and everything else in it is restored. This applies when an item is restored in place.

Not backed up

Which products a market's catalog includes (its publication)	Product availability per market is not read in this version; each product's sales channels are backed up with it
A market's own delivery settings, and the discounts limited to it	Shopify's newer market delivery and discount links are not read in this version
Quantity rules and volume pricing in a price list	Not read in this version

Store languages

Restored and checked field by field

Details	Language, Default language
Sales channels	Published, Domains and subfolders

Limits

A restore can't put these back exactly. Most are Shopify's own rules, and a few are choices made to protect you or your customers; each one says why. A receipt names each one it meets.

Which language is the store's default is set only in Shopify's settings, so a restore never changes the default language. This applies to every restore.
Shopify deletes a language's translations when the language is removed, and turning it back on does not bring them back. They come back when you restore the translations of each item. This applies when a deleted item is re-created.

Not backed up

The translations themselves, in this entry	Each translated item's translations are backed up as an entry of their own, and restored from there

Customer segments

Restored and checked field by field

Details	Name, Conditions

Limits

A restore can't put these back exactly. Most are Shopify's own rules, and a few are choices made to protect you or your customers; each one says why. A receipt names each one it meets.

Shopify checks a segment's conditions again when it is re-created: a condition that names something the store no longer has (a removed app's filter, a deleted metafield definition) is refused, and the receipt says so. This applies when a deleted item is re-created.

Not backed up

Which customers a segment holds	Shopify works that out from the conditions, which are backed up

Customers

Restored and checked field by field

Details	First name, Last name, Email, Phone, Language, Note, Tags, Tax exempt, Tax exemptions, Addresses, Default address, Email marketing consent, SMS marketing consent, Data sale opt-out, Account status, Number of orders, Amount spent
Metafields	Metafield

Limits

A restore can't put these back exactly. Most are Shopify's own rules, and a few are choices made to protect you or your customers; each one says why. A receipt names each one it meets.

Email and SMS marketing consent and the data sale opt-out are backed up but never restored: they are the customer's own choices, so a restore leaves them as they are now, and a re-created customer starts unsubscribed, because putting back a subscription the customer took away breaks anti-spam law. This applies to every restore.
Whether a customer has an active account is theirs and Shopify's: a restore never changes it, and a re-created customer has no account until you invite them again from Shopify. This applies to every restore.
The number of orders and the amount spent are worked out by Shopify from the customer's orders, so a restore never changes them. This applies to every restore.

Not backed up

Customers, until Shopify approves the app's access to customer data	Shopify gives an app its customers only after reviewing how it protects them; until then Home says so and nothing of them is read
Saved payment methods, store credit, subscriptions and B2B profiles	the app never reads payment data; Shopify keeps them
Customer account passwords	Shopify gives them to no app; a re-created customer is invited again from Shopify
Timeline comments on a customer	Shopify's timeline is not available to apps as content

B2B companies

Restored and checked field by field

Details	Company name, Note, Company ID, Customer since, Contacts, Locations, Location name, Location ID, Location note, Location phone, Location language, Billing address, Shipping address, Tax exempt, Tax exemptions, Tax ID, Orders need approval, Buyers can edit the shipping address, Payment terms, Deposit, Catalogs
Metafields	Metafield, Location metafield

Limits

A restore can't put these back exactly. Most are Shopify's own rules, and a few are choices made to protect you or your customers; each one says why. A receipt names each one it meets.

Shopify lets an app set the date a company became a customer only when the company is made, so a restore in place leaves that date as it is. A re-created company gets it back. This applies when an item is restored in place.
A company's contacts are customers: a restore links back each contact whose customer is in your store, and names any contact that waits for its customer to be restored first. Which locations a contact may order for is given again in Shopify. This applies to every restore.

Not backed up

Which locations each contact may order for (contact roles), and staff assigned to a location	a restore links each contact back to the company; give roles and staff again in Shopify
A company's orders, draft orders and store credit	each is backed up as an item of its own kind
What a catalog holds (its products and prices)	a catalog is shared by many locations and markets; the backup records which catalogs each location is in

Store credit accounts

Restored and checked field by field

Details	Owner, Balance, Transactions

Limits

A restore can't put these back exactly. Most are Shopify's own rules, and a few are choices made to protect you or your customers; each one says why. A receipt names each one it meets.

Store credit is money a customer or a company holds: it's backed up and in your export, but never restored, because putting a balance back would be a payment. This applies to every restore.

Not backed up

Store credit, until Shopify approves the app's access to customer data	Shopify gives an app its store credit only after reviewing how it protects it; until then Home says so and nothing of it is read

Gift cards

Restored and checked field by field

Details	Code (last characters), Initial value, Balance, Expiry date, Enabled, Deactivated, Note, Theme template, Customer, Recipient, Issued, Transactions

Limits

A restore can't put these back exactly. Most are Shopify's own rules, and a few are choices made to protect you or your customers; each one says why. A receipt names each one it meets.

A gift card is money a customer holds: it's backed up and in your export, but never restored. Shopify shows an app only the last characters of a card's code, so a backup can't make the same card again, and a new card would be new money. This applies to every restore.

Not backed up

Gift cards, until Shopify approves the app's access to customer data	Shopify gives an app its gift cards only after reviewing how it protects them; until then Home says so and nothing of them is read
A gift card's full code	Shopify shows apps only its last characters

Orders

Restored and checked field by field

Details	Email, Phone, PO number, Note, Tags, Custom attributes, Shipping address, Order number, Date, Status, Payment status, Fulfillment status, Currency, Taxes, Sales channel, Customer language, Customer, Billing address, Shipping, Discounts, Totals
Variants	Line items
Metafields	Metafield

Limits

A restore can't put these back exactly. Most are Shopify's own rules, and a few are choices made to protect you or your customers; each one says why. A receipt names each one it meets.

An order's line items, prices, taxes, discounts, shipping lines, totals, statuses, dates, customer and billing address are the record of the sale: Shopify lets an app change only an order's email, phone, PO number, note, tags, custom attributes, shipping address and metafields, so a restore puts those back and leaves the rest as it is. This applies to every restore.
A deleted order is not re-created: a new order would get a new number, reach every other app on the store as a new sale (a fulfilment app could ship it again) and show payments that never happened, so its backup stays in the export instead. This applies when a deleted item is re-created.

Not backed up

Orders, until Shopify approves the app's access to customer data	Shopify gives an app its orders only after reviewing how it protects them; until then Home says so and nothing of them is read
Orders placed more than 60 days before the app first read them, and changes to an order after it is 60 days old	Shopify lets an app read only the last 60 days of orders until it approves the app's request to read all orders
Payments, refunds, fulfilments, returns and fraud analysis	the app never reads payment or fulfilment records; Shopify keeps them

Draft orders

Restored and checked field by field

Details	Draft order number, Status, Email, Phone, Note, PO number, Tags, Tax exempt, Currency, Custom attributes, Customer, Company, Billing address, Shipping address, Shipping, Reserve items until
Prices	Price, Line discount, Discount, Discount codes, Automatic discounts, Totals
Variants	Line items, Quantity
Metafields	Metafield

Limits

A restore can't put these back exactly. Most are Shopify's own rules, and a few are choices made to protect you or your customers; each one says why. A receipt names each one it meets.

A draft order's status (open, invoice sent or completed) is Shopify's record of what happened to it: a restore never changes it, and a re-created draft starts open, with no invoice sent. This applies to every restore.
A draft order's totals and taxes are worked out by Shopify from its lines, discounts and shipping, with today's tax rates. This applies to every restore.
A deleted draft order comes back as a new draft with a new number, because Shopify numbers drafts itself. This applies when a deleted item is re-created.
A product's line in a restored draft takes the product's title, SKU and price as they are that day, unless the draft set its own price for it, which is put back. A custom item keeps everything it had. This applies to every restore.

Not backed up

Draft orders, until Shopify approves the app's access to customer data	Shopify gives an app its draft orders only after reviewing how it protects them; until then Home says so and nothing of them is read
A draft's payment terms, invoice email and timeline	Shopify keeps them; set payment terms again on a re-created draft

Backed up for your records, never restored

Gift cards and store credit. They're money, so the app never writes them back, and Shopify shows an app only the last characters of a gift card's code, so no backup could recreate a card anyway.

Never backed up, by design

Blog comments. The app never reads them.
A download of a theme. Themes are backed up and can be compared, but Shopify's App Store rules don't let an app offer a theme as a download, so no export ever holds one.

Think something is missing from this page? Write to me at support@aislekit.app and I'll check it.