ChannelEngine: go live on a channel in five steps
About this article
This article explains how to go live on a new channel in five easy steps, from importing your product data to publishing listings.
Table of contents
Step 1: provide your product data
Step 2: add and authorize the channel
Step 3: select products and map fields
Step 5: validate and resolve errors
Introduction
To configure a channel on ChannelEngine and make your products available for sale on it, follow a similar set of steps – submit your product data to ChannelEngine, add a channel, tell ChannelEngine which products to send and in which format, activate the channel, and fix any errors.
This is a quick-start guide for your first channel. Each marketplace has its own requirements, so read the relevant marketplace guide before you begin.
Overview
Refer to the diagram below to visualize how your product data travels from your system, through ChannelEngine, to the channel.
Requirements
Make sure you have the following ready:
- Product data from your PIM, ERP, webstore, or available as a product feed.
- An approved seller account on the marketplace you want to sell on. Check common requirements that marketplaces ask of sellers.
- The credentials that ChannelEngine requires to access your marketplace account, such as API keys or marketplace login details. The credentials differ per channel, so consult the respective marketplace guide.
- Access to your ChannelEngine tenant with sufficient permissions to add and configure channels.
Step 1: provide your product data
ChannelEngine imports product data from your source system and uses it to prepare and send product data to your connected channels. Your PIM, ERP, webstore, or feed remains the source of truth.
When you add or update a product in your source system, that change flows to every channel you list it on. There are three main ways to get the data into ChannelEngine.
| Method | How it works | Best for |
| Product feed | You provide a URL to an XML, CSV, or JSON file. ChannelEngine retrieves and imports it on a schedule. | Fast onboarding, non-technical teams, catalogs that change a few times a day. |
| Plugin | A prebuilt integration with your webstore or ERP platform, e.g.: Adobe Commerce or Shopify, pushes data to ChannelEngine. | Merchants already running on a supported platform. |
| Merchant API | Your own system posts products, prices, and stock directly to ChannelEngine, close to real time. | Large catalogs, frequent stock changes, custom workflows. |
Read more:
Step 2: add and authorize the channel
Adding a channel connects your ChannelEngine tenant to your seller account on the marketplace. See ChannelEngine: add a channel.
- In your ChannelEngine tenant, go to the Dashboard.
- Click + Add channel.
- Search for the channel and click + Add on its card.
- Complete the Setup step: enter the credentials the channel requires, or complete its authorization flow.
Authorization differs per channel. Some channels ask for an API key from your seller account, others use a login redirect. E.g.: Mirakl-based channels use a Mirakl Connect SSO account.
Each channel has its own marketplace guide in the Help Center that lists the authorization and configuration steps for that channel. Read it before you start the setup.
Step 3: select products and map fields
Step 3 is where you tell ChannelEngine which products to send to the channel, and how to translate your data into the structure the channel expects. It is the longest step and the one that determines how many errors you see when product data is exported to the channel.
Product selection
In the Product selection step, define which part of your catalog goes to this channel. You can select all products, or filter by brand, category, stock level, price, or any other field. Selections are per channel, so you can sell a different assortment on each marketplace.
Categorization
In the Categorization step, match your own category names to the categories of the channel. The category you choose determines which fields the channel requires, so categorizing is essential before you map fields.
If your catalog is large, generate category recommendations with AI category mapping and accept or reject them per category or per product.
Mappings
In the Mappings step, match your content and offer fields to the attributes of the channel. Start with the fields that apply to All products, then work through fields specific to each category. See ChannelEngine: content mappings and ChannelEngine: offer mappings.
Each line shows how many attributes are required to map, conditionally required, and optional, and how many of them you have already mapped. Unmapped required attributes can prevent a product from being exported or accepted.
Below is an example showing how your own fields map to commonly required attributes:
| Your field | Channel attribute | Note |
Name |
Product title | Often has a maximum length. |
Long_description |
Description | Some channels accept HTML, others reject it. |
Brand |
Brand | Usually required, and often validated against a fixed list. |
It is possible and often required to map your carriers to the carriers that are supported and accepted by a channel. Do so at Mappings, Carrier mappings.
Pricing and stock
In the Pricing step, map the price fields that the channel expects. In Pricing, Price rules: each price field of the channel appears as a separate tab, and per tab you map at least a Base price and a Min. price. Use price rules if you wish to adjust the price value before it is exported. E.g.: subtract a fixed amount, add a percentage to cover the commission of the channel, or convert to another currency.
The Stock step controls how much of your available stock is communicated to this channel. Exporting more stock than you can fulfill may lead to undesired cancelations. If needed, cap the stock quantity the channel sees using Stock limit or Stock buffer.
Step 4: activate and publish
Complete the Activation step of the channel. From that moment on, ChannelEngine exports your offers and content to the channel on a schedule and keeps prices, stock, and content in sync.
After activation:
- Check the Listed products overview to confirm your products reach the channel. Do so by checking the status of the product's export to the channel in the Overview tab.
- Allow time for the channel to publish. A successful export means ChannelEngine sent the data successfully. The marketplace may still, however, need to validate or manually approve the listing on its own timeline.
- Place a test order if the channel supports it, and confirm that the order, shipment, and return flows work end to end.
Step 5: validate and resolve errors
ChannelEngine sends your products to the channel, and the channel validates them. Typical checks are whether required fields are present, whether values use the expected format, whether field lengths are within limits, and whether the product meets the rules of its category.
To review the results, go to the Listed products step in the channel configuration and open the Validation and feedback tab. While the Listed products tab shows the general status of your offers and content, this tab shows the reason a specific product was not exported or was rejected.
Work through the errors as follows:
- Group the errors by message. One missing mapping usually explains multiple failed products.
- Decide where the fix belongs: in your mapping, or in your source data. A wrong field pairing requires a mapping update, an empty or malformed value requires a source data update.
- Update and wait for the next export cycle, or trigger a new import if you changed the source data.
- Check the tab again and repeat.
Common issues
| Issue | Likely cause | What to do |
| Products are not visible on the channel. | The products failed validation, or the channel has not published them yet. | Check the Validation and feedback tab, then allow time for the channel to publish. |
| Products are missing from the mappings view. | The products are not categorized, and the channel requires categorization. | Categorize them in the Categorization step. |
| A required attribute is reported as missing. | The attribute is unmapped, or the source field is empty. | Check Content mappings first, then check the value in your source system. |
| Child products are rejected. | Parent or grandparent products are not exported. | Include all levels of the hierarchy in your product selection. |
| Content or stock updates do not arrive. | The feed import failed, or the API integration stopped sending updates. | Check the validation report of the feed, or the logs of your integration. |
Next steps
Once your first channel is live, you can:
Comments
0 comments
Article is closed for comments.