Deliveroo checks your bundle (combo) prices every time you publish your menu. If any bundle breaks one of Deliveroo's rules, Deliveroo rejects the whole menu, not just that bundle, so none of your menu changes go live until it is fixed.
⚠️ Error example: premium too high
If a choice inside a bundle costs more than it should, publishing fails with a message like this:
DSP_REJECTED: Deliveroo rejected the menu: (400) (PUT /menu/v1/brands/your-brand/menus/your-menu-id) Deliveroo API Status Error: invalid bundle item prices in modifier: <bundle group ID> invalid item price for item: <item ID>
What it means: a choice in the bundle group named in the message has a premium (extra charge) that is too high. The item named in the message is the first one Deliveroo found.
Your message will show your own IDs and may have extra quote marks or slashes, but the key words to look for are invalid bundle item prices.
How to fix a "premium too high" error
Find the item named in the error. If you can't tell which bundle group or item the IDs belong to, send both IDs to Stream support and we will tell you which ones to check.
Open the bundle and find that item in its bundle group.
Lower the item's premium, or set it to £0 so it is included in the bundle price.
Check the other items in the same bundle group (and any other bundle that uses the same item), because Deliveroo reports only one problem at a time.
Save, then publish your menu again. Wait about a minute between publishes, as Deliveroo limits how often a menu can be sent.
The Deliveroo bundle rules
1. An item can't cost more inside a bundle than it does on its own. The premium is the extra charge a customer pays for choosing that item in the bundle. A useful guide: keep the premium no higher than the item's regular price minus the price of the cheapest choice in the same group. This is our best guide to how Deliveroo checks premiums, so if a publish is still rejected after you follow it, contact support.
2. The bundle price can't be higher than the cheapest option in each group added together. Bundles must be a genuine saving for the customer. See How to Create a Bundle / Combo.
3. Every bundle group needs at least one free choice. A free choice is an available item with no premium. Groups can include choices with a premium, but they can't contain only choices with a premium.
4. A bundle group can't be empty. If every item in a group is out of stock or switched off, Deliveroo rejects the menu. Make at least one item available again, or turn the bundle off until your stock is back.
5. Every bundle item must also be on your full menu. Items in a bundle group must be present and active on your full menu before you publish. See How to Create a Bundle Group.
Worked example (made-up prices)
A "Burger Meal" bundle has a group called "Choose your burger":
Classic Burger: £8.00 on its own, premium £0 (this is the cheapest choice, and it is free)
Double Burger: £11.00 on its own, premium £3.00. This is fine: £11.00 minus £8.00 is £3.00, so the premium is within the guide.
Deluxe Burger: £12.00 on its own, premium £6.00. This will be rejected. £12.00 minus £8.00 is £4.00, so the premium should be £4.00 or less.
To fix it, lower the Deluxe Burger premium to £4.00 or less, or set it to £0.
Other errors you might see
"invalid bundle item prices" with "cannot create bundle without any free items in each section": a bundle group has no free choice (rule 3). Add a free item, or set one item's premium to £0. If your choices are all optional extras, add a "No thanks" item priced at £0.
"optionGroup has no items" (you may also see "bundle items must also exist on the menu"): a bundle group is empty or contains items that aren't on your full menu (rules 4 and 5).
A message saying the bundle price cannot exceed the total of the cheapest item prices in each section: the bundle price is too high (rule 2). Lower the bundle price.
Still can't publish?
Mark the bundle that is failing as unavailable so the rest of your menu can publish while you fix it.
Deliveroo reports only one problem at a time, so after each fix publish again and check whether a new error appears.
If the error keeps coming back, contact Stream support using the pop up at the bottom right corner within your account, and include the full error message.