Section 9(5) CGST Deemed Supplier — Cloud Kitchen FMCG Bridge

An FMCG manufacturer’s GST controller closes the books on 30 September with a Section 52 TCS credit claim of ₹14.6 lakh in GSTR-2X across four quick-commerce ECOs and a parallel ingredient-supply register of ₹38.4 crore in cloud-kitchen B2B invoices for the trailing twelve months. The two flows are routinely confused by junior tax teams — both involve e-commerce operators, both involve restaurant-adjacent buyers, and both engage GST provisions that took final shape between 2022 and 2024. But the two flows are governed by entirely separate provisions: Section 9(5) CGST on the food-service leg the cloud kitchen sells to the consumer (Swiggy or Zomato as deemed supplier, 5% without ITC) versus Section 9(1) on the FMCG manufacturer’s ingredient supply into the cloud kitchen (normal forward charge at the ingredient HSN). When the same FMCG brand also sells the same molecule as a packaged consumer product through Blinkit, a third provision engages — Section 52 TCS at 0.5%. Section 9(5) CGST cloud kitchen FMCG classification, drawn correctly across these three lines, is the difference between a clean GSTR-1 cycle and a Section 73/74 notice on mis-classified supplies.

Quick reference

The reconciliation in one paragraph

The provision boundary between Section 9(5) and Section 9(1) is not academic — it determines which legal entity pays GST, at what rate, on what value, with or without ITC. For an FMCG manufacturer with a national portfolio that touches cloud-kitchen B2B ingredient supply (HUL into a Rebel Foods or Curefoods kitchen serving on Swiggy and Zomato), quick-commerce packaged-goods supply (HUL into Blinkit, Zepto, Instamart), and modern-trade general-trade flows, the channel-mix register must classify every outward supply correctly because the GSTR-1 sub-total per classification, the GSTR-3B liability per HSN, and the GSTR-2X TCS credit claim each draw from a different leg. Mis-classification compounds across the cycle: an ingredient-supply invoice mis-flagged as a Section 9(5) deemed-supplier event drops the brand’s output liability illegitimately on a leg where it had legitimate forward-charge exposure, while a goods supply through quick-commerce mis-flagged as a Section 9(5) service skips the 0.5% TCS reconciliation entirely. The cleanest discipline maintains a four-bucket register — B2B ingredient (cloud kitchen, foodservice, restaurant chain), quick-commerce packaged goods (with TCS), general-trade and modern-trade flows, and any contract-manufacturing co-pack engagements — and reconciles each bucket on its own statutory clock.

What the cloud-kitchen FMCG supply chain actually looks like in India

A cloud kitchen is a delivery-only food-service business. It carries no dine-in seats, operates from a low-rent commissary kitchen often in an industrial estate or a mixed-use building basement, and sells exclusively through aggregator apps — Swiggy, Zomato, and increasingly through the brand’s own ordering app. The cloud-kitchen operator ranges from a small single-kitchen entrepreneur up to large national chains — Rebel Foods (Faasos, Behrouz, Oven Story, Lunchbox), Curefoods (EatFit, Sharief Bhai, Cake Zone), Box8, Biryani by Kilo. Cloud kitchens consume FMCG ingredients at industrial scale: dairy concentrates, sauces, mayonnaise, packaged batter mixes, frozen pre-cuts, packaged spice blends, sweetened beverage concentrates including malt-based drinks like Horlicks used as a dessert-shake ingredient. The FMCG manufacturer’s go-to-market into cloud kitchens runs through a HoReCa (Hotels, Restaurants, Catering) channel — sometimes called Foodservice or Out-of-Home (OOH) — separate from its general-trade and modern-trade flows. The HoReCa team manages a B2B sales motion: meeting cloud-kitchen procurement managers, designing pack-sizes suited to commercial-kitchen use (5 kg dairy-base bags, 20 kg concentrate jars rather than retail consumer packs), running ingredient-development programmes where the brand co-creates a syrup or mix for a specific cloud-kitchen menu item. The invoicing flow is B2B GSTIN-to-GSTIN: HUL raises a tax invoice on the cloud-kitchen entity at the ingredient HSN’s prevailing GST rate, the cloud kitchen claims input tax credit, and the supply is reflected in HUL’s GSTR-1 outward register as a B2B taxable supply. Downstream of the cloud-kitchen’s kitchen door, an entirely different flow begins. The cloud-kitchen plates and packages the cooked menu item — a dessert shake using HUL’s Horlicks concentrate as a base — and lists it on Swiggy or Zomato at a consumer price. When a consumer orders the shake, Swiggy collects the consumer payment, deducts its platform commission, deducts the GST on the food-service value as the Section 9(5) deemed supplier (5% without ITC since 1 January 2022), and settles the net amount to the cloud kitchen. The cloud kitchen records the receipt as ECO-routed restaurant-service revenue, notes the GSTIN of the ECO that deemed-supplied, and includes the value in its GSTR-1 with the appropriate Schedule III narration.

