HSN Codes for Marketplace Sellers: A Guide
HSN codes look like bureaucratic trivia — a number you typed once when creating a listing. But for marketplace sellers, HSN accuracy quietly controls three things: the GST rate applied to every order, the HSN summary in your GSTR-1, and how defensible your classification is when a notice arrives. This guide covers what marketplace sellers actually need to know about HSN, without drowning in tariff-schedule detail.
What HSN is and why GST cares
HSN (Harmonised System of Nomenclature) is the international commodity classification system GST uses to identify goods. Your product's HSN chapter and heading determine its GST rate — the rate is attached to the classification, not to your opinion of the product. Invoices must carry HSN codes at a minimum digit length that depends on your aggregate turnover: lower-turnover sellers report fewer digits, higher-turnover sellers report more. The digit thresholds are notification-driven, so check the current requirement for your turnover band rather than relying on remembered numbers.
The three places HSN must agree
Marketplace selling creates an HSN triangle, and drift between the corners causes real problems:
| Location | Role | Failure when wrong |
|---|---|---|
| Marketplace listing | Drives the GST rate the platform applies to the order and prints on the invoice | Wrong tax collected from the customer on every order of that SKU |
| Your books / item masters | Feeds accounting entries and the GSTR-1 HSN summary | HSN summary diverges from the rate-wise tables; audit friction |
| Purchase invoices | Your supplier's classification of the same goods | You claim ITC at one classification and sell under another — a red flag worth resolving |
The most common drift: a listing created years ago with a guessed HSN keeps applying an outdated rate while your books use the corrected classification. Because the marketplace generates customer invoices from listing data, the error propagates order by order until the listing is fixed. Rate-mismatch symptoms and diagnosis are covered in our guide to GST rate differences on marketplace invoices.
Treat HSN hygiene as a quarterly habit rather than a crisis response. Sample your top SKUs by order volume and verify three things for each: the listing's classification, the item master in your books, and the HSN your supplier used on recent purchase invoices. New product launches are where wrong codes enter the system, so make HSN assignment — with a source noted — a mandatory field in your listing-creation checklist. Ten minutes per quarter on the SKUs that carry your volume prevents the classic discovery of a year of orders on a wrong code.
The GSTR-1 HSN summary
GSTR-1 includes an HSN-wise summary of outward supplies (Table 12): for each HSN at the required digit length, the quantity, taxable value, and tax amounts. For a marketplace seller this table must be buildable from order-level data — which means every order line in your books needs an HSN inherited from a well-maintained item master. Two disciplines make the summary painless:
- One SKU, one HSN, everywhere. Maintain a master mapping of SKU to HSN and rate, and enforce it across marketplaces and books. When a classification changes, change it everywhere on the same date.
- Reconcile the summary to the rate tables. The HSN summary's tax totals should tie to your rate-wise B2C/B2B tables. If they do not, an item is misclassified or a rate is misapplied somewhere. Our GSTR-1 guide shows where this check sits in the filing flow.
Choosing codes without guessing
Practical sourcing hierarchy for the right HSN: your supplier's invoice for the same goods, the classification used by established competitors for identical products, the tariff schedule's chapter notes — and, for anything ambiguous or high-volume, a qualified CA or tax professional's written opinion. Classification disputes are among the oldest genres of indirect-tax litigation; for your top-selling SKUs, a confirmed classification is cheap insurance. Do not crowdsource HSN from seller forums for products where the rate difference is material.
Keeping order-level HSN data flowing into Tally
Marketplace reports carry SKU-level detail on every order, and your books need that detail to produce a defensible HSN summary. TallySutra converts Amazon, Flipkart, and Meesho reports into balanced TallyPrime vouchers that preserve item-level information and GST rates per line, so Table 12 can be generated from Tally rather than reconstructed from downloads at filing time. Where a report row cannot be confidently mapped to an item, it lands in the exception queue for a human decision instead of a silent default — see the features overview for how that works.
Educational disclaimer: HSN digit requirements, rate schedules, and classification positions change through notifications and rulings. Verify current requirements and confirm material classifications with a qualified CA or tax professional before relying on them.
Frequently asked questions
How many HSN digits must I show on invoices?
The minimum digit length depends on your aggregate turnover band and is set by notification — smaller sellers report fewer digits, larger sellers more. Check the current threshold rules on the GST portal or with your CA rather than relying on remembered figures.
What happens if my marketplace listing has the wrong HSN?
The platform applies the rate tied to that classification on every order and prints it on customer invoices, so the wrong tax is collected repeatedly until the listing is corrected. Fix the listing, then align your books and assess past exposure with your CA.
Does GSTR-1 need HSN details for B2C marketplace sales?
Yes — the HSN summary in Table 12 covers outward supplies including B2C, at your applicable digit length, with quantity, taxable value, and tax. It should reconcile with your rate-wise tables.
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