HSN Codes for Clothing and Textiles - Complete Guide 2025

Practical textile chapter references with pricing threshold and apparel GST considerations.

HSN Codes for Cotton Fabric (Chapter 52)

Start cotton analysis from Chapter 52. Distinguish yarn and finished fabric clearly.

HSN Codes for Synthetic Fibres (Chapters 54-55)

Man-made fibers commonly involve Chapter 54 and Chapter 55. Blend details matter.

HSN Codes for Knitted Garments (Chapter 61)

Knitted apparel often maps through Chapter 61, with common references like HSN 6109.

HSN Codes for Woven Garments (Chapter 62)

Woven apparel often falls in Chapter 62, including items like HSN 6203.

T-Shirts and Casual Wear - 5% vs 12% GST

Pricing and category conditions can influence slab treatment. Configure ERP logic with effective-date controls.

Sarees, Shawls and Dupattas

Composition and fabric type can affect final mapping. Keep product metadata complete at SKU creation stage.

Under Rs 1000 vs Over Rs 1000 Rule

Where threshold treatment is relevant, add automated checks to flag price-band transitions before invoicing.

Practical Compliance Workflow for textile and apparel SKU mapping

A strong production workflow begins with source control for tax logic. Keep one approved HSN/SAC master, version every change, and include approver name, date, and legal reference. Without this, teams silently overwrite mappings and later fail to explain why one SKU changed rate in a specific month. This single control has the highest impact on audit readiness and protects both finance and operations from repeated correction cycles.

Next, align catalog language with billing language. Product naming in e-commerce or sales CRM is often marketing-led, while invoice naming needs legal precision. Build a mapping layer so teams can search with commercial terms but bill with compliant descriptions. This is especially useful for large catalogs where one family has multiple variants, bundles, accessories, and promotional kits.

Then implement monthly exception checks. Review top-revenue SKUs, top-returned SKUs, and recently added SKUs. Compare code, GST slab, and chapter against prior month and flag all mismatches. Most practical errors are operational drift, not legal complexity. Early detection avoids expensive re-issuance effort and protects return filing timelines.

For internal controls, use maker-checker approval on all tax-master updates. The person creating mapping should not be the final approver. Keep review notes short but explicit: product type, chapter rationale, exclusions considered, and decision date. This gives enough context for future teams and prevents dependency on one individual's memory.

Finally, maintain a quarterly legal review rhythm. Even if the majority of items remain stable, periodic checks reduce confidence risk and catch edge cases before they become departmental issues. If your business operates high-volume categories, store code-level evidence for those top items and review after major notification cycles.

This disciplined approach turns classification from reactive firefighting into predictable operations. Teams invoice faster, reconcile faster, and respond to scrutiny with documented reasoning instead of manual reconstruction. For production-grade compliance programs, process quality is the durable advantage.