I am using UPS for shipping method and set the shipping origin to colorado USA, products have set their weight but i am getting only three shipping methods to ship I am on CE 1.7.0 i have checked with another installation with same version and that working great, so i have copied the shipping module to my live site and this is super unfortunate that tihs is not working.

United Parcel Service

    Next Day Air Saver $99.97
    Next Day Air $107.35
    Next Day Air Early AM $140.65

Note : I have set up all the conditons to a test site with same CE 1.7.0 version there they are working fine but for live site only three rates are coming.

Any idea for this.


closed as too localized by Ben Lessani - Sonassi, Marius, Fabian Blechschmidt, davidalger, philwinkle May 14 '13 at 18:52

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center. If this question can be reworded to fit the rules in the help center, please edit the question.

  • Before you started this process, what was selected in System Config -> Shipping Methods -> UPS -> Allowed Ship Methods? – Fiasco Labs May 11 '13 at 16:48
  • We were testing for second day air a.m. as it were not populating and some general methods was selected ground and next day air.. for canada and US only. – ravisoni May 11 '13 at 17:28

Ok folks i have solved the problem

I have searched for all ups setting in core_config_data table and delete all the entries

the query was select * from core_config_data where path like '%ups%' deleted all the records and re-save the settings this solved the problem.

Hope this could help some one.

  • Don't edit the database directly. Ever. – Ben Lessani - Sonassi May 11 '13 at 11:40
  • 2
    The trouble is that you're probably in this position because you've manually edited the DB in the past. Its a continuous circle. Thankfully there is no keys to be broken in core_config_data - but we don't advocate editing the DB under any circumstance. Its a road to ruin ... – Ben Lessani - Sonassi May 11 '13 at 13:52
  • 2
    @sonassi I hate to disagree with you, but there is no harm done by altering the config tables in this way. And for what it's worth, Magento has put out bulitins which walk one through doing things directly with the database such as clearing out test order data. It's a matter of knowing what not to touch apart from the resource model layer, and this is not one of them. – davidalger May 11 '13 at 16:22
  • 2
    @davidalger - I agree with you. But my (sweeping) comment was pointed at those not "in the know". More often than not, there isn't a use case for editing the DB directly - and unless the person doing it knows exactly what they are doing (the OP in this case didn't); then there is much more room for harm than good. Files are repairable - databases are not. Once you've screwed up a foreign key relationship; its not easily seen, and it will cause lasting effects. – Ben Lessani - Sonassi May 11 '13 at 16:26
  • 1
    @sonassi - That being clarified, I will agree with you! :) – davidalger May 11 '13 at 16:29

Not the answer you're looking for? Browse other questions tagged or ask your own question.