Vending Machine Customer Instructions: Test the Purchase with a First-Time User

01   /   BUYER NOTES

Start with a realistic purchase task

Choose a task that reflects the location, such as buying a particular drink, selecting a size or collecting a reserved order. Give the participant the task rather than telling them which buttons to press. A rehearsed demonstration can hide problems because the demonstrator already knows the sequence.

Use the intended product catalogue, payment configuration and language. A test with placeholder names or a special demonstration menu may miss the very distinctions customers need. Where real payments are involved, organise the test through the operator’s authorised process and keep the transaction identifiable.

Observe without collecting unnecessary personal information. You usually need the points where a participant hesitated, the message they interpreted and whether they completed the task. A practical note such as “looked for a collection button after payment” can be more useful than a long recording with no analysis.

02   /   BUYER NOTES

Check whether the first action is obvious

Look at the machine from the customer’s approach. They may see a promotional screen, physical products, a payment terminal and a collection door at once. Determine whether the interface makes clear which element starts the purchase and whether the next step follows the customer’s expectation.

Keep instructions close to the action they describe. A small notice on the side panel may not help a person looking at the screen. Use the supported interface and the venue’s sign guidance to place information where it is needed, without covering labels, controls or required notices.

Avoid multiple competing instructions. If one sign says to select first and another suggests presenting a card first, the customer must guess. Confirm the actual workflow with the supplier and align all visible guidance with that sequence.

03   /   BUYER NOTES

Explain waiting states and payment transitions

Some steps take time while the system checks payment, recognises products or prepares delivery. A customer should be able to tell that the process is continuing and whether another action is needed. Review the supported messages rather than leaving a blank or ambiguous pause.

Do not encourage repeated tapping or payment attempts when the first request may still be processing. Ask the provider how pending, cancelled and failed states should be described. The message needs to reflect the actual system state, especially when the outcome is not yet final.

Use clear language for any authorisation hold or later finalisation where applicable. Avoid presenting all payment models as identical. The instructions should match the specific machine and provider arrangement the customer is using.

04   /   BUYER NOTES

Treat collection as part of the interface

Watch where the customer looks after the transaction progresses. A collection opening may be visually obvious to the operator but unfamiliar to a new user. Check whether the person can identify the correct opening, retrieve the product and understand that the purchase has finished.

For lockers or multiple-item orders, demonstrate the complete sequence. A customer may need to collect more than one package or wait for a second delivery. Do not assume the first item appearing means the person understands that more items remain.

Keep physical instructions consistent with the equipment’s approved use. If a door or collection mechanism needs specific handling, use the manufacturer’s guidance. Do not invent a shortcut that requires customers to force or reach into the machine.

05   /   BUYER NOTES

Revise one source of confusion and test again

Turn observations into specific changes: clarify a prompt, distinguish two products, move a permitted sign or explain a waiting state. Record what changed and which task will verify it. “Make the interface easier” is too broad to establish whether the revision worked.

Repeat the task with someone unfamiliar with the earlier version where practical. A participant who has already learned the process may succeed from memory even if the revised instruction is still unclear. Keep conclusions proportionate to the small test and continue reviewing real support questions after launch.