Summary Package Tracking Inquiry - Bad Request Error

SOLVED

Hello,

Recently, when we are using the "Package Tracking" button in the "Summary Package Tracking Inquiry", it does not show the tracking information anymore.  Rather, it gives a 400 Bad Request Error (please see the screenshot below).  Can anyone advise on how we can fix this?  Thank you!

Parents Reply Children
  • +1 in reply to btmlinesoft
    verified answer

    Hi everyone,

    Sage has implemented a replacement package tracking for iShip.  This new implementation is now live and is used in both Sage 100 and Sage 500.  The new implementation will now use the tracking id, to determine which carrier it belongs to and re-direct to the appropriate site.  The carriers that this will handle automatically will be USPS, UPS, Fedex, DHL, and Ontrac.  If the package id is not determined to be one of the aforementioned carriers, it will be re-directed to a google search with that package id.

    In Sage 100, this will work from any package tracking buttons (ie Shipping Entry) and for paperless emails that use the embedded tracking token [TrackingNo]

    Thanks

  • 0 in reply to jepritch

    That's awesome! I just tried it. Although I wish it had the major LTL carriers like my personal fav...ABF that's not a problem to look it up from the google search page. Thanks!!

  • 0 in reply to jepritch

    Would you be able to share the RegEx pattern or logic that you're using to determine the carrier from the tracking number so we could add this to our Sage100 integrated portal?