Google has added a consumer notice attribute to Merchant Center that lets merchants attach safety warnings, legal disclaimers and California Proposition 65 disclosures to individual products, with the text shown to shoppers inside Google's AI checkout before they pay. Emmanuel Flossie, founder of the Google Shopping consultancy FeedArmy and a Google Ads Diamond Product Expert, documented the attribute on November 20, 2026, in a FeedArmy guide and in a post on MerchantCodex, the forum community he runs.

The field itself is modest. Its behaviour at the limit is not. Google accepts up to seven notices per product, and an eighth is not simply ignored: according to Google's own documentation, the most recent seven are kept and the first one is thrown away.

In Short

Google Merchant Center now has a consumer_notice field where sellers can add safety warnings, legal disclaimers and California Prop 65 notices to each product, and those notices appear in Google's AI checkout before the shopper pays. It matters to anyone selling goods that carry legal warnings, because Google's developer guide calls the field mandatory for such items while its help page calls it optional. The catch is the limit: a product can carry seven notices, and an eighth silently pushes out the first.

A field for the fine print

Google's help page for the attribute, titled "Consumer_notice [consumer_notice]", describes it as "vital for product compliance and customer transparency." The page says the attribute exists to carry mandatory legal disclosures and essential safety information before a customer completes a purchase, and names two kinds of notice in its introduction: safety warnings and Prop 65 disclosures.

Flossie put it more bluntly. "Google has quietly added a new attribute to Google Merchant Center called consumer notice [consumer_notice]," he wrote in the FeedArmy guide. His examples were concrete: a toy suitable only for children aged three and over, or a product containing a chemical such as formaldehyde, which California requires sellers to warn about because it can cause cancer.

Google's checkout runs on the Universal Commerce Protocol, or UCP, the standard Google launched on January 11, 2026 with Shopify, Etsy, Wayfair, Target and Walmart among the co-developers. In the forum post, Flossie described the purpose of the new field in one line: "This is designed to show the legal disclaimer alongside the UCP (AI checkout)." According to Google's help page, when a shopper is in the UCP flow for a product that carries the attribute, an expandable "Product warning" section appears in checkout. Google's page calls the element a "zippy". Clicking it opens a popup with the warning text. Where a product has more than one notice, Google consolidates them and shows each as a separate paragraph.

Flossie stressed the narrowness of that placement. "It isn't shown everywhere in Google Shopping; it appears during product checkout in that flow," he wrote. Google's benefits list on the same help page is broader, stating that "The warning is automatically displayed in the product checkout flow and other relevant product surfaces." The page does not say which other surfaces it means.

Reference table: consumer_notice at a glance

Element Specification, according to Google's help page
Main attribute consumer_notice, a repeatable group
notice_type Required. One of legal_disclaimer, safety_warning or prop_65
notice_message Required. Text of up to 1,000 characters
Combined format notice_type:notice_message
HTML permitted in the message <b>, <br>, <i> and <a href>
Character set Unicode accepted, ASCII recommended
Maximum per product 7. If more are sent, the last 7 are kept
schema.org markup Not supported
Requirement level "Optional for all products" (help page); "mandatory for items with regulatory warning requirements" (UCP developer guide)
Where it appears "Product warning" section in UCP checkout, opening a popup
Countries Not listed

How the attribute works

According to Google's help page and Flossie's guide, the documented process has six parts:

  1. Structure. Each notice is one instance of consumer_notice, made of two required sub-attributes, notice_type and notice_message, combined as notice_type:notice_message.
  2. Notice type. The notice_type tells Google what kind of legal detail the notice holds. Only three values are accepted: legal_disclaimer, safety_warning and prop_65. Google's supported values list labels them "legal disclaimer", "safety warning" and "prop 65 warning".
  3. Message. The notice_message is the text the shopper reads. It is capped at 1,000 characters and accepts four HTML tags: <b> for bold, <br> for a line break, <i> for italic and <a href> for links. Flossie noted that the link option allows a notice to point to a manufacturer's legal or safety page rather than compressing everything into the character limit.
  4. Submission route. The attribute travels through the main product feed or a supplemental feed. Google's format table marks schema.org support as "No", so structured data on a landing page is not a route for it. "Honestly, for detailed product information like this I never rely on structured data anyway," Flossie wrote.
  5. Repetition. A product can carry up to seven notices. In text feeds each notice sits in its own column with the same consumer_notice header; in XML the whole block is repeated; in the Merchant API each notice is a separate custom attribute entry.
  6. Display. In checkout, the notices sit behind the "Product warning" section. A click opens the popup, and multiple notices appear as separate paragraphs.

Flossie also published his own six-point checklist, which runs from listing the products that legally need a warning to showing the same warnings on the merchant's own landing pages, so that the disclosures are not confined to Google.

Escaping, format by format

Warning text is awkward to put in a feed. "Most errors with this attribute will come from escaping, because warning texts are full of colons, commas and quotes," Flossie wrote. The colon is the problem: it is also the separator between notice_type and notice_message, so a message such as "WARNING: Choking hazard" contains a second colon that a parser can misread. Google's help page sets out different rules for each submission format.

