WhatsApp's 250-a-day messaging limit and your Shopify store
New WhatsApp Business accounts can message 250 customers a day. What counts, how order notifications use it up, and how the limit grows past 2,000.
Somewhere around the 250th order of a busy day, a store that just connected WhatsApp sees its notifications start failing. Nothing is wrong with the template, the token still works, and the first 249 customers got their confirmation. The 250th did not, and neither will anyone else until tomorrow. This is WhatsApp's messaging limit, and it catches Shopify merchants out because nothing in the admin warns about it and the number is far lower than most people assume.
This post explains what the limit actually counts, how a typical order-notification setup consumes it, how Meta raises it, and what Beacon Messenger does when a send bumps into it. It is written for stores on the official Cloud API; if you connect WhatsApp by scanning a QR code, the constraints are different and worse, and we covered them in the linked-device post.
What the limit counts
Meta's Messaging Limits page describes the limit as the number of unique customers a business can start a conversation with in a rolling 24-hour period. Newly created business portfolios start at 250. Three words in that sentence do most of the work.
- Unique. Messaging the same customer five times in a day counts once. An order confirmation, a shipping update and a delivery notice to one person are one unit of your limit, not three.
- Start. Only business-initiated conversations count. If a customer writes to you first, your replies within the 24-hour service window are free of the limit, however many you send.
- Rolling. It is not reset at midnight. A customer you messaged at 3 pm stops counting at 3 pm the next day. In practice that means a bad afternoon bleeds into the next morning.
Every message Beacon Messenger sends on a Shopify event is business-initiated, because the customer placed an order rather than messaging you. Order confirmations, shipping updates, cash-on-delivery confirmations and abandoned-checkout reminders all use approved templates and all count toward the limit, one per customer per day.
How quickly a Shopify store reaches 250
The arithmetic is simpler than most quota maths. Count the distinct customers who place an order in your busiest 24 hours, add the distinct customers who abandon a checkout if you remind them, and compare with 250. A store doing 80 orders on a normal day is fine. The same store on the first day of a sale, with 300 orders and 150 abandoned checkouts, is not, and the people who miss out are the ones who ordered last, which on a launch day are the ones most likely to message asking where their confirmation is.
Two things make the day worse. The first is testing: every test order to a new phone number is a unique customer. The second is multiple numbers under one portfolio. The documentation now reports the limit through a field on the business portfolio rather than the phone number (the old per-number field is marked deprecated), so a support number and a notifications number in the same portfolio draw on the same allowance.
How the limit grows
The same page sets out the path from 250 to higher limits, and it is not purely a matter of waiting. To move to 2,000, a portfolio has to complete one of three scaling paths: verify the business, have the partner that onboarded it verify the business, or send 2,000 delivered template messages to unique customers outside service windows within a rolling 30 days, using templates with a high quality rating. Meta then reviews message quality and either approves or defers the increase.
Beyond 2,000, the increases to 10,000, 100,000 and unlimited happen automatically, and the documented criteria are that quality stays high across every phone number and template in the portfolio and that the business has used at least half of its current limit in the previous seven days. A store that never gets near its limit is not asked to prove it can handle more, which is reasonable but means a slow store on a sudden good day cannot borrow capacity it has not earned.
| Limit | How you get there |
|---|---|
| 250 | Default for a newly created business portfolio |
| 2,000 | Business verification, partner verification, or 2,000 delivered high-quality template messages in 30 days, then a quality review |
| 10,000 and up | Automatic, when quality stays high and at least half the current limit was used in the last 7 days |
The practical lesson is to verify the business before the day you need the headroom, not during it. Business verification is done in Meta Business Suite and asks for documents that show the legal name and address of the company. If you set up WhatsApp a month before a launch and verify straight away, you give yourself a chance of the 2,000 limit arriving in time. Set it up the week before and you will be running the launch on 250.
What happens inside Beacon Messenger at the limit
When Meta refuses a send because the limit has been reached, the Cloud API returns an error rather than silently dropping the message. Beacon Messenger records the message as Failed on the Messages page with Meta's error code and text, so you can see exactly which customers were affected. Throughput errors (code 130429), where Meta asks the app to slow down for a moment, are retried automatically; a messaging-limit refusal is not retried, because the correct time to retry is up to a day later and by then a shipping update may have overtaken the confirmation.
That leaves you with a list and a decision. For order confirmations, the honest answer is that Shopify already emailed the customer and you can let it go. For cash-on-delivery confirmations, where the message asks the customer to confirm the order before you dispatch it, the list matters: those orders need a phone call or an email instead. The delivery verification post walks through reading the Messages page and cross-checking with WhatsApp Manager.
Choosing which messages spend the limit
If you are close to the ceiling, decide which notification you would rather lose. Each trigger in Beacon Messenger can be switched off independently, and because the limit counts unique customers rather than messages, turning off the shipping update does not help a store whose problem is too many distinct buyers. What helps is removing a trigger that reaches people who did not order.
- Keep the order confirmation on. It reaches only people who bought, and it is the message customers notice is missing.
- If you send abandoned-checkout reminders, they reach a different and larger set of people than orders do. Pausing them on a launch day can keep every buyer inside the limit.
- Hold off on test orders to new numbers while the day is busy. Use a number you have already messaged today.
- Reply to inbound chats freely. Replies within a service window do not touch the limit at all.
This week's change on the billing side
The limit is about how many people you can reach. A separate change this week is about paying for it. From 1 October 2026, Meta charges per delivered service message, the free-form replies sent inside a customer's 24-hour window, at the same per-market rate as utility and authentication messages, and businesses without a payment method on file by 30 September had service-message delivery stopped (Times of India, News18). If replies to customers have stopped going through since Wednesday, check the payment method on the WhatsApp Business account before you look at anything else. The rate changes themselves are covered in our pricing post.
Beacon Messenger's own plans cap messages per month, from 50 on Free to 10,000 on Pro, and the cap is checked before every send. It is a different ceiling from Meta's and the two do not talk to each other: a Pro plan does not raise Meta's 250, and business verification does not raise ours. Pick the plan that matches your order volume, and verify your business so Meta's side keeps up.
Frequently asked questions
Why can my WhatsApp Business account only message 250 customers a day?
Meta gives every newly created business portfolio a messaging limit of 250 unique customers in a rolling 24-hour period for business-initiated conversations. It is a spam control, not a billing tier. The limit rises to 2,000 once the business is verified or has a record of high-quality template sends, and higher limits are granted automatically after that.
Do Shopify order notifications count toward the WhatsApp messaging limit?
Yes. An order confirmation or shipping update is a template message the business sends first, so it opens a business-initiated conversation and counts. Several messages to the same customer within 24 hours count once, so a store's exposure is the number of distinct customers it messages per day, not the number of messages.
How do I increase the WhatsApp messaging limit?
Complete one of Meta's scaling paths: verify your business in Meta Business Suite, have the partner that onboarded you verify it, or send 2,000 delivered template messages to unique customers in 30 days with high quality ratings. After a quality review the limit moves to 2,000, and further increases are automatic when quality stays high and you use at least half of your current limit in a week.
What does Beacon Messenger do when the WhatsApp messaging limit is reached?
The Cloud API refuses the send and Beacon Messenger records the message as Failed with Meta's error code and message, so you can see which customers were affected. It does not retry those messages the next day, because a stale confirmation can arrive after the shipping update. Shopify's own email notifications still go out as normal.
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, 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 INR billing deadline: Indian Shopify stores
- 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