Skip to content
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

Closed
jotaras opened this issue Dec 23, 2024 · 20 comments
Assignees
Labels
FBA Inbound Issues related to FBA Inbound APIs Support Issue Issues that requires a Developer Support case

Comments

@jotaras
Copy link

jotaras commented Dec 23, 2024

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:

{"transportationSelections":[
    {"shipmentId":"shd1d6b5c1-10ee-4694-a8e1-2f51800b891a","transportationOptionId":"toa99a670f-165b-4949-afc8-eec8fbd873aa"},
    {"shipmentId":"shd31e5fb9-99eb-49c8-9115-f16f9ca5cbef","transportationOptionId":"to57feb7cf-812d-405e-b685-8460cd666aa5"},
    {"shipmentId":"she67fe58d-61c8-401b-acf6-a83a952215b4","transportationOptionId":"to1beac56c-caa4-4b37-8661-6a99f3466f29"},
    {"shipmentId":"shc96388b5-2946-4138-b094-7cefbba27147","transportationOptionId":"toa35b6528-be1b-407c-a359-5776d9056a22"},
    {"shipmentId":"sh1ce7f9ca-696c-45bf-8a57-5c4b3840ea47","transportationOptionId":"to45530225-bb26-4e76-8f4f-55910d8baf46"}
]}

Transport for shipment "shd1d6b5c1-10ee-4694-a8e1-2f51800b891a":

{
      "carrier": {
          "name": "UPS FREIGHT",
          "alphaCode": "UPGF"
      },
      "preconditions": [
          "CONFIRMED_DELIVERY_WINDOW"
      ],
      "shipmentId": "shd1d6b5c1-10ee-4694-a8e1-2f51800b891a",
      "shippingMode": "FREIGHT_LTL",
      "transportationOptionId": "toa99a670f-165b-4949-afc8-eec8fbd873aa",
      "shippingSolution": "USE_YOUR_OWN_CARRIER"
}

Transport for shipment "shd31e5fb9-99eb-49c8-9115-f16f9ca5cbef":

{
    "carrier": {
        "name": "UPS FREIGHT",
        "alphaCode": "UPGF"
    },
    "preconditions": [
        "CONFIRMED_DELIVERY_WINDOW"
    ],
    "shipmentId": "shd31e5fb9-99eb-49c8-9115-f16f9ca5cbef",
    "shippingMode": "FREIGHT_LTL",
    "transportationOptionId": "to57feb7cf-812d-405e-b685-8460cd666aa5",
    "shippingSolution": "USE_YOUR_OWN_CARRIER"
}

Transport for shipment "she67fe58d-61c8-401b-acf6-a83a952215b4":

{
    "carrier": {
        "name": "UPS FREIGHT",
        "alphaCode": "UPGF"
    },
    "preconditions": [
        "CONFIRMED_DELIVERY_WINDOW"
    ],
    "shipmentId": "she67fe58d-61c8-401b-acf6-a83a952215b4",
    "shippingMode": "FREIGHT_LTL",
    "transportationOptionId": "to1beac56c-caa4-4b37-8661-6a99f3466f29",
    "shippingSolution": "USE_YOUR_OWN_CARRIER"
}

Transport for shipment "shc96388b5-2946-4138-b094-7cefbba27147":

{
        "carrier": {
            "name": "USA TOURLINE INC",
            "alphaCode": "USBJ"
        },
        "preconditions": [
            "CONFIRMED_DELIVERY_WINDOW"
        ],
        "shipmentId": "shc96388b5-2946-4138-b094-7cefbba27147",
        "shippingMode": "FREIGHT_LTL",
        "transportationOptionId": "toa35b6528-be1b-407c-a359-5776d9056a22",
        "shippingSolution": "USE_YOUR_OWN_CARRIER"
}

Transport for shipment "sh1ce7f9ca-696c-45bf-8a57-5c4b3840ea47":

{
    "carrier": {
        "name": "UPS FREIGHT",
        "alphaCode": "UPGF"
    },
    "preconditions": [
        "CONFIRMED_DELIVERY_WINDOW"
    ],
    "shipmentId": "sh1ce7f9ca-696c-45bf-8a57-5c4b3840ea47",
    "shippingMode": "FREIGHT_LTL",
    "transportationOptionId": "to45530225-bb26-4e76-8f4f-55910d8baf46",
    "shippingSolution": "USE_YOUR_OWN_CARRIER"
}

