Selling Partner APIs for Fulfillment Outbound

Name: Selling Partner APIs for Fulfillment Outbound API
Brand: Selling Partner APIs for Fulfillment Outbound
Availability: InStock

✓ Official Vendor SpecE CommerceOrder Managementoauth214 EndpointsREST

For Agents

Quickstart

Get started with Selling Partner APIs for Fulfillment Outbound in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create a Multi-Channel Fulfillment order on Amazon"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Selling Partner APIs for Fulfillment Outbound API.

Generate fulfillment previews and delivery offers for a basket of SKUs before committing to an order

Create, list, retrieve, update, and cancel Multi-Channel Fulfillment orders shipped from Amazon FBA inventory

Submit fulfillment order status updates and return requests against existing seller fulfillment orders

Fetch carrier tracking details for shipped MCF packages by package number

GET STARTED

Start building with Selling Partner APIs for Fulfillment Outbound API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Selling Partner APIs for Fulfillment Outbound API for, with concrete tasks.

★ Direct-to-Consumer Order Fulfillment from FBA

Brands selling on Shopify, BigCommerce, or their own storefront can route orders to Amazon's fulfillment network using the Multi-Channel Fulfillment API. The integration creates a seller fulfillment order with the buyer's address, line items, and chosen shipping speed, then pulls tracking once Amazon hands the package to the carrier. Setup typically takes one to two weeks including LWA app authorization.

Create a fulfillment order with sellerFulfillmentOrderId 'SHOP-12345', shipping speed 'Standard', destination address in the US, and a single SKU 'SKU-ABC' at quantity 2 via POST /fba/outbound/2020-07-01/fulfillmentOrders

Pre-Checkout Delivery Quotes

E-commerce checkouts can call the deliveryOffers endpoint to show buyers accurate delivery dates and shipping speed options sourced from Amazon's network before they pay. The response returns expected ship and delivery windows per offered speed, so the storefront can charge correctly and set realistic expectations. Most teams wire this in alongside cart updates in a few days.

Call POST /fba/outbound/2020-07-01/deliveryOffers with the buyer's postal code and a list of SKU/quantity pairs and return the earliest available delivery date for the 'Priority' shipping speed

Returns and Tracking Sync to Helpdesk

Customer support tools can pull MCF tracking details and submit return requests so agents do not have to swivel-chair into Seller Central. The integration listens for buyer return tickets, calls createFulfillmentReturn with the right reason code, and posts status updates back into the helpdesk thread. Reason codes are pulled from listReturnReasonCodes per SKU.

Look up valid return reason codes for sellerSku 'SKU-ABC', then call PUT /fba/outbound/2020-07-01/fulfillmentOrders/{sellerFulfillmentOrderId}/return with reason code 'CR-DAMAGED' for two units

AI Agent Order Operations

AI agents handling seller-side operations can use this API through Jentic to manage MCF orders end-to-end without storing Amazon LWA refresh tokens in the agent context. The agent searches Jentic for the right operation, loads the input schema, and executes against a scoped credential held in the Jentic vault. Useful for ops copilots that triage stuck shipments and trigger cancellations or updates.

Find the open fulfillment order with sellerFulfillmentOrderId 'SHOP-12345', cancel it via PUT /fba/outbound/2020-07-01/fulfillmentOrders/{sellerFulfillmentOrderId}/cancel, and confirm the new status is 'Cancelled'

Key Endpoints

14 endpoints — the selling partner api for fulfillment outbound lets amazon sellers create, preview, and manage multi-channel fulfillment (mcf) orders that ship from inventory already stored in amazon's fulfillment network.

METHOD

PATH

DESCRIPTION

POST

/fba/outbound/2020-07-01/fulfillmentOrders

Create a Multi-Channel Fulfillment order

POST

/fba/outbound/2020-07-01/fulfillmentOrders/preview

Preview a fulfillment order before committing

POST

/fba/outbound/2020-07-01/deliveryOffers

Get shipping speed and delivery date offers

GET

/fba/outbound/2020-07-01/fulfillmentOrders

List existing fulfillment orders

GET

/fba/outbound/2020-07-01/fulfillmentOrders/{sellerFulfillmentOrderId}

Get a single fulfillment order

PUT

/fba/outbound/2020-07-01/fulfillmentOrders/{sellerFulfillmentOrderId}/cancel

Cancel a fulfillment order

PUT

/fba/outbound/2020-07-01/fulfillmentOrders/{sellerFulfillmentOrderId}/return

Create a return on a fulfillment order

GET

