GSTR-1 for Marketplace Sellers: Filing Guide
GSTR-1 is where you tell the government what you sold. For a marketplace seller, it is also the return most likely to be cross-checked against someone else's data — because every supply you report through Amazon, Flipkart, or Meesho is independently reported by that operator in GSTR-8. This guide walks through building a GSTR-1 that survives that comparison: which tables matter, how e-commerce supplies are disclosed, and how returns and credit notes should flow in.
The tables that matter for e-commerce sellers
Most marketplace sales are B2C — goods delivered to unregistered consumers. Your typical GSTR-1 footprint looks like this:
| Section | What goes there for a marketplace seller |
|---|---|
| B2C supplies (large and other) | Consumer sales, reported rate-wise and place-of-supply-wise; inter-state supplies above the specified invoice value get invoice-level disclosure |
| B2B supplies | Any sales to registered buyers (e.g., business purchases on marketplaces where the buyer's GSTIN was captured) |
| Credit/debit notes | Customer returns and price adjustments — registered and unregistered sections respectively |
| Table 14 | Supplies made through e-commerce operators, reported operator GSTIN-wise, as applicable |
| HSN summary (Table 12) | Rate-wise, HSN-wise summary of outward supplies per the applicable digit requirement |
| Documents issued | Invoice and note number ranges for the period |
Before diving into the individual tables, two housekeeping disciplines make everything downstream easier. First, maintain a separate invoice series per marketplace and per GSTIN — the documents table asks for number ranges, and clean series make it trivial while also making duplicates instantly visible. Second, remember that nil-rated and exempt outward supplies have their own disclosure line; if your catalogue includes exempt goods, they belong there rather than disappearing from the return entirely.
Table 14: the e-commerce disclosure
GSTR-1 asks sellers to disclose supplies made through each e-commerce operator, identified by the operator's GSTIN, where applicable. This is precisely the field the system can compare against the operator's GSTR-8. The practical implication: you need your sales data segmented by marketplace, not as one merged sales ledger. If Amazon and Flipkart sales are indistinguishable in your books, Table 14 becomes guesswork.
Because the place of supply for B2C goods is the delivery state, your marketplace reports' ship-to state column drives how each sale lands in the B2C tables. Get that mapping wrong and your state-wise figures diverge from the operator's data — the subject of our place of supply guide.
Returns, cancellations, and credit notes
Marketplace selling means high return rates, and every return that reverses a reported supply should be captured through a credit note in GSTR-1. Two disciplines matter:
- Do not net returns silently. Reporting sales already reduced by returns, without credit notes, understates both your documents and your gross figures relative to marketplace data.
- Track RTO vs customer return. An order returned before delivery may never have been a completed supply in the same way a delivered-then-returned order was; your CA should set the policy, and your books should apply it consistently.
The GST treatment of credit notes, including timing limits, is covered in our credit note guide.
The reconciliation before filing
A GSTR-1 prepared straight from marketplace downloads, without books, is fragile; one prepared from books that were never tied to marketplace data is worse. The robust sequence is:
- Import every marketplace's monthly sales, returns, and settlement reports into your accounting system.
- Reconcile order-level data against settlements so books and payouts agree.
- Generate GSTR-1 figures from those reconciled books: rate-wise B2C, state-wise place of supply, operator-wise totals, credit notes.
- Sanity-check operator-wise totals against each marketplace's own tax reports for the month.
This is the workflow TallySutra automates for TallyPrime users: Amazon, Flipkart, and Meesho reports become balanced vouchers with marketplace-wise ledgers, GST rate and state captured per line, settlement reconciliation, and duplicate-safe re-imports — so the GSTR-1 your CA files is generated from books that already match operator data. TallySutra prepares the books; the filing itself happens on the GST portal or through your filing software.
Common GSTR-1 errors from marketplace data
- Using order date vs invoice date inconsistently across months, shifting supplies between periods.
- Missing marketplace-collected recharges or promotions that adjust taxable value.
- Duplicated invoices when a corrected report is imported over an old one — duplicate-safe importing exists for exactly this reason.
- HSN summary totals not tying back to the rate-wise tables.
Filing frequency options and due dates change periodically, so check the current schedule on the GST portal. And since classification, credit-note timing, and Table 14 applicability involve judgment, have a qualified CA or tax professional confirm your return before filing — if you work with one, our CA review workflow was built for that handoff.
Frequently asked questions
Do marketplace sales go in the B2C tables or a special table?
Both dimensions apply: consumer sales are reported in the B2C tables rate-wise and state-wise, and supplies made through e-commerce operators are additionally disclosed operator GSTIN-wise in Table 14 as applicable.
How do customer returns appear in GSTR-1?
Through credit notes reported in the return, which reduce your outward liability. Silently netting returns out of sales understates documents and creates mismatches against the marketplace's GSTR-8 data.
Why must my sales be segmented by marketplace?
Because Table 14 reporting is operator GSTIN-wise and the system can compare your figures with each operator's GSTR-8. A single merged sales ledger makes operator-wise disclosure and reconciliation guesswork.
TallySutra turns Amazon, Flipkart and Meesho reports into reconciled, reviewed TallyPrime vouchers — duplicate-safe, with every rupee traceable to its source row.
Book a 30-minute demo