linkfox-amazon-store-fulfillment-outbound

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Amazon 店铺 Fulfillment Outbound

Amazon店铺Fulfillment Outbound

Use this Skill for Amazon Multi-Channel Fulfillment workflows on Fulfillment Outbound

v2026-07-04

. It exposes all nine operations in Amazon's current Outbound model plus the overview page's associated

getInvoiceHeaders

operation from Invoices

v2026-06-25

, while keeping the existing production

linkfox-amazon-store-fba

and

linkfox-amazon-store-external-fulfillment

implementations untouched.

本Skill适用于基于Fulfillment Outbound

v2026-07-04

版本的Amazon Multi-Channel Fulfillment（MCF）工作流。它开放了Amazon当前Outbound模型中的全部9项操作，以及概览页关联的Invoices

v2026-06-25

版本的

getInvoiceHeaders

操作，同时不改动现有生产环境中的

linkfox-amazon-store-fba

和

linkfox-amazon-store-external-fulfillment

实现。

Prerequisites

前置条件

Require linkfox-amazon-store-auth
. Run
```
python scripts/check_auth_dependency.py
```
; exit code
```
42
```
means the dependency must be installed or loaded first.
Select one authorized store and obtain its
```
sellerId
```
and
```
region
```
. Accept only
```
NA
```
,
```
EU
```
, or
```
FE
```
.
Never accept or forward
```
amzAccessToken
```
,
```
accessToken
```
, or
```
refreshToken
```
; the server resolves authorization from
```
sellerId + region
```
.
Read references/api.md for operation contracts and references/workflows.md before a create, update, or cancel action.
After explicit user confirmation, pass boolean
```
confirmWrite: true
```
to
```
createOrder
```
,
```
updateOrder
```
,
```
cancelOrder
```
,
```
updateOrderStatus
```
, or
```
updatePackage
```
; the wrappers reject writes without it.
When Amazon assigned a multi-tenant service identifier, pass it only as top-level
```
fulfillmentServiceId
```
(1–40 characters). The proxy maps it to
```
x-amzn-fulfillment-service-id
```
; never put the raw header name in query or body.

依赖**
```
linkfox-amazon-store-auth
```
**。运行
```
python scripts/check_auth_dependency.py
```
脚本；若退出码为
```
42
```
，则必须先安装或加载该依赖。
选择一个已授权的店铺并获取其
```
sellerId
```
和
```
region
```
。仅接受
```
NA
```
、
```
EU
```
或
```
FE
```
区域。
切勿接受或转发
```
amzAccessToken
```
、
```
accessToken
```
或
```
refreshToken
```
；服务器会通过
```
sellerId + region
```
解析授权信息。
在执行创建、更新或取消操作前，请阅读references/api.md中的操作契约和references/workflows.md中的工作流说明。
获得用户明确确认后，向
```
createOrder
```
、
```
updateOrder
```
、
```
cancelOrder
```
、
```
updateOrderStatus
```
或
```
updatePackage
```
传递布尔值
```
confirmWrite: true
```
；未携带该参数时，包装器会拒绝写入操作。
当Amazon分配了多租户服务标识符时，仅需将其作为顶层参数
```
fulfillmentServiceId
```
（1-40字符）传递。代理会将其映射为
```
x-amzn-fulfillment-service-id
```
；切勿将原始头部名称放入查询参数或请求体中。

调用方式

API 端点：
```
POST /spApi/developerProxy
```
（完整参数/响应/错误码见
```
references/api.md
```
）

Python 脚本：

python scripts/<operation_script>.py '<JSON 参数>' [--inline] [--no-cache]

调用约束：本工具沿用 Amazon Store Skill 的统一免费配置；同一会话同一参数组合默认只调用一次，脚本带 24h 本地缓存。失败/空结果不得自动换参数、翻页或连续试探；需要继续调用时先征得用户同意。

输出策略（脚本默认行为）：

始终将完整响应写入

