Salesforce Storefront Next + Contentful Acquisition 2026: What It Means For Shopify Hydrogen

Two Salesforce announcements ten days apart. Last week the company launched Storefront Next — a React-based storefront pilot for B2C Commerce with click-based setup, hosted runtime, and an agentic developer toolkit. On June 1 it signed to acquire Contentful, the API-first headless CMS used by 4,800-plus enterprises. Read together, this is Salesforce stitching a full "Headless 360" stack — storefront, content, and Agentforce-driven personalization — and aiming it directly at Shopify Hydrogen's positioning, not at its own legacy SFCC base.

John Surdakowski, founder of Avex, called it on LinkedIn yesterday in one of the sharper reads on the launch: this is not Salesforce trying to replace SFCC. It's Salesforce trying to give brands an alternative to Shopify on the dimensions Shopify has won on for years — speed, simplicity, and developer experience.

For Hydrogen teams, this isn't an immediate threat. The product is in pilot, the acquisition won't close until Q3 of Salesforce's fiscal year 2027, and the integration story still has to be built. But it's the most credible competitive signal Hydrogen has faced this year, and Hydrogen teams running enterprise pitches in Q3 and Q4 need to know what they're up against.

What Storefront Next actually ships with

The product launched in pilot in late May 2026. The technical surface, from the official GitHub template and the Salesforce Watson Weekly walkthrough with Lennart Stevens, VP of Product Management for Agentforce Commerce:

1. The stack is genuinely modern

React 19, React Router 7, TypeScript, Tailwind CSS 4, Shadcn UI components, server-side rendering. Node.js 24, pnpm. This is the same generational stack Hydrogen is on today — React Router 7, Vite, server-first rendering, modern React. The architectural envy that drove Salesforce customers toward Hydrogen is no longer a clean differentiator on the front-end framework alone.

2. Click-based provisioning in Business Manager

The headline pitch: in under 30 minutes, a merchant operating Business Manager can stand up a storefront template, hosted on Salesforce Managed Runtime (MRT), with connected APIs and a GitHub repository created for them. Type a name, click next, get a storefront. This is exactly the onboarding curve Shopify has used as a competitive moat since the original Storefront API launched.

3. Managed Runtime as the hosting layer

Storefront Next runs on MRT, Salesforce's hosted edge runtime — their answer to Oxygen. Same architectural shape: hosted, edge-deployed, abstracted from the developer. Everything routes through SCAPI (Salesforce Commerce API), the equivalent of Shopify's Storefront API and Customer Account API layered together.

4. The Agentic B2C Developer Toolkit is the real bet

