CLP hazard pictograms on the product page
CLP hazard pictograms belong on the product page, not only on the parcel
Job: show CLP/GHS hazard pictograms and statements on the product page for distance-selling offers of hazardous substances and mixtures, before purchase. A pack shot on the parcel path is a different surface.
Create a hazard profile (pictograms + H/P statements), review missing fields, sync to the storefront, then confirm the live PDP. The app stores and displays content you enter. It does not classify the mixture. Not legal advice.
Install, attach hazard info, confirm the live product page
The paid path is hazard information visible on the product page, not a backend note staff forget to open.
- Install CLPLens (CLP Hazard Info Display) from the App Store.
- Attach the hazard display to the product this guide covers.
- Open the live product page and confirm the hazard info renders where buyers see it.
- Keep the in-app record of what you attached before you roll out to the next SKU.
The app helps display hazard content you configure. It does not classify substances for you. This page is not legal advice.
Install CLPLens → attach hazard display → confirm live product page
Demo
Short walkthrough of the app flow. Then follow the start path below.
A gallery photo is not a CLP label on the offer
| Surface | What the shopper gets before buy |
|---|---|
| On-pack CLP label | Pictograms, signal word, H- and P-statements on the unit |
| Gallery / pack shot only | Often unreadable; not structured statements |
| SDS in a footer | After-the-fact download - not the offer itself |
| Product-page hazard block (this page) | Same pictograms and statements as the profile, before purchase |
Do not mix with Prop 65 (California chemical-name short form) or EU food allergen labelling - different templates.
Suggested path:
- Install CLPLens: CLP Hazard Display.
- Create product hazard profiles with GHS pictograms and the statements already on the label/SDS.
- Review missing fields before publish; sync app-owned metafields to a theme block when that path is live on the listing.
- Confirm the live PDP matches the profile. Keep the audit record.
Example profile fields (paraphrase, not a classification):
signal word
GHS pictograms
hazard statements (H…)
precautionary statements (P…)
supplemental information as on the labelWhat this page is not
- Not legal advice, a classification service, or a compliance certification.
- Not a California Prop 65 warning. That job is 2028 product-page short-form warnings.
- Not EU food allergen labelling. That path is allergen info before purchase.
- Not an EU textile fibre name check. That job is Annex I fibre composition.
- Not CRA product duty / Article 14 incident records. That path is Cyber Resilience Act duty files.
Do CLP/GHS hazard pictograms have to appear on the product page?
For distance selling of hazardous substances and mixtures, shoppers need the CLP label elements before they buy — not only on the parcel. That set includes GHS pictograms, signal word, hazard and precautionary statements as they apply to the product. This page is not legal advice. Confirm Regulation (EC) No 1272/2008 as amended, including online-offer rules, not this paraphrase.
Is a photo of the bottle enough?
A pack shot can be unreadable on a phone and can omit statements the label requires. The job on this page is a structured hazard profile (pictograms + statements) shown on the product page, with missing fields reviewed before you publish. Do not treat a gallery image as the label.
Does an app classify the mixture or write the SDS?
No. Classification, labelling, and the safety data sheet are legal facts you already have (or your supplier has). A listing can store a hazard profile, sync it to a theme block via app-owned metafields, and keep an audit record of what you published. It does not decide the hazard class.
Is this the same as a California Prop 65 warning?
No. Prop 65 is a California safe-harbor warning with a listed chemical name. CLP is EU classification and labelling with GHS pictograms. Do not copy a Prop 65 short form onto a CLP product page, or the reverse.
Is this the same as EU food allergen labelling?
No. Food information (Regulation (EU) No 1169/2011) is a different pre-purchase job: Annex II allergens, nutrition, origin. CLP covers hazardous substances and mixtures. A food SKU and a detergent SKU do not share a label template.
What should I review before the hazard block goes live?
Missing pictograms, signal word, hazard statements, and precautionary statements relative to the profile you intend to show. Create the profile first; metafield sync to the storefront is a later step on the listing. Check the live product page after sync. Keep the audit record of what you published.
Where do I put CLP/GHS pictograms on the product page?
Create a product hazard profile with GHS pictograms and statements, review missing fields, then sync app-owned metafields to a theme block. CLPLens: CLP Hazard Display is the App Store listing this site already uses for that job. Open the listing, install, build the profile, then confirm the live product page. It is not a compliance certification.
Related pages
- CLPLens: CLP Hazard Display — live App Store listing
- Cyber Resilience Act duty records — product cybersecurity duties / ENISA drafts, not GHS pictograms
- EU food allergen labelling before purchase
- EU textile fibre composition label
- Prop 65 2028 product-page warning
- Shopify apps hub
- Tools
Not legal advice. Not a classification or SDS service. Confirm CLP as amended before you treat a product page as in or out of scope. The app displays hazard content you enter.