Skip to main content
Talk to an expert
Hygraph logo

Hygraph integration for ecommerce content and media

Product media and pages published once, consumed everywhere Hygraph separates content authoring from storefront presentation so editorial teams own asset governance while storefronts pull product media reliably. iWeb integrates Hygraph with your commerce platforms so content flows are named, approval workflows are enforced and publishing failures surface clearly. Works with Adobe Commerce, Magento Open Source, Shopify Plus, BigCommerce and other storefronts.

Also searched as: CMS integration, headless CMS, content, DAM, digital asset management, product media.

HygraphiWeb integration layeryour storefront
Talk to an expertSee the estate map ↓
Works with - Adobe Commerce · Magento Open Source · Shopify Plus · BigCommerce · Other storefronts
On this pageGet a brief reviewed
01 · What you get

What a Hygraph integration gives you.

Content published once, consumed everywhere

Editorial teams author product media, descriptions and campaign pages in Hygraph; storefronts, marketplaces and campaigns consume them independently. No copy-paste or manual syndication.

Editorial and ecommerce workflows decouple

Content can be authored, reviewed and scheduled in Hygraph on an editorial calendar. Storefronts subscribe to content events and pull it on their own schedule, avoiding bottlenecks when platforms are down or deploying.

Asset governance and brand consistency enforced

Approved product images, variant rules and brand guidelines live in Hygraph. Storefronts pull only approved assets, and asset retire or refresh events propagate so stale imagery cannot remain in use.

Content readiness visibility for operations teams

Ecommerce and marketing teams can see at a glance which product content is complete, approved and ready to publish across each channel. Missing content or unapproved variants surface as exceptions.

Faster time to market for campaigns and seasons

Staged content in Hygraph can be scheduled months in advance. Storefronts deploy independently without waiting for manual content sync or staging rewrites.

02 · When it's worth it

Where a Hygraph integration earns its place.

If two or more of these are true, the integration usually pays for itself quickly.

Publishing product media, rich descriptions and category content to multiple ecommerce platforms from a single editorial source
Managing landing pages, campaign assets and promotional content with scheduled publishing and version control
Syncing rich text, SEO metadata and variant-specific content across web, mobile app and marketplace feeds
Storing and transforming digital assets (images, PDFs, videos) with CDN delivery and variant generation
Separating editorial workflow and approvals from storefront deployment so content can be staged before going live
03 · The limits

Where off-the-shelf connectors fall short.

Vendor connectors are fine for simple cases. Here's where the real ones need more.

No native product inventory awareness

Hygraph does not know about stock, pricing or real-time product availability. The integration must explicitly feed product master records from PIM or commerce platform into Hygraph, or ensure storefronts combine Hygraph content with live product data from ERP or OMS.

Manual product-to-content linking

Hygraph does not automatically associate content with products in your ERP or commerce platform. Editorial teams must maintain manual links, or the integration must build a reference layer that maps SKUs to content IDs.

No multi-storefront content-variant rules

Hygraph does not enforce which content variations are required for which storefronts or channels. The integration must define and validate channel-specific content readiness before publishing.

Asset transformation and CDN caching are platform features

Hygraph provides asset APIs and optional CDN delivery, but the integration must configure image sizing, format conversion and cache-expiry rules. Stale assets can linger if cache headers are not tuned.

No built-in approval workflow governance

Hygraph supports workflow states, but does not integrate approvers from outside systems. Approval rules and escalation paths must be designed during integration, not assumed.

04 · The real work

Content governance often fails because editorial, product and ecommerce teams own content authoring in different systems and manual sync becomes invisible, then breaks.

05 · Where it sits

Where this integration sits in your estate.

Hygraph holds the commercial record. The iWeb integration layer manages the rules, mappings, monitoring and exceptions. The commerce platform presents the customer-facing experience. The estate map helps agree ownership before anything is built.

Storefront independent. Hygraph feeds stock, pricing, orders and customer data into your chosen platform.

System of record
Source / owner
Hygraph
Headless content and asset platform for editorial and product media
  • Product images and digital assets
  • Product descriptions and rich editorial content
  • Landing pages and campaign content
  • Content versions and publishing schedule
  • Asset CDN delivery and transformation rules
  • Editorial workflows and approvals
iWeb integration layer
Customer-facing commerce
Commerce platform
Adobe CommerceMagento Open SourceShopify PlusBigCommerceOther storefronts
  • Storefront presentation and customer experience
  • Cart, checkout and customer session
  • Live pricing and stock display
  • Customer account and order records
  • Channel-specific product display rules
Connected neighbours
Integration layer
PIM and ERP
Product master data, SKUs, attributes, variant rules and pricing flow from PIM or ERP. Hygraph wraps this with editorial content and assets. Changes to product definitions trigger content refresh alerts in Hygraph.
Integration layer
Email and marketing platforms
Campaign content and promotional assets authored in Hygraph are syndicated to email, social and ad platforms. Publishing events notify marketing systems when content is ready.
Integration layer
Search and discovery
Hygraph content is indexed for search. Meta descriptions, category content and product narratives feed search relevance. Merchandising rules on storefronts may reference Hygraph-managed category pages.
Integration layer
Analytics and reporting
Publishing events, content versioning and asset usage are logged and flow to BI systems. Content teams see dashboards on which pages and assets are live and performing.
Two-way sync where relevant
06 · Surrounding systems

Systems this integration usually sits next to.

Examples, not a closed list. iWeb is platform-agnostic on both sides: we wire this integration into whatever ecommerce platform and surrounding systems your estate already runs.

Ecommerce platforms (examples)
  • Adobe Commerce
  • Magento Open Source
  • Shopify Plus
  • BigCommerce
  • Other storefronts
Surrounding systems (examples)
  • Contentful (alternative headless CMS)
  • Product Information Management (PIM) for product master data
  • Enterprise Resource Planning (ERP) for product and pricing changes
  • Digital Asset Management (DAM) for brand governance
  • Email marketing platform for campaign content
  • Search and merchandising system for content indexing
Not sure?

Not sure if this works with your stack?

Tell us what you’re using and what needs to connect. We’ll give you a straight view on what’s possible, what might be awkward, and the safest way to approach it.

07 · Data flows

The data flows we wire.

Each flow has a direction and an owner. We agree both before a line of code is written.

→Into COMMERCE & SALES CHANNELS & REPORTING
←From COMMERCE
↔BOTH WAYS
Product media and descriptions: Images, videos, rich text and structured product content flow from Hygraph into the commerce platform via API or scheduled export
The integration ensures product media stays in sync across platforms and respects variant-specific copy and imagery rules.
Landing pages and campaigns: Authored pages, banner content and promotional assets move from Hygraph into commerce storefronts, email campaigns and marketplace headers
Publishing schedules and version histories remain auditable.
Product metadata triggers content updates: Changes to product names, SKUs or categories can flow back into Hygraph as content hints so editorial teams know when product master data has shifted and content may need refresh.
Asset governance and approvals: Brand asset libraries, approved image variants and content-approval workflows exist in Hygraph; publishing events notify storefronts and marketing systems when assets are ready or revoked.
Content performance and usage: Metrics on which pages are published, when updates occurred and which assets are in use flow to analytics and BI systems for content inventory and governance tracking.
08 · How we build it

How iWeb configures the integration around your business.

Same method on every integration. The decisions come before the code.

  1. 01
    Ownership mapping and governance

    iWeb names who owns content in Hygraph, who owns product master records in ERP or PIM, who owns the storefront experience, and how changes flow between them without orphaning or overwriting data.

  2. 02
    Data flow and API design

    iWeb designs the APIs and scheduled exports from Hygraph into storefronts, handles pagination and rate limits, and ensures content is fetched only when changed to avoid unnecessary refreshes.

  3. 03
    Content-variant and channel-readiness rules

    iWeb defines which content fields are required for which channels (image counts, text length limits, metadata rules) and builds validation that flags unready content before it reaches storefronts.

  4. 04
    Asset transformation and CDN integration

    iWeb configures image sizing, format conversion and CDN headers in Hygraph so that storefronts receive correctly sized assets and cache rules are consistent across channels.

  5. 05
    Publishing orchestration and exception handling

    iWeb builds workflows so that when content is approved in Hygraph, publish events trigger storefront updates. Failed publishes, rollbacks and retry logic are named and monitored.

  6. 06
    Monitoring, alerting and audit trails

    iWeb installs observability so that content teams can see which pages are live, when they were published, what failed and why. Audit trails show who authored, approved and changed what.

09 · Ownership

Who owns what.

The single most important table in any integration. One system owns each field; everything else reads it.

Data
Source / owner
Maintained by
Notes
DataProduct media and images
Source / ownerHygraph
Maintained byMarketing, product and editorial teams
NotesImages are authored in Hygraph, versioned and approved before syndication to storefronts and channels. Variant-specific imagery rules (e.g. gallery order, hero asset) are maintained in Hygraph configuration.
DataProduct descriptions and rich content
Source / ownerHygraph
Maintained byContent and product teams
NotesLong-form copy, feature tables, use-case narratives and variant-specific text are authored in Hygraph. Storefronts pull and display this content; updates in Hygraph trigger storefront content refresh.
DataLanding pages and campaign content
Source / ownerHygraph
Maintained byMarketing and editorial teams
Notes
DataCategory and navigation hierarchy
Source / ownerHygraph or PIM (defined per project)
Maintained byMerchandising and content teams
NotesCategory names, descriptions and navigation rules may live in Hygraph (for editorial categories and landing pages) or in PIM (for product taxonomy). Integration must clarify the boundary and prevent duplication.
DataDigital assets and media library
Source / ownerHygraph
Maintained byMarketing operations and brand teams
NotesPDFs, videos, brand guidelines and downloadable assets are stored in Hygraph. Approval workflows and asset retirement are tracked; deleted assets trigger storefront alerts if still in use.
DataPublishing schedule and workflow state
Source / ownerHygraph
Maintained byEditorial and marketing teams
NotesContent publishing schedule, approval status and versioning live in Hygraph. The integration surfaces publishing events so that storefronts and campaigns know when to pull updates.
DataIntegration transport, monitoring and exception handling
Source / owneriWeb integration layer
Maintained byiWeb operations and ecommerce team
NotesAPI calls, scheduled exports, failure queues, retry logic and alerting are owned by the integration. Content teams see alerts when publishes fail; operations monitor API rate limits and asset CDN health.
10 · Experienced integrator

Built this kind of integration before

iWeb has integrated multiple headless CMS platforms with commerce estates. We understand how Hygraph sits between editorial teams and storefronts, and how to govern content so that product information, assets and campaign copy flow reliably without collision or manual rework.

iWeb designs content ownership models so Hygraph feeds product media and campaign pages while ERP or PIM remains the source for product master data, attributes and pricing.
iWeb configures Hygraph feeds for multiple storefronts independently, handling content variants, channel-readiness rules and asset transformation so each platform gets the content it needs.
iWeb builds approval and publishing workflows that make content governance visible, so editorial teams and ecommerce operations know what is live, what is pending and what failed.
iWeb integrates Hygraph publishing events with commerce platforms and email systems so campaigns and seasonal content go live on schedule without manual sync.
iWeb installs monitoring and alerting so that content staling, asset rot and publishing failures surface early and do not cascade into storefront or campaign failures.
11 · Before launch

What we test before launch.

Every one of these is rehearsed before a customer ever sees the integration.

Verify that content published in Hygraph appears on all expected storefronts within the configured sync interval and that stale content does not linger.
Confirm that product data changes in ERP or PIM trigger content refresh alerts in Hygraph and that editorial teams are notified of changed product information.
Test that content-readiness rules validate required fields and channel-specific variants before publishing, and that incomplete content is blocked or flagged.
Check that asset URLs do not break if images are moved or deleted in Hygraph, and that storefronts degrade gracefully if an asset is missing.
Confirm that publishing failures (API timeouts, rate limits, authentication errors) are logged and alerted to operations, and that fallback content is served.
Verify that approval workflows in Hygraph enforce that only reviewed content publishes, and that unapproved changes do not reach storefronts.
Test that scheduled content publishes at the expected time across all storefronts without manual intervention and that timezone handling is correct.
12 · Failure points

Common risks and where they bite.

We name these on day one. A risk written down is a risk you can plan around.

Stale or missing content on storefronts

If Hygraph feeds are not pulling frequently enough, or if a storefront fails to consume updates, content can age. If no fallback content rule exists, storefronts may display incomplete or outdated product information.

Product and content going out of sync

If product master records change in ERP or PIM but Hygraph content is not refreshed, storefronts may display stale descriptions or outdated variant information. The integration must make those refreshes automatic or surface them as alerts.

Unapproved or incomplete content publishing

If approval workflows in Hygraph are not enforced or if channel-readiness rules are missing, incomplete or unapproved content can reach storefronts and marketplaces, damaging brand trust and conversion.

Asset URL rot and missing images

If Hygraph asset URLs are referenced directly in storefronts and those assets are deleted or moved in Hygraph, images break. CDN or asset-versioning strategies must be defined upfront.

Publishing queues and manual workarounds

If the integration does not handle scheduling, retries and failure exceptions, content teams fall back to manual sync or re-export, creating bottlenecks and reducing trust in the system.

Content collision between editorial and ERP systems

If both Hygraph and the ecommerce platform allow editing of product descriptions or category copy, conflicts can arise. Ownership and read-only boundaries must be enforced to prevent overwrites.

