Amazon Shortage Claims: Why They Happen and How to Dispute (and Re-Dispute) One

A payment came in short, the remittance shows a deduction against an invoice you were sure was complete, and you want that money back. Vendor Central will let you dispute it, but the claim lives under Payments, away from the Operational Performance screens where chargebacks are handled, and the window to find and work it is shorter than it looks. This guide covers why the claim was raised, where to find it, how to file the first dispute, and how the re-dispute works when the first answer doesn't recover everything.

If you only need the definition, the Shortage Claim glossary entry is the short version, and the console paths below follow it. Some of the dispute and re-dispute detail comes from ChannelEngine and SPS Commerce, which both publish guidance for vendors working these claims, so we name whichever one said it.

Why Amazon Claims a Shortage

A shortage claim is Amazon saying you invoiced for more units than its receiving process recorded. The gap sits between two numbers, the quantity you billed and the quantity the fulfillment center logged when the shipment was booked in. Where Amazon's count is lower, Amazon pays the lower one and raises a claim for the rest, taken off the payment on that invoice.

The two counts can come apart at several points between your dock and Amazon's, and every one of them lands as the same deduction:

• Packing and labeling errors, where the units in a carton don't match the label or the paperwork.
• An incorrect carton assignment, where units are logged against the wrong carton.
• Counting mistakes during goods-in booking at the fulfillment center.
• Transport damage between your dock and Amazon's.
• Missing delivery scans, where freight arrived but was never scanned in.
• Incomplete invoice data, where the invoice doesn't carry what Amazon needs to match it to the receipt.

ChannelEngine adds errors in Amazon's own receiving process to the list. That matters when you decide whether to dispute, because several of these causes start on Amazon's side of the dock, and your records are the only way to show it.

The timing works against you too, because Amazon usually opens the claim about five days before the invoice comes due, so the first time most teams see it is as a smaller number on the remittance than the one they billed.

Where Shortage Claims Live in Vendor Central

Shortage claims are filed and tracked under Payments, and how far back you can see depends on which screen you open.

• Payments, then Invoices, then Review/Dispute Shortages shows the claims raised in roughly the last 30 days. This is the working queue.
• Payments, then Invoices, then View all Invoices reaches older claims. Search by shortage invoice or by invoice date, up to about 90 days back.
• Payments, then Dispute management is a second place to file. Pick the shortage invoice there.
• Deductions and Credits is where the claim itself appears, keyed to the invoice number with an "SC" suffix.
• Financial Scorecard carries a shortages section, which is the place to look when you want the trend across invoices.

Vendor Central's navigation varies by region and account type, so check these labels in your own account before you write a path into a team process. On the remittance itself, the claim is one deduction line posted against a specific invoice; the remittance advice entry covers how to read those lines.

Shortage Claims and Chargebacks Are Separate Paths

Shortage claims and chargebacks both come off your payments, so a lot of teams lump them together, but Vendor Central runs them on separate tracks. A shortage claim is tied to one invoice and settled on the payment side, which puts it outside the Operational Performance chargeback categories. Those categories score compliance defects on their own schedule and carry their own dispute path.

In practice, no scorecard records a shortage claim as a defect, so it never comes up in the weekly or monthly reviews a team builds around Operational Performance, and unless someone reads remittances line by line, the deductions pile up without anyone noticing.

If the deduction in front of you is a compliance charge (ASN accuracy, carton content, PO on-time, prep and labeling), you're on the wrong page. Our guide to Amazon chargebacks on Vendor Central explains the categories, and How to Dispute an Amazon Vendor Chargeback walks through that dispute.

How to Dispute a Shortage Claim

Plan around a 30-day window. ChannelEngine says Amazon generally allows disputes within 30 days of the invoice due date, and Review/Dispute Shortages only lists about 30 days of claims, so the dispute window and the screen that lists the claim close on roughly the same schedule. Work claims as they appear, and when several are open, start with the oldest.

1. Open Payments, then Invoices, then Review/Dispute Shortages.
2. Find the claim and note the invoice number, the PO, the units you invoiced, and the units Amazon recorded as received.
3. Pull your evidence for that shipment before you open the dispute form (the packet is listed below).
4. Select the claim and start the dispute. If you're working an older claim you found through View all Invoices, file from Payments, then Dispute management, and pick the shortage invoice there.
5. Write a short explanation: the invoice and PO, the quantity you shipped, the quantity Amazon recorded, and which attachment proves your number.
6. Attach the documents and submit.
7. Log the submission date next to the claim.

The packet ChannelEngine recommends for a shortage dispute:

• Packing lists and invoices that match each other and clearly show the quantities shipped.
• Shipping confirmations with tracking numbers, proof of dispatch, and delivery confirmations.
• Photos of the packed goods taken before the shipment left.
• Related correspondence with Amazon or your suppliers that explains the shipment.

