Just Eat [Menulog] JET Connect Universal Integration

Summary 

Just Eat Take​away​.com is a lead­ing glob­al online food deliv­ery mar­ket­place, con­nect­ing con­sumers with over 680,000 part­ners in 20 countries including Australia, New Zealand and the United Kingdom. 

You will find them as:

Menulog in Australia & New Zealand

Just Eat in the United Kingdom, Ireland, France, Switzerland, Italy, Demark and Spain

Grubhub in the United States

SkipTheDishes in Canada

In Australia, New Zealand and the UK they offer both pickup and delivery ordering options. 

Just Eat [Menulog] accesses Polygon Central via API to post orders which are then sent to the POS.

This document details how to enable the Just Eat [Menulog] integration and relevant troubleshooting information for ongoing support.

 

This document refers to the JET Connect Universal APIs integration which is designed to function more effectively across all regions, released for use in May 2024 it replaces the original Australian bespoke integration.

---

Polygon POS Management Configuration

The Redcat Menulog interface receives orders from the Menulog server via API, and then utilises the Web Menu data in Polygon Central to send orders to POS in the same format as the Redcat Customer Ordering module would normally do. 

Therefore, programming in the BOH must be completed as per Polygon Customer Ordering.

PLUs

All PLUs to be sold via Menulog should: 

• Be tagged as a Customer Ordering PLU 
• Have the relevant Ingredients programmed if further choices or modifications are available for the PLU.   Instructions and modifiers included for the PLU in the Menulog sale will be validated against this list.
• Contain a link to the relevant customer ordering image
  Note: there may be a delay for new images to be visible to customers as they must pass through an approval process with Menulog.  This could be up to 24-48 hours.

Images

MenuLog has provided the following specifications to ensure that images are successfully displayed on the menu

• File size must be between 1MB and 10MB (Redcat recommends less than 2MB)
• Aspect ratio: Landscape (4:3)
• File type: .JPG, .JPEG or .PNG
• Minimum resolution: 1024 x 768px
• It will help if you save your photo with the name of the dish, exactly as it appears on your menu e.g. LargeChickenNuggetsAndChips

Keypads

Keypads should:

• Be created, one for each Category of menu items.
• Be tagged as a Customer Ordering Keypad

A ‘Main’ keypad will need to be created that includes a Keypad Change button to each of the keypads above. This keypad is the one that will be assigned as the integration menu for Menulog in Polygon Central.  The integration menu assignment is not generally exposed to Admin users and will need to be set by your Redcat contact.  The setting is located:

Configuration | Ordering | Integration Menus | Menulog Ordering Menu

---

Publishing a Menu Update

When programming is complete in Polygon POS Management ensure a standard update is sent to the POS network.  In addition, you need to export the menu to Menulog. 

To do this: 

• Access POS Network Updates using the POS Updates button on the toolbar.
• Choose the Web Menu Interfaces tab.
• Ensure the Menulog tick box is enabled.
• Use the Publish Update to Web Menu Interfaces button to send the data to Polygon Central. 

Limitations with the Menulog Menu Export

Images: While images assigned to Customer Ordering PLUs will be included in the menu export to Menulog, these will not automatically be included in the Menulog menu.  Images will undergo an approval process by Menulog before they are displayed for the customer.  As such, there may be a delay of 24-48 hours before new or updated images are visible on the Menulog menu.  There is no feedback loop for images that are rejected by Menulog – if the publishing of new or changed images does not occur within the above timeframe, you will need to contact Menulog. 

Default Ingredients: Menulog does not support ‘default’ ingredients for menu items. 

Free Choices: Menulog does not support ‘free choices’ for PLU ingredients.  If a choice set has 1 or more free items programmed Menulog will interpret this to mean that all items within the choice set are free. Therefore Redcat provides a modified version of choice sets in the menu export.  For example:  If a choice set is "choose 4, 2 are free" two choice sets will be displayed on Menulog - 1 for the selection of 2 free choices, and 1 for the selection of 2 priced choices.

Custom Trading Hours: Menulog does not support custom trading hours from within the menu export.  Clients can provide Menulog with a spreadsheet of custom trading hours for implementation, but these will be overwritten with the normal trading hours the next time a menu is published. 

Average Make Time: The average make time is implemented and maintained by Menulog.  They do not recognise any make time included in the menu export. 

Nested Choice Sets: Menulog limits the number of nested choice sets for items to 3.
For example:

Parent item:  Burger Meal Deal
Choice Set 1: Choose Side Size
Choice Set 2: Choose Side Item
Choice Set 3: Choose Side Flavouring

---

Managing Orders at POS

Orders received via the interface are recognised at POS as both Web Orders and Delivery Orders. These can be viewed either in the Finalised section of the Manage Delivery Orders file, Manage Pick Up Order file, or in the Manage Web Orders file. 

---