Troubleshooting
“Test connection” fails
Section titled ““Test connection” fails”- Check the mode: test credentials only work in test mode and live credentials only in live mode.
- Check for spaces before or after the client ID and secret.
- The Log tab shows Walmart’s answer (masked).
- “Client authentication failed” / 401 on the token call: the client ID or secret is wrong, or a production key pair is used in test mode (production credentials do not work in the Walmart dynamic sandbox) or the other way round.
- “Invalid access token”: the token expired (it is renewed once automatically) or the key pair was regenerated in Seller Center; enter the new pair.
- Sandbox: only part of the Walmart APIs run in the dynamic sandbox and full item setup through feeds is not supported there; use test mode to check the connection, orders, shipping and inventory, then switch to Live.
- Your server must be able to reach the provider over HTTPS (outgoing port 443) and have a current CA bundle.
Nothing happens after an order changes status
Section titled “Nothing happens after an order changes status”- Check Settings > General > Enable and the order status settings.
- Check the license status bar on the add-on pages.
- Open Jobs: queued jobs wait for cron. If the counts never change, the cron job is not running; run the command from the settings page by hand once.
A job is “Waiting to retry” or “Gave up”
Section titled “A job is “Waiting to retry” or “Gave up””The last error is shown in the list. Fix the cause (credentials, data, provider outage) and press Retry. Jobs are retried automatically after 5 minutes, 15 minutes, 1 hour, 3 hours and 12 hours before they give up.
A listing is refused or never appears
Section titled “A listing is refused or never appears”- The product shows Walmart’s own message (code and text) on the Listings page. The most common one: the GTIN is not in the Walmart catalog. This version creates offers for items that already exist at Walmart; for a brand new item use Seller Center.
- “Waiting”: Walmart accepted the feed and is still processing it; the state changes on one of the next runs.
- The barcode must be a GTIN of 8, 12, 13 or 14 digits and the price must be above zero.
- Stock or price rejected for a SKU Walmart does not know yet: the item has to be live on Walmart first.
Orders are missing or are skipped
Section titled “Orders are missing or are skipped”- A new order without a shipping address is skipped and logged.
- An order with an unmapped SKU is not imported; the error is shown on the Orders page and the import is retried. Map the product (the barcode is the SKU) and it is picked up.
- Orders older than 180 days are not returned by Walmart.
- Cancelled lines are left out; an order whose lines are all cancelled is imported as cancelled.
“Walmart is throttling this API”
Section titled ““Walmart is throttling this API””Walmart limits calls per API (token buckets; answer headers x-current-token-count and X-Next-Replenishment-Time). A 429 answer is retried by the job queue; the message names the time the next call is possible. Price updates are the tightest limit (100 single price calls per hour for default accounts).
Tracking is not sent
Section titled “Tracking is not sent”- Turn on “I ship with my own carrier” on Rules and create the shipment with a tracking number in CS-Cart.
- For a carrier Walmart does not know by name (known: UPS, USPS, FedEx, DHL, OnTrac) set a tracking URL template on Rules; Walmart requires the tracking URL then.
The cron address answers “Forbidden”
Section titled “The cron address answers “Forbidden””The key in the address is wrong. Copy the address again from the settings page.
Still stuck
Section titled “Still stuck”Contact us through https://cs-cart.kaviolabs.com with the add-on version, the CS-Cart version and the relevant log lines (secrets are masked automatically).