WhatsApp order messages when customers speak several languages

A Beacon Messenger automation sends one template in one language. What that means for a store with customers in two or three languages, and the four ways to handle it.

A store in Montreal ships to customers who write in French and customers who write in English. A store in Barcelona has Catalan, Spanish and a growing number of English-speaking tourists. A store in Dubai has Arabic and English in roughly equal measure. All three ask the same question when they set up order notifications on WhatsApp: can the message go out in each customer's language?

The short answer for Beacon Messenger is that each automation sends one template in one language, and the app does not pick a language per customer. That is a deliberate limit, and this post explains where it comes from, what it means in practice, and the four ways merchants work with it, from a bilingual template body to one store per language.

How a template gets its language

On WhatsApp, a message template is not one object. It is a name plus a language, and Meta approves each name and language pair separately. order_confirmation in en and order_confirmation in fr are two approvals, two bodies, and potentially two different statuses, which is the subject of our post on template language mismatches. When Beacon Messenger loads your templates from Meta, it keeps every approved pair, and the picker on an automation shows them as separate entries.

When you save an automation, the app stores the template name and the template language together. At send time it looks for exactly that pair in the approved list and sends it. There is no second lookup, no fallback to another language, and no reading of anything about the customer to choose between pairs. Every order confirmation from that automation goes out in the language you picked.

Why the app does not read the customer's language

Shopify does record a locale on an order: the language of the checkout the customer used. It would be possible to read it and choose a template pair to match. We have not done that, for three reasons that are worth stating because they are the same reasons you should think about before wanting it.

  • The locale says which checkout language the shopper saw, not which language they want a message in. On a store that only publishes one language, every order has that locale, including orders from customers who would much rather read a different one. On a bilingual store, a shopper who never touched the language selector gets whatever the store defaulted to for their market.
  • Half-covered template sets fail silently. If the French pair is approved and the English one is pending, a per-customer rule would send French to some customers and nothing to the rest, and you would find out from a customer rather than from the app. One pair per automation means it either works for everyone or fails visibly for everyone.
  • Merge fields are values, not sentences. Customer names, order numbers and totals read the same in any language; the surrounding text is what carries the language, and that text lives in the template body, which Meta has approved in one language. There is no way to mix two languages inside one approved body except by writing both in.

None of these are permanent objections, and we may add a per-market or per-locale option later. Today the behaviour is one language per automation, and the rest of this post is about getting a good result inside that.

Option one: a bilingual template body

The most common solution, and the one most of our bilingual merchants use. Write the body in both languages, one after the other, and submit it as a single template. Meta approves templates in one declared language, but it does not reject a body because a second language appears in it, as long as the content is still clearly a transactional message. A Canadian order confirmation might read: Merci pour votre commande {{1}}. Nous vous écrirons quand elle sera expédiée. Thank you for your order {{1}}. We will message you when it ships.

Keep it short. WhatsApp messages are read on a phone, and a body that doubles in length doubles the scrolling. Put the language most of your customers use first. Give each half its own placeholders and map both to the same field in the automation; the order number appears twice in the body, but it is one order number, and the mapping screen lets two placeholders point at the same merge field. Buttons are the exception: a button label is one string, so pick the shorter language or a word both groups understand, such as Track or Suivi.

For the examples in our template examples post, doubling each body is a ten minute job per trigger. The cash on delivery confirmation is the one to spend the most time on, because the customer replies to it, and the reply has to be understood.

What happens to replies in another language

The cash on delivery automation asks the customer to confirm the order by replying. Beacon Messenger classifies the first word of the reply, and the classifier is multilingual on purpose: confirm, confirmar, confirmo, yes, si, sí, ok, sim, oui, ja and the Hindi haan all count as a confirmation, and cancel, cancelar, no, não, non, nein and nahi all count as a cancellation, along with the thumbs up, thumbs down, tick and cross emoji. A bilingual template that says Reply YES to confirm / Répondez OUI pour confirmer therefore works for both groups without any configuration.

