GST Registration for Cloud Kitchen

Yes, but it depends on your turnover and how you sell. Cloud kitchens are classified as restaurant services under GST, governed by Section 22 of the CGST Act, 2017, which means registration becomes mandatory once your annual turnover crosses ₹20 lakh in most states, or ₹10 lakh in special category states such as the northeastern and hilly states.

However, even if your turnover is below this threshold, registration becomes compulsory regardless of revenue the moment you start selling through a food delivery aggregator such as Swiggy or Zomato that collects Tax Collected at Source (TCS), under Section 24(ix) of the CGST Act. Since almost every cloud kitchen relies on these aggregators for orders, GST registration is effectively required from day one for most operators.

If you operate purely through your own website or app and stay below the turnover threshold, you may not be legally required to register, but most cloud kitchens cross this threshold quickly or rely on aggregator platforms, making registration a practical necessity from the start.

Cloud kitchens fall under restaurant services for GST classification purposes, under Notification No. 46/2017 – Central Tax (Rate). As a service-classified business, the applicable registration threshold under Section 22(1) of the CGST Act is ₹20 lakh in annual turnover for most Indian states.

In special category states — including Himachal Pradesh, Uttarakhand, and the northeastern states such as Arunachal Pradesh, Sikkim, and Assam — this threshold is lower, at ₹10 lakh, reflecting the smaller average business scale typically seen in these regions under GST rules.

It is worth noting that this is the threshold for the general turnover-based requirement only. Selling through a food delivery aggregator overrides this threshold entirely and triggers mandatory registration from the very first sale, regardless of your actual turnover.

Yes. Under Section 24(ix) of the CGST Act, any business supplying goods or services through an e-commerce operator that is required to collect TCS must Register for GST, regardless of turnover. Both Swiggy and Zomato fall under this category, deducting 1% TCS on gross sales before remitting payments to the cloud kitchen.

This means that even a brand-new cloud kitchen with just ₹50,000 in monthly sales, selling exclusively through these aggregator platforms, is legally required to hold a valid GSTIN — the regular ₹20 lakh turnover exemption simply does not apply once aggregator sales are involved.

In practice, Swiggy and Zomato also require a valid GSTIN (along with your FSSAI license) as part of their onboarding process for restaurant and cloud kitchen partners, so registration is both a legal requirement and a practical prerequisite to getting listed on these platforms.

The core documents required are a PAN card for the business or proprietor, Aadhaar card for identity verification, proof of business address (such as a rental agreement, electricity bill, or property tax receipt for the kitchen premises), and bank account details for the business.

Depending on your business structure, you will also need entity-specific documents — a partnership deed for partnership firms, or the certificate of incorporation along with a board resolution for private limited companies. If the kitchen premises is rented, a No Objection Certificate (NOC) from the property owner is typically required alongside the rent agreement.

While not a GST document per se, having your FSSAI license ready before applying for GST is advisable, since aggregator platforms like Swiggy and Zomato require both registrations together during onboarding, and keeping them aligned in terms of business name and address avoids mismatches later.

Cloud kitchens are classified as restaurant services under GST and are subject to the same rate structure as regular restaurants. The standard applicable rate is 5% GST without Input Tax Credit (ITC), as stipulated under Notification No. 11/2017 – Central Tax (Rate), which applies to most cloud kitchen and food delivery operations regardless of whether the order is for dine-in, takeaway, or delivery.

There is also an alternative option to charge 18% GST with ITC available, though this option is typically more relevant to certain catering-classified services rather than standard cloud kitchen food sales, and eligibility depends on the specific nature of the supply.

It is important to distinguish this from packaged or branded food products, which may attract different GST rates — typically 5% or 18% depending on the specific product — if a cloud kitchen also sells packaged items such as sauces, snacks, or branded merchandise alongside its prepared food.

This depends on which GST rate you choose to charge on your sales. If you opt for the standard 5% GST rate on food sales — the most common choice for cloud kitchens — you cannot claim Input Tax Credit on your purchases, including raw materials, packaging, rent, and kitchen equipment. This rate is intentionally concessional but comes with the trade-off of forfeiting ITC.

If instead you opt to charge 18% GST with ITC (where eligible based on the nature of your services), you become entitled to claim credit for GST paid on inputs such as ingredients, packaging materials, equipment purchases, and various services used in running the kitchen, which can meaningfully offset your output tax liability.

Most cloud kitchens that primarily sell to retail customers through delivery platforms operate under the 5% no-ITC structure, since this is the default treatment for restaurant services and tends to keep consumer-facing prices more competitive on aggregator platforms.

Under the current rules for restaurant services supplied through e-commerce operators, the aggregator platform — Swiggy or Zomato — is treated as the deemed supplier for GST purposes on the food order itself. This means the aggregator collects 5% GST from the end customer and remits it directly to the government, rather than the responsibility falling on the individual cloud kitchen for that specific transaction.

