Publishing to Webflow

When you click Publish [locale] to Webflow, StoreLingo executes our Strategy A write-back:

1. For each source product on the site, we check whether a per-locale duplicate already exists (tracked via webflow_locale_product_id in our DB).
2. If yes, we update that duplicate with the latest translated name, description, summary.
3. If no, we create a new duplicate Webflow product with a locale-prefixed slug (e.g., nl-ceramic-mug) and link it.
4. After every product is processed, we trigger a Webflow site publish.

Why duplicates and not the Webflow Localization API?

Webflow's native Localization does not currently cover Ecommerce products. Duplicate-product write-back is the only clean, SEO-friendly way to deliver translated product pages today. When Webflow opens native Ecommerce localization, StoreLingo will offer a one-click migration to the native model.

What gets duplicated

• Product name, description, summary
• Locale-prefixed slug
• SKU variants (see SKU translation)

What is NOT yet duplicated

• Product images
• Categories
• Custom fields beyond the three above (configurable in a future release)

Plan count impact

Each duplicate product counts against your Webflow site's product limit. Plan accordingly.