UPS API Change Request #37534
Comments
|
Hi @ntmhung. Thank you for your report.
Join Magento Community Engineering Slack and ask your questions in #github channel. |
|
@magento give me 2.4-develop |
|
HI, Please provide patch to us so we continue to use UPS as shipping method |
|
This is a major S0 issue that Adobe will need to address in the immediate future. The immediate impact is that starting this coming Monday, June 5 2023, merchants will no longer be able to add UPS rates to Magento. UPS will no longer generate any XML API keys, which Magento requires. The long-term impact is that as of June 2024, every merchant that uses Magento's native UPS rate connector will no longer get rates from UPS. This has a high probability of breaking checkout, as most US merchants do not offer multiple parcel shipment providers. Until this is resolved in Magento core, Merchants have the option of switching to a third party provider for their UPS rates, but that involves additional costs and setup. That's not an acceptable solution in the broad picture. See eg. https://twitter.com/saas_boss/status/1664354635346243585 |
|
Hello @rhoerr, Adobe team is working on a solution for new 2.4.6 customers. |
|
Great, thank you for the info @chernenm . Will look forward to that in the 2.4.7 release coming up soon. |
|
Plz give link of any 3rd party that giving ups with Magento
…On Fri, 2 Jun 2023, 23:08 Ryan Hoerr, ***@***.***> wrote:
This is a major S0 issue that Adobe will need to address in the immediate
future.
The immediate impact is that starting this coming Monday, June 5 2023,
merchants will no longer be able to add UPS rates to Magento. UPS will no
longer generate any XML API keys, which Magento requires.
The long-term impact is that as of June 2024, every merchant that uses
Magento's native UPS rate connector will no longer get rates from UPS. This
has a high probability of breaking checkout, as most US merchants do not
offer multiple parcel shipment providers.
Until this is resolved in Magento core, Merchants have the option of
switching to a third party provider for their UPS rates, but that involves
additional costs and setup. That's not an acceptable solution in the broad
picture.
—
Reply to this email directly, view it on GitHub
<#37534 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AE3VJ3B53BUYX7O5MM5DJALXJIQK7ANCNFSM6AAAAAAYNFKIWY>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
Seriously, this is not a joke! Something needs to be done about this, now. There is no point in using Magento if it can't calculate shipping. If this doesn't get fixed soon, I foresee a mass exodus from Magento. |
|
hello @ihaveathumb, @techguysourav, |
|
@chernenm Is the message at the top of that extension listing still applicable?
Also, when will 2.4.7 with the UPS REST API be released? There's not currently any published release date for 2.4.7, which suggests it won't be until sometime in 2024. That's cutting it close for the many merchants that will need to update. Thanks |
|
hi @rhoerr, The API update is planed to be included into 2.4.7-beta2 version which scheduled for October 2023. In addition we are working on a hotfix for new 2.4.6 customers and ensuring that UPS extension documentation is up to date at Magento marketplace. |
That doesn't work for me, because I'm not in the very few countries that it supports. |
|
This is an issue as UPS will no longer generate keys and the extension on marketplace isn't for the USA! |
|
Can you still generate keys on UPS as I have not been able to? |
|
Hello, @maxq, Adobe is currently working on the solution for this issue, we will be releasing a hotfix for 2.4.4, 2.4.5 and 2.4.6 customers. |
|
When, though? This is taking way too long for an issue that you knew far
ahead of time was going to happen!!!
…On Thu, Aug 3, 2023, 5:29 PM chernenm ***@***.***> wrote:
Hello, @maxq <https://github.com/maxq>,
Adobe is currently working on the solution for this issue, we will be
releasing a hotfix for 2.4.4, 2.4.5 and 2.4.6 customers.
—
Reply to this email directly, view it on GitHub
<#37534 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACQJYIRNP2OENNRYNMIDBOTXTQJ35ANCNFSM6AAAAAAYNFKIWY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Is there any update on this? |
|
Hello @joemstar, The fix will be published tomorrow, September 14 around noon CST at https://experienceleague.adobe.com/docs/commerce-knowledge-base/kb/overview.html?lang=en |
|
Thank you @chernenm! That's good to see. |
|
@chernenm for 2.4.3-p1 patch is applying? |
|
hello @laconica-vasilij, the patch is only applicable for supported versions of Adobe Commerce and Magento Open Source which are 2.4.4+ |
|
Applied the patch, anyone know how to get credentials from UPS? |
Look at the instructions https://developer.ups.com/get-started. You need to create an application to receive API keys |
|
Their API signup is so bad you go through all the steps then get this. See this stuff so much nowadays wonder who's coding this stuff. Also love this little gem. |
Hi @rahuldambare, Unfortunately we do not have a patch for a 2.3 versions, since it is no longer supported. |
|
@chernenm Please connect us support@ecomplugins.com for magento 2.3.x support. |
|
@Franciscof-Serfe Why flagged me ? why I can not help to other peoples ? |
|
Does anybody have issues not receiving their negotiated rates after switching? |
|
Yes, same issue here. |
|
@jaminion @yomyyo You must check API logs in magento var/log/shipping.log "ShipmentRatingOptions" => array( Then check admin setting if negotiated rates enabled in ups plugin. If still facing issues then contact us support@ecomplugins.com |
|
you should check admin setting if enabled or check var/log/shipping.log if tag being pass ? |
|
Admin settings are enabled, reviewing the log confirms that negotiated rates are being requested, but the returned rates are significantly higher than the rates the XML API is returning for identical shipments. |
|
Can you share api logs? |
|
Hey @jaywilliams if you are reviewing the log check and see if the "ResidentialAddressIndicator" is being passed in the request. In the new UPS REST API, they do not check the value of that parameter - they only check if it exists to determine if the request is residential or not. UPS also does not itemize out the residential rate adjustment in the data returned so it's difficult to determine if that's affecting you. magento2/app/code/Magento/Ups/Model/Carrier.php Line 1109 in c893121 It looks to me like they are still putting that parameter in the request and setting the value of it based on whether it's intended to be a residentially-rated request, rather than only including the parameter if it is to be rated residential. |
|
@jaywilliams i think issue with discounted rates. $rateParams['RateRequest']['Shipment']['ShipmentRatingOptions']['NegotiatedRatesIndicator'] = "Y"; So need to confirm if above parameter being pass in request. Then need to review API response. |
|
I've added the necessary lines to the API request, and am still getting significantly higher quotes on the REST API. @jaminion the residential address indicator is being passed, which does increase the rates, but I am passing the same residential flag on the XML request so they should still be the same. While debugging this issue, I've found that the stock M2 UPS REST patch sends "01" as the |
|
That's the really tricky thing about the residential indicator for rating on their REST API - they changed how it works (it's wild and awkward and I have no good things to say about it). It's difficult to get to the documentation as searching doesn't really work since they hide/show the content based on clicks. If you go the rating api, and look under Shipment->ShipTo->Address, there is a "ResidentialAddressIndicator" element, and their documentation there is:
If the rates are wildly off then yeah it's probably something else, but we were seeing differences from about $3 to $5.50 which were accounted for when editing the patch to change how that works (only include that entire element in that section conditionally). |
|
I'm a little confused with the explanation regarding the negotiated
rates with UPS. My rates are being correctly calculated when I use my
UPS negotiated rates account number in the admin back end. I am unable
to produce a shipping label when trying to save after my items were
added to my package. If I go back in to the admin area and change the
account id back to the standard six digit number I can create the
shipment with the negotiated rate.
|
|
If you are facing lots of errors then hire any magento developer or buy any 3rd party extension. |
|
I have added patch of 2.4.4 in Magento 2.3 and override method in my custom module. However Sometimes I am getting error as "The shipping method is missing. Select the shipping method and try again." on payment page. This error is coming from vendor/magento/module-quote/etc/di.xml from Magento\Quote\Model\ValidationRules\ShippingMethodValidationRule Even I have data available in total_segments shipping still this error shows. when moving from shipping page to payment page order summary gets reload and shipping amount removed from order summary . Functions I have override in my custom module after adding patch in 2.3 version as below My Customization are available on url https://www.file.io/YghI/download/vfXL5oVlg3Cd |
|
Not able to open file There was an error retrieving your file. Connect us at ecomplugins support for integration help. |
|
Upsphp.txt |
|
There are many issues. Main issue with ups token. You can not call again and again. There are API limits. You must cache it. You have many hardcoded variables and using session which also created these type issues like sometime showing shipping methods and next call hide rates. |
|
Could you please highlight the code or provide some correction which can help to fix this bug. |
Finally got word back from developer support. The issues with negotiated rate was due to using the non-production url to send our requests to (https://wwwcie.ups.com/api/rating/). We need to be using https://onlinetools.ups.com/api/rating/ to send our requests as that is the production URL |
|
ok, the default values where changed in 20.9.0 but they're also configurable in the backend |
|
Hi, |
|
M2.4.7-p2 Leaving this for anybody else: Using With the defaults, tracking responses kept giving results for Tracking Number "1Z1202R66698804005", no matter what the request tracking number was. |
|
@klou Thank you for sharing that information, that solves the issue I was experiencing with incorrect negotiated rates showing up. I created this patch to change the Magento defaults to use the production API endpoint: diff --git a/vendor/magento/module-ups/etc/config.xml b/vendor/magento/module-ups/etc/config.xml
index aaeccf87..10d21849 100644
--- a/vendor/magento/module-ups/etc/config.xml
+++ b/vendor/magento/module-ups/etc/config.xml
@@ -21,13 +21,13 @@
<free_method>GND</free_method>
<gateway_url>https://www.ups.com/using/services/rave/qcostcgi.cgi</gateway_url>
<gateway_xml_url>https://onlinetools.ups.com/ups.app/xml/Rate</gateway_xml_url>
- <gateway_rest_url>https://wwwcie.ups.com/api/rating/</gateway_rest_url>
+ <gateway_rest_url>https://onlinetools.ups.com/api/rating/</gateway_rest_url>
<handling>0</handling>
<model>Magento\Ups\Model\Carrier</model>
<pickup>CC</pickup>
<title>United Parcel Service</title>
<tracking_xml_url>https://onlinetools.ups.com/ups.app/xml/Track</tracking_xml_url>
- <tracking_rest_url>https://wwwcie.ups.com/api/track/</tracking_rest_url>
+ <tracking_rest_url>https://onlinetools.ups.com/api/track/</tracking_rest_url>
<unit_of_measure>LBS</unit_of_measure>
<username backend_model="Magento\Config\Model\Config\Backend\Encrypted" />
<password backend_model="Magento\Config\Model\Config\Backend\Encrypted" />I'd also like to make everyone aware that Magento has released updated patches which fix an issue with UPS dimensional shipping. |
|
@klou and @jaywilliams thanks for your observation onto the same, internal team is looking into this if this is a required change and we will update you ASAP on this. |
|
Hi @ntmhung, Internal team has looked into the issue and following are the observation: As we have given the avenue of having a Live Account set as “No” by default which will work on sandbox authorisation and shipment. Where the user has the option of setting it up as “Yes” making it to production.
2.The same way as Live Account option , By Default we have given the Sandbox “Tracking” and “Rating” Urls which can be edited from admin panel to production Gateway Urls, and we kept the possibility open for the user to edit the same as they want. We have tried to keep it streamlined for REST APIs. Having said that we also understand that this may have caused some confusion. Thanks. |
|
Hi @ntmhung, Our internal team has updated the Developer documentation on “Sandbox” and “production” setup steps. Please go through the same while you are setting up the shipping.
We will update further on the default URLs change once delivered. Thanks. |
and others
Description
My client has informed me that starting from June 5, 2023, UPS no longer issues new access keys. UPS is going to change to use Oauth 2.0.
I think the magento/module-ups module should be updated to meet the requirement. It needed to be done before June 5, 2023. This is the API document https://developer.ups.com/api/reference#operation/GenerateToken.
Expected behavior
The magento/module-ups supports using the OAuth security model from UPS.
Benefits
It will help new users planning to use the UPS shipping method connect to the UPS API after June 5, 2023.
Additional information
No response
Release note
No response
The text was updated successfully, but these errors were encountered: