Migrating Fulfillment Inbound workflows
迁移履行入站工作流程

This guide describes how to migrate from the Fulfillment Inbound API v0 (“v0”) to the Fulfillment Inbound API v2024-03-20 (“v2024-03-20”). It follows the v0 workflow and describes how to accomplish the same tasks with v2024-03-20. This migration is necessary, as certain operations in v0 are deprecated.
本指南介绍如何从 Fulfillment Inbound API v0（"v0"）迁移到 Fulfillment Inbound API v2024-03-20（"v2024-03-20"）。它遵循 v0 工作流程，并介绍了如何使用 v2024-03-20 完成相同的任务。这种迁移是必要的，因为 v0 中的某些操作已经过时。

🚧

Important! 重要！

Review the new Fulfillment Inbound shipment workflow before you go through this migration guide.
在阅读本迁移指南之前，请先查看新的 Fulfillment 入站装运工作流程。

Create an inbound shipment plan
创建进货装运计划

To create an inbound shipment plan, the seller provides key information to Amazon about the items, such as:
要创建入站发货计划，卖家要向亚马逊提供有关商品的关键信息，如

• Ship-from address 发货地址
• Items summary 项目摘要
• Label and prep preference
  标签和预处理偏好

Amazon uses this information to create a shipment plan for your items, so the items can be appropriately packed and sent to an Amazon fulfillment center.
亚马逊会利用这些信息为您的物品创建一个装运计划，以便对物品进行适当包装并发送到亚马逊履行中心。

The v0 operation createInboundShipmentPlan is replaced with a set of operations in v2024-03-20. These new operations provide sellers with several packing and placement options, similar to the Send To Amazon workflow in Seller Central:
v0 操作 createInboundShipmentPlan 在 v2024-03-20 中被一组操作取代。这些新操作为卖家提供了多个包装和放置选项，类似于卖家中心的 "发送到亚马逊 "工作流程：

Request and response mapping
请求和响应映射

When you make requests and interpret responses with the new operations, consider the following:
在使用新操作提出请求和解释响应时，请考虑以下几点：

• destinationMarketplaces is replaced with shipToCountryCode and ShipToCountrySubdivisionCode in requests.
  请求中的 destinationMarketplaces 被替换为 shipToCountryCode 和 ShipToCountrySubdivisionCode 。
• Label and prep preference is replaced with Label and prep owners.
  标签和预置首选项被替换为标签和预置所有者。
• PrepDetailList is not available as an input. The seller must enter the prep category in Seller Central in advance for each SKU. This is a one-time activity per SKU and the prep category persists.
  PrepDetailList 不能作为输入。卖方必须事先在卖方中心为每个 SKU 输入预处理类别。这是每一 SKU 的一次性活动，预处理类别将持续存在。
• You retrieve fees and discounts from the listPackingOptions response for the packing option, and from the listPlacementOptions response for different placement options.
  您可以从 listPackingOptions 响应中获取包装选项的费用和折扣，从 listPlacementOptions 响应中获取不同放置选项的费用和折扣。
• createInboundPlan generates shipment IDs. These are different from shipmentConfirmationIDs, which are the identifiers that appear on labels (for example, FBA1234ABCD). getShipment retrieves both of these IDs, along with the Amazon reference ID, after confirming placement in the next step.
  createInboundPlan 生成装运标识。它们与 shipmentConfirmationIDs 不同，后者是出现在标签上的标识符（例如， FBA1234ABCD ）。 getShipment 在下一步确认放置后，会检索这两个 ID 以及 Amazon 参考 ID。
• The v0 operation createInboundShipmentPlan returns the DestinationFulfillmentCenterId. In v2024-03-20, getShipment returns this at the shipment ID level.
  v0 操作 createInboundShipmentPlan 返回 DestinationFulfillmentCenterId 。在 v2024-03-20 中， getShipment 返回货件 ID 级别的信息。
• The v0 operation createInboundShipmentPlan returns the EstimatedBoxContentsFee. Use the v0 operation getShipments to retrieve this. For more details, refer to the Preserved workflows section.
  v0 操作 createInboundShipmentPlan 返回 EstimatedBoxContentsFee 。请使用 v0 操作 getShipments 检索。有关详细信息，请参阅 "保留的工作流 "部分。

