This guide covers the form-based editors for configuring Product Link Rules, Naming Conventions, and Transformations on Asset Families.

All three editors are accessible from the Product Link Rules tab (for PLR and Naming Convention) and the Transformations tab on an Asset Family's edit page. Each editor includes a Form / JSON toggle, allowing you to switch between the visual form editor and the raw JSON editor at any time.

Naming Convention

The naming convention automatically extracts structured information from asset codes or filenames to populate asset attributes.

Empty State

When no naming convention is configured, you will see an Add naming convention button.

Configuring a Naming Convention

Click Add naming convention to display the configuration form. The form contains:

Note: When Code is selected as the source property, the Channel and Locale fields are automatically cleared and hidden, since asset codes are neither scopable nor localizable.

Removing a Naming Convention

Click the X button in the top-right corner of the naming convention card to clear all settings. The configuration will be reset to empty, and you can save the asset family to persist the change.

Product Link Rules

Product link rules automatically link assets to products based on configurable conditions. You can define up to 2 rules per asset family.

Empty State

When no rules are configured, you will see an Add rule button.

Adding a Rule

Click Add rule to create a new rule. Each rule has two sections:

Product Selections

Product selections define which products will receive the asset. Multiple selections combine with AND logic.

Choosing a Value

The Value field is a guided selector rather than a free-text box. Its behaviour depends on the operator.

For single-value operators (=, !=, STARTS WITH, CONTAINS, DOES NOT CONTAIN), a Choose a value type dropdown offers:

• Asset attribute: <code> — one entry per attribute of this asset family. Selecting it stores the {{attribute_code}} placeholder, so the product is matched dynamically against the asset's own value.
• Boolean: Yes (true) / Boolean: No (false) — for boolean product fields such as enabled. The value is stored as a real boolean, not as the string "true".
• Text value — reveals a free-text input where you type a static value.

For IN and NOT IN, the value becomes a list. Type a static value and press Enter to add it as a tag, or use the Add a value from the list dropdown to append an asset attribute placeholder or a boolean. Values already in the list are removed from the dropdown so they cannot be added twice. Switching between a single-value and a list operator converts the existing value automatically.

Click Add selection to add additional product selection conditions within the same rule. When a rule has more than one selection, each card gets an X button to remove it.

Assign Assets To

This section defines which product attribute receives the asset and how.

Choosing the Destination Attribute

The destination dropdown (Choose a product attribute or asset attribute placeholder) lists:

• Product attribute: <code> — the asset collection attributes linked to this asset family. This is the classic case: assets land in that attribute.
• Asset attribute: <code> — a simple text attribute of the asset family (neither scopable nor localizable). It is stored as {{attribute_code}}, so each asset resolves its own destination attribute at execution time from the value it carries.
• Other (custom placeholder) — reveals a free-text input where you can type any placeholder expression, for example {{collection_name}}.

If no asset collection attribute is associated with this asset family, a warning is displayed with a link to create one (if the user has attribute creation permissions).

Click Add assignment to assign assets to multiple product attributes from the same rule. When a rule has more than one assignment, each card gets an X button to remove it.

Unlinking Products

An assignment whose mode is add shows the checkbox Unlink products that no longer match after an update.

With the option ticked, editing an asset so that it no longer matches a product does not only link the asset to the newly matching products — it also removes the asset from the products that only matched through the previous value. Without it, the old link is left in place.

Sorting Options

Each assignment includes a collapsible Sorting options section. This section auto-expands if any sorting value is already set.

Dynamic Locale/Channel Assignment

Each assignment includes a collapsible Dynamic locale/channel assignment section. This section auto-expands if any value is already set.

Both dropdowns list the asset family attributes that can hold a locale or channel code: single option, option collection, and simple text (not text area) attributes.

Multiple Rules

You can add up to 2 rules. Each rule card displays its rule number and has its own X button to remove it. When two rules are defined, the Add rule button is hidden.

Removing Rules

• Click the X button on a rule card header to remove that individual rule.
• Removing all rules results in an empty configuration ([]), which can be saved without errors.

Transformations

Transformations automatically generate media variations from a source media file carried by your assets: thumbnails and resized packshots, colour and resolution conversions, watermarked images, format conversions (WebP, TIFF, AVIF) and AI-powered edits such as background removal or auto crop. You can define up to 10 transformations per asset family.

Each transformation reads one source media file attribute, applies an ordered list of operations, and writes the result to one target media file attribute of the same asset.

Who Can Configure and Run Transformations

Two distinct permissions govern the tab (Settings > Roles > Permissions > Asset Manager), on top of the edit rights on the asset family itself:

When Variations Are Generated

Saving a transformation defines the rule; it does not, on its own, produce the variations. Two mechanisms generate them.

Apply Transformations Automatically

Above the transformation list, a Apply transformations automatically Yes/No switch appears as soon as the family holds at least one transformation.

• Yes — variations are regenerated in the background every time the source media file of an asset changes: on asset creation, on a new upload in the asset form, and on updates coming from imports, mass edit or the API.
• No — nothing is generated when assets change. Variations are only produced when someone clicks Launch transformations. Use this when you want to control precisely when the (potentially credit-consuming) transformations run.

Launch Transformations

The Launch transformations button in the page header runs the Compute asset transformations job over every asset of the family. A notification confirms the launch: "Transformations have been launched. Once this job is finished, you will see your new variations updated in your assets."

Follow the job in Activity > Process tracker. Assets that could not be processed are listed there as warnings, with the transformation label, the asset code and the reason — for example an unsupported file type, a file that is too large, or a failed AI operation. The job continues with the remaining assets.

