I have noticed mods have made an increased effort as of late to assist, so I figured now may be the best time to get an answer to this question, as well as educate other sellers of a common problem managing FBA inventory and a common receiving issue when they think Amazon has lost inbound inventory.
Mods, please get one of your fellow Amazonians from the appropriate silo, to explain to sellers why negative receiving is used to move items internally instead of using transfers. See below…
@SEAmod, @Quincy_Amazon, @CR_Amazon, @Tiff_Amazon, @Ricardo_Amazon, @Gary_Amazon, @Wyatt_Amazon
The internal use of this movement, causes sellers to see their received inventory diminish in the Manage FBA Shipments GUI, thinking their items were never checked in on their shipment. It also prevents sellers from seeing their on hand inventory via the reserved line.
In our example above, we had 0 inventory prior to July 11, then 48 received, but looking at the Manage FBA Shipments page it looks like this now 10 days later.
This causes confusion for sellers, as to if product was received, and makes managing inventory impossible when inventory is not correctly visible to sellers in the Manage FBA Inventory page as it does not show up in reserved when negative receiving is used. Please explain what tools can be used to mitigate this confusion, that sellers rely on for inventory management, and what purpose it serves to use negative receiving to internally move inventory around the platform, as the inventory almost always simply appears at another destination later on.
Thank you, @VTR, for the acknowledgement, and for surfacing this issue for a broader discussion and investigation.
I will troubleshoot the example provided within this thread, and use that context to get more clarity or a solution from our FBA team.
I understand this topic has been discussed widely within the community, so I welcome other sellers to share their similar experiences so that we can gather additional insights.
Thank you,
Gary
@VTR
Shame on me…I missed your thread…
I’m pretty good at finding lost/negative items.
But there are limitations to what sellers (and amazon) can do.
The received inventory report identifies the items/shipments by FBA Shipment ID.
This report identifies also the source of the missing/negative quantity.
So far, it’s easy.
The problem is if later on amazon locates the items, either adds to the inventory or reimburses the sellers.
At this point, the seller does not know the source, when, and why these items appeared in our account.
I assume that in many cases amazon also does not why an item was found where it should not be in the first place.
Not every thing has an explanation and can be traced.
Old code.
Bad Code.
DBAs (“Database Administrators”), & SysAdmins, and decision makers enjoying higher perches than those in the bureaucratic hierarchy, who are not worth their salt.
Take your pick - there’s plenty of blame to go around.
Here is another example of a negative receipt making a seller think their inventory is missing during receiving.
Here is another example of the GUI telling sellers Amazon never received their stuff when the reports show it was counted.
Here is another example. Check your reports before assuming your stuff is missing.
Greetings @Gary_Amazon,
Noticed you have not been back with a reply, even if just to tell us you found nothing since August 15. Did you find anything, is there a reason this is happening to sellers causing them to think their inventory is lost and in some cases stolen?
I just hope people understand that there is more than one avenue to reimbursement if there is a negative receipt after your shipment was entered into inventory. It requires one to wait then file for lost inventory using the reports data.
Obviously, if you made a shipment to TUL2 and there is a negative receipt at RDU1, 7 days later, which you have never made a shipment to, you have a clear case for reimbursement, escalation to the executive channels, and clear evidence to hand to your lawyer for arbitration purposes.
I have noticed mods have made an increased effort as of late to assist, so I figured now may be the best time to get an answer to this question, as well as educate other sellers of a common problem managing FBA inventory and a common receiving issue when they think Amazon has lost inbound inventory.
Mods, please get one of your fellow Amazonians from the appropriate silo, to explain to sellers why negative receiving is used to move items internally instead of using transfers. See below…
@SEAmod, @Quincy_Amazon, @CR_Amazon, @Tiff_Amazon, @Ricardo_Amazon, @Gary_Amazon, @Wyatt_Amazon
The internal use of this movement, causes sellers to see their received inventory diminish in the Manage FBA Shipments GUI, thinking their items were never checked in on their shipment. It also prevents sellers from seeing their on hand inventory via the reserved line.
In our example above, we had 0 inventory prior to July 11, then 48 received, but looking at the Manage FBA Shipments page it looks like this now 10 days later.
This causes confusion for sellers, as to if product was received, and makes managing inventory impossible when inventory is not correctly visible to sellers in the Manage FBA Inventory page as it does not show up in reserved when negative receiving is used. Please explain what tools can be used to mitigate this confusion, that sellers rely on for inventory management, and what purpose it serves to use negative receiving to internally move inventory around the platform, as the inventory almost always simply appears at another destination later on.
I have noticed mods have made an increased effort as of late to assist, so I figured now may be the best time to get an answer to this question, as well as educate other sellers of a common problem managing FBA inventory and a common receiving issue when they think Amazon has lost inbound inventory.
Mods, please get one of your fellow Amazonians from the appropriate silo, to explain to sellers why negative receiving is used to move items internally instead of using transfers. See below…
@SEAmod, @Quincy_Amazon, @CR_Amazon, @Tiff_Amazon, @Ricardo_Amazon, @Gary_Amazon, @Wyatt_Amazon
The internal use of this movement, causes sellers to see their received inventory diminish in the Manage FBA Shipments GUI, thinking their items were never checked in on their shipment. It also prevents sellers from seeing their on hand inventory via the reserved line.
In our example above, we had 0 inventory prior to July 11, then 48 received, but looking at the Manage FBA Shipments page it looks like this now 10 days later.
This causes confusion for sellers, as to if product was received, and makes managing inventory impossible when inventory is not correctly visible to sellers in the Manage FBA Inventory page as it does not show up in reserved when negative receiving is used. Please explain what tools can be used to mitigate this confusion, that sellers rely on for inventory management, and what purpose it serves to use negative receiving to internally move inventory around the platform, as the inventory almost always simply appears at another destination later on.
Thank you, @VTR, for the acknowledgement, and for surfacing this issue for a broader discussion and investigation.
I will troubleshoot the example provided within this thread, and use that context to get more clarity or a solution from our FBA team.
I understand this topic has been discussed widely within the community, so I welcome other sellers to share their similar experiences so that we can gather additional insights.
Thank you,
Gary
@VTR
Shame on me…I missed your thread…
I’m pretty good at finding lost/negative items.
But there are limitations to what sellers (and amazon) can do.
The received inventory report identifies the items/shipments by FBA Shipment ID.
This report identifies also the source of the missing/negative quantity.
So far, it’s easy.
The problem is if later on amazon locates the items, either adds to the inventory or reimburses the sellers.
At this point, the seller does not know the source, when, and why these items appeared in our account.
I assume that in many cases amazon also does not why an item was found where it should not be in the first place.
Not every thing has an explanation and can be traced.
Old code.
Bad Code.
DBAs (“Database Administrators”), & SysAdmins, and decision makers enjoying higher perches than those in the bureaucratic hierarchy, who are not worth their salt.
Take your pick - there’s plenty of blame to go around.
Here is another example of a negative receipt making a seller think their inventory is missing during receiving.
Here is another example of the GUI telling sellers Amazon never received their stuff when the reports show it was counted.
Here is another example. Check your reports before assuming your stuff is missing.
Greetings @Gary_Amazon,
Noticed you have not been back with a reply, even if just to tell us you found nothing since August 15. Did you find anything, is there a reason this is happening to sellers causing them to think their inventory is lost and in some cases stolen?
I just hope people understand that there is more than one avenue to reimbursement if there is a negative receipt after your shipment was entered into inventory. It requires one to wait then file for lost inventory using the reports data.
Obviously, if you made a shipment to TUL2 and there is a negative receipt at RDU1, 7 days later, which you have never made a shipment to, you have a clear case for reimbursement, escalation to the executive channels, and clear evidence to hand to your lawyer for arbitration purposes.
Thank you, @VTR, for the acknowledgement, and for surfacing this issue for a broader discussion and investigation.
I will troubleshoot the example provided within this thread, and use that context to get more clarity or a solution from our FBA team.
I understand this topic has been discussed widely within the community, so I welcome other sellers to share their similar experiences so that we can gather additional insights.
Thank you,
Gary
Thank you, @VTR, for the acknowledgement, and for surfacing this issue for a broader discussion and investigation.
I will troubleshoot the example provided within this thread, and use that context to get more clarity or a solution from our FBA team.
I understand this topic has been discussed widely within the community, so I welcome other sellers to share their similar experiences so that we can gather additional insights.
Thank you,
Gary
@VTR
Shame on me…I missed your thread…
I’m pretty good at finding lost/negative items.
But there are limitations to what sellers (and amazon) can do.
The received inventory report identifies the items/shipments by FBA Shipment ID.
This report identifies also the source of the missing/negative quantity.
So far, it’s easy.
The problem is if later on amazon locates the items, either adds to the inventory or reimburses the sellers.
At this point, the seller does not know the source, when, and why these items appeared in our account.
I assume that in many cases amazon also does not why an item was found where it should not be in the first place.
Not every thing has an explanation and can be traced.
@VTR
Shame on me…I missed your thread…
I’m pretty good at finding lost/negative items.
But there are limitations to what sellers (and amazon) can do.
The received inventory report identifies the items/shipments by FBA Shipment ID.
This report identifies also the source of the missing/negative quantity.
So far, it’s easy.
The problem is if later on amazon locates the items, either adds to the inventory or reimburses the sellers.
At this point, the seller does not know the source, when, and why these items appeared in our account.
I assume that in many cases amazon also does not why an item was found where it should not be in the first place.
Not every thing has an explanation and can be traced.
Old code.
Bad Code.
DBAs (“Database Administrators”), & SysAdmins, and decision makers enjoying higher perches than those in the bureaucratic hierarchy, who are not worth their salt.
Take your pick - there’s plenty of blame to go around.
Old code.
Bad Code.
DBAs (“Database Administrators”), & SysAdmins, and decision makers enjoying higher perches than those in the bureaucratic hierarchy, who are not worth their salt.
Take your pick - there’s plenty of blame to go around.
Here is another example of a negative receipt making a seller think their inventory is missing during receiving.
Here is another example of a negative receipt making a seller think their inventory is missing during receiving.
Here is another example of the GUI telling sellers Amazon never received their stuff when the reports show it was counted.
Here is another example of the GUI telling sellers Amazon never received their stuff when the reports show it was counted.
Here is another example. Check your reports before assuming your stuff is missing.
Here is another example. Check your reports before assuming your stuff is missing.
Greetings @Gary_Amazon,
Noticed you have not been back with a reply, even if just to tell us you found nothing since August 15. Did you find anything, is there a reason this is happening to sellers causing them to think their inventory is lost and in some cases stolen?
Greetings @Gary_Amazon,
Noticed you have not been back with a reply, even if just to tell us you found nothing since August 15. Did you find anything, is there a reason this is happening to sellers causing them to think their inventory is lost and in some cases stolen?
I just hope people understand that there is more than one avenue to reimbursement if there is a negative receipt after your shipment was entered into inventory. It requires one to wait then file for lost inventory using the reports data.
Obviously, if you made a shipment to TUL2 and there is a negative receipt at RDU1, 7 days later, which you have never made a shipment to, you have a clear case for reimbursement, escalation to the executive channels, and clear evidence to hand to your lawyer for arbitration purposes.
I just hope people understand that there is more than one avenue to reimbursement if there is a negative receipt after your shipment was entered into inventory. It requires one to wait then file for lost inventory using the reports data.
Obviously, if you made a shipment to TUL2 and there is a negative receipt at RDU1, 7 days later, which you have never made a shipment to, you have a clear case for reimbursement, escalation to the executive channels, and clear evidence to hand to your lawyer for arbitration purposes.