What is Adobe Commerce as a Cloud Service (ACCS): What Changes for Merchants?

Starting June 1, 2027, Adobe will no longer maintain Cloud environments running unsupported Commerce versions and reserves the right to decommission them. Currently, enterprise merchants who are on Adobe Commerce on Cloud should consider this as a platform direction signal with a hard enforcement date.

Adobe Commerce as a Cloud Service is Adobe's recommended long-term destination for all Adobe Commerce Cloud merchants. It is a fully managed SaaS model where Adobe handles the core application, infrastructure, and updates automatically. The June 2027 deadline gives enterprise merchants 11 months to evaluate their options, select a migration path, and begin the transition. This guide provides a comprehensive understanding of what Adobe Commerce as a Cloud Service is and how to choose the right migration path before the deadline closes.

What is Adobe Commerce as a Cloud Service (ACCS): What Changes for Merchants?

Adobe Commerce as a Cloud Service is a fully managed SaaS commerce platform where Adobe handles the core application, infrastructure, security patches, and automatic upgrades. Merchants no longer manage the underlying platform. Instead, customization happens through extensibility points including APIs, App Builder, and UI SDKs. The core application code is locked, providing no direct codebase modifications.

To understand what ACCS changes, it helps to see where it sits relative to the two deployment models merchants run today:

• Adobe Commerce on Cloud (PaaS): Adobe hosts the environment, but merchants manage application code, upgrades, patching, and infrastructure configurations. This is the shared responsibility model most enterprise Adobe Commerce merchants currently operate on.
• Adobe Commerce as a Cloud Service (SaaS): Adobe manages everything at the platform level. Merchants focus entirely on their storefront, integrations, and business logic built on top of stable APIs. No upgrade cycles, patch management, or version dependencies.

The most significant operational change is the versionless architecture. Adobe pushes updates automatically to all ACCS merchants. New features and security updates appear in the staging environment first, giving merchants 30 days to test before Adobe applies changes to production.

Three additional capabilities ship with every Adobe Commerce as a Cloud Service implementation:

• Commerce Storefront: Personalized storefronts powered by Edge Delivery Services with industry-leading page speed performance
• Intelligent Services: Live search, catalog service, and product recommendations delivered as composable APIs
• Adobe Developer App Builder: Extension framework for building custom applications and integrating ERP, CRM, and PIM systems through API Mesh

The June 2027 ACCS Enforcement Deadline: What It Means and Who it Affects

Adobe's enforcement policy is confirmed directly from its official lifecycle documentation. Starting June 1, 2027, Adobe will no longer maintain Cloud environments running unsupported Commerce versions and reserves the right to decommission them.

The deadline applies specifically to Adobe Commerce on Cloud merchants. Three commercial consequences apply to merchants who do not act before the deadline:

• Environment decommission risk: Adobe reserves the right to shut down Cloud environments running unsupported versions after June 1, 2027.
• PCI compliance exposure: PCI compliance is at risk from the end of 2026 for merchants on affected versions. Adobe strongly recommends consulting a qualified security assessor and prioritizing migration before the end of 2026 to maintain compliance.
• Loss of support: Security patches, quality fixes, and platform maintenance stop for unsupported versions. Every vulnerability discovered after the end of support date becomes a permanent, unpatched exposure.

Adobe Commerce as a Cloud Service Architecture: Four Components to Know

Adobe Commerce as a Cloud Service architecture is built around four products that work together as a unified SaaS system. Understanding each helps enterprise merchants assess what changes operationally after migration and what capabilities become available:

Commerce Storefront

The customer-facing interface where shoppers browse and purchase products. Commerce Storefront is powered by Edge Delivery Services and fully headless, with a decoupled architecture that delivers all merchandising data through a GraphQL API layer.

Before planning migration, every Adobe Commerce on Cloud should know that ACCS does not support Luma storefronts. Merchants currently running Luma must rebuild their storefront on Edge Delivery Services as part of the migration process.

Merchandising Services