Format How notices are entered Escaping rules
Text / TSV feed One column per notice, each headed consumer_notice. Google recommends a tab delimiter rather than comma or pipe Wrap values in double quotes, required when the message contains a comma or colon. Double any quote inside the message. Select "using quoted fields" when setting up the supplemental feed
Google Sheets One column per notice Escape commas and colons with a backslash (\, and \:). Escape a literal backslash with a second one (\\). Do not wrap values in double quotes, which become part of the value
XML A g:consumer_notice element with g:notice_type and g:notice_message children, repeated for each notice HTML tags inside the message must be escaped as XML characters
Merchant API A custom attribute named consumer_notice, with groupValues holding notice_type and notice_message Escape double quotes (\"), backslashes (\\) and control characters such as new lines and tabs

The examples in Flossie's guide show the differences. In a text feed:

safety_warning:"WARNING: Choking hazard. Not for children under 3; adult supervision required"

In Google Sheets, the same kind of warning loses its quotes and gains backslashes:

safety_warning:WARNING\: Choking hazard\, small parts. Not for children under 3.

In XML, each notice is its own block:

<g:consumer_notice>
  <g:notice_type>safety_warning</g:notice_type>
  <g:notice_message>Choking hazard. Small Parts. Not for children under 3 yrs.</g:notice_message>
</g:consumer_notice>

And in the Merchant API:

"customAttributes": [
  {
    "name": "consumer_notice",
    "groupValues": [
      { "name": "notice_type", "value": "safety_warning" },
      { "name": "notice_message", "value": "<b>Warning</b>: Choking Hazard. Small Parts. Not for children under 3 yrs." }
    ]
  }
]

Two details stand out. Google's own text-feed example quotes both halves of the value, as in "safety_warning":"Safety warning notice text", while Flossie's example quotes only the message. And in the Merchant API the notice is sent as a custom attribute rather than as a dedicated product field. For merchants that manage catalogues programmatically, that is the route Google now points to, having scheduled the Content API for Shopping to shut down on August 18, 2026, a year after it made the Merchant API generally available.

Seven notices, and an eighth that erases the first

"This is the most important thing in the whole article," Flossie wrote of the limit. Google's help page states the rule in a single sentence: "if you submit more than 7 notices at one time, only the last 7 notices will be kept." The page's own example spells out the consequence. An eighth notice overwrites the first, leaving notices two to eight.

Most systems discard the overflow. This one discards the oldest entry. "Google keeps the last 7 and drops the earliest ones," Flossie wrote, calling the behaviour "really strange". In practice, column order in a text feed, or block order in XML, decides which warning survives. A merchant who places the most legally significant warning first and then adds seven more would find that warning missing from checkout, with no indication in the documentation that an error is raised.

Why would a field built for legal warnings drop the first entry rather than the last? Google's page does not explain. Flossie's own recommendation is never to send more than seven and to include only the notices that are legally required.

Optional, or mandatory?

Google describes the requirement level in two different ways. The help page is permissive: "Optional for all products. You may use it to provide information required by local laws or regulations."

Google's developer documentation for UCP is firmer. The guide "Prepare your Merchant Center account", last updated on November 17, 2026, three days before Flossie's post, lists consumer notices among the product data that signals checkout readiness and states: "This is mandatory for items with regulatory warning requirements (e.g., California Proposition 65)." The same guide says the warnings are "displayed prominently on the Checkout screen" when provided.

The two statements can be read together - optional as a feed field, required where the law requires a warning - but they are not worded the same way, and only the developer guide uses the word mandatory. That guide sets out the rest of the product data for Google's checkout: a native_commerce attribute whose checkout_eligibility value defaults to FALSE, meaning products without it are not eligible for checkout; a cart_eligibility value that is opt-out; item identifiers; and variant options. At account level, it requires a Merchant Center account in good standing with products approved for free listings, a return policy and at least one customer support contact. It excludes subscriptions, instalment purchases, personalised goods, pre-orders, age-restricted items, healthcare and pharmaceutical products and digital goods.

California's rules explain why a checkout warning matters. Proposition 65, the 1986 ballot measure, requires warnings for exposure to listed chemicals. Under the warning regulations, section 25602(b) of title 27 of the California Code of Regulations, a warning for an internet purchase must be provided through one or more of three methods: "a warning on the product display page", a clearly marked hyperlink on that page using the word WARNING, or "an otherwise prominently displayed warning provided to the purchaser prior to completing the purchase." The regulation adds that a warning is not prominently displayed "if the purchaser must search for it in the general content of the website." Amendments filed on November 26, 2024 became operative on January 1, 2025. For internet purchases made before January 1, 2028, a retail seller is not responsible for posting a new warning online until 60 calendar days after receiving it.

When the purchase is completed inside Google's interface, the retailer's own product page may not be on the path to payment at all. The consumer_notice field places the warning on the checkout screen instead. Google's help page, however, does not say who bears responsibility for the content. Flossie made the same point: the help page explains how to submit the attribute, not which disclosures a product legally needs, and he referred merchants with doubts to a qualified legal adviser.

Errors in Google's own documentation

Google's pages contain at least three inconsistencies, two of which Flossie flagged.

The first concerns the value itself. "One thing I noticed: Google's own XML example uses prop65 without the underscore, while the list of supported values says prop_65," Flossie wrote. The help page's sub-attribute list and its XML rules both specify prop_65; its XML example uses prop65. Flossie recommended prop_65, with a check of diagnostics after the first upload.

The second concerns the name of the protocol. Google's help page refers to the "Universal Checkout Protocol (UCP)" and links that phrase to its own page titled "About the Universal Commerce Protocol (UCP)". Flossie's guide repeats the "Universal Checkout Protocol" wording. Google launched and documents the standard as the Universal Commerce Protocol. The XML section of the help page also repeats the JSON escaping rules with typographical errors, writing "/n" and "/tab" for the control characters.

The third concerns geography. "Note that Google's help page does not list which countries it applies in," Flossie wrote. Prop 65 is a California law, and the help page links to California's Prop 65 warnings site, but it names no country or market for the attribute as a whole.

Where Google's checkout stands

The field arrives as Google widens the reach of its checkout. On March 2, 2026, a Merchant Center help page restricted UCP checkout to US products from selected merchants who had submitted an interest form, carried the native_commerce attribute and used a payment service provider able to accept a Google Pay token. On May 5, UCP checkout moved out of AI Mode into main search results, with Wayfair the only confirmed retailer at that point. Adoption on the merchant side was thin: in May, Originality.ai found only 26 UCP implementations, with the big names absent.

Google then enrolled merchants on their behalf. Starting September 18, 2026, it switched on native checkout by default for Shopify stores matched to their Merchant Center accounts, leaving opt-out as a manual step. On October 6, it opened a Merchant Center hub where selected US merchants can choose cart transfer, native checkout and identity linking, with Canada and Australia pushed to 2027. On October 15, Universal Cart reached US Search and the Gemini app, though not YouTube.

That sequence matters for the new field. Stores switched on by default since September may already have products in Google's checkout without any consumer_notice values, because the attribute is new and none of the documentation says whether Shopify's integration fills it. In agentic commerce, where the shopper may never visit the retailer's site, the feed becomes the only place a seller can attach the fine print.

Why this matters for merchants

Merchant Center has been absorbing legal obligations one attribute at a time. In October 2026, Google added a warranty attribute after Quebec's planned obsolescence law brought three- to six-year legal warranties into force on October 5, with durations to be displayed near the price. Earlier in the year, Google made pickup cost and minimum order value mandatory in the UK, Switzerland and the EEA, with enforcement from September 30. In July, it merged its Shopping ads and free listings policies into a single set from September. Consumer notices extend that pattern to product safety and chemical exposure.

Flossie expects enforcement to follow, though Google has said nothing of the kind. "In the beginning I don't expect Google to suspend anyone for leaving it out. Eventually, though, Google will start using automated checks to see which merchants submit it and which don't," he wrote. His reasoning is that once some merchants submit warnings for a product type, Google learns that the type carries legal requirements. That is a forecast, not a stated Google policy. PPC Land has reported Flossie's findings before: in January, his test found Merchant Center's automatic import about nine days out of date, and in March he highlighted a stricter out-of-stock buy button rule.

Google's help page carries no publication date, and no entry for the attribute appears in the Merchant Center announcements change log. A guide from AdTribes, which makes a WooCommerce feed plugin, already maps the field and shows a last-modified date of October 2, 2026, so the specification may predate Flossie's post by several weeks. Google has not said which countries the attribute covers, whether missing notices lead to disapprovals, which "other relevant product surfaces" display the warnings, or why the earliest notice is the one discarded.

Key facts

Timeline

Summary

Who: Google, through its Merchant Center product data specification and its UCP developer documentation, and Emmanuel Flossie, founder of FeedArmy and MerchantCodex, who documented the attribute. Merchants selling products that carry safety warnings, legal disclaimers or California Prop 65 disclosures are the ones affected.

What: A new consumer_notice attribute with two required sub-attributes, notice_type (legal_disclaimer, safety_warning or prop_65) and notice_message (up to 1,000 characters, with four HTML tags allowed). Up to seven notices can be sent per product; if more are sent, Google keeps the last seven and discards the first. The notices appear in a "Product warning" section of Google's UCP checkout.

When: Flossie published his guide and forum post on November 20, 2026. Google's UCP developer guide describing the attribute was last updated on November 17, 2026. Google's help page carries no date.

Where: In Google Merchant Center feeds, supplemental feeds and the Merchant API, with display in the UCP checkout flow on Google. Google lists no countries for the attribute; the Prop 65 value relates to California law.

Why: Prop 65 regulations require online warnings to appear on the product page or prominently before a purchase is completed. When checkout happens inside Google rather than on the retailer's site, the feed is the place where such warnings can be added. Google's help page calls the attribute optional, while its developer guide calls it mandatory for items with regulatory warning requirements.