Shopify WebMCP checkout: agents can place the order now

Your checkout is an API now, and you did not ship it. Shopify turned on WebMCP support for checkout today — including Shop Pay — for all eligible merchants. Browser-based AI agents can read the checkout screen, change it, and submit the order with the buyer's authorization. No screenshots. No scraping. Actual tool calls against actual checkout state. If you sell on Shopify, the agentic commerce conversation stopped being a 2027 roadmap item at some point this morning.

What actually happened

Per TechCrunch, Shopify extended WebMCP past the storefront and into checkout. Three tools do the work: get_checkout reads the current state, update_checkout changes things like the shipping address or delivery option, and complete_checkout places the order once the buyer approves. Shopify's own framing: "Shopping with an agent shouldn't feel like watching paint dry."

The Shopify docs fill in the rest. The checkout tool set also includes create_checkout and cancel_checkout. Every response carries a status field, and complete_checkout is gated — it will not fire until status reads ready_for_complete. For most integrators on general access, checkout escalates back to your storefront through a continue_url instead of completing programmatically inside the agent.

Two things worth noting. First, checkout registers its own WebMCP tools, so the tool list an agent sees changes the moment a shopper crosses from your storefront into checkout. Second, the storefront half of this is already live — Shopify's changelog says WebMCP tools are on every Liquid storefront and the Hydrogen developer preview with nothing to install or configure.

Same day, Instinct announced a Shopify partnership — product discovery, checkout, and order updates in one conversation, settling with Shop Pay. Meta's Muse already had the door open. Meanwhile Amazon and Adidas are going the other way and blocking agent purchases outright.

Why agentic checkout matters for your business

"Nothing to install" means you already opted in. Platform-level defaults are how this arrives. You did not write a spec, review a security model, or decide your delivery-option copy needed to read well to a language model. It shipped anyway. Go look at what your own checkout returns from get_checkout before a customer's agent does.

Your funnel analytics are about to get weird. Sessions with no scroll depth, no hover, no time-on-page, converting at rates that do not match anything in your dashboard. If you cannot separate agent-driven checkouts from human ones, every conversion-rate decision you make next quarter is downstream of a blended number. Tag the traffic now while the volume is still small enough to reason about.

The continue_url escalation is the interesting line in the docs. When the agent hands the buyer back to your storefront to finish, you own that last mile — the payment step, the fraud check, the confirmation. That is a better place to be than having an agent submit payment on someone's behalf and sorting out liability later. Know which path your store is on.

Delivery options are now a machine-readable decision. update_checkout lets an agent pick a different delivery option. An agent optimizing for the buyer will take the cheapest one every time, with none of the hesitation a human feels about a five-day wait. If your margin depends on shoppers upgrading shipping at checkout, model what happens when that stops.

Refunds and returns are the unglamorous risk. An agent that buys fast buys wrong sometimes. Plan for the return rate on agent orders to run higher than your baseline, and decide now whether your restocking policy treats "my agent ordered the wrong size" as a customer error.

Sources: TechCrunch, Shopify Checkout MCP docs, Shopify developer changelog.