Overview

On certain days in 2024, sellers uploading shipping‑override feeds to Seller Central began receiving error 13011, which blocks the file from processing. The error indicates that a shipping amount is present without the required override‑type identifier, causing Amazon’s validation to reject the submission. Fixing the issue promptly restores the ability to adjust shipping costs and prevents listing inaccuracies.

Key Points

• Error trigger — The feed is rejected when any shipping‑amount column (e.g., Amt2) contains a value while its matching type column (e.g., Type2) is empty or missing.
• File formats affected — Both tab‑delimited spreadsheets and XML‑based override feeds can generate error 13011 if the amount‑type pair is incomplete.
• Mandatory pairing — Every amount field must be accompanied by a valid override‑type entry; Amazon’s system discards rows where the pair is broken, regardless of the row’s position in the file.
• Resolution path — Identify the mismatched pairs, insert the correct type code from Amazon’s accepted list, save the file, and resubmit.
• Impact on listings — Until the feed passes validation, any intended shipping‑cost changes remain inactive, potentially showing outdated fees to shoppers.
• Preventive measure — Embedding a pre‑upload validation step that flags empty type fields eliminates recurring occurrences.

How Shipping Override Validation Works

1. File ingestion — When a seller uploads a shipping‑override file, Amazon parses each row and extracts every amount column (Amt1, Amt2, …). Example: A spreadsheet line reads SKU123 | 5.99 | where the amount column (Amt2) holds 5.99 but the adjacent Type2 cell is blank.
2. Pair verification — The platform checks that each amount column has a corresponding type entry. If the amount is non‑zero and the type field is empty, the validator flags the row and returns error 13011. Example: The system sees and , triggering the error.