Restaurant Inventory Turnover, Par Levels and the Reorder Point

Why stock is money standing still

An owner rarely asks "what is my inventory turnover". The question that actually gets asked is simpler and angrier: why is there so little money in the account when the walk-in is full, and why did we throw out a case of something last week that we had just paid for.

Both halves of that question have the same answer. Stock is cash that has been converted into a form you cannot spend. It cannot pay rent, it cannot pay a supplier, it cannot pay a wage. It can only turn back into money by being cooked and sold — and until that happens it sits on a shelf losing value, taking up space, and quietly demanding attention from people who could be doing something else.

This is not an argument for holding nothing. A kitchen that runs out of its own signature dish at half past seven has converted a cash problem into a guest problem, which is worse. The whole subject of this page is the distance between those two failures, and the fact that the distance can be calculated rather than guessed.

Three ideas do the calculating, and they are usually taught as three separate topics:

• inventory turnover tells you how fast the money in your stock is coming back to you;
• a par level tells you how much of an item to have on the shelf;
• a reorder point tells you when to place the order.

They are not three topics. They are three views of one arithmetic, and the middle of this page shows them meeting: the par level you set is what produces the turnover you measure. Set the par level from habit and the turnover figure is just a description of your habit.

Two boundaries before we start, so you know what this page is and is not. What the count turned out to say — where product went missing between the delivery van and the plate — is a different question, worked through on theoretical vs actual food cost. What share of your sales the product ate is a third question, and it lives on restaurant food cost percentage. This page is about how much to hold and when to buy, and it does not repeat either of them.

Inventory turnover: what it divides, and what the answer is measured in

Inventory turnover — cost of goods sold divided by average inventory value, for the same period. The result is a number of times, not money and not a percentage.

Inventory turnover = COGS ÷ Average inventory value

• COGS — cost of goods sold over the period, at your booking prices, in PLN;
• Average inventory value — the average value of stock held over that same period, at the same booking prices, in PLN;
• the result — how many times the stock was consumed and replaced during the period, in times per period.

Average inventory value = (Opening inventory + Closing inventory) ÷ 2

• Opening inventory — counted value of stock at the start of the period, in PLN;
• Closing inventory — counted value of stock at the end of the period, in PLN.

Check the dimension out loud, because this is where the concept is most often mangled: PLN divided by PLN cancels to a pure number. That pure number only means anything once you say which period it belongs to. "Turnover of four" is not a statement. "Four times a month" and "four times a year" describe two completely different businesses, and one of them is not a restaurant.

Everything below is a worked example built from round teaching numbers. They were chosen to make the arithmetic visible, not measured in any restaurant, and they are not targets for yours.

A restaurant closes a 30-day period. Stock counted at the start came to 17 000 PLN, stock counted at the end to 15 000 PLN, and cost of goods sold for the period was 60 000 PLN. Average inventory is (17 000 + 15 000) ÷ 2 = 16 000 PLN. Turnover is 60 000 ÷ 16 000 = 3.75 times in that month.

Why this page prints no target range for turnover

You have certainly seen a band quoted — some number of turns per month presented as what a well-run kitchen achieves. We went looking for a publisher before printing one, and there is none. What food service holds in stock is published: GUS, Wyniki finansowe przedsiębiorstw w 2025 r., published 02.04.2026 puts the closing inventory of the 653 catering companies with ten or more employees that keep full accounts at 345.8 mln PLN on 31 December 2025. How fast that stock turns is not published: the ratios the statistical office calculates by industry are cost level, profitability, trade payables against trade receivables and financial liquidity, and inventory turnover is not among them. The ranges circulating online trace back to software vendors' blog posts citing each other. The reason a universal band cannot exist is arithmetical rather than editorial, and it is demonstrated further down this page: turnover is largely dictated by how often your supplier delivers and how long the van takes, so two honestly run kitchens on different delivery calendars will produce different turnover figures and both will be right. The general case of this problem — an industry number with no traceable source — is worked through on restaurant prime cost.

Days of inventory on hand: the same number in a unit you can act on

Days of inventory on hand — days in the period divided by inventory turnover: how many days your current stock would last at the current rate of consumption.

Days of inventory = Days in period ÷ Inventory turnover

• Days in period — the length of the period you measured, in days;
• Inventory turnover — the figure calculated above, in times per period;
• the result — in days.

Days divided by times-per-period gives days. On the running example: 30 ÷ 3.75 = 8 days.

