Overview

The Unified AI Configurations feature introduces a centralized location for managing all AI-related attribute configuration settings in Akeneo. This includes prompt-based enrichment, asset generation, and translation customization previously configured at the attribute or family level.

By consolidating AI settings into one dedicated area, users benefit from a streamlined, scalable, and more maintainable configuration experience.

Access the page via:
Settings → AI Configurations

Configuration Structure

The new AI configurations page enables users to define reusable configurations that can be applied via the Rules Engine or manually from the Product Edit Form. These can be for multiple attribute types or specific to one attribute, as defined by you in the configuration.

Each configuration includes:

• General Information
  • A label and code for identification, and the status (enabled/disabled).
• Target & Source
  • Select a specific attribute (or apply to all)
  • Define which attribute values should be used for content generation.
    (Note: This does not apply to translations)
• PX Insights User Reviews (Optional)
  • Automatically includes relevant customer review data if PX Insights is enabled.
    (Contact your CSM for more details)
• Assets (Optional)
  • You can include assets to be considered for your configuration; you can also choose specifically which asset collections to consider. 
• Instruction Prompt
  • Choose a predefined prompt or define your own custom instruction.

Example of AI configuration page

 

 

 

Example Configurations

1. SEO Metadata Generation

Example Configuration:

• Label: SEO Meta Generator
• Code: seo_meta_generator
• Target Attribute: seo_metadescription
• Context Attributes: product_name, short_description
• Assets: Not included
• PX Insights: Enabled
• Prompt:

You are an expert SEO copywriter. Using the selected attributes' values, generate a SEO-optimized meta description that:
• Does not exceed 155 characters (including spaces)
• Naturally incorporates the primary keywords
• Ends with a clear call to action
Return only the meta description text.

2. Data Quality Audit

Example Configuration:

• Label: Data Quality Audit
• Code: data_quality_audit
• Target Attributes: All
• Assets: Included
• PX Insights: Disabled
• Prompt:

You are a PIM data quality specialist. Analyze all attribute values and assets for each product record. Identify:
1. Missing or empty required fields
2. Format inconsistencies (currency mismatches, incorrect date formats)
3. Logical clashes (e.g. weight greater than dimensions)
4. Discrepancies between assets and attribute values
5. Detection of anomalous or outlier values (e.g., values far outside expected ranges, like a product weight in the hundreds of kilograms or a price of $0.01)
For each issue, provide a bullet list item with:
– The attribute or asset name
– A brief description of the problem
– A recommended corrective action

3. Tone-Controlled Translation

Example Configuration:

• Label: Brand Tone Translation
• Code: brand_tone_translation
• Target Attributes: All localizable text fields
• Assets: Not included
• PX Insights: Disabled
• Prompt:

You are a professional translator and brand voice custodian. Translate these fields using a friendly yet professional tone.

Execution Options

1. Manual Execution via Product Edit Form

• Navigate to a product in the grid
• Locate the Ask AI button next to the target attribute
• Select Generate from configuration
• Choose the desired AI configuration
• The generated value will be populated immediately in the interface.

2. Automated Execution via Rules Engine

• Go to Settings → Rules
• Create or edit a rule
• Define product conditions as needed
• Add an action: Generate attribute value with AI
• Select the appropriate AI configuration from the list

Best Practices & Troubleshooting

• Use high-quality, relevant assets for better generation results
• Refine prompts to clarify tone, focus, or format
• Review all AI-generated content before publishing
• Check permissions and feature flags if you can’t access a feature
• If errors occur, try simplifying the prompt or reducing the number/size of assetsSecurity & Data Privacy

Security Overview

Akeneo takes your data security and privacy seriously. All product enrichment, whether generated from attributes, from assets (images, PDFs), or translations, is governed by robust security standards and privacy controls. We use OpenAI Enterprise and Google Gemini Enterprise, ensuring that the data we provide isn't utilized in model training. This data flows exclusively within their servers, returning directly to us without storage or reuse. We share only precise information with OpenAI to ensure that we generate accurate content tailored to your requirements.

