Catalog enrichment
Catalog enrichment is a native Adobe Commerce capability that helps you improve product names and long descriptions so that your catalog is represented more accurately when shoppers use LLMs and AI assistants for product research and discovery.
How it works how-it-works
Your Adobe Commerce product catalog is the system of record for product data: names, descriptions, attributes, pricing, and inventory. Adobe Commerce Storefront MCP (Model Context Protocol) connects live catalog data to Adobe AI experiences. From there, the Catalog Agent uses that interface so Adobe LLM Optimizer can identify gaps in product names and long descriptions, propose improvements, and write approved changes back to Commerce so you can review them in the Commerce Admin.
With catalog enrichment, you can:
- Identify gaps and inconsistencies in product names and long descriptions that affect how LLMs interpret your products.
- Review suggested improvements with supporting context, including justifications and before-and-after comparisons.
- Apply approved updates directly to the Commerce catalog so the Admin, storefront, and other channels that read those fields stay aligned.
Because product names and long descriptions live in Commerce, improving copy once can benefit every channel that consumes that product data. The benefit depends on how and when your systems refresh.
Who this is for who-this-is-for
- Digital marketers and merchandisers who want product data to be accurate and consistent in LLM-driven answers.
- Digital marketers and merchandisers who need a controlled way to improve catalog copy at scale.
- Commerce administrators who own catalog integrity, Admin processes, and integrations (API, CSV, PIM) that feed product attributes.
Prerequisites prerequisites
The following prerequisites apply when you have access to catalog enrichment.
- Your storefront can be crawled by LLM-oriented and agentic bots where crawl coverage is required for catalog-aware suggestions.
- Required Commerce services and catalog connectivity are enabled and healthy. See Enable catalog enrichment to learn more.
- IMS is configured).
- You have access to the Adobe Admin Console.
If you do not have an IMS organization, contact your Adobe account team to provision one.
Enable catalog enrichment enable-catalog-enrichment
Work with your Commerce administrator or implementation partner to ensure the following before you review or apply suggestions:
Install catalog enrichment and catalog services extensions
-
Install the catalog enrichment extension in your Commerce instance by running the following command:
code language-bash composer require magento/module-catalog-enrichment --no-update composer update magento/module-catalog-enrichment -
If you have not already installed Catalog services, do so.
Catalog enrichment is now available in your Commerce instance.
Access catalog enrichment
After you install the catalog enrichment and catalog services extensions, the catalog enrichment capability is available in the Admin under Catalog > Catalog Enrichment.
Configure catalog enrichment
Configure catalog enrichment on the Settings tab so Adobe LLM Optimizer can connect to your Adobe Commerce environment and surface suggestions in the Commerce Admin.
-
In the Admin, go to Catalog > Catalog Enrichment.
-
In the Scope list at the top of the page, select the store view you want to configure, or leave All Store Views to manage settings across store views.
-
Open the Settings tab.
-
In Commerce Configuration, expand the store view panel labeled with its URL.
Provide your Adobe Commerce environment details to enable the Catalog LLM Optimizer Service and audit workflows.
-
Enter the required connection details for the store view.
- Store View URL: URL corresponding to the store view (for example,
https://brand.example.com/fr/). - Environment ID: Unique identifier for the Adobe Commerce environment that the connection accesses.
- Website Code, Store Code, and Store View Code: Website, store, and store view codes for the Commerce website. These values must match the codes in your Commerce Admin.
- Store View URL: URL corresponding to the store view (for example,
-
Optional: Enter Host Name and API Key if your environment requires them.
- Host Name: Host name of your Adobe Commerce instance.
- Adobe Commerce Endpoint: This field is not used.
- API Key: Authentication key used to securely access Adobe Commerce APIs. Click Copy next to the field if you need to copy the key elsewhere.
-
Click Save.
After you save, wait for any initial sync or validation job to complete before relying on catalog or audit results for that store view. It may take up to 24 hours for product suggestions to appear on the Catalog Enrichment page.
To remove a store view configuration, expand that entry and click Delete.
Field descriptions commerce-connection-fields
Required fields are marked with an asterisk (*) on the Commerce Configuration form.
https://brand.example.com/fr/).Review and apply catalog enrichment review-and-apply
After catalog enrichment is enabled and configured, product suggestions display on the Agentic Opportunities tab. From here, you can review suggestions and apply approved updates to product names and long descriptions in your Commerce catalog.
Catalog enrichment uses the following workflow views:
- Current Suggestions: New or active items to review.
- Fixed Suggestions: Items you already applied or resolved.
- Ignored Suggestions: Items you intentionally excluded from action.
Deploy approved suggestions review-deploy-catalog
To deploy approved suggestions:
- Select Current Suggestions.
- Click the expand control for the URL or SKU row to show the proposed product name and product description updates.
- Review the suggestion and confirm it matches your merchandising and SEO strategy.
You can edit a suggestion before you deploy it or move it to Ignored Suggestions if it does not match your strategy.
- Select the row for the URL or SKU to update.
- Click Deploy optimizations and confirm.
Approved name and description changes are saved to your Adobe Commerce catalog like other product updates.
After you apply an update, suggestions move to Fixed Suggestions with a Marked as Fixed status.
Verify enrichment in the Admin verify-in-admin
To verify applied catalog enrichment:
-
Go to Catalog > Products in the Commerce Admin.
-
Use filters and the Store View selector as needed (for example, Default Store View).
-
Search for the SKU.
-
Open the product in edit mode.
The product form shows the enriched product name and/or description.
-
Optional: Select Override LLM Optimizer provided Product Name if you want to keep a manually entered name instead.
Manual overrides affect how suggestions stay in sync with the catalog. For more information, see Manual override in the Admin.
-
Expand the Content section and locate the description field.
The enriched description appears when you applied description changes.
-
Optional: Select Override LLM Optimizer provided Description if you want to keep a manually entered description instead.
Manual overrides affect how suggestions stay in sync with the catalog. For more information, see Manual override in the Admin.
Verify enrichment on the storefront verify-storefront
To verify enrichment on the storefront:
-
Search for the SKU on your storefront.
-
Open the product page.
-
Confirm that the product name and description matches what you approved.
It may take some time before enrichments appear on your storefront.
-
Confirm that regions that show the long description match what you approved.
-
Optional: Confirm downstream channels that consume the same catalog attributes, where relevant to your rollout.
Overrides, ingestion, and outdated suggestions overrides-ingestion
After catalog enrichment updates a product’s name or description, other ingestion systems may change the same fields. Examples include REST API calls, CSV imports, and PIM feeds.
Original value re-ingested original-value-reingested
If an external process writes the original name or description (the value that existed before enrichment was applied), Commerce continues to honor the enriched value for that field according to the catalog enrichment rules. The suggestion may not revert automatically based on that ingestion alone.
New value re-ingested new-value-reingested
If the external process sends a new value that is not a repeat of the pre-enrichment text, Commerce honors the new catalog value. For example, a rename from “Red Shoes” to “Iconic Red Shoes” replaces the enriched value. The related enrichment suggestion is typically marked as Outdated because the live catalog no longer matches the suggestion context.
Manual override in the Admin manual-override-in-the-admin
If you manually edit the product name or description in the Adobe Commerce Admin:
- The Admin value wins as the system of record for that manual change.
- The enrichment suggestion is marked Outdated.
- The suggestion workflow moves back toward the original state for that item so you can re-baseline or accept a new suggestion if analysis runs again.
These rules help you know whether catalog enrichment, ingestion feeds, or Admin edits are authoritative when multiple channels touch the same SKU.
Limits and considerations limits
- Enrichment applies to product names and long descriptions only. It does not change PDP layout, widgets, or other page-level storefront content.
- Large catalogs and high URL counts can affect how quickly analysis completes and how many suggestions appear at once.
- Meaningful suggestions assume that LLM-relevant bots can access the product URLs you care about. Robots rules, authentication, geo-blocking, and heavy personalization can reduce coverage.
Best practices best-practices
- Document system ownership for product name and description so that PIM or feed jobs do not unintentionally conflict with catalog enrichment.
- Coordinate with SEO and brand teams before bulk applying titles or descriptions.
- Re-sync or re-analyze after major catalog imports so that suggestions reflect the current catalog state.