Version 0 features 0 版功能

When you call createInboundShipmentPlan with an address and required shipping information, it returns a list of inbound plans, each containing a shipment ID, destination FC, items, and fees.
当您使用地址和所需运输信息调用 createInboundShipmentPlan 时，它会返回一个入站计划列表，每个计划都包含一个运输 ID、目的地 FC、项目和费用。

Version 2024-03-20 features
2024-03-20 版功能

You create inbound shipment plans in a highly customizable way in the new version:
在新版本中，您可以通过高度定制的方式创建进货装运计划：

📘

Note 备注

All POST operations in the new flow are asynchronous and must be followed by getInboundOperationStatus to retrieve their status.
新流程中的所有 POST 操作都是异步的，必须在操作后跟上 getInboundOperationStatus 以获取其状态。

Create an inbound shipment
创建入站装运

An inbound shipment indicates to Amazon that a shipment of items will arrive at a particular Amazon fulfillment center soon.
入站货物向亚马逊表明，一批货物将很快抵达亚马逊的某个履行中心。

In v0, you use createInboundShipment for this task. In v2024-03-20, you use confirmPlacementOption.
在 v0 中，您可以使用 createInboundShipment 来完成这项任务。在 v2024-03-20 中，使用 confirmPlacementOption 。

Request and response mapping
请求和响应映射

When you make requests and interpret responses with the new operations, consider the following:
在使用新操作提出请求和解释响应时，请考虑以下几点：

• In v0, InboundShipmentHeader and InboundShipmentItems must be passed for each shipment ID in the request. In v2024-03-20, only inboundPlanId and placementOptionId are required.
  在 v0 中，必须为请求中的每个货件 ID 传递 InboundShipmentHeader 和 InboundShipmentItems 。在 v2024-03-20 中，只需要 inboundPlanId 和 placementOptionId 。
• shipmentID in v0 is replaced with shipmentConfirmationID in v2024-03-20 and is generated when you create an inbound shipment.
  v0 中的 shipmentID 在 v2024-03-20 中被 shipmentConfirmationID 取代，并在创建入站装运时生成。

Version 0 features 0 版功能

To create an inbound shipment, send an inbound shipment header with shipment items and a marketplace ID for each shipment ID.
要创建入站快件，请发送包含快件项目和每个快件 ID 的市场 ID 的入站快件标题。

Version 2024-03-20 features
2024-03-20 版功能

The confirmPlacementOption operation confirms the placement option for an inbound plan, selects the placement splits for an inbound plan, and creates confirmed shipment IDs for all shipments within the inbound plan. The shipmentConfirmationID generated in this step is the shipment identifier that appears on labels (for example, FBA1234ABCD).
confirmPlacementOption 操作确认入站计划的放置选项，选择入站计划的放置分割，并为入站计划中的所有货件创建确认的货件 ID。在此步骤中生成的 shipmentConfirmationID 是出现在标签上的货件标识符（例如 FBA1234ABCD ）。

Note that this step is performed after generating transportation options only when carton content is known in advance. For the correct order of operations to create a shipment plan using the new APIs, refer to Creating a shipment when the seller knows the carton-level information up-front
请注意，只有提前知道纸箱内容时，才会在生成运输选项后执行此步骤。有关使用新 API 创建装运计划的正确操作顺序，请参阅 "当卖方预先知道纸箱信息时创建装运计划"。

Submit carton content information
提交纸箱内容信息

The POST_FBA_INBOUND_CARTON_CONTENTS feed in v0 is replaced with setPackingInformation.
v0 中的 POST_FBA_INBOUND_CARTON_CONTENTS feed 被替换为 setPackingInformation 。

Request and response mapping
请求和响应映射

The POST_FBA_INBOUND_CARTON_CONTENTS feed contains all information about the cartons in XSD format for the shipment ID level. setPackingInformation requires the same information at either the Packing group level or Shipment ID level. Box weight and dimensions are new.
POST_FBA_INBOUND_CARTON_CONTENTS 源包含以 XSD 格式提供的装运 ID 级别的所有纸箱信息。 setPackingInformation 要求包装组级别或货件 ID 级别的相同信息。纸箱重量和尺寸是新信息。

Version 0 features 0 版功能

