How to Tell If a Dish Is Failing Because of Price or Recipe

A dish that isn't performing well presents owners with two very different possible diagnoses that, from the outside, can look almost identical: either it's priced wrong, or something about the recipe itself isn't landing with guests. Treating a recipe problem as a pricing problem wastes a price cut that won't fix anything. Treating a pricing problem as a recipe problem sends a perfectly good dish through an unnecessary and possibly damaging rework.

The tell that separates the two

The signal that distinguishes them is what happens among the guests who actually order the dish despite its low volume. If those guests report liking it, genuinely enjoying what they got, but the dish still isn't ordered often, the barrier is more likely upstream of the eating experience: price, description, or placement discouraging people from trying it in the first place. If the guests who do order it come away unimpressed, the barrier is the dish itself, and no amount of repricing or repositioning will fix a recipe problem.

This distinction only becomes visible when you're tracking satisfaction separately from order volume. Looking at sales data alone, both scenarios look identical: a dish that doesn't sell much. It's only once you add the satisfaction layer that the two diverge into clearly different problems requiring clearly different fixes.

A simple diagnostic checklist

• Low orders, high satisfaction among those who tried it: likely a price, placement, or description issue
• Low orders, low satisfaction: likely a recipe or execution issue worth reviewing with the kitchen
• Check whether the price sits noticeably above similar dishes in the same category without an obvious justification
• Check whether the description or name undersells what the dish actually is

Why guessing wrong here is expensive

Cutting the price on a dish that's actually a recipe problem doesn't just fail to help, it can actively hurt. A cheaper price brings in more guests to try a dish that's going to disappoint them, which multiplies the number of people forming a negative impression rather than limiting it. On the flip side, sending a perfectly good dish through a recipe overhaul because you assumed it was a quality problem wastes kitchen time and risks changing something guests already liked, all to fix a problem that was never actually there.

Getting this diagnosis right the first time saves both the wasted effort and the risk of making a working dish worse while trying to fix a problem it doesn't have, and it keeps the kitchen's attention on the dishes that genuinely need a recipe review.

A third possibility worth ruling out

Price and recipe aren't the only two explanations, though they're the two most common ones. Sometimes a dish is failing simply because guests don't understand what it is from the name and description alone, which shows up looking identical to a pricing problem: low orders, high satisfaction among those who tried it. The way to tell these apart is checking whether the price sits reasonably in line with similar dishes. If it does, and satisfaction is strong among people who order it, the issue is very likely visibility or description rather than price itself, and a menu rewrite is a cheaper first move than a price cut.

How long to wait before concluding a fix worked

Whichever fix you choose, give it real time before judging the outcome. A price change or a description rewrite needs at least a few weeks of order data to separate a genuine shift from ordinary week-to-week noise. Checking after just a few days risks either declaring victory on a lucky week or abandoning a fix that simply hadn't had time to show up in the numbers yet.

TasteGraph's dashboard separates order volume from like rate for every dish, which makes this exact diagnosis straightforward: a dish flagged for low orders but strong reaction points toward a pricing or visibility fix, while one flagged for low orders and weak reaction points the kitchen toward the recipe itself.