How to Organise Kitchen Storage Locations (Lessons From 350 Items)

Here is a question that sounds simple and is not: where do you keep your cumin?

"The spice cupboard" is fine until somebody else is cooking in your kitchen. Then it becomes: which cupboard, which shelf, front or back. We catalogued a real kitchen — 350 items — specifically to find out what a location system needs to survive contact with an actual house.

Flat lists stop working at about thirty items

The first version let you name any location you liked. That gives you a list like this:

• Shelf
• Back side
• Bottom cabinet left of stove
• Bottom cabinet right of the stove
• Bottom tall cabinet
• Left of the microwave
• Cabinet far right of microwave

Seven entries, five of which start with a word you have to read past. Finding anything means scanning the whole list. At 25 locations it is genuinely slow, and the names get longer as you add more, because each new one has to distinguish itself from all the others.

The names are not the problem. The structure is missing.

Two levels is the right number

What works is a main location and a sub-location inside it:

• Cabinets — 167 items across 14 sub-locations
• Pantry — 81 items across 5
• Counter — 60 items
• Fridge — 26 items
• Freezer — 16 items

Five things, matching the five places that exist in the room. Open Cabinets and you get its shelves. "Bottom cabinet right of the stove" becomes "Cabinets / Bottom cabinet right of the stove", and you never have to read that full string to find it — you tap Cabinets first.

Three levels is tempting and not worth it. Nobody wants to navigate Kitchen → Cabinets → Lower → Right → Back. Two levels covers a domestic kitchen and stays quick.

Not every main location needs children

Counter, Fridge and Freezer have no sub-locations in our kitchen and it would be silly to invent some. A system that insists on two levels everywhere produces "Fridge / Fridge", which helps nobody.

So sub-locations are optional. Main locations that have none just open straight to their contents.

Sort by what is in them, not alphabetically

Alphabetical ordering put "Back side" — twelve items — at the top, and buried Cabinets with 167. Ordering by contents puts the fullest first, which is where the thing you are looking for probably is.

Alphabetical order carries no information when half your entries start with the same word.

Search beats browsing, so lead with it

Most of the time you are not touring your kitchen. You want one thing.

Typing "flour" and getting five results, each with its full location, answers the question faster than any amount of navigating:

• Atta (Whole Wheat Flour) — Pantry / Back side
• All-Purpose Flour — Pantry / Shelf
• Jowar Aatta — Pantry / Shelf

So the search box goes first, and browsing is the fallback rather than the main event.

The empty-location trap

One more thing worth knowing if you are building this. We built the location list from the items in it — which meant a cupboard with nothing in it did not appear at all.

Add a new shelf, and nothing happens. It looks broken. It was not broken; the shelf existed and was invisible, which is worse than a visible failure, because your next move is to add it again.

Build the tree from the locations and fill it with items, not the other way round. When we fixed that, seven empty shelves appeared that had been there all along.

The short version

A location system for a kitchen needs: two levels, optional at the second, sorted by how full they are, with search in front and empty places still visible.

That is a small set of rules, and every one of them came from the flat version being annoying in a specific way.