The Feeds API is a separate API for bulk updates. The feeds input must conform to the XSD format.
Feeds API 是用于批量更新的独立 API。输入的 Feeds 必须符合 XSD 格式。

Version 2024-03-20 features
2024-03-20 版功能

• setPackingInformation simplifies the submission of carton content information.
  setPackingInformation 简化了纸箱内容信息的提交。
• You can provide packing information at two stages depending on whether carton level information is known at the time of packing:
  您可以在两个阶段提供包装信息，具体取决于包装时是否知道纸箱级别信息：
  • If packing information is known, call setPackingInformation with the packing group ID before placement confirmation.
    如果知道包装信息，请在确认放置前致电 setPackingInformation 并提供包装组 ID。
  • If packing information is unknown, call setPackingInformation with the shipment ID after placement confirmation.
    如果包装信息不详，请在下单确认后致电 setPackingInformation 并提供装运编号。

For an outline of the two workflows, refer to Fulfillment Inbound shipment workflow.
有关这两个工作流程的概要，请参阅履行进货装运工作流程。

Submit transportation information and estimate shipping cost
提交运输信息并估算运费

When you submit transportation information and get an estimate of shipping costs for Amazon-partnered carriers, you also provide information that Amazon fulfillment centers can use to plan for the arrival of your shipment.
当您提交运输信息并获得亚马逊合作承运商的运费估算时，您也提供了亚马逊履行中心可用于计划货物到达的信息。

Request and response mapping
请求和响应映射

When you make requests and interpret responses with the new operations, consider the following:
在使用新操作提出请求和解释响应时，请考虑以下几点：

• The v0 operation putTransportDetails requires shipment type (small parcel or a Less Than Truckload/Full Truckload [LTL/FTL]) whether using a partnered carrier or not. It requires transport details for parcel or LTL data if using an Amazon partnered carrier. Few details, such as name and tracking details, are required for non-partnered carriers. In v2024-03-20, generateTransportationOptions requires ship from address, ready to ship date, and pallet information (if applicable) to generate estimates.
  无论是否使用合作承运商，v0 操作 putTransportDetails 都需要货物类型（小包裹或零担/整车 [LTL/FTL]）。如果使用亚马逊合作承运商，则需要包裹或零担数据的运输详细信息。对于非合作承运商，则只要求提供少量详细信息，如名称和跟踪详细信息。在 v2024-03-20 中， generateTransportationOptions 要求提供发货地址、准备发货日期和托盘信息（如适用），以便生成估价。
• The v0 operations estimateTransport and getTransportDetails use shipmentID as the identifier. In v2024-03-20, listTransportationOptions requires a placement option ID and shipment ID.
  v0 操作 estimateTransport 和 getTransportDetails 使用 shipmentID 作为标识符。在 v2024-03-20 中， listTransportationOptions 需要贴装选项 ID 和装运 ID。
• In v0, the PartneredEstimate response element contains the estimate. In v2024-03-20, the list response includes all available transportation quotes for all available ship modes and carrier options.
  在 v0 中， PartneredEstimate 响应元素包含估价。在 v2024-03-20 中，列表响应包括所有可用运输方式和承运商选项的所有可用运输报价。

Version 0 features 0 版功能

• Estimates are generated based on the shipment type and carrier details provided by the seller. This is applicable only to partnered carriers.
  估价是根据卖家提供的货运类型和承运商详细信息生成的。这仅适用于合作承运商。
• v0 uses putTransportDetails to request estimates, followed by estimateTransport and getTransportDetails. The estimate is returned in the PartneredEstimate response element.
  v0 使用 putTransportDetails 来请求估算，然后是 estimateTransport 和 getTransportDetails 。估算结果将在 PartneredEstimate 响应元素中返回。

Version 2024-03-20 features
2024-03-20 版功能

• Amazon generates a list of transportation options. This list contains all available shipping modes and carrier options for each shipment within each placement option based on delivery date and address.
  亚马逊会生成一份运输选项列表。该列表包含根据交付日期和地址在每个放置选项中为每个货件提供的所有可用运输模式和承运商选项。
