Shopify Theme Update Checklist: Test Your Store Before Publishing

Updating a Shopify theme is more than installing a newer design. Customers still need to find a collection, select a size or colour, add the correct product to their cart and navigate the storefront on a phone. The useful question is whether the updated theme preserves the important buying journeys that work in the current version. A structured comparison turns that question into practical checks before a manually added draft theme is published.

This guide covers theme versions, copies, the transfer of editor customisations and code edits, and a focused review of navigation, collections, variant selection, cart, languages, mobile interaction and keyboard access. A fictional comparison table helps distinguish what should happen from what you actually observe. You can examine these customer-facing journeys without placing a paid order.

Record the current theme version and establish a reliable baseline

Begin in Online Store in your Shopify admin. Check the version number of the published theme and the versions of any installed draft themes. If an update is offered, read its release notes to see which features and changes are included. Write down the current theme, the proposed version and any storefront customisations that matter to your business. Having both versions clearly identified makes comparison easier, especially when several older draft themes are already listed.

Before reviewing the update, use the live storefront as a customer would. Open the homepage, expand the main navigation, visit a collection, choose a filter, open a product with several variants and add it to the cart. Record what actually works. For example, the mobile menu opens without losing its subcategories, selecting a colour filter refines the collection, and changing a size updates the displayed price. These are meaningful baseline behaviours rather than subjective impressions of the design.

Choose different page types rather than repeatedly checking the same template. A straightforward product with one version cannot reveal problems in a multi-option product form. Include an available variant and, when present, a sold-out variant. Check a collection with filtering, a second collection with a different layout, and a cart with two distinct items. Those examples exercise the parts of the theme that help shoppers move from discovery to a specific purchase.

A useful baseline describes expected behaviour in short sentences: ‘the Women menu opens the right collection’, ‘the colour filter can be cleared’, ‘the selected size has the corresponding price’ and ‘the cart identifies the chosen option’. You are not requiring the new theme to look pixel-for-pixel identical. You are making sure that a changed layout still lets a shopper complete the same important task.

Duplicate the theme without confusing it with a store backup

The Shopify theme duplication command is available in the theme action menu. It creates another theme entry that you can keep as a reference or customise separately. Give your copies distinguishable names or record the relevant version and date. An identifiable earlier version helps when you need to compare the updated design with the working storefront. Keep an eye on the number of draft themes already installed, as Shopify sets a limit on how many can be stored in the admin.

A duplicated theme is not a complete copy of a Shopify store. Products, collections, navigation menus, pages, blog articles, customers and orders are not all packaged as a store database inside that theme. A theme download likewise does not transfer the entire catalogue and content to another account. Within the same store, those administrative resources remain managed separately from which theme is currently published.

Think of the theme copy as a reference for presentation, template files and theme-specific settings. It does not represent an independent snapshot of product inventory, payment configuration or every setting held by installed apps. An app block or embed may be part of the theme's editor configuration, while its wider application settings live outside the theme. Test both the visible block and its intended interaction when reviewing an updated theme.

The distinction matters when you switch themes. Re-publishing an earlier theme changes the storefront presentation and associated theme configuration, not the history of orders or product stock. Similarly, editing a product in the Shopify admin while you review a draft may affect what both the old and new themes display. Avoid confusing such a shared data change with a regression introduced by the theme update.

Review the updated draft and check which custom code was carried across

When a supported manual theme update is available, Shopify lets you add its updated version to Draft themes. The new copy can be opened through Review before you select Publish to make it live. Adding it to drafts does not immediately replace the published storefront. This allows you to assess the new version and make appropriate changes while customers continue to use the current theme. Check the version and release notes first.

Shopify carries over customisations made in the theme editor during this update process. These include theme settings, sections and blocks that were added or rearranged, their configured data sources, newly created templates, app embeds and extensions, and text changes made using the theme content editor. Carried-over settings still need a visual and functional review. A configured section might remain present but take a different position or occupy more space in the updated layout.

