When you set the Variation Axes Target Mode to Standard in your global settings, the connector bypasses the Akeneo custom tables. Instead, it writes your product model variations directly into the native Salesforce Commerce ProductAttribute structure.
Prerequisites
Before activating Standard mode for variations, you must prepare the standard ProductAttribute object to receive your PIM variation fields.
Create Custom Picklist Fields on ProductAttribute
For each variation axis defined in Akeneo (such as color, size, or material), you must manually create a corresponding custom picklist field on the standard Salesforce ProductAttribute object.
- Go to Setup > Object Manager > ProductAttribute
- Create a new field with the Data Type Picklist
Critical Requirement
Under the Picklist Values configuration, you must select Enter values, with each value separated by a new line (Local values). Do not select Use global picklist value set.
Why this matters: Salesforce standard Commerce architecture requires local picklists for attributes. If you use a Global Value Set, the connector's option synchronization will fail, and Salesforce will prevent your variants from rendering properly on the storefront.
Example Configuration:
- Field Label: Size
- Field Name: Size (API Name: Size__c)
- Values Selection: Choose Enter values, with each value separated by a new line. You can simply enter a placeholder value like Default or None to save the field; the connector will dynamically inject your Akeneo values (e.g., Small, Medium, Large) later during the transfer.
Optional: Configure Salesforce Self (For Automatic Option Sync)
By default, the connector will map variant data, but it will not automatically populate or create new picklist options (values) in Salesforce when they are added in Akeneo.
- If you want the connector to automatically update and inject new picklist values inside Salesforce Setup, you must complete the Salesforce Self connection setup (covered in a separate guide)
- If Salesforce Self is not configured, you must manually pre-populate all possible variation options (e.g., Blue, Red, Green) inside the Salesforce picklist settings before running a transfer
Data Cleansing & Existing Records Limitation
Standard Salesforce variation architecture enforces strict rules.
- No Conversion: The connector cannot transform an existing simple standard Product2 record into a Variant Parent or Variant Child record
- If you have already synced variant data into custom tables or created them as simple products, you must clean up or delete those records in Salesforce before initiating your first Standard mode transfer
Configuration & Activation Steps
To activate the standard variation synchronization, follow these two configuration steps:
- Map your Variation Axes: You must register your Akeneo axis codes against your newly created Salesforce picklist fields. Please follow the step-by-step instructions and references detailed in our main guide: App Settings & Advanced Configuration > Configure Variation Axes Mappings.
- Open the Akeneo Connector Configuration (either via the App Homepage or via Salesforce Setup > Custom Metadata Types > Akeneo Connector Configuration > Manage Records)
- Open your main Akeneo Connector Configuration record
- Locate the Variation Axes Target Mode field
- Change the value from Akeneo Custom Objects to Standard
- Click Save
Important Deployment Note
Saving a target-mode change deploys custom metadata asynchronously. Always wait for the metadata deployment to completely finish before attempting to run a data transfer.
Validation Strategy
To verify that your multi-variant catalog is syncing properly in Standard mode:
- Run a test transfer containing a single Product Model and its associated variant products
- In Salesforce, navigate to your Commerce App or the standard Products tab
- Search for the parent product. Verify that the variation attributes are correctly mapped, that options are assigned, and that variant child products are neatly linked under the parent structure via the native Salesforce Commerce interface
