Seller Forums
Sign in
Sign in
imgSign in
imgSign in
user profile
Seller_BLAngMAuwHHN1

FBF suffix Shipments in Shipping Queue. Please help us remove them.

Hello,

Our team utilizes SP-API to create shipments to FBA. We've found that from April 12 to April 18, 2024 shipments suffixed with "_FBF" have been created in Seller Central without our direct creation. We have no record of generating these shipments on our end.

We already removed our connections from third-party tools.

This has resulted in us receiving "abandoned shipment" defects. Is this an error on Amazon's end?

Case IDs: 15377074801, 15376982191

Please help us resolve this issue and kindly remove all the FBA IDs with the "FBF" suffix

Thank you for your help.

52 views
7 replies
10
Reply
user profile
Seller_BLAngMAuwHHN1

FBF suffix Shipments in Shipping Queue. Please help us remove them.

Hello,

Our team utilizes SP-API to create shipments to FBA. We've found that from April 12 to April 18, 2024 shipments suffixed with "_FBF" have been created in Seller Central without our direct creation. We have no record of generating these shipments on our end.

We already removed our connections from third-party tools.

This has resulted in us receiving "abandoned shipment" defects. Is this an error on Amazon's end?

Case IDs: 15377074801, 15376982191

Please help us resolve this issue and kindly remove all the FBA IDs with the "FBF" suffix

Thank you for your help.

10
52 views
7 replies
Reply
7 replies
user profile
Seller_z3XfkorVSmnEY

We don't use SP-API to generate shipments, but there was another seller with the same issue -- about 3-4 weeks ago. I'd suggest searching/scrolling through the forums to see if you can find that post and any resolution.

good luck.

11
user profile
Seller_t2tuQuWC2xm0R

We were having the same issue and I know what is causing this. It is caused when you submit shipments through the API and Seller Central spits the shipments. If you create one shipment but not the other/others, the shipment/shipments that you didn't create will populate as _FBF shipments in your shipping queue 72 hours later. It will then show up as the abandoned shipment defect 30 days after the "other half" of that shipment is received by Amazon.

An example being, I submit a large shipment for "Oversize" items every morning using the API. Sometimes there are "Extra Large" items mixed in with the "Oversize" when I submit the shipment. When that is the case Seller Central will come back with two locations (shipments) for the one shipment I submitted. If I only create one of the two shipments the other will populate as the aforementioned _FBF shipment in my shipping queue.

A worse example is if you are not paying the inbound placement fees and dealing with all of those split shipments. If you are only creating shipments that are going to locations you want to ship to/are financially feasible to ship to, and not creating everything you will get buried with these errors.

Hope this helps.

10
user profile
TaylorR_Amazon

Thank you for posting, @Seller_BLAngMAuwHHN1! I will look into this issue.

10
Follow this discussion to be notified of new activity
user profile
Seller_BLAngMAuwHHN1

FBF suffix Shipments in Shipping Queue. Please help us remove them.

Hello,

Our team utilizes SP-API to create shipments to FBA. We've found that from April 12 to April 18, 2024 shipments suffixed with "_FBF" have been created in Seller Central without our direct creation. We have no record of generating these shipments on our end.

We already removed our connections from third-party tools.

This has resulted in us receiving "abandoned shipment" defects. Is this an error on Amazon's end?

Case IDs: 15377074801, 15376982191

Please help us resolve this issue and kindly remove all the FBA IDs with the "FBF" suffix

Thank you for your help.

52 views
7 replies
10
Reply
user profile
Seller_BLAngMAuwHHN1

FBF suffix Shipments in Shipping Queue. Please help us remove them.

Hello,

Our team utilizes SP-API to create shipments to FBA. We've found that from April 12 to April 18, 2024 shipments suffixed with "_FBF" have been created in Seller Central without our direct creation. We have no record of generating these shipments on our end.

We already removed our connections from third-party tools.

This has resulted in us receiving "abandoned shipment" defects. Is this an error on Amazon's end?

Case IDs: 15377074801, 15376982191

Please help us resolve this issue and kindly remove all the FBA IDs with the "FBF" suffix

Thank you for your help.

10
52 views
7 replies
Reply
user profile

FBF suffix Shipments in Shipping Queue. Please help us remove them.

by Seller_BLAngMAuwHHN1

Hello,

Our team utilizes SP-API to create shipments to FBA. We've found that from April 12 to April 18, 2024 shipments suffixed with "_FBF" have been created in Seller Central without our direct creation. We have no record of generating these shipments on our end.

We already removed our connections from third-party tools.

