Restaurant inventory par levels: how to set them so you stop running out and stop drowning in stock
The assistant manager opens the walk-in at 5:40 a.m. and finds two cases of chicken thigh, half a case of romaine, and almost no citrus. Service starts in eighty minutes. Nobody on the line is sure who counted last, the counts live on a stained clipboard behind the prep sink, and the par sheet on the wall was last rewritten eighteen months ago. The shift that follows is a master class in substitutions, emergency runs, and write-offs. Most of that pain traces back to a single missing discipline: clear restaurant inventory par levels that the team actually uses.
Par levels sound like a back-office accounting topic, but they decide what your cooks can cook, what your bartenders can pour, and whether the menu you designed last month is still possible tonight. This guide walks through how to set par levels that match how your restaurant actually runs, how to keep them current, and how to wire them into the daily rhythm of a working kitchen without turning every shift into an inventory project.
What a par level actually is
A par level is the amount of an item you want to have on hand at a specific moment in the operating cycle. It is not the amount you own, the amount you ordered, or the amount you hope to use. It is a target quantity that triggers a reorder once your on-hand count drops below it. In most restaurants, the moment that matters is the start of service, so the par usually reflects what the kitchen and bar need in the building before the doors open.
Two numbers work together. The par level is the target, and the par reorder point is the lower threshold that tells you it is time to buy. If your par for olive oil is six liters and you want to reorder when you have two left, the par is six and the reorder point is two. Some operators collapse these into a single number (“always keep six on hand, order when we hit two”), which works fine as long as the team understands the difference between target and trigger.
Par levels apply to anything that runs out: produce, proteins, dairy, dry goods, beverages, disposables, and even smallwares that quietly break service when they vanish. The format and the math are similar across all of them, even if the review cadence is not.
Why par levels matter for a working restaurant
Bad par levels are expensive in ways that never show up on a single P&L line. They cause missed sales, slow tickets, angry servers, and tired cooks who spend service improvising. They also drive food cost up, because the only reliable cure for a stockout is an emergency vendor run, and emergency runs almost always cost more per unit than the planned order.
Good par levels protect four things at once:
- Service quality. The menu you actually printed is the menu you can serve. If limes disappear by 8 p.m., your bar program and your taco special both suffer at the same time.
- Food cost. Ordering the right amount, at the right cadence, keeps average inventory value down and shrink down with it.
- Cash flow. Stock sitting in a dry-goods cage is cash that is not in the bank. Par levels keep the right amount of working capital tied up in product.
- Team sanity. A cook who trusts the counts can plan prep. A bartender who trusts the counts can build prepped juice without hoarding. Trust comes from a system, not from memory.
None of those benefits require a perfect system. They require a working system that the team understands and that gets revisited when the menu changes.
The core math behind restaurant inventory par levels
Most par level formulas are the same shape: figure out how much you use between orders, add a buffer, and that becomes your target. The detail is in how you measure each variable honestly.
Usage per service period
Start with how much of an item the restaurant actually consumes in one operating cycle. For produce and proteins that turn quickly, the cycle is usually one service. For dry goods and disposables, the cycle can be a week. Track the same unit the team will count with: liters, kilograms, cases, eaches, not a mix.
Lead time
Lead time is the gap between placing an order and having it on the shelf ready to use. Include delivery days, minimum-order cutoff times, off-days, and any time the receiving team will not put product away. If your produce vendor delivers every other day and you need to order by 2 p.m. the day before, the real lead time from the line cook’s point of view is roughly 48 hours.
Safety stock
Safety stock is the cushion that absorbs a busy weekend, a missed delivery, a portioning mistake, or a menu spike. A small cushion is rational; a giant cushion is just hiding money in the walk-in. The honest number depends on how predictable your demand and supply are.
A simple par formula that works
For most line items, a workable par level is:
Par level = (usage per operating period × number of periods between orders) + safety stock
For example, if a café uses four liters of whole milk per service, reorders every other day, and wants one extra service as a buffer, the par is roughly (4 × 2) + 4 = 12 liters. The reorder point would be 4 liters, which is one service of usage. That keeps the line stocked through one missed delivery and a busy morning.
The same shape works for bar and supply items. If a bar uses eleven liters of house vodka per week, orders twice a week, and wants two extra days of cushion, the par is (11 × 0.5) + ~3 = ~9 liters, and the reorder point is the amount you expect to need before the next delivery lands.
Choosing the right counting unit and review cadence
Par levels only work if the team can count accurately in the unit the par is written in. A par sheet that says “flour” with no unit is a par sheet that gets ignored. Pick the unit that matches how the product is actually received and used.
Counting units that match reality
- Eaches for bottles, cans, and prepped items that move one at a time.
- Kilograms or pounds for proteins and produce that the team portions in weight.
- Liters for liquids that are poured or measured by volume.
- Cases for items that arrive and are stored as cases, even if service pulls them out individually.
- Portions for prepped mise en place that already reflects the recipe yield, which is useful for items like portioned fish or pre-cut fries.
Review cadences that fit the product
| Item category | Typical review cadence | Why |
|---|---|---|
| Fresh produce | Daily or before each order | Shrink, weather, and demand swings hit hard and fast. |
| Proteins | Before each order | Cost per unit is high, so accuracy matters. |
| Dairy | Daily or every other day | Short shelf life and steady usage. |
| Dry goods and staples | Weekly | Slow-moving, easy to over-order. |
| Beverages (beer, wine, spirits) | Weekly for fast movers, biweekly for slow movers | The slow end of the list absorbs a surprising amount of cash if par is ignored. |
| Disposables and smallwares | Monthly or per delivery | Run out less often, but the failure mode is total service stoppage. |
The cadence is less important than keeping it. A weekly review that actually happens beats a daily review that drifts after two weeks.
How to set par levels for each area of the restaurant
The shape of the math is the same everywhere, but the failure modes are different. A few area-specific habits tend to make the system stick.
Kitchen: proteins, produce, and prepped mise
Start from your last four weeks of invoices and pull the average usage of the top twenty items by spend. Those are the items where a 10 percent error costs real money. Use real usage, not theoretical usage, because menu changes, weather, and local events shift demand more than most operators expect.
For prepped items, the par should be written in the unit the line cook thinks in. If the cook pulls four trays of cut romaine at a time, the par is trays, not heads of lettuce. A par that matches the working unit is a par that gets used.
Bar: beer, wine, and spirits
Bar pars are where many restaurants carry invisible waste. A bottle of mid-shelf rye that “always” lives behind the bar can quietly tie up cash. Build the bar par from sales mix, not personal preference. Fast-moving well liquor and a few call-liquor favorites need tighter, higher-turn pars. Premium bottles with one or two drinks a night need a par closer to real demand, or they should be reordered only when stock reaches a clear threshold.
For a second working reference, Toast’s guide to restaurant par levels shows the common usage-times-lead-time calculation and explains how demand, delivery schedules, and safety stock change the result.
Draft beer pars depend on keg size, line length, and the time it takes to change a keg mid-service. A reasonable par for a single popular IPA is one full keg on the floor plus one backup, not three full kegs that will go stale before they pour.
Front of house: disposables, smallwares, and paper
To-go containers, napkins, and serviceware tend to be the items the team only notices when they are gone. Their par levels look more like warehouse restock rules: how many cases do we want on the shelf, what is the trigger to reorder, and what is the lead time. A simple bin label with a min and max line works for almost every disposable in the building.
Cleaning and chemical
Sanitizer, dish soap, and grill cleaner run out rarely but the consequences of running out are real. Their pars are often set by safety stock alone, because the only acceptable answer to “do we have enough chlorine tabs” is “yes, always.”
Building a par sheet that the team will actually use
A par sheet is a working document, not a binder that lives in the office. It needs to be readable in the storage area where the count happens, with consistent columns and a clear unit on every line.
Columns that earn their place
| Column | What it holds | Why it matters |
|---|---|---|
| Item name | The exact product as it is stored | “Onion, yellow” and “onion, red” cannot share a row. |
| Storage location | Walk-in, dry store, bar, line | Counters count where the product lives. |
| Unit | kg, L, each, case | Prevents silent unit drift. |
| Par level | Target on hand | What the count should look like at the start of service. |
| Reorder point | Trigger to buy | The number that says “order now.” |
| Preferred vendor | Primary supplier | Removes the guess when several suppliers carry the same product. |
| Notes | Pack size, prep state, allergens | Captures context that does not fit elsewhere. |
Keep one master sheet per area, and post a printed copy in the area where the count happens. The printed copy is the one that gets used. The spreadsheet is the one the manager updates after the count.
What good and bad par sheets look like
A weak par sheet says “pars” in a single column with no unit, no reorder point, and no location. A strong par sheet says exactly what is in the bag, in the unit it is actually used, with a reorder point that a new hire can read and act on. The point of the document is to remove decisions, not to capture them.
Counting and physical inventory without burning the shift
Par levels only stay accurate if the counts behind them are honest. Spot-check culture matters more than the counting method itself.
- Count at the same time every cycle. Before the order goes in is usually best, because the count feeds the order directly.
- Count in the same unit as the par. If the par is in kilograms, weigh the product. Estimating from “half a bag” is how pars drift.
- Count what is actually usable. Trim, spoilage, and product that does not meet spec are not part of the par. Note them separately so the data is honest.
- Have a second set of eyes for high-value items. Proteins and premium spirits are where counting errors cost the most.
- Do not move product during a count. Pause receiving and transfers until the count is done, or the numbers will be wrong by the time the clipboard reaches the manager.
For most operators, a weekly full count is the realistic floor, with a daily walk-through of the items that swing the most. A monthly full count is too slow for fresh product, and a daily full count is more accurate than a small team can sustain.
How menus, sales mix, and seasonality change pars
A par sheet that never changes is a par sheet that gets wronger every month. Three forces push pars out of date faster than anything else: menu changes, sales mix shifts, and seasonality.
When a dish is added or removed, the ingredients tied to that dish need their par reviewed in the same week. A new cocktail that uses a botanical liqueur will quietly drain a par that was set for another era. A dish that gets pulled because it is not selling still leaves a par behind that someone has to remember to retire.
Sales mix shifts are slower and more dangerous. A bar that leans more into tequila over time will burn through agave at a different pace than the par sheet was built for. A neighborhood that fills up with office workers in the winter will change lunch pars compared to the slow summer pattern. A useful habit is to recalculate usage from invoices every quarter and adjust pars that have drifted more than 15 to 20 percent from the new reality.
Seasonality is the same problem on a clock. A coastal town in July and a ski town in February are not the same restaurant. A short note on the par sheet that says “summer par” or “winter par” is enough; a full rewrite every season is not necessary.
Par levels, food cost, and contribution margin working together
Pars are a quantity tool. Food cost is a dollars-and-cents tool. They are tightly linked, but they are not the same thing. A par that is set too high will lift your average inventory value and pull food cost up even if usage is correct. A par that is set too low will trigger emergency orders that quietly inflate invoice cost. The middle is the place where pars and contribution margin both behave.
That is also why pars deserve a place next to menu engineering rather than in a separate silo. Menu engineering looks at which dishes make money and which ones do not, and pars are how the kitchen actually backs those decisions in product. A dish that is priced tightly on paper but cannot be made because the par on its key ingredient is wrong is not really a menu item, it is a promise the kitchen cannot keep. The same idea shows up in a working menu engineering exercise, where the math is only useful if the kitchen can execute it on a Friday night.
Contribution margin and par level also meet on the reorder point. A high-margin dish that sells in volume deserves tighter par discipline on its inputs, because every missed sale costs more. A low-margin dish with sporadic demand can carry a looser par, because the upside of perfect availability is smaller. This is the same logic that contribution margin calculations use on the revenue side, applied to the supply side.
Common par level mistakes and how to fix them
Most par problems are not math problems. They are process and culture problems that show up as math problems.
- One person owns the par sheet. If the assistant manager writes it and the cooks never see it, the counts will be approximate at best. Put the pars where the team counts and ask the team to flag the lines that feel wrong.
- Pars are set from memory instead of usage. Memory is useful, but it is biased toward loud memories. The recent weekend that ran out of limes is more vivid than the quiet Tuesday that used six bottles of the same juice. Use the invoice data, then adjust.
- Par and reorder point are the same number. This collapses the safety stock and turns every order into an emergency. Separate them, even if the gap is small.
- Pars are set per case, but the team counts eaches. A par that does not match how product is counted will be quietly ignored.
- The par sheet is not revised when the menu changes. A dish leaves, but its par stays. The ingredient quietly accumulates until someone notices the cash tied up in old menu leftovers.
- Pars are reviewed once and forgotten. Even a good par sheet drifts within a season. A short monthly check is enough to catch the worst drift.
Tools that help, from clipboard to software
There is no single right tool. There is only the tool the team will use without being chased.
- Clipboard and printed par sheet. Best for small operations with one storage area. Cheap, fast, and the team already knows how to use it.
- Shared spreadsheet. Works for multi-location operators who want a single source of truth. The risk is that the spreadsheet becomes a back-office document the line never sees.
- POS-integrated inventory tool. Pulls usage straight from sales, which is helpful if the recipes and counts in the POS are accurate. Garbage in, garbage out applies here as much as anywhere else in a restaurant.
- Handheld scanner workflow. Faster for larger operations with hundreds of SKUs. The cost is real, but the labor savings show up quickly in operations of a certain size.
The tool matters less than the habit. A clipboard system that gets used every week will outperform expensive software that nobody opens. Many operators also pair pars with a short marketing calendar review and a menu revision schedule, so the pars stay aligned with what the restaurant is actually selling and promoting.
Wiring par levels into the weekly rhythm of the restaurant
Pars become real when they are part of a routine that already exists. Three rhythms tend to cover most of what matters.
Daily: count, order, receive
Before each order, the responsible person walks the storage areas and counts the items that swing the most. The par sheet tells them what to count and what to compare against. The order goes in. The receiving team checks the delivery against the order and notes any short ships or substitutions. The par is the start and end of that chain.
Weekly: review the par sheet
Once a week, the manager walks the par sheet line by line and asks three questions: did we run out of anything we should not have, did we have to throw anything away, and did the order size match usage. A short note next to the lines that drifted is enough. The full rewrite happens later, only if the drift is meaningful.
Monthly: tune the numbers
Once a month, the manager pulls the last four weeks of invoice data and compares actual usage to the current par. Lines that have drifted more than 15 to 20 percent in either direction get a new number. Everything else stays. The discipline of small, frequent corrections keeps the par sheet from needing a full rewrite, and from drifting past the point of usefulness.
Special cases: par levels for tricky items
Some items do not fit the standard model cleanly. The principles still apply, but the form changes.
Prepped and partially used items
Trim, sub-primal cuts, and prepped mise en place are easy to over-count because the human eye rounds up. Weigh the actual usable portion and write the par in the unit the cook thinks in. A par on trimmed brisket should be in trimmed kilograms, not in primal weight.
Items with multiple uses
Eggs go into brunch, bakery, and pasta. A par set only against the brunch forecast will leave the bakery short on a Tuesday. The fix is to write the par against total weekly usage and split the order between the responsible stations, rather than letting each station set its own number in isolation.
Limited-quantity and seasonal items
Truffles, ramps, and other short-window items should be parred against the season, not the year. A “par” that assumes year-round availability is a par that produces waste. A reasonable approach is to set a per-week cap and reorder only when the cap is hit.
Cross-trained ingredients
Items that multiple stations share benefit from a single owner. If the bar and the kitchen both use limes, one person sets the par and both stations report counts. Otherwise the pars fight each other and both sides run out at once.
How par levels connect to the wider business
Pars are a small system inside a larger one. They touch almost every operational decision a restaurant makes, and they quietly shape how the menu feels to the guest.
Service quality is the most visible payoff. A line cook who trusts the counts can hold a ticket instead of running to the walk-in. A bartender who trusts the counts can pre-batch without hoarding. A manager who trusts the counts can spend the night on the floor instead of the ordering screen. That same trust is what makes a small restaurant feel bigger than its headcount, and it is the backbone of any serious marketing plan that promises consistency to guests.
Pars also link to how a restaurant grows. A second location cannot run on the same par sheet as the first, because the demand pattern, the storage layout, and the supplier relationships are different. A par system that is documented in plain language, with units and notes, is a par system that can be handed to a new opening team without losing accuracy. That is also how pars become part of how a brand scales its signature dishes across more than one room.
A short checklist for the first time you build par levels
- Pull the last four weeks of invoices and list the top items by spend.
- Convert each item to the unit the team will count with.
- Estimate usage per operating period and the realistic lead time from each vendor.
- Set the par as (usage × periods between orders) plus a small safety stock.
- Set the reorder point at one period of usage, or sooner if lead time is long.
- Print the par sheet and post it where the count happens.
- Schedule a weekly review and a monthly tune-up.
- Flag pars that drift more than 15 to 20 percent and adjust in writing.
- Revisit the par sheet whenever the menu changes, not at some vague future date.
Frequently asked questions
What is the difference between a par level and a reorder point?
The par level is the amount of an item you want to have on hand at a given moment, usually the start of service. The reorder point is the lower amount that triggers a new order. They are different numbers, even when they are written on the same line.
How often should a small restaurant count inventory?
For most small operations, a weekly full count with a daily walk-through of fresh items is a sustainable rhythm. Daily full counts are more accurate than a small team can usually maintain, and monthly counts are too slow for fresh product.
What is a good safety stock for restaurant inventory par levels?
A common starting point is one extra operating period of usage on top of what the cycle needs. Restaurants with predictable vendors and steady demand can run a tighter cushion, while restaurants with irregular deliveries or sharp demand swings need more.
Should par levels be set in cases or eaches?
Set the par in the unit the team actually counts and uses. If the team pulls product one bottle at a time, the par should be in bottles. If product is received and stored as cases and pulled by the case, the par can stay in cases, as long as that is also the unit the counter uses.
How do I set a par for a brand new menu item?
Start with the recipe yield and a conservative estimate of weekly sales, then add a safety stock. Treat the first four to six weeks as a calibration period and adjust the par based on actual usage once you have invoice data and sales numbers.
Do par levels work for bar programs the same way they do for kitchens?
The math is the same, but the failure modes are different. Bar pars benefit from being built on sales mix, with tight pars on fast-moving well liquor and looser pars on slow-moving premium bottles. A useful bar par prevents both stockouts and the slow accumulation of cash in dusty bottles.
How do I know when a par level is wrong?
Two reliable signals are repeated stockouts on the same item and repeated waste on the same item. Either pattern means the par does not match how the restaurant actually runs, and the number needs to be revisited with fresh usage data.
Can I use the same par sheet for multiple locations?
Only as a starting template. Each location has its own demand pattern, storage layout, and vendor lead times. A shared template saves time, but the numbers on it have to be tuned per site to be honest.
What is the link between par levels and food cost?
Par levels decide how much cash is tied up in inventory and how often the restaurant pays emergency-order prices. A par that is set too high inflates average inventory value, and a par that is set too low drives emergency orders. Both push food cost up; the middle keeps it stable.
Do I need software to manage par levels well?
No. A printed par sheet, a clipboard, and a consistent weekly habit will outperform any software the team does not open. Software helps at scale, especially for operators with many SKUs or multiple locations, but the system matters more than the tool.