There is a second road to the same number, and taking it is a good habit because it catches arithmetic mistakes immediately:

Days of inventory = Average inventory value ÷ (COGS ÷ Days in period)

• COGS ÷ Days in period — average daily cost of goods sold, in PLN per day.

Average daily COGS here is 60 000 ÷ 30 = 2 000 PLN per day, and 16 000 ÷ 2 000 = 8 days. The two roads meet, as they must.

Days is the version to put in front of a chef, and turnover is the version to put in front of an accountant. "We hold eight days of food" is a sentence a kitchen can argue with. "Our turnover is 3.75" is a sentence nobody can act on.

The whole-restaurant figure hides the only thing worth knowing

Eight days across the whole kitchen is an average of things that have nothing in common. Inside it there is fish that must move in a day or two, and there is a sack of flour that will still be there next month. Both are averaged into one number, and the number describes neither.

That is why the aggregate turnover figure is worth calculating once a period and acting on almost never. The decisions live one level down — at the group, and then at the item. A whole-restaurant figure is useful for exactly one thing: comparing this month against your own previous months, on the same definitions, to see whether the total amount of cash you are keeping on shelves is drifting.

Comparing it against another site of your own is the same trap one size larger. Two kitchens with different menus, different suppliers and different storage will produce different turnover figures with nobody doing anything wrong, so each site needs its own series before any of them can be read side by side — which is the general problem of running several locations on one screen.

Average daily usage: the one input both par level and reorder point are built from

Everything from here on is built on a single measured quantity, and if you get this one wrong, both systems downstream inherit the error.

Average daily usage — the quantity of an item consumed per day, measured over a period long enough to include your quiet days and your busy ones.

Average daily usage = Quantity used over the period ÷ Days in the period

• Quantity used over the period — in the item's own unit: kilograms, litres, pieces;
• Days in the period — the number of days measured, including the days you were closed if the period covers them;
• the result — in units per day.

Follow one item through the rest of this page. Chicken breast, bought at 20 PLN per kilogram, and over a 30-day period the kitchen used 360 kg. Average daily usage is 360 ÷ 30 = 12 kg per day.

"Used" is a count, not an invoice

Quantity used is not quantity purchased. It is opening stock plus deliveries minus closing stock, in units rather than in money — the same shape as the money formula, one level of detail lower. A month in which you happened to buy heavily ends with product still on the shelf, and reading purchases as usage would tell you to buy heavily again. Where that difference comes from, and what it means when the counted usage and the recipe-implied usage disagree, is the subject of theoretical vs actual food cost; here it is enough to know that par levels built on invoices instead of counts inflate themselves every cycle.

Peak daily usage is a second, separate measurement

Peak daily usage = the highest single-day consumption observed in the same period

• measured in the same unit, from the same records, over the same days.

For the running item, the busiest single day took 18 kg. This is not the average plus a comfortable margin; it is an observed maximum, and it has to be observed rather than invented, because it is what the safety stock is built from. If your records cannot produce it, that is itself the finding: build the record first and the par level afterwards. If instead of looking backwards you want to look forwards — because next week has a public holiday and a football match in it — the arithmetic of turning a demand forecast into an order quantity belongs to restaurant demand forecasting, and this page takes the usage figure as given.

Par level: the quantity that carries you to the next delivery

Par level — the target quantity of an item to hold on the shelf at the start of each order cycle, so that it lasts until the next delivery arrives.

Par level = Average daily usage × Order cycle days + Safety stock

• Average daily usage — in units per day;
• Order cycle days — the number of days between one delivery of this item and the next, in days;
• Safety stock — a buffer quantity, in units, calculated in its own section below;
• the result — in units.

Units per day multiplied by days gives units, and units plus units gives units. The dimension survives.

The running item is delivered every three days, and its safety stock works out at 12 kg. Par level is 12 × 3 + 12 = 48 kg.

A par level is not an order. It is a target you top up to:

Order quantity = Par level − Stock on hand at the moment of ordering

• both terms in the item's own unit; a negative result means you already hold more than the par level and order nothing.

Delivery day arrives and the count shows 19 kg still on the shelf. The order is 48 − 19 = 29 kg. Nobody has to remember what was ordered last time or guess how busy next week feels — the shelf is counted and the arithmetic does the rest.

The shorter the cycle, the smaller everything in that formula becomes. At the extreme — an operation ordering for tomorrow, every day — the cycle term almost disappears and the par level collapses towards the safety stock alone. That is a very cheap way to hold stock and a very unforgiving one, because a single mistake in the daily order has nowhere to hide: the shape of that failure is described in what happens when a daily order changes.

