Amazon: error 8058
About this article
This article explains what Amazon error 8058 means, why it occurs, and how to resolve it on ChannelEngine.
Table of contents
Introduction
Error 8058 occurs when you provide an invalid value for a required attribute. Amazon validates all attribute values against its accepted value definitions. When a submitted value does not meet those requirements, the data is rejected for the affected SKU.
Cause
This error is typically caused by one of the following:
- A required companion field is missing. For example, a weight value is provided, but the
item_weight_unit_of_measureattribute is left empty within your category-specific mappings. - A field contains a value that is not on Amazon's accepted values list for that attribute.
- A field contains a value in the wrong format, such as a text string where a numeric value is expected.
- A value exceeds the maximum character or numeric limit for the field.
Resolution
To resolve error 8058, follow these steps:
- Open the affected SKU in Listed products, Validation and feedback.
- Identify the field name specified in the error message returned by Amazon.
- Download the category-specific inventory file template from the Add Products via Upload section in Amazon Seller Central.
- Open the Data Definitions tab in the template and review the accepted values for the field in question.
- Correct the value in your product data in the Mappings step on ChannelEngine, ensuring that all companion attributes for the corrected attribute are also mapped.
- If the error is about
title/item_name, confirm:- Export content is enabled in Mappings, Content mappings.
- No product rule sets Export content to No.
- Wait for ChannelExport to re-export your product data.
NB: attributes like weight, dimensions, and volume each require a corresponding unit of measure. Always check that both the value attribute and its unit attribute are populated when submitting physical product attributes.
More information
More information on this error can be found on Amazon's Seller Central.
Comments
0 comments
Article is closed for comments.