SP-API Update: New 'PendingSchedule' Status Coming for Easy Ship Orders on June 11
On 11 June 2025 Amazon will add a new ShipmentStatus value “PendingSchedule” to SP‑API getOrder/getOrders for Easy Ship orders awaiting carrier assignment. The status will automatically change to “ReadyForPickUp” once a carrier is assigned. Sellers must update parsing logic before the compliance deadline to avoid misrouting.
Overview
On 11 June 2025 Amazon will add a new shipment status called PendingSchedule for Easy Ship orders. The status appears in the SP‑API getOrder and getOrders responses whenever an Easy Ship order has been placed but a carrier has not yet been assigned. Sellers and developers need to update their order‑processing logic to recognize this value, or risk misclassifying early‑stage Easy Ship shipments.
Key Points
- New enum entry — The
ShipmentStatusfield will return the literal string “PendingSchedule” for Easy Ship orders that are waiting for carrier assignment. - Automatic state change — As soon as Amazon’s logistics system assigns a carrier, the status flips to “ReadyForPickUp” without any additional API request from the seller.
- Marketplace coverage — The rollout will be simultaneous across all North American (US, CA, MX) and European (DE, FR, IT, ES, UK) marketplaces, meaning every seller with Easy Ship enabled will see the same value.
- Compliance deadline — All integrations must be able to parse and handle “PendingSchedule” by 11 June 2025; otherwise parsing errors may cause orders to be routed to the wrong fulfillment queue.
- Clear early‑stage signal — The new status eliminates the need for developers to infer the early Easy Ship stage from a combination of
FulfillmentChanneland missing later statuses. - No extra polling required — Because the transition to “ReadyForPickUp” is automatic, sellers do not need to call a separate endpoint to learn when a carrier has been scheduled.
How the New PendingSchedule Status Works
-
Order creation — When a buyer selects Easy Ship at checkout, Amazon records the order but does not yet assign a carrier.
- Example: A seller receives an order for a set of silicone baking mats; the
getOrderpayload now contains"ShipmentStatus":"PendingSchedule"indicating the order is in the scheduling queue.
- Example: A seller receives an order for a set of silicone baking mats; the
Analysis & Recommendations
Why This Matters
The “PendingSchedule” status gives a definitive signal that an Easy Ship order is waiting for carrier assignment, eliminating the need to infer from FulfillmentChannel. Without handling it, orders may be placed in the wrong fulfillment queue, alerts may fire incorrectly, and analytics dashboards will miss a new category, leading to operational delays.
Key Takeaways
- A new enum entry “PendingSchedule” will appear in the ShipmentStatus field for Easy Ship orders starting 11 June 2025.
- The status automatically flips to “ReadyForPickUp” when Amazon assigns a carrier, requiring no extra API call.
- The rollout covers all North American (US, CA, MX) and European (DE, FR, IT, ES, UK) marketplaces, and compliance is required by 11 June 2025.
Recommended Actions
- →Update code to include a branch for `ShipmentStatus == "PendingSchedule"` in order‑processing services (e.g., in your Python microservice).
- →Test the new flow in the SP‑API sandbox: create an Easy Ship test order via Seller Central > Developer Console > Sandbox, poll `getOrder` and verif...
- →Modify warehouse alerts and customer‑facing messages in Seller Central > Settings > Notifications to display “Your shipment is being scheduled” whe...
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!