Your First Item List: A Starter Guide for a Back Room and a Spreadsheet

You do not have a tracking problem yet. You have a list problem.#

The operations that get organized successfully almost never start by choosing software. They start by writing down what they own, in a form somebody else could read. That list is the asset. Everything after it — labels, counts, reorder points, an app — is a way of maintaining the list.

The failure mode is not laziness. It is ambition. Someone opens a spreadsheet, decides this is the moment to do it properly, builds twenty-two columns including one for depreciation, fills in four rows, and never opens the file again. Three months later the back room is the same and the spreadsheet is a monument.

This guide is the opposite approach. Six columns, one afternoon, and a list that survives contact with a second person.

Step one: decide what counts as an item#

Before you write anything, settle one question, because getting it wrong doubles your work: is a thing you own an item, or is it a variation of an item?

The rule that holds up in a small operation: something is a separate item if you would ever need to know the count of it by itself. Blue nitrile gloves in medium and blue nitrile gloves in large are two items, because you run out of mediums first and that is the whole point. Two identical folding tables are one item with a quantity of two.

Applied honestly, this cuts the list badly — in the right direction. Many back rooms turn out to hold a few hundred genuine items at most, while the owner guesses "about a thousand" because they are counting units, not items.

The second decision is where to stop. Do not catalog everything. Start with the things that cause a bad day when they run out or go missing: the consumables you actually reorder, and the equipment expensive enough that you would notice it gone. The decorative wreath in the storage closet can wait for the list to earn its keep.

Step two: six columns, and why the seventh is a trap#

Here is the whole starter sheet:

That is it. A category column is a reasonable seventh if you have more than about a hundred items and want to filter them.

What is deliberately absent is a value or cost column, and this is worth defending. The moment you add cost, the list stops being a list and becomes an accounting exercise: someone has to source a number for every row, half the numbers are stale, and the sheet tends to stall at row forty. Cost is genuinely useful later, once the list is complete and being maintained. It is a burden on day one, and a common reason a first attempt dies.

There is a second reason to leave money out of a first sheet, and it is not a spreadsheet problem — it bites when you migrate. "Cost" and "price" are two different numbers: what you pay your supplier, and what you charge. Any system you eventually move to will have a field for each, and a single ambiguous money column labeled something like "unit cost" is exactly the sort of thing that lands in the wrong one. If you do add money to your sheet later, label the two columns unambiguously — Cost for what you pay, Price for what you charge — and never ship one column doing both jobs.

On the code column

You need a code because names drift. "Blue gloves M" becomes "Gloves - blue (med)" the second time someone types it, and now you have two rows for one thing.

Keep it short, keep it typeable, and use letters, or letters plus a number: GLV-BLU-M, TBL-6FT, URN-40C. Avoid slashes, avoid spaces, avoid making it clever. If you already have supplier part numbers on the boxes, use those — you get free cross-referencing with your own invoices, which is a real gift when reordering.

Leave gaps in any numbering you invent. A-01, A-02, A-05 costs you nothing today and saves a full renaming exercise the first time something new belongs between them.

Step three: name the locations for the person who does not know#

Location naming is where small operations create their own future misery, and the mistake is always the same: naming for what is true now rather than what a stranger can find.

"Behind the fridge" and "Mike's shelf" both work perfectly until Mike leaves. So do "Storage 1" and "Storage 2", right up until someone has to guess which one is which.

The rule is: a location name should let a person who has never been in the building walk to it. "Kitchen - upper cabinets", "Back hall closet - top shelf", "Garage - shelf B". Broad to narrow, said out loud the way people already say it.

Two judgment calls come up every time:

How granular? Go one level less specific than feels right. If you can walk into a room and find the item in under thirty seconds, the room is the location. Shelf-level detail is worth it only for a closet so packed that finding something takes real searching. Over-specifying is expensive because every location you invent is a location somebody must maintain.

What about things that move? Put them where they are supposed to live, not where they are. A folding table that spends half the year in the fellowship hall is stored in the storage closet. The list records the home, not the current whereabouts — the alternative is a list that is wrong every Sunday afternoon.

Step four: count it properly, once#

Do not fill the quantity column from memory or from the last delivery note. Count it, physically, one location at a time, in one sitting per location.

Print the sheet with the quantity column blank and write the numbers by hand as you go. Typing on a phone while holding a clipboard and a box is how rows get skipped. If two of you are doing it, split by location and never by alphabet — two people in the same closet trip over each other and double-count.