<cwd>/linkfox/<YYYY-MM-DD>/<session>/data/linkfox-amazon-store-fulfillment-outbound-<timestamp>.json

（

<session>

取自

SESSION_ID

；禁止写入

/tmp

，当前目录不可写则报错）

响应体 ≤ 8 KB：落盘后把完整 JSON 打印到 stdout
响应体 > 8 KB：落盘后 stdout 只输出摘要（顶层字段、常见计数、最大列表字段长度及前 3 条样本）
加
```
--inline
```
强制全量打印到 stdout（同样落盘）
加
```
--no-cache
```
强制本次读/预览操作访问网关；只在用户要求刷新或已确认外部状态变化时使用

读数据建议：先看摘要；需要具体字段时用

jq

或

ConvertFrom-Json

从保存文件按需抽取。

API 端点：
```
POST /spApi/developerProxy
```
（完整参数/响应/错误码见
```
references/api.md
```
）

Python 脚本：

python scripts/<operation_script>.py '<JSON 参数>' [--inline] [--no-cache]

调用约束：本工具沿用 Amazon Store Skill 的统一免费配置；同一会话同一参数组合默认只调用一次，脚本带有24小时本地缓存。失败/空结果不得自动更换参数、翻页或连续试探；需要继续调用时需先征得用户同意。

输出策略（脚本默认行为）：

始终将完整响应写入

<cwd>/linkfox/<YYYY-MM-DD>/<session>/data/linkfox-amazon-store-fulfillment-outbound-<timestamp>.json

（

<session>

取自

SESSION_ID

；禁止写入

/tmp

，当前目录不可写则报错）

响应体 ≤ 8 KB：落盘后把完整 JSON 打印到 stdout
响应体 > 8 KB：落盘后 stdout 只输出摘要（顶层字段、常见计数、最大列表字段长度及前 3 条样本）
加
```
--inline
```
强制全量打印到 stdout（同样落盘）
加
```
--no-cache
```
强制本次读/预览操作访问网关；只在用户要求刷新或已确认外部状态变化时使用

读数据建议：先看摘要；需要具体字段时用

jq

或

ConvertFrom-Json

从保存文件按需抽取。

Operation Guide

操作指南

Stage	Operation	Script	Availability
Quote	`getOffers`	`get_offers.py`	Production
Preview	`getOrderPreview`	`get_order_preview.py`	Production
Create	`createOrder`	`create_order.py`	Production
Read	`getOrder`	`get_order.py`	Production
List	`listOrders`	`list_orders.py`	Production
Release hold / update	`updateOrder`	`update_order.py`	Production
Cancel	`cancelOrder`	`cancel_order.py`	Production
Simulate order status	`updateOrderStatus`	`update_order_status.py`	Amazon dynamic sandbox only
Simulate package status	`updatePackage`	`update_package.py`	Amazon dynamic sandbox only
List invoice headers	`getInvoiceHeaders`	`get_invoice_headers.py`	Production, Invoices v2026-06-25

阶段	操作	脚本	可用性
报价	`getOffers`	`get_offers.py`	生产环境可用
预览	`getOrderPreview`	`get_order_preview.py`	生产环境可用
创建	`createOrder`	`create_order.py`	生产环境可用
查询	`getOrder`	`get_order.py`	生产环境可用
列出	`listOrders`	`list_orders.py`	生产环境可用
解除保留/更新	`updateOrder`	`update_order.py`	生产环境可用
取消	`cancelOrder`	`cancel_order.py`	生产环境可用
模拟订单状态	`updateOrderStatus`	`update_order_status.py`	仅Amazon动态沙箱可用
模拟包裹状态	`updatePackage`	`update_package.py`	仅Amazon动态沙箱可用
列出发票头	`getInvoiceHeaders`	`get_invoice_headers.py`	生产环境可用（Invoices v2026-06-25）

Workflow Rules

工作流规则