Backend services that manage product catalogs, pricing, and inventory, merchandising Services delivers live search, product recommendations, and catalog service as composable APIs. They optimize performance at scale without requiring custom development for each capability.

Product Visuals

Digital asset management for product images and media integrated with Adobe Experience Manager. Product Visuals dynamically links digital assets to the appropriate merchandising entities, including products and categories based on SKU or other key attributes. It removes the manual asset management overhead that large catalog merchants currently handle inside Adobe Commerce.

Developer Platform

The Developer Platform gives development teams comprehensive tools including App Builder, API Mesh, Events, Webhooks, and Admin UI SDK to build custom applications. They connect ERP, CRM, and PIM systems, and orchestrate APIs into a unified GraphQL schema. Customization in ACCS happens above the platform rather than inside it, which makes implementations significantly more stable and upgrade-safe than the current PaaS model.

What Changes Operationally After Migrating to Adobe Commerce as a Cloud Service

The operational changes after migrating to Adobe Commerce as a Cloud Service affect three teams differently.

For system administrators

• Instance management moves to Commerce Cloud Manager, Adobe's self-service provisioning portal.
• Sandbox and production environments launch in minutes. User management and access control operate through Adobe Admin Console.
• Infrastructure responsibility shifts significantly toward Adobe, freeing system administrators from day-to-day environment management.

For merchants and merchandising teams

• Day-to-day commerce operations in the Commerce Admin remain familiar.
• Product management, order management, and store configuration all continue through the same interface.
• The upgrade experience changes entirely with new features and security updates arriving in staging automatically.

Teams test for 30 days before Adobe applies updates to production.

For development teams

• Direct core code modification is no longer available.
• All customization happens through App Builder, API integrations, webhooks, and the Admin UI SDK.
• Development teams with expertise in core code modification need to retrain around API-first extensibility.
• Customizations built on the API-first model survive every platform update automatically, eliminating compatibility testing at every upgrade cycle.

Adobe Commerce as a Service Migration Paths: What is Right for You?

Adobe confirms three migration paths for merchants moving to Adobe Commerce as a Cloud Service. The right path depends on store complexity, customization depth, and how quickly the business needs to move.

• Incremental migration: It moves data, customizations, and integrations in stages while keeping the existing store operational. This is the recommended path for large enterprise merchants with complex ERP integrations and heavily customized implementations.
• Commerce Optimizer: A transitional step that allows merchants to adopt key SaaS capabilities including Catalog Channels and Edge Delivery storefronts while the full ACCS migration is planned. It suits merchants who want to capture immediate benefits without committing to a full migration timeline upfront.
• Full migration: This completes the move in one planned project. The path suits merchants with fewer customizations and simpler integration requirements who need to move quickly.

Moreover, Adobe Summit 2026 introduced the Commerce Developer Agent, which scans existing implementations, produces a readiness report, assigns a complexity score, and generates a step-by-step migration roadmap.

Adobe Commerce as a Cloud Service vs Salesforce Commerce Cloud: A Decision Framework

For enterprise merchants evaluating platforms in light of the June 2027 deadline, Adobe Commerce as a Cloud Service vs Salesforce Commerce Cloud is one of the most common comparisons that surfaces during the planning process. Merchants can refer to the comparison below on which platform fits their specific situation rather than defaulting to a generic recommendation.

Choose Adobe Commerce as a Cloud Service if:

• The business is already invested in Adobe Experience Cloud including AEM, Marketo, and Adobe Analytics
• B2B commerce complexity is a core requirement: company accounts, contract pricing, approval workflows, and net payment terms
• The development team has existing Adobe Commerce (Magento) expertise the business wants to preserve
• Total cost of ownership matters more than speed of deployment
• The business runs both B2B and B2C from a single instance

Choose Salesforce Commerce Cloud if:

• The business runs its CRM, service, and marketing on Salesforce and commerce strategy is inseparable from that investment
• Speed of deployment and a unified Salesforce ecosystem matter more than B2B depth
• The business is primarily B2C with straightforward catalog requirements