MWS FBA API no longer allowing "UpdateInboundShipment" to add SKUs since FBA inbound change on Saturday
PREFACE: We are in the process of transitioning to SP-API (which is due by end of March) but currently still use MWS API.
On Saturday the FBA inbound system changed to handle the more elaborate system splits.
Now it seems that the FBA MWS API, specifically "Update Inbound Shipment" no longer allows adding SKUs to an existing shipment. It fails with:
'Message' => ' Reason: Invalid attempt to add following new item(s) to shipment FBA_____: AG-___-____.',
(I blocked out our FBA shipment ID and SKU with ____)
This has broken our inbound systems we have been using for 10 years.
It seems that the new changes have broken the ability to "UpdateInboundShipment".
@TaylorR_Amazon @Bryce_Amazon
MWS FBA API no longer allowing "UpdateInboundShipment" to add SKUs since FBA inbound change on Saturday
PREFACE: We are in the process of transitioning to SP-API (which is due by end of March) but currently still use MWS API.
On Saturday the FBA inbound system changed to handle the more elaborate system splits.
Now it seems that the FBA MWS API, specifically "Update Inbound Shipment" no longer allows adding SKUs to an existing shipment. It fails with:
'Message' => ' Reason: Invalid attempt to add following new item(s) to shipment FBA_____: AG-___-____.',
(I blocked out our FBA shipment ID and SKU with ____)
This has broken our inbound systems we have been using for 10 years.
It seems that the new changes have broken the ability to "UpdateInboundShipment".
@TaylorR_Amazon @Bryce_Amazon
17 risposte
Seller_tDdfg68JbduAe
We are facing the same issue. Our operation has stopped as well.
Amazon was going to close MWS at the end of March but suddenly closed one of the features that was supposed to work till April.
Seller_TTG0TX5GOhqmW
Yes so I have dug further -- it seems the SP-API may not allow this operation going forward ("ADDING" a SKU to UpdateInboundShipment...)
It seems that (A) the SP-API may no longer support adding a SKU to a shipment via UPDATE... and (B) that MWS functionality may have been prematurely changed prior to the transition date.... our outbound systems have been halted basically.
See the following documentation details:
the "SP-API" has a specific note that says:
-------
(FROM SP-API DOCUMENTATION)
Operation: updateInboundShipment
Description: Updates or removes items from the inbound shipment identified by the specified shipment identifier. *** Adding new items is not supported. ***
-----
But we are using the MWS API -- which is clear through the end of month.
The MWS API specifically allows to add an item to the shipment: (FROM MWS DOCUMENTATION):
"If you include the InboundShipmentItems request parameter, the behavior is as follows:
Including an item that doesn't exist in the inbound shipment, as identified by the SellerSKU, *** adds the new item to the inbound shipment. ***"
----
@TaylorR_Amazon @Bryce_Amazon
Seller_TTG0TX5GOhqmW
The response we just received from within Amazon is:
"The UpdateInboundShipment API call cannot be used to add new items to an existing MWS shipment for US MP shipments, but can still be used to update or remove items."
However the MWS API documentation allows for it specifically (see below screenshot) and the system has been allowing this to happen for probably 10 years we have been creating shipments this way.
Seller_2qD7697gjKURc
Hello,
We have been using MWS to combine shipments. Recently this no longer works and shows the error described in this forum. We have tried doing the following:
Increasing the amount of skus sent in a createInboundShipmentPlan request. This results in the following error:
Number of InboundShipmentPlanRequestItems exceeded the maximum allowed limit of 200 per createInboundShipmentPlan request
Switching to SP API to update a shipment, this results in the following error:
"Invalid attempt to add following new item(s) to shipment"
We need a solution which allows us to send more than a 200 sku count variety to FBA. If you have solution, please share.
Seller_TTG0TX5GOhqmW
So here you have it -- straight from Amazon support... they are taking the position of "too bad".... that they have made changes to Seller Central, and thus the API must conform to that (and in this case regardless of impact to sellres).
I don't have an issue with the new SP-API not support a prior feature -- while that is annoying, at least we have had notice. What I do have a problem with is unilaterally changing the existing API, basically breaking it, a mere 30 days before it is due to be removed. What is the point of an end of service date if it's not going to work as expected until then?
See below:
=====
"I understand how this change to the FBA Inbound Placement policy can be an inconvenience; however, please keep in mind that changes to the policy take precedence over API functionality, as we aim to align to Seller Central, not override the current features.
In this case, as you mentioned, the API is not broken, but working as intended, as it is working along what the policy establishes. In the end, the API is in charge of applying the rules set by the owner teams, and if it is not allowed to add new SKUs to shipments after creation due to this policy change, we will follow and respect this rule."
====
Dominic_Amazon
Hi @Seller_TTG0TX5GOhqmW,
Dominic from Amazon here, some Sellers have had issues with the API functionality and split shipments. We have notified the team of this and they are working on addressing this.
Best,
Dominic
