Every composable vendor pitch carries the same promises. Better customer experience, faster iteratio…
Native Shop System Frontends Compared: Hydrogen, Spartacus, FastStore and the Limits of Built-in Storefronts
Every serious e-commerce platform now ships its own frontend solution. Shopify has Hydrogen, SAP Commerce Cloud comes with Spartacus, commercetools sells commercetools Frontend (formerly Frontastic), VTEX has FastStore, BigCommerce bets on Catalyst, Adobe Commerce ships PWA Studio plus Edge Delivery, Shopware offers Shopware Frontends. On the surface this sounds straightforward: pick a backend, take the matching native frontend, ship.
In practice, European brands hit three walls with this logic time and again: the frontend is locked to one specific backend, the custom build takes six to twelve months, and marketing teams need an engineering ticket for every landing page. That is exactly why a new category has emerged: agentic frontend management platforms that work independently of the underlying shop system and bundle storefront rendering, visual studio, UI library and AI operations into one platform.
In this article we look at which native frontend solutions the major shop systems offer worldwide, where their limits sit, and at what point a composable frontend platform becomes the more sustainable choice.
Which Shop Systems Ship Which Frontend Solution
We focus on the twelve platforms with the largest share in Europe and globally. A complete list including open source and SMB platforms appears at the end of this article.
Shopify and Shopify Plus ship Liquid themes and Online Store 2.0 for the classic storefront, plus Hydrogen (React) and Oxygen Hosting for brands that want to run a headless stack on Shopify. Hydrogen is tightly coupled with Storefront API, Metaobjects and Shopify-specific data structures.
BigCommerce offers Stencil themes for classic storefronts and Catalyst, an official Next.js reference storefront for composable setups. Catalyst is relatively new in the market and positions itself as BigCommerce's headless answer.
Adobe Commerce / Magento combines Luma themes (PHP-driven) with PWA Studio (React-based) and Edge Delivery Services, which Adobe has been expanding since 2024 as an additional performance layer. The complexity of this stack is high because three rendering strategies coexist.
Salesforce Commerce Cloud offers SFRA (Storefront Reference Architecture) as a classic storefront and Composable Storefront / PWA Kit as a headless path. Both are tightly coupled to Salesforce identities and the customer data model.
SAP Commerce Cloud ships Spartacus as the official composable storefront. Spartacus is Angular-based, focuses on B2B and enterprise setups and typically requires deep SAP Hybris expertise on the team.
commercetools sells commercetools Frontend after the Frontastic acquisition, a composable storefront with studio and backend integration for commercetools. The stack is primarily focused on its own backend provider.
Shopware offers two worlds: the Shopware 6 Default Storefront (Twig/Symfony) for classic setups and Shopware Frontends (formerly Shopware PWA) for composable brands. The latter is React-based and targets headless projects.
VTEX provides VTEX IO and FastStore (built by the IO team), a Next.js-based composable storefront solution. FastStore is performance-optimized and used widely across Latin America.
Spryker ships Yves as the default frontend (Twig) plus a Composable Frontend Reference designed for modern B2B and enterprise architectures.
Elastic Path offers Elastic Path Studio plus a Composable Frontend Reference Storefront for brands entering its composable stack.
Saleor ships a Saleor Storefront Reference on Next.js plus Saleor Apps for custom extensions.
Medusa runs on a Medusa Next.js Starter combined with Medusa Admin, marketed as an open source stack.
Beyond these, you find WooCommerce with Storefront theme and WooCommerce Blocks, Centra with custom themes, Intershop with its own PWA, OroCommerce for B2B, Kibo Commerce, Vendure with storefront starters in Angular, React, Vue and Qwik, Sylius with Symfony Twig, plus SaaS platforms such as Wix Commerce, Squarespace Commerce, Ecwid and JTL Shop, each with its own theme engine.
Where All Native Frontends Hit the Same Walls
As different as these frontend solutions look, the problems European brands run into are remarkably similar. We see the same patterns in every sales conversation and every architecture review.
Backend lock-in by default
Hydrogen only works with Shopify, Spartacus only with SAP Commerce Cloud, FastStore only with VTEX, Catalyst only with BigCommerce, commercetools Frontend only with commercetools. As soon as you run multi-brand with different backends, internationalize, or plan a backend migration, you have to rebuild the frontend or run multiple frontends in parallel. For brands that are on Shopify today and want to migrate to Shopware or commercetools tomorrow, this is a risk that can burn frontend investments.
Dev-first architecture
Native frontends are essentially code repositories. A marketing person wanting to ship a new promo landing page typically files a ticket with engineering, waits for a sprint, waits for a deploy, and then negotiates a pull request review. Theoretically this works, in practice it delays campaigns by weeks.
Implementation marathon
Custom builds on Hydrogen, PWA Studio, Spartacus, Catalyst, FastStore or Shopware Frontends typically run six to twelve months. Brands need an engineering team experienced with the respective framework (React, Next.js, Angular, Vue, Symfony Twig, depending on the platform). During this build phase no storefront value is created, no conversion lift, no new brand experience. The investment only pays off after go-live, often after quarters.
Missing AI integration at the frontend layer
Native frontends ship with very few agentic AI features. Layout suggestions, automated conversion optimization, AI-driven content synchronization across markets or a storefront-wide agent are custom development in native frontends. Anyone needing AI as a platform feature looks for it in vain in Hydrogen, Spartacus or FastStore.
Rarely European compliance out of the box
Most of the platforms named above come from the United States or are sold globally. EU hosting in Frankfurt, GDPR-compliant data processing agreements, WCAG 3.0 readiness and German-language support are the exception. For brands in regulated industries (financial services, public sector, DORA-affected companies) this is often not enough. The compliance gap is then closed with custom setups, which pushes TCO up further.
Multi-brand and multi-market are custom
Native frontends are typically built for one storefront per setup. Brands with ten labels or ten markets run ten storefronts with ten code bases, ten deployments and ten maintenance tracks. A central platform view in which one marketing person manages all brands does not exist in the native frontend model.
When a Native Frontend Is Enough and When It Is Not
Native frontends are not the wrong choice per se. There are setups in which they are exactly right:
- One brand, one backend, an established engineering team whose primary job is building the storefront.
- Highly individual storefronts with unique rendering logic that no platform could capture.
- Setups in which the engineering team actively wants to build competitive advantage in the frontend and consciously keep the platform close to the backend.
But as soon as one of the following points applies, the equation tips:
- Multi-brand or multi-market strategy with multiple backends.
- Marketing teams expected to publish landing pages, campaigns and promotions independently.
- Time-to-market expectations of weeks instead of months.
- AI-driven storefront operations as a strategic lever.
- Strict EU compliance, GDPR, DPA, WCAG 3.0 and European-specific support.
In these cases, moving to an agentic frontend management platform pays off.
The Category Closing the Gap: Agentic Frontend Management
An agentic frontend management platform is a platform layer above your commerce backend that bundles the entire storefront rendering, visual page building, UI components and AI operations in one place. Unlike Hydrogen or Spartacus, it is backend-agnostic and brings a visual studio in which marketing and content teams work without engineering tickets.
This is exactly the category where Laioutr is positioned. We connect natively to more than nineteen commerce backends, including Shopify, Shopware, commercetools, Adobe Commerce, SAP Commerce Cloud, VTEX, BigCommerce and Salesforce Commerce Cloud. Storefronts run on themes and a complete UI library. Marketing teams build landing pages and product worlds directly in Laioutr Studio. Larry, our AI agent, takes over storefront operations, from layout suggestions to conversion optimization. EU hosting in Frankfurt, standard DPAs, WCAG 3.0 readiness and German-speaking founder support are included as platform standard.
For a closer look at how this works inside your stack, see the overview here: Agentic Frontend Management Platform.
The Next Step: Composable Digital Experience Platform
Frontend alone is no longer enough today. E-commerce brands need a platform that orchestrates storefront, content, commerce, personalization and AI in a single system. A Composable Digital Experience Platform (Composable DXP) is the answer to what monolithic DXPs (Adobe Experience Manager, Sitecore, Acquia) had to deliver, but without their heaviness in modern composable architectures.
Laioutr's Composable DXP combines the agentic frontend management layer with native connections to headless CMSs (Storyblok, Contentful, Hygraph), commerce backends, personalization tools and AI workflows. Brands get a platform that scales with their composable strategy instead of locking them into a monolithic DXP cage.
For more on how Composable DXP works and what role Laioutr plays in it, see: Composable Digital Experience Platform.
Bottom Line: Native Frontends Are a Tool, Not a Platform
Hydrogen, Spartacus, FastStore, Catalyst, commercetools Frontend, PWA Studio, Shopware Frontends and the other native frontend solutions of the major shop systems are mature tools. For brands with the right setup size, a strong engineering team and a clear single-backend setup, they work. As soon as multi-brand, multi-backend, marketing self-service, time-to-market in weeks, AI-first or European compliance enter the picture, they fall short.
European e-commerce brands positioning themselves strategically today increasingly choose an agentic frontend management platform over a native frontend solution. The platform logic brings composable commerce into a form that works for marketing, engineering and compliance at the same time.
Quick Reference of All Native Shop System Frontends
Enterprise and mid-market globally: Shopify (Hydrogen, Liquid), BigCommerce (Catalyst, Stencil), Adobe Commerce (PWA Studio, Edge Delivery, Luma), Salesforce Commerce Cloud (Composable Storefront, SFRA), SAP Commerce Cloud (Spartacus), commercetools (commercetools Frontend), Shopware (Shopware Frontends, Default Storefront), VTEX (FastStore, VTEX IO), Spryker (Composable Frontend, Yves), Elastic Path (Studio), WooCommerce (Storefront theme), Centra, Intershop, OroCommerce, Kibo Commerce.
Open source and modern headless: Saleor (Saleor Storefront), Medusa (Medusa Next.js Starter), Vendure (storefront starters), Sylius (Symfony Twig), PrestaShop, OpenCart, nopCommerce.
SaaS and SMB: Wix Commerce, Squarespace Commerce, Ecwid, Big Cartel, Volusion, Lightspeed eCom, JTL Shop, xt:Commerce, Gambio.
Asia focus: Tmall, JD.com, Rakuten Ichiba, Cafe24, NHN Commerce.
All data is based on publicly available information, sales conversations with European e-commerce brands and our own platform tests. Stand: April 2026. The feature sets of the native shop system frontends listed above evolve continuously, so when in doubt please verify against the vendor documentation for the current state.