Inside Akeneo #1 – Channels & scope

Achtung: Dieser Beitrag ist mehr als drei Jahre alt. Er könnte veraltet sein.

This article is the first one of a series focused on the key concepts of Akeneo.

Channels
The purpose of a PIM system is to enable the propagation of your product information from a single point to many heterogeneous destinations. Those destinations could be an e-commerce website, a mobile application, a print catalog, a marketplace, or any third-party system. That’s what we are calling channels.

In Akeneo, you will be able to create as many channels as you want directly from the back-end. Each channel will have a few properties to define what should be the exact subset of data associated to the channel (locales, currencies, categories).

Scope
For a same product, some of your attributes could have different values depending on the channel. For instance, you could have a different description for your e-commerce website and your mobile application. Or different pictures!

Instead of multiplying the number of attributes (description_ecommerce, description_mobile, …) you can create in Akeneo only one description attribute and set its scope to „Channel“. An attribute with a „channel“ scope will allow the user to fill a different value for each activated channel directly from the edit form (as previewed in the animation below).

screen_scope4
Multichannel features are at the core of Akeneo. We will explain in our next post what are the relations between channels and completeness. Stay tuned!

Lesen Sie auch...

Inside Akeneo #2 – Data quality & completeness

We talked in our previous post about the relation between channels and scoped attributes in Akeneo. Another important channel-related mantra to keep in mind for our future users is : „There is no mandatory attribute in Akeneo„. It means that an user will never be prevented to create or save a product because he only…

Weiterlesen