COD reply not tagged: how Beacon Messenger matches replies
A customer answered the cash-on-delivery message but the order has no tag. The five checks a WhatsApp reply must pass, which words count, and where to look.
The cash-on-delivery check is the one automation where the customer talks back, and that is also why it is the one that raises support tickets. The message went out, the customer wrote yes, and an hour later the order still has no beacon-cod-confirmed tag. Nothing is broken in most of these cases. A reply has to pass five checks before Beacon Messenger will touch the order, and each of them exists so the app never tags an order on the strength of a message it cannot tie to that order. This post walks through the five, in the order the app applies them, and ends with where to look in the message log.
1. The reply has to be a reply
WhatsApp tells the app which message a customer is answering only when the customer actually answers it: by tapping one of the template's buttons, or by long-pressing the message and choosing Reply. In both cases Meta attaches the original message's id to the incoming webhook. A fresh message typed into the thread carries no such reference, even if it says yes and arrives thirty seconds after the question.
The app does nothing with a message that has no reference. It cannot know which order the yes belongs to, and guessing (the most recent order, the only unconfirmed one) is exactly how the wrong order gets confirmed. This is the single biggest reason a reply goes unrecorded, and it is why the automation page warns when the template you picked has no reply buttons: a button tap always carries the reference, a typed yes often does not.
2. The original message has to be a COD check from your shop
With a reference in hand, the app looks up the original message in your message log by its WhatsApp id. It has to find a row that belongs to your shop and whose trigger was the cash-on-delivery confirmation. A customer who taps Reply on a shipping update and types yes is answering a message the app sent, but not a question, so the reply is ignored. The same goes for messages sent from WhatsApp Business directly rather than through an automation: they are not in the log, so there is nothing to match.
3. The number has to match
Every webhook from Meta names the phone number it arrived on. The app checks that this is the number connected to your shop before it reads anything else, and discards the event if not. If you have two numbers and the COD template went out from the one that is not connected to Beacon Messenger, the replies land somewhere the app never looks.
4. The text has to start with a word the app knows
Once the reply is tied to a COD message, the app decides what it means. It reads, in this order of preference: the payload of a tapped button, the visible text of that button, the id or title of an interactive reply, the title of a list choice, and finally the plain text the customer typed. Buttons win, which is another reason to use them: a button labelled Confirm order classifies the same way every time, whatever language the customer speaks.
Typed text is matched against two short lists, and the match is anchored to the start of the message. The first word has to be one of these:
| Result | Recognised first words |
|---|---|
| Confirmed | confirm, confirmed, confirmar, confirmo, yes, y, si, sí, ok, okay, sim, oui, ja, haan, ha, confirm order, ✅, 👍 |
| Cancelled | cancel, cancelled, cancelar, cancelo, no, nope, não, nao, non, nein, nahi, nahin, ❌, 👎 |
| Other | Anything else, including a sentence that contains yes but does not begin with it |
So Yes please and OK thanks are confirmations, and No, cancel it is a cancellation. I confirm, Sure, and Yes but can you deliver after 6pm are all Other, because the first word is not on the list or because the message starts with something else. Case does not matter. The anchor is deliberate: a reply like no problem, confirm it would otherwise be read as a cancellation, and the cost of a wrong tag is higher than the cost of a missed one.
5. Other is recorded, not acted on
A reply classified as Other is written to the message log against the original COD message, with the text the customer sent (trimmed to 200 characters), and nothing else happens: no tag, no acknowledgement. It is not lost. On the Messages page the original row shows a Reply badge with the classification and the text, so a Reply: other:Yes but can you deliver after 6pm line is a customer who did answer and needs a human to read it. Confirmed and cancelled replies show in the same place, which makes the badge the first thing to check when a tag is missing.
What happens when a reply passes
For a confirmed reply the app removes beacon-cod-cancelled from the order if it is there and adds beacon-cod-confirmed. For a cancelled reply it does the reverse. The removal comes first so an order never carries both tags, and so a customer who answers twice ends up with their latest answer. The app does not cancel the Shopify order, restock anything or refund anything; the tag is a signal for you, or for a Shopify Flow you build, as described in the COD guide.
Then the customer gets a short acknowledgement, in the language of the COD template you selected, confirming or cancelling with the order number. If the tag write fails, because the order was deleted or the app lost access, the failure is logged against the message and the acknowledgement still goes out, so the customer is never left waiting on your side of a problem.
A checklist for a missing tag
- Open Messages and find the COD row for the order. No Reply badge at all means the reply never reached the app: the customer typed a new message rather than replying, or it arrived on a different number.
- A badge reading other means the words were not recognised. Read the text and act on it by hand, then consider whether the template needs buttons.
- A badge reading confirmed or cancelled with no tag on the order means the tag write failed. The error is recorded on the same row.
- Check the automation page for the No reply buttons warning. Adding Confirm order and Cancel order buttons to the template, and waiting for Meta to approve them, removes most of the typed-text cases.
- If customers keep writing in a language whose words are not on the list, tell us. The lists are short on purpose and we add words when a market needs them.
Frequently asked questions
The customer wrote yes in the chat. Why was the order not tagged?
Most likely the yes was a new message rather than a reply to the COD message. WhatsApp only tells the app which message is being answered when the customer taps a button or uses Reply on it, and without that reference the app cannot tell which order the yes belongs to, so it leaves the order alone.
Does Beacon Messenger understand replies in Spanish, Portuguese or Hindi?
Yes, for a short list of first words in each: si, sí, confirmar and confirmo; sim; oui; ja; haan and ha for confirmations, and cancelar, cancelo, não, nao, non, nein, nahi and nahin for cancellations, plus thumbs-up, tick, thumbs-down and cross emoji. Anything else is recorded as other and left for you to read.
What does Reply: other mean on the Messages page?
The customer answered the COD message, the reply was tied to the right order, but the first word was not one the app recognises. The text is shown next to the badge so you can read it and tag or cancel the order yourself. No acknowledgement was sent for it.
Can a customer change their answer?
Yes. Each recognised reply removes the opposite tag before adding its own, so an order that was confirmed and then cancelled ends up with only beacon-cod-cancelled. The message log keeps the most recent classification on the original message row.
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
- 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