> For the complete documentation index, see [llms.txt](https://help.urbanpiper.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.urbanpiper.com/pos-integrations/foodics/syncing-menu-changes-to-urbanpiper.md).

# Syncing Menu changes to UrbanPiper

{% embed url="<https://urbanpiper-support.portal.trainn.co/share/wsiHZaI4t3U1KVUc0O6bfQ>" %}

UrbanPiper’s integration with Foodics allows you to **pull the menu directly from the Foodics POS**, ensuring consistency across all aggregator platforms. Follow the steps below once all necessary changes have been made in the Foodics console.

**Step-by-Step Process:**

1. **Login to Atlas (UrbanPiper Business Manager):**\
   Navigate to the Atlas dashboard using your UrbanPiper credentials.
2. **Go to Catalogue → Items:**\
   In the left-hand menu, select **"Catalogue"**, then click on **"Items"**.
3. **Initiate Menu Import:**
   * Click on the **three dots (⋮)** on the top right corner.
   * Choose **“Import Menu”** from the dropdown.
   * Select the appropriate **location** for which you want to sync the menu.
   * Click on **"Import"** to start the process.
4. **Wait for Sync to Complete:**\
   The import process typically takes a **few minutes**. UrbanPiper will pull the latest menu data (items, modifiers, prices, etc.) from Foodics.
5. **Publish the Menu to Aggregators:**\
   Once the menu has been refreshed on UrbanPiper:
   * Go to the **“Catalogue”** section.
   * Select the relevant location and channel (e.g., Talabat).
   * Click on **“Publish”** to push the updated menu to the aggregator platforms.

<figure><img src="/files/IUfaMPFcfblivfZR7q5o" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://help.urbanpiper.com/pos-integrations/foodics/syncing-menu-changes-to-urbanpiper.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.