Overview

Amazon has opened an early‑access program for the Fulfillment Inbound API version 2024‑03‑20. The refreshed endpoints let sellers programmatically create, modify, and monitor FBA inbound shipments while keeping full parity with the Send to Amazon UI. Early adopters can choose from multiple placement services, edit shipments after creation, and cut down on manual steps in their inbound workflow.

Key Points

• All placement services exposed — The new API lists every inbound option, including Small Parcel, LTL and Amazon‑direct‑store‑delivery, so sellers can select the most cost‑effective method per shipment.
• Two‑way editability — A shipment generated in the Send to Amazon console can be updated via the API, and an API‑created shipment can be edited in the UI, guaranteeing consistent data across both channels.
• Limited early‑access enrollment — Sellers must request entry; approved accounts receive sandbox credentials and a production rollout schedule.
• Improved error diagnostics — Additional response codes and richer messages pinpoint problems such as malformed SKUs or weight limits that exceed carrier thresholds.
• Versioned endpoint coexistence — The v2024‑03‑20 path (e.g., /fba/inbound/v2024-03-20/shipments) runs alongside older versions, allowing a phased migration without breaking existing integrations.
• Flexible shipment interchange — Sellers can pull a shipment’s current state, add or drop inventory units, and even change the destination fulfillment center without recreating the whole shipment.

How the New Fulfillment Inbound API Works

1. Create a shipment plan — Send a POST /shipments call that includes SKU, quantity, and the preferred placement service.

   • Example: A vendor with 150 units of a seasonal candle selects “Small Parcel” and receives a plan that assigns the shipment to the PHX fulfillment center.

2. Confirm the shipment — Invoke to lock the plan and generate carrier labels.