On this page
A growing share of shoppers no longer type "women's medium dress" into a search bar — they ask an AI assistant "will this fit me" and expect a direct answer. That question can only be answered well if the brand behind the product has published fit data the assistant can actually read. Most haven't, and it's starting to cost them visibility.
A New Purchase Flow: Asking Before Clicking
The old funnel was browse, click, check the size chart, guess, buy. The emerging one is different: a shopper describes themselves once to an AI assistant — height, usual size in a familiar brand, maybe a fit preference — and then asks that assistant to shop across multiple sites on their behalf. Google has folded a "try it on" experience directly into Search, letting people preview garments on a body-shaped model without leaving the results page, while a separate standalone try-on app, Doppl, was wound down in 2026 as the capability consolidated into core Search instead. That consolidation matters: it signals the feature is becoming infrastructure, not a novelty experiment.
When an assistant is doing the comparing, it isn't reading marketing copy or looking at lifestyle photography the way a human would. It's parsing whatever structured data it can access — product attributes, size charts, return policies, and increasingly, fit metadata. If that data doesn't exist in a machine-readable form, the assistant either skips the product, falls back to a generic size chart lookup, or — worse — guesses, and gets it wrong in a way the shopper blames on the brand, not the AI.
What "Machine-Readable Fit Data" Actually Means
Concretely, this is not the same thing as having a nice-looking size chart page for humans. An AI assistant needs data it can query and compare across brands without a person interpreting a table. That includes garment measurements in consistent units, not just letter sizes; body-to-garment fit mapping (how much ease a "regular fit" tee actually has at the chest); and ideally a structured recommendation input/output pair — given a shopper's measurements, what size does the brand itself recommend.
A useful mental model: a size chart tells a human "here are the numbers." A size recommendation system tells a shopper "here is your size," having done the comparison already. AI assistants are far better suited to consuming the second kind of data, because it's already a decision, not a table they'd have to reason over themselves — and reasoning over inconsistent brand-specific sizing is exactly where these systems still make mistakes.
| Data type | Human-readable? | AI-queryable? |
|---|---|---|
| Marketing description ("relaxed, breathable fit") | Yes | Poorly |
| Static size chart image | Yes | Rarely (needs OCR/inference) |
| Structured size chart (HTML table / schema) | Yes | Yes, with effort |
| Garment measurement API / fit engine output | No (raw) | Yes, directly |
Why the Gap Hurts Conversion, Not Just Accuracy
Consider the mechanics of an AI-mediated purchase: if the assistant can't confidently state a size, it will either present the item with a hedge ("check the size chart yourself") or drop it from the shortlist entirely in favor of a competitor whose data resolved cleanly. Neither outcome is neutral for the brand — one adds friction back into a flow that was supposed to remove it, and the other means the product never gets shown at all.
This is a variant of a problem the industry already understands well from search and cart behavior. Fashion brands have spent years fighting cart abandonment caused by sizing uncertainty; an AI assistant that can't resolve fit is essentially reintroducing that uncertainty at an earlier stage, before the shopper even reaches the product page. The National Retail Federation has documented that the US online return rate sits near 19-20%, with apparel and footwear among the highest-return categories — a large share of that is fit-driven, and unresolved fit questions upstream tend to show up as returns downstream regardless of which channel drove the sale.
The Cost of Getting Recommended Wrong
There's also a downside scenario that's easy to overlook: being recommended, but inaccurately. If an assistant guesses a size using generic body-type assumptions rather than actual brand measurements, and the shopper buys and it doesn't fit, the return happens exactly as it would with a bad size-chart guess — except now the shopper trusted an AI's confident-sounding answer, which can make the disappointment (and the negative brand association) sharper. Returns already cost fashion brands an estimated $40 billion or more per year globally, according to McKinsey, and fit-driven AI mis-recommendations are a plausible new contributor to that figure rather than a one-off edge case.
Brands that have historically treated their size chart as a static PDF or a low-priority page are the most exposed here. It's worth revisiting how to read a size chart correctly as a baseline, but the more urgent question for 2026 is whether that chart exists anywhere an assistant can actually parse it — as structured markup, an API, or a feed — rather than only as an image embedded in a product description.
Where YourSizer Fits
YourSizer's core function — turning a shopper's measurements into a specific, brand-accurate size recommendation — happens to produce exactly the kind of structured output AI shopping assistants need to consume. Instead of an assistant trying to infer fit from a static chart or generic body-type heuristics, a brand running YourSizer already has a live mapping between shopper inputs and garment-specific size outputs, generated per product rather than guessed at a category level.
This isn't a claim that YourSizer is "built for AI shopping" as a headline feature — it's simpler than that. A size recommendation engine that already resolves fit accurately for human shoppers on-site is, by construction, closer to being legible to an assistant trying to do the same job on the shopper's behalf. Brands evaluating size recommendation solutions in 2026 should treat "does this data have a shape a machine can query" as a real evaluation criterion, not an afterthought.
Frequently Asked Questions
Do AI shopping assistants actually check size charts today?
Increasingly, yes, though the sophistication varies widely by platform and by how well-structured the merchant's own data is. Assistants integrated into search engines and shopping apps generally try to pull whatever sizing information is exposed in a product feed or on-page markup, and the results are only as good as that source data — a brand with clean, structured measurements gets a meaningfully better outcome than one relying on a plain-text description.
Is this different from having good SEO for product pages?
It overlaps but isn't identical. Traditional SEO optimizes for how a page ranks and reads to a search crawler and, ultimately, a human clicking through. Fit-data readiness is about whether a specific, narrow slice of information — garment measurements and size logic — is exposed in a form an automated system can extract and reason over without misinterpreting a marketing phrase like "true to size" as a precise measurement.
What should a brand do first if it has no structured fit data at all?
The most practical starting point is auditing whether size charts exist as structured HTML or data rather than only as images, and whether there's any per-product fit logic beyond a generic chart shared across dozens of styles. Brands that already use a size recommendation tool are generally in better shape here than those relying purely on static charts, since the underlying comparison logic already exists in a queryable form somewhere in the stack.
Conclusion
AI-mediated shopping is still early, but the direction is clear: the assistants doing the comparing on a shopper's behalf will keep rewarding brands whose fit data is structured and machine-readable, and keep skipping or mishandling the ones whose sizing only makes sense to a human reading a page. Treating fit data as an accuracy problem worth solving now, rather than a formatting detail to clean up later, is likely to matter more with each product cycle as this behavior moves from novelty to habit.
