Find below a list provided by OTTO of the most common errors and OTTO's advice to solve them:
Error |
Details |
How to solve it |
---|---|---|
"100013 - EAN_MUST_BE_UNIQUE" |
Within your product selection on Otto, this EAN is already used for another product. |
You need to make sure that every product has a unique EAN. The SKUs with the EAN must first be deactivated so that the new SKUs with the same EAN can be imported. |
"200003 - WRONG_FORMAT" |
Make sure to review the attribute rules and/or the feed preview. |
Please transmit data for the fields only in the correct data format. |
"400007 - WRONG_SALE_PRICE_PERIOD" The start date for the reduced price must be greater or equal than today. The timestamp for "startDate" does not map the processing time in the OTTO system. |
 |
The startDate should be set systemically when uploading the data to OTTO. |
"200004 - VALUE_MUST_BE_UNIQUE" In this case, the SKUs have been imported under a different productreference without first deactivating the SKUs under the existing productreference. The affected SKUs are online but no changes/adjustments can be made to the product data for these SKUs. |
The attribute "productreference" is the one used to set variation relationships on Otto (parent id). |
If this error occurs, the affected SKUs must be deactivated and then transferred again. This is the only way to resolve the error and changes to the product data will be possible again. The necessary steps would be as follow:
|
"500001 - MANDATORY_ The attribute X must be maintained for the category Y for legal reasons. During data transfer, one or more legally relevant attributes are missing. Â Example: For legal reasons, the 'Material composition' attribute must be maintained for the 'Plaid' category. |
For certain categories, some LEGAL attributes are mandatory.Â
|
Make sure to review your feed and submit the mandatory information. |
"100017 - INVALID_VALUE_DEFINITION" For the attribute X either the attribute name or the value is not given. |
Some of the attribute you set are empty or contains " " only. |
Check the ID with the preview and make sure to send valid content.
|
"200001 - WRONG_TYPE" The type of the field allows the input of "" (INT=integers; FLOAT=decimals). Change the data type according to the defaults. |
Ex: you send the weight unit where it should not be provided. |
Each attribute also contains information about which data type is permitted. Make sure to respect the value types, so it can be analyzed by Otto. |
"100003 - ONLY_EAN_ALLOWED" The EAN (GTIN) must be specified as a numeric, 13-digit value and in a globally unique value rang of the GS1 standard. For example, may not begin with 2. |
 |
Pre-validation of the EAN for validity, e.g., to an initial number of 2 (not allowed). |
"100006 - INVALID_VALUE_ X is not a valid default value for the attribute Y. You can find the list of defaults in the API Categories endpoint under the corresponding category. |
 |
Make sure you set the attribute's value across the list of accepted values. |
"100010 - INVALID_VALUE_COUNT" Only a single value may be specified for the attribute \"{0}\". Several values were sent for attributes. |
 |
Make sure you set the attribute's value across the list of single accepted values. |
"100019 - INVALID_VALUE_DEFINITION" To display the sustainability seal ''{1}'' the corresponding license number ''{0}'' is required. If the customer maintains a feature such as "sustainability seal" in the tool, the mapping feature for the license number must also be maintained. All values can be clustered via the "featureRelevance=Sustainability". |
 |
Representation of "Sustainability" features in a group with the note that if "Sustainability Seal" is maintained, the corresponding license number is to be maintained. |
"200002 - VALUE_TOO_LONG" The value you maintained is too long. Shorten the value to X characters according to the character limit from the API documentation. |
You might have not respected the characters' limitation for such attributes. |
The limits described at the endpoint documentation are already pre-validated and presented directly to the customer. Use the function SMARTTRUNC to limit the amount of characters automatically. |
"100008 - INVALID_VALUE" "" is not a valid brand. Maintain a valid value. Please select only brands that you can query via the Brands endpoint in the API. |
Otto allows the product selection over a list of accepted values. |
Please make sure to map your catalog brands with the ones allowed on Otto. If your brand is not within the list, please contact Otto support for brand creation. Once accepted, contact the Lengow support team for a structure update. |
"400009 - SALE_PRICE_BIGGER_THAN_ The reduced price must be lower than the standard price. |
Adjust the prices accordingly. |
The prices should be checked against each other and validated before the transfer so that the sale price is smaller than the standard price. |
"400008 - WRONG_SALE_PRICE_PERIOD" The end date for the reduced price must be greater than or equal to today. |
 |
The endDate must be in the future and should be set by the customer. |
"100005 - INVALID_VALUE_CATEGORY" "" is not a valid product category. Please select only categories that you can query via the Categories endpoint in the API. |
 |
Make sure all categories are mapped at the first feed step, Categories mapping. |
"400014 - INVALIDE_VALUE_ The MSRP must be greater than zero. Please check the deposited price. |
 |
If an "amount" is maintained for "msrp", this value must not be =0. In this case, the value should be removed from the export. |
Â