WooCommerce WPML chatbot: the multilingual AI that actually reads your translated catalog

The only WooCommerce chatbot with native WPML support in 2026 is Storebird. Every other chatbot — Tidio, Crisp, WoowBot, LiveChat — supports multiple UI languages but does not integrate with WPML's translated product catalog. That means translated slugs, translated attributes, and language-switched visitors all break. Here is what "multi-language chatbot" actually means on a real WPML WooCommerce store, and how to test any tool before you commit.

Key takeaways

• Most "multilingual" chatbots translate the widget UI, not the product catalog. Your Dutch visitor still gets English product names and links.
• WPML stores have translated slugs, translated attributes, and a language switcher — a chatbot that ignores these creates a broken experience.
• Storebird detects the visitor's WPML language, reads the translated catalog, and replies in the correct language. One knowledge base, not one per language.
• Tidio Lyro supports multiple languages for replies, but does not read your WPML-translated product data. It pulls from your default-language FAQ.
• Zero dedicated content exists in Google for "WPML chatbot" or "multilingual WooCommerce chatbot" — which tells you how few tools actually solve this problem.

Written by the Storebird team. Last updated: April 12, 2026.

The WPML problem most chatbot vendors ignore

If you run a WooCommerce store with WPML, you already know the stack is more complex than a single-language shop. WPML does not just translate strings — it creates separate post IDs for each language version of a product. Your Dutch "Leren Jas" and your English "Leather Jacket" are two different WordPress posts linked by WPML's translation management.

That matters for chatbots because most chatbots read the default-language product data and call it done.

Here is what breaks in practice:

• Translated slugs. Your English product lives at /product/leather-jacket/. Your Dutch version lives at /nl/product/leren-jas/. A chatbot that scrapes the English page will link a Dutch visitor to the wrong URL — or worse, to a 404 if the English slug doesn't exist in the Dutch language scope.
• Translated attributes. "Size" becomes "Maat" in Dutch, "Größe" in German. "Color" becomes "Kleur" or "Farbe." If the chatbot reads the default-language attribute labels, it serves a half-translated response that looks broken.
• The language switcher. WPML's language switcher sets a cookie and rewrites URLs. A chatbot that does not respect this context will reply in the default language regardless of what the visitor selected. The visitor is browsing in French; the chatbot answers in English. That is not a multilingual experience — it is a bug.

These are not edge cases. WPML's own compatibility page lists only a handful of tested chat plugins, and the testing focuses on widget translation — not catalog data. If you sell across the EU — where WooCommerce powers roughly 39% of all online stores — your chatbot is actively working against the multilingual experience you spent months building.

What "multi-language chatbot" actually means (and what vendors leave out)

When a chatbot vendor says "supports 100+ languages," they almost always mean one of two things:

UI translation

The chat widget — the greeting bubble, the "type a message" placeholder, the "powered by" footer — appears in the visitor's language. This is the bare minimum. It is also what most vendors mean when they say "multilingual."

UI translation is table stakes. It does not make a chatbot multilingual in any meaningful sense for a WooCommerce store.

Reply-language detection

The AI detects the visitor's language from their message and replies in that language. Tidio's Lyro does this. So do several other tools. This is better than UI-only translation, but it still misses the core problem: the data the AI uses to generate those replies is still in the default language.

If your Dutch visitor asks "Hebben jullie deze jas in maat L?" and the AI's product data says "Leather Jacket — Size: L — In Stock," the reply might be in Dutch, but it references the English product name. The link it generates goes to the English slug. The attribute labels are English. The customer notices.

Catalog-aware translation (what actually matters)

A truly multilingual WooCommerce chatbot reads the WPML-translated version of the product for the visitor's active language. That means:

• The product name the chatbot uses is the translated name
• The product URL the chatbot links to is the translated slug
• The attribute labels ("Maat," "Kleur") match the language context
• The price and currency match the locale configuration
• The stock status is read from the correct variation (WPML can have language-specific stock in some setups)

This is what Storebird does. It queries WPML's translation links to find the correct post ID for the visitor's language, then reads that post's product data. One knowledge base, one product sync — WPML handles the translation layer, Storebird respects it. See how Storebird handles multi-language stores.

No other WooCommerce chatbot does this as of April 2026. If you find one that does, run the test in section seven of this article and verify it yourself.

How Storebird handles WPML natively

Storebird's WPML integration is not a toggle or an add-on. It is built into the product sync. Here is how it works at a technical level, simplified for non-developers:

