> For the complete documentation index, see [llms.txt](https://staylime.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://staylime.com/docs/theme-companion/theme-updates/understanding-your-update-summary.md).

# Understanding your update summary

After the app merges your theme with the new version, it shows the result as an update summary: what carried over on its own, what needs your attention, and how to proceed. You can leave this screen and come back anytime — your progress is saved for the entire 30-day update window.

What the summary shows depends on what the merge found.

### If nothing conflicts: ready to finish

When every customization carried over automatically, the summary says so — there are no decisions to make. Preview the theme to check that everything looks right, then finish the update.

<figure><img src="https://1681854268-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUyDyU30RpMsjQtm2Gbnm%2Fuploads%2FIDYEGJHYRRUU3qfYOD5x%2FScreenshot%202026-08-19%20at%2017.01.19.png?alt=media&#x26;token=811ec026-5472-47c0-b255-74ab4f17c035" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Right after the merge, **Preview theme** and **Finish update** stay disabled for a short while — the app is adding the preview theme to your Online Store. They become available as soon as it's ready.
{% endhint %}

### Files with conflicts

Files where your customizations and the new theme version changed the same code. Each conflict needs your decision, and the summary offers three ways to make them:

* **Apply new theme changes** — the fastest option. Your customizations are already applied everywhere they could be; in the remaining conflict areas, the new version's code is used.
* **Review conflicts manually** — go through each conflict and decide what to keep. You only see the places that need your attention — everything else is already resolved. See [Resolving conflicts](/docs/theme-companion/theme-updates/resolving-conflicts.md).
* **Get expert help** — the Staylime team completes the update for you at a fixed price. See [Get expert help](/docs/theme-companion/theme-updates/get-expert-help.md).

Once every conflict is resolved, the section is renamed to **Files with resolved conflicts**.

<figure><img src="https://1681854268-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUyDyU30RpMsjQtm2Gbnm%2Fuploads%2FPOpnoyz8cJgLEHqvCbpC%2FScreenshot%202026-08-19%20at%2018.12.38.png?alt=media&#x26;token=9f0703d0-e7bd-4f2d-b12d-0664fd60d3df" alt=""><figcaption></figcaption></figure>

**Files marked "Blocks preview".** In these files, the code has diverged too much for the theme to be assembled until their conflicts are decided — so **Preview theme**, **Finish update**, and **Apply new theme changes** stay unavailable until you resolve them. If several files carry this badge, you're looking at a heavy update: a good moment to consider [Get expert help](/docs/theme-companion/theme-updates/get-expert-help.md).

<figure><img src="https://1681854268-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUyDyU30RpMsjQtm2Gbnm%2Fuploads%2F2QaKiyPhT4m28JTWXlzP%2FScreenshot%202026-08-19%20at%2018.15.03.png?alt=media&#x26;token=8fad1724-d016-43da-b60d-cc746361deb1" alt=""><figcaption></figcaption></figure>

### Files with customizations not present in the updated version

This section appears only when the update runs into it: files you customized that the new theme version no longer includes. The vendor restructured the theme, so there is nothing to merge these files with. They are kept in your updated theme untouched — but the new version may no longer load them, so their effect can quietly disappear.

After the update, check the storefront pages these files affected — especially the ones you customized heavily. If a customization from one of these files matters to you, it needs to be re-applied in the new version's structure: see [When conflicts get hard](/docs/theme-companion/theme-updates/when-conflicts-get-hard.md) for your options, including [Get expert help](/docs/theme-companion/theme-updates/get-expert-help.md).

<figure><img src="https://1681854268-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUyDyU30RpMsjQtm2Gbnm%2Fuploads%2FsrPZw1vx0ryZwLJjekTe%2FScreenshot%202026-08-19%20at%2018.17.38.png?alt=media&#x26;token=ff5ddc74-fa0f-481e-b4c2-e2cee1d9afaf" alt=""><figcaption></figcaption></figure>

### Successfully updated files with customizations

Files where your customizations were carried over automatically, with no overlaps. Nothing to do here — the list exists so you can see exactly what moved. It also includes files you added to the theme yourself (such as `robots.txt.liquid`): they are carried over as-is.

### Some files couldn't be prepared for update

A red banner that can appear while you work through conflicts: during the merge, some files developed structural issues that Shopify would reject, and **Preview theme** and **Finish update** are unavailable until they're fixed. The **Fix rejected files** button opens a screen built for exactly this — see [Fixing rejected files](/docs/theme-companion/theme-updates/fixing-rejected-files.md).

<figure><img src="https://1681854268-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUyDyU30RpMsjQtm2Gbnm%2Fuploads%2FZQQ1KP4rHEi8tkfdQqZK%2FScreenshot%202026-08-19%20at%2018.21.05.png?alt=media&#x26;token=3ecd56f5-ae07-4c3a-93b4-01e9d43041be" alt=""><figcaption></figcaption></figure>

***

Once every conflict is resolved and any rejected files are fixed, the update is ready to finish: preview the result, then finish the update.

Whatever the summary shows along the way, your live theme stays untouched: you can cancel the update at any point, and nothing is published until you decide.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://staylime.com/docs/theme-companion/theme-updates/understanding-your-update-summary.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.