A customer comes to the counter to collect an order and mentions having paid online already. The employee must assess that quickly before starting a terminal request. Handover and payment come together at this point, but are different actions. A well-configured terminal pilot therefore shows which order is being collected and whether its verified payment context indicates any amount still due.
Start with existing order information
In a fictional collection store, the customer paid online yesterday. The goods are ready today and appear on the collection list. A new employee sees the order there and thinks it still needs card payment. This shows why a collection list must not act as payment instructions. The employee must first open the order and assess current payment information under the agreed procedure. Goods still awaiting collection say nothing about an outstanding amount.
Have the customer use their order reference and check an appropriate identifying detail. A payment confirmation they show may provide context, but the store must independently retrieve the correct order and verified payment information. Do not use an isolated screenshot as the sole basis for changing a technical status. The existing Yindle terminal component provides a foundation for order-linked payments; interaction with previously used online payment routes must be designed and tested for your own store.
Make the check's result clear
If the order is demonstrably paid, the employee must be able to proceed to the agreed handover procedure. If uncertainty remains, first assess the existing payment. Make both situations recognisable on screen. A prominent payment button may unintentionally suggest that every opened order needs paying again. The interface must match the actual order context and permissions agreed in the pilot.
Technical payment status should be based on a verified provider outcome with an amount and currency matching the relevant order. That also applies when the customer paid through another supported route. Employees need to know where confirmation comes from and who investigates a discrepancy. The correct next step is then a specific check, not a new terminal attempt to sidestep uncertainty about old information.
Practise with similar collection orders
Create three fictional orders with very similar products: one already paid, one still awaiting payment through your own route and one with an outcome requiring review. Have an employee carry out the counter task without verbal hints. Observe whether they recognise the different next steps. Include a customer who convincingly says they have paid while the employee has not yet found the correct order. The procedure must remain calm and factual then too.
Update the display or instructions where employees trust the wrong cue. Retain the trial as part of acceptance for the collection counter. To discuss how order context and execution fit together, explore Yindle Connect as a starting point. Handling an unclear payment question fits the capabilities around Yindle Desk. The result is that an already-paid customer can go straight to the right collection step, while an unclear status is investigated specifically first.