13 · Where it applies

Relevant services and sectors.

14 · Questions

Common questions about Hygraph integrations.

Should our product master data live in Hygraph or in our PIM?

Hygraph is designed for editorial and asset content, not product master data. Product attributes, SKUs, variant rules and base descriptions belong in your PIM or ERP. Hygraph can pull product metadata from PIM and wrap it with rich editorial content (use cases, stories, images). The integration defines which system owns each field and ensures they do not collide.

How do we prevent stale content on our storefronts?

iWeb configures Hygraph feeds to publish on a schedule or on content-change events. Storefronts are configured to pull on that schedule or subscribe to webhooks. If a pull fails, retry logic and fallback content rules ensure customers see something sensible. Monitoring alerts ecommerce operations if content is older than expected.

Can we manage different content for different storefronts?

Yes. Hygraph supports content variants and channel-specific fields. The integration defines which content fields are required for which storefronts, validates readiness before publishing, and allows storefronts to consume only their approved variants. Without this governance, content teams end up managing content ad hoc.

How do product changes in our ERP trigger content refresh in Hygraph?

iWeb builds a workflow so that when a product is created or updated in ERP or PIM, an event notifies Hygraph or a staging system. Content teams then know to refresh descriptions, images or variant data. Alternatively, if product metadata is static, Hygraph can be updated on a scheduled batch. The integration clarifies which changes are automatic and which require manual review.

What happens if Hygraph is down when we need to publish?

If Hygraph is unavailable, storefronts should have a fallback so they can still operate. This might be cached content, content stored redundantly in commerce platform databases, or a message to customers. iWeb designs the fallback behaviour upfront so that editorial downtime does not become a storefront outage.

How do we handle asset URLs and image CDN?

Hygraph provides built-in asset storage and CDN. iWeb configures image sizing, format variants and cache headers so that storefronts receive optimised, consistent images. If you use an external CDN or asset service, iWeb integrates with that instead. The key is to avoid hardcoding asset URLs; use reference fields so that if an asset moves, the link updates automatically.

Can we schedule content to go live at specific dates and times?

Yes. Hygraph supports publish scheduling and content versioning. iWeb configures storefronts to poll for scheduled updates or subscribe to publish events. This allows campaigns and seasonal content to be approved weeks in advance and go live without manual intervention.

How do we know which content is complete and ready to publish?

iWeb defines content-readiness rules for each channel (image counts, text length, required fields, SEO metadata). Hygraph workflow states and iWeb validation expose which content is missing or incomplete. Content dashboards and reports show which pages and products are ready across each storefront.

What happens if we edit content in both Hygraph and our storefront?

To avoid conflicts, ownership is clarified: Hygraph is the source for certain content (product media, campaign pages), and storefronts are read-only consumers. If storefronts also allow editorial edits, those edits are quarantined and do not overwrite Hygraph content. The integration makes this boundary clear so content teams do not inadvertently lose edits.

How do we audit who changed content and when?

Hygraph tracks user and timestamp for each content change. iWeb integrations feed those audit logs into reporting and BI systems so that content teams and compliance can see change history. Publishing events are also logged so you can see which versions went live to which channels.

Can we translate or localise content in Hygraph?

Yes. Hygraph supports multi-language content models and localisations. iWeb configures the integration so that storefronts pull content in their language or locale. Translation workflows and approval for each language can be managed in Hygraph. The integration ensures only approved translations publish.

How do we integrate Hygraph with our email marketing platform?

iWeb can configure Hygraph to export campaign content and assets to email marketing systems. Marketing teams author campaigns in Hygraph, approve them, and the integration pushes them into your email platform on schedule. This keeps email content in step with storefront promotions and campaign messaging.

What if our storefronts are built with different frameworks or platforms?

Hygraph is platform-agnostic; it exposes content via APIs and supports multiple storefronts simultaneously. iWeb builds integrations for each platform independently so that a Other storefronts, Shopify, Adobe Commerce and a custom app can all consume Hygraph content. Each storefront is responsible for pulling on schedule or subscribing to updates.

How do we monitor and alert on publishing failures?

iWeb installs monitoring so that when Hygraph publishes fail, API calls time out or assets are missing, alerts fire to content and ecommerce teams. Observability dashboards show publishing latency, failure rates and asset inventory. On-call escalation ensures failures are caught quickly.

Next step

Have a Hygraph integration brief?

Send the brief, or tell us what is breaking. You will get a written response from a senior expert: the integration boundary, the realistic shape, the risks worth naming, and what it takes to support after launch.
Talk to an expertOr browse all integrations →