• Carrier options include Amazon-partnered and non-partnered carriers. Each quote includes the cost, a void window, and an expiration date. The void window is the time period in which a seller can cancel a shipment and receive a refund for their transportation quote. If pallet information is not included, LTL transportation options are not generated.
  承运商选项包括亚马逊合作承运商和非合作承运商。每个报价都包括成本、无效窗口和到期日期。作废窗口是卖家可以取消货运并获得运输报价退款的时间段。如果不包括托盘信息，则不会生成零担运输选项。
• Generate transportation options with generateTransportationOptions, then list transportation options with estimated costs using listTransportationOptions.
  用 generateTransportationOptions 生成运输方案，然后用 listTransportationOptions 列出运输方案及估计成本。
• To generate delivery window options separately, use generateDeliveryWindowOptions. Delivery windows are seven-day periods during which a seller can deliver their shipment to the destination fulfillment center. An available delivery window option is necessary for all shipments that don't have an appointment slot with a fulfillment center. For example, all shipments through non-partnered carriers need a confirmed delivery window. This is a new feature in v2024-03-20.
  要单独生成交付窗口选项，请使用 generateDeliveryWindowOptions 。交付窗口是指卖家可以将货物交付给目的地履行中心的七天时间。对于没有与履行中心预约时间段的所有货件，都需要一个可用的交货窗口选项。例如，所有通过非合作承运商运送的货物都需要确认交付窗口。这是 v2024-03-20 中的一项新功能。
• Call generateDeliveryWindowOptions to generate delivery window options, followed by listDeliveryWindowOptions to review available delivery window options for each shipment within an inbound plan. Note that each option has an expiration date (validUntil). The delivery must be confirmed before this date.
  调用 generateDeliveryWindowOptions 生成交货窗口选项，然后调用 listDeliveryWindowOptions 查看入站计划中每个货件的可用交货窗口选项。请注意，每个选项都有一个过期日期 ( validUntil )。必须在此日期之前确认交付。

Confirm the transportation request
确认运输请求

When a seller confirms a transportation request for an Amazon-partnered transportation option, they also confirm that they:
当卖家确认亚马逊合作运输选项的运输请求时，他们也会确认自己：

• Accept the Amazon-partnered shipping estimate
  接受亚马逊合作的运费估算
• Agree to allow Amazon to charge their account for the shipping cost
  同意亚马逊向其账户收取运费
• Request that the Amazon-partnered carrier ship the inbound shipment
  要求与亚马逊合作的承运商运送入境货物

Request and response mapping
请求和响应映射

When you make requests and interpret responses with the new operations, consider the following:
在使用新操作提出请求和解释响应时，请考虑以下几点：

• In v0, confirmTransport requires only the shipmentID. In v2024-03-20, confirmDeliveryWindowOptions requires shipmentID and a selected delivery window option ID. To call confirmTransportationOptions, the seller must pass the shipment ID, selected transportation option ID, contact information (needed for partnered carriers for LTL shipments), and estimated delivery date (needed for non-partnered carriers).
  在 v0 中， confirmTransport 只需要 shipmentID 。在 v2024-03-20 中， confirmDeliveryWindowOptions 需要 shipmentID 和选定的交货窗口选项 ID。要调用 confirmTransportationOptions ，卖方必须提供货物 ID、所选运输选项 ID、联系信息（零担货物的合作承运商需要）和预计交货日期（非合作承运商需要）。
• v0 returns TransportStatus, which provides the status of the Amazon-partnered carrier shipment.
  v0 返回 TransportStatus ，提供亚马逊合作承运商货物的状态。

Version 0 features 0 版功能

confirmTransport confirms the transportation request at the shipmentID level.
confirmTransport 在 shipmentID 层确认运输请求。

Version 2024-03-20 features
2024-03-20 版功能

• Choose delivery windows for each shipment within a plan using confirmDeliveryWindowOptions. All transportation options that have the program DELIVERY_WINDOW_REQUIRED require you to confirm a delivery window before you confirm a transportation option. This is a new requirement in v2024-03-20.
  使用 confirmDeliveryWindowOptions 为计划中的每批货物选择交货窗口。所有具有程序 DELIVERY_WINDOW_REQUIRED 的运输选项都要求您在确认运输选项之前确认交货窗口。这是 v2024-03-20 中的新要求。
