HSN Codes for Food Products - Fresh, Packaged and Processed

How food HSN treatment shifts across fresh, packaged, and processed states with GST implications.

Fresh Vegetables and Fruits - 0% GST

Fresh produce generally starts with Chapter 07 and Chapter 08 references in unprocessed form.

Cereals and Pulses - 0% GST

Cereal categories often start from Chapter 10 and include examples like HSN 1006.

Dairy Products - 0% to 12% GST

Dairy treatment varies by product state; fresh milk references often include HSN 0401.

Packaged and Branded Food - 5% GST

Packaged categories should be validated carefully since branding and processing level can alter treatment.

Processed and Ready-to-Eat - 12-18% GST

Higher processing typically means higher slab exposure. Use item-level documentation for every variant.

How Branding Affects GST Rate

Branding and declaration format can materially affect treatment. Keep legal review integrated with packaging updates.

Practical Compliance Workflow for food product classification

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.