Edited your WhatsApp automation? What queued messages send
Beacon Messenger queues every Shopify WhatsApp message and re-reads the automation at send time. What happens if you edit the template, pause or disconnect.
You switch the order confirmation to a new template at 3 pm. At 3:04 a message goes out for an order placed at 2:59. Which template did it use? Or you pause the abandoned checkout automation for the weekend while twenty checkouts from Friday evening are still inside their delay. Do those twenty send on Monday, or ever? Merchants ask this in slightly different forms every time they change something, and the answer is the same every time, because Beacon Messenger has one rule for it.
Every message is queued, even the instant ones
Nothing is sent from inside a Shopify webhook. When an order, fulfillment or checkout arrives, the app works out who the recipient is, whether they consented and which order fields the template will need, and writes that as a scheduled message with a run time. Order and cash-on-delivery confirmations get a run time a few seconds out, which is the short window that lets a cancellation pull them back (the which orders trigger a message post covers that). Shipping updates run as soon as the worker picks them up. Abandoned checkout reminders get a run time hours later, whatever delay you configured.
A worker then takes due messages in run-time order and delivers them one by one. The queue row carries two things: a dedupe key, which is the same id the message will have in your log, so a duplicate webhook can never produce a second send, and a payload with the order data frozen at the moment it was queued. Everything else is looked up when the message is actually sent.
What is frozen and what is live
| Thing | When it is decided | Consequence |
|---|---|---|
| Recipient phone number | Queue time | A phone number edited on the order after the fact does not change where the message goes |
| Marketing consent flag | Queue time | Consent is recorded as it was at checkout |
| Order fields (name, totals, items, tracking) | Queue time | The message describes the order as it was when the event happened |
| Automation on or off | Send time | Pausing stops everything still in the queue |
| Which template and language | Send time | The template selected when the message is due is the one filled in |
| Require consent setting | Send time | Turning it on applies to queued messages too |
| WhatsApp connection | Send time | Disconnecting skips queued messages as not connected |
| Monthly plan allowance | Send time | A message that was queued under the cap but sends over it is skipped |
The split is deliberate. Order data belongs to the moment the customer acted, so it is captured then. Your settings belong to you, and the most recent version of them is the one you mean, so the sender asks for them fresh. In practice this gives you an emergency brake: switching an automation off stops messages you have not seen yet, not only future ones.
The checks, in the order they run
- Is a message with this id already sent, delivered or read? Then stop; this is a duplicate.
- Is the automation for this trigger enabled? If not, the message is logged as skipped with the reason automation disabled.
- Does the automation have a template selected? If not, skipped as no template.
- Is a WhatsApp number connected? If not, skipped as not connected.
- Is there a recipient? If the frozen payload has no phone, skipped as no phone.
- If the automation requires consent, did the customer give it? If not, skipped as no consent.
- Is there room in this month's allowance? If not, skipped as quota exceeded.
- Does the selected template name and language still exist on your WhatsApp account, and is it approved? If not, skipped as template not found.
- Fill the template from the frozen payload and send. A transient failure from Meta is retried with increasing waits; a permanent one is logged as failed with the error code.
Every skip is a row in the Messages log with its reason, so a pause does not make messages disappear; it makes them visible as skipped. The checklist for an automation that is on but silent explains each reason, and the log search post shows how to filter by it.
Four scenarios
- You change the order confirmation template at 3 pm. Orders placed at 2:59 and still in their short window send with the new template; the payload has the order data, the template is read at send. If the new template uses a merge field the old one did not, the field is filled from the same frozen payload, which has every supported order field regardless of which template was selected when it was queued.
- You pause the abandoned checkout automation on Friday night with twenty reminders due over the weekend. All twenty are skipped as automation disabled when their time comes. Switching the automation back on Monday does not resurrect them; the skip is final. New checkouts from Monday queue normally.
- You disconnect the WhatsApp number to move to a new one, and reconnect two hours later. Messages due during the gap are skipped as not connected. Messages due after you reconnect send through the new number, with whichever template of that name exists on the new account; if the new account does not have it, they are skipped as template not found until you select one that exists.
- You cross your plan's monthly allowance on the 28th. Messages already queued are not exempt; each one is checked against the counter when it is due. Upgrading mid-month raises the allowance for everything still in the queue.
What a template edit on Meta's side does
Editing a template's text in WhatsApp Manager sends it back for review. While it is pending, the sender still finds the template by name and language, submits it, and Meta rejects the send with a template status error, which is recorded as failed, not skipped. The template status post goes through pending, paused and disabled in detail. If you need to change wording during a busy period, create the new template under a new name, wait for approval, then select it in the automation; messages due after that moment use it, and nothing is in limbo.
If you want a message to go out anyway
A skipped message can be retried from the log once you have fixed the reason: switch the automation on, select a template, reconnect. The retry re-queues the same id with the same frozen payload and the same run-time rule, so it goes through the full list of checks again against your current settings. A message that is skipped for no phone or no consent cannot be fixed by a setting, because the missing piece is in the payload; those are the customers to contact another way.
Questions merchants ask
If I switch templates, do messages already in the queue use the old or the new template?
The new one. The template is read when the message is due, not when the order came in. Only the order data (recipient, consent, order fields) is frozen at queue time.
Does pausing an automation delete the pending messages?
No. They stay in the queue until their run time, and are then logged as skipped with the reason automation disabled. Turning the automation back on later does not send them; they can be retried individually from the log.
I changed the customer's phone number on the order. Will the message go to the new number?
Not if the message was already queued. The recipient is part of the frozen payload. For a message that has not been sent yet, the practical fix is to let it skip or fail, then message the customer directly from WhatsApp.
Can a message be sent twice if I retry it?
No. The log id is the dedupe key, and a message whose id is already sent, delivered or read is never sent again, whether the duplicate comes from a webhook or from a retry.
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
- 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 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