Shoe sizes
TryYourSize answers shoe sizes with the same elements, events and API as clothing. Shoppers who added their feet see their size for your shoes; everyone else sees nothing new. Feet are optional for shoppers, and footwear is optional for your store.
For your store
Section titled “For your store”- In Studio, create a product with the category Footwear.
- On its Size chart tab, enter your sizes as you publish them (EU, UK, US men, US women or Mondopoint; choose which one your store shows), the length per size, and the shoe type (sneaker, dress shoe, boot, sandal). Width fittings (narrow, wide, E, EE…), width and ball girth are optional.
- Publish. Footwear has no 3D view and no fit check to approve.
Your integration does not change: sizeGuide, the inline element and the recommendation event work for footwear products as they do for clothing.
What shoppers see
Section titled “What shoppers see”| Shopper | What they see |
|---|---|
| Added their feet | “Your size: 40”, or “between 40 and 41” when their foot sits at the boundary of two sizes |
| No feet yet | Your size guide as today, and an optional “Add my feet” in the TryYourSize window |
Answers are numbers, not opinions: the room in front of the toes and how the width compares with the foot, per size. Shoppers measure their feet once at home with paper and a pen; it takes about two minutes.
In your code
Section titled “In your code”The recommendation event for a footwear product has the usual status and size. When the foot sits between two sizes, it also has between, in your size labels:
el.on("recommendation", (r) => { if (r.status !== "ready") return; // r.size: the size to preselect ("41"); r.between: ["40", "41"] or undefined preselect(r.size);});Was this page helpful?
Thank you. We read every answer.