Gift orders on WhatsApp: buyer's phone or the recipient's?
A gift order has two people and often two phone numbers. Which one receives the order confirmation and the shipping update, and how to avoid spoiling it.
Most of the year an order has one person in it. The buyer pays, the buyer receives the parcel, and the buyer's phone is the only phone on the order. From late November that stops being true. A daughter in Madrid orders slippers for her father in Sevilla, pays with her card, and types his address and, because the courier asks for one, his mobile number. Now the order has two people and two numbers, and an app that sends WhatsApp messages has to pick. This post explains which number Beacon Messenger picks for each message, where that goes wrong for gifts, and what you can do about it before the Christmas orders arrive.
Where the phone numbers on an order come from
A Shopify order can carry a phone number in four places, and the checkout fills them in different ways.
- **The order's contact phone.** Filled when the shopper types a phone number instead of an email in the Contact field at the top of checkout, on stores that allow it. Empty when they used an email.
- **The shipping address phone.** The Phone field under the delivery address. Whether it is shown, optional or required is a checkout setting. This is the field a gift buyer fills with the recipient's number, because it sits next to the recipient's street and postcode.
- **The billing address phone.** Present when the billing address differs from the shipping address and the shopper fills it in.
- **The customer's phone.** Stored on the customer profile from an earlier order or an account.
For an ordinary order the first two are the same number or one of them is blank, so it does not matter which is read first. For a gift it matters a lot. The post on orders without a phone number covers the checkout settings behind these fields.
Which number each message uses
Beacon Messenger does not guess who the gift is for. It reads the fields in a fixed order and takes the first one that holds a usable number. The order is different for the confirmation and for the shipping update, because the two messages are built from different Shopify events.
| Automation | First | Second | Third | Fourth |
|---|---|---|---|---|
| Order confirmation and cash on delivery | Order contact phone | Shipping address phone | Customer phone | Billing address phone |
| Shipping update | Shipping address phone on the fulfillment | Order contact phone | Shipping or billing address phone on the order | |
| Abandoned checkout | Checkout contact phone | Shipping address phone | Billing address phone | Customer phone |
The reasoning behind the order is simple. A confirmation is a receipt, so it prefers the number the shopper gave as their own contact. A shipping update is about a parcel, so it prefers the number attached to the delivery, the one the courier will also ring.
Four gift orders, four outcomes
| What the buyer typed at checkout | Order confirmation goes to | Shipping update goes to |
|---|---|---|
| Own phone as contact, recipient's phone on the address | Buyer | Recipient |
| Email as contact, recipient's phone on the address | Recipient | Recipient |
| Email as contact, own phone on the address | Buyer | Buyer |
| Email as contact, no phone on the address, phone on billing | Buyer | Buyer |
The first row is how most people would want it to work. The buyer gets the receipt and the recipient hears that something is on its way, which is useful if they need to be at home.
The second row is the one to worry about. The buyer checked out with an email, so the order has no contact phone. The next field in line is the shipping address phone, which holds the recipient's number. Dad gets a WhatsApp message on the 2nd of December confirming an order he did not place. The name in the greeting comes from the customer record first, so it probably says Hi Lucia, and if your template includes the item summary and the total, he now knows it is slippers and what they cost.
That is not a bug in the fallback order. For every non-gift order, falling back to the shipping phone is what gets the confirmation delivered at all. It is a consequence of a checkout form that has one phone field and two people.
What the recipient sees in a shipping update
The shipping update greets by the name on the shipping address, so the recipient is addressed correctly: Hi Antonio, order #1042 is on its way. What else it reveals depends on your template. The merge fields available to a shipping update include the item summary, the first item title and the order total as well as the tracking number and link.
If you sell things people give as presents, write the shipping template as if a recipient will read it. Order number, carrier, tracking link. Leave the item names and the total for the confirmation. A buyer who receives that message loses nothing, because they already know what they bought.
The tracking button is worth a thought too. A button that opens the Shopify order status page shows the items and the amounts to whoever taps it. A carrier tracking link in the body shows only the parcel's progress. The button guide explains which links can go where.
Making the confirmation safer for gifts
You cannot make the app tell a gift from a normal order, and Shopify's checkout does not ask. What you can do is reduce the cases where the confirmation lands on the recipient, and reduce the damage when it does.
- Keep the confirmation template short during gift season. Greeting, order number, a thank you, a link. Take the item summary and the total out. The example template in the app includes the total, which is fine for most of the year and less so in December. The buyer has them in the email confirmation and on the order status page.
- If your market allows phone as a contact method at checkout, leave it enabled. Buyers who check out with their own phone as contact always get the confirmation themselves, whatever they type on the address.
- Say it on the product page or in the cart for giftable products: the phone on the delivery address is used for delivery updates. One line of text sets the expectation.
- If you offer gift wrapping or a gift note as a product or a cart attribute, mention the same thing there. That is the moment the shopper is thinking about the recipient.
- Check the log after the first few gift orders. Each row shows the number the message went to. Compare it with the order and you will see which of the four cases your shoppers fall into.
Switching the shipping address phone field off altogether is the blunt option. It removes the recipient's number from the order, so every message goes to the buyer or is skipped. It also removes the number your courier uses, which for many carriers and countries is not acceptable. Most stores are better off with a neutral template.
Consent and the recipient
A recipient did not buy anything and did not give you their number; the buyer did. Order and shipping messages are transactional, and a delivery notice to the person receiving the parcel is the same thing the courier does by SMS. Even so, keep it to that. Do not put offers in the shipping template, and do not add recipients to marketing lists. The abandoned checkout automation requires marketing consent by default, and that consent belongs to the shopper who was at the checkout, not to the person whose number is on the address. Leave that setting on.
If a recipient replies asking who this is, that reply shows up wherever you answer WhatsApp chats. A short, friendly answer that a parcel is on its way to them, without naming the contents, keeps the surprise.
Digital gift cards are a different case
A Shopify gift card sent to a recipient by email has no shipping address and no fulfillment with a destination. The confirmation goes to the buyer's contact phone or customer phone if there is one, and there is no shipping update to send. Nothing reaches the recipient over WhatsApp.
A quick test before the rush
- Place a test order with an email as contact and a second phone number of your own on the shipping address.
- Watch which phone gets the confirmation. It will be the second one.
- Read the message as if you were the recipient. If it gives away the present, edit the template now.
- Fulfill the order with a tracking number and read the shipping update the same way.
Ten minutes with two phones tells you more than any table. Once the templates read well for both people, the fallback order stops being a risk and becomes what it is meant to be: the reason a message arrives at all.
Questions
Who receives the WhatsApp order confirmation on a gift order?
The number in the order's contact phone if the buyer checked out with a phone. If they used an email, the app falls back to the shipping address phone, which on a gift order is often the recipient's number, then the customer's phone, then the billing address phone.
Who receives the WhatsApp shipping update on a gift order?
The phone on the delivery address comes first for shipping updates, so if the buyer typed the recipient's number there, the recipient gets the tracking message. If that field is empty, the message goes to the order's contact phone.
Can Beacon Messenger detect gift orders and message only the buyer?
No. Shopify's checkout does not mark an order as a gift, and the app reads the phone fields in a fixed order. Write templates that are safe for either person to read, and keep item names and totals out of the shipping update.
Will the recipient see the price of the gift?
Only if your template includes the order total or a button to the order status page. A shipping update with the order number, carrier and a carrier tracking link shows no prices.
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
- 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?
- 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