Feed quality score
The Quality check starts with your feed quality score. The score is based on how much of your export data is either incomplete or incorrect.
There is a colored bar showing three things.
- Blue: blue is the number of checks passed, which refers to fields that are filled with valid data.
- Pink: in pink you see the number of mandatory fields that are empty or incorrect.
- Orange: in orange you see the number of recommended fields that are empty or incorrect.
Below the score there is a line-by-line description of any problems with your feed. At the right, you will see "Action" buttons to assist you in making the necessary adjustments to maximize your feed quality score. The "Finalize" button takes you to the Finalize-step, where you can link your fields in Channable to export fields. The "View" button shows you a list of products that have the issue.
Types of errors
There are a number of different issues that the Quality check will show. You will encounter most of the following error messages. This section explains how to solve each one.
-
'description'/'size'/'brand' contains values that are empty
-
'availability'/'condition'/'mpn' is not connected to a field, check the mapping in 'Finalize'
-
'id'/'gtin'/'ean' contains values that are not unique
-
'gtin'/'ean' contains invalid EAN/GTIN values
1. 'description'/'size'/'brand' contains values that are empty
What does the error mean? If the error is shown it means that the field you linked in the Finalize-step is empty for a number of products. You can click on the error to see for which items the field is empty.
How do I solve this error? How to solve this error depends on the missing information and if the information is available in another field of your items. For example, if the size is missing for some products but you have always included the size in your titles, you can use a search for value rule to fill in the missing sizes. However, if the information is not available in another you will have to add the information in your import file.
2. 'availability'/'condition'/'mpn' is not connected to a field, check the mapping in 'Finalize'
What does the error mean? When you see this error it means that in the Finalize-step you have not linked an internal field to the channel field name. Clicking on the button to the right will forward you to the Finalize-step where you will see a "-" symbol under the internal field.
How do I solve this error? To solve the error you need to link an internal field to the channel field name in the Finalize-step. For example, for the channel field name "availability" you can link the internal field "availability".
3. 'id'/'gtin'/'ean' contains values that are not unique
What does the error mean? Identifiers such as id, gtin, and ean codes should be unique for every item, meaning that there should not be multiple items that have the same identifier. If it does happen that one of these identifiers is shared between items you will see this error.
How do I solve this error? There are two ways to solve the error. If the items that share the identifier are the same item, 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.
4. 'gtin'/'ean' contains invalid EAN/GTIN values
What does the error mean? There are certain constraints that can make an EAN code or GTIN code valid and whenever these constraints are not met the code is considered invalid. This error shows you which items contain an invalid code.
How do I solve this error? If the level of the error is "recommended" you can check the items that contain the error and change the code in your import file to a valid code. If the code is empty you will not necessarily need to add it to your import file.
However, if the level of the error is "mandatory" the code is necessary and needs to be filled in correctly for all items in the feed. You can either exclude the items that contain an invalid code from your feed, or you can change and add the codes in your import file so that they become valid codes.