Overview

Sellers see error 13012 when Amazon rejects a shipping‑override feed because a shipping‑type entry lacks its matching amount. The issue appears during the upload of either tab‑delimited or XML override files and stops the feed from processing. Fixing the error quickly restores the ability to update custom shipping rates, which is essential for maintaining accurate charge structures.

Key Points

• Root cause — The feed contains a shipping‑type value (e.g., “Standard”) while the adjacent amount field is empty or omitted.
• Applicable file types — Both tab‑delimited spreadsheets and XML‑based override feeds trigger the same validation error.
• Paired‑field rule — Every shipping‑type column must be paired with a numeric amount column; a blank amount is treated as an incomplete configuration.
• Typical symptom — Amazon returns “Error 13012: Missing Shipping Override Amounts” and rejects the entire file, leaving existing shipping settings unchanged.
• Quick remedy — Populate every missing amount, save the file, and resubmit the corrected feed.
• Preventive tip — Use a pre‑validated template that highlights required columns, reducing the chance of blank cells slipping through.

How Error 13012 Occurs

1. Upload of a custom shipping file — A seller prepares a file that lists shipping methods (e.g., “Expedited”) and uploads it through Seller Central. Example: a row reads “Expedited” in the ShippingType column but leaves ShippingAmount blank.
2. System validation checks paired fields — Amazon’s ingestion engine scans each row for a matching amount. When it finds a type without a numeric value, it flags the row as incomplete. Example: the engine records the missing amount for the “Expedited” entry and generates error 13012.
3. Feed rejection and error reporting — The entire feed is rejected, and the seller receives a status message indicating the missing amount issue. Example: the feed status shows “Failed – Error 13012: Missing Shipping Override Amounts,” preventing any shipping updates from taking effect.