There are a multitude of different reasons for rejection, in both the ‘Content’ and ‘Price & Availability’ areas. Each channel has different rejections, and each rejection has a different way of being resolved. Below is a list some of the common rejections you may encounter. This is not an exhaustive list, but includes some of the most commonly encountered errors and their resolutions.
For more information on specific channels, see any one of the channel specific feed rejection guides located here.
If the error still persists after following the steps below, contact content@getquipt.com for more support.
| Channel Rejection Appears On |
Content or Price & Availability Error |
Error Message Description |
Reason for Error |
Resolution |
|
ALL CHANNELS |
Content |
“Content: Unsupported export category. Build within retailer's portal manually.“ |
This error occurs when you try to publish an item to a channel that is not currently supported by Quipt. |
|
|
ALL CHANNELS |
Content |
“Content: A value is required for the "Processor Brand" field.” |
This error occurs because of a bad mapping. Required attribute names are either missing from the mapping, or were spelled incorrectly. |
|
|
AMAZON |
Content |
“Content: There is a restriction in effect at the item level (because of Item-Level gatings on an offer” |
This error occurs because of brand gatings on Amazon. We are unable to sell products with this brand. |
|
|
NEWEGG |
Content |
“Content: Error(s). Item not created. Manufacturer - Cannot create item by restricted manufacturer - [BRAND] is restricted by Newegg.com” |
This error occurs because of a brand gating on Newegg, We are unable to sell items with this brand. |
|
|
NEWEGG MARKETPLACE/ NEWEGG BUSINESS |
Content |
“Content: MSRP cannot be lower than SRP” |
This error is caused because the MSRP of the item is lower than the SRP. The MSRP cannot be lower than the SRP. |
|
|
NEWEGG MARKETPLACE/ NEWEGG BUSINESS |
Content |
“Content: Item not created. Duplicate Request with the same Action Create Item.” |
This error occurs because you are toggling Newegg Business and Newegg Marketplace at the same time or too close to each other. |
|
|
OVERSTOCK MARKETPLACE |
Content |
“Content: Error: Variation long description cannot contain Like new. Reason: Unable to list an item as like new onsite” |
This error occurs because the condition of the item has been included in the irem description. Overstock does not allow for the words “like new” to be in the item description. |
|
|
RAKUTEN |
Content |
“Content: Invalid Category - Products can no longer exist in category 6156.“ |
This error is caused because we are mapping items to categories that Rakuten is no longer using. |
|
|
WISH |
Content |
“Content: Code:1000 Message:shipping_cost exceeds maximum value of 1000” |
This error is typically a timing/caching issue. Shipping information is hard coded into the system, so this isn’t a mapping issue. |
|
|
WALMART |
Content |
“Content: Ingestion status: SYSTEM_PROBLEM - There item cannot be published. Usually an error of this type must be resolved with the assistance of Marketplace Support. Reason for the status change: Business - Brand Management” |
This error is caused because of a selling restriction on Walmart.com. |
|
|
WALMART |
Content |
“Content: Ingestion status: UNPUBLISHED - The item has been made unavailable on Walmart.com because of back-end rules, such as being without inventory for too long or problems with imagery. Reason for the status change: Reasonable Price Not Satisfied” |
This error is caused because Walmart’s algorithms have determined that your item is not priced competitively enough, usually meaning the price is too high. Walmart has special algorithms it used to determine what a ‘reasonable’ price is, so it’s a bit of a guessing game to find a price that will allow you to get your item published. *See note at bottom of page.* |
|
|
WALMART |
Content |
“Content: SYSTEM_ERROR ERR_INT_DATA_0101123 It looks like there was a glitch on our end. Please try again. If the problem persists, contact Walmart Partner Support.” |
This error is caused by a glitch in the Walmart system. Typically re-toggling the feed clears it out and resolves the error. |
|
|
WALMART |
Content |
“Content: DATA_ERROR ERR_PDI_0003 Input XML validation failed. Expected attribute not found which is followed by: 'compatibleDevice'. Missing expected attribute name:compatibleDevices” |
This error is caused by a mapping mistake. A required attribute is either missing or incorrectly formatted or spelled. |
|
|
WALMART |
Content |
“Content: SYSTEM_ERROR ERR_PDI_0047 ID Type=UPC, ID Value=8837950031868, invalid product ID length: 13” |
This error is caused by an invalid UPC. The length value shows you that the length of the UPC you’ve inputted is 13 numbers, but a valid UPC has only 12 numbers. |
|
Most important is that after you think you have fixed the error that you’re working on, you want to re-toggle (turn off, and then back on again) your feed so that you can get a feedback loop and see whether you’ve fixed the source of the error or not. If you work through rejections channel to channel, then go to partner settings and click the channel you’ve just finished working on. Go to the advanced settings and ‘toggle unpublished’ to re-toggle all the rejections in that channel at once, so you don’t have to do them one at a time.
Comments
0 comments
Please sign in to leave a comment.