MEGATHREAD New POS

[Amanda Cantwell]

personally i think reverting a register back to an operating system that crashes when you hit the quantity button is a bad idea but what do i know, i just have the highest nps in my district 🤷‍♂️

say what you want about old pos (and I will absolutely agree) but it is lightning fast and predictable. I know the quantity button will crash it. new pos is getting better and it's *almost* there. but not quite

 

[Xanatos]

personally i think reverting a register back to an operating system that crashes when you hit the quantity button is a bad idea but what do i know, i just have the highest nps in my district 🤷‍♂️

Yeah guests keep coming back to Target for that quantity button.

 

[Amanda Cantwell]

Yeah guests keep coming back to Target for that quantity button.

exactly. if we can provide good service, guests don't care. right now I can provide better guest service (speed, overrides) with old pos.

 

[baba777]

What is this I hear about the quantity button? K2? How does that crash the system?

 

[sunnydays]

say what you want about old pos (and I will absolutely agree) but it is lightning fast and predictable. I know the quantity button will crash it. new pos is getting better and it's *almost* there. but not quite

i find classic to be extremely fast, extremely unreliable, and extremely unpredictable. i am glad that your mileage is different, but there is a reason why target is running away from it right before q4

What is this I hear about the quantity button? K2? How does that crash the system?

if you change quantity of an item during a return it will hard crash classic registers, full stop. so if someone is returning 50 cans of cat food you have to scan all 50 cans instead of scanning one and changing the quantity

Yeah guests keep coming back to Target for that quantity button.

no but they certainly don't like it when a register crashes right in the middle of you trying to do a return. great service!!!

 

[Anelmi]

They also don't like it when you can't do a direct exchange but again, that's not a big deal and perfectly okay from a guest service standpoint according to you. My store also has the highest NPS in the district with IGS and no SCO so what do I know?

 

[REDcardJJ]

average speed of transaction is faster across the chain on new point of sale compared to classic. just putting that out there.

 

[sunnydays]

They also don't like it when you can't do a direct exchange but again, that's not a big deal and perfectly okay from a guest service standpoint according to you. My store also has the highest NPS in the district with IGS and no SCO so what do I know?

no, it's really not a big deal

 

[Amanda Cantwell]

average speed of transaction is faster across the chain on new point of sale compared to classic. just putting that out there.

i wonder what would happen to those metrics if they included first transaction setup time. (Logging into pos, etc). Linux versions I’ve heard are better but as it stands the time it takes me from walking up to a lane to being able to scan an item is embarrassing, literally. It’s an awful guest experience to be staring at the cashier for 30 seconds before they can do anything.

 

[Atlas First]

Yeah for some reason the electronics registers are mad fast. I was closing the lanes and logging into them was like almost instant. If all the registers were like that then no one would have a problem logging in or switching apps. Weird only electronics has it hmm

 

[sunnydays]

i wonder what would happen to those metrics if they included first transaction setup time. (Logging into pos, etc). Linux versions I’ve heard are better but as it stands the time it takes me from walking up to a lane to being able to scan an item is embarrassing, literally. It’s an awful guest experience to be staring at the cashier for 30 seconds before they can do anything.

sounds like you've got the first half down (service), now it's time to master the second half (engagement)

 

[TurgetCirkl]

Yeah for some reason the electronics registers are mad fast. I was closing the lanes and logging into them was like almost instant. If all the registers were like that then no one would have a problem logging in or switching apps. Weird only electronics has it hmm

When they do test builds of registers they usually give it to the places outside of the lanes (in my experience) like SB and Electronics. Back then when they were first configuring linux to run on the registers it was SUPER buggy. It got so bad that they couldn't fix it they bricked the registers. Now though, it is soooo nice. Since this is a web based POS system they can run it on practically anything.

EDIT: Since it's web-based if they improve the memory management (which linux takes up a lot less ram than windows) it can cut down login times.

 

[NotCynicalYet]

Just talked with my etl last night and they said that they couldn’t do it…idk if they’re just lazy or don’t know how or what but that was the end of that conversation…and btw the classic register was crashed again…

Our second classic got re-reverted and we're back to one. This is sadistic.

 

[NotCynicalYet]

personally i think reverting a register back to an operating system that crashes when you hit the quantity button is a bad idea but what do i know, i just have the highest nps in my district 🤷‍♂️

