My Shopify theme broke after an update: what should I do?

You updated your Shopify theme, or someone did it for you, and now something looks or works differently. Maybe a section has disappeared, the layout is off, a custom feature is missing or the cart no longer behaves as before.

Typical symptoms include:

• custom sections or blocks are missing
• colors, fonts or spacing have changed
• a feature added by a developer no longer works
• an app widget, such as reviews or a size guide, has disappeared
• the cart or "add to cart" button behaves differently
• pages look fine on desktop but not on mobile

The good news is that in Shopify a theme update does not normally destroy your old theme. In most cases the previous version is still in your theme library, and you can go back to it while you work out what changed.

This guide explains how theme updates work in general, why customizations may not carry over, how to restore the previous version safely and how to avoid the same problem next time.

How do Shopify theme updates work?

A Shopify theme is a set of templates, sections, settings and code that controls how your store looks and behaves.

When a theme from the Shopify Theme Store has a new version, Shopify usually lets you add the updated version to your theme library rather than overwriting the theme you are using. The exact steps can vary depending on the theme and on how Shopify presents updates at the time, but the general idea is:

• the update arrives as a new copy of the theme
• settings made in the theme editor are generally carried over where possible
• changes made directly to the theme code are generally not carried over
• your current theme stays in the library until you remove it

This is why an update can look broken even though nothing was "lost": the new version simply does not include the custom code that was added to the old one.

Themes bought from other sources, or custom themes built by a developer, may not update this way at all. They may need to be updated manually, file by file.

Why did my theme break after the update?

Custom code was not carried over

If a developer, an agency or an app edited the theme files, those edits live only in the old version. Common examples:

• custom sections or snippets
• changes to the product page or cart
• tracking or analytics code
• small style fixes
• code added by an app during installation

The new version starts from the theme developer's original code, so these changes are missing.

Sections and settings changed in the new version

Theme developers sometimes rename, merge or remove sections and settings between versions. A setting you relied on may now work differently or not exist. Content tied to a removed section may not appear.

App embeds and app blocks need to be enabled again

Many apps add features through app embeds or app blocks in the theme editor. On a new theme version, some of these may need to be turned on again or placed again in the right section.

Older apps that injected code directly into the theme files may not appear at all in the new version, because that code was part of the old theme.

The update was published straight away

If the updated theme was published before anyone checked it, customers see the problems immediately. This is the most common reason a routine update becomes urgent.

First, find out what changed

Before you change anything else, answer these questions:

• When was the theme updated, and by whom?
• Was the new version published, or is it still unpublished?
• Is the previous version still in your theme library?
• What exactly is broken: a page, a section, a feature, the cart?
• Does the problem happen on desktop, mobile or both?
• Was the old theme customized with code, by a developer or by apps?

If someone else did the update, ask them which version they installed and whether they knew about custom code in the old theme.

What can you safely try?

Go to your theme library

Go to Online Store → Themes. You will see your current (published) theme and a library of other themes. Look for the previous version: it often has the same name with a different version number or date.

Preview the previous version

Preview the old version before doing anything. Previewing does not change what customers see. Check that it still looks and works as you expect, including the cart.

Publish the previous version if needed

If the store is clearly broken and the old version works, publishing the old version is usually the quickest way to restore the store for customers. You can then work on the new version calmly, unpublished.

Before you publish, think about anything you changed in the new version since the update, such as new content in sections or new settings. Those changes may not exist in the old version. Note them down so they can be re-applied later.

Check app embeds and blocks

Open the theme editor for the theme that is missing an app feature and check the app embeds section. If an app's embed is off, turning it on may bring the feature back. Some apps also need their block placed again in a specific section.

Keep both versions

Do not delete the old version. It contains the custom code that needs to be carried over to the new version. Keep it in the library until the new version is complete and tested.

What should you avoid doing?

Avoid:

• deleting the old theme from the library
• editing the live theme's code without a duplicate
• installing another update on top of a broken one
• uninstalling apps to "clean up" before you know what they do
• copying files from the old theme to the new one without understanding them
• assuming the old version will update itself again later

Change one thing at a time and preview every change before publishing.

How can you avoid this next time?

A theme update should be treated like any other change to a live store:

1. Duplicate first. Before editing code or applying an update, make a duplicate of the live theme. It costs nothing and gives you a clean fallback.
2. Keep a record of custom code. A short list of what was changed, where and why makes updates far easier.
3. Update in the library, not live. Add the new version, keep it unpublished and check it carefully.
4. Re-apply customizations to the new version before publishing it.
5. Test the important journeys: home page, collection, product page, cart, checkout start, mobile view.
6. Publish at a quiet time and keep the old version for a while in case you need it.

When should you ask for technical support?

It is a good idea to get help when:

• the old theme contains custom code and you do not know what it does
• the cart, checkout start or product options are affected
• apps that used to work no longer appear
• the previous version is missing from the library
• you need the new version's features but also your old customizations
• the theme is custom-built or not from the Theme Store
• you have already tried a few changes and are not sure what state the theme is in

You do not need to know exactly what broke before asking for help.

What information should you collect?

Useful details include:

• your store URL
• the theme name and the old and new version numbers
• when the update was done and by whom
• whether the new version is published
• what is broken, with screenshots
• a list of known customizations and apps that interact with the theme

If someone needs to work on your theme, add them as a staff member or collaborator from the Shopify admin. Do not send your admin password by email.

How D4Hub can help

D4Hub can help with:

• identifying the previous working version and restoring it safely
• comparing the old and new theme versions to find the custom code
• carrying customizations over to the new version
• re-enabling and placing app embeds and blocks
• testing the product page, cart and checkout start on the new version
• documenting your customizations so future updates are easier
• setting up a safer process for theme updates

You can ask for support at any stage, whether you only need help finding the right version or want the whole update handled.