Start with the dish's portion cost, labor reality, and the price a guest can understand, then compare the finished menu to nearby restaurants. A price is useful when it covers its own work and makes the next operating decision clearer.
- Write down the dish as sold today. Include the portion, garnish, sauce, packaging when relevant, and the actual selling price. Do not use a remembered recipe. If the dish changes by shift, write down both versions and choose the version guests most often receive.
- Cost the ingredients using the invoice or current supplier list. Record the usable quantity, not only the package price. Trim loss, yield, and substitutions matter. If a supplier price is uncertain, mark the input as an estimate and revisit it after the next delivery.
- Add the work that the dish creates. Prep, pickup, plating, cleanup, and packaging can all take time. You do not need a perfect labor model to make a better decision. A dish that looks cheap on paper but consumes the line can be priced or redesigned before it becomes a recurring problem.
- Separate contribution from popularity. A high-volume item can still deserve a change if it leaves too little after its direct work. A quiet item can still earn its place if it is profitable, distinctive, and easy for the team to execute. Keep those questions separate so a busy item does not hide a weak return.
- Compare like with like. Look at nearby restaurants serving a similar portion, service style, and occasion. Public menus are evidence of displayed prices, not proof of their costs or sales. Save the menu URL and access date. Avoid copying a competitor's price when the guest promise is different.
- Check the guest's reading speed. A short menu description, a clear portion cue, and one reason to order can make a price easier to evaluate. Do not bury a price change inside a description. If the dish needs a long explanation to seem reasonable, test the dish or the portion before raising the number.
- Choose a small test. Change one item, channel, or service period and decide what you will watch: orders, contribution, substitutions, waste, and guest questions. Keep the test long enough to include normal variation, and write down the start date so a later decision has a record.
- Review the result with the team. If the price worked, document the reason and update the recipe or menu. If it did not, ask whether the issue was value, visibility, execution, or demand. spotr can collect the public signals and draft the call, but the owner decides what the restaurant should do.
Sources
- Texas Comptroller mixed beverage receipts (accessed 2026-10-14)
- Austin open data portal (accessed 2026-10-14)