Selling on Multiple Marketplaces — One GST Return
- You file one GSTR-1 per GSTIN — all marketplaces merge into it, not one return each.
- Returns net across platforms within the same state and rate bucket. The platform is not part of the key.
- Filter every report by invoice date, not order date — this is the top cause of totals not matching.
- Four platforms deduct TCS separately but all credits land in one electronic cash ledger.
- Reconcile your consolidated total back to the four source reports before filing. Errors here are silent.
On this page
Selling on one marketplace is a filing task. Selling on four is a consolidation task, and that is a different problem — because the four platforms give you four differently shaped reports, four TCS deductions, and four sets of column names, all of which have to end up as a single GSTR-1 under a single GSTIN.
The mistake that costs sellers the most is treating each platform as a separate filing. It is not. There is one return.
One GSTIN, one return
You file one GSTR-1 per GSTIN per period — not one per marketplace. All sales merge into the same Table 7, netted together per place of supply and per rate.
That last point is the one people get wrong. If you sold ₹40,000 into Maharashtra at 5% on Meesho and had ₹6,000 of Maharashtra returns at 5% on Amazon, those net against each other. They are the same bucket — same state, same rate, same GSTIN. The platform is not part of the key.
Getting the right report from each platform
Every platform names its tax report differently and puts it somewhere different. The report you want is the one with taxable value, tax rate, place of supply and invoice date — not the settlement or payout report, which is about money rather than tax.
| Platform | What to look for | Watch out for |
|---|---|---|
| Meesho | GST / tax report for the month | Returns are usually separate rows that must be netted, not a separate file |
| Amazon | Merchant tax report (MTR) | Contains multiple transaction types — shipment, refund, cancellation — which must be treated differently |
| Flipkart | Sales / GST report | Column names change between report versions; do not hard-code positions |
| Myntra | Sales report from the partner portal | Fee itemisation is often not included, so profit needs the settlement report too |
The period boundary problem
This causes more "my sales don't match" complaints than anything else. Platforms do not all use the same date to decide which month a transaction belongs to. Some use order date, some invoice date, some dispatch date.
GSTR-1 goes by invoice date. An order placed on 31 March but invoiced on 1 April belongs to April. If you filter each platform's report by order date, you will pull the wrong set of rows from at least one of them.
- Always filter on invoice date, not order or dispatch date
- Check the first and last three days of the month specifically — that is where the drift lives
- A return processed in a later month is a credit note in that later month, not a retroactive edit to the original month
Netting returns across platforms
Returns net against sales within the same place of supply and the same tax rate. Not per platform, and not as one number at the bottom of the return.
Two situations need care:
- Returns exceeding sales in a bucket. A small state can end a month with more returns than sales at a given rate, producing a negative. The portal rejects negative values in Table 7, so this must be handled as a credit note rather than a negative line.
- Returns of pre-22-September-2025 sales. A credit note carries the rate of the original supply. If you sold apparel at 12% before the change, the credit note for that return is also at 12%, even though 12% no longer exists for new supplies.
Four TCS deductions, one ledger
Each platform deducts 0.5% TCS on its own net taxable supplies and reports it in its own GSTR-8. All four credits land in the same electronic cash ledger under your GSTIN.
So your reconciliation is many-to-one:
- Compute expected TCS per platform: 0.5% of that platform's net taxable value
- Sum them
- Compare against your cash ledger balance after accepting all TCS credits
A shortfall usually means one platform has not filed GSTR-8 yet (due the 10th), or has your GSTIN wrong on its seller panel. Full detail in the TCS guide.
Keeping HSN consistent across platforms
The same product listed on four platforms must carry the same HSN code in your return. Platform category trees will not agree with each other — they are built for shoppers, not for classification — so the mapping has to live with you, not with the marketplace.
Maintain one product-to-HSN master and apply it to every platform's data. This also makes Table 12 reproducible month to month, which matters because inconsistency across periods is itself something the department notices. See the HSN and rates reference.
A monthly workflow that holds up
- Download all four reports before starting. Do not begin with partial data.
- Filter each by invoice date for the period.
- Normalise the columns — every platform names taxable value and place of supply differently. Map them to one common shape.
- Apply your product-to-HSN master and the current rate.
- Merge, then net returns per state and rate across all platforms together.
- Reconcile: your consolidated taxable value should equal the sum of the four reports' taxable values, to the rupee. If it does not, stop — do not file.
- Check GSTR-1 against 3B before submitting — mismatch checker.
- Accept TCS credits from all four platforms on the portal.
When this stops being an Excel job
One platform and a few hundred orders is manageable by hand. Four platforms and a few thousand orders is not, for a specific reason: the errors are silent. A wrong place-of-supply code does not produce an error message — it quietly moves tax between IGST and CGST/SGST while the grand total still looks right. You find out when the department reconciles head-wise.
Whatever you use — a spreadsheet, a tool, or an accountant — the non-negotiable is that the final numbers get reconciled back to the source reports every single month.
Four reports in, one reconciled GSTR-1 out
Upload the reports from every marketplace you sell on. GSTWali normalises the columns, nets returns across all of them per state and rate, and shows the reconciliation against your source totals before you download.
Try it free →Frequently asked questions
Do I file a separate GSTR-1 for each marketplace?
No. You file one GSTR-1 per GSTIN per period. Sales from Meesho, Amazon, Flipkart, Myntra and any other platform all merge into the same return and are netted together per place of supply and per tax rate. The marketplace is not part of how the data is grouped.
Which date should I use to decide which month a sale belongs to?
Invoice date. GSTR-1 reports by invoice date, but marketplace reports can default to order date or dispatch date. An order placed on 31 March and invoiced on 1 April belongs to April. Filtering on the wrong date is the most common reason a seller total does not match.
How do returns work across different marketplaces?
Returns net against sales within the same place of supply and the same tax rate, regardless of which platform the sale or the return came from. A Maharashtra return at 5% on Amazon nets against Maharashtra sales at 5% on Meesho, because they are the same bucket.
What rate applies to a return of something sold before the GST 2.0 change?
A credit note carries the rate of the original supply. If you sold apparel at 12% before 22 September 2025, the credit note for that return is also at 12%, even though 12% no longer applies to new supplies.
Do I get separate TCS credit from each marketplace?
Each platform deducts 0.5% TCS on its own net taxable supplies and reports it in its own GSTR-8, but all of those credits land in the same electronic cash ledger under your GSTIN. There is one pool. You still need to accept each credit on the portal.
Should the same product have the same HSN code on every platform?
Yes. The HSN belongs to the product, not to the platform listing. Maintain one product-to-HSN master and apply it to every platform report. Platform category trees are built for shoppers and will not agree with each other or with the HSN schedule.