• The way you select transportation options for each shipment within an inbound plan using the confirmTransportationOptions operation is similar to v0. You must confirm a transportation option before printing labels, even for non Amazon-partnered transportation.
  使用 confirmTransportationOptions 操作为入库计划中的每个货件选择运输选项的方式与 v0 相似。 在打印标签前必须确认运输选项，即使是非 Amazon-partnered 运输。

Send shipment tracking numbers to Amazon
向亚马逊发送货物跟踪号码

To share tracking details with Amazon after sending a shipment to Amazon's fulfillment network using a non-partnered carrier, use updateShipmentTrackingDetails.
要在使用非合作承运商将货物发送到亚马逊履行网络后与亚马逊共享跟踪详细信息，请使用 updateShipmentTrackingDetails 。

Request and response mapping
请求和响应映射

In v0, putTransportDetails requires shipment tracking numbers using TrackingId (small parcel) and PRO number (LTL). In v2024-03-20, updateShipmentTrackingDetails requires shipment ID and tracking details for LTL or small parcel shipments.
在 v0 中， putTransportDetails 要求使用 TrackingId （小包裹）和 PRO 号码（零担）提供货物跟踪号码。在 v2024-03-20 中， updateShipmentTrackingDetails 要求提供零担或小包裹货物的货物 ID 和跟踪详情。

Version 0 features 0 版功能

Tracking details are embedded in the putTransportDetails operation.
跟踪详情嵌入 putTransportDetails 操作中。

Version 2024-03-20 features
2024-03-20 版功能

putTransportDetails is a dedicated operation for updating tracking details. For LTL shipments, the seller must provide a PRO number (also known as Freight Bill number) and can optionally provide a Bill of Lading (BOL) number. For small parcel shipments, the seller must share an array of box IDs and associated tracking IDs.
putTransportDetails 是更新跟踪详细信息的专用操作。对于零担货物，卖方必须提供 PRO 编号（也称为货运单编号），并可选择提供提货单 (BOL) 编号。对于小包裹货物，卖方必须共享一个箱子 ID 和相关跟踪 ID 阵列。

Mark your shipments as shipped
标记货物已装运

You do not need to mark your shipments as shipped in v2024-03-20. Amazon automatically tracks the shipments based on the carrier and tracking details.
在 v2024-03-20 中，您无需将货物标记为已发货。亚马逊会根据承运商和跟踪详情自动跟踪货物。

Cancel a transportation request
取消运输申请

To cancel a transportation request, use cancelInboundPlan.
要取消运输请求，请使用 cancelInboundPlan 。

Request and response mapping
请求和响应映射

In v0, you cancel transportation requests at the shipment ID level. In v2024-03-20, you do it at the inbound plan level.
在 v0 中，您可以在装运 ID 级别取消运输请求。在 v2024-03-20 中，则在入站计划层面取消。

Version 0 features 0 版功能

v0 uses voidTransport to cancel the transportation request. After you confirm a transportation request, you have 24 hours to void it for a small parcel shipment, and one hour to void it for an LTL/FTL shipment.
v0 使用 voidTransport 取消运输请求。确认运输请求后，如果是小包裹货运，您有 24 小时的时间取消请求；如果是零担/整车货运，您有 1 小时的时间取消请求。

Version 2024-03-20 features
2024-03-20 版功能

cancelInboundPlan also cancels the fees associated with the transportation options selected by the seller if it's called within the void window. The void window is 24 hours after you confirm a small parcel shipment transportation request or one hour after you confirm an LTL/FTL shipment transportation request. This is the same as in v0.
cancelInboundPlan 如果在作废窗口内呼叫，也会取消卖方所选运输选项的相关费用。作废窗口为确认小包裹货物运输请求后 24 小时或确认零担/整车货物运输请求后 1 小时。这与 v0 相同。

Preserved workflows 保留工作流程

The following v0 operations are not deprecated:
以下 v0 操作未被弃用：

🚧

Important! 重要！

Use shipmentConfirmationID in place of shipmentId for all v0 operations that are not deprecated. There is a known issue where single SKU details are not shown in the box labels in the new version.
使用 shipmentConfirmationID 代替 shipmentId 进行所有未废弃的 v0 操作。有一个已知问题，在新版本中，单个 SKU 的详细信息不会显示在包装盒标签中。

Create a listing and convert it to FBA remains a prerequisite step for using the new version.
创建列表并将其转换为 FBA 仍是使用新版本的前提步骤。