What Are Par Levels and Why Do They Matter?
A par level is the minimum quantity of an ingredient you need on hand at all times. When your stock drops to par, you reorder. When it's above par, you wait. It's the baseline that keeps your kitchen running without the panic of a Saturday night stockout.
Without par levels, restaurant operators wing it. They order when the walk-in looks empty, when a cook says they're running low, or when a manager notices something is out. That's how you get stockouts on busy nights, over-ordering that spoils before it's used, and vendor relationships damaged by last-minute rush orders at a premium.
ParSheetOS was built specifically to solve this: staff count inventory at end of shift, the system flags what's below par, and purchase orders go out automatically. No guesswork, no stockouts, no spoilage from over-ordering.
The Par Level Formula
Setting par levels starts with one formula:
Each component is a decision you make based on your restaurant's actual data:
Average Daily Usage
How much of the item you use per day, on average. Do not guess this. Pull it from your POS data or from actual inventory logs over 2–4 weeks. Track all usage: what goes into dishes, what gets prepped and trimmed, what gets comp'd, and any predictable volume spikes (Friday dinner rush, Sunday brunch, holidays).
If your usage varies wildly by day of the week, weight your average by actual volume. A restaurant that sells 40 chicken dishes on Saturday and 8 on Tuesday should use a higher average daily figure than a simple arithmetic mean would suggest.
Lead Time
The number of days between placing an order and receiving the stock on your shelf. This is not the vendor's stated lead time — it's your actual cycle.
Here's the nuance: most operators order 2–3 times per week, not daily. If you order Tuesday morning and receive Wednesday, and you order again Friday morning and receive Saturday, your effective lead time is roughly 3–4 days — the average time between orders that you're trying to cover between deliveries.
Use your actual delivery schedule, not the vendor's SLA. Broadline distributors (Sysco, US Foods) are typically 1–2 days. Specialty and local vendors may be 3–5 days. Alcohol distributors often run weekly routes.
Safety Stock
A buffer on top of your base quantity that absorbs two risks: unexpected demand spikes and late or incomplete deliveries. It's calculated as a percentage of the base quantity.
Different items warrant different safety stock levels:
- 10% safety stock: Stable items with reliable vendors and predictable demand (flour, dry goods, canned tomatoes)
- 15% safety stock: Items with moderate demand variability or vendors with occasional delays (most proteins, dairy)
- 20–25% safety stock: High-risk items where running out causes a direct service failure (your top 5 selling proteins, signature dish ingredients, vendors with inconsistent delivery records)
Perishables with short shelf life (fresh herbs, delicate produce) should use lower safety stock — a high safety stock on a perishable just means more spoilage before you use it.
3 Worked Examples
Example 1 — Chicken Breast (High Volume, Reliable Vendor)
- Average daily usage: 10 lbs (tracked from 4 weeks of usage data)
- Vendor lead time: 2 days (order in morning, receive next day)
- Safety stock: 20% (top seller, stockout = lost revenue)
Safety stock = 20 × 0.20 = 4 lbs
Par level = 20 + 4 = 24 lbs
When chicken on hand drops below 24 lbs, place an order. You'll have 2 days of coverage plus 4 lbs of buffer.
Example 2 — Roma Tomatoes (Medium Volume, Variable Demand)
- Average daily usage: 6 lbs (salsa, bruschetta, salad prep)
- Ordering twice a week, effective lead time: 3.5 days
- Safety stock: 15% (demand varies by menu mix)
Safety stock = 21 × 0.15 = 3.2 lbs
Par level = 21 + 3.2 = 24.2 lbs → 24 lbs
Round to practical quantities your staff can count. 24 lbs on a sheet is easier to manage than 24.2.
Example 3 — Heavy Cream (Low Volume, Short Shelf Life)
- Average daily usage: 2 quarts (pasta sauce, desserts, a la carte)
- Vendor delivers twice a week, effective lead time: 3.5 days
- Safety stock: 10% (short shelf life, higher safety stock = waste)
Safety stock = 7 × 0.10 = 0.7 quarts
Par level = 7 + 0.7 = 7.7 quarts → 8 quarts
Lower safety stock for perishables prevents waste. 8 quarts on hand, used daily, stays fresh without over-ordering.
Common Par Level Mistakes
Setting par levels wrong creates two failure modes: stockouts (too low) or spoilage (too high). Here are the most common ways operators get both:
Setting par too high "just in case"
Over-ordering is the #1 cause of food waste in restaurants. When par is set too high, you consistently have more on hand than you use, and the excess spoils before you get to it. Start with data-based par levels and adjust down if you're consistently above par at delivery time.
Using the same safety stock for every item
A bottle of hot sauce doesn't need the same buffer as your top-selling protein. Tailor safety stock by item risk: stable items with reliable vendors get 10%, high-volume or unreliable items get 20–25%. A blanket 20% on everything wastes money on items that don't need the buffer.
Setting par levels once and never updating them
Your restaurant isn't static. Menu changes, seasonal shifts, staffing changes, and new vendors all change your actual usage. Par levels should be reviewed every quarter minimum — and immediately after any significant menu or operational change.
Guessing daily usage instead of measuring it
Most operators set par levels based on what "feels right." The result: par levels are wrong in both directions — too high for slow-moving items, too low for fast-moving ones. Two weeks of actual usage tracking eliminates this guesswork entirely and gives you numbers you can defend to your vendor.
Ignoring effective lead time vs. vendor lead time
If you order twice a week, your effective lead time is the average time between your orders (roughly 3–4 days), not the vendor's 1–2 day delivery window. Operators who use vendor lead time instead of their actual order cycle consistently under-order and trigger emergency purchases.
When to Update Your Par Levels
Par levels aren't set-and-forget. Your restaurant's usage changes — seasonally, by menu, and by staffing. Here's when to revisit yours:
- Quarterly review: Even if nothing has changed, review par levels every 3 months to catch drift. Usage patterns shift slowly and operators don't notice until it's a problem.
- Menu changes: Adding a dish that uses chicken thighs? Your chicken par level needs to increase. Removing a popular item? Lower it.
- Seasonal volume shifts: A beachside restaurant in August has meaningfully different usage than in February. Adjust par levels seasonally, not just once a year.
- Vendor changes: Switching from Sysco to a local farm changes your effective lead time, delivery reliability, and order minimums. Recalculate par levels after any vendor change.
- Consistent over/under-ordering: If you're regularly above par at delivery, your par is too high. If you're regularly stocked out between deliveries, your par is too low. ParSheetOS tracks this automatically and flags when par levels need adjustment.