Shopify Agent Checkout Can Now Carry Customer Consent

On October 16, Shopify said its Checkout MCP and Cart MCP now support the UCP buyer consent extension. In plain terms, when a shopper buys from a Shopify store through an AI agent, the privacy and marketing choices they would make in the store's own checkout, such as opting in to email or SMS, can now travel with the purchase back to the merchant.

That sounds like a compliance footnote. It is closer to a missing piece of agentic checkout. A merchant that loses the checkout page still keeps the order, the payment and the fulfillment obligation. Without commerce-platform support for that consent exchange, the permission collected during checkout could fall out of the agentic transaction. Shopify has now added the mechanism, but only for agents that negotiate and use it. When checkout becomes portable, customer permission has to become portable too.

What Shopify shipped

According to Shopify's developer changelog:

• Version. Support starts with UCP version 2026-08-25, for agents that negotiate the buyer consent extension in their profile. Agents that do not declare it, or that use an earlier UCP version, are unaffected.
• Discovery. Shopify storefronts now list the extension in their UCP discovery profiles, covering both cart and checkout.
• Purposes. Shopify storefronts advertise at least four consent purposes: analytics, preferences, sale or sharing of personal data, and marketing, with separate email and SMS choices under marketing. Each arrives with its current state, a description and links to the shop's policies.
• Delivery. The agent sends the buyer's choices when it creates, updates or completes a cart or checkout, and Shopify says shops receive them with the cart, checkout and order.

What happens when the agent says nothing

The defaults carry the operational detail. If an agent does not send consent, Shopify applies the shop's default settings for the buyer's country. If the buyer's country is unknown, consent defaults to opt-out.

One case can stop a purchase. If a buyer opts in to SMS marketing but the checkout has no phone number, Shopify returns a missing_consent_data warning, and the checkout cannot complete until the agent collects the missing detail. The UCP specification states the general rule: a business should warn about missing data on create and update calls, and must not complete a checkout while a confirmed consent choice lacks the data it depends on.

How the specification works

The UCP buyer consent specification models consent in two levels. A purpose, such as marketing, carries a yes or no. A segment, such as SMS under marketing, can override its parent, so a buyer can decline marketing in general and still accept text messages.

Every value also records who set it. A source of "business" means the value is the merchant's default. A source of "platform" means the buyer actually made that choice in the agent's flow. The rules are strict. Agents decide which choices to show, but when they show one they must use the merchant's own description and policy links. They must not ask about purposes the merchant did not advertise, and they may mark a value as the buyer's choice only when the buyer stated it. A choice given to one merchant cannot be reused as the buyer's choice for another.

This is a real change from the earlier version. In UCP 2026-04-08, consent was a set of yes-or-no flags an agent could send into checkout. The 2026-08-25 release notes describe restructuring it into a map that the business advertises and the agent confirms. The merchant now defines the choices, and the record shows who made each one.

What the specification does not do

The specification is explicit about its boundary. It defines how consent state is represented and exchanged. It does not dictate how either party behaves in response: how a merchant acts on consent and how an agent displays existing choices are governed by business policy and applicable regulation. Its purpose names are operational definitions, not legal categories.

Receiving a consent record does not by itself establish that a merchant may lawfully market to the buyer in every jurisdiction. What a recorded choice permits where your customers live is a question for counsel, not for the protocol.

Three permissions, not one

Agentic commerce is now building three separate controls, and they are easy to blur.

Agent authorization asks what the agent may do for the customer. That is the territory of Personal Agent Protocol, where the customer grants access and the business sets parameters for what it will accept.

Permission to place the order asks whether the buyer agreed to this purchase at this total. Shopify's checkout documentation tells agents to get the buyer's approval before completing checkout, separately from proving which agent is calling, a line I looked at when Shopify opened checkout to browser agents.

Buyer consent asks what the merchant may do with the shopper's data and communications afterward.

A shopper can authorize an agent, approve an order and still decline marketing. Each answer has to be captured separately, and none implies the others.

Why this matters commercially

When checkout leaves the merchant's site, the retailer keeps the order but loses the moment it used to collect permission: the email opt-in box, the SMS checkbox, the analytics and sale-of-data choices. I argued that checkout was where an anonymous buyer became a known, reachable customer, and that this is what the retailer risks when checkout disappears. Without a transmitted consent state, an agentic order can deliver a customer the merchant cannot assume it may market to.

The gap shows up elsewhere. Google says merchants are Merchant of Record for checkout in its AI surfaces, but its UCP FAQ still lists an explicit marketing opt-in during checkout as a planned feature, as I noted in the Universal Cart guide.

What it does not show yet

Support on Shopify's side is not adoption on the agent side. An agent has to declare the extension and present the choices, and I found no public announcement from an AI platform that it does. Agents that do not negotiate it are unaffected, so this does not mean every agent checkout now collects marketing consent. It also says nothing about how much agentic checkout is happening.

What merchants should do

• Review the consent defaults your store applies by country, because they now also govern agent checkouts that send no choices.
• Read your consent descriptions and policy links out of context. When an agent shows them, it has to use them as written.
• Check how consent captured through an agent appears in your customer records, and keep the difference between a default and a buyer's stated choice in your marketing rules.
• Ask the AI platforms you sell through whether they negotiate the extension.

If an agent brings you the order but not the permission, is that customer yours?