One device can serve several people
A counter device may be used by many colleagues in turn. Sharing a device is not a reason to share a user account. Otherwise later questions about an order, payment or time entry are harder to answer. Decide how each person signs in and how a change between colleagues becomes visible. Bonzumo offers personal identity and roles as a framework for that attribution.
Test the handover during a busy period, not only on a quiet morning. If switching is awkward, shortcuts emerge: one person carries on under the previous name or a shared code is kept by the screen. That signals a device and shift flow needing improvement. A short, clear login does more for traceability than a long policy nobody can follow.
Make shift start a deliberate handover
At the start of a shift, a colleague checks the workstation, open tables and assigned tasks. Add identity change to that routine. Who is signed in, which role is active and which open transactions were started by someone else? A new login should not hide an open table bill, but new actions should not inherit the previous operators name.
Have two colleagues serve a test table in turn. The first enters the order; the second later handles a change and a payment request. Both should be able to explain what they did and what was already true when they took over. Identity then becomes practical. It supports cooperation during service and later questions from a shift lead.
Keep checkout and time entry distinct
A checkout workstation may be close to a time clock, yet “I am on duty” and “I am handling this sale” are different actions. An open checkout screen should not be treated as proof of worked hours; a time punch should not decide who owns a payment. Explain the purpose of both routes and let new staff practise them separately.
For example, a colleague starts a shift, takes over checkout later and has a break in between. Payment and working time each need their own status. Bonzumo includes team and sales areas; setup should make the transitions clear. Where several devices are used, note where each action happens and who reviews a wrong entry.
Do not borrow someone elses privileges
A service colleague needs approval for an exception. A tempting shortcut is to hand the device to the shift lead and then continue working under the leads account. The next ordinary order is then attributed to the wrong person. Use an explicit handover: the lead handles or confirms the limited action, then service resumes under personal access.
Test this with a realistic exception, such as a correction requiring permission. Who can see approval occurred? How does the screen return? Can the original colleague continue the normal transaction? Train these steps on the shared device. Access design helps only if the switch is clear enough that no one routinely works under another persons profile.
Hand over open work visibly
Signing out is not the whole handover. A table may remain open, a partial payment may await confirmation and a special request may already have gone to kitchen. The incoming colleague needs transaction status without inheriting another identity or rights. Define a short handover with table number, next action and unresolved questions. Shared order context supports that conversation.
Try a split bill where the serving colleague changes mid-payment. The second person should distinguish the part already paid from the outstanding balance before acting. If card-terminal status is unclear, they must not charge again prematurely. Such details show identity, payment and table context working together. They matter more than merely displaying a name at the top of a screen.
Set up the device environment thoughtfully
A shared tablet may sit open at the bar; another may move between terrace and dining room. Check where sensitive information appears, who can see a passing screen and how devices are kept after service. Staff documents should not be exposed in a public work area. Access settings and physical placement support each other.
Bring two devices and two example roles to a demonstration. Sign in in turn, pass a table over and inspect the screen left for the next person after sign-out. Unclear transitions become visible early. Bonzumo can support personal attribution within shared work; the venue must organise device care, login discipline and understandable handovers. There is less guessing when a transaction later needs explanation.
