Skip to main content

Digital Asset Management

The right image on the right variant in the right channel

Assets are linked to families or individual variants with a role and channel scope. Variants inherit family media unless they have their own.

Walk through it All capabilities

The capability

Relationships, not attachments

A hero image attached directly to 300 variants becomes 300 links to maintain. A dimension drawing that is only correct for one size gets shown on all of them. The problem is not storage, it is the relationship between asset and product.

Autonera links assets to products with a level, a role and a channel scope. A family-level primary image applies to every variant until a variant gets its own; a variant-specific dimension drawing overrides the generic one. Channel scope controls which assets each destination receives, so print can use high-resolution drawings while marketplaces get approved product shots only.

Relationship changes are governed like data changes. Replacing a primary image or relinking a compliance document can require approval, and assets that lose all product links are surfaced as orphans rather than silently remaining in the library.

Problems it solves

Where this work usually breaks down

  1. 01

    Same asset linked hundreds of times

    Updating a family image means touching every variant.

  2. 02

    Wrong drawing on the wrong size

    Generic drawings are shown where a variant-specific one exists.

  3. 03

    Channel-inappropriate media

    Internal or print-only files reach marketplaces.

  4. 04

    Orphans accumulate

    Retired assets remain in the library with no product context.

Functional capabilities

What Product Asset Relationships includes

Many-to-many links
One asset can serve many products and one product can use many assets.
Asset roles
Primary image, gallery, dimension drawing, manual, compliance document and custom roles.
Family inheritance
Variants inherit family assets by role unless overridden.
Channel and locale scope
Limit each link to the channels and locales where it applies.
Orphan detection
Report assets without product links for review or archive.
Governed relinking
Require approval for changes to sensitive roles such as compliance documents.

How it works

Resolve assets for a ladder variant

Pick a variant and channel. The 24 inch model has its own hero and drawing; the others inherit family assets. Channel scope removes assets not approved for that destination.

Fiberglass step ladder family · assets resolved for LD-24 on web

  • Primary image · 24 in model heroVariant-specific
  • Dimension drawing · Dimension drawing, 24 inVariant-specific
  • Compliance document · Safety data sheetInherited from family
  • Application image · Workshop lifestyle photoInherited from family

ORPHANED ASSETS

  • Retired hero, 2019

Assets with no product link are surfaced for review before they are archived.

In industrial operations

A ladder manufacturer ships variant-specific drawings

Generic drawings appeared on every ladder height, and distributors repeatedly asked for the correct dimensions.

  1. Family-level hero and compliance assets are linked once.
  2. Variant-specific dimension drawings override the generic one.
  3. Print and marketplace scopes are set per role.
  4. Orphaned legacy images are archived after review.

Result: Each variant shows correct dimensions, and family updates happen in one place.

Autonomous operations

How autonomous execution changes product asset relationships

Agents propose asset links from file metadata and image content, and detect conflicts between family and variant assets.

Agents carry out

  • Suggest product links for new assets
  • Detect variants showing generic drawings when specific ones exist
  • Report orphaned assets
  • Check channel scope before syndication

People decide

  • Approve links for compliance roles
  • Decide archive or relink for orphans
  • Set channel scope policy

Evidence recorded

  • Who linked or unlinked each asset
  • Inheritance resolution used for each export
  • Orphan decisions

Related capabilities

Works alongside

Feature guide

Digital Asset Library

Images, drawings, video and documents searchable by product context.

Feature guide

Product Families & Variants

Family templates, variant axes and inherited values with SKU-level exceptions.

Feature guide

Asset Versioning & Rights

Approved, licensed versions selected per channel, region and date.

Feature guide

Channel-Specific Product Content

Templates that shape one governed record for each buying channel.

Capability area

Digital Asset Management

See where Product Asset Relationships fits in the wider Digital Asset Management capability.

Buyer FAQs

Questions evaluators ask

Do variants automatically inherit family images?

Yes, by role. A variant-specific asset with the same role overrides the inherited one.

Can one asset belong to products in different families?

Yes. Links are many-to-many, so a shared manual can apply across families.

How are channel-specific images handled?

Each link carries channel and locale scope that syndication respects.

What is an orphaned asset?

An asset with no product link. Orphans are listed for review so they can be relinked or archived.

Are relationship changes audited?

Yes. Link and unlink actions are recorded and sensitive roles can require approval.

Your next step

See Product Asset Relationships on data like yours.

Bring a real file, catalog or record set. We will walk through how Autonera would handle it and where your team keeps the final say.

Book a Demo