When the Akeneo App runs in Standard Objects Mode, product information is written directly into native Salesforce Commerce objects instead of the app's custom objects
This guide explains how a Salesforce administrator can display this native data - Variations, Translations, Media, and Categories - on the Product2 record page using native Salesforce components and fields
Architectural Note
The app does not ship, activate, or modify any Product2 Lightning record pages or classic page layouts
Domain Mapping Quick Reference
The following table summarizes which standard objects hold your Akeneo data and the native components required to render them
| Domain | Native Salesforce Object | Native Record Page View / Component |
|---|---|---|
| Variations | ProductAttribute, ProductAttributeSet | Variants list and Product Variations components |
| Translations | Product2DataTranslation | Native Translations component, or Data Translation in Setup |
| Media | ProductMedia, CMS ManagedContent | Product List Image (PLP) and Product Detail Images (PDP) |
| Categories | ProductCategoryProduct | Categories related list on the Related tab |
Before You Start
When the Akeneo App runs in Standard Mode, product information is written directly into native Salesforce Commerce objects instead of the app's custom tables. Before modifying your product page layouts in the Lightning App Builder, you must ensure that your system environment and data domains are fully ready:
- Verify the Domain Configuration: Ensure your app target modes are explicitly set to Standard. For detailed, step-by-step guidance on how to verify these properties in your Custom Metadata Types, please see our dedicated Post-Installation Configuration Guide.
- Verify Native Feature Prerequisites: Standard Mode relies entirely on your organization's core Salesforce licensing, CMS setups, and workbench activations. Before making these components visible, make sure you have fully satisfied all the mandatory environment checks detailed in our Standard Objects Requirements Section.
Structural Warning
The packaged components shipped with the app (such as Product Media Gallery and Product Variants List) only read legacy custom objects and will remain empty in Standard Mode. Always use the native Salesforce Commerce components detailed in the sections below.
Product Assets Visibility
In Standard mode, the app publishes each eligible asset to your configured Salesforce CMS Workspace, automatically creating a ManagedContent record. It then links it to the product with a native ProductMedia record placed within specific ElectronicMediaGroup buckets.
To add these components to your product page layout:
- Go to Setup ➔ Object Manager ➔ Product2 ➔ Lightning Record Pages and open your active page
- In the Lightning App Builder components palette, search for the native Commerce media components
- Drag and drop Product List Image and Product Detail Images onto your layout
- Click Save and Activate
Once activated, these components render synchronized images and videos directly on the record page. The app can link up to 2 PLP records (Product List Image bucket) and up to 8 PDP records (Product Detail Images bucket) per product.

Product Translations Visibility
In Standard mode, the connector writes localized field values directly into your organization's standard Salesforce Product2DataTranslation object. At runtime, the app automatically maps and resolves these localized values, aligning completely with the native Salesforce data translation framework.
To add this component to your product page layout:
- Go to Setup ➔ Object Manager ➔ Product2 ➔ Lightning Record Pages and open your active page
- In the Lightning App Builder components palette, search for Translations
- Drag and drop the component onto your page layout (preferably within a dedicated "Translations" tab or section)
- Click Save and Activate
Once activated, the component dynamically renders a structured grid listing every synchronized language (for example, English, French, and German). For each language row, users can directly view the translated values for standard fields like Product Name and Product Description, alongside a native Add Translation action button for manual overrides.

Product Models and Variations Visibility
In Standard mode, the app adapts to the native Salesforce Commerce variant architecture. It links the parent (model) Product2 record to a standard ProductAttributeSet and automatically creates a native ProductAttribute record for each child variant, mapping the axis values (for example, Shirt Size).
To add this component to your product page layout:
- Go to Setup ➔ Object Manager ➔ Product2 ➔ Lightning Record Pages and open your active page
- In the Lightning App Builder components palette, search for Product Variation
- Drag and drop the component onto your page layout
- Click Save and Activate
Once activated, the component dynamically adapts to the product type. On a variation parent, the page automatically renders a native Variants list grid and a Product Variations grid (the variation attribute set, e.g., Akeneo_Shirt_Size). On a variant child, the component dynamically displays its assigned axis values and provides a link back to its parent product.

Product Categories Assignments Visibility
In Standard mode, the app creates a standard ProductCatalog, a ProductCategory hierarchy, and automatically links each assignment with a native ProductCategoryProduct record.
To add this component to your product page layout:
- Go to Setup ➔ Object Manager ➔ Product2 ➔ Lightning Record Pages and open your active page
- In the Lightning App Builder components palette, look at the product's Related tab layout
- Ensure the native Categories related list component is positioned within your tab view
- Click Save and Activate
Once activated, category assignments are automatically displayed via the native Categories list grid. The page will render the exact synchronized catalog tree path alongside columns such as Category and Is Primary Category. The app completely controls the catalog, category structure, and sorting order from the PIM.
