What documents do Zomato and Swiggy typically ask for in India?
If you want to go live on a food aggregator this month, the fastest mental model is simple: Zomato and Swiggy usually want proof that the outlet exists, the kitchen is licensed, the business can be paid, and the menu can actually go live without customer complaints. In practice, founders are commonly asked for some mix of:
- FSSAI licence / registration with the correct business name and premises details
- GSTIN where required for the business structure or onboarding flow
- PAN of the proprietor or entity
- Bank account proof such as cancelled cheque, bank statement, or account verification
- Owner / authorised signatory ID for KYC
- Outlet and kitchen photos
- Menu details with item names, prices, and categories
- Packaging photos or packaging readiness details for delivery-first brands
- Entity proof such as proprietorship, partnership, LLP, or company documents where applicable
That list is intentionally framed as typically required, not guaranteed. Aggregator onboarding forms change, city teams request additional evidence, and partner apps sometimes ask different questions for a cloud kitchen versus a dine-in restaurant. Treat this guide as a speed checklist, then confirm the current requirements inside the official partner app before you submit.
For most founders, the real delay is not menu upload. The delay is that FSSAI and GST are the first serious compliance checks. If those two are unclear, everything else becomes slower: bank verification, listing approval, settlement setup, and billing.
Why FSSAI and GST are the usual blockers
The two documents operators struggle with most are the same two documents aggregator teams care about most:
- FSSAI proves you are legally allowed to sell food.
- GST helps the platform, payouts, invoicing, and tax records stay consistent.
FSSAI is usually the hard stop. A food-delivery listing without a valid FSSAI number is difficult to move forward because the platform has to show a compliant food business, not just a logo and a menu. If your FSSAI name, address, or outlet category is mismatched against what you submit in onboarding, review cycles drag out quickly.
GST is the second big blocker because aggregator commerce creates accounting complexity even for small operators. Settlements, commissions, TCS, and invoice trails are easier to reconcile when the business is set up correctly from the start. Even where a founder is still discussing threshold questions with a CA, the platform will usually expect clean tax identity details before commercial activation feels smooth.
If your goal is speed, do the boring work first:
- Get the FSSAI number correct for the outlet and premises
- Confirm whether you need to register or update GST for your situation
- Make sure PAN, bank account name, and legal business name all align
That sequence saves more time than polishing menu descriptions for a week.
A practical view of the typical onboarding packet
Think of the listing packet in four buckets:
| Bucket | What the platform is trying to verify | Typical items |
| --- | --- | --- |
| Food compliance | Can this outlet legally sell food? | FSSAI number, licence copy, premises details |
| Business identity | Who owns the outlet? | PAN, entity documents, owner ID, signatory proof |
| Payout readiness | Can settlements be paid correctly? | Bank KYC, account proof, cancelled cheque |
| Storefront readiness | Can customers order confidently? | Menu, outlet photos, kitchen photos, packaging readiness |
Founders often underestimate the last bucket. Aggregators are not just validating compliance; they are also validating listing quality. If the menu is incomplete, the outlet photos are unclear, or the delivery packaging looks unreliable, the listing may not be rejected outright, but it can still slow down activation and performance.
For that reason, founders who go live fastest usually prepare the whole packet at once rather than waiting for one query at a time.
Cloud kitchen vs dine-in outlet: what changes for listing?
The document categories stay broadly similar, but the evidence you provide can differ.
Cloud kitchen / delivery-only brand
A cloud kitchen usually has to prove the production kitchen is real and compliant even if there is no walk-in dining room. That means platform teams may focus more on:
- Kitchen premises match
- Production area photos
- Delivery packaging readiness
- Brand name consistency across FSSAI, invoices, and menu assets
Because there is no dine-in storefront to reassure the reviewer, the kitchen identity has to carry more weight. If the trade name used on the listing is different from the legal entity or FSSAI record, clarify that early.
Dine-in restaurant or cafe
A dine-in outlet often has an easier time proving customer-facing existence, but reviewers may scrutinize:
- Exterior storefront photo
- Signboard / brand visibility
- Kitchen plus service-area consistency
- Menu-price consistency with the live brand
In other words, cloud kitchens are judged more on backend readiness; dine-in outlets are judged on both backend readiness and public-facing consistency.
Neither format is automatically easier. The faster operator is usually the one with cleaner documentation and consistent names, not the one with more beautiful interiors.
Do you always need GST for Zomato or Swiggy onboarding?
This is where founders want a yes-or-no answer and rarely get one.
At a high level, aggregators, e-commerce rules, settlement mechanics, and restaurant tax treatment make GST readiness extremely important even when a founder initially assumes turnover is too small to matter. The exact legal position depends on turnover, business structure, place of supply, scheme choice, and current law. That is why the right operating approach is:
- Do not assume a friend's setup applies to you
- Do not rely on an old YouTube comment about thresholds
- Do confirm your current position with a CA before onboarding at scale
This article is not tax advice. It is a commercial readiness guide. The safe founder move is to treat GST as part of aggregator launch planning, not as an afterthought for next quarter.
If you need the broader tax context around food delivery, commission, and payout reconciliation, read our guide on GST for cloud kitchens and food delivery along with our GST registration guide.
Commission, TCS, and settlement awareness before you go live
You do not need to become a tax specialist to launch, but you do need to understand the flow of money.
Most founders think in terms of menu price and payout. Aggregator settlements are more layered:
- The platform may deduct commission or service fees
- It may apply delivery-related commercial adjustments
- It may report TCS and other tax-related entries depending on the transaction structure
- You still need your own books to reconcile gross orders, deductions, and net payout
That is why founders feel confused after the first settlement cycle. The outlet is live, orders are coming in, but the payout sheet does not resemble the menu total in their head.
The solution is not to avoid aggregators. The solution is to launch with a GST-ready billing and reconciliation process. A modern restaurant POS software stack helps because it keeps invoicing, order values, and reporting cleaner from day one. Pair that with CA guidance if you are unsure how Zomato or Swiggy deductions should appear in your books.
Again, this is high-level awareness only, not tax advice. Rules and invoicing treatment can change, and your CA should confirm the current treatment for your business.
Checklist before you apply
Use this list before opening the partner app form:
| Before you apply | Why it matters |
| --- | --- |
| FSSAI copy is ready and readable | Reviewers need a valid food-compliance record |
| GST position is confirmed | Prevents last-minute onboarding confusion |
| PAN, entity name, and bank name match | Reduces KYC and payout delays |
| Outlet photos are current | Avoids re-upload requests |
| Menu is final enough to publish | Saves remapping during activation |
| Packaging is ready for delivery | Prevents poor first-order experience |
| Owner or signatory ID is accessible | Speeds KYC completion |
If even two of these are still unresolved, pause the onboarding form and fix them first. The fastest applications are the ones submitted once, not the ones resubmitted three times.
Checklist during onboarding
While submitting to Zomato or Swiggy, keep this operating discipline:
- Use the same business spelling everywhere. Brand name differences are manageable; legal-name contradictions are not.
- Upload clean scans, not cropped screenshots. Many delays are caused by unreadable documents.
- Match the outlet address exactly to your compliance records wherever applicable.
- Prepare menu categories thoughtfully. Bad initial mapping hurts first-week conversion.
- Respond to queries fast. A 24-hour response window feels much faster than reopening the process after a week.
If the partner team asks for something not listed in this article, that does not mean the request is abnormal. It usually means the workflow, city, or outlet type triggered an extra validation step.
Checklist after go-live
Approval is not the finish line. The real work starts after the outlet is visible:
| After go-live | What to check |
| --- | --- |
| Menu accuracy | Prices, variants, add-ons, and availability are correct |
| FSSAI display | Number appears where legally required on packaging or invoices |
| Bank settlements | First payouts reconcile against orders and deductions |
| GST-ready billing | Records are clean before month-end chaos begins |
| Ops readiness | Prep times, packaging, and dispatch flow are stable |
| Review management | First customer reviews are answered promptly |
Many founders win approval and still lose momentum because the backend is manual. If invoice records, menu updates, and dispatch flow live in three different places, aggregator success creates its own mess.
A 30-day founder plan to go live this month
If you are trying to compress the launch timeline, use this practical sequence:
Week 1: compliance first
- Finalise FSSAI status
- Confirm GST position
- Align PAN, bank, and entity details
Week 2: listing packet
- Shoot outlet and kitchen photos
- Finalise delivery packaging
- Clean up menu names, prices, and categories
Week 3: onboarding
- Submit in the partner app
- Reply quickly to review queries
- Prepare opening hours, service area, and dispatch workflow
Week 4: go-live controls
- Test first settlements
- Reconcile orders with billing
- Fix menu and packaging issues based on live feedback
This is also the right time to install systems that help after approval, not just before approval. Going live on aggregators without GST-ready billing or clean order operations creates avoidable cleanup work in the first month.
Where TasteIQ fits: compliance help first, then GST-ready operations
TasteIQ is not affiliated with Zomato or Swiggy, does not control their onboarding forms, and cannot guarantee listing approval. What TasteIQ can do is help founders reduce the usual bottlenecks around compliance readiness and post-approval operations.
If you need help getting the basics in order, start here:
- FSSAI help: /fssai-license
- GST help: /gst-registration
Once the outlet is ready to sell, the next problem is usually operational: invoices, menu control, order flow, and cleaner reconciliation. That is where restaurant POS software matters. TasteIQ's software stack is built for founders who want GST-ready billing and a smoother operating layer after launch, not just a prettier menu PDF.
If you want a human to sanity-check your launch docs and next steps, message TasteIQ on WhatsApp and ask for compliance assist.
If you are already document-ready and want the software side, you can also start your free trial and set up GST-ready billing before aggregator volume gets messy.
Related reading for aggregator and compliance founders
If this article is the immediate-launch checklist, these guides help with the next layer of detail:
- Cloud kitchen licenses in India
- GST for cloud kitchens and food delivery
- FSSAI licence documents, fees, and timeline
- GST registration for restaurants in India
Final disclaimer before you submit
Platform forms, city workflows, tax treatment, and reviewer checks can change. TasteIQ is not affiliated with Zomato or Swiggy, and this guide does not guarantee listing approval, legal eligibility, or tax treatment. Always confirm current requirements in the relevant partner app and, where needed, with your chartered accountant or licensing advisor.
The commercial takeaway is still straightforward: if you want to go live this month, prepare FSSAI, GST, PAN, bank KYC, photos, and menu as one packet, then set up GST-ready billing before order volume makes reconciliation painful. That is how founders launch faster and stay calmer after go-live.
