In this article, you can find solutions to some of the more common issues when using the Foodora integration.
Issues shown on the Operation reports page
All non-order-related issues are found on the Operation reports page. This includes menu publishing, busy mode, and snoozing.
Menu publishing
Error message or issue | How to resolve |
Menu updates are blocked and won't go through, even though you keep trying to publish. | Your store was set up to block menu updates. Contact our support team so we can confirm and switch this on for you. |
Menu push fails because the store is suspended or inactive in Deliverect. | Your store isn't active in Deliverect. Contact our support team to confirm your subscription and reactivate the store, then publish your menu again. |
Menu publish fails with a connection or timeout error. | This is usually a temporary connection issue. Wait a few minutes and try publishing your menu again. If it keeps failing, contact our support team. |
Menu publish fails because a product appears in more than one category. | Foodora doesn't allow the same item to appear as a top-level product in more than one category. Check your menu and make sure each product only lives in one category, then republish your menu. Modifiers can still be reused across multiple products without issue. |
Menu publish fails with an image upload error or an “import failed for vendor” message. | This is a known compatibility issue on Foodora's side. Contact our support team so we can apply the right menu format setting for your store. |
Menu publish fails with a “KeyError” referencing an item ID. | One of your modifiers has also been added to the menu as a stand-alone product, which isn't supported. Find that item, remove it (or recreate it properly as a product), and republish your menu. |
You see a warning about the menu being pushed “without validation.” | Contact our support team – we'll update a setting on your store to switch to the newer, supported menu format, then you can republish your menu to clear the warning. |
Busy mode
Error message or issue | How to resolve |
Busy mode fails because the store is already open or already closed. | You're trying to set a status the store is already in. Check the current store status before trying to change it again. |
Busy mode fails with “changing state is disabled for this restaurant.” | Busy mode only works during your restaurant's opening hours, or Foodora may have disabled status changes for your store. If it's outside opening hours, try again during business hours. If it persists, contact Foodora directly to have status changes re-enabled. |
Busy mode fails with a generic “something went wrong” internal error. | This is usually a temporary timeout. Wait a moment and try again. |
Snoozing
Snoozing on Foodora can fail if your Restaurant ID or Global Entity ID aren't correctly set up in your channel settings. If snoozing items isn't working, contact our support team to confirm these IDs are entered correctly.
Other
Error message or issue | How to resolve |
Allergen tags added in Deliverect don't show up on Foodora. | Foodora doesn't support allergen tags through the connection. Add allergen information directly into each product's description instead. Note that diners won't be able to filter by allergen tag on Foodora – that's a Foodora limitation. |
Orders occasionally arrive outside your listed opening hours. | Foodora only sends an order to Deliverect once a rider has been assigned, which can happen slightly after your closing time if the order was placed right before close. You can accept this as normal, or close a little earlier to avoid it. |
Nested modifiers aren't displaying or working as expected. | For nested modifiers to work on Foodora, the first modifier group must be set to require exactly one selection (min 1 / max 1), and only three levels of nesting are supported in total. |
Some products show up on Foodora without pictures. | This is a known Foodora display bug. It typically resolves once a diner enters a delivery address near the restaurant, which refreshes the images. |
A category containing alcohol isn't showing on Foodora. | Foodora requires an alcohol disclaimer to be added to the category description, in every language you use, before it will display. |
Categories can't be left empty. | Make sure every category on your menu has at least one visible item – don't leave a category empty or with everything snoozed. |
Image uploads are rejected or don't display correctly. | Foodora has strict image rules and blocks image file names containing spaces, dashes, commas, accented characters, or percent signs. Rename your image file using only plain letters and numbers, re-upload it, attach it to the product, and republish your menu. |
Emojis in menu text don't display properly. | Emojis aren't supported in Foodora menus and will show as a question mark instead. Remove emojis from your product names and descriptions. |
A product has more than 20 variants. | Foodora doesn't support more than 20 variants per product. Reduce the number of variants and republish your menu. |
