Send to Amazon will replace the send/replenish workflow for API-created shipments
On March 1 2023 Amazon retired the MWS/SP‑API send/replenish endpoints, making the Send to Amazon web UI the sole method for creating inbound shipments. After a shipment is created in the UI it can no longer be fetched, updated, or deleted via any API, and calls to the old endpoints now return “InvalidShipmentId” errors.
Overview
On March 1 2023 Amazon discontinued the legacy “send/replenish” flow that developers accessed through MWS and the SP‑API. The new “Send to Amazon” web interface now serves as the exclusive method for creating and managing inbound shipments. Sellers who depend on automated pipelines must shift to the UI‑based process or risk inbound disruptions.
Key Points
- Effective date — Starting March 1 2023 the Send to Amazon tool replaces every API‑driven send/replenish operation for all sellers.
- Universal scope — The change covers inbound shipments of any size, product category, or fulfillment program that were previously generated via the API.
- API blackout — After a shipment is created, viewed, or edited in the Send to Amazon UI, it can no longer be fetched, updated, or deleted through any MWS or SP‑API endpoint.
- Legacy shipments — Inbound plans that were fully processed before the cutoff remain unchanged; any new inbound activity must originate from the Send to Amazon interface.
- Consolidated workflow — Label creation, carrier selection, and shipment confirmation are now performed in a single web‑based wizard, eliminating the need for multiple API calls.
How Send to Amazon Works
- Create shipment in the UI — The seller signs into Seller Central, opens the “Send to Amazon” page, selects a destination fulfillment center, enters SKUs and quantities, and clicks “Create plan.” For example, a vendor with 500 units of a holiday plush toy would type the SKU and quantity into the form and submit.
- Generate labels and carrier options — Amazon automatically determines the most efficient packaging layout, produces printable barcode labels, and displays carrier rates. A seller shipping a 30‑pallet order might see a recommendation to use UPS Ground based on weight and distance.
- Confirm and schedule pickup — After reviewing the label batch and chosen carrier, the seller confirms the shipment. Amazon then sends an email containing pickup instructions and a tracking number that links back to the inbound record in Seller Central.
Analysis & Recommendations
Why This Matters
Sellers relying on automated inbound pipelines will see immediate failures after March 1 2023, risking stockouts and shipment delays. The UI‑only workflow removes the ability to programmatically manage shipments, so code must be removed or replaced and staff trained on the new wizard.
Key Takeaways
- Effective date is March 1 2023; Send to Amazon replaces every API‑driven send/replenish operation.
- After a shipment is created in the UI it cannot be fetched, updated, or deleted via MWS or SP‑API.
- Legacy shipments fully processed before the cutoff remain unchanged; new inbound activity must start in the UI.
- API calls to retired endpoints now return “InvalidShipmentId” errors.
Recommended Actions
- →Remove or disable code that calls CreateInboundShipmentPlan, CreateInboundShipment, or UpdateInboundShipment in MWS/SP‑API.
- →Update SOPs and train staff: go to Seller Central > Send to Amazon and follow the wizard for label creation, carrier selection, and confirmation.
- →Configure monitoring to alert on “InvalidShipmentId” API errors and automatically ticket the affected inbound plan for migration to the UI workflow.
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!