Shopify Theme Update Without Losing Customizations — Practical Guide for SA Businesses

A Shopify theme update without losing customizations is achievable — but only if you understand which of your changes Shopify preserves automatically and which it cannot protect. For South African store owners running on Shopify, a theme update is one of those admin tasks that looks routine until a miscalculation wipes out weeks of careful configuration. The good news is that the risk is almost entirely predictable once you know how Shopify categorises your changes.

Shopify separates your store into two distinct layers: a settings layer (what you configure through the visual theme editor) and a code layer (anything modified directly in theme files). These two layers behave very differently during an update, and confusing them is the source of most post-update surprises. Before you click "Update", this guide gives you the pre-update audit SA merchants actually need.

What a Shopify theme update replaces — and what it doesn't

A theme update in Shopify replaces the code layer of your theme — the Liquid files, CSS, and JavaScript shipped by the theme developer — but it leaves the settings layer intact. Understanding which of your customizations live in each layer is the first step to a safe update.

Step-by-step: how to do a Shopify theme update without losing customizations

The safest way to update a Shopify theme without losing customizations is to duplicate your live theme, document every code edit, then install the update as an unpublished draft and re-apply any code changes that Shopify's merge could not carry over automatically. Shopify's official guidance confirms you should always save a copy of any customized code before updating — the steps below make that practical.

Step 1: Duplicate your live theme as a backup. Duplicating before any update is the most important step. Go to Shopify Admin → Online Store → Themes → find your current theme → click Actions → Duplicate. This creates a backup copy in your theme library that you can restore instantly if something goes wrong. You can also click Actions → Download theme file to keep a local ZIP on your computer.

Step 2: Audit and document your code edits. Before installing the update, open Actions → Edit Code on your live theme and review every file you or a developer has modified. Record the filename and the specific change — a spreadsheet or notes document works fine. This step is your shopify theme customization backup for the code layer.

Pay particular attention to custom snippets in the /snippets/ folder, any custom Liquid blocks you've added, and any CSS or JavaScript that isn't part of the original theme files. Copy the modified code sections to a safe document before proceeding.

Step 3: Check for the update. In Shopify Admin, go to Online Store → Themes. Under your current published theme, Shopify displays the theme version. If an update is available, you'll see the option to add the new version alongside release notes describing what changed.

Step 4: Install the update as a draft. Select the option to add the updated version to your theme library. Shopify installs it as an unpublished draft — named "Updated copy of [your theme name]" — without touching your live store. Review the draft before publishing.

Step 5: Read Shopify's post-update message. After the draft is created, Shopify displays one of two messages: "Theme added: code edits successfully included" or "Theme added: code edits could not be included." The second message means your code edits conflicted with the new version and were not carried over — you'll need to re-apply them manually to the draft using your Step 2 documentation.

Step 6: Compare and re-apply as needed. Open the updated draft in Edit Code and compare it against your Step 2 notes. Where edits were not carried over, paste your custom code back in. Use a diff tool (Diffchecker works well for this) to compare files side-by-side against your backup theme if needed.

Step 7: Preview and test before publishing. Use the theme preview to walk through your key pages: homepage, product pages, collection pages, cart, checkout flow. Test your payment gateway integrations and check that all sections render correctly on mobile. Only when everything looks right should you click Actions → Publish on the updated draft.

Which code edits are most at risk during a Shopify theme update

Not all code edits carry the same risk during an update — the degree of danger depends on whether your change touches the same files the theme developer modified in the new version.

Edits to theme developer Liquid files are the highest-risk category. When you open a file like sections/header.liquid or layout/theme.liquid and make changes, you're working in the same file the theme developer updates. If the new version changes that file, your modification conflicts and will not survive.

Custom CSS or JavaScript injected into theme files shares the same risk. If you've added styling directly to assets/theme.css or a similar vendor file, a theme update that modifies that file will overwrite your additions. The safer long-term approach is to create a separate asset file (e.g., assets/custom.css) and include it via a reference in your theme.liquid — a new file you created won't conflict with the theme developer's updates.

App code manually pasted into Liquid files is particularly problematic. Some older app integrations required you to paste a snippet into theme.liquid or a specific section file. If the theme update overwrites that file, the snippet disappears. Modern apps using Shopify's App Embed or App Block architecture don't require manual Liquid injection and are fully update-safe.

Beyond the duplicate-and-edit: three more update methods

Three alternative update methods — theme-developer updater tools, Shopify's GitHub integration, and a clean theme migration — serve stores that have outgrown the manual duplicate-and-document approach.

Theme-developer updater tools. Some theme developers publish their own updater tools alongside their themes. Out of the Sandbox, for example, offers "Theme Updater & Backups" for its Turbo and Flex themes, which uses AI-powered merging to carry customizations across versions. If your theme developer offers a similar tool, confirm it supports your specific theme before relying on it — these tools are typically scoped to one developer's theme catalogue, not a universal solution for any Shopify store.

