# Jahez

Aggregator code: `jahez`

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. **Sub-category** — Configuring the sub-categories is not NOT supported.
3. **Category Timing Groups** — Support for configuring the Category Timing Group is NOT available.
4. **Item Price** — All the locations of a brand will have a common menu price. Location level menu pricing is NOT supported.
5. **Item Level Taxes & Charges** — Support for item-level taxes and charges configuration are NOT supported.
6. **Recommended Items** — Support for Featured/bestsellers/recommended items is NOT supported for this aggregator.
7. **Nested Option Groups** — The configuration of Nested Option Groups and Nested Options are NOT supported.
8. **Option Price** — Similar to items, location-level pricing for the options(add-ons/variants) is NOT supported.
9. **Order Level Charges** — Support for Order-level charges are NOT available.
10. **Discounts** — Configuration of any sort of Offers/Promo/Discounts is NOT supported via UrbanPiper.
11. **Discounts Information** — Jahez doesn't share the discount information on the order.
12. **Charges & Taxes Information** — Jahez doesn't share the taxes and charges information on the order.
13. **Order States** — Support for Order states like - *Food Ready, Dispatched, Completed* are not required to push from POS to UP. Since the aggregator will not be consuming these order states information from UP. The information of the cancellation on the order by the aggregator end is not shared with UP hence the same will NOT be relyed to POS partners.
14. **Option Actions/Toggle** — Options enable/disable toggle functionality is NOT supported for this aggregator.
15. **Store Actions/Toggle** — Support for store enable/disable toggle functionality is NOT supported for this aggregator.


---

# 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/jahez.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.