Skip to main content
Talk to an expert
Akeneo Asset Manager logo

Akeneo Asset Manager integration for ecommerce content and media

Governed product media published cleanly to all storefronts Akeneo Asset Manager centralises product images, videos and brand assets so editorial teams control versions, approvals and publishing schedules. iWeb synchronises asset metadata, transformations and delivery to commerce platforms and content systems without losing approval workflows or asset lineage. 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.

Akeneo Asset ManageriWeb 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 Akeneo Asset Manager integration gives you.

Product media governance

Asset teams can enforce brand standards, approval workflows and version control across all product images and videos. Commerce teams know which assets are approved and ready for each channel.

Faster campaign and content launches

Approved assets are published to storefronts and content systems without manual file uploads or email handoffs. Campaign teams can schedule asset release in line with content publishing deadlines.

Reduced asset-sync failures

Assets, metadata and transformation rules sync reliably without stale image URLs, missing alt-text or broken video embeds reaching customers. Errors surface to the right team immediately.

Multi-channel asset consistency

The same product image, video or downloadable file is published to Adobe Commerce, Shopify, marketplace listings and mobile apps with consistent metadata, naming and approval status.

Asset performance visibility

Editorial teams can see which product images, video variants and campaign assets are driving traffic, engagement and conversions. This data informs which assets to refresh, reposition or retire.

02 · When it's worth it

Where a Akeneo Asset Manager integration earns its place.

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

Publish product images and videos to multiple commerce storefronts with consistent metadata and alt-text governance
Sync asset transformation rules (crops, resizing, format variants) so storefronts always receive the correct visual asset
Automate product media refresh when assets are updated in Asset Manager without losing commerce content links
Manage downloadable product documents (datasheets, compliance files, instructions) with version control and channel-specific access
Coordinate editorial asset approval workflows so assets reach storefronts only when published
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 multi-tenant asset isolation

Asset Manager does not natively prevent different commerce brands, regions or business units from accessing each other's assets. Integration design must add permission boundaries and asset-access rules if the estate requires strict separation.

Limited real-time asset transformation on delivery

Asset Manager can define transformation rules, but storefronts expecting dynamic crops, format conversion or watermarking on-the-fly may need a separate CDN or image-optimisation layer to avoid latency.

No built-in fallback or asset-not-found handling

If an asset fails to deliver or is deleted, Asset Manager does not automatically serve a placeholder or notify commerce that a product image is missing. The integration must handle asset-loss scenarios and alert editorial teams.

Approval workflows are asset-centric, not channel-centric

Asset Manager can enforce approval gates, but it does not natively understand channel-specific readiness rules (e.g. 'this image needs a US product disclaimer before it appears on Shopify'). Integration must map channel rules to asset attributes or approval steps.

Asset metadata sync is one-way by default

Asset Manager publishes metadata to storefronts, but commerce platforms do not natively feed back asset-performance signals, usage counts or deprecation notices. The integration must set up return flows if analytics or usage data need to inform asset strategy.

04 · The real work

The tension is clarity of ownership: asset teams focus on brand and governance, commerce teams care about launch speed, and both need the same images to arrive fast and approved. Without integration boundaries, neither team fully owns the outcome.

05 · Where it sits

Where this integration sits in your estate.

Akeneo Asset Manager 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.

Commerce platform agnostic. Connect Akeneo Asset Manager across your entire technology stack.

System of record
Source / owner
Akeneo Asset Manager
Centralised digital-asset and product-media repository with approval workflows and transformation rules
  • Product images, videos and 360 views
  • Asset metadata (alt-text, captions, usage rights, tags)
  • Asset transformation and variant rules
  • Campaign and content assets
  • Downloadable product documents
  • Asset approval workflows and publishing schedules
iWeb integration layer
Customer-facing commerce
Commerce platform
Adobe CommerceMagento Open SourceShopify PlusBigCommerceOther storefronts
  • Asset display and rendering on storefronts
  • Product-to-image linking in the catalogue
  • Customer-facing image galleries and carousels
  • Local caching and CDN acceleration
  • Asset-click and engagement metrics
