Skip to main content

UPS - User Id and Shipper Number combination is not qualified to receive negotiated rates.

Today I started to receive the following message from the UPS API:

User Id and Shipper Number combination is not qualified to receive negotiated rates.

and to make matters worse, the result of this issue caused the checkout process to error preventing our customers from finishing their orders.

So after doing a little research on my end I ended up calling the UPS technical support phone number for the United States:

Over the phone we went over the following steps:

UPS.COM
You must add and authenticate your account using Account Summary to view Negotiated Rates in UPS Internet Shipping, Time and Cost Calculator on ups.com, and the UPS Developer Kit - Shipping and Rating APIs.

To add and authenticate an account:

1. Login to ups.com using your My UPS ID and password.
2. Select the My UPS tab at the top of the page.
3. Select Account Summary from the navigation menu or the tab rollover.
4. From there select Add an Existing UPS Account.
5. Follow the steps to authenticate the account. To authenticate your account you will need the following information from your most recent UPS invoice: invoice date, amount due, invoice number, and control number.


Normally this should work but for us it did not because we already did those steps. My case was escalated and I am waiting for a call back.



I disabled UPS on the website so our customers could still place an order.  Now I can breath a little easier.

I will update this post with the resolution as it becomes available.

*UPDATE at 1:57pm*
UPS called me back and told me there is a global outage for negotiated rates.  They estimate a minimum of 2 hours to restore access.

Comments

Popular posts from this blog

How to get ProxyPass to ignore a URL so you can still use Apache HTACCESS

On a few of my servers I use Apache with Apache Tomcat. and ProxyPass to forward requests from apache over to Tomcat for my Coldfusion pages. The part I have been struggling with for so long was how to do password protected directories in apache.  Either by adding the config to the VirtualHost directive or by .htaccess. It seemed no matter what I did, requests were getting proxied and there was nothing I could do about it. Tonight I finally found my answer: The ProxyPass !  combo: ProxyPass /dealers/ ! Here is the whole apache configuration I use for connecting Apache to Tomcat and URL Rewriting: I found this mentioned on a  Sitepoint Post

Jetty Locking Files on Windows

I went to edit a css file today on a server an OpenBD Jetty install and the file was locked.  After doing some research I found this  http://docs.codehaus.org/display/JETTY/Files+locked+on+Windows I chose to just stop and restart Jetty because I was on a dev box.  The instructions seem to be straight forward. My question is though.  If I disable the memory mapped files will there a performance degradation?