The role of channels in product enrichment

Channels are named contexts for PIM product enrichment. In the current implementation, a channel is associated with the attribute requirements of a product family: it is used to define which attributes are required in a given enrichment context. A channel has a persistent code, order, and language-specific names.

In the current implementation, a channel is not a separate price list, a product visibility switch, or a price or availability context automatically selected by the storefront. Channel-specific product attribute values have not yet been implemented in the current enrichment view.

What does a channel define?

AI Commerce 's PIM channel defines a single, persistently coded product enrichment context. A product family attribute can be associated with the channel and marked as mandatory. The channel's References count tells you how many product family attribute rows use that channel.

The same attribute can belong to a product family with different channel requirements, but this does not mean that the product will have a different name, description, price, or availability across channels. The current product enrichment uses the AICC channel as the active channel for viewing attribute groups, requirements, and mandatory information.

Language-specific channel names make it easier to identify in the dashboard. Integrations and CSV structures use a permanent channel code, so the code must be designed before creation and cannot be changed later.

Check and search for channels

In the Channels view, the /pim/channels list shows the columns ID , Code , English name , Finnish name , Order , and References . References is the number of attribute rows, not the number of products or published product data.

The Search channels field searches for a channel by code and language-specific names. The search does not change the data, and the list can be reloaded if there are more than one page of results. Open the record by clicking on the ID or selecting Open from the row.

If a language-specific name is missing, the view can use the channel code as an identifier. It is therefore a good idea to keep the code short, descriptive, and consistent across environments.

Create a new channel

In the Channels view, select New Channel to create a new channel . Fill in the following information:

1. Enter Code . Use lowercase ASCII letters, numbers, a dash or an underscore, for example web or marketplace-fi .
2. Enter the Order as an integer. A lower value places the channel earlier in the channel lists.
3. In the Translations section, enter the channel display name for each required language.
4. Select Save channel .

The code must be unique. After creation, the dashboard will open the new channel details page, and the code will become read-only. If the code is incorrect or already in use, correct it before saving again.

The channel registry is a PIM structure, so before creating, verify the owner of the code, its purpose, and the spelling used in integrations. Do not create another channel with almost the same name just for a temporary experiment.

Edit channel order and names

The channel details page is code locked. You can change the Order value and language-specific names. Changes in edit mode are automatically saved after a short delay; the separate Save Channel button is only used when creating a new channel.

Make one logical change at a time and wait for the save to complete before exiting. An incorrect order or language-specific value will display a field error and will not be silently replaced with a default. The same language may only appear once in translations.

Changing the name does not change the channel code or product family attribute references. The integration must use the code and not the user-visible translation as a permanent identifier.

Delete the channel only after references

Deleting a channel is initiated by using the Delete function on the details page. The confirmation shows the number of attribute rows referring to the channel. The backend blocks the deletion if the number is greater than zero.

If the channel is in use, open the attribute requirements for the product families that use it and remove or move references as planned. A channel should not be removed simply because its display name is outdated; the name can be changed without breaking the code and references.

When there are no more references, confirm the deletion. The deletion will also delete the channel's language-specific names. Before deleting, make sure that the owners of the integrations and CSV profiles do not use the persistent code in data flows.

Channels do not yet choose the price or availability of the storefront

AI Commerce 's current PIM channel registry does not demonstrably select product price, name, description, or availability in the storefront. The dashboard's own help text limits channel-specific product attribute values for later enrichment implementation, and current backend searches use the channel to limit the attribute requirements for the product family.

If you need different pricing, visibility, or availability for different markets, use the existing pricing, domain, customer group, status, and publishing tools for that feature. Don't assume that code added to the Channels view will change the product information in your online store.

The channel registry creates a stable classification for future and current PIM structures, but the intended use must be verified on a per-feature basis. The mere existence of a channel does not publish a product to any external channel or product feed.

Good to know

The channel code in the Channels view is permanent and unique. The product family attribute rows referring to the channel prevent deletion, and language-specific names can be changed without changing the code. The feature is part of the PIM product information management structures and its availability depends on the customer's subscription and usage rights.

Design your code to be consistent across environments, document its purpose, and use names only as user interface translations. Check the References chapter before making structural changes, and verify external data flows before deleting.

Summary

The Channels view manages the permanent channel codes, order, and language-specific names for PIM product enrichment. In the current implementation, channels are linked to the attribute requirements of product families. References indicate the number of attribute rows using the channel, and a channel in use cannot be deleted.

The channel does not currently publish a product, change the price, or hide a product in the storefront. Create the channel only in a clear enrichment context, keep the code stable, and change the order or names on the autosaved details page if necessary.