Great post very interesting. With this produce issue... it happens a lot!!
I don't understand the quantity issue... if you put something through as 2 x an item why wouldn't it count it as 2 items?! It might speed up the scan rate but self-serve has the lowest scan rates out of anyone on registers!
You are either a really bad troll or an imbecile. It is your responsibility to check your roster. I mean how hard is it to look at a piece of paper once per week?
I don't get it either... But thats what Area Champ said, so I dunno. I always use quantity on NCR, so I reckon Ill use it heaps on WoWPoS SCO too.
So you have 7 staff that get regular service shifts? lol, wow. We don't even have a 3IC. We have the CSM, 2IC, another full-time supervisor (who's on holidays at the moment). Then there's me I work full-time between front end and office, another girl that does Wed night and Sat and another girl that does Mon & Tue nights (but shes on holidays too). We have just enough staff with 6 but if anyone wants a day/night off for some reason we are pretty screwed.
So, I don't get what you're saying.. what are the customers doing? Weighing 2 apples, putting them into the bag, then putting another 2 apples into the bag as well without weighing them? lol.
Haha, wait, on normal checkouts? Silly... any reduction of hours from the use of the quantity button (that only a handful can use) would be negligible. And it's only fair, it does take less time to process an order if you use it, so why should you have more hours
ok for some reason the self-serve machine is set to accept any weight for produce items, so if someone weighs 4 apples (not in a produce bag) say the total was 1kg, then they place 2 of them in the bag, the security scale thinks that 0.5kg is the weight of the apples (i.e. 2 apples), then they put the next 2 apples in the bag and the self-serve thinks that they haven't scanned those apples = unexpected item, assistance requested > attendant comes over > store log in > checks list > 4 apples weighed and 4 apples in the bag, everything fine but the sco thought something was wrong!!
very close! its to do with SMS hours for frontend. Basically they work out how many items are produce items, as well as items that are marked down (for anybody that is still using hand-written markdowns) and give frontend a certain percentage of extra hours, based on the fact it takes the few extra seconds to find the item in the drill down menu's. This is an issue for the long-term as if you are constantly using quantities rather than scanning each individual item, they will cut back those hours.
Ok, so you get the people that don't want to put their produce in a bag, so they put all the individual apples on the scale, weigh them as normal, but then have to put a couple in to the bagging area, then a couple more etc. I believe with WoWPoS SCO to eliminate lots of weight issues fresh stuff is entered into the system as 'Accept any weight'. When the customer puts the first couple of apples into the bagging area it accepts that as the weight, so when they put the next couple it thinks its an unscanned item.So, I don't get what you're saying.. what are the customers doing? Weighing 2 apples, putting them into the bag, then putting another 2 apples into the bag as well without weighing them? lol.
Haha, wait, on normal checkouts? Silly... any reduction of hours from the use of the quantity button (that only a handful can use) would be negligible. And it's only fair, it does take less time to process an order if you use it, so why should you have more hours
Yeah, that makes sense. Thanks for clearing that up. I think I will still be using quantity though, cause no customer likes to stand there and scan 20 cat foods or 20 tuna cans.
Oh, okay, I see. I can't speak from experience but the impression I got from the trainer was that the SCO knows how much to weight to expect in the bagging area because the item was just weighed. This seemed straight forward to me, but someone a bit slower in our group asked (when he was saying customers can ring up their own produce items) "how does the machine know I'm not putting more than what I've weighed?" lol and the trainer was sort of like.. well they've just weighed it so it's going to expect that (duh).Ok, so you get the people that don't want to put their produce in a bag, so they put all the individual apples on the scale, weigh them as normal, but then have to put a couple in to the bagging area, then a couple more etc. I believe with WoWPoS SCO to eliminate lots of weight issues fresh stuff is entered into the system as 'Accept any weight'. When the customer puts the first couple of apples into the bagging area it accepts that as the weight, so when they put the next couple it thinks its an unscanned item.
I can see the merit behind eliminating weight requirements for fresh items (especially meat/bakery and quantity produce) but since the SCO knows the exact weight of the produce (since its just weighed it) surely they should have kept it the same as NCR
About the quantity - this is on SCO - I really don't know it either, but she specifically told me to limit the use of it, and that she doesn't like her staff using it all on SCO. Seems a bit pedantic to me.
Yeah, that makes sense. Thanks for clearing that up. I think I will still be using quantity though, cause no customer likes to stand there and scan 20 cat foods or 20 tuna cans.
edit: Oh no! Now I keep saying 's-ko'! They've got me already!
I know when we were roleplaying attendants and customers we were working out ways to cheat the system and we would try saying 1 avocado but putting 2 in the bag and the SCO didn't pick up anything at all. But then again, we just assumed it was still learning the weights of things, since you have to weigh an item 15 times or something before the average weight gets assigned... *shrug* 
We have
Lol, pretty sure I know the store mgr there.
Incorrect use of the quantity function at woolworths has the potential to cause a lot of problems with the automated stock replenishment system (ie. automatic ordering). Unless each SKU is 'quantitied' separately, the SOH counts will become incorrect.