Product Data
Sneaker Size Availability
A shoe marked in stock but available only in sizes no one wants is, to most buyers, out of stock.
Updated 2026-07-01 · 7 min read
For most products, a single in-stock flag is enough. For footwear it is almost meaningless. A shoe is not one item but a grid of sizes, and its availability is the pattern of which of those sizes are in stock — not a single boolean. A listing marked available may have nothing in the size a given shopper needs, which from that shopper's point of view is indistinguishable from out of stock.
This page argues that size-level availability is the unit that matters for footwear discovery, explains size runs and regional size systems, and connects the data problem to offer quality and normalization. It is a companion to buyer-facing size and fit guidance, but focused on the data layer beneath it.
Why product-level stock is insufficient
Product-level stock answers the wrong question. It tells a shopper that the shoe exists somewhere in some size, not that it exists in their size. Because footwear demand is concentrated in common sizes and long-tail at the extremes, a product can be technically in stock while being unavailable to the majority of interested buyers, or available only at the ends of the size run.
The consequence for a discovery platform is that ranking and filtering on product-level stock produces misleading results. A shoe surfaced as available can lead the shopper to a dead end on the merchant's page, which erodes trust in the platform even though the merchant, not the platform, holds the missing stock. Size-level data is what prevents that.
Per-size stock as the real unit
The meaningful availability signal is per-size: for each size in the run, is it in stock at this merchant, at what price, and how fresh is that information. Held this way, availability supports the questions buyers actually ask — is my size available anywhere, which shops have it, and is it discounted in my size specifically.
Capturing per-size stock requires the pipeline to preserve the size grid rather than collapsing it. During normalization, each size variant is kept as its own availability entry with its own timestamp, so the platform can answer size-specific queries and can tell when a particular size's data has gone stale. Collapsing the grid to save space is a false economy — it discards exactly the information footwear buyers care about most.
Size runs and their shape
A size run is the set of sizes a shoe is offered in, and its shape carries information. Availability across a run is rarely uniform: middle sizes sell through fastest, extremes linger, and a shoe late in its life cycle often shows a characteristic gap-toothed pattern of scattered remaining sizes. Reading that pattern helps a platform judge how genuinely available a shoe is.
Size runs also differ by audience. Men's, women's, and unisex runs overlap but are labelled differently, and a shoe cut for one audience may map awkwardly onto another's sizing. A discovery platform that wants to answer "in my size" has to understand which run a size belongs to before it can match it to a shopper's stated size — otherwise it risks offering a size that does not mean what the shopper thinks.
Regional size systems
Sizing is fragmented across regional systems — EU, UK, US and Japanese conventions among them — and the same physical shoe carries different numbers depending on the market a retailer serves. A cross-border platform therefore cannot compare sizes as raw numbers; it has to normalise them to a common reference so that a size in one system can be matched against the same physical size expressed in another.
This normalisation is approximate at the edges, because conversions between systems are not always exact and brands vary in fit. The platform should convert to a canonical scale for matching while retaining the original labels for display, so a shopper sees the size in the terms their market uses even though the system matched on a normalised value underneath. This is central to cross-border search and to any platform serving multiple regions.
Freshness and the cost of being wrong
Per-size availability decays faster than almost any other field, because a popular size can sell out between feed refreshes. Stale size data is worse than stale price data: a wrong price disappoints, but a wrong size sends the shopper to a page where the thing they came for is simply not there. Each size entry therefore needs its own freshness stamp, and stale entries should be flagged or suppressed rather than shown as confident fact.
This ties size availability directly to offer quality and to price freshness: the trustworthiness of a listing depends on the freshness of its most volatile fields, and for footwear the most volatile field of all is often per-size stock.
Sources & further reading
- Google Search Central, “Product availability and variant structured data” (2024)
Sources are attributed to their publishers and link to each publisher's own site. Figures reflect general market direction rather than point-in-time precision; consult the linked publishers for their current data.