Overview

Amazon provides a set of XML Schema Definition (XSD) files that sellers and developers must use when constructing data feeds for Seller Central. These schema files define the exact structure, data types, and validation rules for every feed you submit and every report Amazon generates. Understanding how to work with these core schemas is essential for any seller who uses XML-based feed submissions to manage their catalog, inventory, pricing, or order data at scale.

Key Points / What Sellers Need to Know

• XSD files are the blueprint — XML Schema Definition files dictate the precise format your feeds must follow in order for Amazon to accept and process them. Submitting feeds that don't conform to these schemas will result in processing errors.
• Three core schemas are required — Every XML feed submission relies on three foundational schema files: the header schema (amzn-header.xsd), the base schema (amzn-base.xsd), and the envelope schema (amzn-envelope.xsd). These must be used alongside the specific feed type schema for your submission.
• Always use the latest XSD versions — Amazon notes that sample XSDs shown in documentation pages may be outdated. Sellers should always download the most current versions directly from the provided XSD links to avoid validation issues.
• UTF-8 encoding is mandatory — All XML feeds must use the Unicode character set with UTF-8 encoding. While standard ASCII characters encode identically in UTF-8, foreign characters with diacritical marks (such as ü, é, or ñ) require proper UTF-8 mapping.
• Character encoding is your responsibility — Amazon places the burden on sellers and developers to correctly convert any ASCII-encoded characters to proper UTF-8 format before feed submission.

How the Core Schemas Work Together

Amazon's XML feed system is built on a layered schema architecture. At the foundation, the base schema (amzn-base.xsd) defines common data types and elements that are reused across all feeds. The header schema (amzn-header.xsd) specifies the metadata structure that identifies your merchant account, the feed type, and processing instructions. The envelope schema (amzn-envelope.xsd) wraps your actual data payload and ties the header to the message body. On top of these three core files, each feed type — whether it's product data, inventory, pricing, images, or order acknowledgments — has its own dedicated schema that defines the specific fields and requirements for that data category. All four schemas (three core plus one feed-specific) must be referenced and followed for a valid submission.