Updating Guild

Documentation scope: Guild 0.1.x pre-release builds. The exact public release version will be confirmed in the changelog before Theme Store publication.

This guide explains the safe update workflow for Guild after a new version is available.

Theme updates can include bug fixes, platform compatibility changes, new sections, setting improvements, documentation updates, and occasionally changes that require extra merchant review. Always test an update before publishing it on a live storefront.

Before you update

Before updating Guild:

1. Duplicate your current live theme.
2. Review the Guild changelog and release notes for the version you want to install.
3. Note any custom code, Custom HTML, Custom Liquid, app embeds, or app-specific styling added to the current theme.
4. Check whether the update mentions product forms, cart, collection filters, search, header navigation, localization, apps, media, or checkout handoff.
5. Schedule the update outside your busiest sales window when possible.

Custom code and app changes can make updates more complicated. If the issue only appears after custom code, app embeds, or modified theme files are added, test the update on an unmodified copy first.

Recommended update workflow

Use this workflow for routine updates:

1. Add the updated theme as an unpublished theme.
2. Keep the current live theme available as a rollback copy.
3. Open the updated theme in the theme editor.
4. Review key templates and section settings.
5. Reapply or adjust custom code only when it is still needed.
6. Test critical storefront paths.
7. Publish the updated theme only after review.

Do not edit the live theme directly when reviewing an update.

What to test after an update

At minimum, test:

• Home page layout and header navigation.
• Product page variant selection and Add to cart.
• Product media, external videos, 3D media, and image galleries where used.
• Collection page filters, sorting, pagination, Load more, or Infinite scroll where used.
• Blog post and collection cards, including Article thumb and Collection thumb images and any media-overlay content.
• Search and predictive search where used.
• Cart quantity updates, cart notes, checkout handoff, and empty-cart state.
• Contact forms, newsletter forms, popups, and announcement-style sections.
• Apps, app embeds, app blocks, and third-party widgets.
• Custom HTML, Custom Liquid, and custom code.
• Mobile layout and touch navigation.
• Country/language selectors when markets or multiple languages are enabled.

For stores with custom development, also test the custom code against the updated theme before publishing.

When an update may need extra care

Take more time to review an update when release notes mention:

• product forms, cart behavior, checkout handoff, quantity rules, selling plans, or gift cards;
• collection filters, search, predictive search, product cards, or Quick view;
• section or block setting changes;
• app blocks or app embeds;
• accessibility, focus handling, keyboard behavior, or modal behavior;
• external media, maps, videos, or browser storage;
• renamed, removed, or changed settings.

These changes are not automatically bad, but they can affect customizations, apps, and merchant workflows.

Custom code and updates

Custom code changes are outside standard Guild support unless support explicitly confirms otherwise. This includes edited theme files, Custom HTML, Custom Liquid, third-party snippets, external scripts, and code copied from tutorials.

Before publishing an updated theme:

• compare the custom code against the updated theme;
• remove custom code that is no longer needed;
• test product forms, cart, search, popups, and app-related areas after reapplying custom code;
• keep a record of what was changed and why.

If an issue appears after reapplying custom code, test the same page in an unmodified copy of Guild before contacting support.

Rollback guidance

Keep the previous live theme until the update has been tested on the live store. If a serious issue appears after publishing the updated theme, publish the previous theme again while you investigate.

When reporting an update-related issue, include the previous Guild version, the new Guild version, the affected URL, steps to reproduce, recent app or code changes, and whether the issue appears in an unmodified copy.

Documentation version

This guide applies to Guild 0.1.x pre-release builds. Each public release entry in the Changelog will identify the version-specific changes and any manual review steps.