Starting a new thread here to see if we can finally get some help with this issue.
Error "This product must be removed from the shipment because there are currently no fulfillment centers in the destination country capable of receiving the product." is received for 17 out of 76 SKUs in STA workflow wf904c8497-ed8c-4d0d-86f7-fc3f088c7758.
Items are simple color variants of SKUs that are able to be sent in without error. Error SKUs are brand new to Amazon, UPCs are new to Amazon. Not hazmat. Plenty of warehouse capacity on my end.
Multiple cases have been created with seller support to no avail. It's been suggested by Seller Support that I "convert to Manufacturer's Barcode" (the SKUs are already MBC!). "Enroll in GSS" (irrelevant to this issue as we ship from our US warehouse to US FBA warehouses!).
@Seller_AomAH9L10QgVb stated on another forum post that he was informed that this is a back end issue. I truly believe this is the case. I have thoroughly inspected all attributes of my error SKUs and the only possibility here is that product type has been changed in Amazon's backend (totebag to handbag) as evident in a recent Category Listings Report. I need a knowledgeable seller support team to assist here and inspect from the backend rather than throw out templated, irrelevant solutions.
This is a problem for many sellers, including but not limited to @Seller_XknM2neeprIUf @Seller_n5l349c4ltMie @Seller_3AGQB6weiRihw @Seller_BTDwdwB62QL1v @Seller_bjgtX4Lwxw8Dz @Seller_4qkDNEtr9M8A5 @Seller_AomAH9L10QgVb @Seller_SQma86pxB0R4M @Seller_v16x17sNxDtky @Seller_AomAH9L10QgVb @Seller_AqH21oHaSxElD @Seller_T9rAVUeY6RUaN @Seller_bjgtX4Lwxw8Dz @Seller_8y6DLc369B80e @Seller_uQaocYXBBNJQR @Seller_zEC0XcGfbZCSB
AMAZON...please assist. I urge your internal teams to see if there is in fact an internal error triggering these errors in STA workflow. I'm sitting on an entire spring launch to send in to FBA.
Many thanks.
same issues here , looking forward to get this fix. weird case
Yes this is still ongoing for us. After over a week, more than 15 reps have touched my case and offered tons of "answers" that were just plain wrong, and my case was closed yet again today with a lengthy response instructing me on how to create an FBA shipment. I've been creating FBA shipments for over 10 years! Worthless, frustrating, and insulting. I may reopen it and try again in a day or 2, but right now that feels like punching myself in the face.
BTW, my problematic SKUs are NOT new. I have been successfully sending them to FBA for years until this started happening around 2 weeks ago. I made no changes to these SKUs on my end.
Case ID 14817618241.
Hi @Seller_WesbTv28yW9q5,
Dominic from Amazon here, I am working with our internal team to investigate this issue, resolve it and provide the guidance to Sellers. I have acknowledged that in this thread as well. I am working on this as quick as I can to try to get a resolution. I understand the frustration with this and not being able to send in inventory we are moving as quick as we can.
Best,
Dominic
Same problem with my ASINS. I think its mostly eyewear ASINs are effected.
its pretty much all new ASINs and some old ASINs.
i am having the same issues 4 shipments today. I few went through but then it stopped. Hope they find a solution soon. 9 days over memorial weekend 2023 we could not send a single shipment. Its a shame. I hope they can fix this soon. Please help
SUCCESS. After multiple back and forth with Seller Support this weekend, I received a response stating that the issue was temporary and that I should now be able to create a STA workflow without errors.
It's true...error-free workflow has been created early this morning and we're shipping ASAP!
@Dominic_AmazonI would be interested in knowing if this was a back-end issue.
We were getting this error on 3/1, for products that Amazon said we needed to emergency replenish…
I have the same error. Do you have any suggestions on how to solve this? i must send inventory ASAP
I finally was able to resolve this. The issue is with the product category. This is the response from the support (which I was able to get after tons of correspondence with them). And it really worked:
This is XXXX with the Amazon Selling Partner Support Leadership team.
I understand that your concern is in regards to creating a shipment for units of XXXXXXXX and the impact that this has on your account.
After investigating, I determined that incorrect attribute data for XXXXXXX is preventing it from being sent in to a Fulfillment Center on a shipment.
I saw that the product type was set to shoes when this item should be classified as apparel. More information about the product type attribute can be seen here https://sellercentral.amazon.com/help/hub/reference/GYV2F6WS9N9FDYD9
I made an update to set the product type to be Apparel. Please allow 24 hours for this change to be applied to your ASIN. Then, please create a new Send to Amazon shipment workflow to create a shipment for your item.
And again here it comes.. Same issue after it has been fixed just couple of weeks ago. Please help!!!!
Workflow ID: wf5d11d313-f23b-4497-9dc3-a0db7c72f87d
Starting a new thread here to see if we can finally get some help with this issue.
Error "This product must be removed from the shipment because there are currently no fulfillment centers in the destination country capable of receiving the product." is received for 17 out of 76 SKUs in STA workflow wf904c8497-ed8c-4d0d-86f7-fc3f088c7758.
Items are simple color variants of SKUs that are able to be sent in without error. Error SKUs are brand new to Amazon, UPCs are new to Amazon. Not hazmat. Plenty of warehouse capacity on my end.
Multiple cases have been created with seller support to no avail. It's been suggested by Seller Support that I "convert to Manufacturer's Barcode" (the SKUs are already MBC!). "Enroll in GSS" (irrelevant to this issue as we ship from our US warehouse to US FBA warehouses!).
@Seller_AomAH9L10QgVb stated on another forum post that he was informed that this is a back end issue. I truly believe this is the case. I have thoroughly inspected all attributes of my error SKUs and the only possibility here is that product type has been changed in Amazon's backend (totebag to handbag) as evident in a recent Category Listings Report. I need a knowledgeable seller support team to assist here and inspect from the backend rather than throw out templated, irrelevant solutions.
This is a problem for many sellers, including but not limited to @Seller_XknM2neeprIUf @Seller_n5l349c4ltMie @Seller_3AGQB6weiRihw @Seller_BTDwdwB62QL1v @Seller_bjgtX4Lwxw8Dz @Seller_4qkDNEtr9M8A5 @Seller_AomAH9L10QgVb @Seller_SQma86pxB0R4M @Seller_v16x17sNxDtky @Seller_AomAH9L10QgVb @Seller_AqH21oHaSxElD @Seller_T9rAVUeY6RUaN @Seller_bjgtX4Lwxw8Dz @Seller_8y6DLc369B80e @Seller_uQaocYXBBNJQR @Seller_zEC0XcGfbZCSB
AMAZON...please assist. I urge your internal teams to see if there is in fact an internal error triggering these errors in STA workflow. I'm sitting on an entire spring launch to send in to FBA.
Many thanks.
Starting a new thread here to see if we can finally get some help with this issue.
Error "This product must be removed from the shipment because there are currently no fulfillment centers in the destination country capable of receiving the product." is received for 17 out of 76 SKUs in STA workflow wf904c8497-ed8c-4d0d-86f7-fc3f088c7758.
Items are simple color variants of SKUs that are able to be sent in without error. Error SKUs are brand new to Amazon, UPCs are new to Amazon. Not hazmat. Plenty of warehouse capacity on my end.
Multiple cases have been created with seller support to no avail. It's been suggested by Seller Support that I "convert to Manufacturer's Barcode" (the SKUs are already MBC!). "Enroll in GSS" (irrelevant to this issue as we ship from our US warehouse to US FBA warehouses!).
@Seller_AomAH9L10QgVb stated on another forum post that he was informed that this is a back end issue. I truly believe this is the case. I have thoroughly inspected all attributes of my error SKUs and the only possibility here is that product type has been changed in Amazon's backend (totebag to handbag) as evident in a recent Category Listings Report. I need a knowledgeable seller support team to assist here and inspect from the backend rather than throw out templated, irrelevant solutions.
This is a problem for many sellers, including but not limited to @Seller_XknM2neeprIUf @Seller_n5l349c4ltMie @Seller_3AGQB6weiRihw @Seller_BTDwdwB62QL1v @Seller_bjgtX4Lwxw8Dz @Seller_4qkDNEtr9M8A5 @Seller_AomAH9L10QgVb @Seller_SQma86pxB0R4M @Seller_v16x17sNxDtky @Seller_AomAH9L10QgVb @Seller_AqH21oHaSxElD @Seller_T9rAVUeY6RUaN @Seller_bjgtX4Lwxw8Dz @Seller_8y6DLc369B80e @Seller_uQaocYXBBNJQR @Seller_zEC0XcGfbZCSB
AMAZON...please assist. I urge your internal teams to see if there is in fact an internal error triggering these errors in STA workflow. I'm sitting on an entire spring launch to send in to FBA.
Many thanks.
same issues here , looking forward to get this fix. weird case
Yes this is still ongoing for us. After over a week, more than 15 reps have touched my case and offered tons of "answers" that were just plain wrong, and my case was closed yet again today with a lengthy response instructing me on how to create an FBA shipment. I've been creating FBA shipments for over 10 years! Worthless, frustrating, and insulting. I may reopen it and try again in a day or 2, but right now that feels like punching myself in the face.
BTW, my problematic SKUs are NOT new. I have been successfully sending them to FBA for years until this started happening around 2 weeks ago. I made no changes to these SKUs on my end.
Case ID 14817618241.
Hi @Seller_WesbTv28yW9q5,
Dominic from Amazon here, I am working with our internal team to investigate this issue, resolve it and provide the guidance to Sellers. I have acknowledged that in this thread as well. I am working on this as quick as I can to try to get a resolution. I understand the frustration with this and not being able to send in inventory we are moving as quick as we can.
Best,
Dominic
Same problem with my ASINS. I think its mostly eyewear ASINs are effected.
its pretty much all new ASINs and some old ASINs.
i am having the same issues 4 shipments today. I few went through but then it stopped. Hope they find a solution soon. 9 days over memorial weekend 2023 we could not send a single shipment. Its a shame. I hope they can fix this soon. Please help
SUCCESS. After multiple back and forth with Seller Support this weekend, I received a response stating that the issue was temporary and that I should now be able to create a STA workflow without errors.
It's true...error-free workflow has been created early this morning and we're shipping ASAP!
@Dominic_AmazonI would be interested in knowing if this was a back-end issue.
We were getting this error on 3/1, for products that Amazon said we needed to emergency replenish…
I have the same error. Do you have any suggestions on how to solve this? i must send inventory ASAP
I finally was able to resolve this. The issue is with the product category. This is the response from the support (which I was able to get after tons of correspondence with them). And it really worked:
This is XXXX with the Amazon Selling Partner Support Leadership team.
I understand that your concern is in regards to creating a shipment for units of XXXXXXXX and the impact that this has on your account.
After investigating, I determined that incorrect attribute data for XXXXXXX is preventing it from being sent in to a Fulfillment Center on a shipment.
I saw that the product type was set to shoes when this item should be classified as apparel. More information about the product type attribute can be seen here https://sellercentral.amazon.com/help/hub/reference/GYV2F6WS9N9FDYD9
I made an update to set the product type to be Apparel. Please allow 24 hours for this change to be applied to your ASIN. Then, please create a new Send to Amazon shipment workflow to create a shipment for your item.
And again here it comes.. Same issue after it has been fixed just couple of weeks ago. Please help!!!!
Workflow ID: wf5d11d313-f23b-4497-9dc3-a0db7c72f87d
same issues here , looking forward to get this fix. weird case
same issues here , looking forward to get this fix. weird case
Yes this is still ongoing for us. After over a week, more than 15 reps have touched my case and offered tons of "answers" that were just plain wrong, and my case was closed yet again today with a lengthy response instructing me on how to create an FBA shipment. I've been creating FBA shipments for over 10 years! Worthless, frustrating, and insulting. I may reopen it and try again in a day or 2, but right now that feels like punching myself in the face.
BTW, my problematic SKUs are NOT new. I have been successfully sending them to FBA for years until this started happening around 2 weeks ago. I made no changes to these SKUs on my end.
Case ID 14817618241.
Yes this is still ongoing for us. After over a week, more than 15 reps have touched my case and offered tons of "answers" that were just plain wrong, and my case was closed yet again today with a lengthy response instructing me on how to create an FBA shipment. I've been creating FBA shipments for over 10 years! Worthless, frustrating, and insulting. I may reopen it and try again in a day or 2, but right now that feels like punching myself in the face.
BTW, my problematic SKUs are NOT new. I have been successfully sending them to FBA for years until this started happening around 2 weeks ago. I made no changes to these SKUs on my end.
Case ID 14817618241.
Hi @Seller_WesbTv28yW9q5,
Dominic from Amazon here, I am working with our internal team to investigate this issue, resolve it and provide the guidance to Sellers. I have acknowledged that in this thread as well. I am working on this as quick as I can to try to get a resolution. I understand the frustration with this and not being able to send in inventory we are moving as quick as we can.
Best,
Dominic
Hi @Seller_WesbTv28yW9q5,
Dominic from Amazon here, I am working with our internal team to investigate this issue, resolve it and provide the guidance to Sellers. I have acknowledged that in this thread as well. I am working on this as quick as I can to try to get a resolution. I understand the frustration with this and not being able to send in inventory we are moving as quick as we can.
Best,
Dominic
Same problem with my ASINS. I think its mostly eyewear ASINs are effected.
its pretty much all new ASINs and some old ASINs.
Same problem with my ASINS. I think its mostly eyewear ASINs are effected.
its pretty much all new ASINs and some old ASINs.
i am having the same issues 4 shipments today. I few went through but then it stopped. Hope they find a solution soon. 9 days over memorial weekend 2023 we could not send a single shipment. Its a shame. I hope they can fix this soon. Please help
i am having the same issues 4 shipments today. I few went through but then it stopped. Hope they find a solution soon. 9 days over memorial weekend 2023 we could not send a single shipment. Its a shame. I hope they can fix this soon. Please help
SUCCESS. After multiple back and forth with Seller Support this weekend, I received a response stating that the issue was temporary and that I should now be able to create a STA workflow without errors.
It's true...error-free workflow has been created early this morning and we're shipping ASAP!
@Dominic_AmazonI would be interested in knowing if this was a back-end issue.
SUCCESS. After multiple back and forth with Seller Support this weekend, I received a response stating that the issue was temporary and that I should now be able to create a STA workflow without errors.
It's true...error-free workflow has been created early this morning and we're shipping ASAP!
@Dominic_AmazonI would be interested in knowing if this was a back-end issue.
We were getting this error on 3/1, for products that Amazon said we needed to emergency replenish…
We were getting this error on 3/1, for products that Amazon said we needed to emergency replenish…
I have the same error. Do you have any suggestions on how to solve this? i must send inventory ASAP
I have the same error. Do you have any suggestions on how to solve this? i must send inventory ASAP
I finally was able to resolve this. The issue is with the product category. This is the response from the support (which I was able to get after tons of correspondence with them). And it really worked:
This is XXXX with the Amazon Selling Partner Support Leadership team.
I understand that your concern is in regards to creating a shipment for units of XXXXXXXX and the impact that this has on your account.
After investigating, I determined that incorrect attribute data for XXXXXXX is preventing it from being sent in to a Fulfillment Center on a shipment.
I saw that the product type was set to shoes when this item should be classified as apparel. More information about the product type attribute can be seen here https://sellercentral.amazon.com/help/hub/reference/GYV2F6WS9N9FDYD9
I made an update to set the product type to be Apparel. Please allow 24 hours for this change to be applied to your ASIN. Then, please create a new Send to Amazon shipment workflow to create a shipment for your item.
I finally was able to resolve this. The issue is with the product category. This is the response from the support (which I was able to get after tons of correspondence with them). And it really worked:
This is XXXX with the Amazon Selling Partner Support Leadership team.
I understand that your concern is in regards to creating a shipment for units of XXXXXXXX and the impact that this has on your account.
After investigating, I determined that incorrect attribute data for XXXXXXX is preventing it from being sent in to a Fulfillment Center on a shipment.
I saw that the product type was set to shoes when this item should be classified as apparel. More information about the product type attribute can be seen here https://sellercentral.amazon.com/help/hub/reference/GYV2F6WS9N9FDYD9
I made an update to set the product type to be Apparel. Please allow 24 hours for this change to be applied to your ASIN. Then, please create a new Send to Amazon shipment workflow to create a shipment for your item.
And again here it comes.. Same issue after it has been fixed just couple of weeks ago. Please help!!!!
Workflow ID: wf5d11d313-f23b-4497-9dc3-a0db7c72f87d
And again here it comes.. Same issue after it has been fixed just couple of weeks ago. Please help!!!!
Workflow ID: wf5d11d313-f23b-4497-9dc3-a0db7c72f87d