In this article, you can find solutions to some of the more common issues when using the Just Eat integration.
Issues shown on the Orders page
Error message or issue | How to resolve |
️Invalid Discount PLU / Invalid Delivery PLU / Invalid Service Charge PLU | Add the correct PLU codes to your channel link settings. |
Issues shown on the Operation reports page
All non-order-related issues are found on the Operation reports page. This includes setting up the menu publishing, busy mode, and snoozing.
Menu publishing
Error message or issue | How to resolve |
️{'message': 'error converting menu to Just Eat format: EAT_IN menus are not supported. There was a problem with the menu pushed. Please double check it.', 'resolution': 'Check menu payload before trying again', 'code': 'INVALID_FORMAT'} | Change the menu's type to either Delivery, Pickup, or Delivery and pickup. |
️ {'message': 'error sending menu to delivery partner: 4 level items detected - remove a layer. There was a problem with the menu pushed. Please double check it.', 'resolution': 'Remove a layer from the 4 level items. It is not possible to send an item with a modifier that contains a modifier that contains another modifier', 'code': 'INVALID_FORMAT'} | Ensure that modifiers have a maximum of three levels, as Just Eat does not support any additional levels. |
️ Invalid request body - validation errors: [menus.0.categories.5.items.4.modifiers.0.options.3.price: Must be greater than or equal to 0 | Ensure that you don't have items with a negative price. |
️{'message': 'error converting menu to Just Eat format: Failure while mapping availabilities. There was a problem with the menu pushed. Please double check it.', 'resolution': 'Check menu availabilities, are there availabilities?, does the menu have duplicate availabilities?, only 2 time periods are supported and must not overlap.', 'code': 'INVALID_FORMAT'} | Check your opening hours and menu availability to ensure that there is a maximum of two time periods. |
️{'message': 'error sending menu to delivery partner: The request was rejected due to invalid authorisation. Please contact Flyt to fix it.', 'resolution': 'Contact JET Connect to ensure the menu destination (Just Eat) setup is correct', 'code': 'INVALID_CONFIGURATION'} | |
️ {'message': 'error sending menu to delivery partner: Configurable values for communication with Just Eat were not found. Please contact Flyt to fix it.', 'resolution': 'Contact JET Connect to ensure the menu destination (Just Eat) configuration is populated', 'code': 'INVALID_CONFIGURATION'} | |
️{'message': 'error converting menu to Just Eat format: Seems like not all menu card fields have been populated in JET Connect. Please contact Flyt to fix it.', 'resolution': "Ensure all menu card fields have been populated in JET Connect's menu destination connector configuration.", 'code': 'INVALID_CONFIGURATION'} | |
️ "message": "no API found with those values" | |
️ "message": "Invalid authentication credentials" |
Busy mode
Error message or issue | How to resolve |
️Failed to set busy mode: 404 Client Error: Not Found for url: https://api.flytplatform.com/restaurants/X/offline ️ Failed to set busy mode: [Open/close store] Updating [JUST_EAT] Restaurant status to online for location X failed with HTTP status 404 and error message restaurant availability not registered for the specified restaurant . Please contact Flyt. ️ Failed to set busy mode: [Open/close store] Updating [JUST_EAT] Restaurant status to offline for location X failed with HTTP status 404 and error message restaurant availability not registered for the specified restaurant . Please contact Flyt. | |
️ Failed to set busy mode: [Open/close store] Updating [JUST_EAT] Restaurant status to offline for location X failed with HTTP status 403 and error message restaurant availability not enabled for the specified restaurant . Please contact Flyt. ️ Failed to set busy mode: [Open/close store] Updating [JUST_EAT] Restaurant status to online for location X failed with HTTP status 403 and error message restaurant availability not enabled for the specified restaurant . Please contact Flyt. | |
️ Failed to set busy mode: [Open/close store] Updating [JUST_EAT] Restaurant status to offline for location X failed with HTTP status 403 and error message restaurant availability not enabled for brand . Please contact Flyt. | |
️ Failed to set busy mode: [Open/close store] Updating [JUST_EAT] Restaurant status to offline for location X failed with HTTP status 401 and error message Invalid authentication credentials." ️ Failed to set busy mode: [Open/close store] Updating [JUST_EAT] Restaurant status to online for location X failed with HTTP status 401 and error message Invalid authentication credentials." | |
️ Failed to set busy mode: [Open/close store] Updating [JUST_EAT] Restaurant status to offline for location X failed with HTTP status 401 and error message No API key found in request. ️ Failed to set busy mode: [Open/close store] Updating [JUST_EAT] Restaurant status to online for location X failed with HTTP status 401 and error message No API key found in request. |
Snoozing
Error message or issue | How to resolve |
️ InvalidChannelConfiguration: [JUST_EAT] Snooze failed for X: {"error_message":"Restaurant not registered for item availability updates - contact Flyt team for support","success":false} | |
️ InvalidChannelAPIResult: [JUST_EAT] Snooze failed for X: { "message":"Invalid authentication credentials" }. Response status code 401 | |
️ InvalidChannelAPIResult: [JUST_EAT] Snooze failed for X: {"message":"No API key found in request"}. Response status code 401 |