Adobe Commerce Optimizer Explained: What It Is and Who Needs It

Adobe Commerce Optimizer is a SaaS product from Adobe for the customer-facing side of commerce: catalog, product discovery, merchandising and a fast storefront. Adobe describes it as a solution "for improving storefront, catalog, product discovery, and merchandising experiences". It does not replace your commerce backend. You keep your existing system for cart, checkout and orders, which can be Adobe Commerce or a third-party platform, and Optimizer powers what shoppers see on an Edge Delivery Services storefront.

This guide explains what Optimizer includes, how it differs from classic Adobe Commerce and the Cloud Service, who it fits and who it does not, and what to confirm with Adobe before you plan around it.

Where Optimizer sits in Adobe's lineup

Adobe now offers two SaaS products: Adobe Commerce as a Cloud Service (ACCS), a full commerce platform run by Adobe, and Adobe Commerce Optimizer (ACO), an experience layer that can sit on top of a backend you already have. The long-standing self-hosted and cloud infrastructure (PaaS) editions continue alongside them. If you need the full map of editions first, read what Adobe Commerce (Magento) is.

What Optimizer includes

According to Adobe's Optimizer documentation (checked November 2026), the main components are:

• Merchandising Services: a SaaS catalog component built on catalog views and policies. Catalog views define which products, prices and locales a storefront or channel sees. Policies are data access filters inside those views, for example limiting a B2B customer group to certain brands.
• Product Discovery: search, facets, search rules and synonyms.
• Recommendations: AI and machine learning product recommendations.
• Commerce Storefront on Edge Delivery Services: product listing, product detail, cart and checkout pages built from Adobe's drop-in components, with content authored in documents. Adobe's storefront documentation states that an Optimizer licence includes the Storefront.
• Data Sync monitoring: visibility of how catalog data is flowing in.

How catalog data gets in

• From any backend: a REST Data Ingestion API adds and manages product and pricing data, directly or from third-party systems. The storefront reads it through a read-only GraphQL Merchandising API, scoped by catalog view, policy, locale and price book.
• From Adobe Commerce PaaS: the Adobe Commerce Optimizer Connector syncs catalog and pricing from Adobe Commerce on cloud infrastructure or on-premises. Store views map to catalog sources and websites map to price books.

Cart and checkout still need a transactional platform. If that platform is not Adobe Commerce, Adobe points to API Mesh and App Builder to connect it.

Optimizer vs classic Adobe Commerce vs the Cloud Service

Our explainer on Adobe Commerce as a Cloud Service covers the SaaS platform in more depth.

Optimizer with an existing Adobe Commerce store

This is the combination many current merchants ask about. Adobe's storefront documentation (checked November 2026) says a PaaS licence alone does not include the Edge Delivery drop-in components; they need an added Optimizer licence. Licensing can change, so confirm it with Adobe. A PaaS store using this path installs:

• the Storefront Compatibility package, which extends GraphQL for cart, checkout, account and order operations, and
• the Adobe Commerce Optimizer Connector, which syncs catalog and prices into Merchandising Services.

An optional bridge can share cart and sign-in sessions between existing Luma pages and new Edge Delivery pages, which allows a gradual move. Adobe also notes that Magento Open Source is not supported for this storefront path.

Adobe's platform and services overview also states (as of November 2026) that Optimizer capabilities replace the separate Catalog Service, Live Search and Product Recommendations extensions for projects that adopt it. Check how that affects any search or recommendation setup you have today.

Fit criteria: who needs Optimizer

Optimizer is a strong candidate when several of these are true:

• You want to keep your commerce backend, whether Adobe Commerce or another system, but your storefront is slow, dated or expensive to change.
• A third-party system already owns cart and checkout, and you need a better browsing and discovery layer in front of it.
• You sell through many catalog variations: brands, regions, dealers or B2B customer groups that each need a different slice of the catalog and prices. Catalog views and policies are designed for this.
• Merchandisers need more control over search, rules and recommendations without developer tickets.
• You already use Adobe Experience Manager or Edge Delivery Services and want commerce in the same delivery model.

Who probably does not need it

• A single-brand store on Adobe Commerce with a fast Hyvä storefront and a working search setup.
• Merchants on Magento Open Source, since this storefront path is not supported for Open Source.
• Teams without front-end JavaScript skills or a partner to build Edge Delivery blocks and drop-ins.
• Stores whose main problems are backend: slow integrations, order processing or data quality. Optimizer does not fix those.

How Optimizer relates to composable commerce

Optimizer is Adobe's own step toward a composable architecture: a replaceable experience layer, fed by APIs, in front of whichever backend handles transactions. It gives you some composable benefits, such as an independent storefront and catalog service, without assembling every piece from different vendors. Our guide to composable commerce explains the wider trade-offs, including the integration work any multi-system setup brings.

Questions to confirm with Adobe

Availability, packaging and licensing are moving quickly. Before planning around Optimizer, confirm in writing:

1. Which Optimizer licence and limits apply to your catalog size, catalog views and traffic (Adobe publishes a boundaries and limits page).
2. Whether your current Adobe Commerce licence includes any Optimizer entitlement, or it is an added purchase.
3. Which drop-in components you need (B2C and B2B drop-ins exist) and whether they cover your checkout and account flows.
4. How your existing search, recommendations and Catalog Service setup will change.
5. For non-Adobe backends, how cart and checkout will connect and who supports that integration.
6. Regional and data residency options for your markets.

What an Optimizer project usually involves

1. Catalog design: define catalog views, policies, locales and price books.
2. Data ingestion: install the connector (Adobe Commerce) or build ingestion from your backend through the API.
3. Storefront build: set up Edge Delivery Services, configure drop-ins and build custom blocks.
4. Transaction integration: connect cart, checkout and accounts to your backend.
5. Merchandising setup: search rules, synonyms and recommendation placements.
6. Migration: move traffic page type by page type, with redirects and SEO checks.

FAQ

Is Adobe Commerce Optimizer a replacement for Adobe Commerce?

No. It is an experience layer. You still need a transactional backend for cart, checkout and orders, which can be Adobe Commerce or another platform.

Can I use Hyvä with Optimizer?

Optimizer's storefront is Commerce Storefront on Edge Delivery Services. Hyvä is a theme for the PaaS application's own storefront. A store could keep Hyvä pages during a gradual move, but the Optimizer storefront itself is Edge Delivery.

Does Optimizer work with Magento Open Source?

Adobe's storefront documentation states that Magento Open Source is not supported for this storefront path, as of November 2026.

Next step

If Optimizer fits, most of the work is storefront and data. Mistri's Edge Delivery storefront service covers Commerce Storefront builds, and our headless Adobe Commerce service covers the API and integration side.

Sources

Adobe Commerce Optimizer overview (Adobe Experience League); Adobe Commerce Optimizer Connector overview (Adobe Experience League); Commerce Storefront supported backends (Adobe Experience League); Adobe Commerce Optimizer developer documentation (Adobe Developer); Adobe Commerce platform and services overview (Adobe Experience League).