Listing removed due to product type mismatch, plus FBA listings became stranded after variation update (Case ID: 12923193932)
Hello everyone,
I would appreciate any advice from experienced sellers or Amazon moderators regarding a catalog issue that I have been trying to resolve.
Case ID: 12923193932
Issue 1 (Current Support Case)
I have a variation family with four child ASINs.
One child listing (ASIN 4) was removed from my inventory after it was detached from the parent variation. While working with Catalog Support, an Amazon representative investigated the backend and informed me that the product type for this child ASIN had somehow changed to INCENSE, while the parent and all other child ASINs use TOOTH_WHITENER.
The representative confirmed this mismatch was the reason the listing was removed and submitted a backend request to correct the product type to match the parent. I was advised that the correction would take 24–48 hours.
However, more than 48 hours have now passed and the listing is still removed.
Support also advised me to recreate the offer using the same SKU, but Seller Central returns the error:
"SKU entered is already being used in your catalog."
Therefore, I cannot recreate the listing using the existing SKU, even though Support instructed me to do so.
Issue 2 (Separate issue)
This issue is not part of the current support case.
Around the same time, my other three child ASINs (ASIN 1, ASIN 2 and ASIN 3) unexpectedly changed from FBA to Merchant Fulfilled and became inactive.
The FBA inventory still exists in Amazon fulfillment centers (available inventory is visible in Inventory Health), but the listings became stranded due to the fulfillment channel changing.
I had experienced this exact situation before, so instead of opening another case, I uploaded an Update Price & Quantity file with the fulfillment channel set to amazon (FBA) and left the quantity blank, exactly as Amazon's documentation instructs.
The upload completed successfully with 0 errors, but after more than 48 hours, the listings are still inactive and the inventory remains stranded.
Has anyone experienced either of these backend catalog issues?
If an Amazon moderator is able to review Case ID 12923193932, I would greatly appreciate it if the case could be reviewed or escalated to the appropriate Catalog/Technical team, as this appears to be a backend catalog and SKU mapping issue rather than a seller-side error.
Thank you in advance for any guidance.
@Seller_CW0P5hgbsiqWX@Sandy_Amazon
Listing removed due to product type mismatch, plus FBA listings became stranded after variation update (Case ID: 12923193932)
Hello everyone,
I would appreciate any advice from experienced sellers or Amazon moderators regarding a catalog issue that I have been trying to resolve.
Case ID: 12923193932
Issue 1 (Current Support Case)
I have a variation family with four child ASINs.
One child listing (ASIN 4) was removed from my inventory after it was detached from the parent variation. While working with Catalog Support, an Amazon representative investigated the backend and informed me that the product type for this child ASIN had somehow changed to INCENSE, while the parent and all other child ASINs use TOOTH_WHITENER.
The representative confirmed this mismatch was the reason the listing was removed and submitted a backend request to correct the product type to match the parent. I was advised that the correction would take 24–48 hours.
However, more than 48 hours have now passed and the listing is still removed.
Support also advised me to recreate the offer using the same SKU, but Seller Central returns the error:
"SKU entered is already being used in your catalog."
Therefore, I cannot recreate the listing using the existing SKU, even though Support instructed me to do so.
Issue 2 (Separate issue)
This issue is not part of the current support case.
Around the same time, my other three child ASINs (ASIN 1, ASIN 2 and ASIN 3) unexpectedly changed from FBA to Merchant Fulfilled and became inactive.
The FBA inventory still exists in Amazon fulfillment centers (available inventory is visible in Inventory Health), but the listings became stranded due to the fulfillment channel changing.
I had experienced this exact situation before, so instead of opening another case, I uploaded an Update Price & Quantity file with the fulfillment channel set to amazon (FBA) and left the quantity blank, exactly as Amazon's documentation instructs.
The upload completed successfully with 0 errors, but after more than 48 hours, the listings are still inactive and the inventory remains stranded.
Has anyone experienced either of these backend catalog issues?
If an Amazon moderator is able to review Case ID 12923193932, I would greatly appreciate it if the case could be reviewed or escalated to the appropriate Catalog/Technical team, as this appears to be a backend catalog and SKU mapping issue rather than a seller-side error.
Thank you in advance for any guidance.
@Seller_CW0P5hgbsiqWX@Sandy_Amazon