Thanks for the update Mike. Look for to the solution. 

Darrick

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

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

jepritch - Thanks.  are you saying the existing buttons will now work?  The user clicks on the tracking button as they have in the past?

Yes, exactly.  We changed the service that receives the request.

Worked for UPS and Fedex. 

I tested this and it worked for me.