Getting started
Item setup
Item setup methods
Item content, imagery, and media
Variant management
Restored or Pre-Owned items
Automotive fitment
Troubleshooting
Track item setup or maintenance activity in Seller Center
Troubleshoot item setup errors
Troubleshoot product ID errors
Request a GTIN exemption
Troubleshooting common integration errors
Troubleshoot items on hold
Troubleshoot product variant errors
Troubleshoot automotive fitment errors
Catalog management
Seller Fulfillment Services
Listing optimization
Order management
Taxes & payments
Policies & standards
Growth opportunities
Advertising
Walmart Fulfillment Services (WFS)
This is a non-exhaustive list of common errors you may encounter through Walmart APIs, Seller Center, or via Solution Providers. If the error persists after following the steps below, select the Help button in the Seller Center menu bar to contact Support.
API HTTP errorsÂ
# | Action performed | Error description | Reason for error | Resolution | |
---|---|---|---|---|---|
H1 | Order refund | (HTTP 400) | This error occurs when you send an order refund request that exceeds the original amount paid for that order. Since refunds are cumulative, this could be due to a partial refund processed on that order earlier. |
| |
H2 | Order cancellation | (HTTP 400) | This error occurs when you try to cancel an order that is already shipped or canceled. Orders that are already shipped can't be canceled. |
| |
H3 | Order shipment failure | (HTTP 400) | This error occurs when a shipment notification is received for orders that are already shipped or canceled. Orders are auto-canceled if they are not shipped within 10 days. |
| |
H4 | Item operations: update price or inventory | (HTTP 400) |
|
| |
H5 | Any operation | (HTTP 401) |
|
| |
H6 | Item update | (HTTP 404) | This occurs when you try to update an item that was not ingested successfully. It can occur either when an item is still in the process of ingestion, or if there was an error in the ingestion. |
| |
H7 | Any operation | (HTTP 405) | This error occurs for API calls where the request method is not valid for a particular endpoint. For example, an API call to "Get all orders":Â GETÂ https://marketplace.walmartapis.com/v2/orders{nextCursor}Â using DELETE method will return an error. |
| |
H8 | Using POST create/update request for item, inventory or price | (HTTP 423) | This error occurs for API POST calls when creating or updating an item, inventory or price. For example, a call to https://marketplace.walmartapis.com/v2/feeds?feedType=item with the POST method may return an error. |
| |
H9 | Any operation | (HTTP 500) | This error occurs when an incorrect content type is specified while making an API call, or a payload is included that is inconsistent with the content type. |
| |
H10 | Item create / update | (HTTP 500) | This error occurs due to internal system issues, such as the inability to connect to any of the underlying systems, internal system data issues (duplicate data), etc. |
| |
H11 | Any operation | (HTTP 503)Â | The GMP Gateway is unavailable. |
| |
H12 | Order shipment failure | (HTTP 500.456) | This error occurs when shipment notification is received for orders with "Quantity Overshipped: Some or All Line(s)/Quantity cannot be Shipped due to invalid Lines or Quantity more than allowed." |
|
Non-HTTP errors
# | Action performed | Error description | Reason for error | Resolution |
---|---|---|---|---|
N1 | Item create / update feed | Data Error for a specific item | This error occurs when the XML feed contains invalid or missing mandatory information for individual items. The error is returned at an individual item level. |
|
N2 | Item ingestion | Data Error for a specific item: | This error description is generated when your item encounters a specific data corruption condition. |
|
N3 | Item ingestion | Data Error for a specific item: | This error description is generated when you ingest an item that has a different SKU, but the same GTIN or UPC as an item that you have already ingested. |
|
N4 | Item update | Data Error for a specific item: | This error message is generated when an item is ingested with invalid data. All the mandatory information should be provided while calling the API. A common example of invalid data is Shipping/Billable Weight set to 0. |
|
N5 | Item create / update | Data Error for entire file: | This error message is generated when there are special characters / malformed data in the Feed File of the item ingestion or item update operations. The entire file is not processed in this scenario. |
|
N6 | Item create / update | Data Error: | This error message is generated during the item create / update operations when the UPC for any specific item is not 12 digits. |
|
N7 | Item create / update | Data Error: | This error message is generated during the item create / update operations when the information you've provided for this item does not match the information we currently have for this item. |
|
Solution Provider desynchronizationÂ
You should routinely check the integration between your chosen Solution Provider and Seller Center to ensure your Marketplace orders are being accurately logged.
If your Solution Provider loses connection with Seller Center and there are active Marketplace orders impacted, reach out to your strategic account manager with the information below. If you don’t have a strategic account manager, create a case for Seller Support with the following information:
- Timeline of the issue:Â How long has the connection been severed?
- Integration Type: Are you directly integrated or are you using a third party solution provider? If so, name the provider.
- API Used:Â What was the API? What data passed through the API?
- Error Type: What was the error observed? If using a solution provider, please include logs.
- Error Timeline: At the time of reporting, was the error intermittent or continuous?
If you fulfilled a Marketplace order but it was not marked as shipped and the order was auto cancelled due to third-party desynchronization, Walmart is not responsible for any loss of product associated with the impacted orders, and you shall bear all costs for such a loss.