How to Price a New Dish Without Guessing

A new dish usually gets priced in the last twenty minutes before it goes on the menu, often by whoever is standing closest to the POS system when someone asks what number to type in. That is not a knock on any one owner. Pricing feels like it should be simple, cost plus margin plus a bit of intuition, and most of the time nobody sits down to actually work through it properly.

Start with the real cost, not the rough one

The first step nobody skips on paper but plenty skip in practice is calculating true food cost down to the garnish. Not just the protein and the headline ingredient, but the oil, the herbs, the sauce components, the side that comes with it. A dish that looks like it costs 90 to make often actually costs 115 once every component is counted, and that 25 gap, multiplied across hundreds of orders a month, is real money quietly leaking out of a margin that looked fine on a napkin calculation.

Compare against the category, not just the cost

Cost plus a target margin gives you a number, but that number still has to make sense sitting next to everything else in its category. A new pasta dish priced well above every other pasta on the menu needs a clear reason, a premium ingredient, a more involved technique, or it will simply look overpriced regardless of what it actually costs to make. Look at where the new dish would land relative to its neighbors before finalizing anything.

• Calculate full cost including garnish, sauce, and sides, not just the headline ingredient
• Set a target margin consistent with similar dishes in the same category
• Check where the price lands relative to its immediate neighbors on the menu
• Launch at that price but plan to revisit it after real order data comes in

Watch what similar restaurants near you actually charge, not what they advertise

It helps to check what comparable restaurants in your area charge for something close to your new dish, but do this carefully. A competitor's printed price doesn't tell you whether that dish is actually selling well for them or quietly struggling at that price point. Use competitor pricing as one data point among several, a sanity check on whether your number is wildly out of step with the market, not as the primary basis for your decision. The restaurant down the street might be pricing a similar dish badly too.

It also helps to note down your reasoning at the time you set the price, even a single sentence: priced at the top of the category because of the imported cheese, or priced low deliberately to build volume early. Six months later, when you're deciding whether to adjust it, that note tells you whether the original logic still holds or whether circumstances, ingredient cost, competitor pricing, guest reaction, have shifted enough to revisit the number.

Treat the launch price as a first draft

The number you land on before a dish has ever been ordered is an educated guess, however careful the math behind it. The only way to know if it's right is to watch what happens once real guests are paying it. If the dish sells briskly and guests report it back favorably, the price was probably fine, maybe even a little low. If it sells rarely and the few guests who do order it seem satisfied, the problem is more likely the price than the dish itself. That distinction matters enormously, because dropping the price fixes one problem and doing nothing fixes neither.

Most restaurants never make this second pass, because getting a clean read on guest reaction to a specific price point used to require surveys nobody fills out or a POS report that only shows volume, not sentiment.

TasteGraph closes that gap by collecting a quick reaction from guests right after each dish, so a new item's real performance, not just its sales count but whether guests actually liked what they got for the price, shows up in your dashboard within days of launch instead of after a full quarter of quiet underperformance.