Seller Forums
user profile
Seller_nsTqZobQWJSCX

Amazon.Found Asins

Why is Amazon creating “Amazon.Found” ASINs for almost all our ASINs, making it insanely complicated to keep an overview of our stock?

Is there a way to turn this off?

186 views
9 replies
Tags:ASIN, Listings, SKU
10
Reply
user profile
Seller_nsTqZobQWJSCX

Amazon.Found Asins

Why is Amazon creating “Amazon.Found” ASINs for almost all our ASINs, making it insanely complicated to keep an overview of our stock?

Is there a way to turn this off?

Tags:ASIN, Listings, SKU
10
186 views
9 replies
Reply
9 replies
user profile
Seller_NbYSGJ8Tehgbv

user profile
Seller_nsTqZobQWJSCX

Why is Amazon creating “Amazon.Found” ASINs for almost all our ASINs, making it insanely complicated to keep an overview of our stock?

View post

Items that were missing from your shipments were, eventually, found by Amazon's warehousing staff. They could not tie it to your specific SKU on the ASIN so they created their own.

user profile
Seller_nsTqZobQWJSCX

Is there a way to turn this off?

View post

Unfortunately, there is no way to turn this off.

10
user profile
Seller_xo4Akj7FBBnfC

We’re seeing the same issue, and it’s generating bogus data in our inventory reports that must now be manually verified and overridden — creating unnecessary work and increasing the risk of errors in both planning and stock levels.

The warehouses clearly seem to know which SKUs are being renamed — each renamed SKU (“Amazon.Found.ASIN”) has the ASIN pulled from the original.

Our inventory system uses data from several reports, including the Date Range Transaction Report, which lists only manufacturer SKUs (no ASINs). That field is now corrupted, breaking the link between transactions and product identifiers.

Another poorly conceived change that creates risk and wastes sellers’ time.

I'd be interested to know how other sellers are dealing with this.

30
user profile
Seller_Xm9ZXdbDd6NZw

I'm glad they are finding them. But it's really weird seeing as how I make my own products and am the only seller that they can't put it with the other inventory. Yet they tie it to the same listing, so they know what product it is...

Oh well, guess it's better than them relabeling my barcode to a different sku as they did once.

10
user profile
Seller_LMU08yXnnE5ph

We used to see very sporadic cases of these SKUs being created for our products as well, and two weeks ago started seeing an insane amount of SKUs and QTY available for these. I'm trying to understand why is this happening, so if anyone knows the reason I'd be very interested to know.

20
user profile
KJ_Amazon

Hello @Seller_LMU08yXnnE5ph @Seller_nsTqZobQWJSCX @Seller_Xm9ZXdbDd6NZw and other sellers asking questions about replacement inventory.

"Amazon.Found" in the SKU indicates that this is inventory that was previously mislabeled and has now been assigned back to the seller.

As this inventory had labeling issues during the receive, we cannot receive this inventory as labeled inventory in our network and we are unable to merge these listings.

For the "Amazon.Found" SKUs, you can offer the inventory under this listing alongside your existing listing or you can place a removal order."

You can read more about this designation here: Seller Help: Reversed Reimbursement

Please check back if you have questions or comments for our partner teams.

img

02
Follow this discussion to be notified of new activity
user profile
Seller_nsTqZobQWJSCX

Amazon.Found Asins

Why is Amazon creating “Amazon.Found” ASINs for almost all our ASINs, making it insanely complicated to keep an overview of our stock?

Is there a way to turn this off?

186 views
9 replies
Tags:ASIN, Listings, SKU
10
Reply
user profile
Seller_nsTqZobQWJSCX

Amazon.Found Asins

Why is Amazon creating “Amazon.Found” ASINs for almost all our ASINs, making it insanely complicated to keep an overview of our stock?

Is there a way to turn this off?

Tags:ASIN, Listings, SKU
10
186 views
9 replies
Reply
user profile

Amazon.Found Asins

by Seller_nsTqZobQWJSCX

