Changes are not showing after you edit a product

Check the saved design, selected store, and publication update before troubleshooting a stale storefront page.

You edited a product in the Design Studio, but the storefront still shows the old version. This guide helps you push the change live and explains the short delay you sometimes see. It is for any merchant who has just changed a template and wants it reflected on the store.

Start with the publication: saving a design does not update an existing storefront publication by itself.

Save and check the publication update

The storefront only shows what you have saved and published. An open edit you have not saved yet is not on the store. Follow these steps in order.

Save the template in the Design Studio

Save your work in the Design Studio. Saving writes the change as a new version of the design. Until you save, the edit lives only in your editor and shoppers never see it. The button in the top bar is both the action and the status: it reads Save while there is something to write, and settles back to Saved with a check once the version is stored.

DashboardThe Design Studio top bar with an unsaved edit, showing Save between the undo controls and Preview
Save sits in the top bar, left of Preview. It reads Save while an edit is waiting.

Republish the product

Open the product and use its update action for the existing publication. Confirm the intended store and design changes, then check the result. A saved-but-unpublished change will not appear on the store. See publish a product to your storefront for the distinction between first publication and updating an existing one.

Every link looks finished from the one before it. That is what makes this hard to spot.

Check the update result

Confirm that the publication update completed for the store and product URL you are checking. If it failed or is still pending, waiting or refreshing the storefront does not complete it.

Hard refresh the product page

Reload the published product page. You can also try a hard refresh using your browser’s reload controls. A refresh can help diagnose stale browser resources, but it does not publish a design or guarantee that every cache has been cleared.

How the storefront checks for an update

The storefront mapping loader rechecks the product mapping on each new sequential load. Concurrent requests share one request, and stored mapping data is tied to a specific publication revision. There is no fixed 60-second browser timer that publishes your edits. An already open customizer can still be using the publication it loaded.

If a new visit still shows old content after a successful update, record the product URL, selected store, update result and time. Check these details before treating the problem as a cache delay or publishing repeatedly.

Frequently asked questions

I edited the template but the store looks the same. What do I do?

Save the design, update the existing publication for the intended store, check the result, then reload the published product page.

How long until changes go live?

First confirm that the publication update succeeded. Saving alone does not change the storefront; there is no universal one-minute delivery guarantee.

A different shopper still sees the old version. Why?

Compare the exact product URL and selected variant, and ask them to open a fresh visit. An existing customizer may still hold an earlier publication. If the mismatch persists, send support the publication result and both observations.

Next, learn how publishing works end to end in publish a product to your storefront.

Related articles