Send different attributes to different channels

Your website, marketplace and ERP each need a different set of fields from the same product. SKULaunch scopes attributes to channels, so one product record holds everything, and each channel receives only what it needs, in the shape it expects.

The problem

Without channel scoping, teams keep a copy of the product per channel: a website version, a marketplace spreadsheet, an ERP extract. Each is edited separately and they drift. Or every channel gets every field, so marketplaces reject feeds with unexpected columns and the website shows internal data it should not.

Before and after

An illustrative example for one product across three channels.

Before: three copies

Website description updated in March. Marketplace spreadsheet still has last year's title. ERP extract missing the new dimensions.

After: one record in SKULaunch

• Website: full description, all filter attributes, SEO fields
• Marketplace: title to its formula, required attributes, bullets
• ERP: codes, units, weights and dimensions only
• All three generated from the same approved record

How it works in SKULaunch

1. Define channels. Set up each destination, such as your website, a marketplace or the ERP.
2. Scope attributes. Choose which attributes each channel receives.
3. Measure readiness per channel. See completeness against each channel's requirements.
4. Publish or export. Send each channel its fields from the same record.

One record, many views

The principle is simple: hold every fact once, and decide per channel what to show. Channel-specific content, such as a shorter marketplace title, becomes its own attribute rather than an edited copy of the product. That way a spec change made once reaches every channel, while each channel keeps its own presentation.

What changes

No more per-channel copies. Every channel gets the right fields from the same up-to-date record.

Common questions

Can channels need different copy?

Yes. Hold channel-specific titles or descriptions as separate attributes.

Can we see if a product is ready for one channel but not another?

Yes. Completeness is measured per channel.

Which channels are supported?

Connectors include Magento, Akeneo, Shopify, Mirakl, Plytix and WooCommerce, plus file exports.

See different copy per channel, marketplace syndication, and ecommerce sync.