Why is Amazon creating “Amazon.Found” ASINs for almost all our ASINs, making it insanely complicated to keep an overview of our stock?

Is there a way to turn this off?

Tags:ASIN, Listings, SKU
10
186 views
9 replies
Reply
9 replies
9 replies
Quick filters
Sort by
user profile
Seller_NbYSGJ8Tehgbv

user profile
Seller_nsTqZobQWJSCX

Why is Amazon creating “Amazon.Found” ASINs for almost all our ASINs, making it insanely complicated to keep an overview of our stock?

View post

Items that were missing from your shipments were, eventually, found by Amazon's warehousing staff. They could not tie it to your specific SKU on the ASIN so they created their own.

user profile
Seller_nsTqZobQWJSCX

Is there a way to turn this off?

View post

Unfortunately, there is no way to turn this off.

10
user profile
Seller_xo4Akj7FBBnfC

We’re seeing the same issue, and it’s generating bogus data in our inventory reports that must now be manually verified and overridden — creating unnecessary work and increasing the risk of errors in both planning and stock levels.

The warehouses clearly seem to know which SKUs are being renamed — each renamed SKU (“Amazon.Found.ASIN”) has the ASIN pulled from the original.

Our inventory system uses data from several reports, including the Date Range Transaction Report, which lists only manufacturer SKUs (no ASINs). That field is now corrupted, breaking the link between transactions and product identifiers.

Another poorly conceived change that creates risk and wastes sellers’ time.

I'd be interested to know how other sellers are dealing with this.

30
user profile
Seller_Xm9ZXdbDd6NZw

I'm glad they are finding them. But it's really weird seeing as how I make my own products and am the only seller that they can't put it with the other inventory. Yet they tie it to the same listing, so they know what product it is...

Oh well, guess it's better than them relabeling my barcode to a different sku as they did once.

10
user profile
Seller_LMU08yXnnE5ph

We used to see very sporadic cases of these SKUs being created for our products as well, and two weeks ago started seeing an insane amount of SKUs and QTY available for these. I'm trying to understand why is this happening, so if anyone knows the reason I'd be very interested to know.

20
user profile
KJ_Amazon

Hello @Seller_LMU08yXnnE5ph @Seller_nsTqZobQWJSCX @Seller_Xm9ZXdbDd6NZw and other sellers asking questions about replacement inventory.

"Amazon.Found" in the SKU indicates that this is inventory that was previously mislabeled and has now been assigned back to the seller.

As this inventory had labeling issues during the receive, we cannot receive this inventory as labeled inventory in our network and we are unable to merge these listings.

For the "Amazon.Found" SKUs, you can offer the inventory under this listing alongside your existing listing or you can place a removal order."

You can read more about this designation here: Seller Help: Reversed Reimbursement

Please check back if you have questions or comments for our partner teams.

img

02
Follow this discussion to be notified of new activity
user profile
Seller_NbYSGJ8Tehgbv

user profile
Seller_nsTqZobQWJSCX

Why is Amazon creating “Amazon.Found” ASINs for almost all our ASINs, making it insanely complicated to keep an overview of our stock?

View post

Items that were missing from your shipments were, eventually, found by Amazon's warehousing staff. They could not tie it to your specific SKU on the ASIN so they created their own.

user profile
Seller_nsTqZobQWJSCX

Is there a way to turn this off?

View post

Unfortunately, there is no way to turn this off.

10
user profile
Seller_NbYSGJ8Tehgbv

user profile
Seller_nsTqZobQWJSCX

Why is Amazon creating “Amazon.Found” ASINs for almost all our ASINs, making it insanely complicated to keep an overview of our stock?

View post

Items that were missing from your shipments were, eventually, found by Amazon's warehousing staff. They could not tie it to your specific SKU on the ASIN so they created their own.

user profile
Seller_nsTqZobQWJSCX

Is there a way to turn this off?

View post

Unfortunately, there is no way to turn this off.

10
Reply
user profile
Seller_xo4Akj7FBBnfC

