When your Magento 2 shop's Luma theme sits at a 5-second mobile LCP, the frontend question is on…
commercetools Sphere and Autonomous Commerce: Who Owns the Experience Layer?
commercetools helped define the composable commerce market, and it is visibly moving toward autonomous, agent-assisted commerce flows - a direction it frames under the Sphere brand. For teams that build on commercetools, this raises a practical question. As the backend makes more decisions and produces more output on its own, who owns and operates the customer-facing experience layer? We see the experience layer as a distinct discipline. And as a commercetools partner, we argue it is best operated by a Frontend Management Platform (FMP) that sits on top of commercetools.
What autonomous commerce means for the backend
Autonomous commerce pushes logic down into the platform. Catalogue, pricing, promotion and, increasingly, decisions about the next sensible offer are computed in the backend, sometimes prepared by agents. That is a sound direction: commercetools is strong at exposing domain logic as an API. The result is a backend that returns not only data but intent and suggestions. This is also where a new line of responsibility begins. A suggestion is not yet a page. An agent output is not yet an experience.
Why the experience layer is a separate concern
The experience layer answers different questions than the backend. How does an agent output become a view that loads fast, stays accessible and fits the brand? Who decides which suggestions appear where? How does a marketing team intervene without triggering a deployment? More backend autonomy does not answer these questions - it makes them more urgent. The more autonomous the source, the more you need a layer that curates, renders and controls the output. This does not compete with commercetools. It is the logical complement above the API.
Rendering agent output, not just displaying it
When an agent produces a recommendation, a bundle or a dynamic arrangement, the experience layer has to turn that into a dependable rendering. Rendering here means taking structured output and building a consistent component that works in every context - home page, category, search result, app. An FMP for commercetools translates backend intent into stable frontend building blocks instead of passing raw agent output straight through to the browser. The backend output stays autonomous while the presentation stays predictable.
Performance and accessibility remain frontend work
An autonomous backend does not change the hard requirements of delivery. Core Web Vitals, caching, rendering strategy and WCAG conformance all live at the edge with the user, not in the domain logic. When content is computed more at runtime, the need for a layer that disciplines caching, fallbacks and load behaviour actually grows. An agentic frontend management platform treats performance and accessibility as a contract, not as an afterthought.
Marketer control is not at odds with autonomy
Backend autonomy must not mean marketing teams lose control. If anything, the opposite is true: delivering autonomous suggestions requires clear guardrails - where agent output may appear, which rules apply, how manual curation takes priority. The experience layer is where this governance becomes visible. Editors arrange, override and test without blocking development cycles. People stay in the driving seat while the backend works in the background.
The clean split: commercetools below, experience above
The durable line is easy to state. commercetools owns domain, data and increasingly autonomous decisions. The experience layer owns presentation, delivery, accessibility and editorial control. A composable frontend architecture makes that split explicit instead of wiring it into the storefront. The result is a division of labour that plays to both strengths: commercetools stays the strong core, and the FMP becomes the operational layer for everything the customer sees.
What this means for commercetools teams today
Teams evaluating Sphere and autonomous flows should not treat the experience layer as a side effect. The question is not whether the backend becomes more autonomous - it is who curates, renders and delivers the output. Teams that own this layer on purpose can absorb backend innovation quickly without compromising on performance, accessibility or marketer control. That is the role a Frontend Management Platform plays alongside commercetools.
Next steps
If you run commercetools and take the autonomous direction seriously, it is worth looking closely at the experience layer. See how a headless frontend for commercetools renders agent output, protects performance and keeps marketing teams in control.
More from the platform
Marcel Thiesies, Co-Founder, Laioutr
All data is based on publicly available information, insights from sales conversations with DACH e-commerce brands, and our own platform testing. As of July 2026. commercetools features may have evolved since.