Product Data for Women's, Men's & Kids' Shoes: Getting Size Runs Under Control

A customer looks at a trail shoe online. They wear EU 42.5. The size dropdown jumps from 42 to 43. Do they buy the 43 and hope? Do they leave? In footwear, the answer to that question is decided long before the product page renders — in the product data. And shoe sizing is one of the messiest data problems in retail, because there is no single system to lean on.

Product data for shoe sizes is the discipline of modelling complete, consistent size runs across incompatible size systems. Women's, men's and kids' shoes each behave differently, and the same physical shoe arrives from different suppliers under different labels. This is a sub-topic of the broader challenge of product data in footwear retail — the segment where size, color and width already make every article a matrix.

Why do shoe sizes differ across women's, men's and kids' segments?

The core issue is that "size" is not one thing. Each segment carries its own conventions, and a shoe assortment has to hold all of them at once:

• Women's: typically EU 35–43, frequently with half sizes, and often given in a UK or US scale on imported brands.
• Men's: typically EU 39–48, half sizes, plus widths (comfort, wide) on many brands — a second axis on top of length.
• Kids': its own logic entirely — small steps, frequent buying by inner-length in centimeters, and the same EU number spanning different age groups across brands.
• Cross-system labels: the same shoe can arrive as EU 42, UK 8 or US 9 depending on where the supplier data originates.

Put a half-size run and a width axis together and one model can become dozens of size variants — each needing an EAN/GTIN, each needing to be mapped to a leading system so the shop filter and the size advisor actually work.

What makes a size run complete — and why does an incomplete one cost sales?

A size run is the full range a model is offered in — say EU 40 to 46 with half sizes. The run is a property of the model; stock is a separate, changing fact. Confusing the two is where the money leaks:

• If a size is missing from the data, the shop can't show it at all — it looks like the shoe was never made in that size.
• If a size is in the run but out of stock, the shop can show it greyed out, offer a notify-me, and keep the customer.
• Suppliers often deliver only the currently-available sizes, so importing stock-as-run silently amputates the run every time inventory dips.

Clean product data keeps the size run and the availability as two separate attributes. The run comes from the model master data; stock comes from the feed. That separation is what lets you offer half sizes, back-in-stock alerts and honest size filters instead of a dropdown full of holes.

Which size systems and standards exist — and where do they stop?

There is no ISO-clean, universally-applied shoe size standard the way there is a GTIN for identification. What you actually have is a set of scales that need mapping between them:

In short: a GTIN tells you which variant, but not that EU 42 equals UK 8. That translation — and keeping it consistent across women's, men's and kids' — is manual work unless it lives in a maintained mapping.

How does Productbay handle shoe size runs?

The fix is to stop treating sizes as free text on each article and start treating them as linked attributes — and that's exactly how Productbay models them:

• Central size catalog: one maintained set of size systems and EU/UK/US conversion tables, referenced by every article instead of retyped per supplier. Change the mapping once, and it applies everywhere.
• Normalize on import: incoming supplier sizes are matched to the leading system, half sizes and widths are aligned, and a gap in a run is flagged for review — so an incomplete run never silently goes live. Read more on how we consolidate and normalize multi-supplier data.
• AI fills the gaps: AI reads missing size, width or inner-length attributes out of datasheets and whitelisted sources, and can assign the right category — always with a review step before publish.

The result: a size run that stays complete and consistent from supplier import to shop, ERP and marketplace. Productbay is built for specialist retailers running multi-supplier, multi-channel footwear catalogs, and it's the same engine that manages images and media via DAM next to the size data.

Frequently Asked Questions