-
Notifications
You must be signed in to change notification settings - Fork 752
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ConfrimTransportationOptions operation returns: "ERROR: Requested transportation options do not have the same carrier as confirmed options." #4464
Comments
Hi, |
HI @jotaras, |
@puppsupr, sure. Here is the inbound plan ID: |
Hello, we are also experiencing this exact same issue when we try to use different carriers for LTL shipments. Is there any update with this issue? |
Hi @puppsupr, Could you clarify if this behavior is a documented restriction of the API or if it might be a bug? |
Team is still looking into this. |
I am having the same issue. Shipment It gives the following error while confirming transportation options:
|
Thanks all for your patience. We are still looking into the issue and will get back when we have an update. Thanks |
We are having the same issue(!) Any update on this? We have committed to pallets for a shipment to go via LTL and have chosen two different LTL carriers (one for each shipment) 'operationId' => '5ec1fe03-285a-4be6-9842-24ba3a4676fb', I have opened a case # as well -- side note, it does not seem to have to do with same or different carriers. I have tested using same APC LTL carrier for both shipments (2 in this plan). |
I asked Amazon tech support. Basically if one of the LTL is using 'Amazon Freight LTL', then all of the LTL needs to be 'Amazon Freight LTL'. So you either use 'Amazon Freight LTL' for all of them, or none of them.
|
Both of my shipments (from same plan) are going APC LTL. I want to correct my information -- it turns out that there were TWO errors going on... (A) I was getting an error that others were getting related to the shipment carriers being different. When I changed to the same carrier, that error went away (B) I am getting a second error " { I don't know what is causing this particular error. |
I am not very sure... I will follow up if I can figure it out myself... |
This is very concerning -- this issue has been open for almost a month now (Dec 23rd) and there is no resolution. These issues affect sellers ability to send freight and lower our costs. The forced API changeover date was Jan 20th and most of us have fully switched our operations to the new API. Please advise on the status of this. How can this take 3+ weeks to troubleshoot? |
@MetaMan2023 The issue that your having appears to be different than this issue (same vs different LTL carriers across shipments within a plan). If you had opened a support case already, can you please share the id? |
I am actually having BOTH errors -- the error noted above and this new error I mentioned. For the second error, I opened case #17058898711 Here is a separate GitHub thread for it: But my question is still the same for the issue in this thread -- is there any update/transparency on this particular issue? This thread has been open since December 23rd -- a full month. It's very concerning that it's still being looked into. |
FYI -- this is the latest information I received on this issue (as of January 23rd, 2025) -- it's not good, and still no transparency or timing: "Multiple partnered carrier options for LTL shipments: We are aware that this functionality is missing. Unfortunately, for now, the seller can use multiple carriers for LTL shipments, if the carrier is non-PCP. But for PCP currently Seller cannot use multiple carriers for the LTL shipments." This issue has a direct financial impact for sellers and needs to be addressed ASAP and here is a specific example:
To move forward with APC LTL under the new API we have to choose to lose potentially thousands of dollars per shipment plan, or else book our own shipments. Questions:
|
@jotaras @company-programs @Alvaromero @haoxi911 Have any of you gotten anywhere outside of these message boards? Any response to any external cases? The last Amazon response here was 10 days ago. |
I think we're on the same page. I am listing all LTL quotes from various carriers, but I have to group these quotes by the carrier as the API doesn't allow us to use carrier A for shipment 1 and carrier B for shipment 2. |
@MetaMan2023, I do see responses on the case, please do follow up over there as thats the right platform for troubleshooting. |
I just want to make sure you have closed the correct case -- this specific case was opened by another seller (with 4-5 others reporting this issue). This case involves "mixing" different LTL carriers in the same shipment. I do not believe there has been a clear answer on this. The last answer on this thread was that "it is being looked into" and receiving unclear answers internally.
|
Hi, Amazon returns an error when confirming transportation options where at least one of the shipments has a different carrier.
The example when confirming FREIGHT_LTL(USE_YOUR_OWN_CARRIER) transportation options:
Transport for shipment "shd1d6b5c1-10ee-4694-a8e1-2f51800b891a":
Transport for shipment "shd31e5fb9-99eb-49c8-9115-f16f9ca5cbef":
Transport for shipment "she67fe58d-61c8-401b-acf6-a83a952215b4":
Transport for shipment "shc96388b5-2946-4138-b094-7cefbba27147":
Transport for shipment "sh1ce7f9ca-696c-45bf-8a57-5c4b3840ea47":
The delivery window is confirmed for all shipments as required. But the confirmTransportationOptions operation is failing with this response:
In the example above 4 shipments have the same carrier: "UPS FREIGHT" and 1 shipment ha "USA TOURLINE INC". In the documentation, there is a note about that:
But in that case, there is the same error.
Within the same plan, if we change USA TOURLINE INC to UPS FREIGHT so that all shipments will have the same carrier
The operation will succeed.
Is it a problem on our end, or is it an issue with API?
Thanks for the response in advance!
The text was updated successfully, but these errors were encountered: