# UberEats Aggregator code: `ubereats` 1. **Nutritional Information and Servings** — Passing the nutritional information and Servings for every item is optional. The complete list of Nutritional values is mentioned in the [Add/Update Menu](https://api-partner-docs.urbanpiper.com/v/api-documentation/endpoints/menu/add-update-menu) API. The Nutritional info value should be a positive integer. 2. **Store Timing Groups** — Configuring the store timings is mandatory. 3. **Order States** — Ubereats supports only "Acknowledged" and "Cancelled" states from us. "Dispatched" and "Completed" are supported for self-delivery orders only. 4. **Item Level Taxes & Charges** — Support for item-level taxes and charges configuration is NOT supported. 5. **Discounts** — Configuration of any sort of Offers/Promo/Discounts is NOT supported via UrbanPiper. 6. **Discount Birfucation** — Ubereats doesn't share the split of discounts share. 7. **Taxes information** — Ubereats doesn't share the taxes information on the order. While configuring the menu items, the item prices must be inclusive of the tax value. 8. **Store On/Off** — Store On/Off functionality is supported. 9. **Item On/Off** — Item On/Off functionality is supported. 10. **Order Modification** — Ubereats doesn't support the order edit functionality. 11. **Images** — Following are the image requirements for ubereats - File type = jpg, png, gif. Max 10 MB size. Height: 440-10,000 pixels. Width: 550-10,000 pixels. Between 5:4 and 6:4 aspect ratio. --- # 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/ubereats.md?ask= ``` 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.