How to Open a Case in Vendor Central: Contact Us, the Case Log, and Escalation Paths

Something on the account needs Amazon to act: a payment that hasn't arrived, a routing request you need changed after it was tendered, a listing that changed under you. For most vendors the fix starts with a support case, which runs through Contact Us and the Case Log, and even vendors who still have a named Amazon contact usually get sent back there. The catch is that most of the guides you'll find describe Seller Central, whose menus and case statuses don't match what a vendor account shows.

This guide follows the order you'll meet things in: finding Contact Us, picking the case category, writing a description that gets worked on the first pass, and reading the Case Log afterwards. It finishes with when a Vendor Manager or an AVS contact gets involved.

Where Contact Us lives in Vendor Central

Every support case starts from Contact Us, and the path most vendor guides describe goes like this:

1. Log in to Vendor Central.
2. Click Help in the top-right corner of the screen.
3. In the box that opens, click Contact Us at the bottom.

Menus differ between accounts, so if your Help panel doesn't match, find Contact Us in your own account's help area and write the path down where whoever covers for you can see it. That way the next person on your team who has to open a case doesn't start by hunting for the button.

Be careful with paths borrowed from seller guides. If one tells you to open Performance and then Account Health to reach the Case Log, it's describing Seller Central, and you won't find those menus in a vendor account.

Pick the category that matches the problem

Contact Us asks what the case is about before it asks you to describe it. Amazon uses that choice to decide which team sees the case first, so a case filed under the wrong topic starts with people who then have to pass it along.

Category names vary by account, so there's no fixed list worth memorizing. Two examples from our other guides show how specific the right choice can be:

• Changing a Collect routing request after it has been tendered goes through Contact Us with Shipments as the support topic, per Amazon's vendor shipping manual. The PO shipping guide covers when that applies.
• Paper invoice corrections go through Contact Us, then Accounting, then "Where's my payment?", according to Amalytix. The invoices and payment holds guide covers the rest of that process.

Three rules keep the choice simple:

1. Choose by what Amazon has to change. A late payment caused by an invoice problem belongs with accounting, even if you first noticed it while looking at a PO.
2. File one problem per case. A case that mixes a shipment issue with a payment issue lands with one team that owns only half of it.
3. When nothing fits, pick the closest topic and say in the first line of the description which team you think should handle it.

Write the case so it gets worked on the first pass

Your opening description stays attached to the case for its whole life. The Case Log keeps it alongside the creation date, the case ID, the status, the status notes, and the case owner's email, so whoever picks the case up next week reads exactly what you wrote today. Write it for someone who has never seen your account.

Before you submit, check the description against this list:

• The ask comes first. The opening sentence says what is wrong and what you need Amazon to do about it.
• Every identifier the problem touches. PO numbers, ASINs, invoice numbers, and for freight problems the ARN, BOL, and PRO numbers. Type them as text so they can be searched and copied.
• Dates and amounts. When it happened, what you expected, and what you actually got.
• What you've already tried. Include the case ID of any earlier case on the same problem so the history stays connected.
• A watched inbox. The case owner's email is recorded on the case, so open it from a login whose inbox someone on your team actually reads.

After you submit: reading the Case Log

The Case Log is where Vendor Central lists every case you've submitted or been copied on, each with its case ID, status, and status notes. A Vendor Central case has one of three statuses: open, resolved, or expired.

Status notes are the field to read closely, because a note there means one of two things. Either Amazon needs something from you before the case can move, or Amazon has reopened the case for further investigation. The second is easy to miss, since a case your team thought was finished can be back in play without anyone noticing.

A few habits keep cases from sitting:

1. Check the Case Log on a set schedule, and daily while an active problem is open.
2. Read the status notes on resolved cases as well as open ones.
3. When a note asks for information, answer it in the case and quote the case ID.
4. If you have to raise the issue anywhere else, lead with the case ID.

The Case Log glossary entry defines each field and status in full.

When a human gets involved

Whether anyone at Amazon works your case personally depends on which of three situations your account is in.

You have a Vendor Manager. A Vendor Manager owns your commercial relationship within one product category and typically carries 50 to 150 vendor accounts at once. VMs are scored on category sales and profitability, and their attention follows those two numbers. If you know your VM's name, you can call Amazon's corporate number, 206-266-1000, and ask for them. Expect that call to end with a suggestion to create a case under Contact Us, which Amazon treats as the faster way to solve the issue. So keep the VM for the commercial relationship they own, and when an operational problem does come up with them, bring the case ID.

You're enrolled in AVS. AVS (Amazon Vendor Services) is Amazon's paid, invitation-only account-management program. Enrollment comes with an assigned contact, called a Customer Success Manager in some accounts and a Brand Specialist in others, who handles catalog work for the account. That contact is separate from your Vendor Manager, who still owns the category relationship.

You have neither. Vendors whose accounts don't move the VM's category numbers increasingly lose a personal Amazon contact, and their support becomes partly or completely automated. For those accounts the Case Log is the whole support channel, so the category you pick and the description you write are the only levers you have.

Chargebacks run on a separate track

Chargeback disputes follow their own process. They go through Reports, then Operational Performance, and they don't appear as cases in the Case Log, so don't wait for a dispute to show up there. The chargeback dispute guide walks through that process, and the chargebacks glossary entry defines the categories.

If you came from Seller Central

Seller Central has its own Case Log, and if you learned Amazon support there, it's natural to expect the vendor version to work the same way. It differs in three places:

• Where the log lives. Seller Central puts the Case Log under Performance, then Account Health. Neither of those menus is a Vendor Central path.
• Statuses. Seller Central cases are Open, Pending, or Closed. Vendor Central has no Pending status, and it has an expired status that Seller Central doesn't. If a guide tells you to look for Pending cases, it's describing the Seller Central tool.
• Where the action items show up. In Vendor Central, the signal that Amazon needs you, or has reopened something, lives in the status notes.

If you run a hybrid account, keep the two processes separate in your team's notes and open each case from the account that owns the problem. The Vendor Central, Seller Central, and hybrid comparison covers how the two account types differ more broadly.

What Vendor Central will not give you

The Case Log only tracks problems someone already noticed and filed. Nothing in it tells you that a buy box was lost overnight, that a variation broke, or that content changed on a listing, so a person has to spot each of those first. And because chargeback disputes run on their own track, the Case Log isn't a complete record of everything you have open with Amazon either.

InsightLeap does the noticing step continuously. It monitors the full catalog and sends daily email notifications for lost buy boxes, replenishment code changes, broken variations, and content changes, so you can open the case with the ASIN and the change already in hand.

Before you open the next case, write the one-line ask, collect every identifier the problem touches, and pick the category by what Amazon has to change. Then put the Case Log and its status notes on your team's regular checklist so a reopened case doesn't sit unanswered.