Countries
Read onlyHi,
I made a 1 SKU shipment on an entire pallet. Amazon blantently lost 361 units of my product now are CLAIMING that there was an unexpected SKU and can't find the product. They were all labeled with the same TRANSPARENCY SKU and on 1 Pallet. Please @KJ_Amazon help me get reimbursed this is insanity. It's legitimate stealing.
"Our research shows that the 361 units of FNSKU X002U5NA5V that you sent with shipment FBA18M57X6NK have arrived at our fulfillment center as an unexpected FNSKU when compared to your shipping plan. Unfortunately, we are unable to recover the physical inventory of the located item at this time, due to the error in shipment plan creation. We are unable to reimburse or reconcile the discrepancies you have asked to investigate for these items because of the error."
CASE ID: 17095467541
This must be addressed. We are all having the same issue. This is akin to coordinated theft.
We have noticed that there seems to be a nominal threshold. If they lost 1-5 items, then they will just reimburse you within 24 hours.
However, if there are a lot of items missing - like 20+ - then you enter the endless vortex of nonsensical automated messages.
It's obvious what is happening. The call centers clearly got instructions from corporate to pay out as little as possible.
Thank you for those details about your recent shipping disputes, @Seller_0KzODj7TYxI4v
I asked our partner team to review CASE ID: 17095467541 and the related investigation to determine if any additional steps are available for you to escalate your disputes.
KJ_Amazon
Were any other shipments going out the same day from the same origin?
Is it possible the wrong Amazon labels were on cartons/pallet, even if the transparency codes on the ASINs were correct?
Was a 3PL or supplier handling the outbound, and is it possible they could have mixed up the labels?
Did you drop ship it from the vendor or pack it yourself and send it?
If you drop shipped it you really have no idea how it was labeled.
Did this ever get resolved? We just experienced the same issue.