The toolkit connects Storefront Next directly to OpenClaw, Agentforce Vibes (Salesforce's in-house coding agent), GitHub Copilot, and other AI coding assistants. The framing in Stevens' walkthrough: "agentic coding is the default" for new Storefront Next customers. Templates ship with Figma associations so designers can export tokens and developers can pick up immediately. The whole product is built around the assumption that the implementation team is AI-augmented from day one.

5. Page Designer embedded by default

Salesforce's drag-and-drop visual editor is bundled into the experience, with React components and content blocks reusable across the storefront. This is the equivalent of pairing Hydrogen with a visual builder — except Salesforce is shipping it as one product, not as a marketplace ecosystem.

What the Contentful acquisition adds

Signed June 1, expected to close in Q3 of Salesforce's fiscal year 2027, subject to regulatory approval. The strategic logic, in plain terms:

Contentful fills the content-layer hole in Salesforce's Headless 360 vision. Agentforce wants to assemble 1:1 personalized experiences in real time across channels — email, web, mobile, kiosk, agentic shopping surfaces. To do that, agents need a structured, API-queryable content layer. Salesforce had Customer 360 (data), Data 360 (analytics), Agentforce (agents), Storefront Next (presentation) — but no native content engine. Contentful slots into that hole with 4,800-plus enterprise customers, an API-first architecture, and 12 years of composable-CMS execution.

For Storefront Next specifically, this means a future-state where the content model, the storefront, the runtime, the APIs, and the AI agent layer are all native Salesforce — no integration tax, no separate vendor relationships, no schema-mapping work between systems. That's the value proposition.

Whether it materializes cleanly is a different question. Contentful's customer base is going to spend the next 12 months asking whether contract terms, EU data sovereignty, API stability, and pricing will hold through the integration. Several CMS-industry analysts (CMSCritic, Cosmic JS, CrafterCMS) have already flagged the integration uncertainty. The acquisition is a strategic signal, not a shipped capability.

How this compares to Shopify Hydrogen today

A clean side-by-side, on the dimensions that actually matter for an enterprise decision:

Time to first storefront

Storefront Next: Click-based setup in Business Manager. Storefront template, hosting, APIs, GitHub repo in under 30 minutes per Salesforce.

Hydrogen: npx @shopify/create-hydrogen scaffolds in under 5 minutes; deploying to Oxygen or Vercel adds another 15-30. The Hydrogen CLI advantage is still real, but Storefront Next has closed most of the gap. The remaining differentiation is that Hydrogen developers can deploy anywhere; Storefront Next is MRT-locked at present.

Runtime architecture

Storefront Next: Salesforce Managed Runtime, hosted edge, opinionated.

Hydrogen: Oxygen by default but deploys cleanly to Cloudflare Workers, Vercel, or anywhere Node.js or workerd runs. Hydrogen wins on portability.

Content modeling

Storefront Next (current): Page Designer for visual layout, B2C Commerce metadata for product attributes. Limited compared to a real headless CMS.

Storefront Next (post-Contentful): Native Contentful integration, projected. Full composable content modeling with content types, references, localization, asset management.

Hydrogen: Metafields for structured product content (very strong), pair with Sanity, Contentful (today), Storyblok, or Builder.io for editorial. The Shopify metafield system is mature and well-instrumented.

Agentic readiness

Storefront Next: Agentic B2C Developer Toolkit ships with the product. Agentforce integration is the headline.

Hydrogen: Shopify Hydrogen Skills for Claude Code, Cursor, Copilot, Windsurf, Gemini CLI. Storefront Catalog MCP implements UCP since April 22, so every Hydrogen storefront is an agent-readable endpoint by default. Agent-driven merchant operations through Perplexity Computer and ChatGPT Operator are already real for Shopify Admin. Hydrogen's agentic story is more mature and more distributed; Storefront Next's is more centralized and more tightly coupled to Salesforce's own AI stack.

Pricing and TCO

Storefront Next: Pilot/beta, pricing not yet public. SFCC platform pricing has historically been enterprise-tier with revenue-share components; whether Storefront Next gets a more aggressive pricing model is the open question.

Hydrogen: Free framework. Oxygen included with Shopify Plus. Shopify Plus base pricing is published and competitive against SFCC by an order of magnitude on most deal sizes.

Ecosystem depth

Storefront Next: New. Component library is what Salesforce ships plus what early pilot customers build. Page Designer ecosystem exists but is SFCC-specific.

Hydrogen: Three years of community packages, multiple production themes, every major headless CMS integrated, multi-thousand-package npm ecosystem, and three years of agency expertise across firms running serious Hydrogen builds. This is Hydrogen's biggest moat for the next 18 months.

Why this matters for Hydrogen teams in the next two quarters

Three concrete reads:

Enterprise pitches in Q3 and Q4 will start to surface Storefront Next as an alternative. Sales teams selling Hydrogen builds to brands evaluating SFCC migration paths will hear "we're evaluating Storefront Next too" in deals starting around August. The Hydrogen pitch needs the side-by-side ready. The strong arguments hold: portability, pricing, ecosystem maturity, agent-readiness today versus future. But the React-Router-7-on-edge-runtime argument is no longer asymmetric.

The Contentful question becomes active for Hydrogen builds shipping in 2026. Teams currently shipping Hydrogen + Contentful builds need to think about what Salesforce ownership means for their roadmap. The acquisition won't close until Q3 FY27, the platform contractually continues to operate as Contentful, but enterprise customers on multi-year contracts are going to ask hard questions. Sanity, Storyblok, Builder.io, and Hygraph are the obvious alternatives. Hydrogen teams should be ready to recommend a CMS migration path if a client raises the concern.

Salesforce's "Headless 360" framing is a competitive narrative Hydrogen needs to counter. The pitch — storefront plus content plus customer data plus agents in one stack — is genuinely compelling for risk-averse enterprise buyers who want one neck to choke. Hydrogen's counter-narrative is the opposite: best-in-class at every layer, portable across runtimes, no vendor lock-in, and a partner ecosystem that's already shipping enterprise builds at speeds Salesforce hasn't matched in a decade. Both narratives are real. Hydrogen's is more credible today but needs to be defended in deal conversations.

The bottom line

Storefront Next is a real product. The Contentful deal is a real strategic move. Read together, they signal that Salesforce has finally stopped fighting on SFCC's terms and started building a Shopify-shaped competitor. The combined stack — once it actually ships and integrates, somewhere in 2027 — will be the most credible alternative to Hydrogen on the enterprise side of the market.

Hydrogen wins on ecosystem, portability, pricing, and agent-readiness today. Those advantages are durable for the next 12 to 18 months. The teams that lose deals to Storefront Next in 2027 will be the ones that didn't sharpen the comparison in 2026.

If your team is pitching a Hydrogen build against SFCC or Storefront Next, or you're already on Hydrogen + Contentful and want to think through CMS migration paths before the acquisition closes, the Weaverse team takes on Hydrogen engagements end-to-end — including platform-selection consulting, headless CMS migration, and competitive-positioning support for enterprise pitches. Senior engineers, fast scoping, deep platform fluency across the moving Shopify, Salesforce, and headless commerce landscape. Talk to us →