Amazon Store Fulfillment Inbound

This Skill covers 45 operations of Amazon Fulfillment Inbound

v2024-03-20

, as well as 6

v0

query/document operations that still need to be used with new processes. All requests continue to use the production link of the Amazon Store series:

POST /spApi/developerProxy

, with authorization resolved by the server via

sellerId + region

Prerequisites (Must Read First)

This Skill depends on linkfox-amazon-store-auth
. Run
```
python scripts/check_auth_dependency.py
```
first; if the exit code is
```
42
```
and stderr contains
```
DEPENDENCY_MISSING:
```
, install or load this dependency first.
Select a store via the auth Skill to obtain
```
sellerId
```
and
```
region
```
.
```
region
```
only allows
```
NA
```
,
```
EU
```
,
```
FE
```
.
Do not receive, store, or transmit
```
amzAccessToken
```
,
```
accessToken
```
,
```
refreshToken
```
. Do not allow callers to override Amazon
```
path
```
,
```
method
```
or gateway
```
queryString
```
.
Read the grouped documentation matching the task first; the complete contract entry is available at references/api.md.

Calling Methods

API Endpoint:
```
POST /spApi/developerProxy
```
(complete parameters/responses/error codes can be found in
```
references/api.md
```
)

Python Script:

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

Calling Constraints: This tool follows the unified free configuration of Amazon Store Skills; the same parameter combination in the same session is only called once by default, with the script having a 24h local cache. Do not automatically change parameters, paginate, or continuously retry on failure/empty results; obtain user consent before proceeding with further calls.

Output Strategy (Default Script Behavior):

Always write the complete response to
```
<cwd>/linkfox/<YYYY-MM-DD>/<session>/data/linkfox-amazon-store-fulfillment-inbound-<timestamp>.json
```
(
```
<cwd>
```
is the working directory when the script is executed,
```
<session>
```
is taken from the environment variable
```
SESSION_ID
```
; writing to
```
/tmp
```
is prohibited, and an error will be reported if the current directory is not writable)
Response body ≤ 8 KB: Print the complete JSON to stdout after saving to disk
Response body > 8 KB: Print only a summary (top-level fields, common counts, maximum list field length and first 3 samples) to stdout after saving to disk
Add
```
--inline
```
to force full printing to stdout (still saves to disk)
Add
```
--no-cache
```
to force the current read/generation operation to access the gateway; only use when the user requests a refresh or confirms external state changes

Data Reading Suggestion: Check the summary first to see if it is sufficient; when specific fields are needed, prefer to extract them from the saved JSON file using

jq

ConvertFrom-Json

as needed, avoiding loading the entire JSON into context.

Working Mechanism

Each public script represents only one fixed operation, and executes at most one gateway call per run. The unified executor is responsible for:

Validating public fields, path/query/body, enums, pagination limits and key nested constraints;
Performing percent-encoding on path segments and query parameters;
Mapping lowerCamelCase parameters from v0 CLI to PascalCase wire names required by Amazon;
Identifying 200/201/202/204 successful responses and parsing JSON;
Returning explicit
```
nextAction
```
for asynchronous responses, but not automatically polling;
Saving the complete response, and only displaying a summary in stdout for large responses.

Calling Format:

bash

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

Public Parameters:

Parameter	Required	Description
`sellerId`	Yes	Authorized Seller ID
`region`	Yes	`NA` / `EU` / `FE`
path/query parameters	Conditional	Use lowerCamelCase names from each operation's documentation
`requestBody`	Conditional	Amazon JSON body; it is recommended to explicitly pass this object, and it is also compatible with placing body fields at the top level
`confirmWrite`	Required for submission operations	Pass the boolean value `true` after the user explicitly confirms the target and selection; the script will reject the gateway call if this value is missing for 8 deterministic submission operations
`skipDepCheck`	No	Only for local debugging

Examples:

bash

python scripts/get_inbound_plan.py '{"sellerId":"A1...","region":"NA","inboundPlanId":"wf12345678-1234-1234-1234-123456789012"}'

python scripts/create_inbound_plan.py '{"sellerId":"A1...","region":"NA","requestBody":{"destinationMarketplaces":["ATVPDKIKX0DER"],"items":[{"labelOwner":"AMAZON","msku":"SKU-1","prepOwner":"SELLER","quantity":10}],"sourceAddress":{"name":"Warehouse","addressLine1":"1 Main St","city":"Seattle","countryCode":"US","phoneNumber":"+1-206-555-0100","postalCode":"98101","stateOrProvinceCode":"WA"}}}'

