WhatsApp usernames and BSUIDs: what changes for Shopify order messages
WhatsApp usernames mean a reply may arrive with no phone number. What that means for order notifications, COD replies and the Beacon Messenger log.
WhatsApp is adding usernames. Through 2026 users can pick a unique handle and, if they want, hide their phone number from businesses they talk to. For a business sending through the Cloud API the visible change is in the webhook: a message from a user who adopted a username may arrive with the phone number missing and a new identifier in its place, a business-scoped user ID or BSUID. If you run a Shopify store and send order messages over WhatsApp, the question is what that does to the messages you send, the replies you receive and the records you keep. For Beacon Messenger the answer is: less than it sounds, with one case worth knowing about.
What a username and a BSUID are
A username is an optional display handle. The account still has a phone number behind it; the username is a layer on top that lets a person be found and shown without the number. Businesses can adopt one too, for branding, but a business's phone number stays visible to users regardless.
A BSUID is the identifier Meta gives a business for a user when the phone number is not to be shared. It looks like a country code, a dot and a long string: US.13491208655302741918. It is scoped to one business portfolio, so the same person has a different BSUID with every business they talk to, and it cannot be used with another portfolio's numbers. It survives a username change and is regenerated if the person changes their phone number. Microsoft's overview for its WhatsApp channel and Vonage's explainer both carry the same warning from Meta's documentation: the from field of an inbound message may now be empty, so do not assume it holds a phone number.
Outbound order messages: nothing changes
Every message Beacon Messenger sends starts from the phone number on the Shopify order. The shopper typed it at checkout, Shopify stored it on the order, and the app sends the template to that number. A username does not enter into it: the app is not looking anyone up by handle, and a customer who has hidden their number from businesses in general has still given it to you on the order. Order confirmations, shipping updates, COD checks and abandoned checkout reminders all go to the number on the record, exactly as before. The no phone number post remains the relevant one when a message is skipped: the cause is a missing or malformed number on the order, not a username.
What the customer sees at their end does not change either. Your messages arrive from your business number with your display name, as the display name post describes. Whether the customer has a username is between them and WhatsApp.
Inbound COD replies: matched by the message, not the number
The one place Beacon Messenger reads inbound messages is the cash on delivery confirmation. The app sends a COD check with buttons or a question, the customer replies, and the app tags the order confirmed or cancelled. It matters how that reply is matched to the order. The app does not look at who sent it; it looks at what the reply is a reply to. WhatsApp attaches the ID of the quoted message to a reply, the app finds its own sent message with that ID in the log, checks that it was a COD check from your shop, and reads the order from there. The reply matching post walks through the whole sequence.
Because of that, a reply with no phone number in it is matched exactly as well as one with. The classification runs, the reply is stored on the log row, and the order is tagged. A customer who adopted a username yesterday and taps Confirm on your COD check today is confirmed like anyone else.
The one gap: the thank-you message
After tagging the order the app sends a short acknowledgement, a free-form text such as thanks, your order is confirmed, in the language of the template. It sends that to the sender's number as reported in the reply. If WhatsApp has withheld the number, there is no number to send to, the send fails, and the failure is written to the server log. The order is already tagged by then, so the automation has done its job; what the customer misses is the one-line confirmation of their confirmation.
How often this happens depends on how many of your customers adopt usernames and choose to hide their number from businesses, which for a store they have just given their number to is likely to be a small share. Meta's own rules also make the number available in some situations even when a username exists, so an empty from field is the exception rather than the new normal. We are tracking it, and the app's handling of the acknowledgement is the piece that will change if it becomes common. Everything on the tagging side already works without a number.
What this means for the message log
The log records the recipient of every outbound message, which is the order's phone number, and stores the classified reply on the same row. Nothing in the log is keyed on the inbound sender, so a reply with no number leaves the same trail as before: the row shows sent, delivered, read, and the reply text with its classification. If you search the log for a customer, search by order or by the number on the order, as the log search post suggests; that has always been the reliable key.
What to tell your team
- Order messages still go to the number on the Shopify order. Keep collecting it at checkout; the phone field settings in the no phone number post are still the ones to review.
- COD replies are tagged by what they reply to, so a hidden number does not stop the order being confirmed or cancelled.
- If a customer says they confirmed but got no thank-you, check the order tags before anything else. A tagged order means the reply was received and processed.
- A customer cannot be messaged by username. If someone writes in with a handle and no number, ask for the number; templates need it.
Frequently asked questions
Can Beacon Messenger send a Shopify order notification to a WhatsApp username?
No, and neither can any other app yet. Messages are sent to a phone number, which comes from the Shopify order. A username is a display handle on top of a number, not an address you can send to. The customer has already given you their number at checkout, so this does not affect order messages.
Will cash on delivery replies still be tagged if the customer has a username?
Yes. The app matches a reply by the ID of the message it quotes, not by the sender's phone number. It finds its own COD check in the log, reads the order from it, classifies the reply and tags the order. A missing phone number in the reply does not change any of that.
What is a BSUID?
A business-scoped user ID, the identifier Meta gives your business for a user whose phone number is not shared with you. It has the form of a country code, a dot and a long string, is unique to your business portfolio, stays the same if the user changes their username and is regenerated if they change their phone number.
Does WhatsApp hide every customer's phone number now?
No. Usernames are optional and most users have not adopted one. Even when a user has, Meta's rules make the number available to businesses in some situations. The change is that a webhook may arrive without a number, so software must not assume one is always present.
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
- 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