Product Data in Running Retail: Shoe Technology and Sizing Logic Under Control

A running shoe looks like a simple product until you try to describe it in data. A customer wants to know the drop, whether it's a neutral or stability shoe, how heavy it is and how much cushioning it carries — and then they need it in exactly their size and width. Two data jobs in one product: a set of technology attributes that only matter if they're comparable across brands, and a size-and-width run that only works if every variant is modeled cleanly.

Product data for running shoes lives on two axes at once: technology attributes as the comparison basis, and size-width variants as the buying decision. This is a focused corner of the broader sports & outdoor challenge, and it overlaps heavily with the footwear data logic — but running pushes both problems to their extreme.

Why are running shoe technology attributes so hard to compare?

Running is a category where customers genuinely shop on specs. Drop, stack height, weight and pronation support are the attributes a serious runner filters and compares on. The trouble is that no two brands describe them the same way:

• Drop (heel-to-toe offset): sometimes a clean millimeter value in a feed, sometimes buried in a PDF datasheet, sometimes only implied by two separate stack numbers.
• Cushioning: one brand markets a trademarked foam name, the next gives a stack height, a third only describes the ride in prose — three ways to say the same thing.
• Pronation support: neutral vs. stability vs. motion control, labeled inconsistently or left out entirely.
• Weight and use case: weight varies by sample size, and terms like „daily trainer", „tempo" or „race" are marketing words, not structured fields.

To let a customer filter by drop or compare cushioning across brands, you first have to pull those attributes out of inconsistent feeds and map them to one shared set. That mapping is the comparison basis — without it, the filters on your shop are lying.

How do you unify sizes and widths across brands?

The second axis is fit, and it's where the SKU count explodes. The same foot maps to different EU, UK and US numbers depending on the brand, widths are labeled inconsistently (or not at all), and half sizes appear in some ranges but not others. A clean running catalog has to solve all of it:

Get this wrong and stock, ordering and returns all drift. The key insight: each size-and-width combination is its own variant with its own EAN/GTIN, but all of them must stay linked to one parent shoe so the technology attributes are shared, not duplicated.

Where do FEDAS and the pools stop?

FEDAS classifies the article as a running shoe and gives the assortment a shared merchandise-group language — genuinely useful for structure. Buying-group pools (Intersport, Sport 2000) deliver clean master records for the big listed running brands. But both stop well short of what a running catalog needs: FEDAS carries no drop, no stack height, no cushioning attribute and no size-width matrix, and the pools cover only the listed brands — not the smaller labels, own brands or accessories. The technology depth and the sizing logic are exactly the layer no standard hands you, which is why the manual work never disappears. It's the same gap the whole footwear category lives with, just sharper because runners compare on numbers.

How does Productbay keep running shoe data clean?

Productbay is built for exactly this two-axis job — comparable attributes plus clean variants — with linked attributes as the core of the sizing logic:

• Consolidate: import every brand feed once — CSV, Excel, feed URL, FTP, API — and match by SKU or EAN/GTIN so existing shoes update and new models are created, each as a parent article.
• Model the fit: every size and width becomes a linked variant with its own EAN/GTIN, all tied back to one parent shoe so the technology attributes are shared once, not re-entered per size.
• Enrich the technology: AI parses drop, stack, cushioning, weight and support out of titles and PDF datasheets, maps brand sizes to your unified scale and width scheme, writes descriptions and fills gaps from whitelisted sources — always with a review queue before anything publishes.
• Publish: two-way sync to Shopify and Shopware, ERP connections (Xentral, weclapp) and feed exports for Amazon, OTTO and Kaufland — each with per-channel transformations.

The payoff is a catalog where a customer can filter by drop, compare cushioning across brands and land on exactly their size and width — because the attributes are comparable and the variants stay linked. Productbay is built for specialist retailers running multi-supplier, multi-channel catalogs, from mid-sized shops to large chains.

Frequently Asked Questions