The delivery window is confirmed for all shipments as required. But the confirmTransportationOptions operation is failing with this response:

{
    "operationStatus": "FAILED",
    "operationId": "c4500a92-885f-4a58-81f4-3300247b85ea",
    "operation": "confirmTransportationOptions",
    "operationProblems": [
        {
            "severity": "ERROR",
            "code": "FBA_INB_0354",
            "details": "There's an input error with the resource 'shd1d6b5c1-10ee-4694-a8e1-2f51800b891a'.",
            "message": "ERROR: Requested transportation options do not have the same carrier as confirmed options."
        },
        {
            "severity": "ERROR",
            "code": "FBA_INB_0354",
            "details": "There's an input error with the resource 'shd31e5fb9-99eb-49c8-9115-f16f9ca5cbef'.",
            "message": "ERROR: Requested transportation options do not have the same carrier as confirmed options."
        },
        {
            "severity": "ERROR",
            "code": "FBA_INB_0354",
            "details": "There's an input error with the resource 'she67fe58d-61c8-401b-acf6-a83a952215b4'.",
            "message": "ERROR: Requested transportation options do not have the same carrier as confirmed options."
        },
        {
            "severity": "ERROR",
            "code": "FBA_INB_0354",
            "details": "There's an input error with the resource 'shc96388b5-2946-4138-b094-7cefbba27147'.",
            "message": "ERROR: Requested transportation options do not have the same carrier as confirmed options."
        },
        {
            "severity": "ERROR",
            "code": "FBA_INB_0354",
            "details": "There's an input error with the resource 'sh1ce7f9ca-696c-45bf-8a57-5c4b3840ea47'.",
            "message": "ERROR: Requested transportation options do not have the same carrier as confirmed options."
        }
    ]
}

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:

You can include a mix of Small Parcel Delivery (SPD) and LTL shipments in one inbound plan.

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

{
      "carrier": {
          "name": "UPS FREIGHT",
          "alphaCode": "UPGF"
      },
      "preconditions": [
          "CONFIRMED_DELIVERY_WINDOW"
      ],
      "shipmentId": "shc96388b5-2946-4138-b094-7cefbba27147",
      "shippingMode": "FREIGHT_LTL",
      "transportationOptionId": "to000005cf-ca5f-474a-8964-b863141e4e42",
      "shippingSolution": "USE_YOUR_OWN_CARRIER"
}
{"transportationSelections":[
    {"shipmentId":"shd1d6b5c1-10ee-4694-a8e1-2f51800b891a","transportationOptionId":"toa99a670f-165b-4949-afc8-eec8fbd873aa"},
    {"shipmentId":"shd31e5fb9-99eb-49c8-9115-f16f9ca5cbef","transportationOptionId":"to57feb7cf-812d-405e-b685-8460cd666aa5"},
    {"shipmentId":"she67fe58d-61c8-401b-acf6-a83a952215b4","transportationOptionId":"to1beac56c-caa4-4b37-8661-6a99f3466f29"},
    {"shipmentId":"shc96388b5-2946-4138-b094-7cefbba27147","transportationOptionId":"to000005cf-ca5f-474a-8964-b863141e4e42"},
    {"shipmentId":"sh1ce7f9ca-696c-45bf-8a57-5c4b3840ea47","transportationOptionId":"to45530225-bb26-4e76-8f4f-55910d8baf46"}
]}

The operation will succeed.

{
    "operationStatus": "SUCCESS",
    "operationId": "38279dd1-c2b7-4252-9684-5677b1337425",
    "operation": "confirmTransportationOptions",
    "operationProblems": []
}

Is it a problem on our end, or is it an issue with API?
Thanks for the response in advance!

@puppsupr
Copy link

Hi,
Checking with the FBA inbound team on this.

@puppsupr puppsupr self-assigned this Dec 24, 2024
@puppsupr puppsupr added Support Issue Issues that requires a Developer Support case FBA Inbound Issues related to FBA Inbound APIs labels Dec 24, 2024
@puppsupr
Copy link

HI @jotaras,
Can you share the inbound plan ID as well ?

@jotaras
Copy link
Author

jotaras commented Dec 24, 2024

@puppsupr, sure. Here is the inbound plan ID: wfd9d8f4e1-4e47-4c1d-bd3a-898d7931fec2. The plan has already been canceled, but the problem occurs in every other plan, too.