The regulatory overlay — Section 9(5) versus Section 9(1) versus Section 52

The three provisions stack as follows. Section 9(5) CGST is a reverse-charge style deeming provision. It empowers the government to notify categories of services where the ECO is treated as the supplier for the purpose of paying tax — even when the actual supplier is an unregistered or small registered service provider operating through the platform. The current notified list under Section 9(5) read with Notification 17/2017-CTR (as amended) contains four services: passenger transport via cab aggregator (Ola, Uber); housekeeping under specified tariff (Urban Company); restaurant service including cloud kitchen (Swiggy, Zomato — effective 1 January 2022 via Notification 17/2021-CTR); and hotel accommodation under specified tariff (the OYO-style aggregation). The rate on restaurant service is 5% without ITC — meaning the ECO discharges output tax at 5% on the food-service consideration but cannot claim ITC on its own platform inputs against that liability. Critically, Section 9(5) does not extend to goods at all. A goods supply through any ECO platform — whether the platform happens to also run a Section 9(5) service business — remains under the normal Section 9(1) forward-charge regime with the underlying merchant as the legal supplier. Section 9(1) CGST is the default forward-charge mechanism that governs the overwhelming majority of GST supplies in India. The registered supplier raises a tax invoice at the HSN-determined rate, the recipient pays the gross-of-tax amount, the supplier remits the tax to government, and the recipient claims ITC subject to the standard Section 17 restrictions. HUL’s invoice on a Horlicks concentrate to a Rebel Foods kitchen is Section 9(1) territory: HUL is the supplier, the cloud kitchen is the GSTIN recipient, the rate is per the ingredient HSN (currently 5% on most dairy-based ready-to-drink mixes under the GST 2.0 consolidation, though the brand should verify the specific HSN for the concentrate SKU), and the cloud kitchen claims ITC on the input. Section 52 CGST is a TCS collection mechanism distinct from both. When an ECO collects consideration on behalf of an underlying merchant for a taxable goods supply, the ECO must collect TCS at 0.5% (effective 10 July 2024 per Notification 15/2024-CT, reduced from the previous 1% rate) on the net value of taxable supplies. The underlying merchant remains the legal supplier and charges its own GST at the goods HSN rate; the TCS sits as an additional collection mechanism layered on top of the goods supply, and the merchant claims the TCS credit in GSTR-2X. The full mechanics are walked in Section 52 TCS on quick-commerce FMCG supplies. The boundary lines are summarised below.

A worked example — HUL Horlicks-flavoured concentrate into a cloud-kitchen menu

