Uniforms are an odd kind of inventory, because most of what you own isn't on your shelf. It's on your staff. So a uniform inventory sheet counts each item in three places: new and in stock, issued to an employee, and returned in a state to be issued again. It also has to do it by size, because twenty chef coats are no use to a new cook if none of them is a medium. The reorder flag looks only at the new stock in each size. A second sheet records who holds what, which is where the issued numbers come from and how you get things back when someone leaves. Below is a sheet for a made-up restaurant, how to set the levels, and the file.
The short version
- One row for each item in each size.
- Three counts on each row: new in stock, issued, returned and usable.
- Reorder on the new stock for that size, not on the total you own.
- A second sheet: who was issued what, when, and when it came back.
- Write off what's worn out or never returned, with the reason.
- Order sizes from who you actually hire, not an even spread.
- TaroStack counts stock by size and location on a phone. More below.
An example sheet
| Item | Size | New, in stock | Issued | Returned, usable | Total owned | Reorder at | Status |
|---|---|---|---|---|---|---|---|
| Chef coat | S | 2 | 3 | 1 | 6 | 2 | REORDER |
| Chef coat | M | 1 | 6 | 0 | 7 | 3 | REORDER |
| Chef coat | L | 4 | 5 | 1 | 10 | 3 | OK |
| Chef coat | XL | 2 | 2 | 0 | 4 | 1 | OK |
| Bib apron | One size | 6 | 14 | 2 | 22 | 6 | REORDER |
| Server polo | M | 3 | 4 | 0 | 7 | 2 | OK |
| Server polo | L | 0 | 5 | 1 | 6 | 2 | REORDER |
| Cap | One size | 5 | 12 | 0 | 17 | 4 | OK |
This restaurant owns 79 pieces. Twenty-three are new on the shelf, worth $351.00 at cost. Four rows need reordering, and the totals hide it: there are 27 chef coats in the building and one new medium.
Why by size. The medium chef coat is the row to look at. Six are issued, which says medium is the size this kitchen hires most, and one is left. The reorder level of three reflects that. The XL level is one, because two people wear it.
Returned, usable is its own column because a returned coat isn't new and isn't gone. It can cover a replacement for someone who already has the item, and you'd rather give a new hire a new one. Keep it out of the reorder sum.
Setting the level for a size
| Chef coat, medium | |
|---|---|
| Coats given to a new cook | 2 |
| New cooks in this size you might hire before an order arrives | 1 |
| Spare for a ruined coat | 1 |
| Reorder at | 3 |
The numbers are this restaurant's own. The reasoning carries over: enough new stock in each size to outfit the next hire and replace one loss while you wait for the supplier. If embroidered items take a month to arrive, the level is higher than for a blank apron you can buy tomorrow. More in reorder point example.
Who holds what
| Employee | Item | Size | Issued | Returned | Condition |
|---|---|---|---|---|---|
| K. Souza | Chef coat | M | Oct 6 | ||
| K. Souza | Bib apron | One size | Oct 6 | ||
| M. Lee | Server polo | L | Sep 15 | Nov 10 | Usable |
Write the row on the day the item is handed over. When someone leaves, their rows are the list of what to ask for. What comes back goes to "Returned, usable" or is written off. What doesn't come back is written off too, with "not returned" as the reason, and after a year you'll know what that costs.
Whether an employer may charge for a uniform that isn't returned, or deduct it from pay, depends on wage law where you are. Ask before you write it into a policy.
Counting and write-offs
Count the shelf every quarter, by size. Check the issued numbers against the second sheet at the same time: the issued column should equal the open rows for that item and size. Write off stained, torn and missing items when you find them. A count sheet for any stock is in cycle count form, and a sheet for clothing you sell, with sizes and colors, in t-shirt inventory template.
Get the sheet
Download the uniform inventory sheet. Two sheets and a read-me: the inventory by item and size, with total owned, a REORDER flag on new stock and its value, and the log of who was issued what. It's an ordinary Excel file with no macros, and it works in Google Sheets, LibreOffice and Numbers.
Where this stops working
A staff of twenty in one building is a sheet and a shelf. Three locations, with coats moving between them and a laundry service holding a third of everything on any given day, is a count nobody can do in one place. The sheet says ten large coats. Four are at the other restaurant and three are in the laundry's bags.
How TaroStack does it
TaroStack keeps each size as its own item, in each place it's held.
Each size is an item, with its own stock, reorder point and supplier.
Stock is held by location: the uniform shelf, the laundry, each restaurant. Transfers between sites are on Business.
Counting works on a phone with no signal. A count shows what each difference is worth.
Every adjustment carries a reason: worn out, stained, not returned.
A reorder list in days of cover, with the supplier's lead time and minimum order.
| The job | Spreadsheet | In TaroStack |
|---|---|---|
| New mediums on the shelf | A cell someone updates | Stock for that item and place |
| What's at the laundry | Unknown | Stock at that location |
| What wasn't returned this year | Unknown | Adjustments by reason |
| When to reorder each size | Rows in red, if opened | The reorder list |
TaroStack doesn't record which employee holds which item: keep the issue log in the spreadsheet. Stock, counts, adjustments and reordering are on every plan, from $9.99 a month (50 items). The first 14 days are free, with no credit card. If you'd like a hand setting up, ask, and we'll do it with you.
