Adobe Commerce as a Cloud Service (ACCS): What UK Merchants on Magento Need to Know

Most UK merchants on Magento haven't heard of Adobe Commerce as a Cloud Service yet. Those who have assume it's expensive or not relevant. Both assumptions are worth examining — here is what ACCS actually means commercially and what to do about it.

<p>Most UK merchants currently running on Magento or Adobe Commerce have not heard of Adobe Commerce as a Cloud Service. Those who have tend to assume one of three things: that it is expensive, that it is complicated, or that it is not relevant to them yet.</p>

<p>All three assumptions are worth examining carefully. Because for a significant number of UK manufacturers and retailers on Magento PaaS right now, ACCS is not a distant platform upgrade. It is a commercial decision with meaningful implications for budget, capability and competitive positioning — and the window to make that decision thoughtfully, rather than reactively, is open now.</p>

<p>This article is not a technical deep-dive. It is a strategic overview for the MD or operations director who wants to understand what Adobe Commerce as a Cloud Service actually means for their business — and what, if anything, to do about it.</p>

<h2>What Adobe Commerce as a Cloud Service Actually Is</h2>

<p>Adobe Commerce as a Cloud Service, universally abbreviated to ACCS, was announced at Adobe Summit in March 2025 and became generally available in June 2025. It represents a fundamental shift in how Adobe Commerce is deployed, managed and maintained.</p>

<p>The simplest way to understand it is: ACCS moves Adobe Commerce from a platform you run to a platform that runs itself.</p>

<p>Under the traditional model — Adobe Commerce on Cloud, known as PaaS — merchants license the software and share responsibility for the infrastructure with Adobe. That means managing patches, security updates, version upgrades and performance optimisation. Developer hours spent on maintenance rather than growth. Upgrade projects that consume agency retainer time and budget every twelve to eighteen months.</p>

<p>ACCS eliminates all of that. Adobe manages the infrastructure, the upgrades, the security patches and the scaling entirely. Merchants get a fully managed, cloud-native commerce platform with automatic updates, zero DevOps overhead and no more upgrade projects.</p>

<p>Adobe now offers three deployment models. ACCS is the SaaS model — fully managed, headless-first, built on Edge Delivery Services for the frontend and App Builder for customisation. Adobe Commerce on Cloud remains available as the PaaS model for merchants who need full code-level customisation. Self-hosted Magento Open Source continues for those who want complete infrastructure control.</p>

<p>The UK context matters here. Adobe Commerce and Magento has its second-largest market globally in the UK, with approximately 7,577 UK companies running on the platform — the largest Adobe Commerce market in Europe by some distance. The arrival of ACCS is not an abstract global development. It is directly relevant to thousands of UK merchants, many of whom are making platform decisions right now.</p>

<h2>The Three Questions UK Merchants Are Actually Asking</h2>

<p>When ACCS comes up in a commercial conversation, the same three questions arise consistently.</p>

<h3>Is it expensive?</h3>

<p>The published licence fee range is $22,000 to $125,000 and above per year, scaled to GMV. Seen in isolation, that number stops conversations. But seen in context, it looks very different.</p>

<p>The right question is not what ACCS costs — it is what your current setup actually costs when you account for everything. The licence or hosting fee you pay is visible. The developer retainer hours spent on patches, version upgrades and security fixes are less visible but often more significant. The agency time consumed by upgrade projects that deliver no commercial return is rarely calculated.</p>

<p>ACCS does not add cost to a business. For many merchants, it reallocates it — converting invisible maintenance spend into visible licence fees while freeing agency and internal capacity for growth work. The comparison is not ACCS cost versus current licence cost. It is ACCS cost versus true total cost of ownership, including all the budget that currently goes on keeping the platform running rather than making it perform.</p>

<h3>Is it complicated?</h3>

<p>For merchants, the answer is no. It is materially simpler than what they run today. Adobe handles the complexity. Instances can be provisioned in minutes. There are no upgrade projects to manage, no security patches to apply, no performance optimisation overhead.</p>

