Search Engine Journal reports that none of 122 leading Shopify storefronts passed all nine purchase-decision checks in probes conducted during August and September 2026. The audit tested different groups of stores for different functions, and its results show uneven performance across checkout, policy answers and product-page accessibility (Search Engine Journal’s audit).
What the audit tested
The audit examined 122 leading Shopify storefronts, with test groups that varied by task: 88 stores for policy-tool questions, 74 for live checkout, 68 for product-page accessibility and two for browser-based WebMCP checkout. It also checked policy text at 56 stores.
That distinction matters when applying the results: a figure from one test group does not describe every store or every function. The audit also supplied each store with the product to buy, so it did not assess whether an agent could choose among sizes, models or related products.
Checkout tools still require buyer involvement
In all 74 live Universal Commerce Protocol (UCP) checkout tests, the audit reports that a checkout could be created for one in-stock item directed to a Boston address, read and canceled. Each returned a handoff URL, and all 74 required buyer input or escalation. The tests did not submit an order or send payment details; a repeat cancellation returned a coded refusal.
Shopify’s September 28, 2026, announcement describes WebMCP checkout tools operating in the buyer’s browser session. The tools can navigate to a storefront, read and update checkout, and submit it after buyer confirmation. Shopify says the tools return control to the buyer when more input is needed, including for 3D Secure (Shopify Developer Changelog).
Search Engine Journal’s separate browser test on September 30 covered two stores. It read checkout state without submitting orders, a narrower test than a completed purchase.
Which buyer questions policy tools answered
In the audit’s 88-store policy-tool cohort, usable answers varied sharply by question. A return-window question received a usable answer from 70 stores; only two gave a usable answer about when a buyer could cancel after ordering.
| Buyer question | Stores with a usable answer | Policy-tool cohort |
| What is the return window? | 70 | 88 |
| What is shipping cost to Boston, and when will it arrive? | 0 | 88 |
| How long after ordering can a buyer cancel? | 2 | 88 |
| Can a buyer return a used or open-box item? | 5 | 88 |
The live-checkout results show a related gap in fulfillment details: 36 of 74 tests returned a shipping price to the tested Boston address, while none returned an arrival estimate or carrier. Across 93 stores with UCP fulfillment declarations, the audit found shipping listed but no pickup declaration. These findings make the exact buyer question important: an answer about the return window does not tell a shopper what shipping will cost or when a package will arrive.
What the UCP order specification lists
UCP describes order records, adjustments, an order-event webhook and a dev.ucp.shopping.order:manage scope for post-purchase operations. Its operations table lists order retrieval through GET /orders/{id} and the webhook, but no command to cancel, amend or return an order (UCP Order Capability specification).
That protocol distinction is separate from the audit’s finding that none of the 122 tested stores exposed an agent tool to cancel, change or return an order. The specification includes post-order data and permissions; its listed operations do not provide an order-mutation command.
Checks merchants can apply to their own stores
A practical way to use these findings is to try buyer-worded questions against the store’s agent-facing tools: ask about the return window, shipping cost and arrival time, cancellation timing, and eligibility for used or open-box returns. Then check whether the answers are usable and whether the fulfillment information reflects the store’s actual options, including pickup when offered. These checks address the specific gaps measured in the audit; they do not predict recommendations or sales.
Product-page accessibility is another distinct part of readiness. In its static server-HTML checks of 68 stores, the audit found that 31 passed its full semantic floor and 19 had no add-to-cart control in the HTML. The audit notes that JavaScript-added content may not appear in a server-HTML check, so merchants can also inspect how their product controls and labels appear to an agent in practice.
In a Shopify subreddit discussion, u/TheCryptoBillionaire recommended plain-language product details, FAQs, policies and collection copy. u/Agitated_Offer_4343 raised a related concern about size charts or return policies presented only as graphics (the discussion).
Shopify says its product-page readiness signals are informational and do not guarantee that agents will surface products. It also says Agentic Storefronts are enabled automatically only for eligible stores (Shopify’s agent-readiness page).
