Amazon created new ASINs / FNSKUs for my SKUs
Below are the details in sequential order regarding my issue:
• SKU 1912001 was first created on 24-April-2024 as ASIN / FNSKU B0D31ZV5B4 (see batch ID# 50006019843) .
• We shipped FBA inventory to Amazon on 9-May-2024 under shipment ID# FBA17ZRFHWR2 for SKU 1912001 under ASIN / FNSKU B0D31ZV5B4.
• Then on 30-May-2024 I updated some item attributes per the instructions given me in case IDs# 15327936831, 15334062171, 15354041841, 15354066851, 15360891471, 15360968261, 15360868421, and 15360823571 as well as this forum reply https://sellercentral.amazon.com/seller-forums/discussions/t/f1a08067-b2f9-4b98-9884-0bb2646c5728?postId=a613e06d-9f96-46ae-9665-5966abc3647a using an upload feed (batch ID# 50030019873) which inadvertently created the new ASIN / FNSKU B0D5MSG26D for SKU 1912001, resulting in this issue of two ASIN / FNSKU for a single SKU.
• I deleted this new, incorrect listing for SKU 1912001 under ASIN / FNSKU B0D5MSG26D on 30-May-2024 and relisted using the prior item attributes (batch ID# 50034019873, 50035019873) and the resulting listing used ASIN B0D31ZV5B4 (correct) but FNSKU B0D5MSG26D (incorrect).
• I have been trying to get Amazon to change the FNSKU back to B0D31ZV5B4 for SKU 1912001 but have not had any success. I need this done because this is the FNSKU that contains the inventory for this SKU, as mentioned earlier.
Here are the questions I still have:
Why can you not remap FNSKU B0D31ZV5B4 back to SKU 1912001? This seems like a straightforward solution, doesn't it? Is it because you do not know how? Do you need to escalate this to someone who does know how to do this because I'm sure it can be done? It's probably just outside of your area of expertise.
What will happen to the inventory under ASIN / FNSKU B0D31ZV5B4 for SKU 1912001 that was shipped under shipment ID# FBA17ZRFHWR2? If you do not remap FNSKU B0D31ZV5B4 back to SKU 1912001 won't this cause confusion on the FBA side since they have inventory for SKU 1912001 under FNSKU B0D31ZV5B4.
If we can't remap FNSKU B0D31ZV5B4 back to SKU 1912001, then how do we get the existing inventory under FNSKU B0D31ZV5B4 to reflect under the new FNSKU B0D5MSG26D?
Why did SKU 1912001 relist with the original ASIN B0D31ZV5B4 but the new, incorrect FNSKU B0D5MSG26D but our other two SKUs (1912002 and 1912003) relisted correctly, with the original ASIN and FNSKU?
Can you do a system rollback on our listings back to a date prior to 30-May-2024 when the data was correct?
Amazon created new ASINs / FNSKUs for my SKUs
Below are the details in sequential order regarding my issue:
• SKU 1912001 was first created on 24-April-2024 as ASIN / FNSKU B0D31ZV5B4 (see batch ID# 50006019843) .
• We shipped FBA inventory to Amazon on 9-May-2024 under shipment ID# FBA17ZRFHWR2 for SKU 1912001 under ASIN / FNSKU B0D31ZV5B4.
• Then on 30-May-2024 I updated some item attributes per the instructions given me in case IDs# 15327936831, 15334062171, 15354041841, 15354066851, 15360891471, 15360968261, 15360868421, and 15360823571 as well as this forum reply https://sellercentral.amazon.com/seller-forums/discussions/t/f1a08067-b2f9-4b98-9884-0bb2646c5728?postId=a613e06d-9f96-46ae-9665-5966abc3647a using an upload feed (batch ID# 50030019873) which inadvertently created the new ASIN / FNSKU B0D5MSG26D for SKU 1912001, resulting in this issue of two ASIN / FNSKU for a single SKU.
• I deleted this new, incorrect listing for SKU 1912001 under ASIN / FNSKU B0D5MSG26D on 30-May-2024 and relisted using the prior item attributes (batch ID# 50034019873, 50035019873) and the resulting listing used ASIN B0D31ZV5B4 (correct) but FNSKU B0D5MSG26D (incorrect).
• I have been trying to get Amazon to change the FNSKU back to B0D31ZV5B4 for SKU 1912001 but have not had any success. I need this done because this is the FNSKU that contains the inventory for this SKU, as mentioned earlier.
Here are the questions I still have:
Why can you not remap FNSKU B0D31ZV5B4 back to SKU 1912001? This seems like a straightforward solution, doesn't it? Is it because you do not know how? Do you need to escalate this to someone who does know how to do this because I'm sure it can be done? It's probably just outside of your area of expertise.
What will happen to the inventory under ASIN / FNSKU B0D31ZV5B4 for SKU 1912001 that was shipped under shipment ID# FBA17ZRFHWR2? If you do not remap FNSKU B0D31ZV5B4 back to SKU 1912001 won't this cause confusion on the FBA side since they have inventory for SKU 1912001 under FNSKU B0D31ZV5B4.
If we can't remap FNSKU B0D31ZV5B4 back to SKU 1912001, then how do we get the existing inventory under FNSKU B0D31ZV5B4 to reflect under the new FNSKU B0D5MSG26D?
Why did SKU 1912001 relist with the original ASIN B0D31ZV5B4 but the new, incorrect FNSKU B0D5MSG26D but our other two SKUs (1912002 and 1912003) relisted correctly, with the original ASIN and FNSKU?
Can you do a system rollback on our listings back to a date prior to 30-May-2024 when the data was correct?
0 replies
Cooper_Amazon
Good Morning @Seller_bSx9HFpKbODEi,
I just wanted to reach out to let you know I have escalated the situation shared above regarding FNSKU B0D31ZV5B4 and SKU 1912001 to one of our internal teams to review. They should get back to us within the next few business days. Until then, have a fabulous rest of the week and take care.
Sincerely, Cooper_Amazon
Cooper_Amazon
Good Morning @Seller_bSx9HFpKbODEi,
The team has completed the review of your concerns and let us know that the SKU 1912001 is properly mapped to ASIN B0D31ZV5B4 at this time. Additionally ASIN B0D5MSG26D was not found in your seller inventory at this time, so we are unable to report anything out about that ASIN.
Please let us know if you have any questions regarding the outcome of our investigation and have a lovely rest of the week.
Sincerely, Cooper_Amazon