@company-programs
Copy link

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?

@Alvaromero
Copy link

Hi @puppsupr, Could you clarify if this behavior is a documented restriction of the API or if it might be a bug?

@puppsupr
Copy link

Team is still looking into this.

@haoxi911
Copy link

I am having the same issue. Shipment sh9d161a36-f242-427a-9a28-7cd477271b93 uses Amazon partnered UPS. Shipment shaacbd1f6-2d08-4bd6-96ac-83ff8d187651 uses Fedex Ground, both are SPD.

It gives the following error while confirming transportation options:

{
    "operationStatus": "FAILED",
    "operationId": "1745ca2f-3a06-449e-b622-9b386b433c2d",
    "operation": "confirmTransportationOptions",
    "operationProblems": [
        {
            "severity": "ERROR",
            "code": "FBA_INB_0354",
            "details": "There's an input error with the resource 'sh9d161a36-f242-427a-9a28-7cd477271b93'.",
            "message": "ERROR: Requested transportation options do not have the same carrier as confirmed options."
        },
        {
            "severity": "ERROR",
            "code": "FBA_INB_0354",
            "details": "There's an input error with the resource 'shaacbd1f6-2d08-4bd6-96ac-83ff8d187651'.",
            "message": "ERROR: Requested transportation options do not have the same carrier as confirmed options."
        }
    ]
}

@MeenaAmz
Copy link
Contributor

Thanks all for your patience. We are still looking into the issue and will get back when we have an update.

Thanks
Meena

@MetaMan2023
Copy link

MetaMan2023 commented Jan 21, 2025

@MeenaAmz @puppsupr

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',
'operationProblems' => [
{
'message' => 'ERROR: Provided PCP-LTL shipment has missing freight information.',
'details' => 'There's an input error with the resource 'XXXXX'.',
'code' => 'FBA_INB_0352',
'severity' => 'ERROR'
} (...this is partial list of errors to keep private resource #s)

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).

@haoxi911
Copy link

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.

For LTL Shipments:

  • If using Partner carriers: All carriers must be consistent across shipments
  • If using Non-Partner carriers: Different carriers may be selected

For SPD Shipments:

  • All carriers must be the same across all shipments, no exceptions

@MetaMan2023
Copy link

@haoxi911

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 " {
'message' => 'ERROR: Provided PCP-LTL shipment has missing freight information.',
'details' => 'There's an input error with the resource 'XXXX'.',
'code' => 'FBA_INB_0352',
'severity' => 'ERROR'
}"

I don't know what is causing this particular error.

@haoxi911
Copy link

I am not very sure... I will follow up if I can figure it out myself...

@MetaMan2023
Copy link

@puppsupr @MeenaAmz

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?

@MeenaAmz
Copy link
Contributor

@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?

@MetaMan2023
Copy link

@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:

#4547

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.

@MetaMan2023
Copy link

@puppsupr @MeenaAmz

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:

  • We have a two shipment plan (shipment A and shipment B), and have generated transport options

  • Amazon has returned a list of APC LTL carriers with pricing for both shipments

  • The best price carrier for shipment A ("Central Transport") does not exist for shipment B -- meaning under the current implementation, we cannot choose the best price option for shipment A as there is no carrier match in shipment B. Not only that, carrier prices are wildly different -- for example "Central Transport" is $440 but "ABF Freight" is $1100.

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:

  • Why does the API even return carrier options that are impossible to select?

  • Why have we been forced into a new API that forces us to lose money?

  • Why is there no transparency or timeline for a fix? Extending v0 functionality is no longer an option -- at this point it is assumed most sellers have changed their operations over to the new API due to the deadlines.

@MetaMan2023
Copy link

@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.

@haoxi911
Copy link

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.

@puppsupr
Copy link

@MetaMan2023, I do see responses on the case, please do follow up over there as thats the right platform for troubleshooting.

@MetaMan2023
Copy link

@MetaMan2023, I do see responses on the case, please do follow up over there as thats the right platform for troubleshooting.

@puppsupr

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.

  • Does Amazon know what is causing the issue not allowing LTL carriers to be mixed within a plan?
  • Does it plan to be fixed, and if so what is the timeline?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
FBA Inbound Issues related to FBA Inbound APIs Support Issue Issues that requires a Developer Support case
Projects
None yet
Development

No branches or pull requests

7 participants