A restaurant inventory and waste tracker

Ask a restaurant owner where their margin goes and most will say food cost. Ask them exactly which items, on which days, for which reasons, and the answer usually gets vague. Inventory is counted on a clipboard and typed into a spreadsheet when somebody has time. Waste goes in the trash without a word. By the time the monthly numbers arrive, it is too late to change anything.

A restaurant inventory and waste tracker fixes the gap. Counts happen on a phone in the order you walk your storage, waste is logged at the station with a reason, and the owner sees food cost and waste by item every week. This guide covers what to include, how to describe it in plain words so an AI platform can build it, and how to get a busy kitchen to use it.

What clipboards and spreadsheets cost a kitchen

• Counts that take too long. Clipboards in a random order mean walking the walk-in twice. Long counts get rushed, and rushed counts are wrong.
• Numbers that arrive too late. If counts are typed into a spreadsheet days later, the week's food cost is history before anyone sees it.
• Invisible waste. Most waste is never written down. Without a log, the difference between expected and actual usage is a mystery: was it waste, over-portioning, or theft?
• Ordering by gut. Without par levels and current counts in one place, orders depend on whoever is on that night and what they remember.
• One person holds it all. The kitchen manager's spreadsheet works until they leave, and the next person starts from scratch.

What the tracker should contain

Items

Each inventory item needs:

• Name, as your team actually calls it.
• Category: protein, produce, dairy, dry goods, beverage, paper and supplies.
• Storage area and shelf position, so counts follow the walk.
• Count unit, such as case, pound, each or quart, and the purchase unit if different, with the conversion.
• Unit cost, updated when invoices change.
• Supplier.
• Par level: how much you want on hand after delivery.
• Whether it is a daily count item.

Count sheets

A count sheet is a list of items in walking order for one storage area: walk-in, reach-ins, dry storage, bar, freezer. The counter opens it on a phone, enters each quantity, and moves to the next. Previous count shows beside each item, which catches typos such as 40 instead of 4. When the count is submitted, it records who counted and when.

Two schedules work well together:

1. Full count weekly or at period end, every item.
2. Daily count of a short list of high-cost or fast-moving items.

Purchases

Record deliveries by supplier with items, quantities and costs, or at least invoice totals by category. With purchases and counts, the tracker can calculate usage and food cost.

Waste log

The waste log is the part that changes behavior. Each entry has:

• Item, picked from the list.
• Quantity and unit.
• Reason: spoiled or expired, overproduction, prep mistake, dropped or contaminated, guest return.
• Station and shift.
• Who logged it.
• Optional photo.

Cost is calculated from the unit cost, so nobody does math at the station.

Screens

• Count: pick a storage area, count in order, submit.
• Log waste: three taps and a number. Item, reason, quantity.
• Order suggestions: current count against par, grouped by supplier.
• Manager dashboard: food cost for the week, waste cost by reason and by item, and items with the largest gap between expected and actual usage.

Roles

Notifications

• The kitchen manager is reminded if a scheduled count is not submitted by its deadline.
• A single waste entry above a set cost alerts the chef the same shift.
• Items below par after the daily count appear on the order list, and the person who orders is told.
• The owner gets a weekly summary: food cost, waste cost, top five waste items, and count completion.

Reports

• Food cost percentage by week, using beginning inventory, purchases, ending inventory and sales you enter.
• Waste cost by reason, by item, by station and by shift.
• Variance: the gap between what you should have used and what you did use, for your highest-cost items.
• Count completion and time taken per count.
• Price changes from suppliers, item by item.

Expected versus actual usage, in plain words

Actual usage is simple: what you had at the last count, plus what was delivered, minus what you have now. Expected usage is what you should have used based on what you sold. If you sold 200 burgers at 6 ounces each, you should have used about 75 pounds of ground beef. If actual usage was 90 pounds, 15 pounds went somewhere.

The waste log explains part of that gap. If cooks logged 6 pounds of waste, the other 9 pounds point to over-portioning, recording errors or loss. You do not need to calculate expected usage for every item. Pick your five most expensive items, enter their portion size per menu item, and enter how many of each you sold. That is where most of the money hides.

More than one location