We’re seeing the same issue, and it’s generating bogus data in our inventory reports that must now be manually verified and overridden — creating unnecessary work and increasing the risk of errors in both planning and stock levels.

The warehouses clearly seem to know which SKUs are being renamed — each renamed SKU (“Amazon.Found.ASIN”) has the ASIN pulled from the original.

Our inventory system uses data from several reports, including the Date Range Transaction Report, which lists only manufacturer SKUs (no ASINs). That field is now corrupted, breaking the link between transactions and product identifiers.

Another poorly conceived change that creates risk and wastes sellers’ time.

I'd be interested to know how other sellers are dealing with this.

30
user profile
Seller_xo4Akj7FBBnfC

We’re seeing the same issue, and it’s generating bogus data in our inventory reports that must now be manually verified and overridden — creating unnecessary work and increasing the risk of errors in both planning and stock levels.

The warehouses clearly seem to know which SKUs are being renamed — each renamed SKU (“Amazon.Found.ASIN”) has the ASIN pulled from the original.

Our inventory system uses data from several reports, including the Date Range Transaction Report, which lists only manufacturer SKUs (no ASINs). That field is now corrupted, breaking the link between transactions and product identifiers.

Another poorly conceived change that creates risk and wastes sellers’ time.

I'd be interested to know how other sellers are dealing with this.

30
Reply
user profile
Seller_Xm9ZXdbDd6NZw

I'm glad they are finding them. But it's really weird seeing as how I make my own products and am the only seller that they can't put it with the other inventory. Yet they tie it to the same listing, so they know what product it is...

Oh well, guess it's better than them relabeling my barcode to a different sku as they did once.

10
user profile
Seller_Xm9ZXdbDd6NZw

I'm glad they are finding them. But it's really weird seeing as how I make my own products and am the only seller that they can't put it with the other inventory. Yet they tie it to the same listing, so they know what product it is...

Oh well, guess it's better than them relabeling my barcode to a different sku as they did once.

10
Reply
user profile
Seller_LMU08yXnnE5ph

We used to see very sporadic cases of these SKUs being created for our products as well, and two weeks ago started seeing an insane amount of SKUs and QTY available for these. I'm trying to understand why is this happening, so if anyone knows the reason I'd be very interested to know.

20
user profile
Seller_LMU08yXnnE5ph

We used to see very sporadic cases of these SKUs being created for our products as well, and two weeks ago started seeing an insane amount of SKUs and QTY available for these. I'm trying to understand why is this happening, so if anyone knows the reason I'd be very interested to know.

20
Reply
user profile
KJ_Amazon

Hello @Seller_LMU08yXnnE5ph @Seller_nsTqZobQWJSCX @Seller_Xm9ZXdbDd6NZw and other sellers asking questions about replacement inventory.

"Amazon.Found" in the SKU indicates that this is inventory that was previously mislabeled and has now been assigned back to the seller.

As this inventory had labeling issues during the receive, we cannot receive this inventory as labeled inventory in our network and we are unable to merge these listings.

For the "Amazon.Found" SKUs, you can offer the inventory under this listing alongside your existing listing or you can place a removal order."

You can read more about this designation here: Seller Help: Reversed Reimbursement

Please check back if you have questions or comments for our partner teams.

img

02
user profile
KJ_Amazon

Hello @Seller_LMU08yXnnE5ph @Seller_nsTqZobQWJSCX @Seller_Xm9ZXdbDd6NZw and other sellers asking questions about replacement inventory.

"Amazon.Found" in the SKU indicates that this is inventory that was previously mislabeled and has now been assigned back to the seller.

As this inventory had labeling issues during the receive, we cannot receive this inventory as labeled inventory in our network and we are unable to merge these listings.

For the "Amazon.Found" SKUs, you can offer the inventory under this listing alongside your existing listing or you can place a removal order."

You can read more about this designation here: Seller Help: Reversed Reimbursement

Please check back if you have questions or comments for our partner teams.

img

02
Reply
Follow this discussion to be notified of new activity