Patch [AC-15210]: USPS REST api no tracking, not preserving allowed methods ...

[bluedarter2]

This patch isn't ready for production use:

1. it does NOT provide tracking information
2. It doesn't preserve the Allowed Methods settings if the API choice is changed.
3. it should protect against sending unneeded requests to the USPS API, because:
4. it does not report or protect against the "429" Quota limit result. Hitting the limit means no rates are returned from the interface. If you are presenting rates to a customer, this is a disaster.

Here is an example quota limit exceeded result, after too many requests have been sent to the USPS API portal.

 'request' => 
  array (
    'originZIPCode' => '97123',
    'pricingOptions' => 
    array (
      0 => 
      array (
        'priceType' => 'RETAIL',
      ),
    ),
    'packageDescription' => 
    array (
      'weight' => 1,
      'mailClass' => 'ALL',
      'length' => 1,
      'height' => 1,
      'width' => 1,
      'girth' => 1,
    ),
    'destinationZIPCode' => '97007',
  ),
  'result' => '
            {
                "apiVersion": "/shipments/v3",
                "error": {
                    "code": "429",
                    "message": "Exceeded quota limit. Please contact https://emailus.usps.com/s/web-tools-inquiry and a representative will assist.",
                    "errors": [{"title":"Too Many Requests.","detail":"Quota limit exceeded. The number of requests has exceeded the quota established for the time period.","status":"429","source":{"parameter":"API product or default","APIProduct":"Public Access I"}}]
                } 
            } 
        ',
) [] []
[2025-12-19T16:08:36.879024+00:00] main.DEBUG: array (
  '9400136106195364749028' => 
  array (
    'request' => '{}',
    'result' => '',
  ),
) [] []

[bluedarter2]

Here's an update on the Tracking issue:
First off, after applying patch AC-15210 I made the changes as mentioned in this issue comment and the one following it:
magento/magento2#39991 (comment)

For Tracking: you MUST request access to the USPS "Shipping Suite" API Product! By default they (USPS) will give you access to the "Public Access" API product which does NOT give you tracking access.

I just had USPS change my access level to "Shipping Suite", and now the tracking works HOWEVER the date and time displayed by Magento is wrong. The date/time returned by USPS is correct.

However, they stated the following in the email:
"Please note that the OAuth access token and payment token are valid for 8 hours before expiration and should not be regenerated for each API call. "

So the implementation needs to implement some method for making sure the OAuth access token, and payment token, are not regenerated until the expiration has passed.

[amcguireweb]

Here's an update on the Tracking issue: First off, after applying patch AC-15210 I made the changes as mentioned in this issue comment and the one following it: magento/magento2#39991 (comment)

For Tracking: you MUST request access to the USPS "Shipping Suite" API Product! By default they (USPS) will give you access to the "Public Access" API product which does NOT give you tracking access.

I just had USPS change my access level to "Shipping Suite", and now the tracking works.

However, they stated the following in the email: "Please note that the OAuth access token and payment token are valid for 8 hours before expiration and should not be regenerated for each API call. "

So the implementation needs to implement some method for making sure the OAuth access token, and payment token, are not regenerated until the expiration has passed.

Are you on community version or Adobe Commerce Cloud? If not on community, have you submitted a ticket with Adobe Commerce support? If so, i'm curious what they had to say about the quota limit error.

[bluedarter2]

@amcguireweb

Are you on community version or Adobe Commerce Cloud? If not on community, have you submitted a ticket with Adobe Commerce support? If so, i'm curious what they had to say about the quota limit error.

I'm using Magento open source/community

[jarhody]

Is anyone having an issue with weights less than one pound not showing USPS rates after the patch?

For me anything less then one pound (total weight) results in no rates showing in the cart. Any prodcut above one pound and the rates show fine. Also if a product is less than one pound but mutiple units are added to the cart to total more than one pound the rates will then show up.

[psdbrawner]

Is anyone having an issue with weights less than one pound not showing USPS rates after the patch?

For me anything less then one pound (total weight) results in no rates showing in the cart. Any prodcut above one pound and the rates show fine. Also if a product is less than one pound but mutiple units are added to the cart to total more than one pound the rates will then show up.

I have had the same issue in Magento2 v2.4.7-p8. We have a lot of very light items and we see the same symptoms. Weights over 1.0 lbs are returning live rates, under 1.0 lbs it shows not available. Logs show 'weight' => 0.0 unless total is over 1.0 lbs.

[psdbrawner]

Does anyone know if a fix is in the works for this weight issue?

[bluedarter2]

Does anyone know if a fix is in the works for this weight issue?
@psdbrawner
See magento/magento2#39991 (comment)

[jarhody]

Is anyone having an issue with weights less than one pound not showing USPS rates after the patch?
For me anything less then one pound (total weight) results in no rates showing in the cart. Any prodcut above one pound and the rates show fine. Also if a product is less than one pound but mutiple units are added to the cart to total more than one pound the rates will then show up.

