Always dispute. They are equally as incompetent at resolving these kind of problems as they are at receiving inventory. Use that to your benefit.
We had one last year where they ran out of inventory and could not validate the issue so it went away.
We prefer to see this …
than admit to making a mistake.
Yes, we have this option. We have used it from time to time. Thank you VTR!
I’ll keep everyone updated on the outcome! Thank you
Always dispute. They are equally as incompetent at resolving these kind of problems as they are at receiving inventory. Use that to your benefit.
We prefer to see this …
Autoreplying to myself…
I figured the reason for this may also be that the boxes get unpalletized by amazon after the initial receival and right after that, shipped to 30-40 fulfillment centers at a time.
So it may be that only one of the fulfillment centers involved in this initial distribution, catches the faulty units.
…also auto-liking
Normally the receiving DC will be the DC that dings the no-scan upon receipt. They are the only entity at Amazon counting against the shipped qty. You will never run into a situation I don’t believe, and we haven’t, where the same shipment gets hit more than once, by more than 1 entity of Amazon’s.
The receiving DC determines the health of the shipment, where it gets transferred to is only double checking the qty transferred if they even do that. They may not. Those may be blind receipts, trusting that the receiver has received the full qty and accounts for the inventory.
It doesn’t make logistical sense for the receiving FC, on transfer, to count it again in the name of speed and efficiency.
In a past life, when I ran a chain of stores, our DC was so good, (routinely audited), that we made the decision as a company that the stores would just trust that what we said we shipped to them was shipped. Open the boxes, put the product on the shelf, mark shipment received, inventory updated, move on to selling…
These were all company owned stores so I guess it really didn’t matter but our inventories were always 99%+ accurate on cycle counts and year end counts. Low shrink / theft business back in the day.
I’m grateful for the clarity you’ve provided!
It must have been a relief to have such high accuracy levels in your stores…
A different dimension from what we experience here 
What actually happens is that the receiving FC certainly does scan and count what other FCs send them, and this is why when something is sent between FCs, the “loss” of one or more units can logged, and the seller blamed for “incorrect quantity”, even though Amazon’s inventory ledger shows all items counted properly at the first FC to get the shipment.
Amazon lost 1300 units last summer, and I had to fight for reimbursement on each and every one.