Shopify and Vercel are rebuilding Hydrogen as an open, runtime-agnostic foundation. Hydrogen now dep…
K5 2026, Day 1: The Field Is Talking Agentic Commerce, but Who Controls the Experience Layer?
I am on the K5 floor today. ESTREL Berlin, 9 in the morning, and the tone is already set: this year, agentic commerce is the defining topic.
The field is talking about AI hubs piping product, price, and availability data directly to ChatGPT, Copilot, and Perplexity. Backends that respond autonomously to demand signals. Pricing agents reacting in real time to competitor data. Fulfillment orchestration without human intervention. That is genuinely interesting - and I think it describes real progress.
But there is a question I am not hearing on the floor today.
Two different problems
What the market is primarily discussing is the backend problem: how do I structure and expose my business data so that an AI agent can work with it? That is legitimate and important.
The other problem is the experience layer: what does the person - or the agent - actually encounter at the end of the flow? Who controls what gets rendered when three agents are simultaneously repricing products, adjusting recommendations, and delivering promotions?
These two problems are complementary. But they are not the same problem. And in today's K5 discourse they are often named in the same breath, as though one automatically follows from the other.
That is my take from the floor: solving the autonomous backend does not automatically answer the question of who governs the experience layer.
What I hear at the commercetools stand
Booth #37 is busy. "Agentic Jumpstart" is the term commercetools has brought to K5 - a structured offering that enables merchants to expose product and pricing data to AI agents via MCP and ACP. It is a concrete, well-thought-through step.
I find this noteworthy, not problematic. The market needs this backend layer. The question I keep asking is: and then what? When the agent knows the availability, the price, the promotion - on which surface does it meet the user? Who designed that surface? Who ensures it stays on-brand, performant, and conversion-ready while the agent is computing in the background?
That is not a criticism of commercetools. It is the next open question the field has not yet closed.
The experience layer is not a downstream problem
There is a temptation to treat the experience layer as "the thing that comes after." Backend agents deliver the data, the storefront renders it. Sounds straightforward.
The reality in production systems is more complicated. The experience layer is what carries brand identity, conversion rate, and customer trust. It is where campaign timing, A/B tests, and personalisation converge. When three agents are simultaneously writing into this layer - or indirectly influencing it - that layer needs its own governance logic.
That is the core of what we build at Laioutr: an Agentic Frontend Management Platform that treats the frontend layer as an independently governable layer - backend-agnostic, but not backend-indifferent. Compatible with autonomous backends, but not dependent on their governance decisions.
The platform connects 50+ backends, delivers a median LCP of 1.2 seconds, and returns control of the storefront layer to marketing teams - no developer ticket, no deployment cycle required.
Agentic discovery: the unsolved problem of experience governance
A lot of the conversation at K5 today is about "AI-native discovery." A buyer asks ChatGPT: "Which treadmill under 1,500 euros is worth buying?" The agent responds with a product suggestion and a link. The merchant gets visibility - if they have the backend infrastructure for it.
But who controls the page that link leads to? Who decides what the user sees when they arrive from an agent flow onto a storefront page? This is a different kind of traffic than organic or paid - context is missing, session history is missing, classical personalisation signals are absent.
Shoptalk Europe 2026 already pointed in this direction, showing where commerce architectures are heading across the industry. What I see at K5 today is the DACH version of that conversation - concrete, pragmatic, with the next open problem already visible on the horizon.
For anyone who was wondering before K5 which frontend questions really matter in this context, the pre-event piece on the K5 ecosystem is where this live take begins - this post is the arc from preparation to floor reality.
What the field has not yet answered
I am on the floor until 15:00. The sessions I am still planning to attend today all revolve around the backend side: agentic architectures, AI hubs, autonomous pricing.
What I have not found yet - and what I am curious to see whether it still comes - is a session that addresses the governance of the frontend layer specifically, for when agents take over discovery and product presentation.
Anyone who solves only the backend problem in the agentic commerce conversation has half the architecture. The other half is the experience layer: the question of who controls it when agents decide the destination.
That is my open question after Day 1 at K5 2026.
Marcel Thiesies is Co-Founder and CEO of Laioutr. He writes from direct experience about composable commerce, frontend architecture, and the questions that arise at the intersection of agentic AI and merchant-controlled experience. LinkedIn
Further reading
- Composable Visual Page Builder - making the experience layer visible and governable