What changed, and who needs this guide
Shopify announced Checkout MCP and Cart MCP support for dev.ucp.shopping.buyer_consent on October 16, 2026. The extension belongs to UCP 2026-08-25; this was a Shopify support update, not a new protocol release. Earlier-version integrations and agents that do not negotiate the extension are unaffected by this change.
This guide is for developers and technical merchants implementing store-specific privacy and marketing choices. EcomAgentHub reviewed the public documentation on October 17. We did not connect a store, submit a checkout, purchase anything or test legal compliance. The fixture checklist below is a proposed implementation review, not a record of successful transactions.
Negotiate the extension before debugging the consent object
Check the storefront discovery profile at /.well-known/ucp and declare dev.ucp.shopping.buyer_consent at version 2026-08-25 in the agent profile. Successful negotiation makes buyer.consent available in cart and checkout responses. Shopify advertises analytics, preferences, sale_or_sharing and marketing purposes, including email and SMS segments.
Shopify's profiles documentation uses meta.ucp-agent.profile to point an MCP request at the agent profile. Confirm the actual profile URL and negotiated response rather than assuming that updating a local configuration changed the served profile. Keep the version, shop domain and a redacted response with the issue report. An absent consent object is first a discovery or negotiation question, not evidence that the buyer refused marketing.
Preserve store defaults and the origin of each choice
Shopify applies the shop's country-specific defaults when consent is not supplied. If the buyer's country is unknown, the default is opt-out. Do not replace a known-country shop default with a global preference invented by the agent.
The UCP specification distinguishes business-asserted values from buyer-stated preferences attributed to platform. Display the advertised descriptions, policy links and grouping. Use source: platform only for an actual buyer-stated preference; otherwise preserve the advertised source. A segment's value overrides its parent for that segment. Custom identifiers are opaque, so their spelling alone is not a consent policy.
When submitting a consent map, include every advertised purpose and segment with granted and source; an omitted key cannot stand for a value. Omitting the whole consent field means no consent update. Do not invent unadvertised choices or carry a business-specific decision into another shop as platform consent. Persisted preferences should remain changeable.
Recover from missing_consent_data without changing the buyer's answer
The specification treats missing dependencies on create or update operations as warnings; the advertised consent decision remains valid. A confirmed decision with an unmet dependency blocks complete_checkout from reaching completed. For example, an SMS choice may require buyer.phone_number. Read the message's code and path rather than guessing which field is missing.
Our suggested recovery flow separates the buyer's choice from the information needed to honor it. Keep the current consent state visible, explain the missing contact detail and let the buyer provide it or explicitly revise the choice. Do not silently switch consent to true, fabricate a number, or change an opt-in to opt-out merely to make an error disappear.
- Retain the latest response, shop identity, advertised choices and warning path in a redacted debug record.
- Ask for the indicated contact detail in the appropriate field. An email address and an SMS number are separate dependencies; do not infer either from unrelated text.
- Submit the corrected state using the operation's documented semantics, then inspect the new response. Keep an unchanged buyer decision distinct from a newly stated preference.
- If the dependency remains unresolved, explain that checkout has not completed and offer the supported merchant handoff. Retry only after something relevant changes.
Respect cart replacement, checkout status and purchase authorization
Shopify documents update_cart as full replacement, not a patch of individual fields. Build a retry from the intended complete cart state so fixing a phone number does not remove unrelated contents. Cart MCP can accept unauthenticated requests; Checkout MCP requires authentication or a signed request. Consent negotiation does not supply either account access or purchase authorization.
Use the response's continue_url for the supported merchant checkout handoff when required. A consent warning disappearing is not proof of an order: read the returned checkout state. Privacy or marketing consent is not permission to charge the buyer, and protocol conformance does not establish legal compliance. Merchant policies and applicable obligations need their own review.
Review these synthetic fixtures before an authorized store trial
Use a mocked response and expected request pair for each case. Compare the full request, displayed choice and resulting application state. These cases are our suggested acceptance criteria and have not been executed against Shopify.
- Unknown country, no buyer choice: verify that the interface does not label the shop's opt-out default as an explicit user decision.
- Known country, unchanged defaults: retain the shop's advertised values and source; do not substitute a country policy table maintained by the agent.
- Parent marketing value differs from the email segment: verify that the displayed email state follows the advertised segment.
- Buyer changes only SMS: build a complete advertised map while preserving untouched values and their attribution.
- SMS opt-in without a phone number: show the warning, retain the decision, and withhold any completion message until the actual checkout response supports it.
- Corrected contact data during update_cart: verify that line items and other intended state remain present.
- A second shop appears: do not reuse the first shop's business-specific consent as a decision for the second.
- The UI says done but checkout is unresolved: report the observed state and supported next step, not an invented purchase receipt.
Keep a small, useful implementation record
Record the integration version, profile revision, shop domain, displayed purpose and segment keys, redacted outgoing state, returned warnings and observed checkout status. Keep personal contact values out of shared debugging artifacts. Review both the successful path and the buyer's decision to decline or change a preference.
Use the Shopify collection below to compare adjacent store workflows, or the workflow setup service to discuss a bounded implementation review. Consent capture, customer-support drafting and fulfillment automation solve different tasks; success in one does not validate the others.