/fba/outbound/2020-07-01/tracking

Get package tracking details

POST

/fba/outbound/2020-07-01/fulfillmentOrders

Create a Multi-Channel Fulfillment order

POST

/fba/outbound/2020-07-01/fulfillmentOrders/preview

Preview a fulfillment order before committing

POST

/fba/outbound/2020-07-01/deliveryOffers

Get shipping speed and delivery date offers

GET

/fba/outbound/2020-07-01/fulfillmentOrders

List existing fulfillment orders

GET

/fba/outbound/2020-07-01/fulfillmentOrders/{sellerFulfillmentOrderId}

Get a single fulfillment order

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Amazon LWA refresh tokens and the IAM role used to sign Selling Partner requests are stored encrypted in the Jentic vault. Agents receive a short-lived, scoped access token at execution time — the long-lived refresh token never enters the agent context.

Intent-based discovery

Agents search Jentic by intent (e.g. 'create a Multi-Channel Fulfillment order' or 'cancel a seller fulfillment order') and Jentic returns the matching Selling Partner operation with its input schema, so the agent calls the right path without browsing the Amazon developer docs.

Time to first call

Direct Selling Partner integration: 1-2 weeks for LWA app registration, IAM role setup, request signing, and rate-limit handling. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

ShipStation

Multi-carrier shipping platform that aggregates UPS, USPS, FedEx, and DHL instead of routing through Amazon FBA

Choose ShipStation when the seller wants to fulfill from their own warehouse or 3PL with multiple carriers; choose Amazon MCF when fulfilling from existing FBA inventory

Alternative

ShipEngine

Carrier-agnostic shipping API for label generation and rate shopping outside the Amazon network

Pick ShipEngine when the agent needs to compare rates across multiple carriers; pick Amazon MCF for FBA-stocked items shipped to non-Amazon channels

Complementary

Shippo

Shipping label and tracking API often used alongside MCF for non-FBA orders

Use Shippo when the order cannot be routed through FBA (out-of-stock SKU, oversize item) so the agent can fall back to a third-party label

Complementary

FedEx

Direct carrier API for tracking and rate quotes when the MCF carrier is FedEx

Useful for richer tracking detail than the MCF tracking endpoint exposes when FedEx is the assigned carrier

FAQs

Specific to using Selling Partner APIs for Fulfillment Outbound API through Jentic.

What authentication does the Selling Partner Fulfillment Outbound API use?

The Amazon Selling Partner API uses Login with Amazon (LWA) OAuth 2.0. Agents exchange a refresh token for a short-lived access token sent in the x-amz-access-token header on each request. Through Jentic, the LWA refresh token is held in the Jentic vault and never enters the agent's context — only scoped, short-lived access tokens are injected at call time.

Can I create Multi-Channel Fulfillment orders with this API?

Yes. POST /fba/outbound/2020-07-01/fulfillmentOrders creates a seller fulfillment order against the seller's existing FBA inventory, with a destination address, line items, shipping speed, and a sellerFulfillmentOrderId you supply. POST /fba/outbound/2020-07-01/fulfillmentOrders/preview returns delivery and fee estimates first if you want to confirm before committing.

What are the rate limits for the Selling Partner Fulfillment Outbound API?

Amazon publishes per-operation rate plans rather than a single global limit. Most outbound fulfillment operations sit at 2 requests per second with a burst of 30, but createFulfillmentReturn and getFulfillmentPreview are lower. Check the Selling Partner API documentation for the live numbers per operation, since Amazon adjusts them.

How do I cancel a fulfillment order through Jentic?

Search Jentic for 'cancel a Multi-Channel Fulfillment order'. Jentic returns the operation backed by PUT /fba/outbound/2020-07-01/fulfillmentOrders/{sellerFulfillmentOrderId}/cancel, you load the schema (the only input is the sellerFulfillmentOrderId), and execute. The Jentic SDK handles the LWA token exchange so the agent never sees the refresh token.

Does this API cover inbound shipments to Amazon warehouses?

No. This spec is the Fulfillment Outbound API only — orders shipping out of FBA to a buyer. Inbound shipments to Amazon warehouses are covered by the separate Selling Partner Fulfillment Inbound API. Order placement on amazon.com itself is also out of scope; this is for sellers fulfilling their own non-Amazon channels via Amazon's network.

Can I get carrier tracking through this API?

Yes. GET /fba/outbound/2020-07-01/tracking returns carrier name, tracking number, current status, and event history for an MCF package. You pass the packageNumber (returned on the fulfillment order) and Amazon returns the latest scan events.