SKU-8210 · Walmart Solution Provider

Open Blockers — Waiting on Walmart

Items in the Full Service Provider validation that we can't complete on our side and need Ganga / the Walmart onboarding team to unblock. Everything else in the matrix is done, evidenced, or a safe production-pilot read.

Owner (Walmart): Ganga Udiyar Pilot seller: partusa Target launch: 2026-08-12 Updated: 2026-07-18
1
Launch-blocking
1
Should-have (provisioning)
1
Non-blocking clarification
1

Return / Refund simulation — sandbox endpoint unavailable

Launch-blocking
Blocks
Returns → Full refund (Must-have) and the refund demo scenario. POST /v3/returns/{returnOrderId}/refund needs a returnOrderId, which only a return can produce.
Issue
The return-simulation endpoint 404s in our dynamic sandbox, while every other simulation endpoint works with the same credentials + headers.POST https://sandbox.walmartapis.com/v1/simulations/returns → 404 {"code":"CONTENT_NOT_FOUND","description":"No static resource v1/simulations/returns."}
Proven working
Full order lifecycle in the dynamic sandbox — /v1/simulations/items, /v1/simulations/orders, acknowledge, ship, cancel, and /v1/simulations/orders/{po}/deliver — all HTTP 200. We also retried the return call on a successfully delivered order and tried 4 path variants; identical 404.
The ask
Enable the return-simulation endpoint for our sandbox app, or advise the recommended way to generate a test return/refund for validation.
Status
Emailed Ganga + team 2026-07-18 (kickoff thread). Awaiting reply.
2

WFS Restock Recommendations — partusa seller provisioning

Should-have
Blocks
The WFS Restock Recommendations use case (GET /v3/wfs/recommendation/restock).
Issue
On the production pilot the endpoint returns 400 WFS.100 "sellerId must be 32 characters". Walmart derives sellerId from the OAuth token / account and ignores any client-supplied value — proven across 7 param/header locations (query sellerId, WM_PARTNER.ID, WM_CONSUMER.ID, etc.); the error is identical whatever we send. No 32-char seller GUID exists anywhere in our data or partusa's Developer Portal (which shows only Client ID/Secret + numeric partner id 10002506668).
The ask
Confirm / complete WFS seller provisioning for partusa (the 32-char sellerId), or advise how a Solution Provider is expected to obtain it.
Status
Seller-side WFS provisioning gap — Walmart-side, no client workaround.
3

Platform Status (getApiPlatformStatus) — subscribed consumer-id

Non-blocking
Blocks
The Platform Status health card only — not a business API. All order / item / price / inventory / returns / report APIs use standard marketplace auth and work; the UI degrades gracefully to an "n/a" card.
Issue
Partner Management Services requires a WM_CONSUMER.ID that is one of the SP's "2 subscribed consumer ids". Our SP OAuth client_id and the seller partner id (10002506668) are not subscribed consumer ids, and the real value isn't exposed in any SPC credential view we can access. (Header routing itself — WM_SVC.NAME=PARTNERMANAGEMENTSERVICES — is already fixed and deployed.)
The ask
Which consumer-id is subscribed to Partner Management Services for our SP account? (portal clarification)
Status
Non-blocking — cosmetic health indicator. Needs portal / Ganga clarification.