StoreLingo
Coming from Localize

StoreLingo and Localize for Webflow Ecommerce

This page explains how StoreLingo works, so you can compare it with what you use today. It does not describe Localize's plans, prices or features: Localize's own website is the source for those. StoreLingo has no relationship with Localize.

This page is about the translation service Localize at localizejs.com. For Webflow's own Localization feature, which Webflow calls Localize, see StoreLingo and Webflow Localization.

14-day free trial · no card needed to start

How StoreLingo works compared to a translation overlay

Two ways to show a store in more than one language.

A translation overlay

Some translation tools keep your translations on their own servers and show them to visitors through a script on your pages, or by serving the translated pages themselves. Whether a given tool works this way, and what happens to your translations when you stop using it, is described in that tool's own documentation.

StoreLingo

StoreLingo writes your translations into your own Webflow site through the Webflow Data API: products as separate translated copies, and CMS items as translated copies or, on a site with Webflow Localization, into Webflow's own locale for the language. Webflow serves those pages, and StoreLingo places no code on your site. What it wrote is your content and stays in Webflow if you uninstall StoreLingo.

What that means for your store

  • Translated copies count toward your Webflow site plan's own CMS item and product limits.
  • For translated copies, showing each language to the right visitors is your setup in Webflow: listing pages per language, each Collection List filtered by the Locale field StoreLingo adds. On a site with Webflow Localization, CMS translations show on that locale's pages with no setup. StoreLingo does not route visitors, switch languages or add hreflang tags. You do not paste any code.
  • StoreLingo writes straight to your live site and does not publish your whole Webflow site, so your own unpublished Designer changes stay unpublished.
  • 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. Each variant has its own stock in Webflow; the optional stock sync (off by default) passes stock changes between languages, and two shoppers buying the last item in two languages at the same moment can both succeed.
  • Static page text, template labels, navigation, checkout and cart pages, and the emails Webflow sends are not translated.

The full list is in Getting started.

StoreLingo at a glance

What StoreLingo does and does not do. For Localize, see Localize's own website.

Your content
Translations are written into your own Webflow site
✓ Yes
Through the Webflow Data API: products as separate translated copies; CMS items as copies, or into Webflow's own locale on a site with Webflow Localization
Translated pages are served by Webflow
✓ Yes
StoreLingo places no code on your pages
Translations stay in Webflow after you uninstall
✓ Yes
Before uninstalling you can undo them with "Remove translations from Webflow"
Pricing
Flat monthly plans
✓ Yes
$19 / $49 / $99 / $249 (VAT included), each with a monthly AI character allowance
Per-word charges
✕ No
Per-visitor charges
✕ No
Permanent free plan
✕ No
14-day trial, no card needed to start
Webflow Ecommerce
Translated product copies
✓ Yes
Every text field that has text, by default; you choose which in Fields
Product variants
✓ Yes
Every variant, with translated option names and values
Stock sync between languages
~ Partly
Optional per site, off by default. Two shoppers buying the last item in two languages at the same moment can both succeed
Webflow Localization
CMS items into Webflow's own locales
✓ Yes
On a site with Webflow Localization: the same item, its locale version, with no separate copies and no page setup
Products on a site with Webflow Localization
✓ Yes
As separate translated copies, because Webflow Localization does not cover Ecommerce products
Changes your Localization settings
✕ No
StoreLingo does not add or publish locales
Visitors and search
Sends visitors to their language
✕ No
For translated copies, your setup in Webflow: listing pages filtered by the Locale field. With Webflow Localization, Webflow shows CMS translations on that locale's pages
hreflang tags
✕ No
StoreLingo does not add hreflang tags
Translated slugs
✕ No
Translated copies get slugs like de-blue-mug
Workflow
AI translation with DeepL
✓ Yes
Within your plan's monthly AI characters
Translation memory
✓ Yes
Per site and per language pair
Glossary
✓ Yes
A do-not-translate list for brand names and product lines
CSV export and import
✓ Yes
Rows that do not match are reported
Static page text
✕ No
Not translated
Visual in-context editor
✕ No
You edit in the StoreLingo app
Request this →

Bring existing translations with a CSV

If you have your translations as a spreadsheet, you can bring them into StoreLingo's CSV layout.

  • StoreLingo has no importer for Localize
  • Export StoreLingo's CSV, fill in the translations you already have, and import it
  • Each imported row keeps the status written in the file
  • Rows that do not match are reported, not guessed
  • AI translate missing fills the rest, within your monthly AI characters

14-day free trial. No card needed to start. Publishing to Webflow asks for a card on file; nothing is charged before your trial ends.

Questions

Is StoreLingo built on Localize?

No. StoreLingo has no relationship with Localize and does not use Localize's services. It reads and writes your site through the Webflow Data API, and translation is done by DeepL.

What does StoreLingo not do?

It does not translate static page text, template labels, navigation, checkout and cart pages or the emails Webflow sends. It does not route visitors, switch languages or add hreflang tags. It has no visual in-context editor: you edit in the StoreLingo app.

What does StoreLingo cost?

$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. Translations reused from your translation memory do not count, and editing by hand is unlimited. See the plans.

What stays in my site if I stop using StoreLingo?

The translated copies and their variants, the Locale fields, the Locale values on source CMS items tagged by older versions of StoreLingo, and on a site with Webflow Localization the CMS translations in Webflow's locales. They are your content. Before you uninstall, "Remove translations from Webflow" in the app deletes the translated copies and the Locale fields StoreLingo created, and writes the source text back into the locale fields it translated. The docs explain how to remove them by hand if you want to.