Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
D2C brands operating across multiple commercial models on marketplaces and eCommerce platforms must correctly classify each sale under Section 9(5) deemed-supplier rules, Section 52 TCS ordinary marketplace facilitation, Section 9(3) and 9(4) RCM on input services, or ordinary forward-charge B2B treatment, where mis-classification on cloud-kitchen and accommodation flows leads to double GST exposure and platform-settlement reconciliation errors that compound across months.
Tag every sale by GST treatment regime at order ingestion — Section 9(5) (operator-as-deemed-supplier), Section 52 (ordinary marketplace with TCS), Section 9(3) or 9(4) RCM (on inward supplies), ordinary forward charge. Build separate GSTR-1 reporting buckets per regime. For Section 9(5) supplies, expect platform settlements net of commission and without GST element. For Section 52 supplies, expect TCS at 1 percent reflected in GSTR-2B via operator's GSTR-8.
Sale classification rules per platform per SKU per service category, Section 9(5) notified-category register with effective dates, Section 52 TCS rate and reporting calendar, RCM supplier categorisation per Section 9(3) and 9(4), GSTR-1 outward-supplies bucket mapping, and reconciliation rules per regime.
Sales correctly classified by GST regime per platform; GSTR-1 reporting cleanly split between Section 9(5), Section 52, and ordinary forward charge; double GST exposure eliminated on cloud-kitchen and accommodation flows; Section 52 TCS credit per platform reconciled to GSTR-2B; RCM liability and corresponding ITC tracked separately in GSTR-3B; board-ready net realisation view per platform per regime.
A cloud-kitchen D2C brand operates 14 kitchens across Mumbai, Bangalore, and Delhi-NCR, selling through Swiggy (62 percent of revenue), Zomato (28 percent), own website and apps (8 percent), and quick-commerce food legs (2 percent). With ₹38 crore annual revenue split across Section 9(5) platform sales and ordinary direct sales, the brand reconciles two parallel GST regimes monthly. This article is for finance teams at D2C cloud kitchens, accommodation, and hybrid food and beverage operations managing Section 9(5) versus Section 52 versus ordinary GST classification.
What Section 9(5) GST Liability Involves
Section 9(5) of the CGST Act is a deemed-supplier provision. For notified categories, the eCommerce operator becomes the deemed supplier of the service to the end consumer — the operator issues the tax invoice to the consumer, charges the GST, collects it, and remits it to government. The actual service provider (the cloud kitchen, the hotel, the driver) does not charge GST on those supplies. The provision exists to simplify GST collection in industries with very high seller cardinality (every restaurant, every cab driver, every small accommodation property) by centralising tax collection at the operator level.
The India-specific context for D2C is the post-2022 expansion of Section 9(5) to cover restaurant services through eCommerce operators. Effective 1 January 2022, all restaurants supplying through Swiggy, Zomato, and similar operators came under Section 9(5) — the operator now charges and remits GST on every food order routed through the platform. This included not just traditional restaurants but cloud kitchens, the operating model that many D2C food-and-beverage brands use. A cloud-kitchen D2C brand selling on Swiggy and Zomato is squarely in Section 9(5) for those flows, while its direct-channel sales remain under ordinary GST.
How Section 9(5) Reconciliation Works
Tagging Sales by GST Treatment Regime at Ingestion
The first reconciliation step is correctly tagging every sale at order ingestion. The OMS or ordering layer must know whether the order originated on a Section 9(5) platform (Swiggy, Zomato, food-delivery legs of quick commerce) or a Section 52 ordinary marketplace (Amazon, Flipkart, Meesho for goods) or a direct channel (own website, own app, walk-in at the kitchen counter for hybrid operations). Each tag determines downstream GST treatment, GSTR-1 reporting bucket, and settlement-reconciliation logic.
A common error is treating Swiggy and Zomato food-delivery sales as ordinary marketplace sales subject to Section 52 TCS. This leads to the cloud kitchen charging and remitting GST on supplies where the platform has already collected and remitted GST as the deemed supplier under Section 9(5) — double GST exposure that compounds across months and can run to several percent of revenue before discovery in a GST audit.
Section 9(5) Platform Settlement Reconciliation
For Section 9(5) supplies, the platform’s settlement to the cloud kitchen is the order value (food value sold to the consumer) net of commission, packaging fee, delivery service charges where applicable, and any other deductions. The settlement does not include a GST element being passed through to the kitchen — the platform has retained the GST for remittance as the deemed supplier. The kitchen receives the net payable in its bank account on the agreed settlement cycle (typically weekly with T+7 cadence for Swiggy and Zomato).
Reconciliation matches each settlement file to the order ledger, validates order value, commission, and deductions, and posts the net to bank. The kitchen reports the gross order value as outward supply through eCommerce operator under Section 9(5) in GSTR-1 with no tax payable, and the commission and other deductions appear as inward supplies from the operator (invoiced separately by Swiggy or Zomato with 18 percent GST) which are eligible for ITC at the kitchen’s end.
Section 52 TCS Reconciliation for Non-9(5) Marketplace Sales
For sales on non-9(5) marketplaces — typically for the kitchen’s packaged products, retail SKUs, or non-food merchandise sold through ordinary marketplace operators like Amazon — Section 52 TCS applies. The marketplace operator collects 1 percent TCS on the net taxable value of supplies (gross sale minus returns minus discounts), files the operator’s GSTR-8, and the seller (kitchen for its retail SKUs) claims the TCS credit in GSTR-2B. The kitchen continues to charge GST on these supplies under ordinary forward charge — Section 52 TCS does not replace GST; it sits alongside as an advance tax collection.
Reconciliation here matches Section 52 TCS credits per operator GSTIN to the operator’s GSTR-8 filing reflected in GSTR-2B, validates the credit per month, and posts the credit reduction against the kitchen’s output GST liability for that month.
Section 9(5) and Marketplace Reference
| Platform Type | GST Regime | Operator Responsibility | Seller Responsibility |
|---|---|---|---|
| Swiggy, Zomato food delivery | Section 9(5) | Charge and remit GST as deemed supplier | Report outward through operator, no tax payable; pay GST on direct channel only |
| Cab aggregators (Uber, Ola for radio taxi) | Section 9(5) | Charge and remit GST | Driver does not charge GST on those rides |
| Specified accommodation through operators | Section 9(5) | Charge and remit GST | Property does not charge GST on those bookings |
| Amazon, Flipkart, Meesho for goods | Section 52 | Collect 1 percent TCS, file GSTR-8 | Charge GST in invoice; claim TCS credit in GSTR-2B |
| Direct channel (own website, own outlet) | Ordinary forward charge | Not applicable | Charge GST in invoice; remit through GSTR-3B |
Worked Example: ₹38 Crore Cloud Kitchen D2C Brand
A cloud-kitchen D2C brand operates 14 kitchens with ₹38 crore annual revenue. Of this, ₹23.6 crore is Swiggy, ₹10.6 crore Zomato, ₹3 crore direct channel (own website and apps), and ₹0.8 crore packaged retail SKUs sold on Amazon and Flipkart. Under correct classification, ₹34.2 crore (Swiggy plus Zomato) falls under Section 9(5) with the platforms remitting GST as deemed suppliers, ₹3 crore (direct) under ordinary forward charge with the kitchen remitting GST, and ₹0.8 crore (packaged retail) under ordinary forward charge with Section 52 TCS applied at the marketplace level.
Before structured classification, the brand had treated Swiggy and Zomato sales under ordinary forward charge — charging 5 percent or 18 percent GST in its internal invoices to the platforms and remitting through GSTR-3B. The platforms had separately charged and remitted GST as Section 9(5) deemed suppliers. A finance review found a year-and-a-half of double GST exposure totalling approximately ₹2.6 crore — the kitchen had remitted GST that the platforms had already remitted. The double-remit could not be straightforwardly recovered because the GST framework does not refund GST paid in error on supplies that another party has correctly remitted; the kitchen had to pursue corrections through its GSTR-1 amendment cycle within the prescribed window and through claim-of-refund where applicable.
After implementing per-sale GST-regime tagging at OMS ingestion with separate GSTR-1 buckets for Section 9(5), Section 52, and ordinary forward charge, the kitchen prevented further double remittance. The brand also surfaced the commission-and-deduction ITC available on Swiggy and Zomato platform invoices (the platforms invoice the kitchen separately for commission and other charges at 18 percent GST, which is ITC-eligible) — a recurring ITC of approximately ₹68 lakh per year that had been partially under-claimed.
India Compliance Angle: Section 9(5), Section 52, Section 9(3) and 9(4) Reconciled
Section 9(5) notified categories at the current writing include passenger transportation by radio taxi or motor cab through eCommerce operators, accommodation services through specified eCommerce operators where the property does not have GST registration or has turnover below threshold, and restaurant services (including cloud kitchens) through eCommerce operators effective 1 January 2022. The notification list is maintained by CBIC and is updated periodically — finance teams should track new notifications because expansion of Section 9(5) directly affects the GST treatment of platform sales.
Section 52 TCS at 1 percent applies to all other marketplace operations where the platform facilitates supply between a third-party seller and the end customer, and the seller is the supplier of record. Operators file GSTR-8 monthly with line-item TCS collected per seller, and the credits flow into the seller’s GSTR-2B for monthly claim against output GST.
Section 9(3) RCM applies to notified categories of supplies where the recipient is liable to pay GST under reverse charge regardless of supplier status — common touchpoints for D2C are GTA (goods transport agency) services, legal services from advocates, and certain services from government authorities. The recipient pays the GST under RCM, claims ITC for the same amount where the supply is for business purposes, and reports both legs in GSTR-3B. Section 9(4) RCM applies where a registered person receives supplies from an unregistered supplier in notified categories — currently a narrow set covering certain promoters’ real-estate inputs. For ordinary D2C operations, Section 9(4) touchpoints are limited.
To size the recoverable variance from missed ITC on platform commission invoices and from any double-remit exposure, the ITC leakage calculator helps finance leaders estimate the band before commissioning regime-classification work.
For brands also running quick commerce platform reconciliation across consignment, direct-buy, and ad-spend streams, the regime classification overlays on those flows — quick-commerce food legs that operate under Section 9(5) need the same separate bucketing as Swiggy and Zomato. Reconciliation software India finance teams use that supports per-sale regime tagging avoids the silo where Section 9(5) and Section 52 classification errors leak into double GST. Payment gateway reconciliation pipelines extend cleanly to platform-settlement matching with the regime tag preserved through the line-item key. The CBIC GST portal is the authoritative reference for Section 9(5) notified categories and Section 52 TCS treatment.
The following questions address the reconciliation issues D2C brands navigating multiple GST regimes encounter most often.