Picture this: you're ordering ingredients based on last week's reservations, but half your guests order something completely different. Historical portion data shows exactly what people actually ordered, not what you hoped they'd order. And that difference can save you serious money on waste.
Why historical data beats educated guessing
Most kitchen managers order based on reservations or gut instinct. But guests don't follow your script - they order fish instead of steak, skip appetizers, or show up without booking. Historical data reveals what really moves through your kitchen.
💡 Example:
Restaurant De Smaak assumed they'd sell 40 steaks every Friday. Their sales data revealed:
- Past 8 Fridays: average 32 steaks sold
- Orders placed for 40 portions weekly
- Weekly waste: 8 × €18 = €144 per Friday
Annual savings potential: €144 × 50 weeks = €7,200
Essential data points you need
Three data types will transform your purchasing accuracy:
- Dish-specific sales: Exact portions sold per menu item
- Day patterns: Monday vs Saturday volumes, holiday fluctuations
- Seasonal shifts: Summer salad spikes, winter soup surges
Your POS captures this information, but consistent tracking and analysis makes the difference. Most operators ignore this goldmine sitting in their systems.
Building reliable purchasing averages
Basic math works: total portions sold divided by weeks tracked. But smart refinements separate profitable kitchens from wasteful ones.
💡 Example calculation:
Salmon portions over 6 recent Saturdays:
- Week 1: 28 portions
- Week 2: 32 portions (sunny weather)
- Week 3: 24 portions (heavy rain)
- Week 4: 30 portions
- Week 5: 26 portions
- Week 6: 34 portions (local festival)
Weekly average: (28+32+24+30+26+34) ÷ 6 = 29 portions per Saturday
Spotting and handling outliers
Some days break all patterns. Local events, extreme weather, holidays create sales spikes or drops that skew your averages. Smart operators separate these anomalies from normal planning.
⚠️ Watch out:
Don't blindly average everything. If you sold 20, 22, 45, 21 portions across four Saturdays, that 45 was likely an exception. Plan for 21 portions, not the inflated average of 27.
This mistake costs the average restaurant EUR 200-400 per month in over-ordering popular items after one unusually busy night.
Converting portions to purchase quantities
Knowing portion demand is just step one. Converting to actual purchase amounts requires factoring in:
- Portion weights: Grams per plated serving
- Prep losses: Whole fish yields 55-60% fillet
- Buffer stock: 10-15% cushion for unexpected demand
💡 Example calculation:
29 salmon portions needed Saturday:
- Plated portion: 180 grams fillet
- Total fillet needed: 29 × 180g = 5.22 kg
- Whole fish yield: 55%
- Whole salmon required: 5.22 ÷ 0.55 = 9.5 kg
- Safety buffer 15%: 9.5 × 1.15 = 10.9 kg
Final order: 11 kg whole salmon
Tracking seasonal eating patterns
Guest preferences shift dramatically between seasons. Winter brings requests for hearty stews and warming soups. Summer drives demand toward fresh fish and crisp salads.
- Cold months: Braised meats, root vegetables, comfort foods
- Warm months: Seafood, raw preparations, lighter proteins
- Holiday periods: Traditional dishes often outsell regular menu items
Compare your January sales against July data. The patterns will surprise you and inform smarter purchasing decisions.
Technology that simplifies data analysis
Your POS collects sales information but rarely makes analysis simple. You need systems that:
- Calculate day-specific averages automatically
- Identify seasonal trends over time
- Transform portion counts into purchase weights
- Factor prep losses and safety margins
Tools like KitchenNmbrs automate these calculations using your existing recipes and historical sales patterns.
How do you use historical data for purchasing planning? (step by step)
Gather your sales data from the past 6-8 weeks
Pull from your POS system how many portions of each dish you sold per day. Start with your 5 best-selling dishes. Also note any special circumstances like holidays or events.
Calculate averages per day type
Break down your data by day of the week. Calculate for each day (Monday through Sunday) the average number of portions per dish. Leave outliers (like holidays) out of the calculation.
Calculate back to purchasing quantities
Multiply the expected number of portions by your portion size. Account for trimming loss (divide by yield percentage). Add 10-15% safety margin for unexpected rush.
✨ Pro tip
Review your 6 highest-cost ingredients from the past 8 weeks - identify which ones show consistent over-ordering patterns. Reducing waste on just these items typically recovers your analysis time investment within the first month.
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
How many weeks of data do I need for reliable averages?
Start with 6 weeks minimum, but 8-10 weeks gives you better accuracy. For seasonal items, you'll need data from the same period last year to spot reliable patterns.
What if my POS system doesn't track detailed sales data?
Begin manually tracking your 5 highest-cost dishes. Count portions leaving the kitchen daily. Six weeks of manual data will give you actionable purchasing insights.
How do I handle new dishes without historical data?
Estimate conservatively using similar existing dishes as benchmarks. Order small quantities initially, then adjust after 2-3 weeks based on actual performance.
📚 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.
Standardize portions, stabilize margins
Varying portions mean varying costs. KitchenNmbrs records exact quantities per recipe so every plate costs the same. Try it free for 14 days.
Start free trial →