Blank names, twelve-item orders: what WhatsApp merge fields fall back to
What each Beacon Messenger merge field contains when the Shopify order is awkward: no customer name, many line items, foreign currency, odd payment gateways.
A template reads beautifully with the sample order you tested it on: 'Hi Maria, thanks for order #1042 at Casa Verde! Total: $86.00.' Then real orders arrive. One has no name because the shopper checked out as a guest with only an email. One has fourteen line items. One was paid in euros on a store whose currency is dollars. One was paid through a gateway Shopify calls shopify_payments. Each of those changes what lands in the shopper's chat, and none of them is visible in the editor, where the preview is built from a tidy example. This post goes through every merge field Beacon Messenger offers and says exactly what it contains when the order is not tidy. The list of fields per trigger is in setting up order notifications over the Cloud API; this is about the edges.
Names: where the first name comes from
The customer_first_name field is filled in a fixed order. The app takes the first name on the customer record attached to the order; if that is empty, the first name on the shipping address; if that is empty, the first name on the billing address. If all three are blank, it takes the first word of whatever full name it managed to assemble, and if there is nothing at all, the field is empty. customer_name is built the same way from first and last name, falling back to the single name line an address can carry, and finally to the first name on its own.
In practice this covers almost every order, because a shipping address requires a name at checkout and Shopify copies names onto the customer record it creates for guests. The cases that end up blank are the ones with no address at all: digital goods, gift cards sent by email, and pickup orders where the shopper typed only an email and phone. For shipping updates the lookup is slightly different, since the event comes from the fulfilment rather than the order: the name on the customer record first, then the name on the fulfilment's destination address.
Abandoned checkouts are the weak spot. A shopper is counted as having a checkout the moment they enter an email or phone, which is before the address step, so a reminder for a checkout abandoned early often has no name to use. The customer_first_name field for that trigger reads from the checkout's customer, shipping and billing records in the same order, and if the shopper never reached the address form, it is blank. Write abandoned checkout templates on the assumption that the greeting may have no name in it.
What an empty field does to the message
Beacon Messenger does not invent a value. If a merge field is empty, the parameter is sent to Meta as empty text; there is no 'there' or 'Customer' substituted on your behalf, because a wrong guess at a name is worse than none and the right fallback is yours to choose. Meta's template API, however, expects each parameter to carry text, and a blank parameter is one of the common reasons a send is refused at the API rather than delivered. When that happens the delivery log shows the row as failed with Meta's error, and the stored order context lets you retry it once you have fixed the template or the mapping.
The robust approach is to map only fields that cannot be blank for that trigger into positions the sentence depends on, and to keep names out of the first words. 'Thanks for your order {{1}} at {{2}}' works for every order because order name and shop name are always present. If you want the personal touch, put the name where its absence reads naturally, or use a separate template for shoppers with names and let the no-name orders fall through to the plain one; the latter means two approved templates, and only one automation per trigger, so most stores pick the plain wording and move on. Which fields are always present is in the table below.
Items: the first three and a count
Three fields describe what was bought. items_summary lists the first three line items in the order they appear on the order, each as a quantity and a product title, separated by commas: '2× Linen shirt, 1× Belt, 1× Socks'. If there are more than three lines, it appends '+N more', where N is the number of further lines, not units. An order with fourteen lines reads '2× Linen shirt, 1× Belt, 1× Socks +11 more'. item_count is the total number of units across all lines, so that same order might show 19. first_item_title is the product title of the first line alone, useful for templates that want 'your Linen shirt is on its way' without a list.
Two details matter for how this reads. The title is the product's title, not the variant's: the shopper sees 'Linen shirt', not 'Linen shirt - Medium / White', which keeps the summary short at the cost of the size. And 'first' means first on the order, which is the order items were added to the cart, not the most expensive or the one with the most units. If your template leans on first_item_title, know that a shopper who added socks first will be told about their socks.
For shipping updates the items come from the fulfilment, not the whole order, so a split shipment lists only what is in that box; split shipments and late tracking covers that in full. For abandoned checkouts they come from the checkout's line items at the time of the last update, which is the cart as the shopper left it.
Totals and currency
order_total is the order's total formatted as a currency amount: the symbol, thousands separators and two decimals, using the order's currency code. On a store trading in US dollars that is '$86.00'; in euros, '€86.00'; in pounds, '£86.00'. For currencies whose symbol is ambiguous the formatter disambiguates the way an English-language reader would see it, so Canadian dollars come out as 'CA$86.00' and Mexican pesos as 'MX$86.00', and the formatting conventions are English ones: a comma for thousands, a point for decimals, regardless of where the shopper is. A German shopper sees '€1,250.00' rather than '1.250,00 €'. If that matters to your customers, mention the currency in the template text rather than relying on the formatter's symbol.
The amount itself is the total in your store's currency, as carried by the order event Shopify sends. A shopper who paid in euros on a dollar store through Shopify Markets sees the dollar figure in the message, not the euro figure they saw at checkout. That is a limitation of the order payload the app works from, and it is worth knowing before you promise 'Total: {{3}}' to an international audience; 'we have received your order {{1}}' avoids the question entirely. checkout_total, used by abandoned checkout reminders, is formatted the same way from the checkout's own total.
Payment method and the other fields
payment_method is the list of payment gateway names Shopify recorded on the order, joined with commas. These are Shopify's internal names and they are not always pretty: 'shopify_payments', 'paypal', 'manual', or whatever label a cash-on-delivery gateway was given, such as 'Cash on Delivery (COD)'. An order that has not been paid yet, including some draft orders awaiting payment, can have no gateway at all, and then the field is blank. It is a useful field for the cash-on-delivery confirmation, where the shopper already knows how they are paying, and a poor one for a general order confirmation sentence.
| Field | Content | Can it be blank? |
|---|---|---|
| customer_first_name | Customer record, then shipping, then billing first name, then first word of the full name | Yes: no address and no named customer |
| customer_name | First and last name, then an address's full name line, then the first name | Yes, same cases |
| shop_name | Your store's name, or its myshopify domain if the name is unavailable | No |
| order_name / order_number | '#1042' with your prefix and suffix, or '1042' alone | No for order triggers |
| order_total | Formatted total in the store currency, English conventions | No for order triggers |
| payment_method | Gateway names joined by commas, e.g. shopify_payments | Yes: unpaid orders |
| items_summary | First three lines as 'qty× title', then '+N more' | Only on an order with no lines |
| item_count | Total units across all lines | No |
| first_item_title | Product title of the first line | Only on an order with no lines |
| order_status_url(_path) | Shopify's order status page, full or without the domain for buttons | No for order triggers |
| tracking_number / company / url | From the fulfilment; the first number and URL if there are several | Yes, until tracking is added |
| checkout_total / checkout_url(_path) | From the abandoned checkout | No |
shop_name deserves one line of its own. It is the store name as Shopify reports it, which is the name under Settings > General, not your domain and not your legal entity. The app records that name when it is installed and does not currently refresh it after a rename, so if you have renamed your store since installing, write the new name into the template text instead of mapping shop_name, or ask support to refresh it. order_name includes whatever prefix and suffix you set for order numbers, so a store with the prefix 'CV-' gets 'CV-1042' and should not put a '#' in the template in front of it.
Testing with an awkward order on purpose
- Create a draft order in Shopify for a customer record with no first or last name, add four different products with quantities of two or more, and mark it as paid with a manual payment method. Complete it.
- Read the order confirmation that arrives on your test number. Check the greeting, the items line and the '+N more' suffix against the order.
- Create a second draft order for a customer with a name but no shipping address, a single digital product, and complete it. Check that the name appears and the items line has no '+N more'.
- If you sell in more than one currency, place a real test order from a market with a different presentment currency and compare the total in the message with the total at checkout.
- Open the delivery log for each message and compare the row with what arrived on your phone; a failed row shows Meta's error, which is where a blank parameter would surface.
Three orders cover the cases that cause most of the questions, and the delivery log keeps each attempt so you can come back to it later. The templates themselves have to pass Meta's review, and a body full of blanks or technical gateway names can fail that review as well as read badly; why templates get rejected lists the reasons. Beacon Messenger sends what the order contains and shows you what it sent; the wording that survives contact with real orders is still yours to write.
Frequently asked questions
What does the WhatsApp message show when a Shopify order has no customer name?
The customer_first_name and customer_name fields are empty. Beacon Messenger looks at the customer record, the shipping address and the billing address in that order and does not substitute a placeholder word. An empty parameter can cause Meta to refuse the send, so put names where their absence reads naturally or leave them out of templates for triggers where names are often missing, such as abandoned checkouts.
How many items does the items_summary merge field list?
The first three line items, each as quantity and product title, followed by '+N more' where N is the number of additional lines. item_count gives the total units across all lines, and first_item_title gives the product title of the first line only. Titles are product titles without the variant.
Which currency does order_total use?
The store's currency, as carried by the order event Shopify sends, formatted with English conventions and the currency's symbol. A shopper who paid in a different presentment currency through Shopify Markets sees the store-currency amount, so international stores may prefer templates that do not quote a total.
Why does payment_method say shopify_payments?
Because that is the gateway name Shopify records on the order, and the field passes it through unchanged. It is most useful on cash-on-delivery confirmations, where the gateway label is one the shopper recognises. For a general confirmation, leave it out or phrase the sentence so a technical name does not jar.
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
- 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