Document (or remove) ITEM_STRANDED for createInboundShipmentPlan

[johnkw]

The ITEM_STRANDED code is not documented, and needs to be. One possible reason for that error code is if inventory is being sent for a SKU, where some other SKU in that ASIN has inventory in the so-called "stranded" status. (In our case this occurred in bug #401 due to inventory stuck in "FC Processing", but it could probably happen with regularly available inventory as well.)

If you hit this, a fix is apparently to change the so-called "stranded" SKU briefly from Closed to Open, then create the Shipment, and then restore the SKU to its correct Closed state again. The problem is this pointless flip-flopping exposes a few seconds or minutes of a SKU being in the wrong state, and a sale could happen then for a SKU that you don't want being sold.

This all should be documented.... or just removed. ITEM_STRANDED is a seemingly pointless check that has no benefit, and working around it exposes the SKU to problems. It seems to be a case of FBA trying to warn you that you're sending inventory in when you don't need to be, but the warning is horrible and incorrect in this situation. It's unclear what situation it would possibly be useful for, but there needs to be some way to override it if it is going to remain.

[github-actions[bot]]

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.

[johnkw]

Still broken and EXTREMELY PROBLEMATIC.

[github-actions[bot]]

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.

[johnkw]

Turn this stupid bot off and resolve the github tickets as the actual issues are fixed. @adrian-amz @amazon-auto @chapmanjw @amvreddy-amazon @jenilew @parvathm

[github-actions[bot]]

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.

[johnkw]

Please turn this horrible bot off and only close the github tickets as the actual issues are fixed. @adrian-amz @amazon-auto @chapmanjw @amvreddy-amazon @jenilew @parvathm

[github-actions[bot]]

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.

[johnkw]

Please turn this horrible bot off and only close the github tickets as the actual issues are fixed. @adrian-amz @amazon-auto @chapmanjw @amvreddy-amazon @jenilew @parvathm

[johnkw]

This is still broken in the new /inbound/fba/2024-03-20/inboundPlans API but now the error code is FBA_INB_0049.

[shreeharsh-a]

Please reach out to developer support so that we can better help you with issues related to SP API.

Note: SP API or docs related issues / troubleshooting support is managed by a different team. We can help if the issue is related to the content published on this repo.

[johnkw]

This is still an open API bug. This should not be closed, in order to allow everyone to see the current state of things.

[shreeharsh-a]

Please be advised that API related bugs will not be tracked on this repo i.e. selling-partner-api-models. Only issues related to this repo will be tracked to closure here. If this is still an issue, please reach out to developer support. Thanks again!

[johnkw]

@shreeharsh-a "developer support" is not capable of addressing issues like this. This is something that needs to be communicated to the SP-API team. In the mean time though this ticket should remain open so that the community can understand the state of existing open bugs.

[shreeharsh-a]

@johnkw thank you for your feedback but reaching out to developer support is the best mechanism to leverage as they can escalate / forward your issues, etc to the right backend team for resolution. Also, please use discussions instead of issues to keep things open so that the community can discuss etc.

[johnkw]

Filing a bug report with developer support is fine (and yes, I always do) but it doesn't seem to do much, and doesn't provide answers, as developer support just closes the ticket with "thanks" and there's never any information provided on status of a fix. Community insights into currently open bugs have historically been far more helpful.

Thank you for moving this bug report to the "discussions" tab so that it can remain open. Can you move other existing bug reports as well? For example bug #406.