TYPO3 is deeply rooted in the DACH enterprise world, but the frontend often hangs on Fluid templates…
Modernize Intershop Frontend: Headless for B2B
A headless Intershop frontend separates the storefront from the Intershop Commerce Management layer (ICM): catalog, pricing logic and B2B rules stay in Intershop, while you build the presentation layer independently on top. For enterprise B2B merchants, this is the way to get a modern frontend without touching the deep ICM investment.
What "Intershop headless" means
With its PWA (Angular), Intershop already offers a decoupled storefront approach. Headless in the broader sense means your frontend talks to the ICM REST and GraphQL APIs but is not bound to the shipped Angular stack. You choose the presentation layer freely and compose it from interchangeable building blocks. We call this a composable frontend, because the ICM strength stays in the backend and the storefront becomes modular.
The problem many B2B merchants hit today
Enterprise B2B storefronts carry a lot of logic: customer-specific pricing, approval workflows, quote processes, punchout. The shipped frontend stack is powerful, but changes are effortful and tie up engineering for months. At the same time, replacing ICM is not an option for most, because the B2B processes and integrations live there. What needs modernizing is the layer buyers use every day.
How a Frontend Management Platform solves it
A Frontend Management Platform (FMP) sits as a frontend layer on top of ICM. Data access runs through a unified data layer that normalizes the Intershop APIs, so your components speak a fixed model instead of the raw API. Marketing and sales build campaign and portal pages in Studio with live preview, while engineering defines the components and guardrails. Performance and accessibility are built in: Core Web Vitals optimized in the layer, base components WCAG 3.0 ready, EU hosting selectable.
What you gain
- New portal page - Classic ICM frontend build: developer sprint; With a composable frontend: hours in the editor
- Backend coupling - Classic ICM frontend build: frontend tied to ICM release; With a composable frontend: frontend independent, ICM stays
- Performance - Classic ICM frontend build: project-dependent; With a composable frontend: LCP 1.2s median (field data Q2 2026)
- Accessibility - Classic ICM frontend build: manual audit; With a composable frontend: WCAG 3.0 ready out of the box
FAQ
Do I have to replace Intershop?
No. ICM stays the backend for catalog, pricing and B2B processes. Only the storefront becomes standalone.
How long does it take?
A guided migration runs under 14 days on median, depending on the number of your B2B integrations.
Do punchout and customer-specific pricing keep working?
Yes, they stay in ICM. The storefront pulls them through the data layer.
Next steps
If your Intershop frontend is slowing down changes and a backend switch is off the table, a decoupled storefront is the direct path. Book a 30-minute demo and we will look at your ICM integrations.
More from the Laioutr Platform
About the author: The Laioutr Team builds the Frontend Management Platform for Composable Commerce, EU-hosted and agent-ready.