Connected neighbours
Integration layer
PIM
Provides product references, category taxonomy and asset-usage rules; receives product-media URLs from Asset Manager.
Integration layer
Headless CMS
Receives campaign and content assets from Asset Manager; renders approved graphics and videos on landing pages.
Integration layer
Analytics and BI
Tracks asset usage, clicks and engagement; reports signals back to Asset Manager so editorial teams prioritise refreshes.
Integration layer
CDN or image service
Delivers optimised asset variants to storefronts; handles dynamic transformation and caching.
Integration layer
ERP
May link downloadable compliance documents to products for commerce; asset version control stays in Asset Manager.
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)
  • Akeneo PIM (if separate from Asset Manager)
  • Headless CMS (Contentful, Storyblok, Sanity)
  • Commerce platforms (Adobe Commerce, Shopify, BigCommerce)
  • CDN or image-optimisation service
  • Analytics and BI platforms
  • Product information master (ERP)
  • Marketplace connectors
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 & CONTENT SYSTEMS
←From COMMERCE & PIM
↔BOTH WAYS
Product media and asset metadata: Asset Master records, image URLs, video links and associated metadata flow from Asset Manager to commerce platforms and storefronts
Transformation rules and asset variants (mobile crops, thumbnail versions, alternative formats) are applied on delivery to match commerce channel requirements.
Digital assets for campaigns and pages: Authored campaign assets, landing-page images, brand-approved media and digital files sync from Asset Manager to headless CMS and content platforms
Publishing approval status and scheduled release dates control when assets appear in content systems.
Asset usage and performance signals: Commerce platforms report back which assets are in use, performance metrics (click-through rates, view counts) and asset-swap events
These signals help asset teams understand which media drives engagement and inform future asset creation.
Product-to-asset relationships and enrichment tags: PIM systems supply product references, category taxonomy, enrichment tags and asset usage rules
Asset Manager uses these to organise media into logical groups and enforce channel-readiness requirements on product images.
Asset versioning and editorial approval: Asset updates, version history and approval-workflow state sync bidirectionally
Commerce and content systems can signal when an asset variant is no longer needed, and Asset Manager can notify stakeholders when a new asset version is ready for use.
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
    Define asset ownership and governance boundaries

    iWeb maps which team owns each asset type (product images, campaign graphics, downloadable files, video). Approval workflows, versioning, access controls and channel-readiness rules are explicit, not implicit.

  2. 02
    Build the asset-delivery pipeline

    iWeb configures how assets move from Asset Manager into commerce platforms, CDNs, headless CMS and content-delivery channels. Transformation rules (crops, formats, thumbnails) are tested and monitored so storefronts always receive the correct variant.

  3. 03
    Set up asset transformation and variant management

    iWeb builds the logic that generates mobile-optimised crops, video thumbnails, format conversions (AVIF, WebP, legacy formats) and alt-text variants for accessibility. Each commerce platform receives the asset format it needs.

  4. 04
    Connect approval workflows to commerce release

    iWeb integrates Asset Manager approval gates with storefront publishing calendars so assets don't appear in commerce until editorial approval is complete. Campaign assets can be scheduled to go live at a specific date and time.

  5. 05
    Build observability and exception handling

    iWeb adds monitoring for missing assets, broken URLs, failed transformations, stale metadata and approval bottlenecks. Exception queues alert the right team (digital asset manager, editorial lead, commerce ops) immediately.

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 (images, videos, 360 views)
Source / ownerAkeneo Asset Manager
Maintained byDigital asset team / product operations
NotesCommerce platforms and storefronts receive copies; Asset Manager holds the canonical version, metadata, approval status and version history.
DataAsset metadata (alt-text, captions, usage rights, tags)
Source / ownerAkeneo Asset Manager
Maintained byDigital asset team / SEO and accessibility team
NotesSyncs to commerce platforms and headless CMS; Asset Manager is the source. PIM may contribute enrichment tags for asset organisation.
DataAsset transformation and variant rules (crops, formats, sizes, watermarks)
Source / ownerAkeneo Asset Manager
Maintained byDigital asset team / technical asset ops
NotesRules are defined in Asset Manager; applied by the integration pipeline at delivery time. Commerce platforms request variants; Asset Manager supplies them.
DataCampaign and content assets (landing-page images, promotional graphics)
Source / ownerAkeneo Asset Manager
Maintained byContent / campaign team
NotesSyncs to headless CMS and content-delivery platforms. Asset Manager holds approval status and publishing schedule; content systems display approved assets.
DataDownloadable product documents (datasheets, compliance files, instructions)
Source / ownerAkeneo Asset Manager
Maintained byProduct operations / compliance team
NotesLinked to products in PIM or commerce. Asset Manager controls versioning, access and expiry; commerce platforms serve documents to customers.
DataAsset usage and performance signals (views, clicks, engagement)
Source / ownerCommerce platforms and analytics systems
Maintained byCommerce analytics team
NotesFlows back to Asset Manager for reporting. Asset teams use signals to prioritise asset refreshes and understand which media drives engagement.
DataAsset approval workflows and publishing schedule
Source / ownerAkeneo Asset Manager
Maintained byEditorial and asset governance team
NotesApproval state and scheduled release dates control when assets appear in commerce and content systems. Integration respects approval gates before publishing.
10 · Experienced integrator

