To find missing menu prices, start with the dishes and drinks your restaurant intends to price, then compare each one with what a guest can actually see on the live website. Flag an item if its description is visible but its price is absent, unreadable, or impossible to determine from the options presented.
Use an approved price list as the reference, not an old menu file or a staff member’s memory. Check the public menu and the ordering path separately: a price shown in one place may not be visible in the other. The goal is to catch accidental omissions while recognizing items that legitimately vary by size, portion, or availability.
1. List the items that should have a price
Gather the current approved menu, including drinks, specials, add-ons, and variants. Ask the person who approves prices to identify the source of truth and its effective date. That might be a manager’s spreadsheet, a current POS export, or another controlled list. The format matters less than knowing who can approve a correction.
Then make an inventory of the items guests can encounter online. Include the main menu page, downloadable menu if you offer one, specials pages, and the menu reached through an ordering button. Record section names and any item names that differ from the approved list. A breakfast sandwich called “Morning Roll” on the website may appear as “Egg Sandwich” in the internal list.
For each item, establish what a guest needs to know before choosing it:
- Fixed-price item: the approved amount and any included portion or standard preparation.
- Option-based item: the available sizes or choices and the price for each, or a clear base price plus each additional charge.
- Variable-price item: how the price is determined and how a guest can obtain the current amount.
- Non-priced content: a section heading, descriptive introduction, or item no longer offered, which should not be mistaken for a sellable dish.
Ask the kitchen or bar lead to confirm current portions and options. Ask the manager or owner to approve amounts. The person who edits the site should identify where each price is maintained and whether the public menu and ordering menu are edited separately. One person can fill several roles, but the approvals and edits should still be distinct steps.
Decide the audit’s scope before counting. If a seasonal menu is not currently offered, remove it from the active audit or mark it clearly for removal. Otherwise, an outdated page can create both false alarms and real guest confusion. Include an item if a guest can reasonably read it as available, even if it appears only in a promoted special or a PDF.
2. Compare the live menu with the approved source
Open the site as a guest would, without relying only on the editor’s preview. Work section by section and record the result for every sellable item. A useful audit records more than a yes-or-no answer: it shows where the issue appears, what the approved source says, and the next action.
The following is a hypothetical audit for a small cafe. Its prices and menu setup are assumptions, not Fleksa product claims. The table shows three different situations that should not receive the same fix.
| Item | Approved source | Live guest view | Action |
|---|---|---|---|
| Tomato soup | Cup $5; bowl $8 | Description only | Add both size prices and check that each label is visible. |
| Turkey sandwich | $12; cheese add-on $1 | $12 shown; cheese mentioned without an amount | Add the $1 charge or remove the unpriced option until approved. |
| Daily fish | Price varies; staff confirms current amount | “Market price” with no contact direction | Add a clear way to ask for today’s price; check the ordering path. |
The soup is missing all usable prices. The sandwich has a usable base price but an incomplete optional charge. If the guest chooses cheese, the assumed item total is $13: $12 plus $1. That example includes the sandwich and the selected add-on only; it excludes taxes, fees, and other items. The fish needs a clear route to the current price rather than a fabricated fixed amount.
Look for prices that exist but are not usable. Text may be cut off on a phone, displayed in a color that blends into the background, or attached to the wrong size. A price in an image may be too small to read. A downloadable menu may show an amount while the webpage omits it, or the reverse. Record each location separately so the editor knows which version to repair.
Also check what happens after a guest selects an item. Does the guest see the amount before committing to the order? If an option changes the price, is the change clear? For an item with a base price, confirm whether that price buys a complete standard item or whether a required choice adds more. A visible number is not enough if a guest cannot tell what it covers.
Prioritize items guests are likely to encounter immediately, such as popular dishes and the first page of the menu, then finish the full list. Do not treat a quick spot check as a complete audit. Count missing prices separately from incorrect prices and items requiring approval; those categories may need different owners.
3. Handle legitimate variable-price items clearly
Some items do not have one permanent amount. Seafood may change with availability, a catering platter may depend on guest count, and a steak may be priced by portion. That does not mean the menu should leave guests guessing about how to get an amount.
For a market-price dish, explain that the price varies and give guests a practical next step, such as calling the restaurant for the current price. For a catering item, describe the relevant choices and how to request a quote. If a price is stated per unit, identify the unit and make the portion clear enough for a guest to understand the basis of the charge.
Use “starting at” only when the displayed amount corresponds to an actual available choice. Explain which choice receives that price and show the charges for other choices where possible. A starting amount should not stand in for a required option whose price the guest cannot see. Similarly, “from $10” is not a substitute for listing sizes if all sizes are known and offered at fixed prices.
Consider a separate hypothetical catering example: an approved tray serves a stated group size and costs $45 for the standard filling; a premium filling adds $6. If both choices are available, show the $45 starting price and the $6 premium charge. The premium tray totals $51 before any separately stated taxes or fees. This item total includes the tray and selected filling; it excludes delivery and other services. If the restaurant instead quotes every order individually, direct the guest to request a quote rather than displaying an assumed amount.
For ordering, decide what should happen when a current price cannot be presented. Can the item be hidden from online ordering while remaining on an informational menu with a contact direction? Can staff update the amount before making it available? Ask your website or ordering provider how the setup works. Avoid presenting an item as orderable at an unknown amount and expecting staff to resolve the price after submission.
4. Correct the page and repeat the check
Turn the audit into a short fix list. For each issue, record the affected page or ordering view, approved wording and amount, person responsible, and review date. Keep the previous and corrected values in your internal record. That makes it easier to distinguish a missing-price repair from a deliberate price change.
Make corrections in the system that controls each guest view. If a website menu, PDF, and ordering menu are maintained separately, update each applicable version. If the same source feeds more than one view, still verify each destination after the update. Ask the provider how edits are published and how long changes normally take to appear; do not assume an editor preview is the live page.
- Have the price approver sign off on the fix list, especially options and variable-price wording.
- Publish the changes using the normal process, then open the public page in a fresh browser session.
- Check a phone and a larger screen. Open the relevant menu sections, PDF, and ordering path.
- Compare the live result with the approved list. Confirm the correct amount sits beside the correct item and option.
- Record the check date and resolve any remaining mismatch before marking the item complete.
A simulated check can stop at viewing item and option prices; it should not create a real payment, guest message, or courier dispatch. If you decide a live service pilot is needed, plan it separately with staff and the provider, including how any real order will be handled. A simulation alone does not prove that every part of a live transaction works.
Repeat the audit after a menu refresh, seasonal change, or website migration, and assign a routine owner between those events. A simple control is to require the approved price and option details whenever a new description is submitted for publication. Schedule a follow-up review of the live page rather than assuming the edit is complete when it is entered.
If updating several menus is taking too much time, ask who controls each version and how changes reach guests before replacing the whole site. The restaurant website builder comparison can help frame broader selection questions, while the domain ownership guide covers control of the address itself. For the ordering side, ask how your online ordering menu is maintained alongside the informational menu.
Use the checklist on one current menu section today, assign the remaining sections to an owner, and set a date to verify the fixes. If you are evaluating a new setup, ask Fleksa about its restaurant website and verified availability in your US location.
Frequently asked questions
Is a menu item missing a price if it says “market price”?
Not necessarily. A variable-price label can be appropriate, but guests still need a clear way to obtain the current amount. Check whether the item can be ordered online and how the price is presented before an order is submitted.
Should I audit a PDF menu as well as the website page?
Yes, if guests can access it. Compare both with the approved source and check the PDF on a phone. An outdated download can contradict a corrected webpage.
How often should I check for missing prices?
Check after menu changes and migrations, and assign a recurring review based on how often your offerings change. Confirm corrections on the live page, not just in the editing screen.
