StoreLingo and Webflow Localization
Webflow's own Localization feature (Webflow calls it Localize) does not cover Ecommerce products. StoreLingo translates your products, and on a site that uses Localization it writes your CMS translations into Webflow's own locales. This page describes Localization only by quoting Webflow's public documentation, and does not describe its plans or prices: Webflow's own pages are the source for those. StoreLingo is an independent app and is not affiliated with or endorsed by Webflow.
What Webflow says Localization covers
From the Webflow University Webflow Localize checklist (read 18 November 2026). Text in quotation marks is Webflow's own wording.
- The checklist tells you to translate your static pages for each secondary locale.
- "Localize Collection item names, fields, and rich text."
- "Customize page names, slugs, SEO titles and descriptions, Open Graph settings, and custom code for each locale."
"Localize doesn't support Ecommerce Site plan features, so you can't localize products, categories, or Ecommerce pages."
Webflow's Help Center covers the same ground in Webflow Localize overview, Webflow Ecommerce overview and Localize Collection content. Check those pages for Webflow's current position before you decide.
How StoreLingo works on a site with Localization
StoreLingo checks whether your site uses Webflow Localization every time it reads or publishes the site, and works with it.
Into Webflow's own locale
- Publishing a language writes each CMS translation into Webflow's locale for that language: the same item, its locale version.
- Every write names that locale, so your primary-language items and your other locales are not changed.
- No separate copies, no Locale field and no page setup: Webflow shows the translation on that locale's pages, for example /es/blog/....
- The language must be one of the site's Webflow locales. If it is not, StoreLingo refuses to publish it, changes nothing, and names the locales the site has.
- A locale that is not yet published in Webflow keeps the translations until you publish that locale in Webflow.
Separate translated copies
- Webflow Localization does not cover Ecommerce products, so StoreLingo publishes each translated product as a separate copy, with a Locale field, exactly as on a site without Localization.
- A translated product gets every variant of the source, with translated option names and values and the source's price, compare-at price, SKU code and images per variant.
- Showing each language's products is your setup in Webflow: a product listing page per language, its Collection List filtered by the Locale field.
- Translated copies count toward your Webflow site plan's own product limits.
What StoreLingo leaves to you and to Webflow
- StoreLingo does not change your Webflow Localization settings, and does not add or publish locales.
- StoreLingo does not translate static page text, template labels, navigation, checkout and cart pages, or the emails Webflow sends.
- If the site holds separate CMS copies StoreLingo made before it used Localization, the next publish of that language removes them once the translation is in Webflow's locale.
- Publishing again rewrites the translated fields in the locale version, so changes made directly to those fields in Webflow's locale are replaced.
- How Webflow counts locale versions against your plan is set by your Webflow plan.
The details are in Locales and Publishing.
On a site without Webflow Localization
Webflow Localization is optional for StoreLingo. On a site without it, every product and every CMS item gets a separate translated copy with a Locale field, and you show each language with a listing page per language. Getting started lists every change StoreLingo makes in your site and everything you set up yourself.
StoreLingo at a glance
What StoreLingo does and does not do. For Webflow Localization, see Webflow's own documentation.
Questions
No. It is optional. With it, CMS translations go into Webflow's own locales. Without it, CMS items get separate translated copies. Products are separate translated copies either way.
On a site with Webflow Localization, one of the site's Webflow locales: the Add locale dialog lists them. When the site has two Webflow locales of the same language (es-ES and es-MX), add the exact one; StoreLingo never guesses which of the two a translation belongs in.
$19, $49, $99 or $249 a month, VAT included where it applies. Each plan includes a monthly allowance of AI characters, from 20,000 to 2,000,000, for DeepL translation. Translations reused from your translation memory do not count, and editing by hand is unlimited. See the plans.
What StoreLingo wrote stays in your site as your content: the translated products, and on a site with Webflow Localization the CMS translations in Webflow's locales. Before you uninstall, "Remove translations from Webflow" in the app deletes the translated copies and writes the source text back into the locale fields it translated. Ownership explains how to remove everything by hand.