Finding the right HSN code and GST rate
HSN is the code that decides the tax on every invoice you raise. Amazon will accept whatever you enter, which is exactly the problem: nothing validates that it is the right one.
HSN classifies your product and drives the GST rate printed on every invoice. Amazon accepts whatever code you enter without checking it against the product, so a wrong code produces correct-looking invoices at the wrong rate for as long as nobody notices. Classify from the product's material and function, keep a written reason, and get a professional to confirm anything ambiguous.
- The code decides the rate, and nothing in the listing flow validates it.
- Classify on what the product is and does, not on how you market it.
- The same object can sit in two headings. Write down why you chose yours.
- A wrong rate is your liability, not Amazon's, and it compounds every invoice.
- Rates move. A code chosen once and never revisited is a standing risk.
This is the most consequential field on a listing that nobody checks. Everything else fails loudly: a bad image is rejected, a bad price is gated, a bad title is suppressed. A wrong HSN code is accepted silently and keeps being accepted.
What the code actually does
HSN is an international classification, used in India to determine the GST rate on a supply. You put it on the listing; it flows onto the tax invoice Amazon raises on your behalf; the rate it implies is what the buyer is charged and what you account for.
So the field is not administrative. It is the one input on the listing with a direct line to money you owe, and the only one where being wrong accrues quietly instead of stopping you.
Classify on what the thing IS
The classification follows the product's material and function, not its marketing. A cotton kitchen cloth is classified as what it is made of and what it does, not as a kitchen accessory because that is the category you sell it in. Sellers routinely choose by browse node, and the browse node is a merchandising decision with no relationship to the tariff.
Work from the product's composition first, then its purpose. Where composition is mixed, the classification rules have an order of precedence for deciding which material gives the product its essential character, and that order is the thing a professional actually applies.
When two headings both look right
This is the common case and it is not a sign you have misunderstood. Many ordinary products sit plausibly under more than one heading, and the difference between them can be a different rate.
What you can do about it is less about finding certainty and more about building a defensible position: pick the heading that best matches composition and function, write down the reasoning at the time, and keep it with the product record. An assessment years later goes much better with a contemporaneous note than with a recollection.
Why a wrong code compounds
Every invoice raised under it carries the wrong rate. Undercharge and the shortfall is yours to make good, usually with interest, and you cannot go back and collect it from buyers who have long since received their orders. Overcharge and you have charged buyers tax they did not owe, which is its own problem to unwind.
That is the asymmetry worth internalising: the cost is not one bad invoice, it is every invoice since the code was set, discovered at once.
Rates and classifications move
GST rates and the classification of specific goods have been revised repeatedly since the regime began, and a code that was right when the listing was created can imply a different rate later. Nothing in the listing notifies you.
So treat the code as something with a review date rather than something set once. The practical trigger is any announced change touching your categories: at that point the question is not only what the new rate is, but whether your products are still in the heading you assigned.
Where to look it up, and what not to rely on
Use the official tariff and the GST Council's own rate notifications as the source. Rate-finder tools and marketplace help pages are convenient and they are summaries, often of an older position, and they are not what an assessment will be conducted against.
Be particularly careful with a code copied from a competitor's listing or a supplier's invoice. Both are common shortcuts and neither is evidence: the competitor may be wrong, and the supplier's classification covers what they sold you, which is not always what you sell on.
This is the point to involve a professional
Classification is a specialist area, the ambiguity above is genuine rather than a knowledge gap you can read your way out of, and the liability is yours. A chartered accountant or a tax advisor who sees your actual product range is the right input for anything you are not certain about, and certainly for a new category.
Nothing on this page is tax advice, and it is written to help you ask better questions rather than to answer them. Check anything you plan to act on with your own advisor and against the current notifications.
Every invoice traced back to its order
Robnu ingests your Amazon settlements line by line, so a fee, a refund or a tax line is never a number without an origin.
Keeping it straight across a catalogue
The failure at scale is not one wrong code, it is a catalogue where nobody can say why any code was chosen. Keep the classification reasoning with the product, review it when rates change, and make a new product's code a deliberate decision rather than a copy of the nearest existing line.
The cheapest version of this is a column in whatever sheet your catalogue already lives in. The expensive version is reconstructing it under assessment.
Every settlement line matched to its order
Robnu ingests your Amazon settlements with their full line items, so each fee, refund and reserve movement traces back to the order that caused it and a short payment is visible the day it lands.
- Order and settlement matched line by line
- Fees separated from sales and from tax
- Short payments surfaced, not discovered a quarter later
Where this sits in the rest of your Amazon operation
On Amazon, Robnu syncs your orders, returns, payouts and inventory, reconciles every settlement line back to the order that caused it, lists the FBA units Amazon's own ledger has not made good, flags a return that never came back before the SAFE-T window closes, and scans returns in at your dock. It reads your Amazon account rather than writing to it, so accepting orders and making labels run on AJIO and Meesho today. Related reading:
Sources & further reading
- Amazon India, how to list your products the one publicly readable Amazon.in page that states listing figures: title 200 characters, images 500x500 or 1,000x1,000. Read 30 October 2026.
- Amazon listing and image style guides login-gated. It redirects to Amazon sign-in, so the detailed rules it holds are not quoted here and are described as market convention instead. Read 30 October 2026.
- Amazon India seller forums where the failure shapes described here are reported by sellers. Read 30 October 2026.
Not legal or tax advice. Amazon changes fees, windows and policies without notice, and the detailed style guides and account-health thresholds sit behind a Seller Central login, so any figure quoted here as convention is not Amazon-published. Check anything you plan to act on against your own Seller Central account first.
Questions sellers ask
It classifies the product and determines the GST rate printed on every tax invoice raised on your behalf, which is what the buyer is charged and what you account for. It is the one listing field with a direct line to money you owe, and the only one where being wrong accrues quietly rather than stopping you.
No. Amazon accepts whatever code you enter, so a wrong one produces correct-looking invoices at the wrong rate for as long as nobody notices. Everything else on a listing fails loudly, which is exactly why this field is the one that goes wrong undetected.
This is the common case, not a sign you have misunderstood: many ordinary products sit plausibly under more than one heading, sometimes at different rates. Pick the heading that best matches composition and function, write the reasoning down at the time, and keep it with the product record.
Every invoice raised under it carries the wrong rate. Undercharging leaves a shortfall that is yours to make good, usually with interest, and you cannot collect it from buyers who received their orders long ago. Overcharging means buyers paid tax they did not owe. The cost is every invoice since the code was set, found at once.
Both are common shortcuts and neither is evidence. The competitor may simply be wrong, and your supplier's classification covers what they sold you, which is not always what you sell on. Use the official tariff and the GST Council's rate notifications as the source.
Yes. GST rates and the classification of specific goods have been revised repeatedly, and nothing in the listing notifies you when the rate your code implies has changed. Treat the code as having a review date, triggered by any announced change touching your categories.
For anything ambiguous, and certainly for a new category, yes. Classification is a specialist area, the ambiguity is genuine rather than a gap you can read your way out of, and the liability is yours. Nothing here is tax advice; it is written to help you ask better questions.
Related seller guides
More on the operations, money and claims that decide whether a marketplace catalogue actually makes money.
Meesho HSN Code & GST Rate: How to Add Them Right 2026
Adding the correct HSN code and GST rate on a Meesho listing decides your tax, invoicing and payouts. Here is what HSN is, how to find yours, why it matters, and the common mistakes that cost sellers money.
Amazon main image rules, white background and what breaks it
The main image carries stricter rules than the rest, and breaking them gets a listing suppressed rather than flagged. What is settled, what is convention, and how to diagnose a rejection.
Amazon order defect rate, what counts and what does not
ODR is three separate things counted as one, and sellers usually watch the wrong one. What feeds it, the lag that makes it look wrong, and why the threshold is not publicly citable.
Amazon late dispatch rate and the handling time trap
Most late dispatch problems are a handling time set optimistically rather than a warehouse that is slow. What the metric measures, and the settings that quietly cause it.
Amazon Easy Ship label printing and what goes wrong
Most Easy Ship label problems are a browser, a printer driver or a scale issue rather than Amazon. The order to check them in, and the one that risks a rejected handover.
AJIO catalog and listing quality: images, attributes, QC
Shot discipline, attribute completeness, size charts and QC rejection loops, why listing data decides whether AJIO shoppers ever find your products.
Amazon Listing Suppressed: Find the Actual Cause
A suppressed listing is complete enough to exist and Amazon is declining to show it. The six causes, where each one is visible, and why reactivating without a change fails.
How to actually reduce your Amazon return rate
Return rate is decided before the order, by the listing. The four causes that produce most returns, how to tell which one you have, and what each actually costs to fix.