Where the count comes out badly different from what you expected, write the number you actually counted. The first list's job is to be true, not to be flattering.

Step five: the reorder point, and the number that means "off"#

For each consumable, the reorder point is the number where you would want somebody to tell you to buy more. It is not a target, not a minimum you must never breach — it is a trigger.

The arithmetic anyone will give you is: how many you use in a week, multiplied by how many weeks the supplier takes, plus a bit of cover. Gloves at two boxes a week with a two-week lead time and a week of buffer gives you six.

Here is the part that gets left out, and it matters more than the formula.

That calculation produces a fraction for slow movers, and the instinct is to round down. An item you use twice a year, from a supplier who delivers in a week, calculates out to something like 0.04. Round it and you write 0.

Do not write zero. In InventoryQuick — and in most alerting systems — zero is not a very low threshold. It is the off switch. A row with a reorder point of zero can never be flagged, because the check skips every item whose reorder point is not above zero. You have not made that item maximally sensitive; you have made it invisible, in the one column that was supposed to protect it.

So for any item where the arithmetic gives you less than one, do one of two things: write 1, meaning "tell me when I am down to the last one", or leave the reorder point blank and accept that this item is not on the alerting system at all. Both are honest. Zero is a silent lie that looks like diligence, and it fails precisely on the slow, forgettable items that most need a reminder.

Not every item needs a reorder point at all. Equipment does not — you are not going to reorder a projector because you have one. Fill the column for consumables and leave it empty everywhere else.

Step six: decide who maintains it, before you need them to#

A list decays from the day it is finished. The only question is how fast.

Small operations do not usually fail at this because people are careless. They fail because nobody was ever named. Pick one person per area — the kitchen, the shop, the storage closet — and give them one recurring job: walk their area once a month and correct the quantities.

Two practices make that stick:

Correct at the moment of noticing. If someone opens the last box of anything, the list gets corrected then, not later. Later is a synonym for never.

Count a slice, not the whole thing. A full recount of everything is an event that gets postponed. One area per month rotating through is a habit. After a year, everything has been recounted several times and nobody ever lost a weekend.

One thing to be clear-eyed about while you are still on a spreadsheet: check whether your sheet records who changed a number, not only what it now says. If a quantity moving matters enough that you need it attributable to a named person, that has to live in your procedure — a note, a paper log, an initial in a comment. Do not assume a tool is quietly keeping receipts for you; check before you rely on it, rather than discovering the gap during the argument it was supposed to settle.

When to move off the spreadsheet#

Not yet. Not until the list exists, is accurate, and somebody is maintaining it. Software applied to a list nobody maintains produces an expensive list nobody maintains.

The genuine signals are: more than one person needs to edit it at the same time, or you want the reorder points to actually notify somebody rather than sit in a column waiting to be read.

If you do move, the six columns above transfer cleanly. In InventoryQuick, a CSV with headers SKU, Name, Quantity, Min Stock, Location and Supplier is recognized without renaming anything — those headers are read as the fields they look like, and there is a preview step that shows which column it read as what before the rows land, so you can correct it if it guessed wrong. The locations and suppliers named in those cells - and categories, if you add that seventh column - are created as the rows import; you do not have to set them up first.

The honest limit in the same breath: this importer brings in items, and only items. There is no separate location file, so a location that needs a parent location or a type has to be set up in the app afterwards — by hand or by asking the Assistant — importing gives you a flat set of location names, not a hierarchy.

The second thing worth knowing before you rely on it: a low-stock alert fires when an item's total on hand across every location drops to or below the reorder point on that item. Two consequences follow directly. Leaving the reorder point at zero switches alerts off for that item rather than making them sensitive — the same trap as the spreadsheet, enforced the same way. And because the check reads a company-wide total, it cannot tell you that one room's shelf is empty while another room is well stocked. If per-room shortages are what actually hurt you, that judgment stays with the person who walks the rooms.

The shortest version#

Six columns. Real items, not a thousand units. Locations named for a stranger. Counted, not remembered. Reorder points that are 1 or blank, never 0. One named person per area, one area a month.

Everything else is a decision you can make later, from a position of knowing what you own.

Download the free starter item list — the six columns above, landscape, with three worked example rows and the rest blank for the counting pass. A spreadsheet version, with an optional Category column filled in and a fourth example row, is at starter-item-list.csv. No signup.

Related: The reorder point formula and when to reorder · How to run a physical inventory count · A warehouse bin location system · Signs you have outgrown your spreadsheet · Switching from a spreadsheet to inventory software