Adobe Commerce Optimizer Connector
The Adobe Commerce Optimizer Connector is a native, first-party integration between Adobe Commerce (cloud or on-premises) and Adobe Commerce Optimizer. It synchronizes catalog and pricing data from your Adobe Commerce stores into Adobe Commerce Optimizer so you can:
- Power AI-driven product discovery and recommendations
- Run high-performance headless storefronts (including Commerce storefronts powered by Edge Delivery Services)
- Analyze before and after KPIs and data-sync health in a single place
Adobe Commerce remains your system of record for products, prices, and catalog structure. Adobe Commerce Optimizer becomes your experience and merchandising layer, serving fast, relevant results to any connected storefront or channel.
Key benefits key-benefits
Connector architecture connector-architecture
The following diagram illustrates the end-to-end architecture for the connector, from Adobe Commerce through Adobe Commerce Optimizer and out to storefronts and checkout systems.
In this architecture:
- Adobe Commerce (on cloud or on-premises) is the system of record and feed producer
- The connector exports catalog, price, and category feeds
- Adobe Commerce Optimizer ingests and normalizes the feed data into Catalog Sources, Price Books, and Catalog Views
- Storefronts (Commerce storefront on Edge Delivery Services or custom headless builds) call Adobe Commerce Optimizer GraphQL APIs for discovery and recommendations and call Adobe Commerce or another connected third-party platform for cart and checkout operations
How the connector works with Adobe Commerce how-the-connector-works-with-adobe-commerce
The Adobe Commerce Optimizer Connector operates by using your existing Commerce scopes (websites and store views) and customer segmentation to populate the Adobe Commerce Optimizer catalog model:
- Store view → Catalog Sources — Each store view becomes a separate Catalog Source in Adobe Commerce Optimizer. That source includes localized product attributes and any store-view-specific data
- Website → Price Books — Each Adobe Commerce website maps to one or more Price Books in Adobe Commerce Optimizer. Website pricing and customer group pricing export as price books and price entries
- Customer group → Price variants — Adobe Commerce customer group pricing appears as additional entries in the relevant Price Books
After Adobe Commerce Optimizer ingests the data, you can configure:
- Catalog Views and Policies in Adobe Commerce Optimizer Studio (for building region, brand, or customer-specific subsets)
- Product Discovery (search, facets, merchandising rules)
- Product Recommendations
When you enable the connector, the Adobe Commerce instance remains the system of record for catalog and price data. When you update data in Adobe Commerce, the connector syncs those updates to the Adobe Commerce Optimizer instance.
Typical workflows typical-workflows
These workflows describe how teams set up and use the Adobe Commerce Optimizer Connector. For details on how to set up the integration and enable these workflows, see Get Started.
Initial setup and configuration initial-setup
See Configuration steps in the Get Started guide.
Ongoing data synchronization ongoing-sync
After the initial configuration, the connector supports:
- Full catalog sync for initial migration or large structural changes
- Delta syncs for ongoing updates when products or prices change
- Resync commands for targeted feeds
The following feeds are available for the Adobe Commerce Optimizer Connector:
products- products dataproductAttributes- metadata for product attributespriceBooks- price booksprices- product pricescategories- categories data
For additional details, see the following topics:
- For Adobe Commerce CLI resync operations, see the CLI resync command
- Adobe Commerce Optimizer Connector modules and feed endpoints
- Field mapping for connector feeds
Configure merchandising and storefronts merchandising-storefronts
Once Adobe Commerce data is available in Adobe Commerce Optimizer, use Adobe Commerce Optimizer Studio to connect merchandising and storefront experiences to your synced catalog. Typical next steps include:
- Catalog views and policies — Define region-, brand-, or customer-specific subsets and access rules from the Store setup menu
- Product discovery and recommendations — Configure search, facets, merchandising rules, synonyms, and recommendation units in the Merchandising menu. Search and recommendation behavior is managed in Adobe Commerce Optimizer; Live Search and Product Recommendations settings in the Adobe Commerce Admin no longer apply to these flows
- Storefront connections — Point Commerce storefronts on Edge Delivery Services or third-party headless builds at the correct Adobe Commerce Optimizer tenant, catalog view, and Merchandising API endpoints. For an example third-party integration, see the Salesforce Commerce Connector for Adobe Commerce Optimizer
- Checkout — Keep cart, checkout, order management, and customer accounts on Adobe Commerce or a connected third-party platform. Use App Builder and API Mesh for cart handoff when needed
For step-by-step configuration guidance, see Get Started and the Adobe Commerce Optimizer Merchandising tools.
Supported scenarios supported-scenarios
The connector is designed for B2C merchants with Adobe Commerce on cloud and on-premises deployments who want to adopt Adobe Commerce Optimizer without rebuilding their backend.
Common use cases:
-
Modernizing the storefront only
Keep your existing Adobe Commerce backend, move PLP/Search/PDP to Edge Delivery Services storefronts powered by Adobe Commerce Optimizer -
Scaling catalog and search performance
Offload heavy catalog indexing and search to Adobe Commerce Optimizer’s SaaS services while maintaining product and price ownership in Adobe Commerce -
Incremental SaaS adoption
Use the connector as a stepping stone toward Adobe Commerce as a Cloud Service + Adobe Commerce Optimizer, with a compatible composable Adobe Commerce catalog
Responsibilities and implementation prerequisites responsibilities-prerequisites
Adobe Commerce is the source of truth for products, pricing, and customer groups. Make changes in Adobe Commerce; the connector syncs them to Adobe Commerce Optimizer.
Adobe Commerce Optimizer is responsible for:
- Catalog modeling (Catalog Sources, Price Books, Catalog Views, Policies)
- Product discovery and recommendations
- Storefront metrics, data-sync dashboards, and Success Metrics reports
The connector does not:
- Modify Adobe Commerce cart, checkout, or order flows
- Automatically provision storefront projects (Commerce Storefront / Edge Delivery Services tooling handles that)
Before you begin:
- Verify that Adobe Commerce meets the minimum version and Adobe Commerce Optimizer Connector requirements. See Get Started for details.
- Ensure that you have IMS org access, an Adobe Commerce Optimizer instance, and the necessary credentials and region details.
More help on this topic more-help-on-this-topic
- Set up the integration and enable key workflows: Get Started with the Adobe Commerce Optimizer Connector
- Learn about Adobe Commerce Optimizer concepts and architecture: What is Adobe Commerce Optimizer?
- Understand the sync mechanism, initialization, and error handling: Connector sync pipeline
- Field-level data mapping for all feeds: Field mapping for connector feeds
- Integrate headless storefronts using GraphQL and bundle encoding: Headless storefront integration
- Diagnose sync and configuration issues: Troubleshooting