On June 23, commercetools announced two things worth paying attention to: commercetools for Builders and a Commerce Integration Layer. The headline: enterprise commerce that used to take months should now stand up in days. Describe instead of code, one central place for integrations instead of weeks of glue code.

Our take: this is the right direction. Anyone who works in commerce knows the pain of long implementation cycles. When an established platform moves the starting point from “project plan” to “first prompt,” that is a good signal for the whole market.

But one question stays open, and it decides whether the speed you gain actually reaches your customers: where does the experience get built?

What commercetools announced

A short recap so you can place it:

• commercetools for Builders lets teams describe storefronts, catalogs, and checkout experiences instead of building them from scratch, supported by AI development tools like Claude Code, v0, and Cursor. Built on the API-native platform, Sphere.
• Commerce Integration Layer centralizes connections to third-party systems (search, content, promotions, tax) at a single point, so teams stop rewiring the same integration logic in every project.

Both target the same bottleneck: the time between idea and go-live. And both work primarily at the backend and platform layer.

The part that is right: speed and integration are real bottlenecks

Long build times cost twice: once in budget, once in market opportunity. And wiring up search, content, promotions, and tax is genuinely one of the stickiest parts of any project. commercetools tackling exactly that is reasonable, and for existing customers it is a welcome relief.

For you as a product or marketing owner, though, this does not mean “problem solved.” It means the backend build gets faster. The storefront, the thing your customers actually see and use, is its own layer with its own demands: performance, brand consistency, accessibility, SEO, fast campaign iteration. That layer does not finish itself just because the backend stands up in days.

Where the experience gets built: in the frontend

A Frontend Management Platform (FMP) is exactly the layer that sits between your commerce backend and your customers. It is where product data becomes an experience that sells. An FMP like Laioutr does two concrete things:

1. The storefront ships in days, not next sprint.

Marketers compose pages directly in the Visual Page Builder, from a curated UI library with your brand theme. No banner ticket stuck in the dev queue for a week. The median for guided rollouts is under 14 days. And the key point: this storefront runs on your commercetools backend just as it runs on Shopware, Shopify, or Magento. More on our page about the headless frontend for commercetools.

2. The day-to-day operation goes agentic, not only the build.

commercetools leans heavily on AI for the build side and the shopper side. The other half is the daily operation of your storefront, and that is exactly where our operator layer sits. Larry and the Laioutr Frontend Agents take over recurring frontend work: generating content variants, maintaining SEO and GEO markup, running A/B tests, tuning performance. That happens in content management with the Content Agent and in agentic A/B testing, not as a developer ticket. Building agentically is good. Operating agentically is what gives your team time back week after week.

Integration without the rebuild trap

The Commerce Integration Layer addresses a real problem: integration logic that gets rebuilt in every project. On the frontend side we know the same pain, and our answer is the Laioutr App Store: prebuilt connectors for search, payment, analytics, and more that you attach with a click instead of rewiring per project. We wrote about the effect on time-to-stack here: Composable commerce without the maintenance trap.

One point worth weighing in your architecture decision: commercetools Frontend is tightly bound to the commercetools backend. That is the fastest path if you commit to commercetools for the coming years. If you want to keep the backend choice reversible, the frontend layer at Laioutr is deliberately decoupled from it: one frontend, many backends, no rebuild when you switch. This is not a knock on commercetools, it is a question of how firmly you want to commit.

What this means for your team

If you are evaluating right now, these are the three questions that matter:

• Speed to build is solved or on its way to solved across many platforms today. The difference shows up after that.
• Speed to operate is the underrated half. How fast can your marketing team ship a campaign, test a variant, add a market, without a dev dependency?
• Reversibility of the architecture decides how expensive your next backend decision becomes.

The Agentic Frontend Management Platform is built for all three. If you are still working out what an FMP is and when it pays off, start here: What is a Frontend Management Platform.

Keep reading: Agentic-ready frontend and the deterministic render contract and 3 frontend questions to ask at Booth #37.

Ready to make the experience layer as fast as your backend? Take a look at the Agentic Frontend Management Platform or compare pricing. Your storefront, any backend, fully in your hands.