Adobe Adds Catalog Agent for LLM Shopping

Adobe Commerce's Catalog Agent exposes product attributes, variants, compatibility details and relationships that LLM crawlers may miss on JavaScript-heavy storefronts. Adobe documentation says the Product Detail Page workflow serves AI-friendly HTML without changing the shopper experience; a separate beta can generate and publish enriched product names and descriptions. Adobe reported 125% year-over-year growth in AI-sourced US retail traffic for April-June 2026.

Adobe Adds Catalog Agent for LLM Shopping Adobe Commerce's Catalog Agent exposes product attributes, variants, compatibility details and relationships that LLM crawlers may miss on JavaScript-heavy storefronts. Adobe documentation says the Product Detail Page workflow serves AI-friendly HTML without changing the shopper experience; a separate beta can generate and publish enriched product names and descriptions. Adobe reported 125% year-over-year growth in AI-sourced US retail traffic for April-June 2026. Adobe Commerce's Catalog Agent is designed to make product data easier for LLM-powered shopping systems to retrieve. Adobe documentation says the agent compares a merchant's full catalog with what AI crawlers can access on a product detail page, then identifies hidden attributes, variants, compatibility details and product relationships. Coverage from FoneArena, t2ONLINE and CMOtech describes the capability as a response to shopping journeys that begin in conversational assistants rather than conventional search or a merchant storefront. The important distinction is that Adobe documents two related workflows with different effects. Product-page enrichment targets AI crawlers Adobe says many storefronts hide specifications and variants behind JavaScript-rendered tabs, expandable panels, modals and shopping wizards. Human visitors can reveal that material, but an AI crawler may see only a fraction of the product record. The Product Detail Page Enrichment workflow uses Catalog Agent to find those gaps. Adobe's LLM Optimizer can then serve a pre-rendered, AI-friendly HTML snapshot at the CDN edge. The company says this bot-only delivery does not change the Commerce catalog, storefront design, page performance or experience shown to human visitors and SEO crawlers. That approach can improve an assistant's ability to answer compatibility and comparison questions, but it also makes source data quality consequential. Incorrect variants, stale attributes or inconsistent relationships can propagate into an assistant-facing representation even when the visual storefront remains unchanged. Catalog enrichment is a separate beta Adobe also documents Product Catalog Enrichment, a beta for Commerce customers connected to Brand Visibility. This workflow analyzes names, descriptions and value-driving attributes, then proposes more intent-oriented product language. Adobe says users can edit suggestions before applying them. Unlike the bot-only product-page workflow, accepted catalog enrichments are written back to Adobe Commerce and become visible across storefronts and other channels that use the catalog. Adobe says price and inventory are intentionally excluded from the generated description because they change frequently and do not define a product's semantic value. For data and ML teams, keeping those workflows separate matters: one recovers existing catalog facts for AI agents, while the other generates new catalog copy that requires editorial review, rollback and governance. AI-referred retail traffic FoneArena and t2ONLINE cite Adobe Digital Insights data showing traffic from AI sources to US retail sites rose 125% year over year from April through June 2026. Adobe's own traffic materials say its analysis covers more than one trillion visits, but the company has not published an absolute share for assistant referrals in the launch coverage. The percentage therefore signals rapid growth from a small base, not that AI assistants already dominate retail traffic. Still, it explains why catalog lineage, update latency, normalized variants and review of generated language are becoming operational concerns for commerce teams. Key Points - 1Catalog Agent compares Adobe Commerce catalog data with what AI crawlers can access and identifies hidden product attributes and variants. - 2Product Detail Page Enrichment uses bot-only edge delivery, while the separate Catalog Enrichment beta writes reviewed names and descriptions back to the catalog. - 3Catalog lineage, freshness and human review matter because errors can propagate into assistant-facing discovery and recommendations. Scoring Rationale The release is a notable commerce-data tool for LLM-mediated product discovery. Its direct impact is concentrated in ecommerce, but the distinct retrieval and catalog-writing workflows raise broadly relevant data-governance questions. Sources Primary source and supporting public references used for this report. Practice with real Ad Tech data 90 SQL & Python problems · 15 industry datasets Active Search Campaigns by BudgetEasy /problems/sql/active-search-campaigns-by-budget High CPC Clicks & Poor Landing PagesMedium /problems/sql/high-cpc-clicks-poor-landing-page Campaign ROAS by Attribution ModelHard /problems/sql/campaign-roas-by-attribution-model 250 free problems · No credit card See all Ad Tech problems /problems/datasets/adtech