Here we discuss common fixes for post cases.
Recursive Posting
Due to Walmart specifics, for a single posting iteration we can only know the first issue found for each product. That means if there're multiple fields in product that a Walmart doesn't like, we'll learn about them only after posting first time. Once products go online, we do not want them in further posting batches. We do not want double-listings.
Eliminating them is easy. Now with "Show Products" green button you can decide what to do with the values, filter out products and use Copy Data accordingly. Setting Product Tags is also a good way of working through products to bulk tune values. You may use the search to find out the most popular issues types and work on them first.
The amount is shown to the left from results page selector
Validator error: Enum failed, enum:
It follows same structure:
1. ["Array of Walmart expected values is provided"]
2. data: "Bronze" at — tells the value provided on posting
3. properties: metal — the field with unaccepted value
4. For cases when expected values do not match to any extent the real product's parameters, it's recommended:
- Provide "No Metal" in metal field
- Provide metal in product's material
productSecondaryImageURL
Walmart doesn't let posting products with a single image. Add images or assign box images to products.
 | More information about the best support practices and how to create a ticket: |
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article