Prop 65 comparison
Prop 65: native product disclosures vs an approval and audit-log app
Prop 65 Warning Manager (Shopify App Store) is a Shopify app that publishes Prop 65 product-page warnings from templates citing 27 CCR §§ 25601–25607, including 2028 short-form text that names a listed chemical, and requires merchant approval before any warning goes live, with an audit log of every pick, edit and activation.
Free check first: Prop 65 warning question check runs in your browser and sends nothing. Describe a product and see which list names and 27 CCR warning rules to read.
Which Shopify app adds a Prop 65 warning with an approval step?
Native Disclosures (17 June 2026) show typed notices (cancer, reproductive, both, alcohol) on the product page and cart; checkout needs a Checkout UI extension (Shopify product disclosures).
Prop 65 Warning Manager adds a chemical-name template for the 2028 short form, a merchant approval step, and an audit log.
It does not decide whether an exposure requires a warning. Not legal advice.
On 17 June 2026, product Disclosures became native, with types cancer, reproductive, both, and alcohol, so Shopify can show a warning and the gap is not “Shopify cannot show a warning.” OEHHA still treats the old short-form as a safe harbor for products manufactured before 1 January 2028.
The chemical name is the wedge for products manufactured on or after 1 January 2028, plus an approval and audit trail. Chemical names did not become mandatory in January 2026.
Live listing: apps.shopify.com/momiji-prop-65-warning-manager. Attach a short-form template, approve it, then confirm the live product page. Not legal advice.
2028 how-to: chemical name on the product-page short form. Product-page steps: How do I add a Prop 65 warning to a Shopify product page?. Also on the product page: CLP hazard display · EU food information.
What native Disclosures already cover
Native Disclosures already cover typed notices for cancer, reproductive, both, and alcohol since 17 June 2026. A merchant can put Prop 65 wording on the product page without installing an app, or type a listed chemical name into a metafield the theme already prints, when a typed notice is enough and the team already has a publish process to trust.
| Type | What it is for |
|---|---|
| cancer | Cancer endpoint notice |
| reproductive | Reproductive-harm notice |
| both | Cancer and reproductive-harm notice |
| alcohol | Alcohol notice |
- You can put Prop 65 wording on the product page without installing an app.
- You can type a listed chemical name into that text yourself if you need it.
- Sources disagree on whether that native text also appears at cart and checkout. Confirm the live product page, cart, and checkout on your theme. The Prop 65 comparison does not resolve that disagreement.
If a typed native Disclosure is the whole job, stop here. Do not install for “a place to put warning text.”
What an audit-log app still does that native disclosures do not
Native Disclosures already show a typed notice (cancer, reproductive, both, alcohol) but do not keep an approval trail and do not insert the OEHHA chemical name for products manufactured on or after 1 January 2028. Those two jobs are the app wedge — not “Shopify cannot show a warning,” and not a January 2026 chemical-name mandate.
| Job | Native disclosures / metafields | Approval + audit-log app |
|---|---|---|
| Show a warning on the product page | Yes. Native Disclosures (cancer, reproductive, both, alcohol) since 17 June 2026, or a metafield the theme renders. | Yes, as one of several ways. Not the only way. Shopify can already show a warning. |
| Chemical name on the OEHHA short-form (manufactured on or after 1 Jan 2028) | Only if you write that sentence yourself. Native types do not insert the list name. Old short-form remains a safe harbor for goods manufactured before that date. | Short-form templates with a chemical-name placeholder for goods manufactured on or after 1 January 2028, plus the audit trail. |
| Approval trail before go-live | Depends on whoever can edit the product. No dedicated approve step. | Review and approve warning content before it goes live on the storefront. |
| Audit log of what published | Product history is not the warning-text log the Prop 65 comparison means. | Audit log of the warning text you attached and published per product. |
When to stay native, when to add the app path
Stay on native disclosures or metafields when one editor pastes the same sentence the label already uses and a later log is not needed. Use the app path when several people can edit products, a go-live approval is required, or a dated chemical-name short-form row is needed. Prop 65 Warning Manager does not decide whether an exposure requires a warning.
- Stay on native disclosures or metafields when one editor pastes the same sentence the label already uses, and you do not need a later log of that paste.
- Use the app path when several people can edit products, you need a go-live approval, or you want a dated row of the short-form that named the chemical.
Prop 65 Warning Manager helps display and document warning content the merchant chooses. The Prop 65 comparison is not legal advice.
Install, attach the short-form, approve, keep the log
A merchant attaches a cited short-form with an audit log by installing Prop 65 Warning Manager on the store that sells into California, picking a short-form template that already includes a chemical-name placeholder, attaching the template to one product, approving before go-live, and confirming the live product page.
- Open the Prop 65 Warning Manager listing and install it on the store that sells into California.
- Pick a short-form template that already includes a chemical-name placeholder. Use the list name of a chemical you are actually warning for.
- Attach it to one product. Review and approve before go-live.
- Confirm the live product page, then keep the audit record of what published.
The Prop 65 comparison does not add prices. Confirm plan details on the live listing.
Install Prop 65 Warning Manager
What the Prop 65 comparison is not
The Prop 65 comparison explains native product Disclosures versus an approval and audit-log app. The comparison is not a claim that the app is the only way to show a warning, not legal advice, not a compliance certification, and not a decision about whether a product requires a warning.
- Not a claim that the app is the only way to show a warning.
- Not legal advice, a compliance certification, or a guarantee that any warning method is “clear and reasonable.”
- Not a decision about whether a product requires a warning at all.
- Not the full 2028 date table. That lives on the product-page short-form guide.
Can native Shopify product disclosures show a Prop 65 warning?
Yes: on 17 June 2026, product Disclosures became native, with types cancer, reproductive, both, and alcohol, and a merchant can also put warning text in a metafield and render it on the theme. Shopify can show a warning, so an app is not the only way; sources disagree on whether that native text also appears at cart and checkout.
What does an approval and audit-log app still do that native disclosures do not?
OEHHA still treats the old short-form as a safe harbor for products manufactured before 1 January 2028. The app wedge is a chemical name on the short-form for products manufactured on or after that date, plus a merchant approval trail and audit log. Chemical names did not become mandatory in January 2026. Native Disclosures already show a typed notice. Do not frame the app path as “Shopify cannot show a warning.”
Do I have to use an app to name a listed chemical?
No: a merchant can type a chemical-identifying short form into native disclosures or a metafield when a placeholder template, a review-and-approve step, and a record of what went live are not required. The app path is useful when those controls are needed; Prop 65 Warning Manager does not decide whether an exposure requires a warning.
Does either path make the product page Prop 65 compliant?
No: warning content is a legal choice, and neither native disclosures nor an app certifies that a method is clear and reasonable. The Prop 65 comparison is not legal advice and does not guarantee compliance; confirm 27 CCR Article 6 and the live OEHHA materials before publishing warning copy.
Where do I attach a cited short-form with an audit log?
Prop 65 Warning Manager is the App Store listing already used on momiji-space for product-level short-form templates, approval before go-live, and an audit log of what published. Open the listing, install, attach a chemical-name short form, approve it, then confirm the live product page. Confirm live listing text, not the Prop 65 comparison.
Related pages
- Prop 65 storefront activation audit — go-live activation record vs theme copy
- Prop 65 2028 product-page warning — chemical-name short form and label dates
- Prop 65 on the cart vs product page — cart display is not an approval desk
- California-only / US-CA Prop 65 — jurisdiction on structured Disclosures, not an IP pop-up
- Prop 65 alcohol disclosure type — wine, beer, spirits use the alcohol type, not cancer / reproductive
- Prop 65 Warning Manager — live App Store listing
- Reviewer screencast
- CLP hazard product-page guide
- Block PO Box on billing
- Shopify apps hub
- Tools
Not legal advice. Not a compliance guarantee. Confirm 27 CCR Article 6 and the live OEHHA materials before you publish warning copy. Native Disclosures can show a warning (cancer, reproductive, both, alcohol). The old short-form remains a safe harbor for products manufactured before 1 January 2028. The app wedge is the chemical name for goods manufactured on or after that date, plus an approval and audit trail.