Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incomplete enum list for FulfillmentInbound ShipmentStatus in fulfillmentInboundV0.json #270

Closed
jasonhebert opened this issue Aug 24, 2022 · 7 comments

Comments

@jasonhebert
Copy link

Please update the fulfillmentInboundV0.json model file to include undocumented ShipmentStatus value READY_TO_SHIP.

In the fulfilment-inbound-api-v0-model file it lists the following accepted values for the ShipmentStatus enum:

[
        "WORKING",
        "SHIPPED",
        "RECEIVING",
        "CANCELLED",
        "DELETED",
        "CLOSED",
        "ERROR",
        "IN_TRANSIT",
        "DELIVERED",
        "CHECKED_IN"
]

An additional value of READY_TO_SHIP is also returned from the API as shown here:

{
    "payload":
    {
        "ShipmentData":
        [
            {
                "ShipmentId": "FBA********C",
                "ShipmentName": "FBA **********",
                "ShipFromAddress":
                {
                    "Name": "Tian******",
                    "AddressLine1": "******",
                    "DistrictOrCounty": "Na******",
                    "City": "Hu******",
                    "StateOrProvinceCode": "T******",
                    "CountryCode": "**",
                    "PostalCode": "*****"
                },
                "DestinationFulfillmentCenterId": "ONT8",
                "ShipmentStatus": "READY_TO_SHIP",
                "LabelPrepType": "SELLER_LABEL",
                "BoxContentsSource": "INTERACTIVE"
            }
        ]
    }
}
jasonhebert added a commit to powersrc/sp-api-sdk that referenced this issue Aug 24, 2022
The API returns an undocumented value of `READY_TO_SHIP` for the `ShipmentStatus` enum.
Ticket has been filed to have corrected at amzn/selling-partner-api-models#270
norberttech pushed a commit to amazon-php/sp-api-sdk that referenced this issue Aug 25, 2022
The API returns an undocumented value of `READY_TO_SHIP` for the `ShipmentStatus` enum.
Ticket has been filed to have corrected at amzn/selling-partner-api-models#270
@Proladge
Copy link

@jasonhebert , could the issue be closed?

@jasonhebert
Copy link
Author

I received email response on another ticket in a different ticketing system for Amazon that the READY_TO_SHIP status should not be returned from the API. Nothing since then so I am not sure if the issue has been resolved or not. No official word from any Amazon devs on this issue.

@jasonhebert
Copy link
Author

Prior response from other ticket: "I am afraid that there is no current time line, however it is likely that the resolution will be to stop READY_TO_SHIP being issued as a shipment status, since there is no user value to it in terms of the FBA shipping API. Instead, it is likely that this will be mapped to WORKING as this is the least complicated resolution. I will follow up as soon as additional information becomes available."

Received a response just now that the READY_TO_SHIP status is in fact a good status to be returned and the model documentation and swagger docs have now been updated to include the status.

UGH!!!

@clayton-k
Copy link

Hello @jasonhebert, I think the READY_TO_SHIP status has not been added to the model document:
https://github.com/amzn/selling-partner-api-models/blob/main/models/fulfillment-inbound-api-model/fulfillmentInboundV0.json#L6168

@jasonhebert
Copy link
Author

They added it to the getShipments operation as an input value for the ShipmentStatusList parameter but I now see that they have NOT added it to the actual enum that is returned from the operation. Dealing with them on this has been a total nightmare and no-one knows what is going on. It seems there are multiple teams working on this and they have no clue what each is doing. I've received multiple different responses from multiple people over 4 tickets I've filed, nothing has actually been done except this change, and it is incorrect as well it seems.

Would someone else like to take this on? I'm tired boss, so tired.

Copy link

github-actions bot commented May 9, 2024

This is a very old issue that is probably not getting as much attention as it deserves. We encourage you to check if this is still an issue after the latest release and if you find that this is still a problem, please feel free to open a new issue and make a reference to this one.

Copy link

closed for inactivity

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants