Shopify Hydrogen and Contentful: the case for content-driven commerce

Two teams. One Shopify admin. Someone always waiting.

Your editorial team is building a seasonal campaign page, rich imagery, long-form storytelling, curated product pairings. Your commerce team needs to update pricing and product variants before the weekend sale. Both are queued behind the same developer, working within the same theme constraints, because that is how standard Shopify stores work: product data and editorial content live in the same place, managed by the same people, under the same limitations.

You chose Shopify because it works. The checkout infrastructure, the app ecosystem, the reliability, these are real strengths that most commerce teams should not walk away from lightly. But if your brand is starting to feel constrained, if your editorial ambitions are consistently outpacing what your theme can do, there is an architecture that separates these problems without abandoning the commerce platform you rely on.

This article explains how Shopify Hydrogen and Contentful work together to enable content-driven commerce: a storefront where your content strategy and your product catalogue operate in parallel, not in competition.

Want to see what this looks like for your brand? Explore our Shopify Hydrogen service to understand what Apolinar delivers in practice.

What is content-driven commerce?

Content-driven commerce is a storefront model where editorial content — brand stories, buying guides, campaign pages, category education — drives discovery, loyalty, and conversion alongside the product catalogue, rather than serving as an afterthought to it.

Most Shopify stores are product-led by design. Product pages, collection pages, a home page, a blog. The content serves the catalogue. That model works well for stores where the product speaks for itself, commodity purchases, repeat buyers, simple search intent.

Content-driven commerce starts from a different premise: the brand story, the editorial narrative, the richness of the content experience, these are what differentiate you in a market where your competitor's product listing is two clicks away on the same platform.

Think about the brands that have built genuine loyalty: outdoor gear companies with deep editorial roots, food brands with recipe ecosystems, fashion retailers whose seasonal lookbooks drive conversion better than any retargeting campaign. These brands do not treat content as a marketing add-on to the product catalogue. Content is the product experience.

Product-led vs content-led storefronts

A product-led storefront is optimised around catalogue browsing and checkout. It does the job. A content-led storefront is optimised around the full customer relationship: discovery, education, storytelling, loyalty, with commerce woven through it. The difference shows up in organic search performance, in brand recall, in repeat purchase rates.

The challenge is that Shopify's standard architecture, including most themes, no matter how sophisticated, is designed around the product-led model. It is hard to run a genuinely content-led storefront on a standard theme without creating exactly the workflow bottlenecks that slow both teams down.

Why editorial teams and commerce teams need different tools

When your marketing team needs a developer to publish a new campaign page, your content velocity is capped at your developer's availability. When your commerce team is locked inside a CMS designed for blog posts rather than product pricing rules, their agility is constrained by workflows that were never built for them.

The solution is not a better theme. It is a separation of concerns: commerce data managed in Shopify, content managed in a purpose-built CMS, connected via APIs so the storefront draws from both simultaneously. That is the core idea behind headless Shopify Contentful builds — and what Hydrogen is designed to enable.

What Shopify Hydrogen does (and what it doesn't)

Shopify Hydrogen is a React-based storefront framework built specifically for headless Shopify development. It connects directly to Shopify's Storefront API to pull product data, handle cart logic, and process checkout, the core commerce functions that Shopify handles exceptionally well. Deployments run on Shopify's own edge hosting platform, Oxygen, which distributes the storefront globally and keeps load times consistently fast.

The result is a custom storefront built on top of Shopify's commerce infrastructure, rather than inside a theme template. Your design, your UX, your performance profile, without losing Shopify's checkout reliability.

Where Hydrogen ends, and why you need a CMS

Hydrogen is excellent at rendering product data. It isn't a content management system. You wouldn't use it to give a marketing editor the ability to create a new campaign landing page, manage an editorial article, or update a hero banner without writing code.

For those use cases, you need a Shopify headless CMS — one that is API-first and designed to sit cleanly alongside Hydrogen's architecture. This is not a limitation of Hydrogen; it is how the system is designed to work. Hydrogen handles commerce. The CMS handles content. An API connects them at the storefront level.

Ideal use cases

Hydrogen makes sense for brands that have outgrown the customisation limits of Shopify themes, need performance that a standard theme with a heavy app stack cannot reliably deliver, want to serve content across multiple channels from a single source, and have the development resource to build and maintain a custom storefront. It is not the right choice for a small catalogue, a simple store, or a team without dedicated development capacity.

Why Contentful is the right CMS for a Shopify Hydrogen storefront

Contentful is a headless, API-first CMS built around structured content. You do not build pages in Contentful, you define content models (what a "campaign page" is, what fields it contains, how it relates to a product category) and create entries that populate those models. The content is then delivered via API to whatever is rendering it: your Hydrogen storefront, your mobile app, your partner portal.

Structured content that maps to your product model

This is where the Shopify Hydrogen Contentful integration becomes particularly useful. Contentful can store editorial content that references Shopify product data: a campaign landing page that pulls in relevant products, a buying guide that links to the collection it covers, a brand story that connects to the full product range. The content model is designed around how your editorial team thinks, not around how your product catalogue is structured.

Contentful's official Shopify Hydrogen Starter is a documented, supported starting point for this integration. It is not a bespoke workaround, it is a pattern Contentful and Shopify have built to work together.

Editorial independence: publish without a developer

Once the Contentful implementation is in place and the content models are designed, your editorial team can create new campaign pages, publish buying guides, update homepage content, and manage the full content layer without a developer involved. The developer built the system; the marketing team runs it.

This is what makes Contentful the right choice over a simpler CMS option: the structured content approach means editorial freedom is constrained by design, not by access. Editors can do exactly what they need to do, and only that. No accidental template breaks, no layout inconsistencies across the storefront.

API-first: one content layer, multiple channels

Contentful content is available to any channel that can consume an API. Your Hydrogen storefront is one consumer. A mobile app is another. A future regional microsite, a partner portal, a digital display installation, all fed from the same Contentful space, with content managed once. Shopify's own Hydrogen documentation consistently points developers toward headless CMS integrations for exactly this reason.

The combined architecture in practice

Here is what this looks like for a real brand.

Tāwhiri Outdoor Co., a New Zealand outdoor apparel and gear retailer, had been on Shopify for four years. Their commerce operations were solid: 400 SKUs, strong repeat purchase rates, reliable checkout. The problem was editorial.

Their marketing team had a content strategy they couldn't execute: deep product guides, gear selection articles, seasonal lookbooks, regional campaign pages for NZ and Australian audiences. Every new editorial page required a developer. That developer was also maintaining integrations, fixing theme conflicts, and supporting a monthly app stack of 14 tools. Editorial was always last in the queue.

When they rebuilt on Shopify Hydrogen with Contentful as the content layer, the architecture changed fundamentally. Their marketing team now manages all editorial content in Contentful, creating, editing, and publishing campaign pages without waiting on anyone. Product data still comes from Shopify. Algolia handles search across both the product catalogue and the editorial content. The two systems are connected through the Hydrogen storefront, but the teams managing them operate independently.

Outward Bound NZ followed the same architectural pattern. The Shopify Hydrogen and Contentful build Apolinar delivered for them was completed in six months, with a content team that could operate the editorial layer from day one.

What the marketing team can actually do post-launch

After a well-scoped Contentful implementation, a marketing editor with no development knowledge can typically:

• Create a new campaign landing page with hero, editorial sections, and featured products

• Publish a buying guide or editorial article

• Update homepage content, banners, featured categories, seasonal messaging

• Manage content for NZ and AU audiences from a single space, with localisation handled at the content model level

The developer is not involved in any of these tasks. They are available for new feature development, which is where their time is most valuable.

Our Contentful implementation practice designs content models specifically around how commerce editorial teams work. If you want to understand what that looks like for your team's workflow, a discovery call is the fastest way to get a specific answer. Book a 30-minute call with Apolinar — no commitment, no hard sell.

When Shopify Hydrogen + Contentful makes sense (and when it doesn't)

Jamie is Head of Digital at a mid-sized NZ health and wellness brand. When she first evaluated Shopify Hydrogen, the developer she consulted quoted six to nine months and a six-figure budget. The evaluation stopped there. Six months later, Jamie's team was still working around the same theme limitations: content updates queued, campaign launches delayed, the developer stretched across too many competing priorities.

The issue was not that Hydrogen was wrong for them. It was that nobody had scoped the project with their actual team capability and content ambitions in mind. A properly scoped Hydrogen and Contentful build for a brand like theirs, 300 SKUs, an active editorial programme, NZ and AU audiences, was achievable within a more realistic timeframe and cost than that initial quote suggested. The conversation needed to start from business outcomes, not from a developer's estimate of technical complexity.

Use this stack if

• You have 200+ SKUs and an active editorial content programme running alongside the catalogue

• Your brand's competitive advantage is content: guides, storytelling, community, education

• You need to serve NZ and AU audiences with different content from a single platform

• Your development team, in-house or agency, has React capability

• Your current theme with multiple apps is underperforming on speed (Hydrogen storefronts consistently achieve Lighthouse scores of 90+; theme-heavy stores with multiple apps regularly score 40–60)

Consider alternatives if

• Your catalogue is under 50 SKUs and your content needs are minimal

• You do not have the development resource to build and maintain a custom storefront

• A well-configured Shopify theme will genuinely get you to your immediate goal faster

Hydrogen isn't always the right answer. Part of what Apolinar does is tell clients when a simpler approach is genuinely better for their situation. Our strategy and advisory service exists specifically for this kind of platform decision, helping you make the right call before committing to a build.

Getting started with Apolinar

Emma runs marketing for a New Zealand lifestyle brand that had been evaluating headless commerce for 18 months, reading articles, attending webinars, collecting quotes that varied wildly. When she booked a discovery call with Apolinar, the conversation lasted 40 minutes. By the end, she had a clear view of what a Shopify Hydrogen Contentful build would involve for her specific team, catalogue, and content ambitions — including an honest assessment of what was and wasn't worth the investment.

"I'd been collecting opinions for over a year," she told us. "That call gave me a decision."

If you are evaluating this stack, the starting point is understanding what your content operations actually look like today, and what you need them to look like after launch. That is the conversation we start with.

Apolinar scopes and delivers composable commerce Shopify builds — Hydrogen storefronts with Contentful as the content layer — connecting the storefront to your CRM, marketing automation, and analytics stack where relevant. If you have existing content that needs to move across, we have delivered content migrations to Contentful as part of this process for clients making the switch from WooCommerce, Magento, and Shopify's own Online Store.

[Book a discovery call with the Apolinar team →](https://apolinar.agency/solutions)

No commitment required. If Hydrogen and Contentful aren't right for your situation, we'll tell you that too.

Conclusion

The question most brands ask is: "Should we go headless?" The more useful question is: "Do we have a content strategy that a standard Shopify theme is actively getting in the way of?"

Shopify Hydrogen and Contentful answer that second question. They do not replace your commerce infrastructure, they extend it, adding an editorial layer that your content team can own and operate independently. Product data from Shopify. Brand storytelling from Contentful. Both rendered through a Hydrogen storefront that neither team is waiting on the other to update.

For Shopify Hydrogen NZ and AU brands with genuine content ambitions and a catalogue that has grown beyond what a theme can cleanly handle, this is the composable architecture worth exploring.

[Talk to Apolinar about your next build →](https://apolinar.agency/partners/shopify)