Effortless Menu Updates: Keeping Your Swiggy Menu Fresh with UrbanPiper!
Keeping your menu accurate and up-to-date across all your online ordering channels is crucial for a smooth operation and happy customers. UrbanPiper's powerful integrations allow you to centrally manage your menu content, saving you time and ensuring consistency!
No more logging into multiple platforms for every small change – manage it all from one place.
How to Update Your Swiggy Menu via UrbanPiper
The process depends on where your primary menu source is.
Option 1: Your Menu is Managed on Your POS System
If your Point-of-Sale (POS) system is your primary source for menu content and updates, here's the flow:
Update your menu directly in your POS system.
Ingest the Menu to UrbanPiper: Ensure your POS is configured to automatically or manually push (ingest) menu changes from your POS to the UrbanPiper platform. This syncs the latest menu data to your UrbanPiper Atlas dashboard.
If you're unsure about this step or facing issues, please refer to your POS integration guide or contact our support team for assistance with POS ingestion.
Option 2: Your Menu is Configured Directly on UrbanPiper Atlas
If you use the UrbanPiper Atlas dashboard to build and manage your menu content:
Make your menu changes directly in the "Catalog" section of your Atlas dashboard.
Need help with menu configuration in Atlas? Please refer to the "Get Started" section within your Atlas dashboard, or check our Knowledge Base for detailed guides on adding items, categories, pricing, and modifiers.
Final Step: Publishing Your Menu to Swiggy
Once your menu is updated on the UrbanPiper platform (either via POS ingestion or direct Atlas configuration), the final step is to publish these changes to Swiggy:
Log in to your UrbanPiper Atlas dashboard.
Navigate to the "Location" section from the left-hand menu.
Select your specific restaurant location.
Click on the "Publish" button.
From the list of aggregators, select "Swiggy."
Click "Publish" again to confirm.
Your updated menu will now be pushed to Swiggy!
Handling errors:-
Error Message
What It Means
How to Fix It
"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.
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.
Last updated
Was this helpful?