Multilingual E-commerce Customer Support: Selling Across Europe

Selling across Europe means your shoppers write to you in many languages. A customer in Milan asks about delivery in Italian, one in Cluj asks about ingredients in Romanian, and one in Munich wants to know about returns in German. Most shops can afford support in one or two of those languages, and only during office hours.

This article covers how AskMerra answers shoppers in their own language, what you need to set up for it to work well, and practical tips for running a multilingual store: policies, prices and testing.

Why language matters at the moment of purchase

Many cross-border shoppers can read some English. Reading is rarely the problem. The problem is the questions that come right before a purchase: does this suit my skin, will it fit, how much is shipping to my country, can I send it back. People want to ask those in the language they think in, and a misunderstanding at that point often ends in a return or a lost sale.

Translating your product pages helps, but a translated page still cannot answer a question. A shopper with a specific need has to search, guess and compare, in a language that may not be their first. A conversation in their own language removes most of that effort.

Six languages, detected automatically

AskMerra speaks English, Romanian, Italian, French, German and Spanish. There is no language picker for the shopper to find. The assistant detects the language the shopper writes in and replies in that language.

The same question can arrive in many forms:

• "Which serum is best for dry skin?"
• "Ce ser e potrivit pentru ten uscat?"
• "Quale siero per la pelle secca?"
• "Quel sérum pour une peau sèche ?"
• "Welches Serum bei trockener Haut?"
• "¿Qué sérum para piel seca?"

Each one gets an answer in its own language, with recommendations from the same catalog.

It works even if your catalog is in one language

This matters most for smaller shops. You do not need to translate your whole catalog before you can serve shoppers in other languages. If your products are described only in Romanian and a shopper writes in German, AskMerra still searches your catalog, finds the right products and answers in German.

If you do have translated product data, you can import it as well: add a locale column and provide one row per product and language.

Budgets in the shopper's own words

Price phrases are understood across all six languages. "Under €30", "sub 100 lei" and "tra 20 e 40 €" all become real price filters on the search, so the shopper's budget is respected whatever language they use.

The widget speaks the language too

The answers are only half of it. The chat window itself (the greeting, the suggested questions, the header title) should match the shopper's language as well.

The widget chooses its interface language in this order:

1. a language you set on the script tag, if you set one
2. the language your page declares (its html lang attribute)
3. the visitor's browser languages
4. your shop's default language

Separately from the interface, the assistant always replies in the language the shopper writes in.

In the widget designer you write the greeting, up to six suggested questions and the header title for each language, and the designer flags translations that are missing. Missing texts fall back to your default language, then to English. You can also name your assistant, with one name for every language or a different name per language. The name appears in the widget header, and the assistant uses it when it introduces itself.

A tip: write suggested questions for each market rather than translating them word for word. The most common question in one country is not always the most common one in the next.

Policies and FAQ in every language

Shipping and returns are where multilingual stores get the most questions, and where accuracy matters most.

Knowledge documents per language

In AskMerra's knowledge base you create one document per topic and language: shipping, returns, payments, brand, FAQ and custom pages. If a document is missing in a language, the assistant translates from your default-language version when it answers. That is a useful safety net, but for your main markets it is worth writing the policy in that language directly, especially the parts with legal weight, like return windows and conditions.

FAQ entries per language

FAQ entries are short question and answer pairs. When a shopper's question closely matches one, your answer is returned instantly, word for word, without an AI call. Instant answers are matched within the shopper's language, so add entries for each language you serve. In other languages, the assistant still uses your FAQ as a reference when it answers.

Be specific per country

A good shipping document for a cross-border shop lists, for each country you ship to:

• the shipping cost and any free-shipping threshold
• the delivery time and carrier
• order cut-off times

The assistant can only be as precise as what you write. "We ship across the EU" leads to vague answers. A short list per country leads to exact ones.

Currencies and prices

Each product in your catalog carries a currency as an ISO code, such as EUR or RON. If your export has no currency column, the source or shop currency is used. Local price formats like "19,99 lei" or "€19.99" are understood on import, so you do not need to clean up your export first.

Product cards always show the live price, sale price and stock from your latest sync, so the price a shopper sees in the chat matches your catalog.

If you run separate storefronts per country, each one can be its own shop in AskMerra, with its own catalog, knowledge base, widget settings and team. One account can own several shops.

Test every language before going live

Do not wait for customers to find the gaps. Before you publish:

• Ask in each language in the playground. Use the real questions your customers send, typos included. The debug panel shows which products were found and which route answered (FAQ, cache or AI).
• Preview the widget per language. The designer's live preview has a language switch, so you can check every greeting and suggested question.
• Check your FAQ matches. Ask your FAQ questions in a few different wordings in each language to see which ones get the instant answer.

After launch, the overview shows which languages your shoppers use, and the conversations inbox can be filtered by language. That tells you where to put effort next: a missing FAQ entry, a policy that deserves a native version, or a market that turns out to be bigger than you thought.

Privacy across borders

Selling in Europe also means GDPR. AskMerra hosts data in the EU, never stores raw IP addresses, keeps visitors anonymous by default and lets you set how long conversations are kept. Every widget shows an AI disclosure with a link to your privacy policy, and a data processing agreement is available for your compliance file.

Serve every market in its own language

To test all of this on your own catalog, create your account or book a demo. Check the pricing page to see how many languages each plan includes. For setup details, see the docs on widget languages and the knowledge base. If you are new to the idea, start with what an AI shopping assistant is, or see why conversation beats the search box for many shoppers in conversational product search vs keyword search.