# Amazon Aggregator code: `amazon` 1. **Sub-categories** — Unlike other aggregators, Amazon does not have the concept of sub-categories. Sub-categories configured on UrbanPiper would get pushed to Amazon as main categories. 2. **Unique CategoriesName** — Two categories cannot have the same name i.e all category names must be unique. 3. **Categories and Items Count** — There can be a maximum of **50 categories** in the menu publish to Amazon. Each category can contain only **50 items** within it. 4. **Item Entity Constraints** — * No two items within a category can have the same name. * Item names are to be in the title case except for words such as "with", "and", "is" etc. * Item descriptions are to be in sentence case and should end with a full stop. Proper nouns within the description, such as state and city names, should begin with a capital letter. * In the case of an item having alcoholic ingredients, the alcohol ingredient being used should be mentioned mandatorily in the item description. * Unit measures such as "pcs", "ML", "Gms" are to be consistent in both spelling and casing across the menu. For example, there cannot be one item with "Gms" and another with "Grms" in the title or description. 5. **Option Entity Constraints** — * Option names are to be in the title case except for words such as "with", "and", "is" etc * Unit measures such as "pcs", "ML", "Gms" are to be consistent in both spelling and casing across all options. For example, there cannot be one item with "Gms" and another with "Grms" in the title of an option. 6. **Tags and Tag Groups** — All the items mandatorily should have a system-generated cuisine tag associated with them for the menu to get successfully pushed on Amazon. Get in touch with the OM/ACM for more details. 7. **Serves** — Items can have serve values as 1,2,3 & 4. Any value greater than 4 would reflect as 4+ on the Amazon UI. The default serves value for every item is 1. 8. **Food Type** — All Items should mandatorily have a food type. The food type "Egg" appears as Non-veg on the Amazon UI. 9. **Images** — The item images should have the below specifications. Only .jpg items are supported on Amazon. * Image size should be 686x380 pixels. * The image should have only the food item/beverage that is getting delivered. * The image should reflect the same quantity that will be delivered to the customer. * Every dish should be neatly plated without the splash of curry or splutter. * Photoshopped images will not be approved. * Backgrounds should not be splashy nor have obstacles like chairs, hands and items that are not part of the dish. * Images should not contain watermark, logo or texts in it. * Crockery with patterns that takes the focus away from the dish should be avoided. * Avoid steel or copper utensils unless they are of premium quality. * Dishes covered in foil or used as a decorative in the background are prohibited. * The image should be sharp, bright and crisp. * The focus should be on the dish and its accompaniments. 10. **Option Names** — No two options associated with an option group can have the same name. The menu will not be pushed on Amazon. 11. **Discounts** — Discounts in any form are NOT supported on Amazon configured through UrbanPiper. 12. **Charges** — There is no support for Packaging Charges on Amazon through menu publish. This can be configured from their end. 13. **Category Timing Groups** — Time-based availability in the menu can be achieved at the Category level in the catalogue publish request. Amazon will support only slot-based timing groups. 14. **Menu Description** — Description can be passed in for the item and option level. It is not supported at the category level. 15. **Nested Option Group and Nested Options** — Amazon doesn't support the Nested OG and Options. 16. **Phone** — The "phone" number in the Order Relay payload will be a *null* value. 17. **Taxes** — The taxes data will be sent inside each and every item with only GST value. The split of CGST and SGST data is not supported by Amazon. 18. **Nutritional Information** — Passing the nutritional information for every item is mandatory. 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. 19. **Store On/Off** — Store On/Off functionality is supported. 20. **Item On/Off** — Item On/Off functionality is 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/amazon.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.