Reorder point: the level at which the order has to go out

Reorder point — the stock level at which a new order must be placed so that the item does not run out before the delivery arrives.

Reorder point = Average daily usage × Lead time + Safety stock

• Average daily usage — in units per day;
• Lead time — days between placing the order and the goods being usable in the kitchen, in days;
• Safety stock — the same buffer quantity, in units;
• the result — in units.

Lead time — days between placing an order and having the goods usable in the kitchen. Note the last four words. Lead time is not the delivery window the supplier quotes; it ends when the product has been received, checked, weighed and put away, and it includes the hours it spends sitting in a corridor because it arrived during service.

The running item has a lead time of two days. Reorder point is 12 × 2 + 12 = 36 kg. When the shelf reaches 36 kg, the order goes out that day, whatever the calendar says.

One system per item — running both is how you buy the buffer twice

This is the point at which most kitchens quietly go wrong, and it costs real money without ever producing a visible error.

Par level and reorder point are not a pair. They are two alternative control systems, and each one is complete on its own.

Apply both to the same item and you hold the safety stock twice: once inside the par level and once inside the reorder point. The result is a shelf that never runs out and a business that is quietly financing an extra buffer on every line it does this to — invisible, because nothing ever breaks. Pick one system per item and write down which one it is.

In practice the choice usually makes itself. An item that arrives on a fixed supplier calendar — three deliveries a week, take it or leave it — is a par level item. An item you can order on any day, or one whose usage is too irregular for a calendar to fit, is a reorder point item. A kitchen normally runs both systems side by side across the store, but never both on one line.

Safety stock: what it insures against, and what it does not

Safety stock — a buffer quantity held against variation in demand over the lead time.

Safety stock = (Peak daily usage − Average daily usage) × Lead time

• Peak daily usage — the observed maximum, in units per day;
• Average daily usage — in units per day;
• Lead time — in days;
• the result — in units.

Units per day minus units per day gives units per day; multiplied by days it gives units. On the running item: (18 − 12) × 2 = 12 kg.

Now the part that most explanations of this formula skip, and skipping it is how kitchens get blindsided. This buffer does not insure you against a late delivery. Read the formula again: the only variable in it that can move is demand. It answers one question — if the next two days are both as busy as my busiest observed day, do I have enough — and it answers nothing else. If the van fails to arrive on the day it was supposed to, this quantity was never designed to help, and it will not.

Covering a late delivery is a separate decision, and it is a decision rather than a calculation:

Late-delivery buffer = Average daily usage × Delay days you choose to cover

• Delay days you choose to cover — a number you pick, in days;
• the result — in units, held on top of the safety stock.

Choosing one day of cover on the running item adds 12 × 1 = 12 kg. There is no formula that produces the "correct" number of delay days, because it depends on how reliable this particular supplier has actually been and on what an empty line costs you in this particular dish — and both of those you know and we do not. What is not honest is holding the demand buffer and telling yourself it covers the van. Keeping the record of which supplier delivers late, and how late, is the sort of thing that belongs in a system rather than in a memory: see integrations for where supplier documents land, and what a restaurant can hand over to a system for what stays with a person.

The three numbers are one calculation: your par level sets your turnover

Here is the join between the two halves of this page, and it is the reason all three concepts belong on one page rather than three.

Under a par level system, the stock of an item swings between two known quantities. Just after a delivery it stands at the par level. Just before the next one, in an ordinary period, it stands at the safety stock. So the average value of stock held is not a mystery — it is the midpoint of that sawtooth:

Average stock under a par system = (Par level + Safety stock) ÷ 2

• both terms in units; the result in units, converted to money at your booking price.

Run the numbers for the chicken line. Par level 48 kg, safety stock 12 kg, so the average holding is (48 + 12) ÷ 2 = 30 kg, which at 20 PLN per kilogram is 600 PLN of cash sitting in that one line. Monthly usage is 360 kg, so the item's COGS for the month is 360 × 20 = 7 200 PLN. Its turnover is 7 200 ÷ 600 = 12 times a month, and its days of inventory are 30 ÷ 12 = 2.5 days — which is also 30 kg ÷ 12 kg per day, exactly as it should be.

Nothing was measured to get that turnover figure. It fell out of the par level, and the par level fell out of the delivery calendar. Now move one thing at a time and watch what happens.

