1. The Question
“How can I automate inventory management in a restaurant—and reduce food waste?”
This sounds like a software problem. In reality, it’s a business model problem.
2. Why Inventory Management Is So Hard in Restaurants
At the core, there’s one unavoidable fact: Demand is unpredictable. Unlike car manufacturing (Toyota) or e-commerce (Amazon), restaurants can’t reliably forecast demand with data or AI. One night, you get a sudden rush. The next, the room is empty. That volatility hits cash flow directly—and quickly turns into a survival issue. This is why inventory management isn’t just about efficiency. It’s a lifeline. To reduce uncertainty, restaurants must do one of two things: Attract steady daily traffic (dopamine-driven stores), or Build a strong base of repeat customers (endorphin-driven stores)
(1) Inventory Is Not Just a Kitchen Problem
Back-of-house (kitchen) and front-of-house (servers) must work together. You need to:
- Promote slow-moving items
- Temporarily stop selling fast-moving ones
- Level menu rotation intentionally
During recessions, I even paused low-hop beers that go stale quickly and sold only high-hop beers to ensure faster turnover. (Note: High hop beers have a long-lasting flavor.) Once your store concept is clear and menu rotation is balanced, inventory complexity—and waste—drops naturally.
3. Why Restaurant Inventory Becomes Complicated ?
(1) Menu Type: How Dependent Are You on Freshness?
Some dishes are built entirely on freshness:
- Sushi
- Carpaccio
- Steak tartare
- Vongole pasta
These dishes share five traits:
- Low salt → weak preservation
- Low heat → minimal sterilization
- Low acid → higher pH risk
- Low aging → no fermentation buffer
- Low physical processing (raw cutting/slicing)→ more free water, faster spoilage
When a dish has all five “lows,” it highlights pure ingredient flavor—but inventory risk skyrockets.
Low-Dependency Dishes Are Different
Stews, cutlets, and Bolognese work the opposite way. They are:
- High in heat
- Often higher in salt or acidity
- Processed through cooking, crushing, or long simmering
- Compatible with frozen meat and processed vegetables
These are low-dependency dishes. And they are far easier to control. Example:
- Hard mode:
- Vongole (fresh clams, odor risk)
- Aglio e Olio (fresh parsley, garlic timing)
- Easy mode:
- Bolognese
- Lasagna (frozen minced meat + cooked sauces = long shelf life)
(2) Customization Demands
Popular menus invite customization:
- Burgers
- Sandwiches
- Pizza
- Salads
Customization explodes inventory complexity. Every topping multiplies SKU combinations,
making restocking unpredictable. Less familiar cuisines avoid this problem:
- Omakase
- French fine dining
- Traditional Korean food
Customers don’t customize what they don’t fully understand.
Pro tip: Instead of endless sandwich combinations, offer three fixed presets and allow only dressing choices. Sauces last longer. Ingredients stay under control.
(3) Number of Menu Items
More menu items = more SKUs. That’s unavoidable in pubs and gastropubs. The solution isn’t shrinking the menu—it’s designing smarter menus. To stay in control:
- Favor dishes with long shelf life
- Avoid combining menu diversity with freshness-heavy items
My store runs a multi-item menu while keeping fresh-ingredient dependency low.
Result: Food cost stays under 15%, even with a wide selection.
(4) Cooking Method: Instant vs. Heat-to-Serve
Instant-Cooked Dishes
Examples: Pasta, BBQ, Sashimi. These dishes depend heavily on fresh ingredients. That increases inventory volatility and spoilage risk. Fast to cook. Hard to manage.
Heat-to-Serve Dishes
Examples: German stews, Braised meats, Slow-cooked sauces. They require longer preparation upfront, but once cooked, volatility drops sharply.
These dishes allow:
- Batch preparation
- Refrigerated storage
- Minimal last-minute waste
Take Svíčková (Czech national dish) as an example. It involves:
- High salt
- High acidity
- High temperature
- Aging
- Heavy physical transformation
Because of this, there is no meaningful taste difference between refrigerated or frozen beef. Once prepared:
- The dish is refrigerated and aged
- Served later as heat-to-serve
- Inventory complexity is almost zero
| Cooking Method | Customer Satisfaction | Inventory Volatility | Waste Risk |
|---|---|---|---|
| Instant Cook | High | High | High |
| Heat-to-Serve | High | Low | Low |
4. Real-World Inventory Control Strategy
To manage inventory effectively, separate everything into Flow and Stock.
- Flow: What changes daily (sales, production, disposal)
- Stock: What remains (raw ingredients, prepared batches)
You can manage this with a whiteboard or Excel.
(1) Prep Batch Table (Example)
| Menu | Batch # | Initial Qty | Safety Qty | Production Date | Shelf Life (days) | Expiry Date | Remaining Qty |
|---|---|---|---|---|---|---|---|
| Goulash | 1 | 10 | 6 | 06/01 | 5 | 06/06 | 9 |
| Chicken | 2 | 3 | 1 | 06/01 | 2 | 06/03 | 1 |
How to read this:
- If you sold 1 Goulash and 2 Chicken today: Remaining Qty becomes 9 (Goulash) and 1 (Chicken)
- Goulash:
- 5 days left before expiry
- Remaining Qty (9) > Safety Qty (6) → No prep needed
- Chicken: Remaining Qty equals Safety Qty → Prepare a new batch
(2) Raw Ingredient Table (Example)
| Ingredient | Initial Stock (g) | Safety Stock (g) |
|---|---|---|
| Onion | 10,000 | 8,000 |
| Chicken Thigh | 8,000 | 5,000 |
Check every 2–3 days and restock as needed.
(3) Do You Need Software?
For small restaurants, no. Recording daily flow on a memory or whiteboard is enough. Honestly, I memorized most of it. The key is not the tool. It’s understanding:
- Flow vs. Stock
- Safety stock thresholds
Once you grasp that, sales, production, and inventory integrate naturally. If you want automation later:
- Airtable
- Google Sheets
Both work fine.
5. Summary
- Reduce freshness-reliant dishes: Low salt, heat, acid, aging, and processing → inventory becomes fragile
- Limit customer customization: especially for popular foods. The more customers “understand” the menu, the more customization they demand. 3~5 option is enough.
- Use heat-to-serve menus to stabilize volatility: Instant cooking is fast, but freshness makes inventory hard to control
- Separate Flow and Stock: Track production, sales, and remaining inventory clearly
- Keep it simple: For small pubs, a whiteboard is enough. Automate later with Sheets or Airtable if needed