If you're running more than one location, par levels might be the single most important number you're not managing correctly. Most multi-unit operators either set them once and forget them — or worse, use the same par level across every store regardless of volume, delivery frequency, or season. The result? One location is always running out. Another is always throwing stuff away.
This guide covers exactly how to calculate par levels, how to adjust them by location, and why getting this right is the difference between a lean operation and one that bleeds cash every week.
A par level is the minimum quantity of an ingredient or item you need on hand at the start of each shift, day, or week. It's your operational floor — the amount that covers expected usage plus a buffer for demand spikes, supplier delays, or a busier-than-usual Saturday.
The formula is simple:
Par Level = Average Daily Usage × Days Between Orders + Safety Stock
Example: Your cafe uses 5 lbs of espresso per day on average, orders every 3 days, and wants a 20% safety buffer:
Without this number, you're guessing. And guessing in multi-location operations doesn't just cause stockouts — it causes inconsistent guest experiences, wasted manager time, and money left on the table every single week.
For a 3-location cafe group, missing par levels by just 10% per location can cost $2,000–$5,000 monthly in waste and lost sales combined. That's real money.
This is where most multi-unit operators get it wrong. They set a "system par" — one number for every store — and wonder why Location A keeps running out while Location C keeps throwing product away.
Every location is different. Your par levels need to reflect that.
A high-traffic downtown location needs 15–30% higher par levels than a quieter suburban spot. Pull your weekly sales data by location and let the numbers drive the multiplier — not assumptions.
If your supplier delivers daily to one location but only twice a week to another, your par levels must reflect the lead time difference. A location on a 3-day cycle needs nearly double the on-hand quantity of one on a daily cycle.
Summer may drive 40% higher cold brew usage. Winter may drop sandwich sales by 20%. Your par levels from January are wrong in July. Build in a quarterly par review — at minimum — and adjust aggressively around major seasonal shifts or local events.
If one location runs a weekend brunch special or a seasonal LTO that others don't, their par levels for those ingredients are completely independent. Don't let a system-wide average pull those numbers down.
A 4-location restaurant group set uniform par levels across all stores based on their highest-volume location. The result:
Once they adjusted par levels by location using 4 weeks of actual usage data, waste dropped 28% and stockout incidents fell to near zero. Same product. Same supplier. Just the right numbers per location.
These two terms get used interchangeably but they're not the same thing:
Think of it like this: if your average daily espresso usage is 5 lbs and you add a 1 lb safety buffer, your par level is 6 lbs total. The safety stock is the 1 lb — it's not extra inventory, it's insurance against the unexpected.
For stable, shelf-stable items: a 10–15% safety buffer is fine.
For high-variance items (fresh produce, proteins): 25–30% is more appropriate.
For items with unreliable suppliers: build in even more — and look at qualifying a backup supplier.
Don't estimate. Pull your actual usage — units consumed per item, per location, per week — for the last 4 weeks. This is your baseline. If you don't have this data yet, start tracking now. You can't set accurate par levels without real numbers.
For most items, 10–20% is the right buffer. Multiply your average daily usage by your order cycle length, then add the buffer percentage on top. Do this per item, per location — not as a blanket system setting.
Par levels are not set-it-and-forget-it. Block 30 minutes at the end of each month to review your counts against your pars. Are you consistently above par on certain items? Lower it. Consistently running out? Raise it. Seasonal menu changes should trigger an immediate par review — not a reactive scramble when you run out.
Too high: Excess inventory sitting on shelves, higher spoilage rates, cash tied up in stock that doesn't turn fast enough. For perishables, this is waste you can see and smell.
Too low: Stockouts mid-service, frustrated staff, lost sales, inconsistent guest experience. For a cafe or restaurant, running out of a core ingredient on a Friday night isn't a minor inconvenience — it's a reputation issue.
No par levels at all: You're ordering on vibes, counting on memory, and hoping your managers care as much as you do. Some do. Most are just trying to get through the shift.
TrackItWeekly tracks your actual weekly usage in real time across all your locations. Once you set your initial par levels in the system, you can see at a glance which items are approaching par, which locations are burning through product faster than expected, and where you're consistently over-stocked.
Instead of reviewing par levels from memory or pulling spreadsheets, your weekly count gives you the data to make a confident decision: raise it, lower it, or leave it alone. Location by location. Item by item. Every week.
That's the difference between managing your inventory and just counting it.
Start your free 14-day trial at app.trackitweekly.com — no credit card required.