# Swiggy

Aggregator code: `swiggy`

1. **Categories** — Multiple categories cannot have the same name.
2. **Items** — The number of items associated with a store cannot be more than 400.
3. **Option Groups** — An Item should not have more than 4 Variant groups associated with it. Various Option Groups associated with an item cannot have similar names.
4. **Options** — Same options can't be shared with more than one option group associated with the same item.
5. **Charges** — Charges only on an Item level (*i.e, "applicable\_on": "item.quantity*) are supported. It can be either a *Percentage* or a *Fixed* Charge.
6. **Discount** — Swiggy doesn't send **its share** of discount in the Order Relay payload. The configuration of discounts has to be done at the Swiggy backend directly. You can get in touch with your Swiggy PoC for the same.
7. **Taxes on Charges** — To configure the taxes on charges for any brand, you can get in touch with your Swiggy PoC.
8. **Nested Option Groups** — Nested Option Groups and nested options support are available for Swiggy.
9. **Food Type** — Swiggy doesn't support Eggetarian as a food type. If you don't pass any Food Type, Swiggy will take it as Non-Veg.
10. **Goods and Services** — For packaged-good items, the tag value *"packaged-good"* must be associated with an item. For non-packaged-good items, no need to assign any tag.
11. **Nutritional Information** — Passing the nutritional information for every item is mandatory. But as of now, Swiggy expects to pass the nutritional information in the item description.
12. **Item Description** — Description is mandatory for items with keywords such as meals, platter, combo, box, thalis.
13. **Avoid Promo names as metadata info** — Title and description should not contain the promotions, discounts, offer names - "bogo", "off", "promo", "discount", "free", "freebie", "Buy", "offer", "promotion", "sale"
14. **Alcoholic Information** — Title and description should not contain the alcohol drinks and tobacco standalone names such as beer, rum, bira, etc but the words can be tied with supportive words such as "Rum Cake".
15. **Items count per store** — A maximum of 1000 items can be associated with a store.
16. **Type of meat** — Type of meat should be defined for every non-veg item either in the item title or description.
17. **Quantity info** — Quantity info is mandatory for items like pizzas, drinks and cakes.
18. **Order Modification** — Order modification is allowed in Swiggy. [Read more](https://api-partner-docs.urbanpiper.com/v/api-documentation/endpoints/miscellaneous/mark-order-item-stock-out).
19. **Request Callback** — The orders cannot be cancelled directly instead upon receiving the cancellation request from POS, we shall make a callback request to Swiggy.
20. **Store On/Off** — Store On/Off functionality is supported.
21. **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/swiggy.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.