Delivery App Menus vs. Your Website: Stop the Drift

Say you change a dish before a busy weekend. Someone updates the point of sale, or POS. Someone else swaps the website menu. A third person edits each delivery app. Did all three describe the same dish, the same portion and the same choices? Did anyone check the photo?

Our approach is to stop treating each menu as its own decision. Make the POS menu your approved starting point, connect the places your setup supports, and give one person the job of checking everything else. That is a way to manage the work. It is not a claim that every POS updates every website and delivery app on its own.

Price mismatches have their own article, linked below. This one is about the rest of the menu: dishes, extras, photos and sold-out items.

How do menus drift apart?

Start by tracing where each menu gets its information. Is your website connected to the POS, or does someone paste in text? Does the delivery menu come from the POS, an integration provider or a separate merchant dashboard?

Wherever the route is manual, each change needs a person. Connected systems need attention too. DoorDash lists missing items, outdated pricing and incorrect availability among the signs that a POS integration needs work. A connected account is not proof the menu is correct.

Photos deserve their own check. On Uber Eats, a saved menu photo has to be submitted for approval, and Uber either approves it or asks for a new one. An uploaded picture is not live until you see it.

Different images can also travel different routes. Grubhub's documentation for its Deliverect connection says item images can be sent through Deliverect, while search and store header images are not handled through the integration and Grubhub has to update them. That is one example. Ask your own provider how your setup works.

What does a mismatch cost?

Imagine a side dish was removed from a combo, but an old description still lists it. A customer expects it in the bag. Your staff now has a complaint to settle, even though the kitchen made the current recipe correctly.

That can mean time spent explaining, a replacement or a refund, and sometimes an unhappy review. We would not put a dollar figure on it. Track your own complaints and corrections for a month and you will see what it costs you.

When you look into a complaint, compare what the customer saw with what the kitchen received. Keep delivery delays, packing mistakes and menu text separate. Otherwise you may fix a field that was already right.

How do I make the POS the starting point?

Name one person who can approve the master menu. Before a change goes out, that person confirms the item name, description, portion, extras, base price and availability.

Keep the record tied to the POS item. For things the POS cannot hold, such as the current photo, keep a companion note linked to that item. Do not start a second, independent menu.

For each dish, be able to answer:

• What exactly does the customer receive?
• Which choices are required and which are optional?
• Which extras cost more?
• Which photo shows the current portion?
• Which channels carry this item?
• Who approves a permanent change?

If you price a channel differently on purpose, or offer a smaller delivery menu, write that rule in the same record. Confirm what your provider supports, and do not overwrite a deliberate difference during a cleanup.

What does a repeatable change routine look like?

• Approve the change against what the kitchen will actually serve.
• Update the master through the POS and any companion notes.
• Send it through the connections you have, then do the manual ones.
• Open each destination as a customer would and check the item, extras and photo.
• Write down what is live, what is pending and what still needs a fix.

Plan the update earlier in the day, not minutes before service. For sold-out items, agree with your provider on the supported control, test it, and decide who turns the dish back on.

Once a month, pick a complicated dish with extras and follow it from the master record to the website and every delivery menu. Stop before checkout. Add a popular dish, a recently changed dish and a replaced photo to the same check. If the same mismatch keeps coming back, look at the connection instead of patching the screen.

Quick answers

Must delivery prices match dine-in prices?

No. Many restaurants price channels differently on purpose. Write down the decision and check the terms that apply to your setup.

Does a POS connection also update my website?

Not necessarily. Ask your website and POS providers, and do not mark the website done because a delivery connection works.

Why is an old photo still showing?

Check where the image comes from and whether it was approved. Photos can follow a different path than names and prices.