In this guide 6 sections
Footwear returns pile up when the size on the box fails the foot. The usual causes are missing half sizes, a single width, styles built on different lasts and return reasons too vague to trace. Tag returns by style and size. The pattern then shows itself.
Half sizes leave shoppers guessing between two boxes
A shopper who measures between a 7 and a 7.5 has no good answer, so they pick one or order both and send one back. Either path ends in a return.
Count the styles with no half sizes. Then check how sizes convert across UK, EU and US charts, because one conversion table rarely matches the way each brand cuts its shoes. Print foot length beside each size.
Bracketing is the clearest sign. When many orders carry two sizes of one style and only one pair stays, the size chart is failing the shopper.
Width is the option many shops hide
Narrow, standard and wide fits, or the letter widths used in some markets, change how a shoe sits across the ball of the foot. A wide-footed customer who finds only a standard width sends the pair back as too small, and the return gets logged as a sizing error. Length was never the problem.
Return comments show the pattern. Phrases like tight across the ball, cramped toe box, pinching instep or slipping heel point to width and volume, not length. Sort the comments into groups first. Then consider a wider fit.
Width also hides in sandals and boots. A strap that cannot loosen, or a boot shaft that will not zip over a full calf, ends in the same return.
- Tight across the ball of the foot
- Toe box cramped or toes touching the end
- Instep pinches under the laces
- Heel slips when walking
- Calf too snug on boots
- Arch discomfort after a day at home
Two styles in one size can fit differently
A last is the mould a shoe is built around. Each style can use its own last, so a loafer and a trainer marked with the same size can feel half a size apart. Factories also revise lasts between seasons.
Materials add to it. Full-grain leather gives with wear, while mesh and synthetic uppers do not, and lining thickness, insole depth and a stiff heel counter all change how a size feels. Try each style on staff feet.
Give every style a fit note: runs small, true to size or runs large, based on return data and staff try-ons, never copied from a supplier’s catalogue. Guesses do not count.
Read return reasons at style and size level
A pick-list entry reading wrong size hides the answer. Replace it with codes that name the problem: too short, too narrow, loose at the heel, instep too tight, arch discomfort and not as pictured. Make the field mandatory.
Store the code on the return line with the style, the size and width ordered and the size sent as an exchange. Then group by style. One dominant code names the fix, and a style split evenly across codes points to something other than fit, such as a quality fault.
A monthly count of returns per style and code is enough, and it needs no analytics tool beyond an export from the order system and a pivot table.
- Style code and last name
- Size and width ordered
- Return reason code from the pick-list
- Size and width exchanged to
- Days between delivery and return request
- Inspector’s note on the returned pair
Turn the codes into changes on the product page
Act on the loudest style first. Add a fit note beside the size selector, such as order half a size up, and add a width selector where you stock widths. Ask one question at checkout, such as the length of the longer foot in centimetres, and show the size that matches it on that style’s own chart.
The supplier needs the same data. If a style comes back as too narrow every season, ask the supplier for a revised last on the next production run, and warn buyers until then.
Start this week. Export last season’s returns and sort them by style, then take the five styles with the most too-short or too-narrow codes and write a fit note for each.
Footwear fit log
A one-page log, one row per returned pair. Columns hold the style code, last name, size and width ordered, reason code from the pick-list, size exchanged to, inspector’s note and the decision on the fit note. A second block at the foot lists each style with its running fit note and the date its product page was updated.
Open a blank worksheet to printQuestions owners ask
What is a last, and why does it matter for fit?
A last is the mould under every shoe. Its length, toe shape and volume define the fit, so two styles on different lasts feel different even when the printed size matches.
Does a size chart reduce footwear returns?
It helps when it lists foot length for each last, not one chart for the whole brand, and a generic chart only repeats the guesswork. Then watch whether bracketed orders fall.
Should every return carry a reason code?
Yes. A mandatory pick-list at the point of return costs little and fills the data you need, whereas free-text comments alone are too messy to count.
How can I tell a fit problem from a quality problem?
Quality returns cite stitching, sole separation or colour. Fit returns cite pressure, slipping or length. Never mix the two groups in one report.