This article is part of a guide series on setting up an API for your specific Marketplace in Channable. Each step in the process is crucial to ensure that your product data is correctly aligned with Marketplace requirements. Detailed instructions for each step can be found in the following articles.
For information about Marketplaces V2, please refer to this article.
Just like the quality step in feeds, this step provides instant feedback on setup quality, highlighting mandatory and optional errors.
Actions in the Quality step
The actions listed in the quality step identify errors and provide details on the items affected by the errors. They indicate the number of items impacted by a specific error, provide a detailed description of the error, and offer instructions on how to resolve it. Furthermore, there are 'Action' functionality buttons available to quickly address these issues. The 'Action' buttons are:
- View items: This functionality button allows you to see products with specific issues and will take you to the new Preview step.
- View in build: This functionality button redirects you to the Build step, where you can map a field to add the missing information.
- Set categories: This option is only available for the category-field and will direct you to the categories step, where you can set up the missing category.
- Show source: This option is only available for the ID-field. This will take you to the Settings-step. Note that the ID field cannot be modified after creating an API.
Types of Errors
The Quality step will display various types of issues, including most of the following error messages. This section will explain what each error means and how to resolve them:
| Error message | What does the error mean? | How do I solve this error? |
| Description/size/brand contains values that are empty | If the error is displayed, it indicates that the field you linked in the Build-step is empty for multiple products. You can click on the error to view which items have an empty field. | The action to take depends on the missing information and whether it can be found in another field within your items. For instance, if the size is missing for certain products, but has consistently been included in your titles, you can apply a search-for-value rule to populate the missing sizes. However, if the required information is not present in any other field, it will need to be manually added to your import file. |
| Availability/condition/MPN is not connected to a field, check the mapping in 'Build' |
When you encounter this error, it indicates that you have not linked an internal field to the channel field name in the Build step. |
In order to resolve the error, you need to link an API attribute to the field using the correct values from your import. By clicking 'View in Build', you will be directed to the Build-step, where you can connect the appropriate field to the attribute. |
| ID/GTIN/EAN contains values that are not unique | Identifiers such as ID, GTIN, and EAN codes should be unique for each item. This means that no two items should have the same identifier. If multiple items share the same identifier, an error will occur. | There are two ways to solve the error. If the items that share the identifier are the same, you can use a deduplicate items rule. However, if you want to keep both items because they are two different variants of the same product, you need to change the identifiers in your import file. |
| GTIN/EAN contains invalid EAN/GTIN values | Certain constraints must be met in order for an EAN code or GTIN code to be considered valid. Whenever these constraints are not met, the code is deemed invalid. This error will indicate which items contain an invalid code. |
In most marketplaces, the GTIN/EAN is considered 'mandatory,' indicating that the code must be provided and accurately filled out for all items in the API. You have the option to either remove items with invalid codes or modify and include the codes in your import file to ensure they are valid. |