UPS single rate not displayed

[CptCharlesG]

Preconditions and environment

• Magento version: 2.4.7-p3
• UPS module

Steps to reproduce

1. Set UPS credentials in admin and enable UPS shipping
2. Calculate UPS shipping rates for a destination where only 1 shipping rate is available at UPS.
   Example: Cyprus, 3030

Expected result

Show the single available UPS rate

Actual result

No result displayed, customers cannot place order, losing sales

Additional information

Honestly I would call it a bug in the UPS response format.
The problem is that UPS returns RatedShipment as an array if there are multiple rates, but if there is only a single rate available then it returns that rate directly.

Example:
Single rate:
'result' => '{"RateResponse":{"Response":{"ResponseStatus":{"Code":"1", "Description":"Success"}, "Alert":{"Code":"110971", "Description":"Your invoice may vary from the displayed reference rates"}, "TransactionReference":{"CustomerContext":"Rating and Service"}}, "RatedShipment":{"Service":{"Code":"65", "Description":""}, "RatedShipmentAlert":{"Code":"110971", "Description":"Your invoice may vary from the displayed reference rates"}, "BillingWeight":{"UnitOfMeasurement":{"Code":"KGS", "Description":"Kilograms"}, "Weight":"6.5"}, "TransportationCharges":{"CurrencyCode":"HUF", "MonetaryValue":"38750.00"}, "ServiceOptionsCharges":{"CurrencyCode":"HUF", "MonetaryValue":"0.00"}, "TotalCharges":{"CurrencyCode":"HUF", "MonetaryValue":"38750.00"}, "RatedPackage":{"Weight":"6.4"}}}}',

Multiple rates:
'result' => '{"RateResponse":{"Response":{"ResponseStatus":{"Code":"1", "Description":"Success"}, "Alert":{"Code":"110971", "Description":"Your invoice may vary from the displayed reference rates"}, "TransactionReference":{"CustomerContext":"Rating and Service"}}, "RatedShipment":[{"Service":{"Code":"07", "Description":""}, "RatedShipmentAlert":{"Code":"110971", "Description":"Your invoice may vary from the displayed reference rates"}, "BillingWeight":{"UnitOfMeasurement":{"Code":"KGS", "Description":"Kilograms"}, "Weight":"6.5"}, "TransportationCharges":{"CurrencyCode":"HUF", "MonetaryValue":"41750.00"}, "ServiceOptionsCharges":{"CurrencyCode":"HUF", "MonetaryValue":"0.00"}, "TotalCharges":{"CurrencyCode":"HUF", "MonetaryValue":"41750.00"}, "RatedPackage":{"Weight":"6.4"}}, {"Service":{"Code":"54", "Description":""}, "RatedShipmentAlert":{"Code":"110971", "Description":"Your invoice may vary from the displayed reference rates"}, "BillingWeight":{"UnitOfMeasurement":{"Code":"KGS", "Description":"Kilograms"}, "Weight":"6.5"}, "TransportationCharges":{"CurrencyCode":"HUF", "MonetaryValue":"51900.00"}, "ServiceOptionsCharges":{"CurrencyCode":"HUF", "MonetaryValue":"0.00"}, "TotalCharges":{"CurrencyCode":"HUF", "MonetaryValue":"51900.00"}, "RatedPackage":{"Weight":"6.4"}}, {"Service":{"Code":"65", "Description":""}, "RatedShipmentAlert":{"Code":"110971", "Description":"Your invoice may vary from the displayed reference rates"}, "BillingWeight":{"UnitOfMeasurement":{"Code":"KGS", "Description":"Kilograms"}, "Weight":"6.5"}, "TransportationCharges":{"CurrencyCode":"HUF", "MonetaryValue":"38750.00"}, "ServiceOptionsCharges":{"CurrencyCode":"HUF", "MonetaryValue":"0.00"}, "TotalCharges":{"CurrencyCode":"HUF", "MonetaryValue":"38750.00"}, "RatedPackage":{"Weight":"6.4"}}]}}',

How to fix:

In magento\module-ups\Model\Carrier.php line 1273 is the following:
$arr = $rateResponseData['RateResponse']['RatedShipment'] ?? [];
Add the following code below this line in order to convert it to an array if the single rate is exposed directly, not in array:
if (array_key_exists("Service", $arr)) $arr = [$arr];
Maybe it is a bit dirty, but I cannot think about a more fancy solution.

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @CptCharlesG. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant]

Hi @engcom-Bravo. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Bravo]

Hi @CptCharlesG,

Thanks for your reporting and collaboration.

We have verified the issue in Latest 2.4-develop instance and the issue is not reproducible.Kindly refer the screenshots.

We are able to get the available UPS shipping methods.

Kindly recheck the issue in Latest 2.4-develop instance and elaborate the steps to reproduce if the issue is still reproducible.

Thanks.

[CptCharlesG]

Dear @engcom-Bravo

Thank you for your reply!

Well, there are 3 rates on your screenshot.
The problem occurs when UPS returns only one rate.

So first we need to fine a case where UPS returns only one rate.

Maybe you could try modifying the origin to Hungary, 6500 Baja but possibly another API key is needed in that case.

But trust me, the quoted responses are accurate, and the difference is visible there.

Thanks

[engcom-Bravo]

Hi @CptCharlesG,

Thanks for your update.

We have tried to reproduce the issue in Latest 2.4-develop instance with origin to Hungary and we are not able to reproduce the issue.Kindly refer the screenshots.

We are getting 2 available rates in the checkout.

Kindly recheck the issue in Latest 2.4-develop instance and elaborate the steps to reproduce if the issue is still reproducible.

Thanks.

[CptCharlesG]

@magento give me 2.4-develop instance

[CptCharlesG]

Dear @engcom-Bravo ,

Well, it is shipping TO Hungary on your photo.
Please check shipping FROM Hungary TO Cyprus of possible.

Unfortunately I cannot install a new instance until the end of the month.

Thanks!