<p>For agencies and developers, ACCS requires a different approach. Traditional Magento extensions that modify core code do not work in ACCS. Customisation is handled through App Builder, API Mesh and webhooks. Luma-based storefronts need rebuilding using Edge Delivery Services. This is a re-architecture, not a data lift-and-shift — and any agency advising a client on ACCS migration needs to be honest about that scope.</p>

<p>For merchants, the practical implication is straightforward: your agency partner needs genuine ACCS capability, not just familiarity with Adobe Commerce PaaS. The number of UK agencies with real ACCS build experience is currently small. That matters when you are evaluating who to work with.</p>

<h3>Do I need to move now?</h3>

<p>No. Migration from PaaS to ACCS is not mandatory. Adobe has confirmed that existing Adobe Commerce Cloud customers are not required to migrate, and PaaS support continues with no current end date published. Adobe has also extended support for versions 2.4.4, 2.4.5 and 2.4.6 to August 2026, giving merchants on older versions additional runway.</p>

<p>ACCS is recommended for all new Adobe Commerce implementations from mid-2025 onwards. For existing merchants, the migration decision depends on their specific commercial and technical situation — and the answer is not the same for every business.</p>

<h2>The Performance Case: Why Speed Is a Commercial Argument</h2>

<p>One of the most underappreciated aspects of ACCS is what it does to site performance — and what that means commercially.</p>

<p>ACCS is built on Adobe's Edge Delivery Services, which serve frontend assets from the network edge globally, enabling sub-second load times and near-perfect Lighthouse performance scores. Research consistently shows that a one-second delay in page load reduces conversion rates materially. Edge Delivery Services sites have been shown to deliver conversion rate improvements of 4 to 8%.</p>

<p>For UK merchants who have accepted that their Adobe Commerce site performs adequately but not exceptionally — often because performance investment competes with upgrade budget — ACCS removes that constraint. Performance is built in, not bolted on.</p>

<h2>What Happens to Your Existing Magento Customisations</h2>

<p>This is the question that requires the most honest answer, because it is where merchant expectations most often diverge from reality.</p>

<p>A move to ACCS is not a version upgrade. It is a platform re-architecture. The core product data, customer records and order history can migrate through Adobe's tooling. What does not survive unchanged are the customisations built into the existing PaaS environment — PHP modules that modify core Magento code, Luma-based storefronts, and integrations wired directly to the database or legacy REST APIs.</p>

<p>For merchants who have run Adobe Commerce PaaS for several years, this typically means three categories of rebuild work: the frontend (rebuilding from Luma to Edge Delivery Services — usually the largest cost), custom extensions (rebuilding on App Builder rather than core code modifications), and third-party integrations (reassessing ERP, PIM and payment connections against the API-first architecture).</p>

<p>The commercial implication is that migration cost is real and needs to be scoped honestly before any decision is made. The question worth asking is not "can we afford ACCS?" It is "what are we planning to spend on our platform in the next two years regardless — and what does ACCS change about how that money is allocated?"</p>

<h2>Adobe Commerce Optimizer: The Bridge Option</h2>

<p>ACCS was not the only product announced at Adobe Summit in March 2025. Adobe Commerce Optimizer — ACO — was announced alongside it as a distinct, modular offering.</p>

<p>ACO allows merchants to access Adobe's frontend catalogue capabilities — Live Search, Product Recommendations, Edge Delivery Services storefronts — without a full backend migration. It sits on top of an existing commerce backend, including Adobe Commerce PaaS or even other platforms, and delivers performance and merchandising improvements without touching the underlying system.</p>

<p>ACO is genuinely useful for merchants who want measurable frontend performance improvements without committing to full ACCS migration. It is also a sensible first step for merchants who want to experience ACCS architecture in practice before the full commitment. Customisations and integrations built through ACO are forward-compatible with ACCS — which means the work is not wasted if a full migration follows.</p>

<p>Whether ACO is the right move depends on where the commercial pain is. If the primary problem is conversion rate and performance, ACO addresses it without platform change. If the primary problem is the total cost and operational burden of maintaining PaaS infrastructure, ACO does not solve it — only full ACCS migration does.</p>

<h2>The Headless Opportunity: Why ACCS Changes the Architecture Conversation</h2>

<p>ACCS is built headless-first. This is both architecturally and commercially significant.</p>

