Overview
This topic defines the error messages that can appear when creating or shipping an FBA Inbound Shipment and offers troubleshooting solutions.
Error Message List
| ERROR MESSAGE | DEFINITION / POSSIBLE SOLUTION |
| NOT_IN_PRODUCT_CATALOG | This issue occurs when Amazon’s information is not in sync with the information provided by Amazon’s Selling Partner API. This is outside of our control and usually remedies itself the next time Amazon initiates an API sync.
If you still have this issue after 24 hours, contact Seller Central Support and tell them the item is not being found when searched in their Selling Partner API. They should provide a window for when the problem will be solved. |
| INVALID_MSKU_REMAP | This error reason indicates that there is a mismatch between the Product in Sellercloud and its Active Listing in Seller Central, usually the ASIN.
Solution: Make sure that the ASIN and Merchant SKUs of the product match between the two platforms. If your SKU is a Shadow, the reason may be that there is a Shadow persistent field, and the issue lies with the Amazon Product Properties of the Parent SKU. |
| ITEM_EXCLUDED_FROM_COMMINGLING_FOR_EXISTING_MAP | Not all products are eligible for Stickerless Commingled Inventory. Products in grocery, health, beauty, and media must always be labeled. Amazon is always evaluating categories and products and may change product eligibility at any time.
Solution (possible): Add the item to the FBA Shipment in Seller Central. After adding the item, some version of the following message may appear: This product is not eligible for stickerless commingling. This product requires labeling to be received at our fulfillment centers. I agree to apply labels to these products. |
| ITEM_WITH_NO_VALID_FC | Item has no eligible Fulfillment Center because it is hazmat (hazardous material). You cannot send it to FBA. |
| NO_EXTERNAL_IDENTIFIER_FOR_EXISTING_MAP | The product is missing a UPC on Seller Central. |
| Failed to preview package reason= PARENT_IAID | A matrix parent is included in the inbound shipment. Only matrix children can be sent. (The matrix parent SKU is not a real item). |
| UNKNOWN_SKU | This SKU is not in your FBA Catalog.
Solution: Change the product to Fulfilled by Amazon. Launch the product to Amazon, wait several minutes, then retrieve the FNSKU by executing the action Get FNSKU. |
| ILLEGAL_VALUE | |
| ITEM_UNDER_HAZMAT_REVIEW | Potential Hazardous Material (Hazmat). Product under review by Amazon. |
| You must include a valid ShipmentId with a call to the CreateInboundShipment operation. Get ShipmentId values by calling the CreateInboundShipmentPlan operation. The request to CreateInboundShipment must include only items and quantities that have been previously planned through CreateInboundShipmentPlan. | The temporary ID assigned to a previewed shipment expires in 48 hours. |
| Insufficient inventory capacity for the operation | From Amazon Seller Forums: You may have an inventory storage limit. Inventory storage limits generally apply to new FBA sellers and existing FBA sellers with a slower-turning inventory. If your Amazon FBA account is configured for Unlimited storage, one of the items in the Preview has an ASIN-level capacity restriction. Unfortunately, Amazon does not tell us which item is causing the error. |
| MISSING_DIMENSIONS | The product is missing dimensions for FBA.
Solution:
|
| EXTERNAL_ID_MAPS_MULTIPLE_IAIDS | UPC for the listing was assigned to multiple ASINs. When you send the shipment, the ASINs conflict in the back end and cause errors in the system. This can happen when an item that used to be stickerless now requires a label. That’s because the UPC associated with this ASIN used to be associated with that ASIN only, but is now associated with more than one ASIN.
Solution: You may have to create a new listing on Seller Central. |
| Shipping Status is ERROR_ESTIMATING | There’s an error in the address. For example, the zip code is invalid because of a period at the end of the zip code. |
| AmazonContractNotSigned | The seller has not accepted Amazon’s Partnered Carrier Program terms and conditions. The seller should accept Amazon’s Partnered Carrier Program terms and conditions on Seller Central. |
| CannotConfirmTransportContent | The Amazon-partnered shipment request is ineligible for confirmation. Check if the shipment is already confirmed. |
| CannotEstimateTransportContent | The Amazon-partnered shipment request is ineligible for an estimate. Ensure that the Ship From address is in a marketplace eligible for Amazon’s Partnered Carrier Program. |
| CannotVoidTransportContent | The Amazon-partnered shipment request can no longer be voided. |
| CarrierContractNotSigned | The seller has not accepted the carrier’s terms and conditions. The seller should accept the carrier’s existing or revised terms and conditions on Seller Central. |
| CarrierInvalidForMarketplace | The specified carrier is not supported in the marketplace where the inbound shipment originates. |
| InvalidCountrySubdivisionCode | The specified ShipToCountrySubdivisionCode is invalid. Ensure that the ShipToCountrySubdivisionCode value is for a country subdivision that contains an Amazon fulfillment center where the seller is registered. |
| MissingCarrierType | No CarrierName value was specified. Specify a valid CarrierName value. |
| NoPackagesOrPallets | No package information (for Small Parcel shipments) or pallet information (for Less Than Truckload/Full Truckload (LTL/FTL) shipments) was specified. Specify this information using the PackageList or the PalletListparameter of the PutTransportContent operation. |
| TransportContentNotFound | No Amazon-partnered shipment was associated with the specified ShipmentId value. Specify a ShipmentId value that is associated with an Amazon-partnered shipment. |
| UnknownCarrierType | No carrier was found that matched the specified CarrierName value. Specify a valid CarrierName value. |
| Quantity is not divisible by QuantityInCase for SellerSKU: xxxxxxxx | The Qty to Ship is not divisible by the Qty Per Case. For example, Qty to Ship = 1 and Qty Per Case = 50 is incorrect because 1 is not divisible as a whole number by 50. Qty to ship refers to the Qty of Units you are shipping. |
| Unexpected error occurred 500 | An HTTP 500 error isn’t usually an Amazon server issue. the problem should be resolved by itself in 30 minutes to an hour. |
| EXP_DATED_ITEM_HAS_EXISTING_STICKERLESS_MAP | The merchant’s SKU is marked as a commingled product, but it is not commingleable. Amazon may change that error message to: Expiry-dated or lot-controlled product cannot be commingled. Please create a new listing for the same ASIN but a different SKU. |
| LABEL_PREP_OWNER_INCOMPATIBILITY_ERROR | This can occur when AMAZON_LABEL_ONLY is sent. Amazon is returning a message that they do not have enough information about the product to label the product themselves. Example: the product does not have a UPC.
Solution: Add the product information or label items yourself. Use the Seller Label option. |
| Over_ASIN_Guidance | FBA guides sellers to align their inventory supply with buyer demand, and they check if there is sufficient inventory capacity for the given items. You are already at the maximum inventory allowed for this product due to capacity or other restrictions.
Solution: The item must be removed from your batch to finish creating your shipment. |
| Seller is blocked by the AndonCordManager. | This is most likely an FBA compliance issue, not a technical or code issue. Check your account’s status and speak to an Amazon representative if necessary. |
| SupplyCategoryUnavailable | ASIN is enrolled in UNO (Small & Light) program, and MCF cannot fulfill UNO ASINs. Small and Light can be used only to fulfill Amazon orders. |
| EXTERNAL_ID_MAPS_MULTIPLE_IAIDS_FOR_EXISTING_MAP | The item has a new FNSKU and can longer be posted under the existing one. |
| Shipment# reached the maximum recursive calls of 11 (Max recursive calls allowed are 10). | When Sellercloud requests “ListShipmentItems” to retrieve FBA shipment information, Amazon has a constraint on the number of SKUs returned per response document. If the shipment contains more items than can be accommodated in one response, Amazon provides a “NextToken” in the response to indicate that more data is available. To retrieve the remaining items, Sellercloud uses this “NextToken” value in a subsequent call to “ListShipmentItemsByNextToken.” This call is designed to continue where the previous one left off and provide the additional items.
However, there’s a known issue where Amazon occasionally includes the “NextToken” even when all shipment items have already been covered in the response. This can lead to a repetitive cycle: Sellercloud keeps making calls to “ListShipmentItemsByNextToken,” but receives the same response with identical items repeatedly. To prevent being stuck in this loop, Sellercloud implemented a solution – if the same information is received ten consecutive times, the calls to “ListShipmentItemsByNextToken” are ceased, and a note is added to the shipment to indicate this situation – Shipment# reached the maximum recursive calls of 11 (Max recursive calls allowed are 10). The limitation and the decision to halt querying the shipment only apply to this particular instance. The automatic querying of eligible shipments in the future remains unaffected. |
| This shipment was converted to Send to Amazon and no updates can be made to this shipment |
Amazon does not allow an Inbound Shipment to be managed directly on Seller Central and via API (i.e., through Sellerlcoud). You will see this error (as well as a Shipment note and a warning banner) if a user has edited the Inbound Shipment directly on Amazon. |
