# Talabat

Aggregator code: `talabat`

1. **Menu Publish** — The menu push to the aggregator is supported only at the brand level and NOT at the location level. When the Menu Publish request is raised to the aggregators, the menu will be published to all the stores.
2. **Arabic translation** — Arabic translation is mandatory for all the catalogue entities for the title and description parameters.
3. **Item Level Taxes & Charges** — Support for item-level taxes and charges configuration are NOT supported.
4. **Recommended Items** — Support for Featured/bestsellers/recommended items is NOT supported for this aggregator.
5. **Discounts** — Configuration of any sort of Offers/Promo/Discounts is NOT supported via UrbanPiper.
6. **Order Modification** — Editing of the order is NOT supported.
7. **Discount Birfucation** — Talabat doesn't share the split of discounts share.
8. **Taxes information** — Talabat doesn't share the taxes information on the order.
9. **Order States** — Aggregator doesn't consume the Order status - *Dispatched* from UP. Passing this order state to UP from the POS system won't make any difference.
10. **Store Actions/Toggle** — Store enable/disable toggle functionality is supported for this aggregator.
11. **Item Actions/Toggle** — Item Actions/toggle is supported.
12. **Category Sorting** — Sequencing of the category is NOT supported.
13. **Charge** — Talabat sends the service fee information and it is passed as "Service Charge". Talabat also sends the "Delivery Charge".
14. **Nested Option Groups and Nested Options** — Only one level of Nested Option Groups and Nested Options are supported.


---

# 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://api-docs.urbanpiper.com/downstream/aggregator-constraints/talabat.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.