Troubleshooting scenarios for the Adobe Commerce Optimizer Connector
This page describes behaviors you may observe when working with the Adobe Commerce Optimizer Connector that are typically caused by misconfiguration or misinterpretation of sync results. Use the descriptions below to identify the root cause and apply the appropriate resolution.
Feed status shows “Success” but data is not visible in Adobe Commerce Optimizer
Issue: The Data Feed Sync Status page reports a successful sync, but products, prices, etc. are not appearing as expected in Adobe Commerce Optimizer.
Cause: A successful feed status means the data was accepted by the ingestion endpoint, not that it has finished propagating through Adobe Commerce Optimizer. Propagation can take several minutes after ingestion.
Solution:
- Wait a few minutes and refresh the Adobe Commerce Optimizer view.
- Confirm that the tenant ID configured in Adobe Commerce matches the Commerce Optimizer environment you are checking.
- Verify that the correct catalog source (store view code) or price book is selected in Commerce Optimizer.
Products are missing from the exported catalog
Issue: Some products do not appear in Adobe Commerce Optimizer after a full catalog sync.
Cause: If products fail validation during export they are omitted from sync. Products that are disabled or not visible in catalog will not be returned by the products API.
Solution:
- Confirm that the affected products are assigned to the website and store view used as the catalog source.
- Check that the products are enabled and set to a visibility that includes catalog listings.
- Review per-item error details for the catalog feed in System > Data Transfer > Data Feed Sync Status.
Prices are incorrect or missing in Adobe Commerce Optimizer
Issue: Products appear in Adobe Commerce Optimizer but display no price returned with products GraphQL query, or the price does not match what is configured in Adobe Commerce.
Cause: The price book feed uses a scope that maps to a specific website and customer group. A wrong catalog view configuration can lead to missing or incorrect prices.
Solution:
- Verify that the website is configured for sync in the connector’s export configuration. See Customize the data export configuration.
- Confirm that the price book ID used in Commerce Optimizer is present in the catalog view configuration used to perform the products query.
Data in Adobe Commerce Optimizer is overwritten or unexpectedly modified after sync
Issue: Data changes applied directly in Adobe Commerce Optimizer by an external system (such as a PIM or ERP) are lost or reverted after the connector runs a sync.
Cause: When systems other than Adobe Commerce write directly to Adobe Commerce Optimizer—for example, a PIM or another external system—data conflicts can occur. The connector syncs data one way, from Adobe Commerce to Adobe Commerce Optimizer, and does not sync changes back to Adobe Commerce. As a result, data written directly to Adobe Commerce Optimizer is not reflected in Adobe Commerce and can be overwritten during a later sync.
Solution:
Instead of writing catalog modifications directly to Adobe Commerce Optimizer, use catalog layers to apply changes outside of Adobe Commerce. Catalog layers let external systems enrich or override catalog data within Adobe Commerce Optimizer without conflicting with the connector sync.
Troubleshooting scenarios for common SaaS Data Export issues
For issues related to the underlying SaaS Data Export that may affect the connector, see Troubleshooting scenarios for SaaS Data Export.