Getting a change live

There are exactly two ways something reaches the live shop, and it is worth knowing which one you are using — because they take different amounts of time and only one of them needs a developer.

1. A change you make in the admin

Products, prices, descriptions, photos, metadata.

Save it in the Medusa admin and it is live within five minutes. Nothing to press, nobody to ask.

The shop re-reads the catalogue every five minutes rather than on every visit, so it stays fast and stays up even if the admin is briefly down. That five minutes is the whole delay.

If it has been longer than five minutes:

• Is the product Published?
• Is Glemor Online ticked under sales channels?
• Does it have an MYR price, and is that price greater than zero? The shop refuses a catalogue with a free product in it and quietly uses its built-in copy instead — so one unpriced product can freeze every product's edits.
• Try the page in a private window, in case your browser is showing you a cached copy.

2. A change to the site itself

Wording on the home page, a new section, a stockist, a bug fix.

That lives in code. A developer opens a pull request, it gets merged into main, and both apps redeploy themselves — the storefront to Vercel, Medusa to Railway. No one uploads anything by hand.

The wait is however long the deploy takes, usually a few minutes, and the release is recorded automatically: the version number, the tag, and both changelogs are generated from the commit messages. Nobody writes them. See What's New.

A quick map

The one thing worth double-checking

After any price change, open the live product page and read the price back. It is the one number on the site that is also a promise — the checkout charges exactly what the catalogue says.