Storefront Backend Options

Storefront supports three backend types. Follow only the guidance for your backend—prerequisites and setup differ, and mixing steps causes errors.

• Commerce PaaS — Existing Adobe Commerce Cloud or on-premises (no Adobe Commerce as a Cloud Service or Adobe Commerce Optimizer license)
• Adobe Commerce as a Cloud Service — Cloud Service customer; license includes Storefront
• Adobe Commerce Optimizer — New Adobe Commerce Optimizer customer, or existing PaaS customer who added Adobe Commerce Optimizer

Not sure which backend you have?

Commerce PaaS = existing cloud or on-premises. Adobe Commerce as a Cloud Service = Customer with Storefront in license. Adobe Commerce Optimizer = Adobe Commerce Optimizer customer or PaaS + Adobe Commerce Optimizer.

Feature	Commerce PaaS	Adobe Commerce as a Cloud Service	Adobe Commerce Optimizer
License includes Storefront	No	Yes	Yes
Setup	Manual install required (see Prerequisites below)	Fully automated	Fully automated
Version	v2.4.7+ self-managed	Auto-managed	Fully managed SaaS

PaaS + Adobe Commerce Optimizer Connector

The Adobe Commerce Optimizer Connector (PaaS-to-Adobe Commerce Optimizer) requires manually installing the PHP extension on the PaaS platform and configuring the Adobe Commerce Optimizer UI. See the Adobe Commerce Optimizer documentation for connector setup.

Loading diagram...

Key components: EDS connects to PaaS, Adobe Commerce as a Cloud Service, or Adobe Commerce Optimizer. Luma Bridge (PaaS only) bridges EDS and Luma—independent of Adobe Commerce Optimizer. Cloud Service has no Luma; it pairs with Adobe Commerce Optimizer for catalog. The Adobe Commerce Optimizer Connector syncs PaaS catalog/pricing into Adobe Commerce Optimizer.

Prerequisites

Commerce Platform-as-a-Service (PaaS)

Product license

Adobe Commerce Cloud or on-premises (Magento Open Source not supported). Or with the Adobe Commerce Optimizer Connector —requires Storefront Compatibility package.

Version

v2.4.7 or later

Storefront Compatibility package

Required. See Storefront Compatibility package (2.4.7 or 2.4.8).

Storefront services (manual install)

• Without Adobe Commerce Optimizer Connector: Data Connection, Services Connector, Catalog Service, Live Search, Product Recommendations. See Commerce Services Connector .
• With Adobe Commerce Optimizer Connector: PHP extension on PaaS + Adobe Commerce Optimizer UI configuration. Data Connection support may differ—see connector documentation.

Luma Bridge and Adobe Commerce Optimizer

Luma Bridge works without an Adobe Commerce Optimizer license or the Adobe Commerce Optimizer Connector on PaaS with a Luma store. Luma Bridge is the session bridge between Edge Delivery Services and a Luma/PHP storefront. It is separate from Adobe Commerce Optimizer, which solves catalog and merchandising problems. With Adobe Commerce Optimizer and the Adobe Commerce Optimizer Connector, Luma Bridge still works for session sharing during migration. See Luma Bridge.

Adobe Commerce as a Cloud Service

Product license

Adobe Commerce as a Cloud Service (License includes Storefront)

All requirements

Automatically managed by Adobe. No manual installation.

Adobe Commerce Optimizer

Product license

Adobe Commerce Optimizer (License includes Storefront)

All requirements

Fully managed SaaS. No manual installation.

Adobe Commerce Optimizer + PaaS

PaaS customers who add Adobe Commerce Optimizer can use Luma Bridge to keep cart, checkout, and account on PaaS while migrating to Edge Delivery Services drop-ins.

Backend	Next step
Commerce PaaS	Complete prerequisites below, then Storefront Setup
Adobe Commerce as a Cloud Service	Storefront Setup
Adobe Commerce Optimizer	Storefront Setup

PaaS: required packages and services

Note

Adobe Commerce as a Cloud Service and Adobe Commerce Optimizer auto-install and auto-configure everything below. Skip this section if you are not on Commerce PaaS.

Storefront Compatibility package

Extends the GraphQL schema for cart, checkout, account, and order. See Storefront Compatibility package (2.4.7 or 2.4.8).

Storefront services

Read-only catalog data via GraphQL; required for high Lighthouse scores.

Service	Documentation
Data Connection	Data Connection Guide
Services Connector	Commerce Services Connector
Catalog Service	Catalog Service Guide
Live Search	Live Search ; eventing for headless
Product Recommendations	Events ; setup

Multiple stores in one Commerce environment

Contact Adobe Commerce Support if only one store migrates to Edge Delivery Services—Live Search must stay active without disabling Elasticsearch for other stores.

Next steps

Storefront Setup — Create your storefront from the boilerplate and configure your backend.