NEW FBA API - Inbound New Workflow - "Box Name" (Seller Central) + new API and how to match labels to boxes??
We are trying to move to the new API which has a December 20th deadline and are running into huge logistical issues.
With old API we used 2D barcodes + Amazon Partnered Carrier. We asked Qty for splits up front then created shipments. This worked fine.
With the new API we found we CANNOT use 2D barcodes OR APC when we have not pre-packed boxes. This was issue #1 -- so we are rebuilding our systems to pack boxes up front.
We have now hit a new snag regarding matching boxes (with specific contents) up with UPS labels -- we have done testing on Seller Central and have questions re: API as well.
SELLER CENTRAL
(A) It seems that if you enter a custom box name, the shipment creation fails at the "ACCEPT CHARGES" stage -- it seems that when it goes to create the labels, the workflow fails if you have changed the box naming format from P# - B# -- this is a huge issue, as our internal box ID structure is different and we may have many different shipments in process at a time. ** IS IT CORRECT YOU CANNOT ENTER YOUR OWN BOX NAME / BOX ID HERE AND MUST USE P# - B# FORMAT? **
(B) It seems the boxes come out in "BOX NAME" Alpbabetical order -- we can work around this by setting a custom box name for example ### - Name so that the boxes "sort" in the order we want, but (A) seems to indicate we cannot set our own custom name.
API ISSUES
We are looking in the API for a way to set a box name -- but do not see any information on this -- can we not set a box name for the labels through the API??
These are huge issues -- we have a giant pack room with multiple shipments in process at a time. Our boxes are in a particular order on the line -- how are we suppose to match up packed boxes to specific labels if we can't set a custom box ID/name? This could take us HOURS to send shipments even if we only work on one shipment at a time as we process so many SKUs in a shipment.
And if the only solution is to process one product at a time (per shipment) our shipping costs will skyrocket due to small # of boxes.
How is anyone handling this??
NEW FBA API - Inbound New Workflow - "Box Name" (Seller Central) + new API and how to match labels to boxes??
We are trying to move to the new API which has a December 20th deadline and are running into huge logistical issues.
With old API we used 2D barcodes + Amazon Partnered Carrier. We asked Qty for splits up front then created shipments. This worked fine.
With the new API we found we CANNOT use 2D barcodes OR APC when we have not pre-packed boxes. This was issue #1 -- so we are rebuilding our systems to pack boxes up front.
We have now hit a new snag regarding matching boxes (with specific contents) up with UPS labels -- we have done testing on Seller Central and have questions re: API as well.
SELLER CENTRAL
(A) It seems that if you enter a custom box name, the shipment creation fails at the "ACCEPT CHARGES" stage -- it seems that when it goes to create the labels, the workflow fails if you have changed the box naming format from P# - B# -- this is a huge issue, as our internal box ID structure is different and we may have many different shipments in process at a time. ** IS IT CORRECT YOU CANNOT ENTER YOUR OWN BOX NAME / BOX ID HERE AND MUST USE P# - B# FORMAT? **
(B) It seems the boxes come out in "BOX NAME" Alpbabetical order -- we can work around this by setting a custom box name for example ### - Name so that the boxes "sort" in the order we want, but (A) seems to indicate we cannot set our own custom name.
API ISSUES
We are looking in the API for a way to set a box name -- but do not see any information on this -- can we not set a box name for the labels through the API??
These are huge issues -- we have a giant pack room with multiple shipments in process at a time. Our boxes are in a particular order on the line -- how are we suppose to match up packed boxes to specific labels if we can't set a custom box ID/name? This could take us HOURS to send shipments even if we only work on one shipment at a time as we process so many SKUs in a shipment.
And if the only solution is to process one product at a time (per shipment) our shipping costs will skyrocket due to small # of boxes.
How is anyone handling this??
4 replies
Seller_TTG0TX5GOhqmW
*BUMP*
Have a thread going on GitHub too -- very little response or traction on this issue. Seamods please take note
GitHub forums "selling-parter-api-models" Post #4365
** NOTE: This GitHub forum is where we are told to go, but we cannot link to it from the Amazon forums (we get an error for posting non-Amazon URLS)
KJ_Amazon
Hello @Seller_TTG0TX5GOhqmW and @Seller_V64vFDcfYsdRa
I am following up on your questions about the inbound Fulfillment API.
I reached out to our partner team with your seller forums threads, and they asked me to share:
- GitHub forums are the right place to discuss these questions, share feedback, and seek responses
- You can also submit questions more directly to Developer Support.
Of course, you can also discuss these issues here, but the mods are limited as to how much support we can provide.
KJ_Amazon