python scripts/get_labels.py '{"sellerId":"A1...","region":"NA","shipmentConfirmationId":"FBA...","pageType":"PackageLabel_Letter_2","labelType":"UNIQUE"}'

Selecting Operations

Group	Purpose	Detailed Parameters & Scripts
Inbound Plans	Create, read, cancel, rename, view plan content	inbound-plans.md
Packing	Generate/confirm packing plans, submit box specifications, view packing groups	packing.md
Placement	Generate, list, confirm placement plans	placement.md
Shipments	Read shipments, boxes/items/pallets, names and addresses, tracking	shipments.md
Content Updates	Preview and confirm content changes for existing shipments	shipment-content-updates.md
Delivery	Delivery windows and delivery challans	delivery-windows-and-documents.md
Self-Ship	Self-ship appointment slots and bookings for India	self-ship-appointments.md
Transportation	Generate, compare, confirm transportation solutions	transportation.md
Prep / Compliance / Labels	Prep work, compliance, and product labels	prep-compliance-labels.md
Async Status	Query the execution status of `operationId`	asynchronous-operations.md
Retained v0	Prep instructions, box labels, BOL, legacy shipment queries	legacy-v0.md

Execution Rules

First confirm the current workflow stage and existing IDs; see references/identifiers.md for ID sources and cross-version mappings. When there are existing plans/shipments, prioritize read-only recovery and avoid duplicate creation.
Confirm user intent and target store before write operations. The following 8 deterministic submission operations must display key selections to the user and obtain explicit confirmation before execution:
```
cancelInboundPlan
```
,
```
confirmPackingOption
```
,
```
confirmPlacementOption
```
,
```
confirmShipmentContentUpdatePreview
```
,
```
confirmDeliveryWindowOptions
```
,
```
cancelSelfShipAppointment
```
,
```
scheduleSelfShipAppointment
```
,
```
confirmTransportationOptions
```
.
```
confirmTransportationOptions
```
may involve transportation fees; display the option, fee, currency, time limit, and expiration for each shipment before confirmation. Do not select paid items by default for users.
After 19 asynchronous initiation operations return
```
operationId
```
, only call
```
get_inbound_operation_status.py
```
to query. Stop and inform the user to check later when the status is
```
IN_PROGRESS
```
; display
```
operationProblems
```
when
```
FAILED
```
, and do not proceed to downstream write steps; only continue when
```
SUCCESS
```
.
The script layer does not automatically paginate, poll, retry with different parameters, or replay POST/PUT requests. The existing gateway will only refresh the token and transparently retry once when token expiration is detected; when results are uncertain due to 429/500/503 or timeout, prioritize restoring status via status/read operations.
A 204 empty body for
```
updateInboundPlanName
```
and
```
updateShipmentName
```
indicates success and should not be treated as a parsing failure.
```
getLabels
```
/
```
getBillOfLading
```
must use the
```
shipmentConfirmationId
```
returned by
```
getShipment
```
; the script also accepts this alias. Download URLs may expire quickly, so download immediately after obtaining them and do not save the URLs for long-term use.

Complete standard paths, Pack Later, India, self-carrier, and shipment content update processes can be found in references/workflows.md. Marketplace restrictions are available in references/marketplace-constraints.md.

Output & Error Handling

The complete response is saved to

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

; stdout will print the actual path.

Print the complete JSON when the response does not exceed 8 KB; print a summary for larger responses;
```
--inline
```
forces printing of the complete JSON.
Always check
```
developerProxy.errcode
```
first, then
```
httpStatus
```
, and finally read the operation result fields.
Handle 401/402, API Key, authorization, points or balance issues according to references/onboarding.md.
When Amazon returns 400/403/404/409/413/415/422, correct the input or process status and let the user decide whether to call again.

Reference Routes

Fields, responses, pagination, error semantics: Read references/api.md.
Business process selection: Read references/workflows.md.
ID generation and v2024/v0 mapping: Read references/identifiers.md.
Country/market differences: Read references/marketplace-constraints.md.
Method/path/body/script for a specific operation: Only read the corresponding grouped documentation in
```
references/apis/*.md
```
.

For issue feedback, use

skillName: linkfox-amazon-store-fulfillment-inbound

, and attach the desensitized operation, associated ID, and

developerProxy

response.

Points Consumption Rules

No points are consumed (subject to actual gateway billing).

More cross-border Skills: LinkFox Skills

linkfox-amazon-store-fulfillment-inbound

NPX Install

Tags

SKILL.md Content (Chinese)