Why your Deliveroo menu prices differ from the ones you set

Restaurant operators on Deliveroo most often find the old price still live because the edit was saved but never published. Menu Manager separates “Save” from “Publish”, and Deliveroo’s own help article warns “Don’t forget to ‘Publish’ your menu if you want your saved changes to go-live for your customers to see”. Sites without Menu Manager access request changes through a form instead, where “Changes take up to 3 days”. Bulk price and stock work runs through CSV uploads that cannot be undone once confirmed.

Where do you change a Deliveroo price, and why does saving not change it?

Deliveroo’s editing flow has two commit points and only the second one reaches customers. The help article for editing an item lists the steps as making “any changes to the item name, description, image, price or tax rates”, then “Click ‘Save’ once you’re done”, then “Click ‘Publish’ to set the menu live with the edited menu item” (help.deliveroo.com). Deliveroo repeats the warning for deletions, telling partners not to forget to publish “if you want your saved changes to go-live for your customers to see”.

An unpublished Deliveroo edit is the single most common price mismatch on this platform, and it is invisible from the inside. The operator who saved the change sees the new price in Menu Manager whenever they log back in, because Menu Manager shows the saved draft. The customer sees the last published version. Both parties are reading a Deliveroo screen showing a Deliveroo price, and the two numbers differ, so a call between head office and the branch will not resolve it. Only the storefront settles the question.

What happens if your Deliveroo site has no Menu Manager access?

Not every site edits its own menu. Deliveroo’s guidance is explicit about the fallback: “You can make quick and easy changes to your Deliveroo menu(s) by using Menu Manager in Partner Hub. If you don’t have access to Menu Manager yet, please use the ‘Get in touch form’ on the Help page in Hub to ask for any menu changes. Changes take up to 3 days, but we do our best to get them done as quickly as we can” (help.deliveroo.com).

A chain therefore runs on two clocks at once. Sites with Menu Manager change price at publish time, and sites still on the request form change up to three days later. A brand rolling out a price rise on one date will genuinely have two prices live for several days, and the gap is documented behaviour rather than a fault anyone can be asked to fix.

Bulk work adds a third pace. Deliveroo’s Bulk Management tool changes prices by CSV upload, and its stock availability action carries a hard ceiling stated as “Important: You can update a maximum of 10 sites at a time”, so a forty site estate is at least four uploads. The flow is one way: “You cannot undo an upload once confirmed, so review carefully before completing” (help.deliveroo.com). A CSV with a decimal in the wrong column publishes rather than fails.

Why does a Deliveroo menu push return MATCH_EXISTING_MENU?

For chains pushing menus from a POS, Deliveroo’s Menu API is a whole-menu replacement rather than a field-level edit. The documented flow is that “The partner submits a menu to be updated. Deliveroo accepts the menu payload, performs a validation and starts asynchronous menu processing. Once the menu is processed and published the webhook to notify a partner is called” (api-docs.deliveroo.com).

There is one important silent case. Deliveroo states that “In the case of the menu details to be uploaded are the same as the existing menu details, then a successful response is returned with the additional information of the result. The result will contain the value MATCH_EXISTING_MENU“, and that the notification webhook fires after each successful upload “excluding the case when the menu matches existing menu”. An integration whose price change never reached the payload gets a success and no webhook, and only the result value tells it apart from a repriced menu.

What does changing the Deliveroo Menu ID do to your prices and offers?

Deliveroo treats the menu identifier as the identity of the menu itself, and the consequences reach past pricing. The documentation states that “Menu ID is a unique identifier for your entire menu and its content”, that “From the system’s point of view: new menu ID = completely new menu, even if it looks the same”, and that “When you change the menu ID, our system will treat it as a completely new resource. This means that no items or modifiers can be shared between menus” (api-docs.deliveroo.com).

Deliveroo spells out the cost directly, warning that “using a different menu ID has impact on reporting, item performance and offers” and recommending “you use the same menu ID wherever possible”. A POS provider that generates a fresh menu ID on every export therefore rebuilds the whole menu each time. Prices land correctly and offers attached to the previous items do not, so items revert to full price with no error anywhere in the chain.

Does Deliveroo require your app price to match your dine-in price?

In the UK it does, and this is the only parity clause among these platforms with money attached. Deliveroo’s UK partner terms state that prices “should be the same as the prices for menu items published in your dine-in or in-store menu”. Enforcement follows: “You agree that if a customer provides us with evidence that, without reference to promotional offers, the price in-restaurant/store is lower than the price of the menu item on the Platform, we will refund the difference to the customer and deduct an amount equal to the refund from the payment we make to you” (merchants.deliveroo.com legal terms).

Two details matter for operators. The trigger is a customer producing evidence, not an audit, so the exposure is unpredictable rather than systematic, and it lands as a deduction from settlement rather than as a warning. Deliveroo also reserves editorial rights over the listing, stating that “We reserve the right to edit menu items for display on the Deliveroo Platform”. The UAE partner terms carry the Menu Manager conditions but not this parity clause.

Why does one Deliveroo price show for delivery and another for pickup?

Because a Deliveroo item does not hold one price, it holds a default plus a stack of overrides. Pricing is carried in price_info, and Deliveroo explains that “price overrides are managed through the price_info.overrides field”. The supported contexts are named individually: “Default Price: The standard item price. It is set at the root of the “price_info” property “price””, then MODIFIER for the price “when an item is selected as a modification”, ITEM for the price “when used as a modification within a specific parent item”, PICKUP_ITEM for “Price for pickup orders”, and PICKUP_MODIFIER (api-docs.deliveroo.com).

One override has a side effect worth knowing before it happens. Deliveroo notes that “If the base price is set to 0 and a pickup price is specified, the item will be available only for pickup”, so a zeroed base price does not make an item free, it removes it from delivery. The ceiling is generous enough to hide mistakes, since “There should be no more than 100 price overrides set on a single item”, and a stale override outlives every edit made to the default price.

How long can a wrong Deliveroo price stay live before anyone notices?

Longer than any closure, because a closure has a symptom and a wrong price does not. A Deliveroo site that stops trading is noticed the same evening, since the order count collapses and somebody asks why. An unpublished price change produces no such signal at all. The site trades normally, the orders arrive, and the only evidence is the gap between the price the brand decided and the price the customer paid, which appears in no Deliveroo screen and in no alert.

Because a Deliveroo price is only real after it is published, and because a bulk upload can be confirmed but not reversed, the practical check is to read the live storefront rather than the draft in Menu Manager, which is what Kitchain (kitchain.co) does across every branch each day. Ownership, markets and the full set of Deliveroo signals are covered on the Kitchain Deliveroo page.