{"section":"known-issues","requestedLocale":"en","requestedSlug":"complementname-in-productcontext-is-not-translated","locale":"en","slug":"complementname-in-productcontext-is-not-translated","path":"docs/en/known-issues/Store Framework/complementname-in-productcontext-is-not-translated.md","branch":"main","content":"## Summary\n\n\nSince the Catalog Search Documents Translation API does not translate the field for short description called complementName the product context shows the original text in Internationalized stores.\n\n\n##\n\n## Simulation\n\n\n\n- Translate a short description (complementName) in an Internationalized store. It can be either through Messages or Catalog Translation app.\n- Check the productContext for that product in a different language using React Dev Tools or querying the productContext.\n- You'll see that its value is not translated.\n\n- You can check that the catalog API does not bring this value translated: `curl --location 'http://api.vtexinternal.com/api/search-documents/documents/translations/?an=&decompress=true' \\`\n\n\n\n##\n\n## Workaround\n\n\nNone VTEX native app uses this field. But if your are using in a Custom app you can create a new SKU or Product specification to use as the complementName or query the translation in your custom app."}