How StoreLingo publishes translations into your Webflow site

There are two broad ways to show a website in another language. A translation service can deliver translated pages from its own systems, or translated content can be written into the site itself. StoreLingo takes the second route: it writes translated copies of your products and CMS items into your own Webflow site. This post explains what that means in practice, including the parts you have to set up yourself and what stays behind if you stop using StoreLingo.

What StoreLingo is

StoreLingo is a Webflow app that connects to your site. It opens from Webflow in its own browser tab; it does not run inside the Designer. It asks Webflow for these permissions: authorized_user:read, sites:read, sites:write, cms:read, cms:write, ecommerce:read and ecommerce:write. It does not ask for custom code access and places no code on your published pages. Translations are made with DeepL.

What gets translated

• Products: by default every text field that has text on at least one product (for example the name and the description), and image alt text. In Settings you choose which. Variant option names and values ("Size", "Small") are translated too.
• CMS items: by default every text field that has text on at least one item, per collection. You choose which in Settings.
• Not translated: static page text, labels typed into page templates (such as an "Add to cart" button), navigation, the cart and checkout pages, emails Webflow sends, Ecommerce categories, and slugs.

Every translation has a status (AI, Edited or Approved), and you can edit any of them by hand before publishing.

What publishing creates

You publish one language at a time. For each language:

1. One translated copy per product. For each source product that has at least one translated field, StoreLingo creates a separate product in Webflow: a duplicate carrying the translated text and every variant of the source, with the source's other fields copied as they are at publish time.
2. One translated copy per CMS item in the collections you translate, created the same way.
3. A slug with a language prefix. The copy's slug is the language prefix followed by the source name, for example de-blue-mug. It is not translated. If Webflow reports that slug as taken, StoreLingo tries -2, then -3, up to -10.
4. 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; source CMS items tagged by older versions of StoreLingo keep their value.
5. No site publish. Everything StoreLingo writes goes straight to your live site. StoreLingo never publishes the whole Webflow site, so your own unpublished Designer changes stay unpublished.

Variants

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 archived in Webflow gets an archived translated copy on the next publish. The full picture is in the variants post.

Stock

A translated copy is a separate product, so each of its variants has its own stock in Webflow. Stock sync is optional, set per site and off by default. When it is on, every translated variant takes its source variant's stock, and 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, except in one case: when you delete a variant from a source product, the next publish sets its translated copy out of stock and then deletes it, so it cannot be sold.

What you set up yourself

StoreLingo does not route visitors, does not switch languages and does not add hreflang tags. 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. Your source items carry no Locale value, so the source-language list shows the items where Locale is not set. After the first publish, the app shows a routing guide with these steps.

Each translated product and item also has its own page under Webflow's normal template for that collection. Text that lives in the template itself stays in the source language.

Keeping translations up to date

• StoreLingo registers Webflow webhooks for collection items being created, changed and deleted; product edits fire them too. When a source product or CMS item changes, StoreLingo updates its own copy of the source (texts, options and variants) and marks the affected translations Needs review. Nothing is re-translated or re-published automatically.
• The Re-sync button pulls the latest source content on demand.
• When you publish again, StoreLingo updates the translated fields, the options and every variant's price, code and images on the copy it created earlier rather than making a new one. It keeps the Webflow ID of each copy for that purpose.
• If that link is lost, for example after a reinstall, the Lost translations dialog finds translated copies in Webflow that StoreLingo is no longer linked to, and lets you adopt them back or delete them.

What it costs you in Webflow

Every translated copy is a real product or CMS item, so it counts toward your Webflow site plan's own CMS item and product limits. Count before you publish: your translated source products times the number of languages is the number of new products, and the same goes for CMS items. Check the limits of your Webflow plan on Webflow's pricing page.

What stays in your site after you uninstall

The translated content is your content and lives in your Webflow site, so uninstalling StoreLingo does not remove it. These stay:

• every translated product and its variants;
• every translated CMS item;
• the Locale field on the Products collection and on each CMS collection StoreLingo published;
• the Locale value on source CMS items tagged by older versions of StoreLingo.

Before you uninstall, Remove translations from Webflow in StoreLingo's site menu does this for you. It deletes every translated product (with its variants) and every translated CMS item StoreLingo published to that site, and the Locale fields StoreLingo created; a Locale field you made yourself is left alone. Your own products and items are not changed, and the translations stay in StoreLingo, so publishing again puts everything back. A removed product page stays reachable by its direct link until your next site publish in Webflow, and Collection List filters on the Locale field have to be removed in the Designer. Run it before you uninstall: after an uninstall StoreLingo cannot reach your site.

To remove them by hand in Webflow:

1. Delete or archive the translated products (Ecommerce, Products). They are the ones whose Locale is a target language, or whose slug starts with the language prefix.
2. Delete or archive the translated CMS items (filter each collection by Locale).
3. Delete the Locale field in each collection's settings.
4. Publish the site.

On StoreLingo's side, Webflow removes StoreLingo's webhooks when the app is uninstalled. StoreLingo notices the lost access in a daily check and deletes your account and all stored data 30 days later; reinstalling within those 30 days picks up where you left off. Account, Delete account deletes everything at once. Deleting a language in StoreLingo removes StoreLingo's translations for it, but the copies already in Webflow stay.

Things StoreLingo does not have

• No visual editor on the live page. Editing happens in StoreLingo's own panel.
• No automatic re-translation or re-publishing when the source changes.
• No hreflang tags, no language switcher and no visitor routing.

You can also do all of this by hand: create a product, give it a de- slug, paste in the translated text, and repeat for every product and language. For a handful of products that is a reasonable choice. StoreLingo does the translating, the copying and the record keeping for you.