How to set up a Shopify staging store (and publish changes safely)

Shopify lets you preview an unpublished theme, but there is no staging area for store content. Products, collections, pages, navigation and metafields all change on the live store the moment you save. A staging store is a second Shopify store used to prepare and check those changes before customers see them.

This is the whole job, including the parts that are free, the parts Shopify cannot do, and the cases where you do not need a second store at all.

Does Shopify have a staging environment?

Not for store content. Themes have something close to one: an unpublished theme can be edited and previewed without affecting the live store, and published when it is ready. Everything else — a product title, a collection, a page, a menu item, a metafield — is live on save, with no preview and no history to go back to.

So “staging” on Shopify means a second store you control, not a feature you switch on.

Which second store to use

Shopify Plus: an expansion or sandbox store

Plus includes expansion stores and a sandbox store. Either works as staging and neither costs extra, so Plus merchants already have the second store and do not need anything to create one.

Other plans: a free development store

A development store, created through a Shopify Partner account, is free and is the usual answer on Basic, Grow and Advanced. Two limits matter before you rely on it:

It is always password protected. The password page cannot be removed while the store is a development store. Fine for staging; it does mean nobody can see it without the password.
It cannot take real payments. Orders can only be tested with Shopify’s Bogus Gateway or your payment provider’s own test mode, and store credit and gift cards are not supported. A checkout you test on staging is therefore not the checkout your customers will use.

That second limit is the honest reason staging on Shopify is about content rather than the full purchase journey. If what you need to test is a real card payment, a development store will not tell you.

A duplicate theme, when the change is only the theme

If you are changing layout, sections or theme settings and nothing else, duplicate the theme on the live store, edit the copy, preview it, and publish when it is right. That is faster than any second store and is what Shopify built the feature for. A staging store earns its keep when the change touches products, collections, pages or navigation — the things a duplicate theme cannot hold.

What copies across, and what does not

Setting up staging is mostly copying. It is worth knowing in advance which parts have a route and which do not.

Has a route

Theme. Download the live theme as a .zip and upload it to staging. Theme settings travel with it.
Products and variants. Products → Export, then Import on staging. Rows are matched on the product handle, so handles must agree on both stores.

Has no route in the admin

Collections, pages and menus. There is no CSV export for these in the Shopify admin. They are recreated by hand or copied with an app.
Installed apps and anything stored inside them. Apps install per store. An app on staging is a separate installation with its own, empty data.
Checkout, payments, shipping, taxes and domains. These are store settings, configured once per store.
Customers, orders and discount codes. Not copied, and on a development store, not usable in a real transaction anyway.

The practical consequence: staging is a faithful copy of what your pages say, and never a faithful copy of how your store sells.

The hard part is publishing, not staging

Copying live into staging is the easy direction. If it goes wrong, nobody sees it. The direction that matters is staging back into live, and that is the one Shopify gives you no path for.

Two things make it harder than it sounds:

A CSV import writes every field in the file. It does not write only the fields you changed. If the export is a week old, re-importing it also puts back a week of other edits — inventory, prices, anything — silently and in bulk.
Shopify keeps no history of product fields. Once a value is overwritten there is nothing in the admin to revert to. Whatever the old value was, it is gone unless you wrote it down first.

So a workable publish step needs three things that no export and no import gives you: a field-by-field list of what actually differs between the two stores, the ability to publish only the differences you approve, and a copy of live’s version of every value you overwrite, taken before you overwrite it.

A publish checklist

List what differs between staging and live, field by field, and read it. Anything on the list you did not intend is the whole reason for doing this.
Publish only the items you approved, not the whole store.
After publishing, read each changed value back from live. A write that silently failed looks identical to one that succeeded until a customer finds it.
Keep live’s previous values for everything you touched, so a bad publish can be put back rather than reconstructed.
Check anything downstream that reads your content: feeds, marketplace listings, and any app that caches product data.

When you do not need a staging store

Most changes do not warrant one, and setting one up for them costs more than it saves:

Theme-only work. Duplicate the theme. That is the native answer and it is better than staging for this.
One product, or a few. You can see the field before you save it, and you can write the old value down in a second.
Anything you can test with a draft. Pages and blog posts can sit unpublished on the live store.

A staging store is worth the setup when a single change set touches many products, collections, pages or menus at once — a seasonal rebuild, a catalogue restructure, a migration — because that is when reviewing before publishing is the difference between a mistake you spot and a mistake your customers do.

SafeStage — Make changes on a staging store, review every difference, publish only what you approve, and undo any publish.
Free · Starter $49/month · Pro $149/month
Install SafeStage free on the Shopify App Store →

Common questions

Does Shopify have a built-in staging environment?

Not for store content. An unpublished theme can be edited and previewed without affecting the live store, but products, collections, pages, navigation and metafields go live the moment you save, with no preview and no history. Staging on Shopify means a second store you control, not a feature you switch on.

Can I use a Shopify development store as staging?

Yes, and it is free through a Shopify Partner account. Two limits matter: a development store is always password protected and the password page cannot be removed while it stays a development store, and it cannot take real payments at all. Orders can only be tested with Shopify's Bogus Gateway or a payment provider's test mode, and store credit and gift cards are not supported.

Do Shopify Plus merchants need a staging app?

Not to create the second store. Plus includes expansion stores and a sandbox store, either of which can be used as staging at no extra cost. What Plus does not give you is a way to compare the two stores field by field and publish only approved changes back to live.

What does not copy from a live Shopify store to a staging store?

Collections, pages and menus have no CSV export in the Shopify admin. Installed apps and the data held inside them do not copy, because apps install per store. Checkout, payments, shipping, taxes and domains are per-store settings. Customers, orders and discount codes do not copy either. Themes and products do have a route: a theme downloads as a .zip, and products export and import as CSV matched on the product handle.

Why is publishing from staging to live the difficult part?

Because Shopify gives it no native path, and the two obvious workarounds both lose information. A CSV import writes every field in the file rather than only the fields you changed, so an older export silently puts back other edits as well. And Shopify keeps no history of product fields, so once a value is overwritten there is nothing in the admin to revert to.

When is a staging store not worth setting up?

For theme-only work, duplicate the theme on the live store and preview it instead. For one product or a few, you can see each field before saving it. Pages and blog posts can sit unpublished on the live store. A staging store earns its setup when one change set touches many products, collections, pages or menus at once.