Amazon Vendor Central Not Working? A Triage Guide Before You Open a Case

You were halfway through a weekly sales pull, a PO check, or an invoice question when Vendor Central stopped cooperating. Maybe the sign-in page won't let you through, maybe a Retail Analytics report came back empty, or maybe the numbers suddenly look twice as big as last week. Before you open a case, work out which kind of problem you have, because several things that look like a broken console turn out to be a setting on your side or Amazon working as designed: a sign-in step your browser is blocking, a report setting that changed which ASINs Amazon is counting, or a reporting period whose data hasn't landed yet.

This guide goes symptom by symptom, in the order you tend to hit them. For the problems that do need Amazon, it hands you off to our guide to opening a case in Vendor Central instead of repeating it here.

You can't sign in

The Vendor Central sign-in page has two error states worth recognizing by their exact wording, because each one tells you what to do next.

The first reads "Please Enable Cookies to Continue." The sign-in page needs cookies to work, so this is your browser refusing them, and nothing is wrong with your account. Work through it in this order:

1. Allow cookies for the Vendor Central sign-in in your browser settings.
2. Turn off any privacy or ad-blocking extension that strips cookies, then reload the sign-in page.
3. If the error survives both, try a different browser. If that works, a managed browser policy on your work machine is the likely blocker, and that's a ticket for your IT team.

The second is a passkey failure. You'll see "Something went wrong, please sign-in another way," or the longer version: "Sorry, your passkey isn't working. There might be a problem with the server. Sign in with your password or try your passkey again later." Amazon's own message gives you the way in, so sign in with your password and try the passkey again later.

If neither fallback gets you in and a colleague with access to the same account can still sign in, ask them to open the case for you from inside the console, since that's where cases are filed.

If what you're looking at is a message about the account itself, such as a suspension or the end of your vendor relationship, nothing in this guide applies. That's a commercial conversation with Amazon, and our guide to avoiding vendor suspensions is the better starting point.

The report loads but shows nothing

You're in, you've opened Reports, then Retail Analytics, and the report you need is blank or far smaller than it should be. Before assuming the console is broken, check the four settings that decide what a Retail Analytics report contains. Our Retail Analytics walkthrough covers where each control sits on the page.

1. Check the period against Amazon's data latency. Weekly reporting periods close on Saturday, and their data becomes available by end of day Monday, 48 hours after the period closes. Daily periods take 72 hours, and in some cases the delay stretches to as long as a week. So last week's report opened on Monday morning, or yesterday's daily report, can come back empty because the data doesn't exist yet. Move the date range back one period and see whether the report fills in.
2. Check the Distributor View. On the Sales and Inventory reports, Sourcing View counts only the ASINs Amazon bought from you under your own vendor code, and Manufacturing View counts every ASIN carrying your brand, whatever vendor code Amazon bought it through. An ASIN that reaches Amazon only through a distributor will never show up in Sourcing View. If the Manufacturing option is missing from your account entirely, that's because Amazon reserves it for the registered brand owner, so check brand ownership before you file anything. The Manufacturing vs Sourcing View glossary entry explains both settings.
3. Check the program. Reports default to Retail, and accounts that sell into other programs, such as Amazon Fresh or Amazon Business, can switch between them. If your volume runs through Fresh and the report is set to Retail, the total will look far too small.
4. Check the ASIN filter. The additional-filters control narrows a report to a specific set of up to 100 ASINs, and it applies to both the screen and the export. If a filter is applied, any ASIN outside that set drops out of both the screen and the file.

If all four check out and the report is still empty for a period that should have landed days ago, you have something worth a case.

If you came from Seller Central

In Seller Central you went to Reports, then Business Reports, and picked By Date or By ASIN from the left rail. Vendor Central replaces that with report families under Retail Analytics, and the per-ASIN cut you used to pick from the rail becomes a filter you apply inside a report. The Distributor View and the program switch have no Seller Central counterpart, because they sort Amazon's purchases by vendor code and selling program, and they're the first two settings a former seller should check when a number looks wrong.

The numbers look doubled

The opposite symptom is a total that suddenly looks inflated, with nothing in your POs or shipments to explain it.

Amazon reports Retail Analytics data separately for each combination of Distributor View (Manufacturing or Sourcing) and Selling Program (Retail, Business, or Fresh). Pull more than one of those combinations without filtering and the same ASIN and day appear more than once, which inflates Shipped COGS, shipped revenue, and shipped units when you total them.

In practice it usually comes from one of two places: exports pulled under different settings that got stacked into the same spreadsheet, or a reporting connector that pulls every combination and sums them. To find it:

1. Count rows per ASIN per day. More than one row for the same ASIN and day means you're looking at more than one view or program.
2. Add a column to every export that records the view and program it was pulled under, so the duplicates become visible.
3. Pick one view per question. Sourcing View answers what Amazon bought from you, and Manufacturing View answers how your brand did across every route to Amazon. Since Manufacturing View already includes the ASINs Amazon bought from you, adding the two together counts your own volume twice.
4. If a connector feeds your dashboard, filter it to the view and program you mean before it totals anything.

The same mismatch is why two people quoting the same week's sales can disagree, so name the view and program whenever a figure leaves Vendor Central.

A specific workflow is stuck

Some problems live inside one workflow, and each has its own guide:

• A PO you expected isn't where you remember it, or you need to know what you confirmed three weeks ago: how to track purchase order history in Vendor Central.
• An invoice is sitting in a status you don't recognize, or payment hasn't arrived: Vendor Central invoices, rejections, holds, and getting paid.
• A listing changed and nobody on your team changed it: how to audit catalog and content changes on Vendor Central.
• A deduction showed up on your remittance: how to dispute Amazon vendor chargebacks and how to dispute and re-dispute shortage claims.

When it really is Amazon

Sometimes the console is down. If pages won't load at all, look at a public outage tracker to see whether others are reporting the same thing, and ask a colleague to try from their own login and network. If it's down for everyone, there's nothing to fix on your side, so note the time and come back later.

If the site is up, you've ruled out the sign-in fallbacks, the latency window, and the four report settings, and the problem is still there, open a case. Put what you already checked into the first description: the report, the date range, the granularity, the Distributor View, the program, and any ASIN filter. Those are the details support needs to reproduce what you're seeing, and putting them in up front saves a round trip of questions. Our case and Case Log guide covers writing the case and escalating it when it stalls, and the Vendor Central console map shows where everything else lives.

What Vendor Central will not give you

Every check above is something you do by hand each time, because the console leaves three jobs to you:

1. The diagnosis. Vendor Central won't tell you whether an empty week is still inside the latency window or simply set to the wrong view or program. So you run the same checklist yourself whenever a report looks off.
2. A record of the settings. Each download covers one report, one date range, and one view, and nothing joins those downloads across reports, so a figure from last month's deck can't be reproduced unless someone wrote down the settings behind it.
3. The weekly repeat. Because last week's data lands on Monday, and sometimes days later, somebody has to come back and pull it once it's there, every week.

InsightLeap does that pull continuously: it connects to Vendor Central, Amazon Advertising, and Amazon.com, pulls product-level sales, inventory, traffic, returns, and open PO units on a schedule, and keeps historic Vendor Central reports past the window Amazon's own interface shows.

Next time a report looks broken, run the four checks in order before anything else: the period, the Distributor View, the program, and the ASIN filter. Then write those four settings next to any number you send on, so the person reading it can pull the same figure.