I think it's only you seeing this because a cookie is set, or you are logged in to an account that has an address established.
Try using a browser you never use, and do not log into any account.

Thanks,
David

Still haven't had much luck so far with fixing our rates, tried the XML line query on our PHP end but did not have any luck. I've reached out to UPS to see what they can do, otherwise I did peak into our XML Logging and did see that it is actively requesting Negotiated Rates based on this line:

ShipmentRatingOptions":{"NegotiatedRatesIndicator":"Y"}}}}

But somehow returns published it seems.

Hi Mafluet
How about adding the parameter …
$dumpshippingxml=TRUE;
…to your includes.php file then try getting rates and then send that JSON that should appear to UPS. It really seems like the request is ok as if you don’t have the default ship state and request negotiated rates, UPS will error. So for some reason they are not completing the request and the answer will probably be in that JSON.

Vince

Click Here for Shopping Cart Software
Click Here to sign up for our newsletter
Click Here for the latest updater

dbdave, I wasnt logged to begin with. I had a new private tab open when I made the addition of defaultshipstate= and then after I added the parameter then upon refresh my state became the default. Furthermore, I opened new private tabs on Chrome, Firefox, and Edge and without logging in I saw the same behavior from my pc. To just make sure even further, I opened up a new Safari tab on my phone and saw the same as well as a new private Chrome tab on an Android and saw the same result.

3 devices, using 5 different private tabs, none of which are logged in, all showing the same result, which has a clear correlation, and can be reverted back by removing the defaultshipstate= parameter.

I’m fairly certain that I am seeing this correctly that defaultshipstate= is doing it’s job correctly. It’s intended to make the shipping estimator’s default state to what you want it be.

The issue is that I dont want there to be a default state. Removing the parameter breaks the new UPS setup.

Imo, the addition of a new parameter such as UPSdefaultshipstate= could give UPS what it needs while not disrupting the defaultshipstate= which I want to remove so I can have no default state pre-selected in the estimator / checkout