DocumentationCommerceInformation Center

Implementation architecture options

Last update: October 21, 2026

CREATED FOR:

  • Developer
  • Leader

Adobe Commerce implementation architectures combine three layers: a commerce backend (Adobe Commerce or Adobe Commerce Optimizer), a storefront, and a set of connected services and integrations. Compare the following options to identify which system owns catalog, pricing, cart, checkout, orders, and customer transactions in each architecture.

Architecture options summary

Compare the options by transaction ownership and by storefront experience.

Commerce platform and transactions

Option
System of record
Transaction path
Best fit
Adobe Commerce as a Cloud Service with Commerce Foundation
Adobe-managed Commerce Foundation
Managed Commerce Foundation and connected Commerce services
Customers that want Adobe-managed software as a service (SaaS) Commerce with reduced infrastructure ownership
Adobe Commerce on Cloud or on premises with the Adobe Commerce Optimizer Connector
Existing Commerce Foundation, for Commerce data and transactions
Existing Commerce Foundation APIs and connected transaction services
Customers that want to add Optimizer discovery and merchandising capabilities to an existing Adobe Commerce deployment
Stand-alone Adobe Commerce Optimizer with an external commerce backend
Existing or third-party commerce platform. Catalog and price data are added to Optimizer from an external source
API Mesh, App Builder, or direct integrations connect the storefront to third-party cart, checkout, customer, order, payment, tax, shipping, and fulfillment services
Customers that want Optimizer capabilities while retaining an existing or third-party transactional commerce platform
Adobe Commerce on Cloud or on premises with Commerce Foundation
Commerce Foundation
Commerce Foundation APIs and configured payment, tax, shipping, inventory, and fulfillment integrations
Customers that need the full Adobe Commerce platform with deployment control over cloud or on-premises infrastructure

Storefront experience

Storefronts connect to Commerce Foundation APIs, Storefront Services (Catalog Service, Live Search, and Product Recommendations), or Adobe Commerce Optimizer Merchandising Services.

Option
Storefront experience
Storefront data path
Adobe Commerce as a Cloud Service with Commerce Foundation
Commerce Storefront powered by Edge Delivery Services or another supported headless experience
Storefront Services, plus Commerce Foundation APIs for core platform data
Adobe Commerce on Cloud or on premises with the Adobe Commerce Optimizer Connector
Edge Delivery Services or custom headless storefront using Optimizer experiences
Commerce Optimizer Merchandising Services GraphQL APIs for Optimizer-managed catalog and merchandising data
Stand-alone Adobe Commerce Optimizer with an external commerce backend
Commerce Storefront powered by Edge Delivery Services or a custom headless storefront
Commerce Optimizer Merchandising Services GraphQL APIs for catalog and merchandising data
Adobe Commerce on Cloud or on premises with Commerce Foundation
Edge Delivery Services, Luma, PWA, or custom headless storefront
Commerce Foundation APIs, plus Storefront Services when configured

Adobe Commerce as a Cloud Service

Architecture diagram of Adobe Commerce as a Cloud Service with managed Commerce Foundation and Storefront Services feeding a Commerce Storefront {width="600" modal="regular"}

Key boundary—Adobe manages the Commerce Foundation platform. The architecture uses Storefront Services, including Catalog Service, Live Search, and Product Recommendations, for storefront experiences. Product Visuals powered by AEM Assets is an optional SaaS integration. See AEM Assets integration for Commerce.

References:

Adobe Commerce with Commerce Foundation

Architecture diagram of Adobe Commerce on Cloud or on premises with Storefront Services and Commerce Foundation APIs feeding a Commerce Storefront {width="600" modal="regular"}

Key boundary—Commerce Foundation owns the Commerce platform and transaction flows. Catalog Service, Live Search, and Product Recommendations provide optimized storefront access to catalog, search, and recommendations when configured. AEM Assets integration is optional. See AEM Assets integration for Commerce.

References:

Adobe Commerce with the Optimizer Connector

Architecture diagram of the Adobe Commerce Optimizer Connector synchronizing catalog and price data from Adobe Commerce to Adobe Commerce Optimizer, feeding a Commerce Storefront through Merchandising Services APIs {width="600" modal="regular"}

Key boundary—The Connector synchronizes catalog and price data from Adobe Commerce to Adobe Commerce Optimizer. Adobe Commerce remains the transaction system, while Optimizer supplies discovery and merchandising experiences through its Merchandising Services APIs.

References:

Stand-alone Commerce Optimizer with a third-party backend

Architecture diagram of customer-owned source systems sending catalog and price data through Data Ingestion to a stand-alone Adobe Commerce Optimizer, feeding a Commerce Storefront connected to a third-party commerce backend {width="800" modal="regular"}

Key boundary—Stand-alone Adobe Commerce Optimizer owns catalog discovery and merchandising experiences, but not the transactional Commerce backend. Catalog and price data enter through the Data Ingestion REST API. The Edge Delivery Services storefront uses Merchandising Services GraphQL APIs for product experiences and connects to the third-party backend for cart and checkout.

References:

Terminology quick reference

Preferred term
Meaning
Avoid using as a current architecture label
Commerce Foundation
Base commerce and transactional capabilities
Core Commerce, PHP Foundational Layer
Storefront Services
Storefront-oriented APIs for Catalog Service, Live Search, and Product Recommendations
A label limited to only one Commerce platform
Commerce Optimizer Merchandising Services
Optimizer APIs for catalog discovery and merchandising experiences
Commerce Foundation APIs
Commerce Storefront powered by Edge Delivery Services
Customer-facing storefront implementation
An API family
recommendation-more-help
commerce-help-information-center