Building software or managing backend architecture for food tech apps, cloud kitchens, or multi-outlet restaurant chains requires more than just clean API integrations and payment gateways. You also need to navigate India's complex Goods and Services Tax (GST) compliance layers.
For founders, tech leads, and digital commerce operators, understanding the flat 5% GST structure without Input Tax Credit (ITC) and the automated tax collection mechanics under Section 9(5) of the CGST Act is critical to avoiding compliance errors.
1. The Core 5% GST Model Without Input Tax Credit
Under Notification No. 11/2017-Central Tax (Rate), food supply services provided by restaurants and delivery-only cloud kitchens fall under SAC 9963.
- The Rate: A uniform 5% GST (2.5% CGST + 2.5% SGST or 5% IGST) applies across dine-in, takeaway, and digital delivery orders.
- The Blocked ITC Rule: Operating under this concessional 5% tax slab strictly prohibits claiming Input Tax Credit (ITC) on business inputs. Taxes paid on raw materials, commercial rent, kitchen hardware, packaging supplies, and aggregator commissions cannot be offset against your output liability.
- The Hotel Exception: The 18% GST rate with full ITC benefits applies only to restaurants located inside commercial hotel premises where the declared room tariff exceeds 7,500 INR per night. Standalone cloud kitchens cannot use this rate.
2. Section 9(5) Deemed Supplier Logic for Swiggy & Zomato
Under Section 9(5) of the CGST Act, 2017, E-Commerce Operators (ECOs) like Swiggy and Zomato are categorized as "deemed suppliers" responsible for collecting and remitting GST on restaurant services sold through their platforms.
How the Transaction Flow Works:
- Checkout & Tax Collection: When an end user places an order on Swiggy or Zomato, the platform calculates and collects 5% GST on the food value.
- Direct Remittance: The aggregator remits this 5% tax directly to the government cash ledger. The restaurant receives its net payout without handling the tax component.
- GSTIN Handshake: Even though tax liability shifts to the platform, food aggregators require a valid 15-digit GSTIN during restaurant onboarding for audit and reporting handshakes.
3. GSTR-1 & GSTR-3B Return Reporting Protocols
To prevent double taxation and portal mismatch errors during monthly return filings, transactions must be segregated correctly:
- Direct Counter / App Sales: Reported in GSTR-1 (Table 4/7) and GSTR-3B under Table 3.1(a) (Taxable Outward Supplies). The restaurant collects and pays 5% tax directly.
- Swiggy / Zomato Orders (u/s 9(5)): Reported in GSTR-1 under Table 14 (Supplies made through ECO) and GSTR-3B under Table 3.1.1(ii) (Supplies on which ECO is liable to pay tax). Output tax payable by the restaurant for these orders is 0 INR.
Summary Compliance Matrix for Digital Food Outlets
| Sales Channel / Item | Applicable GST Rate | Tax Collection Responsibility | ITC Eligibility for Kitchen |
|---|---|---|---|
| Direct Takeaway / Dine-in | 5% (2.5% CGST + 2.5% SGST) | Restaurant / Cloud Kitchen | Blocked (0%) |
| Swiggy / Zomato Orders | 5% (Remitted u/s 9(5)) | E-Commerce Operator (Swiggy/Zomato) | Blocked (0%) |
| Platform Commission Fees | 18% GST on Commission | Charged by Swiggy/Zomato to Outlet | Non-Recoverable Expense |
| Customer Delivery Fees | 18% GST on Delivery Fee | Collected and Remitted by ECO | Not Applicable |
Professional Guidance & Advisory
Automating multi-channel sales reconciliation, avoiding double tax exposure on aggregator payouts, and maintaining clean GSTR-3B audit logs require specialized tax engineering.
For comprehensive statutory breakdowns, explore the full publication on GST for Restaurants maintained by the experts at Delhi Tax Solutions.
Top comments (0)