Guides

How to Translate Shopify Store Automation Workflows and Flow Triggers for International Markets

Most Shopify merchants who go international translate their product pages and forget their automations entirely — then wonder why French customers are getting back-in-stock emails in English, or why a loyalty reward flow fires identical copy to buyers in Germany and Japan. Getting shopify flow multilingual automation right is less about Liquid magic and more about understanding where Flow's real limits are, and routing around them cleanly.

What Shopify Flow Can (and Cannot) Do for Multilingual Stores

Shopify Flow is a no-code automation builder. It triggers on events (order created, customer tag added, inventory level dropped), evaluates conditions, and runs actions (add tag, send email, make a webhook call). Understanding what it cannot do is the most important starting point for international stores.

Flow's built-in "Send email" action is not a general-purpose email renderer. It does not evaluate arbitrary Liquid expressions at send time the way a Liquid template in your theme does. You can reference a small set of pre-exposed variables (customer email, order name, etc.), but you cannot do dynamic key lookups based on a stored locale value. Any guide that shows you a snippet like {{ customer.metafields.storelingo.locale }} being used inside a Flow email body to swap language is showing you something that will silently render as blank or the raw tag in most Flow email actions.

What Flow can do:

  • Read customer and order metafields as conditions to branch your workflow
  • Add and remove customer tags based on locale signals
  • Fire a webhook to an external endpoint (Klaviyo, your own function, a custom app) that can render locale-aware templates
  • Trigger on Shopify Markets–aware events, since Markets exposes customer.locale through the Storefront API

This distinction shapes every strategy below.

How Shopify Markets Changes the Picture

If you are using Shopify Markets (the recommended approach for international stores in 2024 and beyond), locale routing is handled natively. When a customer checks out through a market, the order record carries a presentment_currency, a locale, and a market_id. These values are accessible in Flow as order conditions.

This means you do not need a custom metafield to detect a customer's language — you can branch on order.locale directly. Use a condition block like:

Order > locale > equals > fr

That single condition lets you route French-language customers into a separate branch without any API writes or webhook gymnastics. Build one workflow per market, or use parallel condition branches inside a single workflow.

If you are running a custom domain-per-market setup (e.g. mystore.fr, mystore.de), the market association is set at checkout and flows through to Flow reliably. Test this with a real order in each market before relying on it in production.

Building Locale-Aware Branches in Flow

Branching on Customer Locale

The practical pattern for most stores:

  1. Create a Flow triggered by Order Created (or whichever event applies)
  2. Add a Condition block: Order > locale > starts with > fr (use "starts with" to catch fr, fr-CA, fr-BE, etc.)
  3. In the True branch, add a Add customer tag action: lang-fr
  4. Repeat for each market locale
  5. In the False / else branch, default to English

Now every customer has a language tag. This tag is what you use downstream — in Klaviyo segments, in email platform filters, or in subsequent Flow conditions — to route them to the right template.

Routing Notifications to External Email Services

Because Flow's native email action cannot render locale-conditional content reliably, the production-grade approach is:

  1. Use Flow to fire a Send HTTP request (webhook) action when a trigger fires
  2. Pass customer.email, customer.locale, order.name, and any other relevant fields as JSON
  3. Your receiving endpoint (a custom app, a Klaviyo Flow, a simple serverless function) selects the correct pre-written template for that locale and sends the email

This is more setup, but it is architecturally correct and does not break silently. For abandoned cart sequences specifically, the same logic applies — see How to Translate Shopify Store Abandoned Cart and Email Flow Content for International Customers for a detailed walkthrough of the email-side implementation.

If you use Klaviyo, the locale tag you set via Flow becomes a profile property you can filter on inside Klaviyo flows. For a full picture of that integration, How to Translate Shopify Store App Emails and Klaviyo Flows for International Customers covers the Klaviyo-side setup step by step.

Translating the Content That Flows Touch

Flow automations often reference or trigger content that lives elsewhere in your store. Getting the automation routing right is half the job; the other half is making sure the destination content is actually translated.

