Adding and editing a product
The Medusa admin is the catalogue. What each field does, and which ones the shop actually reads.
Everything a customer sees on a product page comes from the Medusa admin at glemor-admin.cenvora.dev/app. Sign in, open Products, and pick a scent — or press Create for a new one.
Prices are in ringgit
Type the price the way you would say it. RM108 is 108. Not 10800, not 108.00.
The one mistake that matters
A price typed as 10800 puts a RM10,800 bottle on the live shop, and a customer who
reaches checkout is charged that. Nothing in between catches it. Read the price back
after you save it.
The currency must be MYR. Every product needs a price in the Malaysia region; the shop refuses to display a catalogue where anything costs nothing, and falls back to its built-in list instead — so a missing price shows up as "my edit did not appear" rather than as an error.
The fields the shop reads
Everything else in the admin is real, but these are the fields that change what a visitor sees.
| Field in the admin | Where it shows up |
|---|---|
| Title | The product name, everywhere |
| Handle | The web address — handle woody-muse becomes /shop/woody-muse |
| Description | Two parts, see below |
| Thumbnail | The product photograph. See Product photography |
| Price (MYR) | The price on the card, the product page and the checkout |
| Status | Must be Published |
| Sales channels | Must include Glemor Online |
Description is two things in one box
The first paragraph is the short line under the product name on the shop grid. Then leave a blank line, and everything after it becomes the longer story on the product page.
Sun-bleached driftwood softened by a handful of white flowers.
Glemor shot this one on pale driftwood, white petals scattered across the grain.
The composition reads that way too — dry and grounded first, then something
quietly floral opening underneath.Without the blank line, the whole thing becomes the short line and the product page loses its story.
Metadata — the fields that make it look like Glemor
Scroll to Metadata on the product. These are key-and-value pairs, and the shop reads seven of them. Spelling matters: a mistyped key is silently ignored and the shop uses a default.
| Key | What to put | What it does |
|---|---|---|
series | premium, daily or set | Which series the product is filed under. Anything else is treated as daily |
ml | 30, 15, 5 | The bottle size shown next to the price |
family | e.g. Woody Floral | The scent family label on the product page |
accent | a hex colour, e.g. #6B5A48 | Tints the generated visual for that scent. Sampled from the product's own photography |
notes | see Scent notes | The notes pyramid |
verified_notes | true or false | Whether the "notes are indicative" line appears |
sold | a number | The quiet "sold" count |
rating | a number | The rating shown on the card |
accent is not a brand colour
The accent tints one product's generated visual and nothing else. It is never a button, a background or a piece of text. The shop has exactly one accent colour — the antique gold — and adding a second one is the fastest way to make the site stop looking like Glemor.
Adding a new scent, in order
- Products → Create. Title and handle. Keep the handle lowercase with hyphens.
- Description — short line, blank line, story.
- Add a variant with the size as its option (
30ml,15ml,6 × 5ml) and a MYR price in ringgit. - Sales channels — tick Glemor Online. A product that is not in the channel does not exist as far as the shop is concerned.
- Metadata — the keys in the table above.
verified_notesisfalseunless someone has actually confirmed the notes. - Status → Published.
- Wait five minutes and check the live shop.
Taking a product off sale
Set Status to draft, or untick Glemor Online. Either one removes it from the shop within five minutes. Do not delete it — a deleted product takes its history with it, and its web address starts returning a "not found" page to anyone who saved the link.