<p>Traditional Magento and Adobe Commerce implementations use Luma, Adobe's built-in frontend theme, which tightly couples the frontend to the backend. Headless architecture separates the two entirely, allowing the frontend to be built in any technology while the commerce backend handles transactions, catalogue and customer data. The result is faster performance, greater design flexibility and the ability to deliver commerce experiences consistently across multiple channels from a single backend.</p>

<p>For <a href="/insights/b2b-ecommerce-for-uk-manufacturers">UK manufacturers in particular</a>, headless architecture opens a commercially significant possibility: serving a <a href="/insights/how-to-choose-b2b-ecommerce-platform-trade-portal">B2B trade portal</a>, a DTC storefront and potentially a trade configurator or dealer portal from a single Adobe Commerce backend — each with its own distinct frontend experience. That is difficult to achieve cleanly in a monolithic Luma setup and considerably more straightforward in a headless ACCS architecture.</p>

<p>The key requirement is working with an agency that has genuine headless build experience. ACCS is a different technical discipline from traditional PaaS delivery, and the agency selection decision matters accordingly.</p>

<h2>Who Should Be Considering ACCS Now — and Who Should Wait</h2>

<p><strong>Consider ACCS seriously now if:</strong></p>

<p>You are planning a new Adobe Commerce implementation — ACCS is the recommended model for all new builds from mid-2025. You are approaching a major version upgrade on PaaS and the upgrade cost is significant — the budget comparison with ACCS migration may be closer than expected. You are spending a material proportion of your agency retainer on maintenance, patching and upgrade work rather than growth activity. Your business is growing into genuine complexity — multi-brand, multi-region, multi-channel — where ACCS's catalogue management capability becomes relevant. You are already working with a headless-capable Adobe agency.</p>

<p><strong>Wait, or proceed carefully, if:</strong></p>

<p>Your current PaaS setup is heavily customised with core code modifications that would require significant rebuild. Your business operates below the threshold where ACCS licence costs make commercial sense against your true total cost of ownership. You are mid-way through a significant PaaS investment and the migration cost would duplicate rather than redirect that spend. Your agency does not have genuine ACCS build experience.</p>

<p>ACCS is the future direction of Adobe Commerce. It is not the right decision for every merchant today. But the merchants who evaluate it properly now — understanding their true TCO, assessing their rebuild requirements and getting a genuine demo — are making the decision with the right information. Those who defer indefinitely are making a different kind of decision by default.</p>

<h2>Five Questions Worth Asking Before Any ACCS Decision</h2>

<p><strong>What is our true current platform cost?</strong> Not just the licence or hosting fee — the full picture including developer retainer hours on maintenance, upgrade project costs over the last two years and any internal resource attributed to platform management. Most merchants have never calculated this number. It is almost always higher than expected.</p>

<p><strong>What is our upgrade position?</strong> Are we on a supported version? When is our next planned upgrade? What will it cost? For merchants on versions 2.4.4 to 2.4.6 with extended support running to August 2026, the upgrade decision is imminent regardless of ACCS.</p>

<p><strong>What does our customisation footprint look like?</strong> How much of what we have built sits in core code modules versus API integrations? The answer shapes the migration cost estimate materially.</p>

<p><strong>Is our agency partner genuinely ACCS-capable?</strong> Have they delivered a live ACCS build? Do they have real headless commerce experience at scale? ACCS is a different technical discipline from PaaS. The agency that built your current site may or may not be the right agency to migrate it.</p>

<p><strong>What commercial outcome are we trying to achieve?</strong> ACCS is not an objective — it is a platform decision in service of a commercial outcome. Reduced maintenance cost. Faster frontend performance. Multi-channel capability. Better <a href="/insights/how-to-choose-b2b-ecommerce-platform-trade-portal">B2B trade portal functionality</a>. The outcome should be defined before the platform decision is made.</p>

<h2>The Practical Next Step</h2>

<p>For most UK manufacturers and retailers on Magento, the right move right now is not to commit to ACCS or dismiss it. It is to understand it properly.</p>