Transactional email notifications (order confirmation, shipping update) live in Shopify's notification templates, not in Flow. Those need to be localized separately — How to Translate Shopify Email Notifications and Transactional Messages explains how Shopify's notification localization works and where the gaps are.

Post-purchase pages and checkout extensions that a Flow might redirect customers toward also need translated content. How to Translate Shopify Checkout Extensions and Post-Purchase Pages covers those surfaces.

Promotional content — if your Flow fires a discount code or surfaces a banner — needs to be in the customer's language. How to Translate Shopify Discount Codes, Banners and Promotional Content for International Campaigns addresses that specifically.

For stores using bundles or subscriptions that trigger reorder or renewal flows, How to Translate Shopify Bundle and Subscription Product Content for International Markets is worth reading alongside this guide, since the product content those flows reference also needs to exist in each locale.

Keeping Brand Terms Consistent Across Automated Touchpoints

Automated messages are often written once and forgotten, which makes them the most likely place for brand inconsistency to creep in. If you use a glossary to enforce terms like a product line name or a brand-specific phrase (StoreLingo has a built-in glossary for exactly this), apply the same term list to any copy you are writing for locale-specific email templates or webhook-triggered messages. Inconsistency in automated messages is particularly damaging because customers receive them at high-intent moments — after a purchase, after a support request — where trust matters most.

Measuring Whether Your Locale Routing Actually Works

You cannot improve what you do not measure, and Flow does not give you locale-segmented open rates natively. Here is where to look:

  • Flow run history: In your Shopify admin under Apps > Flow, each workflow shows a run log. Filter by date and look for unexpected branch distributions — if 90% of orders are going to your English branch but 30% of your traffic is French, your locale condition is misconfigured.
  • Email platform analytics: If you are routing through Klaviyo or another ESP, segment your campaign reports by the locale profile property you are writing via Flow tags. That is where you get open rates, click rates, and revenue per locale.
  • Shopify Analytics > Sales by market: Cross-reference conversion rates per market against email engagement. A market with high traffic but low conversion often has an automation gap. How to Measure ROI from Your Shopify Multilingual Store: Traffic, Conversions and Revenue by Language goes deeper on the analytics layer for international stores.

What to Translate Before You Build the Flows

There is no point routing French customers to a French email if your product pages and store content are still in English. Before investing time in Flow localization, make sure your core catalog is translated. StoreLingo translates products, collections, pages, and articles — including SEO meta fields — using AI, with a glossary to keep brand terms consistent, and change detection so only updated content needs re-translating. If you have a large catalog, How to Bulk-Translate Hundreds of Shopify Products in Minutes shows how to move through it efficiently.

Add StoreLingo on the Shopify App Store →


FAQ

Can Shopify Flow read a customer's locale directly, or do I need a custom metafield? If you are using Shopify Markets, the order record carries a locale field that Flow can read as a condition — no custom metafield required. For stores not using Markets, writing a locale value to a customer metafield via a custom app or webhook and then reading it in Flow is the standard workaround.

Does Flow's built-in "Send email" action support multilingual templates? No — Flow's native email action exposes a limited set of variables and does not support dynamic locale-based content switching. For locale-aware emails, use Flow to fire a webhook to an external email service (such as Klaviyo) that can select and render the correct locale template server-side.

How do I test that my locale-branching workflow is routing correctly before going live? Place a real test order through each of your Shopify Markets storefronts (use a separate browser session or incognito window pointed at the market's domain or URL parameter), then check the Flow run history to confirm the order hit the correct branch. Do not rely on manually setting customer tags to simulate this — the locale value on the order is what Flow evaluates, and it only gets set at checkout through a real market session.

Choose from 47 languages

StoreLingo translates products, collections, pages and articles with AI — review and approve by default. On paid plans from Starter, auto-translate is off by default and publishes new or updated products automatically. Keep your brand terms consistent.

Add to Shopify →