{"section":"known-issues","requestedLocale":"en","requestedSlug":"translation-issues-when-using-a-subaccount-to-implement-multilanguage-stores","locale":"en","slug":"translation-issues-when-using-a-subaccount-to-implement-multilanguage-stores","path":"docs/en/known-issues/Intelligent Search/translation-issues-when-using-a-subaccount-to-implement-multilanguage-stores.md","branch":"main","content":"## Summary\n\n\nCatalog Unified Indexing considers the messages' translations only from the main account, even when using a subaccount architecture to implement cross-border stores.\n\nThis leads to a different translation in the search and product page, as the content from the search page is based only on the translations retrieved by the Catalog Indexer.\n\n\n##\n\n## Simulation\n\n\n\n- Create a subaccount and implement cross-border stores;\n- Translate the catalog content in the subaccount;\n- Compare the search and product page; they will have different translations.\n\n\n##\n\n## Workaround\n\n\nSet the additional languages (bindings and Messages content) in the main account, replicating the translations from the subaccount also in the main account."}