Supplier support tickets: filing, following up, and escalating to the merchant

A ticket asks Walmart to act on what you cannot change yourself.

Fix it by resubmission when the field is editable (attributes, content, images, packaging data) through the Maintenance Hub loop that Content maintenance covers.

File a ticket when:

• a submission is stuck in processing well past normal time, with no error and nothing in your action queue or Walmart's (one waiting on Walmart's review is the merchant's queue, not a ticket);
• content was accepted and the record holds the new value, but the page shows the old one;
• a page or import fails with a system error, not a field error;
• an identifier conflicts: your GTIN sits on another item, or one item has two Walmart item numbers;
• the data sits in Walmart's catalog, not editable by you.

Take it to the merchant when the outcome is a decision: approval, assortment, store assignment, or re-grouping a live group you cannot edit in the Catalog (Variant groups and re-parenting covers which); Issue resolution covers the triage.

Tickets are raised in Supplier One, in most accounts under Help → Manage tickets (sometimes labelled Walmart Supplier Help), which lists current and closed tickets and creates new ones; labels change. Retail Link's help desk, by phone, handles access and account problems; either way, raise each issue once.

The issue type (and the channel — stores or online — and subtype, where the form asks) matters most: it decides which queue reads the ticket; a miscategorized one waits to be re-routed.

Include:

• the Walmart item number;
• the GTIN at the affected packaging level: each UPC for a page problem, case GTIN-14 for a warehouse pack;
• your supplier number;
• the Submission ID the Submissions Manager (older guides: Activity Monitor) shows, with its date, where a listed submission caused it (submissions age out);
• current state and requested state;
• evidence: a dated screenshot, export row or approved specification.

One issue per ticket. Items sharing an issue and requested state can share one, listed per line; four problems get one answer, and three disappear.

A ticket sits in your current or closed list, and while current may be flagged as needing your action; other status names vary, so read a status as whose move it is. The flag matters: a ticket left there can be closed with nothing fixed, and a closed ticket looks resolved in a report.

• Reply in the same ticket. A second agent reads it from the top; a new ticket restarts the clock without history.
• Answer what was asked. If the reply wants an identifier you already sent, send it again; arguing costs a round-trip.
• Chase on the stated clock. Wait out any response time the ticket states; an early reminder reads as a new message, not a nudge.
• After a close, cite. Walmart's help docs currently say a closed ticket is not reopened: file a new one on the same issue type, naming the old number in its first line and reattaching the evidence.

Record the ticket ID and the date of your last reply against the item in your tracker.

The merchant (buyer) is not a second support queue. Escalate for two reasons:

1. a ticket on a commercially important item has stalled: several rounds with no change, or a ticket closed after you had replied, with nothing fixed;
2. the outcome is a merchant decision from the list above, which support cannot grant.

A ticket closed because your own reply was late is not a stall; refile it.

Bring a message the merchant can forward unedited: ticket IDs with dates and status, Walmart item numbers and GTINs, and one paragraph: what is wrong, what you have done, the result you need. A merchant can route what support cannot.

Switch paths deliberately. If a ticket is still open when the merchant steps in, say so in both places and let the merchant path be the record. A ticket and a merchant request running at once produce two answers, and the second often undoes the first.

A ticket marked resolved describes the ticket; the item is resolved when you have looked. Open the item on walmart.com (the item record for store-only items) and compare it with the requested state, then check the Submissions Manager: nothing for the item should still be processing or waiting on your action. If both match, close the row with the date, ticket ID and what you saw; otherwise reply with a fresh dated screenshot, in the open ticket or a new one citing the old number, or escalate after a second failed round.

Log the cause: your data, a Walmart-side processing fault, an identifier conflict, a merchant decision.

In order:

1. File the ticket with identifiers and evidence.
2. Reply in the same ticket, answering what each response asks.
3. If the ticket stalls or closes unfixed, refile citing the old number or escalate to the merchant.
4. When the ticket reports resolved, verify on walmart.com and in the Submissions Manager.
5. Close the row in your tracker and log the cause.