Guide
Selling clothes online means asking someone to buy something they cannot try on. Most of the work, then, is not decoration: it is removing doubt — about fit, about fabric, about what happens if it does not work out. These are the practices I apply when I redesign the most strategic touchpoints of a fashion store: homepage, product list and product page.
Sizing uncertainty is the main reason clothing goes back. Answering it on the page is cheaper than processing a return.
Images do the work a fitting room would do. Their quality sets the ceiling for everything else on the page.
Delivery costs, return terms and honest stock states decide whether a basket becomes an order.
Ten practices
A clothing homepage earns the next click. Lead with the current reason to shop — a season, a drop, a single strong edit — and one clear path into the range. Rotating banners that show three unrelated messages tell a first-time visitor nothing about what the store is for.
Shoppers scan product list pages in rows, not one card at a time. Keep each card to what actually decides a click: image, name, price, available colours and sizes. Move promotions into one consistent slot so they never compete with the product itself.
Colour, fit, length, fabric, occasion — not the names used inside the merchandising system. Filters should be combinable, show how many results they leave, and never land on an empty page without an obvious way back.
The real job of a product page for clothing is reducing uncertainty about fit. Model height and size worn, garment measurements, a “fits true to size” note and a size chart in the customer's units all belong near the size selector, not behind a link in the description.
Several angles, a flat lay, a close-up of the fabric and the garment moving on a real body. Zoom has to be honest about texture and transparency. A single studio shot plus a colour swatch is the shortest route to a return.
Sizes that are gone should stay visible with a restock alert rather than vanish while the customer scrolls. If part of a size run has sold out, the page should say so before someone starts choosing.
Guest checkout first, address autofill, errors shown where they happen, and progress that is visible at every step. Every extra field or forced account is an invitation to leave with the basket already full.
Costs, timing and the return window belong on the product page and in the basket, not only in a policy page in the footer. For clothing, a clear and generous return path is a conversion argument, so it should be readable before checkout.
Size terms, filter logic and component behaviour should behave the same in every market and across web, app and store. A shared design system is what keeps that promise true while the catalogue and the team keep growing.
Short usability sessions and session recordings show where people hesitate; A/B tests settle what is left. Change one variable at a time, keep the losing variants in the record, and write the reasoning down so the next designer does not reopen it.
Where this comes from
Homepage, product list and product page in the retail and digital experience for the leading legwear brand. Every practice above came out of those three screens: what a customer needs in order to choose a pair of tights online without being able to touch them.
Redesign of the product discovery and checkout flow for a mountain brand, unifying the experience across markets with a scalable component library — the same consistency problem any store faces once it grows past one country.
A place to start
Working on a clothing store and want a second pair of eyes on the journey? Tell me where customers drop off.