This has resulted in us receiving "abandoned shipment" defects. Is this an error on Amazon's end?

Case IDs: 15377074801, 15376982191

Please help us resolve this issue and kindly remove all the FBA IDs with the "FBF" suffix

Thank you for your help.

Tags:FBA
10
52 views
7 replies
Reply
7 replies
7 replies
Quick filters
Sort by
user profile
Seller_z3XfkorVSmnEY

We don't use SP-API to generate shipments, but there was another seller with the same issue -- about 3-4 weeks ago. I'd suggest searching/scrolling through the forums to see if you can find that post and any resolution.

good luck.

11
user profile
Seller_t2tuQuWC2xm0R

We were having the same issue and I know what is causing this. It is caused when you submit shipments through the API and Seller Central spits the shipments. If you create one shipment but not the other/others, the shipment/shipments that you didn't create will populate as _FBF shipments in your shipping queue 72 hours later. It will then show up as the abandoned shipment defect 30 days after the "other half" of that shipment is received by Amazon.

An example being, I submit a large shipment for "Oversize" items every morning using the API. Sometimes there are "Extra Large" items mixed in with the "Oversize" when I submit the shipment. When that is the case Seller Central will come back with two locations (shipments) for the one shipment I submitted. If I only create one of the two shipments the other will populate as the aforementioned _FBF shipment in my shipping queue.

A worse example is if you are not paying the inbound placement fees and dealing with all of those split shipments. If you are only creating shipments that are going to locations you want to ship to/are financially feasible to ship to, and not creating everything you will get buried with these errors.

Hope this helps.

10
user profile
TaylorR_Amazon

Thank you for posting, @Seller_BLAngMAuwHHN1! I will look into this issue.

10
Follow this discussion to be notified of new activity
user profile
Seller_z3XfkorVSmnEY

We don't use SP-API to generate shipments, but there was another seller with the same issue -- about 3-4 weeks ago. I'd suggest searching/scrolling through the forums to see if you can find that post and any resolution.

good luck.

11
user profile
Seller_z3XfkorVSmnEY

We don't use SP-API to generate shipments, but there was another seller with the same issue -- about 3-4 weeks ago. I'd suggest searching/scrolling through the forums to see if you can find that post and any resolution.

good luck.

11
Reply
user profile
Seller_t2tuQuWC2xm0R

We were having the same issue and I know what is causing this. It is caused when you submit shipments through the API and Seller Central spits the shipments. If you create one shipment but not the other/others, the shipment/shipments that you didn't create will populate as _FBF shipments in your shipping queue 72 hours later. It will then show up as the abandoned shipment defect 30 days after the "other half" of that shipment is received by Amazon.

An example being, I submit a large shipment for "Oversize" items every morning using the API. Sometimes there are "Extra Large" items mixed in with the "Oversize" when I submit the shipment. When that is the case Seller Central will come back with two locations (shipments) for the one shipment I submitted. If I only create one of the two shipments the other will populate as the aforementioned _FBF shipment in my shipping queue.

A worse example is if you are not paying the inbound placement fees and dealing with all of those split shipments. If you are only creating shipments that are going to locations you want to ship to/are financially feasible to ship to, and not creating everything you will get buried with these errors.

Hope this helps.

10
user profile
Seller_t2tuQuWC2xm0R

We were having the same issue and I know what is causing this. It is caused when you submit shipments through the API and Seller Central spits the shipments. If you create one shipment but not the other/others, the shipment/shipments that you didn't create will populate as _FBF shipments in your shipping queue 72 hours later. It will then show up as the abandoned shipment defect 30 days after the "other half" of that shipment is received by Amazon.

An example being, I submit a large shipment for "Oversize" items every morning using the API. Sometimes there are "Extra Large" items mixed in with the "Oversize" when I submit the shipment. When that is the case Seller Central will come back with two locations (shipments) for the one shipment I submitted. If I only create one of the two shipments the other will populate as the aforementioned _FBF shipment in my shipping queue.

A worse example is if you are not paying the inbound placement fees and dealing with all of those split shipments. If you are only creating shipments that are going to locations you want to ship to/are financially feasible to ship to, and not creating everything you will get buried with these errors.

Hope this helps.

10
Reply
user profile
TaylorR_Amazon

Thank you for posting, @Seller_BLAngMAuwHHN1! I will look into this issue.

10
user profile
TaylorR_Amazon

Thank you for posting, @Seller_BLAngMAuwHHN1! I will look into this issue.

10
Reply
Follow this discussion to be notified of new activity