Restaurant inventory: a practical routine for receiving and stock counts
- restaurant inventory
- stock counts
- purchasing
- Published
- Reading time
- 6 min read
- Written by
- eRestro Editorial Team
A stock number becomes useful when the team can explain where it came from. A delivery adds to it, a recorded use or waste movement reduces it, and a physical count checks the result against the shelf. If these steps use different units or happen at different times, even a polished inventory screen can show a misleading answer.
Start with a manageable group of ingredients: the items used most often, the items that regularly run short, or the ingredients that need a closer cost review. Establish a reliable routine before expanding the catalogue. The purpose is to help the next service and the next purchase, not to create a second job that nobody has time to maintain.
Give each ingredient one clear stock unit
Choose the unit in which the kitchen can reasonably record and count an ingredient. Flour might be tracked in kilograms, milk in litres and sealed soft-drink bottles in units. A supplier may sell a sack, carton or case; that purchasing pack is not automatically the same as the stock unit.
Write the conversion down where the receiver can see it. If one sealed sack contains five kilograms, two sacks mean ten kilograms received. If the supplier changes the pack size, verify the conversion before accepting the old default. Similar product names can also hide differences in usable quantity, so keep distinct stock items when the operation needs that distinction.
Recipe quantities must agree with this setup. A recipe entered as 200 kilograms when the intended quantity was 200 grams will create a much larger problem than a missed weekly report. Ask the person who prepares the dish to check the unit and quantity, then test the record with a small, understood example.
Record the delivery that arrived, not only the purchase that was ordered
A purchase order records the restaurant’s request. Receiving records what was actually accepted. Keep those events separate so a short delivery does not make the shelf look fuller than it is.
For each delivery, compare the supplier, item, pack size and quantity with the purchase record. Check the physical delivery using the restaurant’s established receiving procedure. Record the accepted quantity and leave a clear note about an unresolved difference. A substitute item needs a deliberate decision; it should not silently inherit the old ingredient’s name or conversion.
| Situation | Useful inventory action | Question to resolve |
|---|---|---|
| Ordered ten kilograms; eight arrived | Record eight kilograms received | Will the supplier deliver the remainder? |
| Two cartons arrived in a different pack size | Check the quantity conversion before receiving | What is the actual stock-unit quantity? |
| One item was rejected | Keep rejected quantity out of accepted stock | Who follows up on the supplier adjustment? |
| The delivery arrived after the count | Record the timing consistently | Does this receipt belong before or after the count cutoff? |
The eRestro inventory walkthrough shows stock, purchasing and audit screens. Treat the purchase and receiving controls as part of this operating routine, rather than assuming the software can inspect the physical delivery for the team.
Use a consistent count cutoff
A count needs a clear point in time. Counting the storeroom while ingredients continue to move into service makes the result difficult to interpret. Choose a practical cutoff and tell the team how to handle receipts, transfers or use during the count.
For a small venue, one person can count and another can review the larger differences. Work in a consistent shelf order so the same open pack is not counted twice or missed between locations. Record the quantity that is actually present before looking for an explanation. Adjusting the count to match the expected number defeats the purpose of counting.
Keep the measurement method consistent too. An open container may require weighing or another repeatable measurement. Do not compare an exact weight this week with an unexplained “roughly half full” estimate next week and treat the difference as a precise operational signal.
Work through one difference before changing the record
Consider a fictional ingredient tracked in kilograms. The opening record is ten kilograms. Eight kilograms are received, six are recorded as used and one is recorded as waste. The expected closing quantity is eleven kilograms: ten plus eight, minus six, minus one.
If the physical count is nine kilograms, the unexplained difference is two kilograms. That does not establish a cause. Check the receipt, unit conversions, waste entry and count timing first. A missed movement or mistaken pack size can create the same difference as unrecorded use.
Write down the reason for a correction once it is understood. If a difference remains unresolved, preserve that fact rather than inventing a confident explanation. The useful outcome is a better record and a change to the process that caused the problem. Individual blame based on one number rarely produces either.
This is also why a food-cost and menu review needs operational context. Stock and cost figures depend on what was recorded; a report alone cannot explain every change in the kitchen.
Record waste close to the event
Make it easy for the team to record the ingredient, quantity, unit and reason while the event is still understood. A short note such as “prep trial” or “spilled during transfer” is more useful than reconstructing a week of losses on count day.
Review recurring reasons with the kitchen. Repeated preparation waste may suggest a recipe or batch-size conversation; repeated unused stock may suggest a purchasing rhythm problem. Neither observation proves a particular saving is achievable. Change one practice, maintain the records and compare a suitable period with its service context.
Do not count a discarded ingredient as usable stock simply because it remains physically near the shelf. Follow the restaurant’s existing handling procedure and keep the inventory record aligned with what the team can actually use.
Make the routine fit a real shift
Before opening, review the ingredients needing attention and confirm any expected delivery. During receiving, record the accepted quantity once. During service, record meaningful waste or adjustments through the agreed process. At the count cutoff, count consistently and review differences before changing the record.
Assign responsibility clearly. The receiver owns the delivery entry; the counter owns the physical observation; the reviewer checks unexplained differences and approves the next action according to the venue’s permissions. In a small restaurant these may be the same person, but the decisions should still be separate and understandable.
Start the first week with a short review: which entries were confusing, which unit needed explanation, and which count took too long? Improve the routine before adding more reports. A dependable ten-item process is a stronger foundation than a complete catalogue nobody trusts.
Before your first inventory demo
Bring a real example of a stock item, its supplier pack and its recipe unit. Ask the software provider to show a partial receipt, a waste record and a count difference. Review who can change stock and who can see financial information. Confirm module availability, setup help and plan scope in the proposal.
Use the inventory video tour to see the eRestro screens, then compare them with your own receiving and counting process. The goal is a stock record the team can maintain and explain before the next service begins.
Put the guide into practice