Built this before

iWeb has integrated Akeneo Asset Manager with commerce estates where digital-asset governance, multi-channel publishing and editorial approval workflows matter. We understand how asset metadata, transformation rules and approval gates interact with commerce platforms and where ownership becomes ambiguous.

iWeb maps asset ownership boundaries so Asset Manager holds the canonical versions while storefronts hold optimised copies and engagement metrics
iWeb builds asset-delivery pipelines that handle image transformation, metadata sync, alt-text localisation and channel-specific variants without blocking commerce launch
iWeb integrates asset approval workflows with storefront publishing calendars so campaign assets don't go live until editorial approval is complete
iWeb sets up monitoring and exception handling for missing assets, broken URLs, stale metadata and approval bottlenecks so issues surface before customers see blank product images
iWeb connects asset-usage signals and performance data back to Asset Manager so editorial teams can measure which media drives engagement and plan refresh priorities
11 · Before launch

What we test before launch.

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

Verify asset URLs are correct and accessible on all storefronts within 5 minutes of approval in Asset Manager
Test that rejected or recalled assets are removed from storefronts within the configured SLA window
Confirm that image transformation rules (crops, formats, sizes) produce correct variants for each platform
Validate that alt-text and accessibility metadata are present and complete on published product images
Check that scheduled campaign assets appear on their release date and time, not before or after
Test fallback behaviour when Asset Manager is temporarily offline (cached images should serve, not broken links)
Verify that asset-usage signals from commerce platforms flow back to Asset Manager for reporting and analytics
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.

Asset URLs break or drift from Asset Manager to commerce

If Asset Manager changes asset URLs, moves files to a new storage location or retires old assets without coordination, storefronts may serve broken image links or outdated media. Integration must handle URL rewrites and asset-retirement notifications.

Approval workflows block storefront updates

If approval processes are too strict or no one owns the approval queue, product images and campaign assets can be stuck in 'pending' status while storefronts show placeholder content. Asset teams and commerce teams need clear escalation paths.

Asset metadata diverges between systems

Asset Manager holds alt-text, captions and usage rights. If PIM or commerce platforms cache older metadata versions, storefronts may display outdated asset descriptions or lose SEO value from missing alt-text. Integration must define metadata freshness expectations.

Transformation rules silently fail

If image crops, format conversions or watermarking rules fail mid-pipeline, storefronts may serve oversized, wrong-format or unbranded assets without anyone noticing until customers report bad images. Monitoring must catch and alert on transformation errors.

Asset-not-found handling breaks campaign timing

If a campaign asset is moved, deleted or not yet approved when the campaign goes live, storefronts may show broken images or wrong assets. The integration must validate asset availability before campaign release and provide clear warnings.

Multi-channel asset inconsistency

Different commerce platforms may receive different asset variants, metadata or approval status due to channel-specific transformation rules, lazy fallbacks or cache timing. Testing must verify asset consistency across all storefronts.

13 · Where it applies

Relevant services and sectors.

14 · Questions

Common questions about Akeneo Asset Manager integrations.

How do we keep product images in sync between Asset Manager and multiple storefronts?

