Use AI to Check a Restaurant Inventory Variance, One Item at a Time

A variance on the count sheet is a question, not a finding. Before anyone decides what happened, put every number for that one item on the same basis and check each record that feeds it. Then sort the explanations: the ones you've proved go into the list of confirmed corrections, and everything else stays in an unresolved balance. That balance tells you where to look next, not who to blame.

An AI assistant is useful for the tedious parts: arithmetic, unit checks and a clear list of which record would confirm each possible explanation. It can't tell you what happened. That takes a recount, a receiving record or a scale.

This guide uses a fictional example and a prompt you can copy. The prompt is a proposed workflow. It hasn't been tested against any particular AI product, so treat anything it produces as a draft and check it yourself.

Start with one item and one basis

Pick the item with the largest dollar gap, not the whole inventory. Then decide which weight every figure will be in. In this example everything is in raw, as-purchased pounds: counts, deliveries and the recipe portion, which is weighed raw before cooking.

If your kitchen portions protein after cooking, first convert to raw using a cooked yield you have actually measured for that item and method. Mixing raw and cooked weights can create an apparent shortage even when the inventory reconciles on a consistent basis.

What to gather

• Opening and closing counts, with the unit written on every line
• Delivery and receiving records showing when each delivery arrived relative to the count cutoff
• The invoices, exactly as issued
• POS item sales and the recipe quantity for each item that uses the product
• The waste log, transfers and staff meals

Start with the fictional example. For real records, use only data your business has approved for that service and remove employee names, schedules and unrelated confidential details. The assistant needs quantities and units, not people's identities.

The fictional example

Boneless chicken thigh at $3.00 per raw pound. A case holds four 10 lb bags, so 40 lb for $120.

• Opening count: 84 lb
• Receipts on the records: 160 lb (4 cases)
• Closing count as written: 3 lb

Recorded usage: 84 + 160 − 3 = 241 lb.

The POS shows 480 bowls, each with a 5 oz raw portion: 480 × 5 = 2,400 oz = 150 lb of theoretical usage.

Gap: 241 − 150 = 91 lb, or $273.

Check the records line by line

Each line below counts only because a record or a physical check confirms it.

Corrected usage: 84 + 120 − 30 = 174 lb. That equals 150 (bowls) + 8 (catering) + 6 (waste) + 10 (unresolved), so the quantities reconcile.

A note on the late delivery: leave the invoice as it is. For the count, match receipts to when the product physically arrived relative to the cutoff, so the Monday case belongs to the next period's receipts. Whether anything changes in the books is your accountant's call. This guide doesn't set a posting rule.

Annotate the unresolved balance; don't shrink it

The unresolved line stays at 10 lb until evidence moves part of it into the verified list. What you can add is a note on where to look.

Suppose a manager weighs ten raw portions and gets 52.5 oz in total, an average of 5.25 oz instead of 5. If every one of the 480 bowls had run that heavy, the extra would be 480 × 0.25 oz = 120 oz, or 7.5 lb ($22.50). That's an extrapolation from ten portions. It doesn't show what 480 bowls actually averaged.

So the note on the balance reads something like: "Unresolved: 10 lb ($30). Lead: portions may be running heavy. The sample would correspond to 7.5 lb extra only if every bowl averaged the same weight; it establishes no upper bound or historical total. Next check: weigh portions across shifts and stations for a set period, and check the scoop or scale in use." Don't report 7.5 lb as explained, and don't report the other 2.5 lb as a confirmed remainder.

The two-pass prompt

Run the passes separately so the arithmetic is settled before anyone starts explaining it.

Pass 1: check the data

You are helping a restaurant manager check one inventory item. Use only the numbers I give you. Do not guess missing values. First confirm that every count, receipt, recipe quantity and portion is on the same weight basis (raw or cooked). If any is not, stop and ask for a verified yield. Then list: (a) values whose unit is unclear or inconsistent with the pack size, (b) values that look out of pattern and should be recounted, (c) missing records (delivery time relative to the count cutoff, waste log, transfers, POS items without a recipe). Then show recorded usage = opening + receipts - closing and theoretical usage = units sold x recipe quantity, with the arithmetic.

Pass 2: list explanations, and keep them separate

For the gap in pounds, list the possible record or process explanations, easiest to check first. For each one, say what record or physical check would confirm or rule it out, and how many pounds it could explain if confirmed. Put only items I confirm with evidence in a "verified" list. Report the gap minus verified items as "unresolved". Attach every unconfirmed explanation to the unresolved balance as a note with its next check; never subtract it from the unresolved figure. Treat a sample measurement as a lead, not proof about every unit. Do not name, profile or speculate about any person, and do not conclude theft. Do not recommend accounting entries.

Who does what

• The AI does the arithmetic, checks units and the weight basis, and lists the evidence each explanation needs.
• The manager recounts, pulls receiving records, checks recipe links and weighs portions.
• The owner decides which process to fix and whether anything needs escalating. The accountant handles any adjustment to the books.
• Staff keep units on count sheets, log waste at the station and portion to the recipe. They're never named in the prompt.

What success looks like

Every pound of the gap is either verified with evidence or sits in the unresolved balance, and every lead is written on that balance along with its next check. The fixes in this example come from the process itself: a unit on every count-sheet line, a clear delivery cutoff, recipe links for new POS items (catering included), a waste log kept where the waste happens, and a scale for raw protein portions.

When the AI gets it wrong

Recompute every number it gives you. Throw out any pack size, yield, price or explanation it offers that you didn't provide. If the AI output and a recount disagree, repeat the count and check the units and arithmetic before relying on either figure.

If a gap keeps showing up

Count that item on its own for the next few weeks, and tighten receiving and storage. If you have a concern about a specific person, handle it through your normal HR process with proper advice, not in an AI chat.

Related

• Food cost percent: purchases are not the same as consumption, for the period-level view
• How to use AI to read restaurant invoices without losing control of costs, for pack sizes and units
• Restaurant food cost calculator, to cost a recipe from purchased ingredients and usable yield