Repository navigation
Replies: 1 comment 2 replies
|
100% agree -- there are over 100 options for strange named carriers I would never use. Some kind of filter system -- and if there is going to be a filter system it would be great for it to be flexible not only APC, GROUND, LTL but maybe premium carriers or specific carrier names or maybe carriers that are < a certain cost. Some of the carriers returned are not even in English -- the carrier name is in strange unreadable characters. Does anyone understand the "USE_YOUR_OWN_CARRIER" tag -- it seems confusing -- if I am suppose to use my own carrier, why is there a carrier listed? |
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Problem: Too many options (100+) are provided when using: ListTransportationOptions.
I'm specifically looking for an option with shippingMode: GROUND_SMALL_PARCEL and shippingSoultion: AMAZON_PARTNERED_CARRIER . 99% of options returned are not suitable* and it takes several calls to cycle through (using tokens and the max page size 20) to find even one suitable option.
(My program currently stops when the first suitable option is found but this means it could be missing any new suitable transportation options)
Possible solution: Allow shippingMode and shippingSoultion filters in generateTransportationOptions operation in generateTransportationRequest->shipmentTransportationConfigurations.
This will greatly reduce the number of calls needed and show me if new options which are suitable are available
*the majority of options are for shippingMode: OCEAN_LCL, OCEAN_FCL, AIR_SMALL_PARCEL, AIR_SMALL_PARCEL_EXPRESS... and shippingSolution: USE_YOUR_OWN_CARRIER
thank you
All reactions