Choose an outcome
Start from the result you want a shopper to get. The store platform comes after that.
| You sell | The shopper should | Open |
|---|---|---|
| Shoes | See the shoe on their feet | See a shoe on the foot |
| Shoes | Get a size recommendation | Recommend a shoe size |
| Bags or backpacks | See the bag on their body | See a bag on the body |
| Clothing | See the garment on a person | See a garment |
| Clothing | Get a size recommendation | Recommend a clothing size |
Seeing a product and recommending a size are separate setups. A shoe store can launch try-on without size, or size without try-on. One does not turn the other on.
Then pick where the store runs
| Store | Shoe try-on | Shoe size | Bags | Clothing look |
|---|---|---|---|---|
| Shopify | Shopify checklist. No separate WEARFITS account. | Not part of the Shopify app. | Not part of the Shopify app. A 3D file is required. | Only when Apparel access is already on the store. It does not create shoe 3D models. |
| WooCommerce | WooCommerce checklist. Needs a Dashboard API key. | Not part of the shoes plugin. | Not part of the shoes plugin. | Clothing plugin, earlier stage than shoes. |
| Your own website | Own-website checklist. | Size recipe. WEARFITS registers the store before go-live. | Bag recipe. | Clothing recipe. |
Paths at a glance is the same split, written as four setup sequences.
Words that collide
"Size fitting" is three different things. Use the glossary before following a link that only says "size".
- A shoe size is a foot scan plus an advisory recommendation. It is not the clothing API.
- A clothing size compares a body chart with a digital twin. It is not a shoe size.
- An on-shoe fit heatmap is not a setup you can follow in this wiki. Ask your WEARFITS contact if you were shown that experience.
What to read next
- Make the assets — shoe photos, or a 3D file you already have
- Account, keys, and plans — who needs a Dashboard login, and which price list applies
- For developers — hosts, API keys, and the reference pages