<p>That means getting a demo. It means <a href="/insights/should-you-replatform-your-ecommerce-site">calculating your true current platform cost</a>. It means having an honest conversation with an agency that has genuine ACCS build experience about what a migration would actually involve for your specific setup.</p>

<p>Right Partners helps UK manufacturers and retailers make platform decisions from a commercial position rather than a technical one — ensuring the business case is clear before any agency is briefed or any commitment is made. If you are an MD or commercial director currently on Magento or Adobe Commerce PaaS and want to understand what ACCS means for your specific business, <a href="/free-strategy-consultation">book a free 60-minute conversation</a>. No pitch. No slides. A clear picture of where you stand and what your options are.</p>

<h2>Frequently Asked Questions</h2>

<h3>What is Adobe Commerce as a Cloud Service (ACCS)?</h3>

<p>Adobe Commerce as a Cloud Service is Adobe's SaaS delivery model for Adobe Commerce, launched in June 2025. It is a fully managed, cloud-native platform where Adobe handles all infrastructure, security patches, upgrades and scaling. Merchants get the full commercial capability of Adobe Commerce without the operational overhead of managing the platform. It uses Edge Delivery Services for the storefront and App Builder for customisation, and is built on a headless-first architecture.</p>

<h3>Do I have to migrate from Adobe Commerce PaaS to ACCS?</h3>

<p>No. Migration is not mandatory. Adobe has confirmed that existing Adobe Commerce Cloud customers can remain on PaaS, which continues to receive full support with no published end date. Adobe has also extended support for versions 2.4.4, 2.4.5 and 2.4.6 to August 2026. ACCS is recommended for all new implementations from mid-2025, but the migration decision for existing merchants depends on their individual commercial and technical situation.</p>

<h3>How much does Adobe Commerce as a Cloud Service cost?</h3>

<p>ACCS licence fees are GMV-based and range from approximately $22,000 to $125,000 and above per year. The licence fee in isolation is not the right comparison point — the correct evaluation is ACCS total cost against the true total cost of your current PaaS setup, including all maintenance, upgrade and development overhead. Most merchants discover their true platform cost is considerably higher than the visible licence fee alone.</p>

<h3>What happens to my existing Magento extensions and customisations?</h3>

<p>Traditional Magento extensions that modify core PHP code do not work in ACCS. They need to be rebuilt using Adobe's App Builder, API Mesh and webhooks. Luma-based storefronts also need rebuilding using Edge Delivery Services. This makes ACCS migration a re-architecture project rather than a version upgrade. The scope and cost of that rebuild depends on how heavily customised your current setup is.</p>

<h3>What is Adobe Commerce Optimizer and how does it relate to ACCS?</h3>

<p>Adobe Commerce Optimizer is a separate, modular product that allows merchants to access ACCS frontend capabilities — including Edge Delivery Services storefronts, Live Search and Product Recommendations — without migrating the backend. It can run on top of Adobe Commerce PaaS or other commerce platforms. It is a useful bridge option for merchants who want frontend performance improvements without a full migration, and customisations built through ACO are forward-compatible with ACCS.</p>

<h3>What is the difference between Adobe Commerce ACCS and Adobe Commerce PaaS?</h3>

<p>PaaS (Adobe Commerce on Cloud) is a single-tenant environment where merchants share infrastructure management with Adobe. Full code-level customisation is possible but merchants are responsible for patches, upgrades and scaling decisions. ACCS is a multi-tenant SaaS environment where Adobe manages everything. Customisation is limited to App Builder and API-based approaches. ACCS has lower operational overhead but requires a headless frontend and is a re-architecture from a traditional PaaS setup.</p>

<hr>

<p><strong>Further reading:</strong> <a href="/insights/how-to-choose-b2b-ecommerce-platform-trade-portal">How to Choose the Right Ecommerce Platform for Your B2B Trade Portal</a> · <a href="/insights/b2b-ecommerce-for-uk-manufacturers">B2B Ecommerce for UK Manufacturers: The Commercial Opportunity Most Are Still Ignoring</a> · <a href="/insights/should-you-replatform-your-ecommerce-site">Should You Replatform Your Ecommerce Site? A Vendor-Neutral Decision Framework</a></p>

More articles coming soon.