UPS Shipping Rate Issue: Shipping Method Selected but Rate Becomes $0, and Checkout Shows No Methods in the magento 2.4.1

[vsakariya]

Preconditions and environment

I am using Magento 2.4.1 with the built-in UPS shipping method.

Problem:
UPS shipping methods load correctly on the cart page. But when I select any UPS shipping option:

The shipping rate becomes $0 in the subtotal.

When I continue to the checkout page, no UPS shipping methods appear, or I receive an error:

"No shipping method with given code: 02"

We contacted UPS support, and their response was:

"Have you reached out to Magento? We don't control or activate the necessary fields to apply the OAuth credentials. If the fields are not displaying options for the OAuth credentials and information, you would need to reach out to Magento."

We also tested the same UPS configuration on Magento 2.4.7, and the issue still persists.

Steps to Reproduce

Log in to Magento Admin.

Configure UPS shipping (using valid credentials).

Add any product to the cart.

Select any UPS shipping method.

Expected Result

When a UPS method is selected on the cart/checkout page, the correct UPS rate should be added to the subtotal.

Actual Result

The shipping rate displayed becomes $0.00 instead of the actual UPS rate.

Proceeding to checkout results in no UPS methods, or the error
"No shipping method with given code: 02".

Here is a recorded screen video link which helps to check it
https://www.loom.com/share/619fb73719924ed6bc19326ffe421021

Steps to reproduce

Log in to Magento Admin.

Configure UPS shipping (using valid credentials).

Add any product to the cart.

Select any UPS shipping method.

Expected result

When a UPS method is selected on the cart/checkout page, the correct UPS rate should be added to the subtotal.

Actual result

The shipping rate displayed becomes $0.00 instead of the actual UPS rate.

Proceeding to checkout results in no UPS methods, or the error
"No shipping method with given code: 02".

Additional information

No response

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

[devchris79]

This has been previously discussed:
#40116
#40158

If I understand correctly 2.4.1 will no longer work as it uses SOAP, you are now required to use a RESTful API to provide increased security with OATH2.

2.4.4 - 2.4.6 will work with a patch
2.4.7+ should work as standard as the core code implement RESTful API.

[vsakariya]

Hello, Currently, I can't update the Magento version. As a patch is available for the 2.4.4 - 2.4.6. How can I manage it in the current Magento version 2.4.1? Thank you.

…

On Fri, Nov 21, 2025 at 4:11 PM devchris79 ***@***.***> wrote: *devchris79* left a comment (magento/magento2#40308) <#40308 (comment)> This has been previously discussed: #40116 <#40116> #40158 <#40158> If I understand correctly 2.4.1 will no longer work as it uses SOAP, you are now required to use a RESTful API to provide increased security with OATH2. 2.4.4 - 2.4.6 will work with a patch <https://experienceleague.adobe.com/en/docs/experience-cloud-kcs/kbarticles/ka-27146#> 2.4.7+ should work as standard as the core code implement RESTful API. — Reply to this email directly, view it on GitHub <#40308 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMYVXSACR3HJI4MRUE3MFET353T67AVCNFSM6AAAAACMWZ4K3CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKNRSGQ2DSNRQHE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[engcom-November]

Hello @vsakariya ,

Thank you for the report and collaboration.

We have reviewed the issue and recommend referring to the documentation for further details.

https://experienceleague.adobe.com/en/docs/commerce-admin/stores-sales/delivery/shipping-carriers/ups

NOTE
The standard United Parcel Service type is scheduled for deprecation. For new configurations, use the default United Parcel Service REST type. The REST type is also required to generate shipping labels.

For the 2.4.7 release, UPS Type is removed because UPS and UPS XML types are scheduled for deprecation and UPS REST is the default. The United Parcel Service (UPS) APIs used by the native Adobe Commerce integration are temporarily deprecated because it does not currently support the OAuth 2.0 security model.

Please do let us know if you have any concerns meanwhile we are marking this issue as "Needs Update"

Thank you for your cooperation!