Without seeing the actual shipping label, it’s only speculation why it ended being RTS (return to shipper). With my 3 decades of service it was most often due to an unreadable address label caused by another package cutting, scraping, smudging, spilling liquid, smeared ink, etc... across the address, zip, or nowadays the barcode. Poor package handling and automatic belts are brutal on packages, especially the unprotected shipping labels.
Automatic reading/sorting machines can’t scan it at someplace along its journey, and it gets kicked out to be read and hand corrected by a person. If they can’t read it, the package can be opened to see if any address is inside, providing no package invoice is attached to the outside. If after all that it still can’t be corrected, resorted and finally delivered, it is then RTS, providing that shipper can be determined.
What should have happened is the manager/designated employee should have just gone to the address correction area and try to locate the package where it was just sitting, waiting to be corrected/or RTS. But apparently too much time had passed and it was just RTS.
What the CS department at BHQ should have done, either with empowerment or permission, is simply put a hold/BOLO on the RTS package, and once it’s delivered back to BHQ, it simply gets repacked and a new shipping label affixed, and shipped out once again to the OP.
Only because the original email that the OP sent BHQ is not posted, just him telling the facts, we here can only guess if it was a clear and concise email with all pertinent details, leaving out presumption and frustration.
Lots of customers would like to tell of their frustrations and all they went through, before getting to the facts that we could then use to solve the problem. It could turn a 2 minute fix into a huge wasted delay, especially when a particular fact was absent or embellished (I’m not saying that is what happened here).
I’m glad the OP was able to get another in it’s place.
Just my opinion on CS/RTS packages.