The acknowledgement the app sends back after a confirmation uses the language of the template you picked, so on a bilingual setup it comes back in that one language. The post on how COD replies are matched has the full list of what counts and what is only recorded.

Option two: pick the majority language and keep it plain

Some stores decide that one language is enough. If ninety percent of your orders are in Spanish, a Spanish confirmation with the order number and a tracking button is understood by nearly everyone who receives it, because order numbers, dates, amounts and a button labelled with a recognisable word carry most of the meaning. Write the body so that a customer who does not read the language can still see what it is about: the order number near the start, the total with its currency symbol, and a URL button rather than a sentence asking them to visit a page.

This is the option to pick when the second language is small and growing, with the bilingual body as the upgrade once the second group is large enough to matter.

Option three: one store per language

Merchants who run separate Shopify stores per market, rather than one store with Shopify Markets, already have the problem solved. Each store installs Beacon Messenger on its own, connects its own WhatsApp number or the same number, and sets its automations to that store's language. The French store sends French, the English store sends English, and nobody wrote a bilingual body. The cost is everything else that comes with running two stores, which is rarely worth paying for notifications alone, but if the stores exist anyway, use them.

Option four: language-neutral messages

A narrower trick that suits shipping updates in particular. A message that is mostly data needs very little language: the order number, the carrier name, the tracking number and a Track button. Write the one sentence of text in the shortest form you can and let the fields do the work. It is not elegant, and it does not suit an abandoned checkout message, which has to persuade, but for a shipping update it is often what customers prefer anyway.

Choosing in practice

Which approach fits which store
SituationApproach
Two languages, roughly even split, one storeBilingual body in every template
One dominant language, a small second groupMajority language, data-first wording
Separate stores per market alreadyOne language per store, nothing special
Shipping updates onlyLanguage-neutral body with fields and a button
Three or more languages, one storeBilingual body in the two largest, data-first wording for the rest

Whatever you pick, check it on a real phone in each language before turning the automation on. The test message checklist walks through sending one to yourself. Read it as a customer who only speaks the second language would, and if the first thing they understand is the order number, the message is doing its job.

A note on right-to-left languages

Arabic, Hebrew and Urdu bodies work in templates and in Beacon Messenger's preview. In a bilingual body that mixes a right-to-left and a left-to-right language, put each language in its own paragraph with a blank line between them, and keep numbers and placeholders inside the paragraph of the language they belong to, so neither half ends up with a stray number at the wrong end of a line. Shopify's admin itself gained Arabic, Hebrew and Urdu earlier this month, which is a reminder that the stores asking for this are not edge cases.

If you need a language picked per customer, tell us at support which signal you would want it to use, the checkout locale, the shipping country or a customer tag. The answer shapes what we build. Until then, the bilingual body is the solution we recommend, and Beacon Messenger sends it exactly as Meta approved it.

Questions about languages and templates

Can Beacon Messenger send a French template to French customers and an English one to the rest?

Not today. Each automation stores one template name and one language and sends that pair to every recipient. The usual solution is one template whose body contains both languages, which Meta accepts as long as the message stays transactional.

Does Meta reject a template that contains two languages?

Not for that reason alone. A template is submitted under one declared language, and the body can contain text in another. Rejections come from content that reads as promotional under a utility category or from formatting problems, not from the second language itself. Review the body as carefully as you would a single-language one.

Will customers who reply oui or sí to a cash on delivery message be understood?

Yes. The reply classifier recognises confirmation and cancellation words in English, Spanish, Portuguese, French, German and Hindi, plus the common emoji. The acknowledgement the app sends back uses the language of the template you selected for the automation.

I have the same template approved in two languages. Which one is sent?

The one whose name and language you picked when you saved the automation. The other approved pair is ignored for that automation. If you later change the automation to the other pair, every message from then on uses it.

More guides