How to Use Amazon's Price Feed to Set and Manage Product Pricing
Explains Amazon's Price Feed schema for setting standard prices, sale prices, and MAP values via XML feeds. Essential reference for sellers managing pricing programmatically or in bulk.
Overview
Amazon's Price Feed is the mechanism sellers use to programmatically set, update, and manage pricing for their catalog listings. Whether you're adjusting everyday prices, running limited-time sales, or complying with manufacturer minimum advertised price (MAP) requirements, understanding the Price Feed schema is essential for accurate and efficient pricing management across your Amazon storefront.
Key Points / What Sellers Need to Know
- SKU is the primary identifier — Every product in the Price Feed must be referenced by its unique SKU. Each SKU must be distinct within your catalog to avoid pricing conflicts or errors.
- Standard price is required — The base (non-sale) price must always be included for each item in the feed. This is the default price customers see on your listing.
- Sale pricing requires start and end dates — If you set a sale price, you must also specify when the sale begins and when it ends. Omitting either date will cause the sale configuration to fail.
- MAP compliance is built in — The feed supports a Minimum Advertised Price field for products where the manufacturer dictates a price floor. Both your standard and sale prices must exceed the MAP value.
- Multiple currencies are supported — The Price Feed accepts values in USD, GBP, EUR, JPY, and CAD, making it suitable for sellers operating across Amazon's international marketplaces.
How the Price Feed Works
The Price Feed uses Amazon's XML-based flat file schema to process pricing updates in bulk. Sellers submit an XML envelope containing one or more messages, each tied to a specific SKU. Each message includes the standard price and can optionally include sale pricing details and MAP values. The feed is processed as part of Amazon's broader feed submission system, which means updates are queued and applied asynchronously rather than in real time. Sellers typically submit Price Feeds through Seller Central's feed upload interface, third-party listing tools, or direct SP-API integrations.
Setting Up Sale Prices
Running a sale through the Price Feed requires three components: a start date, an end date, and the discounted sale price. The start date indicates when the sale price becomes visible to customers, and the end date marks the last day the sale is active. After the end date passes, the listing automatically reverts to the standard price. This makes the Price Feed a reliable way to schedule promotional pricing windows in advance without needing to manually toggle prices on and off. Sellers should double-check that the sale price is lower than the standard price and higher than any applicable MAP value to avoid feed processing errors.
Analysis & Recommendations
Why This Matters
Pricing accuracy directly impacts Buy Box eligibility, profit margins, and customer trust. Understanding the Price Feed schema helps sellers avoid feed errors that can suppress listings or display incorrect prices.
Key Takeaways
- Every Price Feed entry requires a unique SKU and a standard price; sale pricing additionally requires both a start and end date.
- MAP values act as a price floor — both standard and sale prices must exceed the MAP or the feed will be rejected.
- MAP functionality is not supported in all Amazon product categories, so sellers should verify eligibility before using it.
- Feed submissions are processed asynchronously, so sellers should monitor processing reports to catch and fix errors quickly.
Recommended Actions
- →Validate your Price Feed XML against Amazon's XSD schema before submitting to catch formatting errors early.
- →Always include start and end dates when setting sale prices to prevent feed processing failures.
- →Review feed processing reports after each submission to identify and resolve rejected entries promptly.
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!