A customer pays at a self-ordering kiosk and the screen stops before showing a confirmation. The floor attendant needs to find the original order, check whether payment went through and tell the kitchen whether to start. A useful kiosk recovery plan gives the team those checks in order. With Rewardly, CommerceOS holds the order, PaymentOS provides payment evidence, and LoyaltyOS gives staff a separate record of member activity. In this fictional Singapore café, the manager rehearses that handover before the lunch queue forms.
Find the original order before taking another payment
Move the conversation away from the kiosk so the customer can show their order reference without holding up everyone else. Ask for the time, amount and order number if one appeared. The assigned staff member checks the original order in the POS. A manager can use CommerceOS Order Management to search the outlet and kiosk source, then open the order to review its items and payment entries. The list opens on paid orders by default. Clear that filter to see pending and other states.
A missing receipt does not settle the question. Check the merchant’s configured payment record before you collect money again. For a connected PayNow method, the PaymentOS reports show recorded payments. The PayNow Report filters Paid and Refunded, so an absent row alone cannot resolve an uncertain attempt. If the order and payment records disagree, give the supervisor the order reference, amount, time and method. Tell the guest who is checking and when you will update them.
Set up pay at counter before you need it
The Rewardly kiosk guide describes a configured Pay at Counter option for eligible Quick Service outlets. It needs a supported app version, an open register shift and a new dine-in or takeaway order with an amount due and no payment applied. If the customer has already used points or store credit on the order, this handover is unavailable. With an eligible handover, the kiosk shows the order number and Payment pending. The cashier uses that order to collect payment, and preparation waits until payment is confirmed.
Rehearse a failed handover as well as a successful one. The kiosk requires a connection for ordering and payment. When a connection drop leaves the handover unconfirmed, staff should check the order on the POS before opening another order or starting another payment. If the outlet cannot see the original record, use the approved exception procedure and let the supervisor confirm the next step. Avoid promising a collection time until the team knows which order the kitchen should prepare.

Check the member’s reward separately
Suppose a member intended to use points when placing lunch. Check the existing order first for a partial payment or an applied benefit, then review the member’s History & Transactions where staff have access. LoyaltyOS calculates earned points after payment. Verify the recorded earning or redemption before offering a manual adjustment. Explain the confirmed outcome and who will follow up on any unresolved benefit. A second loyalty adjustment can create another discrepancy even if the payment issue is already resolved.
Give the kitchen one clear instruction
Agree who can say that preparation should start. The floor attendant identifies the case, the cashier or manager confirms the order and payment, and the kitchen follows the release instruction from that person. For example, one guest used the kiosk while another staff member took the same meal request verbally. Identify which order the team will fulfil before anyone sends a second ticket. When a bag is ready, use the agreed pickup reference to match it to the guest. The next shift needs the original order reference and a clear next action if the case is still open.
Write the fallback down before opening the outlet. In CNA’s 10 November 2026 report on the Tappee school meal ordering incident, SATS said it activated continuity arrangements to keep ordering and delivery running. That is a separate case involving school meals. The practical question for a café is who takes over if the usual path stops. The IMDA and Enterprise Singapore Food Services Industry Digital Plan factsheet, updated 16 July 2025, also sets out training and cybersecurity roadmaps alongside digital adoption. Use a short rehearsal with fictional details so staff can practise without exposing customer information.
Give the team a short list of decisions to practise. If payment is confirmed and the kitchen has no ticket, have the lead check whether the order is already being prepared before giving an instruction. If payment is still uncertain, keep the order and the exception visible to the shift lead. If the customer leaves, agree how your store will update them without recording more personal information than it needs. At closing, compare unresolved cases against the merchant’s records and assign each one an owner.
Try one normal order and one interrupted checkout
Run an ordinary kiosk order first. Then repeat with a payment that needs checking and an eligible unpaid order handed to the counter. Ask staff to show the original order, the payment evidence and the member’s transaction history. Record which step required a supervisor, whether the kitchen received one clear instruction, and how the customer was told about the delay. Compare the recovery with your broader kiosk and QR ordering checklist. Bring your outlet type, preferred payment methods and one loyalty offer to a Rewardly demo so the team can test the setup it will actually use.



