So, I haven't seen this problem before, wasn't able to locate it in the forums (maybe wrong keyword search?) and a PM to a 'guide' hasn't been answered yet, so I'd like to ask the community:

On July 31st, I ordered ten books from the same person. Everything was confirmed and the order was sent through; I had confirmations on my end, emailed to me, and my order status on PBS says "waiting for member".

I got a message today from this member asking me to "close my window", because he's getting a message that says I'm still ordering stuff - even though I got final confirmations. My browser has been closed and my computer completely turned off since that time, so I don't have any open windows. (I'm not sure why this wasn't addressed days ago and not moments before the sending deadline.)

The other user can't finalize the order because of this. I even tried deleting a book and re-ordering a different book in case the order needed to be jumpstarted. No luck.

Any ideas would be appreciated!

That's an odd one, I have no idea.  Possibly an internal glitch, you may wish to contact PBS admin?
 

I haven't heard of this happening before, but please go down to the bottom right corner of any page here.  Under "company" click on "contact us" and use the Feedback option to ask the Admin Team to clear it up.

This sounds like a glitch. There is a message that comes up when there are pending requests. It tells a sender that he needs to accept all requests from this user before printing the label and he may need to wait for the 1 hour buyer's remorse period to end before he can do that.

If you don't have any pending requests, then it could be that you or the sender cancelled one of the requests; or maybe you added a book to your order and then removed it before submitting. Something confused the system.

Whatever happened, it's left things in a bad state and the sender is not able to print the wrapper. The only thing to do is use the Contact Us link at the bottom of the page under Company and see if someone at PBS can fix it for you before the transactions time out.

It looks like it corrected itself - no idea why or how, but it was nothing I did on my end!

Either way, all clear.