A counter may be open while the payment process is not yet ready for the first customer. The tablet has started, but the employee does not know which terminal is connected or where an unclear payment is followed up. A short opening check makes the process predictable. For a Yindle Mollie Terminal pilot, that check covers the agreed order flow, the recognisable workstation and the available support before customers arrive at the counter.
Start with the workstation being used today
In a fictional collection shop, a spare device sits beside the usual terminal. An employee on the morning shift did not work the previous day and does not know which device is active. The opening instructions therefore need to identify the workstation and terminal for the shift. Use recognisable names that match the setup. An employee should not have to guess which device receives the request based on where it sits on the desk.
Then check that the agreed screens are accessible and show the right shop context. This is a normal usage check, not a request to copy keys or technical settings. The existing Yindle terminal component provides a basis for initiating a payment from an order on a connected Mollie terminal. An initial implementation belongs to a defined merchant and location. The exact equipment, roles and supported payment flow must be agreed before that pilot.
Keep the opening checklist short enough for daily use
- The employee recognises the correct order environment and workstation.
- The intended payment device is identifiable and available according to the shop’s own device procedure.
- Open cases from the previous shift have been handed over.
- The contact for an unclear outcome is known.
Only add checks that lead to a specific decision. If a check fails, the employee needs to know the next step. A long list without follow-up mainly turns opening into an administrative exercise. For example, agree that the employee notifies the responsible colleague if the workstation is not recognisable. Do not let an employee improvise with another terminal or a new payment method before the supported route has been established.
Check the first order action too
During preparation, practise with a fictional order how the employee checks the order, amount and selected terminal. This does not have to become a real payment every day. The shop needs to choose its own appropriate checking procedure for hardware and software. A test environment and an actual customer payment are different situations. Keep exercises clearly identifiable so a test order does not unintentionally become an operational instruction to the warehouse or customer communications.
Discuss what “ready for use” means if a payment later has an unclear status. The employee needs to find the correct order and attempt and follow the agreed assessment. A screen message alone must not cause the order to be treated as paid without a verified provider status and matching amount and currency. That principle belongs in the pilot acceptance criteria. The opening checklist then mainly helps employees find the correct route and owner.
Let the morning shift try the checklist themselves
Give the checklist to someone who was not involved in setup and observe where explanation is missing. Update only the relevant points. You can connect the operational working agreements with Yindle Desk; the specific terminal application can be scoped with Yindle. The result is a counter that starts the day with recognisable equipment, a clear order flow and a useful next step when something is not ready yet.