Hungry Panda Integration (User Guide)

Summary

Polygon POS Management Configuration

Apply the Integration in Polygon Central

Pausing the Integration

Limitations with the Hungry Panda Integration

Summary 

Polygon POS Management Configuration

The Hungry Panda integration will need to be enabled in the default system settings (use the Apply to All option if relevant) and in the system settings for the relevant POS location(s).

To do this:

• Access Polygon POS Management.
• Access the Default Location System Settings (or POS Location System Settings as appropriate).
• Place a tick in the Enable the Hungry Panda web menu ordering module box under External System Settings | Web Menu Ordering Interfaces | Hungry Panda.

Applying the (Default) POS Location Setting will enable Hungry Panda as an option in the External Web Menu Ordering Interfaces on the POS Location Details form.

• Open the POS Location Details form for the relevant location.
• Place a tick in Hungry Panda.

Apply the Integration in Polygon Central

Now that the setup is complete, the final step is to assign the store for the Hungry Panda integration.

Admin users will need to be assigned the following User Role:

• Access to Hungry Panda Store Configuration
  
  

  You can learn more about User Roles in this article.

Assign Stores to Hungry Panda Integration

The stores available for the Hungry Panda Integration for ordering must be assigned in Polygon Central. 

To do this:

• Access Polygon Central | Integrations | Hungry Panda
• Use the Add Integration button to add the locations that will accept orders from Hungry Panda.
  • Choose the relevant location from the Locations List drop-down.
  • Enter the Store ID provided by Hungry Panda for this location in the Hungry Panda Store ID field.

• Use the Submit button to save.

Note: a menu export will be pushed to Hungry Panda whenever the integration record is saved.

Force Store Offline

The Force Store Offline option is available to Admin Users as an emergency response for crisis situations.

This option will send an export to Hungry Panda and the store will be listed as Closed on the app, preventing customers from placing an order.

While the Force Store Offline option will take the store offline, you will need to remove the tick to return the availability manually.  It is therefore recommended that the Control Console be used, as a return-to-service can be programmed within the rule. 

Pausing the Integration

Limitations with the Hungry Panda Integration

❌ Composite Items
Placeholder PLUs @ $0.00 will need to be utilised for sizes.

❌ Nested Choice Sets
The menu will only support single-layer nesting.  Each parent item can have choice sets, but none of those choice sets may contain further choices.

❌ Individual Product Availability times
Day-part assignment at Item level is not supported.

❌ Multiple Menus
You must use the same menu for both Pick-Up and Delivery sale types.

❌ Number of Free Choices within Choice Sets
If a choice set with x free choices before charges apply is found when exporting the menu, the choice set will be excluded if it is an optional choice set.  If it is a required choice set, the parent item will be excluded from the menu.

❌ Upselling
Any programming regarding upselling will be ignored.

❌ Dietary and Allergen Tags
Any programming regarding tags will be ignored.

✅ Day-Part Menus at submenu level only

✅ Scheduled/Future-Dated ordering

✅ Choice display order/ranking

✅ Category and item display order/ranking

Ordering Limitations

While Hungry Panda supports shop (client-managed) delivery, the integration does not pass the statuses required to enable this.

• ❌ Client Managed Delivery