How footwear sizing works on a Shopify store
The data decisions that make or break a shoe catalog, explained before we get to features.
Pick one size system, then convert consistently
Many shoe stores grow up with mixed size labels: EU on the styles bought from one factory, US on another, UK on a third. Shoppers notice, and it erodes trust in every chart on the site. We start by choosing a base system for your variant data and writing the conversion table once, as structured data, so every product page and chart reads from the same source.
Men’s and women’s US sizes sit on different scales, and kids’ sizes have their own. Each gets its own chart, stored as a metaobject and linked to the right products with a metafield. If you sell in several regions, Shopify Markets lets you localize currency and content per market, and we show the size label shoppers in that market expect alongside the conversion, rather than relabeling variants per country.
Width is an option, not a footnote
If a style comes in widths, width needs to sit right next to size. Buyers with wide or narrow feet look for it first and leave quickly when they cannot find it. We set width up as its own product option with plain labels such as narrow, standard and wide, and show the letter code (for example D or 2E in US men’s sizing) where your customers know it.
Half sizes need care too. Variant order on Shopify follows the order of option values, so a careless import can put 10.5 after 11 or scatter half sizes across the picker. We fix the order in the data, not with theme tricks, so it holds in filters, quick add and the admin.
Fit notes belong to the style
A size chart describes your scale. It does not tell a shopper that a particular boot runs narrow in the toe box or that a sneaker suits a half size down. That knowledge usually sits with your customer service team. We give it a home: a fit metafield per style (runs small, true to size, roomy), a short advice line such as “between sizes, go up”, and notes on toe shape, instep and break-in.
Reviews add a second source. Apps like Judge.me can collect structured fit and comfort feedback, which the theme summarizes near the size picker. Over time this answers the question shoppers trust most: how did this shoe fit other people?
Keep variant data clean as the range grows
Footwear catalogs multiply quickly, and small data errors turn into inventory problems. Duplicate SKUs, missing barcodes, sizes created with slightly different labels and orphaned variants after a colorway is retired all cause stock mismatches with your warehouse or POS. Before launch we audit every variant, agree SKU and barcode conventions and document how new styles should be added.
- One naming convention for sizes and widths
- Unique SKU and barcode for every variant
- Inventory tracked per location for retail stock
- A checklist your team follows for every new style
Releases, restocks and the size curve
Footwear sells unevenly across sizes. The middle of the run goes first, the ends linger, and a restock that only refills popular sizes can leave product pages looking half empty. We design the product page so sold-out sizes stay visible and clearly marked, with a back-in-stock alert for that exact size and width. Those alert sign-ups are useful demand data when you plan the next production run.
For limited releases the priorities shift to fairness and stability. Products are prepared and scheduled ahead, early access can go to tagged customers, raffle apps can replace first-come ordering for the most wanted pairs, and per-customer limits stop one buyer clearing a size. The theme stays lean so the release page loads quickly when the email or social post goes out.
