Overview

Amazon sellers may see feed processing fail with error 13037 when they submit pricing or shipping overrides that contain a currency code other than USD for the Amazon.com marketplace. The rejection stops price updates from reaching the catalog, potentially leaving listings with outdated or incorrect prices. Fixing the issue quickly restores normal pricing flow and prevents sales disruption.

Key Points

• Root cause — The feed includes a non‑USD currency code (e.g., EUR or GBP) while targeting the Amazon.com marketplace, which only accepts US dollars.
• Immediate effect — All rows that contain the invalid code are rejected, so the intended price or shipping changes never appear on the product detail page.
• SKU confusion — The error often appears alongside a “SKU not found” notice, prompting sellers to double‑check both the currency field and the SKU’s existence in the US catalog.
• Simple remedy — Replacing the offending code with “USD” and resubmitting the file resolves the problem in a single cycle.
• Multi‑marketplace risk — Sellers who reuse a single template across Amazon’s global sites may unintentionally push European or Japanese currency codes to the US feed, triggering the error.
• No health penalty — The issue does not affect account health metrics, but it does halt pricing automation until corrected.

How the Error Occurs

1. Feed creation — A seller builds a bulk pricing or shipping override file in a spreadsheet, selecting “EUR” for the Currency column because the same template is used for Amazon.co.uk. Example: Row 12 lists SKU B07XYZ, Price 19.99, Currency EUR.
2. Marketplace selection — The file is uploaded to the Amazon.com feed endpoint, either via Seller Central or an API call, without changing the Currency value. Example: The upload command points to the US marketplace ID “ATVPDKIKX0DER.”
3. Schema validation — Amazon’s XSD schema recognises “EUR” as a valid code globally, but the US marketplace logic enforces USD exclusively, so the system flags the row and generates error 13037.