How to Set Restaurant Menu Prices: A Practical Framework

A recipe cost is a starting point, not a menu price

The supplier invoice is current, the recipe is standardized, and a fish plate costs €5.40 to prepare. That still does not tell you whether €16, €18, or €20 is the right price for the portion, the room, and the experience you offer.

Recipe costing tells you what goes into the plate. Pricing is the decision about what the operation needs each sale to contribute and what guests can understand as fair value. If you are setting up the broader system first, start with Digital Menu for Restaurants: How It Works, Benefits, and Why to Adopt It. For the recipe and yield calculations, see How to Calculate Food Cost for a Restaurant Menu. This guide focuses on turning a current cost into a price you can explain and review.

1. Start with the cost of the portion you actually serve

Before comparing prices, make sure the cost belongs to the dish guests receive today. Use the current recipe, standard portion, usable ingredient yields, sides, sauces, and garnish. If the kitchen serves different portions at lunch and dinner, or the delivery version includes different packaging, keep those versions distinct in your costing record.

For example, if a fish supplier changes the pack size or the kitchen trims more from each delivery, the previous cost per portion may no longer describe the plate. Update the recipe-cost record before using it as the basis for a price decision. A price review built on an old portion or yield can look precise while pointing in the wrong direction.

2. Build a financial baseline for your operation

A cost percentage can help you test a price, but it should come from your own operating plan rather than a number copied from another restaurant. Review expected sales alongside labor, occupancy, utilities, other operating costs, and the profit the business needs to plan for. That gives you a business-specific range to use when checking prices across the menu.

The Penn State chapter on menu and recipe pricing describes setting a baseline from projected sales, labor, overhead, and a profit goal. It also explains why applying a familiar percentage, such as 30%, by habit may not fit an individual operation. Treat a food-cost calculation as one reference point, not a rule that every item must meet on its own.

Some dishes may have a higher ingredient-cost share but bring guests in, complete a category, or make sense as a signature item. Other dishes may carry more contribution toward the rest of the business. The whole menu has to work together; a single target for every plate can hide that mix.

3. Check the value guests can see

Guests do not compare ingredient invoices. They see the portion, preparation, ingredients, service, setting, and convenience attached to the price. A lunch bowl served quickly at a counter and a carefully plated dinner in a full-service room are not the same offer, even if both contain chicken and rice.

Compare your price with similar choices in your area, but compare like with like: portion, sides, service model, quality, and what is included. A nearby restaurant's lower price is useful context, not an instruction to copy it. If your team regularly has to explain that bread, a side, or a size upgrade costs extra, make that information clear before the guest decides.

Penn State's pricing chapter discusses the relationship between price and value, including the effects of location, service, experience, portion, and menu mix. Use those factors to ask whether the price makes sense for the complete offer, not just the ingredients.

4. Set prices within a category, then review the menu mix

Look at a group of comparable items together: starters against starters, mains against mains, or cocktails against cocktails. Consider the category's price range and the role each item plays. A clear entry option, a familiar middle choice, and a higher-priced signature dish can help guests compare without making every item follow the same markup.

Then look beyond the percentage. If you have point-of-sale sales data, compare how many portions sell with the contribution each one leaves after its standard food cost. A dish with a lower food-cost percentage does not automatically contribute more cash per sale, and a high-contribution dish that rarely sells may need clearer wording or a different place in the category before a price cut.

The Penn State menu-analysis chapter recommends comparing similar items and considering both popularity and contribution. The restaurant menu engineering guide shows how to turn those signals into a practical keep, improve, feature, or retire decision. If you do not have reliable sales counts, start with the records you do have and ask the service team which questions or objections repeat; do not treat menu views as orders.

5. Check the economics of each service channel

The same dish may have different costs when it leaves the restaurant. Takeaway packaging, delivery-specific portions, condiments, and marketplace charges can change what remains from a sale. Use the costs in your own supplier invoices and platform agreement rather than a generic percentage.

For instance, a dine-in fish plate may include a shared side, while the delivery version uses a sealed container and a different accompaniment. Cost and review those as two offers. If the restaurant chooses different prices by channel, make sure each public menu and ordering path shows the correct one. If it keeps one price, check that the price still works for the service that costs more to fulfil.

For multiple locations, check local supplier prices, portions, and service conditions before assuming that one approved price fits every branch. A shared dish name does not guarantee the same cost or guest offer everywhere.

6. Test one decision and review it after service

Write down the current price, proposed price, reason for the change, effective date, and person responsible. If you can, change one meaningful variable at a time. Changing the price, portion, description, and category placement together makes it difficult to see what helped or hurt.

After the new price has been used through comparable services, review:

• portions sold and the contribution from those sales, if point-of-sale data is available;
• ingredient and portion costs against the current recipe;
• waste, substitutions, or stockouts that affected availability;
• repeated questions or price objections reported by the service team; and
• other changes, such as a promotion, holiday, or menu redesign, that affect the comparison.

One busy Saturday is not enough to prove that a price worked or failed. Compare a useful period with a similar one, note what else changed, and set the next review date. If guests are confused, the answer may be a clearer description or portion note rather than a lower price.

A short restaurant menu price review record

Keep the decision somewhere the person who costs the recipe and the person who publishes the menu can both find it:

Set the price, then keep it connected to the operation

A useful menu price starts with a current portion cost, then accounts for the restaurant's financial needs, the value guests receive, the role of the item in its category, and the cost of serving it through each channel. Review the result with real service information instead of assuming one formula settles every decision.

Once the team approves a price, update the guest-facing menu and any separate ordering channels before the change takes effect. Menuit helps restaurants keep menu prices, descriptions, and translations together in a live menu. Pair that publishing flexibility with current recipe costs and a review date so the price on a guest's phone matches the offer the kitchen is ready to serve.