Ever since the ShipRush software was updated a few months back, my UPS end of day has begun to error out on occasion. It has happened twice now. Despite temporary fixes from the ShipRush support team, I was told that this is most likely an issue on our 3rd party software connected to ShipRush's end. We have had the same coding for 10+ years, and the issue NEVER happened until this update, and has since happened twice. I was told that certain shipments show up as USPS in the UPS directory and that is causing the problem. Is there some kind of new coding that needs to be put in on our end? I tested by scanning a package that was for UPS, the label printed as UPS, but showed in shiprush as a USPS priority mail order.

There haven't been any specific changes to cause this type of issue. If it shows up as USPS Priority Mail, that would indicate that the value that your SDK app is passing for service is incorrect. Are you able to re-create the specific call for the shipment you see that is set as USPS Priority Mail? It would need to be reviewed.

The odd thing is that the software that we use hasnt changed in 10+ years. Then all of a sudden, we began to experience this issue. When you say re-create the call, do you mean simply trying to scan the package again and see if it shows up the same as before?

Would this be something that a senior tech could remote into the PC and assist me with?

When I say re-create the call, I mean, process the shipment again through your app that is using the SDK for ShipRush
Do you see the same issue in View Shipments?

Launch ShipRush itself and dial up the shipment manually and create the shipment (leave the SDK out of the process)
Do you see the same issue in View Shipments?

If you can replicate with either of the above, we need to more information. If you can replicate with the SDK connection, then we would need to know:
- What type of SDK connection is being used?
- Your actual call to our SDK (so we can review the data being sent to ShipRush to cause the issue)

I'm the developer for them and we are using the Browser Integration method. I have 2 examples. Both examples were shipped using USPS First Class Mail and then example 1 shows up in the daily report as UPS Ground and example 2 shows up in the report as USPS First Class.

The first part of the link for Example 1 is as follows (I'm not posting all of the link so as to not expose the customer data):
nntp://ship?Carrier=Endicia&ShipmentXML=%3c%3fxml+version %3d%221.0%22%3f%3e%3cRequest%3e%3cShipTransaction% 3e%3cShipment%3e%3cUPSServiceType+Value+%3d+%22U01 %22%2f%3e%3cDeliveryAddress%3e%3cAddress%3e%3cFirs tName+Value+%3d+%22bill

The same part of example 2 is as follows:
nntp://ship?Carrier=Endicia&ShipmentXML=%3c%3fxml+version %3d%221.0%22%3f%3e%3cRequest%3e%3cShipTransaction% 3e%3cShipment%3e%3cUPSServiceType+Value+%3d+%22U01 %22%2f%3e%3cDeliveryAddress%3e%3cAddress%3e%3cFirs tName+Value+%3d+%22Donna

This code has been in use untouched for several years.
Attached is a screenshot of the report.