Every cell is arithmetic from the formulas above, on the same 12 kg per day of usage and the same 20 PLN per kilogram.

Three things are worth saying out loud about that table.

The kitchen did nothing in any of the three rows. Same dishes, same portions, same guests, same discipline. Turnover moved from 12 to 15 and down to 8.57 because a supplier's calendar and a supplier's van moved. That is the whole answer to "what should my turnover be": it is largely a property of your supply arrangements, which is why nobody can publish a number for it.

Ordering more often released cash, and the amount is calculable. Going from a three-day cycle to a two-day cycle cut the average holding on this one line from 600 PLN to 480 PLN — 120 PLN freed, permanently, on one ingredient. Whether that is worth it depends on the delivery fee, the extra receiving labour and the extra counting, all of which you can price and we cannot.

A longer lead time is expensive twice over. It raises the safety stock and it raises the reorder point, so the same restaurant carries 42 kg instead of 30 kg — 240 PLN more cash parked in one line — purely because the van got slower. When a supplier proposes a change to the delivery schedule, this is the arithmetic that says what the change is worth.

Scale that logic to the whole store and it stops being an ingredient story:

Cash released = (Days of inventory before − Days of inventory after) × Average daily COGS

• Days of inventory — in days, before and after the change;
• Average daily COGS — cost of goods sold divided by days in period, in PLN per day;
• the result — in PLN, released once.

Days minus days multiplied by PLN per day gives PLN. On the whole-restaurant example, moving from 8 days of inventory to 6 releases (8 − 6) × 2 000 = 4 000 PLN. It is released once, not every month — this is a one-off return of working capital, not a recurring saving, and calling it a monthly gain is one of the more common ways this calculation gets oversold. Where that money shows up in the accounts, and why it is not profit, is a finance question rather than a kitchen one: see finance and the numbers an owner actually looks at.

Product groups do not turn at the same speed, and should not

Averaging fish with flour produces a number that describes neither. Grouping is the first thing to do to an aggregate turnover figure, and the groups more or less pick themselves.

Notice that the column is "faster or slower than the others", not a number of turns. There is no published figure for how fast each group should move, and any table that hands you one has invented it.

The one place where the groups get a genuinely hard limit is fresh product, and it comes from law rather than from management.

Polish law puts a ceiling on the par level of perishables

You can decide how much cash to keep in flour. You cannot decide that about product past its date. Under the Polish act of 25 August 2006 on food and nutrition safety, art. 100(1)(1), consolidated text Dz.U. 2023 poz. 1448 as amended by Dz.U. 2025 poz. 1424, anyone who "uses in production or places on the market a foodstuff after its use-by date or its date of minimum durability" is liable to a fine. Art. 100(2) raises the penalty to detention, restriction of liberty or a fine in one narrower case only: food of significant value that is past its use-by date specifically. Food that is only past its date of minimum durability stays outside art. 100(2) altogether — the fine under art. 100(1)(1) still applies to it, the arrest does not.

Read as a stock rule, that says something specific: for any item carrying a use-by date, the par level has a legal ceiling regardless of what the usage arithmetic produces.

Maximum defensible par level = Average daily usage × Remaining shelf life in days on receipt

• Remaining shelf life in days on receipt — days from delivery to the date on the pack, in days;
• the result — in units.

Units per day multiplied by days gives units. If the usage-based par level comes out above this ceiling, the ceiling wins and the order cycle has to shorten — the arithmetic is telling you to buy more often, not to buy more. And the days remaining on receipt are a receiving check, not an assumption: product delivered with less date on it than usual silently lowers this ceiling on the day it arrives.

Turning stock too fast is also expensive

The reflex of the whole topic is "more turns is better", and pushed far enough it stops being true. Very high turnover means very little slack, and slack is what absorbs an ordinary bad evening.

What it actually costs shows up in four places, none of which appear in the turnover figure itself. Stockouts become routine, and their cost is calculated in the next section. Emergency buying replaces planned buying — someone drives to a cash-and-carry at retail prices, which converts a supply problem into a food cost problem and hides it there. Receiving labour multiplies: every extra delivery is a person off the line, checking, weighing, putting away. And delivery fees and minimum order values turn small frequent orders into a per-kilogram premium that is easy to overlook because it hides in the invoice rather than in the ingredient price.

So the honest framing is not "raise turnover" but "hold the smallest quantity that keeps the menu available at the delivery frequency you can actually afford". Those three constraints — cash, availability, delivery cost — are what the par level formula balances, and they are why the answer is specific to your restaurant.

