A customer replied STOP to a WhatsApp order message. Now what?

What Beacon Messenger does when a shopper answers STOP to a Shopify order or shipping message, what it leaves to you, and how to honour it in Shopify.

It is a short message and it arrives without warning: STOP, or Stop sending me messages, or unsubscribe, sitting in the thread under the shipping update you sent an hour ago. Sometimes it is polite and sometimes it is not. Either way it is a request you have to act on, and it is worth knowing in advance what Beacon Messenger does with it, which is less than you might assume, and what the right response looks like on the Shopify side.

What the app does with an inbound STOP

Beacon Messenger reads every inbound message on your WhatsApp number, because that is how it hears replies to cash-on-delivery confirmations. It acts on exactly one kind: a reply, in the WhatsApp sense of swiping to quote a message, to a COD confirmation the app itself sent. For that reply it looks at the first word, decides between confirmed, cancelled and other, writes the result on the log row, and tags the order when the answer is one of the first two. The reply matching post walks through those checks.

STOP is not in the confirm list or the cancel list, so a STOP quoted against a COD message is classified as other. The log row records other:STOP, no tag is applied, and no acknowledgement is sent. A STOP that quotes a shipping update, or an order confirmation, or nothing at all, does not pass the first check and the app does not touch it. In every one of these cases the message stays in the inbox of whatever tool you use to read that number, and nothing in the app changes for that customer.

That is deliberate rather than lazy. An app that unsubscribed a customer on the strength of a single word would also unsubscribe the person who wrote Stop, I meant to order two of these, and the one who replied STOP to the wrong thread. Consent is a customer record, it lives in Shopify, and the decision to change it belongs with a person who has read the message.

Where consent actually lives

Beacon Messenger does not keep its own list of who has opted in or out. When it is about to send, it reads the customer's SMS marketing status from the order or checkout Shopify handed it, and treats subscribed as consent and anything else as no consent. Each automation has a Require consent switch. It is on by default for abandoned checkout reminders, which are marketing, and off by default for order confirmation, COD confirmation and shipping updates, which are transactional. The consent post explains how that status gets set at checkout in the first place.

So the lever for honouring a STOP is the customer's marketing status in Shopify, and the question of what STOP covers is answered by which automations have Require consent on. With the defaults, unsubscribing the customer stops abandoned checkout reminders and nothing else; the next order they place will still produce a confirmation and a shipping update.

Deciding what the customer meant

Read the thread before you change anything. A STOP under a cart reminder almost always means stop marketing me, and the defaults already draw that line. A STOP under the third shipping update of a split order often means too many messages, and the fix is on your side rather than theirs: fewer parcels, or the shipping automation off for a store that splits most orders. A STOP under a perfectly ordinary order confirmation is the rare case where someone does not want to hear from you on WhatsApp at all, transactional or not.

  • Marketing only. Unsubscribe the customer in Shopify. Abandoned checkout reminders stop; order and shipping messages continue.
  • Everything on WhatsApp. Unsubscribe the customer in Shopify, and turn Require consent on for the transactional automations too. That setting is per automation and shop-wide, so it changes the rule for every customer without consent, not just this one; weigh that before flipping it.
  • Too many messages. Leave consent alone and look at the volume: the split shipments post explains why one order can produce several updates, and the Pro plan question of whether to send them at all is yours to make.

Unsubscribing the customer in Shopify

  1. Open the order the message relates to in Shopify, then open the customer from the order.
  2. In the customer's marketing card, edit the SMS marketing status and set it to unsubscribed. Shopify records the change with a date and the source, which is your audit trail if anyone asks later.
  3. Reply in the thread. The customer wrote to you, so WhatsApp allows a free-form reply for 24 hours without a template. One line confirming you have taken them off is enough, and it is the part they will remember.
  4. If the customer asked you to stop everything, decide on Require consent for the transactional automations as above, knowing it applies to every customer without consent.

The change takes effect at the next send. Beacon Messenger resolves consent when a message is about to go out, not when the order was created, so a reminder already queued for later today reads the new status and is logged as skipped with the reason no consent, rather than sent.

What WhatsApp expects of you

Meta's business messaging rules require that people can opt out of marketing messages and that businesses honour those requests. They do not prescribe the word STOP or the mechanism, but they do watch the outcome: a customer who keeps receiving messages after asking you to stop tends to block or report the number, and blocks and reports feed the quality rating on your phone number. A low rating reduces how many new conversations the number can open, which is a bigger problem than one lost reminder. Treating a STOP promptly is as much self-interest as courtesy.

Transactional messages sit outside the opt-out requirement in Meta's rules, which is why the app's defaults do not gate them on consent. A customer can still ask you to stop them, and you can still agree. The difference is that marketing consent is a legal line and transactional preference is a customer service one.

Keeping track

If the STOP was a reply to a COD message, the log row shows other:STOP, which is a useful breadcrumb when you look back at that order. If it was not, the app has no record of it and your inbox is the only trace, so note the request on the customer's profile in Shopify with a timeline comment. A month later, when a colleague wonders why this customer gets no cart reminders, the comment answers the question in one line.

Where a STOP lands, by what it was replying to
Customer replied toWhat Beacon Messenger doesWhat you do
COD confirmationLogs other:STOP, no tag, no acknowledgementConfirm or cancel the order by hand, then handle the opt-out
Order confirmation or shipping updateNothing; message stays in your inboxRead it, unsubscribe in Shopify if asked, reply once
Abandoned checkout reminderNothing; message stays in your inboxUnsubscribe in Shopify; reminders stop at the next send
No quoted messageNothingSame as above, judged from the thread

Frequently asked questions

Does Beacon Messenger unsubscribe a customer who replies STOP?

No. The app only acts on replies quoting a COD confirmation, and even then STOP is recorded as other and nothing changes. Consent is read from the customer's SMS marketing status in Shopify, so you unsubscribe the customer there and the app picks it up at the next send.

Will order and shipping messages stop once I unsubscribe the customer?

Not by default. Order confirmation, COD confirmation and shipping updates have Require consent off because they are transactional. Turn Require consent on for those automations if you want them gated too, keeping in mind the setting applies to every customer without consent.

Can I reply to the customer without a template?

Yes. When a customer messages you, WhatsApp opens a 24-hour window in which the business can send free-form text. A short reply confirming the opt-out inside that window needs no approved template.

What if a queued abandoned checkout reminder is already scheduled for this customer?

Consent is checked when the message is about to send, not when it was queued. Once the customer is unsubscribed in Shopify, that reminder is logged as skipped for no consent rather than sent.

More guides