Shopify and Vercel are rebuilding Hydrogen as an open, runtime-agnostic foundation. Hydrogen now dep…
Spree BBQ 2026: What DACH Mid-Market Is Actually Discussing
Tonight at 18:00, Dock 10 Berlin. The Spree BBQ 2026 kicks off, and Laioutr is there as co-sponsor. What we hear in the conversations on the ground is not industry background noise. It is a clear read on where the DACH mid-market actually stands in 2026.
Tomorrow the K5 Future Retail Conference opens its doors (June 23 and 24, ESTREL Berlin) - the summit of the German retail scene, with 250+ speakers and more than 200 exhibitors. The Spree BBQ is the informal evening before: smaller, more direct, no keynote theater. That is exactly why you hear what is actually on the table.
Three topics that are genuinely in the room tonight
1. "When is Composable the right move for us?"
This is the most common question in the DACH mid-market in 2026. Not "What is Composable Commerce?" - that education phase is largely done. The conversation has moved to timing and fit.
What we consistently see at events like the Spree BBQ: mid-market decision-makers understand composable architectures. They know that decoupled systems bring flexibility. What they are looking for are concrete signals - when is their own situation ready for that step?
Our answer is not a formula. But there are patterns: shops where every frontend change requires a developer ticket. Marketing teams that have to freeze Black Friday campaigns weeks in advance. Companies running multiple backend systems in parallel, each with its own theme. These are the situations where a decoupled frontend layer makes a real operational difference - not as an architectural ideal, but as a practical lever.
If you are asking what Composable Commerce means for your specific stack, the starting point is understanding what a Composable Headless Frontend actually changes day to day - not on paper, but in operations.
2. The backend question is shifting
For years, the first question was: which backend? Shopware, commercetools, OXID, Spryker - backend decisions dominated roadmaps.
In 2026 the conversation is flipping. The frontend layer is becoming the central control plane for customer experience, campaign speed, and conversion optimization. The backend stays relevant - it is the transactional nervous system. But it is no longer the market differentiator.
At the Spree BBQ we talk to teams that are right in the middle of this transition: they have solid backend investments (often Shopware or commercetools), they want to modernize the frontend layer without touching the backend. That is the core use case of our Agentic Frontend Management Platform - not as a replacement for existing backends, but as a decoupled experience layer on top.
The broader industry direction on this came through clearly at Shoptalk Europe 2026, and what that event revealed about where commerce architectures are heading applies directly to the conversations happening in Berlin tonight.
3. AI agents: curiosity without panic
At the Spree BBQ, AI is a topic - but in a different register than at US conferences. The DACH mid-market is curious, not euphoric. The questions are practical: what changes in my frontend when agents start executing purchases? How do I make sure my product data is structured enough for AI buyer flows?
Those are the right questions. And they point precisely to why the frontend layer matters more in 2026, not less. Anyone who wants to serve AI agents - whether as shopper agents or B2B buyer agents - needs structured data, clean APIs, and a storefront layer that renders deterministically. That is not a 2027 problem. It is a now problem.
This is where the Composable Digital Experience Platform sets the right architectural frame: backend-agnostic, API-first, ready for the next stack decision.
What this means for your frontend
The Spree BBQ is not a conference event with action items on slides. But the conversations tonight show a clear pattern: the DACH mid-market is in evaluation mode. Composable is no longer a buzzword - it is a planning variable.
The question is not whether, but how the move toward a decoupled frontend architecture plays out - and whether it raises or lowers operational complexity.
Our position on this is straightforward: the right entry point is frontend-first, not big-bang replatforming. You modernize the experience layer without touching the backend. Your team gains speed - marketing can build pages without a developer ticket, engineering can focus on backend stability.
If you want a preview of what the K5 stage will cover tomorrow with 250+ speakers, our team has already mapped out which three frontend questions actually matter at booth #37.
Our take after tonight
The DACH mid-market is more sophisticated than its reputation. The conversations at the Spree BBQ are pragmatic, sometimes skeptical, always concrete. That is a good thing.
What is sometimes missing is not understanding of Composable Commerce - that understanding exists. What is missing is a clear first step: where do you start without putting the running business at risk?
The answer is in the frontend. Not in the backend, not in the CMS, not in an 18-month greenfield project. The frontend layer is the movable part - the part you can modernize while everything else keeps running.
That is the message we bring to Dock 10 tonight. And the one we continue at K5 tomorrow.