DinePlan Version | 2.270.1 |
Here are the steps to connecting to eDine from DinePlan
Pre-Requisites
Here are the pre-requisites for this integration to work. This should be getting from the DinePlan Team
Items | Description |
|---|---|
eDine API Url | The url of the eDine Api. The Url will be look like one below https://hoft.apiplan.xyz |
Tenant Id | Tenant Id of the eDine or DineConnect. |
Location Id | The Wheel Location Id of the eDine and it should be fetched from the DineConnect → Wheel → Location Screen  |
User | Username is to get authenticated with eDine API |
Password | Password is to get authenticated with eDine API |
eDine has the three modes of Ordering (Dine-In, TakeAway, and Delivery).
Here are the steps to be done
Configure the Program Settings
Configure the Local Settings
Configure the Action and Rules
STEP 1: Configure the Program Settings
eDine will be properly working in the DinePlan if the Program Settings are properly configured. To Configure eDine
Go to Back Office → Settings → Program Settings → eDine (Tab) and it goes as below
Here are the explanations for the program settings
Items | Description |
|---|---|
Url | The url of the eDine Api. The Url will be look like one below |
User | Username is to get authenticated with eDine API |
Password | Password is to get authenticated with eDine API |
Tenant Id | Tenant Id of the eDine or DineConnect. |
Location Id | The Wheel Location Id of the eDine and it should be fetched from the DineConnect → Wheel → Location Screen |
PrintTemplate | Template for Priniting QR Code and Here is the sample of it <L>Hello eDine
<F>-
<QR>{URL}
<L>{PinCode}
<F>-
{URL} → will be replaced by actual URL of the eDine {PinCode} → It will be replaced by OTP |
PaymentType | eDine comes with the online payments (Omise, PayTm, GooglePay and many more). This payment type helps to close the DinePlan ticket with the particular payment type and real consolidation of payment type will be happen at DineConnect |
OtherCharge | There are delivery charge, service charge in eDine and that will be calculated via OtherCharge |
NonMappedMenuItem | If the item is not available in Local DinePlan for the relevant eDine Item, NonMappedMenuItem will be used to create Order. |
STEP 2: Configure the Local Settings
There are two local settings available and here are the explanation for that
Go to Back Office → Settings → Local Settings
The settings are
Name | Explanation |
|---|---|
eDine | DinePlan uses this setting for Generation of QR Code for the Customer to Order from the Table Page  |
eDineSync | All the tickets created will be automatically called and sync into the Machine where it is activated to true. If the eDineSync is false, the tickets will not be locally pulled from the Server to DinePlan. |
STEP 3: Configure Actions and Rules
Here is the action to update the Status of the Table as below
The above action should be mapped to the Rule as below (New Rule)
