WhatsApp INR billing deadline: Indian Shopify stores
Meta bills Indian businesses for WhatsApp in rupees. Accounts not moved to INR by 31 December 2026 stop delivering. What to check and what to update after.
If your store is in India and its order confirmations go out over WhatsApp, there is a date in Meta's pricing documentation that deserves a calendar entry. Businesses that Meta bills in India must have every WhatsApp messaging account billed in rupees by 31 December 2026. From 1 January 2027, in the words of Meta's pricing page, Meta will no longer deliver the messages of accounts that are still in another currency.
That is seven weeks away, and it lands in the middle of the wedding season and the new year sales. A store that set up the WhatsApp Cloud API a year or two ago, picked US dollars because that was the default, and has not opened the billing screen since is exactly the store this catches. This post covers who the rule applies to, how to check in five minutes, what the move to INR does to the account, and what to update in Beacon Messenger afterwards so order messages keep sending.
What Meta has said
Three statements matter, and all three are on the pricing page under billing localisation for India.
- Local billing in India started on 1 January 2026 for solution providers and directly integrated businesses whose Sold-To country in Meta's Billing Hub is India.
- Those businesses must migrate all of their messaging accounts to INR by 31 December 2026.
- From 1 January 2027, Meta stops delivering messages from their accounts that are not billed in INR.
Note what decides it. The rule follows the country Meta bills your business in, the Sold-To country on the legal entity in Billing Hub. It does not depend on where your customers are or whether the WhatsApp number starts with +91. An Indian company messaging customers in the Gulf is covered. A Singapore company with an Indian phone number is not.
Stores that connect their own Meta account to an app, which is how Beacon Messenger works, count as directly integrated: your business pays Meta, on your card, in your account's currency. If a provider resells WhatsApp to you and sends you its own invoice, the provider owns the migration and you should ask them for a date.
Check your account in five minutes
- Open Billing Hub in Meta Business Suite and look at the legal entity for your business. If the Sold-To country is not India, stop here. The rule does not apply.
- In Business settings, open Accounts and find your WhatsApp accounts. Meta split the old WhatsApp Business Account into a messaging account and a WhatsApp account during September and October 2026, and billing sits on the messaging account. The post on that split explains which is which.
- Find the currency of each messaging account. If the settings page does not show it, the last WhatsApp charge on your card statement or Meta invoice will.
- If every account is in INR, you are done. If any is in USD or another currency, it has to move before the end of December.
Check every account in the portfolio, including the test account you created on the first day and forgot. The rule says all messaging accounts, and an unused one in dollars is one more thing to explain to Meta support in January.
What moving to INR does to the account
The awkward part is that a messaging account's currency is chosen when the account is created and cannot be edited afterwards. Meta's answer is a currency migration, available since June 2026, that creates a new messaging account in the target currency and moves billing to it. Guides that have gone through Meta's migration documentation, such as this one, summarise the result like this:
| Item | After the move |
|---|---|
| Messaging account | A new account, billed in INR, with a new account ID |
| Phone numbers | Stay registered and send under the new account |
| Templates | Most are copied across; template IDs change |
| Old account | Cannot send once the switch completes |
| Insights and invoices | History stays on the old account |
| Numbers using the Business app and the API together (coexistence) | Not eligible for the migration API; needs a different route |
Read Meta's own page before starting, and if your number runs in coexistence mode, read that section twice. The coexistence post describes that setup. We are describing the general shape here so you know which parts of a Shopify integration are touched, not replacing Meta's instructions.
What to update in Beacon Messenger afterwards
Beacon Messenger stores four things from Meta: the WhatsApp Business Account ID, the phone number ID, a permanent access token and the app secret. It sends each message through the phone number and identifies the template by its name and language, not by its template ID. That detail makes this migration lighter than it could have been. A template called order_confirmation in English is still order_confirmation in English on the new account, so your automations do not need to be remapped as long as the template was copied and approved.
What does change is the account ID. The app uses it for two jobs: loading your template list, and subscribing to the account's webhooks so that delivered, read and failed statuses come back to the message log. Until the new ID is saved, the app is still looking at the old account. Do this once the migration reports complete:
- In Meta Business settings, copy the ID of the new INR messaging account.
- Check that your system user still has access to the new account and that the permanent token works against it. If Meta asks you to assign the asset again, do that first.
- In Beacon Messenger, open WhatsApp account and click Update credentials. Paste the new ID in WhatsApp Business Account ID, confirm the phone number ID against what Meta now shows, re-enter the token and app secret, and click Save credentials. Saving subscribes the app to the new account.
- Click Refresh templates. Compare the count and the status of each template with what you had. A template that did not copy, or came across as pending, needs to be resubmitted in WhatsApp Manager before its automation can send.
- Use Send a test message with your own number.
- Place a test order, or wait for the next real one, and confirm in the message log that it moves from sent to delivered. Delivered proves the webhook subscription on the new account is working.
The credentials post has more on each field, and the status reference explains what the app does with a template that is not approved.
If you miss the date
Meta's wording is that messages will no longer be delivered. It has not published which error code the API will return, so we will not guess. What we can say is how the app behaves when Meta refuses a send for any account-level reason: the row appears in the message log as failed with the error Meta returned, the order itself is untouched in Shopify, and a refusal of that kind is not retried automatically. Once the account is fixed, failed rows can be retried from the log, as covered in finding one message in the log.
Shopify's own email notifications are not affected by any of this, which is one more reason to leave them on. A customer who gets no WhatsApp message on 2 January still has the email.
Pick a quiet day, not 30 December
Meta's page gives a date without a time of day or a time zone, and a migration that copies templates can leave one or two waiting for review. Both are arguments for doing this in November or the first half of December, on a weekday morning when order volume is low and someone can watch the log for an hour afterwards. For cash on delivery stores in particular, where the confirmation message is what keeps return-to-origin rates down, a silent gap of a few days in early January is expensive.
One side effect is pleasant. Paying in rupees against Meta's INR rate card removes the currency conversion from every charge, and the guides tracking the two rate cards report that the rupee prices currently work out lower than the dollar ones for messages to Indian numbers. Meta's rate cards are the source to check for today's figures.
Beacon Messenger's own plans are separate from all of this: a flat monthly fee billed through Shopify, with Meta's per-message charges going straight from Meta to you. If you are setting up WhatsApp order notifications for an Indian store for the first time, create the messaging account in INR from the start and this deadline never applies to you. See the plans.
Questions
Does the WhatsApp INR billing deadline apply to my Shopify store?
It applies if the Sold-To country on your business's legal entity in Meta's Billing Hub is India and you pay Meta directly for WhatsApp Cloud API messages. It does not depend on where your customers are or on the country code of your WhatsApp number.
What happens on 1 January 2027 if my account is still billed in USD?
Meta's pricing documentation says it will no longer deliver messages from non-INR messaging accounts of businesses covered by the rule. Order confirmations, shipping updates and cash on delivery confirmations sent through that account would stop reaching customers until the account is moved.
Do I need to rebuild my automations in Beacon Messenger after moving to INR?
Usually not. Automations refer to templates by name and language, which stay the same when templates are copied to the new account. You do need to save the new account ID under Update credentials and click Refresh templates, then check that every template you use is approved.
Will my WhatsApp phone number change?
No. According to Meta's migration documentation the phone number stays registered and continues sending under the new INR account. Customers see the same number and display name.
More guides
- WhatsApp Business app drops order tools: move orders to Shopify
- A customer replied STOP to a WhatsApp order message. Now what?
- WhatsApp marketing templates leave the Cloud API in October 2027
- WABA to Messaging Account: what changes for Shopify WhatsApp
- Order paid later, refunded or edited: which WhatsApp messages send
- Edited your WhatsApp automation? What queued messages send
- How to add a WhatsApp chat button to your Shopify store (2026)
- How to send Shopify order confirmations and shipping updates over WhatsApp with the official Cloud API
- Cash on delivery on Shopify: confirm orders over WhatsApp before you ship
- Recovering abandoned checkouts on Shopify with WhatsApp, the compliant way
- Why WhatsApp apps get your number banned: linked device vs API
- How a "free" WhatsApp app for Shopify ends up charging you
- Por qué una app de WhatsApp "gratis" para Shopify te cobra
- Pushdaddy or SuperLemon alternative: WhatsApp apps compared
- How to verify Shopify WhatsApp notifications were delivered
- Chat button still on your store after uninstalling the app?
- WhatsApp API pricing changes on Oct 1, 2026: Shopify impact
- Setting up the WhatsApp Cloud API with Meta's MCP and an AI agent
- WhatsApp chat outside business hours: what shoppers should see
- WhatsApp product sharing on Shopify: tracking dark social
- WhatsApp template rejected? Fixing Shopify order templates
- One WhatsApp number or two? Shopify notifications & support
- Shopify Canvas and Beacon Messenger: what works today
- Shopify now collects WhatsApp marketing consent at checkout. Here is what it changes
- Split shipments on Shopify: how many WhatsApp updates to send
- WhatsApp's 250-a-day messaging limit and your Shopify store
- WhatsApp, SMS or email for Shopify order notifications?
- WhatsApp is down: what happens to your Shopify order notifications
- Shopify orders with no phone number: why WhatsApp messages get skipped
- Shopify rollout discounts and WhatsApp order messages
- Add a Track order button to WhatsApp order messages
- Which Shopify orders trigger a WhatsApp message?
- The abandoned checkout timer restarts every time the shopper comes back
- Blank names, twelve-item orders: what WhatsApp merge fields fall back to
- Who looked at your customers' phone numbers? The access log behind a WhatsApp app
- Send a WhatsApp test message before your first order: what the Connect and Test buttons check
- Disconnect, update credentials, app secret: what each does
- COD reply not tagged: how Beacon Messenger matches replies
- WhatsApp template language: why name alone is not enough
- Finding one WhatsApp message in the Beacon Messenger log
- WhatsApp automation is On but nothing sends: a checklist
- Mapping WhatsApp template variables to Shopify order fields
- Every WhatsApp chat button setting in the Shopify theme editor
- WhatsApp template examples for Shopify: order, shipping, COD, cart
- The Share on WhatsApp block, setting by setting
- WhatsApp order messages when customers speak several languages
- Reading the Beacon Messenger dashboard: sent, delivered, failed, skipped
- Shopify batch fulfilment: what happens to 250 WhatsApp shipping messages
- WhatsApp template status: approved, pending, paused, disabled, and what sends
- WhatsApp quality rating: the field on the Connected number card
- COD returns (RTO) on Shopify: confirm orders on WhatsApp first
- WhatsApp error codes on failed messages: a reference
- WhatsApp display name: what customers see on your order messages
- Shopify Messaging WhatsApp automations vs Beacon Messenger
- OXXO, bank transfer and pay-later orders: when the WhatsApp confirmation goes out
- How many WhatsApp messages will Black Friday send? Sizing your plan
- WhatsApp usernames and BSUIDs: what changes for Shopify order messages
- Reconciling your WhatsApp bill with the Beacon Messenger log
- Track with Shop vs WhatsApp shipping updates on Shopify
- Meta changed my WhatsApp template from utility to marketing
- Shopify's new app security review: what Beacon Messenger can access
- A shopper cancels their own Shopify order: what WhatsApp sends
- Customer erasure in 5 days: what the WhatsApp log keeps
- WhatsApp template headers: text, image or document?
- Gift orders on WhatsApp: buyer's phone or the recipient's?
- WhatsApp order messages at night: when each one sends
- Downgrading a WhatsApp app plan after peak season: what changes
- Shopify subscription renewals and WhatsApp order messages