When I first saw a complaint about this on the FUFE today, I assumed that it was a typo by the OP, and that they meant to say ‘ASIN’. Since then, I have seen several more complaints.
Is Amazon really doing this?
4 Likes
I believe I’ve found one of the discussions you’ve seen in the Screaming Harridan’s Abomination NSFE:
https://sellercentral.amazon.com/seller-forums/discussions/t/608efe98-ff79-40cb-95cb-789e2b39b93b
Between Q3 of 2011 & Q2 of 2015, it was so-common an occurrence, for us, to have Amazon remap our ASINs to a different one - thereby wreaking havoc with our then-used methodology for off-site marketing efforts to drive buyers to said product directly - that I was forced to write a “Improper Remapping” template for our people to use in creating cases for having the change over-turned.
Now it must be admitted that this former practice became less and less frequent, for us, over the two-plus years that we wielded that template, successfully, in multiple remapping cases, but such occurrences had petered out to nothing by Q2 of 2018 (which was the last time said template was employed); I can’t say with any certainty whether or not our dogged determination to contest unexpected ASIN-remaps had anything to do with that, or if it’s attributable to other factors strictly under Amazon’s control - such as a policy change, etc. - but I can say that Amazon has been known to change ASINs, willy-nilly.
Over the years, I’ve seen a few isolated reports of the automated mechanisms doing the same for a MSKU/SKU, but I don’t recollect any as seemingly-credible as this one appears to be.
My best guess, should this actually be happening, is that the largest clue is likely to be detailed by the remapped SKU’s format: “Amazon.Found.ASIN;” at first blush, such nomenclature might seem akin to an Error 8541 problem - i.e., some Key Attribute of an Offer-Listing having been associated with another one - but I wouldn’t lightly overlook the possibility of the ongoing AWD/IXD tweakings playing a role is such an remapping of a SKU…
4 Likes
To me this would make sense, based on the “Amazon.Found.ASINXXX” part, of Amazon … 1) finding a previously lost item 2) possibly with a different FNSKU, possibly not 3) that Amazon wanted to keep separate from their other inventory.
If so, it actually would be a good idea for tracking purposes.
5 Likes
@ASV_Vites, I know that you’ve mentioned participating in the newest iteration of the FBA Grade and Resell Program (link, SAS), and that you’re adept in deciphering presented data that you can peruse; may I ask if you can confirm that a SKU change, similar to the “Amazon.Found.ASIN” format which is perplexing the OP of the NSFE discussion referenced upthread, can be substantiated from what you’re tracking for the Offer-Listing ASINs for which you’ve opted-in them to this program?
3 Likes
Inventory Ledger report
Scroll baby scroll … all the way down on this page at the very bottom … you will find this …
5 Likes
It’s also found here - Reconcile your shipment - Down below the View the Status messages section/graph under “Why do I see my product being received as merchant SKU “Amazon.Found.Bxxxxxxxxx”?”
ETA: I wonder, and something one might try … “If you create a listing for the Amazon.Found.Bxxxxxxxxx merchant SKU, your inventory for this merchant SKU will be subjected to commingling” … soooooooooo could one just create a new offer with this format and Amazon make it commingled regardless of your settings?
4 Likes
I got this email from Amazon:
Hello,
You’re receiving this notification because we’ve assigned your mislabeled inventory back to your Seller Central account.
When your products are not correctly labeled, we receive them as mislabeled inventory and assign them SKUs that start with “Amazon.Found.”
To make your mislabeled inventory available to customers, where possible, we’ve copied the active offers of your labeled inventory to the mislabeled inventory of the same product that starts with SKU “Amazon.Found.”
However, we’re not always able to copy your listings, including when your existing offers are not active or when the listing requires additional inputs from you.
To review listing status for mislabeled inventory, follow these steps:
- Go to FBA Inventory.
- Search for SKUs that start with “Amazon.Found.” and review the listing status.
- If you have any listings that are not active, go to the Recommended action for the SKU to resolve the stranded inventory and make it available for sale to customers.
If you don’t resolve your stranded inventory, it will be removed from our fulfillment centers based on your auto-removal settings.
Note that your inventory with SKUs starting with “Amazon.Found.” will be subject to virtual tracking. The rest of your labeled inventory is not affected.
The Fulfillment by Amazon team
5 Likes
HA! Me too and for the account I’ve been trying to close since Sept. This only complicates and prolongs things.
Someone tell me how inventory with the FNSKU on the trade dress, that Amazon received without issue somehow became miss labeled???
Did the print blow off the label or melt off in FBA’s 200 degree warehouses?
Super frustrating and par for the course. Let’s see how long this removal order takes to execute since we have removal orders from 9-15 that haven’t completed yet.
4 Likes
We have 2 Stranded ASINs created on 12/08/2024 with the Amazon.Found.
We received the Stranded Inventory email on 12/09/2024.
We received the “mislabeled inventory” email today, 12/10/2024.
I am curious to see what they look like when they are auto-returned to us.
I am nervous having Amazon offer them as FBA without me inspecting them first.
4 Likes