Skip to content

Languages & Translations

WhatPro can match the language of an outgoing message to the customer, and falls back sensibly when no exact match exists. There are two layers: the per-shop toggle in Settings and your plan.

When a flow fires, WhatPro detects the customer’s language from the storefront locale and the order’s customer locale. It then looks for a flow variant in that language. If language matching is off — or your plan doesn’t include it — every send uses your shop default language instead.

An active flow always wins over sending nothing. If the exact language has no usable variant, WhatPro falls back in this order:

  1. A flow in your shop default language.
  2. A flow in English.
  3. Any other active flow for that flow type.

This means a send never fails just because the customer’s exact language isn’t configured — it uses the best available variant.

A language-preference toggle in Settings turns automatic language matching on or off for the whole store. When it’s off, WhatPro forces the shop default language on every send, so each flow uses the single language you chose for it.

Sending in the customer’s language automatically is a Plus feature.

PlanLanguage matching
StarterShop default only
BasicShop default only
GrowthShop default only
PlusMatches the customer’s language automatically

On Starter, Basic, and Growth, you still choose the language for each flow — you just create one variant per language manually, and each flow sends in its own chosen language. On Plus, WhatPro detects the customer’s language and routes to the matching variant when one exists.

For building per-language flow variants, see Flow languages.

Message bodies are configured per flow inside WhatPro. Storefront-facing copy — the chat button, newsletter popup, and Checkout Gate text — integrates with Shopify’s Translate & Adapt app, so you manage those translations in the same place as the rest of your theme’s copy. Explicit edits you make in WhatPro’s admin take precedence over Translate & Adapt values.