StoreLingo
Start free trial →

Troubleshooting

Common issues, in order of how often customers hit them.

"No products synced yet"

Your Webflow site needs an active Ecommerce plan (Standard or higher) for StoreLingo to see products. Free and Starter Webflow plans don't include Ecommerce.

Fix: upgrade your Webflow site to Ecommerce Standard, then disconnect and reconnect the site in StoreLingo. The sync will pick up your products on the new connect.

"Found N translations from a previous install" - what do I do?

Your Webflow site already has translated CMS rows from an earlier StoreLingo install (or another StoreLingo account). The toast offers a Recover button that opens the Orphan Recovery dialog. Adopt them all to keep your existing translations without re-running AI. See Orphan Recovery for the full walkthrough.

"Reauthorize to enable Automatic hreflang" appears in the Hreflang dialog

Your Webflow OAuth token was issued before StoreLingo added the Custom Code scope (needed to register the hreflang script). One click on Reauthorize StoreLingo runs OAuth again, Webflow shows the consent screen with the new scope, you accept, you land back in the dialog with Automatic mode now working.

Doesn't affect anything else; you can keep using Manual or Off mode without the extra scope.

"Unable to open this product because a variant is missing" in Webflow Designer

This was a real bug in StoreLingo's publish flow before 2026-06-19: we were copying the source product's default-sku ID into the duplicate, so Webflow Designer couldn't find the duplicate's own SKU. Fixed and the existing duplicates were repaired with a one-time backfill.

If you still see this error on a product after 2026-06-19, contact support - it means a duplicate row was created before the fix and missed the backfill. We can repair it in under a minute.

"Variant is missing" workaround if you can't wait

If you need to open the product in Designer immediately, you can manually fix the default-sku field: open the product in Webflow Designer, change the SKU to its own (the duplicate's SKU should show as the only option), save. The StoreLingo backfill script does this same operation programmatically.

OAuth callback says "identity_lookup_failed"

This means StoreLingo could not read your account info from Webflow. Causes:

  • Your Webflow OAuth app config doesn't include authorized_user:read scope. (Affects your dev-app dashboard config, not our app code - if you're a self-hosted StoreLingo install, fix this in your Webflow Developer Apps settings.)
  • A temporary Webflow API outage.

Fix: visit /auth/webflow/start to re-run the OAuth flow. If the issue persists for more than a few minutes, check the Webflow status page.

Publish job stuck "running"

Open the Jobs panel (sidebar) to see the current state. If a job has been running for more than 5 minutes:

  • Check the Webflow status page - Webflow's Data API has rate limits and rare outages.
  • Check your DeepL quota if you triggered AI translate before publish.
  • Open the StoreLingo support widget; we can inspect the job and rerun the failed steps without losing progress.

The publish flow is idempotent - re-running it always produces the same end state. You can safely retry a stuck job by clicking Publish again.

Translations look wrong

DeepL is high-quality but not perfect for every domain. Click into the product, edit manually, click Approve. Approved translations are never overwritten by future AI runs, and they get cached into your Translation Memory so the same source string propagates the approved version to other items.

For consistent brand language across translations, set up your Glossary before running AI translate. Once a wrong translation is cached in TM, you have to clear it from TM (or overwrite via Approve) to undo it.

Glossary terms are still being translated

Check the term is spelled exactly as it appears in your source text (case-sensitive). Glossary matching uses literal string replacement, not pattern matching. "Acme" in glossary won't protect "ACME" or "acme" - you need separate entries for case variants if your source uses them inconsistently.

I want to delete a duplicate Webflow product

Removing a locale in StoreLingo does NOT delete the duplicate Webflow products it created. Two ways to clean up:

  1. Via Webflow Designer: open your Products collection, find rows with the locale-prefixed slug (e.g., de-blue-mug), delete them in Designer.
  2. Via Orphan Recovery: disconnect and reconnect the site in StoreLingo. The orphans (deleted-locale duplicates with no DB linkage) will appear in the dialog. Choose Delete on each and click Apply.

Path 2 is faster for cleaning up many rows at once.

Connect a new site without losing my existing connection

Click + Connect another site in the sidebar. The SitePicker opens. Pick the new site. Your existing connections are not affected.

OAuth is account-level, so no re-authorization is needed if you've already connected one site on this account.

The chip shows X/Y but I translated everything

X/Y counts source-content fields against your translatable-fields allowlist. If a source product has a value in a field that's in your allowlist but you haven't translated it, the chip counts the product as incomplete.

Three places to investigate:

  1. Open Fields in the toolbar. The allowlist shows every field StoreLingo expects to translate. If a field is checked but the product has source content you haven't filled in the target locale, that's the gap.
  2. Open the product editor. Scroll all the way down. Any field where the target column is empty but the source column has content is the missing translation. Fill it, save.
  3. Click AI translate missing to backfill any remaining empty fields.

Hreflang dialog says "Add a target locale first"

Automatic mode requires at least one non-source locale to have anything to point at. Add a locale (sidebar + Add locale), then re-open the Hreflang dialog. Automatic will unlock.

Cancel and restart on the same Webflow site

Sometimes the cleanest debug step is a full disconnect/reconnect cycle. Two things to know:

  • Disconnect only removes the StoreLingo site row. Your OAuth token stays valid.
  • Reconnect goes straight to the SitePicker (no OAuth prompt). Pick the site. Sync runs.
  • Orphan Recovery auto-prompts if previous translations are still in the site.

Still stuck?

Open a support ticket and a real human replies within one business day on every plan, same-day on Pro and Agency. The form takes your SL-XXX-NNN error code and the screen you were on so we can reproduce immediately. Prefer email? support@storelingo.com works too.