Added to Amalert: Jan 30, 2026
SP-API Update: Fulfillment Outbound API Now Returns Tracking Numbers for MCF Orders
The SP‑API Fulfillment Outbound getFulfillmentOrder call now returns an "amazonTrackingNumber" field (e.g., "TBA123456789US") for every Multi‑Channel Fulfillment shipment. Sellers can immediately feed this ID into GET /shipping/v1/tracking to obtain carrier details, cutting the lookup steps from multiple calls to a single request.
Overview
Amazon’s Selling Partner API (SP‑API) has added native tracking number support to the Fulfillment Outbound API for Multi‑Channel Fulfillment (MCF) orders. As of the latest release, the getFulfillmentOrder call now returns an amazonTrackingNumber field, allowing sellers to retrieve MCF tracking data programmatically without extra lookups. This change shortens the time between shipment creation and customer notification, a critical factor for sellers who fulfill orders from external platforms such as Shopify or WooCommerce.
Key Points
- New
amazonTrackingNumberfield — ThegetFulfillmentOrderresponse now includes a tracking identifier for every MCF shipment that has been assigned a number. - Two‑step tracking flow — Sellers can feed the returned tracking number into the
getTrackingendpoint to obtain carrier details, event history, and estimated delivery dates. - MCF‑focused visibility — The enhancement mirrors the tracking experience already available for Amazon marketplace orders, eliminating the previous gap for off‑Amazon sales.
- Unified response payload — Tracking data is embedded directly within the fulfillment order object, keeping the API schema unchanged and reducing integration overhead.
- Real‑time assignment — Tracking numbers appear as soon as Amazon’s fulfillment network generates them, enabling faster automated communications.
How the Update Works
-
Request fulfillment order — Call
getFulfillmentOrderwith the specific fulfillment order ID.- Example: A seller submits
GET /fba/outbound/v0/fulfillmentOrders/1234567890and receives a JSON payload that now contains"amazonTrackingNumber": "TBA123456789US".
- Example: A seller submits
-
Extract tracking number — Parse the response to capture the
amazonTrackingNumbervalue.
Analysis & Recommendations
Why This Matters
Embedding the tracking number in the fulfillment order response eliminates the manual Seller Central lookup and the previous multi‑call workflow, saving API quota and reducing latency to minutes. This enables faster automated customer notifications and real‑time dashboard updates for MCF orders shipped from external platforms like Shopify.
Key Takeaways
- New field "amazonTrackingNumber" appears in getFulfillmentOrder responses for MCF shipments.
- Example tracking ID format: "TBA123456789US" returned alongside order ID 1234567890.
- Sellers can call GET /shipping/v1/tracking/<amazonTrackingNumber> to retrieve carrier events and estimated delivery.
- If amazonTrackingNumber is null, a retry should be scheduled after 30 minutes (expedited) or 2 hours (standard).
Recommended Actions
- →Update your integration code to parse and store the amazonTrackingNumber field from getFulfillmentOrder responses.
- →Add logic to call GET /shipping/v1/tracking with the retrieved ID and push the carrier link (e.g., https://track.amazon.com/TBA123456789US) to your...
- →Implement a retry scheduler in your system to re‑query getFulfillmentOrder after 30 minutes or 2 hours when amazonTrackingNumber is missing.
Comments
Join the discussion
Log in or create an account to share your thoughts on this update.
No comments yet. Be the first to share your thoughts!