Ecommerce Website Development in Pune: What GST 2.0's New Slabs Mean for Your Checkout and Product Pages
If your online store hasn't touched its tax display logic since September 2025, it's overdue for a review — and the review needs to happen in the codebase, not just the accounts ledger. GST 2.0 rationalised India's tax structure by scrapping the 12% and 28% slabs entirely and moving to a simpler 0%, 5%, 18%, and 40% structure, effective 22 September 2025. Compensation cess was scrapped on nearly everything except a short list of tobacco and pan masala products. For a store selling anything that used to sit in the old 12% or 28% brackets, the product-level tax rate genuinely changed, and every place that rate is hard-coded, cached, or assumed by your ecommerce website — product pages, cart calculations, invoices, marketplace listings — needs to reflect the new rate correctly, not just the finance team's spreadsheet.
This is squarely a web development problem, not only an accounting one, which is why it belongs in a conversation about ecommerce website development in Pune rather than only with your CA. A GST rate that's correct in your accounting software but wrong on your product page or at checkout creates a mismatch that shows up as a customer complaint, a failed reconciliation, or in the worst case, a compliance question during a GST audit.
What Actually Changed, in Practical Terms
The GST Council announced the rationalisation on 3 September 2025, and it took effect nineteen days later. The core structural change: the 12% and 28% slabs were abolished, with items redistributed into either the 5% band (many daily essentials — food products, medicines, milk-based items, EVs, and insurance moved here) or the standard 18% band. A new 40% bracket was introduced specifically for luxury and sin goods — tobacco and tobacco products, pan masala, aerated and caffeinated beverages, large passenger vehicles, motorcycles above 350cc engine capacity, yachts, personal aircraft, casinos, and online money gaming. Compensation cess, which used to apply on top of GST for many of these categories, was scrapped from 22 September 2025 for everything except a narrow list of tobacco-related products where cess continues to apply for now.
For e-commerce operators specifically, marketplace and platform commission services are taxed at 18%, with the notable exception of restaurant services delivered through food-delivery platforms, which remain at 5%. E-commerce operators are also required to continue collecting 1% Tax Collected at Source (TCS) on the net value of taxable supplies made through their platform — this obligation didn't change with GST 2.0, but it's worth confirming your platform's TCS calculation logic is still correctly separated from the underlying product GST rate, since the two are calculated independently and sometimes get conflated in custom-built checkout systems.
The Slab Change in One Table
| Old structure (pre-22 Sep 2025) | New structure (GST 2.0) | What moved here |
|---|---|---|
| 0% | 0% | Unchanged — most exempt categories stay exempt |
| 5% | 5% | Many essentials stayed, plus items that moved down from 12% — food products, medicines, milk-based items, EVs, insurance |
| 12% | Abolished | Redistributed into 5% or 18% depending on the specific item |
| 18% | 18% | Standard rate — largely unchanged, plus items that moved down from 28% where applicable, and e-commerce operator commission services |
| 28% | Abolished | Redistributed into 18% for most goods, or 40% for the specific luxury/sin list |
| — | 40% (new) | Tobacco, pan masala, aerated and caffeinated drinks, large passenger vehicles, motorcycles above 350cc, yachts, personal aircraft, casinos, online money gaming |
The practical takeaway for a store owner: if none of your products fell into the old 12% or 28% brackets, your rate exposure from this change is minimal — a quick confirmation is still worth doing, but you're not likely to find surprises. If your catalogue included anything in those two abolished brackets, a rate audit isn't optional; it's the only way to know which direction each affected product moved.
Where This Breaks on a Typical Ecommerce Website
Hard-coded tax rates in product data
The most common failure point is a product catalogue where GST rate was entered once, at the time a product was added to the store, and never revisited. If your store was built before September 2025 and products were tagged with a 12% or 28% rate that's now supposed to be 5%, 18%, or 40%, those tags need auditing product-by-product against the new HSN-code-to-rate mapping, not assumed to have updated automatically just because the law changed.
Cached pricing and pre-generated invoices
Some ecommerce platforms cache calculated prices (including tax) for performance reasons, regenerating them only when a product is edited. If a product's underlying GST rate changed but nobody edited the product record itself after 22 September 2025, a cached price shown to a customer, or a PDF invoice template that hard-codes a tax line, can silently keep showing the old rate long after it stopped being correct.
Marketplace listings versus your own website
A business selling on both its own website and third-party marketplaces (Amazon, Flipkart, Meesho) needs the GST rate to match across every channel. It's a genuinely common error for a business to update pricing on its own site correctly while a marketplace listing — synced less frequently, or maintained by a different team — continues showing the old rate, creating a discrepancy that a sharp-eyed customer or, worse, a marketplace's automated compliance check can flag.
GST rate display on the product page itself
Many Indian ecommerce sites show "inclusive of all taxes" pricing without breaking out the GST rate on the product page, which is legally acceptable in most cases, but any site that does show a rate explicitly (common for B2B-facing stores where the buyer needs the GST breakdown for their own input tax credit claim) needs that displayed figure to be accurate, not a leftover from before the rate change.
A Practical Audit Checklist
- Export your full product catalogue with current GST rates and cross-check each HSN code against the post-GST-2.0 rate mapping — this is a spreadsheet exercise your CA or GST consultant should lead, but your developer needs the corrected mapping to actually apply it in the system.
- Confirm whether your platform calculates tax at the point of sale dynamically (from a rate stored against the product or HSN code) or generates and caches prices in advance — if it's the latter, force a full re-generation after correcting the underlying rates.
- Check invoice templates specifically, since these are often built as static templates with assumptions baked in about which tax lines to show, rather than dynamically pulling the current rate at generation time.
- Reconcile pricing across every sales channel — your own website, marketplace listings, and any point-of-sale system used in a physical store connected to the same inventory — to confirm they all reflect the same corrected rates.
- Separately verify your TCS collection logic is still functioning correctly and hasn't been affected by whatever code changes were made to fix product-level GST rates, since the two calculations often live in the same checkout module even though they're legally distinct.
Platform-Specific Notes Worth Knowing
WooCommerce stores
WooCommerce typically manages tax through tax classes assigned to products, with rates configured centrally in WooCommerce's tax settings rather than hard-coded per product — which is good news, since correcting a tax class's rate in one place propagates to every product assigned that class. The audit work here is less about finding hard-coded rates and more about confirming every product is assigned to the correct tax class after the slab reshuffle, since a product that moved from 12% to 5% needs to be reassigned to a different class, not just have its existing class's rate edited (which would incorrectly change the rate for every other product sharing that class).
Shopify stores
Shopify's tax settings are similarly centralised, but Indian GST handling on Shopify often relies on a third-party tax app or a custom Liquid template modification for GST-inclusive pricing display and invoice generation. If your store uses one of these apps, check specifically whether the app vendor has published an update reflecting GST 2.0's rate changes — some tax apps ship generic slab tables that need a vendor-side update before your store reflects the new rates correctly, and that update may not happen automatically without you asking.
Custom-coded stores
A custom-built ecommerce platform has the most flexibility and the most risk in roughly equal measure. Flexibility, because a well-architected custom system should store GST rates against an HSN-code lookup table that can be corrected centrally, exactly like a properly configured WooCommerce or Shopify setup. Risk, because a custom system built without that separation — where a developer, under time pressure at some point in the past, hard-coded a rate directly into a checkout calculation or an invoice template to hit a deadline — carries technical debt that only becomes visible when a change like GST 2.0 forces it to the surface. This is exactly the kind of issue worth raising with whichever developer or agency maintains your custom platform, framed specifically as "show me where our GST rate lives in the codebase," not just "please fix the checkout."
Testing the Fix Properly
Once rates are corrected, test with more than a single sample product. Pull one product from each affected bracket — something that moved from 12% to 5%, something that moved from 12% to 18%, something that moved from 28% to 18%, and something new that now falls under the 40% bracket if your catalogue includes any such item — and run each through a complete test purchase: product page display, cart total, checkout tax breakdown, and the generated invoice or receipt. Confirm the number matches what your GST consultant has confirmed as correct for that specific HSN code. Testing only the checkout total and assuming the invoice template inherits the same logic is a common shortcut that misses template-level hard-coding, which is precisely the failure mode described earlier in this article.
Who Should Actually Do This Work
The rate mapping itself — which HSN code now falls under which slab — is a GST compliance question your CA or tax consultant should confirm; getting this wrong at the source makes any amount of correct coding moot. Once the correct rates are confirmed, applying them across your product catalogue, checkout logic, and invoice templates is development work, and it's worth treating as a proper scoped task rather than a quick patch — a rushed fix that corrects the checkout total but misses the PDF invoice template, for instance, creates exactly the kind of mismatch that causes problems later. For a fuller look at the broader compliance landscape your checkout and invoicing setup needs to handle, our guide on GST, invoicing and legal compliance for ecommerce websites covers HSN codes, e-invoicing thresholds, and consumer-protection display requirements beyond the GST 2.0 rate change specifically.
Do I need to rebuild my ecommerce website because of GST 2.0?
No — for the large majority of stores, this is a data-correction and testing task, not a rebuild. The exception is a store built with tax rates hard-coded directly into page templates rather than pulled from a product database or HSN-code lookup table, which is a sign of a more fundamentally inflexible build that GST 2.0 has simply exposed; if that's your situation, it's worth treating this as a prompt to discuss a more maintainable architecture with your developer, not just patching around the immediate problem.
How do I know if my products were affected by the slab changes?
Cross-reference your product HSN codes against the published post-GST-2.0 rate schedule (available through the GST Council's official notifications or a reliable tax reference like ClearTax's updated rate list). Products that were previously taxed at 12% or 28% are the ones most likely to have moved; products that were already at 5% or 18% are more likely — though not guaranteed — to be unaffected.
What happens if I don't fix this and continue charging the old rate?
Overcharging GST on a sale creates a liability to refund the excess to the customer or account for it correctly with the tax department; undercharging creates a shortfall the business owes regardless of whether it was collected from the customer. Neither is a technical inconvenience — both are compliance exposures with real financial consequences, which is why this is worth prioritising over less urgent development backlog items.
Does this affect the 1% TCS I already collect as an e-commerce operator?
Not directly — TCS is calculated as a percentage of the net taxable value of supplies made through your platform, and that obligation and rate didn't change under GST 2.0. What can go wrong is a checkout system where the code calculating TCS was written expecting to reference the same rate table used for product GST, and a rushed fix to one accidentally breaks an assumption the other was relying on. This is exactly why testing a full transaction end-to-end, rather than checking the headline GST total alone, matters — a TCS miscalculation is easy to miss if you're only glancing at the customer-facing total.
Where This Fits With Other 2026 Ecommerce Priorities
GST 2.0 compliance sits alongside other technical priorities Pune ecommerce businesses have been weighing this year — our guide on ONDC integration for your online store covers one of the bigger strategic decisions, but it shouldn't take priority over a straightforward compliance fix that has a real financial and legal cost attached to getting wrong.
How We Approach This at Govindani Infotech
When we build or maintain an ecommerce website, product GST rates are pulled dynamically from an HSN-code-linked rate table rather than hard-coded per product, specifically so a change like GST 2.0 can be corrected centrally in one place rather than requiring a product-by-product manual edit across a large catalogue. If your store wasn't built that way and you're now facing exactly this kind of scattered correction work, we can audit the existing build and recommend whether a targeted fix or a more structural change makes sense for your specific platform.
Get in touch through our contact page if you want a second pair of eyes on whether your checkout, product pages, and invoicing are correctly reflecting the current GST slabs before it becomes a bigger reconciliation problem at year-end — this is the kind of fix that's cheap to do properly now and considerably more expensive to unwind after months of incorrect invoices have already gone out to customers.
A note on scope: this article explains the practical website and system implications of the GST 2.0 rate change. It is not tax advice — confirm the correct HSN-code-to-rate mapping for your specific products with a qualified GST practitioner before making any changes to your live pricing or invoicing systems.
Sources: Kotak Mutual Fund — GST 2.0: New 5% & 18% slabs effective 22 Sep 2025, ClearTax — GST Rates in India 2026: Updated list of tax slabs, Busy — New GST on E-Commerce Operator 2026: 18% rate on e-commerce, TaxTMI — GST 2.0 Next Generation Reform: Streamlined notifications effective September 22, 2025