amzn / selling-partner-api-models

This repository contains OpenAPI models for developers to use when developing software to call Selling Partner APIs.
Apache License 2.0
619 stars 741 forks source link

Feature request: add filter to `GET /inbound/fba/2024-03-20/inboundPlans/{inboundPlanId}/transportationOptions` aka `listTransportationOptions` #4238

Open johnkw opened 1 month ago

johnkw commented 1 month ago

Feature request: add filter to GET /inbound/fba/2024-03-20/inboundPlans/{inboundPlanId}/transportationOptions aka listTransportationOptions

This is a pseudo-regression from the previous API, which only ever returned APC freight specifically.

We only ever want entries with 'shippingMode' == 'FREIGHT_LTL' and 'shippingSolution' == 'AMAZON_PARTNERED_CARRIER'. But we have to wade through 1000s of carrier options, that are mostly useless parcel mode or whatever. Very wasteful and slow.

lightningja commented 1 month ago

second that. btw, I was never able to get AMAZON_PARTNERED_CARRIER for FREIGHT_LTL, and none of the LTL option include quote. Are you facing the same issue?

MeenaAmz commented 1 month ago

Thank you for raising this request. Please provide more details on your use case and impact so we can review the feature request.

Thanks, Meena Selling Partner API Developer Services

johnkw commented 1 month ago

The impact is that retrieving a few 1000 rows of listTransportationOptions information takes around a minute, and is around a megabyte of pointless network bandwidth transfer.

If we could filter down to just 'shippingMode' == 'FREIGHT_LTL' and 'shippingSolution' == 'AMAZON_PARTNERED_CARRIER' it would be much smaller and much faster.

Actually upon further pondering here, the filter should really be on the https://developer-docs.amazon.com/sp-api/docs/fulfillment-inbound-api-v2024-03-20-reference#generatetransportationoptionsrequest call. If Amazon has to do some sort of back-end work to create these transportation options in the first place, there's no purpose in creating options for us for non-LTL shippers, and non-APC shippers. We have no intention right now of ever using either.

hamduc7 commented 1 month ago

I have the same problem: I list 5 SKUS, but it generates 5 placement options. Each option has 2 shipments, and each has 185 transportation options, for 1850 options.

But actually, we only care about Amazon-partnered carriers, or some carriers like UPS, USP...

It is too slow. If we have a way to filter the transport options then it will speed up the process.

MeenaAmz commented 1 month ago

Thank you @johnkw, @lightningja and @hamduc7 for proposing this enhancement. We have submitted the feature request for review. Once we receive additional information we will post an update.

Thanks, Meena Selling Partner API Developer Services

github-actions[bot] commented 1 day ago

This issue is scheduled to close soon. If you are still encountering problems, please feel free to open a new issue and make a reference to this one.