Match the evidence to the cause where you can. A missing delivery scan is answered by delivery confirmation for that shipment, while a counting mistake at goods-in is answered by a packing list and photos showing the full quantity leaving your dock. If the ASN you sent for the shipment carried the right quantities, include it, because it shows Amazon had your count before the freight arrived.

Don't submit without attachments, since Amazon then has nothing to weigh against its own receiving count. Amazon reviews each claim within 35 days of creating it, so check the claim's status in the same screen on a fixed day each week.

How to Re-Dispute a Shortage Claim

SPS Commerce describes the re-dispute as a separate second step with its own rules. Once the first dispute on a shortage claim is resolved, any shortage that remains can be re-disputed once more, and Amazon reviews each shortage individually and in greater detail on that pass.

What that means for eligibility, going by SPS Commerce's guide:

• The first dispute has to be resolved. A claim still under review isn't ready for a re-dispute.
• There has to be something left to recover. The re-dispute covers the shortage that remains after the first decision.
• Settled claims are closed. Once a claim has been settled, Amazon won't accept a re-dispute on it.
• You get one. SPS Commerce describes it as one more pass, and for many vendors it is the last chance to recover the deduction.

On timing, SPS Commerce says Amazon typically resolves shortage re-disputes within 1 to 4 weeks of submission, and it tells vendors to work the oldest eligible claims first, especially those about to reach the two-year mark, when they expire.

Before you submit, SPS Commerce says to make sure all of your proof is already attached to the claim. Since you only get one pass, read the first decision for what it didn't accept and add the document that answers it, which is usually whatever ties your count to the exact shipment Amazon received: the delivery confirmation, the carton-level packing list, or the photos. Resubmitting the packet that lost the first time gives Amazon no reason to decide differently.

Where the re-dispute option sits in Vendor Central can vary by account, so open a resolved claim in your own account and confirm where the option appears before you write the step into a team process.

If You Came From Seller Central

If most of your Amazon experience is in Seller Central, the thing to know is that a shortage claim comes off what Amazon pays you for an invoice. It shows up on the remittance as a deduction line against that invoice, and because no scorecard treats it as a defect, nothing in the performance reports will point you to it. The only way to find shortages is to read your payments, which most Seller Central teams never had to do.

Reading Shortages as a Rate

Disputing claims one at a time gets money back, but it won't tell you which shipments keep coming in short. For that you need shortages as a rate, and three numbers do most of the work:

• Fill Rate (Receive Fill Rate) is Units Received divided by Quantity Confirmed for the period. It sits on the Forecast and Inventory Planning report in Amazon Retail Analytics (ARA) Premium. When it drops below 100%, compare units received against the ASN and the invoice for the same POs. Any receipt below the ASN quantity is logged as a shortage, and that shortfall is the money at risk.
• Fill Rate - Accepted Rate and Fill Rate - Backordered Rate measure how you answered each PO at confirmation. They sit on the Operational Metrics report as "Accepted confirmation rate" and "Backorder confirmation rate". A high accepted rate next to a low receive fill rate means you confirmed the units and the freight still came in short, which is the pattern that produces shortage claims.
• Net Received is the net amount Amazon received after subtracting what it returned to you in the period, from the Inventory Health report. Set beside what you invoiced over the same weeks, it shows the receiving gap as a trend across shipments.

Then cut your own shortage log by the warehouse or 3PL that shipped, the carrier, and the receiving fulfillment center. If shortages cluster on one 3PL or one lane, the cause is probably on your side and worth fixing before you dispute the next claim. If they spread evenly across lanes and your paperwork is clean, keep disputing, because your records are what will win those claims.

What Vendor Central Will Not Give You

The console lets you find and dispute individual claims, and three parts of the job stay manual.

• History. Review/Dispute Shortages shows about 30 days and the invoice search about 90, so a claim nobody worked in time takes real effort to locate, and a year of shortage history exists only if you kept it.
• The join. The claim sits on the payment side, the receive fill rate sits in ARA Premium, and the PO and ASN quantities sit somewhere else again. Tying a claim back to the shipment that caused it starts as a manual match every time.
• The monthly view. ARA doesn't provide a monthly Net Received, so comparing a month of receipts against a month of invoices means rebuilding it from weekly figures.

InsightLeap does the pulling continuously. It keeps historic Vendor Central reports beyond what Amazon's interface lets you see and holds product-level purchase order data next to its Fill Rate (accepted and backordered), Net Received, and Monthly Estimated Net Received metrics, so the receiving side of a shortage is already lined up when a claim lands. The features page covers what it includes, and the metric glossary defines each field.

Where to Start This Week

Open Payments, then Invoices, then Review/Dispute Shortages, and list every open claim with its invoice number, amount, and invoice due date. Take the oldest first, pull the packet for each, and file. Then look in View all Invoices for anything from the last 90 days nobody touched, and put the Review/Dispute Shortages check on the calendar for the same day every week.