What is Send to Amazon?
Amazon’s new Send to Amazon workflow streamlines the shipping process, helping sellers get products to fulfillment centers more efficiently. All new shipments from sellers using Fulfillment by Amazon (FBA) must be created using the Send to Amazon workflow, or through APIs.
What is changing?
Send to Amazon replaces the legacy “Send/Replenish” inventory workflow for API-created shipments for all sellers. Starting March 1, 2023, Send to Amazon replaces the send/replenish inventory workflow for API-created shipments for all sellers.
Shipments that have been created, viewed, or edited using Send to Amazon cannot be viewed or edited via API. This includes shipments that have been created or edited via API in the past. Once you use Send to Amazon with a shipment, you can no longer use an API-based method to view or edit the shipment.
Can I still create Amazon shipments?
Yes, please keep in mind however that once a shipment that have been created, viewed, or edited using Send to Amazon, it cannot be viewed or edited via API. This includes shipments that have been created or edited via API in the past.
Will I see changes to shipments created in the past?
No, unfortunately changes cannot be detected via API for existing shipments created using the send/replenish method - or new shipments created using the Send to Amazon tool.
Is Amazon planning future support for viewing/editing Send To Amazon shipments via the API?
Yes, but the ETA is not fixed yet. Amazon will send an announcement once the launch date is decided. *Note from IP Support - we will update as soon as we hear more!
How will this impact my Inventory Planner account?
Changes related to shipment status or receiving will not be available in Amazon's API. The expectation is that Inventory Planner cannot see receiving details (thus “transfer in” or “on order” qtys will remain), but will however see stock changes through nightly syncs.
This impacts a fundamental part of the replenishment workflow where ‘Amazon receives FBA shipments, and increases stock’. The flowcharts below demonstrate the disconnect prompted by this issue using POs as a method to send stock to Amazon (directly from a Vendor) or Transfers between warehouses. In both cases, replenishment is likely to be understated since status and receiving details will be missing in Amazon's API.
Is there a workaround?
There is no effective workaround available for this issue unfortunately. Customer issues need to be investigated on a case-by-case basis. Open a conversation with Inventory Planner Support using the chat widget in the bottom right, or by emailing [email protected] - and please provide the following:
A clear explanation of the problem(s).
At least one specific example (per problem, if there are multiple) to demonstrate.
Screenshots from Inventory Planner of the example vs. the same example in Amazon to demonstrate the expected behavior.
Further context on how your workflow is impacted by the issue, and if any communications have been exchanged with Amazon Support.
Your feedback will be directly relayed from Inventory Planner Support to our Engineering and Product teams to improve their understanding of the problem and brainstorm solutions. The more details you can provide, the better!
Why am I seeing incorrect manual fees in Amazon?
There is a secondary issue with the “Send to Amazon” workflow where customers are being charged for not providing box content information, although it’s not possible to do with FBA shipments created via API. Amazon is aware of the issue, and merchants can contact Amazon support regarding incorrectly calculated manual fees. If more information is needed, please contact Inventory Planner Support.
We will keep this article up-to-date, and will share more details as we receive them from Amazon and the developer community. Despite the inconveniences the workflow changes may cause initially, there is certainly light ahead with Amazon's upgraded features. We look forward to improving functionality in Inventory Planner as updates become available.