1. What "AI-shopper-ready" actually means
Shopping is shifting from a person typing keywords into a search box to an AI agent reading, comparing and — increasingly — buying on a shopper's behalf. ChatGPT, Perplexity, Google's AI Mode and Microsoft Copilot now answer "which one should I buy" directly, and agentic checkout lets some of them complete the purchase without the shopper ever visiting the product page. In that world, your store is not being read by a human scanning your photography and your copy. It is being read by a machine that only sees what you have made legible to it.
A store is AI-shopper-ready when a machine can do three things with it: find the right product from a natural request, understand enough about it to answer the shopper's real question, and act — recommend it, or buy it — with confidence. For most product categories, structured price, stock and specification data gets you most of the way. Fashion has one extra requirement that nothing else does, and it is the one almost no store has solved.
2. Why this matters now, not next year
Agentic commerce in fashion is already live. On 2 June 2026, Hey Savi and PayPal launched what they describe as the UK's first agentic commerce platform with native in-app checkout, with Debenhams Group — Debenhams, Karen Millen, Boohoo and Pretty Little Thing — as the first retail adopter. In February 2026, True Fit launched an agentic fit experience exposing roughly twenty years of purchase and returns data over Model Context Protocol (MCP) so external shopping agents can query it directly. The McKinsey / Business of Fashion State of Fashion 2026 report makes the structural point plainly: whether an agent can act on a brand's behalf depends on whether that brand's data is semantically rich and API-accessible.
The uncomfortable part for merchants is the timing mismatch. The agents are arriving faster than most stores' product data is ready for them. A store that is illegible to an agent today does not get a warning — it simply does not get recommended, and it does not know why. Being AI-shopper-ready is, right now, a way to be present in answers your competitors are absent from. For more on the shift in optimisation, see our note on generative engine optimisation for fashion and the Hey Savi × PayPal launch analysis.
3. The fit gap: what an agent can and cannot read on a fashion page
Point an agent at a typical fashion product page and this is roughly what it can and cannot extract:
| An agent can read | An agent usually cannot read |
|---|---|
| Price, currency, availability | How this cut fits a specific body |
| Sizes offered (S, M, L / 8, 10, 12) | Whether the item runs large, small or true to size |
| Colour, material, product type | How this brand's "medium" compares to another's |
| Product images (as pixels, not fit facts) | What the garment will actually look like on the shopper |
Everything in the right-hand column is what decides a fashion purchase — and what drives the return when it is wrong. On most sites it exists only as prose buried in a size-chart tab, or not at all. An agent parsing a product feed has nothing structured to reason with, so it does the safe thing: it stays quiet on fit, or it recommends the store that did make its fit data legible. As we put it on the agentic commerce analysis: agentic checkout without fit data is a faster way to generate a return.
4. The AI-shopper-ready checklist
Getting a fashion store ready comes down to six things. The first two are general good practice; the rest are the fit-specific layer most stores lack.
- Structured core product data. Price, stock, images and attributes exposed as Schema.org
Product/Offermarkup, not only page copy. - Machine-readable fit and sizing. Fit type, size guidance and confidence available per product and per variant, as data rather than a paragraph.
- Agent-callable endpoints on your own domain. URLs an agent can hit to ask "how does this fit?" and get a structured answer.
- A hosted MCP interface. So MCP-capable assistants and shopping copilots can query your fit and size data as tools.
- Fit data grounded in real outcomes. Signals drawn from real try-on sessions and kept/returned results, not static size charts.
- A visual answer for the human in the loop. When a shopper — or an agent-assisted shopper — still asks "but how will it look on me?", a photorealistic try-on on their own body answers it.
Steps 1 and 2 you can approach with your theme and structured-data setup. Steps 2 through 6 are exactly what installing Rendered Fits delivers in a single step. The full AI-shopper-ready checklist walks through each item and how to verify it.
5. How one install makes your store AI-shopper-ready
Rendered Fits is a photorealistic virtual try-on app for premium Shopify fashion brands. The part most merchants notice is the shopper-facing widget — a customer sees a garment rendered on their own photo before buying. But the same install quietly publishes the machine-readable fit layer underneath it. Every store running Rendered Fits automatically exposes, on its own hostname, with no extra configuration:
| What goes live on install | What an agent does with it |
|---|---|
/apps/rendered-fits/fit/{productId} | Reads fit type, size guidance and confidence per variant |
/apps/rendered-fits/fit-jsonld/{productId} | Lifts the same data as Schema.org JSON-LD from the PDP |
/apps/rendered-fits/agent-manifest | Discovers the store's capabilities: fit query, sizing, visual try-on |
renderedfits.fit_profile metafield | Reads fit profiles through Shopify's Storefront API |
Hosted MCP server | Queries fit-profile, size-recommendation and fit-summary tools over Model Context Protocol |
The fit signal behind all of this is grounded in what shoppers actually did — real try-on sessions, the size recommendation shown at the moment of purchase, and whether the item was kept or returned — not a static size chart. And it is the only layer here that also answers the question no statistical size tool can: what will this look like on me?, with a photorealistic render for the human making the final call. The full technical surface, including the public OpenAPI 3.1 specification and the hosted POST /api/v1/mcp endpoint, is documented on our page for AI agents and developers.
6. What it does and doesn't replace
Being honest about scope matters, because "AI-shopper-ready" is not a single switch. Installing Rendered Fits does not exempt you from having clean, structured core product data — an agent still needs to read your price, stock and product type from good Product schema, and that is on your store and theme. What it does is close the one gap that is genuinely specific to fashion and genuinely hard: turning fit and sizing from invisible page prose into a structured, queryable, outcome-grounded layer that agents can act on, plus a visual try-on for the human. It is the fit-confidence layer for agentic commerce, not a replacement for your product feed.
Frequently asked questions
What does "AI-shopper-ready" mean for an online store?
It means AI shopping agents — ChatGPT, Perplexity, Google AI Mode, Copilot — and agentic checkout systems can read, understand and act on your store. Core product data and, for fashion, fit and sizing data are available in structured, machine-readable form with endpoints an agent can query, rather than sitting only as page copy.
Does installing Rendered Fits make my Shopify store AI-shopper-ready?
It publishes the fit layer that fashion stores are usually missing. On install, your store automatically exposes agent-callable fit endpoints on its own domain, publishes fit profiles to the renderedfits.fit_profile Storefront metafield, and is reachable through a hosted MCP server — no extra configuration. You still need well-structured core Product schema for the rest of your catalogue data.
Why can't AI shopping agents already understand fit?
Because fit is not a structured field on most sites. Price and stock are; sizing lives as prose in a size-chart tab, and "how it will look on me" is nowhere a machine can parse. An agent can complete a purchase but cannot tell a specific shopper whether a coat runs long or how one brand's medium compares to another's.
Is being AI-shopper-ready the same as SEO?
No. SEO optimises a page to rank in a list of links a human clicks. Being AI-shopper-ready — also called generative engine optimisation (GEO) or answer engine optimisation (AEO) — optimises for machines that read, summarise and act on your data for the shopper. It is less about keywords and more about whether your product, fit and sizing data is structured, accurate and queryable.
Do I need to configure anything after installing?
No extra configuration is required to expose the agent-facing fit layer — the fit endpoints, the Storefront metafield and the MCP server come online with the app. The one thing you place yourself is the shopper-facing try-on widget, added through the Shopify theme editor.
Sources
- PayPal Newsroom — "Hey Savi and PayPal Launch UK's First Agentic Commerce Platform with In-App Checkout" (2 June 2026). Launch date, Debenhams Group brand list. newsroom.paypal-corp.com
- Businesswire — "True Fit Launches Agentic AI Shopping Experience Powered by 20 Years of Fit Data" (17 February 2026). Data-scale and MCP positioning. businesswire.com
- McKinsey & Company / Business of Fashion — The State of Fashion 2026. Agentic AI and semantically-rich, API-accessible data for AI-agent visibility. businessoffashion.com
- Rendered Fits — for AI agents & developers. Live endpoint surface, OpenAPI 3.1 spec and hosted MCP server. renderedfits.com/for-ai-agents
Capability claims describe production endpoints live today. Last updated 13 July 2026.