How to translate a Webflow Ecommerce store: the options

You run a Webflow Ecommerce store and want to sell in more languages. There are a few broad ways to do it, and they differ in where the translations live, what they cover, and what you have to set up yourself. We make StoreLingo, so read this with that in mind; we have tried to describe our own product's limits as plainly as the rest.

The broad options

1. Webflow's own Localization feature.
2. A translation service that delivers translated pages from its own systems.
3. Translated copies written into your Webflow site, by a tool such as StoreLingo or by hand.

Option 1: Webflow Localization

Webflow's Localization feature lets you add languages to a site, translate static pages and CMS items (including with machine translation), and manage the localized versions inside Webflow.

If most of what you need translated is static pages and blog content, start there. If your products are what needs translating, read on. You can also combine Localization for your pages with another option for products. For Localization's price, see Webflow's pricing page.

Option 2: a service that delivers translated pages

Some translation services keep the translations on their side and deliver translated pages to visitors themselves, for example through a script on your site or a separate domain they serve. Products differ in how exactly they work, so ask each vendor directly:

• Where are the translations stored, and can I export them?
• What happens to my translated pages if I cancel?
• How are product variants, the cart and checkout handled?
• How is usage counted and priced (words, visitors, languages)?
• What does it add to my site, and how do I remove it?

Option 3: translated copies in your Webflow site

Here the translated content becomes part of your site: each translated product or CMS item is a real item in your Webflow CMS that you can open and edit like any other. You can do this by hand, or have StoreLingo do it.

What StoreLingo does

• StoreLingo is a Webflow app that connects to your site and opens in its own browser tab. Translations are made with DeepL into DeepL's supported target languages.
• By default it translates every text field that has text on your products and CMS items, and image alt text; in Settings you choose which fields are translated. You review and edit translations in StoreLingo's panel.
• When you publish a language, it creates one translated copy of each product and CMS item in your Webflow site, with a slug such as de-blue-mug (the slug is not translated) and a Locale field set to the language code.
• A translated product gets every variant of the source: the same options with translated names and values, and per variant the source's price, compare-at price, SKU code and images. Publishing again updates them, adds new variants and removes deleted ones.
• It writes straight to your live site and does not publish your whole Webflow site, so your own unpublished Designer changes stay unpublished.
• Stock sync is optional, per site and off by default. When it is on, a stock change in one language is passed on to the others; two shoppers buying the last item in two languages at the same moment can both succeed. When it is off, each translated variant has its own stock in Webflow and StoreLingo does not read or change it.
• Translated copies count toward your Webflow plan's product and CMS item limits.

What StoreLingo does not do

• Routing. It does not route visitors or switch languages. You duplicate your listing pages per language and filter each Collection List by the Locale field; the app shows a guide after the first publish.
• Template and static text. Static page text, labels typed into templates (such as "Add to cart"), navigation, cart and checkout pages, and emails Webflow sends are not translated.
• Hreflang. It adds no hreflang tags and places no code on your pages.
• Automatic updates. When a source item changes, the affected translations are marked Needs review. Nothing is re-translated or re-published until you do it.

After you uninstall

The translated products, their variants, the translated CMS items and the Locale fields stay in your Webflow site, because they are your content. If you want them gone, run "Remove translations from Webflow" in StoreLingo before you uninstall: it deletes the translated copies and the Locale fields StoreLingo created. After an uninstall StoreLingo cannot reach your site, so you would delete them in Webflow yourself; the steps are in the publishing post.

Price

Starter $19, Growth $49, Pro $99 and Agency $249 per month (VAT included where it applies), with limits on sites, languages, products per site and AI characters per month. Text reused from translation memory and editing by hand do not use AI characters. The trial lasts 14 days, needs no card, and runs on Starter's limits. Details are in the cost post.

By hand

You can create the translated copies yourself in Webflow: duplicate a product, give it a language-prefixed slug, and paste in the translated text. For a few products and one language that is a sensible choice. The work grows with every product, every language and every later change.

Choosing

Questions about whether StoreLingo fits your store go to hello@storelingo.com; we reply within one business day (Monday to Friday, CET).