Theme updates and apps

Keep the current working theme while you test a new one. A successful upload, an app block appearing in the editor, or a familiar-looking preview is not a complete update check.

Before an update

1. In Online Store → Themes, identify the theme currently used by customers.
2. Use its actions menu to duplicate it. Give the copy a recognisable name and date.
3. Keep a downloaded theme copy where available, together with the original theme download and purchase record.
4. Record the edition, your key template assignments, chosen products and collections, menus, page templates, app blocks and app embeds.
5. Note any custom code or developer changes and which app or developer supplied them.
6. Read the update instructions supplied with the actual release.

Expected: you can identify the working theme and a separate recoverable copy without relying on memory.

A theme copy preserves theme files and settings. It is not a complete backup of products, orders, customers, uploaded files or app data. Follow the relevant Shopify or app backup process for those resources.

Install and preview without publishing

Add the new version as a separate, unpublished theme. If your purchase channel provides an update workflow, follow its instructions and inspect the resulting copy before publishing.

A fresh ZIP upload should be treated as a new starting theme. Do not assume it will automatically import the design settings, section order or resource selections from the old theme. Changing global colors or typography does not replace your page layouts.

Work in the new theme's editor and preview. Keep the live theme available while you reconnect content and run the Launch checklist.

An unpublished theme separates the theme presentation, not all store settings. Product data, payment settings, shipping rules and some app settings are shared across the store. A change in an app's own admin may affect the live shop as well. Use test products and plan any store-wide payment or app changes carefully; do not assume the theme preview provides a separate checkout environment.

Reconnect and verify your resources

Use this list even if the preview already looks familiar:

Area	What to check	Expected result
Header and footer	Chosen menus, logo, links and menu image-card destinations	Links open your real pages and collections.
Home and collection sections	Product and collection selections, buttons, mobile images	Your intended content appears without empty offers.
Product templates	Products' assigned template names and each template's blocks	The right fields, choices and purchase instructions appear on each product.
Pages	Page content, assigned page templates and navigation links	Story, guide and contact content uses the intended layout.
Personalization	Field names, required fields, limits, preview settings and confirmation	Details remain correct through the bag and a test order.
Gift extras	Selected products, both quantity rules and bag suggestions	Actual products and quantities match the offer.
Shopping experience	Quick shop, after-add destination and eligible payment buttons	The expected purchase route is available.
Apps	App blocks, app embeds, installation steps and purchase options	The required app function works in this theme, not only the old one.

Products, collections, Shopify Pages and menus are store resources; the theme chooses where to display them. A new theme upload does not create those resources for you. Renaming a template or selecting a different resource can change the layout or content shown, so verify actual product and page previews rather than only their editor names.

If a selection is missing, choose the intended resource again in the new theme. Do not delete a store product or page just to fix a missing theme reference. Use Navigation and pages, Personalized products and Gift extras for the relevant setup steps.

Add an app carefully

Use the installation steps provided by the app developer. Where the app supports a theme app block, add it in a supported section. Where it uses an app embed, check its embed setting for the theme being tested. Some apps also require settings in their own admin.

Expected: the feature works in the unpublished storefront preview and remains present after the editor is saved and reopened.

An app block in a product template can add purchase requirements. Keepsake routes that product through its full product page rather than allowing quick shop or a separate product payment form to skip those requirements. Non-empty Custom Liquid in that product section follows the same cautious route. See Quick shop and payment buttons.

Apps that inject fields in another way may need additional setup. If the app adds a required choice, confirm it cannot be bypassed by quick shop or another purchase button. You can turn off Allow quick add for simple products on that product template while investigating. Do not remove the required choice to make the shortcut appear.

Test the integration you actually use

At minimum, check:

1. The product page with all required app choices and validation.
2. The selected variant, quantity and price after choices change.
3. The bag, including edits, linked extras and removal if those features apply.
4. Checkout and a test order, including the details your fulfilment process needs.
5. A phone-sized layout and a real device used by your customers.

For a subscription app, verify plan selection and the resulting subscription purchase. For reviews, verify how real review content and ratings are supplied. For a personalization or fulfilment app, verify the production data and supplier handoff in that app.

The theme's text fields and name illustration do not generate production artwork, approve a print proof, calculate an app's pricing rules, or send work automatically to a print-on-demand supplier. Compatibility with a named app is not implied by these controls. Obtain app-specific confirmation and test your configuration before relying on it.

Isolate an issue without disrupting customers

Use an unpublished duplicate. Change one setting at a time and record the result. If you temporarily remove an app block or turn off an embed to compare behaviour, do that only in the test copy, save it, then restore the feature before the final purchase test.

If the problem occurs only with one app enabled, send the app developer the reproduction steps and ask about their theme requirements. If it also occurs with ordinary theme content in the clean copy, use Contact and support. Include the comparison result so neither support team has to guess.

Publish and keep a return path

Publish only after the new theme passes your store's Launch checklist, including its actual purchase flow. Keep the prior working theme in the library so it can be republished if needed.

Switching back to a previous theme does not undo orders, product changes, app settings or other store changes made during the update. If a problem appears after publishing, record the time and affected action, restore the appropriate working experience, and investigate on the unpublished copy.

For common symptoms, start with Troubleshooting.