How can you force the Square POS to logout after each transaction? My staff are not logging in to record their sale and all sales are going to "Untracked Sale". There should be a way to force them to login - they'll get used to it.
Open the Square App and sign in with your owner email, or a device code. If you sign in using a device code, be sure to enter your passcode with permissions to manage settings.
From the navigation menu, tap Settings > Security > Passcodes > Enable Passcodes.
Under Require Passcode, select between After Each Sale, After Log Out, or When Backing Out of a Sale to cancel a payment.
Enter your passcode to save these changes.
Select a preferred time-out period for the Square app.
Tap Log Out on the bottom right to allow your team members to log in and begin accepting payments.
Is it possible for the Square Terminal to Power On into the Passcode code entry screen first, instead of going straight to the Charge screen ready to Charge?
Thank you for reaching out! Welcome to our Seller Community 😊👋
At this time, it's not possible for Square Terminal to power on and require a passcode first.
I can see how this would be a useful feature, and will share your feedback with our team for consideration.
The closest option to this would be to require an employee passcode after timeout. When your point of sale is inactive for a set amount of time, it will ask for the passcode.
To enable this, tap on the three lines in the top left on your Square Terminal > Settings > Security > Require Employee Passcode > After Timeout > Select a time > Save 👍
We have the timeout set already. The best reason why it is useful for passcode login on starting up is to avoid someone who is not authorised to use the terminal in any way on Power On.
Also, under the current operation, the Team Member who charged the first transaction is not captured.
@steviet Totally understand this would be useful for your business! We'll continue tracking this feature request in this thread and I will comment back if I hear anything. To be transparent I've not heard anything about the possibility of this one either way at the moment, but I'll pass on your feedback - it makes a good case.
Thinking of a few alternative ways of doing things here as a workaround in the meantime:
Would it be easier to simply not turn the Terminal off? It doesn't use much power when it goes to sleep, so not turning it off until a time you absolutely need to could help avoid needing to enter a passcode. This seems like the simplest solution!
If you want to stick to turning off the Terminal, you could also sign out of the app. It would mean you need to manually sign-in with your username and password each time, but it's one way to block someone from being able to turn on Terminal and take a payment.
Let me know more about what you don't want staff to be able to do upon turning on the Terminal. Provided you have permissions set up, there isn't much more they'd be able to do than take a sale, depending on what permissions you've given them.
Hi, We just upgraded to Square for Retailer and noticed that the logout after each transaction is not an option anymore. We use to use point of sale and relied on that feature to track sales for each staff member. It looks like this thread touches on this a bit.
We would love if that feature could be added to square for retailer. We don't like the timeout option because sometimes we have transactions that last more than 5 mins or have multiple transactions done within 5 mins and it could be more than one employee using the register.
While I don't have much experience using Square for Retail, though took a look and was not able to find these options in the Square for Retail app. I was able log in/out manually, but not perform an automated sign out at the completion of the sale - is this specifically what you were looking for?
EDIT:
One thing you can try is this:
Sign into Squarer Point of Sale > Go into the applicable team settings > Turn ON “After each sale” > The force quit the Retail app > Re open Retail and test again. This may cause the settings to be retained, but I hear it's hit and miss. We do plan on properly building this feature as soon as we can - hopefully later this year, though I don't have a firm ETA.
