Using WPML with WooCommerce Review Summaries
How per-shopper review summary language works on a WPML store, what happens on first page view in a new language, and which languages are supported.
WPML and a review summary plugin solve different problems on a WooCommerce store. WPML translates your product pages, navigation, and checkout flow so that shoppers can browse and buy in their own language. A review summary plugin reads what your buyers wrote and turns that text into a short, readable summary. They sit alongside each other. WPML does not translate your customer reviews, and a review summary plugin does not translate your store pages.
Where they connect is at the product page. If a shopper is browsing your store in French, a review summary in English is not useful to them. Sumzy, a WooCommerce AI review summary plugin, has a per-shopper language feature available on the Business plan that solves this: each shopper sees a summary in the language they are browsing in, generated from the same underlying review corpus.
Here is how it works in practice.
What WPML does and what Sumzy does
WPML handles the translation layer for your WooCommerce store. It gives you a language switcher, lets you maintain translated versions of product pages and categories, and routes shoppers to the correct locale. It is about your store's content in multiple languages.
Sumzy reads your WooCommerce product reviews, text written by buyers who have purchased from you, and generates a summary of what those buyers said. The summary is not a translation of anything you wrote. It is a synthesis of buyer feedback.
On any Sumzy plan, you set a single store-wide output language in the settings page. All summaries are generated in that language, regardless of what language individual reviews were written in. If your store language is German, every summary is in German. That single-language mode works well for stores that primarily serve one language audience.
The per-shopper feature extends this: instead of one store-wide output language, Sumzy generates a separate summary in each language that shoppers browse your store in. WPML provides the language detection. It tells the page what language the current shopper is using, and Sumzy uses that to pick or generate the right summary.
How per-shopper summarization works on a WPML store
When a shopper lands on a product page, WPML has already determined their language from their selection on the language switcher (or from browser preferences, depending on your WPML configuration). Sumzy checks whether a summary in that language already exists for that product.
If it does, the summary renders immediately from your local database. There is no external request on page load. The summary is stored locally and served from your own database, so your product pages stay fast even if Sumzy's backend is temporarily unavailable.
If no summary in that language exists yet, Sumzy queues a generation job. The first shopper to view a product page in a new language will see a loading state, a skeleton placeholder, while the summary is being generated. Once generation is complete, the summary is stored and every subsequent shopper in that language sees the result immediately.
This is called lazy creation. Sumzy does not pre-generate summaries in every supported language for every product when you first activate the feature. It creates language variants as shoppers request them. For most stores, this means the common languages fill in during normal traffic, and less common languages fill in when a shopper in that language arrives.
What happens on first page view in a new language
The first time a shopper in a new language visits a product page, there are two possible states.
If a summary in that language does not exist, the widget shows the loading state, a placeholder in the shape of the finished card, while generation runs in the background. The shopper does not see a blank widget or an error. The page does not update itself while they are on it, though. The summary appears on the next load of that product page after generation finishes, whether that is the same shopper coming back or the next visitor browsing in that language.
If your store is new to a language and no shoppers have visited that product page in that language yet, you can also trigger summaries manually from the wp-admin summaries list. This lets you pre-populate the languages you expect before the first real shopper arrives, if you prefer not to have the loading state at all.
Either way, once a language variant exists for a product, it is served from your local database on every subsequent page load with no generation step.
Summary refresh: when the language-specific summary updates
Language-specific summaries refresh on the same cycle as your main summaries. When new reviews arrive and the automatic refresh runs, summaries in all existing language variants for that product are queued for regeneration. You do not need to trigger per-language regeneration manually.
If you edit a summary in approval mode (Professional plan and above), the edit applies to the specific language variant you edited. Other language variants are not automatically updated when you edit one.
Polylang as an alternative to WPML
Polylang is the main alternative to WPML for multilingual WooCommerce stores. The per-shopper summarization feature works with Polylang as well. The behaviour is the same: Polylang provides the language context, Sumzy uses it to select or generate the right summary variant.
If you are running a Polylang store and considering Sumzy, the Business plan and the per-shopper feature work the same way regardless of which multilingual plugin you are using. You do not need WPML specifically.
For single-language stores or stores where you want one output language regardless of shopper language, any Sumzy plan supports the store-wide output language setting, and you do not need WPML integration at all.
Supported languages
The supported-languages list covers the languages Sumzy can generate summaries in. Major European languages are supported: German, French, Spanish, Italian, Dutch, Portuguese, Polish, Swedish and others. Some less commonly spoken languages may not be on the supported list. You can check the current list in your account settings.
There is no per-product variant cap on Business. Sumzy generates a summary in each shopper's language as they arrive, and keeps them all. Only invisible abuse protection applies, and no ordinary store would reach it.
If a shopper browses in a language that is not on the supported list, Sumzy falls back to your store-wide output language setting rather than attempting generation in an unsupported language.
A next step
If you want to understand how the store-wide output language setting works before enabling per-shopper mode, the show reviews in your shopper's language post covers the single-language setup.
For a broader view of how multilingual stores use review summaries, including what happens with mixed-language review corpora and which languages the model handles well, the handling reviews in multiple languages post is a good starting point.
The multilingual stores use-case page has the full configuration details and explains how the per-shopper feature fits into a WPML or Polylang store setup.
Sumzy's Business plan is where the per-shopper language feature lives.