四月 07, 2025
At Adobe Summit 2025, Adobe Commerce was included in the main keynote for the first time since the Magento acquisition. That visibility reflects a major shift.
Adobe Commerce is now positioned as a modern, cloud-native, AI-powered platform, built to scale, integrate and to reduce complexity for merchants and developers.
This product is the result of five years of steady, strategic transformation.
Adobe Commerce as a Cloud Service (ACCS)
ACCS moves Adobe Commerce from a PaaS model to a fully multi-tenant SaaS solution. It builds on the platform's existing strengths, while solving long-standing pain points.
Key components already in place and in production:
-
GraphQL Storefront APIs
-
Backend REST APIs for admin and integration
-
AppBuilder for extensibility outside the core
-
SaaS APIs for Catalog, LiveSearch, and Product Recommendations
-
Edge Delivery Services for a decoupled CMS and storefront
These tools are mature, widely used and stable. Many customers already rely on them today. The new element is infrastructure. Merchants no longer deploy custom code within their own PaaS environment. Customization is now handled through AppBuilder.
What this means for Adobe Commerce customers
ACCS eliminates the need for ongoing platform upgrades and patching. That significantly reduces the total cost of ownership — one of the biggest historical challenges with Adobe Commerce.
Edge Delivery Services is now integrated into the core Adobe Commerce offering, delivering faster frontends and advanced content management capabilities.
ACCS will be recommended for all new implementations starting mid-2025.
For existing Adobe Commerce customers, migration is not mandatory. The current Adobe Commerce Cloud service remains fully supported.
A phased path forward for current customers
-
Start by integrating available SaaS APIs into your existing frontend.
-
Adopt Edge Delivery Services and begin refactoring your frontend experience.
-
Audit backend PHP customizations and move high-value logic into AppBuilder.
This approach unlocks immediate performance and AI capabilities, spreads cost and effort over time and avoids the risk of a large-scale, one-time migration.
What this means for Adobe Commerce developers
PHP development for Adobe Commerce is being phased out.
All new development should shift to AppBuilder and Edge Delivery Services. Even if a client remains on the current platform, development should follow the new patterns to prepare for future migration.
Key use cases are already supported:
-
Payment provider integrations via AppBuilder with storefront GraphQL APIs
-
Real-time inventory validation using synchronous webhooks
-
ERP integration using the AppBuilder event framework and Integration Starter Kit
Node.js skills are now essential for Adobe Commerce development.
Commerce Optimizer expands reach
Adobe is extending key capabilities beyond Adobe Commerce through Commerce Optimizer.
Edge Delivery Services and SaaS APIs can now be used with other platforms like Salesforce or SAP. Merchants on third-party platforms can deploy Adobe’s high-performance storefront and content tools independently of their backend.
Integration is fast, powered by SaaS APIs and native drop-in components.
The shift is already underway
Adobe Commerce has transitioned from a monolithic commerce engine to a flexible, API-first SaaS platform.
ACCS simplifies operations, cuts maintenance and unlocks AI-powered tools through a modern architecture.
Customers benefit from faster time to value, lower TCO and more scalable development. Developers gain a clear path forward built around modern tooling and patterns.
The pieces are in place, adoption is accelerating — this is the new Adobe Commerce.