HUL launches a horeca-pack variant of the Horlicks-flavoured concentrate aimed at the cloud-kitchen dessert and breakfast category — a 5 kg powder concentrate that reconstitutes into a base for milkshakes, breakfast bowls, and dessert layers. The brand signs a national supply agreement with a large multi-brand cloud-kitchen operator (illustrative — call it CloudFoods India Pvt. Ltd.) that operates 187 cloud-kitchen sites across nine cities, with menu items running through six in-house brands on Swiggy and Zomato. Over the financial year FY 2025-26, the supply runs to approximately ₹38.4 crore in B2B ingredient invoices. Illustrative — the example brand and counterparty are representative; public disclosures do not reveal the specifics of any HoReCa supply contract. Cross-verify against your own GSTR-1 export and the cloud-kitchen counterparty agreement before action. The flow walks through four stages on a typical month. Stage 1 — HUL B2B ingredient supply to the cloud kitchen. HUL raises a tax invoice on CloudFoods India Pvt. Ltd. for ₹32.4 lakh in the month of October 2025 covering 8,100 units of the 5 kg concentrate pack at ₹400 per unit (illustrative pricing on the ingredient leg, exclusive of tax). The HSN classification for the malt-and-dairy concentrate sits in HSN 2106 (food preparations) — the brand should verify against its product technical sheet — and the GST rate post-22-September 2025 follows the GST 2.0 consolidation applicable to the relevant sub-HSN. HUL records the invoice in its GSTR-1 outward register as a B2B taxable supply at standard forward charge. CloudFoods records the invoice in its GSTR-2B input register and claims ITC on the input. Stage 2 — CloudFoods uses the concentrate to plate the menu item. The kitchen at each CloudFoods site reconstitutes the powder, blends it with milk, and serves it as a branded dessert shake on Swiggy and Zomato for a consumer price of ₹179 per portion (illustrative). The shake appears on the consumer app under one of CloudFoods’ brand names, with the cloud-kitchen origin disclosed per FSSAI requirements. Stage 3 — Swiggy or Zomato as Section 9(5) deemed supplier on the food order. A consumer in Bengaluru orders the shake on Swiggy at the ₹179 consumer price. Swiggy collects the consumer payment (₹179 plus delivery and packaging charges separately accounted), discharges the 5% Section 9(5) restaurant-service GST (₹8.52 included in the ₹179 menu price), deducts its platform commission, and settles the net merchant amount to CloudFoods. The Section 9(5) GST is discharged by Swiggy as deemed supplier — CloudFoods does not charge GST on the food-service leg, and CloudFoods cannot claim ITC on the inputs it consumed in producing that meal against Swiggy’s Section 9(5) liability (the 5% without ITC structure). Stage 4 — Channel-mix register and GSTR reconciliation closure. HUL’s GST controller closes the month’s channel-mix register with the ₹32.4 lakh CloudFoods ingredient supply correctly classified as a B2B Section 9(1) supply, flowing into GSTR-1 Table 4A (B2B taxable supplies). No Section 9(5) flag appears anywhere on HUL’s side because HUL has no Section 9(5) exposure on this leg — the deeming binds Swiggy, not HUL, and binds on the food-service supply Swiggy facilitates to the consumer, not on the upstream ingredient-supply chain. Separately, HUL’s quick-commerce register for the same month (HUL packaged-goods supply via Blinkit, Zepto, Instamart, Swiggy Instamart) is reconciled per the quick-commerce FMCG settlement reconciliation discipline with Section 52 TCS at 0.5% claimed in GSTR-2X. The total channel-mix split for HUL in the month of October 2025 might look like the following.

Common reconciliation breakages

Several specific patterns recur in FMCG GST teams new to the cloud-kitchen channel.

