We currently use the new Inbound API to create our shipments. But there is a critical failure point when booking LTL shipments on an Amazon Optimized Split (5 ways).

All 5 splits for LTL must go via the same carrier otherwise both the API calls error out and Seller Central does not work either. This is likely, not intentional as the interface in Seller Central intentionally prioritizes "Earliest and Cheapest", but is causing massive problems as we have lots of freight needing to go out via partnered carrier and cannot choose the same carrier for all 5 splits (And/or it being extremely expensive).

I have opened a case, but am spinning my wheels. When opening the shipments in SC, the pallet weight/dims do not load from the API information unless we click on non-partnered, let it load, click partnered again, and then refresh. The information is there, but there is a backend glitch that is causing massive errors in this process.

None of our shipments are small. All 5 splits are multiple pallets each. No this is not the application side because these errors are present in Seller Central under manage shipments.

Additionally, we have found we cannot use Non-Partnered LTL carriers and Partnered LTL carriers in the same shipping plan. Why this is a limitation does not make sense.

Case ID: 16876567271