Fulfillment Inbound API FAQ
Frequently asked questions about Fulfillment Inbound.
v0 to v2024-03-20 migration
How long do I have to migrate to the new Fulfillment Inbound v2024-03-20 API?
Select to expand the answer.
With the launch of Fulfillment Inbound v2024-03-20, we are deprecating 10 operations within Fulfillment Inbound API v0, which will be removed on December 20, 2024. If you use Fulfillment Inbound API v0, use the Fulfillment Inbound v2024-03-20 API use case guide to migrate your workloads and integrate with this new version.
How can I receive support for my migration?
Select to expand the answer.
For more information about the new APIs and how to integrate your systems, refer to the Migration Guide and Use Case Guide. For additional support or to provide feedback, go to Developer Support or contact your account manager.
Which operations in the Fulfillment Inbound v0 API are deprecated?
Select to expand the answer.
The following table provides all Fulfillment Inbound v0 operations and their planned removal date:
Operation | Removal date |
---|---|
createInboundShipmentPlan | December 20, 2024 |
updateInboundShipment | December 20, 2024 |
createInboundShipment | December 20, 2024 |
getPreorderInfo | December 20, 2024 |
confirmPreorder | December 20, 2024 |
getTransportDetails | December 20, 2024 |
putTransportDetails | December 20, 2024 |
voidTransport | December 20, 2024 |
estimateTransport | December 20, 2024 |
confirmTransport | December 20, 2024 |
getPrepInstructions | Will remain operational. |
getShipments | Will remain operational. |
getShipmentItemsByShipmentId | Will remain operational. |
getShipmentItems | Will remain operational. |
getLabels | Will remain operational. |
getBillOfLading | Will remain operational. |
Deprecated APIs will not be supported after their deprecation date. Calls to deprecated APIs will fail as of their removal date.
What are the benefits of the Fulfillment Inbound v2024-03-20 API?
Select to expand the answer.
The Fulfillment Inbound v2024-03-20 API supports FBA inbound shipment creation, which you can use to:
- Select from multiple inbound placement service options
- Access and edit a shipment interchangeably on both Send to Amazon and via API
- Create larger plans, with support for 1500 SKUs per plan, instead of 200 SKUs per plan on APIs today
- Retrieve shipment information (for example: amazon reference number, shipment status)
- Print SKU labels for your shipments
How do I set a SKU prep category with the API?
Select to expand the answer.
You cannot set the prep category for a SKU with the v2024-03-20 API release. However, this will be supported in a future release. To set a prep category for each SKU, the seller must enter it in advance in Seller Central. This is a one-time activity per SKU.
Do I need to upload carton information using feeds?
Select to expand the answer.
No. You must upload carton information using setPackingInformation
. For more information, refer to Submit carton content information in the Migration Guide.
How do I use shipment IDs to create labels?
Select to expand the answer.
When you confirm the placement option (confirmPlacementOption
), shipmentConfirmationID
(v2024-03-20) is generated. shipmentConfirmationID
(for example, FBA1234ABCD
) is the identifier that appears on labels. This value must be used in all retained v0 operations as shipmentID
.
How can I get EstimatedBoxContentsFee
, quantity shipped, and quantity received for an inbound shipment?
EstimatedBoxContentsFee
, quantity shipped, and quantity received for an inbound shipment?Select to expand the answer.
Use getShipments
(v0) to get EstimatedBoxContentFee
. Use getShipmentItemsByShipmentId
(v0) to get quantity shipped and quantity received.
These v0 operations will remain operational past the deprecation date. You can call them with a shipment confirmation ID (shipmentConfirmationID
), which is generated after you confirm the placement option (confirmPlacementOption
) as input.
Do I have to mark my shipment as shipped in v2024-03-20
Select to expand the answer.
You don't need to mark your shipments as shipped. Amazon automatically tracks the shipments based on the carrier and tracking details. For shipments with non-Amazon partnered carriers, you must input the tracking ID with updateShipmentTrackingDetails
.
General
What additional features have been added in the general availability launch?
Select to expand the answer.
Fulfillment Inbound API v2024-03-20 supports the following features:
- New feature: View and select one of the available delivery windows for a shipment arrival at an Amazon facility.
- New feature: Print SKU labels for your shipments
- Select partnered carriers for less-than-truckload shipments
- Update the name of inbound plans and shipments
- Update the quantity of units of a SKU after shipment confirmation
Which marketplaces are available with Fulfillment Inbound API v2024-03-20?
Select to expand the answer.
The ability to create inbound shipments with the new Fulfillment Inbound API v2024-03-20 is available in the following marketplaces:
- Canada
- US
- Spain
- UK
- France
- Netherlands
- Germany
- Italy
- Sweden
- Singapore
- Australia
- Japan
We will announce support for these marketplaces as they become available:
- Mexico
- Brazil
- Poland
- Egypt
- Turkey
- Saudi Arabia
- United Arab Emirates
- India
Can I have multiple expiration dates per SKU on a single inbound plan?
Select to expand the answer.
No. Multiple expiration dates per SKU within a single inbound plan is not supported. To send a SKU with multiple expiration dates to the fulfillment network, you must create multiple inbound plans.
Can I create any shipment type when I don't know carton-level information upfront?
Select to expand the answer.
If you don't know the carton-level information upfront, you can only create a Less Than Truckload/Full Truckload (LTL/FTL) shipment. Refer to the Use Case Guide for more information.
Updated 16 days ago