--- title: "Add a new language to the product and its variants" slug: "add-a-new-language-to-the-product-and-its-variants" tags: ["Task"] updated: 2026-08-03T12:17:52Z published: 2026-08-03T12:17:52Z canonical: "docs.staedean.com/add-a-new-language-to-the-product-and-its-variants" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.staedean.com/llms.txt > Use this file to discover all available pages before exploring further. # Add a new language to the product and its variants Use this procedure to add a new language translation to an existing main product and its related variants. The **Translation update strategy** must be set to **On** (Product and variant updates). ## Steps 1. Go to **Organization administration** > **Languages**. 2. Confirm that the new language is enabled in D365 F&SCM. 3. Go to **Engineering change management** > **PLM integration** > **PLM systems**. The **PLM systems** list page opens. 4. Select and open the relevant PLM system. 5. Set **Translation update strategy** to **On** (Product and variant updates). 6. Save the PLM system. 7. Import the existing product from the PLM source with the new language translation. For example, include a Spanish translation for a product that currently has only English and German translations. 8. Go to **Engineering change management** > **PLM integration** > **PLM staging journals**. 9. Locate and open the staging journal created by the import. 10. Select the relevant journal line and open the **Translations** tab. 11. Confirm that the new language code, translated part name, and translated part description are displayed. 12. Click **Post journal**. The system validates the translations and adds the new language to the main product and its related variants. 13. After posting is complete: - The journal status changes to **Posted**. - The new language translation is added. - Existing translations with unchanged values are not updated. - The Infolog displays the processing results. 14. Go to **Product information management** > **Products** > **Released products**. 15. Locate and open the main product. 16. Open the **Translations** form and confirm that the new language was added. 17. Open the product variants for the main product. 18. Select the relevant variant and open its **Translations** form. 19. Confirm that the same language translation was added to the variant. 20. Repeat the verification for any other related variants. > [!NOTE] > Note > > - Existing translations remain unchanged if the imported values are identical to the stored values. > - If the new language code is invalid or not enabled in **Organization administration** > **Languages**, the system skips the translation and records a warning in the Infolog. > - The Infolog identifies the new language translation and confirms that it was added to both the main product and its related variants.