Cost per wear usually shows up as a permission slip. “It’s $400, but it’s basically $4 a wear.” Said at checkout, before the first wear, by someone who really wants the coat.
The math is fine. The way it gets used is the problem. Here’s how to use it as a decision tool, one that sometimes tells you no.
The formula
Price divided by the number of times you’ll actually wear it. That’s it.
One upgrade: add what it costs to keep the piece going. Dry cleaning, tailoring, a cobbler visit. If a blazer needs cleaning after every few wears, that belongs in the price.
The formula is only as good as the number you put in. Everything below is about getting that number right.
Be honest about the wears
The wear count is where most people cheat. They count the wears from the fantasy week, the one with the dinner, the trip, and the gallery opening. Your real week has a commute, a desk, and a laundry day.
Run the piece through a few questions before you pick a number:
- Can you name three outfits you’d build with things you already own?
- Does it suit the week you actually have, not the one you post about?
- Is it still comfortable at hour six?
- Will you still want it once the trend has moved on?
- Will it survive your bag strap, your washer, and your weather?
If you stalled on the first question, your number is lower than you think. When you’re torn between two counts, use the smaller one.
Ask what it replaces
A piece that replaces something you’d buy anyway is a different decision from a piece that replaces nothing.
If you’re going to need a winter coat regardless, compare the two coats against each other. If the piece is a pure add, a fourth black boot or a fifth going-out top, it has to earn its wears from scratch, because it will split them with everything it’s sitting next to.
Duplicates are where cost per wear quietly falls apart. Two near-identical pieces don’t each get 40 wears. They share 40.
A worked example
Example only. These are made-up round numbers to show the math, not real prices or real products.
Coat A: $400. You’d honestly wear it about 50 times over its life. $400 ÷ 50 = $8 per wear.
Coat B: $120. You like it, but the fabric will pill and you’ll stop reaching for it after about 12 wears. $120 ÷ 12 = $10 per wear.
The pricier coat wins, but only by a little. The gap comes from the wear counts, not the price tags. If Coat A would only get 25 wears, it lands at $16 and loses.
Add the “replaces” question. If Coat B means buying another coat in a year or two, the real comparison gets even less friendly to the cheaper one. If you’d keep wearing Coat B for years, it gets friendlier.
When the pricier piece loses
Same disclaimer: still invented numbers.
Sandal A: $300, sculptural, very fit-check. You’d wear them maybe 10 times, because you can’t walk far in them. $300 ÷ 10 = $30 per wear.
Sandal B: $90, simple, comfortable, goes with nearly everything. About 45 wears. $90 ÷ 45 = $2 per wear.
That’s not close. The expensive pair isn’t a bad purchase because it’s expensive. It’s a bad purchase because the wear count is small. Sometimes the right call is to love Sandal A on someone else and buy B.
The same thing happens with very trend-specific pieces, anything that needs a particular outfit to work, and anything that’s uncomfortable. Price isn’t the variable that matters. Wears are.
Where cost per wear stops helping
It can’t tell you if you can afford the piece today. A low per-wear number doesn’t change the total on your card. It also can’t tell you whether you love something, and a piece you love but wear 8 times can still be a good buy if you know that going in.
So “worth it” shouldn’t be a justification you build after wanting something. Run the numbers first, with the honest count. If the piece still holds up, great. If it doesn’t, you saved yourself a lowkey regret.
A habit that helps: put the piece on a list, write down your three outfits, and come back in a week. If you can still name the outfits and you still want it, the count is probably real.
That’s the edit. Fewer pieces, each with a reason.