If you run several locations, give each its own storage areas and counts, but share one item list and one set of waste reasons. That lets the owner compare food cost and waste across locations on the same terms, and spot the location that needs help.

Example request

Example request: "Build an inventory and waste tracker for our restaurant. We have a walk-in, two reach-ins, a freezer, dry storage and a bar. Each item has a name, category (protein, produce, dairy, dry goods, beverage, supplies), storage area, shelf order, count unit, purchase unit with conversion, unit cost, supplier, par level, and whether it is a daily count item. Count sheets show items for one storage area in shelf order with the previous count beside each, and record who counted and when. We do a full count every Sunday night and a daily count of proteins and seafood before service. Deliveries are logged by supplier with items, quantities and costs. The waste log takes item, quantity, unit, reason (spoiled or expired, overproduction, prep mistake, dropped, guest return), station, shift, who logged it and an optional photo, and calculates cost. Show order suggestions comparing current count to par, grouped by supplier. Alert the chef when one waste entry is over 40 dollars. Remind the kitchen manager if the Sunday count is not submitted by 11 pm. Every Monday, send the owner food cost for the week using sales we enter, waste cost by reason, the top five waste items and count completion. Cooks can log waste and count but cannot change items or costs. Roles are owner, chef, sous chef and cook. Only invited staff can sign in."

How to roll it out

1. Build the item list in walking order. Walk each storage area with your chef and list items in the order they sit on the shelves. This one step cuts count time more than anything else.
2. Enter costs and pars. Pull unit costs from recent invoices. Set pars from what you actually use in a normal week plus a buffer.
3. Start with the daily count. Count proteins and seafood daily for two weeks. It is short, high value, and builds the habit.
4. Add the waste log at one station. Put a phone or tablet at the prep station and ask the team to log everything for two weeks. Tell them you are looking for patterns, not people.
5. Run the first full weekly count. Compare the time it took to the clipboard count.
6. Share the first waste report with the team. Show the top waste items and talk through causes together. When cooks see their entries lead to better prep lists, they keep logging.
7. Move ordering onto the suggestions. Once pars are tuned, order from the suggestion list and adjust pars monthly.

Mistakes to avoid

• Counting in alphabetical order. Count sheets must follow the shelves, or counts take twice as long.
• Too many waste reasons. Twenty reasons means nobody picks the right one. Keep it to five to seven.
• Punishing honest waste logs. If logging waste gets someone yelled at, logging stops. Address patterns in team meetings.
• Stale costs. Food cost is only as good as unit costs. Update them when invoices change.
• No count owner. Every count needs a named person and a deadline.
• Tracking everything daily. Daily counts are for the expensive items. Count the rest weekly.

How to measure that it works

Write down your numbers for the four weeks before launch, then compare:

• Weekly food cost percentage.
• Waste cost per week and its top reasons.
• Time to complete the full count.
• Number of emergency orders or 86'd items.
• Variance on your five highest-cost items.

A first sign of success is often that recorded waste goes up, because waste that was invisible is now logged. Then, as the team acts on the patterns, waste cost comes down.

Launch checklist

1. Items are listed by storage area in shelf order.
2. Units, conversions, costs and suppliers are entered.
3. Pars are set from real usage.
4. Daily count items are marked.
5. Waste reasons are five to seven and agreed with the chef.
6. The waste log is on a device at the station.
7. Count reminders and the high-cost waste alert are on.
8. The owner's weekly summary is scheduled.

How FORGE handles it

On FORGE, your chef or general manager describes the tracker in plain words, like the example above, and FORGE builds it. A panel of top AI models plans the tool, a dedicated AI crew builds it, and every piece is checked for quality and security before it is saved, with the tool checked at every step. Most teams have their first real tool the same day, on phones and tablets in the kitchen and a computer in the office.

Your costs, suppliers and counts stay inside your company. People join only by invite, and each role sees what it should, so cooks log waste without seeing costs they do not need. There is a complete record of who did what. Cooks and staff who only use the tracker are free; builders are $49 a seat a month with 3 builds included, and changes cost a small fraction of a build. We onboard every team ourselves, starting with a workflow workshop. Talk to us or see pricing.

Questions people ask