Complete GST return guide for e-commerce operators and sellers in FY 2026-27 — covering GSTR-8, TCS, reconciliation, section 9(5), and reporting obligations.
E-commerce in India has matured into a multi-lakh-crore ecosystem covering marketplaces, D2C brands, food aggregators, and quick-commerce platforms. Under GST, the compliance burden is shared between the e-commerce operator (ECO) and the seller listed on the platform. For FY 2026-27, GST Council circulars and the Finance Act 2026 have tightened the reconciliation requirements between GSTR-1, GSTR-3B, GSTR-8, and the autopopulated GSTR-2B.
Who is an e-commerce operator under GST
An e-commerce operator is any person who owns, operates, or manages a digital platform for the supply of goods or services. Marketplaces such as Amazon, Flipkart, Myntra, Zomato, Swiggy, and Urban Company are operators. Operators must register under GST irrespective of turnover and collect TCS at 1% (0.5% CGST + 0.5% SGST or 1% IGST) on the net taxable value of supplies made through them.
Returns to be filed by e-commerce operators
- GSTR-8 — Monthly TCS return reporting supplies made through the platform and TCS collected. Due by the 10th of the following month.
- GSTR-1 — Outward supplies of the operator's own services (commission, advertising, logistics).
- GSTR-3B — Monthly summary return with output tax, input tax credit, and tax payable.
- GSTR-9 and GSTR-9C — Annual return and reconciliation statement where turnover thresholds apply.
Returns to be filed by e-commerce sellers
Sellers on e-commerce platforms must register for GST irrespective of the ₹40 lakh / ₹20 lakh threshold if they supply goods. Service suppliers also need to register, except for specific notified services. The seller files:
- GSTR-1 — Monthly or quarterly statement of outward supplies, including B2C and B2B invoices.
- GSTR-3B — Monthly summary return that captures liability and ITC claims.
- Reconciliation with GSTR-8 filed by the operator, ensuring TCS credit appears correctly in the seller's electronic cash ledger.
- GSTR-9 / GSTR-9C where applicable.
TCS credit and reconciliation
The TCS deducted by the operator flows to the seller's electronic cash ledger after the operator files GSTR-8. The seller must accept the TCS in TDS/TCS Credit Received tile on the GST portal. Failure to reconcile creates working-capital leakage and triggers automated notices under section 61. Run a monthly three-way match: marketplace settlement report vs GSTR-8 vs your GSTR-1.
Composition scheme and e-commerce
Sellers supplying goods through e-commerce operators cannot opt for the composition scheme under section 10. For services, restaurants supplying through aggregators like Zomato and Swiggy have a special carve-out — the aggregator is liable to pay GST on restaurant services under section 9(5) at 5% without ITC. This shifts the compliance burden away from small restaurants.
Penalties and late fees
Late filing of GSTR-8 attracts ₹200 per day (₹100 CGST + ₹100 SGST), capped as per the latest CBIC notification. Non-collection of TCS attracts interest plus penalty under section 122. Operators that suppress supplies face penal action under section 52(14), and the GSTN's analytics now cross-checks platform settlement data with declared turnover.
Practical scenarios — marketplace, food delivery, and SaaS
Marketplace sellers (Amazon, Flipkart, Myntra) face the standard ECO-TCS flow: monthly settlement, TCS in GSTR-8, credit in their cash ledger. Food delivery operators (Zomato, Swiggy) operate under section 9(5) for restaurant services — the platform pays GST at 5%, and restaurants are largely insulated from monthly GST filing for those supplies but continue to file returns for non-restaurant revenue.
SaaS and digital service marketplaces (Urban Company, BookMyShow) operate as ECOs for services. TCS applies on the service supply value, and the underlying supplier reconciles credit. For cross-border SaaS exports through a marketplace, the GST classification depends on place of supply and the LUT route for zero-rated supplies. Sellers using their own websites (D2C) are not subject to ECO-TCS but still register and file standard GST returns.
- Build a monthly settlement report and three-way match before filing GSTR-3B.
- Track marketplace fees, returns, and chargebacks separately for accurate ITC accounting.
- Reconcile multiple marketplace presences (Amazon plus Flipkart plus own D2C) for consolidated GSTR-9.
- Maintain dispatch-level documentation including e-way bills for inter-state stock transfers.
GST authorities increasingly use analytics to compare marketplace settlement data with declared turnover, so operators and sellers must reconcile every payout cycle. Late or skipped GSTR-8 by an operator blocks the seller's TCS credit and creates working-capital strain across the supply chain. Sellers should treat GSTR-8 acceptance and reconciliation as a non-negotiable monthly ritual, with exception management built into accounts receivable workflows. Cross-border e-commerce introduces additional complexity around place of supply, LUT-based zero-rated exports, and OIDAR registration for foreign digital service providers.
Conclusion
GST compliance for e-commerce operators and sellers in FY 2026-27 is a coordinated exercise. The operator collects TCS and reports it monthly; the seller claims credit and reconciles every settlement cycle. Treat GSTR-8 reconciliation as a non-negotiable monthly ritual, and your working capital and notices both stay under control.
