> 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.md). # Foodics A Guide for UrbanPiper Integration with Foodics. #### **Introduction** The **Foodics <> UrbanPiper integration** streamlines restaurant operations by bridging the POS system (Foodics) with major food aggregators through UrbanPiper’s middleware platform. This integration ensures accurate order syncing, centralized menu control, and reduced manual errors—ultimately improving operational efficiency for restaurants. *** #### **Integration Capabilities:** * **Real-Time Syncing**: Automatic synchronization of orders, menus, and item availability between Foodics and online delivery platforms (e.g., Talabat, Careem, Zomato). * **Centralized Management**: Control multiple aggregator menus and operations from a single UrbanPiper dashboard. * **Inventory & Stock Sync**: Item stock updates from Foodics are reflected on aggregators through UrbanPiper. * **Order Status Updates**: Seamless transmission of order status changes (accepted, preparing, dispatched) from Foodics to aggregators. *** #### **Order Relay:** * Orders placed on aggregators are received by UrbanPiper and instantly **relayed to Foodics POS**. * Ensures **minimal delay** in order entry, reducing the dependency on manual punch-ins. * **Order details** like customer info, delivery instructions, and modifiers are passed completely. * **Order status changes** in Foodics automatically reflect on aggregator platforms via UrbanPiper. *** #### **Menu Management:** * Merchants can **push menu changes from Foodics to UrbanPiper**, which then syncs to all linked aggregators. * **Menu version control** ensures changes are traceable and consistent. * Supports: * Item and modifier mapping * Tax & pricing structure sync * Availability toggling (e.g., mark items out-of-stock from Foodics) * Reduces **operational overhead** of managing menus on each aggregator manually. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.urbanpiper.com/pos-integrations/foodics.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.