Amazon Error 8058: Fix Missing Required Fields

Error 8058 is Amazon telling you that your flat file row is missing one or more fields it considers mandatory. The full message reads: "Missing required attributes: [attribute_name]". It is one of the most common upload rejections, and it is often caused by something as simple as a blank cell in the wrong column.

This guide covers what triggers 8058, how to identify the missing fields, and how to fix the error, including the less obvious cases where fields become required based on other values in the same row.

What error 8058 actually means

When you upload a flat file, Amazon validates each row against the schema for that product type. The schema defines which fields are required, which are optional, and which are conditionally required (more on that below). If a required field is blank or missing entirely from your row, the upload fails for that row with error 8058.

The error message usually names the missing attribute. For example: "Missing required attributes: brand_name" or "Missing required attributes: external_product_id_type". When multiple required fields are missing, the message may list several at once or fire separate 8058 errors for each one.

Required fields vary by product type

Amazon does not have a single universal set of required fields. Each product type (Clothing, Grocery, Electronics, Home, and so on) has its own template with its own required columns. A field that is optional in one category may be mandatory in another.

For example, "size_name" and "colour_name" are required for most Clothing listings but optional for Books. "material_type" is required in some Home subcategories but not in others. This means you cannot reuse a flat file template from one category for another without checking the requirements.

Commonly missed required fields

These are the fields that cause error 8058 most frequently, based on our experience with UK flat file uploads:

• product_type: tells Amazon which product category the listing belongs to. Every row needs this, and leaving it blank is surprisingly common when copying data between templates.
• brand_name: the brand as registered in Amazon Brand Registry. Must match exactly, including capitalisation.
• manufacturer: often the same as brand_name, but a separate field. Amazon requires it on most product types, and sellers regularly leave it blank assuming the brand field covers it.
• item_type_keyword: a single keyword that tells Amazon what the product is (e.g. "running-shoes", "coffee-mug"). The valid values are specific to each category, and a typo or unsupported value will also cause a rejection.
• external_product_id_type: must be set to "UPC", "EAN", or "GTIN" alongside the barcode value. Missing this field while providing the barcode itself triggers 8058.
• Category-specific fields: size_name, colour_name, material_type, department_name, and others depending on the product type.

How to find which fields are required

There are two reliable ways to check which fields Amazon requires for your product type.

1. The Data Definitions tab

Every category-specific flat file template downloaded from Seller Central includes a "Data Definitions" tab. This tab lists every column in the template along with its status: Required, Optional, or Conditionally Required. It also includes a brief description of what each field expects.

To get a fresh template: go to Seller Central, navigate to Catalogue > Add Products via Upload, select your product type, and download the template. Do not reuse an old template. Amazon updates required fields periodically, and a template from three months ago may be missing new required columns.

2. The Product Type Definitions API

If you submit listings programmatically via SP-API, you can query the Product Type Definitions API to get the current schema for any product type. The schema response includes a "required" flag on each attribute. This is more reliable than reading the template manually because it reflects Amazon's live validation rules rather than a downloaded snapshot.

Fixing error 8058

The fix is straightforward in most cases: populate the missing field and resubmit.

1. Open the processing report Amazon returned after your upload. Find the rows with error code 8058 and read the error message to identify which attribute is missing.
2. Open your flat file and find the column for that attribute. If the column exists, fill in the correct value for every affected row. If the column does not exist in your file, you are using the wrong template, as the required column was never included.
3. Download a fresh category-specific template and ensure all required columns are present. Copy your data into the new template rather than adding columns to the old one, since column order matters in some template formats.
4. Resubmit the corrected flat file and check the new processing report.

Partial updates and required fields

A common trap: you submit a partial update (for example, only changing the price or quantity) and leave other fields blank because you did not intend to change them. Amazon still requires certain fields on every row, regardless of whether you are updating them. brand_name, product_type, and external_product_id are typical examples.

If you are doing a partial update, either include all required fields alongside the fields you are changing, or use the "PartialUpdate" listing action, which has a smaller set of mandatory fields. Check the Data Definitions tab for which fields are required under each listing action.

Conditional required fields

Some fields are not always required. They become required when another field in the same row is set to a particular value. These "conditionally required" fields are a frequent source of 8058 (and the related error 90041).

Common examples:

• batteries_required = "true": makes battery_type and number_of_batteries required.
• is_expiration_dated_product = "true": makes shelf_life or expiration_date fields required.
• variation_theme: setting a variation theme on a parent listing makes parentage and the theme's attributes (e.g. size_name, colour_name) required on child rows.
• fulfillment_channel = "DEFAULT" (FBA): may require additional fields like package dimensions and weight that are optional for merchant-fulfilled listings.

The Data Definitions tab marks these fields as "Conditionally Required" and states the condition. Read the notes carefully when populating fields that trigger dependencies.

Error 8058 vs error 90041

Both errors mean a required field is missing, but they fire at different validation stages and for different reasons:

• 8058: fires during the initial schema validation pass. A top-level required attribute is blank or absent from the row. The error message names the missing field directly.
• 90041: fires during deeper product-type-specific validation. The row passed the initial schema check, but a conditionally required field is missing based on other values in the row. The error message is often less specific, sometimes referencing a group of related attributes rather than a single field.

If you are seeing both 8058 and 90041 on the same upload, fix the 8058 errors first. Some 90041 errors resolve on their own once the top-level required fields are present, because Amazon's conditional logic can now evaluate correctly.

Preventing 8058 before upload

Most 8058 errors are preventable with a pre-upload check:

• Always start from a fresh category-specific template downloaded from Seller Central. Never reuse templates from previous uploads or different categories.
• Before submitting, scan every column marked "Required" in the Data Definitions tab and confirm no rows have blank cells in those columns.
• For variation listings, confirm that parent and child rows both have their respective required fields filled in. Parents need parentage and variation_theme. Children need the variation attributes (size, colour) plus all the standard required fields.
• If you use conditional fields like batteries_required or is_expiration_dated_product, check whether they trigger additional requirements.

Our flat file errors guide covers other common errors you may encounter alongside 8058, including 8541 (catalogue conflicts), 8572 (barcode mismatches), and the silent FBA-to-FBM switch.

If you want automated alerts when Amazon rejects rows in your feed, our flat file monitor explains how to set that up.