# Integrate your Foodics account with UrbanPiper

This guide outlines the **onboarding steps**, **timelines**, and **key operational guidelines** for completing the UrbanPiper–Foodics integration successfully.

An UrbanPiper Onboarding Manager will be assigned to work alongside the Foodics team and support you throughout the entire integration process.

### **Onboarding Process Overview**

The onboarding process consists of **three major phases**:

1. **Authorization**
2. **Menu Setup on Foodics**
3. **Menu Pull & Aggregator Mapping**

***

### **1. Authorization**

Follow the steps below to grant integration permissions to UrbanPiper and generate your brand-specific token.

#### **Step 1: Log in to the Foodics Console**

* Log in using **Owner-level access**.
* Navigate to the **Marketplace**.

#### **Step 2: Search & Open the UrbanPiper App**

* Search for **UrbanPiper** in the Marketplace.
* Click the app to open its details screen.
* Enter the credentials:

```
Username: xxxx
Password: xxxxxxxxxxx

UrbanPiper Onboarding Manager will assist you with the password during your onboarding process.
```

#### **Step 3: Authorize the Integration**

* On the UrbanPiper screen, click **Authorize**.
* You will be redirected to Foodics — click **Authorize** again to complete the process.

***

### **2. Menu Setup on Foodics**

#### **Menu Grouping**

* Ensure the **entire menu** is placed under the **UrbanPiper** group.
* The group name must match exactly in spelling (case can differ).

#### **Add Products to the UrbanPiper Group**

* All products that need to appear on aggregator platforms must be assigned to the UrbanPiper group.

#### **Create Charge IDs**

* Create an **Open Charge ID**.
* Add both **Pickup** and **Delivery** charges.

#### **Price Tags (for Differential Pricing)**

If the brand has differential pricing, add the following price tags and associate them with the relevant products:

```
up-talabat
up-toyou
up-mrsool
up-deliveroo
up-radyes
up-eateasy
up-chatfood
up-noonfood
up-hungerstation
up-jahez
up-careem
```

* Tag names are **name-sensitive but not case-sensitive**.

**Pricing Logic**

* If a product has a price tag for a specific aggregator → **that price is used**.
* If no tag exists → **base price is used**.
* If no tags at all → **base price applies to all aggregators**.

***

### **3. Menu Pull in UrbanPiper**

* Once the menu setup is completed and verified in Foodics, UrbanPiper will **pull the menu into the UrbanPiper system**.
* This initiates the **mapping process**.

***

### **4. Aggregator Mapping**

After the menu pull, the UrbanPiper Onboarding Manager will coordinate with the various aggregators to map the brand’s locations.\
This is a **manual process,** and timelines differ by aggregator.

#### **Mapping Timelines**

| Aggregator        | Mapping Timeline                                                            |
| ----------------- | --------------------------------------------------------------------------- |
| **Deliveroo**     | 24–48 hours from request                                                    |
| **Talabat**       | Requests raised every **Sunday/Tuesday**; go-live on **Wednesday/Thursday** |
| **Careem**        | Mapping raised on **Wednesdays**; go-live on **Thursday**                   |
| **Noon / Smiles** | 24–48 hours from request                                                    |
| **Chatfood**      | 3–4 days                                                                    |
| **Keeta**         | Depends on the Keeta mapping team (variable)                                |

***

#### **Completion & Go-Live**

* Once the mapping is completed across all aggregators, the UrbanPiper Onboarding Manager will share the final status.
* Orders can then begin flowing through **Foodics × UrbanPiper**.

\ <br>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.urbanpiper.com/pos-integrations/foodics/integrate-your-foodics-account-with-urbanpiper.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.