• Mis-flagging HoReCa supplies as Section 9(5) just because the buyer sells on Swiggy. A junior tax executive sees the cloud-kitchen counterparty’s name on a food-delivery app and concludes the entire upstream supply chain falls under Section 9(5). It does not. The HoReCa supply is straight Section 9(1) — the brand’s invoice carries forward-charge GST at the ingredient HSN rate and the cloud kitchen claims ITC. Catch with a customer-master flag distinguishing “B2B HoReCa buyer” from “B2C ECO platform” at customer onboarding.
• Confusing Section 9(5) restaurant rate (5%) with the ingredient HSN rate. The cloud kitchen’s downstream food-service supply through Swiggy is taxed at 5% without ITC by Swiggy. That has nothing to do with the rate at which HUL invoices the upstream ingredient supply, which follows the ingredient HSN — and post-22-September 2025 GST 2.0, the ingredient HSN may be 5%, 12%, 18%, or in some categories the 40% NSAB slab. Maintain HSN-rate effective dates per SKU in the master and let the invoicing engine pick the right rate.
• Failing to track Section 52 TCS on quick-commerce packaged-goods supplies. When HUL also sells the same molecule as a packaged consumer product through Blinkit, Section 52 applies on that leg. Brands that bundle all “platform” flows together miss the TCS credit in GSTR-2X. Split the quick-commerce channel from the HoReCa channel at the customer-master level — the quick-commerce FMCG settlement reconciliation discipline walks the full TCS mechanics with examples per ECO.
• Treating cloud-kitchen private-label runs as ordinary B2B supplies. When the cloud-kitchen brand asks HUL to contract-manufacture a private-label SKU under the cloud-kitchen’s own brand mark, the relationship changes shape. The flow is a service supply (contract manufacturing) that engages Section 393(1) Sl. 4 of the Income-tax Act 2025 — payment codes 1001 (Individual/HUF deductee at 1%) and 1023 (other resident at 2%) — and the brand must deduct TDS on the manufacturing-charges component reconciled per Form 26AS. Flag co-pack contracts at the agreement-master level so the AP team applies TDS correctly.
• Confusing Section 9(5) with reverse charge mechanism on the same invoice. Section 9(5) is a deeming on the supplier identity, not a reverse-charge on the recipient. The ECO pays the tax as if it were the supplier — the recipient (consumer) pays the gross-of-tax amount as part of the consumer price. Do not mark Section 9(5) flows as “RCM” in the accounting system; they are forward-charge tax discharged by a deemed supplier.

How a reconciliation platform handles this

A reconciliation platform shifts the channel-classification register from a manual quarter-end exercise into a continuous control. Customer-master flags drive the leg-level classification automatically: B2B HoReCa supplies route to the Section 9(1) bucket and feed GSTR-1 Table 4A; quick-commerce ECO supplies route to the Section 9(1) plus Section 52 bucket and pull the corresponding TCS line from each ECO’s settlement file for GSTR-2X reconciliation; general-trade and modern-trade flows route to their own Section 9(1) buckets with the matching scheme-accrual and trade-discount reconciliations. Variance reports surface mis-classified invoices before the GSTR-1 cycle closes, and the customer-benefit outcome is fewer Section 73/74 GST notices, cleaner annual-return reconciliation, and an audit-ready evidence trail for the channel-mix split. Match rate improvements of 51 percent to 88 percent typical of structured reconciliation deployments come from removing exactly this kind of leg-level classification ambiguity — paired with the Section 15(2) scheme-accrual discipline for BOGO and slab-discount flows, the boundary between Section 9(5), Section 9(1), and Section 52 stays clean across the year.

Cross-cluster bridges

For the broader FMCG settlement reconciliation patterns, the FMCG reconciliation software India money page anchors the commercial pillar, and the quick-commerce FMCG settlement reconciliation article handles the parallel Section 52 TCS mechanics on packaged-goods supplies through Blinkit, Zepto, and Instamart. The BOGO scheme accounting under Section 15(2) CGST article addresses the trade-discount valuation overlay that interacts with B2B HoReCa supplies when the brand runs a value-pack promotion for the cloud-kitchen channel. The five FAQs below address the operational questions Indian FMCG tax and GST teams ask most often when navigating cloud-kitchen, quick-commerce, and Section 9(5) boundary cases.

Terra Insight Reconciliation Infrastructure

Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →

Published 27 June 2026

Domain expertise

TDS Reconciliation GST Input Credit Platform Settlements NACH Batch Matching Bank Reconciliation Form 26AS Matching ERP Integrations Enterprise Finance Ops

Reviewed by

NK

Navin Krishnan

Managing Director & Founder — Terra Insight

Ex Amazon India · Intuit QuickBooks · Tata nexarc

ISO 27001:2022 Patent Pending Incorporated 2024