Stockouts: how to count them, and what an empty line costs in the dining room

Most kitchens never count stockouts at all, which means the entire cost side of the argument for holding stock is missing from the conversation. Counting them is not hard and it does not need a system to start.

Stockout — an item unavailable when it was supposed to be on sale: a lost sale and a service failure at the same time.

Stockout rate = Days an item was unavailable ÷ Days the item was on the menu × 100

• Days an item was unavailable — days on which the dish could not be sold, in days;
• Days the item was on the menu — days on which it was supposed to be available, in days;
• the result — a percentage.

Days divided by days cancels, and multiplying by 100 makes it a percentage.

There is no published threshold for this figure either, and inventing one would be the same offence as inventing a turnover band — what makes it useful is the ranking. Sort your menu by it, and the top of that list is where the par levels are wrong.

Then price it. The instinct is to treat every guest who wanted the missing dish as a guest lost, and that instinct overstates the damage badly, because most guests order something else.

Stockout cost = Walkouts × Contribution margin per cover + Substitutions × (Contribution margin of the unavailable dish − Contribution margin of the substitute)

• Walkouts — guests who left rather than order something else, in guests;
• Contribution margin per cover — the margin an average guest contributes, in PLN per guest;
• Substitutions — guests who ordered a different dish instead, in guests;
• the two contribution margins — in PLN per dish;
• the result — in PLN.

Guests multiplied by PLN per guest gives PLN; guests multiplied by a difference of two PLN-per-dish figures gives PLN; PLN plus PLN gives PLN. The definition of contribution margin per cover is not ours to make up twice — it belongs to the restaurant break-even point, and this page uses it unchanged.

An evening where the salmon runs out at 19:40. Fourteen guests would have ordered it; eleven took something else and three left. The salmon contributes 38 PLN, the dish they switched to contributes 29 PLN, and an average cover contributes 34 PLN. The cost is 3 × 34 + 11 × (38 − 29) = 102 + 99 = 201 PLN.

Two pieces of honesty about that 201 PLN. The walkouts are an estimate, not a measurement. Your till has no record of a guest who read the board and left; somebody has to notice and write it down, and if nobody does, the first term of this formula is a judgement call. And the substitution term is usually the bigger one — here 99 PLN of the 201 PLN came from guests who stayed and spent, just on something less profitable. That is the part the "lost guest" framing misses entirely, and it is also the part you can reduce without holding a gram more stock, by making sure the substitute suggested is a good one.

Set that 201 PLN against the cost of preventing it. Carrying an extra two days of salmon means more cash on the shelf and a real risk of throwing it away against a hard date. Sometimes the arithmetic says hold more; on slow lines with short shelf lives it very often says the opposite, and take the occasional hit.

Counting: full counts, cycle counts, and a daily short list of your most expensive lines

Every formula on this page needs a count. Without one, usage is an invoice total, the par levels drift upwards, and the turnover figure is describing your buying rhythm rather than your kitchen.

The three are not alternatives; they stack. The full count is what closes the period and is the only one that produces a turnover figure. Cycle counting is what keeps par levels honest between closes. And the daily short list — the handful of lines with the highest value moving through them, not ten items because ten is a round number — is what turns a monthly discovery into a same-day one.

One warning that belongs on somebody else's page and gets one line here: a count is only as good as what was booked in against it, and receiving errors — the invoice weight that was never checked against the actual weight — corrupt the arithmetic before the kitchen touches it. That failure and what it does to your numbers is theoretical vs actual food cost; getting supplier documents into the books without retyping them is invoicing automation.

What these three numbers do not tell you

They are useful because they are narrow, and the narrowness has edges worth naming.

They say nothing about price. An item whose supplier raised the price by a fifth turns over at exactly the same speed and costs you more; that belongs to food cost percentage. They say nothing about why product disappeared — stock that walked out of the back door reduces your closing count and raises your turnover figure, which is one of the few cases where a number moving in the "good" direction is bad news. They say nothing about demand next week: every formula here is built on what already happened, and turning an expectation into an order quantity is restaurant demand forecasting.

They also cannot see a supplier who is unreliable rather than slow. A lead time of two days that is honoured eight times in ten is not a two-day lead time in any useful sense, and no amount of safety stock arithmetic fixes a supply relationship — it only prices it.

