Changes are not showing after you edit a product

Edits in the Design Studio not appearing on your store? Save and republish, then wait up to a minute for the storefront cache, or hard refresh.

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.

Most of the time the fix is two actions: save, then republish. After that, a short cache means the change appears on its own within about a minute.

Save and republish, then wait a minute

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.

Save to write your edit as a new version.

Republish the product

Open the product and republish it. Republishing tells the storefront to use the new version you just saved. The store always serves the last published version, so a saved-but-unpublished change will not appear yet.

Republish so the storefront picks up the new version.

Wait up to a minute

Give it up to a minute. The storefront keeps a copy of the product mapping for 60 seconds per visitor, so the page can show a slightly older version for that short window. The new version then loads on the next visit.

Hard refresh the product page

Hard refresh the product page to clear the copy your own browser is holding. On most browsers, hold Shift and click the reload button. This forces a fresh load instead of the cached page.

Why a change can lag for a few minutes

A short delay after you publish is normal. Composerie keeps the storefront fast by caching the product mapping in two places.

The first is a 60 second cache held per visitor in the browser. It skips a network call on quick page reloads within the same visit. After 60 seconds it expires and the next load fetches the current version.

The second is a short edge cache that sits in front of the mapping. It can serve a slightly older response for a few minutes while it refreshes in the background. You do not need to do anything: the change rolls out on its own.

There is one more case. Right after a Composerie release, a product page may quietly reload itself once. That happens when the page booted with an older cached version of our storefront code and then corrects itself to the newest one. It is a single reload, and the page comes back on the current version.

If you have waited several minutes, hard refreshed, and the old version is still showing, see common issues or check that the product is actually published in publish a product to your storefront.

Frequently asked questions

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

Save the template in the Design Studio, then republish the product. Wait up to a minute and hard refresh the product page by holding Shift and clicking reload.

How long until changes go live?

Usually within a minute for you. Through the edge cache it can take up to a few minutes before everyone sees it.

A different shopper still sees the old version. Why?

Their browser is holding the 60 second cache. It clears within a minute. You can also ask them to hard refresh the page.

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

Related articles