Products / New Feature

Product "Disclosures" Field
The end of burying warning notices inside product descriptions

Statutory and optional notices such as Prop 65 or choking hazards can now be registered as structured data (metafields) in a dedicated field in the Shopify admin, instead of being mixed into product descriptions or theme code.

On this page
  1. What's actually changing (understand it in 30 seconds)
  2. How it works: the flow from input to display
  3. Available disclosure types
  4. Old approach vs. the new field
  5. Theme support and fallback
  6. Three steps to get started
  7. Five points developers should know
  8. Three use cases you can apply to your business
  9. A one-line summary for your pitch

1What's actually changing

Until now, notices such as Prop 65 warnings were product descriptions, theme code, or custom workarounds stored by embedding them in.
From now on, you can register them directly as structured data in the dedicated "disclosures" field in the Shopify admin.

Old way: mixed into descriptions and code

Warnings were written into product descriptions, theme code, or custom workarounds. They couldn't be handled as data, making them hard to reuse or search.

New way: structured in a dedicated field

Stored as a product metafield. They can be managed with types (Prop 65, choking hazard, custom), and on supporting themes they appear automatically in a dedicated section.

2How it works: the flow from input to display

Admin Enter a disclosure Choose a type Merchant Product metafield As structured data Linked to and saved on the product Stored on Shopify's side Supporting theme On the product page Automatic "Disclosures" display Unsupported / custom storefront Reference the metafield and render manually What buyers see ⚠ Disclosures Product detail page
Key point : Data (metafields) and presentation (theme) are kept separate. On a supported theme, just enter the values and they appear in the "Disclosures" section. Even on unsupported themes or custom storefronts, you can access the metafield and render it yourself.

3Available disclosure types

Built-in

California Prop 65 warning

A warning notice based on California Proposition 65. Provided as a dedicated type.

Built-in

Choking hazard

A caution notice about choking risks from small parts and similar items. This is also available as a built-in type.

Custom

Custom disclosure type

Freely add your own type for product-specific warnings or notices beyond those above.

Where responsibility lies : Deciding which disclosures are required and what they should say is the merchant's own responsibility. Shopify only provides the container (the field); it does not guarantee whether a disclosure is needed or that its wording is correct.

4Old approach vs. new field

ItemOld (workaround)Disclosures field
Storage location Mixed Product description, theme code, custom workarounds Dedicated Product metafield
Data structure Unstructured (buried in free text) Structured Managed with assigned types
Predefined types Hand-built Prop 65 and choking hazard provided built-in
Display Modify the theme each time Automatically shown in the "Disclosures" section on supported themes
Reuse and reference Difficult Can be referenced from APIs and custom frontends via metafields

5Theme support and fallback

Supported Online Store themes

When you enter disclosures, they automatically appear as a new "Disclosures" section on the product detail page. No extra implementation is needed on the theme side.

Unsupported themes and custom storefronts

You need to access the disclosure metafields and render them yourself. The data is available, so you only need to provide the rendering logic.

The way you enter the data is the same.Only the display method branches based on the theme's support status. If you first enter it in the admin, you can later enable the display simply by switching to a supported theme.

63 steps to get started

1

Open a product

Open the target product page in the Shopify admin.

2

Choose a disclosure type

Select Prop 65, choking hazard, or your own custom type.

3

Enter the content and save

Enter the body of the notice. On supported themes it appears automatically on the product page.

For details on the exact location of the settings screen and the operation steps, see the Shopify Help Centerin the relevant guide. This article does not include step-by-step instructions for each screen.

75 points developers should know

meta

1. It's really a product metafield

Disclosures are stored as product metafields. This means you can design around referencing and retrieving them via the Admin API / Storefront API.

Predefined Custom

2. Two types: built-in and custom

Prop 65 and choking hazard are built-in types; anything else is a custom type. The design uses different types depending on requirements.

3. Data and display are separated

Supported themes render automatically, while unsupported themes and custom frontends render manually. Whether you maintain your own display logic determines your frontend implementation approach.

4. Deciding what's required is the merchant's responsibility

Determining which disclosures are needed and whether the wording is appropriate is up to the merchant. The system does not validate this, so you need to design operational rules and a review process separately.

5. Room to migrate from the existing "embed in description" approach

Stores that have been writing warnings in product descriptions or theme code can structure them by moving that content into the dedicated field.When migrating, watch out for duplicate display (showing it both in the description and the Disclosures section), and it's safest to proceed together with removing the old text. The specific API field names and schema are not described in this article, so check the Help Center / API documentation.

83 use cases for your business

Prop 65
USE CASE 1

Centrally manage Prop 65 warnings for U.S. sales as "product data"

Challenge
California Prop 65 warnings have until now been hand-written at the end of product descriptions or inside theme code, which makes it easy to miss products or end up with inconsistent wording.
Solution
Move to the built-in Prop 65 disclosure type and register it as a field on the relevant products. On supported themes, it displays consistently in the Disclosures section.
Impact
Warning management is consolidated into the product data, ensuring consistent wording and making it easier to check for omissions.
Technical notes
Because it becomes a metafield, you can design workflows that pull a list of affected products or run audits via the API.
Note A Note B Note C
USE CASE 2

Standardize product-specific notices for toys, food, cosmetics, and more with custom types

Challenge
Notices required by category—choking hazards, allergens, usage precautions, and so on—are written inconsistently across products, making them hard to standardize brand-wide.
Solution
Use the built-in type for choking hazards and define custom disclosure types for the rest, turning them into per-category operational rules.
Impact
You can standardize the "template" for notices internally, so it serves as an input guideline when registering new products.
Technical notes
Designing the naming and granularity of custom types up front makes later aggregation and conditional front-end display much easier.
Custom Front end
USE CASE 3

Implement disclosure display on headless / custom storefronts

Challenge
On custom storefronts like Hydrogen or on unsupported themes, you want to surface each product's legal and optional notices consistently.
Solution
Fetch the disclosure metafields and render them yourself as a dedicated Disclosures component on the product detail page.
Impact
Data entry stays consolidated in the admin, while display is fully controlled to match your front-end design.
Technical notes
Display is the responsibility of the merchant/developer implementation. The specific metafield reference names are not stated in this article, so check the API documentation before implementing.

9A one-line summary you can use in a pitch

"Graduate notices like Prop 65 and choking hazards from being embedded in descriptions or theme code, and
manage them centrally as structured data in a dedicated 'Disclosures' product metafield field.
Supported themes display them automatically, and custom front ends render them via API references. Deciding whether they're needed and what they say remains the merchant's responsibility."