1. Language detection. When a visitor loads a page, Storebird reads the active WPML language from the page context (ICL_LANGUAGE_CODE). This happens before the chat widget renders.

2. Catalog query in the correct language. The chatbot queries WooCommerce product data using the WPML-translated post ID — not the default-language post. Product name, attributes, price, and stock are all from the correct language version.

3. Translated slug links. Product links use the translated permalink. A Dutch visitor gets /nl/product/leren-jas/, not /product/leather-jacket/. No redirect chains, no 404s.

4. Reply in the visitor's language. The AI responds in the same language as the catalog data. No mixing English product names into a Dutch sentence.

5. Single knowledge base. Return policy, shipping FAQ, and custom instructions are maintained once. Storebird generates replies in the visitor's language from the content you provide — no separate FAQ per language.

The result: a visitor browsing your German store sees a chatbot that speaks German, knows the German product names, links to the German pages, and uses German attribute labels. It behaves as if the chatbot was built for that store.

For the full feature overview, see Storebird's product intelligence page.

Tidio, Crisp, and WoowBot: how competitors handle multi-language

Every chatbot vendor checks the "multilingual" box. Here is what that box actually contains for the three tools WooCommerce stores most commonly evaluate.

Tidio (Lyro AI)

Tidio Lyro supports reply-language detection — it can reply in Dutch if the visitor writes in Dutch. That part works. The problem is Lyro's data source: it is trained on your FAQ knowledge base and website content, not your WPML-translated product catalog. If you wrote your FAQ in English, Lyro's Dutch reply pulls from English source material. Product names, attribute labels, and links default to the English versions. Tidio does not read WPML translation links or translated post meta.

For a deeper Tidio comparison, see our full Tidio alternative breakdown.

Crisp

Crisp supports multilingual chat greetings and canned responses. You can configure a different welcome message per language. Crisp's AI (Crisp AI) can reply in multiple languages. But like Tidio, it does not integrate with WPML. The chatbot does not know which product translation the visitor is viewing, and it does not generate translated-slug links. For general-purpose multichannel chat, Crisp is solid. For WPML-aware WooCommerce support, it is not.

WoowBot

WoowBot is the oldest WooCommerce chatbot plugin. It supports basic keyword search against your product catalog. WoowBot Pro added WPML "support" in the sense that it can display the chatbot in the site's language. But WoowBot's product search is keyword-matching against the default-language product titles — it does not query the WPML-translated catalog. If a German visitor types "Lederjacke," WoowBot searches for that term in your English product titles and finds nothing. For a modern alternative, see our Storebird vs WoowBot comparison.

The honest summary

If your store is English-only, any of these tools will work. If you run WPML, only one of them actually integrates with your translation layer.

The EU compliance angle: why language matters beyond UX

This is the part most chatbot articles skip. It matters anyway.

GDPR does not mandate that chatbots reply in a specific language. But EU member states layer their own consumer protection rules on top:

• Germany: The BGB requires pre-contractual information — product details, return policies, pricing — in German for German consumers.
• France: The Toubon Law requires commercial communications with French consumers to be in French.
• Netherlands: The ACM expects consumer-facing information in Dutch when targeting Dutch consumers.

A chatbot answering order status or product questions is providing pre-contractual information. If it replies in English to a German visitor on a German-language store, you create a gap between your store's language promise and the actual experience.

Will you get fined tomorrow? Probably not. But a consumer complaint referencing an English-only chatbot on a Dutch store is a credibility problem you do not want. The simpler argument: you spent weeks translating your store. Your chatbot should respect that work.

For stores that want the full WooCommerce compliance picture, our AI chatbot ecommerce guide covers GDPR data handling in more detail.

When Storebird is not the right choice

Storebird handles WPML better than anything else on the market. That does not make it the right tool for every store.

You don't use WPML. If your multilingual setup is Polylang or TranslatePress, Storebird's WPML-specific integration does not apply. We are evaluating Polylang support, but it is not shipped as of April 2026. If Polylang is your stack, test Storebird anyway — the AI's reply-language detection still works — but the deep catalog-aware translation requires WPML.

You need a full helpdesk. Storebird is a chatbot with live handoff, not a ticketing system. If you need shared inboxes, email threading, SLA management, and multi-agent assignment across channels, look at Freshchat or Zendesk and accept the WPML gap.

You need Messenger, Instagram, and WhatsApp in one inbox. Storebird is web chat only. If your customers message you from three different channels, Crisp is the stronger pick — even without the WPML integration.