Which Variations Are Recomputed

Whether it runs automatically or from the button, a transformation only regenerates what is out of date. A variation is (re)computed when:

• the target attribute is empty; or
• the target file is older than the source file; or
• the target file is older than the last change made to the transformation itself.

The practical consequence: editing and saving a transformation marks its variations as stale, so the next run regenerates them, while the variations of the transformations you did not touch are left untouched and cost nothing.

Supported Source Files and Limits

• Supported source media types: JPEG, PNG, TIFF, GIF, PSD, WebP and AVIF. Any other file (PDF, video, office document, …) is skipped and reported in the job as an unsupported mime type.
• Source files larger than 200 MB are not transformed. The asset is reported in the job with an explicit "exceeds the maximum size allowed for transformation" message.
• The AI-powered operations (Remove background, Aspect ratio, Auto crop, AI prompt) have a much lower limit of about 32 MB. Beyond it the operation fails, and the asset is reported in the job with an error while the remaining assets are still processed.
• Up to 10 transformations per asset family.

Empty State

When no transformations are configured, you will see an Add transformation button.

Transformation Card

Each transformation is displayed as a collapsible accordion card. Click the card header to expand or collapse it. The card header shows the transformation label — or Transformation 1, Transformation 2… while the label is still empty — and a summary of its operations (e.g. "Scale, Colorspace").

When the family holds a single transformation, its card is expanded automatically; otherwise all cards start collapsed so long configurations stay readable.

Drag-and-Drop Reordering

Transformations can be reordered by dragging the handle on each card header. The order determines the processing priority — transformations are applied in the order they appear.

Configuring a Transformation

An expanded transformation card contains the following sections:

Label

A required, non-empty name for the transformation (e.g. Thumbnail_160x160). It identifies the transformation in the card header, in the job report and in validation messages, so a descriptive label pays off when something goes wrong.

Operations

One or more image operations applied in sequence, top to bottom. Available operation types:

Click Add operation to add another operation to the transformation. Each operation card has an X button in its top-right corner to remove it (as soon as more than one operation exists). Changing an operation type resets its parameters to that operation's defaults.

Convert Image Format

The Convert image format operation exposes only the controls that are meaningful for the selected format, so the parameters change when you change the Format dropdown. Switching format resets the parameters to that format's defaults.

Watermark

The Watermark operation composites an overlay image — a logo, a copyright mark — on top of the generated variation.

Watermark Image

A first dropdown selects where the overlay comes from:

• Upload an image — click Upload an image to pick a file from your computer. The selected filename is displayed next to the button, which then becomes Replace. While the upload runs the button shows Uploading…, and an error message is displayed if the upload fails.
• Use an existing asset — pick an asset family, then pick an asset from that family. The main media of the selected asset is used as the overlay. The selected asset is displayed as an asset card; remove it to bring the asset picker back. Only one asset can be selected, and if that asset is later deleted the field is cleared automatically.

Switching between the two sources clears the current image.

Watermark Placement

Source

Select the source media file attribute and optionally specify a channel and locale. Only media file attributes defined on this asset family are available — if the attribute you need is missing, create it first in the Attributes tab. Channel and locale fields only appear if the selected attribute is scopable/localizable respectively. Valid locales are filtered based on the selected channel; leaving a field empty means "all channels" / "all locales".

Target

Select the target media file attribute where the generated variation will be stored. Channel and locale fields behave the same as for the source.

On the asset form, a field used as a transformation target displays the helper "This field is used as a target in an asset transformation." Its content is overwritten every time the transformation runs, so it should not be filled in manually.

Filename and Output Format

Configure a prefix and/or suffix for the generated file. At least one of the two is required, so that each variation gets a unique filename. The default is the suffix _transformed. For example, a source file packshot.jpg with the suffix _thumb generates packshot_thumb.jpg.

The extension of the generated file depends on the operations:

• no format-changing operation — the variation keeps the format of the source file;
• Optimize JPEG — the variation is written as .jpeg;
• Convert image format — the variation takes the extension of the chosen format (.webp, .tiff or .avif).

Configuration Rules and Validation

When you save, the configuration is checked as a whole. Any problem is listed in a red banner at the top of the section, prefixed with the label of the transformation concerned. The rules to know:

• At most 10 transformations per asset family. Once the limit is reached, the Add transformation button disappears.
• The same operation type cannot be used twice within a single transformation.
• A single transformation cannot combine two operations that change the output format (Optimize JPEG and Convert image format). Use two separate transformations instead.
• Watermark must come after the operations that resize or repaint the image (Resize, Scale, Thumbnail, Aspect ratio, Auto crop, Remove background, AI prompt); otherwise the watermark would itself be resized or painted over.
• An attribute used as a source cannot be the target of a transformation.
• Two transformations cannot share the same target.
• For a given source attribute, the prefix + suffix combination must be unique.
• Source and target attributes must exist on the asset family, and the label must not be empty.

Removing Transformations

• Click the X button on a transformation card header to remove it.
• Removing all transformations results in an empty configuration, which can be saved cleanly. Variations already generated in the target attributes are kept as they are.

Form / JSON Toggle

All three editors include a Form | JSON toggle in the section header. This allows you to:

• Use the Form view for guided, visual editing.
• Switch to JSON view to see or edit the raw JSON configuration directly. 

Changes made in one view are reflected in the other when you switch. A configuration written in JSON that the form cannot represent — an unknown operation, for example — is still displayed in the form through the raw JSON parameter editor, so nothing is lost when switching views.

Saving Changes

After making any configuration changes, click the Save button in the page header. The page will display an "Unsaved changes" indicator when modifications have been made but not yet saved.