Prop 65 comparison

Prop 65: native product disclosures vs an approval and audit-log app

On 17 June 2026, product Disclosures became native, with types cancer, reproductive, both, and alcohol. Shopify can show a warning. The gap is not “Shopify cannot show a warning.”

OEHHA: the old short-form warning is still a safe harbor for products manufactured before 1 January 2028. The chemical name is the wedge for products manufactured on or after that date, plus an approval and audit trail. Chemical names did not become mandatory in January 2026.

Install Prop 65 Warning Manager

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. Also on the product page: CLP hazard display · EU food information.

What native Disclosures already cover

Use native Disclosures — or a metafield the theme already prints — when a typed notice is enough and your team already has a publish process you trust.

Native product Disclosure types (since 17 June 2026)
Type What it is for
cancer Cancer endpoint notice
reproductive Reproductive-harm notice
both Cancer and reproductive-harm notice
alcohol Alcohol notice

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 and metafields vs approval + audit log
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 this page means. Audit log of the warning text you attached and published per product.

Native Disclosures already show a typed notice (cancer, reproductive, both, alcohol). They do not keep an approval trail, and they do not insert the OEHHA chemical name for products manufactured on or after 1 January 2028. Those two are the app wedge — not “Shopify cannot show a warning,” and not a January 2026 chemical-name mandate.

When to stay native, when to add the app path

The app helps display and document warning content you choose. It does not decide whether an exposure requires a warning. This page is not legal advice.

Install, attach the short-form, approve, keep the log

  1. Open the Prop 65 Warning Manager listing and install it on the store that sells into California.
  2. Pick a short-form template that already includes a chemical-name placeholder. Use the list name of a chemical you are actually warning for.
  3. Attach it to one product. Review and approve before go-live.
  4. Confirm the live product page, then keep the audit record of what published.

This page does not add prices. Confirm plan details on the live listing.

Install Prop 65 Warning Manager

What this page is not

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. You can also put warning text in a metafield and render it on the theme. Shopify can show a warning. An app is not the only way. Sources disagree on whether that native text also appears at cart and checkout; confirm your theme.

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 this as “Shopify cannot show a warning.”

Do I have to use an app to name a listed chemical?

No. You can type a chemical-identifying short form into native disclosures or a metafield. The app path is useful when you want a placeholder template, a review-and-approve step, and a record of what went live on which product. It 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. Neither native disclosures nor an app certifies that a method is clear and reasonable. This page is not legal advice and does not guarantee compliance.

Where do I attach a cited short-form with an audit log?

Prop 65 Warning Manager is the App Store listing this site already uses 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 this page.

Install Prop 65 Warning Manager

Related pages

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.