# Dos & Donts for the integration

## **Dos & Don’ts for UrbanPiper × Foodics Integration**

### **✅ DOs**

#### **Authorization & Access**

* **Use Owner-level access** while enabling the UrbanPiper app on Foodics.
* **Ensure the correct credentials** (admin login) are used for authorization.
* **Verify the authorization is completed** on both the UrbanPiper and Foodics screens.

#### **Menu Setup**

* **Create the ‘UrbanPiper’ menu group** exactly as required (spelling must match).
* **Place all relevant menu items** inside the UrbanPiper group.
* **Add correct Charge IDs** (Pickup + Delivery) as open charges.
* **Use accurate price tags** for each aggregator where differential pricing applies.
* **Double-check product names, variants, tax settings, and availability** before confirming the menu.

#### **Coordination**

* **Inform UrbanPiper promptly** once your Foodics setup is complete for menu pull.
* **Respond quickly** to mapping queries from the UrbanPiper onboarding manager.

#### **Post Go-Live**

* **Monitor orders regularly** during the stability period.
* Ensure the **menu is pulled on UrbanPiper** every time there is a change in the menu on Foodics.

***

### **❌ DON’Ts**

#### **Authorization & Access**

* **Do NOT proceed without owner-level access** — other roles may block permissions.
* **Do NOT edit or delete the UrbanPiper group** after mapping starts.
* **Do NOT change the base menu or product IDs** once onboarding begins without informing UrbanPiper.

#### **Menu Setup**

* **Do NOT rename or alter price tag labels** (names must match exactly).
* **Do NOT add products outside the UrbanPiper group** if they need to appear on aggregators.
* **Do NOT create duplicate product entries** in Foodics, as this causes mapping confusion.

#### **Coordination**

* **Do NOT contact aggregators directly** for mapping — this is handled manually by the UrbanPiper team.
* **Do NOT raise Foodics system issues to UrbanPiper** — these must go via the Foodics AM and their support team.
* **Do NOT request urgent escalations** for non-P0/P1 issues.

#### **Operational**

* **Do NOT make menu changes during mapping** without notifying the UrbanPiper onboarding team.
* **Do NOT expect instant mapping** — timelines vary by aggregator (e.g., Talabat weekly cycle).
* **Do NOT deactivate the UrbanPiper group** or make structural changes during go-live.