Stores get ready for AI agents: what stays with a person in the ordering systems I build

In one week Shopify, Vercel, Cloudflare and Commerce.com each explained how a store should look to an AI agent: structured data instead of HTML, search and cart through MCP, payment with saved details. And in every one of these setups the last step is left to a person: confirming the amount and the payment method. For a business owner who takes orders, bookings or requests, the question goes like this: which step in your process should stay with a person, and is that written into the system or does it depend on an employee's habit?

What came out

On October 20, Practical Ecommerce described the joint work of Shopify and Vercel. At the Ship 26 conference in San Francisco on October 15, Tobi Lütke and Guillermo Rauch showed a rebuilt Hydrogen SDK and the open Vercel Shop template. The template gives people a regular storefront, and agents get the same pages in Markdown, with the description, prices, variants and availability. Catalog search, stock by variant, the cart and checkout links are available through the Universal Commerce Protocol and MCP on the merchant's domain.

On October 21, Cloudflare explained how it turned on WebMCP for almost 100,000 Commerce.com storefronts. WebMCP is an experimental browser standard proposed by Google: the page declares tools such as search_products and add_to_cart to the agent, and the agent calls them instead of guessing which button to press. The tools run in the shopper's session on the store's domain, so the agent sees the same prices and the same cart, and the credentials stay where they are. The shopper clicks checkout themselves. The standard is still behind Chrome flags and in Origin Trials.

On October 13, Shopify announced Shop MCP: a single connection to mcp.shop.com gives an agent search across more than a billion products, a cart and checkout through Shop Pay. Search works without an API key. A purchase is completed with a complete_checkout call, but only after the shopper has confirmed the amount and the payment method. There are no webhooks at launch, so checkout status has to be polled through get_checkout.

On October 23, Vercel added managed Stripe keys to Vercel Connect: each agent or task gets its own restricted key, with permissions you choose. A reporting agent gets read-only access to payments, an onboarding agent can only write customers. Of all this news, I like this one best: most integrations still run on a single key with full access.

On October 22, Stripe summed up Money20/20 in one paragraph: stablecoins, agents and “always-on” money are pushing financial infrastructure into the background. I didn't see anything beyond the announcement.

On October 22, Apple opened volume purchasing of app subscriptions through Apple Business Manager and Apple School Manager: an organization buys the number of seats it needs and hands them out through its own device management tools. If you sell your product to companies on a subscription, check the setting in App Store Connect.

Example: car rental and the insurance add-on

Take a car rental company. Today a customer books through the website, tomorrow through an agent on their phone. The agent will pick the car and the dates. But the extra insurance is cheap, it's useful for the customer to remember it, and for the company it's an additional sale. An agent hunting for the lowest price will skip it.

So you can hand search and order assembly to the agent. The steps where the company earns money or takes on risk should be written as rules in the system, and then it doesn't matter who put the cart together.

Where I draw the line

At a car rental company in South Africa, starting in October 2024, I took the website to a full booking cycle, all the way to passing the data into the managers' internal app. During booking the site offers extra services on its own, including that same insurance. Payment is checked against a screenshot the customer attaches: it's a check by image, with no automatic reconciliation with the bank.

In the “Coffee Together” service, which I built in September and October 2026, the line is drawn more strictly. An employee picks an exact item from the Tasty Coffee catalog, the format, the package size and the quantity; free text can't be submitted. With one button the organizer combines requests into a single supplier order, and the service fills the cart in the supplier's wholesale account by itself. But placing and paying for the order with the supplier stays manual: the integration never clicks the final button. The service allows the “Ordered” mark only after every payment has been checked and the order has actually been placed. I did this on purpose: the total appears only after the real cart is reconciled with the supplier's discount, and the person responsible for the money should confirm it. Altogether the service saves employees and administrators more than 100 hours a month.

On my own website in October I added llms.txt and Markdown versions of the pages in four languages. Same idea as Vercel Shop, only for services. I don't have numbers on the effect yet.

What I would do

Write down in the system which steps an agent can do on its own: search, selection, cart.

Single out the steps that involve money and risk: confirming the amount, payment, handover. A person stays on those, and the system doesn't let anyone get around them, whether it's an agent or an employee going through the API.

Give integrations separate keys with minimal permissions, the way Vercel did for Stripe. In my “Coffee Together” service the wholesale account login sits in private server environment variables, and the token exists only in memory.

I covered what to define before development in the article What to decide before building a rental app. Earlier I wrote about which terms get lost outside the product page and how to tie together a payment attempt, a cancellation and the account record. On the same topic: business logic flaws in bookings and carts and a customer portal with finger signing. Services: a customer product connected to the business and API integrations. Projects: car rental in South Africa and “Coffee Together”. If your orders or bookings pass through several hands, tell me where a person stands in the process today and why. Discuss your task.