Translate your Webflow store.
Own every word of it.

When the same source text was translated into the same language on the same site before, StoreLingo reuses the stored translation and it does not use AI characters. Your edits and approvals win over machine output. The glossary is a do-not-translate list for brand names and product lines.

Products: name, description and summary by default, plus other text fields you add in Settings, including image alt text. Variant option names and values (such as "Size" and "Small") are translated and published with the product. Variant names that Webflow generates are built from the translated product name and options; variant names you typed yourself can be translated. CMS items: name, summary and description by default, plus fields you add per collection.

• Translated copies. For each language you publish, StoreLingo creates a separate translated copy of each product that has at least one translated field, and of each CMS item. The copy takes the source's other fields as they are at publish time.
• Every variant. 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 variants that are new in the source and removes variants deleted there (Webflow does not allow removing a product's default variant, so that one is set to stock 0). A source product you archive in Webflow gets an archived translated copy on the next publish.
• A Locale field. On the first publish StoreLingo adds a plain text field named Locale to the Products collection and to each CMS collection it publishes, and sets it on every translated copy (de, fr and so on). Your own source products and CMS items are not tagged.
• Slugs. A translated copy's slug is the language prefix plus the source name, for example de-blue-mug. Slugs are not translated. If a slug is taken, a suffix is added (-2 to -10, or a short one from Webflow when the slug belonged to a deleted item).
• No site publish. StoreLingo writes its copies straight to your live site and never publishes your whole Webflow site, so your own unpublished Designer changes stay unpublished.
• Item limits. Translated copies count toward your Webflow site plan's own CMS item and product limits.
• Stock sync is optional. Each translated copy is a separate product, so each of its variants has its own stock in Webflow. Stock sync is set per site and is 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, StoreLingo does not read or change stock.

• Routing. Showing each language to the right visitors is your setup in Webflow: duplicate your listing pages per language and filter each Collection List by the Locale field (for the source language, the items without a Locale value). StoreLingo does not route visitors and does not switch languages. The app shows a routing guide after your first publish.
• No code to paste. StoreLingo places no code on your pages and does not add hreflang tags.
• Pages StoreLingo does not translate. Static page text, labels typed into your templates (such as "Add to cart" buttons and headings), navigation, checkout and cart pages, emails Webflow sends, Ecommerce categories and slugs.
• After you uninstall. The translated copies and their variants, the Locale field, and the Locale values on source CMS items tagged by older versions of StoreLingo stay in your site: they are your content. To remove the copies and the Locale fields StoreLingo created, run "Remove translations from Webflow" before you uninstall; afterwards StoreLingo cannot reach your site. The docs explain how to remove them by hand in Webflow. StoreLingo deletes your account and stored data 30 days after it loses access.