Copilot shopping, for merchants

01

What the documentation covers

Applies to marketplace onlyown storefronthybrid

The primary document covers three components together: Copilot Checkout surfaces, Microsoft Merchant Center store settings, and the feed attributes that carry product information into them.¹ Having the surface, the settings, and the data requirements in one publication means the setup question and the data question can be answered from a single source.

It documents requirements rather than outcomes.¹ It states which stores are admissible and which fields a record needs; it does not describe how often items are shown or to whom.

02

The three stated eligibility conditions

Applies to marketplace onlyown storefronthybrid

The documented condition names three requirements at once — the storefront is English-language, the buyers are in the United States, and the currency is USD — and only merchants meeting all three are described as eligible, at this time.¹ The closing qualifier indicates a sentence the documentation expects to revise.

The three cover different properties of a business, and a store can meet some and not others.

Because the conditions are stated together, meeting two of them is not a partial qualification with a partial result. For this store the currency row settles the question on its own, and the product-record work described later does not affect it.

03

Settings documented as a pilot to select customers

Applies to marketplace onlyown storefronthybrid

Some store settings are marked as a pilot to select customers.¹ The capability exists for some accounts, and the documentation does not state that it is available for any particular one.

The practical consequence is that readable documentation can describe a settings screen an account does not have. Where a documented setting is absent, the documentation attributes that to the pilot scope rather than to a configuration state the merchant controls.

The documentation describes selection rather than a queue, so there is no stated position or waiting time to track. What can be recorded is whether the setting is present in the account and on what date that was checked.

04

The route through a commerce platform

Applies to marketplace onlyown storefronthybrid

Most resellers reach this surface through their commerce platform rather than through a direct integration. Shopify lists Copilot alongside Google AI Mode and Gemini and Meta as channels where an active direct checkout allows a customer to pay without leaving the AI channel, and publishes a conditions page for each.³ Where that applies, the platform’s page is the operative document and Microsoft’s provides the surrounding context.

The platform page carries its own conditions: the store must sell to customers in the United States, direct checkout is switched on by default once a store qualifies rather than being opted into, and the documentation states that satisfying the listed requirements does not ensure the checkout block renders.² Both sets of conditions apply on this route.

The same page documents specific exclusions, which are the entries most likely to affect a working catalog.

The analytics row has a consequence for interpretation. A checkout that completes without firing those pixels produces a sale that standard reporting does not record, so an absence of measured activity on this route is consistent with the documented instrumentation behavior and does not by itself indicate the level of activity.

05

The feed attributes and how they compare

Applies to marketplace onlyown storefronthybrid

The feed attributes documented for this surface cover identity, price, availability, condition, and the fields that let a system determine whether an item matches a request.¹ These are the same categories the other surface documents in this course ask for, under differing field names.

Because the categories converge, a single well-formed item record satisfies most of what several surfaces require, and the differences are largely in naming. That is why the attribute work is not conditional on eligibility: it is required by every documented path.

1. Compare the attribute list against what the store already produces for other channels, so the work is scoped to the difference.
2. Fill the genuine gaps in the existing record rather than maintaining a second parallel record for this surface.
3. Confirm condition and availability are read from the same source as every other channel rather than re-entered, since re-entry is where two surfaces begin to disagree about one item.
4. Note which attributes this surface requires that others do not, so the difference is recorded rather than rediscovered.

Applied to the camera, nearly every field the store already produces maps across under a different name. What has no field on any of these surfaces is the shutter defect, which is carried in prose and depends on where in the listing the seller places it.

06

The eligibility note for one store

Applies to marketplace onlyown storefronthybrid

The record for this lesson is four lines naming, for one store, which condition applies and what would change it.

Each of the first three has a specific event attached to it, which is what makes a later re-check short. The temporal qualifier in the eligibility sentence, the pilot scope, and the platform’s confirmation are three separate things to re-read, and none of them is affected by further preparation.

07

The current eligibility position

Applies to marketplace onlyown storefronthybrid

Microsoft documents Copilot Checkout surfaces, Merchant Center store settings, and feed attributes together, states eligibility as English-language merchants selling to US buyers in USD at this time, marks some store settings as a pilot to select customers, and lists feed attributes covering identity, price, availability, and condition.¹ Shopify lists Copilot among the channels where an active direct checkout allows payment without leaving the AI channel.³ The platform’s direct-checkout page requires the store to sell to US customers, activates the checkout by default once a store qualifies, states that meeting the requirements does not ensure the block renders, and documents unsupported product types, unavailable delivery methods, and analytics that does not fire.²

The sources do not describe how items are selected for display on this surface, and they do not state when the eligibility conditions or the pilot scope will change. Where a line in the eligibility note is unestablished, it records a question put to a supplier and not yet answered on the date shown.