Daily internet cafe operations checklist

Before the first customer

Check the shop from both sides: what staff see in the portal and what a customer sees on a PC.

• Confirm expected stations are online and have the correct names or seat numbers.
• Investigate an unexpected active session before assigning its PC to a new customer.
• Review the rates and any scheduled changes for the day.
• Check the customer lock screen and run a short session after an installation or significant update.
• Confirm staff can sign in with their own accounts and access their assigned work.

During the shift

Confirm the PC or player before every top-up. Guest and account balances are separate, and the right amount applied to the wrong destination still creates a counter problem.

In Cloud Timer, monitor supported request queues such as orders, redemptions, reservations, and staff requests. Read the request details before marking work complete. A zero count means no pending items in that queue, not proof that every part of the shop has been checked.

Keep checkout consistent. Review the session, confirm the amount, record the payment through the intended workflow, and verify the PC is ready for the next customer.

At closing or shift handover

Use the reporting and history views available in your product to compare activity with the shift's collections. Select the intended date range and account for the shop's local time when reviewing records.

Session usage, top-ups, and product payments describe different events. Avoid adding every displayed total together without checking what it includes. Investigate unusual adjustments or unmatched payments while staff can still explain the transaction.

• Review sessions that remain active and hand them over explicitly.
• Review pending requests and purchases awaiting completion.
• Check credit adjustments and unusual activity in the available logs.
• Record unresolved issues with the PC name, time, and action involved.
• Review your backup arrangement before making installation or configuration changes.

What an owner should review regularly

Look for repeat problems: PCs frequently offline, rates staff cannot explain, top-ups applied to the wrong balance, or requests left pending. Use those patterns to decide whether the next improvement should be training, configuration, or hardware maintenance.

When a workflow is unclear, repeat it on a test PC and document the expected result for staff. For product support, include the relevant version and a specific example rather than only a total from the end of the day.