QSR inventory management for single-store operators

"Inventory management" in restaurant-industry content usually means one of two things: either very basic "take a count once a week" advice aimed at someone who has never run inventory, or enterprise-grade recipe-costing systems that take two months to set up and require a full-time inventory manager.

There's a big gap in the middle: the single-store QSR operator who knows what they're doing, doesn't need to be told what PAR is, and doesn't have the budget or the headcount for Restaurant365. This article is for that person.

The actual job

The job, simplified to its core:

1. Not run out of things during a shift (don't 86)
2. Not sit on spoiling inventory (don't waste)
3. Not spend more than ~30 min/week on inventory work (don't burn ops time)

Everything else — recipe costing, variance analysis, food-cost-percent targets — is secondary. Useful if you have time, optional if you don't.

The minimum viable workflow

Every single-store QSR ultimately runs some variant of this:

1. Set PAR per inventory item. One number per item you count. See PAR fundamentals.
2. Count weekly. Same day, same time, same order each week. Takes 15–20 min for a 30-item count.
3. Order the gap. PAR - on_hand = shortfall. Round up to the next case. Submit to vendor.
4. Revisit PARs periodically. Every 4–6 weeks, or when sales shift.

That's it. The variations come in at each step — how you set PAR (gut feel vs math vs tool), how you count (clipboard vs app), how you order (phone vs portal vs EDI), how you revisit (memory vs sales data).

What QSR is different from

If you've read general "restaurant inventory" advice, a lot of it doesn't apply. QSR — quick-service restaurants — differs from full-service restaurants in ways that matter for inventory:

• Shorter shelf life on more items. QSR is usually higher-perishable: dough, bagels, pastries, dairy. Full-service can lean on frozen proteins, shelf-stable pantry items. Your PARs need to be tighter.
• Higher day-of-week variance. QSR traffic is strongly weekday vs weekend vs meal-period. Full-service averages out more. Your PARs need to account for the Saturday bump.
• Simpler menu. 30–80 items in QSR, often 150+ in full-service. You have fewer items to manage, which means the math is easier — but each miscalculation has bigger impact.
• Smaller ordering cadence. Many QSRs order multiple times a week. Full-service often does weekly. Your PAR formula uses different days of coverage.

If you read an inventory article and it talks about steakhouse meat aging or wine cellar PAR, you're in the wrong article for QSR work.

What scale you should use which tool at

Rough sizing guidance:

The mistake operators make: skipping the lightweight-tool tier and jumping from spreadsheet to MarketMan. You don't need MarketMan's feature set at 30 items. You need the PAR math done automatically and the count entry to be fast.

Categories of items to track

Not everything in your shop needs a PAR. Rough bucketing:

• Must-PAR: Perishables with daily/weekly impact. Dough, bagels, dairy, produce, prepared sauces. Count these every time.
• Should-PAR: Semi-perishables with monthly impact. Dry goods, coffee beans, packaging. Count less often (biweekly or monthly).
• Don't-bother-PAR: Things that rarely run out and have long shelf life. Sugar packets, stir sticks, receipt paper. Check quarterly, buy in bulk, forget about it.

Trying to PAR everything is a common beginner mistake. You spend your count time on items that never move and miss the ones that actually matter.

The once-a-week rhythm

Weekly counts work for the majority of single-store QSRs. A typical operator's week:

• Sunday night or Monday morning: Count. Before the week's first vendor delivery.
• Monday afternoon: Submit orders based on count + PAR.
• Tuesday–Friday: Deliveries come in, you receive and restock.
• Saturday–Sunday: Highest-volume days, test your PARs against reality.

If you're missing items consistently on Saturday afternoons, your PARs are too low. If you have a stack of unsold product on Sunday night, they're too high.

The recompute rhythm

Every 4–6 weeks, revisit your PARs. Signs your PARs have drifted:

• Running out. If an item went to zero mid-shift in the last two weeks, its PAR is too low.
• Throwing out. If you threw out more than ~2–3 of an item in a week, PAR is too high.
• Menu change. Any menu item added, removed, or recipe-changed in the last month requires a mapping update and a PAR recheck for affected inventory items.
• Seasonal shift. If you're entering a known busy or slow period, recheck in advance, not after the first week of short-counts.

What breaks QSR inventory systems

Where Par Inventory fits

Par Inventory is built for the single-store-to-small-multi-unit QSR operator who's in the 30–60 inventory-item range and counts weekly. It does the PAR math from your Toast sales data, handles the menu-item-to-inventory-item mapping, and gives you a clean count page for the weekly walk-through. It does not try to do recipe costing, food-cost-percent analysis, or vendor management — those are separate jobs that other tools handle.

The goal is: set it up once, recompute PARs when you want (weekly if you want — it's cheap), spend 20 minutes counting, submit your order. Not 2 hours of spreadsheet work.