Understanding Error 90236: Blocked Attribute Values in Amazon Listings
Error 90236 occurs when sellers try to assign a blocklisted value to a product attribute. This reference explains what triggers the error, how to identify the problematic value, and how to resolve it by selecting compliant attribute data.
Overview
Error 90236 is a product listing validation error that Amazon sellers may encounter when creating or updating listings in Seller Central. This error triggers when a seller attempts to assign a value to a product attribute that Amazon has explicitly restricted. Understanding how to identify and resolve this error can save sellers significant time and prevent listing delays.
Key Points / What Sellers Need to Know
- Blocklisted values are enforced automatically — Amazon maintains lists of prohibited values for certain product attributes, and any attempt to use these values will be rejected at submission.
- The error message identifies the problem — Error 90236 specifies both the attribute name and the restricted values, giving sellers a clear starting point for correction.
- This applies to both new and existing listings — Sellers may encounter this error when creating a listing for the first time or when editing an attribute on a product already in the catalog.
- Flat file uploads and API submissions are affected — This validation check runs regardless of whether a seller submits data through the Seller Central interface, inventory file uploads, or the SP-API.
- Resolution requires choosing an approved value — Sellers must replace the blocklisted value with a compliant alternative that accurately describes their product.
How This Error Works
When Amazon processes a listing submission, it validates every attribute value against a set of rules specific to that product category and attribute type. For certain fields, Amazon maintains a blocklist of values that are no longer accepted, may be misleading, or violate catalog data standards. If a submitted value matches any entry on that blocklist, the system rejects the change and returns Error 90236. The error message follows the format: "Attribute '{attribute_name}' must not be changed to any of the following blocklisted values: {blacklisted_values}." This tells the seller exactly which attribute triggered the issue and which specific values are prohibited.
Common Causes and Affected Attributes
Sellers most frequently encounter this error when working with brand names, material types, color specifications, or other structured attributes that Amazon has tightened over time. For example, generic or placeholder values such as "N/A," "None," "Unknown," or overly broad descriptors may have been added to blocklists as Amazon works to improve catalog data quality. Sellers who are migrating listings, updating product details in bulk, or copying attributes from older templates are particularly susceptible, as previously accepted values may have since been restricted. Category-specific attributes can also carry their own blocklists that differ from one product type to another.
Analysis & Recommendations
Why This Matters
Listing errors can delay product launches and disrupt bulk upload workflows. Understanding how to quickly resolve Error 90236 helps sellers keep their catalog submissions on track and avoid repeated rejections.
Key Takeaways
- Error 90236 names the exact attribute and blocked values so sellers can pinpoint the issue immediately
- Always use current inventory templates and style guides, as accepted attribute values change over time
- Generic or placeholder values like 'N/A' or 'Unknown' are common triggers for this error
- Bulk upload users should validate files before submission to catch blocklisted values early
Recommended Actions
- →Review the full error message to identify the specific attribute and blocked value, then consult your category's style guide for accepted alternatives
- →Download the latest flat file template from Seller Central to ensure your attribute values align with current requirements
- →Audit existing listings periodically for attribute values that may have been added to blocklists since original submission
Comments
Join the discussion
Log in or create an account to share your thoughts on this update.
No comments yet. Be the first to share your thoughts!