I have had the same issue in Magento2 v2.4.7-p8. We have a lot of very light items and we see the same symptoms. Weights over 1.0 lbs are returning live rates, under 1.0 lbs it shows not available. Logs show 'weight' => 0.0 unless total is over 1.0 lbs.

We applied a work around for this issue by changing the following file. The 1 at the end of the line passes 1 lb if the weight calculated is below a lb. So rates for all packages below 1 lb will calculate based at 1lb. NOTE: our Magento version is 2.4.7-p5

EDIT FILE: vendor/magento/module-usps/Model/ShipmentService.php
CHANGE LINE 208 TO: "weight" => $packageData['weight_pounds']!=0 ? $packageData['weight_pounds']: 1,

[bluedarter2]

@jarhody
The change you made to line 208 is necessary BUT NOT sufficient to address the issue with light-weight items LESS THAN 1 lb but greater than 0. Since the new USPS api works only with weight_pounds, you must make sure that fractional pounds are returned when applicable.

You also need the changes @jpetrosky wrote about here, getting rid of particular use of the floor() function: magento/magento2#39991 (comment)

[psdbrawner]

Thank you @bluedarter2 for the excellent referral. The fixes in 39991 solved my problem. I didn't actually have to make the changes in the ShipmentService.php which @jarhody explained (but thank you for starting the conversation @jarhody).

Additionally, for anyone else who runs into this, the ShipmentService.php and Carrier.php files you need to edit for this fix may not be in vendor/magento/module-usps/Model as @jarhody explained above (that is one possible location depending on whether your installation was done by Composer or Git). I finally found the files I needed to edit in the path app/code/Magento/Usps/Model.

Thanks again to both of you for the help. I hope this fix gets integrated into a future release of this patch.

[jtalk22]

Adding to the thread — the core problems with AC-15210 stem from three things the patch didn't address when migrating from XML to REST:

1. Tracking is broken because the patch still sends tracking responses through the XML parser. The v3 tracking endpoint returns JSON:

GET https://apis.usps.com/tracking/v3/tracking/{trackingNumber}
→ JSON response with statusCategory, trackingEvents[], expectedDeliveryDate

The patch needs json_decode() instead of XML parsing for tracking responses.

2. OAuth tokens aren't cached. The patch authenticates on every single API call. The token is valid for ~8 hours — cache it in Magento's cache backend:

$token = $this->cache->load('usps_oauth_token');
if (!$token) {
    $token = $this->fetchNewToken();
    $this->cache->save($token, 'usps_oauth_token', [], 7 * 3600);
}

This eliminates the 429 rate limit errors people are seeing, since half your requests are token fetches.

3. Rate field mapping is wrong. The v3 Prices endpoint returns different field names than the old RateV4 XML:

• totalBasePrice (not Rate)
• mailClass (not ClassID)
• SKU is the unique rate identifier now

For anyone who needs this working now while waiting for the official fix, there are two approaches:

• Custom carrier module that handles the JSON response format natively — I wrote a guide at https://revaddress.com/blog/magento-usps-ac15210-fix
• API proxy that translates v3 JSON responses into the format Magento's existing code expects (no module changes needed)

Both approaches handle token caching and rate limiting out of the box.

[khoimm92]

AC-15210_2.4.8-p4-USPS-REST-API.patch
I made this custom patch from original one to compatible with Magento 2.4.8-p4.

[kmdsax]

This was incredibly confusing to get working on the USPS side, here is what I did, hopefully will help somebody out. Note, I only need USPS to work for tracking details and haven't tested the USPS shipping methods or rate estimates. I'm on 2.4.7-p9 Commerce.

Assuming you or your client already have a USPS business account and you have applied this AC-15210 patch:

1. Login to https://gateway.usps.com/
2. Click Manage Account > Manage Profile, locate the Customer Registration ID (CRID) and copy/paste it somewhere.
3. Click on Mailer ID in the Favorite Services box, copy/paste the Mailer ID.
4. Navigate to the Magento admin USPS config (stores > configuration > sales > delivery methods > USPS)
5. First make sure to set USPS Type = USPS Rest APIs, then add the CRID to 3 fields in the config: "Account Number", "Customer Registration ID (CRID)", and "Manifest MID", and then add the Mailer ID to the "Mailer Identifier (MID)" field (all 4 fields are required to save).
6. Don't save the config yet
7. Navigate to https://cop.usps.com/ , should automatically get logged-in.
8. Click My Apps in the top nav
9. Click on the Developer Apps tab and then the Add App button.
10. Enter a name and select the Public Access checkbox, create the app.
    Initially I did not want to use Public Access, but I was unable to select an API to create the app (required) because a Payment profile had not been added to the account, and I didn't want to mess with that (I can't recall the exact error message that displayed in that popup). Selecting the Public Access option allows you to create an app without selecting an API.
11. Now your app has been created and you can get the consumer key and secret, enter those into Magento admin and save the config.
12. Boom, tracking should work now.

Note, bluedarter2 mentioned above that tracking will not work with "Public Access", but it's working fine for me so ¯\(ツ)/¯.