And a closing caution on the money. Cash released from stock is a one-off, not an income stream. The first time you shorten your cycle you get a payment back; from then on, you simply hold less. It is a genuinely good thing to do, and it is not a monthly saving, whatever anyone tells you. Keeping the ordering rhythm, the counts and the supplier calendar in one place instead of three notebooks is what integrations and forecasting are for, with external signals covering the calendar events that move usage before they move your shelf. The wider set of restaurant economics pages sits together in our section for restaurants.

Frequently asked questions

What is a good inventory turnover for a restaurant?

There is no published figure this page will give you, and the reason is arithmetical rather than cautious. Turnover is set mostly by your supplier's delivery frequency and lead time: on identical usage, moving from a three-day to a two-day delivery cycle takes the worked example on this page from 12 turns a month to 15, and stretching the lead time from two days to four takes it down to 8.57. Two well-run kitchens on different supply arrangements will produce different figures and both will be correct. What is real is your own series — the same calculation across your own closed periods, with the events noted beside each one.

How do I calculate a par level?

Multiply your average daily usage of the item by the number of days between deliveries, then add the safety stock. On the worked example on this page — 12 kg a day, delivered every three days, safety stock 12 kg — the par level is 12 × 3 + 12 = 48 kg. The order you actually place is the par level minus what is on the shelf when you order: with 19 kg counted, you order 29 kg. Average daily usage has to come from counts rather than from invoices, or the par level inflates itself every cycle.

What is the difference between a par level and a reorder point?

They are two different control systems, not two steps of one. A par level works on a calendar: the delivery day comes, you count, and you top up to the target. A reorder point works on a level: whenever the shelf drops to the trigger quantity, the order goes out, whatever day it is. Use one or the other on any given item. Running both on the same line means the safety stock is included twice, so you carry an extra buffer permanently and nothing ever visibly breaks to tell you.

How much safety stock should a kitchen hold?

Take your observed peak daily usage, subtract your average daily usage, and multiply the difference by the lead time. On the worked example: (18 − 12) × 2 = 12 kg. Be clear about what that quantity does — it covers demand being higher than average while you wait for the delivery, and nothing else. It does not cover a delivery that arrives late. Covering that is a separate quantity, average daily usage multiplied by the number of delay days you decide to carry, and how many days that should be is a judgement about your supplier that no formula can make for you.

Can inventory turnover be too high?

Yes, and the costs of it do not appear in the turnover figure. Very fast turnover means very little slack: stockouts become routine, someone starts buying at retail prices in an emergency and hides a supply problem inside your food cost, every extra delivery takes a person off the line to receive it, and delivery fees or minimum order values add a premium per kilogram. The target is not the highest possible number of turns but the smallest holding that keeps the menu available at a delivery frequency you can afford.

How often should a restaurant count inventory?

Count everything at period close, because that is the only count that produces a closing value and therefore a real COGS and a real turnover figure. Between closes, cycle count a rotating subset so that drift on individual lines shows up while you can still do something about it, and count a genuinely short list of your highest-value lines daily. The three stack rather than compete. A period that ends without a full count gives you an estimate, and an estimate cannot serve as a baseline for the next comparison.

What does a stockout actually cost?

Less than a lost guest and more than nothing, and the arithmetic separates the two. Count the guests who left, multiply by the contribution margin of an average cover, then count the guests who ordered something else instead and multiply by the difference between the contribution margin of the missing dish and that of the substitute. In the worked example on this page, three walkouts and eleven substitutions come to 3 × 34 + 11 × (38 − 29) = 201 PLN, and most of that is the substitution difference rather than the walkouts. Bear in mind that the walkouts are estimated: your till never sees a guest who read the board and left.

How do receiving errors distort inventory numbers?

They corrupt the arithmetic before the kitchen is involved. If the invoice says a weight that was never checked against the scales, then your purchases figure is wrong, your usage figure is wrong, and every par level built on that usage is wrong in the same direction. Short deliveries booked in full also lower the remaining shelf life you can rely on, which quietly lowers the ceiling on your par level for that item. Weigh against the document at the door, record the difference, and treat receiving as part of the count rather than as paperwork.

Take one item — the one you most often run out of, or the one you most often throw away — and put your own three numbers into the formulas above: average daily usage from counts, days between deliveries, and lead time measured to the moment the product is actually usable. That gives you a par level, a reorder point and, from those two alone, the turnover that item will produce. Then write beside it which of the two control systems you are running on that line, so the next person to look at the shelf does not add the buffer a second time.