Manual code changes have an important condition: Shopify includes code edits when they do not conflict with the update. The updated draft theme card states whether they were included. Read the message rather than assuming success. ‘Theme added: code edits successfully included’ is different from ‘Theme added: code edits could not be included’. If edits were not carried over, identify the specific custom functionality that should be retained, restore what is appropriate and test it in the new version.

Custom CSS needs a similar comparison. A selector that targets a button or section in the old markup might no longer reach the intended element after the theme structure changes. Inspect spacing, product labels, menu behaviour and any specially styled calls to action. Having CSS text in a file is not the same as confirming that the relevant page still looks and works as intended. Changes introduced by an installed app to theme code may also need attention.

Not every Shopify theme update follows this manual draft-and-publish flow. Shopify also applies certain automatic updates, including fixes for bugs and security issues, and describes these as not changing the theme's look, content or settings. If the admin reports an automatic update, inspect the status and release notes rather than looking for a draft you must publish yourself. The official Updating themes guidance explains both paths.

Follow the customer from navigation to collections and filters

Start the draft review with the main menu. Check primary categories, dropdowns, submenus and links to key content pages. On a phone, open the drawer or mobile menu, move through nested categories and close it again. Different animations and spacing are expected in a new design. What matters is that shoppers can still reach the relevant collections and understand which section they are browsing.

Open a collection that offers several filters. Compare product cards, titles, images, prices, sorting and available values. Select one filter and check that the visible product set changes as expected, then clear it and verify that the original list returns. The updated theme may place filters in a sidebar, above the products or behind a mobile control. The location can change as long as the action remains obvious and usable.

Repeat the check in another collection with a different template or a smaller product range. A successful homepage review does not establish that every collection template works. Follow a product card link and make sure it opens the intended item. Compare image crops and product titles, but focus particularly on missing links, inaccessible controls or information that prevents the visitor from recognising the offer.

Check the empty-results state after choosing a combination that has no matching products, where that case exists in the store. Shoppers should understand that the chosen filters produced no matches and be able to clear their selections. On mobile, look for selected filter values after the filter panel is closed. Those details help visitors recover and continue browsing rather than being stranded on an apparently empty collection.

Test selected product variants and the cart together

Open a product with at least two genuine purchase variants. Select one size and colour, and check that the visible option labels, image, price, availability and Add to cart button describe the same version. Change one option and repeat. The theme can introduce a new visual selector, but the selected product must not silently remain the previous variant. For a focused explanation of this consistency check, see Product Variant Selection: Size, Colour, Price, Stock and Cart. A correct price next to an incorrect selected size is not a successful result.

Include an unavailable variant if the product offers one. The stock message and purchase button must agree with the active combination. If there is a sticky mobile purchase bar, compare its price, availability and selection with the main product form. Rapidly switch between options and inspect the resulting state before buying. This can expose a form that visually updates but still submits the identifier of a previous variant.

Add an available version to the cart and inspect its title, variant options, quantity and corresponding price. Change the quantity, then add a different size or colour of the same model. The two choices should remain distinguishable. Remove an item and confirm that the remaining line is correct. You can exercise this cart behaviour and the available route towards checkout without creating a paid order.

Check an empty cart as well as a filled one. If the theme uses a cart drawer, ensure it opens, closes and reports the current selection correctly. If the cart is a dedicated page, follow the navigation to it. Confirm that relevant checkout steps are reachable and readable in the visible interface. Payment processing and completed order operations are separate from this presentation check.

Check languages, mobile layouts and keyboard interaction

Repeat the critical journey in the storefront languages that are actually published. Open the menu, a collection, a product page and the cart in at least one language other than the default. Examine button labels, selected variant names, messages and the language switcher. Translated text often takes more horizontal space than its source. A product button that fits in English may wrap awkwardly in another language after a layout change.

Test both a narrow and a wider phone screen. Look for menu items hidden behind an overlay, filter options that cannot be reached, overlapping price text or a sticky purchase button that covers another essential control. Touch the actual controls when possible, rather than relying only on a desktop window resized to mobile width. Check opening and closing drawers, changing a size and returning from a supplementary information panel.

