Why do I keep buying spices I already own?

Because a spice jar gives you almost no information at a glance. It is opaque or close to it, it looks identical to every other jar of the same brand and size, and it usually stands in a row with a dozen others that look just the same from the front. You do not remember owning cumin the way you remember owning a blender — you remember that you cook with cumin, which is a different fact, and the only way to turn that into "yes, and it's within reach" is to actually find the jar. When finding it costs more effort than a couple of dollars at the shop, buying wins, almost every time.

A spice rack hides quantity as well as location

Most things you might duplicate at least tell you something when you look at them — a shampoo bottle you can heft to feel how much is left, a bag of rice you can see through. A spice jar mostly just sits there looking the same whether it holds two teaspoons or two months' worth, and it rarely sits alone. Spice storage packs a lot into a small space, so the jar from three years ago and the one from three weeks ago end up shoulder to shoulder, sorted by nothing more organised than the order they arrived in. The jar you actually want quietly migrates to the back row, and a back row you cannot read without physically moving six other jars is, for practical purposes, gone.

The three ways it actually happens

You go looking, don't find it, and assume you're out. A recipe calls for cumin, you check the rack, and it isn't in the first three jars you can actually read. The honest move would be to take everything out and look properly; the fast move is to add it to the list and move on. Nine times out of ten that isn't wrong — but the tenth time it was two rows back the whole time, and you now own two.

The new name for a spice you already have. A recipe wants smoked paprika and you own sweet paprika, or it wants Aleppo pepper and you own chilli flakes. Either would likely have done the job well enough, but the recipe used a specific word and you went looking for that exact word, not for "something in this family." A slow pile of near-duplicate spices builds this way — not from buying the same jar twice, but from buying the adjacent one each time.

It arrived, it wasn't chosen. A spice blend from a trip, a starter jar tucked into a gift hamper, a duplicate from when two people in the house both did a "big shop" the same week. None of these were a decision to restock, so none of them got weighed against what was already in the rack — and a jar with an unfamiliar label often reads as new information rather than as the plain paprika sitting three jars over.

Why spices going stale hides the problem for years

With most duplicates, using the newer one eventually forces a reckoning — you finish the second umbrella and only then rediscover the first. Spices rarely give you that moment. Ground spices lose most of their strength well before they look or smell obviously off, so the older jar just gets weaker and weaker while sitting untouched, and the newer, more pungent one keeps getting reached for instead because it actually tastes like something. The old jar never gets "used up" in a way that forces you to notice it existed. It just quietly loses its case for ever being picked again.

What actually helps, without alphabetising the whole rack

You don't need a labelled, decanted, uniform-jar system for forty spices — most people who set one up abandon it within a season, and the rack goes back to whatever order things landed in. What actually matters is much narrower: knowing, in the two minutes before you buy a spice, whether you already own something that does the same job, including under a different name. A short note of what's in the rack, even a rough one, beats trying to remember it standing in an aisle, because the failure here was never memory of cooking with cumin — it was memory of exactly which jar, and where.

Where a short note beats a tidier rack

This is a case where being shown the truth works better than reorganising harder, because the problem was never that you don't know you cook with paprika — it's that "I own paprika" and "I can put my hand on it right now" are two different facts, and only the second one stops a purchase. Kept is built to make that kind of list painless to start: say out loud what's in the rack, or photograph it in one go, and recognition drafts the entries for you to confirm rather than typing jar by jar. Then the next time a recipe sends you toward the spice aisle, the check-before-you-shop search answers the question that actually matters — not whether you have ever owned paprika, but whether the jar about to go in the cart is the third one.