I hope your NPS doesn't suffer from people not being able to pay bills or the other missing functions.

 

[NotCynicalYet]

say what you want about old pos (and I will absolutely agree) but it is lightning fast and predictable. I know the quantity button will crash it. new pos is getting better and it's *almost* there. but not quite

I did a qty of 128 on classic the other day. It worked, but what an adrenaline rush. Better than skydiving. (ed: forgot it was a purchase not a return, which would explain why it worked. Still scared me though)

 

[sunnydays]

I hope your NPS doesn't suffer from people not being able to pay bills or the other missing functions.

well there are no other missing functions i can’t do workarounds for other than payment on account and you know, i have a classic register just for that like everyone else and that’s all we use it for. so, no problems

 

[REDcardJJ]

if you only use the classic register for things that the new point of sale cannot do, it will not crash for when you actually need it

but the fact that you’re all seeing so many crashes speaks volumes about why switching off of classic was necessary

 

[Guest Avocado]

I get that JJ, but when you're a store like mine that is a High Volume Super with 1/3 Service Desk registers on New POS, Classic POS tends to be used a lot more than it has to with the length the lines can get sometimes.

 

[baba777]

I voided a return on the guest selects reason on pin pad screen. In the background while it was voiding it showed the reasons on the screen. Hopefully that means we’ll be able to select it and not have the guest do it each time.

Apparently we can’t do Consumer Cellular phone returns on the New POS. When I scanned the receipt and item barcode at GS, it popped up with “item must be returned at Tech”. Went down to tech, scanned the barcode and IMEI, and it said “item not eligible”. Had to do it on the old POS.

 

[sunnydays]

phone returns have always been weird, tbh

 

[TurgetCirkl]

I voided a return on the guest selects reason on pin pad screen. In the background while it was voiding it showed the reasons on the screen. Hopefully that means we’ll be able to select it and not have the guest do it each time.

Apparently we can’t do Consumer Cellular phone returns on the New POS. When I scanned the receipt and item barcode at GS, it popped up with “item must be returned at Tech”. Went down to tech, scanned the barcode and IMEI, and it said “item not eligible”. Had to do it on the old POS.

This. It was SUPER weird. I tried it the other day because it was the wrong phone for the guest and when I scanned it it said activation didn’t match which was weird because I didn’t scan the activation in the return. Not very many things with activations are returned so i see this being a minor problem for now.

 

[Atlas First]

This. It was SUPER weird. I tried it the other day because it was the wrong phone for the guest and when I scanned it it said activation didn’t match which was weird because I didn’t scan the activation in the return. Not very many things with activations are returned so i see this being a minor problem for now.

phone returns have always been weird, tbh

Speaking of phone returns….this happened today. Can anyone please explain this cause no one even hardline 4 etl had no idea what’s happening. I tried to cut out all the information about the store as much as possible and Rec num.

I did return on classic POS. Scanned receipt from guests phone, scanned the iPhone, POS asked $35 waive would be charged. Said ‘continue’. Asked ‘Is there anything wrong with these items?’ Said no (to defect later since this was the second time doing this return). Afterward the POS does some weird screen glitch and basically does the $35 restock fee automatically. I hit total it show the recommended refund back to ‘credit’. Ask guest to insert a credit card (only once!) and then POS shows recommended refund screen again with $16 and some change. Recommended refund doesn’t work so I go back to the scan items/receipts screen and the press total again. Pretty sure I didn’t hit nothing but it randomly says ‘This cannot be zero’ then I hit clear and it pops the drawer open by itself saying change due that $181 amount at the bottom. Does anyone have any idea cause none of the totals make sense and the card was only put it once so ideky there 2 credits back.

 

[DBZ]

Those visa credits and change due????? WTF??

 

[Anelmi]

That has happened to me once or twice on classic POS but usually when doing a same day return and then applying $$ toward new purchase. It is super confusing and usually results in the guest getting more $$ back than they should but restarting the return doesn’t fix the issue.

 

[Atlas First]

That has happened to me once or twice on classic POS but usually when doing a same day return and then applying $$ toward new purchase. It is super confusing and usually results in the guest getting more $$ back than they should but restarting the return doesn’t fix the issue.

It was a pickup from the day before and I remember because I did that too.