The 2025 GST reform rationalised India's tax slabs, and for any retailer selling over WhatsApp that means one concrete job: your in-chat catalogue prices, your MRP stickers and your invoice rates must all move to the new rate on the same effective date, together. Get the three in sync and a rate change is a quiet overnight update; leave the catalogue quoting an old price while the invoice bills the new one and every order becomes a customer dispute. Treat every specific rate and date below as something to confirm with your CA, because the slabs and the transition rules changed in the reform and continue to be clarified.
What GST 2.0 actually changed for a retailer
The headline of the 2025 reform was slab rationalisation — collapsing the older multi-slab structure toward fewer, simpler rates so that many everyday goods moved down a slab and a smaller set moved up. For a shopkeeper the politics don't matter; three operational facts do. First, the rate against many of your SKUs changed, so the tax line on their invoice changed. Second, the change carried an effective date, and stock billed before and after that date is taxed differently. Third, if your prices are published anywhere a customer can see them — a printed MRP, a website, or a WhatsApp catalogue — those published prices are now out of step with your billing until you update them. The reform didn't just change a number in your accounting software; it changed every place you quote a price, and WhatsApp is now one of those places.
Why WhatsApp commerce makes repricing urgent, not optional
A rate change used to be an accountant's problem, invisible to the customer. The moment you sell over WhatsApp it becomes a customer-facing one, because the price is now written down in a thread the customer keeps. If your WhatsApp catalogue still shows the pre-reform price and your invoice bills the post-reform rate, the customer has a screenshot of the gap and a reason to argue. The same is true in reverse — a rate cut you don't pass through in the catalogue looks like quiet profiteering. Anyone already running a WhatsApp catalogue has to treat a GST change as a catalogue-update event, not just a back-office one. This is exactly the kind of price consistency that supermarkets and grocery stores live and die by, where a single mislabelled shelf becomes a Legal Metrology complaint.
The four places a rate change has to land
A clean repricing hits all four of these on the effective date, in this order:
- Your billing / GST software — the source of truth. Update the HSN-to-rate mapping first so every new invoice bills correctly from the effective date.
- MRP re-stickering on physical stock — pre-packed goods carry a printed MRP; a rate change that moves the tax-inclusive price needs a revised MRP sticker under Legal Metrology rules for old stock (confirm the current re-stickering directive with your CA, as government notifications set the mechanics and window).
- Your WhatsApp catalogue prices — every product tile customers browse in chat must show the new tax-inclusive price, updated the same day the invoices change.
- Any broadcast or template that quotes a price — a saved "price list" template or an in-progress promo must not go out quoting the old rate after the effective date.
The failure mode is doing one or two and forgetting the rest — updating the billing software but leaving the WhatsApp catalogue stale is the most common, because the catalogue feels like marketing, not accounting. It isn't; it's a published price.
Get a 1-minute BSP audit on WhatsApp
Drop your WhatsApp number — we line-item your current invoice against Meta India rates in under 60 seconds. India-hosted, DPDP-compliant.
Pre-reform habit vs GST-2.0-ready workflow
| Task | Old habit | GST-2.0-ready on WhatsApp |
|---|---|---|
| Rate update | Change it in the billing app only | Billing + MRP + catalogue + templates, same date |
| Catalogue price | "Marketing", updated whenever | Published price — synced on the effective date |
| Transition stock | Guesswork on old vs new rate | Billed by invoice date, documented in-thread |
| Customer query | "Why is the bill different from the quote?" | Quote and invoice already match |
| Price-list broadcast | Old saved template re-sent | Template re-approved with new prices before send |
Handling transition stock and the effective date
The trap in any rate change is stock you bought or packed before the effective date and sell after it. The governing rule is generally the time of supply — the invoice date usually decides the applicable rate, not when you procured the goods — but the reform's transition provisions and any special notifications are exactly the fine print your CA is for. The practical discipline over WhatsApp: don't let a customer place an order against a catalogue price on one side of the effective date and receive an invoice from the other side without the difference being explained in the thread. If a promised price and the billed rate diverge because of the transition, say so in the conversation before you send the invoice, not after. The documented nature of WhatsApp cuts both ways — it's your evidence of a fair quote, or the customer's evidence of a broken promise.
Turning a rate change into a customer touchpoint
A repricing is also a reason to message opted-in customers with something genuinely useful — "prices updated per the new GST rates, here's the current list" reads as transparency, and for the SKUs that got cheaper it's a real offer. Two guardrails. Send it only to customers who opted in, not a bought list — a price-drop blast to strangers is still spam and no provider can promise immunity from a block on that. And send the price-list update as a properly categorised message; a broadcast of new prices is marketing and bills at the marketing rate. Done cleanly, the same reform that forced the catalogue update hands you a legitimate reason to re-engage your list.
Running it on RichAutomate
RichAutomate runs on the official WhatsApp Business API (Meta Cloud API) with ₹0 platform fee, ₹0 setup and ₹0 monthly minimum — you pay per conversation on Meta's category rates: Client Pay at ₹0.10/message plus Meta's per-conversation rate, or SaaS Pay at ₹1.20/marketing and ₹0.30/utility conversation all-in. For repricing that means the catalogue lives in one place you update once, invoice-confirmation messages bill as low-cost utility conversations, and a one-time "new GST prices" note to your opted-in list bills at the marketing rate — so a rate change costs you a catalogue edit and one broadcast, not a fixed monthly SaaS bill. A 14-day trial with 100 free credits and no card lets you set the catalogue up before the next notification lands. The full cost picture is in the WhatsApp Business API cost guide. Going live on the official API in India effectively requires GST registration for business verification — treat GST as required, not optional.
Bottom line
GST 2.0 turned a back-office rate change into a front-of-shop one, because your prices now live in a WhatsApp thread the customer keeps. Update all four places on the effective date — billing software, MRP stickers, catalogue tiles and any price-quoting template — and a rate change is a quiet overnight sync instead of a week of "your bill doesn't match your quote" arguments. Confirm every rate, effective date and transition rule with your CA, because the reform's specifics are still being clarified and both the slabs and the platform's pricing change periodically.