The Pulse
Shopify Adds Browser-Agent Tools for Checkout
Shopify’s checkout WebMCP tools let browser agents read and update an active checkout, then submit an order after the buyer confirms it. The tools run in the buyer’s browser session, and Shopify says they require no merchant configuration o
AI.info Team · Written with AI ·
Checkout moves into the browser agent’s reach
On September 28, 2026, Shopify added WebMCP tools that let browser-based agents read and update an active checkout in a buyer’s browser session. Agents can now assist beyond product discovery and cart management, continuing through checkout and order confirmation, the company said in its developer changelog.
The tools expose four actions. navigate_to_storefront takes the agent to a store; get_checkout reads checkout state, messages and post-completion order details; update_checkout changes supported fields; and complete_checkout submits the purchase after the buyer confirms. Shopify says the tools run inside checkout-web and use the same state as the checkout interface.
Buyer approval still gates the order
The new tools do not remove the shopper from the transaction. Shopify says complete_checkout submits an order after buyer confirmation, and the agent hands control back whenever the flow requires the buyer’s input. Its examples include 3D Secure authentication and blocking user-interface extensions.
That handoff is a boundary between agent assistance and actions that still require a person. The agent can handle supported checkout updates, but the company’s description does not present checkout as a fully autonomous purchase process: buyer confirmation remains part of submission, and additional authentication or extension prompts can interrupt the agent’s work.
Shopify’s checkout documentation says the buyer sees the same checkout state as the agent and handles page interactions, including Shop Pay login or payment challenges. Before the agent calls complete_checkout, the buyer must confirm the order. If checkout presents a review step, the buyer reviews and authorizes submission on the page before the agent calls the tool again.
No separate merchant integration
Shopify says merchants do not need to configure checkout or expose a new API for these browser tools. They operate against the active checkout session rather than creating a separate checkout flow. That keeps the agent’s actions tied to the checkout already presented to the shopper.
The checkout tools register on eligible checkouts. get_checkout can read the current checkout or an order receipt on the Thank you page. update_checkout can change buyer contact details, fulfillment choices, discount codes, declared fields and payment information; it does not place an order. Shopify’s documentation cautions that updates use PUT semantics, so an agent should build its requested state from a fresh checkout reading.
The scope differs from Shopify’s server-side agent tools. The company’s WebMCP documentation describes tools used by agents shoppers bring to a store in their browser; agents connecting directly to Shopify’s MCP servers follow a separate path. Shopify says its storefront WebMCP tools are available on Liquid storefronts and Hydrogen developer previews, while agent support for WebMCP is currently limited to Chromium-based browsers.
From browsing to order confirmation
Before the checkout update, Shopify’s browser tools already covered storefront and cart actions. Adding checkout tools extends that browser-based sequence to supported checkout updates and order submission, without requiring merchants to install or configure another integration. The new step also gives agents access to order details after completion through get_checkout.
The practical reach depends on the browser agent supporting WebMCP and on the checkout not requiring a human action the agent cannot perform. When authentication or a blocking extension intervenes, Shopify’s specified behavior is explicit: control returns to the buyer. That limit is part of the feature’s design: the agent acts on the open checkout, but the buyer handles required page interactions and confirms the order.