Fulfillment Inbound API FAQ

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.

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.

The following table provides all Fulfillment Inbound v0 operations and their planned removal date:

Deprecated APIs will not be supported after their deprecation date. Calls to deprecated APIs will fail as of their removal date.

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

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.

No. You must upload carton information using setPackingInformation. For more information, refer to Submit carton content information in the Migration Guide.

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.

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.

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.

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

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

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.

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.