Fulfillment Inbound API v2024-03-20 listPackingOptions Always return only 1 option

[mynamevincent]

Fulfillment Inbound API v2024-03-20 listPackingOptions Always return only 1 option

1.The expected return is multiple

2.And many return parameters are empty.

return data: { "packingOptions": [ { "packingGroups": [ "pgfcd64a3d-a632-4aa2-b232-2583a701803e" ], "fees": [], "discounts": [], "packingOptionId": "po00000000-0000-0000-0000-000000000000", "supportedShippingConfigurations": [], "inboundPlanId": "wf19edcae3-15a7-405f-9746-b37b3c7bdeb2", "status": "ACCEPTED" } ], "pagination": [] }

[harguph]

Hello @mynamevincent ,

Per the documentation of listPackingOptions "Packing options must first be generated by the corresponding endpoint before becoming available.".

Please ensure:

• generating packing options before invoking this call.
• where multiple packaging options are available use pageSize and paginationToken to retrieve information accordingly.

In case, you are still facing issues please open a developer support case sharing the full request and response so that team can have a look and assist you further.

[stesmyth]

We're still having the same issue... Can't get it to work regardless of what's posted on github. And the feedback from the API itself is nonsense...

• packingOptionId is always '0000'
• supportedShippingConfigurations is always empty
• contentInformationSource Barcode / Content Provided gives the same issue

"errors": [ { "code": "InternalFailure", "message": "We encountered an internal error. Please try again.", "details": "" } ]

Occurs on SetPackingInformation... every time

[stesmyth]

Per the documentation of listPackingOptions "Packing options must first be generated by the corresponding endpoint before becoming available.". Please ensure:

• generating packing options before invoking this call.
• where multiple packaging options are available use pageSize and paginationToken to retrieve information accordingly.

This reply is nonsense, as the original poster has already taken all of those steps... And the same issue still occurs....

See example...

22/05/2024 15:33:47 | Status (createInboundPlan) [7898e7fb-38e1-4c75-a6bc-11cd87713137] 22/05/2024 15:33:52 | Status (IN_PROGRESS) [7898e7fb-38e1-4c75-a6bc-11cd87713137] ... ... ... 22/05/2024 15:34:00 | Status (SUCCESS) [7898e7fb-38e1-4c75-a6bc-11cd87713137]

22/05/2024 15:34:06 | Status (generatePackingOptions) [da6e77a6-2bcb-416e-b532-f0d426645119] 22/05/2024 15:34:11 | Status (IN_PROGRESS) [da6e77a6-2bcb-416e-b532-f0d426645119] ... ... ... 22/05/2024 15:34:13 | Status (SUCCESS) [da6e77a6-2bcb-416e-b532-f0d426645119]

"packingOptions": [ { "packingGroups": [ "pg0ff66378-6c99-4280-a3b5-b89f66e78b82" ], "fees": [], "discounts": [], "packingOptionId": "po00000000-0000-0000-0000-000000000000", "supportedShippingConfigurations": [], "inboundPlanId": "wf0cf8caec-7f52-4153-9b5e-c3e5da97913b", "status": "ACCEPTED" } ]

Note: generatePackingOptions Response status is always 'ACCEPTED' even before 'confirmPackingOption' is called.

Calling createInboundPlan and then picking up in the SendToAmazon GUI works fine, but generatePackingOptions via API doesn't. (UK Marketplace)

[chastain1337]

Identical issue here, despite calling GeneratePackingOptions and waiting for the operation to complete.

[tamt]

I'm having the same problem.

[rustyfausak]

Why was this issue closed? It's still a problem. We are also receiving only one ACCEPTED packing option with packingOptionId = po00000000-0000-0000-0000-000000000000

The associated packing groups have reasonable IDs and items associated with them.