Every established menu has a few dishes that have outlived their reason for being there. They're not popular enough to be signatures and not unpopular enough to force an obvious cut. They stay because nobody has decided to remove them. That inertia has a cost that's easy to overlook, and it's worth taking a regular, honest look at which dishes have earned their place and which are only there out of habit.

The Hidden Cost of a Dish Nobody Orders

A slow-selling item still takes up resources:

  • Inventory: ingredients that have to stay in stock even if they're rarely used, and that often end up as waste
  • Prep and storage: mise en place that's made daily and thrown out half-used, plus space in a crowded walk-in
  • Consistency: cooks who make a dish twice a week are more likely to make it inconsistently than cooks who make it twenty times a night
  • Menu space: a line on the menu competing for the guest's attention with dishes you'd rather sell

None of these costs is dramatic alone. Across five or six slow items, they add up to real operational drag and a menu that's harder to navigate than it needs to be. Sometimes a single item creates most of the trouble, as we explore in the hidden menu item killing your kitchen's efficiency.

Use Data, Not Gut Feeling

Start with the numbers. Menu engineering sorts items into four groups based on two measures: popularity (how often it sells compared with the rest of its category) and profitability (how much contribution margin it earns per sale).

  • Stars: popular and profitable. Protect them, and feature them prominently.
  • Plowhorses: popular but low margin. Keep them, but look at portion size, recipe cost, or price.
  • Puzzles: profitable but rarely ordered. Try better placement, a new description, or a server recommendation before giving up on them.
  • Dogs: unpopular and low margin. These are the first candidates for removal.

Pull item-level sales from your POS for at least a full quarter, so one slow month or a weather-driven dip doesn't skew the result. Combine it with your recipe costing, then sort. Our free menu engineering tool can do the classification for you, and our guide to the art of menu engineering explains the method in detail.

Looking to Build Your Restaurant Management System?

EatlyPOS is a modern, responsive frontend template built with Next.js that provides a solid foundation for developing a complete restaurant management system. Visit our homepage to explore the interactive demo, check available licenses, and kickstart your development with a professional codebase.

Low-Volume Isn't Always Low-Value

Not every slow seller should go. Some dishes do a job that sales numbers don't capture:

  • The only substantial vegetarian or vegan main, which keeps a mixed group from choosing another restaurant
  • A gluten-free or allergy-friendly option that lets you say yes to guests with dietary needs
  • A dish that a small group of high-spending regulars orders every visit
  • An item that shares ingredients with best-sellers, so it adds almost no inventory or prep burden

The honest distinction is between a dish that sells slowly but plays a strategic role, and a dish that sells slowly because it never quite worked.

When deciding, weigh these factors together:

  • Sales data over at least a full quarter, not a single slow month
  • Strategic value, such as dietary coverage, menu balance, or a loyal niche following
  • Operational cost: a dish that's both slow-selling and hard to execute is the clearest candidate for removal
  • The kitchen's view, since cooks often know which dishes cause more trouble than they're worth

Prepare for the Guests Who Ask

Even a slow item usually has a few loyal fans, and someone will eventually ask what happened to it. Brief the floor team before the change, with a simple, honest explanation and a specific recommendation. "We retired the lamb shank to make room for the fall menu, but if you liked it, the braised short rib has a lot of the same flavors" works far better than an awkward apology from a server who didn't know the dish was gone.

For a true regular, consider letting them know ahead of time, or offering the dish as an occasional special. That small gesture often turns disappointment into loyalty.

Time Removals Around Natural Transitions

Removing items during a planned update, such as a seasonal menu change or a periodic reprint, feels more natural to staff and returning guests than a single unexplained cut from an otherwise unchanged menu. Bundling several removals into one update also gives the kitchen one transition to absorb instead of a series of disruptions throughout the year.

Make Menu Review a Regular Habit

The healthiest approach isn't a dramatic menu purge every few years. It's a calm, regular review, quarterly works well for most restaurants, so underperforming dishes are caught before they've been dragging on the kitchen for years. Menus reviewed this way stay tighter, more coherent, and easier for both the kitchen and guests to work with. And every dish that leaves makes room for one that can earn its place.