Your bestselling butternut squash ravioli suddenly tanks, and you're wondering if autumn's over or if something else is killing sales. Pull it too fast and you lose a winner. Keep it too long and you're bleeding money. Smart data tells you which scenario you're facing.
Why this distinction matters
Wrong calls drain cash. Axing popular dishes too fast kills revenue. But keeping flops around too long creates waste and crushes profitability.
? Example:
Your pumpkin soup moved 120 portions weekly in October. November hits—suddenly just 40 portions.
- Trend: Guests got tired of pumpkin
- Temporary: Competitor's running a pumpkin soup special
- Structural: Weather's warming up, soup demand's falling
Without numbers, you're guessing.
Data you need
Track these metrics over 4-6 weeks minimum:
- Weekly portion counts per dish
- Average spend per table (does removing pricey dishes hurt your check average?)
- Food cost percentage for each seasonal item
- Weekly revenue totals (are other dishes picking up the slack?)
- Guest feedback—complaints and praise
Spotting temporary dips
These patterns usually signal short-term issues:
? Example of temporary trouble:
Your game dishes drop from 80 to 30 portions weekly:
- Competitor launched a game festival
- Negative media coverage about game
- Supplier hiked prices, you raised menu prices
- New chef changed the preparation
These problems have solutions.
- Sharp drops (not gradual slides over weeks)
- Other menu items hold steady
- Total revenue stays flat (guests just order different dishes)
- Season still makes sense (pumpkin soup in October, not January)
- Clear external trigger (competition, media, pricing)
Recognizing structural shifts
These signals point to lasting demand changes:
? Example of structural change:
Your hearty winter dishes slowly fade:
- Week 1: 100 portions
- Week 3: 85 portions
- Week 5: 70 portions
- Week 7: 55 portions
Steady decline plus seasonal shift equals structural change.
- Steady weekly declines over multiple weeks
- Season's winding down (heavy dishes in March, soups in May)
- Multiple seasonal items declining together
- Guest requests for lighter fare
- Rising food costs as seasonal ingredients get expensive
The 3-week rule
Every dish deserves at least 3 weeks to prove itself. That timeframe reveals true performance patterns—something most kitchen managers discover too late after making hasty menu cuts based on one bad weekend.
⚠️ Watch out:
Don't pull dishes after one weak week. Guests need time discovering new options.
Week 1: Launch phase (weak sales expected)
Week 2: Trial period
Week 3: True popularity emerges
Week 4+: Trends become obvious
Your action plan
For temporary dips:
- Address root causes (pricing, prep methods, promotion)
- Wait another 2-3 weeks
- Push the dish harder (daily specials, social posts)
For structural changes:
- Line up replacement dishes
- Test new seasonal options
- Phase out gradually
- Burn through remaining inventory to cut waste
Digital tracking
Manual data collection eats up hours. Systems that automatically track per-dish sales and food cost trends help you catch patterns faster.
Related articles
How do you spot the difference? (step by step)
Collect 4 weeks of data
Note per dish: number sold, food cost %, customer reactions. Use your POS system or count manually.
Find the pattern
Sudden drop = probably temporary. Gradual drop over weeks = probably structural. Also pay attention to the season.
Test your theory
With temporary dip: fix the cause and give it 2 weeks. With structural change: prepare a replacement and gradually remove it.
✨ Pro tip
Compare each dish's current 3-week average against its historical 6-week performance from the same season last year. This eliminates weather and holiday fluctuations that throw off your judgment.
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 long should I wait before removing a struggling dish?
What if my entire seasonal menu bombs?
Should food cost factor into removal decisions?
Can I modify struggling dishes instead of removing them?
How do I avoid making hasty menu decisions?
What portion count drop signals real trouble?
Should I track competitor menus when making these decisions?
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
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.
kennisbank.more_in_category
Related questions
Explore more topics
Purchase smarter with real-time insights
Seasonal prices fluctuate — so do your recipe costs. KitchenNmbrs automatically recalculates your margins when purchase prices change. Never get surprised again. Start free.
Start free trial →