Localization (Universal Editor)

Learn to localize your Commerce storefront using AEM Sites authoring with Universal Editor. For the complete AEM translation workflow, refer to the official Adobe documentation linked below. For Commerce-specific tasks, see Commerce localization tasks.

Choosing your authoring approach

Two approaches for authoring with Edge Delivery Services:

• AEM Sites Authoring (this guide): Content authored in AEM as a Cloud Service, published to Edge Delivery Services. Supports AEM Translation Projects and Multi-Site Management (MSM) features.

• Document Authoring: Content authored on da.live. See Localization (Document Authoring Tool) for the da.live Translation app workflow.

Prerequisites

• You have access to AEM as a Cloud Service with Universal Editor enabled.
• Your storefront project is configured to use AEM Sites as the content source for Edge Delivery Services.
• Path mapping is configured between AEM content paths and Edge Delivery Services URLs.
• You have the necessary permissions to create translation projects in AEM as a Cloud Service.
• You know the basics of using the Universal Editor ( Universal Editor authoring ).
• You have completed the multistore setup to create the folder structure for localized content.

Workflow overview

Localizing a Commerce storefront with AEM Sites authoring involves:

1. Complete the multistore setup: Set up the folder structure, store views, and configuration (see multistore setup).
2. Follow the AEM translation workflow: Create language copies, translation projects, and publish (see the Adobe documentation below).
3. Complete the Commerce-specific tasks: Translate placeholder files, verify store views, and test Commerce functionality (see Commerce localization tasks).

AEM translation workflow

For the complete AEM translation workflow, follow the official Adobe documentation:

1. Set up language copies and translation projects:

   • AEM as a Cloud Service Translation and Localization
   • Multi-Site Manager and Translation

2. Review translations using Universal Editor:

   • Universal Editor authoring

3. Publish to Edge Delivery Services:

   • Publishing from AEM Authoring to Edge Delivery Services

4. Configure path mapping:

   • Path Mapping Configuration

Choosing between AEM Sites and Document Authoring

Both approaches work with Commerce storefronts, but they differ significantly:

Feature	AEM Sites Authoring (this guide)	Document Authoring (da.live)
Translation Services	Microsoft Translator, Google Cloud Translation, custom enterprise connectors	Google Translate by default, other services configurable
Workflow Management	Full AEM Translation Projects with MSM, language copies, approval workflows	Simple Translation app (Traverse + Translate)
Setup Complexity	Requires AEM as a Cloud Service infrastructure	Simpler setup on da.live
Authoring Style	Component-based pages in AEM Sites console or Universal Editor	Document-based (like Word/Docs)
Best For	Enterprise localization with professional translation services, complex workflows	Quick localization with basic translation needs

See also: Localization (Document Authoring Tool) for the da.live workflow.

Both approaches handle Commerce-specific requirements (placeholder files, store views, multistore configuration) the same way. The main difference is the authoring and translation management system.

Next steps

After completing the AEM translation workflow:

1. Complete Commerce tasks: Follow the Commerce localization tasks guide to translate placeholder files, verify store view configuration, and test Commerce functionality.

2. Review best practices: See Commerce-specific best practices in the Commerce localization tasks guide.

3. Troubleshooting: For Commerce-specific issues (product data, drop-in labels, store views), refer to the troubleshooting section in Commerce localization tasks.

For AEM translation workflow issues, refer to AEM Translation Troubleshooting or contact Adobe Support.