Shopify Theme Upgrade Guide for Live Stores
Upgrading a Shopify theme on a store that already takes orders is a release, not a click. Merchants in the United States and Europe usually discover this the week after a sale, when a tracking pixel is gone, a size chart is blank, or an ad still points at a product handle the new template does not render. This guide is the sequence we use on devdiy.com when a store moves from an older theme onto a current DEVDIY theme, including Summit for wholesale catalogs. The same sequence works if you are only applying a minor update from the theme editor.
Treat the live theme as production. Duplicate it before you touch a setting. Shopify lets you keep several themes and publish one. The unpublished copy is your rehearsal. Do not edit the published theme “just to see.” Customers see it. So do the ads you cannot pause in the next ten minutes.
Decide if this is an update or a replacement
A minor update keeps your sections and tries to bring in bug fixes. A replacement is a new theme with a new information architecture. They fail in different ways. An update fails when a customized file blocks the merge and you accept the new file without reading the diff. A replacement fails when you copy the homepage and forget the product template, where the money is. Write one sentence at the top of the project: we are applying the vendor update, or we are moving to a new theme. If you cannot pick, you are doing both, and you should stop until you pick.
DEVDIY releases are meant to be installed as a new unpublished theme when the changelog mentions templates, not only color tokens. Read the changelog for three words: checkout, cart, and account. If any of them moved, schedule a full purchase rehearsal, not a visual glance. If the changelog is only spacing and a new section you do not need, you can still rehearse, but you do not need a weekend freeze.
Inventory what the new theme will not know
Open the theme code only long enough to list custom files. You are not hunting for elegance. You are listing anything a developer added: a delivery-date picker, a B2B price script, a Klaviyo form, a cookie banner required for EU visitors, a size guide in a metafield. Put each item on a row with the template it lives on and the person who owns it. Apps that inject code through the theme editor are easy to miss because they do not show up as a file you remember writing. In the admin, open each app that mentions “theme” and note whether it asks you to re-enable an embed after a publish.
Tracking is its own list. Google and Meta tags, server-side events, and the consent mode your EU lawyer asked for do not move themselves. A new theme can look perfect and still report zero purchases for two days. That is not a traffic problem. Export a baseline before the cutover: sessions, add-to-cart rate, and checkout completion for the last fourteen days. You will compare the first forty-eight hours against that baseline, not against a feeling.
Rehearse the purchase on the unpublished theme
Preview the unpublished theme and buy something with a real card you can refund, or with a test payment if your gateway allows it. Do this on a phone. Most US and EU sessions are not desktop. Check the product that has the most variants, not the simple one. Add a quantity. Apply a discount code your ads mention. Open the cart drawer and the cart page, because some themes use one and your emails use the other. Continue to checkout and confirm shipping rates for a domestic address and, if you sell into the EU, for a second country. If you use Shopify Markets, switch the market and confirm the currency symbol is the market’s, not a hardcoded dollar sign in a section.
Wholesale stores have extra steps. Create or use a company account. Confirm the logged-in price is the contract price, not the guest price. Try a quantity under the minimum. Request a quote if that is how large orders start. Summit keeps those regions in the product template so you are checking settings, not a one-off code snippet. If the price is wrong in preview, do not publish and “fix it live.” Fix it on the copy.
Click every link in the main menu and in the footer policy pages. Policy pages are where EU stores get into trouble when a theme update drops the link to shipping, returns, or privacy. Broken policy links are not a design issue. They are a reason a payment provider asks questions later.
Cut over, then watch the first two days
Publish during a quiet hour in the time zone where most orders originate. If you sell to both coasts of the United States and to the UK, pick the overlap when your support team is awake. Announce the freeze to anyone who edits products that morning. Theme publish does not lock the product admin, but a merchandiser changing a template suffix at the same minute will confuse the rehearsal.
After publish, repeat three checks, not thirty. Place one small order. Open the storefront from an ad link or a saved campaign URL. View one old blog or collection URL that sales still sends in email. If any of those fail, roll back to the previous theme. Rollback is a button. Pride is not a monitoring plan. Keep the previous theme installed for at least two weeks so you are not rebuilding from memory.
Redirects come next, not first. If the new theme changed a handle, add a redirect from the old path. Do not “clean up” handles because they look dated. External sites, marketplaces, and PDF line sheets still use them. On devdiy.com we leave handles alone unless a lawyer or a product rename forces the change, and then we redirect on the same day.
For the next forty-eight hours, compare the baseline. A small dip in conversion can be noise. A drop to zero purchases with normal sessions is a broken button or a broken pixel. Check the theme editor embeds, then the checkout extensibility apps, then the payment method. Do not start a redesign while you are debugging a release. Write what broke, fix that, and put the note in the changelog your team actually reads.
The stores that upgrade calmly are the ones that decided, in writing, what “done” means: one real order, one market, one logged-in price, one ad landing, and a baseline that still looks like a store. DEVDIY themes, Summit included, are built so those checks sit on templates you can preview. Use the preview. The live theme can wait an afternoon.
