Every restaurant has the same Sunday-night ritual: someone in the walk-in with a clipboard or a phone, counting cases of chicken thighs and tubs of aioli, typing numbers into a Google Sheet while the line cooks break down the kitchen. That sheet is where food cost percentage — the number the whole business lives or dies on — actually gets computed.
It's also where the pain lives. The produce supplier delivers Tuesdays and Fridays, the meat guy wants orders in by Wednesday noon, and the dry-goods rep works off a completely different calendar. Par levels exist mostly in the chef's head, so a busy brunch quietly drains the brisket and nobody notices until a server has to 86 the special mid-service. Meanwhile spoilage — the half-case of greens that turned — vanishes into the food cost number with no trace of where it went.
Restaurant inventory platforms pitch themselves as the fix, at roughly $325 a month plus the chore of retraining every closing manager. There's a cheaper route: keep the count sheet, and let AI build a free dashboard on top of it — the same play as our core inventory dashboard walkthrough, adapted for a kitchen.
Whatever your closing manager already fills in works as-is. A typical kitchen sheet carries one row per item:
| Column | Example |
|---|---|
| Item | Chicken thighs |
| Unit | Case (40 lb) |
| Par level | 3 |
| On hand | 1.5 |
| Supplier | Riverbend Meats |
| Order day | Wednesday |
| Cost/unit | $118 |
| Last count | Jul 20 |
Prep items, bar stock, and paper goods can sit on separate tabs — the AI reads all of them.
Sign up at lovespreadsheets.com; the free plan is all a single restaurant needs to build this and run it daily. Paid kicks in only for extras like manager logins or putting the tool on your restaurant's own web address.
Choose the Dashboard template. If you use an ordering or vendor platform that issues API keys, you can wire it in for live pricing and delivery data — optional, since the count sheet alone is enough to start. Then lay out the kitchen's reality:
"We're a 60-seat restaurant counting inventory Sunday and Wednesday nights. Each item has a par level, a supplier, and that supplier's order day. Build a dashboard showing everything under par, an order list grouped by supplier and due date, and our total inventory value against last month."
Then the request that changes service:
"Add a chatbot the kitchen can ask things like 'what do we order from the produce guy tomorrow?' or 'which items are under par right now?'"
Three add-ons worth naming in the same breath:
Answer the AI's clarifying question or two, and the build wraps in about 15–20 minutes.
You get a link the whole kitchen can open: everything under par in one column, tomorrow's order list already grouped by supplier, and inventory value tracked over time. Wednesday's meat order stops being an archaeology project through old texts — it's a list the dashboard wrote from the sheet, and the chatbot fields the "are we good on short rib for the weekend?" questions the chef used to answer from memory.
Counts stay fast. Nobody wants new software in the walk-in at 11 p.m. The clipboard-to-sheet routine your closers already know keeps working; the dashboard reads it the second it's saved.
Par levels come out of the chef's head. Written thresholds mean the Tuesday sous can order correctly when the chef takes an actual day off.
Food cost gets a witness. Snapshot history shows the drift between what was counted, what was ordered, and what should be left — which is where waste and over-portioning finally show up by name.
Can it handle two count frequencies? Yes — daily counts for proteins and weekly for dry goods is just something you say in the description.
We order from six suppliers. Does that break it? The opposite: supplier and order day are columns, so the dashboard sorts every order list by who and when automatically.
Can the bar have its own view? Ask for one — bar stock on its own tab becomes its own page, with its own pars and alerts.
Bring the count sheet from last Sunday to lovespreadsheets.com, describe your pars and your suppliers' order days, and let it build. By the next count, "did anyone order the chicken?" is a question the dashboard already answered.
The team turning other people's spreadsheets into software they actually trust — one sheet at a time.