By Eric Kuvykin. Substantially revised October 17, 2026. The original publication date and URL are retained.
Define what must survive the shift change
A busy point-of-sale operation needs more than a new employee signing in. The next shift must know which orders are open, which customer promises remain unresolved and whether any payment exception needs a manager. Build the handoff around those items rather than a broad instruction to “check the register.”
Keep the procedure short enough to use during ordinary service. It should identify the source screen for each item, the person accepting responsibility and the reference needed to find it later. A handwritten description without an order or payment reference can create more confusion.
Separate employee access from drawer responsibility
Use named accounts where supported and confirm that each person can perform only the necessary actions. Record how a supervisor approves refunds or price overrides. Do not make sharing a manager’s credentials the normal way to keep a queue moving.
Ask the provider to demonstrate its supported closeout process, including corrections. Determine how the system records an action performed by one employee and approved by another. The payment-security discussion should include people and process as well as the device itself.
Create an exception handoff
List unresolved refunds, uncertain payment attempts, uncollected orders and customer callbacks. For each, record the next step and owner. Avoid recording card details in a shift book or shared chat. Point staff to the approved system and transaction reference.
For a Florida location using seasonal employees, rehearse the procedure before the busiest period. Include a scenario in which an employee leaves unexpectedly and another person must finish the day. This is a staffing example, not a claim that a particular POS is designed for seasonal demand.
Review the handoff after the close
Compare the closeout report with the exception list and any separately approved adjustments. Investigate differences without assuming the cause is misconduct. A training gap, missed refund or reporting cutoff may require a different remedy from an access problem.
Keep records of unresolved issues in the operating system until they are closed. A completed shift should not make an outstanding customer promise disappear. Confirm that a manager reviews items carried across more than one shift.
When the business changes software or roles, repeat the handoff test. A useful POS procedure lets employees serve customers confidently while preserving a clear trail of approvals, corrections and unfinished work.
References and related reading
Primary resource checked for this review: PCI Security Standards Council’s merchant resources. Confirm the current requirements and implementation with the responsible provider or appropriate adviser.
Continue with Choosing a POS System: Test the Full Workday Before Signing and Payment Cybersecurity: Protect Access, Device Changes and Recovery.
For state and local business resources alongside this operating checklist, use the Florida business operations guide on All State Merchants.
