What is a channel?
A channel in SKULaunch defines a specific use case or output context for product data. Channels allow you to control which attributes are relevant for a given purpose without changing your core data model.
Typical examples include:
eCommerce
Marketplace listings
Print catalogues
Supplier source data
Internal data views
Channels do not store data themselves. Instead, they reference existing attributes and define where and how those attributes are used.
Why channels matter
Channels make it possible to:
Reuse the same attributes across multiple outputs
Keep schemas clean and purpose-driven
Avoid bloated “one size fits all” attribute sets
Align data with downstream systems and teams
For example, an eCommerce channel might require rich descriptions, images, and nutritional data, while a Source Data channel may only reference raw supplier inputs.
Viewing channels
To view existing channels:
Navigate to Product settings → Channels
The table shows:
Channel code
Label
Number of related attributes
Creation date
Click a channel to view or manage its attributes
This view helps you understand how attributes are distributed across different outputs.
Creating a new channel
To create a channel:
Click New channel
Enter a Code
System-friendly and lowercase
Example:
e_commerce,source_data
Enter a Label
Human-readable name
Example: eCommerce, Source Data
Click Create
The channel is now available but contains no attributes yet.
Linking attributes to a channel
After creating a channel:
Open the channel
Click Link attributes
Select the attributes you want to associate with this channel
Save your selection
Only linked attributes will be considered part of that channel.
Managing channel attributes
Within a channel, you can:
View all linked attributes
Remove attributes that are no longer needed
Adjust channel composition as requirements change
Removing an attribute from a channel does not delete the attribute or its data. It only removes it from that specific output context.
Channel vs attribute groups
Channels and attribute groups solve different problems:
Attribute groups organise attributes for UI and usability
Channels define which attributes are relevant for a specific output
An attribute can belong to multiple channels and multiple attribute groups at the same time.
Best practices
Create channels based on real output needs
Keep channel scopes focused and intentional
Reuse attributes across channels rather than duplicating them
Review channel composition as integrations evolve
Avoid using channels as a replacement for taxonomy or families
Well-designed channels keep your product data flexible, scalable, and easy to maintain as your catalogue grows.