Bilingual Delivery Notifications in Québec: Getting the Language Right at Every Step

A tracking link is only reassuring if the customer can read what it says. In Québec that raises a question most national retailers never face: which language should the update arrive in? Guess wrong and a message designed to reassure becomes one more thing to decode. Get it right and the customer barely notices, which is the point.

This is a practical guide to the decisions behind bilingual delivery notifications: how to learn the customer's language, what each message needs to say, where English and French differ in ways that are easy to miss, and what to test before it goes live.

Ask once, at the point of order

The most common mistake is to infer language from the customer: from a surname, a postal code, or the language of the browser. All three are weak signals. Plenty of French-speaking customers carry English surnames, plenty of English speakers live in francophone neighbourhoods, and a browser set to English is often just the way a work laptop was configured.

The reliable method is to ask. A language field at checkout, set next to the phone number or email address because that is where the notifications go, costs a customer one tap. Pre-select the browser language if you like, but show the choice and let it be changed. Then pass the answer along with the order so that whoever sends the tracking link uses it. If the field is blank, decide in advance what the default is; for most Québec businesses it is French.

The messages that need both languages

A delivery generates more messages than most retailers realize: an order confirmation, a shipped notice, a delivery-day notice with a window, a delivered confirmation with a photo, and, when needed, a missed-delivery message and return updates. Each one has a job, and each has a way to go wrong in translation.

Notice that these are not word-for-word translations. A literal rendering of "out for delivery" produces something that reads as nonsense in French. The French message is written the way a francophone would write it, and that is the standard to hold every template to.

Details that differ between the languages

Beyond vocabulary, English and French in Québec handle the small details of a notification differently, and they are the details most likely to be wrong when a template is simply translated.

• Time. French in Québec uses the 24-hour clock with a space around the h: "14 h 30". English uses "2:30 p.m.". A template that mixes them in the same message looks careless.
• Dates. "10/12" means the tenth of December to some readers and the twelfth of October to others. Write dates out, "Thursday, October 12" and "jeudi 12 octobre", or use the ISO form (2026-10-12), which is widely understood in Québec.
• Money and numbers. French puts the symbol after the amount with a space, "25 $", and uses a decimal comma, "12,50 $". English writes "$25" and "$12.50".
• One word for one thing. Choose a single French term for each concept and use it every time. For a pickup, both ramassage and cueillette are heard in Québec; either is fine, but the same message set should not use both.

What SMS does to French

There is a technical detail that surprises people who send French text messages. Many SMS systems use a compact character set that includes é, è, à and ù but not ê, â, î, ô, û or the French quotation marks « ». A single character outside that set can switch the whole message to a different encoding that fits far fewer characters in each text, which means one long message becomes two or three billed ones.

The practical consequence is to keep French notifications short, put the tracking link early, and check how your sending provider counts message segments before you finalize the wording. It is a good reason to avoid long, formal sentences.

What the law says, and what it does not

The Charter of the French language gives consumers in Québec the right to be informed and served in French (section 5), and recent amendments have tightened a number of requirements around labels, signage, advertising and contracts. Whether a specific automated delivery message falls under a specific obligation is a question for a lawyer or for the Office québécois de la langue française, and this article does not answer it.

As a practical matter, treat French as the default for Québec customers and English as the alternative they can choose, rather than the other way around. It is simple to explain, it avoids most problems, and it is how a customer who reads French expects to be addressed.

Test before it goes live

1. Send every template in both languages to real phones.Look at them on the screen where customers will see them: a lock screen preview cuts off long messages.
2. Check the accents.Confirm that accented characters display correctly in the email subject, the SMS and the tracking page, and that nothing turns into question marks.
3. Have a native speaker read each French message.Someone who reads French every day will spot an awkward phrase in seconds. A translation tool will not.
4. Run a language-switching test.Create one order in English and one in French and follow each through every status, including a missed attempt and a return.

Delivery language is part of the same discipline as preventing failed delivery attempts: both depend on collecting a little more information at checkout. If your courier offers bilingual customer notifications, ask whether the language can be set per order rather than per account, since customers in the same household do not always share a language. It is one of the questions worth asking any courier before you commit, and it matters even more if you also run returns, where more messages are sent.