Fulfillment Inbound API FAQ
入站 API 常见问题
Frequently asked questions about Fulfillment Inbound.
关于入境履行的常见问题。
v0 to v2024-03-20 migration
从 v0 迁移到 v2024-03-20
从 v0 迁移到 v2024-03-20
How long do I have to migrate to the new Fulfillment Inbound v2024-03-20 API?
我需要多长时间才能迁移到新的 Fulfillment Inbound v2024-03-20 API?
我需要多长时间才能迁移到新的 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.
随着 Fulfillment Inbound v2024-03-20 的推出,我们将淘汰 Fulfillment Inbound API v0 中的 10 个操作,这些操作将于 2024 年 12 月 20 日删除。如果您使用 Fulfillment Inbound API v0,请使用 Fulfillment Inbound v2024-03-20 API 用例指南迁移您的工作负载并与新版本集成。
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.
有关新 API 和如何集成系统的更多信息,请参阅《迁移指南》和《使用案例指南》。如需其他支持或提供反馈,请访问开发人员支持或联系您的客户经理。
Which operations in the Fulfillment Inbound v0 API are deprecated?
Fulfillment Inbound v0 API 中的哪些操作已被弃用?
Fulfillment Inbound v0 API 中的哪些操作已被弃用?
Select to expand the answer.
选择以扩展答案。
The following table provides all Fulfillment Inbound v0 operations and their planned removal date:
下表提供了所有 Fulfillment Inbound v0 操作及其计划删除日期:
Operation 运行 | Removal date 拆除日期 |
---|---|
createInboundShipmentPlan | December 20, 2024 2024 年 12 月 20 日 |
updateInboundShipment | December 20, 2024 2024 年 12 月 20 日 |
createInboundShipment | December 20, 2024 2024 年 12 月 20 日 |
getPreorderInfo | December 20, 2024 2024 年 12 月 20 日 |
confirmPreorder | December 20, 2024 2024 年 12 月 20 日 |
getTransportDetails | December 20, 2024 2024 年 12 月 20 日 |
putTransportDetails | December 20, 2024 2024 年 12 月 20 日 |
voidTransport | December 20, 2024 2024 年 12 月 20 日 |
estimateTransport | December 20, 2024 2024 年 12 月 20 日 |
confirmTransport | December 20, 2024 2024 年 12 月 20 日 |
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.
在废弃日期之后,将不再支持废弃的 API。自废弃日期起,对废弃 API 的调用将失效。
What are the benefits of the Fulfillment Inbound v2024-03-20 API?
Fulfillment Inbound v2024-03-20 API 有哪些优势?
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:
Fulfillment Inbound v2024-03-20 API 支持 FBA 入站货件创建,您可以使用它来创建货件:
- Select from multiple inbound placement service options
从多种入境安置服务选项中进行选择 - Access and edit a shipment interchangeably on both Send to Amazon and via API
通过 "发送至亚马逊 "和应用程序接口可互换访问和编辑货件 - Create larger plans, 1,500 SKUs per plan, instead of 200 SKUs per plan on APIs today
创建更大的计划,每个计划 1,500 个 SKU,而不是现在应用程序接口上的每个计划 200 个 SKU - Retrieve shipment information (for example: amazon reference number, shipment status)
检索装运信息(例如:亚马逊参考编号、装运状态) - Print SKU labels for your shipments
打印货运的 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.
必须使用 setPackingInformation
上传纸箱信息。有关详细信息,请参阅《迁移指南》中的提交纸箱内容信息。
How do I use shipment IDs to create labels?
如何使用货运 ID 创建标签?
如何使用货运 ID 创建标签?
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
.
确认放置选项 ( confirmPlacementOption
) 时,会生成 shipmentConfirmationID
(v2024-03-20)。 shipmentConfirmationID
(例如, FBA1234ABCD
)是出现在标签上的标识符。该值必须在所有保留的 v0 操作中作为 shipmentID
使用。
How can I get EstimatedBoxContentsFee
, quantity shipped, and quantity received for an inbound shipment?
如何获取入站货物的 EstimatedBoxContentsFee
、已发货数量和已收货数量?
EstimatedBoxContentsFee
, quantity shipped, and quantity received for an inbound shipment?如何获取入站货物的
EstimatedBoxContentsFee
、已发货数量和已收货数量?Select to expand the answer.
选择以扩展答案。
Use getShipments
(v0) to get EstimatedBoxContentFee
. Use getShipmentItemsByShipmentId
(v0) to get quantity shipped and quantity received.
使用 getShipments
(v0) 获得 EstimatedBoxContentFee
。使用 getShipmentItemsByShipmentId
(v0) 可以得到发货数量和收货数量。
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.
这些 v0 操作在废弃日期后仍可继续使用。您可以使用装运确认 ID ( shipmentConfirmationID
)调用它们,该 ID 会在您确认作为输入的放置选项 ( confirmPlacementOption
) 后生成。
Do I have to mark my shipment as shipped in v2024-03-20
我是否必须在 v2024-03-20 中将货物标记为已装运
我是否必须在 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
.
您无需将货物标记为已发货。亚马逊会根据承运商和跟踪详情自动跟踪货物。对于非亚马逊合作承运商的货物,您必须使用 updateShipmentTrackingDetails
输入跟踪 ID。
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:
Fulfillment Inbound API v2024-03-20 支持以下功能:
- 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
新功能:为您的货物打印 SKU 标签 - 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
发货确认后更新 SKU 的单位数量
Which marketplaces are available with Fulfillment Inbound API v2024-03-20?
Fulfillment Inbound API v2024-03-20 支持哪些市场?
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:
使用新的 Fulfillment Inbound API v2024-03-20 创建入站货件的功能可在以下市场中使用:
- 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?
在一个入站计划中,每个 SKU 可以有多个过期日期吗?
在一个入站计划中,每个 SKU 可以有多个过期日期吗?
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.
如果事先不知道纸箱级别信息,则只能创建零担/整车(LTL/FTL)货运。有关详细信息,请参阅《使用案例指南》。
Why does listPackingOptions
always return one option?
为什么 listPackingOptions
总是返回一个选项?
listPackingOptions
always return one option?为什么
listPackingOptions
总是返回一个选项?Select to expand the answer.
选择以扩展答案。
listPackingOptions
returns one option because it is designed to provide the most optimized packing solution based on the input criteria. This is the expected behavior.
listPackingOptions
返回一个选项,因为它旨在根据输入条件提供最优化的打包解决方案。这是预期行为。
Can I print unique shipment labels for shipments that are created with the Fulfillment Inbound API v2024-03-20 operations?
能否为使用 Fulfillment Inbound API v2024-03-20 操作创建的货件打印唯一的货件标签?
能否为使用 Fulfillment Inbound API v2024-03-20 操作创建的货件打印唯一的货件标签?
Select to expand the answer.
选择以扩展答案。
Yes. To print unique shipment labels, use the Fulfillment Inbound API v0 getLabels
operation. You need to provide {{baseUrl}}/fba/inbound/v0/shipments/:shipmentId/labels?PageType={{PageType}}&PageSize={{PageSize}}
, where shipmentId
is shipmentConfirmationId
.
要打印唯一的货物标签,请使用 Fulfillment Inbound API v0 getLabels
操作。您需要提供 {{baseUrl}}/fba/inbound/v0/shipments/:shipmentId/labels?PageType={{PageType}}&PageSize={{PageSize}}
,其中 shipmentId
为 shipmentConfirmationId
。
What is the generateSelfShipAppointmentSlots
operation used for?
generateSelfShipAppointmentSlots
操作有什么用途?
generateSelfShipAppointmentSlots
operation used for?generateSelfShipAppointmentSlots
操作有什么用途?Select to expand the answer.
选择以扩展答案。
The generateSelfShipAppointmentSlots
operation generates an appointment slots list. This is applicable for the MX, BR, EG, SA, AE, and IN marketplaces.
generateSelfShipAppointmentSlots
操作会生成预约时段列表。这适用于 MX、BR、EG、SA、AE 和 IN 市场。
How can I update the quantities and box contents after my inbound shipments are confirmed?
进货确认后,如何更新数量和包装箱内容?
进货确认后,如何更新数量和包装箱内容?
Select to expand the answer.
选择以扩展答案。
To update the quantities and box contents after your shipments are confirmed, use the following steps.
确认发货后,请按以下步骤更新数量和包装箱内容。
-
Use
generateShipmentContentUpdatePreviews
to update item quantities and generate a preview of the updated shipment contents and transportation costs.
使用generateShipmentContentUpdatePreviews
更新项目数量,并生成更新后的装运内容和运输成本预览。 -
Use
listShipmentContentUpdatePreviews
to retrieve a paginated list of previews, which summarizes the changes and cost implications.
使用listShipmentContentUpdatePreviews
检索分页预览列表,其中概述了更改和成本影响。 -
Use
confirmShipmentContentUpdatePreview
to confirm a shipment content update preview and accept the changes in transportation costs.
使用confirmShipmentContentUpdatePreview
确认装运内容更新预览并接受运输成本的更改。
How can I determine if a shipment used an Amazon Partnered Carrier or my own carrier?
如何确定货物是使用了亚马逊合作承运商还是我自己的承运商?
如何确定货物是使用了亚马逊合作承运商还是我自己的承运商?
Select to expand the answer.
选择以扩展答案。
To determine if a shipment used an Amazon Partnered Carrier or your own carrier, use the listTransportationOptions
. If Amazon confirms your shipment, then listTransportationOptions
returns a list with only one confirmed transportation option (AMAZON_PARTNERED_CARRIER
or USE_YOUR_OWN_CARRIER
) in the shippingSolution
field.
要确定货物使用的是 Amazon 合作承运商还是您自己的承运商,请使用 listTransportationOptions
。如果亚马逊确认了您的货物,则 listTransportationOptions
返回一个列表,在 shippingSolution
字段中只有一个确认的运输选项( AMAZON_PARTNERED_CARRIER
或 USE_YOUR_OWN_CARRIER
)。
How can I retrieve all inbound details for shipments that are created with the Send to Amazon UI?
如何检索使用 "发送到亚马逊 "用户界面创建的货件的所有入站详细信息?
如何检索使用 "发送到亚马逊 "用户界面创建的货件的所有入站详细信息?
Select to expand the answer.
选择以扩展答案。
For shipments created with the Send to Amazon UI, you can retrieve all inbound details with the listInboundPlans
operation and the Fulfillment Inbound API v2024-03-20 GET operations:
对于使用发送到亚马逊用户界面创建的货件,您可以使用 listInboundPlans
操作和 Fulfillment Inbound API v2024-03-20 GET 操作检索所有入站详细信息:
-
Use
listInboundPlans
to retrieve your inbound plans, shipment IDs, packing IDs, placement IDs, and transportation IDs.
使用listInboundPlans
检索入站计划、装运 ID、包装 ID、放置 ID 和运输 ID。 -
Use the values from step 1 to call the Fulfillment Inbound API v2024-03-20 GET operations. For more information about the GET operations, refer to Fulfillment Inbound API v2024-03-20.
使用步骤 1 中的值调用 Fulfillment Inbound API v2024-03-20 GET 操作。有关 GET 操作的更多信息,请参阅 Fulfillment Inbound API v2024-03-20。
Can you combine Small Parcel Delivery (SPD) and LTL in to one inbound plan?
能否将小包裹递送(SPD)和零担货物运输(LTL)合并为一个进货计划?
能否将小包裹递送(SPD)和零担货物运输(LTL)合并为一个进货计划?
Select to expand the answer.
选择以扩展答案。
Yes. To combine SPD and LTL shipments in to one inbound plan, use the following steps.
要将 SPD 和 LTL 货运合并为一个进货计划,请使用以下步骤。
-
Use the
generateTransportationOptions
operation to generate a list of SPD and LTL transportation options. You must usegenerateTransportationOptions
to generate transportation options before they're available to thelistTransportationOptions
operation in the next step.
使用generateTransportationOptions
操作生成 SPD 和 LTL 运输选项列表。必须使用generateTransportationOptions
生成运输选项,然后才能在下一步的listTransportationOptions
操作中使用。 -
Use the
listTransportationOptions
operation to retrieve all transportation options for the shipment. Retrieve theshipmentId
andtransportationOptionId
for the SPD and LTL shipments.
使用listTransportationOptions
操作检索货件的所有运输选项。检索 SPD 和 LTL 货件的shipmentId
和transportationOptionId
。
Example response: 答复示例:
{
"transportationOptions":[
{
"carrier":{
"name":"United States Postal Service",
"alphaCode":"USPS"
},
"preconditions":[
"CONFIRMED_DELIVERY_WINDOW"
],
"shipmentId":"sh1xxxxxxxxxxxxxx",
"shippingMode":"GROUND_SMALL_PARCEL",
"transportationOptionId":"to1xxxxxxxxxxxxxx", ---> choose to confirm
"shippingSolution":"USE_YOUR_OWN_CARRIER"
},
{
"carrier":{
"name":"XXXXX",
"alphaCode":"ABCD"
},
"carrierAppointment":{
"startTime":"2024-10-11T00:00Z",
"endTime":"2024-10-11T23:59Z"
},
"quote":{
"cost":{
"amount":326.54,
"code":"USD"
},
"expiration":"2024-10-09T22:40Z"
},
"preconditions":[
],
"shipmentId":"sh2xxxxxxxxxxxxxx",
"shippingMode":"FREIGHT_LTL",
"transportationOptionId":"to2xxxxxxxxxxxxxx", ---> choose to confirm
"shippingSolution":"AMAZON_PARTNERED_CARRIER"
}
]
}
- Use the
confirmTransportationOptions
operation and pass in theshipmentId
andtransportationOptionId
for the SPD and LTL shipments.
使用confirmTransportationOptions
操作,并为 SPD 和 LTL 货运输入shipmentId
和transportationOptionId
。
Example request: 请求示例:
{
"transportationSelections": [
{
"shipmentId": "sh1xxxxxxxxxxxxxxxxxxx",
"transportationOptionId": "to1xxxxxxxxxxxxxxxxxxx"
},
{
"shipmentId": "sh2xxxxxxxxxxxxxxxxxxx",
"transportationOptionId": "to2xxxxxxxxxxxxxxxxxxx"
}
]
}
When I print a label through the API, the address shows the company name, but the label from Seller Central does not. Can I remove the company name from the API result?
当我通过 API 打印标签时,地址会显示公司名称,但卖方中心的标签不会。我能否从 API 结果中删除公司名称?
当我通过 API 打印标签时,地址会显示公司名称,但卖方中心的标签不会。我能否从 API 结果中删除公司名称?
Select to expand the answer.
选择以扩展答案。
No. The discrepancy is intentional and is based on the carrier that is used for the shipment:
不会。这种差异是故意造成的,而且是根据装运所使用的承运商造成的:
-
Amazon Freight or first-party PCP LTL carriers: These shipments don't show detailed address information, but have an extra barcode at the bottom of the label. The absence of the address is by design and is accepted by Amazon's fulfillment centers.
亚马逊货运或第一方 PCP LTL 承运商:这些货物不显示详细地址信息,但在标签底部有一个额外的条形码。不显示地址是亚马逊履约中心设计并接受的。 -
Third-party LTL PCP carriers: For shipments handled by third-party carriers, the labels show detailed address information which includes the company name.
第三方零担货物 PCP 承运商:对于由第三方承运商处理的货物,标签上会显示详细的地址信息,包括公司名称。
To check a shipment's carrier in Seller Central, navigate to the shipment summary page, select the shipment, and choose Show More.
要在 "卖家中心 "中检查快件的承运商,请导航至快件摘要页面,选择快件,然后选择 Show More 。
How can I avoid inbound shipment cancellation charges?
如何避免进港货运取消费用?
如何避免进港货运取消费用?
Select to expand the answer.
选择以扩展答案。
To avoid cancellation charges, you must cancel the inbound shipment within the specific SLAs, which vary based on the type of shipment:
为避免收取取消费用,您必须在特定的 SLA(服务水平协议)范围内取消入站货件,具体服务水平协议因货件类型而异:
-
SPD: You must cancel the inbound plan within 24 hours after shipment creation for Amazon Partnered Carriers.
SPD:对于亚马逊合作承运商,您必须在货物创建后 24 小时内取消入站计划。 -
Pallet shipments (LTL/FTL): You must cancel within 1 hour after shipment creation for Amazon Partnered Carriers.
托盘货物(零担/整车):对于亚马逊合作承运商,您必须在货物创建后 1 小时内取消。
The charge restrictions don’t apply for non-partnered carrier options.
收费限制不适用于非合作运营商选项。
Do you have a list of shipment statuses and their meanings?
您有装运状态及其含义的清单吗?
您有装运状态及其含义的清单吗?
Select to expand the answer.
选择以扩展答案。
Status 现状 | Description 说明 |
---|---|
ABANDONED | Indicates something went wrong during the shipment creation process. 表示在创建货件的过程中出了问题。 |
CANCELED | Indicates that the shipment was canceled. 表示货物被取消。 |
CHECKED_IN | Indicates that the fulfillment center has acknowledged delivery of the shipment and has checked it in. 表示履行中心已确认货物已送达并已托运。 |
CLOSED | Indicates that there are no further actions to take on the shipment. 表示对货物没有进一步的操作。 |
DELETED | Indicates that the shipment was deleted prior to it being shipped. 表示货物在发运前已被删除。 |
DELIVERED | Indicates that the carrier has delivered the shipment to the fulfillment center, but the fulfillment center has not yet checked it in. 表示承运商已将货物交付给履约中心,但履约中心尚未托运。 |
IN_TRANSIT | Indicates that the shipment is within the carrier network and is in the process of being couriered. 表示快件在承运网络内,正在快递过程中。 |
MIXED | Used for a special placement option where sellers send in a single shipment but the carrier will distribute it across Amazon fulfillment centers. 用于特殊投放选项,即卖家发送单件货物,但承运商将在亚马逊各履行中心进行配送。 |
READY_TO_SHIP | Indicates that shipment preparation is complete and the shipment is ready to be shipped. 表示装运准备工作已完成,可以装运。 |
RECEIVING | Indicates that the fulfillment center is receiving the shipment's contents. 表示履行中心正在接收快件内容。 |
SHIPPED | Indicates that the shipment was dropped off at (or picked up by) a carrier. 表示货物已在承运人处投递(或由承运人提取)。 |
UNCONFIRMED | A tentative shipment exists, but it is still in the planning stage. 暂定有一批货物,但仍处于规划阶段。 |
WORKING | The initial status of a shipment once created. 货物创建后的初始状态。 |
What are the eligibility dimensions and weight requirements for SPD and LTL options?
SPD 和 LTL 选项的合格尺寸和重量要求是什么?
SPD 和 LTL 选项的合格尺寸和重量要求是什么?
Select to expand the answer.
选择以扩展答案。
To review eligibility dimensions and weight requirements for SPD, refer to Small-parcel delivery to Amazon. To review eligibility dimensions and weight requirements for LTL options, refer to Pallets (LTL/FTL) delivery.
要查看 SPD 的合格尺寸和重量要求,请参阅亚马逊小包裹递送。要查看零担选项的合格尺寸和重量要求,请参阅托盘(零担/整车)交付。
How many SKUs and items for each SKU can I add to one inbound plan?
一个入站计划可以添加多少个 SKU 和每个 SKU 的项目?
一个入站计划可以添加多少个 SKU 和每个 SKU 的项目?
Select to expand the answer.
选择以扩展答案。
For one inbound plan, you can add a maximum of 1,500 SKUs and a maximum of 10,000 items for each SKU.
一个入站计划最多可添加 1,500 个 SKU,每个 SKU 最多可添加 10,000 个项目。
Updated about 6 hours ago 约 6 小时前已更新