Choosing a Theme for a Clothing Store
Fashion is the hardest WooCommerce category because one product is thirty variants with different stock, different photographs and a return rate nothing else comes close to. The theme either handles that or quietly makes it your problem.
Clothing is the hardest WooCommerce category, and it is hard for one reason: a single product is thirty sellable things. Five colours by six sizes, each with its own stock level, sometimes its own price, and photographs that must change when the shopper picks a colour. A theme that handles this well is worth more than any amount of visual polish, and most theme demos are built with three products that have no variations at all.
Test candidates with a real garment, not with the demo.
What the product page has to do
Load a variable product into a candidate theme and check the behaviour, not the screenshot:
- Swatches, not dropdowns. Two select boxes labelled Colour and Size are the WooCommerce default and they are poor for fashion. Colour swatches and size buttons show availability at a glance.
- Out-of-stock variants stay visible. Struck through, not removed. A shopper needs to see that the dress exists in their size but has sold out, or they conclude you do not stock it.
- The gallery follows the selection. Choosing "olive" must swap the gallery to the olive photographs, not just the single featured image.
- Price updates without a reload, including sale prices on individual variants.
- Fit information near the buy button — model height and the size they are wearing does more work than a paragraph of copy.
The mechanics of setting these up correctly are in adding product variations in WooCommerce. If a theme is fighting you on any of the five points above, that is the theme telling you it was built for a shop selling candles.
Filtering is a shop-page requirement, not a nicety
Browsing behaviour in fashion is filter-first. Someone lands on a category with two hundred items and immediately narrows by size and colour. Two things follow.
The filter must query variation-level stock, not product-level. Filtering to "size 12" and returning items where only sizes 6 to 10 remain in stock is worse than no filter, because it burns the shopper's trust on the first interaction.
And the filter must be a plugin. Theme-supplied filtering ties your entire browsing experience — and often the filter URLs that people bookmark and that get linked — to the theme. The category considerations are in WooCommerce product filtering.
| Feature | Where it belongs | What breaks if the theme owns it |
|---|---|---|
| Colour and size swatches | Plugin | Every swatch reverts to a dropdown |
| Attribute filtering | Plugin | Filter URLs 404; browsing collapses |
| Size guides | Plugin or product content | Guides vanish from products |
| Wishlists | Plugin | Saved lists become unreachable |
| Quick view, cart drawer | Theme is acceptable | Cosmetic; degrades gracefully |
| Shop and product layout | Theme | Expected; rebuild on switch |
The last two rows are the honest exception. A cart drawer disappearing is an inconvenience. Losing every customer's wishlist is a support incident.
Photography sets the load time and the ratio
Clothing shops are image-heavy by definition — typically four to eight photographs per colourway. Two decisions made at shoot time govern the site forever.
Pick one aspect ratio and hold it. Portrait, usually around 2:3 or 3:4. Mixed ratios produce a ragged grid, and letting WooCommerce hard-crop to fix it will decapitate half your models. The settings and their consequences are covered in WooCommerce product image sizes.
Resize before upload. A category page pulling forty full-resolution studio shots is the slowest page most fashion sites have, and it is the page where browsing happens.
If you are migrating a catalogue, bulk work is far easier through importing products with a CSV than through the product editor, and it forces you to get your attribute naming consistent first — which is what makes filtering work later.
Returns and shipping are structural, not a policy page
Fashion has a return rate no other category matches, and in the UK and EU distance selling rules give consumers a cancellation window on top of whatever you offer voluntarily. That has design consequences:
- Returns and delivery information belongs on the product page, not only in the footer. It is the last objection before checkout.
- Delivery cost and timescale should be visible before the cart, since unexpected postage is the dominant abandonment reason. Configure it properly first — see setting up WooCommerce shipping.
- A returns portal or at minimum a clear form; expecting customers to email you does not scale past your first busy month.
What to install
Start from the general ecommerce theme criteria and shortlist on variation handling alone. Then add swatches, filtering and size guides as plugins, deliberately, so that a redesign in two years changes how the shop looks rather than how it works.
Before launch, buy something from your own shop on a phone, in a size that is nearly sold out, and change your mind about the colour halfway through.
Frequently asked
- A plugin. Swatch settings attach to your attribute terms and product data, and a theme that stores them in its own options loses every swatch on the day you switch. A plugin keeps them attached to the products where they belong.
- Usually because the source photographs have different aspect ratios and WooCommerce is set to crop rather than fit, or because a theme change registered new image sizes that were never regenerated. Shoot to one ratio and regenerate after any theme change.
- On every product where fit varies, which in clothing is nearly all of them. Returns in fashion are driven overwhelmingly by fit, so a garment-specific measurement table is one of the few site changes with a direct effect on margin.