Your store is on Shopify. Storebird is WooCommerce-only. If you are on Shopify, look at Gorgias AI Agent.

That is the honest list. If none of those apply and you run WPML, keep reading.

The WPML chatbot testing checklist

Before you commit to any chatbot on a WPML WooCommerce store, run this test. It takes ten minutes and will save you a migration later.

1. Switch to a non-default language. Use your WPML language switcher to browse the store in Dutch, German, or whichever secondary language you support.
2. Navigate to a translated product page. Pick a product with translated attributes (size, color) and a translated slug.
3. Open the chatbot and ask a product question. Try: "Is this available in size L?" or "What colors do you have?"
4. Check the response for these failures:

• Does the chatbot use the English product name instead of the translated one?
• Does any product link point to the default-language slug instead of the translated slug?
• Are attribute labels in English when you are browsing in Dutch?
• Did the chatbot reply in English even though you are on a Dutch page?

1. Ask an order status question. If the chatbot handles orders, ask "Where is my order?" and check if the reply is in the correct language.
2. Switch back to the default language and repeat. Confirm the chatbot works correctly in the default language too — some tools break in the opposite direction.
3. Check the link destinations. Click every product link the chatbot generated. Do they land on the correct language version of the page, or do they redirect through the default language first?

If any of those checks fail, the chatbot does not actually support WPML. It supports multiple languages in theory, not on your store.

Storebird passes all seven checks. Run the test yourself during the 14-day free Pro trial — no credit card required. Setup takes under 15 minutes: install from WordPress.org, enter your license key, and WPML is detected automatically. Add your knowledge base (one version, Storebird handles language matching), customize the widget, and run the seven-point test. For the full walkthrough, see our install guide.

Frequently asked questions

Do WooCommerce chatbots work with WPML? Most do not. Generic chatbots support multiple UI languages but do not integrate with WPML's translated product catalog, translated slugs, or language switcher. Storebird is the only WooCommerce chatbot with native WPML integration as of April 2026.

What breaks when you use a regular chatbot on a WPML store? Three things: product links point to the wrong language version, attributes show untranslated labels, and the chatbot replies in the default language regardless of the visitor's language switcher selection. The root cause is that most chatbots read the default-language product data only.

What is the difference between UI translation and catalog-aware translation? UI translation means the widget buttons and greeting appear in the visitor's language. Catalog-aware translation means the chatbot reads the correct translated product names, descriptions, attributes, and prices from your WPML catalog. Most tools offer the first but not the second.

Does Tidio work with WPML? Tidio's Lyro AI can reply in multiple languages, but it does not read your WPML-translated product catalog. Product names, links, and attribute labels default to the English source material. For a complete comparison, read our Tidio alternative guide.

Which languages does Storebird support on WPML stores? English, Dutch, German, French, Spanish, and Italian out of the box, with automatic language detection via WPML. More languages are added based on customer demand.

Do I need separate knowledge bases for each language? With Storebird, no. You maintain one knowledge base for policies and FAQs. The chatbot reads WPML-translated product data directly and generates replies in the visitor's language. With generic chatbots, you typically need one FAQ per language.

Is a multilingual chatbot required for GDPR compliance? GDPR itself does not mandate chatbot language. However, several EU countries — Germany, France, the Netherlands — have consumer protection laws requiring pre-contractual information in the local language. A chatbot answering product or order questions in the wrong language creates compliance and trust risk.

How do I test whether a chatbot actually works with WPML? Switch to a non-default language, go to a translated product page, and ask the chatbot a product question. If it replies with the English product name, links to the English slug, or shows untranslated attributes, it does not support WPML. See the full seven-point test in section seven of this article.

The bottom line for WPML WooCommerce stores

You built a multilingual store with WPML because your customers expect to browse, buy, and get support in their language. Your chatbot should match that expectation — not break it.

Most chatbots claim multi-language support. On a real WPML WooCommerce store with translated slugs, translated attributes, and a language switcher, that claim falls apart. The chatbot serves English data to Dutch visitors, generates wrong-language links, and undermines the translation work you already did.

Storebird is the first WooCommerce chatbot built for this problem. Native WPML detection, catalog-aware translation, translated slug links, and one knowledge base for all languages. Flat pricing at EUR 39 to EUR 199 per month, AI included, no per-reply fees.

Start the 14-day free Pro trial and run the seven-point WPML test yourself. If it passes on your store — and it will — you have your answer.