Online ordering chaos. What to look for when third-party delivery and your in-house menu drift
4 MIN READ · 866 words
If you sell through your own site plus two third-party platforms, you are running three menus. Three menus that started identical and slowly diverge every week as someone adjusts a price, adds a special, or 86s a topping. The drift costs operators real money in refunds, comped meals, and one-star reviews.
- The drift is silent. Nobody sends an alert when a third-party menu falls out of sync.
- Five things go wrong most often: prices, modifiers, hours, prep times, and 86 lists.
- A 20 minute weekly reconciliation routine catches 80 percent of the issues. A daily automated snapshot catches the rest.
- Most operators recover one to three percent of net revenue inside 90 days of starting this practice.
Restaurant Dive has covered the platform-fee tension between independents and the major delivery apps for years. The cost number that gets the most ink is commission. The cost that gets less attention, and is arguably bigger over a year, is refund leakage and review damage caused by menu mismatches. Almost none of those mismatches are intentional. They happen because the operator updates the in-house menu, forgets the platform, and never gets a notification.
This article is the operational checklist we use when we audit a restaurant's online ordering footprint. Print it, run it once a week, and you will catch most of the bleeding.
1. Price drift
Open each platform's menu side by side with your point of sale menu. Look for items where the price differs by more than what you would expect from the platform markup. Common pattern: you raised the in-house price three months ago and the platform menu still shows the old price, so a guest orders, pays the old price, and you eat the difference. Or worse, the platform price is higher than your stated cap and a guest leaves a one-star review about the markup.
What to fix this week: reconcile every item over $12 and every modifier. The under-$12 items rarely move the needle individually but should be audited monthly.
2. Modifier groups
This is the silent killer. You added a new sauce option last month. The base item carries it. The platform menu does not. Or, you removed a topping in-house when supply got tight, and the platform still lets a guest order it. The kitchen makes the call: substitute (creates a guest complaint) or refund (creates a chargeback and lost food cost).
What to fix this week: for every menu item that has modifier choices, confirm the modifier group on each platform matches the in-house version exactly. If a modifier was deleted in-house, delete it everywhere.
3. Posted hours
Holiday hours, special events, and weather closures rarely propagate to every platform. The most expensive version of this is when the platform shows you as open during a closure, accepts orders, and then refunds them an hour later. The guest sees you as the source of the problem.
What to fix this week: open each platform manager app and confirm hours for the next two weeks. Add holiday hours one month in advance.
4. Prep time settings
Most platforms estimate delivery time using your stated prep time. Set it too low and orders show up cold because the driver waited. Set it too high and you lose the order to a competitor showing 25 minutes when you show 45. The sweet spot moves with day-part and weather.
What to fix this week: review your last 30 ticket times by day-part. Update each platform's prep-time setting to match your actual median, not your wishful average.
5. 86 lists
The 86 list is the running list of items you are out of for the day. It lives on a sticky note next to the line, in three managers' heads, and almost never on the platforms. Every order for an 86d item is a refund.
What to fix this week: create a single source of truth (a shared note, a Slack channel, a whiteboard photographed twice a day) and assign one person per shift to push 86 changes to every platform within 15 minutes.
The 20 minute weekly routine
- Print or pull up your in-house menu.
- Open each platform's manager view.
- Spot-check the top 15 items by sales volume for price and modifiers (5 minutes per platform).
- Confirm hours for the next two weeks (2 minutes per platform).
- Update prep-time settings if you changed staffing or volume (1 minute per platform).
- Update 86 list if anything is out long-term.
Twenty minutes once a week. Less time than one customer service call about a missing modifier.
Where AI helps and where it does not
This kind of reconciliation is one of the cleanest fits for an automated daily snapshot. The work is structured (compare two menus and flag differences). It is repetitive (every day, every platform). And the value of catching a discrepancy on Tuesday morning instead of Saturday night is enormous.
What AI does not do well here is the negotiation with the platform when something gets refunded incorrectly. That stays human. But the front-end detection and the daily summary save most of the operator time.
We cover this exact workflow in the audit. If you want a snapshot of where your menus currently disagree, that comes out of the first call.
See where your menus disagree.
The free Tableside AI Stack Audit includes a same-week reconciliation across your platforms. We tell you which items are losing money silently.
Schedule a fit callSources: Restaurant Dive coverage of third-party delivery economics; Modern Restaurant Management (MRM) reporting on refund and chargeback trends; National Restaurant Association technology surveys; RSPA member education on omnichannel POS reconciliation. Platform names omitted intentionally.