GitHub integration. Shopify's GitHub integration for themes connects your store's theme to a Git repository so that every change is tracked as a commit. When you need to update shopify theme code edits across a major version, pull requests give you a full diff view and the ability to revert with a single command.

This is the professional standard for development teams making frequent changes, but it's overkill for a store owner making occasional editor tweaks. Note that the integration only supports the standard Shopify theme folder structure.

Migrating to a new theme. If your current theme hasn't received updates in over a year, or if you're still on an older theme that predates Online Store 2.0, a clean migration to a modern theme is often more practical than repeated patching. You'll rebuild your theme editor configuration from scratch, but you start with a clean code layer and all your store data (products, customers, orders, collections) transfers automatically — it's only the visual configuration, not your catalogue.

SA payment gateways, app integrations, and what survives

South African merchants cannot use Shopify Payments — it's not available in South Africa as of mid-2026 — so every SA store relies on a third-party Shopify payment gateway such as PayFast, Peach Payments, Yoco, or Ozow. The good news is that all of these integrate via Shopify's app framework rather than direct theme code changes, which means their integrations sit in the app layer and are update-safe by architecture.

Where SA stores most commonly run into update trouble is not with payment gateways but with older app integrations — loyalty programmes, review widgets, or wishlist features installed before Shopify's Online Store 2.0 architecture became standard. These older apps often required manual snippet injection into theme Liquid files.

If your store has integrations like this, audit them carefully before any update: check whether the app now offers an App Block alternative, and migrate to it before you update your theme. You'll make the switch once and won't need to revisit it with each future update.

Why South African Businesses Choose Growth Pulse Media

A safe shopify theme update without losing customizations is something SA merchants get wrong most often when they skip the pre-update audit — Dirk van Greuning built and scaled a large South African ecommerce business before founding Growth Pulse Media, so the team's understanding of Shopify's theme architecture comes from operating a real store, not just managing client accounts. That background shapes how we approach theme work: we look at what the store actually does before touching any code, and we document every modification so future updates don't cause surprises.

As a registered Shopify Partner, Growth Pulse Media handles theme customizations, store setup and ongoing optimisation for SA merchants across Johannesburg and beyond. Our Shopify marketing services cover everything from theme configuration to conversion optimisation, and all work is executed in-house — you won't be handed off to a junior developer or an offshore team the moment the brief gets technical. We keep a limited client load specifically so senior attention stays on every store we work with.

Who this is NOT for

Frequently asked questions

Will updating my Shopify theme delete my products and orders?

No. Updating a Shopify theme has no effect on your store data — products, collections, customer records, orders, and inventory all live at the platform level, completely separate from theme files. A theme update only replaces code files; it cannot touch your catalogue or transaction history. Your store data is safe regardless of what happens to the theme code layer.

What does "code edits could not be included" mean after a Shopify theme update?

This message means that one or more of your custom code modifications conflicted with the changes made in the new theme version — so Shopify could not merge them automatically and excluded them from the updated draft. Your theme editor settings (colors, fonts, sections) will still have been carried over. You'll need to review your code documentation and manually re-apply the missing edits to the draft before publishing it.

Do I need to redo my theme settings after a Shopify theme update?

In most cases, no. Theme settings configured through Shopify's visual editor — brand colors, fonts, logo, section content, block layouts — are stored in settings_data.json and are preserved automatically when a theme is updated. If you find that settings haven't transferred correctly after a major version jump, you can manually copy the settings_data.json file from your backup theme to the updated draft using the Edit Code panel.

How often should I update my Shopify theme?

Shopify recommends keeping your theme reasonably current — theme updates include security patches, performance improvements, and compatibility fixes for new Shopify features. A practical approach for most SA stores is to check for updates quarterly, apply them to a duplicate draft, test the result, and publish only once verified. There's no need to apply every minor patch immediately, but falling multiple major versions behind makes future updates harder and riskier.

Does the Shopify GitHub integration protect my customizations from being overwritten?

The GitHub integration tracks your theme code as commits in a repository, which means you always have a recoverable history of your changes. It doesn't automatically protect code edits from being overwritten — it gives you version control so that re-applying lost edits is fast and exact. For stores with active code development, it's the most reliable way to manage theme changes over time; for stores with occasional edits, the duplicate-and-document approach described in this guide is sufficient.

Dirk van Greuning Founder, Growth Pulse Media

Founder of Growth Pulse Media and a specialist in South African search dominance. Dirk translates his experience in scaling South African businesses into high-velocity digital strategies for B2B and retail leaders. He writes about SEO, lead generation, and paid media from an operator's perspective — prioritising pipeline value over impressions.

Connect on LinkedIn