Is GST effectively mandatory for a cloud kitchen on Swiggy or Zomato?
For most founders, the practical answer is yes, plan as if GST registration is required before you go live on a major aggregator. The reason is not only turnover. Once a cloud kitchen supplies through an e-commerce operator such as Swiggy or Zomato, the Section 24 / e-commerce operator discussion enters the picture, along with onboarding requirements, settlement statements, and monthly reconciliation.
This is where cloud kitchens get different advice than a small neighbourhood dine-in restaurant. A standalone outlet might first ask whether its aggregate turnover has crossed the notified GST threshold. A delivery-first kitchen listing on an aggregator is usually told to think one step earlier: "Will the platform, operator tax rules, and current GST notifications make registration effectively unavoidable anyway?"
Because the legal treatment of restaurant services supplied through e-commerce operators has evolved through notifications, and because platform processes often move faster than founder understanding, treat this guide as educational, not tax advice. Before filing or going live, confirm your exact position with a chartered accountant and the latest guidance on gst.gov.in.
Why cloud kitchens face a different GST journey than dine-in restaurants
A dine-in-first restaurant can sometimes launch locally, bill a smaller customer base, and watch turnover before registration becomes urgent. A cloud kitchen does not operate in that order.
It usually starts with:
- Aggregator onboarding
- Menu upload and payout setup
- Commission and settlement documentation
- Monthly operator statements
- Customer invoices, refunds, and reconciliations
That structure means tax hygiene becomes part of launch operations, not a later finance task.
If you want the broader threshold-based restaurant view first, read our main guide on GST registration for restaurants in India. The key difference is simple: cloud kitchens often feel GST pressure earlier because e-commerce operator rules and aggregator paperwork show up before the founder feels "big enough" for formal tax systems.
In plain English:
- A small dine-in cafe may ask, "Have I crossed the turnover limit yet?"
- A cloud kitchen may need to ask, "Can I even run Swiggy/Zomato cleanly without GST registration and monthly reconciliation?"
That is why many CAs tell delivery-first food brands to complete GST setup before marketplace launch instead of waiting for confusion to build.
Where Section 24 and the aggregator angle matter
Founders often hear a simplified rule: "If you sell through an e-commerce operator, GST registration becomes mandatory." That summary points toward Section 24 logic, but you should not rely on a one-line WhatsApp version of the law. Restaurant services supplied through platforms have had special treatment changes, and the interaction between:
- Section 24 compulsory registration concepts
- e-commerce operator supply rules
- platform-side tax handling
- TCS or operator statement reconciliation
- current CBIC notifications
can be more nuanced than a friend's accountant makes it sound.
The safe operating takeaway is this: if your cloud kitchen wants to list on Swiggy or Zomato, act early as though GST readiness is a launch requirement and get a CA to confirm the exact legal basis for your entity and supply model.
That approach solves two real business problems:
- It reduces the risk of delayed onboarding because your GSTIN, entity papers, and bank setup are not ready.
- It prevents a bad first quarter where payouts arrive but the founder cannot reconcile commissions, operator statements, tax amounts, and books.
For SEO searchers asking "GST for cloud kitchen" or "GST mandatory Swiggy Zomato", this is usually the commercially useful answer: whether the compulsion arises from threshold, Section 24, operator-specific treatment, or a current notification, you should plan GST before aggregator launch, not after.
What GST rate do cloud kitchens and restaurant deliveries usually discuss?
For restaurant service in India, founders commonly hear the phrase "5% GST without ITC". That rate is often cited for standalone restaurant service, takeaway, and delivery, but you must verify the current position on gst.gov.in before configuring billing, publishing prices, or advising your staff.
Why the caution matters:
- Restaurant GST notifications have changed multiple times since GST rollout.
- Hotel-linked restaurants can attract different treatment.
- Composition and regular registration have different implications.
- Platform-supplied restaurant orders may require specific interpretation by your CA.
So the correct founder rule is not "blogs say 5%, so I am done." The correct rule is:
Use 5% without ITC only as a common starting reference, then verify the present notification framework, your eligibility, and your invoicing setup with a CA.
That verification should happen before:
- menu taxes are configured in your billing software
- aggregator menu prices are finalized
- invoices start going out to customers or office clients
- accountants map monthly GST returns
Incorrect tax settings create downstream pain. One wrong assumption can affect invoices, settlements, GSTR reporting, and pricing margin all at once.
What founders should understand about aggregator invoices, payouts, and TCS-style reconciliation
Most cloud kitchen founders do not get into trouble because they forgot the word "GST". They get into trouble because they do not reconcile operator paperwork every month.
When you sell through Swiggy or Zomato, you may see:
- order-level sales summaries
- commission invoices from the platform
- promotional or discount adjustments
- refunds or cancellations
- payout statements
- tax deductions, collections, or operator-side tax statements that your CA must map correctly
Many founders casually label all of this "TCS". In practice, the exact statement set and tax treatment can differ depending on the supply structure and current law. For restaurant services via aggregators, your CA should confirm which statements matter, whether any TCS reporting applies in your case, and how the platform's documentation maps into your books and GST returns.
The operational lesson is universal even when the legal detail varies: never treat aggregator settlement reports as self-explanatory cash entries.
Each month, reconcile at least these items:
- Gross order value shown by the platform
- Platform commissions and fees
- Refunds, cancellations, and promos
- Net payout credited to your bank
- Platform tax documents or statements
- Your outward supply records and return preparation
If those six do not tie, the business will eventually leak either compliance time or margin.
This is one of the strongest reasons to use GST-aware restaurant software after registration. A clean restaurant POS software stack gives you structured invoices, order records, and exports your CA can reconcile faster than screenshots and payout PDFs.
Documents needed for GST registration for a cloud kitchen
Most cloud kitchens need the same core GST registration pack as other restaurant businesses, with extra care around premises proof because home kitchens, shared kitchens, and rented commercial kitchens often have messy paperwork.
Keep these ready before starting the application:
- PAN of the proprietor or business entity
- Aadhaar of proprietor, partners, or directors
- Business constitution proof such as proprietorship details, partnership deed, LLP agreement, or certificate of incorporation
- Photograph of proprietor or authorized signatory
- Principal place of business proof
- Rent agreement or ownership document
- Latest electricity bill or utility proof
- No-objection certificate from owner if required
- Bank proof such as cancelled cheque, statement, or passbook page
- Authorized signatory letter or board resolution where applicable
- Digital Signature Certificate for companies and LLPs
- FSSAI registration or licence copy if already available
For F&B founders, the paperwork issue is often not absence of documents but name and address mismatch across PAN, bank, rental proof, and kitchen address. Fix that first. A delivery business cannot afford to delay onboarding because one document says "Floor 2" and another says "Second Floor".
If you are still sorting food licensing, also review our guide to cloud kitchen licenses in India and the FSSAI comparison post on basic vs state vs central licence.
How to approach GST registration if you are launching a cloud kitchen now
This is the cleanest founder sequence in 2026:
1. Finalize the legal entity first
Confirm whether you are operating as a proprietorship, partnership, LLP, or private limited company. The GST application should match the actual commercial structure used for bank account, contracts, and aggregator onboarding.
2. Get your kitchen address papers in order
This sounds basic, but it is where many applications slow down. Make sure the principal place of business proof, landlord NOC where needed, and utility support are consistent.
3. Confirm the aggregator interpretation with a CA
Do this before you assume threshold-based delay is safe. Ask specifically:
- Does my Swiggy/Zomato launch make GST registration effectively mandatory now?
- Which current notification or section drives that position?
- How should restaurant service through an e-commerce operator be treated for my structure?
- What operator statements do we need to reconcile monthly?
4. Apply on gst.gov.in with complete documentation
Use the official portal and keep the ARN safely recorded. If Aadhaar authentication is available and correctly completed, processing is often smoother.
5. Configure billing and accounting before the first large settlement cycle
Do not wait for the end of month to "figure GST later." Once payouts begin, the founder needs clean records immediately.
After GST registration, billing discipline matters more than the certificate
Getting the GSTIN is not the finish line. It is the start of recurring compliance.
Once registered, your cloud kitchen should have:
- GST-configured invoices
- clean order records by channel
- consistent serial numbering
- bank reconciliation against settlements
- monthly return preparation support
- one owner responsible for documents and due dates
This is where software pays for itself. A GST-ready restaurant POS software plus clear plan visibility on pricing helps founders avoid the usual chaos:
- wrong tax configuration
- duplicate manual invoices
- messy aggregator reconciliation
- delayed CA handoff
- payout confusion across channels
TasteIQ is built for food operators who do not want to run tax-sensitive billing out of spreadsheets. If you are comparing tools, start with the workflow that actually matters after registration: invoice structure, channel-wise reporting, order exports, and reconciliation readiness.
Difference between "I can start taking orders" and "I am compliance-ready"
Cloud kitchens often confuse marketplace visibility with operational readiness. Listing on an app is not the same as being ready for tax, books, and settlement control.
A founder is only truly ready when:
- GST position is confirmed with a CA
- FSSAI and business documents are organized
- aggregator paperwork is understood
- billing system is configured correctly
- payouts can be reconciled without guesswork
That is why the smartest delivery-first founders do two things together:
- They complete the compliance layer early.
- They implement billing software before transaction volume gets noisy.
What to do next if you are launching on Swiggy or Zomato
If you are about to launch, the safest path is straightforward:
- Read the official GST guidance on gst.gov.in.
- Get a CA to confirm whether your cloud-kitchen-through-aggregator model is compulsorily registrable now under the current law and notification set.
- Start your document pack before platform onboarding stalls.
- Set up billing that can survive settlements, operator statements, and return filing.
If you want help on the execution side, start at /gst-registration or message TasteIQ on WhatsApp: https://wa.me/916207466460?text=Hi%20TasteIQ%2C%20I%20need%20help%20with%20GST%20registration%20for%20my%20cloud%20kitchen.
Once your registration path is clear, explore TasteIQ's restaurant POS software, review pricing, or go directly to signup at https://partners.tasteiq.in/signup. The goal is simple: get compliant early, get billing right, and make sure aggregator growth does not break your books in month one.
This article is not tax advice. GST treatment, rates, thresholds, e-commerce operator implications, and compliance requirements can change. Always confirm with your chartered accountant and the latest material on gst.gov.in.
