Review Summaries for a Multilingual Shopify Store

Shopify Markets makes a multilingual store straightforward in one direction. Your product titles, descriptions, navigation and checkout can all be served in the shopper's language. Your customer reviews cannot, because they were written by customers and Shopify's translation tools do not touch them.

That leaves a gap on the product page of every store selling into more than one language. The reviews are the most persuasive thing on the page and, for a shopper browsing in French, they are a wall of English. Here is what a review summary can and cannot do about it.

---

Can a Shopify review summary appear in each shopper's language?

Yes, on the Business plan. Sumzy, an AI review summary app for Shopify, can write the summary for a product in more than one language and store all of them together, and the theme block picks the one that matches the language the storefront is rendering in. On every other plan Sumzy writes summaries in a single store-wide output language, which is the right setting when your buyers mostly share a language.

The summary is written from the reviews rather than translated from another summary, so a German shopper reads German prose drawn from the same review corpus rather than a machine translation of an English paragraph. If you are still choosing an approach, the three routes to a summary sets out the options before the language question even arises.

---

What Shopify Markets and Translate and Adapt do, and what they do not

Markets is how you sell into more than one country or language from one store. Translate and Adapt is the tool that manages the translated content: product titles, descriptions, collection pages, theme text, checkout.

What it translates is the content you own. Reviews are not that. They are text your customers wrote, held in your review app, and neither Markets nor Translate and Adapt reaches them. This is not an oversight on Shopify's part. Translating a customer's words and presenting the result as their review is a legitimately awkward thing to do, and most review apps decline to do it for the same reason.

So on a multilingual Shopify store the review section behaves differently from the rest of the page. Everything above it adapts to the shopper. The reviews stay in whatever languages they were written in, which for most stores means mostly the language of your largest market.

A summary is a different object. It is not a translation of a review, it is a description of what reviewers said, and writing that description in a second language raises none of the problems that translating a review would.

---

How a per-shopper summary language works

Three things happen, and it is worth knowing which are yours and which are automatic.

You choose the languages. In Sumzy's settings, a Business store sees the languages its Shopify store publishes, read from the store's own locale settings, and ticks the ones summaries should be written in. Your primary language is always on and is the store default. The extras are your choice, which means adding a market to Shopify does not silently add a language to your summaries. If you want the new market covered, you tick it.

Sumzy writes them together. When a product's summary is generated, and again each time it refreshes, Sumzy writes the store-default summary plus one for each language you ticked. They all go into the same JSON field on the product, so there is one place to look and one thing to keep current.

The theme block picks one. When a shopper loads the product page, the block reads the language the storefront is currently rendering in and selects the matching summary. It reads the language the store is actually serving, not the shopper's browser setting, so it agrees with whatever the rest of the page is doing. No request goes anywhere while the shopper waits. The summary is already on the product.

---

What a shopper sees when their language has no summary yet

If a shopper is browsing in a language you have not turned on, or in one that has been turned on but not yet generated for that product, the widget renders the summary in your store's default language.

They see a real summary, immediately. There is no loading state, no placeholder and no spinner, and the page does not change under them while they are reading it. Once a summary exists in their language, it appears on a later visit to that product page.

One deliberate detail is worth knowing so it does not look like a bug. On that fallback, the widget's own labels are in the shopper's language while the summary text is in your store's default. The two diverge because they come from different places: the widget's interface strings ship with the app and follow the storefront, while the summary prose is generated per language. A French shopper on a product with no French summary yet sees French labels around English prose. That is the intended behaviour and the more useful of the options available, since the alternative is showing them nothing.

If you would rather no shopper met that fallback at all, generate summaries for your catalog after you turn a language on rather than waiting for the next scheduled refresh.

---

Which languages are covered

Sumzy writes summaries in 43 languages, including right-to-left languages, and reads reviews in any language regardless of which one it writes in. A store with reviews in five languages and one output language gets one summary drawn from all of them.

The languages you can turn on for per-shopper summaries are the ones your Shopify store publishes. That intersection is the practical limit: a language has to be both on Sumzy's list and published on your store before a summary can be written in it. If a shopper arrives in a language that is not covered, they get the store-default summary, which is the same fallback described above.

If you are earlier than this and still deciding whether summaries are worth adding at all, whether a summary is worth adding at all yet is the question to answer first. Language coverage only matters once the summary itself is earning its place.

---

When one store-wide language is the better setting

Per-shopper language is not automatically the right choice, and there are stores that should leave it off.

One dominant market. If 90 percent of your traffic browses in one language, one output language is simpler and covers almost everyone. The remaining shoppers get a summary in a language they can usually read, which is better than the review section they had before.

A market you serve in a lingua franca. Plenty of stores sell across Europe in English on purpose. Adding four languages to the summary when the rest of your store is in English produces an inconsistent page.

A catalog with thin review coverage. If most products have few reviews, more languages multiplies work over a signal that is not there yet. Get the reviews first.

It earns its place on a store with real traffic in two or more languages, on products that have accumulated reviews. There the summary does the job the reviews cannot: telling a shopper in their own language what other buyers found.

Per-shopper language is part of the Business plan. The store-wide output language, in any of the 43, is on every plan.

---

A next step

Whichever setting you choose, the summary is stored on the product and rendered by your theme rather than fetched while the page loads, so extra languages do not add anything to page weight. What a summary app costs you on page load covers how to verify that on your own store.

Sumzy offers a 14-day free trial on Shopify. You approve the subscription from your Shopify admin, so there is no separate card to enter and any charge appears on your Shopify bill. The trial becomes a paid plan when the 14 days are up, so cancel before then and you pay nothing.