Info
Content

UrbanPiper Integrations

This document helps to do the UrbanPiper Integration at DineSuite of Applications. UrbanPiper is integrated with DinePlan (with DineConnect) and Only DinePlan. 

The document is divided into the following things 

  1. Urban Piper 
  2. Gateway 
  3. Common Steps in DinePlan
  4. DinePlan Integration (Applicable only if we do not use DineConnect).
  5. DineConnect Settings
UrbanPiper 

Decide on the Location Name and Location Code for the Customer. This is very important to take the customer to accept the Orders from Urban Piper.

  1. Request a Credentials (API Key, User, URL for a Customer) from UrbanPiper Team
  2. If we use only DinePlan for the integration, We have to create the Location Manually in Quint Dashboard
  3. The Webhook should be configured in Quint Dashboard as below 

 

image-1610018555991.png

The URL are 

Order placed https://dcgateway.azurewebsites.net/UrbanPiper/PushOrder
Order status update https://dcgateway.azurewebsites.net/UrbanPiper/PushOrderStatus
Order delivery status https://dcgateway.azurewebsites.net/UrbanPiper/PushRiderStatus
Stores create/update https://dcgateway.azurewebsites.net/UrbanPiper/StoreUpdate
Stores status change https://dcgateway.azurewebsites.net/UrbanPiper/StoreStatusUpdate
Catalogue publish through API https://dcgateway.azurewebsites.net/UrbanPiper/CatalogueUpdate
Item Stock In/Out https://dcgateway.azurewebsites.net/UrbanPiper/ItemUpdate
Gateway

Request Credentials for the Gateway from DinePlan Team. By giving the API Key, User, and URL from the UrbanPiper team. You need to get the Location Id and Location Code from the Gateway.

Steps in DinePlan

Here are the steps to be done at the DinePlan

STEP 1: Program Settings to be updated

PG.png

Menu Screen Menu name (used only if the DinePlan is used for UrbanPiper)
Price Tag

Price Tag name (used only if the DinePlan is used for UrbanPiper)

Location

Location Id from Gateway

Platform

Platforms that we are supporting (used only if the DinePlan is used for UrbanPiper)

Name

This is the Cloudinary URL. Request from the team for the Customer. (used only if the DinePlan is used for UrbanPiper)

https://cloudinary.com/

Key

This is the Cloudinary Key. Request from the team for the Customer. (used only if the DinePlan is used for UrbanPiper)

https://cloudinary.com/

Secret

This is the Cloudinary Secret. Request from the team for the Customer. (used only if the DinePlan is used for UrbanPiper)

https://cloudinary.com/

STEP 2: Configure the Screen as below

1. Create the Department With the Delivery for UrbanPiper in DinePlan and add the tags as below in the Ticket Listener

and It creates the Button below to filter tickets

 

STEP 3: Configure Calculation Types as below

 

STEP 4: Create Ticket Tag and No Mapping Needed

STEP 5: Add Order Tag as below and Make sure that Tax-Free is selected and No Mappings

STEP 6: Make sure that Ticket Type is Tax Exclusive. If the Ticket Type has Tax Inclusive. Create Separate one Ticket Type and assign it to UrbanPiper Department

 

 

 STEP 7:  Create Action as below

Create one more action for Change the Status of the Ticket

Create Automation Command for Updating the Pull Order, Food Ready, and Completed Status

 

 

Rules for the Actions

STEP 8: Create the Trigger

STEP 8: Add Rule as below

STEP 9: For Testing Purpose

Add Automation Command and Attach the Above Action

 

 

DinePlan Integration (Applicable only if we do not use DineConnect).

STEP 1:  The program settings and menu are completely created and make sure that it is synced in UrbanPiper

STEP 2: Create the Product Tag in DinePlan as below 

WpgPG.png

STEP 3: Configure the values if needed in the products as below. Zomata expects tag. 


2LzPG.png

 

The tags for Zomato are 

Veg
Chef Special
Holi Special
Gluten Free
Non-Veg
Meal
Chef Special
Lactose Free
Egg
Cake
Contains Pork
New
Spicy
Restaurant Recommended
Dairy Free
Vegan
Seasonal
MRP Item
FODMAP Friendly

DineConnect Settings

Screen 1:

After you get the DineConnect enabled for UrbanPiper, the following settings should be in Place 

RNcPG.png

  • Push Catalogue button sends all the Menu to UrbanPiper
  • Push Location creates the Location in DineConnect

Screen 2:

The Location should be like this

VFWPG.png

  • Push Catalogue -> Only Sends the Location Level Details to Urban Piper
  • Push Location -> Sends only the Location Enablement of Zomato and Swiggy to Urban Piper
  • Update Catalogue -> Only updates the Disable Items to Urban Piper

Screen 3:

The MenuItem screen helps to manage the Tags for Zomato etc as below 

screencapture-urban-dineconnect-net-Application-Index-2021-01-07-17_36_52.png

Back to top