Most restaurants discover cost overruns weeks too late while smart operators catch price spikes within hours. Your supplier quietly raises beef prices by 15%, but you won't know until month-end reports show your steak margins have collapsed. Automatic threshold alerts change this game completely.
Why automatic alerts matter for your bottom line
Your supplier bumps beef prices 15% on Tuesday. You're clueless. Four weeks later, your steak shows 38% food cost instead of the usual 32%. Damage done.
⚠️ Heads up:
Suppliers bump prices without fanfare all the time. Automatic alerts stop you from bleeding money for weeks while you're in the dark.
Setting the right warning thresholds
Smart restaurants monitor these critical limits:
- Food cost per dish: 35% (standard ceiling)
- Total food cost: 32% of revenue
- Ingredient price jumps: 10% above last week's cost
- Daily purchasing: 20% over your average
💡 Example:
Your signature steak runs 32% food cost normally. Set your alert at 35%.
- Menu price: €32.00 incl. VAT (€29.36 excl.)
- Current ingredient cost: €9.40
- Alert threshold: €10.28
Ingredient costs hit €10.29? You get notified instantly.
Four essential alert categories
Configure these warning types for complete coverage:
- Food cost threshold: Dish exceeds X% food cost
- Price spike: Ingredient jumps X% in cost
- Purchase variance: Daily spending deviates X% from normal
- Budget breach: Weekly purchases blow past budget
💡 Price spike example:
Salmon typically costs €18/kg. You've set a 15% spike threshold.
- Trigger point: €18 × 1.15 = €20.70/kg
- Supplier jumps to €22/kg
- Alert fires: "Salmon up 22% - action needed"
Now you can raise menu prices immediately or source elsewhere.
Alert timing strategies
Different situations need different response speeds:
- Instant alerts: Price jumps over 15%
- Daily summaries: Food cost threshold breaches
- Weekly reports: Purchase budget vs. actual
- Monthly trends: Overall food cost patterns
Turning alerts into action
Getting the alert is just step one. Here's what happens next:
💡 Your alert response playbook:
- Verify the numbers: Confirm the price change is real
- Shop alternatives: Check if competitors offer better rates
- Update pricing: Raise menu prices or tweak recipes
- Brief your staff: Ensure everyone knows about changes
⚠️ Heads up:
Too many alerts create noise fatigue - you'll start ignoring critical warnings. Stick to your 5 most expensive ingredients and you'll stay sane.
Manual tracking vs. automated systems
Manual monitoring eats time and you'll forget to do it consistently. A pattern we see repeatedly in restaurant financials shows that operators using automated systems catch cost overruns 3 weeks faster than those checking manually.
The payoff: you're not manually checking prices daily, but you still catch problems the moment they happen.
How do you set up threshold alerts? (step by step)
Determine your threshold values per dish
Calculate the current food cost of your 10 best-selling dishes. Set the threshold 3-5 percentage points higher than your current food cost. For example: current food cost 30%, threshold 35%.
Choose your alert times
Determine when you want which alerts: immediately for major price increases (>15%), daily for food cost overages, weekly for budget overages. Too many alerts cause alert fatigue.
Test and adjust after a week
Monitor your alerts for a week. Getting too many warnings? Raise the threshold. Too few? Lower the threshold. The goal is to only get truly important signals.
✨ Pro tip
Set a 15-minute alert response window during peak prep hours (9-11 AM weekdays) so price spikes get addressed before your next order goes out.
Calculate this yourself?
In the KitchenNmbrs app you can do this in just a few clicks. 7 days free, no credit card.
Was this article helpful?
Frequently asked questions
Should I set different thresholds for seasonal ingredients?
Absolutely. Asparagus might trigger at 25% food cost in May but 40% in October makes sense. Adjust your seasonal product thresholds quarterly based on market patterns.
How do I avoid alert fatigue with too many notifications?
Focus on ingredients that represent 70% of your food cost - usually 5-7 key items like proteins and premium vegetables. Set conservative thresholds initially, then tighten them as you get comfortable with the system.
What's the fastest way to respond when an alert fires?
Have your supplier contact list ready and know your backup sources. Call to verify the price change first, then immediately check two alternative suppliers before deciding whether to adjust menu prices or switch vendors.
📚 Sources consulted
- EU Verordening 852/2004 — Levensmiddelenhygiëne (2004) — Official source
- EU Verordening 853/2004 — Hygiënevoorschriften voor levensmiddelen van dierlijke oorsprong (2004) — Official source
- EU Verordening 1169/2011 — Voedselinformatie aan consumenten (2011) — Official source
- NVWA — Hygiënecode voor de horeca (2024) — Official source
- NVWA — Allergenen in voedsel (2024) — Official source
- Codex Alimentarius — International Food Standards (2024) — Official source
- FSA — Safer food, better business (HACCP) (2024) — Official source
- BVL — Lebensmittelhygiene (HACCP) (2024) — Official source
- Warenwetbesluit Bereiding en behandeling van levensmiddelen (2024) — Official source
- WHO — Foodborne diseases estimates (2024) — Official source
Food Standards Agency (FSA) — https://www.food.gov.uk
The HACCP standards shown in this application are for informational purposes only. KitchenNmbrs does not guarantee that displayed values are current or complete. Always consult the FSA or your local authority for the latest regulations.
Written by
Jeffrey Smit
Founder & CEO of KitchenNmbrs
Jeffrey Smit built KitchenNmbrs from 8 years of hands-on experience as kitchen manager at 1NUL8 Group in Rotterdam. His mission: give every restaurant owner control over food cost.
Automate your daily kitchen controls
Manual controls take time and miss errors. KitchenNmbrs automates temperature logging, inventory management, and HACCP checks. Try it free for 14 days.
Start free trial →