iWeb builds a synchronisation pipeline where Asset Manager is the source for product media. When images are added, updated or removed in Asset Manager, the integration propagates the change to all connected commerce platforms within the configured latency window (usually minutes). Commerce platforms receive asset URLs, metadata and transformation rules; Asset Manager holds the canonical versions.

What happens when an asset is deleted or moved in Asset Manager?

The integration detects asset retirement and notifies commerce systems so storefronts can show a placeholder or fallback image instead of a broken link. Asset teams can schedule asset deprecation in advance so commerce teams have time to find replacements. The integration tracks asset lifecycle (created, approved, published, retired) for audit and compliance.

How do we handle different image sizes and formats for mobile, tablet and desktop?

Asset Manager defines transformation rules (crops, resizing, format conversion) once. The integration applies the correct variant to each commerce platform based on its requirements. For example, Shopify may request 600x600px JPEG; Adobe Commerce may request 1200x1200px WebP. Asset Manager generates and caches all variants so storefronts receive optimised images without delay.

Can Asset Manager enforce alt-text and accessibility standards automatically?

Asset Manager can require alt-text as a mandatory field before assets are approved. iWeb integrates this into the approval workflow so no image goes to commerce without ALT metadata. The integration can also validate that required metadata (captions, usage rights, SEO keywords) are complete before publishing.

How do we schedule campaign assets to go live at a specific date and time?

Asset Manager allows publishing dates to be set in the approval workflow. iWeb integrates Asset Manager's scheduling with commerce platforms so assets are held in Asset Manager until the release date, then automatically published to storefronts. Campaign teams can see the schedule in one place and trust that assets will appear on time.

What happens if an asset approval is rejected or recalled?

Asset Manager records the rejection reason and version history. iWeb integrates rejection notifications so editorial teams can fix the asset and resubmit. If an already-published asset is recalled, the integration can remove it from storefronts or revert to a previous version depending on the governance rules set up.

How do we prevent unauthorised teams from accessing or publishing assets?

Asset Manager supports role-based access control (viewer, editor, approver, admin). iWeb integrates these roles with approval workflows so only authorised users can release assets to storefronts. For multi-brand estates, the integration can enforce asset-access boundaries so each brand's assets stay separate.

Can we see which product images are driving the most engagement on each storefront?

Yes. Commerce platforms report asset usage, clicks and performance metrics back through the integration. iWeb collects these signals and makes them visible to asset teams in Asset Manager or a connected analytics dashboard. This helps teams decide which images to refresh, reposition or retire.

What if a storefront goes down or the Asset Manager connection fails?

iWeb builds retry logic and dead-letter queues into the integration. If Asset Manager is temporarily unavailable, storefronts continue to serve cached assets. When the connection recovers, queued asset updates are processed in order. The integration monitors for prolonged outages and alerts asset and commerce teams immediately.

How do we localise asset metadata (alt-text, captions) for different languages and regions?

Asset Manager can store metadata variants for each language (e.g. English alt-text, French alt-text). iWeb configures the integration so each regional storefront receives the correct language variant. This ensures product images have SEO-friendly, accessible alt-text in the customer's language.

Can Asset Manager integrate with our headless CMS and content platforms?

Yes. iWeb connects Asset Manager to headless CMS platforms (Contentful, Storyblok, Sanity, etc.) so editorial assets (campaign graphics, landing-page images, brand content) flow into content systems. Asset approval status and publishing schedules are respected, so content teams only see approved assets.

How do we ensure downloadable product files (datasheets, instructions) stay up to date?

Asset Manager can hold versioned documents linked to products in PIM or commerce. iWeb configures the integration so when a new document version is approved, it replaces the old one across all storefronts. Version history is maintained for compliance and audit trails.

What monitoring and alerting do we have if asset delivery fails?

iWeb sets up monitoring for missing assets, broken URLs, failed transformations, stale metadata and approval queue backlogs. Alerts go to the right team (asset manager, editorial lead, commerce ops) immediately. The integration logs all asset movements for audit and troubleshooting.

How do we handle asset backups and disaster recovery?

Asset Manager holds the source assets; commerce platforms hold cached copies. iWeb ensures Asset Manager backups are retained and recovery procedures are tested. In a disaster, asset copies can be restored from commerce caches or Asset Manager snapshots while the source system recovers.

Next step

Have a Akeneo Asset Manager 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 →