Amazon Enforces New Listing Attribute Requirements for SP-API Sellers
Amazon will make previously optional attributes like "Material" and "Battery Type" mandatory for all SP-API and JSON LISTINGS FEED submissions. The new schema, returned by getProductTypeDefinitions, also trims enumerations (e.g., "Grey" → "Gray"). Sellers with ~2,300 electronics listings missing BatteryType must update now.
Overview
Amazon is introducing a comprehensive overhaul of product‑listing metadata that will affect every seller using the Selling Partner API (SP‑API) or the JSON LISTINGS FEED. The change reclassifies several previously optional attributes as mandatory, revises the set of allowed enumeration values, and goes live across all Amazon marketplaces at the same time. Sellers who rely on API‑driven or bulk‑feed workflows must adjust their integrations now to prevent listing rejections.
Key Points
- Optional becomes mandatory — Attributes that were once optional, such as “Material” for apparel or “Battery Type” for electronics, will now be required when a listing is created or updated via the SP‑API or JSON feed.
- Enumeration refresh — Dropdown lists for fields like “Color,” “Size,” and “Package Quantity” are being trimmed, expanded, or renamed; for example, “Medium” may be replaced by “M” and “Large” by “L.”
- All marketplaces at once — The new schema is being deployed simultaneously in North America, Europe, Asia‑Pacific, and other regions, so no market is exempt.
- API and JSON‑feed only — Traditional XML/XSD feeds and manual Seller Central entries are not subject to these rules; only programmatic listings are impacted.
- Search and conversion upside — Listings that meet the richer attribute set are expected to rank higher in Amazon’s search algorithm, potentially boosting visibility and sales.
- Developer‑centric update — The SP‑API’s
getProductTypeDefinitionsoperation will return the revised schema, meaning any hard‑coded attribute maps will become obsolete.
How the Updated Listing Attributes Work
- Schema retrieval — When a developer calls
getProductTypeDefinitions, the response now includes the newly required fields and the refreshed enumeration lists. Example: A request for the “KitchenKnife” product type returns a mandatory “BladeMaterial” attribute that was previously optional. - Payload construction — The integration must populate every required attribute before sending a or request.
Analysis & Recommendations
Why This Matters
Missing mandatory attributes will cause createCatalogItem or updateCatalogItem requests to be rejected, leading to lost sales and extra remediation effort. The simultaneous rollout across all marketplaces means no region is exempt, so every seller must adapt their pipelines immediately.
Key Takeaways
- Attributes such as "Material" for apparel and "Battery Type" for electronics become required in SP-API payloads.
- Enumeration values are refreshed; "Grey" is no longer accepted, only "Gray".
- The getProductTypeDefinitions operation now includes new mandatory fields like "BladeMaterial" for KitchenKnife.
- An audit revealed ~2,300 electronics listings lack the new "BatteryType" attribute.
Recommended Actions
- →Run a script in your integration repo to compare current payload fields against the latest getProductTypeDefinitions output (SP-API > /definitions/...
- →Update your JSON LISTINGS FEED template file to add columns for new mandatory attributes (e.g., BladeMaterial, BatteryLife) and replace deprecated ...
- →Add a nightly job that calls getProductTypeDefinitions, caches the schema, and triggers alerts in CloudWatch when API responses return MissingRequi...
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!