Ordering Platforms - Special Constraints

This article will help you understand the various special constraints involved with the different ordering platforms.

Written By Ops UrbanPiper (Collaborator)

Updated at August 26th, 2021

GENERIC

  1. Images  — Platform-specific item images are supported for Zomato, Swiggy, Amazon and UberEats. Images uploaded for an item have to be in .png or .jpg format and with the dimension 400x400 pixels. (Note: Check the dimension and format specific to Amazon)
  2. Recommended — When you set the recommended as true, you must pass the images for the items.
  3. Timing Groups — Timing Groups associated with Categories will need to have timings ending with XX:00 or XX:30.
  4. Category — No Parent Category should have items associated with it if the same category has sub-categories associated.
  5. Item Price  — Item price cannot be more than INR 5000/-.
  6. Variant Group — Variant Option Groups should have more than 1 Option associated.  If the Item price is 0, a Variant group with a price on an option level must be associated.
  7. Options — Minimum selectable Options cannot be greater than the number of associated options. Minimum selectable Options cannot be greater than max. selectable. More than one Option with the same title cannot be associated with the same Option Group. 
  8. Nested Option Groups — If an option is already part of the parent Option Group, again it should not be part of the Nested Option Group.  

ZOMATO ("zomato")

  1. Hybrid Logistics — Zomato gives the flexibility to choose self (merchant driven delivery) and partner delivery to their merchants. It is termed Hybrid Logistics. This toggle of enabling the Hybrid Logistics to be done at Zomato end. Later, the control of enabling/disabling the logistics will be taken care of from Quint Dashboard.  If a merchant has opted for Hybrid Logistics, then POS Partners have to make sure the "delivery_type" information from the Order Relay payload is shown on the POS screen. If this attribute value is set to,
    •  "self" — the merchant has to deliver the order.
    • "partner" — Zomato delivers the order.
  2. Order Types — Zomato has 2 order/fulfilment types — "delivery" and "pickup". This information can be seen inside the "order_type" attribute in the Order Relay Payload.
  3. Tags — Zomato has the concept of Item Tags. Associating the correct Tags to an item provides more clarity on the dish's taste/cuisine/exclusivity.
  4. Charges — Charges can be configured on an Item or Order Subtotal level. If the Charge is applied on an order Sub-Total level (i.e, "applicable_on": "order.order_subtotal" ), it has to be a Percentage Charge. Charges on an Item level (i.e, "applicable_on": "item. quantity for Fixed and "applicable_on": "item.price" for Percentage).  More than one charge cannot be associated on an order Sub-Total level to each store. If you don't specify any "applicable_on" field for a fixed charge value, by default, the charges will be on order sub-total level.
  5. Title — No two items should have the same "name" value. Zomato doesn't consider the numeric digits present in the item name as a character. Hence, keeping Chicken 65 and Chicken 95 will treat as the same item name at Zomato end. The menu sync will fail.
  6. Category Timing Groups — The Timing Groups associated with Categories should have timings ending with XX:00 or XX:30. If a Category Timing Group is configured for only Monday, by default, the same Timing Group will be applied to the rest of the days in a week for that category. You can explicitly specify if there are any changes required for other days in a week.
  7. Zomato OTP — The last 4 digits of the customer phone in the Order Relay payload will be the Rider OTP.
  8. Rider Body Temperature and Mask Check — To keep the Zomato Safety Tags for your merchants, ensure you pass this information. Also, check with brand Zomato PoC to enable the outlets to receive the RBT and Mask check information. If this is not enabled at the Zomato end, the requests will fail.
  9. Cancellation Reasons — When the orders are cancelled, passing the cancellation reasons is mandatory.
  10. Charges Title — Based on applicability, the title of charges must be Packaging Charge and Delivery Charge.
  11. Taxes Title — Based on applicability, the title of taxes must be one of these - CGST, SGST, GST, Municipality, Kerala.
  12. Nested Option Groups — Nested Option Groups and Nested Options support is available in Zomato. Currently, only one nested option group is supported for each option.
  13. QVM — For QVM items, keep "included_platforms" with only the "zomato" value. Only for QVM items, the markup prices should be specified.

SWIGGY ("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 is currently not 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.

DUNZO ("dunzo")

  1. Charges — The configuration of any kind of charge has to be done directly at the Dunzo backend. You can reach out to your Dunzo PoC for the same.
  2. Discounts  — The configuration of the discounts has to be done directly at the Dunzo backend. You can reach out to your Dunzo PoC for the same.
  3. Nested Option Groups — Nested Option Groups and nested options support is not available for Dunzo.
  4. Rider Details — No Rider details are shared.

ZOMATO MARKET ("zomatomarket")

Along with the Zomato restaurant-specific constraints specified above, below are the list of pointers to be followed for Zomato Market:

  1. Weight — Passing the "weight" attribute with the value for every item is mandatory.

SWIGGY STORES ("swiggystore")

Along with the Swiggy restaurant-specific constraints specified above, below are the list of pointers to be followed for Swiggy Stores:

  1. Option Group and Options — Swiggy Stores doesn't support the configuration of OG and Options.
  2. Taxes and Charges — The Item price should be inclusive of the taxes and charges. No external taxes and charges can be configured.
  3. Menu Mapping — The new menu items mapping will be done manually for the first time. Please reach out to your UrbanPiper PoC to get the mapping done every time the new menu items are synced to the UrbanPiper system. Once the mapping is done, you can update price changes and can make use of the Quint dashboard to sync it to aggregators. 

DOTPE ("dotpe")

  1. Fulfilment Modes — Configuring the fulfilment modes - pickup, delivery is mandatory for every item.
  2. Category Timing Groups — The configuration of the Category timing group is NOT supported.
  3. Nested Option Groups — The configuration of Nested Option Groups and Nested Options is NOT supported.
  4. Included Platforms — It is mandatory to pass the included platforms for DotPe for pickup items.
  5. Discounts — Dotpe doesn't share the split of discounts share.

AMAZON ("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.
  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 the 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 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.

EAZYDINER ("eazydiner")

  1. Fulfilment Modes — Configuring the fulfilment modes - pickup, delivery is mandatory for each and every item.
  2. Category Timing Groups — The configuration of the Category timing group is NOT supported.
  3. Nested Option Groups — The configuration of Nested Option Groups and Nested Options is NOT supported.
  4. Included Platforms — It is mandatory to pass the included platforms for Eazydiner for pickup items.
  5. DiscountsEazydiner doesn't share the split of discounts share.

INRESTO ("inresto")

  1. Fulfilment Modes — Configuring the fulfilment modes - pickup, delivery is mandatory for each and every item.
  2. Category Timing Groups — The configuration of the Category timing group is NOT supported.
  3. Nested Option Groups — The configuration of Nested Option Groups and Nested Options is NOT supported.
  4. Included Platforms — It is mandatory to pass the included platforms for Inresto for pickup items.
  5. DiscountsInresto doesn't share the split of discounts share.

MAGICPIN ("magicpic")

  1. Fulfilment Modes — Configuring the fulfilment modes - pickup, delivery is mandatory for each and every item.
  2. Category Timing Groups — The configuration of the Category timing group is NOT supported.
  3. Nested Option Groups — The configuration of Nested Option Groups and Nested Options is NOT supported.
  4. Included Platforms — It is mandatory to pass the included platforms for Magicpin for pickup items.
  5. Discounts — Magicpin doesn't share the split of discounts share.


GUPSHUP ("gupshup")

  1. Fulfilment Modes — Configuring the fulfilment modes - pickup, delivery is mandatory for every item and charge.  In case if you missed configuring fulfillment_mode then that item/charge will be available for all modes of ordering (dine-in/delivery/pickup).
  2. Category Timing Groups — The configuration of the Category timing group is NOT supported.
  3. Nested Option Groups — The configuration of Nested Option Groups and Nested Options is NOT supported.
  4. Item Images — Item images are sent in the catalogue publish to the aggregator. However, Gupshup’s UI doesn’t have the support for the same yet.
  5. Included Platforms — It is mandatory to pass the included platforms for Gupshup for pickup items.
  6. Discounts — Gupshup doesn't share the split of discounts share.

JAHEZ ("jahez")

  1. Menu Publish — The menu push to aggregator is supported only at the brand level and NOT at the location level.
  2. Sub-category — Configuring the sub-categories are 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) are 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. Order Modification — Editing of the order is NOT supported.
  12. Discounts Information — Jahez doesn't share the discount information on the order.
  13. Charges & Taxes InformationJahez doesn't share the taxes and charges information on the order. 
  14. 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.
  15. Option Actions/Toggle — Options enable/disable toggle functionality is NOT supported for this aggregator. 
  16. Store Actions/Toggle — Support for store enable/disable toggle functionality is NOT supported for this aggregator.

TALABAT ("talabat")

  1. Menu Publish — The menu push to aggregator is supported only at the brand level and NOT at the location level. The Menu Publish to aggregator is not instantaneous. When there is a menu updated in our system and synced to the aggregator, we have to email the Talabat team to update it in their system as well.
  2. Item Level Taxes & Charges — Support for item-level taxes and charges configuration are NOT supported.
  3. Recommended Items — Support for Featured/bestsellers/recommended items is NOT supported for this aggregator.
  4. Order Level Charges — Support for Order-level charges are NOT available.
  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 — Support for store enable/disable toggle functionality is NOT supported for this aggregator.
  11. Category Sorting — Sequencing of the category is NOT supported.

DELIVEROO ("deliveroo")

  1. Menu Publish — The menu push to aggregator is supported at the store level.
  2. Item Tags — The item tag - "non-alcoholic" is mandatory for each item.
  3. Sub-category — Configuring the sub-categories are not NOT supported.
  4. Category Timing Groups — Support for configuring the Category Timing Group is NOT available.
  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. Order Level Charges — Support for Order-level charges are NOT available.
  8. Discounts — Configuration of any sort of Offers/Promo/Discounts is NOT supported via UrbanPiper.
  9. Discount Birfucation — Deliveroo doesn't share the split of discounts share.
  10. Taxes informationDeliveroo doesn't share the taxes information on the order.
  11. Order States — Aggregator doesn't consume the Order states - Acknowledged, Completed and Cancelled from UP. Passing these order states to UP from the POS system won't make any difference.
  12. Store Actions/Toggle — Support for store enable/disable toggle functionality is NOT supported for this aggregator.

RADYES ("radyes")

  1. Sub-category — The support for sub-categories are not present.
  2. Category Timing Group — The support for the category timing group is not available. 
  3. Taxes — The configuration of the external item taxes are not present. The item tax/VAT should be inclusive of the item price.
  4. Nested Option Groups — The support for the configuration of nested option groups are not available. 
  5. Discount — The bifurcation of the merchant sponsored and aggregator sponsored discounts is not available. 
  6. Auto-acceptance — The support for the auto-acceptance of the order is not present as of now.

NOONFOOD ("noonfood")

  1. Sub-category — The support for sub-categories are not present.
  2. Category Timing Group — The support for the category timing group is not available. 
  3. Taxes — The configuration of the external item taxes are not present. The item tax/VAT should be inclusive of the item price.
  4. Nested Option Groups — The support for the configuration of nested option groups are not available. 
  5. Discount — The bifurcation of the merchant sponsored and aggregator sponsored discounts is not available. 
  6. Auto-acceptance — The support for the auto-acceptance of the order is not present as of now.


Was this article helpful?