Navigating Adobe Commerce SaaS: An Agency's Early Look at Headless Delivery

Hey EShopSet community! We often talk about staying ahead of the curve, especially when new platform iterations drop. Recently, a fascinating discussion popped up in one of our developer communities about Adobe Commerce SaaS. The original poster simply asked, "Is anyone using Adobe Commerce SaaS version? Could you please share your story, experience of working with it?" And boy, did we get some gold from an agency insider!

One community member, working at an agency with early preview access, shared a really candid, in-depth look at their experience building first implementations. This isn't just theory; it's boots-on-the-ground insight, crucial for any agency owner, PM, or developer considering this path.

Headless by Design: What to Expect

The core takeaway? Adobe Commerce SaaS is pretty much exactly what you'd expect from a headless commerce instance. It provides robust REST and GraphQL endpoints, which is fantastic for flexibility. However, it also means a shift in the Admin interface – don't expect traditional features like Page Builder to be there in the same way. This is a fundamental change, pushing agencies to rethink content management strategies and how they approach client expectations for administrative control.

Diving into App Builder: A New Paradigm

One of the biggest points of discussion revolved around "Out-of-process Extensibility" via App Builder. Our agency expert noted that this is a major platform pillar, but it presents a significant learning curve, especially for developers accustomed to traditional PHP environments. It's a different paradigm entirely. Imagine shifting from deeply embedded customizations to building external applications that interact with the core via APIs – a true microservices approach.

The good news? App Builder is rapidly maturing. The respondent mentioned that just a few months ago, it felt "brittle and new," with quirks like having to re-enable apps every time you logged in. Those pain points are gone. Updates to things like AdminUISDK and the recent addition of the Management API for store configuration, along with improved storage libraries, mean it's becoming "fairly usable" if you're willing to invest in the learning.

This constant evolution highlights a key challenge for delivery timelines for agencies. When working with a rapidly updating platform feature like App Builder, it’s vital to factor in time for continuous learning and adaptation. What was true last quarter might be significantly improved today, but it still demands developer attention and can impact initial project estimates.

AEM Edge Delivery Services: The Default Head

The conversation also touched on the default storefront: Adobe Commerce Storefront, running on AEM Edge Delivery Services (EDS). This is where things get interesting. While EDS is "starting to become fleshed out," it's still described as "fairly primitive" and doesn't yet replicate all the native front-facing capabilities you'd find in a traditional Luma theme. This means agencies need to be strategic about what features they build custom and what they leverage from EDS.

However, there's a silver lining for developers. EDS is described as a "mixed bag" but generally easier to work with than traditional AEM development. It functions like a Hugo/Gatsby-style theming engine, making its boilerplate and drop-in components "pretty easy to understand." Developers can pick it up with relative ease, which is a big plus for onboarding new team members or upskilling existing ones, potentially speeding up front-end development once the learning curve is overcome.

EShopSet Team Comment

This discussion really underscores the evolving landscape of enterprise ecommerce. For agencies, Adobe Commerce SaaS represents a powerful, future-forward option, but it's not a 'lift and shift' scenario. We believe agencies need to proactively invest in training for App Builder and EDS, and clearly set client expectations around the capabilities and customization approach. The shift to headless and out-of-process extensibility demands a robust agency operations platform to manage the new project complexities, skill requirements, and evolving platform features effectively. Don't underestimate the paradigm shift; plan for it.

Key Takeaways for Your Agency

So, what does this mean for your agency?

• Embrace the Headless Mindset: Be ready for a truly headless experience, which means rethinking traditional content and admin workflows. This will impact how your clients manage their store post-launch.
• Invest in App Builder Skills: This isn't optional. Your developers will need to learn a new way of extending functionality, which requires dedicated training and practice.
• Understand EDS Limitations (and Strengths): While developer-friendly, EDS isn't a like-for-like replacement for all Luma features yet. Plan your front-end strategy accordingly, prioritizing core functionalities and custom-building where necessary.
• Factor in Platform Maturity: The platform is evolving rapidly. This is great for long-term potential, but requires flexibility in project planning and delivery timelines for agencies. Agile methodologies will be your best friend here.

The move to Adobe Commerce SaaS is a significant one, offering immense power and flexibility for the right projects. But as our community expert highlighted, it requires a willingness to learn, adapt, and manage expectations around a platform that's still very much on its growth journey. For agencies, this means proactive planning, continuous learning, and leveraging tools that support agile project delivery in this dynamic environment.