Walmart Solution Provider — Final Demo Run-of-Show

When: Monday, Jul 27 · 12:30 PM PST  ·  Seller: partusa / Siber Ventures (partner 10002506668)  ·  Format: screen-share of the SKU.io UI — seller's perspective  ·  Host: Ganga Udiyar (Walmart)

The one thing to remember: this is a UI demo, not a Postman demo. Ganga wants to see a seller do each task inside your website — "show the item life cycle in your website", "how the error message is displayed to the sellers", "show Feed IDs to the seller". The raw request/response proof was the earlier Verification Phase (the validation .txt bundle — already submitted).

Two environments — by design, not by accident
PILOT · production Walmart (real Feed IDs) SANDBOX · order/return simulation

Item lifecycle + OAuth run on the pilot (real production connection — real feed IDs, real errors). Orders & returns run in the sandbox: every pilot order is already in a terminal state (Delivered/Shipped/Cancelled), so there is no fresh order to acknowledge/ship — and Walmart explicitly accepts sandbox validation for orders/returns. Keep both logged-in tabs open; switch tabs at the marked handoff.

SPre-demo staging — I complete this before Monday

On the pilot (production): In the sandbox: I'll confirm each of these is in place and fill the SKU / PO # / Feed ID columns in Ganga's checklist before the call.

APart A — Pilot (production Walmart)

9
Seller's Walmart authentication
PILOT

Ganga's centerpiece. Start here — it frames the whole "seller's perspective" demo.

Steps (in SKU.io)
  1. Integrations → Add Walmart (or Settings → Authentication).
  2. Show the fields where the seller enters their Walmart Client ID (consumer id) and Client Secret (private key).
  3. Enter a wrong Client ID first → Connect → the page shows an inline error on the same page (token call fails fast) — exactly what Ganga asked for.
  4. Correct it → Connect → success; the integration shows Connected.
✓ Invalid credentials error inline; valid credentials connect and the seller lands on the Walmart dashboard.
10
Disconnect & reconnect
PILOT
Steps
  1. Settings → Disconnect. Explain that this removes both the refresh and access tokens for the seller.
  2. Show the integration is now disconnected.
  3. Reconnect to restore the session (re-enter credentials, Connect).
✓ Disconnect clears both tokens (server-side); reconnect re-establishes the connection.
Rehearse this on a throwaway/second instance if you don't want to drop the live pilot session mid-demo — or do it last.
1
Create items — variants & swatches, 5 in one feed
PILOT
Steps
  1. Listings → Coverage / Publish. Select the net-new SKUs staged across 2 categories (2+ each), including the variant group with colour swatches.
  2. Publish → one MP_ITEM 5.0 feed is submitted; the Feed ID is shown to the seller immediately.
  3. Open Feeds → show the feed ingesting → SUCCESS.
✓ Feed ID surfaced on submit; items ingest SUCCESS on production (variant group + swatches).
Walmart doesn't allow deleting test items — only retiring. Use real, sellable items; we retire them after (proven: DELETE /items/{sku} → 200).
2
Update item — edit the Description
PILOT
Steps
  1. Listings → open the staged existing SKU → edit the Description attribute.
  2. Republish → MP_ITEM update feed → new Feed ID shown.
✓ Update feed submitted; new Feed ID; Feeds page shows SUCCESS.
3
Inventory — bulk update, 5 in one feed
PILOT
Steps
  1. Inventory → set new quantities for the 5 staged SKUs → Push/Update → feed submitted → Feed ID shown.
✓ Bulk inventory feed accepted; Feed ID shown; Feeds page SUCCESS.
4
Price — bulk update, 5 in one feed
PILOT
Steps
  1. Listings / Price → set new prices for the 5 staged SKUs → Push → price feed submitted → Feed ID shown.
✓ Bulk price feed accepted (validated live, HTTP 200); Feed ID shown.
8
Error handling — missing Description
PILOT
Steps
  1. Publish the bad SKU (Description missing).
  2. Open Feeds → the feed shows an item-level DATA_ERROR; open it to show the per-item error message displayed to the seller (which attribute failed and why).
✓ Walmart's ingestion error is surfaced to the seller in the UI, keyed to the Feed ID and the offending field.
11
Feed IDs — success & error
PILOT
Steps
  1. Feeds page → point to the Feed ID column for both a successful feed (S1–S4) and the error feed (S8). Every submission — success or error — surfaces its Feed ID to the seller.
✓ Feed IDs visible to the seller for both success and error cases.

BPart B — Sandbox (order & return simulation)

Switch to the sandbox-connected tab. These use fresh simulation orders because no pilot order is in an actionable state, and Walmart accepts sandbox for orders/returns.

5
Acknowledge & cancel one line of a multi-line order
SANDBOX
Steps
  1. Orders → open the staged multi-line order (PO #) → Acknowledge.
  2. Cancel one line (choose a line, reason) → confirm.
✓ Order acknowledged; the chosen line shows Cancelled, the rest remain active.
6
Acknowledge & ship a multi-line order (tax + shipping)
SANDBOX
Steps
  1. Orders → open the staged order with tax + shipping → Acknowledge.
  2. Ship → enter carrier + tracking → submit fulfillment.
✓ Order acknowledged and shipped; tracking recorded; status → Shipped.
7
Issue refund — individual & multiple lines
SANDBOX
Steps
  1. Returns → open the staged return → Issue refund for a single line.
  2. Repeat / show a refund across multiple lines.
✓ Refund(s) issued to individual and multiple order lines; return updated.

✓Demo-day checklist

Prepared for the SKU-8210 Walmart Full-Service Solution Provider approval. Item-lifecycle + OAuth validated live on the pilot; order/return actions validated in Walmart's sandbox (per Walmart guidance). This run-of-show maps every one of Ganga's 11 Final-Demo scenarios to the exact environment, screen, and expected result.