AI models used

We are currently using OpenAI's ChatGPT models:

Information shared with our AI provider

For content generation

• Product name: the value of the attribute used as a label
• Locale: the language of the generated content
• Values: the values of the product in the selected attributes to take into account
• Prompt: whether it is a pre-defined Akeneo prompt or your custom one that you have defined 

For content translation

• Source locale
• Target locale
• Value to translate
• Prompt: your custom one that you have defined 

For content rephrasing

• Value to rephrase
• Rephrase type 

Additional Security Measures

• Data is transmitted over secure, encrypted channels.
• No personal data or credentials are ever sent to the AI service unless explicitly included by the user.
• You have full control over which attributes, assets, and prompts are used and shared.
• Feature flags and permissions allow granular control of access and usage per user and per customer.

Compliance & Recommendations

• Always review AI-generated content before publishing for accuracy, compliance with company policy, and regulatory standards. You can use Workflows to do so.
• Do not include confidential or sensitive information in prompts or attribute values unless necessary and reviewed.
• If required, consult your legal or data protection team to ensure usage is in line with your organization’s privacy and data governance policies.

Frequently Asked Questions (FAQ)

1. How can I generate content using both attributes and assets?

You can create a configuration that combines product attributes and assets. When defining the configuration, select the relevant attributes and asset collections. The AI will use both types of data to generate the content.

2. Can I use AI enrichment directly in the Product Edit Form?

Yes. Once a configuration is created and the appropriate permissions are enabled, you can click the "Ask AI" button next to supported attributes in the Product Edit Form and select a configuration to generate content.

3. What are the limits for asset-based enrichment?

• Up to 5 images (20MB each)
• 1 PDF (50MB max, first 20 pages analyzed)
• Supported types: JPG, PNG, WEBP, TIFF, single-frame GIF, and PDF
• Only assets from collections with a "main media" attribute are supported

4. Why are some attributes or actions locked when creating rules?

If you’re seeing locked fields in the Rules Engine, it’s likely that the target attribute hasn’t been enabled for AI enrichment. Go to Settings → Attributes, select the attribute, and enable it under the “Generative AI” tab.

5. Is there a limit to the number of AI configurations I can create?

Yes, each environment supports up to 200 AI configurations. You can reuse and update configurations as needed.

6. What are the limits for select-type attributes used with AI?

When generating values for Simple Select or Multi-Select attributes:

• A maximum of 500 options are supported per attribute
• Any additional options beyond the first 500 will be ignored due to prompt size limitations from the AI provider

7. How long does AI enrichment take to run?

Performance depends on several factors, including:

• Number of products targeted
• Number of AI actions per rule
• Number of locales involved
• As a reference, processing 20,000 products with 5 assets each may take up to 24 hours.

8. Can I still use family-level prompts?

Yes. Existing family-level prompts will still apply during AI generation, even though they are not managed through the new configuration page.

9. Is my data secure when using Akeneo AI features?

Yes. Akeneo uses OpenAI’s Enterprise API and Google Gemini Enterprise to power AI features. Your data is:

• Never used for training
• Not stored after processing
• Not transmitted securely over encrypted channels

10. What information is shared with the AI provider?

We do not send customer-identifying metadata (like your company name) unless explicitly included by you in the prompt.

11. Are there usage limits?

Currently, usage is governed by your billing plan. Akeneo monitors AI usage for cost management and fairness. We will be introducing customer-specific usage limits in the future.

12. How can I write better prompts for AI content?

Effective prompts are key to quality results. Include:

• Key product features
• Target audience
• Tone and voice (e.g., professional, playful)
• Technical specs (if needed)
• Clear formatting or character constraints
• You can test prompts in the Product Edit Form before automating them in a rule.

13. Can AI-generated content be reviewed before it goes live?

Yes. You can manually review content in the Product Edit Form or use Workflows to ensure content accuracy, compliance, and brand consistency before publishing.