Size Memory: Remembering a Shopper's Fit So They Stop Starting Over
Apparel has a question most categories never ask: which one fits this body. A shopper who bought a medium that ran small, returned a large that swam, and finally kept a medium in a different cut has taught your store something valuable, at the cost of two returns. Size memory is whether your store bothered to learn it.
What to remember, exactly
Remember the kept size per category, the fit outcome, and any explicit preference the shopper states, such as prefers a relaxed fit or between sizes, sizes up. Kept is the operative word. Purchased sizes include every return that taught the opposite lesson, and a memory built on purchases instead of kept outcomes will confidently recommend the size the shopper already sent back.
Start narrow. Shoes and one core apparel category will prove the pattern. A size memory that covers two categories accurately beats one that covers ten categories from order data nobody cleaned, because fit trust is lost in one bad recommendation and earned over several quiet successes.
Where the memory should show up
On the product page, preselect or highlight the remembered size and say why, in one short line: your usual size in knitwear, medium. On category pages, offer a filter for in stock in my size, which is the single most useful filter in apparel and the one most stores bury. In email, suppress out of stock in their size from the hero spot. Nothing in that list requires a prediction model. It requires the stored fact and the discipline to use it.
Do not use it to shrink the shopper's world. Show the remembered size first, not the remembered size only. People buy gifts, bodies change, and a store that makes it hard to pick a different size feels like a trap wearing a helpful badge.
Returns data is the training set you already paid for
Every return with a fit reason is a labelled example: too small, too large, too long. Stores process these by the thousand and then store almost none of the signal where a product page can use it. Pipe the fit outcome back to the customer record and to the product record, because a product that runs small for everyone should say so to first time buyers too.
That second use, product level fit truth, may be worth more than the personal memory. A note that says this style runs small, most buyers size up, built from actual return reasons, cuts returns for shoppers you have never seen before. Personalization that only helps known customers is half the job.
The line between helpful and watched
Fit data is body data, and some shoppers will not want it kept. Offer the memory as a visible, editable profile setting, not an invisible inference. Let a shopper see their stored sizes, change them, and delete them in one place. Stores that hide the memory get one screenshot on social media and a trust problem. Stores that show it get corrected data and a feature shoppers describe as service.
Test it the way you would test a price change: one category, a holdout group, and returns rate as the headline metric, not clicks. If size memory is working, returns fall. Everything else is commentary.
Keep reading
Related guides on this site: Gift Mode: A Toggle That Keeps Profiles Clean and Surprises Safe Why This Pick: Recommendation Explanations That Build Trust Practical answers about personalization.
Frequently asked questions
What size data should a store store?
The size the shopper kept, per category, plus any fit preference they state themselves, such as sizing up in slim cuts. Kept sizes matter because purchased sizes include returns, which teach exactly the wrong lesson.
How should size memory appear on a product page?
Highlight the remembered size with a short reason, such as your usual size in this category, and offer an in my size stock filter on category pages. Show it first, never exclusively, so gift buying and size changes stay easy.
Can size memory reduce returns?
Yes, when it is built from fit outcomes rather than purchases. Recommending the size similar shoppers kept, and flagging styles that run small from real return reasons, attacks the largest single cause of apparel returns.
Is storing body related data a privacy problem?
It can be if it is hidden. Store it as a visible, editable profile setting that the shopper can review, change, or delete. Transparency turns the same data from surveillance into a service the shopper controls.