Google AI Mode shopping, for merchants

01

The four steps between an item and a surface

Applies to marketplace onlyown storefronthybrid

An item sits in a store; the store runs on a platform; the platform may run a channel connecting to the surface; the surface decides what appears in an answer. Four steps, each decided by a different party.

Four terms recur through the rest of this lesson, and each names a different party’s decision.

The first row is checkable against documentation, the second and third resolve from a platform’s own pages or a written reply, and the fourth is not addressed by any source in this set.

02

What the merchant and developer documentation state

Applies to marketplace onlyown storefronthybrid

The merchant-facing documentation covers market eligibility, onboarding steps, and product-attribute requirements. It describes availability as phased and select, applying to participating merchants and partners and to products holding eligibility in a named list of markets.¹

Two of those words carry specific consequences for reading absence. Because availability is described as phased, an item not appearing on a surface is consistent with the phase the rollout is in and does not, on its own, indicate anything about the item record or the store. Because the path applies to participating merchants and partners, the decision to participate is documented as sitting upstream of the individual seller.

The developer-facing documentation covers the integration model, the checkout paths, and where the merchant of record sits in each.² The merchant of record is the party the buyer has transacted with, and therefore the party carrying the refund obligation. Which name occupies that position differs by checkout path, which is why it is read off the documentation for the specific arrangement rather than assumed.

Between the two pages, a merchant can generally establish whether a documented route currently exists and whether their situation is described by it. For a store on a hosted platform, the operative conditions are usually published by the platform rather than on either of those pages.

03

The platform channel and the conditions published on it

Applies to marketplace onlyown storefronthybrid

For most resellers the route runs through the commerce platform rather than through a direct integration. Shopify runs Google AI Mode and Gemini as one of its agentic-storefront channels and documents it on a page of its own, which is where a merchant on that platform finds the conditions that apply to them.³

Three conditions are stated on that page. The channel is early access and not yet available to every store. Eligibility requires the store to be based in, and selling to, the United States, the United Kingdom, Australia, or Canada. Direct checkout is activated by default for eligible stores, with deactivation offered as the merchant’s choice.³

The third condition sets the decision a merchant is making. Because activation is the default, what remains open is whether to turn it off. For repeatable stock that is a margin and fulfillment question. For a single unit with a recorded defect it is a question about where the condition evidence is read: a buyer completing payment inside the surface may not reach the item page carrying the defect description.

The page’s non-guarantee language is specific in scope: meeting a stated requirement does not guarantee that a checkout block will load.³ It is a statement about the checkout component rather than about discovery or display, and the sources here do not address whether a merchant’s products are shown.

04

The product-attribute requirements

Applies to marketplace onlyown storefronthybrid

Product-attribute requirements are stated as conditions for the checkout path, which gives the attribute work a documented relationship to eligibility.¹ For single-unit stock, the attributes that need attention are the ones written with repeatable catalog goods in mind.

1. Fill every required attribute for one real item without supplying a value that is not true of the unit, since a supplied value and a correct value are indistinguishable to a validator.
2. Where a required attribute does not apply, record what was entered and why, so that a deliberate blank can later be told apart from an omission.
3. Check that condition, quantity, and price carry the same values here as on every other surface the item is sold through.
4. Confirm that the item stops being offered on every surface when it sells, not only on the one being watched.

Applied to the camera, two attributes do not resolve. A manufacturer product code does not exist for a body of that age, and a condition vocabulary built for retail grading has no term for a shutter that is unreliable only below a certain speed. The first is recorded as a blank with a note; the second is written as a plain sentence placed where it is read before payment.

05

What can and cannot be measured on this route

Applies to marketplace onlyown storefronthybrid

A merchant can generally observe that a session arrived and cannot generally observe why an item was selected. No documentation in this source set describes attribution of a placement to a change a merchant made.

The measurable items are the ones the merchant controls directly: whether required attributes are complete, whether availability is accurate within a known lag, and whether prices agree across surfaces. Traffic changes are observable but not attributable, because the sources describe a phased rollout and no control condition exists.

That applies in both directions. An increase after a change does not establish that the change caused it, and an absence after a change does not establish that the change prevented it. The second matters for accuracy of product facts specifically: nothing in the current sources connects a condition disclosure to whether a surface shows an item.

06

The three positions a merchant can be in

Applies to marketplace onlyown storefronthybrid

Reading the documentation resolves a store into one of three positions, each with a different next step.

• Open: follow the platform’s documented onboarding, record what was done, and set the condition under which the experiment stops.
• Gated: complete the attribute work, note the specific condition that is not met, and set a re-read date.
• Unclear: ask the platform in writing and record the reply with its date.

For the camera the position is the second. The attribute work is complete, the outstanding condition is early-access availability, which follows the platform’s release schedule, and the direct-checkout default remains active. That default is the one item in the list the merchant can change now, and deciding it explicitly records a choice that otherwise stands by inheritance.

The attribute work is required by the documented path regardless of which of the three positions applies, so it is not conditional on access opening.

07

What the documentation currently establishes

Applies to marketplace onlyown storefronthybrid

The merchant documentation states market eligibility, onboarding steps, and product-attribute requirements, and describes availability as phased and select for participating merchants and partners.¹ The developer documentation states the integration model, the checkout paths, and where the merchant of record sits.² The platform channel documentation states early access, four named markets for store eligibility, direct checkout on by default with deactivation available, and a non-guarantee limited to whether a checkout block loads.³

The sources do not describe how a surface selects items for an answer, and they do not attribute a placement to any merchant-side change. Where a status in the route map is unconfirmed, it reflects a question put to a supplier and not yet answered on the date recorded.