FragranceAllergenKit is installed

Put the fragrance allergen declaration on your product pages, as clear colour-coded badges instead of a wall of INCI names. You type what your supplier's certificate says; the app lays it out. No code required.

Enter the declaration on the product

Open the product and scroll to Product metafields. The four fields are already there (created automatically).

`frag_allergens`	`linalool, limonene, citral, geraniol, coumarin`
`frag_type`	`leave_on` or `rinse_off`
`frag_free_claims`	`phthalate_free, cruelty_free, vegan`
`frag_notes`	Anything you want to add, one line each

Names are matched loosely, so Linalool, linalool and LINALOOL all work, and a name the app does not recognise is still shown — just without its explanation. Save.

Open products

2

Add the block to the product template

In the theme editor, use the page selector at the top and choose Products › Default product. Click Add block and choose Fragrance Allergens. Save. Important: the block shows product data, so it must live on the product template — not the home page.
Open Theme Editor
3

Check the product page

Open the product's page in your online store: the panel appears automatically. Products with none of these fields filled in show nothing — the rest of your catalogue is unaffected.

Why buyers look for this

In the EU, Annex III of Regulation (EC) No 1223/2009 lists fragrance substances that have to be named individually on a cosmetic product. Commission Regulation (EU) 2023/1545 raises that list from 24 substances to more than 80, with 31 July 2026 for products newly placed on the market and 31 July 2028 for products already on it. A substance is named once it is above 0.001% of a leave-on product or 0.01% of a rinse-off one. Online, none of that is readable before the box arrives — which is why shoppers who react to one of these substances ask in messages before ordering.

You write the declaration, not the app

The app never decides what is in your product and never adds a substance you did not enter. It formats the names you list, adds one plain sentence saying what each substance is and where it comes from, and groups them by scent family so the colours mean something. Everything else on the panel is yours.

The colours

Each badge is coloured by scent family — citrus, floral, spice, woody, balsamic, fresh — with a legend underneath, so a shopper sees the character of the perfume before reading a single name and can spot the family they react to at a glance. “Free from” badges are green, and the two lists are deliberately different colours because they mean opposite things. Amber rather than red for the declared list: a declared allergen is information, not a hazard warning.

Metafield reference

`custom.frag_allergens`	The fragrance substances declared for this product, comma separated INCI names, e.g. "linalool, limonene, citral"
`custom.frag_type`	leave_on or rinse_off — decides which declaration threshold the panel mentions
`custom.frag_free_claims`	Comma separated, e.g. "phthalate_free, cruelty_free, vegan"
`custom.frag_notes`	Optional extra lines, one per line, e.g. where the allergen data comes from

FragranceAllergenKit helps you present a fragrance allergen declaration on your product pages; it is a display tool and not legal advice, and it does not check, analyse or classify any product. What you enter, and whether your labelling meets the rules in your markets, is your responsibility.