Use the keyboard on desktop to follow the navigation and purchase path. Tab should move to links, menus, search fields, filters, variant selectors and purchase buttons in a meaningful order. The focus indicator should remain visible. Open and close any relevant menus or dialogs and make sure the user can continue without getting trapped. A redesigned navigation is only useful when its essential destinations remain accessible.

Review supporting product information too: size guides, product details, delivery information and customer-facing reassurance that was deliberately included in the former theme. These elements may move in a revised layout, but customers still need to find them at the relevant point in their decision. Check a simple product and one requiring more explanation, especially on a phone where sections are stacked vertically.

Use a regression table to turn differences into decisions

Compare the existing theme and updated draft by writing down three things: the expected behaviour, the behaviour actually observed and the next action. Distinguish presentation changes from functional differences. A new border radius or changed spacing may be intentional; a selector submitting the wrong variant is a different matter. The table below demonstrates how to record a specific scenario that another reviewer can repeat.

Every observation in this table is fictional and illustrative. Replace it with the actual page, device and action from your own storefront. Complete the observed column only after testing the draft, and repeat the same scenario after a correction. This gives the publication decision a clear record of the tested behaviour.

Publish or return to the former theme based on observed faults

A manually updated theme draft is ready for publication when the critical storefront journeys work as intended: navigation, collection discovery, filtering, variant selection, cart, available languages and essential mobile and keyboard controls. A deliberate typography change does not need the same response as a failed Add to cart button. Base the decision on whether customers can complete their intended tasks, rather than whether every section looks exactly as it did before.

Write down reproducible defects with the page address, device, language, chosen options and steps leading to the issue. For example: ‘On the mobile product page, selecting L updates the label but not the price’. This is a precise issue to investigate and retest. After a fix, run the same sequence again. That establishes whether the correction resolved the behaviour instead of merely changing something nearby.

After a new theme is published, check the live storefront's main routes once more. Draft review is valuable preparation, but shoppers use the published version. If a genuine blocking problem appears, such as a nonfunctional navigation menu, variant purchase action or cart, you can return to the earlier working theme while correcting the revised one. When you publish a different theme, Shopify moves the previously published one to Draft themes.

Re-publishing an older theme restores the earlier theme presentation, not a snapshot of store transactions or catalogue data. It does not reverse orders, product records, inventory or account-level app settings. If a separate app configuration was changed, that issue needs its own investigation. Treat switching themes as a targeted response to a demonstrated presentation or theme interaction problem.

Kiljano offers a focused Webshop Launch Readiness – 30 Checks covering 30 publicly verifiable readiness points, with a PDF of observations and priorities plus an optional TXT checklist in ZIP. The Technical PrestaShop/Shopify Quick Scan reviews public storefront functions and responsiveness, including navigation, product pages, cart and accessible checkout stages, with a report of priorities and recommendations.

Frequently asked questions about Shopify theme updates

Is duplicating a theme the same as backing up the entire store?

No. A theme copy retains theme-related presentation and files. Products, collections, orders and account information are managed separately and are not packaged into a full store backup.

Do theme editor changes carry over to the updated version?

With a supported manual update, Shopify carries over editor settings, sections, blocks, templates and app embed settings. Review their actual display in the updated draft.

Are custom code changes always preserved?

No. Shopify includes code edits that do not conflict. The updated draft theme card indicates whether they were included. Inspect the related features and custom CSS.

Does every Shopify theme update require manual publication?

No. A manually added updated version can be reviewed as a draft and then published. Shopify also applies certain automatic updates, including fixes for bugs and security issues.

Which storefront tasks should I test first?

Check menus, collections, filters, product variants, price and availability, cart, published languages, mobile controls and keyboard operation.

Do I need to make a paid order to test the theme?

You can verify product selection, adding to cart, quantities and accessible checkout steps without completing a purchase. Payment operations are a separate test.

What happens when I publish the previous theme again?

The earlier theme presentation becomes active. Existing orders, product data, inventory and account-level app settings are not rolled back by changing themes.