Multi-language restock alerts fail in a specific and avoidable way: the widget is translated, the email is translated, and the link in the email drops the customer on the English storefront with prices in the wrong currency. The translation work is the easy half. Carrying the customer's locale from the moment they subscribe to the moment they land back on the product is the half that decides whether any of it converts.
The four surfaces, not two
People plan for two — the form and the email. There are four, and the ones that get missed are the ones customers see when something has gone wrong.
- The subscription widget — the button, the field labels, the consent text, and the error states. "Please enter a valid email address" in English on an otherwise German page is where trust starts leaking.
- The confirmation — the on-page message and, if you send one, the confirmation email.
- The alert itself — subject line, body, button, footer, and the unsubscribe link, which is a legal text in most markets and needs to be readable.
- The destination — the URL in that button. This is the one that breaks.
Capture the locale at subscribe time, not send time
The instinct is to work out the language when you send, from the customer's IP address or their email domain. Both are wrong often enough to matter: a German customer on holiday gets a Spanish email, and a .com address tells you nothing at all.
The customer already told you. They were browsing a specific localised storefront when they clicked notify-me. Store that locale with the subscription and use it for every message afterwards. It is one extra field and it removes the entire class of problem.
The same applies to the market. If you run Shopify Markets with different catalogues or prices per region, the market the customer subscribed from determines which price they should see when they come back, and that has to travel with the subscription too.
The link is the part that breaks
On a Shopify store with translated storefronts, the locale lives in the URL — /fr/products/..., /de/products/.... An alert that links to /products/... sends a French subscriber to the default locale, where the language flips back to English and the currency may flip with it.
The customer does not conclude that your email system has a configuration gap. They conclude the product is priced differently than they remembered, and a good proportion of them close the tab.
Build the link from the stored locale, test it by subscribing on each storefront you run, and click the link in the email that actually arrives rather than in a preview. Previews render the template; they do not always render the link the send would produce.
Right-to-left is a layout problem, not a translation problem
Arabic and Hebrew need dir="rtl" on the email body and the widget, and the layout has to mirror with it — button alignment, list markers, the direction of any progress or step indicator. Punctuation at the end of a mixed-direction line lands in a surprising place if the direction is not set explicitly.
Product names and prices are frequently left-to-right inside a right-to-left sentence, which is normal and handled correctly by the browser only if the surrounding direction is declared. It is worth rendering one real alert in an Arabic mailbox before launching the market, because this is not something a template preview will show you.
SMS has a constraint email does not
This one is concrete and catches people out. SMS uses GSM-7 encoding for the basic Latin character set, which fits 160 characters in a single message. The moment a message contains a character outside that set — an accented letter, Cyrillic, Greek, Arabic, Chinese, or a plain emoji — the whole message switches to UCS-2 and the limit drops to 70 characters.
A restock template that comfortably fits one segment in English will silently become three segments in Greek or Japanese. You pay per segment, so the same alert costs three times as much in those markets, and long messages arrive split on some handsets.
Two practical consequences: write the non-Latin templates shorter rather than translating the English one and hoping, and check your provider's per-segment pricing per destination country before assuming SMS is affordable for a given market. A single emoji in a shared footer can triple the cost of every message you send in half your markets.
What to do about the product name
Translating the template and leaving the product name in English is the most common half-finished version of this, and it is usually a data problem rather than an email problem. If your product titles are translated in Shopify's own translation system, the alert should pull the translated title for the subscriber's locale rather than the default one.
Where it gets awkward is variants. Size and colour names are variant option values, and a store that has translated its product titles has often not translated "Medium" or "Navy". A German alert that says "Medium / Navy ist wieder verfügbar" is not wrong enough to confuse anyone, but it is the detail that makes an otherwise careful translation feel automated. Translate the option values for the markets you actually sell into, or leave the variant out of the subject line and show it in the body where it reads as a spec rather than as prose.
Which languages, in what order
Do not translate by speaker population. Translate by where your orders and your waitlist signups already come from. Your Shopify analytics has sessions and orders by country, and your waitlist has subscriber counts by storefront — those two lists, overlapped, are the priority order, and they will not match anybody's global ranking.
A store with a strong Netherlands business should translate Dutch before Spanish, whatever the relative speaker counts. Start with the two markets that already buy, get the whole chain right for those, then add the third.
Fallbacks, and saying so
You will have subscribers on locales you have not translated yet. Fall back to one clearly written default rather than to machine translation, which reads as carelessness in a way that a plain English message does not. If the storefront is localised but the alert is not, a single line — "this notification is in English" — is more respectful than a template that half-translates.
A checklist before you open a market
- Subscribe on the localised storefront and read the confirmation in that language.
- Restock the product and read the actual alert that arrives, not a preview.
- Click the link and confirm the language, the currency, and the variant all survive.
- Check the unsubscribe text is translated and that the link works.
- For SMS, count the segments your template produces in that language.
- For RTL markets, open the alert on a phone, not only on a desktop client.
Six steps, one product, about twenty minutes per market. It is the difference between a translated alert and one that actually returns the customer to a page they can buy from.
Where to go next
Stok stores the locale with the subscription and sends the alert in the language the customer subscribed in, with the link pointing at the matching storefront. For the channel decision underneath this — and the cost arithmetic that changes in non-Latin markets — see SMS or email for restock alerts, and the complete back-in-stock guide for setup generally.
