Shopify WebMCP Checkout: AI Agents Can Now Buy

Shopify just taught browsers to press your buy button. On September 28, 2026, Shopify's developer changelog announced that browser-based AI agents can read a checkout, change it, and submit the order once the shopper approves. Shopify's own

Shopify just taught browsers to press your buy button.

On September 28, 2026, Shopify's developer changelog announced that browser-based AI agents can read a checkout, change it, and submit the order once the shopper approves. Shopify's own words: the tools "don't expose a new API or require merchant configuration." You did nothing. It is live anyway.

If you run a Shopify store, Shopify WebMCP checkout is now part of your store whether you planned for it or not. The good news is that it is narrower than the headlines suggest. The useful news is where it stops.

What Shopify Actually Shipped on September 28

Shopify switched on three tools at checkout, plus a fourth for getting out of it. Per the Checkout WebMCP documentation, an agent running in the shopper's own browser tab can call:

• get_checkout: read the current checkout, or the order receipt on the Thank you page
• update_checkout: replace contact details, fulfillment, discount codes, extra declared fields and payment
• complete_checkout: place the order after the buyer confirms it
• navigate_to_storefront: leave checkout and go back to the store

TechCrunch's report frames it against a split in the market. Amazon and Adidas are reportedly blocking agents from buying. Shopify went the other direction. Shopify's own agentic commerce product manager, Gil Greenberg, put the pitch on X: use the tools "instead of navigating HTML built for humans."

Checkout is the last piece. The August 5 changelog had already put search, product, cart and policy tools on every Liquid storefront. An agent could shop your store and fill a cart. Now it can finish the job.

The Buyer Still Presses the Last Button

Panic is the wrong response, so here is the limit that matters. Shopify's docs describe a human in the loop at three points.

The buyer handles page interactions such as Shop Pay login or a payment challenge. The buyer confirms the order before the agent calls complete_checkout. And when something needs a person, like 3D Secure authentication or a blocking UI extension, the tools hand control back to the buyer.

When the buyer's input is required, such as 3D Secure authentication or for blocking UI extensions, the tools hand back control to the buyer.

— Shopify developer changelog, September 28, 2026

There is a second wall. The documented fields update_checkout can change are contact details, fulfillment, discount codes, declared fields and payment. Line items are not on that list. And payment runs through a saved Shop Pay card or an existing Shop Pay approval. Send anything else and the docs say the call returns an invalid_request error, so an agent cannot type a new card number into your store.

So this is not an unattended robot spending someone's money on your site. It is a shopper who asked an assistant to do the clicking, and who still approves the total. That is a lower-risk story than "agents can place orders," and the one worth telling your team.

Five Kinds of Checkout Get No Tools at All

Here is the part no launch headline carried. Shopify's docs list checkouts where the tools are not registered, and where the agent must ask the buyer to finish on the page:

1. The standard three-page checkout, unless the buyer checks out with Shop Pay
2. B2B checkout
3. Embedded checkout, and checkouts in mobile checkout SDKs
4. Checkouts with merchandise from another shop
5. Draft orders, order edits and payment collection

The docs add that the tools also do not cover app-defined checkout extension interactions, which the buyer handles on the checkout page.

If you are on a newer checkout with Shop Pay enabled, the tools are probably registered. If you have been putting off the checkout extensibility migration, this is one more reason the old setup is expensive to keep. Shopify's agent tooling is being built for the modern checkout, not the legacy one.

Your Checkout Apps Decide Where the Agent Stalls

The sentence in the docs most store owners will skim past is the one about blocking UI extensions. A blocking extension is any step your apps force the buyer through before the order can go through. Gift message prompts. Age checks. Delivery date pickers. An upsell interstitial. A required custom field.

Each one is now a spot where an agent-assisted checkout hands back to a human. That is by design. It is also a map of your own friction. A shopper who asked an agent to buy a gift and gets handed back at the gift-message app has just learned which part of your checkout is clunky.

Our view: this is the real use of the news. Shopify has handed every store owner a free audit trigger. Open your checkout the way a browser agent would and count how many steps are not data Shopify already knows. Every one of those is a place where the agent stops and a distracted shopper might too.

One field type has explicit support. Shopify's docs describe "declared fields" for things a checkout collects like a tax number. An agent fills them by key and value, and a wrong key or wrong type is rejected. A malformed tax number still fails Shopify's own validation. The take-home: if you collect something extra at checkout, make sure it is collected through Shopify's own field system rather than a bolted-on script.

Discount Codes and Delivery Options Are Now Read by a Machine

Two of the fields an agent can change deserve a second look from any owner.

Discount codes. update_checkout accepts a codes array of buyer-entered codes, and Shopify warns that a returned code does not mean it applied. An agent should check whether the discount actually landed. That puts your code hygiene in play. Our opinion, and it is an opinion: an assistant that can type codes quickly will try every code a shopper hands it. If you have old influencer codes, leaked staff codes or a 40 percent code from a campaign that ended, nothing about agent checkout makes those safer. Retire them.

Delivery options. The agent can change address and delivery option. If your shipping rates are named things like "Standard B" and "Priority 2", a machine choosing for a human has less to go on than the human would. Plain names, with real delivery windows, are cheaper to fix than a wrong pick.

The same logic runs one level up. The August storefront tools include a way for agents to search your shop policies and FAQs. We covered the data side of this in July: an agent reads what is in the field, or it does not recommend you. Your returns policy now has two audiences.

What We Could Not Confirm

A few answers are missing, and we would rather say so than guess.

We found no documented setting to turn Checkout WebMCP off for your store. Our earlier post on Meta's Muse and Agentic Storefronts covers the admin toggle that controls whether your catalog flows to named agents like Muse. The docs we read do not say whether that toggle also governs browser agents using WebMCP. Treat them as separate until Shopify says otherwise.

We also found no Shopify documentation on how an agent-placed order is labeled in your reports. If you need to know how many orders came this way, do not assume your analytics will tell you. Test it with your own order.

And WebMCP is still an emerging standard. Shopify's August changelog says agent support is limited to Chromium-based browsers through an origin trial, so volume today is likely small. We do not have order data from client stores to say otherwise. This is a preparation story, not a panic story.

Run This Check Before a Shopper's Agent Does

Here is the afternoon audit we would do on any Shopify store, in order.

1. Identify your checkout. Is it the modern checkout with Shop Pay, or one of the five excluded types? You cannot plan around what you have not looked at.
2. Count blocking steps. List every app that adds a step to checkout. Ask which of them is worth the handoff.
3. Read your delivery options out loud. If a stranger could not pick the right one from the label alone, rename it.
4. Kill dead discount codes. Anything expired, leaked or over-generous goes.
5. Check your policy fields. Returns, shipping and refund policies should be filled in where Shopify reads them, not just linked in the footer.
6. Place a test order the way an agent would. Go through checkout with Shop Pay and note every spot you had to stop.

None of this is exotic. Most of it is the unglamorous cleanup that makes checkout better for people too, which is the real reason to do it. Our earlier piece on website readiness for agents makes the same point from the site side: the shopper's tool is changing, but the work is still fixing your own house.

If you would rather hand that afternoon to someone who has done it, we audit and fix the checkout, extensions and field setup on Shopify stores. It is a defined job with a defined end, not a retainer.