Key takeaways
- Choose one source of truth for the menu, usually the POS, and push changes out from it rather than editing each app by hand.
- Make 86ing an item a two-minute job with a named owner per shift, and un-86 on a schedule so items do not stay hidden for days.
- Menu prices keep moving, with restaurant prices up 3.5% in the year to September 2026, so price changes need a written routine[1].
- Audit every channel weekly for price, availability, modifiers and allergen wording, using a short checklist.
What goes wrong when menus drift
Most restaurants now sell through several menus at once: the POS, the website, one or more delivery apps, a QR menu, a catering list and sometimes a kiosk. Each copy drifts a little every time someone changes one and forgets the others. The guest feels the drift as an item they cannot get, a price that does not match or a modifier that does not exist.
- An item sells out at 7 pm and keeps taking orders online until close, leading to refunds and angry calls.
- A price rise goes into the POS but not the website, so the restaurant loses margin on every online order until someone notices.
- A dish changes recipe but the app description still lists the old ingredients, which is a problem for guests with allergies.
- A seasonal special ends in the dining room but stays on an app for weeks.
- A modifier, such as “add avocado,” is free online because the online menu never got the new price.
The cost is real because prices are moving. Food-away-from-home prices were 3.5% higher in September 2026 than a year earlier, against forecast food-at-home inflation of 2.3% for 2026[1]. Some inputs move faster: beef and veal prices are forecast to rise 8.7% in 2026[2]. Every delayed update on a high-cost item comes straight out of margin.
Source: USDA Economic Research Service, 2026[1]
Show the data
| Item | Value |
|---|---|
| Food away from home, Sept 2026 | 3.5% |
| Food at home, 2026 forecast | 2.3% |
Pick one source of truth
The fix starts with a decision: where is the menu edited? Everything else follows from that.
| Approach | How it works | Fits when | Watch for |
|---|---|---|---|
| POS-led | Menu edited in the POS and pushed to website and apps through integrations | Your POS integrates directly with your ordering site and main apps | Apps without an integration still need manual updates |
| Menu management or aggregator tool | One tool holds the menu and pushes it to the POS, site and apps | You sell on several apps and your POS integrations are limited | Another system to pay for and train on |
| Manual with a master sheet | A master spreadsheet is the source; staff update each channel by hand | Small menu, one or two channels | Errors and delays; needs strict routines |
Whichever you choose, write it down and tell everyone: “The menu is changed in the POS, nowhere else.” If staff fix problems directly in an app tablet, the source of truth stops being true.
Make 86ing fast and owned
Sold-out items cause more online problems than prices, because they change minute by minute. The goal is that an item marked sold out on the line is unavailable everywhere within a couple of minutes.
Name the 86 owner per shift
Usually the expo or the kitchen manager. They are the only person who marks items out or back in.
Use one place to mark it
Mark the item out in the source of truth. If an app does not sync, mark it there as well, in a fixed order every time.
Shout it, then check it
Announce the 86 to the line and front of house, then check one online channel to confirm the item is hidden.
Handle modifiers too
If you run out of an ingredient, find every item and modifier that uses it. Out of avocado means the avocado add-on as well as the avocado toast.
Un-86 on a schedule
At the start of each shift, review what is still marked out and bring back anything that is available. Items left hidden for days cost sales.
Log repeat 86s
If the same item sells out every Friday, the fix is prep or par levels, not faster 86ing.
A price change routine
Price changes touch every channel and often several price levels. Run them as a short project, not a quick edit.
- Decide the new prices for each price level: dine-in, takeout and each delivery app.
- Update the source of truth once, with an effective date.
- Push to all channels, or update each manual channel from the master sheet.
- Check modifiers, combos and bundles, which often keep old prices.
- Place a test order on your website and each app and compare the receipt to the new prices.
- Update printed menus, menu boards and catering sheets on the same day.
- Tell staff what changed so phone quotes match.
Many operators keep separate app prices. 83% of limited-service and 66% of full-service operators charge more for items ordered through a third-party provider than for dine-in or takeout[3]. If you do, set app prices as their own price level in the POS rather than editing each app by hand, so a cost increase can be applied to every level at once.
Keep descriptions and allergen wording consistent
Descriptions drift more slowly than prices but matter more for safety. When FALCPA passed, the eight major allergens accounted for 90% of US food allergies and serious allergic reactions[4], and sesame became the ninth major allergen, with FDA requirements applying from January 1, 2023[5]. Guests with allergies read online descriptions closely.
- Keep one approved description for each dish in the source of truth and copy it to every channel.
- When a recipe changes, update the description the same day, especially if an allergen is added or removed.
- Use the same allergy wording everywhere, such as “Contains sesame and wheat,” and the same note about cross-contact if you use one.
- Do not promise “allergen-free” online unless your kitchen can guarantee it.
Chains have extra rules. FDA menu labeling requirements apply to restaurants that are part of a chain with 20 or more locations[6], and covered chains must show the 2,000-calorie daily nutrition statement and a statement that written nutrition information is available on request[7]. If you are covered, calorie information on online menus must stay in line with recipe changes too.
Hours, holidays and pausing the whole menu
Store hours are part of the menu. A website that says you are open while the kitchen is closed is the same problem as an item that sold out but still shows online.
- Keep regular hours, kitchen-close time and online ordering cutoff as separate settings. Online ordering often needs to stop 15 to 30 minutes before the kitchen closes.
- Enter holiday hours and closures in the source of truth at least two weeks ahead, then check each channel and your map listings.
- When you pause online ordering during a rush, use timed pauses where the platform offers them so ordering comes back on its own.
- If the kitchen closes early for weather, staffing or equipment, switch off every channel in the same order you use for 86s, and update the phone greeting.
- After any unplanned closure, check the next morning that every channel is open again.
The weekly menu audit
Fifteen minutes a week catches most drift. Assign it to one person and keep the checklist short.
- Pick five items at random, plus your three best sellers, and compare their prices on the POS, website and each app.
- Check that every item marked out in the POS is unavailable online, and that nothing available is hidden.
- Open two items with modifiers on each channel and check modifier names and prices.
- Read the description of any dish that changed this month on every channel.
- Check that specials that ended are gone everywhere.
- Note any differences and fix them in the source of truth, not in the app.
Once a month, add photos, store hours, holiday hours and pickup instructions to the audit.
Example: one source of truth in a two-app restaurant
Example: a fictional ramen shop sells through its own website and two delivery apps. One app syncs with the POS; the other does not. After a weekend where the pork broth sold out at 8 pm and the second app kept taking orders until 10, the owner sets new rules.
The POS becomes the source of truth. The expo is the 86 owner and has a laminated card listing exactly where to mark items out on the second app's tablet. Price changes happen on the first Monday of each month, with a test order placed on every channel afterwards. The weekly audit takes the assistant manager about fifteen minutes on Tuesday afternoon.
Within a month, refunds for unavailable items fall away and the owner finds two modifiers that had been free online since the last price change. If your tablets are the main problem, see taming tablet chaos from multiple delivery apps, and for setting app price levels, see how to price menu items on delivery apps.
Frequently asked questions
How do I 86 an item on all delivery apps at once?
Use a POS integration or menu management tool that pushes availability to each app. Without one, keep a written list of where to mark the item sold out in each tablet and portal, and have one person do it in a set order.
Should prices on delivery apps match my in-store prices?
That is your choice and depends on your platform agreements. Most operators charge more on third-party apps than for dine-in or takeout. If you do, manage app prices as a separate price level in your POS so changes stay consistent.
How often should I audit my online menus?
Weekly for prices and availability, and after every menu change. Do a deeper check of photos, descriptions, modifiers and allergen notes once a month.
What is a menu source of truth?
The one system where the menu is edited, usually the POS or a menu management tool. Every other channel receives changes from it, so a price or sold-out item is changed once and appears everywhere.
References
USDA Economic Research Service (2026). Food Price Outlook - Summary Findings (opens in a new tab) ↑
USDA Economic Research Service (2026). Food Price Outlook - Summary Findings (opens in a new tab) ↑
National Restaurant Association (2026). National Restaurant Association comments to the FTC on the Food Delivery Fees ANPRM (Project No. P267101) (opens in a new tab) ↑
US Food and Drug Administration (2004). Food Allergies (opens in a new tab) ↑
US Food and Drug Administration (2023). Food Allergies (opens in a new tab) ↑
US Food and Drug Administration (2026). Menu Labeling Requirements (opens in a new tab) ↑
US Food and Drug Administration (2026). Menu Labeling Requirements (opens in a new tab) ↑