Starting May 30th, Amazon will require shoe size inputs to be of a standardized format. Taken from the updated help page on the topic, here’s what they’ll be looking for.
- Target gender (ex: female)
- Age range description (ex: toddler)
- Footwear size system (ex: US)
- Footwear age group (ex: toddler)
- Footwear gender (ex: women) – this one isn’t required under all cases, and can differ from Target gender. It’s necessary when the Target genderis Adult.
- Footwear size class (ex: numeric range, alpha/alpha-range, etc.)
- Footwear width (ex: wide)
- Footwear size: (ex: 9.5)
- Footwear to size (ex: 10.5) – this one is only mandatory when Footwear size classis one of the “Ranges.” Footwear sizedenotes the lower end of the range, and this field denotes the other end of the size range. Setting Footwear sizeto 9.5 and Footwear to sizeto 10.5 would create a final value of 9.5-10.5.
- Opposite gender size for unisex products. If a shoe’s Target genderis Unisex and Footwear age groupis Adult, this field describes the shoe size translated into both men’s and women’s sizes for accurate comparison shopping (ex: 10 US Men/12 US Women)
The help doc goes into significant detail about each of the attributes and the logic for each, as well. The doc is worth a read if you’re listing shoes for the first time.
The paragraph that stood out the most is how Amazon is going to handle region-specific width measurements. Some brands/regions have different width metrics (“extra wide” versus “x-wide”, for example). Amazon very plainly states that all width measurements will now be in X-width format (ex: XX-Wide, Narrow, 3X-Narrow, etc.).
All this seems pretty straight forward. There’s some new work that needs doing to bring existing listings into compliance. Amazon has given the deadline of August 30th to make that happen. Unless one has thousands of pairs of shoes or terrible sizing data, this is a no-brainer. Get it done now while it’s still fresh in mind.
The new fields and templates go live on May 30th.