This is a notable departure from how a typical seller-collects-tax model works (such as for Amazon or Flipkart product sales), and it shifts the compliance burden for output GST on the food sale itself to the platform. However, this does not exempt the cloud kitchen from GST registration or other compliance obligations.

Separately, the platforms also deduct 1% TCS under Section 52 of the CGST Act on the gross value of sales made through their app and remit it against the cloud kitchen's GSTIN, which the cloud kitchen must later reconcile and claim as credit through its own GST returns.

Tax Collected at Source (TCS) is a 1% deduction that e-commerce operators like Swiggy and Zomato are required to make under Section 52 of the CGST Act on the gross value of sales made through their platform, before settling Payment to the cloud kitchen. This deduction is separate from the 5% GST charged to the end customer on the food order itself.

The TCS amount deducted is deposited by the platform against the cloud kitchen's GSTIN and appears as a credit entry, which the kitchen owner must accept on the GST portal under the TDS and TCS Credit Received section before it can be claimed as credit against the kitchen's own GST liability when filing returns.

It is important to reconcile this TCS regularly against the platform's settlement reports, since unclaimed TCS credit effectively means leaving money owed to you sitting unclaimed in the government's system rather than offsetting your tax payable.

Yes, voluntary GST registration is available even if your cloud kitchen's turnover is below the ₹20 lakh threshold (₹10 lakh in special category states) and you are not yet selling through an aggregator that mandates registration regardless of turnover.

Voluntary registration offers several practical benefits even before it becomes mandatory: it allows you to claim Input Tax Credit on eligible purchases (if you opt for the 18% rate where applicable), builds credibility with B2B partners such as bulk caterers or corporate clients, and simplifies the process of registering on aggregator platforms or expanding to interstate supply later without having to Apply for GST under time pressure at that point.

Given that most cloud kitchens plan to onboard with Swiggy or Zomato fairly early in their operations — at which point registration becomes mandatory anyway — many founders simply complete GST registration during the initial setup phase alongside their FSSAI license application.

The process begins with applying online through the GST portal at gst.gov.in, under Services, then Registration, then New Registration. You enter your basic business details — PAN, business name, business structure, and state — to receive a Temporary Reference Number (TRN) via email and SMS.

You then log back in using the TRN to complete Form GST REG-01, upload your supporting documents (PAN, Aadhaar, address proof, business constitution documents, and bank details), and choose whether to complete Aadhaar authentication. Opting for Aadhaar authentication generally speeds up the process, whereas declining it means physical verification of your kitchen premises by a GST officer becomes mandatory.

After verifying all details and submitting digitally (via OTP or Digital Signature Certificate, depending on your business type), you receive an Application Reference Number (ARN) to track your application. Once approved by the GST officer, your GSTIN and registration certificate are issued, which you can then use for your FSSAI application, aggregator onboarding, and business bank account setup.

For a complete and accurate application, GST registration is typically processed within three to seven working days. This timeline applies to cloud kitchens in the same way it applies to any other business registering under GST, since the process itself is not specific to the food service industry.

If you choose not to complete Aadhaar authentication during the application, the process can take longer, since physical verification of your kitchen premises by a GST officer becomes mandatory in that case, adding scheduling time to the overall timeline.

Since GST registration is needed before you can complete onboarding with aggregator platforms like Swiggy and Zomato, it is advisable to start the GST application alongside your FSSAI license application, rather than waiting for one to finish before starting the other, to avoid delaying your launch date.

Yes, both are required, but they serve different purposes. The FSSAI license (or registration, depending on your turnover and scale) is mandatory under the Food Safety and Standards Act, 2006, and confirms that your food preparation operations meet hygiene, safety, and quality standards. GST registration, on the other hand, is a tax compliance requirement that allows you to legally collect and remit GST and operate as a registered business.

Aggregator platforms like Swiggy and Zomato will not onboard a cloud kitchen without a valid FSSAI license number, and in practice they also expect a valid GSTIN as part of seller verification, even in cases where GST may technically remain optional based on turnover alone, since selling through the platform itself triggers mandatory registration.

Beyond FSSAI and GST, depending on your city and kitchen scale, you may also need a local trade license, fire safety NOC, and shop and establishment registration — cloud kitchens are still subject to the full range of food business compliance requirements despite having no dine-in space.

No, GST registration is tied to the legal business entity and its place of business, not to individual brand names. If you operate multiple cloud kitchen brands (for example, separate biryani and pizza menus) from the same kitchen premises and the same legal entity, a single GST registration covers all of them.

This is different from FSSAI licensing, where each distinct food brand typically requires its own separate FSSAI license number, even if all brands are prepared in the same physical kitchen under the same business owner — a common point of confusion for multi-brand cloud kitchen operators.

For GST purposes, what matters is your legal business entity (proprietorship, partnership, or company) and the state in which you are registered. If you expand to a second kitchen location in a different state, that new location would require its own separate state-wise GST registration, regardless of how many brands operate from it.

