An Inbound Plan (also referred to as a Workflow in Amazon's SP-API) is Amazon's modern approach to managing FBA shipments. It represents a logical grouping of one or more shipments that share common characteristics and are processed together in Amazon's fulfillment network.Hierarchy#
Inbound Plans (Workflows)
│
├── Shipments
│ │
│ ├── Shipment Items
│ │ ├── Product Details
│ │ ├── Quantity Information
│ │ └── Preparation Details
│ │
│ └── Shipment Fees
│ ├── Transportation Fees
│ └── Placement Fees
│
└── Plan-level Attributes
├── Destination FC
├── Creation Date
└── Status Timeline
The FBA Inbound Shipments API follows a hierarchical structure that reflects Amazon's inbound fulfillment workflow:Inbound Plans (Workflows) - Top-level container for shipments
Shipments - Individual shipments within a plan
Shipment Items - Products contained within each shipment
Shipment Fees - Cost information associated with shipments
Typical Inbound Plan Workflow#
1.
Plan Creation:
Seller creates an inbound plan in Seller Central or via API
2.
Shipment Preparation:
2.1. Items are added to the plan
2.2. Shipments are created within the plan
2.3. Labeling and preparation occurs
3.
Shipping:
3.1. Carrier information is added
3.2. Shipments are sent to Amazon
4.
Receiving:
4.1. Amazon processes the entire plan
4.2. Updates status as items are receive
API Notes#
FBA Shipment ID Support#
Our API supports both legacy (FBA...
) and new (sh...
) shipment ID formats for backward compatibility
Note: Requests using the old FBA...
format may have slower response times
For some endpoints we provide detailed information that is a combination of legacy API and new.
Accessing Raw SP-API Data#
For complete data access, we provide direct proxy endpoints to Amazon's SP-API under the SP-API FBA Shipments
section. Use these when you need:Data fields not available in our endpoints
Direct access to Amazon's raw API responses
The latest SP-API features before we implement them
Modified at 2025-07-21 12:14:29