Seller Support cases: catalog, variation, browse node, and image requests that get acted on

A case asks a person to change what the system would not. Rule out what you control first:

• Your offer. Price, quantity, condition, handling time. An offer-side Inactive or Incomplete status is never a case.
• Your contribution. A missing attribute, a wrong value you submitted, a suppressed listing: the edit page or a PartialUpdate (Listing maintenance).
• Permission. Gated categories and brands need approval (Brand programs and gating).

A case is right when your own upload cannot move the page: a conflict error (Listing creation) where the catalog, not your file, is wrong; a clean report and an unchanged page; a family that flat files cannot fix; a node or image that ignores the right value.

The deciding limit: a case cannot override another contributor's valid data without authority (Brand Registry) or proof the live value is wrong. With neither, asking to change what a brand owner set is declined: that contribution outranks yours by design (Catalog fundamentals).

The path. Help → Get Support, in most accounts. The flow offers articles, then issue paths. The product and listing paths — product page, variations, category or browse node, images — each reach a different team, so pick the one that matches the field. My issue is not listed (the label varies) is for when nothing fits; it bypasses the field-specific paths, so expect a general first reply — put the field and evidence in the first message anyway. Enrolled brand owners also have Brand Registry support, a separate queue inside the Brand Registry portal with authority over brand content.

The first message follows the same discipline as Vendor Central cases (Amazon 1P → Case management):

• one issue per case;
• the SKU, ASIN and marketplace;
• the field by name, the value shown, and the requested value exactly as it should display;
• the evidence, attached: packaging photos, the manufacturer's page, an invoice, the batch ID of the upload that changed nothing.

Catalog data cases — a title, brand or attribute an upload cannot change. State the contribution conflict and attach proof: packaging photos, the manufacturer's page, the GTIN's GS1 record showing the brand. Whitelisting cases (Brand programs and gating) share this shape.

Variation cases — merges, splits, re-parenting, theme changes and broken families that a clean flat file could not fix: the evidence Parenting and variations lists (parent and child ASINs, theme, each child's values, batch ID) plus which children belong under which parent.

Browse node cases — once your own submission changed nothing: the target node ID from the marketplace's Browse Tree Guide (Seller Central help), the item type keyword if listed, and why the current node is wrong. Without an ID it usually comes back.

Image and attribute cases — what you uploaded, what displays, the batch ID, and proof of authority (Brand Registry enrollment) or accuracy (the product as sold). An outranked image is a case, as is a rejection you can show is mistaken; a rule-breaking image is a replacement (Images and video).

Every case lives in the Case Log with a status saying whose move it is: Waiting on Amazon, Waiting on you, Answered, Resolved. Labels change; the loop does not.

• Reply in the same case. A new case on the same issue restarts the evidence trail; parallel cases on one ASIN get contradictory answers.
• Answer inside the window. A case waiting on you closes by itself after a set period; reply before it does.
• Reopen with something new. A resolved case can usually be reopened for a while: bring fresh evidence or a screenshot of the unchanged page, not the first message again. Once that option is gone, open one new case citing the old ID.
• Switch channel when the written loop stalls. Request a call or chat where offered (callbacks are generally a Professional-plan feature; chat is not in every store); a live agent can read the history and request a transfer.
• Keep the case ID in your tracker beside the SKU's submitted and verified statuses (Listing maintenance).

A canned reply is a signal, not an answer. When it restates a help page or the edit page you tried, ask in the same case for a transfer to a specialist team, citing the upload's batch ID.

Brand Registry support is where an enrolled brand owner escalates a case on its own brand's content: authority over what a brand owner set, not over enforcement. Account Health is enforcement, not escalation: a block or policy warning is appealed from the notice on the Account Health page (Account Health support, where offered, is its help line). Catalog issues sent there come back; enforcement sent to catalog support goes nowhere; the wrong line costs weeks.

The lifecycle:

1. Open with SKU, ASIN, field, current and requested value, evidence.
2. Reply in the same case, inside the window.
3. Escalate after a canned reply: specialist team, Brand Registry support, or a call.
4. Verify on the live page — Resolved describes the case, not the page.
5. Close in your tracker with the case ID and the date it displayed.