You’re probably hitting two separate issues here, and I wouldn’t keep adding translation keys to Theme Content yet.
The fact that some filter labels are English while others are Russian usually means those strings aren’t all being pulled from the same translation source.
If this is the standard Shopify collection filters, I’d check it in this order:
Confirm the store’s primary/default language is actually Estonian and that Estonian is the published storefront language.
Check Settings → Languages and look at the Estonian translations, rather than relying only on the Theme Content editor.
If the filters are coming from Shopify Search & Discovery, check the filter configuration itself and determine whether the label is coming from the filter definition or the theme.
Inspect the theme’s locales files. Shopify themes use these JSON locale files for storefront strings, and the active language is selected through the translation keys referenced by the theme.
Most importantly, don’t try to solve the translation-key limit by creating hundreds of additional theme keys. Shopify currently has a 3,400-translation limit for a single locale file, so if you’re already hitting that, the better solution is to identify the source of the problematic strings and fix those specifically.
The Russian part is the biggest clue for me.
I’d inspect the actual filter markup and check which translation key/component is generating those particular words. If they’re hardcoded by the theme or coming from an app/extension, changing Theme Content won’t reliably fix them.
If you can share the theme name + the exact filter labels that are showing in English/Russian, I can point you to where I’d look first and whether this can be fixed without adding more translation keys.
Two different things are going on in that filter box, and they come from two different places.
“Доступность” and “Цена” are your filter names
They are set in Russian in the Search & Discovery app, not in the theme. Theme content can’t change them.
“Translation missing: et…” is theme text with no Estonian
Horizon doesn’t include an Estonian language file. So every theme string you haven’t translated yet shows “Translation missing” (that price one is the “separator” string). Doing them one at a time is what makes it feel endless.
You won’t hit the 3,400 limit doing this. That cap is per language, and Horizon’s theme text is only a few hundred strings.
If you add more languages later, apps like Weglot or Langify handle bulk translation.
Regards,
Ploqo,
Pinflow - Pinterest Virtual Assistant
Hi @xsanxdrox
The issue doesn’t appear to be only with the Theme Content translations. From the screenshot, some text is showing in English/Russian, such as “Translation missing:” and et.fields.separator, while other labels are correctly translated into Estonian.
This usually means that some of the filter text is being generated through translation keys or dynamic app content, rather than the normal Shopify theme translations.
I would check these areas:
et.fields.separator — this looks like a translation key being displayed instead of its translated value, which indicates that the translation lookup is failing.If you send me the filter app name and the relevant Liquid/JS code, I can check exactly where Translation missing: and et.fields.separator are coming from and suggest the cleanest way to make everything display in Estonian.
Best regards,
Devcoder 
If you dont see that button, just manually change set separator to “kuni”.
Steps
Refresh your store. The “Translation missing” text is gone and the filter now reads 0 kuni 39,99.
Notes
Any other filter or button still stuck in English has its own empty Estonian box under Default theme content. Fill those the same way.
Regards,
Ploqo,
Pinflow - Pinterest Virtual Assistant
“Translation missing: et.fields.separator”
this kind of translation is not available in shopify
here is the way to fix it
online store → go to the code of your active store —>Locales section —>open the language file that corresponds to the Estonian (et) language.
then find fields key, there must be a missing key
"fields": {
"separator": "–"
}
Save the file and check whether the “Translation missing: et.fields.separator” message is not visible.
