It's 11AM, I've drank 10 beers so far, so I'll ramble a little bit more.
Another problem is with the dispatch supervisors - the program they use to cut the inbound volume to specific routes won't "see" arbitrary amounts of volume if a proper End-Of-Day wasn't done by the shipper, or by other UPS hubs (most notably, WorldPort - when they screw the pooch on EOD it's a massive problem for the entire network). This isn't really a problem in-and-of itself, but depending on the route levels on any given day, a specific stop (e.g. bulk stops or straight-line residential areas) may or may not be on a certain route. If the PDS doesn't "see" it, it may not wind up on the right route. There is, of course, the fall back of where the specific plan being run will assign it, but it isn't always right.
My understanding is that if a shipper has continual problems with incorrect information, sales is supposed to be contacted, so they can in turn contact the shipper to correct the problem. Now, I don't have to tell most of you that contacting sales probably isn't worth a buffalo poop on a nickel. So, the clerks just get the same incorrect information every day, all day. Maybe it could be corrected in AMS, but one limitation (of many) on that system is that you can no longer (you used to be able to, but not anymore) alias certain addresses to another address in another zip code. So, if the shipper constantly stamps the wrong zip on a package, your pretty much SOL.
Sounds crazy, but the reason why you can't alias outside a specific zip code anymore is because IE got wind that every PDS and his mom was using AMS to "quick fix" problems instead of going back and editing a hundred dispatch plans - which is pretty time consuming. So, the feature was removed and now you get more NIS's and blanks than ever before.
I should add that I'm not a PDS, don't do dispatch, and haven't been trained in any of this. It's just what I've pieced together myself; I could be right, I could be wrong, I don't know.