Installation
Before installing the extension, please make sure to Backup your web directory and store database
You will require to install MageDelight Base Extension first. If it is not installed then please download it from https://www.magedelight.com/pub/extensions/magedelight-base.zip and unzip the package file into the root folder of your Magento 2 installation.
Root Directory is - "app/code/magedelight/#YourExtensionName#"
- Unzip the extension package file into the root folder of your Magento 2 installation.
- Connect to SSH console of your server:
- Navigate to the root folder of your Magento 2 setup
Run command as per below sequence,
php bin/magento setup:upgrade
php bin/magento setup:di:compile
php bin/magento setup:static-content:deploy
php bin/magento cache:clean
- log out from the backend and log in again
If you are using Magento 2.3 or later then you do not need to activate license. Extension will be activated with silent activation mechanism and does not require activation keys to be entered manually.
Backend Configuration (Admin side)
| Field | Description |
|---|---|
| Enable AI Translator | Enables or disables the AI Translation module for the selected store view. Set to Yes to activate all AI translation features. |
| AI Service Provider | Select the AI provider used for translations. Currently supports OpenAI (ChatGPT). The AI model list updates automatically based on the selected provider and API key. |
| OpenAI API Key | Enter your OpenAI API key generated from the OpenAI platform. This key is required to authenticate and use AI translation services. |
| AI Model | Select the AI model to be used for translations. Available options include: • GPT-4.5 (Strongest) – Highest translation accuracy, best for complex, SEO-critical, and brand-sensitive content. • GPT-4.1 (Best for Coding) – Optimized for structured and technical content such as product specifications and attributes. • GPT-4.1 Mini (Fast) – Faster responses with balanced quality and cost, ideal for bulk translations. • GPT-4.1 Nano (Cheapest) – Most cost-effective option, suitable for large catalogs with basic translation needs. • OpenAI o3 (Reasoning) – Enhanced reasoning capabilities, useful for context-heavy or nuanced translations. • OpenAI o3 Pro – Advanced reasoning model offering higher consistency and contextual understanding. • OpenAI o4 Mini – Lightweight model designed for efficient, high-volume translations. • GPT-4o (Multimodal) – Supports advanced contextual understanding and multimodal capabilities, suitable for rich content translations. • GPT-4o Mini (Efficient) – Optimized for speed and cost efficiency while maintaining strong translation quality .• GPT-3.5 Turbo (Legacy) – Legacy model for basic translation use cases and backward compatibility. The available model list dynamically updates based on the selected AI service and API key. |
| Temperature (Creativity) | Controls the randomness and creativity of translations. Lower values (0) produce precise and literal translations, while higher values (up to 2) allow more creative wording. Default recommended value is 0.7. |
| Test Connection | Test the connection between Magento and the AI service using the provided API key and selected model to ensure the configuration is valid. |
| Field | Description |
|---|---|
| Enable AI Translator | Enables or disables the AI Translation module for the selected store view. Set to Yes to activate AI-based translations. |
| AI Service Provider | Select Google Gemini as the AI service provider for translations. The available AI model list updates automatically based on the selected provider and API key. |
| Google Gemini API Key | Enter your Google Gemini API key generated from Google AI Studio. This key is required to authenticate and use Gemini models for translation. |
| AI Model | Select the Google Gemini model to be used for translations. Available options include: • Gemini 2.5 Flash – Fast and efficient model with strong quality, suitable for bulk translations. • Gemini 2.5 Pro – High-quality model with advanced reasoning, ideal for SEO-critical and brand-sensitive content. • Gemini 2.0 Flash – Balanced performance model for general translation use cases. • Gemini 2.0 Flash-Lite – Lightweight and cost-efficient option for large catalogs. • Gemini Flash Latest – Always points to the latest stable Flash model released by Google. • Gemini Flash-Lite Latest – Latest lightweight Flash-Lite model optimized for cost and speed. • Gemini Pro Latest – Latest stable Pro model with the best overall translation quality and context handling. • Gemini 2.5 Flash-Lite – Cost-optimized variant of Gemini 2.5 Flash for high-volume translation workloads. • Gemini 2.0 Flash Experimental – Experimental version with early access to new capabilities (not recommended for production) .• Gemini 2.0 Flash 001 – Fixed version of Gemini 2.0 Flash for consistent and repeatable outputs. • Gemini 2.0 Flash-Lite 001 – Fixed lightweight Flash-Lite version for predictable performance. • Gemini 2.0 Flash-Lite Preview 02-05 – Preview release for testing upcoming Flash -Lite improvements. • Gemini 2.0 Flash-Lite Preview – Early preview model intended for evaluation purposes only. • Gemini Experimental 1206 – Experimental Gemini model with cutting-edge features, recommended only for testing. • Gemini 2.5 Flash Preview Sep 2025 – Preview of upcoming Gemini 2.5 Flash release. • Gemini 2.5 Flash-Lite Preview Sep 2025 – Preview version of the Flash-Lite model for early access testing.The available model list dynamically updates based on the selected AI service and API key. |
| Temperature (Creativity) | Controls the randomness and creativity of translations. Lower values (0) produce more literal translations, while higher values (up to 2) allow more creative phrasing. Default recommended value is 0.7. |
| Test Connection | Tests the connection between Magento and Google Gemini using the provided API key and selected model to ensure the configuration is valid. |
| Field | Description |
|---|---|
| Enable AI Translator | Enables or disables the AI Translation module for the selected store view. Set to Yes to activate AI-powered translations. |
| AI Service Provider | Select Anthropic Claude as the AI service provider for translations. The AI model list updates automatically based on the selected provider and API key. |
| Anthropic Claude API Key | Enter your Anthropic Claude API key generated from the Anthropic Console. This key is required to authenticate and use Claude models. |
| AI Model | Select the Claude model to be used for translations. Available options include: • Claude Sonnet 4 (Latest – Smart & Efficient) – Balanced, intelligent, and optimized for most translation use cases. • Claude Opus 4 (Most Capable) – Most advanced Claude model, recommended for complex, nuanced, and brand-sensitive content. • Claude 3.5 Sonnet – Strong balance between speed and quality, ideal for product descriptions, CMS content, and SEO translations. • Claude 3.5 Haiku (Fast & Efficient) – Lightweight and fastest option, suitable for bulk or short-form translations. • Claude 3 Opus – High reasoning capability within the Claude 3 family, suitable for detailed and context-heavy translations. • Claude 3 Sonnet – General-purpose model offering a balance of performance and accuracy for everyday translation needs. • Claude 3 Haiku – Cost-efficient model for simpler content and large-scale translations. • Claude 2.1 (Legacy) – Older stable release maintained for backward compatibility. • Claude 2.0 (Legacy) – Legacy model with basic capabilities, retained for historical and compatibility purposes. The available model list dynamically updates based on the selected AI service and API key. |
| Temperature (Creativity) | Controls translation creativity and variation. Lower values (0) produce precise and literal translations, while higher values (up to 2) allow more expressive phrasing. Default recommended value is 0.7. |
| Test Connection | Tests the connection between Magento and Anthropic Claude using the provided API key and selected model to ensure the configuration is valid. |
| Field | Description |
|---|---|
| Chat Completions Endpoint | Specifies the API endpoint used for sending translation and content generation requests to OpenAI. By default, this is set to
API gateway, or custom OpenAI-compatible deployment. |
| Models Endpoint | Defines the API endpoint used to fetch the list of available OpenAI models. The default endpoint is
using a self-hosted or enterprise-managed OpenAI-compatible service. |
Leaving these fields empty will automatically use OpenAI’s default endpoints.
Custom endpoints are recommended only for advanced setups, such as:
Corporate proxy servers
Custom API gateways
Private or enterprise OpenAI-compatible deployments
| Field | Description |
|---|---|
| API Endpoint (Base URL) | Defines the base API endpoint used to send translation and content generation requests to Google Gemini. By default, this is set to
model name is automatically appended to this URL when making requests. This field can be customized when using proxy servers or custom Gemini deployments. |
| Models Endpoint | Specifies the endpoint used to retrieve the list of available Google Gemini models. The default value is this endpoint is useful for advanced configurations such as routing requests through a proxy or enterprise-managed API gateway. |
Leave both fields empty to use Google Gemini’s default API endpoints.
Modify these values only if you are:
Using a proxy server
Operating behind a corporate firewall
Running a custom or enterprise Gemini-compatible deployment
| Field | Description |
|---|---|
| Messages Endpoint | Specifies the API endpoint used to send translation and content generation requests to Anthropic Claude. By default, this is set to override this value if you are using a proxy server, API gateway, or custom Anthropic-compatible deployment. |
| Models Endpoint | Defines the endpoint used to retrieve the list of available Claude models. The default endpoint is advanced configurations such as routing requests through a proxy or enterprise-managed API infrastructure. |
Leave both fields empty to use Anthropic Claude’s default API endpoints.
Change these values only if you are:
Using a proxy server
Behind a corporate firewall
Operating a custom or enterprise Claude-compatible deployment
| Field | Description |
|---|---|
| Default Max Tokens | Defines the maximum number of tokens allowed in a single AI response. This setting controls how long and detailed the translated content can be. The default value is 3900, which is suitable for most product descriptions, CMS pages, and SEO content. Increasing this value allows longer translations but may increase API usage and cost. |
Use the default value (3900) for optimal balance between translation quality and cost.
Increase this value only if you are translating very long content such as detailed CMS pages or large product descriptions.
Setting the value too high may result in higher API costs or slower response times.
Backend Functionality
Manage Prompt Templates
- This section allows you to create, manage, and control AI prompt templates used for translating different types of content (products, categories, CMS, etc.) with consistent tone, SEO rules, and brand language.
- Admin Navigation Path: MageDelight → AI Content Translator → Prompt Templates
| Field | Description |
|---|---|
| ID | Unique identifier for the prompt template record. |
| Template Code | System-friendly unique code used internally to identify the prompt template (e.g.,
|
| Template Name | Human-readable name of the prompt template that describes its purpose (e.g., English to Arabic Tone). |
| Content Type | Specifies the attribute or content type this prompt applies to, such as
|
| Entity Type | Defines the Magento entity where this prompt is applied, such as product, category, or CMS page/block. |
| Status | Indicates whether the prompt template is active. Only enabled templates are used during translation. |
| Is Default | Determines whether this prompt template is the default one for the selected entity and content type. Only one default template can exist per combination. |
| Sort Order | Controls the priority of the prompt template. Lower values are processed first when multiple templates are available. |
| Created At | Date and time when the prompt template was created. |
| Updated At | Date and time when the prompt template was last modified. |
| Action | Allows you to edit, enable/disable, or manage the selected prompt template. |
Add New Prompt Templates
| Field | Description |
|---|---|
| Template Code | A unique system identifier for the prompt template. Use only lowercase letters, numbers, and underscores (e.g., be unique. |
| Template Name | A human-readable name describing the purpose of the prompt template, such as English to Arabic Tone. This helps admins easily identify templates. |
| Content Type | Specifies which content attribute this prompt applies to, such as Product Short Description, Product Description, Meta Title, Meta Description, etc. |
| Entity Type | Defines the Magento entity for which this prompt is used. Common values include
|
| Is Active | Enables or disables the prompt template. Only active templates are used during translation. |
| Is Default Template | If enabled, this template becomes the default for the selected entity type + content type combination. Only one default template is allowed per combination. |
| Content Length (Max Tokens) | Sets the maximum number of tokens the AI can generate for this specific content type. This helps control output length and API usage. |
| Sort Order | Determines the priority of the template. Lower values are evaluated first when multiple templates are available. |
- This section defines how the AI should translate content, including tone, rules, and dynamic variables that are replaced automatically at runtime.
| Field | Description |
|---|---|
| Description | Optional helper text or sample content used to quickly test the prompt behavior before saving. This does not affect live translations. |
| Translate | Runs a test translation using the sample content and current prompt configuration to preview the output. |
| Master Prompt | The core instruction sent to the AI model. This defines translation rules, tone, language style, SEO behavior, and how variables are used. The prompt supports dynamic placeholders such as
|
- This popup allows you to translate content on demand using the selected AI service, model, and prompt template.
Click Translate on the product content field.
The AI Content Translator popup opens.
Select the AI Service and AI Model.
Choose the Target Store View.
Select the appropriate Prompt Template.
Review the generated Prompt.
Click Translate to generate and save the translated content.
| Field | Description |
|---|---|
| AI Service | Select the AI provider used for translation (e.g., Google Gemini, OpenAI, Anthropic Claude). This field is mandatory. |
| AI Model | Choose the AI model for translation (e.g., Gemini 2.5 Flash). Click Refresh to reload available models based on the selected service and API key. |
| From | Displays the source language and locale of the content being translated (e.g., English – United States |
| To (Target Store) | Select the target store view where the translated content will be saved. This determines the target language and locale. This field is mandatory. |
| Template | Select the prompt template that defines translation rules, tone, and formatting. The selected template controls how the AI processes the content. |
| Prompt | Shows the final prompt sent to the AI, including dynamically injected variables such as
|
| Variables | Displays the supported variables used in the prompt, such as
|
Translation Review & Approval
- This screen allows administrators to review, edit, approve, re-translate, or reject AI-generated translations before they are published to the target store view.
- Admin Navigation Path:MageDelight → AI Content Translator → Translation Queue → Select Entity → Edit
Go to Translation Queue.
Select the entity and click Edit.
Review Source Text and Translated Text.
Optionally edit the translated content.
Choose one action:
Approve & Publish → Saves translation
Reject → Requires admin notes
Re-translate → Generates a new translation
Translation status updates accordingly.
| Field | Description |
|---|---|
| Status | Current state of the translation. Possible values: Pending (awaiting review), Approved & Published (saved to target store), or Rejected (not published). |
| Entity Name | Name of the entity being translated (e.g., product name). |
| SKU | SKU of the product, if applicable. |
| Entity Type | Type of entity such as Product, Category, or CMS Page/Block. |
| Attribute | Specific attribute being translated (e.g., name, description, short_description). |
| Entity ID | Unique Magento entity identifier. |
| Source Language | Original language and locale of the content (e.g., en_US). |
| Target Language | Target language and locale for the translation (e.g., hi_IN). |
| Source Store | Store view from which the original content was taken. |
| Target Store | Store view where the translated content will be published. |
| AI Service | AI provider used for translation (e.g., Google Gemini, OpenAI, Anthropic Claude). |
| AI Model | AI model used to generate the translation (e.g., gemini-2.5-flash). |
Status determines whether the translation is visible on the storefront.
Translation is published only after approval.
Rejected translations remain in the queue for auditing and re-translation.
Generate Product
AI Content Translator – (Product Name and Description)
- The AI Content Translator is directly available on store-view–scoped product attributes, allowing admins to translate content without leaving the product edit screen.
Go to Catalog → Products.
Open a product (e.g., Erika Running Short).
Switch the Scope to the desired store view (or keep All Store Views for base content).
Locate the attribute you want to translate:
Product Name
Short Description
Description
Click the Translate button next to the attribute.
The AI Content Translator popup opens.
Select:
AI Service
AI Model
Target Store View
Prompt Template
Click Translate.
Review, edit (if needed), and Approve & Publish the translation.
Click Save to store the product changes.
| Field | Description |
|---|---|
| Product Name | Translated and saved per target store view without affecting the base store name. |
| Short Description | Supports rich text translation while preserving formatting and HTML. |
| Description | Supports long-form content, HTML, lists, and Page Builder content. |
Translation works only on store-view–scoped attributes.
Base store content is never overwritten.
Each translation is added to the Translation Queue for review and approval.
Translations can be edited manually before publishing.
AI Content Translator – (Product SEO Meta)
- The AI Content Translator is available for SEO-related, store-view–scoped fields, allowing you to translate metadata while preserving SEO best practices.
Go to Catalog → Products.
Open the desired product.
Scroll to the Search Engine Optimization section.
Switch to the appropriate Store View.
Click Translate next to:
Meta Title
Meta Keywords
Meta Description
The AI Content Translator popup opens.
Select:
AI Service & Model
Target Store View
SEO-optimized Prompt Template
Click Translate.
Review and approve the translation.
Click Save to persist SEO changes.
| Field | AI Behavior |
|---|---|
| Meta Title | Translated with concise phrasing, preserving brand terms and keyword intent. |
| Meta Keywords | Translated as keyword phrases without unnecessary expansion. |
| Meta Description | Optimized to remain within 150–160 characters while preserving search intent and readability. |
- This popup allows administrators to translate SEO metadata using AI while maintaining SEO best practices and store-view isolation.
Click Translate next to the Meta Title field.
The AI Content Translator popup opens.
Select the AI Service and AI Model.
Choose the Target Store View.
Select an SEO prompt template (recommended).
Review or customize the Prompt.
Click Translate.
Review and approve the translation from the Translation Queue.
Click Save on the product page.
| Field | Description |
|---|---|
| AI Service | Select the AI provider used for SEO translation (e.g., OpenAI – ChatGPT). This field is mandatory. |
| AI Model | Choose the AI model for translation (e.g., GPT-4 Turbo). Click Refresh to reload available models based on the selected service and API key. |
| From | Displays the source language and locale (e.g., English – US and read-only. |
| To (Target Store) | Select the store view where the translated Meta Title will be saved. This determines the target language and locale. Mandatory field. |
| Template | Select an SEO-specific prompt template to control tone, length, and keyword usage. |
| Prompt | Displays or allows entry of the final prompt sent to the AI, including variables such as
|
| Variables | Shows the supported variables available for use in the prompt, including
|
Generate Category
AI Content Translator – ( Name and Description)
- The AI Content Translator is available directly on store-view–scoped category fields, enabling quick and consistent translation without leaving the category edit screen.
Go to Catalog → Categories.
Select the category you want to translate (e.g., Gear).
Set the Scope to the appropriate store view.
In the Content section, locate the field to translate:
Category Name
Description
Click the Translate button next to the field.
The AI Content Translator popup opens.
Select:
AI Service
AI Model
Target Store View
Prompt Template
Click Translate.
Review, edit (if required), and Approve & Publish the translation.
Click Save to store the category changes.
| Field | Behavior |
|---|---|
| Category Name | Translated per target store view without affecting the base store category name. |
| Category Description | Supports Page Builder and rich HTML content while preserving structure and formatting. |
AI Content Translator – (Category SEO Meta)
- The AI Content Translator supports SEO metadata translation for categories, enabling localized SEO optimization per store view.
Go to Catalog → Categories.
Select the category you want to translate (e.g., Gear).
Scroll to the Search Engine Optimization section.
Switch to the desired Store View.
Click Translate next to:
Meta Title
Meta Keywords
Meta Description
The AI Content Translator popup opens.
Select:
AI Service
AI Model
Target Store View
SEO-optimized Prompt Template
Click Translate.
Review, edit (if needed), and Approve & Publish the translation.
Click Save to apply SEO changes.
| SEO Field | Description |
|---|---|
| URL Key | Defines the category URL slug. This field is store-view scoped but is not auto-translated to avoid SEO and redirect issues. |
| Meta Title | Category SEO title used by search engines and browsers. Fully supported for AI translation. |
| Meta Keywords | Optional keyword field. Can be translated using AI if required. |
| Meta Description | Category SEO description shown in search results. Fully supported with length awareness. |
- This popup enables administrators to translate category SEO metadata using AI and save it to a specific target store view while maintaining SEO best practices.
| Field | Description |
|---|---|
| AI Service | Select the AI provider used for SEO translation (e.g., Google Gemini). This field is mandatory. |
| AI Model | Choose the AI model for translation (e.g., Gemini 2.5 Flash). Click Refresh to reload models based on the selected service and API key. |
| From | Displays the source language and locale of the category content (e.g., English – US |
| To (Target Store) | Select the store view where the translated Meta Title will be saved. This determines the target language and locale. This field is mandatory. |
| Template | Select a prompt template that defines how the Meta Title should be translated (SEO tone, brevity, keyword handling). |
| Prompt | Displays the final prompt sent to the AI, including dynamic variables such as
|
| Variables | Shows the supported variables available for use in the prompt, including
|
Generate CMS Page
AI Content Translator – ( Name and Description)
- The AI Content Translator is available on CMS page fields, allowing administrators to translate page titles and content into multiple store-view languages directly from the CMS editor.
Go to Content → Pages.
Open the CMS page you want to translate (e.g., Privacy Policy).
Switch the Store View to the desired target language.
Locate the field you want to translate:
Page Title
Content Heading
Main Content
Click the Translate button next to the field.
The AI Content Translator popup opens.
Select:
AI Service (OpenAI, Gemini, Claude)
AI Model
Target Store View
Prompt Template
Click Translate.
Review, edit (if needed), and Approve & Publish the translation from the Translation Queue.
Click Save to apply changes to the CMS page.
| Field | Description |
|---|---|
| Page Title | Translated per store view without affecting the base store page title. |
| Content Heading | Translated independently to match the target language tone. |
| Page Content | Supports long-form text, HTML, and Page Builder content while preserving structure and formatting. |
- Navigate to Content → Pages → Select Page(e.g., Privacy Policy) → Content-> Description -> Edit with Page Builder, then click on the "Translate" button to translate the page content.
- This feature allows administrators to translate full CMS page content created with Page Builder using AI, while preserving layout, blocks, and HTML structure.
- Admin Navigation Path: Content → Pages → Select Page (e.g., Privacy Policy) → Content → Description → Edit with Page Builder → Translate
| Field | Description |
|---|---|
| AI Service | Select the AI provider used for translation (e.g., OpenAI – ChatGPT). This field is mandatory. |
| AI Model | Choose the AI model for content translation (e.g., GPT-4 Turbo). Click Refresh to reload available models. |
| From | Displays the source language and locale of the CMS content (e.g., English – United States |
| To (Target Store) | Select the store view where the translated CMS content will be saved. Determines the target language and locale. Mandatory field. |
| Template | Select a prompt template that defines translation tone, legal accuracy, formatting rules, and structure preservation. |
| Prompt | Displays or allows entry of the final prompt sent to the AI, including variables such as
|
| Variables | Shows supported variables including
|
AI Content Translator – (Page SEO Meta)
- The AI Content Translator supports SEO metadata translation for CMS pages, enabling localized SEO optimization per store view while keeping URLs and compliance intact.
| SEO Field | Description |
|---|---|
| URL Key | Defines the CMS page URL slug. This field is not auto-translated to prevent broken links and unintended redirects. |
| Meta Title | SEO title displayed in browser tabs and search engine results. Fully supported for AI translation. |
| Meta Keywords | Optional SEO keywords field. Can be translated using AI if required. |
| Meta Description | SEO description shown in search results. Fully supported with SEO-friendly length awareness. |
Bulk Content Translation (Single Attribute)
- This feature allows administrators to translate a single attribute (e.g., Product Short Description) for multiple products in bulk using AI, with full control over store views, batching, and overwrite behavior.
Navigate to
MageDelight → AI Content Translator → Bulk Content Translation (Single Attribute).Select a Translation Prompt Template.
Choose the Attribute to Translate (e.g., Product Short Description).
Select the Source Store View.
Select the Target Store View.
Configure:
Skip Empty Attributes (optional)
Overwrite Existing Translations (optional)
Batch Size
Choose Product Selection Method → CSV Upload.
Upload the CSV file containing product SKUs.
Click Start Bulk Translation.
Translations are processed in batches and added to the Translation Queue for review.
| Field | Description |
|---|---|
| Translation Prompt Template | Select the prompt template that defines translation tone, language rules, SEO behavior, and brand terminology (e.g., English to Arabic Tone). |
| Attribute to Translate | Choose the product attribute to be translated (e.g., Product Short Description, Description, Meta Title). |
| Source Store View | Store view from which the original content will be taken (typically Default Store View). |
| Target Store View | Store view where the translated content will be saved (e.g., Arabic Store View). |
| Skip Empty Attributes | When enabled, products with empty source attributes are skipped during translation. |
| Overwrite Existing Translations | When enabled, existing translations in the target store view will be replaced with new AI-generated content. |
| Batch Size | Number of products translated per batch (1–50). Smaller batch sizes provide better stability and error handling. |
| Product Selection Method | Defines how products are selected for translation. Supported method: CSV Upload. |
| CSV File | Upload a CSV file containing product SKUs. The first column must contain SKUs. |
| Download Sample CSV | Download a sample CSV file to follow the correct SKU format. |
| Maximum File Size | Maximum allowed CSV file size is 5 MB. |
All translations are processed in controlled batches.
Translated content is added to the Translation Queue for review and approval.
Base store content is never overwritten unless explicitly configured.
Bulk translation does not auto-publish content.
Bulk Content Translation (Multi Attribute)
- This feature allows administrators to translate multiple attributes at once for multiple products using AI. It is ideal when rolling out new languages across large catalogs, ensuring consistency across all translated attributes.
Navigate to
MageDelight → AI Content Translator → Bulk Content Translation (Multi Attribute).Select a Translation Prompt Template.
Choose the Source Store View.
Choose the Target Store View.
Configure optional settings:
Skip Empty Attributes
Overwrite Existing Translations
Set an appropriate Batch Size.
Select Product Selection Method → CSV Upload.
Upload the CSV file containing product SKUs.
Click Start Bulk Translation.
Translations are processed and added to the Translation Queue for review.
| Field | Description |
|---|---|
| Translation Prompt Template | Select the prompt template that defines tone, language rules, SEO behavior, and brand terminology (e.g., English to Arabic Tone). |
| Attribute to Translate | Choose the product attribute to translate (e.g., Product Short Description). |
| Source Store View | Store view from which the original content will be taken (usually Default Store View). |
| Target Store View | Store view where the translated content will be saved (e.g., Arabic Store View). |
| Skip Empty Attributes | If enabled, products with empty source attributes will be skipped. |
| Overwrite Existing Translations | If enabled, existing content in the target store view will be replaced. |
| Batch Size | Number of products translated per batch (range: 1–50). Smaller batches are more stable. |
| Product Selection Method | Method used to select products for translation (e.g., CSV Upload). |
Multi-attribute bulk translations do not auto-publish.
Admin approval is mandatory before content appears on the storefront.
Translation cost depends on the number of attributes, products, and AI model used.
Partial failures do not block other batches.
Frontend Functionality
Default Store View Translation
- The product image shown belongs to the Default Store View, where the store language is set to English. Since this is the base store view, no translation is applied to the product content or image-related text.
- The AI Content Translator module works only on store-view–specific content. Translation actions are enabled only when a non-default (target) store view is selected. This ensures that:
The Default Store View always remains in English
Original product content is never overwritten
Translated content is saved only in the selected target language store view
Each store view displays content according to its configured locale
When viewing the product under the Default Store View, the image and associated product information are displayed exactly as originally created in English. Translation functionality becomes available only after switching to another store view (for example, Arabic, French, or Spanish)
French Store View Translation
- In this example, the product page is displayed under the French Store View, which is a non-default store view. When a target store view is selected, the AI Content Translator automatically displays the translated product content for that specific language.
The product name, description, and UI labels are shown in French, based on the selected store view locale
The original English content from the Default Store View remains unchanged
Translated content is stored store-view–wise, ensuring language isolation
Product images remain the same, while textual content adapts to the selected language
Each store view independently serves content according to its configured language and currency
This behavior ensures that customers browsing the French Store View experience a fully localized product page, while administrators retain full control over translations without affecting the base (English) content.
Arabic Store View Translation
- In this example, the product page is displayed under the Arabic Store View, which is a non-default store view configured with a right-to-left (RTL) language.
- When the Arabic Store View is selected:
The product name and description are translated into Arabic using the AI Content Translator
Content is rendered in RTL format, matching Arabic reading direction
The original English content from the Default Store View remains untouched
Translations are saved only for the Arabic store view, ensuring language isolation
Product images remain unchanged while text content adapts to the selected language
Pricing, stock status, and SKU remain consistent across store views
- This functionality enables merchants to deliver a fully localized Arabic shopping experience without duplicating products or affecting the base store content.
German Store View Translation
- In this example, the product page is displayed under the German Store View, which is a non-default store view.
- When the German Store View is selected:
The product name and description are translated into German using the AI Content Translator
The Default Store View (English) content remains unchanged
Translated content is stored specifically for the German store view
Product images remain the same, while textual content is localized
Pricing, stock status, and SKU remain consistent across all store views
- This ensures that German-speaking customers see a fully localized product page, while administrators can manage translations independently for each store view without duplicating products or overwriting base content.
Hindi Store View Translation
- In this example, the product page is displayed under the Hindi Store View, which is a non-default store view.
- When the Hindi Store View is selected:
The product name and description are translated into Hindi using the AI Content Translator
The Default Store View (English) content remains unchanged
Translated content is stored specifically for the Hindi store view
Product images remain the same, while textual content is localized in Hindi
Pricing, stock status, SKU, and cart functionality remain consistent across all store views
- This ensures Hindi-speaking customers receive a fully localized shopping experience, while administrators can manage translations independently per store view without duplicating products or affecting the base (English) content.
Gujarati Store View Translation
- In this example, the product page is displayed under the Gujarati Store View, which is a non-default store view.
- When the Gujarati Store View is selected:
The product name and description are translated into Gujarati using the AI Content Translator
The Default Store View (English) content remains unchanged
Translated content is stored exclusively for the Gujarati store view
Product images remain unchanged while textual content is localized in Gujarati
Pricing, stock status, SKU, and cart functionality remain consistent across all store views
- This functionality allows merchants to serve regional language content while maintaining a single product catalog and complete control over translations at the store-view level.
Thank you for choosing MageDelight!





























