Overview

Starting July 25 2022, Amazon will enforce a new validation rule for shipment confirmations on several international marketplaces—including Brazil, Mexico, Canada, and Australia, with Singapore, India, and Japan to follow. The rule requires every confirmation to contain a valid CarrierCode entry. Sellers using bulk feeds, the Selling Partner API, or third‑party middleware must update their processes, or risk orders staying in a pending state and incurring performance penalties.

Key Points

• CarrierCode mandatory — All shipment confirmations for the affected marketplaces must include a non‑empty CarrierCode field, even when the carrier is an Amazon‑partnered service.
• Staggered rollout — The enforcement begins on July 25 2022 for Brazil, Mexico, Canada and Australia; Singapore, India and Japan will be added later under the same validation logic.
• Broad applicability — The requirement covers XML or flat‑file bulk feeds, SP‑API calls such as createShipment and confirmShipment, and any custom integration that pushes confirmation data to Amazon.
• Rejection response — Submissions missing the CarrierCode are rejected with the InvalidCarrierCode error, leaving the order’s “Shipped” flag false and generating a notice in the Feed Processing Report or an API error payload.
• Exact code needed — Amazon expects the official carrier identifier (e.g., UPS, FEDEX, DHL, USPS) as listed in its Carrier Code reference; misspellings or unofficial abbreviations trigger the error.
• Performance risk — Repeated rejections can inflate late‑shipment metrics, lower the On‑Time Delivery rate, and may lead to health warnings on the seller account.

How the CarrierCode Requirement Works

1. Determine the carrier — Identify the precise carrier used for each order before building the confirmation payload.
   A seller ships a Brazilian order via UPS, so the correct identifier is .