Backend options
The storefront supports a few backend types, each with its own prerequisites, so follow only the path that matches your project. Choosing the wrong type leads to misleading signals. For example, GitHub and DA.live look healthy, but previews or drop-ins fail. As a result, you might install packages your license does not require.
For authoring storefront pages (Document Authoring, Universal Editor), see Document Authoring Quick Start. This page covers the Commerce backend the storefront connects to.
All drop-in components require an Adobe Commerce as a Cloud Service or Adobe Commerce Optimizer license. Adobe Commerce on Cloud and on-premises customers who add an Adobe Commerce Optimizer license get drop-in support as part of that license. There is no separate “B2B backend” type.
Backends fall into the following categories:
- Commerce on Cloud or on-premises — Existing Adobe Commerce on Cloud infrastructure or on-premises deployment without an Adobe Commerce as a Cloud Service or Adobe Commerce Optimizer license
- Adobe Commerce as a Cloud Service — Cloud Service deployment whose license includes Storefront
- Adobe Commerce Optimizer — New Adobe Commerce Optimizer deployment, or an existing PaaS deployment that added Adobe Commerce Optimizer
Which backend do you have?
Section titled “Which backend do you have?”| Feature | Adobe Commerce (on cloud, on-premises) | Adobe Commerce as a Cloud Service | Adobe Commerce Optimizer |
|---|---|---|---|
| License includes Storefront | No | Yes | Yes |
| Setup | Manual install required | Fully automated | Fully automated |
| Version | v2.4.8+ (self-managed Commerce) | Continuous release (Adobe-managed) | Continuous release (Adobe-managed) |
Backend topology
Section titled “Backend topology”This diagram focuses on the backend layer. It adds two optional pieces you use during a phased migration to Adobe Commerce as a Cloud Service or Adobe Commerce Optimizer: Luma BridgeA PHP module on your Commerce instance that reads session cookies from EDS drop-ins, letting Luma pages share the same shopper cart and sign-in session during a phased migration to Edge Delivery Services. and the Adobe Commerce Optimizer Connector. Luma is Adobe’s classic server-side Commerce storefront theme. If you run a LumaAdobe Commerce's classic server-side storefront theme, built with PHP. If you run a Luma storefront today, Luma Bridge can help share cart and sign-in sessions with EDS drop-ins while you migrate. storefront and move to Edge Delivery Services, Luma Bridge enables Luma pages and EDS drop-ins to share the same cart and sign-in session. For the full stack (drop-ins, boilerplate, and how services connect), see Commerce services and backends.
Prerequisites by backend
Section titled “Prerequisites by backend”Open only the tab for your backend and read it end to end. Commerce on Cloud or on-premises includes a manual checklist the two managed backends skip.
PaaS: required packages and services
Section titled “PaaS: required packages and services”Install and configure the following on Commerce on Cloud or on-premises before you create your storefront. Adobe Commerce as a Cloud Service and Adobe Commerce Optimizer manage these automatically, so skip this section if you are not on Commerce on Cloud or on-premises.
Minimum checklist before you create a storefront
Section titled “Minimum checklist before you create a storefront”Before Site CreatorApp in Document Author (DA.live) that creates and initializes a storefront by setting up content, optional code, theme choice, and storefront configuration values., manual configuration, or local preview can rely on Commerce APIs, confirm these items on Commerce on Cloud and on-premises:
- You are on Adobe Commerce v2.4.8 or later (Magento Open Source is not supported for this storefront path).
- You installed the Storefront Compatibility packageA PHP package you install on Commerce PaaS that extends the GraphQL schema so cart, checkout, account, and order drop-ins can communicate with your backend as expected., which fills gaps in the core Commerce GraphQL schema that drop-ins require. See Storefront Compatibility Package for who installs it, or Manual installation if you are on Commerce on Cloud or on-premises with Adobe Commerce Optimizer.
- If you build a B2B storefront, install the Storefront Compatibility B2B Package (SCP-B2B) on the same Commerce instance, after Adobe Commerce B2B is configured there.
- You connected the storefront services your project needs (at minimum, plan for Services Connector and Catalog Service, then add Live Search, Product Recommendations, and Data Connection per your rollout). Use the service documentation table below for links.
Storefront Compatibility package
Section titled “Storefront Compatibility package”Your storefront repo still uses npm for JavaScript drop-ins, but these modules run as PHP on the Commerce server. See Commerce services to learn how Commerce services fit together.
Storefront services
Section titled “Storefront services”Catalog Service, Services Connector, Live Search, and Product Recommendations are covered on Adobe Experience League and in Commerce services. Data Connection is optional and comes from a separate product, Adobe Experience Platform.
Headless storefronts must send the required storefront events for Live Search and Product Recommendations. The Adobe Experience League topics in the table cover setup and headless data requirements. On Edge Delivery Services, implement storefront events with the Adobe Client Data Layer and Analytics .
| Service | Documentation |
|---|---|
| Data Connection | Data Connection page |
| Services Connector | Commerce Services Connector |
| Catalog Service | Catalog Service page |
| Live Search | Live Search page ; Headless data collection |
| Product Recommendations | Product Recommendations page ; Headless integration · Drop-in setup |
Next steps
Section titled “Next steps”After confirming your prerequisites, create your storefront and connect it to Commerce.