Amazon Tightens Product Listing Requirements in XSD-to-JSON API Migration
Amazon is migrating all listings to the JSON‑based Listings Items API on 22 marketplaces, making fields like exact dimensions, materialComposition and batterySafetyCertification mandatory. The new Product Type Definitions API and validate endpoint let sellers dry‑run submissions, and early audits show up to 12% of 5,000 SKUs lack required data.
Overview
Amazon is moving all product listings from legacy XML and flat‑file feeds to the JSON‑based Listings Items API. The shift introduces far tighter data validation, meaning attributes that once slipped through with minimal checks are now subject to strict, context‑aware rules. Sellers who create or modify listings via the new API must adapt immediately, or risk rejected submissions and potential sales loss across every Amazon marketplace.
Key Points
- Mandatory fields expand — Identification numbers, exact dimensions, material details and compliance data that were optional in XML feeds are now required for many product types.
- Uniform rollout across 22 marketplaces — The United States, Europe, the Middle East and Asia‑Pacific sites all enforce the same JSON schema updates at the same time.
- Dynamic, conditional logic replaces static XSD checks — Certain attributes become compulsory only when related fields contain specific values, such as a “battery type” field that triggers a safety‑certification requirement.
- Legacy listings stay live — Products already published through older feed formats continue to sell, giving sellers a window to transition new and edited items.
- Programmatic schema access — Amazon provides a Product Type Definitions API that returns the exact set of required and conditional attributes for any product type and marketplace.
- Dry‑run validation available — The Listings Items API includes a sandbox mode that flags schema violations before a live submission is attempted.
How the New JSON Validation Works
- Schema retrieval — A developer calls the Product Type Definitions API, specifying the marketplace (e.g.,
www.amazon.com) and product type (e.g.,SportsEquipment). The response lists every attribute marked as required, optional, or conditionally required for that combination. - Data mapping — The seller’s catalog data is mapped to the JSON structure defined in the schema. For example, a “weight” field must be supplied in kilograms with two decimal places, matching the schema’s property type.
Analysis & Recommendations
Why This Matters
If sellers continue using legacy feeds, new or edited items will be rejected, halting sales across all Amazon sites. The conditional rules (e.g., hasBattery triggers safety certification) add complexity, so immediate schema integration is essential to avoid revenue loss.
Key Takeaways
- 22 Amazon marketplaces will enforce the new JSON schema simultaneously.
- Mandatory attributes now include exact dimensions, materialComposition and conditional batterySafetyCertification.
- An audit of 5,000 SKUs revealed 12% lack precise dimensions, requiring urgent data enrichment.
- The Product Type Definitions API provides real‑time required attribute lists per marketplace and product type.
Recommended Actions
- →In Seller Central, go to the API section and retrieve the Product Type Definitions for each marketplace you sell on; store the schema locally.
- →Run a script against your catalog to compare each SKU to the retrieved schema and flag missing fields like length, materialComposition, or batteryS...
- →Integrate calls to the Listings Items API validate endpoint in your listing workflow to catch errors before live create or update calls.
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!