• Everyone, please help make our jobs easier and choose the correct category. Thank you

Scanner doesn't beep on scan for pkg pickup?

FirstclassPITA

Well-known member
Is it just my scanner that doesn't beep when it scans a package as accepted while doing a pick up? Works fine under "h" and beeps but when i am doing my rrecs activity "o" scans it is silent and annoying. Use to beep and now it stopped and i dunno how/if i could fix it?
 
Is it just my scanner that doesn't beep when it scans a package as accepted while doing a pick up? Works fine under "h" and beeps but when i am doing my rrecs activity "o" scans it is silent and annoying. Use to beep and now it stopped and i dunno how/if i could fix it?
So, let me see if I have this straight . The scanner beeps every 5 minutes while you are loading the vehicle when there is absolutely no need for a beep and the scanner beeps every 5 minutes while you are on EOS time when there is absolutely no need for a beep but when you actually need the beep or the beep would be of some assistance to you, there is no beep.
 
So, let me see if I have this straight . The scanner beeps every 5 minutes while you are loading the vehicle when there is absolutely no need for a beep and the scanner beeps every 5 minutes while you are on EOS time when there is absolutely no need for a beep but when you actually need the beep or the beep would be of some assistance to you, there is no beep.
Lol hahaha now that you put it that way lol
 
So, let me see if I have this straight . The scanner beeps every 5 minutes while you are loading the vehicle when there is absolutely no need for a beep and the scanner beeps every 5 minutes while you are on EOS time when there is absolutely no need for a beep but when you actually need the beep or the beep would be of some assistance to you, there is no beep.

Explain to me how you can change the process by elminating the beep and ADDING AN EXTRA STEP to it. I had 4 packages to pick up and I had to scroll and check scanner to make sure I actually scanned them. Where's my $$$$$$$$$$$????

BUILT IN?!?!?!?!? Where's the union???????????
 
Explain to me how you can change the process by elminating the beep and ADDING AN EXTRA STEP to it. I had 4 packages to pick up and I had to scroll and check scanner to make sure I actually scanned them. Where's my $$$$$$$$$$$????

BUILT IN?!?!?!?!? Where's the union???????????
Oh, you don't have to tell me. There is / are the extra step(s) while on loading and EOS time. Then, the extra step of taking a pic. of the parcel. Now, there is the extra step in the scenario you have explained. Make no mistake, this is NOT and will NOT be the last extra step we encounter. The PO has , since the inception of carrier pickup scanner documentation, used a benchmarking practice / technique to limit our credit for this task. That's why it cuts us off at 5 parcels. The original language in Pub. 399 stated , " It is not required that the carrier scan each piece if a large quantity of parcels ( 6 or more ) are being picked up." You'll notice that this does not state "prohibited from" or "must not" . Only "not required". Doesn't mean we can't. Kinda' like we are not required to go to the door with a parcel that will fit in the box but WE CAN. And, we are not required to go to the door with a postage due that will fit in the box but WE CAN. All of this rhetoric regarding "scanning integrity" is just that. Hollow words. Yeah, I know many carriers scan as prepaid acceptance while on EOS to account for the parcels as well as increase their actual time through EOS. The thing is this, the customer's insurance doesn't take effect until the parcel is scanned as picked up. One of these days, after a carrier picked up a customer's 10 parcels, that customer is going to check into their pickup and wonder why only 5 of their parcels were scanned as picked up. And they are going to complain. Now, the carrier can do the other 5 as prepaid on the street and the insurance and all of that is good to go. But, that carrier is being shorted on the actual RRECS standard for carrier pickup items because the PO benchmarked / limited the number to 5 under the correct and accurate function. The PO wants the business but they don't want to pay for it. We do need proactive , aggressive, and expeditious representation on all of this. This "wait and see" , "after the damage / harm has been inflicted" , "only if the carrier recorded / documented " , etc. is NOT the way to handle any of this.
 
Oh, you don't have to tell me. There is / are the extra step(s) while on loading and EOS time. Then, the extra step of taking a pic. of the parcel. Now, there is the extra step in the scenario you have explained. Make no mistake, this is NOT and will NOT be the last extra step we encounter. The PO has , since the inception of carrier pickup scanner documentation, used a benchmarking practice / technique to limit our credit for this task. That's why it cuts us off at 5 parcels. The original language in Pub. 399 stated , " It is not required that the carrier scan each piece if a large quantity of parcels ( 6 or more ) are being picked up." You'll notice that this does not state "prohibited from" or "must not" . Only "not required". Doesn't mean we can't. Kinda' like we are not required to go to the door with a parcel that will fit in the box but WE CAN. And, we are not required to go to the door with a postage due that will fit in the box but WE CAN. All of this rhetoric regarding "scanning integrity" is just that. Hollow words. Yeah, I know many carriers scan as prepaid acceptance while on EOS to account for the parcels as well as increase their actual time through EOS. The thing is this, the customer's insurance doesn't take effect until the parcel is scanned as picked up. One of these days, after a carrier picked up a customer's 10 parcels, that customer is going to check into their pickup and wonder why only 5 of their parcels were scanned as picked up. And they are going to complain. Now, the carrier can do the other 5 as prepaid on the street and the insurance and all of that is good to go. But, that carrier is being shorted on the actual RRECS standard for carrier pickup items because the PO benchmarked / limited the number to 5 under the correct and accurate function. The PO wants the business but they don't want to pay for it. We do need proactive , aggressive, and expeditious representation on all of this. This "wait and see" , "after the damage / harm has been inflicted" , "only if the carrier recorded / documented " , etc. is NOT the way to handle any of this.

Still never forgot the whole IMPLEMENT & FIX LATER!!!!! Well....... We're waiting............ Relying on your carrier TO DO WHAT IS OUR UNION'S JOB...


ted enjoy GIF


I mean everyone gets mad at NLCA, but at least I feel like they have some sort of intelligence about things. NRLCA is bow down to the master no matter what they ask to do.
 
They must be messing with things because I didn't get confirmation beeps when scanning the blue collection box for a couple days, this past week.
Oh, rest assured , they are ALWAYS messing with things. I think what happens in instances like this is that they inadvertently get caught by the scanner. They were not aware of the "silent scanner" during carrier pickup and now your collection box but they know now. Can there be an isolated instance here and there with a legitimate scanner / battery malfunction ? Sure. However, that issue would tend to be experienced for all of the other scan functions and duties and NOT specific categories.
 
Back
Top