A GST-registered cloud kitchen must file GSTR-1, reporting outward supplies, and GSTR-3B, the summary return covering tax liability and ITC, either monthly or quarterly depending on whether you have opted into the QRMP scheme. If filing quarterly, the Invoice Furnishing Facility (IFF) is also used for the interim months.

If your annual turnover exceeds ₹2 crore, an Annual Return (GSTR-9) is also required, reconciling your monthly or quarterly filings for the full financial year. Cloud kitchens with turnover exceeding ₹5 crore additionally fall under mandatory e-invoicing requirements.

Since most cloud kitchens sell through aggregators that deduct TCS, regular reconciliation of TCS credit reflected in GSTR-2B against the platform's settlement statements is an important additional step beyond standard return filing, to ensure all eligible credit is correctly claimed each filing cycle.

When delivery and packaging charges are bundled together with the food price as part of a single combined order value, they are generally treated as part of the overall food supply and taxed at the same 5% rate applicable to the food itself, since this is treated as a composite supply.

However, if these charges are itemised and billed separately as distinct line items rather than being included in the food price, packaging and delivery charges can attract GST at 18%, typically classified under HSN code 996813 for packaging services.

How an aggregator platform structures this on the customer-facing invoice is generally determined by the platform's own billing system, but it is worth understanding this distinction if you also sell directly through your own website or app and need to decide how to structure your own pricing and invoicing for delivery and packaging.

Under Section 122 of the CGST Act, 2017, failing to register for GST when legally required attracts a penalty equal to 10% of the tax due, subject to a minimum of ₹10,000. In cases where the failure is found to be a deliberate attempt at tax evasion rather than an oversight, the penalty can rise to 100% of the tax due, along with potential legal action.

Beyond financial penalties, the tax authorities also have the power to seize goods, freeze business bank accounts, or take other enforcement action against an unregistered business found to be liable for GST, which can be severely disruptive to ongoing operations.

Practically speaking, since aggregator platforms like Swiggy and Zomato require a valid GSTIN at onboarding, most unregistered cloud kitchens would be unable to operate through these channels at all — making this less of a "what if I get caught" scenario and more a basic operational requirement for accessing the primary sales channel most cloud kitchens depend on.

Yes, a residential address can generally be used as the place of business for GST registration, provided you can submit valid supporting documents such as a utility bill, property tax receipt, or rent agreement establishing your connection to that address, along with an NOC if the property is rented or owned by a family member.

Many home-based cloud kitchens — particularly smaller operations or those run by women entrepreneurs from a home setup — register using their residential address in this manner, which is fully permitted under GST rules as long as the documentation requirements are met.

It is worth checking your local municipal regulations and your aggregator platform's onboarding requirements separately, since some cities or platforms may have additional expectations around commercial kitchen certification or zoning, even if the GST registration itself does not strictly require a commercial address.

A cloud kitchen with turnover within the prescribed Composition Scheme limit can, in principle, opt for it as a restaurant service provider, which offers a concessional flat tax rate with simplified compliance in exchange for giving up Input Tax Credit eligibility.

However, this option is generally not available to cloud kitchens that sell through an e-commerce operator required to collect TCS, such as Swiggy or Zomato. Section 10(2)(d) of the CGST Act specifically bars businesses supplying through such platforms from the Composition Scheme, regardless of their turnover otherwise qualifying.

Since the overwhelming majority of cloud kitchens depend on aggregator platforms for the bulk of their orders, the Composition Scheme is rarely a practical option in this sector, and most operators end up registering as regular taxpayers under the standard 5% (no ITC) or 18% (with ITC) restaurant service rates instead.

If you expand within the same state — for example, opening a second cloud kitchen location in another part of the same city or state — your existing GST registration generally continues to cover the business, since GST registration is state-specific rather than location-specific within a state.

If, however, you expand to a kitchen in a different state, GST law requires a separate state-wise registration for that new location, since each state is treated as a distinct place of business for GST purposes, regardless of whether you are operating under the same brand name and legal entity.

This is a common consideration for cloud kitchen chains using a hub-and-spoke model across multiple cities, since each new state-level kitchen typically needs its own GSTIN, its own state-specific FSSAI compliance, and separate state-level filing obligations, even while operating under unified branding and centralised business management.

There is no strict legal sequencing requirement between the two — you can apply for GST registration and your FSSAI license at the same time, since they are separate processes managed by different authorities (the GST portal and the FSSAI's FoSCoS portal respectively) with no formal dependency on each other's approval.

That said, since aggregator platforms like Swiggy and Zomato require both a valid FSSAI license number and a valid GSTIN to complete onboarding, most cloud kitchen founders apply for both in parallel during the setup phase, so that neither registration becomes a bottleneck for getting listed and accepting orders once the kitchen is ready to launch.

Keeping the business name, address, and ownership details consistent across both applications also helps avoid verification mismatches later when aggregator platforms cross-check your FSSAI and GST details against each other during the onboarding review.