Klaviyo in several languages and markets.

By Alexander Andersson · Updated 1 Nov 2026 · Klaviyo's docs checked 1 Nov 2026

What does Smart Translations translate, and what does it leave to you?

Smart Translations machine-translates the words in an email and leaves market data to you. Klaviyo's docs say it can translate email content into 60+ languages. It is for paid accounts only, and you switch it on under Settings, then Translations [1].

Text blocks, labels and alt text are translated automatically, including universal and saved content placed in the template. Images and links are not translated: you swap them by hand for each language. Product feed content cannot be translated [1]. Klaviyo states that the output comes from machine translation and AI, may contain errors, and should be reviewed before sending. A Do Not Translate list keeps brand names and set phrases in the source language, and a glossary holds approved terms [1].

The feature covers campaigns and flows. In a campaign you translate on the Message step. In a flow you translate each email on its own [2][3]. If you edit the source after translating, Klaviyo marks the out-of-sync elements, and you re-translate, match the source, edit or ignore each one [2]. Translations can also leave Klaviyo as a CSV per message and come back the same way, for an agency or a translation tool. An empty cell in the import overwrites the existing translation [4].

How does Klaviyo decide each profile's language?

Klaviyo reads one profile property, which you pick in the translation settings. The default is Locale. You can choose a Language property instead, collected through a sign-up form, a CSV import, a link that updates the profile, or the Profiles API. Klaviyo recommends BCP-47 codes such as en-GB, and also accepts plain values such as English [1].

Klaviyo does not detect language from browsing behaviour. Some integrations, such as Shopify, sync a Locale property. Klaviyo's advice is to ask for the preference in a form, because estimates based on location can be wrong [5].

Profiles with no language value get a default. The settings article says they receive the email's original language [1]. In the campaign and flow editors you choose that default yourself: the original language or one of the translations [2][3]. An unsupported country variant falls back to the base language, so a profile set to fr-DE is treated as French [1]. Check how many profiles in each market have no value before you rely on translation: they all get the default.

How do you show prices and currencies per market in Klaviyo?

For a Shopify store, the Shopify Markets sync is the main tool. It brings localized titles, prices, compare-at prices, status, currency and URLs into Klaviyo for each active region market [6]. A static product block with "Localize for recipient" switched on shows each recipient the price and currency for their language and region at send time. When that data is missing, Klaviyo falls back to the block's own setting, then the account locale, then en-US, then base product data [6]. Dynamic product blocks match language and country to a catalog locale. B2B and Retail Markets are not synced [6].

Outside Shopify Markets, currency is an account setting. The symbol is set at account level, and Klaviyo does not convert values, so changing the symbol does not change the numbers [7]. Klaviyo recommends a separate account for each regional store or domain, each with its own currency [7].

Older community answers point the same way. In 2021 a Klaviyo staff member called one account per currency the cleaner setup, said product blocks could not show several currencies, and suggested a conditional split by country with a template per region [8]. Those answers predate the Shopify Markets sync, so test them against your own platform before you build on them.

Smart Translations or a separate edition per market?

Smart Translations is enough when markets differ only in language. When markets differ in price, currency, legal line, offer or send time, each market needs its own edition: a separate campaign in one account, or a campaign in each market's account. Klaviyo itself lists a cloned campaign per language segment, and conditional splits in flows, as the alternative to Smart Translations [5].

Holm Coffee is a fictional demo brand. Its fixture has three markets on Klaviyo, with three languages and three currencies.

The trade is plain. One translated email is one build and one source to correct. Three editions are three builds to check, but each one carries its own market's facts. A workable rule: translate when only the language differs, and build an edition when anything a lawyer or a finance team would check differs. The price-reduction rules above are fixture data, not legal advice.

How do universal content blocks fit with approved blocks?

Universal content is Klaviyo's way to reuse one approved block across templates: edit it once and the change reaches every linked copy [9]. When you edit inside a template you choose Edit across all instances, or Unlink and edit independently, which cuts that copy loose from the library [9]. Publishing the change updates every linked instance, including scheduled campaigns and live flows [9].

That is useful for a shared footer and risky for a market line. One edit to a shared block reaches every market that uses it, whether or not each market has reviewed it. Marking a flow email transactional unlinks its universal blocks, so later library edits no longer reach that email [9].

For several markets, keep one universal block per market where the content differs by law, such as the legal line, and one shared block where it does not. Smart Translations translates universal content placed in a template [1], so a translated Danish footer reads in German but still says what the Danish footer says.

Also on.

Klaviyo · Braze · Salesforce Marketing Cloud Next · Voyado · Customer.io · Iterable