Use
```
getOffers
```
for multi-SKU delivery options and expiration times; use
```
getOrderPreview
```
for planned shipments, fees, constraints, and fulfillability.
Show the chosen store, destination, line items, service tier, fees, hold/ship action, and
```
orderId
```
before
```
createOrder
```
.
Treat
```
orderId
```
and every
```
lineItemId
```
as seller-controlled idempotency identifiers. Never invent a replacement ID after an uncertain timeout.
A
```
createOrder
```
response can be HTTP 200 or 202. On 202, use the returned/requested
```
orderId
```
with
```
getOrder
```
; do not automatically poll.
Use
```
updateOrder
```
only to update the supported fulfillment configuration, currently the HOLD/SHIP action. Confirm before releasing a held order.
Confirm before
```
cancelOrder
```
. Amazon only stops fulfillment where cancellation is still possible; do not present 202 as completed cancellation.
Add
```
shipments: "INCLUDE"
```
to
```
getOrder
```
or
```
listOrders
```
when package and tracking details are needed.
Never automatically replay POST/PUT after 429, 500, 503, or a timeout. Recover with
```
getOrder
```
where possible.
Use
```
getInvoiceHeaders
```
only for header-level invoice discovery. Require
```
marketplaceId
```
; provide both issue-date bounds or neither, keep the range within 90 days, and page with
```
nextToken
```
only after user approval.

使用
```
getOffers
```
获取多SKU配送选项及有效期；使用
```
getOrderPreview
```
查看计划发货信息、费用、约束条件及可履约状态。
在执行
```
createOrder
```
前，展示所选店铺、目的地、商品明细、服务等级、费用、保留/发货操作及
```
orderId
```
。
将
```
orderId
```
和每个
```
lineItemId
```
视为卖家控制的幂等标识符。在超时不确定的情况下，切勿自行生成替代ID。
```
createOrder
```
的响应可能是HTTP 200或202。若为202，使用返回/请求的
```
orderId
```
调用
```
getOrder
```
；请勿自动轮询。
仅可使用
```
updateOrder
```
更新支持的履约配置，目前仅支持保留/发货操作的更新。解除订单保留前需确认。
执行
```
cancelOrder
```
前需确认。Amazon仅会在仍可取消的情况下停止履约；请勿将202状态视为取消完成。
当需要包裹和跟踪详情时，在
```
getOrder
```
或
```
listOrders
```
中添加
```
shipments: "INCLUDE"
```
参数。
遇到429、500、503状态码或超时后，切勿自动重放POST/PUT请求。尽可能通过
```
getOrder
```
恢复状态。
仅可使用
```
getInvoiceHeaders
```
进行发票头级别的发票查询。需提供
```
marketplaceId
```
；要么同时提供开票日期范围，要么都不提供，且范围需在90天内；仅在获得用户批准后，使用
```
nextToken
```
进行分页查询。

Important Limitations

重要限制

```
updateOrderStatus
```
and
```
updatePackage
```
are marked
```
x-amzn-api-sandbox-only: true
```
by Amazon. Consistent with the existing FBA skill, their wrappers use the same
```
/spApi/developerProxy
```
request shape as every other operation and do not accept or send a separate
```
sandbox
```
control field. Use them only with sandbox test data; availability depends on the unified gateway/upstream route.
The optional
```
x-amzn-fulfillment-service-id
```
multi-tenant header is exposed only through the typed top-level
```
fulfillmentServiceId
```
parameter. Raw header names, nested aliases, blank values, values over 40 characters, and newline characters are rejected before calling the gateway.
Amazon's Outbound overview role list mentions
```
getInvoiceHeaders
```
, but its Reference path is
```
/finances/invoices/2026-06-25/invoices
```
. This Skill exposes it as an explicitly labeled related Invoices operation; it is not counted among the nine Outbound OpenAPI operations and does not accept
```
fulfillmentServiceId
```
.
Legacy v2020-07-01 returns, features, and package-tracking operations remain in the production FBA Skill and are not copied into this current-version Skill. Read references/migration.md when migrating.

