To improve the overall quality and consistency of menus on the Swiggy platform, Swiggy conducts a Menu Quality Check (QC) on all published menus.
Once the QC is completed and the menu fails:
Any items failing QC standards are removed from the menu by Swiggy, and menu publishing will be on hold until all errors are fixed
All subsequent menu updates for the outlet will be applied only after passing QC.
Error Message: "entity with id : XXXXXXXX was rejected because: Packaging charges Issue (Packaging charges can not be applied beyond the Swiggy Slab)"
Cause: The packaging charges set for an item are higher than allowed by Swiggy’s standard pricing slab.
Resolution: Configure the packaging charge as per the slab below:
If you want to set a packaging charge outside the allowed slab, you must get prior approval from your Swiggy POC (Point of Contact).
Without Packaging charge approval, your menu update will be rejected, and you will see an error message.
Error Message: "Category create/update failed with error: [name: Duplicate 'Category' with id XXXXX and name 'Sandwich' found.], Can't proceed to dependent objects"
Cause: Multiple categories or subcategories with the same name exist (e.g., “Sandwich”).
Resolution: Ensure that all category, sub-category, and item names are unique. Avoid repetition in names within the same menu structure.
Error Message: "[name: Addon group with same name already exists, Cannot update/create addon group.]"
Cause: There is already an addon group with the same name in the menu.
Resolution: Change the addon group name to something unique. If there are multiple (20+) such errors, share the error report with the merchant and guide them on how to rectify each one.
Error Message: "Duplicate entity with same name already exists"
Cause: This occurs when an existing entity is archived and recreated with the same name, or when an entity is edited and ends up duplicating an existing one.
Resolution: Try to republish. This often requires menu clearance from Swiggy’s end for which kindly reach out to
Cause: Menu elements are not in the proper case (e.g., all lowercase or all caps).
Resolution: Follow Swiggy’s formatting standards:
Item, Category, Subcategory, Modifier Group & Modifier Names → Title Case (e.g., Chicken Biryani)
Connecting Words (with, in, on, etc.) → Lowercase
Descriptions → Sentence Case (e.g., A spicy rice dish made with chicken and herbs.)
Error Message: "entity with third_party_id: XXXXXXXX was rejected because: Cake Quantity/Flavour it is mandatory to update"
Cause: Cake items are missing quantity and flavour details in the item description.
Resolution: Update the description to clearly mention both quantity and flavour (e.g., 500g Butterscotch Cake).
Error Message: "Dependent Children Failed to Created/Update."
Cause: This is a system-side failure during menu injection on Swiggy's end.
Resolution: Try to push the menu again ,if the issue persists please reach out to
Always validate item names, descriptions, and structure before publishing.
Keep all names unique and meaningful.
For any recurring QC failures, reach out to your Swiggy POC for support.
Item Price (₹)
Allowed Packaging Charge (₹)
Less than 50
5
51 – 150
7
151 – 300
10
301 – 500
15
Above 500
20
UrbanPiper integration allows you to centrally manage your menu content for all ordering channels.
If your menu is managed on your POS, please ingest the menu from the POS to the UrbanPiper platform. Once the menu is updated on UrbanPiper, you can publish the changes to Swiggy by performing a menu publish.
You can track the status of your menu publishing requests in the Publish Logs.
If the publishing is successful, your changes will reflect on Swiggy.
If any errors occur, check the Error Report, make the required corrections, and republish the menu.
If you continue to experience issues with your menu publish, please for further assistance.
Our system couldn’t connect with Swiggy’s servers.
Re-try after some time. If it keeps failing, please reach out to support.
"Addon Max Limit should be in between -1 to 50"
Add-on group’s maximum selection exceeds 50.
Set the maximum selectable value between -1 and 50.
"Item Image URL must end with either .png or .jpg or .ashx"
The image file format is not accepted.
Use item image URLs ending in .png, .jpg, or .ashx only.
Proper default dependent details are mandatory in case of multiple variant groups
Some variants are missing nested group configurations.
Either associate the nested variant group with all variants, or remove the nested group completely.
Target server error
Menu push is queued up due to multiple pushes or server lag at Swiggy.
Wait for up to 4 hours. Before publishing the menu again.
Target server error with duplicate key error.
An item and a modifier have the same name, causing conflict.
Change the item name or modifier name to avoid duplication.
"Price should be in between 1 to 10000"
Item price is not within Swiggy’s accepted range.
Ensure the item price is between ₹1 and ₹10,000. Reduce if it exceeds ₹10,000.
"Item Price cannot be 0 if pricing combination is empty"
Item price is set to 0 and no variants are configured.
Either set a price at item level or add at least one variant.
"Given restaurant is not correct."
Your store isn’t integrated with Swiggy yet.
Trigger RTGL (Ready To Go Live) from your end. Our Onboarding team will handle it after that.
"Item Packing Charge cannot be greater than Item Price"
The packaging charge is higher than the item price.
Either increase the item price or reduce the packing charge (PC).
"size of variant_combinations in pricing_combinations should be equal to size of variant groups"
A variant group added to the item is also nested within another variant.
Review and remove duplicate nested variant groups that are already added as a direct add-on.
Unable to connect to upstream system. Please try again later.