"Units Not Shipped" ... is that option a trap?

Hi! Does anyone know what happens when you select “units not shipped” in the Shipment Contents tab?

We’re fairly certain our 3PL didn’t ship those units, but Amazon is reporting that they received 19 of them.

I’ve never selected that option before and have always left it untouched when Amazon reported excess units. But thinking about it now, I wonder if selecting it might prompt Amazon to reconcile those units with other shipments or events they actually belong to. That said, I can’t help but worry that by declaring we didn’t ship those units, Amazon might use it against us.

Please let me know if you have experience with this. Thank you!

2 Likes

How long has it been since the shipment closed?

Let’s talk about this example below. Shipment checked in on 9-27 and closed on 11-24.

FBA claims we sent 2X what we said. LOL - Nope. We sent precisely what we said. What they claim we sent wouldn’t even fit on a single maxed out 72" pallet.

We had our SAS manager look into this. On the backend, there are 400 units of the 2220 that are sitting in a trailer somewhere and until they are brought in officially into the FC, this error won’t be fixed. From what he sees, Amazon sees ~2600 now, not 4,776. Prime Eligible is what you should be looking at on the shipment before you take any action. This shipment shows 2203 of 2220 - 17 short, which, BTW, isn’t possible either since they go in cases of 12 but I digress.

We were told to do nothing and just wait by our SAS manager.

This isn’t the first time this has happened either. The situations always correct themselves.

But do check the Prime Eligible # first to see if it’s at or close to what you actually shipped.

image

3 Likes

Thank you for the insights!
The shipment was closed on November 19th.
At this point, I’m not sure I can leverage the Prime Eligible # to draw conclusions.
Prime Eligible shows 1552, and Units Located shows 1511.
We declared we would ship 1080, but we actually shipped 804.
However, this shipment is part of a 5-shipment split, that includes another shipment for which Amazon declared they received nothing at all - zero units (still marked as “In Transit” despite being created back on September 27 and likely received in mid-November).
So, it’s a mess in general.

As for the SKU I initially mentioned in this topic, it was supposedly never shipped in any of the five shipments.
Also, we were out of stock for this sku even before the shipment, so these 19 units must either have been shipped by mistake by the 3PL (unlikely because the odd number), or they are old units that were buried in an FC and somehow got triggered by this shipment.

That said, you’ve made me realize it’s better to wait for the other shipment part of this same workflow to close before investigating further.
I should also check the inventory ledger to see if I can get any insights.

Nonetheless, I’m still curious to know if anyone has ever tried clicking that button to see if it helps Amazon reconcile things without penalizing Sellers

2 Likes

We also ran into an issue with a shipment where Amazon showed they received nearly twice as many units as we actually sent. We shipped 9,000 units, but they recorded 16,000.
This went on for a month, and we ended up being charged storage fees for the extra phantom units.

Everyone, be sure to double-check your shipments and ask for a refund if you’ve been overcharged

3 Likes

Thank you for the heads up @Spaghetti :flushed:

2 Likes

My pleasure! Great community here!

2 Likes