Interrupting work — what remains when you leave

There is no “Pause” button.

Step by step — leave the terminal

The order matters: put goods away first, then leave. Exiting the app does not remove them from you.

1. Finish or close the current item; do not leave halfway through a scan. The terminal blocks Back while it is saving.
2. Put away what you are carrying. The control depends on the mode; the table under “How to clear” lists its name. While goods are assigned to you, you cannot enter another mode.
3. Make sure you are clear: the You are carrying goods dialog should stop appearing when you try to change functions.
4. Press F7 or the Exit button at the bottom-right of the bar (✕ icon, tooltip Esc — Exit). The first presses go back within the mode, one screen layer at a time.
5. When there is nothing left to go back from, End WMS mode? appears with the message You will leave kiosk mode and return to the dashboard.
6. Confirm with Yes, exit. No, stay returns to work.

If you are only stepping away briefly, stop at step 2. Once goods are put away and the item is closed, someone else can take over without you leaving items unrecorded.

Three things people call “pausing”

1. Back

Press F7 or tap Exit in the bottom bar. It first goes back within the mode, removing one screen layer. Only when there is nothing left to go back from does it ask whether to leave the kiosk:

End WMS mode? You will leave kiosk mode and return to the dashboard.

Back is blocked while saving so you cannot leave in the middle of an operation.

2. Put away what you are carrying

This is the real way to pause. Picked goods are assigned to you, not to the screen; exiting the app, closing the browser, or ending your shift does not change that. While goods are assigned to you, you cannot enter another mode.

Back does not destroy packing. The session lives on the server and resumes when you return. Abandoning it is a separate, deliberate action that requires confirmation.

3. Someone else takes over

• Cart — a coworker scans it and confirms the takeover. You lose it immediately, without warning.
• Stocktake location — a coworker sees Location occupied, who it is assigned to, and when it started, and can take over the task.
• Locked cart — if no one is available, a supervisor releases it by force.

Automatic logout

Automatic logout is off by default. A company administrator enables it in Settings → System → Session security and sets the number of idle minutes before the terminal logs out. The administrator can exempt specific users and roles.

When enabled, a red Logging out due to inactivity bar appears before the deadline, with a countdown (“N sec remaining”) and a I’m still working button. It is pinned to the top because the kiosk bar occupies the bottom. The administrator also sets how early it appears.

Scanning counts as activity. Handhelds may inject characters without normal keyboard events, so the terminal listens for scanner input too. Scanner work will not cause an inactivity logout.

The warning vibrates once when it appears, then again 30 and 10 seconds before the deadline. Vibration is independent of the kiosk sound switch: the warehouse is noisy, and the kiosk already beeps on every scan.

A dark screen pauses the countdown, for up to 15 minutes. If the handheld wakes during that period, it gets the full warning rather than a closed door; previously, it logged out immediately on wake without warning. After 15 minutes, the session ends normally, so a handheld nobody returns to does not stay signed in forever.

Logout affects only this device. A handheld on a stand that logs itself out does not sign out anyone else using the same account.

The terminal runs the countdown, not the server. If the browser crashes, the handheld goes out of range, or someone closes its cover, logout cannot run and the session remains open. Close it from My profile → Security, where you can see every device and revoke each session separately.

The time-clock kiosk does not log out. The punch screen is shared by the whole shift, so this setting does not apply to it. It only returns to its start screen after the timeout set on the kiosk itself.