Intershop PWA and Angular Storefront: Modernizing the B2B Frontend

Intershop Commerce Management (ICM) is one of the most established B2B commerce backends in the DACH region, especially for mid-market manufacturers and distributors with complex sales structures. Many Intershop customers run the official PWA reference storefront on top of it, an Angular application connected directly to the ICM REST API. That is a solid starting point, a documented reference implementation, an established enterprise framework, direct API access to price lists, customer organizations, and order history. The question that comes up less often in Intershop teams: who maintains that Angular storefront in month 18, when the next Angular major version ships, a new customer group needs its own pricing rules, or marketing wants three new landing pages for trade show season at once?

The starting point: a PWA reference storefront on Angular

Teams starting with Intershop, or already running it in production, know the PWA reference storefront as the entry point: an Angular application that talks to the ICM REST API and ships B2B basics out of the box, product catalog, cart, checkout, customer accounts with multi-tier organization structures. For engineering teams with Angular experience already in house, that is a fair starting point. You get a reference implementation instead of a bare API, TypeScript typing for ICM entities, and you do not have to derive the shape of the B2B data model yourself.

Everything beyond that, custom price lists per customer group, approval workflows for orders, quote management, guided selling for complex product configurations, lives entirely in your own Angular code from that point on. That is the norm on Intershop projects, not the exception, B2B commerce runs on exactly these special rules.

What the custom Angular build actually costs

The part that rarely makes it into the project plan only shows up once you are in production: from the moment your team customizes the reference storefront, the entire maintenance burden is yours, permanently.

• Angular major upgrades need to be tracked, applied, and tested against your custom code manually
• ICM REST API version bumps mean breaking-change reviews in your own storefront code
• Security patches for npm dependencies land in your backlog, not Intershop's
• Every new pricing rule or customer-group configuration needs a pull request and a deployment
• Marketing cannot build campaign pages or product-line landing pages themselves, because there is no visual editor, only code
• New ICM features Intershop ships after your build point need to be rebuilt manually instead of arriving automatically

This is not an Intershop-specific issue, every independently customized reference storefront carries this property built in. Still, it is worth pricing in honestly, before the Angular build becomes the repository with the biggest technical debt pile in the company.

Laioutr as the managed answer for Intershop B2B frontends

Laioutr modernizes exactly this layer, without putting Intershop as a backend up for debate. Our Composable Headless Frontend takes over the storefront layer, while Intershop Commerce Management stays fully in place as the backend, pricing logic, order processing, catalog management, and customer organizations keep running there unchanged. The difference sits at the operating layer: instead of maintaining an Angular reference storefront yourselves, you connect Intershop through our Orchestr data layer into the frontend. Product, pricing, inventory, and customer data flow, normalized, into our component schema, the same data points the ICM REST API already exposes, just without your team running that connection long-term.

The result is a Frontend as a Service: CI/CD, hosting, framework upgrades, and security patches are platform work, not your team's sprint work. Developers keep full access at the component layer for B2B edge cases, minus the upkeep of the storefront foundation.

How the technical connection works

Technically, the flow stays close to what the ICM REST API already sets out to do. The Orchestr layer talks to the Intershop Commerce Management API, pulls product data, price lists, availability, and order status, and maps it onto our unified component schema. PDP, PLP, and checkout components in the frontend expect the same data shape, regardless of whether Intershop, Shopware, or commercetools sits behind it, the same advantage that carries our decoupling story on the backend side. Start with Intershop today, and if you evaluate a second backend for a subsidiary a few years out, you do not have to rebuild the frontend for it.

For engineering teams, that means concretely: B2B-specific Intershop fields, custom pricing rules, multi-tier approval workflows, request-for-quote flows, get connected through custom resolvers in the Orchestr layer, instead of being rebuilt inside an Angular fork. The basics, product catalog, cart, checkout, customer accounts, already exist as components and do not need to be re-derived from the ICM API.

Who does what: engineering and marketing

The role split stays clean. Engineering teams define components, connect Intershop-specific data points through the Orchestr layer, and extend the component library with B2B specifics, tiered pricing, approval flows, customer-specific assortments. Marketing works in parallel in the Studio editor, composes product-line pages, swaps trade show banners, launches landing pages, all without a pull request and without waiting for a deployment window. A concrete example: when a new customer group gets its own pricing rules in Intershop, an engineering team connects that field once in the Orchestr layer, and the component is then available to every storefront using it, without marketing waiting on a second sprint.

With an independently customized Angular fork, that split does not exist, every change runs through code, whether it is content or structure. For B2B teams with trade show seasonality, channel-specific catalogs, or frequent price changes, that is the difference you feel every week. Teams decoupling backend replatforming from frontend modernization see similar patterns, more on that in B2B storefront without backend replatforming.

Decision framework: build it yourself, go managed, or custom build

Three situations, three sensible answers.

You have a well-staffed Angular team of your own and want full control over every line of code, with no platform layer in between. Extending the PWA reference storefront yourselves is the direct answer, with the maintenance load as a trade-off you are taking on knowingly.

You want to shorten time to launch, and marketing should be able to build product-line and campaign pages themselves, without tying up developer capacity permanently. Laioutr as a managed frontend layer over Intershop is the direct path, predictable in effort, without having to swap out Intershop as your backend.

You are comparing the frontend options for your Intershop setup at a broader level. We covered the wider entry point into headless modernization for B2B in Modernize Intershop Frontend: Headless for B2B. This article goes deeper specifically on the Angular storefront question and what the managed alternative means in practice.

Takeaway

Intershop stays the B2B commerce backend in this picture, unchanged in its role for pricing logic, order processing, and customer management. What changes is the frontend layer: instead of maintaining an Angular reference storefront yourselves long-term, you can hand it to a Frontend Management Platform built exactly for that job. More on the connection in detail: Headless Frontend for Intershop. The usual first step is a technical discovery call, where we map out together which ICM data points your B2B storefront actually needs today.