亚马逊-店铺Fulfillment Outbound

亚马逊 Multi-Channel Fulfillment（MCF）新版出仓履约管理。用于获取配送报价和订单预览，创建、查询、列出、更新或取消履约订单，查看包裹与跟踪、签收证明、投递照片、收件人及 locker/drop-off 信息，并查询相关发票头。用户提到 Fulfillment Outbound、MCF、多渠道配送、亚马逊库存配送到站外客户、配送报价、getOffers、getOrderPreview、createOrder、getInvoiceHeaders、receivedBy、unitIdentifiers、v2026-07-04 时触发。即使未明确说“MCF API”，只要希望用亚马逊库存履约非亚马逊渠道订单，也应触发此技能；External Fulfillment、普通 Orders API 和旧版 v2020-07-01 不属于此技能。

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.

Prerequisites

1. Require linkfox-amazon-store-auth. Run python scripts/check_auth_dependency.py; exit code 42 means the dependency must be installed or loaded first.
2. Select one authorized store and obtain its sellerId and region. Accept only NA, EU, or FE.
3. Never accept or forward amzAccessToken, accessToken, or refreshToken; the server resolves authorization from sellerId + region.
4. Read references/api.md for operation contracts and references/workflows.md before a create, update, or cancel action.
5. After explicit user confirmation, pass boolean confirmWrite: true to createOrder, updateOrder, cancelOrder, updateOrderStatus, or updatePackage; the wrappers reject writes without it.
6. 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.

调用方式

• 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 从保存文件按需抽取。

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

Workflow Rules

1. Use getOffers for multi-SKU delivery options and expiration times; use getOrderPreview for planned shipments, fees, constraints, and fulfillability.
2. Show the chosen store, destination, line items, service tier, fees, hold/ship action, and orderId before createOrder.
3. Treat orderId and every lineItemId as seller-controlled idempotency identifiers. Never invent a replacement ID after an uncertain timeout.
4. A createOrder response can be HTTP 200 or 202. On 202, use the returned/requested orderId with getOrder; do not automatically poll.
5. Use updateOrder only to update the supported fulfillment configuration, currently the HOLD/SHIP action. Confirm before releasing a held order.
6. Confirm before cancelOrder. Amazon only stops fulfillment where cancellation is still possible; do not present 202 as completed cancellation.
7. Add shipments: "INCLUDE" to getOrder or listOrders when package and tracking details are needed.
8. Never automatically replay POST/PUT after 429, 500, 503, or a timeout. Recover with getOrder where possible.
9. 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.

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.

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.

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.

Feedback

Report issues with skillName: linkfox-amazon-store-fulfillment-outbound, operation, masked IDs, resolved path, gateway status, and Amazon response summary. Never include credentials.

Amazon SP-API 接口保护与重试指引

同一店铺连续收到 Amazon SP-API 的 400、403、404 或 429 时，网关会返回 450、453、454 或 459 并短暂冷却。这些自定义状态码不是 Amazon 原生状态，也不表示封号；目的是避免持续异常或高频调用扩大店铺风险。

状态与 message	范围	触发与冷却	处理
450：400，请求异常，请优化您的参数	店铺+接口	60 秒内超过 3 次：5 分钟；10 分钟内超过 4 次：20 分钟	停止原参数重试，检查必填字段、marketplace、ID、日期和请求体
453：403，店铺未授权，请先授权	店铺全部接口	60 秒内超过 2 次：5 分钟；10 分钟内超过 4 次：30 分钟	停止该店铺调用，检查授权、权限、店铺归属和区域
454：404，资源不存在，请优化您的参数	店铺+接口	60 秒内超过 3 次：5 分钟；10 分钟内超过 4 次：30 分钟	确认资源 ID、所属店铺/站点、资源状态和接口路径
459：429限流中，请降低频率	店铺+接口	首次：15 秒；2 分钟内超过 2 次：30 秒；3 分钟内超过 4 次：2 分钟	降低并发、分页和轮询频率并逐级退避

• 立即停止自动或并发重试，不得通过换脚本或重复创建任务绕过保护；优先遵循 retryAfter、blockedUntil，没有时按表中时长说明。
• 450/453/454 必须先修正参数、授权或资源标识，冷却后最多谨慎重试一次；再次触发则停止调用。453 期间停止该店铺全部 SP-API。
• 保留已有 reportId、feedId 等任务 ID；写操作结果不确定时先查询状态，不直接重放。
• 向用户先说明店铺保护，再给原因、处理和等待时间。可回复：“为保护您的亚马逊店铺安全，检测到 Amazon SP-API 连续返回{原因}，当前已进入短暂保护。请先{处理动作}，预计{等待时间}后再试；这不代表封号，也不是套餐或算力限制。”不要只说“LinkFox 限流”或“服务器繁忙”。

算力消耗规则

不消耗算力（以网关实际计费为准）。

---

更多跨境 Skill：LinkFox Skills