Monday
We have a fast paced bar with only one cash drawer. Do any other locations use a "community" POS number for 2-3 employees to use rather than using their own to take orders? They would still clock in and get paid on their own number, but rather than going in and out of pos numbers they would all use one.
Solved! Go to Solution.
yesterday
This is a very common practice, especially in fast-paced environments and QSRs where staff is always bouncing around between front and back of house. As a QSR, we have a "Default Cashier" employee which is the shared employee everyone uses for taking orders at the counter and logging into the KDS. It also acts as the kiosk employee and the online/3rd party auto-fire employee. Basically everything except for clocking in and out, and certain manager-level tasks that require approval. This practice only gets hairy if you aren't using a tip pool for the tips earned by that ghost "employee". If the staff using that login isn't pooling tips, then you may want to save separate stacks of tipped receipts for each employee, and manually reassign the checks to the correct employees after your busy service. If you are pooling, just be careful with the job configuration, and make sure that ghost "employee" is not being allocated any of your staff's hard earned tips 🙂
yesterday
Nick took the words right out of my mouth. This is exactly how we do it at our restaurant minus using tip pooling. We tip out our staff every night in cash, so we manually pool the tips together and divide among the team members. The only issue that i could see arising, is pinning down who did what if you have any issues with card transactions.
yesterday
This is a very common practice, especially in fast-paced environments and QSRs where staff is always bouncing around between front and back of house. As a QSR, we have a "Default Cashier" employee which is the shared employee everyone uses for taking orders at the counter and logging into the KDS. It also acts as the kiosk employee and the online/3rd party auto-fire employee. Basically everything except for clocking in and out, and certain manager-level tasks that require approval. This practice only gets hairy if you aren't using a tip pool for the tips earned by that ghost "employee". If the staff using that login isn't pooling tips, then you may want to save separate stacks of tipped receipts for each employee, and manually reassign the checks to the correct employees after your busy service. If you are pooling, just be careful with the job configuration, and make sure that ghost "employee" is not being allocated any of your staff's hard earned tips 🙂
yesterday
Nick took the words right out of my mouth. This is exactly how we do it at our restaurant minus using tip pooling. We tip out our staff every night in cash, so we manually pool the tips together and divide among the team members. The only issue that i could see arising, is pinning down who did what if you have any issues with card transactions.