What must an AI shopping agent do before placing an order?

What changed, and when.

Shopify announced Checkout WebMCP on 28 September 2026. It lets an agent operating in the buyer's browser read and update an eligible checkout, then place the order after the buyer confirms it. Shopify announced Shop MCP on 13 October 2026 as a separate way for compatible agents to search its catalogue, build carts and complete Shop Pay checkout through one connection. We rechecked both announcements and current checkout documentation on 27 October. The September browser feature and October agent connection are different paths; neither announcement proves that a particular retailer's checkout or agent works today. See sources 1–4.

The business question.

Noesis analysis: can a shopper see and approve the exact order the agent is about to submit? A request such as 'buy a gift' does not settle the final product, delivery option, payment method or total. For a retailer, the practical question is how the customer journey handles a changed amount, a required payment challenge and an uncertain order result. A team building the agent must connect permission to the current order, not to an earlier instruction.

A hypothetical purchase.

Imagine a buyer asking an agent to order a gift. The agent selects an item, but the delivery choice changes the total. Noesis recommendation: show the current order and amount, get fresh permission, and let the buyer handle any required review or payment step. This is an invented scenario, not a Noesis client result or a live Shopify test. The first test should use a test store and payment method, never an actual customer's details.

Choose the right checkout path.

Shopify's current guidance distinguishes Checkout MCP, run from an agent's server, from Checkout WebMCP, which operates on the checkout open in the buyer's browser. Shopify recommends the server path unless the agent needs to run in that browser. The browser tools can read checkout state, update supported fields, return to the storefront and call completion after buyer confirmation. Browser updates do not change line items or attribution. Shop MCP is another agent connection announced in October; it can build a cart and use Shop Pay after the shopper signs in and confirms the total and payment method. Do not treat these interfaces as interchangeable or assume every checkout exposes browser tools. See sources 2–4.

Test the complete journey before release.

Noesis recommendation: select one eligible buying path in a test environment. Write the expected product, delivery option, total and order status before asking an agent to act. Include the person who owns customer support, because a technically valid tool response may still leave a customer with an unresolved purchase.

• Read the latest checkout state before an update. Compare the visible item, amount and delivery choice with the agent's summary.
• Change a discount or delivery option. Require the buyer to confirm the new total before completion.
• Run a case that needs buyer action, such as payment authentication or a checkout review step. Check the handoff back to the person.
• Simulate a delayed or failed update. Read the current state before retrying; do not submit again while the order result is unknown.
• Confirm an order only from a completed checkout status and receipt, then reconcile it in the merchant's test orders and support workflow.

Know the documented limits.

Checkout WebMCP is not registered for standard three-page checkout unless the buyer uses Shop Pay, B2B checkout, embedded or mobile SDK checkout, multi-shop merchandise, draft orders, order edits or payment collection. App-defined checkout extension interactions stay with the buyer on the page. Shopify's documentation also says a ready-for-complete state and agent authentication do not grant permission to place an order; the buyer must confirm the current order and total, and must be asked again if the total changes. Only completed status confirms the order. Shop MCP's October announcement says existing Catalog API integrations need no immediate action and that checkout status must be polled because it has no webhooks at launch. See sources 2–4.

Make the first scope measurable.

Noesis analysis: map one buying journey, the points where a person must act, and the evidence support needs if a purchase fails or is disputed. Measure incomplete checkouts, buyer corrections and orders needing manual help against a baseline. Bring this map to a commerce systems review before adding agent-specific features. This note is based on Shopify documentation, not hands-on verification, and it does not promise higher conversion or lower support cost.