Important Notice from AspDotNetStorefront
It is with dismay that we report that we have been forced, through the action of hackers, to shut off write-access to this forum. We are keen to leave the wealth of material available to you for research. We have opened a new forum from which our community of users can seek help, support and advice from us and from each other. To post a new question to our community, please visit: http://forums.vortx.com
Results 1 to 5 of 5

Thread: Shipping Method Reported Stuck on UPS

  1. 12-15-2009, 08:06 AM #1
    cksite is offline Senior Member
    Join Date
    Apr 2006
    Location
    Easthampton Massachusetts
    Posts
    125

    Default Shipping Method Reported Stuck on UPS

    ML 8.0.1.2/8.0.1.2

    No matter what we do, the receipt to the customer and the order record in admin reports we shipped via UPS. The tracking number is correct

    We have a single ship method configured: "Fedex Ground US Only"
    The Rates table is set for "Calculate Shipping By Weight", and the table is populated.
    The following appconfig are set to the ID for that method: 19
    DefaultShippingCalculationID
    ShippingMethodIDIfFreeShippingIsOn
    ShippingMethodIDIfItemShippingCostsAreOn

    Still UPS persists! What else is there to change?
  2. 12-15-2009, 08:12 AM #2
    cksite is offline Senior Member
    Join Date
    Apr 2006
    Location
    Easthampton Massachusetts
    Posts
    125

    Default

    More info: This only happens when we import /export the shipping file from the distributer. This doesn't happen when we send to FedexSHip Manager.
    On the shipping import export page, Shipping Label Program UPS WorldShip is indicated with a radio button which cannot be turned off because there is no other choice.
    We suspect this has something to do with UPS being reported as the ship method only when we process shipping import export files manually from.

    There does not seem to be an app config parameter for setting Shipping Label Program used for manual import export.
    Any ideas on how to correct this problem?
  3. 02-22-2010, 08:02 PM #3
    tommytl is offline Member
    Join Date
    Sep 2008
    Posts
    34

    Default

    did you ever find a solution to this?? I'm curious too.
  4. 02-22-2010, 08:57 PM #4
    ASPAlfred is offline Senior Member
    Join Date
    Nov 2007
    Posts
    2,244

    Default

    Send into support, we got this taken care of with a patch. thanks
  5. 03-04-2010, 12:35 PM #5
    ccsorensen is offline Junior Member
    Join Date
    Mar 2010
    Posts
    1

    Default

    Quote Originally Posted by AspDotNetStorefront Staff - Alfred View Post
    Send into support, we got this taken care of with a patch. thanks
    I'm having the same issue but am running version 6.1 which and OLD version. aspdotnetstorefront says they won't support it. Is there a way I can get a copy of the patch they sent you?