Understanding Amazon's Base Schema (XSD) for Seller Data Feeds
Amazon's Base Schema (XSD) defines the universal data elements and types used across all seller data feeds, including addresses, product identifiers, currency formats, and order references. Understanding this schema is essential for sellers managing feed-based integrations.
Overview
Amazon's Base Schema (XSD) serves as the foundational data structure that underpins all seller data feeds on the platform. This schema defines the universal elements and data types that every other feed references, ensuring consistency across all data submissions. For sellers who manage their catalog, orders, or pricing through feed-based integrations, understanding this base schema is essential for accurate and error-free data transmission.
Key Points / What Sellers Need to Know
- Foundation for all feeds — The base XSD is not a standalone feed but rather the building block that all other Amazon data feeds depend on. Every feed you submit references elements and data types defined in this schema.
- Standardized address formatting — The schema defines a structured address format with up to three address lines (each capped at 60 characters), city, state/region, postal code, county, and a two-letter ISO 3166 country code.
- Name field is a single entry — The name element is a single field with a 50-character maximum. Sellers are responsible for parsing it into first name and last name within their own systems if needed.
- Multiple identifier types — The schema distinguishes between Amazon-generated identifiers (like Amazon OrderID and Order Item Code) and seller-defined identifiers (like merchant OrderID, merchant Order Item ID, SKU, and Fulfillment Center ID).
- Multi-currency support — The base schema supports transactions in USD, GBP, EUR, and JPY, with currency amounts defined as decimal values up to 20 digits with exactly two decimal places.
How the Base Schema Works
The base XSD functions as a shared library of data definitions that all Amazon feed types inherit from. When you submit a product feed, an order acknowledgment feed, or a pricing feed, those feeds reference the base schema for common elements like addresses, product identifiers, currency amounts, and order references. This architecture means that Amazon can maintain consistency across its entire feed ecosystem without duplicating definitions in every individual feed type. The schema enforces strict formatting rules — for example, country codes must be exactly two characters following the ISO 3166 standard, and currency values must include precisely two decimal places. By constraining these formats at the base level, Amazon reduces the likelihood of data errors propagating through downstream systems.
Analysis & Recommendations
Why This Matters
Sellers who submit data feeds to Amazon need their submissions to conform to this base schema. Errors in formatting addresses, identifiers, or currency values at this level cause feed rejections that can delay catalog updates and order processing.
Key Takeaways
- The base XSD is the foundation all Amazon data feeds reference for shared elements and data types
- Address names are a single 50-character field — sellers must parse first/last names in their own systems
- Country codes must be exactly two letters following ISO 3166, and currency amounts require explicit currency attributes
- The schema supports USD, GBP, EUR, and JPY with decimal precision fixed at two places
Recommended Actions
- →Review your feed submission templates against the base schema to ensure address fields, country codes, and currency formats comply with the defined constraints
- →If experiencing feed rejections, cross-reference error fields against the base XSD element definitions to identify formatting mismatches
- →Ensure your systems can handle the single-field name format and parse it appropriately for your internal records
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!