Amazon将
```
updateOrderStatus
```
和
```
updatePackage
```
标记为
```
x-amzn-api-sandbox-only: true
```
。与现有FBA Skill一致，它们的包装器使用与其他操作相同的
```
/spApi/developerProxy
```
请求格式，且不接受或发送单独的
```
sandbox
```
控制字段。仅可在沙箱测试数据中使用这些操作；可用性取决于统一网关/上游路由。
可选的多租户头部
```
x-amzn-fulfillment-service-id
```
仅通过类型化的顶层参数
```
fulfillmentServiceId
```
暴露。原始头部名称、嵌套别名、空值、超过40字符的值及换行符会在调用网关前被拒绝。
Amazon的Outbound概览角色列表中提到了
```
getInvoiceHeaders
```
，但其参考路径为
```
/finances/invoices/2026-06-25/invoices
```
。本Skill将其作为明确标记的关联Invoices操作开放；它不属于Outbound OpenAPI的9项操作，且不接受
```
fulfillmentServiceId
```
参数。
旧版v2020-07-01的返回结果、功能及包裹跟踪操作仍保留在生产环境的FBA Skill中，未复制到当前版本的Skill中。迁移时请阅读references/migration.md。

Display Rules

展示规则

Present Amazon data and identifiers without exposing internal tool names or access tokens.
Separate operation success from business completion: show gateway
```
errcode
```
, Amazon
```
httpStatus
```
, order
```
status
```
, constraints, and next action.
For offers and previews, show expiration, service tier, delivery interval, currency, price, and item constraints together.
For orders, show
```
orderId
```
, status, line items, shipments, packages, tracking, proof of delivery, drop-off/locker details, unit identifiers, and pagination token only when present.

展示Amazon数据和标识符时，不得暴露内部工具名称或访问令牌。
区分操作成功与业务完成：展示网关
```
errcode
```
、Amazon
```
httpStatus
```
、订单
```
status
```
、约束条件及下一步操作。
对于报价和预览信息，需同时展示有效期、服务等级、配送区间、货币、价格及商品约束条件。
对于订单信息，仅当存在
```
orderId
```
、状态、商品明细、发货信息、包裹、跟踪信息、签收证明、自提点/储物柜详情、商品标识符及分页令牌时才展示。

User Expression

用户指令示例

Ask: “Check MCF delivery options for these Amazon SKUs to this postal code.”

Do: use

getOffers

; do not create an order.

Ask: “Preview and then create this MCF order.”

Do: run

getOrderPreview

, present constraints and fees, obtain confirmation, then run

createOrder

once.

Ask: “Track my MCF order.”

Do: run

getOrder

with

shipments: "INCLUDE"

; do not call the legacy tracking operation.

用户提问：“查询这些Amazon SKU配送至该邮政编码的MCF配送选项。”

执行操作：调用

getOffers

；请勿创建订单。

用户提问：“预览并创建这个MCF订单。”

执行操作：先调用

getOrderPreview

，展示约束条件和费用，获得确认后，再调用一次

createOrder

。

用户提问：“跟踪我的MCF订单。”

执行操作：调用带有

shipments: "INCLUDE"

参数的

getOrder

；请勿调用旧版跟踪操作。

Feedback

反馈方式

Report issues with

skillName: linkfox-amazon-store-fulfillment-outbound

, operation, masked IDs, resolved path, gateway status, and Amazon response summary. Never include credentials.

反馈问题时请提供

skillName: linkfox-amazon-store-fulfillment-outbound

、操作名称、脱敏后的ID、已解析路径、网关状态及Amazon响应摘要。切勿包含凭证信息。

积分消耗规则

不消耗积分（以网关实际计费为准）。

更多跨境 Skill：LinkFox Skills

不消耗积分（以网关实际计费为准）。

更多跨境 Skill：LinkFox Skills